Hello, I failed to install a custom ROM and now when it gets to eRecovery mode I only have the options to reboot, shutdown and download latest verison and recovery. Of course, the download option doesn't work. I tried to get it back to the stock, the adb sees the device only when it's powered off, and it says unauthorized. The only time the fastboot devices show something is when the phone is in the fastboot mode I think and on the phone it displays: PHONE Unlocked and FRP unlock
When i try to fastboot flash system.img it says that FAILED <remote: Command not allowed>.
I tried to search for answers, can anyone help me please? I am doing this for 2 days...
LATER EDIT: I flashed boot,recovery, system. And now the options i have are: reboot system now, wipe data/factory reset, wipe cache partition. wipe data/factory reset just stops after 20%. What can I do?
Which device variant are you using? Which custom ROM did you try to install ? I think it would be better to post on the ROM's post...
Anyway fastboot should be use to flash recovery only, not a system. I'll recommand you to grab TWRP, install it via fastboot (fastboot flash recovery twrp_image_name.img . When it is installed, reboot recovery , back up product and vendor, Wipe everything and flash stock ROM.
Related
Guys... when i tried to flash oos 3.0 on my op2 through twrp, i first wiped the data to install new rom, then install oos 3.0, it failed. I then flashed the recovery i downloaded from the thread, then restart the recovery
I cant boot into the recovery.
System can't boot
Is it called "brick"?
So i tried to flash stock recovery in pc by command, but it says "remote: device is locked. cannot flash images". any solution to this problem?
I can boot into fastboot mode
You need to run the phone in Qualcomm mode on a PC and run the recovery tool to fix you bootloader.
I did the same and it was a royal ball ache trying to find out how to fix it
Don't do what rosswaa said
Why not?
What you should do is boot your phone into fastboot mode, connect it to your pc. Flash this modified TWRP recovery img to your phone https://www.androidfilehost.com/?fid=24459283995297945. After that you have to flash this modified SuperSU (through the new recovery) https://www.androidfilehost.com/?fid=24459283995297946.
The normal recovery doesn't work in OOS 3.0 (just like in HOS) and it's the SuperSU that gives you the soft brick. A dirty flash of the modified SuperSU should fix it.
I also had your problem and I did what rosswaa said which shouldn't be necessary (I lost all my data and backups).
I didn't lose anything, but I tried doing what you said and my bootloader was screwed so wouldn't take a flashed recovery or anything (yes the modified one)
Wish I hadnt been so excited and just flashed but all sorted now
Hmm okay, if it doesn't work with flashing the new recovery img then do what rosswaa said and after that follow this post https://forums.oneplus.net/threads/installation-instructions-faqs-oxygenos-3-0-0.439108/
Obviously try what green says first, if it works then happy days
first i am really glad that someone give some advices on me. But since i am a noob, how can i flash twrp in fastboot mode? using command? "fastboot flash recovery xxx.img"? thx
SPiCa39's said:
Guys... when i tried to flash oos 3.0 on my op2 through twrp, i first wiped the data to install new rom, then install oos 3.0, it failed. I then flashed the recovery i downloaded from the thread, then restart the recovery
I cant boot into the recovery.
System can't boot
Is it called "brick"?
So i tried to flash stock recovery in pc by command, but it says "remote: device is locked. cannot flash images". any solution to this problem?
I can boot into fastboot mode
Click to expand...
Click to collapse
1 Install official TWRP 3.x via fastboot twrp.me/devices/oneplustwo.html
Reboot to recovery
2 install this modified version of TWRP
forum.xda-developers.com/oneplus-2/development/recovery-teamwin-recovery-project-3-0-0-t3310713
Reboot to recovery
3 install oos3 (And supersu)
Sorry i can't post link
Hey guys,
I have a problem with a bricked xiaomi redmi 2 prime.
After a bootloop i tried to fix the problem with a system reset. But this does not work
After i booted into recovery and wiped all data, the phone reboot but than nothing happend. So i tried to flash the rom with the mi flash tool, but there i get the error "remote: failed to write partition".
So i went over to the adb and fastboot programms, with fastboot i erased system, userdata, recovery, boot and then i flashed the images of this elements back on the phone (fastboot flash sayed that flashing went successfully)
Then the phone reboot, nothing happend and i can´t get into recovery mode, also adb doesn´t recognoze the phone anymore
Have you any idea what i can do to fix the phone, or can i put it into the trash?
Thanks for your help
Stop experimenting.
Does fastboot work? Do a full flash with miflash(erasing all storage)(firmware should be of your model itself)
If fastboot doesnt work,try putting in the charger with battery in,if there is any vibration,you have a chance of reviving your r2
#fingerscrossed
Ezio95 said:
Hey guys,
I have a problem with a bricked xiaomi redmi 2 prime.
After a bootloop i tried to fix the problem with a system reset. But this does not work
After i booted into recovery and wiped all data, the phone reboot but than nothing happend. So i tried to flash the rom with the mi flash tool, but there i get the error "remote: failed to write partition".
So i went over to the adb and fastboot programms, with fastboot i erased system, userdata, recovery, boot and then i flashed the images of this elements back on the phone (fastboot flash sayed that flashing went successfully)
Then the phone reboot, nothing happend and i can´t get into recovery mode, also adb doesn´t recognoze the phone anymore
Have you any idea what i can do to fix the phone, or can i put it into the trash?
Thanks for your help
Click to expand...
Click to collapse
Yup actually download the latest version of miui fastboot files..paste them in the fastboot folder... Dont bother erasing you phn again(as it does erase at the time of writing new files...)And most importantly flashing only 3 files is more than enough. Flash them in the order boot.img, system.img, recovery.img and thats it. If your problem is actually not booting into fastboot then....press the volume down button and insert your usb while keeping it pressed.
Hey guys,
thanks for the answers. I tryed to flash only thees 3 files but it doesn´t change anything. fastboot works without trouble so far.
I tried multiple times the xiaomi flashing tool but this only throws errors -.-'
I will try again and keep you by the actual progress ^^
Ezio95 said:
Hey guys,
thanks for the answers. I tryed to flash only thees 3 files but it doesn´t change anything. fastboot works without trouble so far.
I tried multiple times the xiaomi flashing tool but this only throws errors -.-'
I will try again and keep you by the actual progress ^^
Click to expand...
Click to collapse
If you can get the fastboot to work, you can flash recovery on your phone for good or temporarily to flash zips.
How to do it?
1.Get into fastboot on phone
2.Install minimal adb and fastboot in your computer
3.Run adb and install drivers
4.Connect your phone which should be in fastboot to computer
5.Check for devices by using "fastboot devices", if a device is listed, proceed
6.Download a custom recovery, rename the recovery img to something easy than using the full name and copy the img into the folder where minimal adb and fastboot is installed
7.Type in "fastboot flash recovery <name you gave to recovery img>.img" (img for the image format) to flash recovery permanently
OR
7.Type in "fastboot boot <recovery name>.img" to use it temporarily, this method will erase the recovery on reboot so flash whatever you want before rebooting if you're following this method.
8.Flash in your ROM zip, try stock and custom ROMs, see if you can get your phone to work
GOOD LUCK
Same error with my yureka plus (error "remote: failed to write partition"). I'm planning to buy redmi 2 prime.. . Scared if this will happen to redmi 2 prime
OK, 3 days ago I rebooted my ZE551KL and it went into a bootloop. I was completely 100% stock. No root. Locked bootloader. Spent the better part of the weekend trying to troubleshoot it, and I have made almost zero progress.
I've tried a bunch of things, but here is my current status.
Can get into fastboot mode no problem.
POWER + DOWN VOL gets me into stock recovery, but at some point I flashed an older version. I tried flashing TWRP, but after install could never seem to get into it (is that because I'm unrooted and locked?)
Current recovery version: Android system recovery <3e> LRX22G.WW_user_1.16.40.763_20151201
I've tried flashing to a couple different firmware versions from the ASUS website both via ADB and via the SD Card.
Current firmware: UL-z00T-WW-1.17.40.1531-user.zip
Still in bootloop.
Any advice on rebuilding this thing from scratch? I dont care whether I just get stock back, or if I need to root/unlock, install TWRP and a custom ROM. Dont care, just want a functioing phone!
Thanks in advance.
ACFH said:
I dont get it. Did you factory reset your phone? With stock rom, factory work most of the time.
You said that you tried flashing TWRP. If you see successfull message after flash, type "fastboot reboot" and hold volume down button right after hit Enter. If you did right, you can get into twrp, then choses Wipe > format, it more powerfull than factory reset.
Click to expand...
Click to collapse
1. Factory reset from within the phone's OS? No, I cant get that far. Just constant bootloop on ASUS logo.
2. I've used the fastboot erase command to wipe everything, and used the wipe data/factory reset option in the stock recovery. Still bootloop.
3. I've tried flashing TWRP 3.0.0.0 and the newest version of TWRP. I hold down the VOL DOWN key before hitting enter on "fastboot reboot"; it just goes into a faster bootloop, like every half-second. When I release the VOL DOWN key, it goes into the same, slower original bootloop.
ACFH said:
Ok. You can format through fastboot
Code:
fastboot format userdata
fastboot format cache
If it still stuck in bootloop, try reflash boot and recovery, fastboot wipe system. Then copy update.zip to sdcard. Boot into recovery > install update from external sd.
Click to expand...
Click to collapse
Awesome. I'll give that a try and report the results.
I just downloaded the .img with the same date as my recovery version from here. https://asus.kremowka.xyz/categories/show/2
Its been hung at "Verifying update package...." for about 10 mins now. Once this is finished (and probably fails ); I'll give your format commands a try.
ACFH said:
Ok. You can format through fastboot
Code:
fastboot format userdata
fastboot format cache
If it still stuck in bootloop, try reflash boot and recovery, fastboot wipe system. Then copy update.zip to sdcard. Boot into recovery > install update from external sd.
Click to expand...
Click to collapse
Ugh. Didn't work. Here is what I did:
fastboot format userdata
fastboot format cache
fastboot erase system
fastboot format system
Reboot to recovery
install UL-z00T-WW-1.17.40.1531-user.zip from SD card.''
Installation successful.
Reboot.
In a bootloop that shows ASUS logo for 10-15 seconds, flashes a blue screen really quick, then reboots.
What can I try next?
Hi, I've been trying to get out of this situation for days.
My mi 9t went into boot loop after having wipe a twrp wipe.
Now if I try to flash a ROM it returns the antiroolback error check because my arb is 1 and the rom I find is 0.
I can't even install the twrp anymore, the installation process with fastboot is successful but it always restarts in fastboot and not in recovery.
Can someone help me?
m.92.grosso said:
Hi, I've been trying to get out of this situation for days.
My mi 9t went into boot loop after having wipe a twrp wipe.
Now if I try to flash a ROM it returns the antiroolback error check because my arb is 1 and the rom I find is 0.
I can't even install the twrp anymore, the installation process with fastboot is successful but it always restarts in fastboot and not in recovery.
Can someone help me?
Click to expand...
Click to collapse
Download this TWRP'S:
1. CHINESE TWRP - https://mega.nz/#!dVYX3SzT!CN2lTDmF3xmMlEw-LbU9xDWcFFmFdjcB_ZR1vnk_Gas
2. RUSSIAN TWRP - https://mega.nz/#!AcAlVITI!p15vuiNoSDxhViGzW1PhZwuAI9hMi3_k9FFzYiiLhoM
After installation one of these two (your choice ) TWRP'S, you can boot to your rom or:
1. FORMAT /data partition (NEVER wipe System or Persist!)
2. Copy ROM to the internal storage,
3. Install ROM,
4. Reboot,
5. Done!!!
Download Fastboot Rom
Extract
Reboot phone to fastboot
Open cmd
Go Inside folder
Type fastboot flash system system.img
Fastboot Flash Recovery recovery.img
Done
Hey there,
sorry, noob here.
Trying to get an old Redmi 7A up and running again:
Unlocked the bootloader
entered fastboot mode
flashed TWRP
booted successfully into TWRP
wiped data
rebooted into twrp
wiped system, data, dalvik and cache
twrp is gone, stock recovery returned
reflashed twrp
fastboot reboot recovery
back in fastboot
power off, power on
automcatically back in fastboot
I cannot access anything but fastboot now.
What am I missing, what did I do wrong?
Thank you very much!
If you're stuck into fastboot try reflashing the stock rom from the official xiaomi site here
Select the fastboot version of your rom, then use MiFlash Tools to revert back your rom using the flash_all_lock.bat file.
To make miflash to work I had to add a log folder and inside an empty [email protected] file before launching it otherwise you'll get errors.
i think your mistake was wiping before installing custom rom. Follow the instruction closely