Database Info

Issues after cm13 flashing, infamous bootloop, and other festivities

Hi everyone.
Let's start from the beginning, and by advance excuse me for my poor English : I happen to be a delighted owner of the Oneplus One by the Oneplus company. I've flashed different versions of cyanogen on my phone, rooted it multiple times and I never encountered any kind of problems. Thus, until I decide yesterday to flash the latest release of cyanogen, cm13 (nightly). I did some researches, followed the usual steps, flashed the right opengapps version along with cm13 and.. everything went great. Except that my phone couldn't resolve himself to detect my SIM card anymore. I tried different things in order to solve the problem, including re-wipe the phone "factory reset" style, removing SIM card, wait for the phone to cool down and played with data roaming, but nothing worked. Fortunately I had my fresh nandroid backup waiting to be restored. That's when the real deal start :
even after having restored the full nandroid backup (which make me downgrade to cm12.1), the SIM card wasn't detected.
So I decided to wipe data, dalvik, cache and system, in order to get my phone back to its original state. But the problem remains, and worst of all, the phone now tends to reboot punctually without any reasons.
I surely did something wrong for the phone to end in this state, but I can't see what..
I use TWRP 2.8.7.0 custom recovery, and the phone OS is now cm12.1-YOG4PAS3JL.
Oneplus One 64GB.
Sorry for the length of the complaint, and by advance thanks for your answers.
P.S : I did tried to search for similar threads in the forum, but I didn't manage to found anything that was directly related.

It could be an issue with the modem not being flashed properly when you went from Lollipop to Marshmallow due to TWRP 2.8.7.0. Try TWRP 2.8.6.0, and then either restore the nandroid backup or clean wipe + reflash CM13 nightly.

oble said:
It could be an issue with the modem not being flashed properly when you went from Lollipop to Marshmallow due to TWRP 2.8.7.0. Try TWRP 2.8.6.0, and then either restore the nandroid backup or clean wipe + reflash CM13 nightly.
Click to expand...
Click to collapse
Thanks a lot for your response. I've been searching a lot and the problem effectively seems to be the modem not being flashed properly. So I tried to flash it manually, (found the file 2 threads higher, sorry I can't post links yet) via fastboot and then flashing cm13 (with twrp 2.8.6.0), considering the fact it seems to have worked for others.
But no matter what I do, the issue remains : the phone isn't able to detect SIM card and goes into crash, rebooting every 2mn..
I've tried to flash cm13 unnoficial version by sultan, following his instructions, but no improvement either.
Even my nandroid backup (running cm 12.1) can't detect SIM anymore, have serious wifi connectivity issues, and keeps rebooting randomly at very reguliar intervals..
I'm really beggining to feel hopeless,
but thanks again for your time and your advices, really apreciate it.

It seems that I have same problem..... after flashing CM13 and restoring backup
Any progress with this problem?
Edit - If my phone is connected into PC with USB cable it doesnt restarts

gersa said:
It seems that I have same problem..... after flashing CM13 and restoring backup
Any progress with this problem?
Edit - If my phone is connected into PC with USB cable it doesnt restarts
Click to expand...
Click to collapse
Same for me, the phone stops crashing and rebooting randomly once connected to pc via USB cable. But still doesn't recognize SIM card. Wifi also seems to work better.
No further progress unfortunately, I've tried everything, from restoring the phone to its factory state to flashing all "stable" roms (cyanogen), nothing worked.

MethylHaine said:
Hi everyone.
Let's start from the beginning, and by advance excuse me for my poor English : I happen to be a delighted owner of the Oneplus One by the Oneplus company. I've flashed different versions of cyanogen on my phone, rooted it multiple times and I never encountered any kind of problems. Thus, until I decide yesterday to flash the latest release of cyanogen, cm13 (nightly). I did some researches, followed the usual steps, flashed the right opengapps version along with cm13 and.. everything went great. Except that my phone couldn't resolve himself to detect my SIM card anymore. I tried different things in order to solve the problem, including re-wipe the phone "factory reset" style, removing SIM card, wait for the phone to cool down and played with data roaming, but nothing worked. Fortunately I had my fresh nandroid backup waiting to be restored. That's when the real deal start :
even after having restored the full nandroid backup (which make me downgrade to cm12.1), the SIM card wasn't detected.
So I decided to wipe data, dalvik, cache and system, in order to get my phone back to its original state. But the problem remains, and worst of all, the phone now tends to reboot punctually without any reasons.
I surely did something wrong for the phone to end in this state, but I can't see what..
I use TWRP 2.8.7.0 custom recovery, and the phone OS is now cm12.1-YOG4PAS3JL.
Oneplus One 64GB.
Sorry for the length of the complaint, and by advance thanks for your answers.
P.S : I did tried to search for similar threads in the forum, but I didn't manage to found anything that was directly related.
Click to expand...
Click to collapse
`
Here is solution (for me)
http://forum.xda-developers.com/showpost.php?p=64768887&postcount=3
Read whole, its short

gersa said:
`
Here is solution (for me)
http://forum.xda-developers.com/showpost.php?p=64768887&postcount=3
Read whole, its short
Click to expand...
Click to collapse
Already saw it, but thanks ^^ that's where i found my file modemst.bin
so did it work for you ?

