Hi, OnePlus 5 from yesterday, i wanted to install recovery/root. Ok.
I have delete all partitions in TWRP (so bad) and i restore with the TWRP Backup (from rav101). All was fine but data/internal partition was writable only on TWRP, on OxygenOS i can't create folder/trasfers files. So i wanted to restore the factory ROM & restore the Bootloader/Recovery... I have use the tool "TOOL ALL IN ONE" for Lock again the bootloader.
Now my OnePlus 5 BootLoop between official recovery and start, i can't unlock OEM/Bootloader, i can't boot normaly and i can't restore Factory ROM
My answer is, OnePlus offer a tool like ODIN (Samsung) for restore emergency devices like stock? There a solution before/after OxygenOS 4.5.1 will be available?
Thanks
PS: I solve the problem, just launch again "TOOL ALL IN ONE" > Go to Fastboot > Unlock again > Done
I keep this thread if someone has the same problem ^^
Related
Hey guys and gals!
After a few weeks of using the phone, I now feel comfortable doing a Nandroid Backup (TWRP).
I used to do it all the time on my OPO Kitkat, but now with Android Marshmallow, it's quite different.
Here is my situation:
A2017U (us version)
TWRP 3.0.2.2 Installed
Bootloaded Unlocked
Rooted
Xposed Framework v87 installed
Update B29 installed
Inside TWRP>Backup I have many options:
1- Boot (64MB)
2- Cache (2MB)
3- Data(6969MB)
4- Recovery (64MB)
5- System (3723MB)
6- System Image (6144MB)
7- EFS (4MB)
By default, the "Boot", "Data" and "System" are selected, but after some reading I could also backup "System Image" for a near-perfect restore.
Also, some said to backup the EFS in-case it gets corrupted/damage, but some say it can brick your device.
Could anyone tell me what should I backup in case I get stuck somewhere in the future.
Thank you !!
P.S: I have removed any fingerprints and set the lock screen to "Swipe" (no pattern).
First, make sure to flash the official twrp. Do not keep the one we use to unlock bootloader.
There is no harm in backing up efs, in fact it is a good idea to do so. Just do not select it during a restore unless something has wiped your current efs and its the only way to fix.
I don't see a need to back up a full system image but couldn't hurt to at least have one for safe keeping.
Boutchoo said:
Hey guys and gals!
After a few weeks of using the phone, I now feel comfortable doing a Nandroid Backup (TWRP).
I used to do it all the time on my OPO Kitkat, but now with Android Marshmallow, it's quite different.
Here is my situation:
A2017U (us version)
TWRP 3.0.2.2 Installed
Bootloaded Unlocked
Rooted
Xposed Framework v87 installed
Update B29 installed
Inside TWRP>Backup I have many options:
1- Boot (64MB)
2- Cache (2MB)
3- Data(6969MB)
4- Recovery (64MB)
5- System (3723MB)
6- System Image (6144MB)
7- EFS (4MB)
By default, the "Boot", "Data" and "System" are selected, but after some reading I could also backup "System Image" for a near-perfect restore.
Also, some said to backup the EFS in-case it gets corrupted/damage, but some say it can brick your device.
Could anyone tell me what should I backup in case I get stuck somewhere in the future.
Thank you !!
P.S: I have removed any fingerprints and set the lock screen to "Swipe" (no pattern).
Click to expand...
Click to collapse
lafester said:
First, make sure to flash the official twrp. Do not keep the one we use to unlock bootloader.
There is no harm in backing up efs, in fact it is a good idea to do so. Just do not select it during a restore unless something has wiped your current efs and its the only way to fix.
I don't see a need to back up a full system image but couldn't hurt to at least have one for safe keeping.
Click to expand...
Click to collapse
How do I know which TWRP I installed ?
Do you have a link for the official TWRP for the Axon 7 ?
Its in the dev forum titled official twrp.
lafester said:
Its in the dev forum titled official twrp.
Click to expand...
Click to collapse
This? :
https://twrp.me/devices/zteaxon7.html
https://dl.twrp.me/ailsa_ii/
Edit: Looks like there's twrp-3.0.3-0-ailsa_ii Out for the Axon 7
But the official XDA Forum Page it's twrp-3.0.2-0-a2017u
After flashing the 3.0.2-0-a2017u, I now have in the backup sections: Modem (NON-HLOS) (95MB), I don't know if I should back it up.
Hello everyone,
I tried to install SuperSU on my Axon7 (by flashing SuperSU-v2.65-20151226141550 in TWRP) and after that, my phone doesn't boot anymore.... I still have access to TWRP (3.0.2-2) but I can't access to the system. I tried to restore a backup I made with TWRP and wipe cache, DALVIK and data but it didn't work.
When I try to boot, I'm blocked on the screen "ZTE powered by Android".
How can I restore my stock ROM with TWRP?
PS: I was in stock rom and my model is the B06.
Thanks in advance!!
Is your bootloader unlocked? In such case, my advice is to flash the ZADmix7 ROM to your 2017G from TWRP.
Otherwise you can go back to stock using this guide. If you can access recovery or bootloader, then your brick is a very, very soft brick.
st3ph31 said:
Hello everyone,
I tried to install SuperSU on my Axon7 (by flashing SuperSU-v2.65-20151226141550 in TWRP) and after that, my phone doesn't boot anymore.... I still have access to TWRP (3.0.2-2) but I can't access to the system. I tried to restore a backup I made with TWRP and wipe cache, DALVIK and data but it didn't work.
When I try to boot, I'm blocked on the screen "ZTE powered by Android".
How can I restore my stock ROM with TWRP?
PS: I was in stock rom and my model is the B06.
Thanks in advance!!
Click to expand...
Click to collapse
If your BL is still unlocked and you did flash SU2.65 before you should have unlocked it, than you might follow this thread too to unlock your BL first and then flash SU2.65 again
https://forum.xda-developers.com/showpost.php?p=70562463&postcount=154
https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379
Perhaps this might help
Thanks to you two for your help, I followed this tuto: https://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484 and everything is fine now
I thought that TWRP was enough to install SuperSU... Next time, I will read more carefully the tutos
Before going into the subject, I'll say that I have tried to seach this matter in XDA and Google, but nothing showed up.
Okay, so my matter is that I can't restore my backup of stock rom(8.0) after I flash a 8.1 rom. I've backuped with official TWRP "recovery-3.2.1-2-oreo.img".
My procedures are :
back up stock 8.0(system, data, cache, efs) with official TWRP "recovery-3.2.1-2-oreo.img"
flash oreo rom(with wiping internel, data, system, cache) and boot it fine.
restore my stock backup with same TWRP
boot system
The results are :
Goes past boot logo
Boot animation('android one' with colors sliding) shows up
and... just infinite loop of boot animation.
The ROM I used is RR.
I think the main problem is related with encryption.... Just my thought, tho.
So what I'm asking is :
1. If you face the same problem as me?
2. If you aren't and you restore goes fine, please tell me your procedures including ROM used and TWRP used.
3. Whether it is safe to decrypt stock rom?
Thanks in advance!
You don't need to flash stock ROM again. You have a system image backup(system, data, cache, efs), right? Wipe data , system, cache if you are coming from any other ROM. Then reboot to bootloader. Boot into latest TWRP from Fastboot (don't flash). Then go to restore and restore the system image you had backed up. Don't restore efs if you haven't lost your IMEI.
I've done exactly as ypu told, but it doesn't boot...
Did you manage to restore without problem with your method?
Yes I was able to. No problem here.
What TWRP did you use? Also, what ROM have you flashed?
Used the latest TWRP by MohanCM for Oreo. I did it when I was on Lineage os and wanted to go to stock
@guy_infinity Okay, thanks for your answer! Gonna try out later, once more.
Hmmm.... Still didn't boot up.
I thought I had to do everything from the begining, but flashing stock with save userdata option rescued me.
P.S. does anyone know about the error E: recv error on uevent?
try flashing stock rom using mi flash and after flashing restore normally using latest twrp/deadman's without system image voila everything will be back
@arjunbalan1994 Big thanks for your suggestion! Will try that too later
Hi, did you solve your restore problem? I have the same w/ my Redmi Note 5 and stock Miui backup after flashing RR.
Thanks for your help
I was use 8.1 root and twrp recovery. Yesterday fastboot flash may rom and update 2nd may OTA
Don't understand : May rom is Miui rom?
And did you restore your miui rom 8.0 backup ith twpr after the fastboot flash stock?
Using the stock from for my Moto G5 Plus works fine - SIM is detected and Wifi has no issues.
On flashing any custom ROM (e.g. Havoc-OS-v3.5, Arrow-v10.0-potter, PixelExperience_potter-xxx-OFFICIAL, ...) it does no longer detect my SIM card. :crying:
(Unlock Bootloader ->Twrp-> Grant SU -> flash custom image -> :crying::crying
The only solution is to go back to stock ROM, where everything works fine and without any issue.
Which step is missing/wrong?
MarkusStgt said:
Using the stock from for my Moto G5 Plus works fine - SIM is detected and Wifi has no issues.
On flashing any custom ROM (e.g. Havoc-OS-v3.5, Arrow-v10.0-potter, PixelExperience_potter-xxx-OFFICIAL, ...) it does no longer detect my SIM card. :crying:
(Unlock Bootloader ->Twrp-> Grant SU -> flash custom image -> :crying::crying
The only solution is to go back to stock ROM, where everything works fine and without any issue.
Which step is missing/wrong?
Click to expand...
Click to collapse
Check if imei is available in custom ROM. If imei not available, take backup of EFS and persist in stock and restore in custom ROM you want. You will get your network in custom ROM.
riyan65 said:
[...] take backup of EFS and persist in stock and restore in custom ROM you want. You will get your network in custom ROM.
Click to expand...
Click to collapse
Could you please provide set of fastboot based commands ('dd if=..., etc.) to persist in stock and restore in custom ROM?
This would be very helpful. Thank you very much in advance. :angel:
Perform the backup using TWRP. Boot into recovery/TWRP in your moto stock ROM. Select BACKUP. Backup the Persist and EFS partitions, Select storage on your Micro SD card. Swipe to backup. (I would backup all the partitions - when restoring you can select only the Persist and EFS as needed).
Then when you are on the custom ROMS and it does not work, boot into recovery /TWRP, then select RESTORE, then select the directory that the TWRP backup was made in, and check only the PERSIST and EFS partitions, and swipe to restore.
Hope that helped.
Nivead said:
Hope that helped.
Click to expand...
Click to collapse
I will try it later today.
But one additional questions: As the stock ROM (8.1) is bases on kernel 3.18.72 (as of Feb 2019), I expect the PIE-ROM will use a much newer version.
What about the PERSIST and EFS partitions. Will they be binary compatible? Don't the differ in content and/or structure?
Persist and EFS are the radio/modems for the phone. They contain individual software calibrations specific to your phone only. Things like oscillator frequency calibrations, amplifier bias, sensor calibrations, etc. The files are not changed for any of the custom ROMS or stock firmware. There are file ownership problems that some ROMs/OS mark them as theirs and when ROMs are changed, they cant be accessed. TWRP, the latest version 3,3,1-0 does a binary backup of the partitions and it works fine with the Moto G5 Plus. Further info:
what efs and persist are:
https://forum.xda-developers.com/android/general/info-android-device-partitions-basic-t3586565
basic info:
https://forum.xda-developers.com/g5-plus/how-to/fix-persist-resolve-imei0-explanation-t3825147
Hope that helps.
Nivead said:
Persist and EFS are the radio/modems for the phone. They contain individual software calibrations specific to your phone only. Things like oscillator frequency calibrations, amplifier bias, sensor calibrations, etc. The files are not changed for any of the custom ROMS or stock firmware. There are file ownership problems that some ROMs/OS mark them as theirs and when ROMs are changed, they cant be accessed. TWRP, the latest version 3,3,1-0 does a binary backup of the partitions and it works fine with the Moto G5 Plus.
Hope that helps.
Click to expand...
Click to collapse
No unfortunatley it did not help.
I did the following sequence:
// Unlock bootloader
fastboot oem unlock ...
fastboot oem unlock ...
// flash twrp and boot without application
fastboot flash recovery twrp-3.3.1-0-potter.img
fastboot boot twrp-3.3.1-0-potter.img
// backup of EFS and /persists
TWRP backup EFS&Persists
// TWRP Flash su-tools
TWRP flashed Magisk-v20.4.zip
TWRP flashed lazyflasher-no-verity-opt-encrypt.zip
// Reboot in Stock Rom and checked for su
Install" Check su"
// Flash new os
TWRP flashed Arrow-v10.0-potter-OFFICIAL-20200509-VANILLA.zip
TWRP flashed Arrow-v10.0-potter-OFFICIAL-20200509-GAPPS.zip
// TWRP restore EFS&Persists out of backup
TWRP resored backup of above
// Rebooted into PI
--> No SIM
Any further suggestions?
MarkusStgt said:
No unfortunatley it did not help.
I did the following sequence:
// Unlock bootloader
fastboot oem unlock ...
fastboot oem unlock ...
// flash twrp and boot without application
fastboot flash recovery twrp-3.3.1-0-potter.img
fastboot boot twrp-3.3.1-0-potter.img
// backup of EFS and /persists
TWRP backup EFS&Persists
// TWRP Flash su-tools
TWRP flashed Magisk-v20.4.zip
TWRP flashed lazyflasher-no-verity-opt-encrypt.zip
// Reboot in Stock Rom and checked for su
Install" Check su"
// Flash new os
TWRP flashed Arrow-v10.0-potter-OFFICIAL-20200509-VANILLA.zip
TWRP flashed Arrow-v10.0-potter-OFFICIAL-20200509-GAPPS.zip
// TWRP restore EFS&Persists out of backup
TWRP resored backup of above
// Rebooted into PI
--> No SIM
Any further suggestions?
Click to expand...
Click to collapse
As @Nivead said it would be helpful to know if you have a IMEI when on a custom ROMs.
Have you started flashing custom ROMs from 8.1 or did you do any attempts from 7.0 in the start?
Have you tried to not flash Magisk right from the start? Sometimes Magisk causes weird issues and switching to another build like canary may solve the problem.
Maybe your persist partition is not in perfect shape anymore.
Here's a thread how to check the persist file and maybe fix it:
https://forum.xda-developers.com/g5...solve-imei0-explanation-t3825147/post77249207
Also if you prefer DD commands you can backup/restore this way:
Backup:
Code:
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
Restore:
Code:
dd if=/sdcard/persist.img of=/dev/block/bootdevice/by-name/persist
It seems you did everything correctly so these are just some thoughts what to do as a last resort.
Wolfcity said:
As [MENTION=10129789]
Have you started flashing custom ROMs from 8.1 or did you do any attempts from 7.0 in the start?
Click to expand...
Click to collapse
Many Thanks to all. This gave me the important hint. Directly flashing one custom ROM after the first try was wrong.
I solved it by returning back to my STOCK (8.1) by TWRP restore (with SIM and WiFi working fine) and flashing again a new but different custom ROM.
I selected Havoc-OS-v3.5, which now runs fine.
MarkusStgt said:
Many Thanks to all. This gave me the important hint. Directly flashing one custom ROM after the first try was wrong.
I solved it by returning back to my STOCK (8.1) by TWRP restore (with SIM and WiFi working fine) and flashing again a new but different custom ROM.
I selected Havoc-OS-v3.5, which now runs fine.
Click to expand...
Click to collapse
Good to hear you've got it working now. You're welcome.
I have an Axon 7. It was previously running TWRP 3.2.3.0L v1.3 and crDroid 9.0-20200514. The device had full disk encryption enabled.
I couldn't get Google Play Services to work using any of the standard tricks. I decided to factory reset via Settings.
My device rebooted into TWRP, which asked for my device password. When I entered it, it didn't accept it. (I had earlier run into this problem when I considered trying to update my ROM. I decided against it, because I couldn't get TWRP to mount my data partition.).
I figured while I was in TWRP anyway, and since I had already committed to factory reset, I would just prepare to flash the updated ROM.
Following the crDroid instructions here, I wiped cache, system, vendor, and data from within TWRP.
Unfortunately, I then accidentally rebooted before I flashed the new ROM.
My phone is now stuck at the boot screen. I cannot get into recovery. I can, however, get into EDL. (Edited to add: the device also shows up in Windows 10 Device Manager as Qualcom HS-USB 9008, so I should be able to use the Axon7_EDL_Tool.)
The good news is that I have everything backed up (using Titanium, and I have a several month old nandroid backup). Is there any way I can make this device work again?
I would suggest the following:
- Use Axon7_EDL_Tool to flash a full ROM
- Use Axon7_EDL_Tool to flash TWRP
- Use TWRP to flash crDroid
- restore your settings and apps with Titanium Backup