Well, I completely wiped my system. Help appreciated! - Redmi Note 8 Questions & Answers

Hey! First of all thank you all for making this place as awesome as it is! It has helped me incountable times and saved me more than once!
Last night I was trying to root my Redmi Note 8 (ginkgo). Everything was fine. TWRP was working, and I was backing up boot.img to then use it with Magisk when I had the brilliant idea to back everything up in case I messed something up. Before backing up I decided to factory reset the phone so then I could post the stock ROM for people that DID mess it up.
Everything worked out well... Despite the fact that instead of doing a factory reset I completely wiped EVERY SINGLE PARTITION on it, even recovery, modem, everything.
Anyways, the only thing I have access to now is fastboot, which I think should be enough to recover it. I'm right now downloading the last Global Stable ROM I could find to see if I can recover it.
I can't post the URL but the version I found is "V11.0.8.0.PCOMIXM" (MIUI 11, Android 9.0).
My questions are:
Is there any newer stock ROM? Or someone that has posted it in XDADevs?
Does that ROM contain the whole system image? (I literally wiped EVERY partition)
I know I need to make sure that I keep the bootloader unlocked... Right?
Should I go with fastboot straight? Or better stick with Mi Flash Tool?
Is there anything else I should make sure I DO/DON'T?
Anyways, thank you all again for making this such a great place.
Regards!
-fermino-
PS: Xiaomi should really think again about the "the system is destroyed message". It DOES make it look a lot worse than it is hahaha

Happened to me as well... Downloaded stable fastboot, and used mi tool for install. I am now on official tomorrow and unlocked MIUI.

Since you wiped every single partition doesn't that mean you lost imei, wifi Mac adress etc. ?

I suggest you to flash full fastboot ROM. This devices uses SAR and don't wipe system next time.

Related

Phone soft bricked

So I recently had the great idea to root my razer phone after a friend talked me into it, I get the root on but I can't get wifi to turn on, I spend a few hours trying a bunch of different methods to get it working but none of them work. I read magisk can cause an issue, so I delete that and someone says wipe the cache as well in twrp so I do that, switch my slot from b to a and the thing boots straight back to twrp after sitting on the first boot logo for a good 10 minutes. Try the other slot same issue except it boots straight to twrp. So I try and use my backup I made, low and behold its corrupt, at this point I go straight to ****.exe. I try literally everything I can think of and I can't get this thing to take a custom rom, not even a nexbit rom, or a one plus 5t rom. Anyone have any ideas? I've contacted razer and I asked them if there was some way they can fix this without me buying a new phone.
Boltrag said:
So I recently had the great idea to root my razer phone after a friend talked me into it, I get the root on but I can't get wifi to turn on, I spend a few hours trying a bunch of different methods to get it working but none of them work. I read magisk can cause an issue, so I delete that and someone says wipe the cache as well in twrp so I do that, switch my slot from b to a and the thing boots straight back to twrp after sitting on the first boot logo for a good 10 minutes. Try the other slot same issue except it boots straight to twrp. So I try and use my backup I made, low and behold its corrupt, at this point I go straight to ****.exe. I try literally everything I can think of and I can't get this thing to take a custom rom, not even a nexbit rom, or a one plus 5t rom. Anyone have any ideas? I've contacted razer and I asked them if there was some way they can fix this without me buying a new phone.
Click to expand...
Click to collapse
First of all, roms from other phones are not compatible with phones other than what it was designed for. If you tried others, that's why it won't boot up. Secondly, if you read all the posting about how do install twrp, it also said there wasn't any way back EXCEPT for your backups. Unfortunately there is no factory images for the Razer phone released as of yet. If you are unable to restore from your backup (or skipped the step and didn't create one) your only choice is to attempt to restore via the backups Xshooter726 made and posted, and if they don't work, you need to wait till the factory images are released and we don't know when they will be out other then a vague "soon" from a community manager on their forums.
Boltrag said:
So I recently had the great idea to root my razer phone after a friend talked me into it, I get the root on but I can't get wifi to turn on, I spend a few hours trying a bunch of different methods to get it working but none of them work. I read magisk can cause an issue, so I delete that and someone says wipe the cache as well in twrp so I do that, switch my slot from b to a and the thing boots straight back to twrp after sitting on the first boot logo for a good 10 minutes. Try the other slot same issue except it boots straight to twrp. So I try and use my backup I made, low and behold its corrupt, at this point I go straight to ****.exe. I try literally everything I can think of and I can't get this thing to take a custom rom, not even a nexbit rom, or a one plus 5t rom. Anyone have any ideas? I've contacted razer and I asked them if there was some way they can fix this without me buying a new phone.
Click to expand...
Click to collapse
If you're flashing roms for other Devices but now much experience do you have with flashing etc? Ignoring that fact unless backups from other devices work then youve no choice but to wait for razer to put up full factory images in January and flash those. Razer won't help you as you've voided your warranty.
Roxas598 said:
If you're flashing roms for other Devices but now much experience do you have with flashing etc? Ignoring that fact unless backups from other devices work then youve no choice but to wait for razer to put up full factory images in January and flash those. Razer won't help you as you've voided your warranty.
Click to expand...
Click to collapse
I had a decent bit, we only tried to flash another rom after we couldnt find the stock image, it was a last ditch effort.
Boltrag said:
I had a decent bit, we only tried to flash another rom after we couldnt find the stock image, it was a last ditch effort.
Click to expand...
Click to collapse
Well you're lucky none worked it could have made your problem a lot worse. When factory images release you can flash those if the backup doesn't work but until then you're out of luck unfortunately.
Side note if razer ask for imie etc don't give them it. Might be able to list the device as have being unlocked etc.

