Trying to Twrp GApps.
mount -o bind 'data/media' ' /sdcard' process ended with signal: 11
Updater process ended with signal: 11
Error installing zip file '/external_sd/open_gappss-arm-7.1-stock-20170311.zip
I didnt have any problems flashing files until i flashed MIUI 8, which didnt work. I then wiped the usual folders and flashed lineage-14.1 ok but not GApps. Hence the error.:crying:
I'm now back on a Stock rom.
Any idea how to fix?
Use another version of twrp. 3.0.3-n2 by shreps and 3.1 by oadam11 works fine. (search them)
Ok, I'll take a look. I was using twrp-3.1.0-athene_shreps.img. Also twrp not sticking to recovery either.
ddettmer said:
Ok, I'll take a look. I was using twrp-3.1.0-athene_shreps.img. Also twrp not sticking to recovery either.
Click to expand...
Click to collapse
If by twrp isn't sticking you mean the stock recovery keeps loading, reboot into recovery after you've flashed twrp, else the stock recovery will overwrite the custom recovery. After that, twrp should stick around.
Related
I am trying to flash my N4 with cyanogenmod following the official wiki.
I'm at the point where I've installed TWRP into recovery, I've wiped everything (I've even formatted them since I couldn't wipe all of it initially), and the only error I see is "unable to mount /usb-otg".
Then, I've "installed" the CN zip files for the 13 and 12 versions, none of them works in the sense that when I reboot the system, I'm always coming back to TWRP.
What's wrong? Any suggestion?
Thanks
I've the same problems with my nexus 4
gerardgerard said:
I am trying to flash my N4 with cyanogenmod following the official wiki.
I'm at the point where I've installed TWRP into recovery, I've wiped everything (I've even formatted them since I couldn't wipe all of it initially), and the only error I see is "unable to mount /usb-otg".
Then, I've "installed" the CN zip files for the 13 and 12 versions, none of them works in the sense that when I reboot the system, I'm always coming back to TWRP.
What's wrong? Any suggestion?
Thanks
Click to expand...
Click to collapse
Hi gerardgerard,
I also wanted to flash my Nexus 4 with Cyanogenmod 12.1. So I installed TWRP into recovery and wiped everything, like it's explained in the wiki. I can also see the error "unable to mount /usb-otg". When I want to reboot the system I always get back to TWRP. Cyanogenmod doesn't boot correctly. Did you find a solution for the problem?
same problem
Hi
I'm having the same problem. As follows:
Cause (my mistake): I have been using Cyanogen-mod nightlies for a couple of months on my Nexus 4, and made the grave mistake of leaving the phone to upgrade one night but without it being plugged in properly - and it ran out of power part way through! (At least, that's what I think happened).
Fortunately, it would boot into bootloader and I could use adb/fastboot. I (re)installed TWRP 2.8.7.0 (from my Mac, using fastboot). And that works fine - I can boot into twrp ok.
Next I loaded the latest nightly from cm (using fastboot - is this what people call sideloading?) and used twrp to install it. It goes through the installation fine (the only error message is that it can't mount /usb-otg). But when I reboot it just goes back to twrp.
I then tried installing the earlier cm nightly that I know worked, but with the same result.
Finally, before I first installed cm I did a backup (using twrp), and I have tried recovering that. It seems to do all the right things, but again when I reboot it just goes back to twrp.
Any suggestions would be welcome.
Thanks
J
Flash back to a completely stock ROM and run through the set up to make sure everything works. Then copy CM to the phone, reboot to fastboot, flash twrp, immediately boot into recovery using the volume and power button without leaving fastboot, wipe data, cache, system, flash CM, reboot.
If the phone will not boot after flashing a stock ROM, boot to fastboot, flash the userdata.img file, and immediately go to stock recovery without leaving fastboot, wipe data/cache, reboot.
It works now!
I managed to fix the problem ... I found this guide for the Nexus 5:
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
and I applied those instructions. It didn't work first time, so I just repeated them and now it's working. I used the 5.1.1 stock downloaded from https://developers.google.com/android/nexus/images#occam.
I guess this is what audit13 means in their post - so thanks are due there.
I will next reinstall twrp and cm and I don't expect any problems with that (having done it successfully before).
Smaje
I officially upgraded to 3.0.2, unlocked and rooted my phone.
It was fine for the first few times I flashed multiple ROMs. But ever since I flashed Exodus, I keep having issues switching to different ROM.
A week ago, I flashed "Switch to OOS3_H2OSMMv7" zip and was able to flash Resurrection Remix, but today when I tried switching to CM13 or PA it gets stuck at flashing the ROM zip. I tried flashing the firmware zip again and flash the ROM, but to no avail. It won't flash any ROMs now, just stuck at recovery while flashing the zip.
I have a working fastboot and recovery mode though, so I'm trying to avoid flashing the entire factory image but that seems to be only option left. Does anyone have any clue as to why this is happening and how I can fix it?
Edit: Resurrection Remix gets installed fine, CM13 and PA still giving me issues.
Edit: I downloaded the latest version of CM13 and it works. Earlier I was using June 30 build which seems to have issues with the new firmware. I'll try out the new PA build to see if it fixes that too.
What error does your recovery gives?
Do you have Data Backup?
Can you access ADB while in Recovery?
piyushmodi01 said:
What error does your recovery gives?
Do you have Data Backup?
Can you access ADB while in Recovery?
Click to expand...
Click to collapse
It does not show any error as it just looping while installing the zip. I have to force shut down the phone to exit it.
Yes, I have backed up all my data
Yes, I am able to access my phone in both ADB and in fastboot modes.
After flashing Custom ROM, Wipe data, cache, d-cache and then reboot.
If still doesnt work try flashing another custom ROM. You can use adb-sideload to flash another zip in recovery mod.
So i was swapping roms: i booted into twrp, cleared cache and data and flashed my rom ( ResurrectionRemix-M-v5.6.0-20151213-wt88047.zip ) and Gapps.
i noticed flashing RR took just a minute and returned this message:
"unmount of /system failed; no such volume
script succeeded: result was [0.200000]"
after that the Gapps package flashed with no problem, but my phone does not boot properly.
Edit: i also tried different twrp versions, but i got the same result with each of them
It does still boot to fastboot, but i wasn't able to get into android.
i read something about cf.lumen drivers causing this kind of error while swapping roms, but i don't know if they were there in the first place or how to uninstall them.
ap29600 said:
So i was swapping roms: i booted into twrp, cleared cache and data and flashed my rom ( ResurrectionRemix-M-v5.6.0-20151213-wt88047.zip ) and Gapps.
i noticed flashing RR took just a minute and returned this message:
"unmount of /system failed; no such volume
script succeeded: result was [0.200000]"
after that the Gapps package flashed with no problem, but my phone does not boot properly.
Edit: i also tried different twrp versions, but i got the same result with each of them
It does still boot to fastboot, but i wasn't able to get into android.
i read something about cf.lumen drivers causing this kind of error while swapping roms, but i don't know if they were there in the first place or how to uninstall them.
Click to expand...
Click to collapse
Good night, try to flash miui. Then install twrp 3-1 and ROM. But first go to the Lineageos tag and download the modem and flash. Then try ROM again.
I had MIUI installed before the Rom flash, and i was using fastboot ti boot into twrp without actually flashing it.
I eventually solved my issue by flashing a different rom, so i think the one i was using was corrupted or Just bugged.
Thanks for the support.
so i just doing a clean install of the beta 3 rom, i did follow the instruction that written in the thread but some how after installing the update when i'm about to reboot into system it keeps rebooting into the recovery. so i decided to clean wipe and re-flash the rom, and some how it says that there's no rom installed. i've tried to install other custom rom like, LOS 15 and Liquid Remix, but it's still the same, keep booting to recovery and showing that there's no rom installed. plz help...
Go to twrp > wipe > format data > yes
Then transfer oos OB 3 to your phone, use adb push command is better than copy paste(not sure why because sometimes i copy pasted into phone, sometime it bootloop or storage not recognised)
Flash it, then flash magisk 15.2. then reboot. It should work fine. Unless you use a not compatible twrp version.
thanks for ur solution before, but can u tell me the compatible twrp is, cuz i'm using the twrp 3.2.1 by blu spark and it keeps booting into recovery
You need to flash no verity zip. If you are decrypted.
"You need to flash no verity zip. If you are decrypted. "
Thanks god for this comment, use about 2 hours digging around forums and re-flashing, wiping, trying diffrent TWRPs, different roms. And when I found this comment I just isntalled the zip and it worked within 10 seconds.
I am currently using a OnePlus 5 which used to run on a stock based rom, xxxNoLimits v3.1
Since the dev ended the support I wanted to revert back to pure OOS, so I downlaoded the newest 5.1.5 zip and followed the instructions using the newest blu_spark twrp recovery but right after pressing the "flash" button I kept getting error 7, so I download the zip from a mirror link and I have also tried the newest version of codeworkx twrp, still error 7. Then I tried flashing the original stock recovery in order to flash the zip but it instantly threw me back to the zip selection menu, flashing the zip via adb sideload kept quitting at exactly 47%. At this point I was pretty frustrated, I flashed twrp codeworkx again and wiped EVERYTHING, which includes the system, data, cache, dalvik partitions and then I also did a format on the data partition, the point was that now I would have a clean phone only running twrp and I thought I could easily flash the newest zip now without any problems, NOPE, still error 7!!! Now I am stuck here, the stock recovery doesnt let me flash anything and I've tried 4 different versions of twrp recoverys and every single one gives me the same error, I even dug up an older version of OOS, I think it which I had running for a few weeks without any probles so I knew that the zip was not corrupted but same error
Now I had given up and wanted to restore the backup I did just in case anything goes wrong, well, restoring the backup fails when it tries to restore the data partition, so I unchecked everything except system, system image and recovery but it didnt work, now I am sitting here with my phone telling me that there's no OS installed. any advice?
Use Unbrick Tool and Restore
Hey,
You can Flash your Mobile using the Unbrick tool at - https://androidfilehost.com/?w=files&flid=204903
Use the Latest file which I guess comes with OOS 5.1.3 - https://androidfilehost.com/?fid=962339331458999196
If you try to Go to Open Beta ROM First Flash Open Beta 12--> Open Beta 13 --> Open Beta 17
freaky2xd said:
I am currently using a OnePlus 5 which used to run on a stock based rom, xxxNoLimits v3.1
Since the dev ended the support I wanted to revert back to pure OOS, so I downlaoded the newest 5.1.5 zip and followed the instructions using the newest blu_spark twrp recovery but right after pressing the "flash" button I kept getting error 7, so I download the zip from a mirror link and I have also tried the newest version of codeworkx twrp, still error 7. Then I tried flashing the original stock recovery in order to flash the zip but it instantly threw me back to the zip selection menu, flashing the zip via adb sideload kept quitting at exactly 47%. At this point I was pretty frustrated, I flashed twrp codeworkx again and wiped EVERYTHING, which includes the system, data, cache, dalvik partitions and then I also did a format on the data partition, the point was that now I would have a clean phone only running twrp and I thought I could easily flash the newest zip now without any problems, NOPE, still error 7!!! Now I am stuck here, the stock recovery doesnt let me flash anything and I've tried 4 different versions of twrp recoverys and every single one gives me the same error, I even dug up an older version of OOS, I think it which I had running for a few weeks without any probles so I knew that the zip was not corrupted but same error
Now I had given up and wanted to restore the backup I did just in case anything goes wrong, well, restoring the backup fails when it tries to restore the data partition, so I unchecked everything except system, system image and recovery but it didnt work, now I am sitting here with my phone telling me that there's no OS installed. any advice?
Click to expand...
Click to collapse
Flashing newest oos doesn't always work l have had this sometime l have had to go back 3 oos versions then flash them in order to flash the latest release.
freaky2xd said:
I am currently using a OnePlus 5 which used to run on a stock based rom, xxxNoLimits v3.1
Since the dev ended the support I wanted to revert back to pure OOS, so I downlaoded the newest 5.1.5 zip and followed the instructions using the newest blu_spark twrp recovery but right after pressing the "flash" button I kept getting error 7, so I download the zip from a mirror link and I have also tried the newest version of codeworkx twrp, still error 7. Then I tried flashing the original stock recovery in order to flash the zip but it instantly threw me back to the zip selection menu, flashing the zip via adb sideload kept quitting at exactly 47%. At this point I was pretty frustrated, I flashed twrp codeworkx again and wiped EVERYTHING, which includes the system, data, cache, dalvik partitions and then I also did a format on the data partition, the point was that now I would have a clean phone only running twrp and I thought I could easily flash the newest zip now without any problems, NOPE, still error 7!!! Now I am stuck here, the stock recovery doesnt let me flash anything and I've tried 4 different versions of twrp recoverys and every single one gives me the same error, I even dug up an older version of OOS, I think it which I had running for a few weeks without any probles so I knew that the zip was not corrupted but same error
Now I had given up and wanted to restore the backup I did just in case anything goes wrong, well, restoring the backup fails when it tries to restore the data partition, so I unchecked everything except system, system image and recovery but it didnt work, now I am sitting here with my phone telling me that there's no OS installed. any advice?
Click to expand...
Click to collapse
Hi ! Do you have some news about it ? I have the same issue since Monday...
I've tried like anything i've found and even more, but nothing did the job ...
The only way to have my OP5 working is downgrade to an old version running Android 7.1.1