The same thing happened to me last week. I was using Materialized TWRP 2.8.7.0, which I think caused issues with my updating of Sultanxda's 13.1 ROM. SIM card was never detected, phone would restart shortly after every boot. I tried everything I could find to get my baseband and IMEI back.
In the end, only this solution worked for me, and I had to do it twice. I don't know why.

I had the same problem. I got back to TWRP 2.8.6.0 and then flashed the latest CM13(wiped System). after that without wipe i flashed sultans's CM13 then gapps and got the sim working again.

jp.esteban said:
The same thing happened to me last week. I was using Materialized TWRP 2.8.7.0, which I think caused issues with my updating of Sultanxda's 13.1 ROM. SIM card was never detected, phone would restart shortly after every boot. I tried everything I could find to get my baseband and IMEI back.
In the end, only [link] this solution[/URL] worked for me, and I had to do it twice. I don't know why.
Click to expand...
Click to collapse
Thanks for the link. I tried to flash the zip, but twrp(2.8.6.0) gave me an error : Error flashing ONEPLUS+ONE-FIX-Windows.zip
I tried to clean flash it and dirty flash it, nothing seems to work.

ashishsaggu said:
I had the same problem. I got back to TWRP 2.8.6.0 and then flashed the latest CM13(wiped System). after that without wipe i flashed sultans's CM13 then gapps and got the sim working again.
Click to expand...
Click to collapse
I've tried multiple times, it doesn't work. SIM card is not recognized, phones goes to reboot after 30s of use.
Whatever rom I flash the problem ain't solved, even after factory reset from original OS (cm 12.1)..
I really begin to think there is no solution, I've tried to flash my phone at least 20 times with different roms, fix, firmwares, modem, everything that is available on the net and I couldn't notice even the slightest change in the comportment of my phone.
Anyway, thanks a lot for your proposal, I guess it HAVE to work, but for some irrational reason it doesn't...

MethylHaine said:
I've tried multiple times, it doesn't work. SIM card is not recognized, phones goes to reboot after 30s of use.
Whatever rom I flash the problem ain't solved, even after factory reset from original OS (cm 12.1)..
I really begin to think there is no solution, I've tried to flash my phone at least 20 times with different roms, fix, firmwares, modem, everything that is available on the net and I couldn't notice even the slightest change in the comportment of my phone.
Anyway, thanks a lot for your proposal, I guess it HAVE to work, but for some irrational reason it doesn't...
Click to expand...
Click to collapse
Did U flash over TWRP or ADB?

