Hi,
My mom has an Asus TF300T running JB 4.2.1. She tried to root and flash OmniROM by herself and borked it somehow. Unfortunately, she didn't do any backup...
She entered the fastboot screen and there she selected wipe. Then she flashed openrecovery-twrp-2.6.3.0-tf300tg-JB.blob using fastboot.
Now I am trying to help her rescue it.
It's operational, the OS loads up fine and she can use it, install apps etc.
I can get to the fastboot screen and from there to the TWRP no problem, but TWRP can't mount anything besides system.
No dalvik partition, no data partition, not even the SD or external SD.
Naturally, I can't flash another rom...
Tried executing "fix permissions" from the TWRP menu, it didn't help.
Downloaded the latest official Asus blob file TF300T-US_epad-10_6_1_27_5-UpdateLauncher.zip and flashed it using fastboot, hoping it will restore the missing partitions but it didn't make any difference.
Also tried CWM - same issue.
Any ideas?
Thanks,
Sefi
chompy18 said:
Hi,
My mom has an Asus TF300T running JB 4.2.1. She tried to root and flash OmniROM by herself and borked it somehow. Unfortunately, she didn't do any backup...
She entered the fastboot screen and there she selected wipe. Then she flashed openrecovery-twrp-2.6.3.0-tf300tg-JB.blob using fastboot.
Now I am trying to help her rescue it.
It's operational, the OS loads up fine and she can use it, install apps etc.
I can get to the fastboot screen and from there to the TWRP no problem, but TWRP can't mount anything besides system.
No dalvik partition, no data partition, not even the SD or external SD.
Naturally, I can't flash another rom...
Tried executing "fix permissions" from the TWRP menu, it didn't help.
Downloaded the latest official Asus blob file TF300T-US_epad-10_6_1_27_5-UpdateLauncher.zip and flashed it using fastboot, hoping it will restore the missing partitions but it didn't make any difference.
Also tried CWM - same issue.
Any ideas?
Thanks,
Sefi
Click to expand...
Click to collapse
That sounds pretty bad. The factory blob flashed successfully? If it did, did it just bootloop and then you tried another custom recovery? I'm thinking if the factory blob flashed successfully and it didn't work, your only hope beyond sending it in to them would be to use NVflash. However, pretty sure you had to set up NVflash before anything else or an older update for it to work, can't remember off the top of my head. Props to your mom trying to install Omni though. Hope this doesn't deter her from trying on something else. These tablets are a little different than most devices and I had to read a lot to make sure I had everything lined up properly when I've worked on them for customers.
es0tericcha0s said:
That sounds pretty bad. The factory blob flashed successfully? If it did, did it just bootloop and then you tried another custom recovery? I'm thinking if the factory blob flashed successfully and it didn't work, your only hope beyond sending it in to them would be to use NVflash. However, pretty sure you had to set up NVflash before anything else or an older update for it to work, can't remember off the top of my head. Props to your mom trying to install Omni though. Hope this doesn't deter her from trying on something else. These tablets are a little different than most devices and I had to read a lot to make sure I had everything lined up properly when I've worked on them for customers.
Click to expand...
Click to collapse
Hi,
Thanks for your reply.
Yeah the factory blob flashed fine. I can use the device (the OS loads up), I can get into fastboot and from there to TWRP.
There is no backup, and from what I'v read about NVflash, you need to set it up before anything else...
I was hoping the factory blob would recover the partitions...
Is there a way to repartition it?
Maybe using fastboot erase for the data partition?
I guess maybe I am not sure of the exact nature of the issue. If /data was not mounted, you would not be able to install apps. Does it show the proper info in Settings / Storage? Have never seen a device that had the data partition unmount and still be able to use normally while booted.
Related
So my Evo LTE is running 2.13.651.1, and is on what I understand to be the newest HBOOT (1.19). Naturally, I have S-ON as a result. This is my first Android device, and I've had it about a week since switching from an iOS device. I have root and the Teamwin recovery, which I used to backup the phone. I understand this is called a nandroid backup?
I plan to flash Cyanogenmod 10, in fact I already tried once. It resulted in a bootloop, and I restored from the nandroid backup. I have since learned I need to flash the boot.img from CM10 using fastboot, Flash Image GUI, or any other alternative. Once I do this, if I want to go back to Sense 4.1 like I have currently, how would I do so? Once I flash the boot.img from CM10, I won't simply be able to restore to my nandroid from teamwin, will I? I assume that if I tried to restore from the nandroid, due to S-ON I would be unable to write to the boot partition from a recovery utility and I would be left in another bootloop. How can I get a boot.img corresponding to my stock Sense 4.1 rom in the event that I want to revert to stock?
In the folder containing my nandroid backup, I see a file called boot.emmc.win and a boot.emmc.win.md5. I understand what the MD5 is for, but is the boot.emmc.win what I will need to undo the effect of flashing CM10's boot.img? If so, how would I use it (I do not recognize that file extension, and Flash Image GUI does not seem to like it either)? If not, where would I get something that will work?
I've done several searches here and on other forums, but I can't seem to find what I need. If someone has already answered this question, could you simply point me in the direction of that thread?
Thanks in advance,
Kristoffer
I have yet to restore a back up but to avoid any issues I would use dumlock. Install it from twrp advanced menu and reboot, open it in cm and it will backup boot and overwrite it with a temporary recovery, you then reboot and go back to dumlock and restore the back up, then you are free to flash the nandroid backup and reboot
When you reboot, do not boot to recovery, the boot partition has been replaced with a temporary twrp and all you need to do is reboot normally
om4 said:
I would use dumlock. Install it from twrp advanced menu and reboot, open it in cm and it will backup boot and overwrite it with a temporary recovery, you then reboot and go back to dumlock and restore the back up, then you are free to flash the nandroid backup and reboot
Click to expand...
Click to collapse
Once I flash CM and its boot, the boot for my Sense 4.1 will have been overwritten, no? I opened Dumlock in my Sense rom (as I have not yet flashed CM successfully), and it gives me a warning to make a backup of boot PRIOR to using the app, then just under that says the app will make a backup of the boot. If I go ahead and run Dumlock, I'm not entirely sure what is going to happen. It seems that it will move my recovery (TeamWin at the moment) onto the boot partition? If this is the case, why is this something that needs to be done? Does moving the recovery onto the boot partition allow the recovery to write to the boot without S-OFF, thereby allowing a simple restore of the nandroid to replace my rom AND boot at the same time, as if I were restoring with S-OFF? Sorry if I'm not making sense, but I don't really know what I'm talking about here, and thats the only thing that makes sense to me.
I see a button in Dumlock that says "restore original boot." If I install CM and the CM boot, will pushing this "restore original boot" button give me back the boot setup for the stock Sense rom? If it does, then I could just push that button, let it do its thing, and then restore my Sense nandroid with my recovery, right?
Thanks for your help, and quick response.
Install HTC dumlock
Open the app and back up boot
Once back up is successful, press execute
Once the phone restarts it will only boot to twrp, you then go to dumlock menu again and restore boot
Now flash a Rom or restore back up and reboot
Sorry to sound ignorant, but will this method will restore the stock boot regardless of what rom/boot combination I'm currently running? Or is this creating a backup of the currently installed boot, and saving it somewhere for future use? Specifically, do I want to follow this procedure before I upgrade to CM so I have a backup of the current boot, or is this something I want to do if/when I want to go back from CM to Sense that will magically put the boot back how it was from the factory?
Yes, its a workaround that gives access to boot partition and will let you flash normally, I would only use it for stuff like nandroids rather normally flashing because it writes to boot 3 times. It's a lot of unnecessary wear and tear
Awesome, thanks alot for your help. I'm excited to go and try my CM10 rom, now I know how to get back to stock if I don't like it.
Thanks again,
Kristoffer
Hmm. Now I don't know what I've screwed up. I flashed the boot.img from the CM10 zip using Flash Image GUI, then rebooted to recovery and wiped the System partition and cleared dalvik/cache. Then I flashed the CM10 zip using twrp, cleared dalvik/cache, and rebooted. Now, I'm stuck at the CM boot animation again, just like last time. This does not seem terribly complicated, and I don't know what I've done wrong.
I understand twrp cannot flash the boot due to S-ON, but I thought flashing the boot from inside my Sense rom using Flash Image GUI would fix the problem. I restored the Sense nandroid like before, rebooted, and then I got the Recovery boot logo (htc logo, with red text underneath). After maybe a minute, that went away, and I got a Sprint logo and then the normal boot screen with only an HTC logo. The phone then restarted, and this process repeated several times. So, apparently whatever I did to the boot sector with Flash Image GUI wreaked whatever was there before, and failed to replace it with something that would play nice with CM.
A factory reset won't fix the boot, will it? All it will do is overwrite my system partition and internal sd with the default files, and I still won't be able to boot. Any idea what I've screwed up, and how I can fix it?
EDIT:
I reflashed the CM10 zip, and it still gets stuck at the CM boot logo (spinning blue thing). What are the chances my CM10 download is corrupt? Is it worth trying to redownload it, reflash boot with fastboot, then move the new zip to the phone and flash that?
What version of twrp are you using, some people have had issues with the older 2.1.8
Ok, progress. I'm on twrp 2.2.1. I wiped everything again (wiped cache and dalvik, Factory Reset, and then wiped System) and reflashed CM10. It booted this time, so I assume the boot partition is fine. Apparently I'm the retard that can't understand a point-and-click system and follow simple directions
Once it boots, however, I instantly see an error "Unfortunately, the process com.android.phone has stopped." Once I click Ok, the error will either pop back up immediately, or wait for an indefinite period and them come back. Possibly this is the result of the CM10 release not being entirely stable as of yet, I don't know.
But thanks again, your help and your fantastic Don't Panic post together fixed the problem. I think I can figure out what is going on with this error popup and fix it. So long as I have voice service in the interim, which I do, all is well in the world.
It's normal, it pops up when you lose signal, its a bug but its technically a feature. If the phone loses signal, normally android is supposed to prompt you so you are aware. I think its for debugging purposes, normally this is disabled. Not sure if its really a bug in cm or they just haven't gotten around to disabling it, but its normal. It's not a real priority either since it doesn't adversly affect the phone
Hmm. This just gets better and better. So CM10 ran nicely for awhile, then last night I rebooted the phone and the internal SD card failed to mount. Both twrp and the actual OS cannot get it to mount properly. Is this something I broke, or does it sometimes occur at random? I read the following, but I don't quite know where to go with it.
om4 said:
You're card is beyond a simple reformat, the physical address linking the card and or entire card is corrupt. Don't panic, you have to start clean. Back up the info on you external or remove it, make sure you have a ROM available on your PC. Go into recovery and repartition your phone, this will wipe all memory. You then load up a working ROM (a bad back up may be responsible or just reintroduce the problem), after you have flashed the ROM (HBOOT 1.15+ must fastboot kernel, unless S-OFF) go ahead and boot into android and restore your apps.
Click to expand...
Click to collapse
Repartitioning seems simple enough; twrp> advanced >partition SD card>swipe (leaving all settings default).
After that, I can flash the new rom and boot using fastboot from my PC, right? I'm confident that my nandroid of the stock rom is clean, because I didn't develop this problem until after I had been using CM10 for awhile. Could I use fastboot to flash the boot, data, and system from the nandroid, and be good to go? If not, is the most current file avalible to download at http://stockroms.net/file/HTCEvo4GLTE/RUU? the appropriate file I would need to restore the phone to its stock unrooted state.?
Also, none of my nandroid files have a .img file extension. Is this normal? It has the normal .md5 files, but everything else has a .win extention. I've never heard of this one. My boot, for example, seems to be backed up as boot.emmc.win, with a boot.emmc.win.md5 corresponding to it. Cache, data, and system backups are named <option>.ext4.win. Does ext4 has something to do with the filesystem of the backed up partition? If this is the case, what is a .emmc? Can I flash these files with their strange (to me, at least) extensions using fastboot as if they were all .img files?
I can't imagine any of this is really as complicated as it seems. I've used a PC and a jailbroken iDevice extensively, and never managed to break something I couldn't fix. I guess Android just doesn't like me, or something.
Thanks again for all your help.
EDIT:
Apparently physically removing the external SD from the phone allowed me to mount the internal SD as a USB device. The phone still refused to allow me to read/write data to the memory, but somehow managed to allow my PC to see it. I formatted the internal SD to fat32 (one of the limited options) using Windows, and rebooted the phone to recovery. Now, it suddenly can detect its internal SD. I was able to wipe everything, and restore my Cyanogen backup and the SD card now works again. Weird...
Since I didn't have to repartition anything, was the "physical address linking the card and or entire card" corrupt, or did I have some other issue? Also, I'm still curious about my above question pertaining to file extensions and restoring a nandroid via fastboot.
I accidentally formatted my internal SD card with TWRP instead of factory reseting. I can get into recovery, but loading any ROM hangs at the loading screen. For awhile, TWRP was asking for a password, and then somehow I hit the magic combination of things to make that stop happening. I adb pushed an updated TWRP and reinstalling various ROMs.
All this started from trying to install Hyperdrive RLS8. I was running RLS7 fine, went for a clean install, spaced out and formatted the phone, flashed the ROM, and had a whole slew of stability problems. Things would randomly crash instantly, booted only 50% of the time, when it did, installing things would break it, tried various things to fix it, fixing permissions and wiping cache's and such, and results were unpredictable. Kept re-formatting and reflashing with different options until I finally realized that I was formatting it and that's probably what the whole problem was.
Currently I can't boot into a ROM, it hangs on the boot animation. I tried another clean install with RLS7, and the same thing happens. I'm assuming that I need to get back to stock somehow, but I'm not sure how. Odin has always confused me. I used the all in one tool to root awhile back, and I only used odin to send a kernel tar file. If I download a stock build, it's a zip file... so how can I odin it? Is that what I need to do? I'm imagining at this point that the file structure is messed up and I need to rebuild it somehow. I don't have my nandroid backup on this computer, so I haven't tried that yet.
You can either odin stock. It's about a 1.8gb file.
Or you can get a known working ROM on your sd card, factory reset wipe, wipe preload, wipe system, install known working rom+gapps+whatever, wipe cache and wipe dalvik. Reboot. If it sticks at the samsung logo pull the battery and then try to reboot again. Sometimes first boot can take a while. I'd give it 10 minutes before throwing in the towel lol
I bricked my phone by updating Hyperdrive (which I will never (curse words... lots of them) use again. Can someone tell me where to find this stock file? I've been searching long enough to get frustrated and delete several less diplomatic posts, settling with this one.
hey guys, I am a little confused. I just came to the S4 from a galaxy nexus, and I previously used CWM as my recovery option when doing clean install of new ROMS.
When I rooted my S4, I installed TWRP (via goomananger, version 2.5.0.2) because of people saying its much better (on the galaxy nexus forums). However, I keep reading issues of people being stuck in bootloops for TWRP when wiping data.
My question is -- what is this issue? Are you not supposed to clean flash with TWRP?? Or do you only do "factory reset" option in TWRP and not wipe the data?
As I am a little confused on this issue, is it more safe to just install most recent CWM and use that as recovery instead?
Thanks alot
No worries
uberpippi said:
I accidentally formatted my internal SD card with TWRP instead of factory reseting. I can get into recovery, but loading any ROM hangs at the loading screen. For awhile, TWRP was asking for a password, and then somehow I hit the magic combination of things to make that stop happening. I adb pushed an updated TWRP and reinstalling various ROMs.
All this started from trying to install Hyperdrive RLS8. I was running RLS7 fine, went for a clean install, spaced out and formatted the phone, flashed the ROM, and had a whole slew of stability problems. Things would randomly crash instantly, booted only 50% of the time, when it did, installing things would break it, tried various things to fix it, fixing permissions and wiping cache's and such, and results were unpredictable. Kept re-formatting and reflashing with different options until I finally realized that I was formatting it and that's probably what the whole problem was.
Currently I can't boot into a ROM, it hangs on the boot animation. I tried another clean install with RLS7, and the same thing happens. I'm assuming that I need to get back to stock somehow, but I'm not sure how. Odin has always confused me. I used the all in one tool to root awhile back, and I only used odin to send a kernel tar file. If I download a stock build, it's a zip file... so how can I odin it? Is that what I need to do? I'm imagining at this point that the file structure is messed up and I need to rebuild it somehow. I don't have my nandroid backup on this computer, so I haven't tried that yet.
Click to expand...
Click to collapse
Try using odin to flash to stock. Then re-root and install custom recovery and whichever rom. I had a similar problem posted here with no help from the big brains. Had to trial and error with caution on my own. Kinda disappointing since the answer is quite simple once you connect all the dots. Flashing in odin will fix yer internal storage problem because it redefines everything.
cidorov said:
Try using odin to flash to stock. Then re-root and install custom recovery and whichever rom. I had a similar problem posted here with no help from the big brains. Had to trial and error with caution on my own. Kinda disappointing since the answer is quite simple once you connect all the dots. Flashing in odin will fix yer internal storage problem because it redefines everything.
Click to expand...
Click to collapse
uberpippi said:
I accidentally formatted my internal SD card with TWRP instead of factory reseting. I can get into recovery, but loading any ROM hangs at the loading screen. For awhile, TWRP was asking for a password, and then somehow I hit the magic combination of things to make that stop happening. I adb pushed an updated TWRP and reinstalling various ROMs.
All this started from trying to install Hyperdrive RLS8. I was running RLS7 fine, went for a clean install, spaced out and formatted the phone, flashed the ROM, and had a whole slew of stability problems. Things would randomly crash instantly, booted only 50% of the time, when it did, installing things would break it, tried various things to fix it, fixing permissions and wiping cache's and such, and results were unpredictable. Kept re-formatting and reflashing with different options until I finally realized that I was formatting it and that's probably what the whole problem was.
Currently I can't boot into a ROM, it hangs on the boot animation. I tried another clean install with RLS7, and the same thing happens. I'm assuming that I need to get back to stock somehow, but I'm not sure how. Odin has always confused me. I used the all in one tool to root awhile back, and I only used odin to send a kernel tar file. If I download a stock build, it's a zip file... so how can I odin it? Is that what I need to do? I'm imagining at this point that the file structure is messed up and I need to rebuild it somehow. I don't have my nandroid backup on this computer, so I haven't tried that yet.
Click to expand...
Click to collapse
Yes this would probably be your best bet. I wouldn't say the answer "is quite simple when you connect the dots" though, because with that logic there would be no PC problems, you would just connect the dots and format the harddrive and Windows will redefine everything else for you!
But back to seriousness, you have to download a stock factory image and its actually a tar.md5 file and not a .zip because you cant flash zips through odin. The stock factory images can be found in the development section, and they are usually quite large files (2gb+ when extracted!) and you will have to download odin and make sure you have the latest usb drivers from samsung. Then its pretty straight forward, The threads in the development section have guides for how to use odin. The stock image contains all the partitions within in it and will effectively repartition your device when you flash it so no need to use a pit file.
Surge1223 said:
Yes this would probably be your best bet. I wouldn't say the answer "is quite simple when you connect the dots" though, because with that logic there would be no PC problems, you would just connect the dots and format the harddrive and Windows will redefine everything else for you!
But back to seriousness, you have to download a stock factory image and its actually a tar.md5 file and not a .zip because you cant flash zips through odin. The stock factory images can be found in the development section, and they are usually quite large files (2gb+ when extracted!) and you will have to download odin and make sure you have the latest usb drivers from samsung. Then its pretty straight forward, The threads in the development section have guides for how to use odin. The stock image contains all the partitions within in it and will effectively repartition your device when you flash it so no need to use a pit file.
Click to expand...
Click to collapse
Just to follow up, that's what I ended up doing. I used the "No-wipe" factory image, odin'd it, re-rooted (I don't know if I had to do that step, but I did), and then loaded my ROM of choice and it works perfectly now. Thanks!
So I am S-On, running CM 10.1.3 stable.
I was on OTA 3.16.651.3 with 2.09 hboot when I successfully unlocked my bootloader using HTCDev unlock and installed TWRP and SU using BigDaddy619's kit.
I wanted to try out CM 10.1.3 stable ROM. I was able to transfer the zip via usb to the Internal SD, then Installed inside TWRP. I then realized I needed to do the boot.img kernel flash using fastboot. I did this, and the phone booted up!
I have tried CM for the last 3 days, and like some aspects, but I really want GPS and Bluetooth to work.
So I tried to flash back to zhaus's stock ROM. The problem is I no longer have an internal SD mounted, and the phone won't let me download files. I can not for the life of me figure out how to remount the internal SD so I can download to it. Plus, the phone won't allow me to fastboot update or push the file to the phone using ADB. It's weird, since fastboot works but errors, but ADB doesn't even find my device.
Another odd thing is when I enter TWRP and try to do a factory reset/wipe, it always says FAILED.
I am super confused on how to proceed in switching back to a stock ROM. Hoping someone can throw me a life preserver.
You need to format your internal storage. To do this, boot into recovery and connect your phone to your PC. Select the 'Mount' option, then select your internal storage. You should then be prompted to format your storage on your computer.
Also, when wiping with TWRP, choose the advanced wipe option and select Dalvik cache, cache, data & system.
GPS should be working on that build of CM. You may need to try the GPS fix from a Sense ROM before dismissing the issue as GPS simply not working.
Sent from my HTC EVO 4G LTE
bman3333 said:
I have tried CM for the last 3 days, and like some aspects, but I really want GPS and Bluetooth to work.
Click to expand...
Click to collapse
I'm confused, because both of those things work fine on CM10.1. Methinks you should S-OFF to avoid these types of issues going forward . . . .
Captain_Throwback said:
I'm confused, because both of those things work fine on CM10.1. Methinks you should S-OFF to avoid these types of issues going forward . . . .
Click to expand...
Click to collapse
I don't think I properly installed CM 10.1. I initially tried to flash cm-10.1.3-jewel inside TWRP, BEFORE flashing the kernel with the extracted boot.img in fastboot. I never tried to re-flash the cm-10.1.3-jewel zip after flashing the kernel.
My second mistake was selecting factory reset in the bootloader, which screwed up the Internal SD mount.
Thank you guys for the replies.
bman3333 said:
I don't think I properly installed CM 10.1. I initially tried to flash cm-10.1.3-jewel inside TWRP, BEFORE flashing the kernel with the extracted boot.img in fastboot. I never tried to re-flash the cm-10.1.3-jewel zip after flashing the kernel.
My second mistake was selecting factory reset in the bootloader, which screwed up the Internal SD mount.
Thank you guys for the replies.
Click to expand...
Click to collapse
It's best to avoid a factory reset from the bootloader. Anything you do as far as wiping should be done from recovery. Don't sweat it, though, you aren't the first person who has done it and you surely won't be the last
Sent from my HTC EVO 4G LTE
I recently formatted my internal storage because I felt like I needed a clean wipe. After doing so, flashing anything and rebooting into it will make it hang on the Samsung logo. I flash everything through TWRP v2.5.0.2 and I never had problems until I formatted. Now to get anything to work, I have to "format data" through TWRP and flash after that in order to boot into anything (every single time). And even after booting into it, I can't flash anything (or even simply reboot) without having to see the stuck screen again. Any ideas? My phone is MDK.
You need to update TWRP. Latest is 2.6.3.1. Older twrp doesn't use the proper symlinks for the internal data partition that changed in 4.3.
WhoNeedszzz said:
You need to update TWRP. Latest is 2.6.3.1. Older twrp doesn't use the proper symlinks for the internal data partition that changed in 4.3.
Click to expand...
Click to collapse
Thanks! I think that worked
So, where to start.. I just got my redmi note 5 to test all sorts of things on, and my first goal was to successfully unlock it, install TWRP, and root through Magisk.
For this, I've used the 'Flashing TWRP on Redmi 5 Plus (and Root)' guide on the miui blog (can't post the link, unfortunately.)
I unfortunately keep running into a strange problem, which I'm going to explain briefly, because this is the second time that it happened, and I have no idea what to do, to be completely honest.
So, I successfully unlocked my redmi 5 plus, enabled USB debugging, installed ADB Fastboot on my PC, and went on to flash TWRP 3.3.0.0. This worked, the recovery image was properly read, although I could only boot it from fastboot into recovery, by holding the button combination. When trying to reboot after flashing, going into recovery from the system via the console on my pc put me in the normal MIUI recovery. So, I had to flash TWRP again, and do it the way I described. I forgot to mention, but I also copied both Magisk and no-verity to the root folder of my internal storage before installing TWRP, but, when going into TWRP to install, I could not find those zip files.
The internal storage showed as 0MB, and I read that you're supposed to wipe the data, with TWRP, which did in fact let me see the amount of MB on my internal storage, but unfortunately it did not let me find those files either. The sad part is, now my phone is stuck on a bootloop, again, and I can only run either recovery or fastboot, the latter of which I'm going to use to flash stock recovery and do a factory reset, once again.
At this point I'm lost as to what I should do, I'm following the advice from many different sources, and nothing seems to work. Maybe I'm missing something obvious, but being the noob I am, I cannot figure it out .
Give it a shot by trying orange fox recovery
Also I might be wrong but I think there is a fix for 0mb problem
Try OrangeFox Recovery, for me its better than twrp. Internal storage is 0mb because its encrypted, OragneFox can decrypt that partition and make it accessible.
Good luck!
dmrszr said:
Give it a shot by trying orange fox recovery
Also I might be wrong but I think there is a fix for 0mb problem
Click to expand...
Click to collapse
skrubxgt said:
Try OrangeFox Recovery, for me its better than twrp. Internal storage is 0mb because its encrypted, OragneFox can decrypt that partition and make it accessible.
Good luck!
Click to expand...
Click to collapse
Thanks for the advice! I did try one last thing by just installing magisk on my phone normally, and.. well, it actually worked! I don't have a custom recovery, but I was able to root the phone without any issue, so I think this will suffice for now? In the future though, I'll keep the OrangeFox Recovery in mind.
Minik9988 said:
Thanks for the advice! I did try one last thing by just installing magisk on my phone normally, and.. well, it actually worked! I don't have a custom recovery, but I was able to root the phone without any issue, so I think this will suffice for now? In the future though, I'll keep the OrangeFox Recovery in mind.
Click to expand...
Click to collapse
Nice to see that your problem has been solved! You can thank by hitting "Thanks!" button
Flash twrp
Format data
Then flash twrp in twrp
Flash no variety
Reboot to recovery..
Now you will have your twrp permanently installed as recovery
Now do whatever u like with twrp