Related
I can boot with volume up and get to the recovery screen. I am combing threads and doing all I can now. Any help is greatly appreciated. Downloading the SDK on slow work internet now and attempting to get all files I think I might need as we speak.
give members more details [what did u flash etc], so they can help u.
No, if you have recovery mode available nothing is lost.
Just download a ROM you like, and try flashing it. If it doesn't work, try formatting and then flashing again.
I flashed one click stock and I saw that SYSTEM failed while it was running. Now I get no boot but I can get to the stock recovery.
How do I get a rom onto the phone in its current state?
when I boot with the vol up / power combination I get a small menu for reboot bootloader, reboot, recovery or power off. If I select recovery I get the triangle icon with the ! and then after a minute or so I can get to what looks like a very small clockwork menu with: reboot system now, apply update from /sdcard, wipe data/factory reset or wipe cache partition. I have tried to apply a rom I had on in the list but it failed verification and the list is only partital it does not let me go all the way down.
In recovery you can still use adb to transfer files to the device.
Code:
adb push update.zip /sdcard
I am having trouble getting adb to work. I am following these instructions but something seems to be wonky?
http://androidadvices.com/how-to-install-set-up-and-use-adb-for-android-devices/#.UAWbt7Sm_Nk
can you point me in a better direction to get adb access
I just noticed at the bottom of my screen in slightly greyed out copy it reads: FASTBOOT STATUS - FAILINVALID COMMAND
magicwands said:
I flashed one click stock and I saw that SYSTEM failed while it was running. Now I get no boot but I can get to the stock recovery.
How do I get a rom onto the phone in its current state?
when I boot with the vol up / power combination I get a small menu for reboot bootloader, reboot, recovery or power off. If I select recovery I get the triangle icon with the ! and then after a minute or so I can get to what looks like a very small clockwork menu with: reboot system now, apply update from /sdcard, wipe data/factory reset or wipe cache partition. I have tried to apply a rom I had on in the list but it failed verification and the list is only partital it does not let me go all the way down.
Click to expand...
Click to collapse
That small menu as you called it is fastboot.
That recovery is stock recovery.
Connect to phone to computer and use fastboot to flash a custom recovery. Boot into said recovery. Mount usb storage. Transfer rom over to phone. factory reset/format system and flash new rom.
If you don't know how set up and use fastboot. Look it up.
I got the bootloader unlocked and TWRP installed but whenever I try to flash a rom I get the error message " E:error in /tmp/sideload/package.zip (status 7)
Any thoughts?
magicwands said:
I got the bootloader unlocked and TWRP installed but whenever I try to flash a rom I get the error message " E:error in /tmp/sideload/package.zip (status 7)
Any thoughts?
Click to expand...
Click to collapse
Do a full wipe, re-download the rom ( make sure its the correct rom for your device) and try again.
If it still fails. Flash the official stock images and make sure that at least works
I am fully wiped but I am going through the process again just to be sure, all I have on the device right now is TWRP its unlocked and boots into TWRP recovery fine. But everytime I flash, I have tried 3 roms and one was the NS4G_IMM76d_deodexed it hits me with the same error as before: e:error in /tmp/sideload/package.zip (status 7)
I am searching frantically for a fix, any help is appreciated.
magicwands said:
I am fully wiped but I am going through the process again just to be sure, all I have on the device right now is TWRP its unlocked and boots into TWRP recovery fine. But everytime I flash, I have tried 3 roms and one was the NS4G_IMM76d_deodexed it hits me with the same error as before: e:error in /tmp/sideload/package.zip (status 7)
I am searching frantically for a fix, any help is appreciated.
Click to expand...
Click to collapse
Download the following files:
7-Zip from http://www.7-zip.org
https://dl.google.com/dl/android/aosp/sojus-imm76d-factory-10660f4c.tgz
http://android.kcomputerzone.com/stock/sojus-imm76d-factory_windows-scripts.zip
http://android.kcomputerzone.com/extras/crespo-drivers.zip (just in case you need them)
Install 7-Zip
Extract sojus-imm76d from sojus-imm76d-factory-10660f4c.tgz (You will need to go in multiple levels deep to get to folder) to your desktop.
Extract contents of sojus-imm76d-factory_windows-scripts.zip to the sojus-imm76d on your the desktop.
With phone in bootloader mode run flash-all.cmd in the sojus-imm76d folder.
If all worked it should be boot and be working.
That should restore yours to default firmware all using fastboot. Hope this helps.
This site (http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/) got me up and running with TWRP then I been having issues flashing roms, I am able to get a Peter Alfonso stock rom to boot but then if I try to flash I get the same error. I was able to ODIN the stock 4.0.4 but nothing seems willing to flash via clockwork or TWRP.
Ok just to bring some closure to this, thanks for all the help. My problem with the status 7 error was that I was using the wrong clockwork recovery. It was bundled in a one click root for Nexus Galaxy and Nexus S, the Root worked great but the recovery was the incorrect version. In any event I am now 100% functional. Thanks to all that helped out.
magicwands said:
Ok just to bring some closure to this, thanks for all the help. My problem with the status 7 error was that I was using the wrong clockwork recovery. It was bundled in a one click root for Nexus Galaxy and Nexus S, the Root worked great but the recovery was the incorrect version. In any event I am now 100% functional. Thanks to all that helped out.
Click to expand...
Click to collapse
That is the problem with One click root/unroot. I know the simplicity is awesome but the end user is learning nothing. Doing it the ol' fashion way teaches the user how to use SDK, ADB, and other important simple things. I always say use the guide and do it yourself. Problems happen and instead of having to start a new thread you can trouble shoot it yourself. :good:
Hey everyone,
Yesterday i tried flashing the latest CM12 nightly straight onto my Moto G over stock KitKat. After i flashed the ROM, i tried booting and noticed it was taking a lot longer than normal to boot. Ten minutes had gone past so i tried rebooting it again and the same thing happened, just got stuck booting for ages.
So i decided to boot into recovery and do a factory reset to see if this would make any difference. But even after doing this the phone still wouldn't boot, so i decided to just flash the stock KitKat ROM back onto the phone and forget about all the Lollipop stuff.
The KitKat ROM wasn't on my phones storage so i downloaded it from the internet and flashed it via fastboot using and included Windows batch file. I've used this method numerous times to get me out of situations like this and it's always worked, but this time no!
Tried booting after flashing the new stock ROM and now it just keeps going to the 'Warning, bootloader unlocked' screen and then booting back in a loop.
When i boot into ClockworkMod recovery it gives me these errors:
Can't mount /cache/recovery/log
Can't open /cache/recovery/log
Can't mount /cache/recovery/last_log
Can't open /cache/recovery/last_log
Can't mount /cache/recovery/last_install
Can't open /cache/recovery/last_install
And if i attempt to format /data, it says this:
Error mounting /data
Error formatting /data
I hate asking for help like this but unfortunately i don't have much option this time, no idea what to do despite searching forums for many hours.
Please help, any advice would be greatly appreciated!
Bump
You can try getting into fastboot and run commands fastboot erase userdata and fastboot erase cache from your computer to pretty much factory reset the phone.
Sent from my Moto X 2014 Pure Edition
Pursain said:
You can try getting into fastboot and run commands fastboot erase userdata and fastboot erase cache from your computer to pretty much factory reset the phone.
Sent from my Moto X 2014 Pure Edition
Click to expand...
Click to collapse
Thanks for the response. I tried entering the commands you suggested but the problem is still the same, phone stuck in the 'Warning, bootloader unlocked' loop. Does anyone have any other ideas? Really need some help with this, my little Moto has been dead for days!
And just an update on the situation, i noticed that if i go into CWM and select 'Wipe and Format Options' then 'Custom Format Options', choosing to format the cache and /data/media (/sdcard) options will stop the errors stated in the original post, but when i try flashing the ROM again the errors come straight back!
V3-571G said:
Thanks for the response. I tried entering the commands you suggested but the problem is still the same, phone stuck in the 'Warning, bootloader unlocked' loop. Does anyone have any other ideas? Really need some help with this, my little Moto has been dead for days!
And just an update on the situation, i noticed that if i go into CWM and select 'Wipe and Format Options' then 'Custom Format Options', choosing to format the cache and /data/media (/sdcard) options will stop the errors stated in the original post, but when i try flashing the ROM again the errors come straight back!
Click to expand...
Click to collapse
So sad to hear your Moto dead for the last days. Could you tell me more about your Moto? Can it turn off? Get into fastboot? Do you have recovery (stock or custom? Etc.
Sent from my Moto X 2014 Pure Edition
Pursain said:
So sad to hear your Moto dead for the last days. Could you tell me more about your Moto? Can it turn off? Get into fastboot? Do you have recovery (stock or custom? Etc.
Sent from my Moto X 2014 Pure Edition
Click to expand...
Click to collapse
Yeah it sucks having a pretty much lifeless Moto, kinda scary as well not knowing if i'll be able to get it working again! But in response to your questions, i can turn it off and get into fastboot, i'm also able to boot into my recovery which is Philz Touch (ClockworkMod). If you take a quick look at the original post, i updated it a short while ago to show more details about the errors which are displayed.
Bump, still dead!
V3-571G said:
Bump, still dead!
Click to expand...
Click to collapse
If you can get into fastboot you can flash the stock firmware (not backup) back onto your phone that way. I have used fastboot many times to restore my xt1028 Moto G many times after seemingly bricking it. You will need the stock firmware for your phone to do this.
Here is a tutorial:
http://forum.xda-developers.com/showthread.php?t=2542219
and here is a link to moto firmwares:
http://motofirmware.com/
Hope this helps.
classic757 said:
If you can get into fastboot you can flash the stock firmware (not backup) back onto your phone that way. I have used fastboot many times to restore my xt1028 Moto G many times after seemingly bricking it. You will need the stock firmware for your phone to do this.
Here is a tutorial:
http://forum.xda-developers.com/showthread.php?t=2542219
and here is a link to moto firmwares:
http://motofirmware.com/
Hope this helps.
Click to expand...
Click to collapse
Thanks for taking the time to respond to my request for help. I have already tried flashing the stock ROM via fastboot mode but it makes no difference to the situation, even though the new ROM flashes perfectly without error, when i try to boot it just gets stuck in the reboot loop on the 'Warning, bootloader unlocked' screen. I have no idea what to do now!
V3-571G said:
Thanks for taking the time to respond to my request for help. I have already tried flashing the stock ROM via fastboot mode but it makes no difference to the situation, even though the new ROM flashes perfectly without error, when i try to boot it just gets stuck in the reboot loop on the 'Warning, bootloader unlocked' screen. I have no idea what to do now!
Click to expand...
Click to collapse
I would suggest you try to install a custom recovery through fastboot (I use TWRP 2.7.1.0)
Just replace the stock recovery with TWRP in the fastboot file and use the command "flash recovery recovery.img" then reboot into recovery(hold power and volume down button down together for about ten seconds, release and you should see the fastboot screen. Then press recovery and then wipe>advanced>wipe ONLY cache and dalvik and then reboot)
See if that does the trick.
Try this: http://forum.xda-developers.com/showpost.php?p=58116154&postcount=14
You have not stated your model. Don't use batch files to fastboot flash the firmware. Make sure the image is 4.4.4.
classic757 said:
I would suggest you try to install a custom recovery through fastboot (I use TWRP 2.7.1.0)
Just replace the stock recovery with TWRP in the fastboot file and use the command "flash recovery recovery.img" then reboot into recovery(hold power and volume down button down together for about ten seconds, release and you should see the fastboot screen. Then press recovery and then wipe>advanced>wipe ONLY cache and dalvik and then reboot)
See if that does the trick.
Click to expand...
Click to collapse
lost101 said:
Try this: http://forum.xda-developers.com/showpost.php?p=58116154&postcount=14
You have not stated your model. Don't use batch files to fastboot flash the firmware. Make sure the image is 4.4.4.
Click to expand...
Click to collapse
Thanks very much for the responses. Unfortunately i already had Philz ClockwordMod recovery installed on the phone and had attempted the various wipe options a number of times without any success. However, i thought that as i'd only tried flashing the UK ROM to the device, i would attempt flashing a different ROM just to ensure there wasn't an issue here somewhere. I downloaded the stock US ROM and after extracting the archive i ran the Windows batch file to flash the files onto the phone. After the process had completed i rebooted the phone (Didn't bother going into recovery and wiping/formatting cache) and to my surprise the phone booted up completely fine! So weirdly it seems that just flashing a different ROM did the trick. But anyway, my Moto is alive again now, i'm very pleased to say the least!
Hi there, first post on here!
I've bought a nexus 5 off of eBay from some person who tried to root it and failed, thinking it would be an easy matter of restoring it.
However, the standard stock recovery process did not work, and I've encountered a number of issues:
When the device gets to erasing 'cache', it stays there for upwards of half an hour with no results.
With stock recovery flashed, pressing power + volUp immediately makes it erase /data, with no other options given.
It also does not show the stock recovery icon, instead a standing up android figure with a spinning poly in front of it.
Flashing TWRP and booting into recovery, it says 'e' is locked and goes into a boot loop.
Also no options in CWM recovery
I thought I would ask on here because it's out of my league now, I've tried on both windows and mac with no luck and I'm not sure what to try next, maybe just leave it until cache finally erases?
Thanks in advance!
You need to read read and read some more.
Start here:
http://forum.xda-developers.com/google-nexus-5/general/resource-guides-info-threads-linked-read-t2784527
It sounds like the bootloader is locked.
It's almost impossible to brick a nexus.
I've managed to get a version of CWM loaded.
Performing factory reset gives the error that /data cannot be mounted for wiping.
Bootloader is definitely open.
M1kesky said:
I've managed to get a version of CWM loaded.
Performing factory reset gives the error that /data cannot be mounted for wiping.
Bootloader is definitely open.
Click to expand...
Click to collapse
Ok :good:. That means you can install TWRP 3.0.
Try this: flash back to a completely stock MM or LP ROM by manually flashing each partition, inlcuding the userdata.img file. When you have finished flashing all partitions, boot directly to recovery from fastboot mode, perform a factory wipe, and reboot.
I've tried doing that but it just results in the standing up android icon, with power+up leading to it trying to wipe data again. no option to do a factory wipe.
I put TWRP 3.0.0 on just to test and ended up in a worse bootloop, which failed to load TWRP but occasionally got into it and displayed this:
imgur.com/RKyZIJf
Sorry as I am a new user it doesn't let me use links
audit13 said:
Try this: flash back to a completely stock MM or LP ROM by manually flashing each partition, inlcuding the userdata.img file. When you have finished flashing all partitions, boot directly to recovery from fastboot mode, perform a factory wipe, and reboot.
Click to expand...
Click to collapse
Thanks, I gave it another try and did the recovery partition last, and made sure I manually put it into recovery mode from bootloader.
The red triangle and recovery menu are back, I can't thank you enough!
Glad you got it to work. I suggest using TWRP 2.8.7.1. For some reason version 3.0 does not work properly with all N5 phones.
It's still happening.
I've been away for a few days so only had the chance to respond now.
I got into the ususal recovery screen as mentioned previously and tried to do a factory reset, but it had problems with /data again.
I left it the entire night while I slept and it was still saying formatting /data in the morning, nothing had changed.
Anybody got any more suggestions? It's also back to the android with the rotating poly instead of the android with the exclamation mark.
EDIT: when flashing userdata, no matter what version of android I try, it always hangs.
It started on 6.0.1 if that helps.
The userdata.img file is included with each stock rom. I advise against mixing userdata.img files from different stock ROMs.
Sorry, I mean that I've flashed completely whole different versions of android and the result is the same across all of them, not that I've used different userdata img's on the same version of android.
Could be an emmc problem which would require a motherboard swap.
Is that likely to happen when the previous owner said it was fine before they tried to root?
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 friends, when I flash Combination file, or stock file , my phone boots and hang at start up logo, while I restart to recovery I see this error (E:Failed to mount efs, Invalid Argument)?
Can anyone help?
What have you done ? Trying to root and lost your IMEI ?
If so, then go to recovery and do all of the wipes and format Data. Once done, then just flash the exact same ROM as the one which is already installed on your phone.
TheRealKeyserSoze said:
What have you done ? Trying to root and lost your IMEI ?
If so, then go to recovery and do all of the wipes and format Data. Once done, then just flash the exact same ROM as the one which is already installed on your phone.
Click to expand...
Click to collapse
This steps does not work, I need EFS for A8 2018.
I'm having the same problem, I've tried everything. z3x, Odin , won't even let me flash from sd card. Won't load into Oreo just keeps rebooting. I can get into recovery but does nothing as well as boot loader. I did have a utility im pretty sure was made by FACTORY BINARY that was it's own little OS with a bunch of little tools. I have a sm-a530w flashed with boot loader 4 ugggg. If anyone can help find that utility that will wipe the whole thing and let me flash from scratch that would be awesome. I've tryed miracle, Uni-Android, samsung tools 29.5 and flashing with odin. Lets me flash factory FIRMWARE but still error's out on the "Failed to mount EFS" HELPPLEASE
A quick suggestion you probably tried, but i've had failure at boot in the past after returning to stock via odin if i used home_csc. So, if you haven't already tried, use just csc. No home. On home it does system.img until the end, no user_data . Not sure at all what the deal is but it's all i can suggest. Get 'er goin'!
:Failed to mount EFS
Yes I think I tried that, but at this point, I try again. Any more suggestions would be greatly appreciated. An A8 in mint shape just hurts LOL.