Just popping in to say I have the same problem. I'm trying the various solutions presented in the thread and I'll come back and report if anything worked. I would also appreciate any other suggestions that you may have
For the record, I got into this predicament through the following steps:
1. I was flashing some CM nightly (sorry, I don't remember which one), and after reboot the touch screen didn't work anymore
2. I flashed the OxygenOs .zip that I had saved on internal storage through TWRP
3. After flash touch screen worked but no sim detected
4. Flashed CM 12.1 still no sim
5. Flashed back to OxyOs, still no sim. Curiously I am unable to reboot via software.
Anyway, I basically have all weekend to work on this, so awayyyy we go!
---
<Edit>
Wow that was fast. I followed this guy's instructions (fastboot flashing modemst, then CM12.1) and it seems to be working like a charm! Good luck everybody else!

gersa said:
Did U flash over TWRP or ADB?
Click to expand...
Click to collapse
I flashed via TWRP(2.6.8.0) and via ADB for modemst1.bin and modemst2.bin.
By the way, there's a little improvement : I flashed kalkulin's_stock_OPO Rom and that stopped my phone from rebooting.
Now cm13 is running kinda fine, except it still doesn't detect SIM card, even after reflashing modemst1 and modemst2
Edit : When I try to flash oxygenos, oneplus fix or cm12.1, (roms that are supposed to fix sim detection problem), it doesn't work : Error flashing Zip file. via adb or twrp, that's the same. (excepting the fact that error in adb is about trustzone)
I think my efs partition is somehow corrupt, and unfortunately i have no way to restore it.

MethylHaine said:
Thanks for the link. I tried to flash the zip, but twrp(2.8.6.0) gave me an error : Error flashing ONEPLUS+ONE-FIX-Windows.zip
I tried to clean flash it and dirty flash it, nothing seems to work.
Click to expand...
Click to collapse
It's not supposed to be flashed. Unzip the archive on a Windows PC, then use the .bat files in there to fix your phone.

jp.esteban said:
It's not supposed to be flashed. Unzip the archive on a Windows PC, then use the .bat files in there to fix your phone.
Click to expand...
Click to collapse
Effectively, I kinda did things completely wrong there, sorry. (I'm an exclusive linux user for my defense ^^)

Okay guys, I finally solved my problems.
Here's what I did to fix reboot crashes and SIM detection issues :
-Flash TWRP(2.8.6.0)
-Wipe everything except internal storage
-Flash Calkulin's_Stock_OPO_XNPH44S_ROM_v1.0.zip (can't post links yet, sorry)
-Boot system
-Once done, reboot to bootloader (in command prompt : sudo adb reboot bootloader)
-In command prompt, type the following commands (It will delete modem and /persist partition ! be careful) :
fastboot erase modemst1
fastboot erase modemst2
fastboot erase persist
-If you need to fix "Unable to mount /persist" error in TWRP :
adb shell
make_ext4fs /dev/block/mmcblk0p15
-Flash Oxygen OS (i flashed oxygen_1.0.0_flashable.zip)
That should restore EFS and fix the issues.
Well, that was kind off a pain in the ass, but now my problem is solved, and i'm currently running cm13 quite fine.
Make a backup of your EFS partition.
Thanks to all the people that helped me by posting in this thread !

It's a nightly build, it bound to have some problems.

i am having bootloop issue, tried many roms, erased partition too, still no use. continuous bootloops
---------- Post added at 03:08 AM ---------- Previous post was at 03:07 AM ----------
gersa said:
`
Here is solution (for me)
http://forum.xda-developers.com/showpost.php?p=64768887&postcount=3
Read whole, its short
Click to expand...
Click to collapse
i am having bootloop issue, tried many roms, erased partition too, still no use. continuous bootloops

oneplus6 seems damaged following a failed twrp restore

So here is situation.
Phone been running 8.x version of havocos for months, however I was never fully happy due to broken usb tethering and random lockups (blue light freeze).
I decided to work on the phone 2-3 days ago, this involved doing a manual backup of all of data/media, and a nandroid backup. As well as some exports of configs in tasker etc.
I then flashed OOS stock, and nolimits, discovered tethering was still broken (yet it works with same sim in samsung galaxy s7 and hauwei).
This was the only issue tho, everything else was functioning as expected, phone was still fast.
Then I needed quick access to something that was on my phone from havocos, so decided to do a nandroid restore, this nandroid backup had all partitions ticked. The restore I also had all ticked.
The restore failed with an error 255 during data restore, I googled and found out is a nasty known bug for 2 years on TWRP, this backup was done on 3.2.3, I know now is a newer 3.3.x where this particular bug with corrupt backups might possibly be fixed.
I decided to try and boot havoc anyway but it boot looped, so I then went back into TWRP, and restored the vendor partition which was skipped. As it stopped on data, still boot looped, but also now this created a device is corrupt error on every rom boot even on stock OOS.
I spent ages trying to fix this error and during the process, discovered my phone no longer can be detected in flash boot as a com device in windows so currently the phone cannot be used with the MSM tool.
Eventually I reflashed stock using a flash-all script from here, and also put back on twrp using that script, and noticed even more issues that were not there before.
1 - phone is now much slower, stock before booted in one second after first boot, now its way way slower. Over 10 seconds so 10x as slow.
2 - I think before was a cache partition but is now gone. Supposedly these arent a thing anymore tho.
3 - nolimits zip will no longer flash with an error 1, I did exact same process as before but simply doesnt work now, the twrp detailed log right before the error 1 says "Please install the latest Magisk!" which suggests its failing to detect magisk.
4 - camera app is way slower, and OOS feels slower, laggier in general than before the problem.
5 - MTP no longer works when phone is booted up, again this is stock OOS and even if phone isnt rooted no magisk etc. But still works in TWRP. Basically the device pops up, I can see internal storage, but the size information is missing, and is no visible files/folders.
From what I can see I think my EFS is fine, I see an imei number.
I did fix the corrupted device error using a reboot command someone posted in that thread, so that error is gone now at least.

Try to flash oxygen os beta version from the official download links, let it install the stock recovery, then boot into rom, finish the installation progress by just skipping it and then factory reset it twice from recovery mode.
after doing that and finishing the setup , try to take picture and see if its saves it to gallery ( if the picture delete it self try to factory reset it through recovery for 1 more time)

I think you have figured out whats wrong, it just clicked, and I went to post and found your post so sorry no reply yet.
Indeed the problem seems to be a lack of /data/media/0
I have multiple times wiped data, and twrp has been putting files directly in /data/media, I just discovered I Cannot even take screenshots, magisk cannot download modules as well.
So I guess the stock recovery creates this structure?
Pretty shocking that twrp doesnt fix this or even have an option to. I will report back and let you know how things go, thanks.

Issue still there after stock recovery reset, wow these phones are damn hard to work with.
Also it seemed to do nothing, no settings were lost etc.

So basically stock recovery even if I choose full wipe does nothing, there seems to be some kind of lock on the internal storage that anything made by one plus is refusing to write.
I wonder if this is due to the device is corrupt message I had before where it said the device can no longer be trusted.
I can confirm that files that are on there are now visible in file manager and root explorer. But file manager can do no writes. root explorer can create new stuff but cannot delete or overwrite anything there, gets access denied.

I propose to start over again following this guide, option flash-all-partitions.bat. Helped for me.

I already stated thats already been done.
I eventually got msm working. and that luckily worked.

@chrcol ..., but you've issues

chrcol said:
I already stated thats already been done.
I eventually got msm working. and that luckily worked.
Click to expand...
Click to collapse
In recovery, format data. Problem fixed. Wipe will never fix your problem but format will.

One partition/slot corrupted(?)

One of my slots/partitions does not work anymore. Both should have the same OOS with blue_spark kernel and his TWRP mod - but slot A doesn't boot (stuck on the "bootloader unlocked" warning screen, doesn't reboot as far as I can tell) and when I have it active, the recovery doesn't prompt me for my PIN - and all user data is still encrypted. Slot B works flawless though.
(It's been like that for a few months already, I just forgot about it since I haven't rebooted my phone in a while.)
What course of action should I take?
I've looked before and found this thread - https://forum.xda-developers.com/oneplus-6/help/bootloop-one-partitions-t3809859
But honestly, I'm not sure if it's the same issue. I can't tell if it's bootlooping and I assume it isn't, since it's stuck on the warning.
Not very sure how I managed to do this exactly but I think it's because I forgot to remove my fingerprint lock etc. before flashing a new custom rom (or because I removed it directly after and switched partitions unintentionally? I have no clue anymore)
I've back most of my important data up, so I'd be open to basically reset everything, if that's the only way.
Would the appropriate way about this be to just go into recovery and tell it to wipe everything?

Use the MSM tool to flash a fresh image onto your phone. Then, once you're booted, flash an ota image (this will be flashed onto the other slot) via the oneplus local system update option.
This should work as I have faced your issue a couple of times while changing roms.

Personally I would just start fresh and use the MSM tool. Read a post somewhere on Reddit yesterday when I was in the same boat and some guy said you could clone slot A with B and vice versa using TWRP or some Motorola based tool, but seeing as it would have been quicker and cleaner to just do it the MSM route, I went for that.

It sounds like a security patch incompatibility. I don't think there's any way to fix it besides reformatting that slot. You will of course lose all your data.

Can someone fix the pain in the butt A/B slot crap?

my god the A/B slot thing is a *****. has anyone rooted their tmobile and has no issues restarting it. This thing is sensitive. I lose sim when it starts on A slot. Someone needs to make an mega guide just on the A/B crappy thing. Can someone delete or combine both sluts, i mean slots?

I can understand your frustration, it is a bit odd but that's how it is we all have to live with it. One thing I have learnt is never switch slots manually let the phone select the slot itself, also the first thing I do is decrypt the phone, keep in mind you will loose all data on internal drive when you decrypt your phone, I don't have a tmobile but a European oneplus 7 pro, bootloader unlocked, decrypted, twrp, rooted, have tried all the roms in the thread, never switched slots manually and I have never ran into any problems, hope this helps, cheers.

vtec303 said:
I can understand your frustration, it is a bit odd but that's how it is we all have to live with it. One thing I have learnt is never switch slots manually let the phone select the slot itself, also the first thing I do is decrypt the phone, keep in mind you will loose all data on internal drive when you decrypt your phone, I don't have a tmobile but a European oneplus 7 pro, bootloader unlocked, decrypted, twrp, rooted, have tried all the roms in the thread, never switched slots manually and I have never ran into any problems, hope this helps, cheers.
Click to expand...
Click to collapse
Hey thanks. I read a good A/B slot guide and i get it. I haven't decrypted but i should of before i transfered stuff. Its interesting, i now sense what is happing with the slots and which one is having a problem. Call me the slot whisperer lol. Great to hear that you dont have problems. Awesome phone.

trueiceman said:
Hey thanks. I read a good A/B slot guide and i get it. I haven't decrypted but i should of before i transfered stuff. Its interesting, i now sense what is happing with the slots and which one is having a problem. Call me the slot whisperer lol. Great to hear that you dont have problems. Awesome phone.
Click to expand...
Click to collapse
Thats great news, enjoy your phone, all the best, cheers

vtec303 said:
Thats great news, enjoy your phone, all the best, cheers
Click to expand...
Click to collapse
Thanks. Some questions if you don't mind.
1) can we flash everything- cust rom, gapps, twrp and magisk) on one slot and do the exact thing for the other slot?
2) why can"t we delete system and vendor when flashing a custom rom? I have done that with all other phones in the past.
Thanks..

trueiceman said:
Thanks. Some questions if you don't mind.
1) can we flash everything- cust rom, gapps, twrp and magisk) on one slot and do the exact thing for the other slot?
2) why can"t we delete system and vendor when flashing a custom rom? I have done that with all other phones in the past.
Thanks..
Click to expand...
Click to collapse
On these phones wiping system and vendor renders it non bootable, everything gets wiped the phone might still boot in fastboot/bootloader or might get bricked, so don't wipe it.
Most of the ROMS and other flashable scripts get flashed on both slots anyway you don't have to manually switch slots and flash twice, I have never switched slots or flashed any script twice. When you flash twrp watch it flashing it will say running script on slot A and after a few seconds slot B. And yes you can flash everything on both slots but it has to be the exact same ROM and scripts. May be cos I'm decrypted I don't need to flash every file/script twice manually, don't have any experience of encrypted phone. Hope this helps, cheers.

The solution to A/B slot s to make sure both are on the same version of OS.
If not the settings between the two may be different. The system partitions are different, but the shared partitions hold settings.
Make both slots boot on the same version of the OS and you will not have issues.

vtec303 said:
On these phones wiping system and vendor renders it non bootable, everything gets wiped the phone might still boot in fastboot/bootloader or might get bricked, so don't wipe it.
Most of the ROMS and other flashable scripts get flashed on both slots anyway you don't have to manually switch slots and flash twice, I have never switched slots or flashed any script twice. When you flash twrp watch it flashing it will say running script on slot A and after a few seconds slot B. And yes you can flash everything on both slots but it has to be the exact same ROM and scripts. May be cos I'm decrypted I don't need to flash every file/script twice manually, don't have any experience of encrypted phone. Hope this helps, cheers.
Click to expand...
Click to collapse
Oh i see. Thanks so much. Its just frustrating when restarting the phone only to have the sim not detected. When i wipe cache and switch slots it usually comes back. I hate the sensitivity of losing sim. Im still trying to find the best install method.

tech_head said:
The solution to A/B slot s to make sure both are on the same version of OS.
If not the settings between the two may be different. The system partitions are different, but the shared partitions hold settings.
Make both slots boot on the same version of the OS and you will not have issues.
Click to expand...
Click to collapse
Yeah both have the same versions. I cant wait till this thing behaves like a normal solid phone. Thanks.

Question Xiaomi Poco X3 Pro is constantly rebooting itself to recovery mode:

Hello,
About two months ago I successfully rooted that phone through Magisk. Now I am facing the told problem. I searched for some problems like mine, but it is not because of updates. I do not remember I have done something dangerous for the system. However, I tried to install this package. When I tried with the Android package installer, I got an error "it could not be installed". Then I tried to do it through this app manager for rooted devices, and it just stayed loading for a while until I just closed it. I entered the custom app manager and I realized that the app was recognized as an installed app, but however, I could not see it in the poco app launcher. I launched the app and it worked fine, but when tried to make f-droid a system app it displayed an error "/ directory could not be remounted as read-write". I left it be and removed that app. Everything fine... But the next morning the phone was asking for the SIM unlocking code. I unlocked both, the SIM and the phone, but after about five minutes it rebooted to MIUI recovery 5.0. If once in recovery mode the phone is inactive for a while, it automatically reboots to system. The rebooting time once unlocked the SIM was decreasing to two minutes. Apparently, it only will reboot if the SIM is unlocked, and the time is five minutes when the phone is cold and it decreases as it is being restarted. The phone it is not too hot when rebooted.
Thank you if you spent your time by reading the text above. Now the question: How can I fix it without losing my data? Regards.
PD: I do not have enough time to make a backup till it is rebooted, at least from system, and safe mode did not solve the issue.

You tried to install an obsolete app for moving apps to system, an app from 2016... no less?! What were you thinking?
Let me be honest and tell you that that move was extremely stupid. Chalk up your mistake to a brain fart, take the loss and try to reflash the firmware without formatting anything prior to doing so. Leave internal storage, dalvik, cache and everything else untouched. You just might make the phone bootable to backup your data, and then do a PROPER flash procedure.

Tomo123 said:
You tried to install an obsolete app for moving apps to system, an app from 2016... no less?! What were you thinking?
Let me be honest and tell you that that move was extremely stupid. Chalk up your mistake to a brain fart, take the loss and try to reflash the firmware without formatting anything prior to doing so. Leave internal storage, dalvik, cache and everything else untouched. You just might make the phone bootable to backup your data, and then do a PROPER flash procedure.
Click to expand...
Click to collapse
So therefore, which partition should I reflash with the stock ROM?

MxtApps said:
Hello,
About two months ago I successfully rooted that phone through Magisk. Now I am facing the told problem. I searched for some problems like mine, but it is not because of updates. I do not remember I have done something dangerous for the system. However, I tried to install this package. When I tried with the Android package installer, I got an error "it could not be installed". Then I tried to do it through this app manager for rooted devices, and it just stayed loading for a while until I just closed it. I entered the custom app manager and I realized that the app was recognized as an installed app, but however, I could not see it in the poco app launcher. I launched the app and it worked fine, but when tried to make f-droid a system app it displayed an error "/ directory could not be remounted as read-write". I left it be and removed that app. Everything fine... But the next morning the phone was asking for the SIM unlocking code. I unlocked both, the SIM and the phone, but after about five minutes it rebooted to MIUI recovery 5.0. If once in recovery mode the phone is inactive for a while, it automatically reboots to system. The rebooting time once unlocked the SIM was decreasing to two minutes. Apparently, it only will reboot if the SIM is unlocked, and the time is five minutes when the phone is cold and it decreases as it is being restarted. The phone it is not too hot when rebooted.
Thank you if you spent your time by reading the text above. Now the question: How can I fix it without losing my data? Regards.
PD: I do not have enough time to make a backup till it is rebooted, at least from system, and safe mode did not solve the issue.
Click to expand...
Click to collapse
flash the stock firmware with miflashtool and select de option "save_user_data" and done, the firmware will be flashed and your data will stay there

tutibreaker said:
flash the stock firmware with miflashtool and select de option "save_user_data" and done, the firmware will be flashed and your data will stay there
Click to expand...
Click to collapse
OK, that flash was successful, the root and the custom recovery were lost, but it is still rebooting. Should I flash all?

MxtApps said:
OK, that flash was successful, the root and the custom recovery were lost, but it is still rebooting. Should I flash all?
Click to expand...
Click to collapse
if you flash all your data will be lost, any way to install custom recovery and save your data from it ?