today , I unlocked the bootloader of my Real Me 2 Pro and everything was fine and after I tried to boot it back to system after flashing magisk and the decryption.zip , I got this message saying " The current boot / recovery image have been destroyed and can not boot. Please flash the correct image or contact customer service to fix it"
I can just flash the official firmware or any ohter ROM but the PC can't seem to detect the fastboot mode and neither am I able to boot into fastboot / recovery.
can someone please help.!
vishnusai.karumuri said:
today , I unlocked the bootloader of my Real Me 2 Pro and everything was fine and after I tried to boot it back to system after flashing magisk and the decryption.zip , I got this message saying " The current boot / recovery image have been destroyed and can not boot. Please flash the correct image or contact customer service to fix it"
I can just flash the official firmware or any ohter ROM but the PC can't seem to detect the fastboot mode and neither am I able to boot into fastboot / recovery.
can someone please help.!
Click to expand...
Click to collapse
Hi, how about your phone? is your problem have solved?
i have same problem like you. and i want to know about to solve it
thank you
hi, my problem a bit different with recovery.
i have stock recovery with unlocked bootloader. im with coloros 5.2 and can not install coloros 6 update. stock recovery cant find update file in phone storage, wifi doesnt work and starting update from os, returns update failed after one reboot. and suggestion?
vishnusai.karumuri said:
today , I unlocked the bootloader of my Real Me 2 Pro and everything was fine and after I tried to boot it back to system after flashing magisk and the decryption.zip , I got this message saying " The current boot / recovery image have been destroyed and can not boot. Please flash the correct image or contact customer service to fix it"
I can just flash the official firmware or any ohter ROM but the PC can't seem to detect the fastboot mode and neither am I able to boot into fastboot / recovery.
can someone please help.!
Click to expand...
Click to collapse
I face the same issue. Flashed twrp. Then flashed boot+magisk+patched img file. Now the phone halts at the fastboot mode and is not booting up. It also unable to be power off. plz help. The model is Realme2 RMX 1805
Dont worry you do have a unlocked device so u need a pc to do that download system.img, vendor.img for your device and just open cmd then type this fastboot flash system system.img then fastboot flash vendor vendor.img and reboot it second method if you dont have an pc not sure that it will work you need a second device with otg support download bugjaeger app from playstore and use the same commands which i mention in pc method
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
Please help, I need proffessional help.
Android Phone: ASUS Zenfone 2 Laser 5.0 (ROOTED)
Android Firmware: 5.0.2 Lollipop
Aim: To enter into Fastboot mode and Recovery Mode without problems
Situation: Recently installed TWRP Recovery in-app and through software, but when I try to enter in Fastboot Mode (HOLD POWER & VOLUMEUP) or even Recovery Mode (HOLD POWER & VOLUMEDOWN), I just end up in a hanged out ASUS Logo. I can't do anything except pulling out the battery myself and putting it back then booting the device through power button to boot it normally. I don't know if it's the problem with the model, or the phone's system itself, or it's just a bug, or a problem when I rooted my device through ADB.
(Note: When I rooted the device, I wasn't even able to see the blue "FASTBOOT MODE" when I tried it, I only saw the ASUS logo as well.)
For anyone who has any idea on what's going on with my device, please reply and help me. I really want to have the benefits of a rooted phone completly and I'm a new root user so I need assistance.
For anyone who has an idea on what I've done or on what should I do, please help me. Someone told me that I flashed the recovery and locked the bootloader, so it got damaged. If so, would Unlocking the Bootloader (from Wiki.CyanogenMod's Site) help my case?
CrimsonShade09 said:
For anyone who has an idea on what I've done or on what should I do, please help me. Someone told me that I flashed the recovery and locked the bootloader, so it got damaged. If so, would Unlocking the Bootloader (from Wiki.CyanogenMod's Site) help my case?
Click to expand...
Click to collapse
Do you can acesse to twrp recovery on your device
Same problem.....waiting for helping, please
mohamedelkholy said:
Do you can acesse to twrp recovery on your device
Click to expand...
Click to collapse
I think I have "access" to TWRP recovery. However, I can only access it through booting it up from ADB. I used the command "adb reboot bootloader" to boot it to fastboot mode, however only the ASUS screen appears but I treated it as the fastboot mode itself. Then I checked if it was really on fastboot mode through "fastboot devices" and it showed my serial number. I can only enter into TWRP using "fastboot boot twrp.img" . I don't know if I already installed it because although I opened it, I can't do it from the phone (POWER+VOLUMEDOWN)
Ok now boot twrp and then flashamodified zip or cm13 and your phone should eork you dhould to have unlockrd bootloader
Hi to all, i'd re-open this 3d for the same problem. After months I'm trying to re-sleep my ZE500KL. It was in "can't load invalid boot image" loop. I tried to force recovery mode and (wrongly) force to update from update.zip the stock fw stored in the uSD.
Since this time I can't enter in recovery mode more but fastboot only. The problem is that, in spite of the USB drivers are installed, fastboot does not recognize any connected device.
I've run Win 10 pro with a zenbook ux333fn laptop and I remembered android 6 on the phone, the last time I saw it alive.
I've tried also to install twrp 3.1, with no positive results.
Anyone can suggest me any solving way?
Thanks to all
...anybody?
Up.....
sh4d3_ said:
Hi to all, i'd re-open this 3d for the same problem. After months I'm trying to re-sleep my ZE500KL. It was in "can't load invalid boot image" loop. I tried to force recovery mode and (wrongly) force to update from update.zip the stock fw stored in the uSD.
Since this time I can't enter in recovery mode more but fastboot only. The problem is that, in spite of the USB drivers are installed, fastboot does not recognize any connected device.
I've run Win 10 pro with a zenbook ux333fn laptop and I remembered android 6 on the phone, the last time I saw it alive.
I've tried also to install twrp 3.1, with no positive results.
Anyone can suggest me any solving way?
Thanks to all
Click to expand...
Click to collapse
Up...
QFIL or AFT can be the solution.
I have a similar problem, a hard bricked Z00ED (ZE500KL) not able to get into fastboot or recovery.
after reading some thread here an there. that are Processor / Chipset specific flash tools that help flash bootloaders and repartition hard bricked device.
For mobiles with MediaTec devices, there is a tool called SP Flash Tool. I wasted a whole day with it. then understood that Z00ED (ZE500KL) has a Qualcomm Processor MSM8916
Therefore we need a Qualcomm Flasher here (QFIL )
But nos I am stuck with getting firmware for ZE500KL that can be used by QFIL tool, It should have a firehouse*.mbr file that is the programmer (dependent on CPU of the phone) and a rawprogram*.hex file that I don't know where to get from.
Thanks... It seems a bit less wild, but in any case no solving, yet
Up! ...anyone?
Up!
so i accidentally wiper my os using TWRP
now my device has no os or recovery
i can boot to FASTBOOT but whenever i try to use the comand FASTBOOT FLASH etc it says "remote: command not allowed "
the hardware is ok i guess because i can boot to the erecovery but also failed to download the software there , the dload update.app method didn't work "because my phone doesn't have a recovery installed section in "
so what to do ? how to get my system on again am using windows 10 64 bit !
also what box i can use to flash my OS ?
notes:
1- No OS at all
2- Unlocked bootloader
3- FRO locked "idk what is this "
4- Phone boots only to fastboot
5- No recovery at all
so i really do need your help guys am in a blackout down here :/
maybe bootloader got locked... try to unlock it again
FlaimeR said:
so i accidentally wiper my os using TWRP
now my device has no os or recovery
i can boot to FASTBOOT but whenever i try to use the comand FASTBOOT FLASH etc it says "remote: command not allowed "
the hardware is ok i guess because i can boot to the erecovery but also failed to download the software there , the dload update.app method didn't work "because my phone doesn't have a recovery installed section in "
so what to do ? how to get my system on again am using windows 10 64 bit !
also what box i can use to flash my OS ?
notes:
1- No OS at all
2- Unlocked bootloader
3- FRO locked "idk what is this "
4- Phone boots only to fastboot
5- No recovery at all
so i really do need your help guys am in a blackout down here :/
Click to expand...
Click to collapse
first thing, make sure you indeed unlocked your bootloader
If fastboot flash commands fail with command not allowed, there is a big chance that the dload/update.app method fails after 5% as well which means you are trying to flash wrong image (e.g. trying to install L31 onto L21 hardware or vice versa), so make sure you download correct firmware for your hardware and try the dload/update.app method.
Try that : http://forum.xda-developers.com/hua...-downgrade-nougat-to-mm-t3515029#post69987605
i solved it by flashing in a nearby shop , thanks for ur help everyone ^_^
thread closing needed !
Hello,
I need help about my yureka plus on android (YU5510A),
I bought yureka plus yesterday and it comes on stock android 4.4.4 (Kitkat), I try to install custom rom and connect my phone to my laptop with help of YUWARE and try to unlock the bootloader in fastboot mode, it shows the successful message, but phone cant restart, I restart it manually, but it stuck on Yureka logo, trying again for flashing TWRP, same thing happen.
My phone (YU5510A) stuck on yureka plus logo.
So please help me.
Best Regards
Sadique A
sadique2804 said:
Hello,
I need help about my yureka plus on android (YU5510A),
I bought yureka plus yesterday and it comes on stock android 4.4.4 (Kitkat), I try to install custom rom and connect my phone to my laptop with help of YUWARE and try to unlock the bootloader in fastboot mode, it shows the successful message, but phone cant restart, I restart it manually, but it stuck on Yureka logo, trying again for flashing TWRP, same thing happen.
My phone (YU5510A) stuck on yureka plus logo.
So please help me.
Best Regards
Sadique A
Click to expand...
Click to collapse
your device is soft bricked from where i see,
download the drives first for your device link :- https://androidmtk.com/download-yu-usb-driver
download adb platform tools:- https://dl.google.com/android/reposi...st-windows.zip
download recovery:- https://dl.twrp.me/tomato/
download the fast-boot firmware:- http://builds.cyngn.com/factory/tomato/cm-12.1-YOG4PAS8A4-tomato-signed-fastboot-a7a306cebd.zip
download factory image maker :- https://drive.google.com/open?id=0BxGRG9YXw62rUWNLMjdNaGt1a2s
method 1
extract the fast boot firmware and factory image maker in same folder. then follow these steps.
put your phone in fast-boot mode and type fastboot -i 0x1ebf oem unlock (will unlock your bootloader)
and now find flash_all.bat file in the folder where you extracted all files and run as admin. let the process finish you would be back at stock firmware with no boot loops.
if you don't want to go to factory image then
method 2
boot your phone in fastboot and type
fastboot -i 0x1ebf oem lock (to lock your bootloader)
fastboot -i 0x1ebf oem unlock (to unlock your boot loader) as you used yuware or something that might created problem in bootloader so follow both.
fastboot -i 0x1ebf flash recovery name_of_recovery.img
and let it flash recovery then boot into recovery go to advance wipe format data type yes and swipe, install any custom rom and flash gapps done.
if you face still boot loops follow method 1 and flash roms later.
P.s while in fast-boot remove sim cards and memory cards from your phone and then run any commands.
and while flashing any roms please do remove sim cards.
Bhavesh_khatri said:
your device is soft bricked from where i see,
download the drives first for your device link :- https://androidmtk.com/download-yu-usb-driver
download adb platform tools:- https://dl.google.com/android/reposi...st-windows.zip
download recovery:- https://dl.twrp.me/tomato/
download the fast-boot firmware:- http://builds.cyngn.com/factory/tomato/cm-12.1-YOG4PAS8A4-tomato-signed-fastboot-a7a306cebd.zip
download factory image maker :- https://drive.google.com/open?id=0BxGRG9YXw62rUWNLMjdNaGt1a2s
method 1
extract the fast boot firmware and factory image maker in same folder. then follow these steps.
put your phone in fast-boot mode and type fastboot -i 0x1ebf oem unlock (will unlock your bootloader)
and now find flash_all.bat file in the folder where you extracted all files and run as admin. let the process finish you would be back at stock firmware with no boot loops.
if you don't want to go to factory image then
method 2
boot your phone in fastboot and type
fastboot -i 0x1ebf oem lock (to lock your bootloader)
fastboot -i 0x1ebf oem unlock (to unlock your boot loader) as you used yuware or something that might created problem in bootloader so follow both.
fastboot -i 0x1ebf flash recovery name_of_recovery.img
and let it flash recovery then boot into recovery go to advance wipe format data type yes and swipe, install any custom rom and flash gapps done.
if you face still boot loops follow method 1 and flash roms later.
P.s while in fast-boot remove sim cards and memory cards from your phone and then run any commands.
and while flashing any roms please do remove sim cards.
Click to expand...
Click to collapse
Need custom recovery
TWRP 3.0.2 not supported by YU5510A
sadique2804 said:
Need custom recovery
TWRP 3.0.2 not supported by YU5510A
Click to expand...
Click to collapse
TWRP is custom recovery itself, using it on my device since year, works fine you might have flashed wrong twrp. Try rom the link provided and remove every thing from phone before flashing twrp.
Bhavesh_khatri said:
TWRP is custom recovery itself, using it on my device since year, works fine you might have flashed wrong twrp. Try rom the link provided and remove every thing from phone before flashing twrp.
Click to expand...
Click to collapse
I know TWRP is custom recovery
But in my phone (YU5510A, Stock Android 4.4.4) it is not supported.
Whenever I am trying to install, it corrupt the recovery and the firmware of my phone.
After installing TWRP 3.0.2.0 (downloaded from official website under tomato section) my phone cant boot, it stuck on YU logo.
If you have the link please share.
sadique2804 said:
I know TWRP is custom recovery
But in my phone (YU5510A, Stock Android 4.4.4) it is not supported.
Whenever I am trying to install, it corrupt the recovery and the firmware of my phone.
After installing TWRP 3.0.2.0 (downloaded from official website under tomato section) my phone cant boot, it stuck on YU logo.
If you have the link please share.
Click to expand...
Click to collapse
Like i said your device is soft bricked try methods i suggested, but recovery should work fine press vol up+ vol down+power button to boot into recovery you would be able to use TWRP. if not try to flash recovery again as i said yuware might have introduced some bugs install as i suggested. your device stuck at boot loop has nothing to do with recovery not working.
---------- Post added at 08:03 PM ---------- Previous post was at 07:50 PM ----------
Try to flash older versions here is 2.8.4.0 if you on kit-kat or any,
https://dl.twrp.me/tomato/twrp-2.8.4.0-tomato.img
https://dl.twrp.me/tomato/twrp-2.8.5.0-tomato.img
https://dl.twrp.me/tomato/twrp-2.8.6.0-tomato.img
type
fastboot -i 0x1ebf flash recovery twrp-2.8.4.0-tomato.img
remove simcards and memory cards while flashing. hope this helps.
I flashed cm12.1 officially signed, and it worked and i recovered my device, but i want to flashed custom rom and it needs a custom recovery.
That's the problem, and I tried 2.8.7 and 2.8.6 and 2.8.5.
Currently I am on official cm12.1 with cm recovery.
I m also facing same problem.
---------- Post added at 08:26 PM ---------- Previous post was at 08:26 PM ----------
sadique2804 said:
I flashed cm12.1 officially signed, and it worked and i recovered my device, but i want to flashed custom rom and it needs a custom recovery.
That's the problem, and I tried 2.8.7 and 2.8.6 and 2.8.5.
Currently I am on official cm12.1 with cm recovery.
Click to expand...
Click to collapse
Your problem solved bro?
sadique2804 said:
I know TWRP is custom recovery
But in my phone (YU5510A, Stock Android 4.4.4) it is not supported.
Whenever I am trying to install, it corrupt the recovery and the firmware of my phone.
After installing TWRP 3.0.2.0 (downloaded from official website under tomato section) my phone cant boot, it stuck on YU logo.
If you have the link please share.
Click to expand...
Click to collapse
TRY TO UNLOCK BOOTLOADER FIRST.
Twrp won't install properly if the bootloader is locked.
IF THIS HELPS CLICK THANKS :good:
Hangs twrp
My phone got hanged at twrp yureka plus yu5510A stock lollipop plz help
ray pember said:
My phone got hanged at twrp yureka plus yu5510A stock lollipop plz help
Click to expand...
Click to collapse
Flash latest version of twrp using adb
Here is the link
https://dl.twrp.me/tomato/twrp-3.1.1-0-tomato.img.html
My device 5510a I install twrp but touch not working properly so plz help me....next what I do
sadique2804 said:
Hello,
I need help about my yureka plus on android (YU5510A),
I bought yureka plus yesterday and it comes on stock android 4.4.4 (Kitkat), I try to install custom rom and connect my phone to my laptop with help of YUWARE and try to unlock the bootloader in fastboot mode, it shows the successful message, but phone cant restart, I restart it manually, but it stuck on Yureka logo, trying again for flashing TWRP, same thing happen.
My phone (YU5510A) stuck on yureka plus logo.
So please help me.
Best Regards
Sadique A
Click to expand...
Click to collapse
hello for yureka i have some files I hope u don't try fastboot cause yureka have limited rom memory i have some files i encountered the worst case . i went to local vendor he did it for 3dollar. nd yes i read some yureka have a different board in the differnet country so files are bit messed up feel free to message i have somefiles try the luck or better search other thread developers are not doing a lot nowadays i was trying ubuntu but somehow sad life
Hii I have yu yureka plus (yu5510a) the phone is starting and stuck at YU logo after that blue screen appears and phone can't go ahead .
And When i connect the phone with pc it can't detected and an error shows in phone that "do not disconnect the data cable" & in bottom left "your phone is not secure" please help
So, I tried unlocking ZE520KL with ASUS Flash Tool, and after 25 mins of flashing image I disconnected the device. Now, the device only boots into factory mode and recovery mode. Bootloader doesn't work and internal storage isn't mounted when I use the option Install update from SD card, but MicroSD works.
I had the latest update installed before this happened. I tried the latest firmware from the site and installed it via recovery but it shows signature verification failed. The same thing happens if I try to delete the first few lines of the updater script in the META-INF folder.
So help me guys, which firmware should I use and how should I use it? Even ADB sideload didn't work.
Try fastboot flash 'recovery.img', the same version from a firmware you're about to flash than flash the zip from recovery
sanctitude888 said:
Try fastboot flash 'recovery.img', the same version from a firmware you're about to flash than flash the zip from recovery
Click to expand...
Click to collapse
Thanks man. I figured it out though. I flashed the stock MM ROM and it worked. BTW, are there any ports of the stock camera? I really need the stock camera
Hi, my Zenfone 3 is stuck on bootloader screen and reboots again and again ... unable to use my fone
ruchikapoor said:
Hi, my Zenfone 3 is stuck on bootloader screen and reboots again and again ... unable to use my fone
Click to expand...
Click to collapse
Can you enter and stay on fastboot steadily? You need to obtain the whole stock ROM along with fastboot and recovery image from the very same package. Fastboot flash the fastboot and recovery image then flash the ROM from recovery.