Need help: failed to mount cust invalid argument - Huawei Mediapad M3 Questions & Answers

Hope somebody can help! After flashing TWRP, I accidentally flashed a wrong ROM. Now I can't flash any ROM because Cust can't be mounted, "failed to mount '/cust' (invalid argument)".
Please help, thanks!

Can't remember the exact commands, but I would download stock rom and flash using ADB. That way you are just starting over. You should be able to find ample ADB instructions by Googling how to flash stock with ADB.
Sent from my Pixel XL using Tapatalk

ahent said:
Can't remember the exact commands, but I would download stock rom and flash using ADB. That way you are just starting over. You should be able to find ample ADB instructions by Googling how to flash stock with ADB.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
I just found they can use ADB Sideload to flash stock rom. Unfortunately, my phone can't load to get USB Debugging enable.

My guess would be to try a wipe in twrp first then load the stock rom. You are over my head at this point.
Sent from my BTV-W09 using Tapatalk

ahent said:
My guess would be to try a wipe in twrp first then load the stock rom. You are over my head at this point.
Sent from my BTV-W09 using Tapatalk
Click to expand...
Click to collapse
Already tried wipe and format, but it did not work. I still can't flash new rom, "failed to mount '/cust' (invalid argument)".

- Flash stock BTV-DL09C233B030 through TWRP, it still did not work, "failed to mount '/cust' (invalid argument)".
- Format and advanced wipe did not work, "failed to mount '/cust' (invalid argument)".
- adb fastboot flash system, recovery, boot.... did not work.
- Dload stock BTV-DL09C233B030, it was incompatible with current version, failed at 5%.
Last choice was to send the device to the Huawei Service Center: Worked! I did not know what they had done with my device. After waiting for 20mn, they gave back my device with everything working again. And it was back to BTV-DL09C209B009. However, the bootloader was still unlocked. I was charged $5 for the service. Or they told me if they could not have solved this, I would be charged $162 for exchanging with new device in box.
After that, what I had tried was to do factory reset and go to ADB oem relock. Now my device was bootloader locked!

any solution?
I am facing the same problem with my Lenovo Zuk Z2 Plus - any way to resolve this for any / all devices?
Have tried to flash the stock ROM, reformatting, repairing FS, changing FS format, etc to no avail.
Any help will be greatly appreciated.

dexterkarthik said:
I am facing the same problem with my Lenovo Zuk Z2 Plus - any way to resolve this for any / all devices?
Have tried to flash the stock ROM, reformatting, repairing FS, changing FS format, etc to no avail.
Any help will be greatly appreciated.
Click to expand...
Click to collapse
LENOVO SERVICE CENTER maybe ?

Service center is the last resort! There sold be something that we can do as users.
I have access to copy zip files to flash via twrp, but the flashing / modifying / writing, etc fails with the Mount /custom message. So this is more of a software config bug I believe.

It depends:
- Which ROM?
- How you flashed it?
Without correct informations we can't help...

Tried all ROM's, now it is without OS.
The phone was just a day old. I unlocked the boatloader with the file from zuk.
Then flashed twrp.
Then tried installing lineage 14.1 unofficial, which failed with the same error.
Hence I did a factory reset and then tried mokee. Which also failed.
Tried RR - no go.
Tried mounting from twrp - no go.
Tried adb side load - no go.
Tried flashing back stock ROM via QPST - no go.
Now it had become more of a challenge to did this weird issue.
PS - when I try the ROM's now, it says "this device is Z2121" while I know it is Z2132, because it is the lenovo z2 plus India version!

Related

