Related
Hello,
so i backup my phone before i do anything risky. so i was trying to restore my phone (from yesterday backup) using twrp. everything went perfect and when my device rebooted after restore. it stuck on Google Logo. i tried 3 times but no luck. any help? i select Boot, Data, System, System.img
EDIT: should i select vendor / vendor.img ?? while restoring it ?
UPDATE: when i tried 4th time. my phone rebooted after about 72% and stuck on google logo.
Tried clearing cache? Also, what things did you precisely backup?
DJBhardwaj said:
Tried clearing cache? Also, what things did you precisely backup?
Click to expand...
Click to collapse
almost everything including vendor ; no cache
setul34 said:
almost everything including vendor ; no cache
Click to expand...
Click to collapse
I had the same issue when I backed up system image.
DJBhardwaj said:
I had the same issue when I backed up system image.
Click to expand...
Click to collapse
okay so any solution?
Try it without the system image.
DJBhardwaj said:
Try it without the system image.
Click to expand...
Click to collapse
i did but that did not install root / apps / settings. basically i just got data and stock rom.
setul34 said:
i did but that did not install root / apps / settings. basically i just got data and stock rom.
Click to expand...
Click to collapse
No idea, I myself haven't tried further.
Lets see if someone else comes up with something
setul34 said:
Hello,
so i backup my phone before i do anything risky. so i was trying to restore my phone (from yesterday backup) using twrp. everything went perfect and when my device rebooted after restore. it stuck on Google Logo. i tried 3 times but no luck. any help? i select Boot, Data, System, System.img
EDIT: should i select vendor / vendor.img ?? while restoring it ?
UPDATE: when i tried 4th time. my phone rebooted after about 72% and stuck on google logo.
Click to expand...
Click to collapse
Let me guess you are on TWRP 3.0.0.0?
Yes
oneandroidnut said:
Let me guess you are on TWRP 3.0.0.0?
Click to expand...
Click to collapse
@oneandroidnut Yes.
setul34 said:
@oneandroidnut Yes.
Click to expand...
Click to collapse
You don't backup system image, only backup system, data, and boot.
setul34 said:
@oneandroidnut Yes.
Click to expand...
Click to collapse
pm me if you are still having issues we can go to hangouts or something and i can walk you through
oneandroidnut said:
pm me if you are still having issues we can go to hangouts or something and i can walk you through
Click to expand...
Click to collapse
It'd be much better if you did this here, that way the solution is available for others to find, that's pretty much the entire point of the Q&A section. I'm confident it's just a case of selecting the wrong partitions to backup anyway.
Heisenberg said:
It'd be much better if you did this here, that way the solution is available for others to find, that's pretty much the entire point of the Q&A section. I'm confident it's just a case of selecting the wrong partitions to backup anyway.
Click to expand...
Click to collapse
The solution i used when i incorrectly updated vendor image and then tried to restore old system image and vendor image was to use Nexus Tool kit by wugs fresh to flash back to stock while keeping internal card intact. Then flash the rom you were on with correct vendor image in TWRP 3.0.0.0 and then restore your twrp backup without the vendor image etc and boom should be back to normal. At least that is what worked for me. What should you backup and restore? I back up everything and restore everything but vendor stuff. any suggestions?
oneandroidnut said:
The solution i used when i incorrectly updated vendor image and then tried to restore old system image and vendor image was to use Nexus Tool kit by wugs fresh to flash back to stock while keeping internal card intact. Then flash the rom you were on with correct vendor image in TWRP 3.0.0.0 and then restore your twrp backup without the vendor image etc and boom should be back to normal. At least that is what worked for me. What should you backup and restore? I back up everything and restore everything but vendor stuff. any suggestions?
Click to expand...
Click to collapse
That seems over-complicated. You only need to backup/restore system, data, and boot. Vendor is optional if you have Layers that you want to keep. Don't backup/restore system image or vendor image. That's the reason he got into this mess, be backed up and restored system image. I posted the solution a couple of posts back.
okay so i tried to recover Data System Boot, still didn't work. so i remove everything including twrp and installed stock rom. and then i installed twrp 3.0 and somehow it worked and my device is back on
oneandroidnut said:
The solution i used when i incorrectly updated vendor image and then tried to restore old system image and vendor image was to use Nexus Tool kit by wugs fresh to flash back to stock while keeping internal card intact. Then flash the rom you were on with correct vendor image in TWRP 3.0.0.0 and then restore your twrp backup without the vendor image etc and boom should be back to normal. At least that is what worked for me. What should you backup and restore? I back up everything and restore everything but vendor stuff. any suggestions?
Click to expand...
Click to collapse
this worked for me thankyou
Heisenberg said:
That seems over-complicated. You only need to backup/restore system, data, and boot. Vendor is optional if you have Layers that you want to keep. Don't backup/restore system image or vendor image. That's the reason he got into this mess, be backed up and restored system image. I posted the solution a couple of posts back.
Click to expand...
Click to collapse
i won't make that mistake again to backup vendor or system image.
Thanks @oneandroidnut @Heisenberg
setul34 said:
okay so i tried to recover Data System Boot, still didn't work. so i remove everything including twrp and installed stock rom. and then i installed twrp 3.0 and somehow it worked and my device is back on
this worked for me thankyou
i won't make that mistake again to backup vendor or system image.
Thanks @oneandroidnut @Heisenberg
Click to expand...
Click to collapse
No problem man glad it worked!!
I had the same problem.
I tried to restore a backup (MMB29Q - system+data+boot, done after installing the last factory image without root) and I got blocked on the Google logo. I tried twice without managing.
In the end I solved the problem installing supersu v2.68 zip before restarting.
It's as though the restore needs the root to work properly.
What do you think?
Thanks.
Hello everyone! I bring news from the TWRP developers from the #TWRP IRC channel! TWRP 3.0.2-1 has a fatal bug! If you backup and restore EFS it will brick you! Do not backup and restore EFS on 3.0.2-1! Use 3.0.2-0 instead! This has already been fixed in the newer builds!
If you have been bricked you NEED to Erase the EFS partitions and that will fix it immediately.
For the Nexus 6P go to TWRP. Then on PC Open Command Prompt with access to ADB ( Android Debug Bridge) and execute the following commands:
ADB shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst1 bs=16384
and
ADB Shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst2 bs=16384
This should fix it for ANY Nexus 6P users. Users on other phones with the same problem await instructions!
I accidentally deleted the data partition. Everything else works fine including Recovery/Fastboot. Normally I'd be using the Mega Unbrick Guide to restore the partition, but not an option right now for the 5 (128GB). Assistance would be appreciated. Maybe flashing a userdata.img would work?
I'd recommend you to completely wipe and flash Stock OOS from here : https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
That should sort all your problems related to partitioning. Let me know how it goes.
anmolkakkar said:
I'd recommend you to completely wipe and flash Stock OOS from here : https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
That should sort all your problems related to partitioning. Let me know how it goes.
Click to expand...
Click to collapse
Already tried flashing the Full ROM earlier, but that doesn't fix the missing partition. Unless flashing with Stock Recovery would make a difference. Need a link to stock recovery to try that
Was looking into dumping partitions off a working OP5.
https://forum.xda-developers.com/showthread.php?t=2450045
Don't have a second OP5 (128GB) to dump partitions, but I did generate some .img files using this method. Optimally, flashing a proper userdata.img through fastboot should fix the partition, I believe.
aenews said:
I accidentally deleted the data partition. Everything else works fine including Recovery/Fastboot. Normally I'd be using the Mega Unbrick Guide to restore the partition, but not an option right now for the 5 (128GB). Assistance would be appreciated. Maybe flashing a userdata.img would work?
Click to expand...
Click to collapse
fastboot format userdata ?
Hastaloego said:
fastboot format userdata ?
Click to expand...
Click to collapse
The partition doesn't exist right now. It cannot be mounted or formatted. If someone could use the guide above and pull a userdata.img from a 128GB OP5, pretty sure that would restore the partition if I flash it in fastboot.
aenews said:
The partition doesn't exist right now. It cannot be mounted or formatted. If someone could use the guide above and pull a userdata.img from a 128GB OP5, pretty sure that would restore the partition if I flash it in fastboot.
Click to expand...
Click to collapse
Have you tried going into TWRP > Wipe> advance wipe > data >change or repair filesystem > change filesystem> ext4?
This should help.
You can also try restore the nandroid uploaded on my thread
Sent from Funk Tuned 3T
flame360 said:
Have you tried going into TWRP > Wipe> advance wipe > data >change or repair filesystem > change filesystem> ext4?
This should help.
Click to expand...
Click to collapse
Thanks that worked! And much simpler and faster. I didn't realize there was an easy way to repair the filesystem in TWRP (derp) but that's awesome.
Funk Wizard said:
You can also try restore the nandroid uploaded on my thread
Sent from Funk Tuned 3T
Click to expand...
Click to collapse
Thanks for the tip!
Also I *think* I was able to extract a userdata.img after I fixed the partition. In case that's ever needed in the future...
aenews said:
Thanks that worked! And much simpler and faster. I didn't realize there was an easy way to repair the filesystem in TWRP (derp) but that's awesome.
Thanks for the tip!
Also I *think* I was able to extract a userdata.img after I fixed the partition. In case that's ever needed in the future...
Click to expand...
Click to collapse
Welcome buddy
Funk Wizard said:
Welcome buddy
Click to expand...
Click to collapse
So I managed to do the same thing, but with my system partition. I can't figure out what img to flash to system or where to get it from. Can anyone help me please?
Also, first thing I did was attempt to repair the partition via TWRP but no dice on that...
electronicghandi said:
So I managed to do the same thing, but with my system partition. I can't figure out what img to flash to system or where to get it from. Can anyone help me please?
Also, first thing I did was attempt to repair the partition via TWRP but no dice on that...
Click to expand...
Click to collapse
try flashing the stock zip from twrp.
electronicghandi said:
So I managed to do the same thing, but with my system partition. I can't figure out what img to flash to system or where to get it from. Can anyone help me please?
Also, first thing I did was attempt to repair the partition via TWRP but no dice on that...
Click to expand...
Click to collapse
Restore the Nandroid
Sent from my OnePlus5 using XDA Labs
Worked for me to on a OnePlus 3
flame360 said:
Have you tried going into TWRP > Wipe> advance wipe > data >change or repair filesystem > change filesystem> ext4?
This should help.
Click to expand...
Click to collapse
That did it on my girlfriends OnePlus3 thank you very much!
aenews said:
Thanks that worked! And much simpler and faster. I didn't realize there was an easy way to repair the filesystem in TWRP (derp) but that's awesome.
Thanks for the tip!
Also I *think* I was able to extract a userdata.img after I fixed the partition. In case that's ever needed in the future...
Click to expand...
Click to collapse
Can you please share the userdata.img for 128gb and also fastboot image files for one plus 5t, my phone is dead please help
Hello Guys Recently i decided to update my OP5 which was on rooted nougat for a year and some how after countless wipes, bootloops, rom flashes and data mounting errors in twrp, was able to flash OOS 5.0 instead of the OOS 5.1.4 , coz flashing 5.1.4 directly from OOS 4.1.5 ,resulted in "error 7" everytime
Device status is unlocked boot loader, decrypted and rooted with magisk. But after this when i check with TWRP(3.2.3) ,i found that its unable to mount data partion again and cannot flash upadte on it or do anything else in twrp, tried to mount the data partion but that resulted in loosing OS again and had to repeat the whole process to Install OOS 5.0 .
Any Idea how i can update my phone further to 5.1.4 or beyond that?
Akarsh Adithya.K said:
Hello Guys Recently i decided to update my OP5 which was on rooted nougat for a year and some how after countless wipes, bootloops, rom flashes and data mounting errors in twrp, was able to flash OOS 5.0 instead of the OOS 5.1.4 , coz flashing 5.1.4 directly from OOS 4.1.5 ,resulted in "error 7" everytime
Device status is unlocked boot loader, decrypted and rooted with magisk. But after this when i check with TWRP(3.2.3) ,i found that its unable to mount data partion again and cannot flash upadte on it or do anything else in twrp, tried to mount the data partion but that resulted in loosing OS again and had to repeat the whole process to Install OOS 5.0 .
Any Idea how i can update my phone further to 5.1.4 or beyond that?
Click to expand...
Click to collapse
Hello, do you read this similar thread already https://forum.xda-developers.com/oneplus-5/help/oneplus5-ota-update-4-1-15-to-5-0-1-5-1-t3859695 ?
strongst said:
Hello, do you read this similar thread already https://forum.xda-developers.com/oneplus-5/help/oneplus5-ota-update-4-1-15-to-5-0-1-5-1-t3859695 ?
Click to expand...
Click to collapse
Yeah, i checked the thread, but mine is a bit different, coz mine is rooted and has TWRP recovery, and it took me many bootloops and flashs to figure out ,that i have to flash every single version of OOS, for example 4.1 to 5.0 and then, 5.0 to 5.0.4 and then 5.0.4 to 5.1 and on.
You get the point. But now i cant update after 5.0 , as TWRP throws this "unable to mount storage" error and my internal storage doesnt even show up in install section
Akarsh Adithya.K said:
Yeah, i checked the thread, but mine is a bit different, coz mine is rooted and has TWRP recovery, and it took me many bootloops and flashs to figure out ,that i have to flash every single version of OOS, for example 4.1 to 5.0 and then, 5.0 to 5.0.4 and then 5.0.4 to 5.1 and on.
You get the point. But now i cant update after 5.0 , as TWRP throws this "unable to mount storage" error and my internal storage doesnt even show up in install section
Click to expand...
Click to collapse
What twrp(link) do you have?
Did you format internal storage or not?
Don't bother with root until you have undated your os. Updating with twrp is also possible and I did it a lot of times.
strongst said:
What twrp(link) do you have?
Did you format internal storage or not?
Don't bother with root until you have undated your os. Updating with twrp is also possible and I did it a lot of times.
Click to expand...
Click to collapse
Its twrp 3.2.3 and yeah before installing rom , i did a full wipe of dalvik, data, system, internal storage and then did a data format too
Akarsh Adithya.K said:
Its twrp 3.2.3 and yeah before installing rom , i did a full wipe of dalvik, data, system, internal storage and then did a data format too
Click to expand...
Click to collapse
Please link the twrp file you're running. Als also you aware that twrp won't stick if you flash full oos rom?
strongst said:
Please link the twrp file you're running. Als also you aware that twrp won't stick if you flash full oos rom?
Click to expand...
Click to collapse
"https://dl.twrp.me/cheeseburger/twrp-3.2.3-0-cheeseburger.img.html"
Yeah i m aware of it and i flashed twrp back every time i finish flashing full OOS
Akarsh Adithya.K said:
"https://dl.twrp.me/cheeseburger/twrp-3.2.3-0-cheeseburger.img.html"
Yeah i m aware of it and i flashed twrp back every time i finish flashing full OOS
Click to expand...
Click to collapse
Please use the latest blu spark recovery which needs to be installed for the vendor partition from 5.1.4 https://forum.xda-developers.com/devdb/project/dl/?id=30332 or codeworks recovery. If you decrypt internal storage and did not flash no verity zip to stay decrypted, after first boot oos will encrypt interval storage.
strongst said:
Please use the latest blu spark recovery which needs to be installed for the vendor partition from 5.1.4 https://forum.xda-developers.com/devdb/project/dl/?id=30332 or codeworks recovery. If you decrypt internal storage and did not flash no verity zip to stay decrypted, after first boot oos will encrypt interval storage.
Click to expand...
Click to collapse
Its Decrypted , but do i have flash no verity zip, again after flashing twrp img
Akarsh Adithya.K said:
Its Decrypted , but do i have flash no verity zip, again after flashing twrp img
Click to expand...
Click to collapse
If you want to stay decrypted: yes
But first update your twrp, check if data partition is accessible, otherwise format internal storage - easiest way.
strongst said:
If you want to stay decrypted: yes
But first update your twrp, check if data partition is accessible, otherwise format internal storage - easiest way.
Click to expand...
Click to collapse
Thanks man strongst, it worked.
Changing recovery to blu spark twrp made all the difference, now i m on OOS 5.1.4
Akarsh Adithya.K said:
Thanks man strongst, it worked.
Changing recovery to blu spark twrp made all the difference, now i m on OOS 5.1.4
Click to expand...
Click to collapse
To help others mark this thread as [SOLVED] in the the title :good:
strongst said:
To help others mark this thread as [SOLVED] in the the title :good:
Click to expand...
Click to collapse
Yeah And one last question,
I tried ti update it to 5.1.5, using same process, and it throws boot loop, is there any other specifc order to flashing magisk and no verity, Or do i have to use other version of verity.
currently the one i m using is no verity v2
Akarsh Adithya.K said:
Yeah And one last question,
I tried ti update it to 5.1.5, using same process, and it throws boot loop, is there any other specifc order to flashing magisk and no verity, Or do i have to use other version of verity.
currently the one i m using is no verity v2
Click to expand...
Click to collapse
Flash full rom Update 5.1.4, then 5.1.5 then
Just make sure that vendor partition is mounted correctly within twrp, before flashing no verity v2 and after then magisk.
Now you can reboot the first time. If it won't help, you should format internal storage again when you have copied files into it like the rom zip. This can cause a bootloop sometimes.
strongst said:
Flash full rom Update 5.1.4, then 5.1.5 then
Just make sure that vendor partition is mounted correctly within twrp, before flashing no verity v2 and after then magisk.
Now you can reboot the first time. If it won't help, you should format internal storage again when you have copied files into it like the rom zip. This can cause a bootloop sometimes.
Click to expand...
Click to collapse
Again , thank you soo much man .
Turns out enabling that vendor portion after flash rom for no verity and magisk will cause no trouble
and now i m on OOS 5.1.5!!(uninstalling Magisk before flashing new update was important to).
Now that
how do i mark this thread as Solved.
Hello,
I read about partition A/B, but I would like to have more insight some points are not really clear in my head.
My OP6T is rooted on partition B, everything works fine on this partition
On partition A, It automatically boot into recovery
How can I have a fresh install on both partition ?
Does I have to root both partition ?
You don't have to root both partitions, your second partition is probably blank, you can flash a rom to that partition or just let it be, its not a must have for a working device and generally when you root magisk inserts intself into both partitions.
Dark Nightmare said:
You don't have to root both partitions, your second partition is probably blank, you can flash a rom to that partition or just let it be, its not a must have for a working device and generally when you root magisk inserts intself into both partitions.
Click to expand...
Click to collapse
Ok, thank you for quick answer.
how do you flash a rom only on one partition ?
when you wipe in TWRP, does it wipe both or only one partition ?
I would like to have both partition at the same stage of update in case one get broken.
It is possible to make a copy of one partition to the other ?
Soujyu51 said:
Ok, thank you for quick answer.
how do you flash a rom only on one partition ?
when you wipe in TWRP, does it wipe both or only one partition ?
I would like to have both partition at the same stage of update in case one get broken.
It is possible to make a copy of one partition to the other ?
Click to expand...
Click to collapse
Well the whole point of two partitions is to have one in the previous state if an update breaks the current one...
You can flash one of the fastboot roms or full zips available in the general section, but you may have to modify the zip files to only flash to a single slot as the zips currently flash to both slots.
Dark Nightmare said:
Well the whole point of two partitions is to have one in the previous state if an update breaks the current one....
Click to expand...
Click to collapse
that's my point, I want to copy my partition B to my partition A, then modify one or the other, for a period they will be at the same state but this will rapidly change
Dark Nightmare said:
You can flash one of the fastboot roms or full zips available in the general section, but you may have to modify the zip files to only flash to a single slot as the zips currently flash to both slots.
Click to expand...
Click to collapse
is it possible to wipe everything and make a fresh install on both ?
Soujyu51 said:
is it possible to wipe everything and make a fresh install on both ?
Click to expand...
Click to collapse
use fastboot rom.
dieandromeda said:
use fastboot rom.
Click to expand...
Click to collapse
I will need a bit more information please xD
Soujyu51 said:
I will need a bit more information please xD
Click to expand...
Click to collapse
Only system / boot are concerned by the slot organization. Read general texts and tutorials about that and fastboot use. Everything needed is on the internet.
Striatum_bdr said:
Only system / boot are concerned by the slot organization. Read general texts and tutorials about that and fastboot use. Everything needed is on the internet.
Click to expand...
Click to collapse
Thank you very much that is a big help in my questionning
I followed this
https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
and use this one flash-all.bat
it boot on both partition
Thank you
Thanks!
It solved my problems
I flashed TWRP recovery I used last week, to install SparkOS and I do remember following a tutorial that said wipe Dalvik, Cache, Data, System and Vendor, which I did successfully and installed the custom rom. I didn't last much and reverted to Stock Rom.
Cut to yesterday I flashed the same recovery as last time, and when I went to wipe the partitions I didn't find Vendor. Checked Mount menu clicked on Vendor it didn't show up under Wipe.
Should I ignore this and continue with installing my custom rom after wiping (Dalvik, Cache, Data and system only) or this is a problem and I am not able to install any custom rom until I wipe Vendor Partition?
It may cause problem or maybe not. Try Orange Fox recovery or any other recovery which supports to wipe vendor data and then flash your Custom Rom correctly as in tutorial.
ai.Sanaul said:
It may cause problem or maybe not. Try Orange Fox recovery or any other recovery which supports to wipe vendor data and then flash your Custom Rom correctly as in tutorial.
Click to expand...
Click to collapse
I followed it step by step, but I'm gonna try different versions and see if shows up. Otherwise I'll revert back to stock and hang my hat.
ai.Sanaul said:
It may cause problem or maybe not. Try Orange Fox recovery or any other recovery which supports to wipe vendor data and then flash your Custom Rom correctly as in tutorial.
Click to expand...
Click to collapse
Updating the TWRP version from 3.3.1 to 3.6 fixed the problem. Thank you for the help.
Ikarisdruig said:
Updating the TWRP version from 3.3.1 to 3.6 fixed the problem. Thank you for the help.
Click to expand...
Click to collapse
welcome