I was using Google experience 10 and twrp 3.2.2.0 but suddenly my device switch off and when try to start it shut off after asus logo, tried twrp it was stuck on teamwin logo , then I try to flash twrp and new rom it push this msg "failed (remote: partition is write protected)"
Please help
No response
It's look like my phone is now useless, no one has any solution, even service center is in brain dead situation
Rahuljha25 said:
It's look like my phone is now useless, no one has any solution, even service center is in brain dead situation
Click to expand...
Click to collapse
Try to ask or find the solution here
https://forum.xda-developers.com/asus-zenfone-max-pro-m1
Rahuljha25 said:
I was using Google experience 10 and twrp 3.2.2.0 but suddenly my device switch off and when try to start it shut off after asus logo, tried twrp it was stuck on teamwin logo , then I try to flash twrp and new rom it push this msg "failed (remote: partition is write protected)"
Please help
Click to expand...
Click to collapse
If you can access the phone by means of ADB, and if you have phone's Stock ROM ( a .ZIP-file ) at your fingertips, then you can try to re-flash phone's stock ROM via ADB's subcommand "sideload"
Code:
adb devices
adb reboot sideload
adb sideload <FULL_PATH_TO_STOCK_ROM_ON_WINDOEWS_PC>
adb reboot
to bring back phone to its original state.
Related
I have a VIBEZ K910 with locked bootloader after upgrading to version 4.4.2. Now it's bricked. Cannot enter test mode with the combination Volumn - and Power button. I think the droidboot.img is damaged. Cannot enter recovery either. Anybody can help me unbrick the phone? Pls:crying:
Sorry to hear about your bricked phone. I can't help specifically as I don't have a Lenovo, but having a search around XDA there seems to have been some success reported in the following thread:
http://forum.xda-developers.com/showthread.php?t=2597590
See this post - http://forum.xda-developers.com/showpost.php?p=52013378&postcount=412
Another post in that thread suggests:
Turn off the phone --> Run minimal ABD and fastboot as admin--> just write the command for recovery install (don't hit enter yet)--> press volume + and volume - button and connect the phone to pc via usb--> now hit enter and voila. Your phone will boot in recovery.
Click to expand...
Click to collapse
Good luck!
anyone?
f4780y said:
Sorry to hear about your bricked phone. I can't help specifically as I don't have a Lenovo, but having a search around XDA there seems to have been some success reported in the following thread:
http://forum.xda-developers.com/showthread.php?t=2597590
See this post - http://forum.xda-developers.com/showpost.php?p=52013378&postcount=412
Another post in that thread suggests:
Good luck!
Click to expand...
Click to collapse
i tried this aldready, but my phone is locked bootloder so that method is no help. Thank you for your support anyway.
hientran41 said:
i tried this aldready, but my phone is locked bootloder so that method is no help. Thank you for your support anyway.
Click to expand...
Click to collapse
OK, but did you look at the second link there, to the specific post in that thread? It suggests a process for locked bootloader, which is why I thought it might help...
Anyhoo, I hope you manage to get it fixed somehow!
Is anybody have the droidboot.img file from the VibeZ K910 dualsim, pls upload it for me. i cannot find it anywhere.
I look into the second link as well. that method for user have a working phone but locked bootloader and want to downgrade.
Ah, OK. Sorry I couldn't help.
u fix your phone?
hientran41 said:
I have a VIBEZ K910 with locked bootloader after upgrading to version 4.4.2. Now it's bricked. Cannot enter test mode with the combination Volumn - and Power button. I think the droidboot.img is damaged. Cannot enter recovery either. Anybody can help me unbrick the phone? Pls:crying:
Click to expand...
Click to collapse
hi do u fix your phone?
Geguniukas said:
hi do u fix your phone?
Click to expand...
Click to collapse
i bricked also
dunno what to do..
---------- Post added at 12:13 AM ---------- Previous post was at 12:13 AM ----------
hientran41 said:
I have a VIBEZ K910 with locked bootloader after upgrading to version 4.4.2. Now it's bricked. Cannot enter test mode with the combination Volumn - and Power button. I think the droidboot.img is damaged. Cannot enter recovery either. Anybody can help me unbrick the phone? Pls:crying:
Click to expand...
Click to collapse
did you fixed the phone?
lenovo k910e 4.2.2 bricked after TWRP for 4.4.2 installation
Hi , this is my first time on the site , so forgive me if ive posted this in the wrong place.
I briked my Lenovo k910e running 4.2.2 rom with google apps purchased off Aliexpress.
What i did was run the flashrec.exe file for TWRP , but not until too late did i realise it was for 4.4.2 instead of 4.2.2.
Now i cannot boot the phone , TWRP was successfully installed and operational , but after about 20 reboots TWRP flash screen is stuck on the TeamWin logo and not accessable.
Ive tried mostl sugestions on this site and others without luck.
I can get the phone recognised with fastboot only after these commands ;
cd downloads
cd fastboot
adb devices
and it seems i may be able to push files to my device.
Is there a working link to the k910 OEM rom k910_ss_s_2_040_0109_131226 someone could direct me to.
All the links i have found so far are corrupted. Is there a way of repairing the TWRP recovery i have in the phone now.
Am I correct in assuming I have to install the OEM factory 4.2.2 ROM to wipe TWRP and istal Lenovo recovery ?.
Any help would be so appreciated. Thanks
Solution ( k910 bricked )
Ok here is the solution even if your device ( k910 dual sim ) is completely bricked as was mine.
I was stuck in Lenovo logo with no success in finding right and working drivers ( windows 7 64x ) and i was not able to to get in recovery official ...everything was just - somehow - deleted...
I had locked bootloader **** and was not be able to flash cmw in working mode ****
There was nothing for me that could recover my phone even if the "hard" way with QPST or miflash etc
So....after 3 days....find this solution and hope this will help you because it is soooooooooo easy finally!
Steps:
1) Download lenovo driver ( i think it is useless in fact but ok....just run it you dont have anything more to loose )
https://www.dropbox.com/s/frbpz16udrefoit/LenovoUsbDriver_autorun_1.0.112.exe?dl=0
2a) Download and install Minimal adb
https://www.dropbox.com/s/uvngsu4vz4hvsky/minimal_adb_fastboot_v1.1.3_setup.exe?dl=0
So now you have to use the right recovery image ( this file has to be inside minimal adb folder )....so here it is:
https://www.dropbox.com/s/ge05m1fe8n4qgb1/recovery.img?dl=0
2b)
Download this ROM ( this worked for me - with other i did try i did get an error )
http://www.needrom.com/download/lenovo-k910-vibeui-2-0/
prefer the last updated version ( 1501 )
Put this rom in the same ADB folder and renale zip in VIBE1411.ZIP ( in order to be easier later )
3) Turn off the device open Adb and write : fastboot boot recovery.img ( to have it ready )
4) Push volume + $ volume - at the same time and AFTER connect with usb to your pc - At the time the device will vibrate HIT ENTER in ADB
This will flash the recovery and after 1 minute device will open in a recovery screen with an adb update option ***
SELECT THIS adb update OPTION !
Your device kow it is ready to flash the new rom ! ( you will realize that everything is right from many usb beeps you will hear )
5)In adb console write : adb sideload VIBE1411.ZIP
This will take a little ....after that your device will reboot ! Dont panic if for a few minutes it will stuck in lenovo logo....
IT IS NORMAL AND YOU HAVE TO WAIT!
Hope this will help you.....please feel free to tell me if this worked for you.
C u
Same thing happens to my lenovo vibe z k910
buzzbuzz1 said:
Hi , this is my first time on the site , so forgive me if ive posted this in the wrong place.
I briked my Lenovo k910e running 4.2.2 rom with google apps purchased off Aliexpress.
What i did was run the flashrec.exe file for TWRP , but not until too late did i realise it was for 4.4.2 instead of 4.2.2.
Now i cannot boot the phone , TWRP was successfully installed and operational , but after about 20 reboots TWRP flash screen is stuck on the TeamWin logo and not accessable.
Ive tried mostl sugestions on this site and others without luck.
I can get the phone recognised with fastboot only after these commands ;
cd downloads
cd fastboot
adb devices
and it seems i may be able to push files to my device.
Is there a working link to the k910 OEM rom k910_ss_s_2_040_0109_131226 someone could direct me to.
All the links i have found so far are corrupted. Is there a way of repairing the TWRP recovery i have in the phone now.
Am I correct in assuming I have to install the OEM factory 4.2.2 ROM to wipe TWRP and istal Lenovo recovery ?.
Any help would be so appreciated. Thanks
Click to expand...
Click to collapse
After running twrp recovery it operates 3-4 times but now it flashes on twrp screen and screen goes blank and again flashes . I am unable to on it and as it shows only light and lenovo logo after that blank screen . Please help me in this. Its only detecting in adb recovery not any other mode.
lenove vibe Z k910 locked and stuck in logo
hello all
I ve done every word and many other tutorials but still the problem the same:
adb devices give just nothing
but fastboot devices gives the device
the driver is installed correctly detected in devices of the computer
here is the response for :fastboot boot recovery.img:
~/Desktop/lenovo]$ fastboot boot recovery.img (master✱)
< waiting for device >
downloading 'boot.img'...
OKAY [ 0.536s]
booting...
FAILED (remote: Locked)
finished. total time: 0.538s
thanks for everyone to help
Boot into recovery under bricked condition
Today I bricked K910 after reinstalling GMS apk.
The phone hanged at boot logo.
Nothing can be from here.
I decided to take this risk.
I removed the back cover and disconnected the battery terminal.
After that I plugged back the terminal.
Several tries by power button and volume down to get into the recovery mode. All failed.
Each time it hanged at boot logo.
I have to redo the battery terminal unplug sequence again.
This is correct method to get into recovery mode.
Press power button and volume down till the Lenovo logo appears.
Move the power button finger to the position of the " Home " of the touchscreen position.
Hold till the recovery menu appears. Choose factory reset to erase the phone.
There was two lit small icon below. Make your choice.
The phone will be erased by reset.
Reboot after the process.
I solved my phone bricked problem.
Hope the method will solve your problem.
Good day to all K910 users.
my vibe z cannot access the recovery mode (PWR + VLM DOWN), it only vibrate. If turn on only stuck at Logo. Please help .
hi, i work helping my classmates when they stuck on their phones... ok, i'm apologize for my bad english but here is the thing, i now have one Huawei G610-U00 and the phone say "Encryption unsuccessful", i notice that him install the twrp recovery so i try flashing a new recovery using fastboot and the fastboot only say "sending 'recovery'" and nothing else happens(i left all the night, the phone only discharge the battery,), make a search on google and find info related and try them, try using sp flash, try installing a new zip, even try a force-update but when press the vol + and - and the power key, the phone go to recovery, also in the bootloader mode it only say "recovery_status:UPDATED" nothing else, the "adb devices" comand shows '0123456789ABCDEF' the "fastboot devices" show "mt6589_phone_720pv2", please need help i use the adb comand and try to format but only receive error messages, this is that i get on the recovery:
https://drive.google.com/file/d/0B_NnURitRMg-ZUZCUC1WaXVIQkdPSGRCaE90NUFUVUZodnBr/view?usp=sharing
https://drive.google.com/file/d/0B_NnURitRMg-RUN5ZjhWbklDUVRNeThFbXRMLUdfUUNoVkFJ/view?usp=sharing
https://drive.google.com/file/d/0B_NnURitRMg-ZGxqYlhMeTBhbVVXbERHWXNoN0xXYlgxTFdV/view?usp=sharing
https://drive.google.com/file/d/0B_NnURitRMg-bVJRODB1N3hXckxNbnhMZFBpajdhekxhaUc4/view?usp=sharing
Click to expand...
Click to collapse
goluisgerardo said:
hi, i work helping my classmates when they stuck on their phones... ok, i'm apologize for my bad english but here is the thing, i now have one Huawei G610-U00 and the phone say "Encryption unsuccessful", i notice that him install the twrp recovery so i try flashing a new recovery using fastboot and the fastboot only say "sending 'recovery'" and nothing else happens(i left all the night, the phone only discharge the battery,), make a search on google and find info related and try them, try using sp flash, try installing a new zip, even try a force-update but when press the vol + and - and the power key, the phone go to recovery, also in the bootloader mode it only say "recovery_status:UPDATED" nothing else, the "adb devices" comand shows '0123456789ABCDEF' the "fastboot devices" show "mt6589_phone_720pv2", please need help i use the adb comand and try to format but only receive error messages, this is that i get on the recovery:
Click to expand...
Click to collapse
I have a similar problem with Huawei Y320-U030, MTK 6572, Android 4.2.2 with many malware infections. Almost all applications keep crashing, Factory Reset from Settings does not work, but I can do it from the recovery and it seems to complete successfully but when the devices boots, all user applications and files are there. I have flashed it with stock ROM and backup ROM from an other working similar phone, the flashing process completed successfully but when the device boots all user files and applications are untouched, even after formatting the whole flash with Sp flashtool, Volcano box and Miracle box! An applications called DU Speed Booster is set as device administrator with a pattern lock which cannot be deactivated. Uninstalling the imo application makes the device reboot and hang on Huawei logo untill the battery is pulled out. I can't install any new apk or root the device even using PC. Music, videos, and photos in the internal memory can be copied with a computer but cannot be deleted. Formatting the internal memory with a PC seems successful but all files on the device are intact. Very interesting case indeed.
Hi guys, my redmi 5 plus is stuck on logo loading screen and i can only go for fastboot. Cannot neither turn off phone.
I tried with Mi Flash tool but program fail with "Can not find flash_all.bat". I tried different version of roms and Mitool, but still have this error. How can i repair my device? Thnak you all for the future responsed
Ps: sorry for my really bad english
I dont´know what you tried to do before to get this status or if you have an unlocked bootloader to perform some operation in fastboot mode. If you are in stock rom you can try enter to recovery and use MiAssistant feature is a kind of adb sideload in-built that you can use to reinstall again the rom onto your device. Here you will find some guide lines about this behind the concept http://www.xiaomitool.com/adb
SubwayChamp said:
I dont´know what you tried to do before to get this status or if you have an unlocked bootloader to perform some operation in fastboot mode. If you are in stock rom you can try enter to recovery and use MiAssistant feature is a kind of adb sideload in-built that you can use to reinstall again the rom onto your device. Here you will find some guide lines about this behind the concept http://www.xiaomitool.com/adb
Click to expand...
Click to collapse
You right sorry. I have Bootloader unlocked. My brick come becose of me trying to root the phone with "1clickrooter" for redmi5 plus. When phone rebooted on recovery he ask me for a password. No pin works on this pass requesto so i try to wipe cash, phone automatically reboot and stuck in logo screen. Cannot turn of or go to recovery, only action i can make is to go on fastboot mode.
So, i have news, i can go on recovery mode (recovery i have is called "Team Win Recovery Project 3.2.1.0"), but in order to make write action (now i can only read) request me a password, obviously neither 1 of my pass (sim pin/screen unlock) work.
Jackevolution said:
So, i have news, i can go on recovery mode (recovery i have is called "Team Win Recovery Project 3.2.1.0"), but in order to make write action (now i can only read) request me a password, obviously neither 1 of my pass (sim pin/screen unlock) work.
Click to expand...
Click to collapse
If you can reboot now to recovery twrp then just cancel when it prompts for a password and you have to format data in order to can reboot to system again
Jackevolution said:
You right sorry. I have Bootloader unlocked. My brick come becose of me trying to root the phone with "1clickrooter" for redmi5 plus. When phone rebooted on recovery he ask me for a password. No pin works on this pass requesto so i try to wipe cash, phone automatically reboot and stuck in logo screen. Cannot turn of or go to recovery, only action i can make is to go on fastboot mode.
Click to expand...
Click to collapse
SubwayChamp said:
If you can reboot now to recovery twrp then just cancel when it prompts for a password and you have to format data in order to can reboot to system again
Click to expand...
Click to collapse
Already done, now semms to be stuck on the same loading screen, baibe he installing apps? It taking sooo long...
i think this isn't working. It's just 20 minute that phone is stuck on "Mi" screen...
Nope, definetly not worked. There is a way to put filesin the phone from recovery?
Jackevolution said:
Nope, definetly not worked. There is a way to put filesin the phone from recovery?
Click to expand...
Click to collapse
Yes, you can reflash again the rom, put the rom zip in your adb folder and short the name as you can, and flash it using adb sideload, to do this tap on "advanced option" and then "adb sideload" in recovery menu and in adb terminal in your pc type adb sideload nameofrom.zip where nameofrom is te name of the rom, don´t forget the extension .zip as I wrote. TWRP will load the zip and flash it again and then you can flash Magisk to root device.
If you can´t see storage of device in your pc is cause it´s encrypted but you can perform adb sideload anyway
Jackevolution said:
Hi guys, my redmi 5 plus is stuck on logo loading screen and i can only go for fastboot. Cannot neither turn off phone.
I tried with Mi Flash tool but program fail with "Can not find flash_all.bat". I tried different version of roms and Mitool, but still have this error. How can i repair my device? Thnak you all for the future responsed
Ps: sorry for my really bad english
Click to expand...
Click to collapse
Look at the error you got every time "Can not find flash_all.bat" its mean that you are selecting invalid path, okay so here is correct method to flash via fast-boot method:
Download the latest fast boot rom zip one option is http://bigota.d.miui.com/V9.5.12.0....FA_20180525.0000.00_7.1_global_343bc5aaef.tgz
Unzip .tgz using winrar and the zip will be extracted in folder named as vince_global_images_V9.5.12.0.NEGMIFA_20180525.0000.00_7 inside this folder there will be another folder named same.
Open Mi Flash tool and click to select direct to folder vince_global_images_V9.5.12.0.NEGMIFA_20180525.0000.00_7 open the folder and then open the other folder click Ok (don't open the the images folder)
Connect your redmi 5 plus in fast boot mode and click refresh, then choose clean all and click Flash
Hello, my realme 3 pro is stuck in bootloop, I am able to go into fastboot, but unable to write anything using it.
How it happened:
I was installing magisk using the magisk app. I rebooted my phone from the magisk app and the phone got stuck on android screen.
What I have tried:
I used vol up + power button then volume down + power button to go into fastboot. On my PC using fastboot devices I can see my device but whenever I try to execute any command such as
fastboot flash recovery twrp.img
Click to expand...
Click to collapse
It says sending 'recovery' (32056 KB) but takes about a minute before saying FAILED (Write to device failed (no link)).
Can anyone please help me.
Thank You
im facing the same problm .
I fixed the issue be using adb on an older computer with usb 2.0 you can try the same
tell me the complete process
i ve deleted my realme vender and other data files in twrp now im stuck on bootloop of realme 3 pro...
but twrp recovery is loading..
how to fix that please help me
Sparta9000 said:
Hello, my realme 3 pro is stuck in bootloop, I am able to go into fastboot, but unable to write anything using it.
How it happened:
I was installing magisk using the magisk app. I rebooted my phone from the magisk app and the phone got stuck on android screen.
What I have tried:
I used vol up + power button then volume down + power button to go into fastboot. On my PC using fastboot devices I can see my device but whenever I try to execute any command such as
It says sending 'recovery' (32056 KB) but takes about a minute before saying FAILED (Write to device failed (no link)).
Can anyone please help me.
Thank You
Click to expand...
Click to collapse
You should have to install realme ui recovery and vander 3.5gb file from official. Than try official method for installation of twrp ozip supported recovery. And flash any rom and mjsik that you want. In case you accidently delete your vander?
Or
But may be your recovery file is corrupted ?
So I advise you to install twrp from official website .
That will be approx 60mb.
Hey community,
I have been running Poco F1 with twrp and PixelExperience for the last 2 years. Considering the past record of the OS and my experience with the OS, I decided recently to upgrade to the newer PE12 for Poco F1 (maintained by Lakshay Garg). It went smooth initially and after the last OTA update, the phone started behaving weirdly.
Long story short,
This morning the phone went into an automatic restart and is now stuck in a boot loop. It boots and reaches the "G" logo and reboots. However, the weird part is,
Code:
fastboot flash
and
Code:
fastboot boot
are not available, throwing errors. The device is visible in
Code:
adb devices
and
Code:
fastboot devices
. This problem occurs when the phone is not plugged in. Once plugged in, the phone runs fine and everything just works. TWRP is not accessible, as if it is not there anymore and the only recovery that I can reach is the pixel recovery which has no option to flash any custom recovery (newbie, so not sure if something like this should exists or not).
I've tried various threads here and wasn't able to find any solution. Let me know what commands/outputs you guys might need from the device to help me in this.
Thanks in advance. Hope this gets fixed soon.
tysonX5653 said:
Hey community,
I have been running Poco F1 with twrp and PixelExperience for the last 2 years. Considering the past record of the OS and my experience with the OS, I decided recently to upgrade to the newer PE12 for Poco F1 (maintained by Lakshay Garg). It went smooth initially and after the last OTA update, the phone started behaving weirdly.
Long story short,
This morning the phone went into an automatic restart and is now stuck in a boot loop. It boots and reaches the "G" logo and reboots. However, the weird part is,
Code:
fastboot flash
and
Code:
fastboot boot
are not available, throwing errors. The device is visible in
Code:
adb devices
and
Code:
fastboot devices
. This problem occurs when the phone is not plugged in. Once plugged in, the phone runs fine and everything just works. TWRP is not accessible, as if it is not there anymore and the only recovery that I can reach is the pixel recovery which has no option to flash any custom recovery (newbie, so not sure if something like this should exists or not).
I've tried various threads here and wasn't able to find any solution. Let me know what commands/outputs you guys might need from the device to help me in this.
Thanks in advance. Hope this gets fixed soon.
Click to expand...
Click to collapse
Seems to be a battery problem. How old is it? You may need to replace it.
However make sure you followed the clean install method before you come on a conclusion. Also try to not use any Magisk modules.
Best Clean Install method:
Backup all your data. All your data into Internal Storage will be lost during this process.
Download latest Official TWRP Recovery, Pixel Experience build.
Create one Folder and move all the files you downloaded there.
Reboot to Fastboot Mode
Connect your device to PC and Boot into to TWRP via ADB or Minimal ADB and Fastboot:
Code:
fastboot boot <recovery_filename>.img
Example:
Code:
fastboot boot C:\Users\Retrial\Desktop\twrp-3.6.1_9-0-beryllium.img
Select Wipe > Advanced Wipe -> Select Dalvik / ART Cache, System, Data, Internal Storage, Vendor, Cache and then Swipe to Wipe.
Go back and select Wipe > Format Data > type yes
While you are in TWRP, transfer the Folder with the files you downloaded above.
Flash Pixel Experience ROM.
Flashing the ROM will replace TWRP with PE Recovery so OTA updates can be installed without problems since TWRP currently doesn't support decryption on A12 encypted ROMs - If you need in future to change ROM just fastboot boot to twrp via adb and flash img of twrp to recovery partition.
Done! Reboot to system.
Thanks, turns out that it was a battery problem after all. After battery replacement everything is working just fine. I also installed Awaken OS as Pixel Experience was removing the TWRP recovery each time I flashed it. Now as for my fastboot, initially it was not working; it was showing this error whenever I tried to flash TWRP recovery or any stock recovery:
Sending 'boot.img' (38640 KB) FAILED (Write to device failed (Cannot send after transport endpoint shutdown)) fastboot: error: Command failed
After this, the fastboot mode was diconnected and my phone was showing this Error:
Press any Key to Shut Down
It was resolved by running this bat file (as admin) :
https://bit.ly/31T2LcB
After running this file, there was no error and I was able to flash the twrp Recovery smoothly. So thanks for all the help really appreciate it.
tysonX5653 said:
Thanks, turns out that it was a battery problem after all. After battery replacement everything is working just fine. I also installed Awaken OS as Pixel Experience was removing the TWRP recovery each time I flashed it. Now as for my fastboot, initially it was not working; it was showing this error whenever I tried to flash TWRP recovery or any stock recovery:
Sending 'boot.img' (38640 KB) FAILED (Write to device failed (Cannot send after transport endpoint shutdown)) fastboot: error: Command failed
After this, the fastboot mode was diconnected and my phone was showing this Error:
Press any Key to Shut Down
It was resolved by running this bat file (as admin) :
https://bit.ly/31T2LcB
After running this file, there was no error and I was able to flash the twrp Recovery smoothly. So thanks for all the help really appreciate it.
Click to expand...
Click to collapse
Did you face the problem again?
I am using PE11 since last 2 years but suddenly i started facing the same problem. When plugged in, works fine. When I unplug it, works until screen is on and when I use power button to lock or unlock, phone goes into bootloop. I opend it in twrp where it can work as long as battery lasts, that's why I am not sure if it's a battery problem or something else