After OTA upgrade, lost SIM and IMEI

Hey guys,
I just upgraded htc 10 to the latest official version of lineageos, but the installation got stuck in recovery and then I restarted normally.
Unfortunately, I lost the radio signal: no SIM detected! What do you recommend? Can I flash the previous build without encrypt / decrypt issues on partition phone?
I'm on nougat firmware, S-OFF.
Thanks in advance,
Robe
Some details might help .....
RobeStar said:
Hey guys,
I just upgraded htc 10 to the latest official version of lineageos, but the installation got stuck in recovery and then I restarted normally.
Unfortunately, I lost the radio signal: no SIM detected! What do you recommend? Can I flash the previous build without encrypt / decrypt issues on partition phone?
I'm on nougat firmware, S-OFF.
Thanks in advance,
Robe
Click to expand...
Click to collapse
It might be useful to know more specifics about the device we are talking about ? Did you make a COMPLETE Nandroid backup (e.g. with TWRP) before you tried flashing the new image, etc.... What was on it before? What did you (not) wipe prior to attempting the install.... SPECIFICALLY, one could ASSUME a previous LOS build, but assumptions are often dangerous. Also, shouldn't lose the IMEI absent a serious glitch. You CAN blow it away if you wipe the area in TWRP but that would lead to a hope that you also backed it up first. If you CAN, restore what was there before all of this unhappiness began and try again ? Good Luck.
nezlek said:
It might be useful to know more specifics about the device we are talking about ? Did you make a COMPLETE Nandroid backup (e.g. with TWRP) before you tried flashing the new image, etc.... What was on it before? What did you (not) wipe prior to attempting the install.... SPECIFICALLY, one could ASSUME a previous LOS build, but assumptions are often dangerous. Also, shouldn't lose the IMEI absent a serious glitch. You CAN blow it away if you wipe the area in TWRP but that would lead to a hope that you also backed it up first. If you CAN, restore what was there before all of this unhappiness began and try again ? Good Luck.
Click to expand...
Click to collapse
Hi nezlek! You're right: here some useful answer.
Device we are talking about ? HTC 10
Did you make a COMPLETE Nandroid backup ? No... :silly:
What was on it before? lineage-14.1-20180411-nightly-pme-signed.zip
When OTA update has been notified, I installed using the rom tool (not twrp). During the update procedure it stopped in twrp, so I just restarted to system. Then I noticed that the radio did not work anymore...
PS: it's more safer to flash the new build in twrp or continue to use system rom ota update?
Ouch
RobeStar said:
Hi nezlek! You're right: here some useful answer.
Device we are talking about ? HTC 10
Did you make a COMPLETE Nandroid backup ? No... :silly:
What was on it before? lineage-14.1-20180411-nightly-pme-signed.zip
When OTA update has been notified, I installed using the rom tool (not twrp). During the update procedure it stopped in twrp, so I just restarted to system. Then I noticed that the radio did not work anymore...
PS: it's more safer to flash the new build in twrp or continue to use system rom ota update?
Click to expand...
Click to collapse
FIRST - Always better (in my book) to flash with TWRP. Others my have different experiences and opinions but it has never let me down.
You predicament is, in a word, not good. If I were you, I would first try re-flashing the previous Lineage build via TWRP. Unfortunately you are probably going to lose some data in all of this. If anything works well enough to backup your system and data partitions, do that first and move that to removable storage and remove it so it is SAFE. Maybe you have Titanium Backup and can do some of the pieces you need ?? Boot into TWRP and re-flash the build file that was on it before this all started. If that "dirty" flash doesn't give you anything useful, try wiping cache, davlik, etc... and repeating (a full factory reset). If THAT fails, download the zip file(s) - LOS, su-add-on, gapps, etc... and pretend you are doing it for the first time (maybe even wipe data and system but then, your stuff is GONE without a backup). But at this point, what have you got to lose? ASSUMING you get things back to a proper working condition, only then do a complete backup and ponder starting over again. The radio, who knows? Losing the IMEI info is much more of a problem since carriers will often not like that. I know it is trivially easy to restore IMEI data on an MTK device, but yours I have no personal knowledge of. There ARE places that will apparently do it for you if you do a little judicious web searching and are willing to part with a little cash for it, but SOMEBODY out here on XDA has to know how to do it for what you have.
And I'm NOT going to say somebody told you so, but they did. NEVER do this sort of thing without a backup in hand or a willingness to wave goodbye to whatever you have installed on or done to a device. I spend not more than 10 minutes a week doing a Nandroid of devices I use regularly. It has saved me a hell of a lot more time than that the very few times I've needed it. So, with apologies for rubbing salt in the wound, it is always better to have 'em and not need 'em than to need 'em and not have 'em
One thing is pretty certain. Most of us rarely repeat this sort of thing. Good Luck.
Can someone flash My phone without my pin
Even though I encrypted it???
RobeStar said:
Hey guys,
I just upgraded htc 10 to the latest official version of lineageos, but the installation got stuck in recovery and then I restarted normally....
Click to expand...
Click to collapse
I don't have this device but, your best bet is to post this question within the following Official LineageOS thread that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=3528508
If all else fails, and you don't receive any responses from the above thread, you can always try to obtain some member guidance within the following Q&A thread that's specific to your device as well.
https://forum.xda-developers.com/showthread.php?t=3527639
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Yesterday, installing OTA and going from 20191008 to 20191010 destroyed my IMEIs on my Moto X4 payton.
Any idea why this happened?