Tab 7.7 P6810 SERIOUSLY bricked..!! :(

Hi Folks,
I'll try to be as detailed as possible..days ago, I flashed a custom ROM on my ICS 7.7 stock Tab, however it kept on a boot loop. I made a backup via CWM so I tried to restore back to ICS...can't restore it ("Error while restoring /system") OK, no worries....
I tried to flash the HC and ICS stock back using ODIN....can't do it (in both times, It keeps getting stuck at "factoryfs.img" at the beginning)...starting to get worried..
Tried to use adb shell and e2fsck -cy /dev/block/mmcblk0p9.... no luck (kept getting the "error reading block *numbers increasing* (Attempt to read block from filesystem resulted in short read) while reading inode and block bitmaps. Ignore error? yes Force rewrite? yes" and then nothing happened...tried to wipe/format data...CWM crashed
Tried to flash a P6810 PIT file to repartition the tab...no luck, ODIN still stuck at "factoryfs"
Tried to flash Android Stock Recovery...finally got wipe/format data to work...tried to flash "SkyHigh ROM" based on stock ICS (Remember that ODIN method doesn't work?) it installs, BUT when rebooting, it just stays looping at the Samsung Logo... now oficially Freaked out..!!:crying::crying:
Finally everytime I went to recovery mode, I get the following:
"E:failed to mount /preload (Invalid argument)
E:install_application_for_customer:can't mount /preload
your storage not prepared yet. please use UI menu for format and reboot options
copy aplication failed"
Like I said, I can wipe/format data and cache on stock recovery (can't do it on CWM) and also can flash ROM .zips (can't do it in ODIN)
So, to sum it up:
- Can't flash anything using ODIN (stuck at factoryfs)
- Can't flash using CWM (getting Samsung logo bootloop)
- Can't wipe/format data on CWM, it crashes (althought I can do it with stock recovery)
- VERY BASIC skills in adb shell (don't know to use it very much)
- I know (hope) it's not hard bricked because I can enter Download and Recovery modes
- Basically at this point, yeah I'm pretty sure to start banging my head on the wall
Can anyone help me out on this one..??? It's been 4 days trying everything
Any, ANY help will be deeply appreciated... :crying:
Thanks
have you wiped using the stock recovery? this happened to me before (there's a thread here entitled stuck at bootscreen/boot loop) some let the device drain it's battery, what I did was wipe it using the factory wipe the connect via ODIN to install the stock HC ROM
I wiped using the stock recovery...however, everytime I try to flash HC or ICS stock ROM using ODIN, It gets stuck at the very beginning of the "FACTORYFS" phase....
Last night tried to adb shell but now it gives me the "/system/bin/sh failed: no such file or directory"
I've been reading every single thread about how to revive it, but somehow I can't....
Go to notes forum they have threads how to repartation yr tab n make it work
Sent from my GT-P6800 using xda premium
i got stuck at the 'FACTORYFS' in ODIN no matter what i tried. i had flashed CWM using ODIN, but no ROM would flash.
turns out my usb cable being plugged into a USB hub was the culprit. it still flashed CWM like that, but the first time i tried flashing the ROM with the USB plugged right into my desktop, it worked.
just throwing that out there.
Yes. Seems like you have emmc bricked your tab. There is a fix for it. Search for emmc bug
Sent From the Tab
idiotekniQues said:
i got stuck at the 'FACTORYFS' in ODIN no matter what i tried. i had flashed CWM using ODIN, but no ROM would flash.
turns out my usb cable being plugged into a USB hub was the culprit. it still flashed CWM like that, but the first time i tried flashing the ROM with the USB plugged right into my desktop, it worked.
just throwing that out there.
Click to expand...
Click to collapse
to add to this. while i was experiencing this, i too could not flash any zip rom via CWM, it would bootloop also.
however i could wipe cache using CWM, which you can't.
Finally got it working... !!! However I could only installed CM9 "successfully" since it keeps freezing and crashing...Is there any stable custom ROM that I can install via CWM..?? (Odin keeps hanging at "factory's")

[Q] Bricked LG G2 help required

Hi Guys, I was trying to edit the build prop and have encountered a serious issue.
After the restart my mobile im continiously getting com.android.systemui has stopped as a result i cannot do any thing.
I downloaded a rom and tried flashing it adb sideload but it is ailing due to signature verification.
I got this phone as a used phone so it has a recovery which doesnt not have option for toggling the signature verification.
Please help me as ive been trying this since 12 hours now
i have some recovery but it doesnt have much options, just update from sd
update from cache
update from adb
wipe data/ factory reset and
update cache
if i can some one toggle signature verification off i think that shoudl work out.
That's factory recovery, you won't be able to flash ROMs from it.
You will probably have to flash back to stock using the guides here.
is there a way to flash twrp in and then flash any custom rom
pema.yozer said:
is there a way to flash twrp in and then flash any custom rom
Click to expand...
Click to collapse
not sure if there is, but I don't think so
maybe you could try adb pushing a 'good' build.prop file. On kitkat you can adb sideload kk_root.zip from ioroot using stock recovery, for example, so it maybe possible... again I'm not sure, sorry.
but it's probably quicker to just flash the whole ROM from download mode, if you check the development section there's a new easy to use flashtool, where you can choose not to wipe your data.. just make sure you flash the right kdz file

[Q] XT907 Problems with Clockwork Recovery installing Cyanogenmod

I recently rooted my Droid Razr M XT907 and have had nothing but problems. Before rooting, I was on 4.4.2. I used the Towelroot app to root my phone, Root Checker to verify root, and Motopocalypse to unlock my bootloader. I tried to flash a custom recovery and I could not boot into recovery. I also tried to flash a new logo to get rid of the bootloader unlocked warning screen. Apparently I flashed a corrupted file because it caused my phone not to turn on right and I had to go straight to the boot menu and AP fastboot to flash stock 4.4.2 for my phone. I then proceeded to root my phone again, and start over(except I didn't have to unlock my bootloader again). After another few hours, I finally got CWM Recovery v6.0.4.8 installed on my phone. I tried to wipe data/factory reset and it did this:
- - Wiping data. . .
Formatting /data. . .
Error mounting /data!
Skipping format. . .
Formatting /cache. . .
Formatting /sd-ext. . .
E: unkown volume for path [/sd-ext]
Formatting /sdcard/.android_secure!
Skipping format. . .
Data wipe complete.
I am pretty sure that it did not format. I tried goint to mounts and storage menu and mounting /data there and it said:
Error mounting /data!
Thinking it was not a big deal, I proceeded to try and install zip from the external sd card. I went to Install Zip > Choose zip from /storage/sdcard1 and selected the zip I had on there called "cm- 11 -20140218-NIGHTLY-xt907.zip" and this is what it gave me:
- - Installing: /storage/sdcard1/cm- 11-20140218-NIGHTLY-xt907.zip
Finding update package. . .
Opening update package. . .
Installing update. . .
This package is for "xt925, xt926, xt907, vanquish_u, vanquish, scorpion_mini, mb886, qinara, asanti, asanti_c, xt897, xt897c" devices; this is a " ".
E: Error in /storage/sdcard1/cm- 11 -20140218-NIGHTLY-xt907.xip
(Status 7)
Installation aborted
At this point, all i want to do is be able to flash Cyanogenmod on my phone. Is there any way to fix the mounting /data problem? Is there just an easier way to install Cyanogenmod at this point? Any help would be greatly appreciated.
Sporty824 said:
I recently rooted my Droid Razr M XT907 and have had nothing but problems. Before rooting, I was on 4.4.2. I used the Towelroot app to root my phone, Root Checker to verify root, and Motopocalypse to unlock my bootloader. I tried to flash a custom recovery and I could not boot into recovery. I also tried to flash a new logo to get rid of the bootloader unlocked warning screen. Apparently I flashed a corrupted file because it caused my phone not to turn on right and I had to go straight to the boot menu and AP fastboot to flash stock 4.4.2 for my phone. I then proceeded to root my phone again, and start over(except I didn't have to unlock my bootloader again). After another few hours, I finally got CWM Recovery v6.0.4.8 installed on my phone. I tried to wipe data/factory reset and it did this:
- - Wiping data. . .
Formatting /data. . .
Error mounting /data!
Skipping format. . .
Formatting /cache. . .
Formatting /sd-ext. . .
E: unkown volume for path [/sd-ext]
Formatting /sdcard/.android_secure!
Skipping format. . .
Data wipe complete.
I am pretty sure that it did not format. I tried goint to mounts and storage menu and mounting /data there and it said:
Error mounting /data!
Thinking it was not a big deal, I proceeded to try and install zip from the external sd card. I went to Install Zip > Choose zip from /storage/sdcard1 and selected the zip I had on there called "cm- 11 -20140218-NIGHTLY-xt907.zip" and this is what it gave me:
- - Installing: /storage/sdcard1/cm- 11-20140218-NIGHTLY-xt907.zip
Finding update package. . .
Opening update package. . .
Installing update. . .
This package is for "xt925, xt926, xt907, vanquish_u, vanquish, scorpion_mini, mb886, qinara, asanti, asanti_c, xt897, xt897c" devices; this is a " ".
E: Error in /storage/sdcard1/cm- 11 -20140218-NIGHTLY-xt907.xip
(Status 7)
Installation aborted
At this point, all i want to do is be able to flash Cyanogenmod on my phone. Is there any way to fix the mounting /data problem? Is there just an easier way to install Cyanogenmod at this point? Any help would be greatly appreciated.
Click to expand...
Click to collapse
I'm not techy so don't know what exactly is going on, but I advise dealing with the mount problems before you proceed to flashing CM. If flashing stock again via RSD won't fix this, I assume your /data partition is faulty.
Sporty824 said:
I recently rooted my Droid Razr M XT907 and have had nothing but problems. Before rooting, I was on 4.4.2. I used the Towelroot app to root my phone, Root Checker to verify root, and Motopocalypse to unlock my bootloader. I tried to flash a custom recovery and I could not boot into recovery. I also tried to flash a new logo to get rid of the bootloader unlocked warning screen. Apparently I flashed a corrupted file because it caused my phone not to turn on right and I had to go straight to the boot menu and AP fastboot to flash stock 4.4.2 for my phone
. I then proceeded to root my phone again, and start over(except I didn't have to unlock my bootloader again). After another few hours, I finally got CWM Recovery v6.0.4.8 installed on my phone. I tried to wipe data/factory reset and it did this:
- - Wiping data. . .
Formatting /data. . .
Error mounting /data!
Skipping format. . .
Formatting /cache. . .
Formatting /sd-ext. . .
E: unkown volume for path [/sd-ext]
Formatting /sdcard/.android_secure!
Skipping format. . .
Data wipe complete.
I am pretty sure that it did not format. I tried goint to mounts and storage menu and mounting /data there and it said:
Error mounting /data!
Thinking it was not a big deal, I proceeded to try and install zip from the external sd card. I went to Install Zip > Choose zip from /storage/sdcard1 and selected the zip I had on there called "cm- 11 -20140218-NIGHTLY-xt907.zip" and this is what it gave me:
- - Installing: /storage/sdcard1/cm- 11-20140218-NIGHTLY-xt907.zip
Finding update package. . .
Opening update package. . .
Installing update. . .
This package is for "xt925, xt926, xt907, vanquish_u, vanquish, scorpion_mini, mb886, qinara, asanti, asanti_c, xt897, xt897c" devices; this is a " ".
E: Error in /storage/sdcard1/cm- 11 -20140218-NIGHTLY-xt907.xip
(Status 7)
Installation aborted
At this point, all i want to do is be able to flash Cyanogenmod on my phone. Is there any way to fix the mounting /data problem? Is there just an easier way to install Cyanogenmod at this point? Any help would be greatly appreciated.
Click to expand...
Click to collapse
First, you need to update your recovery. > http://goo.gl/7pDg47
Second, your trying to flash an outdated ROM that wont work on the updated KK bootloader. Go to the CM thread and download the correct version for your device. > http://goo.gl/Jx8EOu
Custom boot logos > http://goo.gl/fgOCNb
@ATTACK
Should I stick with CWM or switch to TWRP? Or is it just personal preference? Also, should I reflash stock and try again or just start reflashing the recovery and new ROM? The logo is lowest on my priority list btw.
Edit: So wait, is the Razr M XT907 a part of the Moto_MSM8960 devices? I could just install that like I would the other one?
Sporty824 said:
@ATTACK
Should I stick with CWM or switch to TWRP? Or is it just personal preference? Also, should I reflash stock and try again or just start reflashing the recovery and new ROM? The logo is lowest on my priority list btw.
Edit: So wait, is the Razr M XT907 a part of the Moto_MSM8960 devices? I could just install that like I would the other one?
Click to expand...
Click to collapse
Yup, it's personal preference. I prefer TWRP but just use whatever your comfortable with.
I see no need to go stock, just flash the new recovery then the ROM. And yes, all the moto_msm8960 devices have been unified, this includes the xt907. Just make sure you use the KK bootloader compatible version.
ATTACK said:
Yup, it's personal preference. I prefer TWRP but just use whatever your comfortable with.
I see no need to go stock, just flash the new recovery then the ROM. And yes, all the moto_msm8960 devices have been unified, this includes the xt907. Just make sure you use the KK bootloader compatible version.
Click to expand...
Click to collapse
OK. I downloaded a new custom recovery (I switched to TWRP since is was all touch based and I somehow broke the volume buttons on my last android). I then downloaded the newest CM and flashed it and the GAPPS. Everything works great. I even flashed a custom logo (the batman one). Thank you.
OK, someone please help, got everything else working, except data. I can't get mobile data working. I just want to know if there is anything I can do.
Sporty824 said:
OK, someone please help, got everything else working, except data. I can't get mobile data working. I just want to know if there is anything I can do.
Click to expand...
Click to collapse
Ummm.... try RSDing back to stock and see if your data comes back.
ATTACK said:
Ummm.... try RSDing back to stock and see if your data comes back.
Click to expand...
Click to collapse
Flashed back to stock. Still no data. Any other suggestions?
Edit: Nevermind, started working on stock after I flashed a new radio and reflashed stock. Going to try to install cm when I get home and hope it works
I reflashed stock, and data worked. I flashed CM11, and it didn't. I reflashed stock, and it worked again. I searched the problem online, again. I somehow found a site that I missed when I searched it the first few times. The site provided a fix that involved flashing cm11, gapps, and another zip. I tried it and it worked. For anyone who is having the same or similar problem, the link is below. Thank you ATTACK for all of the help and Deante Flood for making the zip that I flashed that made the data work again.
https://help.ting.com/entries/42358068-LTE-MMS-APN-Fix-Android-4-4-Kit-Kat-

Yu Yureka boots into "FASTBOOT MODE"

So I recently rooted and flashed a custom rom (https://forum.xda-developers.com/yureka/general/rom-bootleggers-rom-v2-1-volte-t3777131) on my device, all was working fine until I realized that I didn't flash gapps. Downloaded gapps tried flashing (on TWRP) it but I got the error "error executing updater binary" . Googled up for a solution and got this:
Step 1:- Go to recovery.
Step 2:- Go to Wipe>>Advanced wipe.
Step 3:- Check data, system, cache & dalvik cache and then swipe to wipe all.
Step 4:- Then go to install zip from SD card and browse the Rom and install it.
Step 5:- Reboot the device
After this, somehow, I lost the rom but had my TWRP recovery still but I was able to flash the rom again using "minimal adb and fastboot". Everything was working fine but I still didn't have gapps and I thought I did something wrong with the steps aforementioned so I took a shot at those steps again. And boom! my device now keeps booting into "FASTBOOT MODE"(can't even go to recovery) and I tried several methods to try and fix and the most frequent "fix" I got for this on Google was to use adb and fastboot and use the command "fastboot oem unlock" but that didn't help either. PLEASE HELP ME OUT. JUST NEED TO GET A RECOVERY (TWRP/CWM) and flash my rom
fastboot -i 0x1ebf erase cache
fastboot -i 0x1ebf erase userdata
Flash twrp 3.2.2
fastboot -i 0x1ebf flash recovery twrp_3.2.2.img
Sent from my AO5510 using Tapatalk
---------- Post added at 06:19 AM ---------- Previous post was at 06:18 AM ----------
brickedmyphone1 said:
So I recently rooted and flashed a custom rom (https://forum.xda-developers.com/yureka/general/rom-bootleggers-rom-v2-1-volte-t3777131) on my device, all was working fine until I realized that I didn't flash gapps. Downloaded gapps tried flashing (on TWRP) it but I got the error "error executing updater binary" . Googled up for a solution and got this:
Step 1:- Go to recovery.
Step 2:- Go to Wipe>>Advanced wipe.
Step 3:- Check data, system, cache & dalvik cache and then swipe to wipe all.
Step 4:- Then go to install zip from SD card and browse the Rom and install it.
Step 5:- Reboot the device
After this, somehow, I lost the rom but had my TWRP recovery still but I was able to flash the rom again using "minimal adb and fastboot". Everything was working fine but I still didn't have gapps and I thought I did something wrong with the steps aforementioned so I took a shot at those steps again. And boom! my device now keeps booting into "FASTBOOT MODE"(can't even go to recovery) and I tried several methods to try and fix and the most frequent "fix" I got for this on Google was to use adb and fastboot and use the command "fastboot oem unlock" but that didn't help either. PLEASE HELP ME OUT. JUST NEED TO GET A RECOVERY (TWRP/CWM) and flash my rom
Click to expand...
Click to collapse
https://dl.twrp.me/tomato/
Sent from my AO5510 using Tapatalk
Thank you very much!! I am so sorry for the late af reply, got a little carried away with some other thing(s). I got the recovery now and I used a micro SD card to flash the rom but the problem now is that I'm getting the error 7 ("Updater process ended with ERROR: 7 Error installing zip file "/external_sd/" followed by filename.zip)
and then it says "Updating partition details... Failed to mount '/cache' (Invalid arguement)
...done"
I do not understand what seems to be the problem....I thought the issue might be with me trying to flash it via the memory card so I tried using the "adb sideload" method which yielded the same results. I have no idea what is to be done now
brickedmyphone1 said:
Thank you very much!! I am so sorry for the late af reply, got a little carried away with some other thing(s). I got the recovery now and I used a micro SD card to flash the rom but the problem now is that I'm getting the error 7 ("Updater process ended with ERROR: 7 Error installing zip file "/external_sd/" followed by filename.zip)
and then it says "Updating partition details... Failed to mount '/cache' (Invalid arguement)
...done"
I do not understand what seems to be the problem....I thought the issue might be with me trying to flash it via the memory card so I tried using the "adb sideload" method which yielded the same results. I have no idea what is to be done now
Click to expand...
Click to collapse
Do factory reset in twrp
Do it twice
Then flash ROM as usual
Sent from my AO5510 using Tapatalk
Rajendran Rasa said:
Do factory reset in twrp
Do it twice
Then flash ROM as usual
Sent from my AO5510 using Tapatalk
Click to expand...
Click to collapse
Thank you very much!!!!! That did it! You da man ) just one last query, I'm about to flash gapps(which was the root of all the problems) and I've downloaded the gapps 64 bit cos yu yureka is ARM with 64 bit cpu architecture right?
Edit: I went ahead and tried flashing it with the 64 bit one and after getting the regular twrp messages I got one as "Insufficient storage space available in system partition. You may want to use a smaller open GApps package or consider removing some apps using gapps-config. See:'/sdcard/open_gapps_log.txt' for complete information"
But right now I did a factory reset(ty again) and there's absolutely nothing in my internal storage. The last passage on twrp looks like this ;
"Error Code: 70
-Unmounting /persist /system
Updater process ended with ERROR: 70
Error installing zip file '/sdcard/open_gapps-arm64-8.1-stock-20180705.zip' "
brickedmyphone1 said:
cos yu yureka is ARM with 64 bit cpu architecture right?
Click to expand...
Click to collapse
Right.:good:
~bump~
Edited the last post with new problems ._.
brickedmyphone1 said:
~bump~
Edited the last post with new problems ._.
Click to expand...
Click to collapse
Internal storage and /system partition are different things.
Either download the Pico Gapps package or increase the /system partition size.
saurav007 said:
Internal storage and /system partition are different things.
Either download the Pico Gapps package or increase the /system partition size.
Click to expand...
Click to collapse
Thank you again!
But pray tell, how do I increase my /system partition size?
brickedmyphone1 said:
Thank you again!
But pray tell, how do I increase my /system partition size?
Click to expand...
Click to collapse
Make sure to read everything and only follow it once you understand everything or you always have a risk of bricking your device. You can also opt for Pico Gapps package if you want where you probably won't have to increase any partition size.
http://forums.yuplaygod.com/threads/39966/
saurav007 said:
Internal storage and /system partition are different things.
Either download the Pico Gapps package or increase the /system partition size.
Click to expand...
Click to collapse
saurav007 said:
Make sure to read everything and only follow it once you understand everything or you always have a risk of bricking your device. You can also opt for Pico Gapps package if you want where you probably won't have to increase any partition size.
http://forums.yuplaygod.com/threads/39966/
Click to expand...
Click to collapse
Thank you once again, I will try the same and revert back.

[HELP OXYGEN OS] Can´t install 5.1.5 update or flash in original recovery!!

Hello, I have an OP 5 with unlocked bootloader and i was rooted. So, I'm in 4.5.13, and i'm trying to install 5.1.5 but i need to be unrooted for this.
Somehow when i removed root (magisk) my phone entered in bootloop mode (i think that magisk lost the original boot img). I flashed the stock boot img and the phone booted normally and without root. However i think that some "crumbs" of the magisk or adway stayed in my system or phone partitions and my phone continues to say that he can´t install the OTA. I've already wiped cache and data in the recovery and tried to install with adb sideload but it fails.
I still have my OOS and is working fine, but I can't update... Any ideas?
Do you think that if I do the normal settings > restore factory settings will it work? Or that option will be also damaged?
Should i boot TWRP in fastboot, and try to do a factory reset and then flash 5.1.5?
For your information, i've never flashed anything besides magisk and the attempts to update. The rom is the original as also the recovery. To flash the magisk i always booted twrp connected by usb to my PC.
I apreciate all the help!!
pdalvares said:
I apreciate all the help!!
Click to expand...
Click to collapse
https://downloads.oneplus.com/oneplus-5/oneplus_5_oxygenos_5.1.5/
This is the full OOS ROM Zip with instructions to flash with either stock Recovery, or TWRP.
Dirk said:
This is the full OOS ROM Zip with instructions to flash with either stock Recovery, or TWRP.
Click to expand...
Click to collapse
Yo, i already tried it different ways, but thank you :/
pdalvares said:
Yo, i already tried it different ways, but thank you :/
Click to expand...
Click to collapse
Fastboot flash TWRP, format partitions and flash full OOS ROM and Magisk. What's the difficulty?
https://www.xda-developers.com/how-to-install-twrp/
Dirk said:
Fastboot flash TWRP, format partitions and flash full OOS ROM and Magisk. What's the difficulty?
https://www.xda-developers.com/how-to-install-twrp/
Click to expand...
Click to collapse
Ok i'm gonna try it i'm sorry for my noobish but you know the smartphone was expensive and i'm afraid to brick it someway :/
Just one question: when you say formating partitions you mean wipe data, cache, system and dalvik / ART cache right?
thanks alot for your help and im sorry for being noob xD
I've my nexus 7 with root and PureNexus rom and had an moto g with custom rom, twrp and root but somehow I'm afraid with the OP5 because it was very expensive to my pocket xD :silly:
pdalvares said:
Ok i'm gonna try it i'm sorry for my noobish but you know the smartphone was expensive and i'm afraid to brick it someway :/
Just one question: when you say formating partitions you mean wipe data, cache, system and dalvik / ART cache right?
thanks alot for your help and im sorry for being noob xD
I've my nexus 7 with root and PureNexus rom and had an moto g with custom rom, twrp and root but somehow I'm afraid with the OP5 because it was very expensive to my pocket xD :silly:
Click to expand...
Click to collapse
Even if you tried really hard it would be almost impossible to 'Brick' a Oneplus phone. We even have unbrick tools to revive dead devices. Oneplus phones are like zombies. Really hard to keep down. The price we usually pay for messing up is nothing more than having to do a clean install and having to set the phone up again. We've all been there!
Once you have TWRP installed you could try a simple swipe-to-wipe from the 'Wipe' menu in TWRP and then flash the full OOS ROM & Magisk. I would recommend going into the 'Advanced' sub menu from 'Wipe' and select every partition. This will erase your Internal Storage, so make sure you have a backup of everything on your PC. Once you've done this you should use the TWRP 'Reboot' menu to reboot back into Recovery. Copy the ROM and Magisk zips back to Internal Storage from PC and Install them from TWRP 'Install' menu.
Dirk said:
Even if you tried really hard it would be almost impossible to 'Brick' a Oneplus phone. We even have unbrick tools to revive dead devices. Oneplus phones are like zombies. Really hard to keep down. The price we usually pay for messing up is nothing more than having to do a clean install and having to set the phone up again. We've all been there!
Once you have TWRP installed you could try a simple swipe-to-wipe from the 'Wipe' menu in TWRP and then flash the full OOS ROM & Magisk. I would recommend going into the 'Advanced' sub menu from 'Wipe' and select every partition. This will erase your Internal Storage, so make sure you have a backup of everything on your PC. Once you've done this you should use the TWRP 'Reboot' menu to reboot back into Recovery. Copy the ROM and Magisk zips back to Internal Storage from PC and Install them from TWRP 'Install' menu.
Click to expand...
Click to collapse
I've made what you said but it gives me the error "Updater process ended with error: 7"
pdalvares said:
I've made what you said but it gives me the error "Updater process ended with error: 7"
Click to expand...
Click to collapse
Which TWRP are you using? It should be the latest Official version, or you could try the latest codeworkx from here:
https://sourceforge.net/projects/cheeseburgerdumplings/files/15.1/cheeseburger/recovery/
Error 7 is a generic error code. The useful information about the error is usually in the body of text.
If you can't get TWRP to play nicely you can use it to format partitions as mentioned before, and then use it to install the stock OOS recovery from the bottom of this page:
https://downloads.oneplus.com/oneplus-5/oneplus_5_oxygenos_5.1.5/
The stock recovery is an .img, so in the TWRP 'Install' menu you need to select Image instead of Zip at the bottom of the screen. Move the stock recovery .img to Internal Storage and flash it. Reboot into Stock Recovery and flash full OOS zip.
Dirk said:
Even if you tried really hard it would be almost impossible to 'Brick' a Oneplus phone. We even have unbrick tools to revive dead devices. Oneplus phones are like zombies. Really hard to keep down. The price we usually pay for messing up is nothing more than having to do a clean install and having to set the phone up again. We've all been there!
Once you have TWRP installed you could try a simple swipe-to-wipe from the 'Wipe' menu in TWRP and then flash the full OOS ROM & Magisk. I would recommend going into the 'Advanced' sub menu from 'Wipe' and select every partition. This will erase your Internal Storage, so make sure you have a backup of everything on your PC. Once you've done this you should use the TWRP 'Reboot' menu to reboot back into Recovery. Copy the ROM and Magisk zips back to Internal Storage from PC and Install them from TWRP 'Install' menu.
Click to expand...
Click to collapse
YO BRO i've made it. I installed other version of the OS and it's working! Now im gonna see if i can update it to the newest version
Thank you for encouraging me!
pdalvares said:
YO BRO i've made it. I installed other version of the OS and it's working! Now im gonna see if i can update it to the newest version
Thank you for encouraging me!
Click to expand...
Click to collapse
Let me know how you get on. :good:
Dirk said:
Let me know how you get on. :good:
Click to expand...
Click to collapse
It all works fine but when doing the OTA in the OOS to 5.1.4 the device reboots, enters in oxygenos recovery but it fails...
EDIT:
Could it be because the bootloader is unlocked?? Is it safe to lock it like i unlocked it? No problem?
pdalvares said:
It all works fine but when doing the OTA in the OOS to 5.1.4 the device reboots, enters in oxygenos recovery but it fails...
Click to expand...
Click to collapse
Work through the steps in post #8. Begin with the latest codeworkx TWRP and go from there.
Check this guide if you think you might be missing something:
https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-unlock-bootloader-flash-twrp-t3624877
Dirk said:
Work through the steps in post #8. Begin with the latest codeworkx TWRP and go from there.
Check this guide if you think you might be missing something:
https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-unlock-bootloader-flash-twrp-t3624877
Click to expand...
Click to collapse
It failed that way
ok so im gonna write here what it says:
" Installing zip file...
Checking for Digest file...
Skipping Digest check: no Digest file found vendor partition is not existed, exit ota!!
Updater process ended with ERROR: 7
error installiong...
Updating partition details...
Failed to mount '/vendor' (Invalid argument)
...done "
pdalvares said:
It failed that way
ok so im gonna write here what it says:
" Installing zip file...
Checking for Digest file...
Skipping Digest check: no Digest file found vendor partition is not existed, exit ota!!
Updater process ended with ERROR: 7
error installiong...
Updating partition details...
Failed to mount '/vendor' (Invalid argument)
...done "
Click to expand...
Click to collapse
Are you trying to OTA or full ROM? OTA is not going to work. Only full ROM .zip will get the job done.
Have you considered giving up on OOS for now and just try flashing a Custom ROM from TWRP? I'd recommend Dirty Unicorns Oreo for now until Pie ROMs mature. You can get their ROM from their website.. Should be no issue at all flashing it. Opengapps ARM64, 8.1 Nano is the Gapps i'd recommend.
Wipe in TWRP, Flash Firmware/ROM/Gapps/Magisk. Job done.
pdalvares said:
It failed that way
ok so im gonna write here what it says:
" Installing zip file...
Checking for Digest file...
Skipping Digest check: no Digest file found vendor partition is not existed, exit ota!!
Updater process ended with ERROR: 7
error installiong...
Updating partition details...
Failed to mount '/vendor' (Invalid argument)
...done "
Click to expand...
Click to collapse
One more thing dude, i've flashed the 5.1.1 on top of the 4.5.14 without wiping, and it is taking along time to boot. I should wipe it? :/
pdalvares said:
One more thing dude, i've flashed the 5.1.1 on top of the 4.5.14 without wiping, and it is taking along time to boot. I should wipe it? :/
Click to expand...
Click to collapse
Initial boot can take some time.
I'm at a loss why your phone hates OOS, but it might love Custom ROMs. Give it some thought.
pdalvares said:
One more thing dude, i've flashed the 5.1.1 on top of the 4.5.14 without wiping, and it is taking along time to boot. I should wipe it? :/
Click to expand...
Click to collapse
MY BROTHER, i really needed to lock the bootloader, wiped everything and adb sideloaded 5.1.1. It booted at android 8 and then i ran the OTA's until the newest one and now i have my phone fully functional, with the latest update, and running all stock. Thank's alot for all the help. I don´t know how to thank you! Peace and see you one day!
EDIT:
Maybe one day I will try some custom ROM, like lineage or other best than that. For now im gonna stay like this for a while, just because yes
pdalvares said:
MY BROTHER, i really needed to lock the bootloader, wiped everything and adb sideloaded 5.1.1. It booted at android 8 and then i ran the OTA's until the newest one and now i have my phone fully functional, with the latest update, and running all stock. Thank's alot for all the help. I don´t know how to thank you! Peace and see you one day!
EDIT:
Maybe one day I will try some custom ROM, like lineage or other best than that. For now im gonna stay like this for a while, just because yes
Click to expand...
Click to collapse
Good news! :good:
You can see how resilient OP phones are. You can pretty much always get them back to a working condition. I can only guess but it sounds like you were right. Something was wrong with your Bootloader after the initial problems. Glad you got it sorted.

Categories

Resources