Related
Ok just noticed this can't tell if it's an m preview 2 problem or just my device. When I go into stock recovery and hit apply update from sd card I get
Supported API: 3
E: unknown volume for path [/sdcard]
-- Couldn't mount /sdcard.
Installation aborted.
it fails to mount /sdcard(check picture). Tried with TWRP and have full access to /sdcard. Tried reflashing this stock one keeps happening. Phone still works perfect tried fixing permissions any ideas?
Did you ever find a solution to this?
I got my Nexus 5X stuck in a boot loop when I try troubleshooting it, I get the same error you got (also using TWRP).
Reflashing with the stock ROM didn't help either.
Try flashing userdata.img from the stock image. Right after flashing the img file, use the buttons to boot into stock recovery, and perform a factory wipe.
audit13 said:
Try flashing userdata.img from the stock image. Right after flashing the img file, use the buttons to boot into stock recovery, and perform a factory wipe.
Click to expand...
Click to collapse
Thanks for the reply. I gave it another shot and I found that the basic procedure of flash the proper files was enough. What was missing was the vendor.img, which most of the guides forget to mention or associate with Nexus 9, for example.
Glad you got it sorted out:good:
Hey,
I have used Sony Developer's documentations in order to unlock my bootloader, then upgraded it with Emma.
Also, I have installed TWRP using fastboot and also tried to install LineageOS.
But, every time I try to turn on the device, it is stuck on Sony's logo and gets warmer with time.
TWRP, fastboot mode and flash mode are accessible.
What can I do?
Thanks!
(D6603)
iTayGNR said:
Hey,
I have used Sony Developer's documentations in order to unlock my bootloader, then upgraded it with Emma.
Also, I have installed TWRP using fastboot and also tried to install LineageOS.
But, every time I try to turn on the device, it is stuck on Sony's logo and gets warmer with time.
TWRP, fastboot mode and flash mode are accessible.
What can I do?
Thanks!
(D6603)
Click to expand...
Click to collapse
How did you tried to install LineageOS? If you want to go back to stock rom use Emma to flash stock.291
Remember that after flashing TWRP you need to enter recovery by pressing power+volume up and then wipe system/data/cache partitions before flashing LineageOS zip
xkeita said:
How did you tried to install LineageOS? If you want to go back to stock rom use Emma to flash stock.291
Remember that after flashing TWRP you need to enter recovery by pressing power+volume up and then wipe system/data/cache partitions before flashing LineageOS zip
Click to expand...
Click to collapse
I have just flashed the stock rom with Emma.
What do you now? What to install in what order?
what I did previously was to use fastboot to flash TWRP and then flash lineageOS through the device itself (using TWRP). But it says the file is corrupted, although i tried 2 different zip files (both for the z3 of course) but both are corrupted.
thanks!
iTayGNR said:
I have just flashed the stock rom with Emma.
What do you now? What to install in what order?
what I did previously was to use fastboot to flash TWRP and then flash lineageOS through the device itself (using TWRP). But it says the file is corrupted, although i tried 2 different zip files (both for the z3 of course) but both are corrupted.
thanks!
Click to expand...
Click to collapse
Nice! Now you can follow Instructions from the How to install section in https://forum.xda-developers.com/z3/orig-development/7-1-cyanogenmod-t3508140 you can skip point 1 and start from 2.
Be sure that your bootloader is still in unlocked status before, otherwise you can unlock it again with flashtool. Otherwise rom won't boot. That's all, good luck
xkeita said:
Nice! Now you can follow Instructions from the How to install section in https://forum.xda-developers.com/z3/orig-development/7-1-cyanogenmod-t3508140 you can skip point 1 and start from 2.
Be sure that your bootloader is still in unlocked status before, otherwise you can unlock it again with flashtool. Otherwise rom won't boot. That's all, good luck
Click to expand...
Click to collapse
Should I use fastboot in order to flash TWRP?
and, why do I need flashtool? do you have a tutorial?
thank you so much!
This is the TWRP log when trying to install LineageOS:
Installing zip file '/external_sd/lineage-14.1-20170523-xkeita-z3.zip'
Check for MD5 file...
Skipping MD5 check: no MD5 file found
Zip file is corrupt!
Error installing zip file /external_sd/lineage-14.1-20170523-xkeita-z3.zip'
Updating partition details...
...done
(bold = red letters_
What have I done wrong?
iTayGNR said:
This is the TWRP log when trying to install LineageOS:
Installing zip file '/external_sd/lineage-14.1-20170523-xkeita-z3.zip'
Check for MD5 file...
Skipping MD5 check: no MD5 file found
Zip file is corrupt!
Error installing zip file /external_sd/lineage-14.1-20170523-xkeita-z3.zip'
Updating partition details...
...done
(bold = red letters_
What have I done wrong?
Click to expand...
Click to collapse
It is probably the zip file itself which is (like TWRP states) corrupted.
Try to redownload the zip from the LOS thread and flash it, guess something went wrong with your first download and/or transfer of the zip to your SD.
Hello, I would like some help since I got this device just yesterday.
I got it with the EMUI 4 Android 6.0 stock installed on it. Since there was no update for it I unlocked the bootloader installed twrp rooted and manually flashed EMUI 5 7.0. Everything worked fine.
I created a backup through TWRP and restored it succefully multiple times.
Then I installed the Meticulus TWRP (since I was told it is a prerequisite for the AOSP). I Flashed the AOSP but it stuck during the boot animation (30 minutes afterwards I powered it off).
I reflashed my old TWRP and tried restoring my backup. IT fails with the explanation "Cannot wipe /vendor" while at the top it says "Cannot mount /vendor (invalid argument)" "Cannot mount /product (invalud argument)".
Anyone has a clue how to fix this? Fastboot adb all works so there should be a way to boot into an OS properly?
Since AOSP was not booting i guess you forgot formatting /data partition to ext4... And did u Used Stock vendor and not openkirin ones ?
Gesendet von meinem Honor 6X mit Tapatalk
As said I have replaced the custom TWRP with the default one so I think this should not apply anymore?
The "cannot mount vendor/product" messages came from the default TWRP after I reflashed it again.
At the top it says "cannot mount /vendor" either so I guess that is the actual problem?
It would be nice to get teh AOSP up but I really want to be able to boot into something first honestly.
And did u Used Stock vendor and not openkirin ones
Click to expand...
Click to collapse
Can you please explain? When I flashed your ROM i was on your TWRP. Does this even matter anymore?
At best I would be able to restore my backup.
To me it appears to be caused by the vendor partition.
Is there any way I can manually create that through TWRP?
algg said:
To me it appears to be caused by the vendor partition.
Is there any way I can manually create that through TWRP?
Click to expand...
Click to collapse
Yes you can but not creating it through twrp, but flashing it by fastboot mode: this is because
image (.img) files needs to be flashed by fastboot mode to avoid any kind of problem.
So, you should look for the last version of stock firmware on which you was before going custom, like BLN-L21CXXXB368 for example; tell me your build number and I'll find the package for you. Then, extract from the UPDATE.APP (a very big file that contains every partition in your phone like recovery, vendor, data, ecc. - you'll find this file inside the zip archive that contains the downloaded update) the vendor.img using Huawei Update Extractor, and then flash it through fastboot mode using the command "fastboot flash vendor vendor.img".
Otherwise, you could rely on dload method to reflash a full update package, and this should really fix everything since that it'll be like a new and clean installation of the OS. Then, unlocking the bootloader again and reflash TWRP to finally restore your previous backup made when it was working would be the final step.
Feel free to ask for further help
Thanks for the reply first really appreciate it.
I got the device on EMUI 4 Marshmallow rooted it and unlocked the bootloader then installed the BLN-L21C185B140 which worked smoothly.
I used that update.zip and extracted into dload root folder and started the huawei recovery installer but it said "package not found".
I tried flashing something to vendor before with fastboot but it said command not allowed.
Maybe I am doing something wrong?
algg said:
Thanks for the reply first really appreciate it.
I got the device on EMUI 4 Marshmallow rooted it and unlocked the bootloader then installed the BLN-L21C185B140 which worked smoothly.
I used that update.zip and extracted into dload root folder and started the huawei recovery installer but it said "package not found".
I tried flashing something to vendor before with fastboot but it said command not allowed.
Maybe I am doing something wrong?
Click to expand...
Click to collapse
Latest build on Nougat after the update was BLN-L22C185B140 so? If yes, the package that you need to download is that one. Unluckily i can't help about dload method, i never had fortune using dload because package verification always failed at 5%, i tried every combination but without success.
Command not allowed while flashing vendor image... but flashing others, like recovery or boot.img is allowed? If yes, i don't know what's causing this sorry... I'm sure that my friend @shashank1320 could surely help more than me about how using dload method correctly. Check his signature, it should contain a guide on how to use it
RedSkull23 said:
Latest build on Nougat after the update was BLN-L22C185B140 so? If yes, the package that you need to download is that one. Unluckily i can't help about dload method, i never had fortune using dload, i never be able to using it successfully because package verification always failed at 5%.
Command not allowed while flashing vendor image... but flashing others, like recovery or boot.img is allowed? If yes, i don't know what's causing this sorry... I'm sure that my friend @shashank1320 could surely help more than me about how using dload method correctly. Check his signature, it should contain a guide on how to use it
Click to expand...
Click to collapse
For fastboot yes flashing recovery or boot do work but vendor does not. Maybe the ISO is corrupted somehow I will try it again on a different machine now with the tool.
The link you posted the dload method from is the one where I initially found it as well so yea.
Also it shouldn't matter what I install since the only thing I need is the actual vendor (and product?) partition to work. I have a functional backup just TWRP cannot create/mount the partitions. So even a way to just create them without any data would actually fix my problem (at least I hope so?)
When trying to use Fastboot to flash the vendor/product img I get remote: Command not allowed (yes my bootloader is unlocked) although I can flash the recovery without any problem.
The dload method does not work as said. I placed the extracted content of the update.zip into the dload folder but the software "cannot find" the package.
algg said:
When trying to use Fastboot to flash the vendor/product img I get remote: Command not allowed (yes my bootloader is unlocked) although I can flash the recovery without any problem.
The dload method does not work as said. I placed the extracted content of the update.zip into the dload folder but the software "cannot find" the package.
Click to expand...
Click to collapse
@RedSkull23, thanks for the tag mate.
@algg, No need to flash the vendor image as you already had the stock vendor img.
Now what else you can try is to flash the stock recovery, boot to stock recovery, select factory reset and reboot. It should most probably fix the issue.
If not, reflash the TWRP, a regular TWRO available and not specific to elite or meticulous, but generic one given by OldDroid.
I hope you have downloaded the content for dload, if not, download these for B140.
Flash this via TWRP- http://update.hicloud.com:8180/TDS/...afnaf/update_data_full_BLN-L21_hw_meafnaf.zip
no further changes and Then use dload method for this file- http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1756/g1755/v105054/f1/full/update.zip
Try above and provide feedback. This is what I could think of best possible way to have everything with all system app working.
If not, let me know and I will try to help further.
Hi, I thought I need the vendor image since TWRP (all versions) tell me "Could not mount/wipe vendor" and "Could not mount/wipe product" "invalid argument" for both.
I tried the factory reset before but it does not work. It stops at 23% then shows a red exclamation mark and just goes to the original screen with the 3 buttons (restart, shutdown and wipe).
I am currently trying to get it to recognize my sd card. But somehow it does not work through TWRP it just does not recognize the 8GB SD Card. Also I am currently on the TWRP I was before all of this happened (3.1 openkirin). Without the SD Card recognized I can't put the dload files for it on it and in turn I can't use the dload.
I mean technically it should very well be possible to fix the device since it isn't a real brick and even TWRP and Fastboot load. It's just that all those little things are somehow ruining it.
Edit: I will get a new micro sd for some reason this one does nt work. I'll say then whether the flash then dload worked.
@shashank1320
Mind explaining why I should first use TWRP to flash something and then on top of it use dload?
And why those specific files?
algg said:
Edit: I will get a new micro sd for some reason this one does nt work. I'll say then whether the flash then dload worked.
@shashank1320
Mind explaining why I should first use TWRP to flash something and then on top of it use dload?
And why those specific files?
Click to expand...
Click to collapse
Sure, let me explain.
The first file is the data file which will install few systems apps like file manager, updater, themes, clock, fm radio etc. This will work via dload as well but the installation time is around 3-7 seconds so, over the course of time and flashing few times, i realised that these PV files cannbe flashed via TWRP and it works perfectly fine specific to PV files( twrp won't supoort other stock zips). We foash this first so that it updates your buld number and also does not replace the recovery with stock (as if you flash the main update zip first, it will replace with stock recovery so flashing the 2nd file will be quick but with unstable system apps, sometime).
Now we flash the main zip file with update.app via dload and it Install the main firmware for boot, vendor, recovery, system, usrdata etc.
Hope this explanation helps, if not let me know and I will rephrase myself.
It does help. I did all of this and now in the dload app I get "Software install failed Incompatibilty with current version please download the correct update package".
When I flashed the zip you linked me with TWRP it said "cannot mount /data /vendor /product". Appearently data cannot be mounted since it is encrypted.
Any clue as to what I am doing wrong? Or is this device now a real brick with functioning recovery but without OS?
Is there any way I can "debug" what is going on while the boot animation is playing?
What is confusing me is that the boot animation plays just normal but it simply does not continue to the actual OS.
algg said:
It does help. I did all of this and now in the dload app I get "Software install failed Incompatibilty with current version please download the correct update package".
When I flashed the zip you linked me with TWRP it said "cannot mount /data /vendor /product". Appearently data cannot be mounted since it is encrypted.
Any clue as to what I am doing wrong? Or is this device now a real brick with functioning recovery but without OS?
Click to expand...
Click to collapse
Not bricked..its just Data is not mounted or encryption. Should never encrypted it. NVM.
Do one thing, boot to twrp recovery. Try flashing and get error, then go to main TWRP page and click on reboot, select recovery out of 4 options( power off, system, bootloader and recovery). It will boot to recovery, now try flashing it again and see. Most if the time it helps.
Else, go to main page, select wipe, click on format rather than wipe here, it will prompt for typing Yes to confirm. Biit to recovery from main twrp page ( as mentioned above). And try this same thing of formatting data couple of times and then flash the zip and then dload.
I know these are tedious steps but inhave revived my device many a times with all these tricks after some efforts.
Good luck
YAY it works.
Just to recap what I did:
I flashed your thing first through TWRP tried to flash your other link with dload (which did NOT work)
Then I flashed the thing (emui5 Android 7 for Europe) through TWRP played in my old backup of exactly this through TWRP cleared dalvik & cache.
Then I waited 20 minutse and now it started.
Really thanks to all of you very nice people here. I would be very baffled if it wasnt able to repair the device since Fastboot and Recovery still work.
But Huaweis recovery is beyond terrible.
algg said:
YAY it works.
Just to recap what I did:
I flashed your thing first through TWRP tried to flash your other link with dload (which did NOT work)
Then I flashed the thing (emui5 Android 7 for Europe) through TWRP played in my old backup of exactly this through TWRP cleared dalvik & cache.
Then I waited 20 minutse and now it started.
Really thanks to all of you very nice people here. I would be very baffled if it wasnt able to repair the device since Fastboot and Recovery still work.
But Huaweis recovery is beyond terrible.
Click to expand...
Click to collapse
It is terrible indeed. Glad your phone working.
Thanks to @RedSkull23 for tagging, else I may have not responded as he was already involved and was helping as usual.:good:
algg said:
Really thanks to all of you very nice people here. I would be very baffled if it wasnt able to repair the device since Fastboot and Recovery still work.
But Huaweis recovery is beyond terrible.
Click to expand...
Click to collapse
I'm happy for you man, indeed it would be so bad, especially because you got this device 3 or 4 days ago if i didn't read bad, anyway what matters is that now it works. Are you able to restore the previous backup through TWRP now? (But before trying... Make a backup of your actual OS )
shashank1320 said:
It is terrible indeed. Glad your phone working.
Thanks to @RedSkull23 for tagging, else I may have not responded as he was already involved and was helping as usual.:good:
Click to expand...
Click to collapse
Are you joking man? I just tagged you for more help, but practically you helped him in everything, not me; I'm sure that you would noticed the thread and helped as always even without my tag, i just speeded up things for being helpful to algg.
algg, I'd like to apologize myself; i didn't vanished after tagging shashank, today i just was at work and obviously i was busy for help, but as i saw with pleasure he already helped you to restore your OS and that was the objective. Nice one, guys!
hello iv been trying to flash emui 5.0 firmware but i always get the same error when i flash the system.img it says FAILED (remote: sparse flash write failure)
and when i tried to flash the cust.img i get FAILED (remote: partition error). so like you figured i damaged the partition
i tried to wipe cache, format data but still doesn't work to flash the system.img and the cust.img but the boot and recovery images are fine to flash.
i also tried the dload method with no luck. so it started of when i updated to nougat 7.0 emui 5.0 from emui 4.1 marsmallow 6.0.1 it didn't update properly and i got some other version
with only google voice input, and crashed. so i decided to flash it manually instead in fastboot but before i flashed i went in to twrp and wiped everything and formated the data.
then i flashed the boot,recovery,cust,system images from the update.app to emui 5.0 for my device but then i damage my partition and got stuck on a boot loop. after that i went
in twrp and wiped everything again flashed the images again but then system and cust img failed errors above. would appreciate any assistance thank you.
are you able to flash any custom ROM?
Try booting to TWRP from TWRP and see if it makes any different instead directly wiping and booting.
shashank1320 said:
are you able to flash any custom ROM?
Try booting to TWRP from TWRP and see if it makes any different instead directly wiping and booting.
Click to expand...
Click to collapse
well i tried to boot from Twrp to Twrp with no result
and i cant seem to flash anything in twrp because i always get (failed to mount)
i tried to flash emui 5.0 nougat firmware for my Frd-L09 but then i got a boot loop, so i went in twrp and wiped everything,
and went in to bootloader and flashed another twrp 3.0.2 wich didn't work it just stuck on your device is booting now...
Android6969xd said:
well i tried to boot from Twrp to Twrp with no result
and i cant seem to flash anything in twrp because i always get Failed to mount '/cust ' (invalid argument)
Failed to mount ' /vendor (invalid argument)
Failed to mount '/product (invalid argument)
i tried to flash emui 5.0 nougat firmware for my Frd-L09 but then i got a boot loop, so i went in twrp and wiped everything,
and went in to bootloader and flashed another twrp 3.0.2 wich didn't work it just stuck on your device is booting now...
Click to expand...
Click to collapse
..
Solution for that
Brother Use Dc phoneix tool... It can flash the firmware into the device in any condition whether its bricked or both frp and bootloader locked.. And its a awsome tool to repair the phone.... Yesterday i have tried it on my phone too.... Flawlessly it worked... But its a paid tool... I bought 3 days licence to repair my phone... Yesterday only i bought the license and still 2 days left... If you wang you can ping me...
My WhatsApp no: +91 7587136151
prasanth.nitrr said:
Brother Use Dc phoneix tool... It can flash the firmware into the device in any condition whether its bricked or both frp and bootloader locked.. And its a awsome tool to repair the phone.... Yesterday i have tried it on my phone too.... Flawlessly it worked... But its a paid tool... I bought 3 days licence to repair my phone... Yesterday only i bought the license and still 2 days left... If you wang you can ping me...
My WhatsApp no: +91 7587136151
Click to expand...
Click to collapse
where do i buy it?
You can buy it from this link
(as iam a blocked member iam not able to post links in this thread... Just go to DC unlocker dot com and you can find the buy option)
DC-Phoneix +HCU timed licence is preferred for repairing of a bricked phone..
And detailed procedure has been given for every problem
prasanth.nitrr said:
You can buy it from this link
(as iam a blocked member iam not able to post links in this thread... Just go to DC unlocker dot com and you can find the buy option)
DC-Phoneix +HCU timed licence is preferred for repairing of a bricked phone..
And detailed procedure has been given for every problem
Click to expand...
Click to collapse
oh it was 19 euro dont have any money on my card, but if u could share your login to save my phone i would be very greatfull
Lol
No problem i will give you the logins...
Ping me on telegram
My username is : @acpdhruva
Dont panic its just a username lol..
prasanth.nitrr said:
No problem i will give you the logins...
Ping me on telegram
My username is : @acpdhruva
Dont panic its just a username lol..
Click to expand...
Click to collapse
do you have kik or a messenger you dont need to add phone number?
having a hard time to sign up without phone number hahah
Android6969xd said:
well i tried to boot from Twrp to Twrp with no result
and i cant seem to flash anything in twrp because i always get (failed to mount)
i tried to flash emui 5.0 nougat firmware for my Frd-L09 but then i got a boot loop, so i went in twrp and wiped everything,
and went in to bootloader and flashed another twrp 3.0.2 wich didn't work it just stuck on your device is booting now...
Click to expand...
Click to collapse
You need to flash the TWRP 3.1 for EMUI 5.0. Once you flash the correct file you can boot.
Do one thing, remove USB and just press power key, it will boot to system.
Sorry my bad english.
If you connect the phone to PC, you can browse the internal or external storage?
If you do, or you have an sdcard, use it to dload mode to flash firmware. Use rollback package to revert back to an old firmware. And don't use twrp to flashing firmwares. Its wont work perfectly with nougat firmwares. Dont use it.
From twrp did not work for me. This method send my phone to bootloop and later just booting to erecovery, or stay a permanent bootloop. TWRP gone and just the dload method works 100 percentage.
Mumtaz77 said:
Sorry my bad english.
If you connect the phone to PC, you can browse the internal or external storage?
If you do, or you have an sdcard, use it to dload mode to flash firmware. Use rollback package to revert back to an old firmware. And don't use twrp to flashing firmwares. Its wont work perfectly with nougat firmwares. Dont use it.
From twrp did not work for me. This method send my phone to bootloop and later just booting to erecovery, or stay a permanent bootloop. TWRP gone and just the dload method works 100 percentage.
Click to expand...
Click to collapse
yes i have access to internal storage and i tried the dload method with my sdcard maybe it only work with micro sd?
shashank1320 said:
You need to flash the TWRP 3.1 for EMUI 5.0. Once you flash the correct file you can boot.
Do one thing, remove USB and just press power key, it will boot to system.
Click to expand...
Click to collapse
i flashed the correct twrp 3.1 but i still get Failed to mount '/cust ' (invalid argument)
Failed to mount ' /vendor (invalid argument)
Failed to mount '/product (invalid argument)
Android6969xd said:
i flashed the correct twrp 3.1 but i still get Failed to mount '/cust ' (invalid argument)
Failed to mount ' /vendor (invalid argument)
Failed to mount '/product (invalid argument)
Click to expand...
Click to collapse
Did you make any changes or flasshed custom ROM?
shashank1320 said:
Did you make any changes or flasshed custom ROM?
Click to expand...
Click to collapse
i tried to flash Lineage 14.1 but that lead to black screen when the device booted
and i tried changing the file system to ext2 back to ext4
Android6969xd said:
i tried to flash Lineage 14.1 but that lead to black screen when the device booted
and i tried changing the file system to ext2 back to ext4
Click to expand...
Click to collapse
Tried dload to restore the phone?
or can go to TWRP and then wipe section, select partition and repair it. and then try the things you want to do
shashank1320 said:
Tried dload to restore the phone?
or can go to TWRP and then wipe section, select partition and repair it. and then try the things you want to do
Click to expand...
Click to collapse
hi i tried the dload method and it worked had to buy a micro sd but it was worth it
i cant believe it myself nvm it failed at 99% thought it was a success
lol tried it a few more times and it worked actually
this was the firmware i used http://androidhost.ru/vb with the dload method
Android6969xd said:
hi i tried the dload method and it worked had to buy a micro sd but it was worth it
i cant believe it myself nvm it failed at 99% thought it was a success
lol tried it a few more times and it worked actually
this was the firmware i used http://androidhost.ru/vb with the dload method
Click to expand...
Click to collapse
best part is your efforts paid and you restored your phone.
PLEASE HELP ME
My phone wont boot (bootloop), I can get into fastboot and recovery (usually eRecovery, only when i flash TWRP and immediately afterwards boot into recovery it goes to TWRP). When I try to restore a backup i made, it Fails (because it cant mount /data).
When i try to change filesystem oder repair filesystem it can't do it either...
Thanks in advance guys,
~Paul
pt_2001 said:
PLEASE HELP ME
My phone wont boot (bootloop), I can get into fastboot and recovery (usually eRecovery, only when i flash TWRP and immediately afterwards boot into recovery it goes to TWRP). When I try to restore a backup i made, it Fails (because it cant mount /data).
When i try to change filesystem oder repair filesystem it can't do it either...
Thanks in advance guys,
~Paul
Click to expand...
Click to collapse
Flash elite twrp 3.1.1 as erecovery then wipe all partition
Download stock firmware extract update.app from zip and place it in dload folder place folder on sdcard flash stock recovery through twrp then use dload method
siddhrsh said:
Flash elite twrp 3.1.1 as erecovery then wipe all partition
Download stock firmware extract update.app from zip and place it in dload folder place folder on sdcard flash stock recovery through twrp then use dload method
Click to expand...
Click to collapse
When i flash elite twrp 3.1.1, it won't boot into recovery unfortunately...
And where can I download stock firmware?
pt_2001 said:
When i flash elite twrp 3.1.1, it won't boot into recovery unfortunately...
And where can I download stock firmware?
Click to expand...
Click to collapse
via firmware finder website. check the dload method in my signature and you will get the site as well.
for your issue, try formatting the data and changing the partition type to ext4 and boot.
shashank1320 said:
via firmware finder website. check the dload method in my signature and you will get the site as well.
for your issue, try formatting the data and changing the partition type to ext4 and boot.
Click to expand...
Click to collapse
When I format data, i think it works, but theres an error (Failed to mount '/system_image' (Device or resource busy))
pt_2001 said:
When I format data, i think it works, but theres an error (Failed to mount '/system_image' (Device or resource busy))
Click to expand...
Click to collapse
what is data partition type?
shashank1320 said:
what is data partition type?
Click to expand...
Click to collapse
its ext4 now, but i still can't boot elite twrp
pt_2001 said:
its ext4 now, but i still can't boot elite twrp
Click to expand...
Click to collapse
Boot to TWRP, format data partition, boot to partition again immediately and then try whatever you are trying.
usually booting to TWRP through TWRP does help.
shashank1320 said:
Boot to TWRP, format data partition, boot to partition again immediately and then try whatever you are trying.
usually booting to TWRP through TWRP does help.
Click to expand...
Click to collapse
ok thanks, my initial problem is solved now. but i can't boot normally, I always get stuck in a bootloop...
pt_2001 said:
ok thanks, my initial problem is solved now. but i can't boot normally, I always get stuck in a bootloop...
Click to expand...
Click to collapse
want to go back to stock or want to continue with Elite ROM?
shashank1320 said:
want to go back to stock or want to continue with Elite ROM?
Click to expand...
Click to collapse
I want to go back to stock
pt_2001 said:
I want to go back to stock
Click to expand...
Click to collapse
Flash the oeminfo file for your model.
use dload method. Done
shashank1320 said:
Flash the oeminfo file for your model.
use dload method. Done
Click to expand...
Click to collapse
ok i downloaded the BLN-L21C432-oeminfo.zip file, but how do i flash it?
pt_2001 said:
ok i downloaded the BLN-L21C432-oeminfo.zip file, but how do i flash it?
Click to expand...
Click to collapse
Via twrp or via multi tool if you are able to access OS.
shashank1320 said:
Via twrp or via multi tool if you are able to access OS.
Click to expand...
Click to collapse
i can only access twrp, if i try to flash it in twrp it says 'Invalid zip file format!'
pt_2001 said:
i can only access twrp, if i try to flash it in twrp it says 'Invalid zip file format!'
Click to expand...
Click to collapse
Let me check the file for you.
shashank1320 said:
Let me check the file for you.
Click to expand...
Click to collapse
Thanks, do I have to flash the file I downloaded, or do i have to extract it first?
When I extract it, it is a unix executable file, so do I have to add .zip to the name then?