Problems restoring nandroid backup to new phone

Hi all,
I believe the original motherboard for my RN5 whyred went bad (spontaneous reboots) and so I found a replacement for it - but it is a RN5Pro whyred board. Since they are both whyred, I figured it would be ok to replace the RN5 with the RN5Pro board. The boards look identical and they're both whyred, so why not? Right?
I made a nandroid backup with OrangeFox (9.2.3 I think?), swapped the boards, everything booted great with the new board. I unlocked the bootloader, installed a slightly newer version of OrangeFox (10.0.3) and then restored the nandroid backup. It restored without any errors, but when I tried to boot it - then the problems started. Since there was no logo or anything to see on the screen, I thought I hard bricked it, but MiFlash saw it and I was able to reinstall a stock MIUI 11.0.3 image. Now it boots, but I have a few questions/issues:
1. It doesn't recognize the SIM any more. It did recognize it when I first booted the new board, so I know it's not an issue of the board not recognizing the SIM by nature. Maybe the nandroid restore bonked it? Not sure what I can do at this point besides asking for a replacement SIM. Any ideas?
2. Is it not possible to restore a nandroid backup from the RN5 to the RN5Pro? Or do you have to use the exact same version of recovery to restore that you used to backup? I would really like to not have to reinstall and reconfigure all my programs, which includes 2FA apps that will be a pain to refresh.
Any help is appreciated,
eisenbergw said:
1. It doesn't recognize the SIM any more. It did recognize it when I first booted the new board, so I know it's not an issue of the board not recognizing the SIM by nature. Maybe the nandroid restore bonked it? Not sure what I can do at this point besides asking for a replacement SIM. Any ideas?
Click to expand...
Click to collapse
OK, so I put the SIM in another phone and it works fine. So the problem is somewhere else. Can anyone point me in the right direction? The new board definitely recognized the SIM before I restored the nandroid backup and now after a stock ROM reflash, it doesn't recognize it. Driver?
eisenbergw said:
OK, so I put the SIM in another phone and it works fine. So the problem is somewhere else. Can anyone point me in the right direction? The new board definitely recognized the SIM before I restored the nandroid backup and now after a stock ROM reflash, it doesn't recognize it. Driver?
Click to expand...
Click to collapse
Persist partition and 1 more are corrupted... Search it on xda
drnightshadow said:
Persist partition and 1 more are corrupted... Search it on xda
Click to expand...
Click to collapse
Thanks for the reply. I found some resources for flashing the persist partition. Which is the other partition you suspect of being corrupted, or how can I discover that? Is it the modem partition/non-HLOS.bin? I've already done the regular stock ROM flash through fastboot, so the 'normal' partitions have already been rewritten. What other 'special' partitions are there besides persist?
eisenbergw said:
Thanks for the reply. I found some resources for flashing the persist partition. Which is the other partition you suspect of being corrupted, or how can I discover that? Is it the modem partition/non-HLOS.bin? I've already done the regular stock ROM flash through fastboot, so the 'normal' partitions have already been rewritten. What other 'special' partitions are there besides persist?
Click to expand...
Click to collapse
Ha, you have them CCA 28 partitions. You need to find out by your self. Start with persist, vendor,... Most common ones than less common. Maybe you should try flashing under EDL mode. I would advise you to check which partitions did restored and start there.
drnightshadow said:
Ha, you have them CCA 28 partitions. You need to find out by your self. Start with persist, vendor,... Most common ones than less common. Maybe you should try flashing under EDL mode. I would advise you to check which partitions did restored and start there.
Click to expand...
Click to collapse
Wow, no idea there were that many. I haven't been this deep into the phone before.
I see there is a file called partition.xml in the fastboot images directory, I assume that is the full list of partitions on the phone (but there are 64 entries there)? Do you actually check them all for corruption, or just try to reflash them all until it starts working? Some of them do not have a filename listed. Not sure what to do with those.
<partition label="apdp" size_in_kb="256" type="E6E98DA2-E22A-4D12-AB33-169E7DEAA507" bootable="false" readonly="false" filename=""/>
The 'flash_all.bat' file (that did the flash that got it working again) looks like it flashes 24 images by default, so I guess there aren't too many others to try.
Any links you can refer me to, to understand how to start poking at this? Thanks!
eisenbergw said:
Wow, no idea there were that many. I haven't been this deep into the phone before.
I see there is a file called partition.xml in the fastboot images directory, I assume that is the full list of partitions on the phone (but there are 64 entries there)? Do you actually check them all for corruption, or just try to reflash them all until it starts working? Some of them do not have a filename listed. Not sure what to do with those.
<partition label="apdp" size_in_kb="256" type="E6E98DA2-E22A-4D12-AB33-169E7DEAA507" bootable="false" readonly="false" filename=""/>
The 'flash_all.bat' file (that did the flash that got it working again) looks like it flashes 24 images by default, so I guess there aren't too many others to try.
Any links you can refer me to, to understand how to start poking at this? Thanks!
Click to expand...
Click to collapse
Start with EDL MODE and flash all.... Check and search 1st how EDL MODE works and how to get into it... Read a lot before you'll mess with your phone... for persist you need to patch file (like notepad++), very simple and for the rest like I said read a loooooot..
But if you use OrangeFox recovery than you should only look at those partitions + persist.. For everything else you need research by yourself, sorry no easy way out.
BE CAREFUL DON'T LOCK YOUR BOOTLOADER OR YOU'LL GET EVEN MORE TROUBLES !!!!!
Good luck.
You should be fine flashing 2 files, persist partition and modem file.
Extract the files from the fastboot rom installed in your device.
Please read and document yourself how to flash those files.
Modem file is called "NON-HLOS.bin" and is fastboot flashable.
Persist partition is recovery flashable by OrangeFox.
The best part is that you managed to hardware repair your device! The software part is easy.
Take care and good luck!
Follow @drnightshadow advice also.
MadK9 said:
You should be fine flashing 2 files, persist partition and modem file.
Extract the files from the fastboot rom installed in your device.
Please read and document yourself how to flash those files.
Modem file is called "NON-HLOS.bin" and is fastboot flashable.
Persist partition is recovery flashable by OrangeFox.
The best part is that you managed to hardware repair your device! The software part is easy.
Take care and good luck!
Follow @drnightshadow advice also.
Click to expand...
Click to collapse
Thanks for the info. I tried both items, flashing modem from fastboot and persist from OF, but it didn't change anything.
So I tried an EDL flash, but it won't flash persist.img. It recognizes that it is sparse, but still gives me a 'ERROR_BAD_FORMAT' error and that is the end of that. Reflashed persist.img from OF, no results. Tried a regular stock fastboot-based flash with no tweaks and now it won't flash the modem with the error:
error:FAILED (status read failed (Too many links))
There's really not much left in the images directory that isn't already flashed -
* ddi.elf
* misc.img
* lksecapp.mbn
* uefi.elf (but that looks like a bootsector kind of thing)
My Google-fu is not strong enough to find any mentions of the first three images or what they are used for.
I do note that rawprogram0.xml mentions a lot of partitions that have no files associated with them. I'm a bit wary of just dropping those images into there without a good reason to do so. But again, Google is not helping here.
Any ideas before I toss the phone and go buy a new one?
Oh, man... I'm no expert at all and really cannot help anymore... There are more android experts here then anywhere else on this web and still your issue found no fix. In my opinion you should try to flash the factory image, the rom which your device came. I did encounter the issue when flashing went wrong a few years ago. No other image was flashable! Had errors with more recent ones but when I went and flash the factory image, my RN5 came to life.
MadK9 said:
Oh, man... I'm no expert at all and really cannot help anymore... There are more android experts here then anywhere else on this web and still your issue found no fix. In my opinion you should try to flash the factory image, the rom which your device came. I did encounter the issue when flashing went wrong a few years ago. No other image was flashable! Had errors with more recent ones but when I went and flash the factory image, my RN5 came to life.
Click to expand...
Click to collapse
I did that and it did come back to life... except for not recognizing the SIM.
There is a lot of help here on xda, but I guess even that has its limits sometimes. If you or @drnightshadow don't have any other ideas, then I guess it's time to get a new phone. A shame really, this one lasted me about 3 years and I've had no reason to replace it until now.
No, you tried and accomplished a lot! You should not give up just because of us. We're no experts. Just try to look and search for similar issues but on other brands! Try this approach. And even if you buy a new phone, continue to look for solutions in order to have a RN5 functional again! I remember I even lost imei and all mac addresses for bth and wireless... Not quite like your issue but similar. Only flashing persisit partition brought my device back.
SIM not recognized after flashing at DuckDuckGo
DuckDuckGo. Privacy, Simplified.
duckduckgo.com
L.E.
You could also try to flash persist partition from other rom version, older or newer from stock images... an idea, something else to try...
MadK9 said:
No, you tried and accomplished a lot! You should not give up just because of us. We're no experts. Just try to look and search for similar issues but on other brands! Try this approach. And even if you buy a new phone, continue to look for solutions in order to have a RN5 functional again! I remember I even lost imei and all mac addresses for bth and wireless... Not quite like your issue but similar. Only flashing persisit partition brought my device back.
SIM not recognized after flashing at DuckDuckGo
DuckDuckGo. Privacy, Simplified.
duckduckgo.com
L.E.
You could also try to flash persist partition from other rom version, older or newer from stock images... an idea, something else to try...
Click to expand...
Click to collapse
I'm thinking - I got into this problem because I tried to restore a nandroid backup from the first board to the new board. I'm wondering if there is something like an IMEI or other 'burned in' identifier that got written in and now the phone has a mismatch so the OS won't recognize the SIM as being installed.
Fortunately, before I started doing anything with the new board I did a nandroid backup of what came shipped with it (I unlocked it and put OF on it first, obviously). A bunch of reading I did today made me think about the efs partition - I had restored persist and modem, but not that one. So I did a full nandroid restore of the clean backup, including efs. Rebooted and it went straight to fastboot, would not boot. No problem, used MiFlash to put MIUI 11.0.3 cleanly on it (no tweaks). When it booted after that - the SIM is back! Woo-hoo!
I'm guessing the EFS partition has something to do with it, but I'd have to do more reading to understand it more fully.
In any case, I have a usable board again. *finally*.
For the record (and for anyone else that might have this problem in the future):
* restore original clean nandroid backup (but probably only needed the *efs* partition)
* forced to do a stock rom install via fastboot (used MIUI 11.0.3)
** got use of the SIM again!
* flashed twrp in fastboot to be able to flash OrangeFox from inside twrp
* updated firmware to latest stable v12.0.2
* flash Lineage 18.1
* flash Magisk
* wipe caches and dalvik
* install gapps
* wipe caches and dalvik
* reboot to usable phone
Thanks for being part of the journey!
Sweet, that's nice to hear... Resurrection of whyred wuuuhuuu ..
good job... See, you just don't give up and success is here.. Remember that I told you persist and 1 more partition are corrupted... You find it, EFS
If it isn't hardware problem, whyred can be always unbricked.
Really, really happy for you man!!!
Well done!!!
Yesterday was about to do more research in order to find a way out for your issue but had something else at my job, only downloaded a fastboot rom and was trying to find that troubled partition, even to tell you about efs... And now, the good news from you is that you were busy and had success!!!
Enjoy your zombi phone! I mean resurrected!

