Hi guys,
My mobile one plus 5 is stuck on logo (Bootloop). Now I am trying to install stock OTA which is downloaded from (OxygenOS 10.0.1) but having this error while doing it via ADB.
Total xfer: 2.00x
The above error is coming after 94% and on mobile installation completed, Please reboot.. I also tried MSM Download tools 4.0.58, But still not installed the OS.
I already lost great time on it till now please help me in this issue.
I searched a lot but still not success.
Related
Hi Guys,
I flashed a custom rom on my new device SM-N900 using TWRP. When I wanted to revert to the stock firmware using ODIN I getting an error saying 'Power Reset or Unknown Upload Mode'.
The flashing of stock firmware is successful using ODIN but when rebooting I am getting the same error. I have tired doing everying I could searched XDA Note 3 forum, other sites as well but nothing worked.
I have even tired the below procedure to get mobile in to working condition but everything failed.
http://forum.xda-developers.com/showthread.php?p=52329946&nocache=1#post52329946
Below are the screenshots of the error and Download screen
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.
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
Guys, my zenfone selfie is in bootloop i guess. I am not sure cause i didnt flash any roms or something. But phone is not turning on except i plug it in with charging cable, it just keeps restarting.
So, first thing i did was, i pulled out my imp. Data from device via adb v29.0.1 . I installed twrp recovery(dont know the version of it, but downloaded from a youtube video link posted on 2017). So now i download stock rom for my device from asus site and try adb sideload, but didnt work,. It shows the error (need adb 1.0.32 or newer to sideload). So then i tried installing rom with twrp, so i pushed stock rom via adb, then tried installing rom,. But then again error comes, md5 file not found and cant install this M package (2017_ 11_ 10_ ___16:15:27 CST) L less than 20160426 build (fri nov 18 18:43:08 EST 2016).
Updater process ended with ERROR:7
error installing zip file.
So this was the error i faced, and cant find other roms for my device anymore.
These all things i learn mostly from xda yesterday.
Plus cant even go to recovery mode without charging cable,.
Guys plzz help me
While flashing pixel experience plus rom, the device did not boot up correctly causing a google loading screen which did not change even after an hour. At that time i realised that the rom didn’t flash correctly, or the rom might have some faults. So I rebooted my mobile in custom recovery mode to flash the stock rom, but it did not complete the flash, it generated error 7. So I tried to install havoc rom and I encountered the same problem. Not just that I have tried installing at least 5 rom which gives me the same problem. I can’t even flash my recovery rom. It generates the same errors which include error 7 and invalid zip file. So I tried solving this problem by unzip the rom and editing the assert script and re zipping the file, and I encounter the same errors. I have even tried using a different custom recovery like TWRP and red wolf (latest updated version), but I face the same errors. The mobile has no os installed and it doesn’t allow me to install any rom. It only allows me to install stock recovery and other custom recovery by using Fastboot mode. I have tried add sideload through the custom recovery and the mobile gets detected, but it gives the same errors.
So I tried using QFIL application as the mobile was a Qualcomm device. The mobile gets detected as 9008. And I tried to download the program files on the mobile, but then it gives me a Sahara fail error.
I have tried to do it multiple times and I end up getting the same error.
The device has a unlocked boot loader but it was never rooted.
Please help me.
Can’t post it in the developer forum for this device as I don’t meet the requirements for posting it
i.am.the.best said:
While flashing pixel experience plus rom, the device did not boot up correctly causing a google loading screen which did not change even after an hour. At that time i realised that the rom didn’t flash correctly, or the rom might have some faults. So I rebooted my mobile in custom recovery mode to flash the stock rom, but it did not complete the flash, it generated error 7. So I tried to install havoc rom and I encountered the same problem. Not just that I have tried installing at least 5 rom which gives me the same problem. I can’t even flash my recovery rom. It generates the same errors which include error 7 and invalid zip file. So I tried solving this problem by unzip the rom and editing the assert script and re zipping the file, and I encounter the same errors. I have even tried using a different custom recovery like TWRP and red wolf (latest updated version), but I face the same errors. The mobile has no os installed and it doesn’t allow me to install any rom. It only allows me to install stock recovery and other custom recovery by using Fastboot mode. I have tried add sideload through the custom recovery and the mobile gets detected, but it gives the same errors.
So I tried using QFIL application as the mobile was a Qualcomm device. The mobile gets detected as 9008. And I tried to download the program files on the mobile, but then it gives me a Sahara fail error.
I have tried to do it multiple times and I end up getting the same error.
The device has a unlocked boot loader but it was never rooted.
Please help me.
Click to expand...
Click to collapse
1. 1st try to flash fastboot rom,
after install fastboot rom if the phone stuck on asus logo or any other error then
2.Try to install Qfll file (select ww_no_fsg.xml file) after successful installation , boot your phone.
3. again connect your phone fastboot mode and flash fastboot rom
If every installation is successfully done then i am sure that your phone is boot properly in stock rom with lock bootloader.
because I faced same issue,
remember 1st try to install stock fastboot rom and then try to flash Qfil files
Wish you good luck :good:
Try flashing fw063 before flashing your custom rom.(that fixed for me)
if it didn't work try this (rooted):-
https://forum.xda-developers.com/showthread.php?t=2522762
Thanks bro. I have successfully unbricked my mobile