Related
So I unlocked this without much trouble, and then when I was attemoting to use adb to flash images to recovery partition, one would just not work, and I stupidly tried to force it, and now it boots and just sits there.
I've seen a different website saying the Q can run Jellybean, and it also has info on getting the stock rom back .. but NO files. I know how to use the damn recovery tools once theyre booted up - those articles were completely useless. I don;t know what else to do. I tried to get the files that argghhhh jad posted to dropbox but they are not available anymore.
Stuck and been trying to fix this for the last 12 hours
EDIT:
Found stock recovery stuff, but I dont think it's going to help any...
Nevermind I suppose
I see that I can try the stock rar file posted for someone else in here to put into recovery, hope it works, I just dont know if the nernel is ok, but I would think so. It stops at the "unlocked"notificaton screen. anyay, yeah. If I get jellybean on instead ill share the info,
I believe you need to fastboot your recovery, not adb. Then you may be able to flash something back on there.
Sent from my XT897 using xda premium
tetrabyt said:
I believe you need to fastboot your recovery, not adb. Then you may be able to flash something back on there.
Sent from my XT897 using xda premium
Click to expand...
Click to collapse
Thanks for the repl! S I actually have been using fastboot because adb for some reason just will not see the device (I checked the version and its correct supposedly). So what I did was take the WWRP rar, pull the contants out and make them into a .zip.and instaled with fastboot flash. The output looked ok:
sending 'userdata' (319120 KB)... OKAY [ 29.814s]
writing 'userdata'... OKAY [ 92.421s]
finished. total time: 122.235s
but what about all the other partitions? I jad done system earlier frok out of the stock zipfile. i think i may just try the entire Stock file insead, or maybe I am missing the fact that I beed to install the kernek into /boot, Any thoughts Thanks much!
EDIT: first im going to fastboot the recovery wit tue TWRP zip file, and try to install it from
I am a little confused, did you manage to get the recovery working? Looks like you were trying to flash the recovery img to your user data partition... Am I misreading your post.
-Saint
Whoaa just saw that. should have unzipped the recovery image and flashed it to the recovery partition with
Fastboot flash recovery recoveryfile.img
Then you can boot into recovery and flash one of the system dumps that these devs have generously posted for when we mess up like this...
Sent from my XT897 using xda premium
tetrabyt said:
Whoaa just saw that. should have unzipped the recovery image and flashed it to the recovery partition with
Fastboot flash recovery recoveryfile.img
Then you can boot into recovery and flash one of the system dumps that these devs have generously posted for when we mess up like this...
Sent from my XT897 using xda premium
Click to expand...
Click to collapse
is this the basic method at present for a stock restore? i was looking at the thread with the files for RSD lite, but i was confused as to whether that was working. thx!
ok so I messed up what to flash from recovery. I had grabbed copies of the system, data, boot, etc for all the partitions thinking i needed to do them all from outside using fastboot,
Herby6262 said:
ok so I messed up what to flash from recovery. I had grabbed copies of the system, data, boot, etc for all the partitions thinking i needed to do them all from outside using fastboot,
Click to expand...
Click to collapse
Ok, the easiest way to get your phone up and running again is to push the newest TWRP from here, put it in your tools folder and push w fastboot:
fastboot flash recovery openrecovery-twrp-2.3.1.0-asanti_c.img
fastboot reboot recovery
Make a backup to your external sd card so that TWRP creates the directory needed to restore the stock system & boot. You should delete this first backup later since it will be broken.
Then download a system & boot image from here, unzip to the /TWRP/BACKUPS/"serial#"/ folder on your external sd. Do full wipes for system, dalvik, & factory reset; then restore Stock from within TWRP. Should be good to go.
:edit:
Just saw that tetrabyt already hit on this, consider this post a more detailed revision.
i must be retardedly doing this the wrong way, i quickly get twrp into recovery and can get in there, and I have the stock photon .zip in 1 big zip and in separate pieces, but how do you get them to the external card.. windows 7 fails to recognize the phone with some message MTP device unknown so I can't transfer it that way ... I dont know. Im about to chuck this thing out the window and be done with it. The whole purpose was to be able to install apps to the sdcard, originally. Only fastboot works from a command prompt, adb doesnt do a damn thing, trying multiple versions of it. I give up
Herby6262 said:
i must be retardedly doing this the wrong way, i quickly get twrp into recovery and can get in there, and I have the stock photon .zip in 1 big zip and in separate pieces, but how do you get them to the external card.. windows 7 fails to recognize the phone with some message MTP device unknown so I can't transfer it that way ... I dont know. Im about to chuck this thing out the window and be done with it. The whole purpose was to be able to install apps to the sdcard, originally. Only fastboot works from a command prompt, adb doesnt do a damn thing, trying multiple versions of it. I give up
Click to expand...
Click to collapse
Do you have an sd adapter or another device you can plug the sd into to transfer from your pc? Does adb fail when booted into TWRP also? Tried uninstalling/re-installing drivers?
Might be able to make a data img you could flash through fastboot, so long as the folder structure was correct... then use recovery from internal storage. Not certain on this: /data/media/sdcard/TWRP/BACKUP/"serial#"/
Maybe someone else can jump in here, this would be my last resort. Use any way possible to get it on external sd first.
-Saint
fallnSaint said:
Do you have an sd adapter or another device you can plug the sd into to transfer from your pc? Does adb fail when booted into TWRP also? Tried uninstalling/re-installing drivers?
Might be able to make a data img you could flash through fastboot, so long as the folder structure was correct... then use recovery from internal storage. Not certain on this: /data/media/sdcard/TWRP/BACKUP/"serial#"/
Maybe someone else can jump in here, this would be my last resort. Use any way possible to get it on external sd first.
-Saint
Click to expand...
Click to collapse
I believe there is a system.img floating around here somewhere.
Check out this thread
http://forum.xda-developers.com/showthread.php?t=1894575
Sent from my XT897 using xda premium
tetrabyt said:
I believe there is a system.img floating around here somewhere.
Check out this thread
http://forum.xda-developers.com/showthread.php?t=1894575
Sent from my XT897 using xda premium
Click to expand...
Click to collapse
Thanks a ton for the help Saint, and others. I finally got it back in working order .. yay! Now to install that powermenu update someone made, and see about making android 4 opeate like the older versions, where you could install apps onto the external SD card. Am I correct in assuming they just F'ed it up by changing the /mnt names, while the software was not updated to accomodate those changes? Why the hell is internal memory now "sdcard" ... so odd. I have a friend whose internal storage is named "USB storage" on his phone. It's USB accessible .. but its a freakin flash card. So odd, and stupid. I really felt like 4.0 was a downgrade, personally. What improved? I see nothing, only things taken away (Im sure the underlying scheduler and thread management/memory mgmt is better, but you know what I mean .. anything visible?)
Herby6262 said:
Thanks a ton for the help Saint, and others. I finally got it back in working order .. yay! Now to install that powermenu update someone made, and see about making android 4 opeate like the older versions, where you could install apps onto the external SD card. Am I correct in assuming they just F'ed it up by changing the /mnt names, while the software was not updated to accomodate those changes? Why the hell is internal memory now "sdcard" ... so odd. I have a friend whose internal storage is named "USB storage" on his phone. It's USB accessible .. but its a freakin flash card. So odd, and stupid. I really felt like 4.0 was a downgrade, personally. What improved? I see nothing, only things taken away (Im sure the underlying scheduler and thread management/memory mgmt is better, but you know what I mean .. anything visible?)
Click to expand...
Click to collapse
Good to hear, glad you got her working again. As for how she runs, definitely snappier than older versions of android. Maybe just hardware, but I still see improvements w the wifes epic running ics, guessing that we will see better results once CM is dropped for this phone.
-Saint
Tried this, still stuck on Bootloader Unlocked Screen. TWRP restores don't seem to work right. I tried restoring an old backup I had of the boot/recovery/system with no luck. Everytime I wiped system/dalvik/cache/factory reset before restore. No errors show up.
So, I can go into fastboot, and I can flash files.
I tried RSD Lite 5.7 with this Zip
It flashes everything until RSD wants me to reboot. Then it reboots and gets stuck on the bootloader unlocked screen.
Any ideas?
[Edit] I flash CWM and found out that I can't mound /sdcard which doesn't seem right...
fallnSaint said:
Ok, the easiest way to get your phone up and running again is to push the newest TWRP from here, put it in your tools folder and push w fastboot:
fastboot flash recovery openrecovery-twrp-2.3.1.0-asanti_c.img
fastboot reboot recovery
Make a backup to your external sd card so that TWRP creates the directory needed to restore the stock system & boot. You should delete this first backup later since it will be broken.
Then download a system & boot image from here, unzip to the /TWRP/BACKUPS/"serial#"/ folder on your external sd. Do full wipes for system, dalvik, & factory reset; then restore Stock from within TWRP. Should be good to go.
:edit:
Just saw that tetrabyt already hit on this, consider this post a more detailed revision.
Click to expand...
Click to collapse
After RSD Lite, it might not have booted up because the system image was removed from the file to make it work. Probably if you flash TWRP after doing the RSD file, and restore Rangerbry's system backup, you might be good..
No Luck.
Just tried this.
Got the following Errors during only system restore:
E:Unable to mount '/cache'
E:unable to mount '/data'
Still stuck on Unlocked bootloader screen.
My emmc might be corrupted I think
I do have sprint insurance. Think they can reflash stock?
yogi2010 said:
After RSD Lite, it might not have booted up because the system image was removed from the file to make it work. Probably if you flash TWRP after doing the RSD file, and restore Rangerbry's system backup, you might be good..
Click to expand...
Click to collapse
coolroman123 said:
No Luck.
Just tried this.
Got the following Errors during only system restore:
E:Unable to mount '/cache'
E:unable to mount '/data'
Click to expand...
Click to collapse
Was that in CWM or TWRP recovery? Just trying to make sure the process was correct, haha. I have only started using TWRP on this device, but i think the 2 recoveries use different backup formats?
coolroman123 said:
Tried this, still stuck on Bootloader Unlocked Screen. TWRP restores don't seem to work right. I tried restoring an old backup I had of the boot/recovery/system with no luck. Everytime I wiped system/dalvik/cache/factory reset before restore. No errors show up.
So, I can go into fastboot, and I can flash files.
I tried RSD Lite 5.7 with this Zip
It flashes everything until RSD wants me to reboot. Then it reboots and gets stuck on the bootloader unlocked screen.
Any ideas?
[Edit] I flash CWM and found out that I can't mound /sdcard which doesn't seem right...
Click to expand...
Click to collapse
Can you boot to bootloader or just to fastboot? There are two control files in that RSD zip, one doesn't flash bootloader, try removing that one and forcing the reflashed bootloader. Then try restoring again. About all I can think of if it successfully flashes the other components... Maybe just restore system and not boot or data?
-Saint
Everything you need is here to return to stock WITH ota update.
http://forum.xda-developers.com/showthread.php?t=2001226
The only thing simple is the belief in simplicity.
i have an asus tf300, unlocked with CWM v6.0.2.3 jelly bean whatever... i wiped data and factory reset it except im in a boot loop now where i can turn the device off... except it will load straight into clockworkmod without me doing anything... now that would be all fine and **** except one thing whoch has been pissing me off all day and every single comandy in CWM is either an error or it just cant do it... im able to reboot and all that but i deadset dont know what to do atm???
owk so i can side load a package but im not sure about that but im guessing im going to have to flash a new rom onto my tablet but how do i sideload it??
Can you mount an external SD card? Also, does "adb devices" or "fastboot devices" show anything?
Were you on Android 4.1 or 4.2 when you installed cwm?
worhello said:
Were you on Android 4.1 or 4.2 when you installed cwm?
Click to expand...
Click to collapse
4.2
with a custom CWM for JB tf300t
even though that was the correct unstallaition i am unable to mount any of the kind.
c0ded said:
Can you mount an external SD card? Also, does "adb devices" or "fastboot devices" show anything?
Click to expand...
Click to collapse
if your talking about mounting a sd card through CWM no. CWM will say "error mounting sdcard" or something like that....
i am using my tablet now but only by forcing adb to put me into bootloader once the device boots straight into CWM automatically which im not sure how it does that? anyway i can cold boot android... my devices is not rooted either because of the situation i am in...
once i am normally in bootloader where i have the selection of 'RCK', 'COLD BOOT'and "WIPE DATA' ... adb doesnt pick up the device any more which isnt a bad thing but i can fast boot comand it and if i try and flash a new recovery.img over the existing no luck and the device freezes and i have to manually reboot...
at the moment im going through CWM, and trying to side load files through that i might try to sideload the 'root.zip' in hope it may root my device... ill cold boot my device after that.
run terminal
and force a recovery.img overwrite from within that which apparently it works that why....
im pretty sure that sideloading is my best bet at the moment but its all try and error... with alot of errors at the moment...... dammmm it i would not be here if that friggen CWM worked properlly and mounted its self for once ahahh wouldnt of wiped the data and done exactly what a load of other peple have done when there CWM did the exact same thing crazy ae
Why not try flashing twrp 2.5 in fastboot? Maybe it was just a bad recovery image?
worhello said:
Why not try flashing twrp 2.5 in fastboot? Maybe it was just a bad recovery image?
Click to expand...
Click to collapse
It is a promblem with the recovery.img but i tried twrp2.5 aswell in bootloader but yeahh same thing it will freeze and i am yet agian to manully reboot my device
I finally successfully flashed TwistedKat (2.5). Everything seems to work fine so far, except I don't have the external storage ("SD card") mounted.
Several apps complains about this, and I suspect this is also why the camera app closes immediately.
Any suggestions?
qabi said:
I finally successfully flashed TwistedKat (2.5). Everything seems to work fine so far, except I don't have the external storage ("SD card") mounted.
Several apps complains about this, and I suspect this is also why the camera app closes immediately.
Any suggestions?
Click to expand...
Click to collapse
Go into recovery and remount your internal sd card and see if that works.
emmanuel_baez said:
Go into recovery and remount your internal sd card and see if that works.
Click to expand...
Click to collapse
It doesn't. I just says that it is unable to mount it.
-dennis
That's no good. Well if your that was actually happening to me yesterday. You may have to flash back to stock using an ruu. Worked perfectly for me. You must relock your bootloader however and you will lose root and your custom recovery after you do flash the the ruu.
Sent from my SM-N900T using xda app-developers app
emmanuel_baez said:
You may have to flash back to stock using an ruu. Worked perfectly for me.
Click to expand...
Click to collapse
That seems sort of dramatic. There must be a way to troubleshoot this problem further - any suggestions guys?
qabi said:
That seems sort of dramatic. There must be a way to troubleshoot this problem further - any suggestions guys?
Click to expand...
Click to collapse
Easy solution: Flash stock RECOVERY only, go to bootloader --> perform "clear storage" --> flash custom recovery again
--> Everything should be fine again
LS.xD said:
Easy solution: Flash stock RECOVERY only, go to bootloader --> perform "clear storage" --> flash custom recovery again
--> Everything should be fine again
Click to expand...
Click to collapse
+1
I had this problem time ago and with these steps work again.
LS.xD said:
Easy solution: Flash stock RECOVERY only, go to bootloader --> perform "clear storage" --> flash custom recovery again
Click to expand...
Click to collapse
Thanks for the suggestion. Still doesn't work:
1) Reflashed stock recovery and chose "Clear Storage", system booted up into android, lost all/most settings/configuration but still no external storage when attempting to start camera or gallery app.
2) Reflashed custom recovery and attempted to mount /storage/sdcard0: "Error mounting /storage/sdcard0!"
Did I do something wrong in the above?
qabi said:
Thanks for the suggestion. Still doesn't work:
1) Reflashed stock recovery and chose "Clear Storage", system booted up into android, lost all/most settings/configuration but still no external storage when attempting to start camera or gallery app.
2) Reflashed custom recovery and attempted to mount /storage/sdcard0: "Error mounting /storage/sdcard0!"
Did I do something wrong in the above?
Click to expand...
Click to collapse
1. Flash stock recovery
2. reboot to bootloader and perform "clear storage" (While in bootloader NOT in recovery)
3. Flash custom recovery again (Must be compatible to Android 4.4.2)
4. Reboot bootloader again
5. THEN boot android (Not at any time before)
In that case it still won't work:
Flash stock recovery --> perform "factory reset + clear storage" -> flash custom recovery again --> flash TwistedKat v2.5 again.
BTW Are you S-ON or S-OFF (Have you flashed TwistedKat kernel if you're S-on?)
LS.xD said:
First flash custom recovery BEFORE booting android and select "Clear storage" in bootloader mode not within the recovery !!!!!
In that case it still won't work:
Flash stock recovery --> perform "factory reset + clear storage" -> flash custom recovery again --> flash TwistedKat v2.5 again.
BTW Are you S-ON or S-OFF (Have you flashed TwistedKat kernel if you're S-on?)
Click to expand...
Click to collapse
Ok, got it. But when choosing clear storage it boots automatically? I didn't do anything. So you need to be pressing vol down button the whole time?
The device is S-ON. Don't know about flashing a kernel, but since I don't know I probably didn't flash this.
qabi said:
Ok, got it. But when choosing clear storage it boots automatically? I didn't do anything. So you need to be pressing vol down button the whole time?
The device is S-ON. Don't know about flashing a kernel, but since I don't know I probably didn't flash this.
Click to expand...
Click to collapse
Device will not boot up automatically as far as i know.
S-ON means you have to flash the kernel manually.
Open cmd:
"fastboot flash boot boot.img"
...
LS.xD said:
"fastboot flash boot boot.img"
Click to expand...
Click to collapse
Oh, so boot.img is the kernel In that case, yes I did
Also: good news. To answer my own question, I had to hold the volume down button in, to not reboot but enter the bootload instead. Thus following your steps above worked like a charm.
Thanks a million!
I know there is another very similar thread that was just opened(http://forum.xda-developers.com/oneplus-one/help/completely-stock-oneplus-one-stuck-t3396207), but his solution didn't help me so I'm making this thread.
I really need to save my internal data, so only as a last resort will I wipe userdata to save my phone.
First of all my phone is completely stock. Locked bootloader, unrooted, stock recovery, and stock rom. Last thursday(June 9th), I got the CM13.1 OTA update which I installed and everything went normal. It finished installing, restarted and booted up, optimized apps, rebooted, but then optimized apps again and again. I thought it might help to just reboot my phone, but it didn't. So I immediately started looking around for solutions.
I can boot into recovery and fastboot mode and since I can boot into recovery I started with wiping cache(Stock Recovery>>Factory reset>>Wipe cache partition). It took ~20mins which seemed like an unusually long time, then I rebooted and it still got stuck in the "optimizing apps/reboot loop". Next, I set up USB drivers, ADB, and fastboot since it seems to be very important to have those set up. I used a few guides to get them properly set up and I checked that they were correct by checking that the cmds "adb devices" and "fastboot devices" returned my device, which they did. I saw someone saying he saved his friends OPO by just ADB sideloading a CM zip file, so it looked hopeful in my case. I downloaded cm 13.0 and 13.1 zip files and tried sideloading them with the cmd "adb sideload cm13.zip". I tried both and they both got to around 50% complete and the install failed. Some of the red text said, "Package expects build fingerprint of oneplus/bacon/A0001:5.1:6.0.1..... & E:Failed to install /sideload/packages.zip ". Next I tried installing TWRP, which looks like it requires an unlocked bootloader to flash it(even to to just boot into it). From all my research it looks like there's no way to unlock the bootloader without wiping data. Even the OPO toolkit says you need to wipe data to unlock your bootloader.
One thing I haven't looked too much into is using fastboot to save my device. This guide http://www.technobuzz.net/fix-bricked-dead-oneplus-one-easily/ shows to flash userdata userdata_64g.img, which I assume wipes userdata.
Maybe I'm just overlooking some simple fix, but if anyone can help me I would be eternally grateful.
Edit: I need my phone working and I'm tired of waiting for help, so I just did a factory rest. Also I've been getting tons of conflicting advice. Thanks everyone for the help anyways
kinda on the same boat here.
may i ask how you set up adb? i cant get it to work
mastersen901 said:
kinda on the same boat here.
may i ask how you set up adb? i cant get it to work
Click to expand...
Click to collapse
download and install the 15 second adb/fastboot installer (http://forum.xda-developers.com/showthread.php?t=2588979)
It'll create a folder: C:/adb, In that folder you can open a cmd prompt window to send cmds to your device through adb/fastboot. that folder is also where you place files that you want to flash or boot into.
Also for the USB drivers just download the oneplus one toolkit, or use this guide: http://www.technobuzz.net/install-oneplus-one-usb-drivers-windows/
the opo toolkit is in the 2nd method
Still looking for help. Phone status: After sideloading cm 12.1 it boots up but I get tons of errors saying com.android.phone failed/ android.system.acore failed which make my phone inoperable, also my phone usually reboots after ~10 seconds after booting up and getting errors.
when you flashed the stock zip via sideloading did you use the full zip or the incremental zip?
itechy said:
when you flashed the stock zip via sideloading did you use the full zip or the incremental zip?
Click to expand...
Click to collapse
The zip I sideloaded was cm-12.1-YOG4PAS1N0-bacon-signed.zip (http://builds.cyngn.com/cyanogen-os...be76f9310/cm-12.1-YOG4PAS1N0-bacon-signed.zip)
I'm pretty sure it's the full zip
woodhaus said:
The zip I sideloaded was cm-12.1-YOG4PAS1N0-bacon-signed.zip (http://builds.cyngn.com/cyanogen-os...e76f9310/cm-12.1-YOG4PAS1N0-bacon-signed.zip)
I'm pretty sure it's the full zip
Click to expand...
Click to collapse
You will have to flash the latest version as performing a downgrade without wiping data will cause issues like the ones you are seeing
Sent from my A0001 using XDA Labs
itechy said:
You will have to flash the latest version as performing a downgrade without wiping data will cause issues like the ones you are seeing
Sent from my A0001 using XDA Labs
Click to expand...
Click to collapse
I can't really find a full cm13.1 zip. On CyanogenMod I only see up to 13.0. I also don't know how to tell the difference between an incremental and full zip D:
woodhaus said:
I can't really find a full cm13.1 zip. On CyanogenMod I only see up to 13.0. I also don't know how to tell the difference between an incremental and full zip D:
Click to expand...
Click to collapse
Visit the support page I grabbed my full update zip from there https://cyngn.com/support
Sent from my A0001 using XDA Labs
itechy said:
Visit the support page I grabbed my full update zip from there https://cyngn.com/support
Sent from my A0001 using XDA Labs
Click to expand...
Click to collapse
Ohh! thanks! I was looking for this!
I just got around to sideloading the cm 13.1 zip. I'm still getting a bootloop /:
Edit: My phone reboots and optimizes apps after getting hung up on the cyanogen boot screen for a while.
I'm in the same situation.
It seems like a cache cleaning is needed but I have no idea whether it possible without a custom recovery and without a full adb support.
hibernick said:
I'm in the same situation.
It seems like a cache cleaning is needed but I have no idea whether it possible without a custom recovery and without a full adb support.
Click to expand...
Click to collapse
You can wipe cache partition in stock recovery also. To boot into recovery mode first power off your device. Press Volume down + Power button together until you see oneplus logo. When device is in recovery mode press volume down and select 'wipe cache partition' and press power button to confirm the action. Reboot after process completes.
saurav007 said:
You can wipe cache partition in stock recovery also. To boot into recovery mode first power off your device. Press Volume down + Power button together until you see oneplus logo. When device is in recovery mode press volume down and select 'wipe cache partition' and press power button to confirm the action. Reboot after process completes.
Click to expand...
Click to collapse
The same like woodhaus I have locked bootloader and there is no USB debug over adb.
I don't have a 'wipe cache partition' in the recovery.
The only things I can use are adb sideload and fastboot.
hibernick said:
The same like woodhaus I have locked bootloader and there is no USB debug over adb.
I don't have a 'wipe cache partition' in the recovery.
The only things I can use are adb sideload and fastboot.
Click to expand...
Click to collapse
I have wipe cache partition but it doesn't seem to do anything. also it takes like 35 minutes to complete
woodhaus said:
I have wipe cache partition but it doesn't seem to do anything. also it takes like 35 minutes to complete
Click to expand...
Click to collapse
How did you do it?
You told you are on stock recovery. Me either and I don't see such option in my recovery.
hibernick said:
How did you do it?
You told you are on stock recovery. Me either and I don't see such option in my recovery.
Click to expand...
Click to collapse
it's under the factory reset option from the main menu on stock recovery
stock recovery>factory reset> erase cache partition
woodhaus said:
it's under the factory reset option from the main menu on stock recovery
stock recovery>factory reset> erase cache partition
Click to expand...
Click to collapse
Oh, thanks. I didn't even go there.
I have a Redmi note 8 with MIUI 12 installed. Bootloader is unlocked and the phone is rooted.
When I try to flash TWRP recovery in fastboot mode using my PC, it successfully flashes and boots into the TWRP recovery. TWRP does not ask for any password for decrypting the files, and when I go to install>sdcard then the storage is all in random letters, completely unrecognizable.
I have tried a lot of tutorials on youtube but none of them worked. I tried flashing the latest version of TWRP, didn't work. I tried formatting all data and rebooting back into recovery mode, didn't work. (if you reboot to system after installing TWRP, the phone automatically deletes TWRP and the next time you open recovery mode you just get the default MI recovery, and you have to flash TWRP again to open TWRP recovery.) I tried almost everything on the internet but none of it worked. Is there any way I can make it ask for the decryption password? or have my files decrypted? I just need the TWRP for a one-time-use to install a custom ROM. I don't need it to be installed permanently, but no problem even if it does get installed permanently. I just want my custom ROM.
Please help
does that work?:
Boot into twrp, then
Code:
adb shell
twrp decrypt myPassword
(myPassword is your user password)
User699 said:
does that work?:
Boot into twrp, then
Code:
adb shell
twrp decrypt myPassword
(myPassword is your user password)
Click to expand...
Click to collapse
It didnt work, "failed to decrypt data" i typed the right password
#JKTheBaskieBoy said:
It didnt work, "failed to decrypt data" i typed the right password
Click to expand...
Click to collapse
Okay, interessting. What's the exact error?
However, since you only want to use twrp to flash a custom OS, you could try to boot twrp (without flashing)
Code:
fastboot boot twrp.img
and then wipe data via twrp and then install your custom OS. You can use sideload which should be located under "advanced" I guess.
Code:
adb sideload myCustomOS.zip
EDIT: Don't boot out of twrp before sideloading, since your os should encrypt everything again after wiping which makes it unpossible for twrp to decrypt again (at least in your case, since it failed for some reason).
If you booted out of twrp, just wipe again and then sideload.
the correct and recommend way to install TWRP is
Flash TWRP
Erase userdata partition <~ it's important to do this as soon as possible since booting your device would just encrypt everything again
Format userdata partition
by doing this you would be able to access data partition files and folder would not be random letters.
User699 said:
Okay, interessting. What's the exact error?
However, since you only want to use twrp to flash a custom OS, you could try to boot twrp (without flashing)
Code:
fastboot boot twrp.img
and then wipe data via twrp and then install your custom OS. You can use sideload which should be located under "advanced" I guess.
Code:
adb sideload myCustomOS.zip
EDIT: Don't boot out of twrp before sideloading, since your os should encrypt everything again after wiping which makes it unpossible for twrp to decrypt again (at least in your case, since it failed for some reason).
If you booted out of twrp, just wipe again and then sideload.
Click to expand...
Click to collapse
Sorry for the late reply. Earlier i just gave up on installing the custom ROM and continued with my stock from. Today a tried again, installed TWRP and turns out it is not showing random letters now. its all regular storage. i didn't even do anything to decrypt it lol it just fixed itself. Now I will install the room myself. Thank you for your help though
Ah sh** here we go again. So i installed the custom rom successfully and everything worked fine, the TWRP too. but when I tried to flash a magisk patched image (the image that I used to root my phone in MIUI) then it got stuck in the boot screen. I had to flash the stock fastboot rom again.. And as expected from my piece of **** that xiaomi calls a phone, TWRP will show encrypted folders, and does not ask for a password. Same problem. Rooted my phone again, using the magisk root image, and it worked like usual, the phone rooted. Now i am stuck again in this bs. I guess I will wait for about 4-5 days and continue using the phone like normal. Maybe it will work again this time. I will try your method here first
User699 said:
Okay, interessting. What's the exact error?
However, since you only want to use twrp to flash a custom OS, you could try to boot twrp (without flashing)
Code:
fastboot boot twrp.img
and then wipe data via twrp and then install your custom OS. You can use sideload which should be located under "advanced" I guess.
Code:
adb sideload myCustomOS.zip
EDIT: Don't boot out of twrp before sideloading, since your os should encrypt everything again after wiping which makes it unpossible for twrp to decrypt again (at least in your case, since it failed for some reason).
If you booted out of twrp, just wipe again and then sideload.
Click to expand...
Click to collapse
Okay i tried wiping the data, cache and dalvik but it shows a huge essay of "error opening xxx/xxxx" in red text. Data wipe failed.
See you after like 4-5 days... hopefully
Update. I finally found a solution. It took literal hours of experimenting to find this.
-Flashed the fastboot ROM of the phone
-Rooted the phone by flashing magisk patched image
-Flashed Inception kernel via FK kernel manager
-Rebooting after flashing the kernel, It will get stuck in a black screen with no text whatsoever (probably a bootloop)
-Installed TWRP (This time TWRP does not show encrypted letters), Wiped all data, Transferred the custom ROM zip to the phone (while in TWRP) and flashing the rom
-The rom is flashed successfully. On the first reboot you get greeted with another bootloop. Fortunately the phone booted into TWRP. This time the folders are encrypted again.
-Successfully wiped the data (advanced>wipe data). No errors in data wiping this time.
-A fully working Corvus OS setup appears on rebooting.
I think the whole TWRP problem was fixed by the custom kernel. Anyways I am finally done with this now. You probably enjoyed seeing all this xD
#JKTheBaskieBoy said:
Update. I finally found a solution. It took literal hours of experimenting to find this.
-Flashed the fastboot ROM of the phone
-Rooted the phone by flashing magisk patched image
-Flashed Inception kernel via FK kernel manager
-Rebooting after flashing the kernel, It will get stuck in a black screen with no text whatsoever (probably a bootloop)
-Installed TWRP (This time TWRP does not show encrypted letters), Wiped all data, Transferred the custom ROM zip to the phone (while in TWRP) and flashing the rom
-The rom is flashed successfully. On the first reboot you get greeted with another bootloop. Fortunately the phone booted into TWRP. This time the folders are encrypted again.
-Successfully wiped the data (advanced>wipe data). No errors in data wiping this time.
-A fully working Corvus OS setup appears on rebooting.
I think the whole TWRP problem was fixed by the custom kernel. Anyways I am finally done with this now. You probably enjoyed seeing all this xD
Click to expand...
Click to collapse
I like that you keep trying and finding a solution, even though you had to invest hours to make it work!
Let's hope it will work if you update the OS though – I'd actually suggest a backup of all of your data before you do an update in the future, just to be safe!
#JKTheBaskieBoy said:
I have a Redmi note 8 with MIUI 12 installed. Bootloader is unlocked and the phone is rooted.
When I try to flash TWRP recovery in fastboot mode using my PC, it successfully flashes and boots into the TWRP recovery. TWRP does not ask for any password for decrypting the files, and when I go to install>sdcard then the storage is all in random letters, completely unrecognizable.
I have tried a lot of tutorials on youtube but none of them worked. I tried flashing the latest version of TWRP, didn't work. I tried formatting all data and rebooting back into recovery mode, didn't work. (if you reboot to system after installing TWRP, the phone automatically deletes TWRP and the next time you open recovery mode you just get the default MI recovery, and you have to flash TWRP again to open TWRP recovery.) I tried almost everything on the internet but none of it worked. Is there any way I can make it ask for the decryption password? or have my files decrypted? I just need the TWRP for a one-time-use to install a custom ROM. I don't need it to be installed permanently, but no problem even if it does get installed permanently. I just want my custom ROM.
Please help
Click to expand...
Click to collapse
tell me how to turn off a smartphone with a non-working sensor?
you can still use adb push command from pc to transfer files to your phone :
adb push "nameoffile" /sdcard
(place the file in your adb folder) I was able to root a phone that had this issue using this technique.
I think u should flash dm verity becoz when i flashed the rom and flashed dm verity it worked fine