Re-Root? Possible partition messup, Lost root now stuck in fastboot

Hello, Sorry to bug you guys...I read multiple different fourms/how2s and I guess I'm a little mixed at what i should do. I Have the oneplus 7t (hd1505) with android 11 rooted, and after that I installed NikGapps after I had it rooted, then flashed nethunter. Was in the terminal as root, all was well..I believe It rebooted and would'nt boot to rom so i went and re'did magisk, may have used a different patched magisk? but now is stuck fastboot. Cant get it to boot.
Sorry for the maybes but I had brain surgry and my memories not the best. Everything was going fine so I didn't document things like normal. Anyways, Is there a program that helps with thiss? MSM somthing? or could anyone please point me in to a nice how2 or some quality links to assist? I really apprricate it, normally I'd just test till I get it, but I think I may be at a point where I could really mess it up.
5k1tz0 said:
Hello, Sorry to bug you guys...I read multiple different fourms/how2s and I guess I'm a little mixed at what i should do. I Have the oneplus 7t (hd1505) with android 11 rooted, and after that I installed NikGapps after I had it rooted, then flashed nethunter. Was in the terminal as root, all was well..I believe It rebooted and would'nt boot to rom so i went and re'did magisk, may have used a different patched magisk? but now is stuck fastboot. Cant get it to boot.
Sorry for the maybes but I had brain surgry and my memories not the best. Everything was going fine so I didn't document things like normal. Anyways, Is there a program that helps with thiss? MSM somthing? or could anyone please point me in to a nice how2 or some quality links to assist? I really apprricate it, normally I'd just test till I get it, but I think I may be at a point where I could really mess it up.
Click to expand...
Click to collapse
If you don't care about data then use msm tools to factory restore. Or you can flash boot image of the rom you were using (unpatched) in fastboot mode itself.
No need to keep data, I'd prefer to wipe device and start fresh instead of getting stuck on the concept of A/B partitions. I get the CMD getvar, but I'm not sure if i flashed the lineage OS to one or both...at 1 point i think i was booted in A, now its saying B. I got overeager and downloaded multiple ROMs and not sure which one worked. In the past I usually downloaded a few and the first one to work I used. Not smart...I know. If I wanted to wipe all and start fresh with gaspps and root, where/how should I do that? I can't just fasatboot oem unlock , could I? Would you recommend stock OS? Lineage? Thanks for your help BTW.
5k1tz0 said:
No need to keep data, I'd prefer to wipe device and start fresh instead of getting stuck on the concept of A/B partitions. I get the CMD getvar, but I'm not sure if i flashed the lineage OS to one or both...at 1 point i think i was booted in A, now its saying B. I got overeager and downloaded multiple ROMs and not sure which one worked. In the past I usually downloaded a few and the first one to work I used. Not smart...I know. If I wanted to wipe all and start fresh with gaspps and root, where/how should I do that? I can't just fasatboot oem unlock , could I? Would you recommend stock OS? Lineage? Thanks for your help BTW.
Click to expand...
Click to collapse
Go to this thread for MSM Tool download and instructions: Unbrick tool to restore your device to OxygenOS

