Sorry this is the wrong board-- i reposted on Help&Trouble shooting, I don't know how to delete the thread
I tried flashing an old, alpha, version of sailfish on my phone and since then it's been bootlooping. I can access the recovery and install CM11 but after booting it restarts, every 1-2 minutes. Flashing some other roms gives me bootloops (First boot takes >1 minute, the phone resets).
I've already backed up all my data and wiped internal and external storage, but flashing gives me the same problems.
What can I do? I have the latest TWRP installed
Have you install the Firmware for Redmi 1s by Xiaomi ?
1. install firmware
2. install rom, gapps etc
3. reboot
Deivid_ said:
Sorry this is the wrong board-- i reposted on Help&Trouble shooting, I don't know how to delete the thread
I tried flashing an old, alpha, version of sailfish on my phone and since then it's been bootlooping. I can access the recovery and install CM11 but after booting it restarts, every 1-2 minutes. Flashing some other roms gives me bootloops (First boot takes >1 minute, the phone resets).
I've already backed up all my data and wiped internal and external storage, but flashing gives me the same problems.
What can I do? I have the latest TWRP installed
Click to expand...
Click to collapse
if the above method dont work then try to flash fastboot rom
It was the firmware. I'd never flashed firmware with other phones and neither needed it with other roms. Thanks
Deivid_ said:
Sorry this is the wrong board-- i reposted on Help&Trouble shooting, I don't know how to delete the thread
I tried flashing an old, alpha, version of sailfish on my phone and since then it's been bootlooping. I can access the recovery and install CM11 but after booting it restarts, every 1-2 minutes. Flashing some other roms gives me bootloops (First boot takes >1 minute, the phone resets).
I've already backed up all my data and wiped internal and external storage, but flashing gives me the same problems.
What can I do? I have the latest TWRP installed
Click to expand...
Click to collapse
first of use latest twrp recovery
then wipe everything that you can see(if i say everything then i mean it)
put the latest cm 13.0 zip and gapps to your sd card and
flash both of these and then enjoy
Phuclun510 said:
Have you install the Firmware for Redmi 1s by Xiaomi ?
Click to expand...
Click to collapse
where i can find that firmwire??
savior** said:
where i can find that firmwire??
Click to expand...
Click to collapse
It's in the second or third post of the Cyanogenmod threads in the ORIGINAL DEVELOPMENT subforum.
Already install fastboot rom? these a link http://en.miui.com/thread-14641-1-1.html
Related
I am on 4.1.2
Ive used all 3 available custom recoveries, 4 if you include the other TWRP
Every recovery with every zip, all md5 checked, say unable to open zip
Am I doing something wrong?
shaunjohn said:
I am on 4.1.2
Ive used all 3 available custom recoveries, 4 if you include the other TWRP
Every recovery with every zip, all md5 checked, say unable to open zip
Am I doing something wrong?
Click to expand...
Click to collapse
What are you trying to flash?
And which recovery VERSION are you using?
Model aand name of rom
Which model do you have?? and what is the rom's name?
210r
ive tried
philz recpvery
cwm
twrp 2/7 and 2/8
ive tried
cm11
rocket
swat(name may be wrong)
kids
Reflash the 4.4.2 firmare from odin all over again and install TWRP (2.8.0.0) the flash rom in recovery
A friendly reminder - please keep all question threads in the Q&A board. Android dev is only for posting releases, not questions.
Thanks!
Same Result
ruzell said:
Reflash the 4.4.2 firmare from odin all over again and install TWRP (2.8.0.0) the flash rom in recovery
Click to expand...
Click to collapse
same result, error opening zip file
Did you ever figure this out? I"m having the same issue.
Can't flash a ROM on Tab 3 7.0 t210r
I am rooted, first thing I did after purchase.
Am currently running 4.1.2, build jzo54k.t210rueamk1
I have flashed PhilZ Touch 6, 6.44.9, ClockworkMod 6.0.4.9 from here:
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/lt02wifi/
I have tried to flash the following ROMs:
Stockrom Series Ultimate Edition
http://forum.xda-developers.com/showthread.php?t=2489395
RocketTab v3.1
http://forum.xda-developers.com/showthread.php?t=2507772
Flash fails with:
Installation aborted (bad), can't open <path to zip file><name of zip>
This happens after a factory reset, wipe data, cache.
I have a Samsung S3 that I have rooted, and then flashed many times. Before that I had an HTC EVO. I am not new to the process, but apparently I am missing something here.
Got any suggestions?
Which Odin Version you are used to install The Recovery? Try an other Version.
Is your Rom on The micro Sdcard ? If you use Philz so is The max capacity 32 GB, if you use TWRP so is max 64 GB supported.
starmaha said:
I am rooted, first thing I did after purchase.
Am currently running 4.1.2, build jzo54k.t210rueamk1
I have flashed PhilZ Touch 6, 6.44.9, ClockworkMod 6.0.4.9 from here:
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/lt02wifi/
I have tried to flash the following ROMs:
Stockrom Series Ultimate Edition
http://forum.xda-developers.com/showthread.php?t=2489395
RocketTab v3.1
http://forum.xda-developers.com/showthread.php?t=2507772
Flash fails with:
Installation aborted (bad), can't open <path to zip file><name of zip>
This happens after a factory reset, wipe data, cache.
I have a Samsung S3 that I have rooted, and then flashed many times. Before that I had an HTC EVO. I am not new to the process, but apparently I am missing something here.
Got any suggestions?
Click to expand...
Click to collapse
bierma32 said:
Which Odin Version you are used to install The Recovery? Try an other Version.
Is your Rom on The micro Sdcard ? If you use Philz so is The max capacity 32 GB, if you use TWRP so is max 64 GB supported.
Click to expand...
Click to collapse
I didn't use Odin to flash the recovery. Downloaded the zip and flashed via recovery.
I have tried with the ROM on the external and internal SD. Same results.
32GB SD.
starmaha said:
I didn't use Odin to flash the recovery. Downloaded the zip and flashed via recovery.
I have tried with the ROM on the external and internal SD. Same results.
32GB SD.
Click to expand...
Click to collapse
u
How do you rooted your Tab?
With Stockrecovery you can not flash a Rom or Recovery.
Flash Philz or TWRP With Odin, reboot to The New flashen Recovery , than you can install a Rom.
All information for The right steps you will find at dev Sektion.
bierma32 said:
u
How do you rooted your Tab?
With Stockrecovery you can not flash a Rom or Recovery.
Flash Philz or TWRP With Odin, reboot to The New flashen Recovery , than you can install a Rom.
All information for The right steps you will find at dev Sektion.
Click to expand...
Click to collapse
To clarify, when I initially rooted, I used Odin to flash recovery and root.
starmaha said:
To clarify, when I initially rooted, I used Odin to flash recovery and root.
Click to expand...
Click to collapse
At first we are turn us i The circle,but now we can come to your prob.
Flash a Rom and make a picture and post that here. So we can See The error message and your Recovery.
starmaha said:
To clarify, when I initially rooted, I used Odin to flash recovery and root.
Click to expand...
Click to collapse
Sounds like the rom download is bad. Check the md5 of the rom before trying to install.
Kind of success. I downloaded the same version of PhilZ, for Odin, on my laptop.
I put the tablet in download mode and flashed the recovery with Odin.
I downloaded the ROM again (http://forum.xda-developers.com/gal...m-stockrom-kitkat-version-16-08-2014-t2849742). This is one I had tried before. This time to my laptop and copied it to the tablet. The other times, I had downloaded the ROM directly onto the tablet.
While it was in the process of flashing, there were some video anomolies.
I rebooted the tablet into recovery and flashed the ROM. It hung on SAMSUNG for a very long time after the flash and reboot. I powered it off and rebooted. It booted completely this time, but not without some issues. The first thing was when the message pops up that Android is optimizing apps. That bar was all screwy looking, snowy. (see attached image)
Once I got to the lock screen and entered the pin, the screen "fractured", pieces shifted around, and the tablet locked up. I wish I had taken a picture of it. Never seen anything like it.
I had not done a data wipe yet. I did a data wipe, rebooted, entered the pin, tablet locked up again.
I then was going to restore the backup I made before the flashing. It wouldn't restore because of an MD5 mismatch. I had restored this backup previously with no problem.
I restored an older backup and then spent a couple of hours getting everything back to the level of the now broken backup.
Flash nolekat and all went fine.
I've had problems as well. I normally flash via a recovery. At times I'll have an md5 mismatch or it just doesn't work; I've even backed up a working ROM only to find out I can't restore the same backup. Seems like a hit or miss with me
I tried flashing NoleKat and it failed on me too.
[/COLOR]
bierma32 said:
At one of your post you write after flashing you must put in the Pin?
So you have make not a clean install or factory reset, you done a wipe cache and wipe dalvik.
You must do a clean install if you come from different Roms or Version.
Click to expand...
Click to collapse
Please post a picture from your Recovery with the error message.
So as the title says, after flashing cm14. 1 can't go into recovery anymore, it just a black screen. I tried to use flashify but nothing, a couple of apps show that I have twrp 3.0.2.1 but can't get into it... Help?
Cheers
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
JKMB888 said:
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Click to expand...
Click to collapse
Which thread is this from please?
JKMB888 said:
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Click to expand...
Click to collapse
Yeah man im in the same boat, if i get time ill try this twrp recovery. Where did that recovery come from?, it seems like the CM recovery for 14.1 nightly high jacks the recovery partition (i call it that,i dont know the term for it)
Sent from my ONEPLUS A3000 using Tapatalk
I believe the official 14.1 nightlies are based on the CB which requires the modified TWRP, which is what @JKMB888 has linked you to.
Hw4ng3r said:
I believe the official 14.1 nightlies are based on the CB which requires the modified TWRP, which is what @JKMB888 has linked you to.
Click to expand...
Click to collapse
I would like to truly confirm that the direct link to recovery, along with the thread in which it can be found, repair the situation. I was able to restore the backup of Freedom OS and the return to CM14.1 backup. We should keep this one somewhere near, jsut in case.
Thanks a lot guys, that did the trick, and done with flashify
JKMB888 said:
I would like to truly confirm that the direct link to recovery, along with the thread in which it can be found, repair the situation. I was able to restore the backup of Freedom OS and the return to CM14.1 backup. We should keep this one somewhere near, jsut in case.
Click to expand...
Click to collapse
@JKMB888 it does work 100% is as simple as flashing the TWRP. Actually, i installed it with CM 14.1 running just fine
Sent from my ONEPLUS A3000 using Tapatalk
Just re flash the TWRP image via Fastboot. Apps like flashify actually use TWRP or whatever recovery installed to flash image file AFAIK. I recommend using modified TWRP,Flashing some roms break the access. But the modified one can withstand almost every new rom installs.
Hope it helps.
Why i have always mount decrypt data when i boot in recovery mode which is TWRP 3.0.2-22 aand ask me to input a password?
Edit: I found the solution, i had a pattern lock screen and i removed it!
HC4Life said:
Why i have always mount decrypt data when i boot in recovery mode which is TWRP 3.0.2-22 aand ask me to input a password?
Click to expand...
Click to collapse
At some point your phone data became encrypted. While booted up if you search for encrypt in settings you'll see your phone is encrypted.
Same thing happened to me yesterday after flashing 3.2.7 and booting up for the first time before going back to TWRP to flash AICP. Only way to decrypt permanently, as far as I know, is to wipe all data including internal and completely start from scratch.
GrandMasterB said:
At some point your phone data became encrypted. While booted up if you search for encrypt in settings you'll see your phone is encrypted.
Same thing happened to me yesterday after flashing 3.2.7 and booting up for the first time before going back to TWRP to flash AICP. Only way to decrypt permanently, as far as I know, is to wipe all data including internal and completely start from scratch.
Click to expand...
Click to collapse
Look at my edited reply...
m4manusraj said:
Just re flash the TWRP image via Fastboot. Apps like flashify actually use TWRP or whatever recovery installed to flash image file AFAIK. I recommend using modified TWRP,Flashing some roms break the access. But the modified one can withstand almost every new rom installs.
Hope it helps.
Click to expand...
Click to collapse
actually flashify did the trick for me as I had no access to a pc for the time
http://forum.xda-developers.com/one...nity-build-t3461648/post68691560#post68691560
Flash this recovery. Fixed the problem for me
JKMB888 said:
I would like to truly confirm that the direct link to recovery, along with the thread in which it can be found, repair the situation. I was able to restore the backup of Freedom OS and the return to CM14.1 backup. We should keep this one somewhere near, jsut in case.
Click to expand...
Click to collapse
i am facing just the same situation with cm14.1 nightly and can't boot into recovery
i tried flashing the recovery image provided by you i.e. twrp-3.0.2-22-oneplus3.img but i face the same problem again
when i go into the recovery all i see is a black screen with a white notification light on and it remains there untill i switch off my phone manually using the power button
i tried facing the problem when i installed the cm14.1 nightly
i was unable to login snapchat as i device was rooted as said by the message on snapchat
so i decided to unroot my device via supersu FULL UNROOT option
after a reboot i successfully logged into snapchat
then i tried to root it again
i went into recovery to flash the supersu zip
and since then i have been unable to see the twrp recovey
please help me
This thread is a life save. Tried everything and it drove me nuts not getting into recovery.
THANK YOU!
gangangan2 said:
http://forum.xda-developers.com/one...nity-build-t3461648/post68691560#post68691560
Flash this recovery. Fixed the problem for me
Click to expand...
Click to collapse
Thank you so much it's work for me now..
After I got the recovery back, I flashed CM13 again and ARM64 6.0 Nano Gapps for my Oneplus 3, but I'm getting an error after the "preparing apps' screen is loaded saying that - unfortunately the process android.process.media has stopped one plus 3 boot and then the phone switches off.
Any solution to this? I've already tried flashing different versions of CM13.
Thank you!! I was looking for hours.
This link fixed the problem!
JKMB888 said:
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Click to expand...
Click to collapse
Hey, guys. I'm pretty sure I bricked my phone and there's no way to get out.
So I was on CM13 official builds on my OP3. Then, on the OTA update system they have, I got moved onto the CM14.1. I downloaded from here and went into my twrp recovery to flash. I made a clean flash and then proceeded to go back to system. I thought everything was ok until I realised I hadn't flashed a gapps package which I pretty much need to survive as all my contacts backups etc. are on there. I powered off my phone and went to go back into the recovery after downloading gapps 7.1 micro. It went past the *You're device can not be trusted'* and then went to the oneplus screen. After that, it stayed like that for about 30 secs and powered off. At first, I thought I messed something up and tried again. I repeated that for about 3 times and it didn't work. I tried going into the normal system and coming back to recovery and it didn't work still. In fact, now I can't even get into system. Now, i can only boot up to fastboot, where my computer still doesn't realise my phone is plugged in.
Anyone got any ideas on how to fix this? I wouldn't say I'm a noob at this because I have flashed many times before but I'm relatively new to the scene. I didn't see this thread before i ripped my hair out and i think wrecked my phone @JKMB888
EDIT: I sorted it out with help from Naman Bhalla's unbrick thread and this. A certain combo works and now I'm on CM14.1 enjoying life
I had CWM Recovery and an older cyanogenmod rom installed and I wanted to upgrade to 7.1.2 from here: https://forum.xda-developers.com/lg.../rom-android-7-0-nougat-20161008-r16-t3476750
I copied the rom to internal memory, rebooted into recovery, selected the rom file to install. It showed some messages about patching, then in a couple of minuted erred with smth like "Erro loki-ifying because of incompatible aboot image".
I then rebooted and now it boots and shows "ANDROID" and is stuck on it - looks like it partially updated the ROM and failed somewhere.
I am not sure what to do now - I tried to boot into recovery (Power off -> Hold Power + Vol down till menu shows) but it doesnt work - it keeps booting onto this stuck boot.
Any ideas?
As I understand it, being an amateur ROM flasher, all those 3rd party ROMs need a TWRP recovery to work. Provided your bootloader is unlocked, I'd flash the stock on via RSDlite, flash TWRP 3.1.1.0 (my best experience), THEN install whatever ROM you like in TWRP. This'll start you from a clean slate and wipe ALL data from the phone. I'm guessing you forgot to wipe dalvik and cache before restarting, to. Someone of more experience may chime in, soon.
Sent from my XT1254 using Tapatalk
Crap. Sorry. Disregard. Thought this was a Droid Turbo thread.
Einsteindks said:
As I understand it, being an amateur ROM flasher, all those 3rd party ROMs need a TWRP recovery to work. Provided your bootloader is unlocked, I'd flash the stock on via RSDlite, flash TWRP 3.1.1.0 (my best experience), THEN install whatever ROM you like in TWRP. This'll start you from a clean slate and wipe ALL data from the phone. I'm guessing you forgot to wipe dalvik and cache before restarting, to. Someone of more experience may chime in, soon.
Click to expand...
Click to collapse
But how do I flash anything if I can't get into recovery?
andreyl79 said:
But how do I flash anything if I can't get into recovery?
Click to expand...
Click to collapse
You missed my edit update. I got confused as to which thread I was replying to.
Sent from my XT1254 using Tapatalk
Einsteindks said:
You missed my edit update. I got confused as to which thread I was replying to.
Click to expand...
Click to collapse
Nevertheless you gave me the idea to try looking for a similar LG recovery tool and I just found one. Flashing stock at the moment - fingers crossed
Ok, I installed LineageOS and it worked fine. Must be an issue with the latest AOSP ROM here
andreyl79 said:
Ok, I installed LineageOS and it worked fine. Must be an issue with the latest AOSP ROM here
Click to expand...
Click to collapse
The reason the flash failed is simply the fact you put the ROM on the internal storage, flashing from there wiped the ROM before it gets written. If you had stored the AOSP on an external SD, it would have worked.
As Lineage is based on AOSP, it should have failed also...
hi, i am having aproblem right now trying to flash miui 12. first time i just formatted the phone in twrp. used adb push to push the zip on the phone. and flashed it. it was successful but after booting into the system it had a password for some reason and there was no setup screen. so i tried to reflash by formatting again and repeating the process. now i boot into system and it just goes into bootloop at the MI boot screen.
Its super weird that it worked the first time. then it doesnt work anymore no matter what (adb sideload, multiple recoveries) and it seems the rom isnt installing correctly because afterwards i cannot flash magisk (cannot mount system partition)
Use fox twrp to flash.
haovh_85 said:
Use fox twrp to flash.
Click to expand...
Click to collapse
I used TWRP. Also tried orangefox
haovh_85 said:
Use fox twrp to flash.
Click to expand...
Click to collapse
I also tried flashing the firmware first
-iwl- said:
hi, i am having aproblem right now trying to flash miui 12. first time i just formatted the phone in twrp. used adb push to push the zip on the phone. and flashed it. it was successful but after booting into the system it had a password for some reason and there was no setup screen. so i tried to reflash by formatting again and repeating the process. now i boot into system and it just goes into bootloop at the MI boot screen.
Its super weird that it worked the first time. then it doesnt work anymore no matter what (adb sideload, multiple recoveries) and it seems the rom isnt installing correctly because afterwards i cannot flash magisk (cannot mount system partition)
Click to expand...
Click to collapse
Wait for some days,when some one success.
I have also flashed the rom first day.
I struggle for 1 hour with my laptop than i booted into LOS 17.1 after destroying my whole 100 gb internal data of my phone.
paradise220 said:
Wait for some days,when some one success.
I have also flashed the rom first day.
I struggle for 1 hour with my laptop than i booted into LOS 17.1 after destroying my whole 100 gb internal data of my phone.
Click to expand...
Click to collapse
did you encounter the same issue? this person has it correctly installed:
https://www.youtube.com/watch?v=x5HJgH8QrMs
also. sometimes it says no os instlaled after i flashed
paradise220 said:
Wait for some days,when some one success.
I have also flashed the rom first day.
I struggle for 1 hour with my laptop than i booted into LOS 17.1 after destroying my whole 100 gb internal data of my phone.
Click to expand...
Click to collapse
i have no idea what to do now
-iwl- said:
did you encounter the same issue? this person has it correctly installed:
https://www.youtube.com/watch?v=x5HJgH8QrMs
also. sometimes it says no os instlaled after i flashed
Click to expand...
Click to collapse
when i flashed miui 12 beta it showed on operating software installed before reboot.
paradise220 said:
when i flashed miui 12 beta it showed on operating software installed before reboot.
Click to expand...
Click to collapse
it seems they released a broken rom. i tested again with lineage os and it worked perfectly. so its xiaomi at fault here
Ive installed It yesterday (dont know where but i Saw someone saying that It need Magisk, i flashed It and It worked).
But i turned back to oficial miui 11, my sim card was not working with this beta
Use chinese twrp
JrAdams said:
Ive installed It yesterday (dont know where but i Saw someone saying that It need Magisk, i flashed It and It worked).
But i turned back to oficial miui 11, my sim card was not working with this beta
Click to expand...
Click to collapse
Gapps or any google related services doesnt seem to be working with this beta. lots of bugs encountered too, i might just go back to havoc os
Yunus Ceyhan said:
Use chinese twrp
Click to expand...
Click to collapse
Got it working already. just had to flash magisk along with the rom
I finally unlocked my bootloader todaye and tried to flash Crdroid following the Munchy youtube tutorial as well as the instructions on the Crdroid forum post.
I've used TWRP 3.9 skkk and the Crdroid build from 28/07/22. Everything was going as planned until i rebooted back in to recovery after flashing the Crdroid ROM. I went to try and flash Gapps and Magisk but no I longer had access to the phones internal storage even though I flashed the ROM from my internal storage. I plugged in my USB stick which also had the Gapps and Magisk files and I flashed them without any errors and then rebooted again.
After rebooting I cant even select internal storage, it stays "stuck" on OTG storage and the internal storage is reported to be "0mb". See picture here (I had unplugged the USB stick before taking this picture).
I decided to try and format data but that was unsuccessful, presumably because there's nothing to format!! Please see picture here.
I followed the Munchy tutorial carefully whilst also reading the Crdroid instructions so I really dont know what I did wrong and i'm now just hoping I haven't bricked my phone as its not even 2 weeks old.
I'd be really grateful for some help.
Go back to stock (without locking bootloader) then follow the first time installation instructions in the crdroid thread
So you had crDroid working, and when you've simply booted into TWRP SKKK, you didn't see the Internal Storage? After flashing GApps or...?
Have you used DFE ?
Are you still able to boot the system?
cyanGalaxy said:
So you had crDroid working, and when you've simply booted into TWRP SKKK, you didn't see the Internal Storage? After flashing GApps or...?
Have you used DFE ?
Are you still able to boot the system?
Click to expand...
Click to collapse
I flashed crDroid without any errors but I never attempted to actually boot in to it, i rebooted back in to recovery after flashing the ROM and when i tried to flash Gapps i realised that something had messed up the internal storage.
I have actually managed to fix the problem using the 'repair file system' option in TWRP. I still dont know why things got messed up in the first place though.
use usb otg to install gapps and magisk from that usb.
if you dont have a usb otg, you can use adb sideload
We have the same issue, but I managed to fix it by using the previous version of TWRP 3.6.0 from SKKK and the version you're referring to version of TWRP 3.9.0 is still buggy for now on alioth/aliothin devices.
TWRP SKKK doesn't seem to be all that reliable. :S
Goooober said:
I flashed crDroid without any errors but I never attempted to actually boot in to it, i rebooted back in to recovery after flashing the ROM and when i tried to flash Gapps i realised that something had messed up the internal storage.
I have actually managed to fix the problem using the 'repair file system' option in TWRP. I still dont know why things got messed up in the first place though.
Click to expand...
Click to collapse
Lol so you had a working ROM but got scared...
When u format data + flash new system u lose access to data untill phone boots for the first time - Rebooting recovery at this point let's you flash gapps from external storage/pc to second slot - But magisk can't be flashed before the phone boots , it will say flashed and all but when you boot the phone magisk won't be there
Instead flash gapps then boot the phone , give it few mins to set everything up then reboot twrp and install magisk.
I don't recommend skk when nebrasy twrp exists
What the **** does "SKKK" mean anyway?
Did the dev's cat's paw land on the keyboard?
Goooober said:
I finally unlocked my bootloader todaye and tried to flash Crdroid following the Munchy youtube tutorial as well as the instructions on the Crdroid forum post.
I've used TWRP 3.9 skkk and the Crdroid build from 28/07/22. Everything was going as planned until i rebooted back in to recovery after flashing the Crdroid ROM. I went to try and flash Gapps and Magisk but no I longer had access to the phones internal storage even though I flashed the ROM from my internal storage. I plugged in my USB stick which also had the Gapps and Magisk files and I flashed them without any errors and then rebooted again.
After rebooting I cant even select internal storage, it stays "stuck" on OTG storage and the internal storage is reported to be "0mb". See picture here (I had unplugged the USB stick before taking this picture).
I decided to try and format data but that was unsuccessful, presumably because there's nothing to format!! Please see picture here.
I followed the Munchy tutorial carefully whilst also reading the Crdroid instructions so I really dont know what I did wrong and i'm now just hoping I haven't bricked my phone as its not even 2 weeks old.
I'd be really grateful for some help.
Click to expand...
Click to collapse
happend with my dad's phone wipe userdata from xiaomiADB/Fastboot Tools watched countless indian videos to fix it