hi - I hope someone can help me. I have a LTE enabled Lenovo Tablet 2 1050L which I attempted to root using the instructions given here ... https://forum.xda-developers.com/thinkpad-tablet/general/how-to-root-yoga-tablet-2-t3251571 ... but I have managed to brick my device. I successfully installed SuperSU but then read that Magisk was better and tried the same procedure with that but it didn't work. Now when the tablet starts up, I get a message which says ... "EFILINUX ERROR [android_image_start_buffer:737] boot image digital signature verification failed : 0000001A" which appears over the initial Lenovo splash screen. I then get to the Android system recovery menu but I can't get the table any further than this. I have tried wiping data / factory resetting but this does not work.
I can boot the tablet into recovery mode using CWM or TWRP but I have no idea what to do now. I guess I shouldn't have messed. I hope someone can help - I've tried the official Lenovo forums but no one has answered in a week.
Kind regards
I've downloaded this ROM ... lenovo-forums.ru/files/file/1074-yoga-tablet-2-10-yt2-1050l_s100192_151119_row_los-50 ... and flashed this onto my tablet using the Intel flash tool and everything seems to be back up and running.
Can someone confirm that this is safe to do? Can I trust this ROM as it's not from an official source?
Thanks
Related
Hello,
Ok, here is the situation
I have a Zuk Z1 with last COS update 12.1 with locked bootloader, no root etc ... (I didn't touch anything).
Yesterday, it reboot by itself but I got bootloop (starting apps then again lenovo boot image ...)
I try to factory reset by using the recovery metohd, it's start normally (optimizing apps ...) but then reboot and again bootloop ...
So I try to sideload the official COS ROM from Cyanogen Support (cm-12.1-YOG4PAS9IG-ham-signed-d4fc2c5394.zip), but the sideload stuck at 47% and saying total xfer: 1.00x and the phone go back to recovery but still have boot loop ...
I try to boot in fastboot and use the All In One tool to flash official ROM but didn't work (Its say that the bootloader is lock)
I find without knowing this menu a debugging hardware tool test, and then I run the test, its say SD : Fail and in another I got SD : Fail and no sd fuse in dir
I saw many thread here and on google, and some say that we have to use qfil/qpst method, and find this which seems complete : http://www.androidbrick.com/lenovo-zuk-phones-qfil-roms-unbrick-guide/
But as I don't know if its hardware issue or soft brick ...
Could someone help me to recover my phone to COS or CM by using the right method ?
Thank you !
wackou said:
Hello,
Ok, here is the situation
I have a Zuk Z1 with last COS update 12.1 with locked bootloader, no root etc ... (I didn't touch anything).
Yesterday, it reboot by itself but I got bootloop (starting apps then again lenovo boot image ...)
I try to factory reset by using the recovery metohd, it's start normally (optimizing apps ...) but then reboot and again bootloop ...
So I try to sideload the official COS ROM from Cyanogen Support (cm-12.1-YOG4PAS9IG-ham-signed-d4fc2c5394.zip), but the sideload stuck at 47% and saying total xfer: 1.00x and the phone go back to recovery but still have boot loop ...
I try to boot in fastboot and use the All In One tool to flash official ROM but didn't work (Its say that the bootloader is lock)
I find without knowing this menu a debugging hardware tool test, and then I run the test, its say SD : Fail and in another I got SD : Fail and no sd fuse in dir
I saw many thread here and on google, and some say that we have to use qfil/qpst method, and find this which seems complete : http://www.androidbrick.com/lenovo-zuk-phones-qfil-roms-unbrick-guide/
But as I don't know if its hardware issue or soft brick ...
Could someone help me to recover my phone to COS or CM by using the right method ?
Thank you !
Click to expand...
Click to collapse
Go with qpst/qfil method to recover your phone
And did you tried changing the USB port or cable while side loading cos ROM .. Cause most of issues are solved by the changing USB port or cable.. So try this.. Or else qfil is the option
shubhambhise said:
Go with qpst/qfil method to recover your phone
And did you tried changing the USB port or cable while side loading cos ROM .. Cause most of issues are solved by the changing USB port or cable.. So try this.. Or else qfil is the option
Click to expand...
Click to collapse
Hello,
I got help on the telegram group, we try many thing, the result is that I can only get ZUI working, if flashing COS via QFIL, I get the same result, if I flash ZUI, unlock bootloader, flash TWRP, wipe everything, then sideload CM13, TWRP say that no os is installed and I get a bootloop at the bootloader ...
ZUI is good, but I get some error regarding notification.
If you have any other idea ?
wackou said:
Hello,
Ok, here is the situation
I have a Zuk Z1 with last COS update 12.1 with locked bootloader, no root etc ... (I didn't touch anything).
Yesterday, it reboot by itself but I got bootloop (starting apps then again lenovo boot image ...)
I try to factory reset by using the recovery metohd, it's start normally (optimizing apps ...) but then reboot and again bootloop ...
So I try to sideload the official COS ROM from Cyanogen Support (cm-12.1-YOG4PAS9IG-ham-signed-d4fc2c5394.zip), but the sideload stuck at 47% and saying total xfer: 1.00x and the phone go back to recovery but still have boot loop ...
I try to boot in fastboot and use the All In One tool to flash official ROM but didn't work (Its say that the bootloader is lock)
I find without knowing this menu a debugging hardware tool test, and then I run the test, its say SD : Fail and in another I got SD : Fail and no sd fuse in dir
I saw many thread here and on google, and some say that we have to use qfil/qpst method, and find this which seems complete : http://www.androidbrick.com/lenovo-zuk-phones-qfil-roms-unbrick-guide/
But as I don't know if its hardware issue or soft brick ...
Could someone help me to recover my phone to COS or CM by using the right method ?
Thank you !
Click to expand...
Click to collapse
Hope this will help you
Check this out
http://forum.xda-developers.com/zuk-z1/help/helpppp-t3505990
http://forum.xda-developers.com/zuk-z1/general/guide-how-to-unlock-root-install-twrp-t3394037
This will help you
Hi all,
I'm hoping someone can shed some light on this problem ..
Background:
- Was running Oxygen OS and went to update it to the new beta, booted into TWRP, flashed the file and rebooted - nothing happened, black screen with a constantly lit blue LED.
- Back into recovery but it didn't ask me for a pattern so it no longer recognised the encrypted partitions.
- Ah well, erased everything a few times and booted back into recovery to flash a new ROM, TWRP loads but no longer responds on the touchscreen, it's stuck at the "swipe to allow modifications to system partition" screen
- booted into fastboot, reflashed TWRP, same deal, Tried all 3 available versions but no difference. Also tried the clockworx build.
- flashed stock recovery and tried to sideload the rom but the first time it bombed out at 48% or so, now it just stops with "Xfer 0.0%" ..
- Saw this thread here https://forum.xda-developers.com/oneplus-5/how-to/unbrick-tool-oneplus-5-t3648169 and downloaded it but the MSM tool does not recognise any connected device even though I have "Qualcomm HS-USB QDLoader 9008 COM23" in the device manager
I'm going pretty nuts now so any tips appreciated :/
Cheers
K
Right - quick update - managed to get it re-flashed using the MSM Downloader tool after a lot of trial and error .. if anyone has any questions about the process just let me know!
on my phone TWRP shows no files on in any folder. can you pls help?
krrunch said:
Right - quick update - managed to get it re-flashed using the MSM Downloader tool after a lot of trial and error .. if anyone has any questions about the process just let me know!
Click to expand...
Click to collapse
Hi! I believe that I am in the same boat as you were. On short: was rooted & wanted to stock. Flashed stock recovery & last OS from oneplus site and got stuck in boot. Afterwards I was no longer able to see my device in the stock recovery adb install....
Can you give me a hand please! Thank you!
Edit: Got it to work with the qualcomm method
Hello,
You should install Hydrogen OS to unbrick your phone.
After that install TWRP and then install the full rom OOS 5.0.4.
Urgent help needed as I'm leaving the country at the end of the week o any help is appreciated!
Just successfully rooted my device:
Black, Unlocked, PRA-LX1, UK, Dual SIM
After doing so successfully, I attempted to flash LineageOS from the following link:
https://forum.xda-developers.com/p8lite/p8-lite-2017-development/rom-lineageos-15-1-hi6250-devices-t3811583
Although when I completed Step 6 on the Installation guide and rebooted the phone, I started seeing the message:
------------------
ERROR MODE
Attention!
Please update system again
(Green Android picture)
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
------------------
Despite this, I didn't receive a box with my phone due to being second hand, and I didn't see the model number on the receipt as it was from a reselling store. I didn't remember to note down the specific model number
It'd be extremely helpful if someone could possibly help just from the device description above as I'm not sure if it's safe for me to just attempt to flash every stock rom for every other LX1 device out there.
---------------------------------------------------------------
Update:
To restore this, I connected via fastboot with a working USB & flashed an original stock recovery in the video found here
(Just in case their download link ever goes down, I have uploaded the same copy to my MEGA, found here)
The recovery installed fine when using the command
fastboot flash recovery oeminfo.img
Click to expand...
Click to collapse
Whenever trying to flash any other recovery such as twrp before this fastboot stuck on a loading icon.
The stock recovery seems to be downloading the original firmware, too.
PRA-LX1C432B202 is presumably the model.
Both the bootloader and FRA were unlocked when everything else was inaccessible.
Looks like the custom ROM's recovery that you've flashed is not compatible with PRA-LX1. Try to flash stock recovery. If not working, then flash stock firmware.
Thanks @Botar230!
I didn't see your comment until just now after deciding to edit this post since I've gotten a step closer to restoring my device.
Your solution was the method I used although I didn't know my phone model, so I found a random solution which just worked for my device, and the eRecovery seems to be downloading the stock firmware anyways. Thanks again
Before flashing this lineage os you should update to EMUI8 to get treble support, i suppose you was running EMUI5, hence the error mode.
Hi Everyone,
I have an issue with my Oneplus8 pro and below are the details
1. The device was working perfectly. I was interested to root the device and install a custom ROM.
2. The method used was to try and flash a patched boot image for the device but I think i landed up using a wrong boot image file.
3. The OS was on 10.5.10 if I remember correctly. I used a patched image file I suppose of an older firmware. Now restarts and goes to "QUALCOMM Crashdump mode". The only options are
a. reboot to fastboot mode
b. flash the TWRP for Oneplus 8 pro but that doesnt mount by storage so cant really transfer anything to flash again.
Requesting some help to fix the issue and apologies if i have not explained correctly.
Tried booting a stock boot image?
neverborn said:
Tried booting a stock boot image?
Click to expand...
Click to collapse
Hey,
Thank you for a quick repsonse. Yes, i had tried doing that and still the same error however while we speak, i just downloaded the msmDownloadtool and tried using it to flash a stock firmware and finally, i am so happy to see the device boot sucessfully
Thank you once again for tryin to help
Regards
Hello.
Clarify exactly how the procedure took place
I did some errors trying to update stock firmware from twrp, now I'm stuck on twrp 3.4 and I cannot install anything to solve it because of the message:
Failed to mount '/odm' ( invalid argument )
What is working:
- Boot to twrp
- Boot to Emui recovery ( it connects to wifi but it do not download/install recovery/firmware )
-- Factory reset from emui recovery
What can I try?
florstat said:
I did some errors trying to update stock firmware from twrp, now I'm stuck on twrp 3.4 and I cannot install anything to solve it because of the message:
Failed to mount '/odm' ( invalid argument )
What is working:
- Boot to twrp
- Boot to Emui recovery ( it connects to wifi but it do not download/install recovery/firmware )
-- Factory reset from emui recovery
What can I try?
Click to expand...
Click to collapse
Most probably you have modified the oem partition and changed the device model this is the reason for not downloading in huawei erecovery.
I had the same error like /odm but my device boots fine and works normal apart from the battery drain
Thank you. I solved it flashing /odm partition with fastboot using this method:
[GUIDE] UN-BRICK Huawei P8 Lite 2017 (And maybe other devices)
THIS IS NOT GUARANTEED TO WORK! If it does not work, feel free to let me know here and i will do what i can to help, but remember I probably can't help everyone. IMPORTANT: ON XDA-LABS APP THIS POST IS KINDA BROKEN IDK WHY SO LOAD IT IN...
forum.xda-developers.com
Thanks to HuRu method, after a lot of reboots and reinstall and erecovery and factory resets I managed to reboot stock rom.
Unfortunately I'm not able to boot any custom rom ( tried all Darkjoker's rom ), but I will make another thread for this.
Honestly I had no idea that modding this phone would have been so difficult, it usually takes me very little time with other devices while in this case every little step requires to solve a lot of troubles.
florstat said:
Thank you. I solved it flashing /odm partition with fastboot using this method:
[GUIDE] UN-BRICK Huawei P8 Lite 2017 (And maybe other devices)
THIS IS NOT GUARANTEED TO WORK! If it does not work, feel free to let me know here and i will do what i can to help, but remember I probably can't help everyone. IMPORTANT: ON XDA-LABS APP THIS POST IS KINDA BROKEN IDK WHY SO LOAD IT IN...
forum.xda-developers.com
Thanks to HuRu method, after a lot of reboots and reinstall and erecovery and factory resets I managed to reboot stock rom.
Unfortunately I'm not able to boot any custom rom ( tried all Darkjoker's rom ), but I will make another thread for this.
Honestly I had no idea that modding this phone would have been so difficult, it usually takes me very little time with other devices while in this case every little step requires to solve a lot of troubles.
Click to expand...
Click to collapse
Most probably you are not following the instruction clearly. I was able to use DarkJoker rom