Question How can I recover data from device stuck on starting page?(PE+ ROM)

Recently I dirty flashed PE+ ROM into my moto g40 fusion in a hurry without looking at the developer instructions(which clearly says I should clean flash). So ,now my phone is stuck on starting screen with a faded Google logo.I did not even take any backup(Silly Me)!
But somehow I am able to turn on flashlight by long pressing lock button(It was previously set ). I even hear alarms. I think That means phone is awake but for some reason the display is just a grey Google logo
How to fix this?What should I do?‍
I think performing a factory reset might boot the device.But Can I somehow recover the data?
@arsradu Can you please help me out?
tableware said:
Recently I dirty flashed PE+ ROM into my moto g40 fusion in a hurry without looking at the developer instructions(which clearly says I should clean flash). So ,now my phone is stuck on starting screen with a faded Google logo.I did not even take any backup(Silly Me)!
But somehow I am able to turn on flashlight by long pressing lock button(It was previously set ). I even hear alarms. I think That means phone is awake but for some reason the display is just a grey Google logo
How to fix this?What should I do?‍
I think performing a factory reset might boot the device.But Can I somehow recover the data?
@arsradu Can you please help me out?
Click to expand...
Click to collapse
Hello,
I don't have the phone anymore. So this is general info.
For as far as I know, you can't recover the data. However, Google does automatical backups at regular intervals, if you let it. So...chances are you might already have a backup. You could try to use it after factory resetting your phone.
Something else you could try...is flashing back the older version you had on top of this one. Maybe it will let you boot into it successfully so you can get access to your data. After that, I would suggest taking a backup, if you don't have one already.
And if you want the newer version again, make sure you follow the instructions given by the developer and see if that works.
I'm not aware of any other way.
Yeah, it could be that the phone is alive, but...if you can't interact with it...it doesn't help.
Thank you arsradu for replying..
arsradu said:
Hello,
I don't have the phone anymore. So this is general info.
For as far as I know, you can't recover the data. However, Google does automatical backups at regular intervals, if you let it. So...chances are you might already have a backup. You could try to use it after factory resetting your phone.
Something else you could try...is flashing back the older version you had on top of this one. Maybe it will let you boot into it successfully so you can get access to your data. After that, I would suggest taking a backup, if you don't have one already.
And if you want the newer version again, make sure you follow the instructions given by the developer and see if that works.
I'm not aware of any other way.
Yeah, it could be that the phone is alive, but...if you can't interact with it...it doesn't help.
Click to expand...
Click to collapse
I knew you don't have the phone anymore.I read that in the conversations.But I was kinda desperate.So, Sorry that I bothered you.
I hadn't allowed Google to backup my data except for photos and videos.
Flashing the older version of the rom on top of it was the first thing I tried,But the PE Recovery said the data was corrupted , didn't let me to boot into it and it wanted me to factory reset ‍. So in the hope of keeping the data I reflashed the same rom.
But, the exact same advice from you today gave me an idea.I know the data is intact in the device, If I somehow can backup this ,I might restore it in a clean flashed rom!
So I went through other XDA threads,watched some YouTube videos.
Then I boot it into twrp(again, thanks to your tutorial) took a backup of only data,wiped everything, flashed the previous version and restored the backup.And now I am writing from my own device🥹🥹.
But the problem is partially solved.I lost some important files from internal storage (as expected) .When I tap, I cannot open important settings options like individual app info, developer options,restore and backup etc .I can't swipe down the quick settings menu.When I try to toggle night light the display is just getting dark altogether.
tableware said:
Thank you arsradu for replying..
I knew you don't have the phone anymore.I read that in the conversations.But I was kinda desperate.So, Sorry that I bothered you.
I hadn't allowed Google to backup my data except for photos and videos.
Flashing the older version of the rom on top of it was the first thing I tried,But the PE Recovery said the data was corrupted , didn't let me to boot into it and it wanted me to factory reset ‍. So in the hope of keeping the data I reflashed the same rom.
But, the exact same advice from you today gave me an idea.I know the data is intact in the device, If I somehow can backup this ,I might restore it in a clean flashed rom!
So I went through other XDA threads,watched some YouTube videos.
Then I boot it into twrp(again, thanks to your tutorial) took a backup of only data,wiped everything, flashed the previous version and restored the backup.And now I am writing from my own device🥹🥹.
But the problem is partially solved.I lost some important files from internal storage (as expected) .When I tap, I cannot open important settings options like individual app info, developer options,restore and backup etc .I can't swipe down the quick settings menu.When I try to toggle night light the display is just getting dark altogether.
Click to expand...
Click to collapse
Glad you managed to find a way! Good job!
My suggestion would be to make a backup, while you still can, and do a clean installation of the rom.

Categories

Resources