my phone stuck on boot and i try to flash stock rom doesnt work
i have efs.img backup i just want to know how to restore it any help
Flash stock rom wth odin
Look for efs backup restore tool in development section.
Sent from my GT-N7100
i flash stock after the device play th bootanimations stuck on samsung word
efs backup and restore tool must have full boot to the device this is missing here
any way to flash efs ?
MaZaGnGy said:
my phone stuck on boot and i try to flash stock rom doesnt work
i have efs.img backup i just want to know how to restore it any help
Click to expand...
Click to collapse
MaZaGnGy said:
i flash stock after the device play th bootanimations stuck on samsung word
efs backup and restore tool must have full boot to the device this is missing here
any way to flash efs ?
Click to expand...
Click to collapse
EFS backup/Restore have nothing to do with recovery of device which got stuck.
This is useful if you lost your IMEI.
Try this
Reboot to recovery (vol up + home+ power)
wipe cache and wipe data(factory reset)
Now if it reboot normally and if you have any issue regarding IMEI, you can restore it. To restore it i recommend to use same tool, from with you made backup.
ok now i solved it like this thread
but i got strange issue now
with all stock or custom roms the device by pass the setup in the start up (select language and gmail ect) and no lockscreen and if i hold the power bottom the device turned off (no power menu)
any idea
The lock screen is a bit bugged in 4.1.2 sometimes it just wouldn't lock. Try disabling and re enabling the lock screen.
Sent from my GT-N7100
not working
but i dont care about lockscreen i want to know how to fix the power bottom issue !!!
finally i got everything workinng again
i found that all my issues becuse my device was in factorymode so i turned it back to user mode and replace the efs folder from ES file explorer and everything working fine again
thank for all of u guys
for anyoe face the same problem this is the common for turn off factory mode
Type su
Then enter the following after the #
echo -n ON > /efs/FactoryApp/factorymode
reboot
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.
I have a problem with my TWRP backups created for 32.3.A.2.33 version. When I restore them, the phone restarts once and in the next boot int goes into recovery directly.
I have flashed:
E6853_32.3.A.2.33_1299-1511_R3D.ftf
Boot and recovery from:
https://forum.xda-developers.com/z5...ting-xperia-z5-z5p-variants-drm-keys-t3437902
And works perfectly, backups creates correctly from recovery, but when I try to recover them doesn't work.
The problem seems to be in system partition , data partition recover with no problems.
Any suggestions?
I have the same problem.
srg84 said:
The problem seems to be in system partition , data partition recover with no problems.
Any suggestions?
Click to expand...
Click to collapse
Is dm-verity turned off in kernel? If not this is the reason why. You need to backup system image instead of backup files from system partition like usually in TWRP.
Can you try to make backup and restore with this recovery?
flash with "fastboot flash recovery lineage_twrp_recovery.img"
To boot into recovery power off phone, wait 5-7 sec then press power+vol_down until it vibrate.
Select "System Image" to system partition backup.
Hi there,
Last friday I broke my lcd screen, it simply does not turn on anymore. Tomorrow an UPS employe will pick up my device and ship it to OP for repair.
My device: Oneplus 3 running TWRP recovery and rooted LineageOS. Adb is enabled in dev settings.
So now I am trying to create a nandroid backup to easily restore my system and data when I get my phone back since OP will reset it ...
I had this genious idea to boot into recovery and create a backup using adb but I ran into a problem.
I have to unlock my device in order to create the backup :/
adb console:
> D:\Desktop\Fastboot+ADB\Win32>adb backup -f backupbeforerepair --twrp system data boot
> Now unlock your device and confirm the backup operation.
So now I am hoping any of you will come up with another genious idea or a workaround so I can create this damn backup
Thanks alot in advance!
If anyone else would ever find himself in the same situation as me I was able to create the backup by doing the following:
You can use open recovery script in TWRP. See http://wiki.rootzwiki.com/OpenRecoveryScript
If you have the file
/cache/recovery/openrecoveryscript
then TWRP will process it when it starts.
If the file contains
backup BSDO myBackup
then the boot (kernel), system, and data partitions will be backed up in compressed format and named myBackup.
So, on your PC, create the openrecoveryscript file, boot into recovery, use ADB to push the file to /cache/recovery/openrecoveryscript then reboot back into recovery. That should trigger the backup process.
Note, the backup will be written to the default location TWRP for backups.
Click to expand...
Click to collapse