Related
Hi guys,
Long time reader, and great help to be found I hope!
I just bought a Z1C, followed successfully the full DRM backup, full root process and bootloader unlocked, from the guide posted : http://forum.xda-developers.com/showthread.php?t=2642081
I took a full backup of DRM keys and Nandroid.
I then went to load the Resurrection Remix ROM. I booted in to PhilZ recovery and did a full wipe and factory reset - "Ready for ROM". This completed successfully.
I then realized I forgot to copy the Resurrection ROM files onto my external SD and cancelled/exit out of PhilZ Recovery.
Now when I power up, all I get is SONY logo. I assume this is because the phone has no operating system due to the ROM being wiped and nothing being installed in it's place.
I can confirm I can get into Fastboot mode (Blue LED, but connecting USB and holding UP volume button) but nothing else!!!
If anyone has any ideas, I would really really appreciate it!
thanks in advance!
... ok, so I found a quick fix, sorry for the alarm. I just used ADB to flashboot a version of CWM6 and made it boot into recovery, copied the Resurrection ROM onto my external SD with a card-reader (seperate) then installed the ROM ... hooray! Now I can sleep.
Thanks to anyone who started reading...
For future reference, just using fastboot to install a boot partition with a recovery on it is sufficient to fix these kinds of issues.
fastboot boot path/to/boot.img
or
fastboot flash boot path/to/boot.img
And for the record, with most recoveries you can mount your SDcard on your computer via USB, in CWM it is available in the mounts menu as "Mount USB storage"
Rekoil said:
For future reference, just using fastboot to install a boot partition with a recovery on it is sufficient to fix these kinds of issues.
fastboot boot path/to/boot.img
or
fastboot flash boot path/to/boot.img
And for the record, with most recoveries you can mount your SDcard on your computer via USB, in CWM it is available in the mounts menu as "Mount USB storage"
Click to expand...
Click to collapse
Thanks for the tips. I'm a bit new to this thing ... I assume your commands above will create a separate partition for booting, but how do I get to that recovery screen? ... and I assume boot.img is a recovery boot file? Renamed from CWM?
My issue above was I couldn't load up anything (Sony logo appears, and nothing else, couldn't proceed to recovery screen by pressing UP volume) ... I only could connect to my computer in flash mode for Flashtools to read, and had to start the whole "root my phone" process again.
I am playing around with the stock Sony UK ROM, but I am keen to flash Aura's AURom or maybe another one ... is there a way that I can basically create a "rollback point" so that if I don't like the new ROM I can re-instate what I am playing with now? I really don't want to have to go through the whole root process again if I semi-brick again! Just want to do an easy "undo" ...
Many thanks for putting up with the noob-ness.
boot.img is an image of the kernel. Note that this command is only for unlocked bootloader.
Seems you are using dualrecovery (which resides inside /system) and since you wiped /system you couldn't get into recovery anymore. If you have unlocked bootloader you should use a custom kernel. You can use the one of [NUT] (same functionality as dualrecovery) or the one from Doomlord.
I really don't want to have to go through the whole root process again
Click to expand...
Click to collapse
You do realize that the root process with unlocked bootloader is as followed:
1. Flash custom kernel
2. Go to recovery and flash SuperSU zip
zxz0O0 said:
You do realize that the root process with unlocked bootloader is as followed:
1. Flash custom kernel
2. Go to recovery and flash SuperSU zip
Click to expand...
Click to collapse
Exactly, and if you have saved your TA partition already, then you can always unlock the bootloader, root, and then relock bootloader by flashing your TA partition back.
Awesome, thanks guys for all the help. I will give the AURom a go and hopefully succeed this time.
One last question, what is contained in the TA backup, and what is in a Nandroid backup? From reading, TA is just a set of keys and Nandroid is a Rom backup?
TA backup is a backup of the Trim Area partition, inside of this partition there are DRM keys. Nandroid backup is a backup of various partitions (/system, /data/, etc.) but not TA partition.
zxz0O0 said:
TA backup is a backup of the Trim Area partition, inside of this partition there are DRM keys. Nandroid backup is a backup of various partitions (/system, /data/, etc.) but not TA partition.
Click to expand...
Click to collapse
Super thanks guys, much appreciated
Hello forum,
i'm currently trying to find the best software solution for my Xperia Z1 Compact and i already got close to what's possible.
I found this ROM which is working almost perfectly except that it overrides the recovery with a dual recovery with an older TWRP version which prevents me from doing critical flashes and backups.
I only need TWRP 3.0.2 on /recovery, nothing else like PhilZ or anything else.
When i flash TWRP 3 for Z1C and reboot to recovery or press Vol-Up when booting i get a blackscreen boot loop which can only be fixed by flashing an old TWRP or wiping the entire phone from fastboot.
Another problem is that updater-script formats /system and /data to ext4 and mounts them like that which is a problem because i'd like to have F2FS on all of my partitions.
I already tried removing /kernel/ and /dualrecovery/ from the .zip and modifying updater-script to not format both patititons and mount them as F2FS, but when trying to flash this modded .zip it fails to flash (probably because an integrity check?).
So what i need to do is:
Remove recovery from .zip
Remove kernel from .zip
Modify updater-script to not format any partitions and mount them as F2FS
Any help, resources and tipps are appreciated. I'm running Windows 10 x64 but i don't think i'm able to build a ROM on my own as i have only little programming experience.
SinusStudios said:
Hello forum,
i'm currently trying to find the best software solution for my Xperia Z1 Compact and i already got close to what's possible.
I found this ROM which is working almost perfectly except that it overrides the recovery with a dual recovery with an older TWRP version which prevents me from doing critical flashes and backups.
I only need TWRP 3.0.2 on /recovery, nothing else like PhilZ or anything else.
When i flash TWRP 3 for Z1C and reboot to recovery or press Vol-Up when booting i get a blackscreen boot loop which can only be fixed by flashing an old TWRP or wiping the entire phone from fastboot.
Another problem is that updater-script formats /system and /data to ext4 and mounts them like that which is a problem because i'd like to have F2FS on all of my partitions.
I already tried removing /kernel/ and /dualrecovery/ from the .zip and modifying updater-script to not format both patititons and mount them as F2FS, but when trying to flash this modded .zip it fails to flash (probably because an integrity check?).
So what i need to do is:
Remove recovery from .zip
Remove kernel from .zip
Modify updater-script to not format any partitions and mount them as F2FS
Any help, resources and tipps are appreciated. I'm running Windows 10 x64 but i don't think i'm able to build a ROM on my own as i have only little programming experience.
Click to expand...
Click to collapse
I don't know much, but I am surprised that flashing twrp 3 causes that problem. What method are you using? Try using Rashr to flash twrp 3 img, then try to boot to recovery. If vol up doesn't work, try vol down, (that's what works for me). Somehow I don't think you'll be able to just remove those things from the ROM and have it flash fine. Your better chance is to get twrp flashed, then figure out the F2FS, etc. Also, there are custom kernels for stock-based roms, and don't forget that twrp 3 is not official on Z1compact, so read threads thoroughly to make sure what you're trying to do is supported. I know many of us have twrp 3 on our phones, so I would look more into that.
Hi,
I had the same issues and maybe this helps.
- install your rom and go into dual recovery and choose twrp
- in twrp go to install and choose "IMG" and not "ZIP"
- you can now install the new twrp version via install !
Maybe you should not flash that ROM because it seems to contain malware. Have a look into the thread.
I'm currently running my OP3 on Resurrection Remix 5.7.4 (MM 6.01), the phone has the latest version of TWRP and I've flashed other ROMs in the past without any issue
RR has proven to be quite unstable for me, the system UI keeps crashing, which renders the phone unusable until after a reboot so I wanted to flash Freedom OS as that worked quite well for me previously. When I tried to flash the ROM in TWRP the ROM seemed to flash successfully but when I rebooted, only the boot logo showed and then the screen went black and the phone refused to respond at all for about two hours, after that exactly the same thing happened. I managed to boot into recovery and tried flashing a different ROM but the result was the same every time, the only way to get the phone to work normally was to flash RR again/restore from a Nandroid backup, either way, the result is the same, I'm stuck on an unstable ROM and I don't know why, the last time I flashed these ROMs they worked fine, I followed all of the instructions for flashing said ROMs to the letter, I have the latest version of TWRP, etc.
Also it seems TWRP can't mount /system, in TWRP under "mount", system is unchecked, I checked it and tried again but found that whenever I rebooted the phone or attempted to flash a new ROM, it would always uncheck itself and flashing the ROM would fail, however strangely flashing the same version of RR was always successful. Is this why the flashing keeps failing and does anyone know what the problem could be?
Thanks!
bronderb said:
Go into your bootloader and format system, cache, and userdata (This will wipe EVERYTHING so be sure to backup). Then latest official flash stock rom and reboot. This should fix it. If this helped hit thanks!
Click to expand...
Click to collapse
Bootloader? There is no option in the bootloader to delete everything as far as I can see, do you mean in recovery? And if I wipe everything off the phone, how do I get the stock ROM onto the phone to flash it? When you say wipe userdata do you mean wipe internal storage or am I misunderstanding and you're telling me to wipe the usual dalvik, cache and data as you would for a normal clean flash?
bronderb said:
No, go into fastboot and plug into pc. Open cmd and type "fastboot format userdata" "fastboot format cache" "fastboot format system"
Click to expand...
Click to collapse
Okay, thanks, and then what? Do I flash TWRP then push the stock ROM to the phone and flash that? And exactly how do I do that?
bronderb said:
You just go into twrp (no need to reflash) then adb sideload oxygen os
Click to expand...
Click to collapse
Thank you, I am now running OOS, hopefully everything else will go smoothly now, planning to go back to FOS again
I didn't even have to use the fastboot commands to format, just sideloading the OOS file wiped everything anyway
Turns out the issue isn't actually fixed, "system" still appears unchecked in TWRP. Could the fact that I didn't actually format everything first have made a difference, given everything was wiped in the process anyway?
Looks like I'm going to be living the sideloading life...
Edit: Sideloading freedom OS failed, ended up having to restore from my TWRP backup. I don't know what I'm going to do, my main reason for using custom ROMs is installing a black theme, and OOS doesn't support Layers or Substratum fully so I can't stay on that
Is the thing that says "mount system as read-only" enabled in the mounts menu? /System isn't ever mounted when TWRP starts, you have to manually mount it, but as long as the updater-script tells /system to mount, it will. However, if that option to make it read-only is enabled, then nothing will ever write to /system. Last resort is deleting the .twrps file from /sdcard/TWRP folder to remove current TWRP preferences and then when you boot into TWRP, that first screen has the swiper to allow modifications, and you'll swipe that
frickinjerms said:
Is the thing that says "mount system as read-only" enabled in the mounts menu? /System isn't ever mounted when TWRP starts, you have to manually mount it, but as long as the updater-script tells /system to mount, it will. However, if that option to make it read-only is enabled, then nothing will ever write to /system. Last resort is deleting the .twrps file from /sdcard/TWRP folder to remove current TWRP preferences and then when you boot into TWRP, that first screen has the swiper to allow modifications, and you'll swipe that
Click to expand...
Click to collapse
It isn't set to read only, I have tried updating and resetting TWRP but nothing has helped, in fact it's got worse, I managed to sideload OOS but my attempted install of FOS failed so I tried to restore from a backup and that also failed, something which didn't happen back when I was on RR.
evilkitty69 said:
It isn't set to read only, I have tried updating and resetting TWRP but nothing has helped, in fact it's got worse, I managed to sideload OOS but my attempted install of FOS failed so I tried to restore from a backup and that also failed, something which didn't happen back when I was on RR.
Click to expand...
Click to collapse
Which version of TWRP are you running? The official 3.1.0-0 is good for OOS and OOS based ROMs only. Try eng.stk's version.
Use the latest eng-stk twrp.
https://forum.xda-developers.com/devdb/project/?id=15934#downloads
In recovery go to Wipe > Format data (this will wipe ALL in youre phone).
It's youre Data in F2FS? If yes you must change it to ext4, in recovery Wipe > Change file system. Reboot recovery. Check if it's changed.
Reboot to Bootloader (Fastboot). From PC reflash recovery.
Now copy Oos rom to the phone memory. Flash rom. Reflash recovery (the rom will overwrite the recovery). Reboot to recovery to see if it works. If not do it again.
I sugest to NOT restore old data. This way you'll have all new in youre phone.
tnsmani said:
Which version of TWRP are you running? The official 3.1.0-0 is good for OOS and OOS based ROMs only. Try eng.stk's version.
Click to expand...
Click to collapse
I was running 3.0.2-2 when the issue started, I updated to 3.0.3 and 3.1.0-0 but nothing changed. Thanks for the suggestion, I will give it a try
null0seven said:
Use the latest eng-stk twrp.
https://forum.xda-developers.com/devdb/project/?id=15934#downloads
In recovery go to Wipe > Format data (this will wipe ALL in youre phone).
It's youre Data in F2FS? If yes you must change it to ext4, in recovery Wipe > Change file system. Reboot recovery. Check if it's changed.
Reboot to Bootloader (Fastboot). From PC reflash recovery.
Now copy Oos rom to the phone memory. Flash rom. Reflash recovery (the rom will overwrite the recovery). Reboot to recovery to see if it works. If not do it again.
I sugest to NOT restore old data. This way you'll have all new in youre phone.
Click to expand...
Click to collapse
Help! I attempted to do this and the process failed, I didn't manage to wipe data because "/data could not be mounted as device or resource is busy"
Edit: Device now has nothing but TWRP and fastboot, no OS, no ADB, no data, no internal storage
If you can reflash twrp from PC. If not reflash recovery from twrp recovery : Instal > Image > Select Recovery (you must have TWRP.img in youre phone memory )
I managed to get hold of a few factory images and attempted to flash system.img through fastboot, resulting error was
"target reported max download size of 536,870,912 bytes" (system image is 3080 MB)
"invalid sparse file format at header magi"
null0seven said:
If you can reflash twrp from PC. If not reflash recovery from twrp recovery : Instal > Image > Select Recovery (you must have TWRP.img in youre phone memory )
Click to expand...
Click to collapse
I reflashed the modified TWRP successfully. The second suggestion wouldn't have worked, given my phone has no internal storage
You can't see internal storage because of the recovery does not work write.
If you have a working recovery you can do all you want.
null0seven said:
You can't see internal storage because of the recovery does not work write.
If you have a working recovery you can do all you want.
Click to expand...
Click to collapse
The recovery was working at this point, the issue turned out to be the data partition, system was formatted to ext4 but I didn't realise data was in f2fs which caused the problem in the first place. I formatted to ext4 and everything worked, I was able to install paranoid android and everything worked...
...until I flashed the wrong firmware and now I've hard bricked it! I'm going to try the hard brick toolkit
Edit: After 12 hours of being an unresponsive brick, the phone suddenly booted, system doesn't work but it has recovery. Unfortunately I seem to be back to square one, if I try to flash something it appears to succeed but then the phone doesn't boot up into system
So I am now back to the original issue of system not mounting, in terminal if I type "mount /system" I get following error:
"mounting /dev/block/sde20 on /system failed: Device or resource is busy"
Anyone know how to solve this?
I formatted everything, reflashed recovery and tried to flash OOS, got following error:
Code:
[FONT="Courier New"]"This package is for OnePlus3 devices, this is a oneplus3t" (it isn't)
"Updater process ended with ERROR: 7
Error installing zip file /sdcard/OOS3.2.6.zip" [/FONT]
Issue was "solved" by flashing PA, GApps and the correct firmware
Hopefully that's the end of all this drama, thanks to everyone for their suggestions
Hi, I'm pretty new at rooting and I seem to have a similar error. I'm getting the "can't mount /system" error in TWRP. I am able to boot into OOS 4.1.3 and run the nandroid backup but, I keep getting the same error and am unable to select "system" when choosing the mount option in TWRP.
Do I need to have all partitions in f2fs? My system partition is in ext4. Is this what solved your issue?
It seems my phone is functional even with the error active but, I've been trying to get systemless SuperSU and MagiskHide working and I think that's what is preventing me from doing so.
hi,
my oneplus 3 has been rote since i got it (i bought it on launch day) but since i updated it to the beta 19, my phone is no longer rooted : when i put the phone in fastboot it says that my bootloader it unlocked but all the apps who requier root are saying that the phne is not rooted and i cant get twrp to work. i tryied with the official app on my phone and with a program called "tool all in one" (https://forum.xda-developers.com/on...ol-tool-one-driversunlocktwrpfactory-t3398993) and when i flash twrp from the program, i can boot into twrp but then i can't access my files and after i boot the phone, i can no longer boot to twrp
does anyone have a solution that doesn't involve me wiping the phone?
You loose root after updating. Try installing twrp again and then rooting it. Use the toolkit for oneplus 3. Simplifies the process
what do you mean by "then rooting it" ?
the program i use does the same thing as the toolkit and when i install twrp, as i said, it can boot on twrp one time and in twrp i can't access my files and after i boot the phone i can't get back to twrp ,i get the stock recovery
Unless your ROM has built-in root, after flashing TWRP, you have to flash SuperSU or Magisk to obtain root. Mere flashing of TWRP will not give you root.
I know but i can't get to the folder when the magisk file is : when in boot into twrp i cant see my files
Few details... it's quite difficult to help you.
What's the root method? Magisk, SuperSU or Kingroot? Which version?
Ps TWRP recovery is not depending by root, you just need to unlock bootloader (surely it's already unlocked) and flash the same recovery, from PC, via the command "fastboot flash recovery filename.img".
Now enter in TWRP:
1) Wipe /system and /cache;
2) Flash another time Open Beta 19;
3) Flash Magisk or SuperSU (be sure to have latest release);
4) Move TWRP img file from computer to device, then flash it another time (because firmware provides the OOS stock recovery);
5) Reboot and wait 5-10 minutes, because of cache rebuilding.
Tell me if you solve
I am using magisk
Yes my bootloader is unlocked
My problem is that when i flash twrp i cant access my files so i don't want to wipe system if i cant reflash something after
I think that I'll wait for the next update, maybe then it will work
But thank you for your help
Which version of TWRP do you have? Try eng.stk's latest version.
I tryied 3.1.1-2
The eng.stk is not available anymore
Your phone is encrypted, so you have to format data ( but your internal storage wiped by formating data, so back it up ,then only twrp read files in your storage)and flash custom kernel then boot restore backup .
how do you know that my phone is encrypted? i never encrypted it
i use titanium backup so i can't back my phone up until i get rot back
Whenever you flash stock ROM it encrypt if you boot into system directly . So twrp could not read internal storage. Whenever you flash stock ROM you must flash custom kernel or any other method to avoid encryption. This is happened to me and what I'd done is flash custom kernel before boot into rom
To save your data try this
https://forum.xda-developers.com/oneplus-3/how-to/unencrypt-oxygenos-loosing-data-t3412228
Who said that? Check this: https://forum.xda-developers.com/devdb/project/?id=15934#downloads
Edit: If you want to save items in internal storage, you can use ADB commands instead of TWRP. You can also simply copy and paste if your PC recognises the internal storage of your phone.
I succeeded but i had to clean everything and use the last backup i made a week ago
Thank you all for your help
I flashed AOSP_10_Quack_Phh-Treble_v208 many times last night.
but always failed,bootloop.
My step:
unlocked + TWRP
1.factory reset + format /data(or not)
2.flash V208.img to system image
3.format /data or not,reboot
My phone showed Redmi-logo and dm-verity error,
and bootloop.
anybody successed?
Could Somebody teach me how to flash GSI?
Maybe to flash AOSP 9?
It's reassuring to see you have attempted multiple times to flash another ROM and haven't hard bricked your phone.
My guess is you need to flash the dm-verity remove zip file. I'm assuming you have selected AVB 2.0 in TWRP? That's all I can think of but I haven't tried anything as clearly I don't have balls as big as yours
I used these following steps from tvardero :
Flash stock
Flash twrp
Make a backup of system and data (to get back into stock if needed)
Format data -> yes
Flash GSI you want to
To flash another GSI or revert to stock you use your backup of system partition.
NEVER EVER RESTORE ANYTHING ELSE THAN SYSTEM OR DATA, softbrick imminent
I try many GSI-ROM
Most bootloop,even I format /data,disable dm-verity/AVB 2.0 (TWRP by wzsx150)
My steps is
fomat /data,reboot to twrp
wipe /system ,2cache and flash gsi.img(Maybe resize /system to flash gapps)
flash magisk
disable dm-verity/AVB 2.0 with TWRP by wzsx150,or flash disabler.ZIP
GSI ROMs had some different bugs,brightness control,NO mobile signal,
sound,nfc-sim support,googlepay ,bank app etc.,
Really nice to see some testings. I hope we have some some development for our devices