Related
1) Used the toolKit to unlock Bootloader
2) install twrp using Toolkit
3) transfered AOKP rom to device using airdroid
4) Went to TWRP, System Wipe 3 times, Clear cache 3 times
5) attempt to flash AOKP ZIP
6) ZIP failed to install no idea why
7) Tried to restart and now stuck at the GOOGLE logo
Please help is there anything i can do?
Hmm could i use the toolkit to flash an img file? Im dling a stock img atm.
First off.. Don't panic ... It wasn't your fault it failed ... I know because it happened to me . don't get it from "downloads" or goomanager .. Get it from the second post I. That thread on the latest date
Second . I don't think otg works in twrp so you will have to use adb to load the ROM
Sent from my Nexus 4 using Tapatalk 2
italia0101 said:
First off.. Don't panic ... It wasn't your fault it failed ... I know because it happened to me . don't get it from "downloads" or goomanager .. Get it from the second post I. That thread on the latest date
Second . I don't think otg works in twrp so you will have to use adb to load the ROM
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I did get it from the second post though, and how can i load into ADB?
italia0101 said:
Second . I don't think otg works in twrp so you will have to use adb to load the ROM
Click to expand...
Click to collapse
OTG does work in TWRP. I have found that it doesn't like some flash drives - no idea why. I've tried quite a few, some of mine work all the time, other just won't work.
adoute said:
OTG does work in TWRP. I have found that it doesn't like some flash drives - no idea why. I've tried quite a few, some of mine work all the time, other just won't work.
Click to expand...
Click to collapse
Ok went to twrp and used the ADB sideload feature but it said OTG cable fail to mount.
FIXED
WOOO FIXED IT NVM! Mod please delete thanks for help guys
Someone with more experience correct me if I'm wrong, but shouldn't we be avoiding wiping system in TWRP prior to flashing ROMs? I believe I read a thread (probably on RootzWiki) that said wiping system messes things up as you lose the ability to flash a ROM in the "traditional" manner. I wipe cache, dalvik, then click factory reset. I leave system alone and I've never had a problem with flashing ROMs.
Hi.
I've searched through a LOT of posts, but only found slightly related (and for me unhelpful) comments.
I have a GT-i9505 (i9505xxuame2), and rooted/flashed it using Odin / modified_cf_root. However, although I have succsessfully installed TWRP - AND have (seemingly) been able to make a full backup to my external sdcard, I am completely unable to install CM 10.1 nightly / AOKP (both i9505 versions).
Whenever i try this (via recovery of course), it always fails, reporting it was unable to mount /system. When restarting the phone, it just 'hangs' on the splash screen. The only solution then is to restore my backup, which works fine... HOWEVER, I suspect that since it has problems with the /system folder, It might not actually have backed this up, and that restore only works because /system happens to be untouced by my attempts to flash it.
Trying various tips & tricks found here on XDA - like manually mounting /system in TWRP, reflashing in Odin etc. has not helped me. I also noticed that when entering download-mode, it states that write protection is enabled (as in this thread - which unfortunatly also did not solve my problem: http://forum.xda-developers.com/showthread.php?t=2267107). I also tried CWM, but using this I'm unable to manually mount both /system, /sdcard AND extSdcard (or whatever extrenal memory was called... don't remember.. ) - and it of course has the same problems trying to flash either ROM.
My feeling is that my unit is not (fully) rooted, but like I said, I've been unable to find a solution. I really hope you can help, because I'd love to have CM on this delightful piece of hardware.
Schildkamp said:
Hi.
I've searched through a LOT of posts, but only found slightly related (and for me unhelpful) comments.
I have a GT-i9505 (i9505xxuame2), and rooted/flashed it using Odin / modified_cf_root. However, although I have succsessfully installed TWRP - AND have (seemingly) been able to make a full backup to my external sdcard, I am completely unable to install CM 10.1 nightly / AOKP (both i9505 versions).
Whenever i try this (via recovery of course), it always fails, reporting it was unable to mount /system. When restarting the phone, it just 'hangs' on the splash screen. The only solution then is to restore my backup, which works fine... HOWEVER, I suspect that since it has problems with the /system folder, It might not actually have backed this up, and that restore only works because /system happens to be untouced by my attempts to flash it.
Trying various tips & tricks found here on XDA - like manually mounting /system in TWRP, reflashing in Odin etc. has not helped me. I also noticed that when entering download-mode, it states that write protection is enabled (as in this thread - which unfortunatly also did not solve my problem: http://forum.xda-developers.com/showthread.php?t=2267107). I also tried CWM, but using this I'm unable to manually mount both /system, /sdcard AND extSdcard (or whatever extrenal memory was called... don't remember.. ) - and it of course has the same problems trying to flash either ROM.
My feeling is that my unit is not (fully) rooted, but like I said, I've been unable to find a solution. I really hope you can help, because I'd love to have CM on this delightful piece of hardware.
Click to expand...
Click to collapse
OMG! same issue here.. exactly, please HELP someone!!!
Format /system in recovery and then try flashing cm. It shouldn't be an issue mounting system if the partition is formated.
live-evil said:
Format /system in recovery and then try flashing cm. It shouldn't be an issue mounting system if the partition is formated.
Click to expand...
Click to collapse
Please elaborate for me,
Wipe does a format of the partition, is that enough or do I need to actually to use Format in the menu, as in kill the whole internal storage?
thanks
Linus
wipe is enough
live-evil said:
wipe is enough
Click to expand...
Click to collapse
thanks for the answer,
I hoped for that and also tried it.
No fun
I think I'll have to go for full format.
Just hope that does nothing bad >.<
Or is CWM maybe a better alternative?
DemonWareXT said:
thanks for the answer,
I hoped for that and also tried it.
No fun
I think I'll have to go for full format.
Just hope that does nothing bad >.<
Or is CWM maybe a better alternative?
Click to expand...
Click to collapse
what error message did you get?
I had the same problem yesterday in twrp 2.5.0.1 I just formated system and preload and factory resteted and then just rebooted and formated system again and it worked.
Grusburk said:
I had the same problem yesterday in twrp 2.5.0.1 I just formated system and preload and factory resteted and then just rebooted and formated system again and it worked.
Click to expand...
Click to collapse
Hehe I well tried that one,
no luck
interesting since 2.5.0.2 it says, unable to mount /system, and then promptly crashes
oh and the same happened in CWM
Hell XD
could I flash AOKP via odin maybe?
not like I like the idea >.<
It generally takes a few goes for the recovery to flash the rom in s4. Until someone works out what causes that bug in the recoviers you kind of just have to reboot and try again and again if necessary until it sticks.
live-evil said:
It generally takes a few goes for the recovery to flash the rom in s4. Until someone works out what causes that bug in the recoviers you kind of just have to reboot and try again and again if necessary until it sticks.
Click to expand...
Click to collapse
Aright, I think I found the way for me
Boot into recovery --> wipe system --> mount system --> if ok --> flash
if not ok --> retry the whole process
Strange stuff, but yay thanks all for your help
Schildkamp said:
Hi.
I've searched through a LOT of posts, but only found slightly related (and for me unhelpful) comments.
I have a GT-i9505 (i9505xxuame2), and rooted/flashed it using Odin / modified_cf_root. However, although I have succsessfully installed TWRP - AND have (seemingly) been able to make a full backup to my external sdcard, I am completely unable to install CM 10.1 nightly / AOKP (both i9505 versions).
Whenever i try this (via recovery of course), it always fails, reporting it was unable to mount /system. When restarting the phone, it just 'hangs' on the splash screen. The only solution then is to restore my backup, which works fine... HOWEVER, I suspect that since it has problems with the /system folder, It might not actually have backed this up, and that restore only works because /system happens to be untouced by my attempts to flash it.
Trying various tips & tricks found here on XDA - like manually mounting /system in TWRP, reflashing in Odin etc. has not helped me. I also noticed that when entering download-mode, it states that write protection is enabled (as in this thread - which unfortunatly also did not solve my problem: http://forum.xda-developers.com/showthread.php?t=2267107). I also tried CWM, but using this I'm unable to manually mount both /system, /sdcard AND extSdcard (or whatever extrenal memory was called... don't remember.. ) - and it of course has the same problems trying to flash either ROM.
My feeling is that my unit is not (fully) rooted, but like I said, I've been unable to find a solution. I really hope you can help, because I'd love to have CM on this delightful piece of hardware.
Click to expand...
Click to collapse
Crap. Have same problem.
I had this problem after flashing MH8 firmware (new bootloader) with Odin.
No matter what I tried in recovery I kept getting an error saying that it failed to mount system.
I had an older version of PhilZ on my ext SD luckily, so I flashed this, rebooted recovery then I could format system and it was mounted again.
then just flashed my newer recovery back and all was good
Hi guys,
it appears I'm having similar issues to you both but after 5 hours of constantly trying to fix this I'm still stuck! I've opened a new thread and I was wondering if you might be kind enough to help me out on there please?
Here's a link to the thread - would really appreciate any help you could provide... http://forum.xda-developers.com/showthread.php?p=46082532
Obagleyfreer said:
I had this problem after flashing MH8 firmware (new bootloader) with Odin.
No matter what I tried in recovery I kept getting an error saying that it failed to mount system.
I had an older version of PhilZ on my ext SD luckily, so I flashed this, rebooted recovery then I could format system and it was mounted again.
then just flashed my newer recovery back and all was good
Click to expand...
Click to collapse
DemonWareXT said:
Aright, I think I found the way for me
Boot into recovery --> wipe system --> mount system --> if ok --> flash
if not ok --> retry the whole process
Strange stuff, but yay thanks all for your help
Click to expand...
Click to collapse
Sh*t! Sorry:laugh: It really works! At least on my LG G2 D802. Thx, man!
---------- Post added at 01:46 PM ---------- Previous post was at 01:12 PM ----------
DemonWareXT said:
Aright, I think I found the way for me
Boot into recovery --> wipe system --> mount system --> if ok --> flash
if not ok --> retry the whole process
Strange stuff, but yay thanks all for your help
Click to expand...
Click to collapse
Sh*t! Sorry:laugh: It really works! At least on my LG G2 D802. Thx, man!
Everytime no matter what ROM I flash on this tablet I just get a bootloop and then I can't do anything in recovery like mounting SD card for instance.
I'm not completely new to this game, I have a nexus 5 that I'm always playing with and never had problems like this with the s3 or HTC one x. Could I be over looking something? Any help or guidance is much appreciated.
Cheers
Anyone?
I have a similar problem. I flashed ParanoidAndroid yesterday and everything seemed okay but now everything I try to launch or install an app the tablet reboots, and I tried to flash cyanogen, flash stock, do all the wipes and factory resets but always reboots to the damaged Paranoid Android ROM.
Reformat /system /cache /data
Then use a otg cable with a USB drive with the ROM you want
Mount in recovery then flash
USBhost said:
Reformat /system /cache /data
Then use a otg cable with a USB drive with the ROM you want
Mount in recovery then flash
Click to expand...
Click to collapse
In my case, reformat, wipe or erase from adb does absolutely nothing, so I don't know how properly erase all the content of the internal storage.
Amd64bits said:
In my case, reformat, wipe or erase from adb does absolutely nothing, so I don't know how properly erase all the content of the internal storage.
Click to expand...
Click to collapse
Tempary boot a recovery
You can do this in the bootloader
Using http://forum.xda-developers.com/showthread.php?t=1766475
USBhost said:
Tempary boot a recovery
You can do this in the bootloader
Using http://forum.xda-developers.com/showthread.php?t=1766475
Click to expand...
Click to collapse
Yeah, I tried that also with CMW, but... didn't work...
Amd64bits said:
Yeah, I tried that also with CMW, but... didn't work...
Click to expand...
Click to collapse
Do it with twrp
USBhost said:
Do it with twrp
Click to expand...
Click to collapse
It is my default recovery but also did it, aaaand, no thing happened . I'm thinking of throwing it apart.
Amd64bits said:
It is my default recovery but also did it, aaaand, no thing happened . I'm thinking of throwing it apart.
Click to expand...
Click to collapse
Did booting a temporary recovery ever work or its your first time trying it
USBhost said:
Did booting a temporary recovery ever work or its your first time trying it
Click to expand...
Click to collapse
I have flashed many times before, always using the installed TWRP, with any problems, and I have booted temporary recoverys before with any issue. The recovery runs without problems, but when the device reboots, all remains the same.
Amd64bits said:
I have flashed many times before, always using the installed TWRP, with any problems, and I have booted temporary recoverys before with any issue. The recovery runs without problems, but when the device reboots, all remains the same.
Click to expand...
Click to collapse
Then try to flash a factory image
And see what happens
USBhost said:
Then try to flash a factory image
And see what happens
Click to expand...
Click to collapse
Nothing...
Amd64bits said:
Nothing...
Click to expand...
Click to collapse
Did the factory image flash good with no errors
USBhost said:
Did the factory image flash good with no errors
Click to expand...
Click to collapse
Yes, with the Succesfull text and all but when I reboot the ****ing Paranoid Android stills appears. I also tried with Adb Sideload, but failed because an error in the footer, although I downloaded it from google one time and from Wug Toolkit another; also the wipe from the stock recovery loaded by Wug Toolkit didn't work.
Amd64bits said:
Yes, with the Succesfull text and all but when I reboot the ****ing Paranoid Android stills appears. I also tried with Adb Sideload, but failed because an error in the footer, although I downloaded it from google one time and from Wug Toolkit another; also the wipe from the stock recovery loaded by Wug Toolkit didn't work.
Click to expand...
Click to collapse
Then I don't know what to do to help you with it
I'm sorry
But that is so interesting and unique
Even I copies the stock image to the SD, but when the Rom boots, it has been disappeared. So annoying.
Sent from my RM-821_eu_spain_435 using Tapatalk
USBhost said:
Then I don't know what to do to help you with it
I'm sorry
But that is so interesting and unique
Click to expand...
Click to collapse
Oh, well.. Thank you, anyways.
Hey, I'm having the exact (more or less) same issue: http://forum.xda-developers.com/showthread.php?t=2783720
I've been using Cyanogenmod, but other than that, I have the same thing going on.
I was actually glad to see this, as it means I'm not alone in this issue!
But still rather strange, and VERY frustrating.
Q&A for [ROM][LOLLIPOP][5.0][LRX21T][UNTOUCHED PURE STOCK][Nexus⁴]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][LOLLIPOP][5.0][LRX21T][UNTOUCHED PURE STOCK][Nexus⁴]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
So i kinda figured it out.
well, I sort of did something(i think) and its now working fine... I went to twrp.. did a factory reset. Then went for advance wipe and wiped system cache and dalvik. Then followed the same procedure. Bootloader-->radio-->Rom-->Kernel. It worked just fine. The first boot took some 15 minutes.
does the internal storage work for you? it works only on twrp for me :/
i can't see anything in file explorer and canìt restore from twrp :/ that's a big problem guys.
If you can not see your old nandroid backups
After rooting If you can not see your old nandroid backups
Via file explorers try to enable usb debuging from
dev. opt. if not worked (Recovires or SuperSU issue)
But you can see and restore your old or new backups via recovery (TWRP tested)
New recoveries and superSU may fix this issues.
Want to ask? SuperSU XDA Thread here
Note: SE Linux Mod Changer may help to fix this issue
Recommended Recovery is TWRP 2.8.1.0
HunterAtXDA said:
I also got this message
Code:
unmount of /system failed: no such volume
followed by
Code:
unmount of /data failed: no such volume
a few minutes later. The process finished a few minutes later without any more output but I'm booting now after wiping the cache and everything seems fine.
Click to expand...
Click to collapse
I had the this same problem. After installing everything, I let it sit for 20 minutes and it finally showed the Android logo. After that it was stuck on a black screen. I wiped everything and repeated the install procedure again, minus the kernal, and got the same "unmount of /system failed: no such volume" while flashing the rom zip. It booted after a while and everything works except my storage is FUKT. I cant see any of my pictures, music, etc, and the only thing I see via PC is the DCIM folder which is empty. Not cool
mattgrantlackey said:
I had the this same problem. After installing everything, I let it sit for 20 minutes and it finally showed the Android logo. After that it was stuck on a black screen. I wiped everything and repeated the install procedure again, minus the kernal, and got the same "unmount of /system failed: no such volume" while flashing the rom zip. It booted after a while and everything works except my storage is FUKT. I cant see any of my pictures, music, etc, and the only thing I see via PC is the DCIM folder which is empty. Not cool
Click to expand...
Click to collapse
Recommended Recovery is TWRP 2.8.1.0
mattgrantlackey said:
I had the this same problem. After installing everything, I let it sit for 20 minutes and it finally showed the Android logo. After that it was stuck on a black screen. I wiped everything and repeated the install procedure again, minus the kernal, and got the same "unmount of /system failed: no such volume" while flashing the rom zip. It booted after a while and everything works except my storage is FUKT. I cant see any of my pictures, music, etc, and the only thing I see via PC is the DCIM folder which is empty. Not cool
Click to expand...
Click to collapse
Nothing wrong with my storage. I installed the bootloader, radio, and rom on top of my existing 4.4.4 rom by sideloading in CWM. Wiped caches and rebooted to make sure everything was working, then back to CWM to sideload the kernel. I haven't rooted yet.
HunterAtXDA said:
Nothing wrong with my storage. I installed the bootloader, radio, and rom on top of my existing 4.4.4 rom by sideloading in CWM. Wiped caches and rebooted to make sure everything was working, then back to CWM to sideload the kernel. I haven't rooted yet.
Click to expand...
Click to collapse
Did you have the "unmount of /system failed: no such volume" while flashing the rom zip?
mattgrantlackey said:
Did you have the "unmount of /system failed: no such volume" while flashing the rom zip?
Click to expand...
Click to collapse
Yes, and a similar error about /data
JaMeVu said:
Recommended Recovery is TWRP 2.8.1.0
Click to expand...
Click to collapse
Same error after using ADB to flash v2.8.1.0 TWRP, full wipe, and reinstall of everything in the correct procedure. My storage is still not working.
mattgrantlackey said:
Same error after using ADB to flash v2.8.1.0 TWRP, full wipe, and reinstall of everything in the correct procedure. My storage is still not working.
Click to expand...
Click to collapse
try this
enable usb debuging via dev opt.
connect phone to pc
put files to your sd card then reboot to recovery then flash
JaMeVu said:
try this
enable usb debuging via dev opt.
connect phone to pc
put files to your sd card then reboot to recovery then flash
Click to expand...
Click to collapse
I always enable usb debugging, didn't help. And as far as the file transfer, it won't let me. I can only access it while in TWRP. All my files are there, its just android can't see them, and wont show under windows either. Not sure what the issue is there, I've tried everything I know of. I'll just flash CM12 that I was using before. Let me know if you figure out this problem, as I'm curious as to what is causing it (and I'm not the only one having it).
mattgrantlackey said:
Wont let me. I can only access it while in TWRP. All my files are there, its just android can't see them, and wont show under windows either. Not sure what the issue is there, I've tried everything I know of. I'll just flash CM12 that I was using before. Let me know if you figure out this problem, as I'm curious as to what is causing it (and I'm not the only one having it).
Click to expand...
Click to collapse
re plug usb cable take it of then plug
no we do not have this kind of problem here many phones we tested and flashed
JaMeVu said:
re plug usb cable take it of then plug
no we do not have this kind of problem here many phones we tested and flashed
Click to expand...
Click to collapse
Same problems as me:
spupuz said:
does the internal storage work for you? it works only on twrp for me :/
i can't see anything in file explorer and canìt restore from twrp :/ that's a big problem guys.
Click to expand...
Click to collapse
spupuz said:
big big problem can't see the internal storage partition at all.
Click to expand...
Click to collapse
mattgrantlackey said:
Same problems as me:
spupuz said:
big big problem can't see the internal storage partition at all.
Click to expand...
Click to collapse
try re flash everything but not autoroot using..
Click to expand...
Click to collapse
try re flash everything but not autoroot using..[/QUOTE]
All of this was without autoroot. Don't worry about it man, I just installed my old rom. For some reason this ROM doesn't like me and spupuz's phone. Thanks for trying to help me, I appreciate your time. Let me know if someone else has the issue and you figure it out, I'm very curious as to what it might be.
mattgrantlackey said:
try re flash everything but not autoroot using..
Click to expand...
Click to collapse
All of this was without autoroot. Don't worry about it man, I just installed my old rom. For some reason this ROM doesn't like me and spupuz's phone. Thanks for trying to help me, I appreciate your time. Let me know if someone else has the issue and you figure it out, I'm very curious as to what it might be.[/QUOTE]
ok but we test it many phones and 1500+ downloads
may be u are using multirom ? or multirom twrp ?
JaMeVu said:
ok but we test it many phones and 1500+ downloads
may be u are using multirom ? or multirom twrp ?
Click to expand...
Click to collapse
Nope, no multirom or multirom twrp. I have no idea.
After rooting If you can not see your old nandroid backups
Via file explorers try to enable usb debuging from
dev. opt. if not worked (Recovires or SuperSU issue)
But you can see and restore your old or new backups via recovery (TWRP tested)
New recoveries and superSU may fix this issues.
Want to ask? SuperSU XDA Thread here
Note: SE Linux Mod Changer may help to fix this issue
Recommended Recovery is TWRP 2.8.1.0
I flashed this ROM this morning, and I initially had the weird can't unmount /system error. I rewiped, using twrp to ensure that /system was wiped too. Install went fine. I have a weird glitch or something on my recent apps list, though. I attached a picture. Anyone know what this is? It doesn't seem to be causing any functional problem, but it looks bad.
Edit: I cleared the cache for google now launcher, and restarted recovery and wiped my cache partition and the error went away.
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.