Hi,
so I need some help. I recently rooted my phone using SuperSU, and was dumb enough not to make a backup of it before trying to update the stock ROM with Android 8.0 one. I flashed it, and the phone didn't boot. Well, I did a factory reset, and by a mistake, clicked update my phone to stock Android 8.0. I tried to flash TWRP, but it just said "failed (remote: partition length get error)".
So, now I am stuck at non-rooted phone what I cannot root. Any way I could get TWRP?
Still with the same problem :/
Please PM me your phone build number @Vizitys
Related
I wanted to factory reset my phone and I was on marshmallow. I had the update.zip file which I used while upgrading fronm lollipop to marshmallow. I thought that "apply update from sd card" in stock recovery and using that same update.zip would be a better way of doing the Factory Reset. The update's installation was aborted because of Status 7 Error Code and since then my phone is stuck in bootloop. The Moto Logo shows up and an android with the "Erasing" written below it follows and then it goes back and follows the same routine. So how can I restore my phone to stock official firmware on Locked Bootloader? I have never rooted my phone or unlocked the bootloader.
Please Help. I'm dying without my phone.
Since you messed up your phone, at this point you might as well try to flash stock firmware in fastboot. Can't get any worse.
Will he need an unlocked bootloader to be able to fastboot stock? I'm new to Motorolas. But I agree, that you need to follow a typical protocol - applying an update.zip when you are already on the update and you are stock, is not typical. Probably causing the issue. I think you can salvage it, I don't think you cannot recover from it. But I could be wrong. Set up Android SDK and go through the processes you'd need to unlock the bootloader and root. Once you have those set up, you can try to fastboot the lollipop return to stock tool.
Read through the mm release thread. In the beginning there are some posts from locked users who successfully flashed stock firmware to recover from issues.
Hello everyone!
A few days ago I bought myself a P10 plus on a vacation to China. Since I live in Sweden I decided to rebrand it to the European firmware (since it had the asian firmware installed) through FunkyHuawei when I got home. I got my bootloader code from Huawei support and succesfully unlocked it as well as installed TWRP. The first problem I encountered was that I was unable to create any backups of my phone as well as being unable to install or flash anything.
I then restarted my phone into recovery mode and suddenly it didn't boot into TWRP anymore, only EMUI stock recovery. I tried flashing TWRP several times but the phone still wouldn't boot into it, so I tried factory resetting the phone and the flashing TWRP once again. This is where the real problems started.
The firmware is gone, no OS is installed, I cannot do anything through TWRP (i only get error messages such as "E:Unable to find partition size for /boot" as well as Failed to mount /cache (Invalid Argument)")
Even worse is that the bootloader wont load as far as i can tell so I can't do anything through adb nor fastboot either. I'm completely stuck in TWRP. I can't even wipe nor change file system.
Is my phone damaged beyond repair or is there anyone on here that might have a solution?
Thanks in advance, any suggestions welcome!
EDIT: Okay this is really weird...
Suddenly my phone booted into the OS, even though TWRP said there were no OS installed. What is the next step from here to ensure this won't happen again?
Check this thread can help you to restore to stock firmwares anytime and even update ur phone.https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108/page44
jkrz said:
Hello everyone!
A few days ago I bought myself a P10 plus on a vacation to China. Since I live in Sweden I decided to rebrand it to the European firmware (since it had the asian firmware installed) through FunkyHuawei when I got home. I got my bootloader code from Huawei support and succesfully unlocked it as well as installed TWRP. The first problem I encountered was that I was unable to create any backups of my phone as well as being unable to install or flash anything.
I then restarted my phone into recovery mode and suddenly it didn't boot into TWRP anymore, only EMUI stock recovery. I tried flashing TWRP several times but the phone still wouldn't boot into it, so I tried factory resetting the phone and the flashing TWRP once again. This is where the real problems started.
The firmware is gone, no OS is installed, I cannot do anything through TWRP (i only get error messages such as "E:Unable to find partition size for /boot" as well as Failed to mount /cache (Invalid Argument)")
Even worse is that the bootloader wont load as far as i can tell so I can't do anything through adb nor fastboot either. I'm completely stuck in TWRP. I can't even wipe nor change file system.
Is my phone damaged beyond repair or is there anyone on here that might have a solution?
Thanks in advance, any suggestions welcome!
EDIT: Okay this is really weird...
Suddenly my phone booted into the OS, even though TWRP said there were no OS installed. What is the next step from here to ensure this won't happen again?
Click to expand...
Click to collapse
You should see if you have the UFS memory or eMMC.
If you have eMMC version the current available TWRP is not working.
I made a testing version for TWRP that works on eMMC and was able to rebrand from China to International.
PM me if you need anything..
So i've gotten my phone working again (with the chinese ROM) but since TWRP won't work there's no way for me to rebrand it. My phone has eMMC 5.0 if that's any help.
MosquitoByte said:
You should see if you have the UFS memory or eMMC.
If you have eMMC version the current available TWRP is not working.
I made a testing version for TWRP that works on eMMC and was able to rebrand from China to International.
PM me if you need anything..
Click to expand...
Click to collapse
can you share the TWRP works in eMMC plz . many thanks
Dear Seniors.
I am facing great hardship because my phone is stuck at boot logo.
No booting in recovery mode to flash another rom.
I did unlock bootloader of it by using tuliptool with success. After that i flashed custom rom in it. after reboot it is happening that.
Please suggest to recover it.
Did you flash twrp after unlocking? Did you make backup of stock ROM? Perhaps find a version of the factory firmware and flash that.
Dear I have no backup and i flashed TWRP recovery.......
It is to aware you that i did relock bootloader now my phone is working properly. but i am unable to enter recovery mode. !!!
Now my phone is running android 6.0.1 B02
But i am failed to root this rom uptill now due above mentioned problem.
modorate said:
Dear I have no backup and i flashed TWRP recovery.......
It is to aware you that i did relock bootloader now my phone is working properly. but i am unable to enter recovery mode. !!!
Now my phone is running android 6.0.1 B02
But i am failed to root this rom uptill now due above mentioned problem.
Click to expand...
Click to collapse
I found software update notification but when i update an error accruing while update. (This update not compatible with this device"
In easy words......... my recovery.img has been corrupted. I have no idea to get rid of this situation.
I planned to unlock my Mini's bootloader this weekend. After reading this post, I decided to act later until the root cause has been figured out.
bao_gg said:
I planned to unlock my Mini's bootloader this weekend. After reading this post, I decided to act later until the root cause has been figured out.
Click to expand...
Click to collapse
Several people myself included have been able to use tuliptool to successfully unlock and root the device.
mine is hard bricked too. but I think it is worse than the case listed on the op.
if you want to hard bricked these are the steps:
follow the procedure to install the Spanish ROM 6.1, than another android m b12, than finally the android seven......use tulip tool and install twpr fine, root ect. amazing ROM.......buuuuut......I lost my IMEI somewhere in this process, and the original FTM which had a small menu changes to another static one, without the menu.
I needed this menu to open the com port to fix the IMEI. than I had the brilliant idea to re-flash android M via twrp (without modifying the zip file to remove the recovery, something I knew so well from the older axon mini).
results:
-lost twpr because the stock ROM wrote over it,
-cannot boot the OS because I flashed android m but the phone had the aboot 7.
-i now have a brick
I need a genious to sujest something to bring it back to life........sh....t...sh...t.....sh...t
any chances I could inject aboot7 via ADB through my dead recovery which somehow the phone recognises? ADB shell still seems to be working
thanks
Hello everyone, following a fairly serious problem that forced me to contact OnePlus and pay 100 euros (It had encrypted all the data after installing the MIUI 9, so I could not install anything because in recovery I saw only a series of codes), today I was given the cell phone, but with Android 7.1.1. Being an "old" version I wanted to upgrade to Oreo 8.1, but I can not get it through OTA or recovery. In OTA it tells me "installation failed" and if I try via recovery the installation will be stuck for some strange reason without even giving an error code. What could I do? Thanks in advance to those who will answer
Alfomod said:
Hello everyone, following a fairly serious problem that forced me to contact OnePlus and pay 100 euros (It had encrypted all the data after installing the MIUI 9, so I could not install anything because in recovery I saw only a series of codes), today I was given the cell phone, but with Android 7.1.1. Being an "old" version I wanted to upgrade to Oreo 8.1, but I can not get it through OTA or recovery. In OTA it tells me "installation failed" and if I try via recovery the installation will be stuck for some strange reason without even giving an error code. What could I do? Thanks in advance to those who will answer
Click to expand...
Click to collapse
Try the full firmware not OTA download this and flash it with TWRP or stack recovery
oneplus_5_oxygenos_5.1.1
https://downloads.oneplus.com/oneplus-5/oneplus_5_oxygenos_5.1.1/
I cannot update my new-from-Amazon TB-X304f from Android 7.1.1 to Android 8.1. The logs say that the update signature doesn't match the UID on the tablet, and the update fails. I've tried from both the system update on the tablet (wiped cache and factory reset just to be sure), and the Lenovo Smart Assistant. Neither work.
Any advice?
The build number I have is: tb-x304f_s000053_180927_row/
The version I'm trying to update to is: tb-x304f_s0001014_181113_row/
Hello, I have a TB-X704F, rooted with Supersu, TWRP and Xposed Framework. For several weeks the tablet wants to install an OTA update. Since the device is rooted, it reboots and then lands at TWRP. The whole thing keeps repeating itself, I am constantly asked to install the update right now or later. In the developer options the automatic system updates are deactivated, nevertheless the tablet wants to update constantly.
When I select full Unroot in Supersu, the tablet stops booting and stops at the Lenovo logo.
What can I do to install the OTA or other update or disable the update prompts?
Thank you!
64erbaz said:
Hello, I have a TB-X704F, rooted with Supersu, TWRP and Xposed Framework. For several weeks the tablet wants to install an OTA update. Since the device is rooted, it reboots and then lands at TWRP. The whole thing keeps repeating itself, I am constantly asked to install the update right now or later. In the developer options the automatic system updates are deactivated, nevertheless the tablet wants to update constantly.
When I select full Unroot in Supersu, the tablet stops booting and stops at the Lenovo logo.
What can I do to install the OTA or other update or disable the update prompts?
Thank you!
Click to expand...
Click to collapse
You need to flash back to factory default and let the OTA install over that.
It's not worth it in my opinion. Im waiting for a new TWRP to be available.
swieder711 said:
You need to flash back to factory default and let the OTA install over that.
It's not worth it in my opinion. Im waiting for a new TWRP to be available.
Click to expand...
Click to collapse
I'm having this same issue. How do I flash back to factory default?
baydude said:
I'm having this same issue. How do I flash back to factory default?
Click to expand...
Click to collapse
Covered many times in this thread. Get in edl mode and flash stock with MiFlash
Orangebanannax said:
I cannot update my new-from-Amazon TB-X304f from Android 7.1.1 to Android 8.1. The logs say that the update signature doesn't match the UID on the tablet, and the update fails. I've tried from both the system update on the tablet (wiped cache and factory reset just to be sure), and the Lenovo Smart Assistant. Neither work.
Any advice?
The build number I have is: tb-x304f_s000053_180927_row/
The version I'm trying to update to is: tb-x304f_s0001014_181113_row/
Click to expand...
Click to collapse
I'm having the same problem, any luck? I've been attempting to flash back to an earlier rom to see if that fixes the problem, but I haven't been able to find a stock rom that actually works yet.
Orangebanannax said:
I cannot update my new-from-Amazon TB-X304f from Android 7.1.1 to Android 8.1. The logs say that the update signature doesn't match the UID on the tablet, and the update fails. I've tried from both the system update on the tablet (wiped cache and factory reset just to be sure), and the Lenovo Smart Assistant. Neither work.
Any advice?
The build number I have is: tb-x304f_s000053_180927_row/
The version I'm trying to update to is: tb-x304f_s0001014_181113_row/
Click to expand...
Click to collapse
Weird fix that seems to have worked. make a backup of the system using twrp following this https://forum.xda-developers.com/thinkpad-tablet/general/twrp-root-tab-4-plus-tb-x704l-f-tb-t3664407, then grab the boot.emmc.win and reflash it using fastboot. I'm currently installing the 8.1 update as I type this.