Took both to get then downgraded to W8.0
The Pro downgraded just fine, and has a recovery partition that I backed up.
The RT, took 3 times, and did not create a recovery partition after reloading.
I did not remove any of my partitions before or after the 8.1 load.
The Tech said if you load RT with 8.1 it destroys the recovery partition, so it only recovers to 8.1
Shameful.
StarLog said:
Took both to get then downgraded to W8.0
The Pro downgraded just fine, and has a recovery partition that I backed up.
The RT, took 3 times, and did not create a recovery partition after reloading.
I did not remove any of my partitions before or after the 8.1 load.
The Tech said if you load RT with 8.1 it destroys the recovery partition, so it only recovers to 8.1
Shameful.
Click to expand...
Click to collapse
Make an RT recovery USB stick and do a full recovery from it (wiping it out). The restore software will ask you whether to repartition.
I'm curious: does the Surface Pro let you disable Secure Boot?
Myriachan said:
Make an RT recovery USB stick and do a full recovery from it (wiping it out). The restore software will ask you whether to repartition.
I'm curious: does the Surface Pro let you disable Secure Boot?
Click to expand...
Click to collapse
if your wondering about installing other OSes on the pro, been done several times now. Its a normal x86 system hardware wise, its just chucked in tablet form factor.
Myriachan said:
Make an RT recovery USB stick and do a full recovery from it (wiping it out). The restore software will ask you whether to repartition.
I'm curious: does the Surface Pro let you disable Secure Boot?
Click to expand...
Click to collapse
Well they did the restore on the RT since the RT was toast, would not connect to anything.
When I got home and tried to run recovery, and got to the screen where you check, to make the USB recovery to write the FULL partition.
Well that box will not let me check it, makes me think the partition is broken.
Hello everyone,
I hope there is somebody out there who can help my Nexus7 -2013 to operate again.
My nightmare started after upgrading Android os to 5.0.2. The tablet started to shutdown from time to time, so i searched for downgrading to an older version but could not find such option on the menu.
Therefore, i followed a youtube video -not knowing what i was doing- and setup TWRP 2.6..0.0 on my tablet. When i opened it again, OS was working but google play and keyboard were not working.
So, i tried to backup, no success. Then i tried all options on TWRP menu (wipe, factory reset etc.) and it got worse.
Currently, when i open the tablet, it takes me to Google logo with a lock, no desktop or OS works. (see picture 1). If i wait long, it takes me to TWRP menu. see pic2)
For the last one week, i tried everything; adb sideload, install, mount etc, nothing solves the problem.
There is no place to run flash commands etc. I connected to computer but only adb sideload works and it does not help me use any other commands.
I had a flash disk with 5.0.2 and 5.0.1 factory images, but it did not setup those two files (and does not see them on flashdisk anymore i do not know why)
I also downloaded twrp 2.6.0.0 and 2.8.5.0 MD5 img's and tried to use but no success, changed file extensions to zip also not worked etc. (see pic3)
Anyway, finally i downloaded alternate rom (CleanROM-5.1.0) and UPDATE-SuperSU-v2.46.
I am trying to setup any of these, just to operate the device.
I install SuperSU (zip1) and CleanRom(zip2) together from install menu and setup was complete (see pic4). CleanRom was setup successfully.
However, when i reboot from TWRP after install it says "root permission appear to be lost..." (see pic4). Whatwer i do, it opens with Google logo and the only place it takes me back is TWRP recovery page.
Your support on this is greatly appreciated.
Thank you
Follow the instructions here. You can transfer installation files in recovery using adb commands or you should be able to copy using Windows Explorer.
http://wiki.cyanogenmod.org/w/Install_CM_for_flo
Or go back to stock using the Nexus images.
Hello everyone!
My oneplus3 is actually running no OS and I'm having a boot loop.
I will try to explain what happened to me with the most details I can.
Before I ****ed everything up, I think I was running OxygenOS 3.28, not really sure about it but im 100% sure it was below 4.0, and it was rooted with TWRP 3.0.2 installed.
1) Today I had a pop up saying OxygenOS 4.0.2 was available (the official one that pops on the screen on boot) "Yay so coooool Nougat!"
1.1) I downloaded it, 1.4Go, then I pressed install
1.2) TWRP showed up, I didn't know what to do and that's where I ****ed up, I set my phone "factory new" in TWRP.
1.3) Phone restarted fresh new, I thought I had 4.0.2 but naaaaah would've been too easy so the official pop up showed again, I was still 3.28 I think.
1.4) Downloaded it once more, TWRP opened again, this time i was looking for the update i just downloaded in the "install" section. I browsed for quite a while and couldn't find it.
1.5) Master ****-up here: I tried to restore a backup. Then the bootloop happened. The black screen with "Oneplus" written in white. I was able to go back in TWRP by pressing power + volume down
1.6) Tried every kind of restore unsuccessfully, and tried ADB but it wouldn't load. Also TWRP said that I was running no OS when I wanted to turn off my phone for example.
2) I downloaded 4.0.2 from one plus website on my mac, and i flashed the official recovery instead of TWRP.
2.1) Transferred the update from my mac to my PC (seems important to me) and installed ADB & everything on both PC/O+3.
2.2) so adb worked in forceboot, i've been able to flash official recovery, tried once more to wipe & everything, but clearly I have no OS now, as TWRP said.
2.3) so i had the update in a folder (not a zip, probably due to the download being done from a mac), I made it a .ZIP with winrar, but "adb sideload update.zip" crashed at 0% everytime
2.4) looked at the archive then i noticed it was first a folder "OnePlus3Oxygen_16_OTA_039_all_1701140133_03b794d8a8b44883" then inside it i had the content like "boot.img" & everything. So i zipped it again but without that first folder because I thought it was the problem, but it kept on crashing 0%.
2.5) restarted my PC, looked on several forums, but i couldn't find any fix. Now adb can't even open update.zip anymore, it fails even before 0%.. I tried naming it .zip.zip, keeping the name "OnePlus3Oxygen_16_OTA_039_all_1701140133_03b794d8a8b44883.zip", using a third party app to allow more RAM to the cmd app...
I've been trying hard for 4 hours but I still have a O+3 without any OS... My last idea is downloading "OnePlus3Oxygen_16_OTA_039_all_1701140133_03b794d8a8b44883.zip" from my PC so it downloads it directly .zip unlike on my mac...
I hope I said everything, sorry for the long post but i'm desperate.. thanks for your attention,
Valentin
Try this guide: https://forum.xda-developers.com/oneplus-3/how-to/guide-flashing-oos-v4-0-1-custom-rom-t3537757
Let me know if it works.
EDIT: See FAQ #1, 2, 4, 12, 14 and 17.
dbabaev21 said:
Try this guide: https://forum.xda-developers.com/oneplus-3/how-to/guide-flashing-oos-v4-0-1-custom-rom-t3537757
Let me know if it works.
EDIT: See FAQ #1, 2, 4, 12, 14 and 17.
Click to expand...
Click to collapse
Thank you for answering! unfortunately i've already tried that and my problem occurs when i try to sideload the update from adb recovery... "couldn't load 'update.zip'"
I dont really know what to do now because I think my only option here is to load the OS through adb as I can't boot my phone to get the update zip inside a specified folder to load it from internal storage.
Try to install the new official TWRP version i think it is 3.0.3-0 through fastboot. Boot up TWRP, wipe every partiton and copy the update.zip onto the phone. You can copy it by connecting it normaly via USB(like you would do in OOS) and install the zip file afterwards.
Sleazy_ said:
Thank you for answering! unfortunately i've already tried that and my problem occurs when i try to sideload the update from adb recovery... "couldn't load 'update.zip'"
I dont really know what to do now because I think my only option here is to load the OS through adb as I can't boot my phone to get the update zip inside a specified folder to load it from internal storage.
Click to expand...
Click to collapse
install stock recovery and then try installing official OS. Or install modded twrp 3.0.2-1.28 and then try installing Freedom OS 2.3 via sideload or through internal storage.
Sleazy_ said:
Thank you for answering! unfortunately i've already tried that and my problem occurs when i try to sideload the update from adb recovery... "couldn't load 'update.zip'"
I dont really know what to do now because I think my only option here is to load the OS through adb as I can't boot my phone to get the update zip inside a specified folder to load it from internal storage.
Click to expand...
Click to collapse
Stop fiddling with the ROM. Download the ROM afresh directly to your Windows PC/laptop. Check the md5. Then start experimenting with the other suggestions but don't again meddle with the ROM!
Sleazy_ said:
Thank you for answering! unfortunately i've already tried that and my problem occurs when i try to sideload the update from adb recovery... "couldn't load 'update.zip'"
I dont really know what to do now because I think my only option here is to load the OS through adb as I can't boot my phone to get the update zip inside a specified folder to load it from internal storage.
Click to expand...
Click to collapse
I read your post again and here are a few things:
* Don't update Stock OOS via "System updates" in Settings if you are rooted and have TWRP
* Back up your data before updating, wiping or doing something with your phone.
* For the ADB error, see the FAQ #17 in the guide I provided.
Now, try this:
Flash TWRP via fastboot > boot to TWRP > connect your phone to your PC and copy the full Stock OOS v4.0.2 OTA to your phone > reboot to fastboot and flash Stock Recovery.
It didn't touch the internal storage. So, try to install from internal storage when you are in Stock Recovery.
Let me know if it worked.
Good morning guys.
I'm not really new to this forum, I've known you for years and I've always followed you for small "mods" or particular problems that I had over time with my devices.
I apologize, but I would like to ask you for help because I have big problems with an ASUS Nexus WiFi 32GB Tablet
Unfortunately, I can in no way connect it to the PC in order to install any rom (I wanted to install the rom stock). I tried everything, I even formatted an old PC and installed windows XP hoping for more compatibility (nostalgic).
The first time, I managed to install a ROM from TWRP recovery 2.8, enabling the USB-OTG and buying the appropriate cable, but then unfortunately, I wanted to try to change ROM and already I was there I wanted to update the recovery to 3.3 .1.0, but I must have been wrong to click somewhere in the recovery. I was convinced that the USB-OTG could always be enabled, so I had the security that I would always be able to install a S.O.
Now the S.O is no longer present in the device and from recovery I can no longer enable USB-OTG, and obviously in the device, no image is present that can help me, probably because I have eliminated everything with different wipes.
The PC in no way manages to see the device, whatever driver I try to install, it tells me that they have no information regarding the connected device, so I can't even use adb.
Please, help me, if needed, format a PC and install Linux or anything else I can use to resurrect this damn device.
Thank you so much for existing ...
Hello, did you try to reboot your tab in bootloader mode, and then install stock factory image from Asus? Maybe After that you will be able to reinstall twrp and custom rom you want... Your tab is unlocked? Did you try the wugfresh tool? Good luck
Thanks for the reply ichi-nii, I tried to reboot the device in bootloader mode (The menu with the open heart robot, Fastboot Mode, right?), Even if it doesn't give me many options, I can only choose whether to Turn off the device, Start it in Recovery (TWRP) or restart the Bootloader, nothing more, and from here I can't install anything anyway.
I believe the device is unlocked, or at least it was, and Fastboot tells me that it is unlocked, so ...
To use the Wugfresh tool, if I didn't err I have to be able to connect this Nexus to the PC and make it see it, but as I said ... No driver allows me to recognize this device from the PC ...
I don't know what to do ...
Isn't there a TWRP terminal way to do something? Some commands that can re-enable the USB-OTG ...
I think I inadvertently (because I didn't know what I was going towards) SELinux enabled, it was after this that the USB-OTG didn't work anymore (I think) ...
Sorry for you bro, so you tell me even in bootloader mode , the tab is not recognized ? Maybe try to connect it when you are in twrp, And another one thing, maybe try another usb port or cable... About otg I can't help you , maybe your connector is broken? Did you try with windows 7 or linux( just to send files to sdcard)
edit: I just try to connect my tab (twrp mode on the screen) to my computer with kali Linux and I Can access to sdcard on the tab
ichi-nii said:
Sorry for you bro, so you tell me even in bootloader mode , the tab is not recognized ? Maybe try to connect it when you are in twrp, And another one thing, maybe try another usb port or cable... About otg I can't help you , maybe your connector is broken? Did you try with windows 7 or linux( just to send files to sdcard)
edit: I just try to connect my tab (twrp mode on the screen) to my computer with kali Linux and I Can access to sdcard on the tab
Click to expand...
Click to collapse
Thank you so much for your help!
I tried to connect the device, both from TWRP and from Fastoboot mode but it is not recognized by Windows ... (Both Windows XP, Windows 7 and Windows 10) I tried to change USB ports and I also tried to change the cable, but nothing ...
The OTG cable is new, I used it on this device and it worked perfectly, I tried it on another device and it works, so the cable is ok, I must have done some **** myself.
Sending any file to the device is just what I'm desperately trying to do, I don't care how, I'm interested in doing it and fixing the damn thing.
If you tell me that your computer with Kali Linux sees it and you can access the memory, I try immediately.
Thank you so much !!
I'm not at all an expert on Linux, how does it work in this case? From Linux terminal? do I have to send commands? Or is it seen as a folder? ....
Forgive my humble ignorance ...
? I'm not an expert too? just install any linux with graphic interface then open the file manager , I did this with kali just because I have it on an old computer.
Good luck
ichi-nii said:
I'm not an expert too just install any linux with graphic interface then open the file manager , I did this with kali just because I have it on an old computer.
Good luck
Click to expand...
Click to collapse
I have to thank you for the help, from Linux I can easily see the device, I managed to insert in the internal memory the rom that I had previously installed ... so I took a big step forward! Unfortunately the misfortune haunts me and the recovery doesn't want to know to install that damn rom. I had to fall back on a Slimroms that I found here on the forum, but I'm not exactly where I want to be. I would like to be able to install my ROM or at most something more complete and updated. Now I try to install the GApps so that I can install some apps that allow me to permanently disable SELinux, then try again to Flash my rom ...
I do not know how to thank you! You have been very helpful.
IgNuReNt said:
I have to thank you for the help, from Linux I can easily see the device, I managed to insert in the internal memory the rom that I had previously installed ... so I took a big step forward! Unfortunately the misfortune haunts me and the recovery doesn't want to know to install that damn rom. I had to fall back on a Slimroms that I found here on the forum, but I'm not exactly where I want to be. I would like to be able to install my ROM or at most something more complete and updated. Now I try to install the GApps so that I can install some apps that allow me to permanently disable SELinux, then try again to Flash my rom ...
I do not know how to thank you! You have been very helpful.
Click to expand...
Click to collapse
Congratulations, like you said it's a big step. Do you use the last twrp? Maybe the problem comes from that...
ichi-nii said:
Congratulations, like you said it's a big step. Do you use the last twrp? Maybe the problem comes from that...
Click to expand...
Click to collapse
I updated the TWRP to 3.3.1.0, I think it is quite up to date, but it is strange that this is so, because from OTG I installed it quietly without problems ... I am convinced that SELinux blocks something ...
I also tried to check the zip file before installation and it gives me an error, it can't install ...
I'm going crazy ... but at least now I have the chance to do tests!
IgNuReNt said:
I updated the TWRP to 3.3.1.0, I think it is quite up to date, but it is strange that this is so, because from OTG I installed it quietly without problems ... I am convinced that SELinux blocks something ...
I also tried to check the zip file before installation and it gives me an error, it can't install ...
I'm going crazy ... but at least now I have the chance to do tests!
Click to expand...
Click to collapse
And now Can you connect the tab to your computer (with windows this Time) If yes you can try install the rom you want from the wugfresh tool?
ichi-nii said:
And now Can you connect the tab to your computer (with windows this Time) If yes you can try install the rom you want from the wugfresh tool?
Click to expand...
Click to collapse
My dear friend! You are an ace, a beast! It was only thanks to you that I was able to solve my problem. Thank you very much, now there is a little 7-year-old who can come back and have fun with this Nexus 7, and of course he also thanks you very much.
I'll tell you briefly how I had to move and the problems I encountered and how I solved it step by step, so that if it happens to someone else, it may have a path to follow eventually.
I was screwed, after I managed to copy the stock image from flash to Kali-Linux inside the Nexus 7, because that damned TWRP crashed during installation without giving me a reason, I had to restart the tablet and that's it; from linux, same speech with ADB Sideload, did not complete the installation.
So I tried to Flashare a custom image, Slimrom that gave me only problems right away, I couldn't touch anything that gave error (but it was installed .. so I was still hoping).
So I tried to flash my damned stock rom directly from Fastboot, but it gave me a thousand mistakes of every kind, from there I suspected that there was something wrong with the file system or the partitions ... something must have messed up something , it was not possible that I could not install any roms anymore, not even the wipe worked, there was something strange, I thought of starting from the base.
So from recovery I found the function that allows you to change File System in the various partitions, so one by one I restored F2FS, the Wipe worked magically, the road was the right one.
I start with the installation of the Stock Rom ... but nothing, errors concerning the lack of files or information (now unfortunately I don't remember in detail)
Reading on the forum, I realized that it could be a common problem and that you could flash the individual files contained in the "stock.img" file that I had downloaded, even individually. So I extracted the archive of the downloaded stockrom, extracted the same .img file inside it, I found myself with all those files.img (boot.img / recovery.img / userdata.img etc etc) at that point I have them flash them one by one with the special fastboot commands.
eeeeeeeeeeeeeeeeeeeee
Taaaaaaaaaaakkkkk
Now it finally starts, it works !!!!!
All this, thanks to you, with that idea of connecting it to linux you gave me hope and it worked !!
I am Italian, from Rimini, if you ever happen in Italy you have a paid fish dinner !!!!!
Thanks again!!!!
IgNuReNt said:
My dear friend! You are an ace, a beast! It was only thanks to you that I was able to solve my problem. Thank you very much, now there is a little 7-year-old who can come back and have fun with this Nexus 7, and of course he also thanks you very much.
I'll tell you briefly how I had to move and the problems I encountered and how I solved it step by step, so that if it happens to someone else, it may have a path to follow eventually.
I was screwed, after I managed to copy the stock image from flash to Kali-Linux inside the Nexus 7, because that damned TWRP crashed during installation without giving me a reason, I had to restart the tablet and that's it; from linux, same speech with ADB Sideload, did not complete the installation.
So I tried to Flashare a custom image, Slimrom that gave me only problems right away, I couldn't touch anything that gave error (but it was installed .. so I was still hoping).
So I tried to flash my damned stock rom directly from Fastboot, but it gave me a thousand mistakes of every kind, from there I suspected that there was something wrong with the file system or the partitions ... something must have messed up something , it was not possible that I could not install any roms anymore, not even the wipe worked, there was something strange, I thought of starting from the base.
So from recovery I found the function that allows you to change File System in the various partitions, so one by one I restored F2FS, the Wipe worked magically, the road was the right one.
I start with the installation of the Stock Rom ... but nothing, errors concerning the lack of files or information (now unfortunately I don't remember in detail)
Reading on the forum, I realized that it could be a common problem and that you could flash the individual files contained in the "stock.img" file that I had downloaded, even individually. So I extracted the archive of the downloaded stockrom, extracted the same .img file inside it, I found myself with all those files.img (boot.img / recovery.img / userdata.img etc etc) at that point I have them flash them one by one with the special fastboot commands.
eeeeeeeeeeeeeeeeeeeee
Taaaaaaaaaaakkkkk
Now it finally starts, it works !!!!!
All this, thanks to you, with that idea of connecting it to linux you gave me hope and it worked !!
I am Italian, from Rimini, if you ever happen in Italy you have a paid fish dinner !!!!!
Thanks again!!!!
Click to expand...
Click to collapse
Yessssss! Congratulations bro ! That's a very good news ?
IgNuReNt said:
My dear friend! You are an ace, a beast! It was only thanks to you that I was able to solve my problem. Thank you very much, now there is a little 7-year-old who can come back and have fun with this Nexus 7, and of course he also thanks you very much.
I'll tell you briefly how I had to move and the problems I encountered and how I solved it step by step, so that if it happens to someone else, it may have a path to follow eventually.
I was screwed, after I managed to copy the stock image from flash to Kali-Linux inside the Nexus 7, because that damned TWRP crashed during installation without giving me a reason, I had to restart the tablet and that's it; from linux, same speech with ADB Sideload, did not complete the installation.
So I tried to Flashare a custom image, Slimrom that gave me only problems right away, I couldn't touch anything that gave error (but it was installed .. so I was still hoping).
So I tried to flash my damned stock rom directly from Fastboot, but it gave me a thousand mistakes of every kind, from there I suspected that there was something wrong with the file system or the partitions ... something must have messed up something , it was not possible that I could not install any roms anymore, not even the wipe worked, there was something strange, I thought of starting from the base.
So from recovery I found the function that allows you to change File System in the various partitions, so one by one I restored F2FS, the Wipe worked magically, the road was the right one.
I start with the installation of the Stock Rom ... but nothing, errors concerning the lack of files or information (now unfortunately I don't remember in detail)
Reading on the forum, I realized that it could be a common problem and that you could flash the individual files contained in the "stock.img" file that I had downloaded, even individually. So I extracted the archive of the downloaded stockrom, extracted the same .img file inside it, I found myself with all those files.img (boot.img / recovery.img / userdata.img etc etc) at that point I have them flash them one by one with the special fastboot commands.
eeeeeeeeeeeeeeeeeeeee
Taaaaaaaaaaakkkkk
Now it finally starts, it works !!!!!
All this, thanks to you, with that idea of connecting it to linux you gave me hope and it worked !!
I am Italian, from Rimini, if you ever happen in Italy you have a paid fish dinner !!!!!
Thanks again!!!!
Click to expand...
Click to collapse
ichi-nii said:
Yessssss! Congratulations bro ! That's a very good news
Click to expand...
Click to collapse
Thanks guys, I stumbled across this thread and changed the file system of System & Data partitions to F2FS (from ext4) and everything seemed to work normally after that. Thank you!
[email protected] said:
Thanks guys, I stumbled across this thread and changed the file system of System & Data partitions to F2FS (from ext4) and everything seemed to work normally after that. Thank you!
Click to expand...
Click to collapse
Congrats
Today i installed LR recovery and rooted my phone then i installed Viper 4 android... everything went well.. at last i uninstalled xiamo sim activation apk because it bothered me every time i reboot my phone... but after uninstalling that my phone is no longer booting up.. it boots to fastboot mode only.. I can manually boot to twrp but my files are also corrupted...
anyway to recover my data? MIUI 11 indonesian rom
You can always try to reinstall the app through adb in recovery mode, maybe then it'll boot. Kind of surprised you can't access your files through recovery mode, thought data decryption worked. There's also the possibility that dirty flashing the entire image on top of your current one will restore the missing apps and allow it to boot. Might want to save that as a last resort.
wang1chung said:
You can always try to reinstall the app through adb in recovery mode, maybe then it'll boot. Kind of surprised you can't access your files through recovery mode, thought data decryption worked. There's also the possibility that dirty flashing the entire image on top of your current one will restore the missing apps and allow it to boot. Might want to save that as a last resort.
Click to expand...
Click to collapse
Unfortunately could not try that i already flashed entire rom to get my phone alived and lost all my data.. but i am still curious why it happened..
Xiaomi security is so high, i regret buying xiaomi instead of samsung..
Btw i also could not find boot from recovery.p file in system folder in LR twrp to replace recovery as instructed there.. do you have any information on that?
Thanks
n70shan said:
Unfortunately could not try that i already flashed entire rom to get my phone alived and lost all my data.. but i am still curious why it happened..
Xiaomi security is so high, i regret buying xiaomi instead of samsung..
Btw i also could not find boot from recovery.p file in system folder in LR twrp to replace recovery as instructed there.. do you have any information on that?
Thanks
Click to expand...
Click to collapse
It's just that there are apk that you should not remove. Look for XiaomiADBFastbootTools, it's a tool designed to disable/enable/uninstall/reinstall Xiaomi bloatware, it doesn't require TWRP or root, just adb, and all the apps there are safe to remove.
antony.ps said:
It's just that there are apk that you should not remove. Look for XiaomiADBFastbootTools, it's a tool designed to disable/enable/uninstall/reinstall Xiaomi bloatware, it doesn't require TWRP or root, just adb, and all the apps there are safe to remove.
Click to expand...
Click to collapse
Thanks for suggestion.. i downloaded Adb flash tools but i cant run it.. it gives error A JNI error has occured... i have latest java already installed in my windows 8.1.. what to do?
Edit: i tried version 6.7 and it opens now, will see what it does
n70shan said:
Thanks for suggestion.. i downloaded Adb flash tools but i cant run it.. it gives error A JNI error has occured... i have latest java already installed in my windows 8.1.. what to do?
Edit: i tried version 6.4 , and the problem is it opens and closes immediately.. what should i do now?
Click to expand...
Click to collapse
I'm using Linux right now, and it only runs on Java 11, maybe it's java version problem? Try to use Oracle Java 11 if Redhat or other OpenJDK distribution doesn't work.
n70shan said:
.......
Btw i also could not find boot from recovery.p file in system folder in LR twrp to replace recovery as instructed there.. do you have any information on that?
Thanks
Click to expand...
Click to collapse
You have to mount the system partition first, go to the mount tab and select system, then try the file manager and look for recovery.p, should be there.
wang1chung said:
You have to mount the system partition first, go to the mount tab and select system, then try the file manager and look for recovery.p, should be there.
Click to expand...
Click to collapse
Oh my bad i forget that.. been out of Android from months..
Anyways issues are resolved now with data lost ?
Thanks
Moderators can close the thread