Related
Hi all,
I've been tracking this thing down all day to absolutely no avail. The main reason I'm after it is I've heard it changes the partition layout to enable a larger /data partition (Essentially turns the phone into a KIS 3).
The download links Comebuy are all completely down it seems, I've even tried using Wayback Machine but that's not coming up with much good either.
Does ANYONE have these tools - as I said, the one for flashing Android to the phone?
Thanks a lot everyone!
Hi.
I have the Open C upgrade tool zip. Is that what you need?
I've uploaded all Open C / Kis 3 Windows flash tool firmwares here. https://drive.google.com/folderview?id=0B9Xj0WNW4yX4b2tOXzFjN1RDRmc&usp=sharing#list
Also see Stock ROMs thread over at MoDaCo for regular firmware updates. http://www.modaco.com/forums/topic/373101-zte-kis-3-zte-open-c-stock-roms/
KonstaT said:
I've uploaded all Open C / Kis 3 Windows flash tool firmwares here. https://drive.google.com/folderview?id=0B9Xj0WNW4yX4b2tOXzFjN1RDRmc&usp=sharing#list
Also see Stock ROMs thread over at MoDaCo for regular firmware updates. http://www.modaco.com/forums/topic/373101-zte-kis-3-zte-open-c-stock-roms/
Click to expand...
Click to collapse
Will these work even if the device won't boot? I can't enable debug mode if I can't get past boot screen.
johnnynmonic said:
Will these work even if the device won't boot? I can't enable debug mode if I can't get past boot screen.
Click to expand...
Click to collapse
Why doesn't the device boot? What happened?
If you can boot to recovery (volume up + power) you can flash a firmware package. If you have Firefox OS bootloader you can boot directly to bootloader with volume down + power key combination and use fastboot to flash/boot recovery image first. I doubt Windows flasher will recognize your device.
KonstaT said:
Why doesn't the device boot? What happened?
If you can boot to recovery (volume up + power) you can flash a firmware package. If you have Firefox OS bootloader you can boot directly to bootloader with volume down + power key combination and use fastboot to flash/boot recovery image first. I doubt Windows flasher will recognize your device.
Click to expand...
Click to collapse
I don't know what happened, it belongs to my friend's daughter. She said she ran it down to 0% battery, then it never would boot up again. It SOMETIMES will boot as far as a welcome screen to set up language, but then says settings failed to start, exchange failed to start. I can't seem to get it into fastboot, but I can get it into recovery. Have tried flashing from sd, and via adb. Any image always fails. Have tried to load stock .zip images and even twmp and cwm, everything fails with either improper signature or footer. So not the end of the world, it's not even my phone, but I'm a chronic fiddler/tinkerer, and the fact that I can't make it work is maddening . Thanks for any tips.
johnnynmonic said:
I don't know what happened, it belongs to my friend's daughter. She said she ran it down to 0% battery, then it never would boot up again. It SOMETIMES will boot as far as a welcome screen to set up language, but then says settings failed to start, exchange failed to start. I can't seem to get it into fastboot, but I can get it into recovery. Have tried flashing from sd, and via adb. Any image always fails. Have tried to load stock .zip images and even twmp and cwm, everything fails with either improper signature or footer. So not the end of the world, it's not even my phone, but I'm a chronic fiddler/tinkerer, and the fact that I can't make it work is maddening . Thanks for any tips.
Click to expand...
Click to collapse
I assume it was running Firefox OS? On Firefox OS bootloader it just hangs on Firefox splash screen when you've booted to bootlader. Do you have proper fastboot drivers installed? ZTE uses generic Google mode for fastboot (18d1:d00d - e.g. USB driver from Android SDK works I've been told).
Stock recovery only allows you to flash matching stock firmware (and packages that are signed with ZTE's private keys). If you can get to bootloader you can flash/boot any recovery (stock or custom) and use it to flash firmware.
KonstaT said:
I assume it was running Firefox OS? On Firefox OS bootloader it just hangs on Firefox splash screen when you've booted to bootlader. Do you have proper fastboot drivers installed? ZTE uses generic Google mode for fastboot (18d1:d00d - e.g. USB driver from Android SDK works I've been told).
Stock recovery only allows you to flash matching stock firmware (and packages that are signed with ZTE's private keys). If you can get to bootloader you can flash/boot any recovery (stock or custom) and use it to flash firmware.
Click to expand...
Click to collapse
Thank you for taking the time to reply. I got it to get to the language selection (where it hangs if I can get it to boot that far). I plug it into the USB, and on the phone select connect to pc via software - then adb was able to detect it as a device. From there did: adb reboot bootloader, and once there was able to use fastboot to install cwm. From CWM was able to flash the EU_FFOS-Android kitkat rom. Works fine now. I see you've spent actually quite a bit of time making different roms and tutorials for theses ZTE phone in various forums. Thanks for sharing your knowledge with the community.
edit: I don't think it had FFOS. vol down+power never seemed to do anything (just perpetual bootsplash). Recovery failed to flash even stock roms (I'm in Thailand, downloaded the stock rom you linked to in another forum, also the stock UK rom. Always returned an error about the footer).
So I gave my IMEI, serial number and $5 to someone on the internet, and in return I got an email attachment to flash to my phone. So I did, and it unlocked the bootloader. Strangely enough, now I'm getting a stupid yellow message that my device is unlocked and can't be trusted, and it's a bit of a roundabout way to get into bootloader or recovery. One ONLY works with buttons, the other ONLY with adb.
Ok, never mind, so I tried installing both the 3.1.1. and 3.2.1 of TWRP custom recovery, but I am unable to boot into it to make it stick. On top of that, my phone now says "encrypted"? WTF?
Clearly this latest incarnation of Nokia is a bunch of asswipes, offering us Sophie's choice instead of just unlocking the damn things from the start, so there's no point in asking them for help, but I'd expect members here would be able to help?
Any ideas how to proceed? Is there a factory ROM somewhere? This is 7.1.2. by the way, I'm not interested in updating. Come to think of it, I hate this so-called "progress" with convoluted "security" and whatnot. Just give me the damn phone and go away, Google+Nokia. Stick your "features" up ya clacker.
1. Okk first you jeed to go this link and download official recovery for nokia 5 running android 8.1 oreo
https://drive.google.com/file/d/1Cl1...w?usp=drivesdk
2. Rename it to twrp and give the command to flash the recovery.
3. After give command fastboot flash recovery twrp.img. Give the command fastboot boot twrp.img
And boooom you enter in official twrp
Jitender Baloda said:
1. Okk first you jeed to go this link and download official recovery for nokia 5 running android 8.1 oreo
https://drive.google.com/file/d/1Cl1...w?usp=drivesdk
2. Rename it to twrp and give the command to flash the recovery.
3. After give command fastboot flash recovery twrp.img. Give the command fastboot boot twrp.img
And boooom you enter in official twrp
Click to expand...
Click to collapse
Link broken. File doesn't exist
Try this
https://drive.google.com/file/d/1Cl1yV7tV_VsIC3XIWlCIJXmFfdDZGUbG/view?usp=drivesdk
Err... no, not quite.
1. Your link is (was) dead, but in any case I'd be wary of installing something stashed in a private Google drive folder... Thanks, but no thanks.
2. I have several versions of TWRP, that's not a problem.
3. I know the correct commands (yours are not), that's not a problem.
And boom - no, you don't end up in TWRP. You end up in system, because it overwrites the TWRP automatically UNLESS you reboot to it immediately after flashing, and THIS is the problem.
It turns out that Nokia needs to be plugged into CHARGER, not the PC, then holding Vol+ and Power button combination will do it. It took me more than a dozen tries, but it worked in the end.
Hi, I had the same problem. I've unlocked bootloader and I successfully installed TWRP and I can go to recovery but the problem is I can't boot the system as it stucks on download mode. Can you help?
Press volume up+volume down+power button at the same time for 7-8 second.
TWRP Custom Recovery for the Onn Android Tablet series​
This is the first fully-featured custom recovery for Walmart's MediaTek-based Onn tablets: ONA19TB002, ONA19TB003 and ONA19TB007. TWRP needs no introduction. If you have come here, you probably have some idea of what it is and what it's used for. This TWRP build does not need the bootloader unlocked or VBMeta verification disabled, although it's recommended that you at least unlock the bootloader.
DISCLAIMER
Everything described in this thread is done at your own risk. No one else will be responsible for any data loss, corruption or damage of your device, including that which results from bugs in this software.
FEATURES
Decrypted data partition
All USB modes functional: MTP, ADB, Mass Storage, OTG, Charging
Fast boot time
Adoptable storage mounting
Firmware image backup and restore
Works under locked bootloader
Android 9 build fits within the 16MB recovery partition -- no compromises or partition resizing necessary
INSTALLATION METHOD 1
Download the recovery to your PC and unzip the image
Unlock the bootloader (skip if you have already done this)
Enable OEM Unlock in Developer Options in Android Settings
Boot into fastboot mode either by holding vol. up+power to power it on and selecting "Fastboot mode", or by running the 'adb reboot bootloader' command from within Android.
Install fastboot and appropriate drivers on your PC if you have not set those up
Unlock the bootloader with the command
Code:
fastboot flashing unlock
...and follow the instructions on the screen. This will wipe your data.
Flash the custom recovery with
Code:
fastboot flash recovery twrp-3.3.1-ONA19TB002.img
(use the right file name path for your device)
Reboot to recovery with
Code:
fastboot oem reboot-recovery
INSTALLATION METHOD 2
This assumes you are familiar with SP Flash Tool or can figure it out on your own
Download the recovery to your PC and unzip the image
Get the appropriate scatter file for your device. The scatter file may be found in the device's firmware under /system/data/misc.
Set up SPFT Download tab as Download Only. Load your scatter file.
Under the recovery line, double-click Location and open your TWRP image.
Click Download and connect your powered-off tablet to your PC. SPFT will automatically flash the recovery to the emmc and disconnect when finished.
INSTALLATION METHOD 3
Head over to Amazing Temp Root for MediaTek ARMv8, read the requirements and directions, and grab the latest mtk-su.
Open a root shell with mtk-su
Flash the (unzipped) recovery with the command:
Code:
dd bs=1048576 if=twrp-3.3.1-0-ONA19TB002.img of=/dev/block/by-name/recovery
(replace the if= file name with your appropriate recovery image path)
Exit root shell
START RECOVERY
Three methods:
On a powered off tablet, hold Vol. up+power for about 3 seconds. In the menu that appears, select "Recovery mode"
With Android ADB, use the command 'adb reboot recovery'
From Android root shell, use the command 'reboot recovery' or just use any root app with OS reboot features
NOTES
Kind of important: Make a backup of your Crypto Footer as soon as you can. This is the encryption key to your data partition. When accessed from TWRP, this key can get "upgraded" so that you will get locked out of Android. TWRP uses a hacky workaround that saves and restores the original footer on every /data decrypt. But that method is not what I would call 100% reliable.
Make sure you have a backup of the untouched stock system and vendor images. There are no official firmware packages available to download.
Only mount system/vendor partitions in read/write mode if you have unlocked the bootloader. It is recommended to choose to leave system read-only at the startup prompt unless you have a specific reason to modify it. If the bootloader is locked, then dm-verity is enforced.* So merely mounting it once in r/w will cause a boot loop.
It's currently not possible to install incremental OTA updates using this TWRP. Use the stock recovery to update the FW. That will only work if you have never mounted system/vendor in write mode.
DOWNLOAD (Nov. 30, 2019)
Current version: 3.3.1-1
ONA19TB002 - Onn 8" model
ONA19TB003 - Onn 10.1" model
ONA19TB007 - Onn 10.1" w/keyboard model
Source code
ONA19TB002 | ONA19TB003 | ONA19TB007
ACKNOWLEDGEMENTS
The team behind TWRP & OmniROM
@tek3195 for testing and feedback on the 8" model
Please post feedback since these are still pretty new and not exhaustively tested. Let me know if I should port it to other models in the series.
Reserved also
grabbing this one too cuz why not
Very nice! I'll download and test the 003 one soon.
I also have a 007 model to experiment with.
I tried about a dozen times to build TWRP and failed miserably LOL. Closest I got was one that would boot but the rotation was all messed up, USB wouldn't work, didn't mount some partitions... Yeah, it was a hot mess.
Do you happen to have sources available?
Hi @NFSP G35,
I'll have the source code soon. Most of the tricks involved patching bootable/recovery. So I need to commit those changes and include the proper patch set from my tree....
Amazing!! Gonna install and test 8" right now.
Has anyone tried a GSI on these tablets yet?
MishaalRahman said:
Has anyone tried a GSI on these tablets yet?
Click to expand...
Click to collapse
I do know @tek3195 , the Onn 8 thread starter, has tried many of them as well as others here, somewhere on that thread he listed his tests and opinion of several of them.
I'm pretty sure others on that thread have also tried GSI's.
MishaalRahman said:
Has anyone tried a GSI on these tablets yet?
Click to expand...
Click to collapse
I did try both Phhuson vanilla and also Liquid Remix (I'm keeping this one for now). I didn't flash them through twrp, but using fastboot via bootloader.
WoW! AwEsOmE! I cannot wait to try this! THANK YOU!!!!!!
Hey,
This is a neat thing to see for the Onn tablets. I have a question though. I own a device based on the mt8163, and am trying to help people with another device I don't own (the powkiddy x18 which also uses the mt8163). One of the things I wanted to do was to make a custom rom for the x18, since it's stock firmware is horrible. And of course, one of the first steps to custom roms is twrp. So I have a question for you that I hope you can answer for me. How did you make this build of twrp? I have seen no device trees for this device so I was kinda curious. If you can help me in any way, I'd be so grateful, and I'm sure the other people with the x18 would be grateful for help.
@diplomatic
Is there a different procedure for installing TWRP on a locked bootloader?
I can confirm that using SP Flash to load your TWRP.img will produce a bootloop when installing to a device with the BL locked. Reflashing the original recovery.img makes the problem go away. You mentioned in the OP that this TWRP will work on a locked BL so I thought I would share my case study with you in following the procedure you defined.
MY SINCERE GRATITUDE FOR YOUR EFFORTS IN PORTING THIS TO THE ONN!
You're welcome, @Spatry.... Can you describe how you ended up with a locked BL? Was it unlocked before? Have you ever tweaked vbmeta? Also, when you say bootloop, do you mean for Android or just for recovery? I'm not going to insist that it works under locked BL. I tested it once and it did boot up...
diplomatic said:
You're welcome, @Spatry.... Can you describe how you ended up with a locked BL? Was it unlocked before? Have you ever tweaked vbmeta? Also, when you say bootloop, do you mean for Android or just for recovery? I'm not going to insist that it works under locked BL. I tested it once and it did boot up...
Click to expand...
Click to collapse
Presently, I am running stock with Magisk patched BOOT on locked bootloader, stock vbmeta. The boot loop was at the ONN Android screen, I could not get it to even boot into recovery.
At one time I did run with the bootloader unlocked (with --disable-verification on stock vbmeta) and I ran Phusson's AOSP, Liquid Remix and Bliss. I found there was no benefit to me in running the other mods so I reverted back to stock courtesy of @CaffeinePizza and the bootloader re-locked to get rid of that annoying 5 second orange state.
In each instance, I always used SP Flash tools to load all .img files. I only used fastboot to install magisk_patched.img onto the stock installation. Unlocking the bootloader erases all data and I did not feel like reinstalling everything again, so I figured I would try to install TWRP per your instruction to see if it would work while the BL was still locked... Restoring the original recovery got rid of the bootloop. I do want to try your TWRP so I will try it with BL unlocked when I get some free time to do so.
Spatry said:
Presently, I am running stock with Magisk patched BOOT on locked bootloader, stock vbmeta. The boot loop was at the ONN Android screen, I could not get it to even boot into recovery.
Click to expand...
Click to collapse
This sounds like you might have flashed a wrong/corrupt image to recovery. It may have to do with AVB checks rather than bootloader lock. But those conditions might be interdependent somehow so I can't tell you for sure. The fact that you are able to boot a patched image on a locked BL says it doesn't care too much about verification. I can tell you for sure that any recovery image must have avb metadata, not necessarily the required hash, for both Android and recovery to boot. Can you try to unzip the image file and flash it over again?
Hmm, the situation with the bootloader lock sounds eerily similar to the Nabi SE. The latter also had a similar implementation where there's not much in the way of locking things down, other than an (easily circumvented) SP Flash Tool signature check and different preloader keys. And here's the real kicker: the nearly-identical Fisher Price Nabi also ran on the MT8163, so it makes me wonder if it's possible to boot Pie on it, or perhaps a GSI assuming that Treble can be tacked onto it.
Also, do you have the source repo to this TWRP port of yours?
If anyone here gave me an XDA ad-free subscription, thanks a lot! I didn't get a notification of who it was. Using this site is a lot more bearable now.
diplomatic said:
If anyone here gave me an XDA ad-free subscription, thanks a lot! I didn't get a notification of who it was. Using this site is a lot more bearable now.
Click to expand...
Click to collapse
Where do I find crypto footer to backup
diplomatic said:
If anyone here gave me an XDA ad-free subscription, thanks a lot! I didn't get a notification of who it was. Using this site is a lot more bearable now.
Click to expand...
Click to collapse
Kinda cool without the ads isn't it. I know I sent one about a week ago or so. I think everybody ought to send you one, you deserve it. THANKS and AWESOME work.
I followed step by step: https://clickitornot.com/install-twrp-recovery-and-root-sony-xperia-x-compact/
(the xda guides lingo was hard to understand and follow, I'm a noob at rooting sony phones. I don't have previous knowledge so I followed the above)
-Got stuck in TWRP recovery mode after following the link posted.
-Looked into it and read something about a boot.img missing?
-Downloaded boot.img from here: https://forum.xda-developers.com/x-compact/how-to/stock-8-0-root-recovery-t3747479
-Flashed recovery on boot_32.img via TWRP, now screen stays at white Sony logo. Cannot go into TWRP at all, computer doesn't recognize phone and Sony flash tools does not recognize phone.
I just need this phone to root and turn on so I can get my old photos and conversation back. :crying:
Been stuck for 12 hours...any help is much appreciated!
1 - what do you ultimately want, rooted stock rom, custom rom, or...?
2 - what was the state of your phone when you started, (fully stock, which fw version, etc)?
3 - Did you do anything else to it besides flashing twrp and flashing boot.img?
levone1 said:
1 - what do you ultimately want, rooted stock rom, custom rom, or...?
2 - what was the state of your phone when you started, (fully stock, which fw version, etc)?
3 - Did you do anything else to it besides flashing twrp and flashing boot.img?
Click to expand...
Click to collapse
1. Anything, I simply just need it to work so I can use a software to get my lost data. In order to get my data back the phone needs to be rooted under the prerequisites for the Dr. Fone software.
2.Fully stock android 8.0
3. No, it was fine and I went through dozens of threads and youtube tutorials. It kept going into TWRP exclusively until I flashed boot.img now it just boot loops or crashes on the white sony screen.
(BTW, my phone finally has been recognized by Flash Tools (Emma). I have updated it via Emma but it has done absolutely nothing.
ThisAintEz said:
1. Anything, I simply just need it to work so I can use a software to get my lost data. In order to get my data back the phone needs to be rooted under the prerequisites for the Dr. Fone software.
2.Fully stock android 8.0
3. No, it was fine and I went through dozens of threads and youtube tutorials. It kept going into TWRP exclusively until I flashed boot.img now it just boot loops or crashes on the white sony screen.
(BTW, my phone finally has been recognized by Flash Tools (Emma). I have updated it via Emma but it has done absolutely nothing.
Click to expand...
Click to collapse
So the whole Emma process completed successfully, but the phone still won't boot? That's strange, because Emma usually overrides everything, (including your userdata, I think, so if you wanted to save it, that may have been the wrong thing to do). If all you did was flash a bad boot img, then re-flashing stock fw should solve the problem, but you might lose your data with Emma, so Androxyde Flashtool might be better choice, since it gives you the option.
Did you unlock the bootloader? If not, then nothing is going to work. If you did, then it will be easy to get the phone booted again...
levone1 said:
So the whole Emma process completed successfully, but the phone still won't boot? That's strange, because Emma usually overrides everything, (including your userdata, I think, so if you wanted to save it, that may have been the wrong thing to do). If all you did was flash a bad boot img, then re-flashing stock fw should solve the problem, but you might lose your data with Emma, so Androxyde Flashtool might be better choice, since it gives you the option.
Did you unlock the bootloader? If not, then nothing is going to work. If you did, then it will be easy to get the phone booted again...
Click to expand...
Click to collapse
The phone itself has been factory reset (long story short x compact said my password was incorrect and factory reset, itself after numerous tries, even though I only have one password) so I know my info is gone but the software can get the most of the things I want.
Yes, boot loader is unlocked. I have basically rooted it but the last step of actually getting to use it is out of reach.
ThisAintEz said:
The phone itself has been factory reset (long story short x compact said my password was incorrect and factory reset, itself after numerous tries, even though I only have one password) so I know my info is gone but the software can get the most of the things I want.
Yes, boot loader is unlocked. I have basically rooted it but the last step of actually getting to use it is out of reach.
Click to expand...
Click to collapse
For TWRP recovery, you need to flash via fastboot. I wasn't clear what you were saying about how you did it before. You should,
- Download TWRP img file (there is official TWRP for xc, so download the latest from TWRP site)
- Open command prompt in the directory you downloaded it to
- Connect the phone in fastboot mode, (power off > hold volume up while connecting cable and don't let go of the button until you see blue led)
- Type
Code:
fastboot flash recovery (name of file).img
Then you can boot into recovery by powering off, and holding volume down while powering on. Then do a reset in recovery.
Now you'll need to flash a boot img...
You said it was stock 8.0, but do you know if it was the latest update? (fw ending in. 118) If so, and if your system files are still intact, then you should be able to download this - https://mega.nz/#!14VkzCCB!GK-KEv0A-ZyhysXc1-IusyJjJEB-D5ZWOLm1DRt31tA - (it's a boot img), and flash it with fastboot. So,
- Download the boot img file
- Open a command prompt in the directory you downloaded it
- Connect the phone in fastboot mode, (power off > hold volume up while connecting cable and don't let go of the button until you see blue led)
- Type in command prompt,
Code:
fastboot flash boot (name of file).img
- Reboot
I'm assuming that since you used Emma already that you have drivers installed, so should work. If the commands complete successfully, but your phone still doesn't boot, then probably system is messed up, and you'll have to flash a new rom.
levone1 said:
For TWRP recovery, you need to flash via fastboot. I wasn't clear what you were saying about how you did it before. You should,
- Download TWRP img file (there is official TWRP for xc, so download the latest from TWRP site)
- Open command prompt in the directory you downloaded it to
- Connect the phone in fastboot mode, (power off > hold volume up while connecting cable and don't let go of the button until you see blue led)
- Type
Code:
fastboot flash recovery (name of file).img
Then you can boot into recovery by powering off, and holding volume down while powering on. Then do a reset in recovery.
Now you'll need to flash a boot img...
You said it was stock 8.0, but do you know if it was the latest update? (fw ending in. 118) If so, and if your system files are still intact, then you should be able to download this - https://mega.nz/#!14VkzCCB!GK-KEv0A-ZyhysXc1-IusyJjJEB-D5ZWOLm1DRt31tA - (it's a boot img), and flash it with fastboot. So,
- Download the boot img file
- Open a command prompt in the directory you downloaded it
- Connect the phone in fastboot mode, (power off > hold volume up while connecting cable and don't let go of the button until you see blue led)
- Type in command prompt,
Code:
fastboot flash boot (name of file).img
- Reboot
I'm assuming that since you used Emma already that you have drivers installed, so should work. If the commands complete successfully, but your phone still doesn't boot, then probably system is messed up, and you'll have to flash a new rom.
Click to expand...
Click to collapse
Thank you, the good news is I can finally get back into TWRP, so that's a relief! I appreciate you for saving me there!
I followed the instructions with the boot.img with the following script
max download size of 536870912 bytes
sending 'boot' (17220 KB)...
OKAY [ 0.556s]
writing 'boot'...
OKAY [ 0.113s]
finished. total time: 0.673s
But I'm back to square one with the screen prompt "your devices has been unlocked and cant be trusted. Your device will boot in 5 sec" with the Sony white screen back to the "your device has been unlocked" screen and then it freezes at the Sony white screen. The only way i can turn off my phone from here is Power button + volume up
ThisAintEz said:
Thank you, the good news is I can finally get back into TWRP, so that's a relief! I appreciate you for saving me there!
I followed the instructions with the boot.img with the following script
max download size of 536870912 bytes
sending 'boot' (17220 KB)...
OKAY [ 0.556s]
writing 'boot'...
OKAY [ 0.113s]
finished. total time: 0.673s
But I'm back to square one with the screen prompt "your devices has been unlocked and cant be trusted. Your device will boot in 5 sec" with the Sony white screen back to the "your device has been unlocked" screen and then it freezes at the Sony white screen. The only way i can turn off my phone from here is Power button + volume up
Click to expand...
Click to collapse
So now you can just decide if you want to go the route of stock rom or custom. Quickest choice to get the phone booted would probably be Omni or something. Just download the rom, download the oem file, and flash in fastboot. Check the Omni threads in "Roms" forum... If you wanted to go stock, I would suggest Androxyde Flashtool, but would be a few more steps... Or you could try Emma again...
levone1 said:
So now you can just decide if you want to go the route of stock rom or custom. Quickest choice to get the phone booted would probably be Omni or something. Just download the rom, download the oem file, and flash in fastboot. Check the Omni threads in "Roms" forum... If you wanted to go stock, I would suggest Androxyde Flashtool, but would be a few more steps... Or you could try Emma again...
Click to expand...
Click to collapse
I tried Emma again but my phone is still frozen on the white Sony screen. I checked out the ROM threads but the "download weekly" links are down for both Pie 9.0 and Oreo 8.1
ThisAintEz said:
I tried Emma again but my phone is still frozen on the white Sony screen. I checked out the ROM threads but the "download weekly" links are down for both Pie 9.0 and Oreo 8.1
Click to expand...
Click to collapse
Strange - I wonder what's going on... I might have a zip I can upload. Meanwhile, maybe try Lineage - https://forum.xda-developers.com/x-compact/development/rom-lineageos-16-0-xperia-x-compact-t4080903
levone1 said:
Strange - I wonder what's going on... I might have a zip I can upload. Meanwhile, maybe try Lineage - https://forum.xda-developers.com/x-compact/development/rom-lineageos-16-0-xperia-x-compact-t4080903
Click to expand...
Click to collapse
Thank you for your help! I checked out the thread but I'm not advanced enough to understand the steps without it being written out as I'm still new to this. Is their any links or tutorials you would recommend? My apologies!
ThisAintEz said:
Thank you for your help! I checked out the thread but I'm not advanced enough to understand the steps without it being written out as I'm still new to this. Is their any links or tutorials you would recommend? My apologies!
Click to expand...
Click to collapse
- Download the zip - https://drive.google.com/open?id=14iXmvLOMXLoZdJoCahcRhBzbUr1Eu7gw (There are 2 options, just pick one - one's a little newer)
- Copy to phone's SD card
- Boot to recovery
- Choose "wipe data/factory reset"
- Choose "install", and select the zip file you downloaded
- Reboot
There are more options, but I think you want to just get the phone to boot at this point. You can do more later if you want...
BTW - what is happening when you flash with Emma? I haven't seen it ever flash successfully, but not work on the phone. Are you getting errors?
levone1 said:
- Download the zip - https://drive.google.com/open?id=14iXmvLOMXLoZdJoCahcRhBzbUr1Eu7gw (There are 2 options, just pick one - one's a little newer)
- Copy to phone's SD card
- Boot to recovery
- Choose "wipe data/factory reset"
- Choose "install", and select the zip file you downloaded
- Reboot
There are more options, but I think you want to just get the phone to boot at this point. You can do more later if you want...
BTW - what is happening when you flash with Emma? I haven't seen it ever flash successfully, but not work on the phone. Are you getting errors?
Click to expand...
Click to collapse
Much appreciated! I will try that out soon. Regarding Emma it seems pretty useless, unless I'm missing something. Every time I use it, it says it's successful but nothing changes.
LEVONE1 YOU ARE THE MAN!!! I cannot thank you enough! It worked! You made my day, I appreciate your patience and willingness to help a stranger out even when you didn't have to!
ThisAintEz said:
LEVONE1 YOU ARE THE MAN!!! I cannot thank you enough! It worked! You made my day, I appreciate your patience and willingness to help a stranger out even when you didn't have to!
Click to expand...
Click to collapse
Glad to hear it... It's been done for me more than once, so....
Maybe your happy with Lineage, but if you're feeling ambitious, you can start messing around with Androxyde Flashtool, and getting back to stock, and you can try my eXistenZ port - https://forum.xda-developers.com/x-compact/themes/existenz-xc-t3867917 - I think eXistenZ is the best rom for this phone, (probably for Sony phones overall). The downside is that it is based on stock, so no updates since 2018 for XC...
The processes are a bit more complicated, so might take some time / learning to get it down, but with TWRP, you can always make a quick backup, and flash right back to where you were any time...
levone1 said:
Glad to hear it... It's been done for me more than once, so....
Maybe your happy with Lineage, but if you're feeling ambitious, you can start messing around with Androxyde Flashtool, and getting back to stock, and you can try my eXistenZ port - https://forum.xda-developers.com/x-compact/themes/existenz-xc-t3867917 - I think eXistenZ is the best rom for this phone, (probably for Sony phones overall). The downside is that it is based on stock, so no updates since 2018 for XC...
The processes are a bit more complicated, so might take some time / learning to get it down, but with TWRP, you can always make a quick backup, and flash right back to where you were any time...
Click to expand...
Click to collapse
Will do. Cheers!
i want to move to lineageos from the custom rom, but i have this problem, tried to google solutions in different ways but i can't find people with the same issue.
phone works fine otherwise, but when i have it completetly OFF and try to start it by holding power+voldown keys i go into fastboot (i can tell cuz if i dont touch it it stays on a black screen with lil to no light). and as soon as i press the power key (effectively choosing to do a reboot), it powers off and on and goes on to boot my old config.
btw i have enabled OEM and usb debugging. but i haven't got root access cuz it's my understanding that to get that i need to do some things to it in fastboot hooked up to a pc with ADB minimal.
any ideas?
hello there! I have the exactly same issue here.. Volume DOWN + Power goes to black screen....
However i could find out that it is, indeed entering in the fastboot as i was able to send commands and unlock the bootloader through the CMD.. But now i cannot get to install the TWRP (get some error). Did you solved it? anyone can help?
alexestanislau said:
hello there! I have the exactly same issue here.. Volume DOWN + Power goes to black screen....
However i could find out that it is, indeed entering in the fastboot as i was able to send commands and unlock the bootloader through the CMD.. But now i cannot get to install the TWRP (get some error). Did you solved it? anyone can help?
Click to expand...
Click to collapse
i just figured it out, what commands are u using to install twrp?
well, for anyone in the future wondering about this **** u gotta make sure the usb port in your pc is 2.0, a 3.0 will return failed access to the unlock data or the flash boot command for twrp
and u gotta use >fastboot flash boot ''twrp file name''.img
also, for this specific model evert or moto g6 plus if u using the lineage official release make sure the number after the mindthegapps file matches your version of android, i ****ed that up many times until i realized i was trying to install MTG 10 in android 13. what a ****head am i!
oh, and finally if u are in fastboot and can't see anything, the path to recovery (and hopefully twrp) is to press 2 times voldown and 1 time power
vesp9 said:
well, for anyone in the future wondering about this **** u gotta make sure the usb port in your pc is 2.0, a 3.0 will return failed access to the unlock data or the flash boot command for twrp
and u gotta use >fastboot flash boot ''twrp file name''.img
also, for this specific model evert or moto g6 plus if u using the lineage official release make sure the number after the mindthegapps file matches your version of android, i ****ed that up many times until i realized i was trying to install MTG 10 in android 13. what a ****head am i!
oh, and finally if u are in fastboot and can't see anything, the path to recovery (and hopefully twrp) is to press 2 times voldown and 1 time power
Click to expand...
Click to collapse
Also, in other topic they pointed out that some Moto G6 Plus have only ONE partition, so you cannot FLASH a recovery (because they dont have a partition for that).. you can ONLY boot on TWRP, if you Flash the TWRP on the partition you cant have a OS at same time..
vesp9 said:
well, for anyone in the future wondering about this **** u gotta make sure the usb port in your pc is 2.0, a 3.0 will return failed access to the unlock data or the flash boot command for twrp
and u gotta use >fastboot flash boot ''twrp file name''.img
also, for this specific model evert or moto g6 plus if u using the lineage official release make sure the number after the mindthegapps file matches your version of android, i ****ed that up many times until i realized i was trying to install MTG 10 in android 13. what a ****head am i!
oh, and finally if u are in fastboot and can't see anything, the path to recovery (and hopefully twrp) is to press 2 times voldown and 1 time power
Click to expand...
Click to collapse
Tried to do that, but stills black screen after 2 volume down plus power
alexestanislau said:
Tried to do that, but stills black screen after 2 volume down plus power
Click to expand...
Click to collapse
u want to enter twrp? make sure a copy of the file its on sd and do ''fastboot devices'' first to make sure connection is ok. then ''fastboot boot (twrp.img)''
changing twrp.img to the exact name of your file. on usb 2.0 or it won't work
vesp9 said:
well, for anyone in the future wondering about this **** u gotta make sure the usb port in your pc is 2.0, a 3.0 will return failed access to the unlock data or the flash boot command for twrp
and u gotta use >fastboot flash boot ''twrp file name''.img
also, for this specific model evert or moto g6 plus if u using the lineage official release make sure the number after the mindthegapps file matches your version of android, i ****ed that up many times until i realized i was trying to install MTG 10 in android 13. what a ****head am i!
oh, and finally if u are in fastboot and can't see anything, the path to recovery (and hopefully twrp) is to press 2 times voldown and 1 time power
Click to expand...
Click to collapse
I have the same issue.
After it boots into TWRP, the screen correctly display TWRP or is still black?
Tiki Thorsen said:
I have the same issue.
After it boots into TWRP, the screen correctly display TWRP or is still back?
Click to expand...
Click to collapse
it correctly displays TWRP, it's black just in fastboot.
u can use adb while in fastboot to order it to boot twrp, that's how i did it. or i guess u could hypothetically make it go into recovery mode (twrp if installed) by moving blindly using vol + or - but i'm not sure.
vesp9 said:
it correctly displays TWRP, it's black just in fastboot.
u can use adb while in fastboot to order it to boot twrp, that's how i did it. or i guess u could hypothetically make it go into recovery mode (twrp if installed) by moving blindly using vol + or - but i'm not sure.
Click to expand...
Click to collapse
Oh that's a relief! I was planing unlock the bootloader and flash LineageOS this weekend. I will report back how it goes.
Tiki Thorsen said:
Oh that's a relief! I was planing unlock the bootloader and flash LineageOS this weekend. I will report back how it goes.
Click to expand...
Click to collapse
remember to use usb 2.0 (not 3.0). this made me waste so much time
vesp9 said:
remember to use usb 2.0 (not 3.0). this made me waste so much time
Click to expand...
Click to collapse
Indeed, I struggle with that on my G7 Plus, cheers!
Update; After successfully unlocking the bootloader, I boot to the Pixel Experience recovery and the screen remains black.
But if I boot to TWRP, it does display it correctly.
Tiki Thorsen said:
Update; After successfully unlocking the bootloader, I boot to the Pixel Experience recovery and the screen remains black.
But if I boot to TWRP, it does display it correctly.
Click to expand...
Click to collapse
i'm guessing the pixel experience recovery is a custom recovery mode, right? maybe the black screen it's a thing with factory menus? idk
vesp9 said:
i'm guessing the pixel experience recovery is a custom recovery mode, right? maybe the black screen it's a thing with factory menus? idk
Click to expand...
Click to collapse
Yes, is just like the LineageOS recovery.
I always replace the Rom's recovery with TWRP in any case.