Hi, I tried to install crDroid ROM on my Huawei y5 2017 and bricked it.
Now, it only boots at TWRP and fastboot.
I had nandroid backup but it didn't work.
I tried flashing RR and miui ROM , but didn't work.
Please provide me the stock ROM of huawei y5 2017 MYA-L22. This is a newly bought phone and I don't want to lose it. Please help me??????
HUAWEI Y5 2017 Bricked
kkboss said:
Hi, I tried to install crDroid ROM on my Huawei y5 2017 and bricked it.
Now, it only boots at TWRP and fastboot.
I had nandroid backup but it didn't work.
I tried flashing RR and miui ROM , but didn't work.
Please provide me the stock ROM of huawei y5 2017 MYA-L22. This is a newly bought phone and I don't want to lose it. Please help me
Click to expand...
Click to collapse
Same here!
I think crDroid ROM reformatted the Boot partition as f2fs and everything fails from here in.
I need urgent help too
I've tried everything I can find on the net
BTW mine has an unlocked bootloader
enviro8 said:
Same here!
I think crDroid ROM reformatted the Boot partition as f2fs and everything fails from here in.
I need urgent help too
I've tried everything I can find on the net
BTW mine has an unlocked bootloader
Click to expand...
Click to collapse
I have TWRP also but nandroid backup didn't work. Can you provide me stock recovery?
When you do a restore do you get a message that says something like: 'Warning:this data backup was made with f2fs file system. The backup may not boot unless you change it to f2fs."?
Mine did, but I modified the back up data files to ext4 and change the data file system to ext4 in TWRP.
But I still had to do the 3 button method to get it to finally boot.
I got lucky and managed to get my Y5 2017 going by holding down volume up and volume down keys until it finally booted up.
However, as I was trying everything I am not sure of what stage I did this, after it rebooted into TWRP or after EMUI download screen came up or after the bootloader unlocked warning screen, etc.
I will try to replicate the actions when I feel a bit braver.
I have found a stock firmware (I think). It can be downloaded from:
http://combinefile.com/home/browse/...w_Official_Firmware_Flash_File_By_Combinefile
It has several upgrade methods:
OTA upgrade
SD Card upgrade
USB upgrade
Upgrade tools&drivers
Download and keep unzipping
Under SD Card upgrade you will find UPDATE.APP
This is the one that the next two youtube methods use
How To Flash Huawei Dlord(UPDATE.APP) In Fastboot Mode
https://www.youtube.com/watch?v=OKRTbv-6Kzc
Using Update.app to load firmware
https://www.youtube.com/watch?v=Rhru9rCA8-8
There are some other ways to do it listed in the file, but I am not sufficiently confident as yet.
Good Luck
Hi. I am also needing a Huawei Y5 (2017) Stock Rom [MYA-L02].
But before thinking about flashing, I must get past the "Bootloader unlocked" message screen at startup (The screen with orange texts and (1) (2) (3) options below.)
Currently, the phone does not boot even when it says "The phone is booting now..." It just restarts, and repeats the same again. I can't boot to erecovery with VolUp button because I had it overwritten with TWRP (corrupted perhaps), and I can't go to fastboot with Power+VolDown buttons for some reason. Basically, I cannot do anything with hardware keys. Without seeing the Huawei boot animation, PC commands in adb console are useless too.
I can't even turn the device off with Power button. I cannot remove the battery pack because I'm afraid I may lose warranty (a sticker is atop of the battery which cannot be tampered).
My last option is to let the battery drain and try the hardware keys again.
With this, I am requesting assistance from you developers.
It may not help but it worked on mine.
Where ever you are, push in and hold in the power button for quite a long time to turn it off.
enviro8 said:
I got lucky and managed to get my Y5 2017 going by holding down volume up and volume down keys until it finally booted up.
However, as I was trying everything I am not sure of what stage I did this, after it rebooted into TWRP or after EMUI download screen came up or after the bootloader unlocked warning screen, etc.
...
Good Luck
Click to expand...
Click to collapse
Are you confirming Y5 2017 can run custom ROM like EMUI ?
ar_156 said:
Are you confirming Y5 2017 can run custom ROM like EMUI ?
Click to expand...
Click to collapse
Emui is the Huawei framework and not a custom ROM. I think your getting confused with MIUI which is available as custom ROM for some phone.
There are no custom time available for our phone that I know of, but it can be rooted and with the use of TWRP, Magisk and Xposed the stock ROM can be customized.
ar_156 said:
Are you confirming Y5 2017 can run custom ROM like EMUI ?
Click to expand...
Click to collapse
No. the EMUI allows updates to be downloaded and installed via update.app. However if the base unit is unlocked and/or rooted the download fails.
The other choices offered in the EMUI screen are reboot and turn off.
Importance of getting up this screen is that you can communicate between the phone and a PC via ADB and FASTBOOT while in it, This permits the major ROM elements to be flashed to the phone ROM and unbrick it. The 3 elements are system.img, boot.img and recovery.img.
Additionally, if you can turn off the phone from the EMUI screen, you can directly enter FASTBOOT and flash the img files to the ROM.
You can extract system.img, boot.img and recovery.img from a stock update.app file and when flashed the phone will reboot into the way it was as new (depending on what the update.app version is)
To force the phone into the EMUI screen I did the following:
At the unlocked warning screen I held the Vol up and down buttons firmly for around 30 - 40 seconds and when the warning screen comes up release the Vol up and keep holding down the Vol down button. The unit will cycle a number of times and the EMUI screen should come up.
If the phone is off, you can go directly to FASTBOOT simply by holding down the Vol down button and the connect the phone to you PC via the USB cable.
To do this you need to install HUAWEI drivers and to get ADB and FASTBOOT.
If you get this far, I can guide you the rest of the way but you must be able to get to the EMUI screen and/or turn the phone off.
It is a bit of a tedious method, though it works and puts you back into an unrooted stock ROM.
However I still am unable to relock the phone.
BTW FASTBOOT can be used to load the TWRP recovery on the phone.
Additionally, the HUAWEI Y5 2017 phone has the following aliases - MYA-L02, MYA-L03, MYA-L22 and MYS-L23 and MYA is often termed MAYA.
Are these fake?
MIUI 9Pro (port) v7.12.7 for Y5 (2017): https://4pda.ru/forum/index.php?showtopic=823938&st=600#entry67801731
CrDroidAndroid (port) 7.1.2 for Y5 (2017): https://4pda.ru/forum/index.php?showtopic=823938&st=600#entry67802080
ar_156 said:
Are these fake?
MIUI 9Pro (port) v7.12.7 for Y5 (2017): https://4pda.ru/forum/index.php?showtopic=823938&st=600#entry67801731
CrDroidAndroid (port) 7.1.2 for Y5 (2017): https://4pda.ru/forum/index.php?showtopic=823938&st=600#entry67802080
Click to expand...
Click to collapse
Unfortunately I can't read Russian. Anybody here can translate?
BETA VERSION CrDroidAndroid (port) based on Android 7.1.2
as changes are made this post will be updated
Source, link to the donor with description and pictures <-
Port spread "as is" solely for the purposes of familiarization and possible revision by enthusiasts.
Backup is mandatory.
Everything you do with your device you do at your own peril and risk! Responsibility for the breakdown, loss of data and other consequences I can not bear.
What changes in the donor:
#
Kernel:
* Replaced Kernel-image from the firmware C10B125
* Fixed fstab.mt6735 to mount the "Data" section . we have f2fs, not ext4
* Corrected init.mt6735.rc and init.project.rc sections #Camera - values taken from C10B125 firmware
* Forced Permissive, encryption disabled, Secureboot disabled .
* Replaced the boot logo, which is without the yellow letters.
System:
* Replaced system \ etc \ trustzone.bin for the stock from the firmware C10B125
* Replaced the contents of the folder system \ etc \ firmware to the stock from the firmware C10B125 (firewood from wireless modules)
* Replaced the contents of the folder system \ etc \ mddb to the stock from the firmware C10B125 (network calibration, etc.)
* Replaced bootanimation \ system \ media \ bootanimation.zip
* Edited buil.prop - almost everywhere now it displays MYA-L22, and so Also introduced some "tweaks"
* Edited system \ usr \ keylayout \ mtk-kpd.kl the line "key 485 SMARTKEY" was replaced by "key 485 MEDIA_PLAY_PAUSE" (to enable the smart button)
* The binaries and the library of the GPS module were changed: system \ xbin \ BGW, mnld system \ lib \ libmnl.so
* The installer contains the patch "FIX NVRAM" - corrects the WiFi error on the Ciagency-based OS
* Replaced libraries for the camera, are taken from the firmware C10B125.
List (most likely some of them are superfluous, but once it works, then ..):
What works:
#
+ Led-indication (LED) works both on the drain (green / red)
+ SMS receives and sends.
+ 2 / 3G catches including mobile Internet.
+ GPS works.
+ WiFi (including as an access point).
+ BT with my clock synchronized and files transferred.
+ FM radio-works (in any case, hisses)))
+ Various multimedia
+ Standard browser works
+ 2x window mode works
+ For those who care about it - Combining drives, checked-works.
+ LiveDispley - night mode, read mode, blue filter no matter how the review, in general it works and almost without animation brakes.
+ Additional button - works
+ Camera. As it should be 8mp rear, 5mp front, both flashes, does not blush, does not green, photos are saved, the video is removed, autofocus plows.
+ Engineering menu-works, call through the utility.
+ Compass (patch below)
+ System ROOT - activate and control access in the "for developers" menu / in Beta2 SuperSu is used .
+ Google Playmarket - of all gaps the current it. So it was at the source and it suits me. All the rest download through the market.
At the moment, the main glitches and flaws:
#
* Beta2 - WiFi does not work immediately after installation. It is treated with a patch on the compass! (ie one patch will fix both)
* Connecting and using the bluetooth headset causes terrible brakes
* Some videos on YouTube (via the application) break up into squares. Through the browser, everything loses normally. I'm using Tubemate and everything is ok.
-all the rest in your feedbacks
Installation:
#
As zip-installer through TWRP, preliminary making wipe dalvick, cache, system, data . Ideally, internal memory is also desirable.
Download (Yandex disk) <-
Download Beta2 (Yandex disk) <-
Additionally:
#
Patches, install through TWRP. After installing the system and first downloading it , as needed.
If the error when turning WiFi on (nvram warning err = x10) is set to <-
If the compass does not plow and WiFi does not turn on in beta2, set it <- Separate patch to camera <-
ar_156 said:
Are these fake?
MIUI 9Pro (port) v7.12.7 for Y5 (2017): https://4pda.ru/forum/index.php?showtopic=823938&st=600#entry67801731
CrDroidAndroid (port) 7.1.2 for Y5 (2017): https://4pda.ru/forum/index.php?showtopic=823938&st=600#entry67802080
Click to expand...
Click to collapse
no they are real , i have installed MIUI 9Pro and works well
Aleko91 said:
no they are real , i have installed MIUI 9Pro and works well
Click to expand...
Click to collapse
I installed CRDroid through TWRP and it bricked my Y5 several times.
This has been reported on several forums as happening by a number of users
On reboot it cycles between the unlocked warning and a screen stating that the storage is locked and to enter an unlock password.
When a password is entered that looks correct, it states that the password was correct but the action was corrupt and to do a factory reset to fix it.
Since I had deleted the system when in TWRP, I used the TWRP factory reset but the message came up again. I cycled through this several times and finally just entered a few random letters as the password and when it said that the password was correct I knew that I was in trouble.
When I got back to TWRP I wiped everything and still got the problem..
I then wiped everything and tried to restore a saved backup, the problem remained.
I then installed MIUI 9Pro and it installed OK but an error panel kept popping up covering the screen. Also the problem with MIUI was that the three software keys, home, back and ?? were missing and it appeared that it worked only with hardware keys which the Y5 does not have.
The error message kept popping up and it was difficult to use the phone and I managed finally to boot into recovery and after deleting the required partitions I restored it and it worked as before I loaded CRDroid.
BTW I have bricked it several times with the warning screen static and/or cycling between it and the Huawei boot flower and I managed to unbrick it.
To unbrick you need to get into TWRP or to get it to power off and then you can install a stock ROM or boot partition from TWRP or use fastboot to install stock boot, system and recovery partitions extracted from an update.app (used to automatically update a locked unrooted phone).
Huawei drivers and adb and fastboot need to be on your PC with the phone plugged into your PC.
enviro8
drdroid rom had problems on my y5 also . but in this 3 roms i think MIUI 9Pro is best yet ...
waiting for new , stable rom for this phone
Aleko91 said:
enviro8
drdroid rom had problems on my y5 also . but in this 3 roms i think MIUI 9Pro is best yet ...
waiting for new , stable rom for this phone
Click to expand...
Click to collapse
How did you get the three software icons back, home and the square to show up?
When I used MIUI they were hidden and I could not go any further. Also an error panel kept popping up and I couldn't get past it.
can you link me to an English forum about ROMs for Y5 (2017)? the translated russian is not easy to understand...
enviro8
y5 is my brother's phone , i have galaxy j320f ...
but i can surely (100%) say that u can show hidden 3 buttons in settings . by default yes , its hidden ... try to find in setting > Additional Settings > Key and Gesture shortcut , or button and gesture shortcuts ...
enviro8 said:
I installed CRDroid through TWRP and it bricked my Y5 several times.
This has been reported on several forums as happening by a number of users
On reboot it cycles between the unlocked warning and a screen stating that the storage is locked and to enter an unlock password.
When a password is entered that looks correct, it states that the password was correct but the action was corrupt and to do a factory reset to fix it.
Since I had deleted the system when in TWRP, I used the TWRP factory reset but the message came up again. I cycled through this several times and finally just entered a few random letters as the password and when it said that the password was correct I knew that I was in trouble.
When I got back to TWRP I wiped everything and still got the problem..
I then wiped everything and tried to restore a saved backup, the problem remained.
I then installed MIUI 9Pro and it installed OK but an error panel kept popping up covering the screen. Also the problem with MIUI was that the three software keys, home, back and ?? were missing and it appeared that it worked only with hardware keys which the Y5 does not have.
The error message kept popping up and it was difficult to use the phone and I managed finally to boot into recovery and after deleting the required partitions I restored it and it worked as before I loaded CRDroid.
BTW I have bricked it several times with the warning screen static and/or cycling between it and the Huawei boot flower and I managed to unbrick it.
To unbrick you need to get into TWRP or to get it to power off and then you can install a stock ROM or boot partition from TWRP or use fastboot to install stock boot, system and recovery partitions extracted from an update.app (used to automatically update a locked unrooted phone).
Huawei drivers and adb and fastboot need to be on your PC with the phone plugged into your PC.
Click to expand...
Click to collapse
Where are you getting the stock partitions from?
I just got one of these and am now stuck with a phone that boots straight to TWRP but I can also get to fastboot.
Related
Any expert who can HELP!!!
i have an asus a500KL zenfone 5 tried software update after reboot got ERROR: invalid boot image
i am fairly experienced with root access, custom roms however this device was never rooted and have been trying to fix this issue for a few days.
I am able to get to csc mode, also powering off and entering BLUE SCREEN csc mode holding power ands vol up for 3 cycles until the screen goes blue, even installed different drivers and full restart of pc and phone, still not work.
I have tried ALL the flash asus tools and everything. tried a few intels but they dont even begin to work as mine is an ARM.
fastboot recognises csc mode!!!
I can flash a boot.img but that is it, does not change the situation.
Everything else gets an error, something like ERROR: Security prevents this action or something about it being locked. I think it might mean the bootloader is locked and cant access anything pretty much.
I have tried every key combination under the sun. (Timing, P + (+), P + (-), P + (+ & -), in all combos and timing combos.
Power + Vol Down gets me to the SD Update option.
CLick the top to continue and the bottom to reboot.
I have tried both and they both take me to the ERROR: invalid boot image
im stumped.
Ive Messed with HTC, Samsungs, Sony, Huawei for gods sake, even iphones and have never come across an issue like this that is so impossible to fix. I think i may have hit my first brick.
Any help will be greatly appreciated.
Regards
I have the same problem...
I have tried everything and I am still stuck with csc mode.
Please help
Best!
jaza-g said:
Any expert who can HELP!!!
i have an asus a500KL zenfone 5 tried software update after reboot got ERROR: invalid boot image
i am fairly experienced with root access, custom roms however this device was never rooted and have been trying to fix this issue for a few days.
I am able to get to csc mode, also powering off and entering BLUE SCREEN csc mode holding power ands vol up for 3 cycles until the screen goes blue, even installed different drivers and full restart of pc and phone, still not work.
I have tried ALL the flash asus tools and everything. tried a few intels but they dont even begin to work as mine is an ARM.
fastboot recognises csc mode!!!
I can flash a boot.img but that is it, does not change the situation.
Everything else gets an error, something like ERROR: Security prevents this action or something about it being locked. I think it might mean the bootloader is locked and cant access anything pretty much.
I have tried every key combination under the sun. (Timing, P + (+), P + (-), P + (+ & -), in all combos and timing combos.
Power + Vol Down gets me to the SD Update option.
CLick the top to continue and the bottom to reboot.
I have tried both and they both take me to the ERROR: invalid boot image
im stumped.
Ive Messed with HTC, Samsungs, Sony, Huawei for gods sake, even iphones and have never come across an issue like this that is so impossible to fix. I think i may have hit my first brick.
Any help will be greatly appreciated.
Regards
Click to expand...
Click to collapse
Do you happen to be QDLOAD mode or QHSUSB? My experience working with SD400 devices, you need to nuke one of your partition to be able entering QDLOAD mode.
edit : For some reason I believe the CSC mode you got into is actually fastboot mode. Did you tried running any fastboot command? If fastboot cant detect, manually replace csc driver in device manager with fastboot driver.
Can you provide a picture of the error codes ?
http://imgur.com/QQ7OxDZ
like this i believe?Im having the same problem
Hi All,
If you have CSC MODE and ERROR: INVALID BOOT IMAGE
I found a solution, that is worked for me.
You don't have to turn on the USB debugging on your phone, connect to the PC, etc.
Steps:
1. Download recovery.img from Official Stock ROM (e.g. WW_12.4.5.58)
1.1. IMPORTANT: Only apply to same SKU update, Example: WW->WW, CN->CN, TW->TW
2. Download Official Firmware from asus.com/Phone/ZenFone_5_A500KL/HelpDesk_Download/ (e.g. UL-ASUS_T00P-WW-12.4.5.58-user.zip)
2.1. Read the Description!!!
2.2. IMPORTANT: Only apply to same SKU update, Example: WW->WW, CN->CN, TW->TW
3. Copy the recovery.img and the <firmware>.zip files to the root of external SD card
4. Power off your device
5. Simultanously push the Power + Volume Down button and waiting for the choice screen
5.1. Choice screen:
1. Enter SD download mode
2. Exit update mode
6. Choose the "1. Enter SD download mode"
7. Choose the "apply update from external storage"
8. Choose the the <firmware>.zip file (e.g. UL-ASUS_T00P-WW-12.4.5.58-user.zip)
9. Waiting for the installation finished
10. Choose the "reboot system now"
Best Regards,
R.
invalid boot image means doesn't go to boot loader, how can i update from sd card then ?
Steve Al-Mousa said:
invalid boot image means doesn't go to boot loader, how can i update from sd card then ?
Click to expand...
Click to collapse
boot doesnt mean bootloader...
thanks for the explaination, I'm not an expert in this, just having this problem since i upgraded the firmware by OTA rebooted and got stuck, I've tried all methods here but useless, i can go to csc only, i get invalid boot image when i go to sd download... any suggestions ?
thanks
Try this
https://forum.xda-developers.com/zenfone-5/general/stock-a500kl-zenfone-5-lte-t3303475
Did you ever get this sorted? I have the same issue......
Steve Al-Mousa said:
thanks for the explaination, I'm not an expert in this, just having this problem since i upgraded the firmware by OTA rebooted and got stuck, I've tried all methods here but useless, i can go to csc only, i get invalid boot image when i go to sd download... any suggestions ?
thanks
Click to expand...
Click to collapse
Dagk66 said:
Did you ever get this sorted? I have the same issue......
Click to expand...
Click to collapse
I have been informed by the stupid Asus Thailand that the main board should be changed
Hello Fellows,
First I'd like to explain my situation in details.
my phone fell while i was walking on the street and it got some dirt on it, so ( foolishly ) I decided to clean it.... and yeah... i washed my phone like washing a dish... i like rinsed the phone in water and in other cleaning liquids for no more than 3 seconds it was all quick thingy... anyway after washing it.... i directly powered it ON and it powered but the screen was OFF ( so i decided to power it OFF, solder it and to remove any clues of water inside on the board or something... after that i used a hairdryer ( which is not recommended ) but i used it at a descent distance so that no harm would be caused to the board... as i was only subjecting air to let water if any existed to dry..
i put the phone in rise and kept it for 1 day... after 1 day i wanted to check out how stuff went.. so i powered it ON and the screen actually turned ON and the vibrator, even the hardware back-light lighted up perfectly but here's the problem I'm facing.
the phone only boots into TWRP 3.1.0.0 no matter what i do.. things i tried:
1- flashed some ROM, through TWRP
2- used "Fixed Contexts" in TWRP
3- Repair File System "System partition" through TWRP
4- used file manager inside TWRP and checked if the internal storage is working and indeed i can show all my files, through TWRP
5- also used the file manager to access "System" Partition and everything was there, through TWRP
6- change File System into EXT4 "System partition" through TWRP
7- Resize File System "System partition" through TWRP
8- Wiping all Partitions "Excluding the internal storage"
and NON WORKED..
note that whenever i attempt to flash a ROM the result shows successful with no errors ..
so whats the problem in here?
i have a guess but i need help in order to apply it.. i think the VOL- is pressed and stuck somehow Electrically on the board ( but no physically as i can press the volume down and hear its tap or whatever you call it.. i even managed to boot into fast-boot and it worked.
is there anyway i can disable the vol- button temporary to see if its causing the problem?
the only thing is i cant see my ROM booting... not even the boot animation showing... just the boot-loader and automatically it goes into the recovery
also i have kernel log attached below followed by the recovery log
EDIT: i also forgot to mention that my PC recognize the phone and i have access to my internal storage.. no problems with transfer speed as well
after tons of attempts and searching online and flashing stuff and blablabla... (i flashed every recovery image op2 support )
FINALLY
I found the solution my self, and everything is back to normal...
the phone was stuck at the early stage of the booting process and maybe couldn't find the boot image in order to boot up the android OS, so all i did was i plugged in the phone into the PC, i started everything in fastboot mode on phone and on PC then i just sent the following command to my phone.
Code:
fastboot continue
fastboot then(meaning after the command) wasnt able to recognize the phone anymore so i knew that its now trying to search for partitions other than recovery.. i waited like 10 seconds and booom it booted into the best ROM i've ever used ( and actually missed ) which is Official RR from our great maintainer "nicesoni_ash"
P.S: the vol- as i said was really stuck and i noticed it not working while on RR ROM, so i just clicked it many times and tried mixing vol+ with vol- .. after many many attempts vol- worked and i then rebooted to make sure if everything is back to normal and no recovery auto boots and indeed it smoothly booted up :laugh:
thanks a lot for all who tried to help out in here or on oneplus forums :highfive:
#back_to_resurrect_and_will_always_remix
Did you try reverting to stock ?
Try getting files from here..
https://forum.xda-developers.com/oneplus-2/general/rom-mirrors-official-oxygen-os-roms-ota-t3209863
I would consider it as bricked, after all attempts failed and go with the unbrick guide here on xda or oneplus forums, maybe this way it can be ressurected.
You probably have already backed up your data..
Damn, that hurts..
mithu.creative said:
Did you try reverting to stock ?
Try getting files from here..
https://forum.xda-developers.com/oneplus-2/general/rom-mirrors-official-oxygen-os-roms-ota-t3209863
Click to expand...
Click to collapse
sorry for this late reply but yes i have tried flashing every ROM from stock to Custom ones even i flashed EVERY SINGLE RECOVERY IMAGE OUR PHONE SUPPORTS XD and non worked... first aid.. qualcomm toolkit... non...
hello bro, i updated a magisk module v4android and when i reboot, it boots up in twrp. and since then it keeps booting into twrp. So, i used fastboot continue and when it boot int the home i deleted that module.
but fastboot continue only works once. After that if i switch-off and switch-on the phone, it goes into twrp. it needs fastboot continue everytime.
please provide me a permanent solution. few other users are facing this too. plz reply i'm waiting.
Hey,
with the help of some others in a Discord server (thanks @thesanjayp#6251 on discord) i managed to find the issue. Appearantly there was a change in /dev/block/bootdevice/by-name/misc for some reason. There was a similar problem on the old LG Optimus G Pro which i owned, so i remembered this.
As I'm not sure if we can just wipe the partition or not, i got a working misc.img attached.
In any terminal (adb shell, twrp terminal or an terminal app in a rom) make sure you have su rights, and then execute the following command:
Code:
dd if=/path/to/misc.img of=/dev/block/bootdevice/by-name/misc
Make sure to adapt the path to the misc.img though to the location you saved it to.
The misc.img I used is attached to this post.
PS: Im not responsible for any broken phones if this didnt work for you.
Hi,
I couldn't figure out where to ask this query since I couldn't find anything regarding my phone. I own a Lava_R1s with StarOS V3.3 with Android Version 6.0. This is a phone available specifically in the U.A.E market since its made without camera and GPS so that it can be used in the oil field.
I tried to root the phone and now its soft bricked. I can enter fastboot mode and recovery mode (TWRP) but every time i try to switch on the phone it keeps going into a loop of the "Lava Powered by android" and switches off and then continues to keep doing that.
Here is what i did.
1. I used fastboot to unlock the OEM.
2. Then I flashed TWRP as recovery for the mobile.
3. After that i installed SuperSU zip file.
After all these steps my phone refuses to start up. It just comes to the LAVA powered by android screen and stays on that screen till i press the power button.
Further more I tried flashing the boot and system with Stock ROM files downloaded from needrom.com. That hasn't helped. In fact the looping of the initial screen started after flashing boot and system files (I used img files for Lava R1 Lite since those where the only ones i could find).
Would be really grateful if anyone could provide me a solution for this issue.
Another thing is that a lot of my colleagues have the same phone, so if there is anyway to extract the rom from their phone and install on mine without actually rooting their device it would also work for me i guess.
Renojjv
Renojjv said:
Hi,
I couldn't figure out where to ask this query since I couldn't find anything regarding my phone. I own a Lava_R1s with StarOS V3.3 with Android Version 6.0. This is a phone available specifically in the U.A.E market since its made without camera and GPS so that it can be used in the oil field.
I tried to root the phone and now its soft bricked. I can enter fastboot mode and recovery mode (TWRP) but every time i try to switch on the phone it keeps going into a loop of the "Lava Powered by android" and switches off and then continues to keep doing that.
Here is what i did.
1. I used fastboot to unlock the OEM.
2. Then I flashed TWRP as recovery for the mobile.
3. After that i installed SuperSU zip file.
After all these steps my phone refuses to start up. It just comes to the LAVA powered by android screen and stays on that screen till i press the power button.
Further more I tried flashing the boot and system with Stock ROM files downloaded from needrom.com. That hasn't helped. In fact the looping of the initial screen started after flashing boot and system files (I used img files for Lava R1 Lite since those where the only ones i could find).
Would be really grateful if anyone could provide me a solution for this issue.
Another thing is that a lot of my colleagues have the same phone, so if there is anyway to extract the rom from their phone and install on mine without actually rooting their device it would also work for me i guess.
Renojjv
Click to expand...
Click to collapse
Check my reply in this post
https://forum.xda-developers.com/android/help/softbricked-lava-r1s-please-help-t3730982
Hello everyone, just wanted to say a quick thanks, after successfully rooting and installing custom roms on two phones thanks to the information on these forums, third time turns out to be a charm and I managed to hard brick my new P10 lite.
The situation right now:
no charge light, no combination of buttons will do anything, phone is dead and will not boot or vibrate.
my computer will recognize that a phone is connected, for example Hisuite will pop up when i connect the phone, and in device manager, it shows Lemobile android device and the submenu says Android bootloader interface.
how i got here:
i was trying to install lineage 14.1 from this haky86
https://forum.xda-developers.com/p8...m-lineageos-14-1-huawei-p8-lite-2017-t3649292
but before i did that, i used this guide to install twrp and supersu:
https://forum.xda-developers.com/p10/how-to/twrp-how-to-root-p10-lite-t3617418
everything went fine, on the stock operating system i had root and system was running.
when i installed lineage, i lost root and couldnt figure out how to get it back. so i used this guide to restore the stock system and was going to try again from the beginning.
https://forum.xda-developers.com/p10-lite/help/original-service-rom-huawei-p10-lite-t3688097
however, when i tried to reinstall lineage for the second, third and fourth time, i kept getting stuck in a bootloop with the lineage animation. it seemed to me that i needed to flash the vendor image, and i found a guide on xda how to do it, but it wouldnt let me flash to the vendor partition. (sorry, i dont recall the exact error and i cant get there anymore :/)
so in massive frustration and desperation, i tried to use this method:
https://forum.xda-developers.com/p8...uide-unbrick-huawei-p8-lite-2017-pra-t3713574
which i know is for a p8 and i never should have tried to install it, but it went through the whole download process and at about 50-60% on the recovery the phone went black and never turned on again.
i have read that perhaps disconnecting the battery for a few minutes might help? or is this something that dc unlocker can help with?
any advice would be greatly appreciated. if more information is needed, please let me know.
Hi,
Have you tried completely turning off your phone (pressing on/off button for roughly 20 seconds) and then booting into recovery (pressing Volume Up and Power key simultaneously for rouhgly 10 seconds)?
Best,
Kenny
Thanks for the reply, but as I said, no button combinations elicit any response. The only sign that the phone is not completely dead is that it will be recognized by my computer as an android phone, but adb (for example) says no device is connected.
lineage gives you bootloop due to wrong data partition format
bricked my p10 lite several times same ending
only way that always gets the phone back to life is flashing lineage, i took haazan's one
BUT BEFORE flashing the lineage 14.1 zip check partition format is ext4
when back on lineage and stock ROM is wanted boot into twrp and re change format to f2ts or how it is named and flash the stock zip
unbricked
edit:
saw your second post too late
if the phone does not response on any button(s) maybe adb sideload command for change partition format and then sideloading the lineage zip is a way?
I have a similar problem, I have a custom rom (Elemental) but I flash another custom rom, it was normal, in the reboot it not turn on, only is in fastboot mode, i flash original system, cust, boot, and another but it is the same, help me please
Note: Posting it here even though ROMs, Kernels, Recoveries, & Other Development would be more appropriate category but this site isn't allowing me to post there 'coz I'm a new user.
Here's a situation: I've got Meizu 5 pro flashed with Flyme 6 which I flashed using TWRP recovery. I made few tweaks of the partitions (deleting and recreating and renaming) and then I wiped data.
Now the phone boots but as soon as it hits main interface I get error saying "internal storage is running out the process has been stopped" then it reboots and starts over, hits the message, reboots, starts over .... stays in this loop.
I still have access to:
- Meizu's recovery mode (which is kinda useless if I can't access root directory)
- locked fastboot mode (also little bit useless if it's locked)
- recovery partition through USB
I also have MRT dongle for repairing Chinese phones but it doesn't seem to work unless the phone boots fully into Android.
What I can do about this ? Any help much appreciated.
hm.. is it Exynos or Mediatek?
aIecxs said:
hm.. is it Exynos or Mediatek?
Click to expand...
Click to collapse
My guess is Exynos as all people here who have dealt with Meizu 5 pro say so.
Allegedly, on this Meizu you can press and hold Vol up and down and press power button once and the
phone's chipset will appear on the screen but my phone doesn't show anything.
[TUTORIAL] Restore hard bricked + lost recovery with locked bootloader Meizu Pro 5
aIecxs said:
[TUTORIAL] Restore hard bricked + lost recovery with locked bootloader Meizu Pro 5
Click to expand...
Click to collapse
Funny. I was just reading the thread when you sent me the link. Looks like my phone's last chance for resurrection, doesn't it ?
besides official meizu flash tool (if exist)