When I initially went to unlock the bootloader, I encountered an issue, which I did not record anywhere. (Don't remember what it was.) In the end, I was able to update the recovery to the newest available version used here. I could install the Lineage OS roms and I did, except the internal memory was decreased to something like 600mb.
I don't remember what I did from there, but I think I tried to load a scatter file over and flash that. Evidently I barely have a grip on what I'm discussing. I would like to salvage this phone. Its currently showing 0mb for internal storage. Not sure how I can flash a rom over that.
I need to fix the partitioning, but I don't know how and I don't know what to do. Please help. The bootloader is unlocked and not secure.
razz0z said:
When I initially went to unlock the bootloader, I encountered an issue, which I did not record anywhere. (Don't remember what it was.) In the end, I was able to update the recovery to the newest available version used here. I could install the Lineage OS roms and I did, except the internal memory was decreased to something like 600mb.
I don't remember what I did from there, but I think I tried to load a scatter file over and flash that. Evidently I barely have a grip on what I'm discussing. I would like to salvage this phone. Its currently showing 0mb for internal storage. Not sure how I can flash a rom over that.
I need to fix the partitioning, but I don't know how and I don't know what to do. Please help. The bootloader is unlocked and not secure.
Click to expand...
Click to collapse
I have had similar issue , with loosing use of internal storage, normally , on my other devices it could be fixed by doing "format data" either in fastboot or twtp. But I found that sometimes that is not working. What I did , and what I suggest you to try, is to fastboot boot stock-recovery.img, then do factory reset.
mrmazak said:
I have had similar issue , with loosing use of internal storage, normally , on my other devices it could be fixed by doing "format data" either in fastboot or twtp. But I found that sometimes that is not working. What I did , and what I suggest you to try, is to fastboot boot stock-recovery.img, then do factory reset.
Click to expand...
Click to collapse
I don't think I can format the data partition right now, but I will check and try that as soon as the phone charges again. I've been trying and sort of giving up, because I have a lot to learn about the basics before I can actually fix anything without any help. Fastboot mode and then how do I boot the stock-recovery.img? Where do I get that?
Do you mean from a stock rom? Should I allow TWRP to enable read-only mode, because I think it said that it may overwrite TWRP with the stock recovery? Sorry for the ignorance, I'm trying to figure out what I can without help, but I've never been this deep. I've always managed to do these things correctly in the past, without having an extensive understanding of the filesystem or what a kernel is or a bootloader.
Thanks for replying, thanks for your work on the roms here too, by the way.
razz0z said:
I don't think I can format the data partition right now, but I will check and try that as soon as the phone charges again. I've been trying and sort of giving up, because I have a lot to learn about the basics before I can actually fix anything without any help. Fastboot mode and then how do I boot the stock-recovery.img? Where do I get that?
Do you mean from a stock rom? Should I allow TWRP to enable read-only mode, because I think it said that it may overwrite TWRP with the stock recovery? Sorry for the ignorance, I'm trying to figure out what I can without help, but I've never been this deep. I've always managed to do these things correctly in the past, without having an extensive understanding of the filesystem or what a kernel is or a bootloader.
Thanks for replying, thanks for your work on the roms here too, by the way.
Click to expand...
Click to collapse
Use the stock recovery linked in this linked thread.
https://forum.xda-developers.com/showpost.php?p=73290731&postcount=8
there is also directions in the same linked thread , few posts down on how to fastboot boot recovery image.
once booted, try to do factory reset, hopefully it formats your data partition for you.
Related
My phone is f'd up.
I tried installing Liquid Smooth 6/10 version, and I got nothing but system UI FC's over and over. So, I held power and volume up until the screen rebooted, and then volume down to get to bootloader.
Then, I selected recovery from there. When I got into recovery, there was nothing in the internal memory, so I did the "fix" where you type in adb on your computer. Every thing went well, I suppose, but when I tried to reboot, it went to the splash screen and did nothing else.
Well, I went back into recovery to restore a backup, a stock Sense back up, and TWRP rebooted. It has been doing this every time I try to get into recovery. I can't do anything. I even installed a previous TWRP by going into bootloader and using an SD converter card with my PC, because ADB doesn't even recognize the device anymore.
I was using Cpt Throwbacks recovery, the newest one, and then I tried reverting to an older one.
Any help....PLEASE!?
Have you tried formatting data and internal storage?
Do you have a recovery log?
Captain_Throwback said:
Have you tried formatting data and internal storage?
Do you have a recovery log?
Click to expand...
Click to collapse
I tried redoing a wipe of dalvik, cache, system, and data....have not tried to do internal, but it reboots before it finishes anyway.
I will try again to do internal.
mcwups1 said:
I tried redoing a wipe of dalvik, cache, system, and data....have not tried to do internal, but it reboots before it finishes anyway.
I will try again to do internal.
Click to expand...
Click to collapse
Sounds like an RUU might be in your future. Some partition(s) seem to be corrupted.
Captain_Throwback said:
Sounds like an RUU might be in your future. Some partition(s) seem to be corrupted.
Click to expand...
Click to collapse
Capt, I did this "fix".
http://forum.xda-developers.com/showthread.php?t=2773203
Could this mess up my partitions?
mcwups1 said:
Capt, I did this "fix".
http://forum.xda-developers.com/showthread.php?t=2773203
Could this mess up my partitions?
Click to expand...
Click to collapse
I honestly don't know. If you used that command I assume you also had the random encryption issue, which could mean you have a different problem altogether.
Did you try using the partition repair options in TWRP?
Captain_Throwback said:
I honestly don't know. If you used that command I assume you also had the random encryption issue, which could mean you have a different problem altogether.
Did you try using the partition repair options in TWRP?
Click to expand...
Click to collapse
I will try partition repair, but is that on the newest version only?
I can still get into bootloader, and when I plug it in to my computer, it still makes the connection sound, but recovery will not stay active. After about 10 seconds, it reboots to splash screen, but goes no further because I don't believe there is anything installed now.
Well, it won't stay in TWRP long enough to do anything. My internal is there now at least. I just don't get it.
Running RUU as we speak. I hope that since I have the .13 firmware installed, that it won't mess up.
Wow. Again.
I made a mistake by doing a backup, then trying to install another ROM, but forgot to wipe data. Went through the process (splash screen, boot animation, updating apps) and it booted for a second and rebooted. I figured it would happen, since I didn't wipe correctly.
Try to go into TWRP, and the damn thing reboots out of TWRP! I can't stay in TWRP for more than 5-7 seconds, before it reboots on its' own. Went to flashboot to reinstall TWRP, no change. I can't even do a restore.
I know I installed a ROM once through fastboot with a "fastboot flash zip rom.zip" command, but that isn't working either. Can't get a log, because I can't stay booted in anything other than fastboot/bootloader.
I searched for an answer, and this is all I got! My phone must be borked. Guess I'll have to RUU again.
I had this issue last night and I got it to restore a backup by unplugging it from the wall first. I think the voltage is too high or something during a flash or something.
mcwups1 said:
I know I installed a ROM once through fastboot with a "fastboot flash zip rom.zip" command, but that isn't working either. Can't get a log, because I can't stay booted in anything other than fastboot/bootloader.
Click to expand...
Click to collapse
You can't install a custom ROM this way, unless it's been built into an image file. This is only for flashing image files that have been zipped up with an android-info.txt file.
Have you tried updating firmware, then booting back into recovery?
Captain_Throwback said:
You can't install a custom ROM this way, unless it's been built into an image file. This is only for flashing image files that have been zipped up with an android-info.txt file.
Have you tried updating firmware, then booting back into recovery?
Click to expand...
Click to collapse
I already RUU'd, so I should have had the appropriate firmware.
mcwups1 said:
I already RUU'd, so I should have had the appropriate firmware.
Click to expand...
Click to collapse
I was suggesting flashing the firmware to normalize your device, so that maybe you could get back into recovery. I wasn't suggesting it because I thought you were on the wrong firmware.
Captain_Throwback said:
I was suggesting flashing the firmware to normalize your device, so that maybe you could get back into recovery. I wasn't suggesting it because I thought you were on the wrong firmware.
Click to expand...
Click to collapse
I ended up RUU'ing again.
If it happens again, I will take your advice and report back.
A lot of dual sim users complain that their phone doesn't boot after installing cwm. I think this is caused by cwm wiping the misc partition. This is based on this post in the ultimate thread.
It is however not a very practical solution, since you have to do every time you access cwm. Instead I tried to prevent cwm from wiping your misc partition, by outcommenting the misc partition in the fstab file.
But, since I don't have don't have the dual sim model, I need someone (experienced, who knows how to fix a bootloop) to test if it works.
I need someone with a filled in misc partition (when entering fastboot, the OS- must be filled in), hboot 1.03 who won't freak out if the phone bootloops.
Multiple people confirmed that it works. I think you can safely try it, but still: everything at your own risk.
Steps:
1. Make sure you have filled in misc partition. This can be done by flashing a firmware.zip, check part 2 of this post: http://forum.xda-developers.com/showpost.php?p=53901933&postcount=6
2. Install the cwm image from below
3. check if the bootup problem is fixed, and check if you have other problems
Cwm_no_misc_wipe.img (hboot 1.03)
https://www.dropbox.com/s/g8g06wi5ipiw9cb/recovery_cwm_no_misc.img?dl=0(hboot 1.02 and below)
Hmm, would flashing the ZIP from the post you linked be enough to fix the /misc partition, so that I can test your CWM? (I'm not afraid of a boot loop as long as I can still go into fastboot)
Bogdacutu said:
Hmm, would flashing the ZIP from the post you linked be enough to fix the /misc partition, so that I can test your CWM? (I'm not afraid of a boot loop as long as I can still go into fastboot)
Click to expand...
Click to collapse
Yes that would be enough, you do however need to be S-off
I don't have s-off
Sent from my HTC Desire 500 dual sim using Tapatalk
Okay, I got the ZIP from the post you linked and installed the recovery from the first post, it works perfectly now (no more issues with booting after power off). Thanks!
Bogdacutu said:
Okay, I got the ZIP from the post you linked and installed the recovery from the first post, it works perfectly now (no more issues with booting after power off). Thanks!
Click to expand...
Click to collapse
Good!
Hope it also fixes for people who's phone barely boots at all.
For this recovery "cwm_no_misc_wipe .img" do i have to be s-off?
kiddoo said:
For this recovery "cwm_no_misc_wipe .img" do i have to be s-off?
Click to expand...
Click to collapse
Not for the recovery.
Just make sure you have a filled in misc partition, else it won't do anything.
I flashed this new recovery and I noticed any difference (seems not working: I still have the same problem after I turn my phone off (power it off); I still have to remove the battery, wait about 15 minutes, put battery back and then I my phone starts normally). Maybe the reason is wiped this misc partition? How can I check it and - if it be needed - repair it?
dummie999 said:
Not for the recovery.
Just make sure you have a filled in misc partition, else it won't do anything.
Click to expand...
Click to collapse
it's a dual sim with unlocked bootloader. didn't trried anything else everything else is stock. is it filled or....?
the OS part is filled with htc release version 1,26,401,2
Ok.
Installed this recovery, SU and ultimate kernel 8 no oc and everything is ok. The phone boots normally. Thank you very much.
I flashed TWRP with unlocked bootloder and its a dual sim with latest software update. So I flashed TWRP and it booted to TWRP but without touch working or any response so i removed the battery and now phone dosent boot up to anything and just a orange led flashes when connected to charger.. I can't even boot to fastboot or Hboot
OK!!!
Great job, it works! Thanks a lot...
Battery got fully discharged phone wont boot
dummie999 said:
A lot of dual sim users complain that their phone doesn't boot after installing cwm. I think this is caused by cwm wiping the misc partition. This is based on this post in the ultimate thread.
It is however not a very practical solution, since you have to do every time you access cwm. Instead I tried to prevent cwm from wiping your misc partition, by outcommenting the misc partition in the fstab file.
But, since I don't have don't have the dual sim model, I need someone (experienced, who knows how to fix a bootloop) to test if it works.
I need someone with a filled in misc partition (when entering fastboot, the OS- must be filled in), hboot 1.03 who won't freak out if the phone bootloops.
Steps:
1. Make sure you have filled in misc partition
2. Install the cwm image from below
3. check if the bootup problem is fixed, and check if you have other problems
Cwm_no_misc_wipe.img (hboot 1.03)
Click to expand...
Click to collapse
It works thanks very much but there is one problem suddenly while i was hanging out i forgot to charge battery and battery was fully discharged..I was lucky that i had in my pocket my secondary symbian nokia and i put my sim into it..When i returned home i connected phone to charge but orange led blinks i charged it about 30min then i used steps to turn on with previous cwm recovery pulling out batt for 10sec and putting back but phone wont boot after waiting 15 min with this cwm no misc..?Plz help
a small question
THANKS A LOT FOR YOUR WORK BUT CAN I KNOW WHAT DID YOU MEAN IN
1-Make sure you have filled in misc partition
would you please explaine this step because i falshed the recovery image normally and nothing change so i think that this is the problem
sensation199290 said:
THANKS A LOT FOR YOUR WORK BUT CAN I KNOW WHAT DID YOU MEAN IN
1-Make sure you have filled in misc partition
would you please explaine this step because i falshed the recovery image normally and nothing change so i think that this is the problem
Click to expand...
Click to collapse
it would be a lot simpler if you actually read the first post (and the two after it), I bet that's what everyone else who has issues now didn't do too.
Bogdacutu said:
it would be a lot simpler if you actually read the first post (and the two after it), I bet that's what everyone else who has issues now didn't do too.
Click to expand...
Click to collapse
i did it and every thing is alright so thanks again it was a huge problem
Hi
My English is poor.
"1. Make sure you have filled in misc partition."
Do mean the misc partition, is the device internal memory ?
Thank you
farzad130 said:
Hi
My English is poor.
"1. Make sure you have filled in misc partition."
Do mean the misc partition, is the device internal memory ?
Thank you
Click to expand...
Click to collapse
The misc partition is stored on you internal memory, yes.
dummie999 said:
A lot of dual sim users complain that their phone doesn't boot after installing cwm. I think this is caused by cwm wiping the misc partition. This is based on this post in the ultimate thread.
It is however not a very practical solution, since you have to do every time you access cwm. Instead I tried to prevent cwm from wiping your misc partition, by outcommenting the misc partition in the fstab file.
But, since I don't have don't have the dual sim model, I need someone (experienced, who knows how to fix a bootloop) to test if it works.
I need someone with a filled in misc partition (when entering fastboot, the OS- must be filled in), hboot 1.03 who won't freak out if the phone bootloops.
Multiple people confirmed that it works. I think you can safely try it, but still: everything at your own risk.
Steps:
1. Make sure you have filled in misc partition. This can be done by flashing a firmware.zip, check part 2 of this post: http://forum.xda-developers.com/showpost.php?p=53901933&postcount=6
2. Install the cwm image from below
3. check if the bootup problem is fixed, and check if you have other problems
Cwm_no_misc_wipe.img (hboot 1.03)
https://www.dropbox.com/s/g8g06wi5ipiw9cb/recovery_cwm_no_misc.img?dl=0(hboot 1.02 and below)
Click to expand...
Click to collapse
didn't fix it on z4dug
HI.
On my rooted 3t i had:
- TWRP 3.0.4-1
- firmware 4.0.3
- ROM RR-N-v5.8.1-20170211
Everything was working great.
I was going through my email when screen went black...
I was not able to turn it on since.
I tried boot to recovery - after few seconds on TWRP flash screen it's not going nowhere... Screen is black and only notification light is white.
Same result when when just starting it.. I see Oneplus logo (powered by Android) and that is it.
Tried to boot into recovery through fastboot with the same result.
Anyone has an idea?
Thank you.
From what you're saying I see that at least the device interacts somehow. Therefore I would suggest trying this --> https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
...no matter how weird and unlucky your situation is
If that won't work then it may be that the Internal memory corrupted
Seems like something went wrong with your internal hardware components. However, try to boot the phone into fastboot mode and try to flash new ROM zip from there with your laptop/pc.
motherninja said:
Seems like something went wrong with your internal hardware components. However, try to boot the phone into fastboot mode and try to flash new ROM zip from there with your laptop/pc.
Click to expand...
Click to collapse
Thank you for responding...
My feeling is the same... Something wrong with hardware.
I did re flash TWRP. TWRP is not loading...
I did try to load TWRP through fastload - same result.
I can (and I think I will) try to flash new ROM but I do not think this would help when even TWRP is not working.
Anyone knows what is warranty situation in my case?
Thank you.
I had the same issue.
Use the unbrick tool. This will help you.
Your problem has nothing to do with hardware.
timobayl said:
I had the same issue.
Use the unbrick tool. This will help you.
Your problem has nothing to do with hardware.
Click to expand...
Click to collapse
Just wondering..
In case of sucessfull unbrick... Does phone would need to be rooted again?
I mean the result is like phone is in original/new state...?
Yes, the phone is like new from the box.
Oos 3.5.4
timobayl said:
Yes, the phone is like new from the box.
Oos 3.5.4
Click to expand...
Click to collapse
The other question is where to go from here... after it is alive again..
What caused that?
Should I go back to
- TWRP 3.0.4-1
- firmware 4.0.3
- latest ROM RR-N-v5.8.1
Thanks
Yes.
For me it works that way.
Maybe its a saver way ota oos Update to 4.0.3.
Than twrp...
TWRP 3.0.4-1 is not restoring internal storage
It is alive...
I ran unbrick tool... and it worked.
Oneplus 3t up and running..
One issue.. TWRP 3.0.4-1 is not restoring DATA completely.
It is showing "Data (excl. storage)" instead of "Data" and not not restoring internal storage (pictures, messages, files).
Anyone knows what to do?
It is the same as before. Nandroid never Backuped the internal storage.
The new twrp show this message to make it ckear for everyone.
What do you think how big is a Nandroid with internal storage?
I was curious, is there anyway to flash the firmware and modem through fastboot instead of TWRP? I accidentally downloaded the OP3 firmware instead of OP3T and then flashed it and well you know how that goes. Thankfully this phone almost impossible to brick even when doing the worst. It shows up in the computer and my bootloader is unlocked, and i was wondering, instead of losing everything and following the unbrick guide if there are actually commands or ways to flash it through fastboot so i don't have to fully wipe the phone? I have TWRP backups that are from yesterday on the phone, so if there was a way to restore that at the very least if i did have to do the full flash then thats fine too. I guess if the unbrick tool didn't wipe out internal storage or something thats fine. Any help is appreciated.
M3drvr said:
I was curious, is there anyway to flash the firmware and modem through fastboot instead of TWRP? I accidentally downloaded the OP3 firmware instead of OP3T and then flashed it and well you know how that goes. Thankfully this phone almost impossible to brick even when doing the worst. It shows up in the computer and my bootloader is unlocked, and i was wondering, instead of losing everything and following the unbrick guide if there are actually commands or ways to flash it through fastboot so i don't have to fully wipe the phone? I have TWRP backups that are from yesterday on the phone, so if there was a way to restore that at the very least if i did have to do the full flash then thats fine too. I guess if the unbrick tool didn't wipe out internal storage or something thats fine. Any help is appreciated.
Click to expand...
Click to collapse
If you're experienced, you can actually flash each individual partition image file back to each partition on your phone using fastboot flash file partition. So yes, if you know what you're doing you could just restore the firmware partitions and you should be back on track. However if you accidentally flash to the wrong partitions you could potentially brick your phone. ?
pitrus- said:
If you're experienced, you can actually flash each individual partition image file back to each partition on your phone using fastboot flash file partition. So yes, if you know what you're doing you could just restore the firmware partitions and you should be back on track. However if you accidentally flash to the wrong partitions you could potentially brick your phone.
Click to expand...
Click to collapse
I'm perfectly comfortable flashing partitions. Done it many times with old HTC's and Nexus's. I just need to know what the actual names of the files are that i'd need to extract from the zips is the other thing.
M3drvr said:
I'm perfectly comfortable flashing partitions. Done it many times with old HTC's and Nexus's. I just need to know what the actual names of the files are that i'd need to extract from the zips is the other thing.
Click to expand...
Click to collapse
Well, I've never really had to do this on the 3t. Last was on an old Huawei mediapad, but you can Google all the partition dumps in the latest full OTA zip, some are self explaining.
hey @M3drvr,
i have now the same problem as you had. i flashed accidentally the wrong firmware file for my op3t and it stucks now at the oneplus booting screen. how did you solved your issue back then? any help is appreciated.
the solution for my problem is to flash the correct firmware via pc - but i dont know how..
mcdachpappe said:
hey @M3drvr,
i have now the same problem as you had. i flashed accidentally the wrong firmware file for my op3t and it stucks now at the oneplus booting screen. how did you solved your issue back then? any help is appreciated.
the solution for my problem is to flash the correct firmware via pc - but i dont know how..
Click to expand...
Click to collapse
With the unbrick tool in the general section.
so i've tried a few roms, and couldn't get gpay working. im going to try a few things mentioned in other threads, but before i start that. i want to properly/fully reset my phone to the stock, to hopefully make sure i don't mess anything up in the future.
my first issue was installing twrp, i tried to `fastboot flash` the recovery, but nothing worked until i followed these steps: https://www.getdroidtips.com/download-and-install-twrp-recovery-for-redmi-k20-pro-latest/
im worried about what might be in the misc.bin in that zip. cuz i couldn't reboot into twrp recovery until i flashed that. does anyone know what that is? i think i just want to flash/reset? everything on my phone back to miui, make sure i update to the latest firmware etc. but, tbh, i find navigating xda difficult and can't seem to find the official firmware anywhere, or steps on how to reset the phone...
thanks for any help
Um, i think ur in the wrong category
thejacer87 said:
my first issue was installing twrp, i tried to `fastboot flash` the recovery, but nothing worked until i followed these steps ...
im worried about what might be in the misc.bin in that zip. cuz i couldn't reboot into twrp recovery until i flashed that. does anyone know what that is?
Click to expand...
Click to collapse
The misc.bin file is basically just a script that tells the Device to directly boot into TWRP, because Xiaomi Devices / MIUI are configured to overwrite TWRP after a reboot. If you still feel uncomfortable having to flash the misc file, try "fastboot *BOOT* TWRP.img" instead of "fastboot *FLASH* TWRP.img".
If you wish to keep MIUI installed instead of an Custom ROM make sure to flash Magisk, as it patches the DM-Verity stuff that causes the Device to either get stuck in a Bootloop or replace TWRP with the Stock Recovery.
If you're planning to run an Custom ROM like LineageOS, AOSiP etc. you don't have to flash Magisk as long as your Device isn't encrypted. Rebooting from TWRP to System without flashing Magisk on an encrypted Device will encrypt your Data Partition and you'll have to format Data to be able to access the Internal Storage again. (Flashing Magisk in that case will prevent your Device from encrypting all your Data again after an ROM Flash.)
Fatal_Scythe said:
The misc.bin file is basically just a script that tells the Device to directly boot into TWRP, because Xiaomi Devices / MIUI are configured to overwrite TWRP after a reboot. If you still feel uncomfortable having to flash the misc file, try "fastboot *BOOT* TWRP.img" instead of "fastboot *FLASH* TWRP.img".
If you wish to keep MIUI installed instead of an Custom ROM make sure to flash Magisk, as it patches the DM-Verity stuff that causes the Device to either get stuck in a Bootloop or replace TWRP with the Stock Recovery.
If you're planning to run an Custom ROM like LineageOS, AOSiP etc. you don't have to flash Magisk as long as your Device isn't encrypted. Rebooting from TWRP to System without flashing Magisk on an encrypted Device will encrypt your Data Partition and you'll have to format Data to be able to access the Internal Storage again. (Flashing Magisk in that case will prevent your Device from encrypting all your Data again after an ROM Flash.)
Click to expand...
Click to collapse
k thanks for the info. what's the difference b/w the boot v flash for twrp?
is the misc.bin from that link i posted safe then? where did it come from? is there a thread here where files like that are posted/talked about?
i definitely plan to stick with either lineage or Pixel experience. i just want to get google pay going. so i think my next attempt will be to relflash magisk and look into that sql fix everyone mentions
thejacer87 said:
so i've tried a few roms, and couldn't get gpay working. im going to try a few things mentioned in other threads, but before i start that. i want to properly/fully reset my phone to the stock, to hopefully make sure i don't mess anything up in the future.
my first issue was installing twrp, i tried to `fastboot flash` the recovery, but nothing worked until i followed these steps: https://www.getdroidtips.com/download-and-install-twrp-recovery-for-redmi-k20-pro-latest/
im worried about what might be in the misc.bin in that zip. cuz i couldn't reboot into twrp recovery until i flashed that. does anyone know what that is? i think i just want to flash/reset? everything on my phone back to miui, make sure i update to the latest firmware etc. but, tbh, i find navigating xda difficult and can't seem to find the official firmware anywhere, or steps on how to reset the phone...
thanks for any help
Click to expand...
Click to collapse
If you're planning to go back to stock MIUI and locked bootloader, I highly recommend using Mi Flash and flashing the original fastboot MIUI ROM which can be found here https://www.xda-developers.com/download-miui-11-xiaomi-redmi-note-7-pro-poco-f1/amp/. All you gotta to do is extract the ROM file which is .tgz to any folder, and in Mi Flash select that folder click on "clean all and lock" in the bottom right corner, and click flash. This should theoretically make your device "out of the box".
Keep in mind that this method requires a PC with all ADB and fastboot drivers, they can be downloaded from here https://forum.xda-developers.com/showthread.php?t=2588979 .
thejacer87 said:
k thanks for the info. what's the difference b/w the boot v flash for twrp?
is the misc.bin from that link i posted safe then? where did it come from? is there a thread here where files like that are posted/talked about?
i definitely plan to stick with either lineage or Pixel experience. i just want to get google pay going. so i think my next attempt will be to relflash magisk and look into that sql fix everyone mentions
Click to expand...
Click to collapse
BOOT will just let the Device temporarily boot into the Recovery (without making changes to the Recovery Partition) FLASH will write the Recovery Image to the Recovery Partition so you can boot to it whenever you want / need to.
I don't know if there's any kind of threads where certain files are talked about sorry, but I could be wrong though.
I don't know much about G Pay, I was gonna try it too but my Bank doesn't support it. I've seen quite a few people reporting success in getting it to work / making payments with it in local stores with the mentioned SQL Fix so if you're lucky it'll work for you too
Fatal_Scythe said:
BOOT will just let the Device temporarily boot into the Recovery (without making changes to the Recovery Partition) FLASH will write the Recovery Image to the Recovery Partition so you can boot to it whenever you want / need to.
I don't know if there's any kind of threads where certain files are talked about sorry, but I could be wrong though.
I don't know much about G Pay, I was gonna try it too but my Bank doesn't support it. I've seen quite a few people reporting success in getting it to work / making payments with it in local stores with the mentioned SQL Fix so if you're lucky it'll work for you too
Click to expand...
Click to collapse
just got gpay to work with the sql fix. thanks for the help