Hello,
Does anyone know how to decrypt the OnePlus 3 yet? I used Garak's latest recovery image.
I tried rooting my OnePlus 3 that arrived in the mail today. To root, I had to OEM unlock the phone. I followed this guide : http://forum.xda-developers.com/oneplus-3/how-to/oneplus-3-how-to-unlock-bootloader-t3398733. I got to the rooting part of the guide, but I was dumb and formatted 'userdata', since the phone started bootlooping. Now I'm in a situation where adb sideload won't upload the ROM 100% (Oxygen OS 3.1.3 found here: http://forum.xda-developers.com/oneplus-3/how-to/stock-firmare-oxygenos-3-1-3-oneplus-t3400384) (always fails at ~50%), TWRP unable to mount storage due to encryption, and no installed operating system. Even worse, I didn't save a backup.
Could anybody help me out? Thanks!
PROBLEM SOLVED!
Loose wires = bad
Appending the command "fastboot format userdata" again fixed the encryption issue and granted me access to my device's storage, which allowed me to fix my other problems.
kentexcitebot said:
PROBLEM SOLVED!
Loose wires = bad
Appending the command "fastboot format userdata" again fixed the encryption issue and granted me access to my device's storage, which allowed me to fix my other problems.
Click to expand...
Click to collapse
Hi, you used format instead of erase?
mirko8054 said:
Hi, you used format instead of erase?
Click to expand...
Click to collapse
Yes. Use the format command.
Next time, create a new thread instead of responding to an old post.
Red "unable to mount storage" line in TWRP boot sequence
kentexcitebot said:
Yes. Use the format command.
Next time, create a new thread instead of responding to an old post.
Click to expand...
Click to collapse
Hi,
I'm posting here since I couldn't really find any thread related for the OP3.
I happen to have this red "unable to mount storage" line during my twrp booting sequence, right after inputting my PIN or password. Even though after that I'm able to get to TWRP and back to my system with everything "apparently" working fine.
I've joined a pic of the sequence, and would like to know if this IS a problem and/or anything to solve it.
Thanx in advance.
FlyingMachete said:
Hi,
I'm posting here since I couldn't really find any thread related for the OP3.
I happen to have this red "unable to mount storage" line during my twrp booting sequence, right after inputting my PIN or password. Even though after that I'm able to get to TWRP and back to my system with everything "apparently" working fine.
I've joined a pic of the sequence, and would like to know if this IS a problem and/or anything to solve it.
Thanx in advance.
Click to expand...
Click to collapse
If decrypt was successfull it shouldn't ask you to enter pin, you could try to repeat process and flash twrp again.
mirko8054 said:
If decrypt was successfull it shouldn't ask you to enter pin, you could try to repeat process and flash twrp again.
Click to expand...
Click to collapse
Thanx for your reply, though it's asking for my security pin cause I have one for entering the system like you would have a scheme or password. It doesn't ask it if I take it off in the OS. And like you can see on the screenshot, decryption is still happening after that and is succesful. I've already gone through updates of twrp by the past but always had this "line" as far as I remember. Still can't figure out what that is.
FSociety 4 Life
FlyingMachete said:
Hi,
I'm posting here since I couldn't really find any thread related for the OP3.
I happen to have this red "unable to mount storage" line during my twrp booting sequence, right after inputting my PIN or password. Even though after that I'm able to get to TWRP and back to my system with everything "apparently" working fine.
I've joined a pic of the sequence, and would like to know if this IS a problem and/or anything to solve it.
Thanx in advance.
Click to expand...
Click to collapse
Its perfectly normal. Its happening like this
1-twrp tries to mount partitions but storage is encrypted
2-then it asks for password
3-then twrp decrypts it
4- boom its done and decrypted partitions are mounted
Dupleshwar said:
Its perfectly normal. Its happening like this
1-twrp tries to mount partitions but storage is encrypted
2-then it asks for password
3-then twrp decrypts it
4- boom its done and decrypted partitions are mounted
Click to expand...
Click to collapse
That's how I was seeing it, Thanx a lot for your reply!
FSociety 4 Life
FlyingMachete said:
That's how I was seeing it, Thanx a lot for your reply!
FSociety 4 Life
Click to expand...
Click to collapse
How long does it really take to decrypt new phone without any apps? Just to have an idea. When I started TWRP it asked for password and I used the PIN assigned to login to screen ... now going on for 5 minutes now. Following on the screen:
Mount
Try Decryption
Updating partition details...
....done
Unable to mount storage
Full SELinux support present
----------------------------------------------------- blue animation
junostik said:
How long does it really take to decrypt new phone without any apps? Just to have an idea. Mine is going on for 5 minutes now. Following on the screen:
Mount
Try Decryption
Updating partition details...
....done
Unable to mount storage
Full SELinux support present
----------------------------------------------------- blue animation
Click to expand...
Click to collapse
It takes just a few seconds for me.
FlyingMachete said:
It takes just a few seconds for me.
Click to expand...
Click to collapse
Should I reboot? I am worried it might cause an issue, please advise.
junostik said:
Should I reboot? I am worried it might cause an issue, please advise.
Click to expand...
Click to collapse
Force reboot it. Then First you should look for the very last modified TWRP that came out 2-3 days ago. Called 3.0.2-0 v11 Blu spark. Only if you're already using f2fs partition. As it's now fully compatible with nougat and f2fs. You can flash it via fastboot or if you can still access your system, via flashify.
FlyingMachete said:
Force reboot it. Then First you should look for the very last modified TWRP that came out 2-3 days ago. Called 3.0.2-0 v11 Blu spark. Only if you're already using f2fs partition. As it's now fully compatible with nougat and f2fs. You can flash it via fastboot or if you can still access your system, via flashify.
Click to expand...
Click to collapse
Thank you, any idea where can I download TWRP 3.0.2-0 v11 Blu spark for 3T? sorry, not able to find any where.
junostik said:
Thank you, any idea where can I download TWRP 3.0.2-0 v11 Blu spark for 3T? sorry, not able to find any where.
Click to expand...
Click to collapse
I'm not on 3T but almost sure i saw something about it on the 3T forums. Search there if not look for the Blu spark team threads or repositories on github. You can also search the posts by developer @eng.stk here on XDA.
junostik said:
Thank you, any idea where can I download TWRP 3.0.2-0 v11 Blu spark for 3T? sorry, not able to find any where.
Click to expand...
Click to collapse
latest modified TWRP by eng.stk here https://forum.xda-developers.com/devdb/project/dl/?id=22429
Sent from my ONEPLUS A3000 using XDA-Developers Legacy app
Flashed this one and I still can't decrypt my storage in recovery. Any other ideas that are working?
Dr. MadMan said:
Flashed this one and I still can't decrypt my storage in recovery. Any other ideas that are working?
Click to expand...
Click to collapse
Hello, can you please confirm if your storage is ext4 or f2fs?
it's ext4
Dr. MadMan said:
it's ext4
Click to expand...
Click to collapse
Then you are is same boat as many of us. No twrp recovery has support for nougat on ext4 file system. Eng stk has made a compatible recovery with f2fs file system. The only workaround I have found is to use that recovery with no password/pin for system. It will work flawlessly then. I anyways need twrp rarely so it's no hassle for me.
Related
Hey guys I want to get into twrp recovery but after staying on the 'entering recovery' screen it will reboot . It worked fine till today and I tried reflashing it to no avail. Any suggestions?
Sent from my HTC One_M8 using XDA Free mobile app
Boot into fastboot and type "fastboot erase cache" then flash the recovery.
Try it with both CWM and TWRP.
i4GS said:
Boot into fastboot and type "fastboot erase cache" then flash the recovery.
Try it with both CWM and TWRP.
Click to expand...
Click to collapse
Yup. Wipe cache and install recovery again, usually solves this.
redpoint73 said:
Yup. Wipe cache and install recovery again, usually solves this.
Click to expand...
Click to collapse
I tried this but it still wouldn't boot into recovery. I then tried installing an older version on TWRP and finally it booted properly. I was looking through it and something caught my eye. MY ENTIRE INTERNAL STORAGE WAS WIPED!!! I have no idea how this happened!! I tried restoring from my sd card but it couldnt mount /data. Would adb sideloading a ROM work do you think?
ILIVE4HEAD said:
I was looking through it and something caught my eye. MY ENTIRE INTERNAL STORAGE WAS WIPED!!! I have no idea how this happened!! I tried restoring from my sd card but it couldnt mount /data. Would adb sideloading a ROM work do you think?
Click to expand...
Click to collapse
It may or may not. Or if it flashes, you might not be able to mount any data partitions or cache.
Try connecting to a PC, and formatting the internal storage with Device Manager.
redpoint73 said:
Yup. Wipe cache and install recovery again, usually solves this.
Click to expand...
Click to collapse
redpoint73 said:
It may or may not. Or if it flashes, you might not be able to mount any data partitions or cache.
Try connecting to a PC, and formatting the internal storage with Device Manager.
Click to expand...
Click to collapse
Last time i couldn't mount /data i just rebooted into recovery and let it sit for a day then it was fine... when I'm about to try to reboot into recovery though it says "no OS installed, are you sure you want to reboot?" will it be safe to reboot?
I hope you get your issues sorted soon. Don't know what i can contribute to help you achieve that. You seem to have more issues than one, but i like to give you one tip and that is to stay in one thread only. I seen you around now in multiple threads and its getting confusing on your actual status. Please don't take this the wrong way, it's very well ment advice
Cheers.
ILIVE4HEAD said:
when I'm about to try to reboot into recovery though it says "no OS installed, are you sure you want to reboot?" will it be safe to reboot?
Click to expand...
Click to collapse
Should be safe. You won't have an OS, so it will just boot into bootloader.
redpoint73 said:
Should be safe. You won't have an OS, so it will just boot into bootloader.
Click to expand...
Click to collapse
Thanks for your help. You answered many of my questions and were very patient with my questions. I regret to say though that my phone is now bricked. Only bootloader will show up, recovery is a black screen and so is bootup. This wouldn't be so bad if my /data is still corrupted after everthing i tried and no computer will recognize my device. I will come back to xda when I actually know what I'm doing and when my phone isn't as valuable. Thanks again for all your help.
Not sure if this is a similar issue or not but I had some issues getting into recovery after doing Sunshine S-Off today. Had TWRP installed and working fine, but after doing the s-off exploit I would see the recovery screen for a split second before the phone would reboot normally again.
Even running fastboot boot recovery.img to run it directly wasn't working.
However, downloaded and installed CWM instead and all is fine again. Phew
ILIVE4HEAD said:
Thanks for your help. You answered many of my questions and were very patient with my questions. I regret to say though that my phone is now bricked.
Click to expand...
Click to collapse
Its not bricked if the screen comes on. I sincerely think we can get this thing back up and running. A phone that doesn't work isn't "valuable" so you might as well keep at it.
Delete all HTC drivers, and connect the phone to a PC. Go to Device Manager, select the option to manually select drivers, and select the generic Android MTP device.
redpoint73 said:
Its not bricked if the screen comes on. I sincerely think we can get this thing back up and running. A phone that doesn't work isn't "valuable" so you might as well keep at it.
Delete all HTC drivers, and connect the phone to a PC. Go to Device Manager, select the option to manually select drivers, and select the generic Android MTP device.
Click to expand...
Click to collapse
wait I was going to replace it but i succeeded re flashing recovery (don't ask). Where do i go into device manager to reformat my storage?
{EDIT} WTF i flashed cwm and now my phone is up and running again... this after TWRP said i had no OS... Im confused
ILIVE4HEAD said:
wait I was going to replace it but i succeeded re flashing recovery (don't ask).
Click to expand...
Click to collapse
Looks like you solved it. But did you mean you were going to replace the phone? That shouldn't ever be necessary just due to software mods you did, as long as the screen comes on. I've seen only one exception so far, where several users here helped the user exhaust every possible fix to the memory not being mountable and nothing worked, and it might have been a fried emmc chip or similar hardware fault. In your case, I still had plenty of hope, as there were still several options that were not tried.
ILIVE4HEAD said:
wait I was going to replace it but i succeeded re flashing recovery (don't ask). Where do i go into device manager to reformat my storage?
Click to expand...
Click to collapse
Control Panel, under Hardware. Also, if you click the Window button in the taskbar, you can just type Device Manager in the "Search Programs and files" area.
ILIVE4HEAD said:
{EDIT} WTF i flashed cwm and now my phone is up and running again... this after TWRP said i had no OS... Im confused
Click to expand...
Click to collapse
No OS is a known issue for some folks on TWRP. It is puzzling, since it only seem to affect some people. TWRP was pretty rock solid and reliable on my past device, so its a bit disheartening to see it appears to be considerably more buggy on the M8.
So is the phone fully up and running, no issues mounting memory?
redpoint73 said:
Looks like you solved it. But did you mean you were going to replace the phone? That shouldn't ever be necessary just due to software mods you did, as long as the screen comes on. I've seen only one exception so far, where several users here helped the user exhaust every possible fix to the memory not being mountable and nothing worked, and it might have been a fried emmc chip or similar hardware fault. In your case, I still had plenty of hope, as there were still several options that were not tried.
Control Panel, under Hardware. Also, if you click the Window button in the taskbar, you can just type Device Manager in the "Search Programs and files" area.
No OS is a known issue for some folks on TWRP. It is puzzling, since it only seem to affect some people. TWRP was pretty rock solid and reliable on my past device, so its a bit disheartening to see it appears to be considerably more buggy on the M8.
So is the phone fully up and running, no issues mounting memory?
Click to expand...
Click to collapse
I reflashed TWRP and restored one of my backups... i have no idea what happened these past few days but thanks for sticking with me. Thanks again!
ILIVE4HEAD said:
I reflashed TWRP and restored one of my backups... i have no idea what happened these past few days but thanks for sticking with me. Thanks again!
Click to expand...
Click to collapse
You're very welcome. Not sure how much I actually helped, as it sounds like you pretty much figured it out yourself. So nice job!
Hello all!
This morning I updated Magisk Manager.
Once updated (or perhaps only downloaded update) the app prompted a reboot.
I rebooted and ended up in TWRP.
But I did not know what to do in TWRP so I rebooted system...
However, now the phone cannot boot and after one try it reboots into TWRP again.
PLEASE HELP ME!
I need my phone for work! Like now-now! :silly: :crying:
dustylambo said:
Hello all!
This morning I updated Magisk Manager.
Once updated (or perhaps only downloaded update) the app prompted a reboot.
I rebooted and ended up in TWRP.
But I did not know what to do in TWRP so I rebooted system...
However, now the phone cannot boot and after one try it reboots into TWRP again.
PLEASE HELP ME!
I need my phone for work! Like now-now! :silly: :crying:
Click to expand...
Click to collapse
How soon is now ? follow the white rabbit:good:
https://forum.xda-developers.com/zenfone2/help/help-bootloop-to-recovery-t3577504
timbernot said:
How soon is now ? follow the white rabbit:good:
https://forum.xda-developers.com/zenfone2/help/help-bootloop-to-recovery-t3577504
Click to expand...
Click to collapse
Well, that rabbit went into quite the hole... hehe
However, at the other end was a person who restored an old backup to revert this problem... And I -MAYBE- have an old backup on my external hdd, but won't that wipe all data that has been written to my phone since that "MAYBE" backup?
The other suggestion was wiping my MISC-partition using commands through ADB - something I have no clue how to setup and/or execute.
Still, thank you so much for your effort!
Reading all of this made me remember that one time I spaced out and tried to install an official firmware update upon release and prompt, which lead to the same issue. I could then just reinstall an older raw firmware version, which left all my files and data intact. Hopefully this will work here too.
BUT... It still feels very risky. If anyone out there has any sure-fire solution to this update Magisk Manager through the built-in updater no-boot issue, then please feel free to let me know - I would be forever in your debt
The best surefire solution is just don't. And BTW always backup before you flash anything in twrp.
Sent from my ASUS_Z00A using Tapatalk
---------- Post added at 08:49 AM ---------- Previous post was at 08:47 AM ----------
timbernot said:
How soon is now ? follow the white rabbit:good:
https://forum.xda-developers.com/zenfone2/help/help-bootloop-to-recovery-t3577504
Click to expand...
Click to collapse
I love what you did there! Lol
Sent from my ASUS_Z00A using Tapatalk
kenbo111 said:
The best surefire solution is just don't. And BTW always backup before you flash anything in twrp
Click to expand...
Click to collapse
I didn't flash anything in twrp. If you're gonna reply at least read the post. Also, none of what you wrote is a solution, unless you're in possession of a time machine. I'll keep it in mind for the next time though (of which there won't be one). Thanks, captain hindsight.
dustylambo said:
I didn't flash anything in twrp. If you're gonna reply at least read the post. Also, none of what you wrote is a solution, unless you're in possession of a time machine. I'll keep it in mind for the next time though (of which there won't be one). Thanks, captain hindsight.
Click to expand...
Click to collapse
That's what the update does. Reboots to twrp and installs the download. Maybe you should know what you're doing before you snap at us.
Sent from my ASUS_Z00A using Tapatalk
dustylambo said:
However, at the other end was a person who restored an old backup to revert this problem... And I -MAYBE- have an old backup on my external hdd, but won't that wipe all data that has been written to my phone since that "MAYBE" backup?
Click to expand...
Click to collapse
No, just restore the boot partition (16MB).
I learnt the hard way about backup, when years ago I didn't make one for my Galaxy S2 and lost everything (pictures, etc). Now after installing TWRP I always do a backup...
You should be able to reflash your boot partition with a fastboot command like "fastboot flash boot boot.img" (people with more knowledge than me can help you)
EDIT: the problem is that our Zenfone2 needs a signature for the boot partition, this is why we have a special Magisk installer that just add the signature to the image. The automatic update installer of Magisk has no clue about this, me and a few others here made the same mistake as you when Magisk popup "I have an update!" and we clicked "Install"...
All your data and app are still there, do not worry, no need to wipe anything, just reflash a signed boot.
kenbo111 said:
That's what the update does. Reboots to twrp and installs the download. Maybe you should know what you're doing before you snap at us.
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
Look... I am sorry if I "snapped" as you put it... But let's make one thing clear - I snapped at YOU; there is no "us" in this case, as you tried to skew it. Don't lump yourself together with these other helpful people, because so far you have nothing in common to me. If I were looking for someone to go "Hey, I got a solution - you know that thing you did? - Don't do it again!" I'd just go stand on the street corner with a sign asking for someone to slap my face.
As for your principal of don't do things if your not sure of how they work, I am totally behind that. But it has NOTHING to offer here as we are past that point. A broad comparison would be like "a solution to world hunger = eat food" ("but we don't have any food!" "you should have thought of that before you started starving now shouldn't you...?!").
In your defense, I guess you really believe you are trying to help. But compare your comment to the other ones posted and it is quickly clear that you are not. However, YOU ARE RIGHT, I should've known better and shouldn't do it again. And obviously I am enerved at this situation, but equally obvious (now) is that what you wrote is NOT "the best sure-fire solution" as what was posted afterward seems at least 100% (would have been more if possible) more applicable to my issue.
Anyway, I'll do the right thing here in the end, after having said so many things, and admit, once again, that I was wrong, you were right, I snapped for no good reason and you were just trying to help.
And I sincerely apologize for my rude behaviour. Hopefully now you can at least understand my reaction.
Also, fair is fair - Maybe TWRP flashes the update before it even enters into it. It would be the first I've EVER heard of something like that. But I am out of my element a bit here, so I will withdraw that comment and once again apologize for snapping at you because of it.
Magister54 said:
No, just restore the boot partition (16MB).
I learnt the hard way about backup, when years ago I didn't make one for my Galaxy S2 and lost everything (pictures, etc). Now after installing TWRP I always do a backup...
You should be able to reflash your boot partition with a fastboot command like "fastboot flash boot boot.img" (people with more knowledge than me can help you)
EDIT: the problem is that our Zenfone2 needs a signature for the boot partition, this is why we have a special Magisk installer that just add the signature to the image. The automatic update installer of Magisk has no clue about this, me and a few others here made the same mistake as you when Magisk popup "I have an update!" and we clicked "Install"...
All your data and app are still there, do not worry, no need to wipe anything, just reflash a signed boot.
Click to expand...
Click to collapse
NOW THIS IS HELPING!
THANK YOU SO MUCH!
Basically, you are saying that I would, in theory, just have to use fastboot and flash boot.img (extracted from any firmware?) again, which I am very familiar with how to do, and presto - boot partition restored and working (once again, in theory)?
Sounds amazing!:good:
dustylambo said:
NOW THIS IS HELPING!
THANK YOU SO MUCH!
Basically, you are saying that I would, in theory, just have to use fastboot and flash boot.img (extracted from any firmware?) again, which I am very familiar with how to do, and presto - boot partition restored and working (once again, in theory)?
Sounds amazing!:good:
Click to expand...
Click to collapse
Yes, if you have a Z00A for instance with MM version 223, take the Z00A.zip file from https://forum.xda-developers.com/zenfone2/general/bl-unlock-ze551ml-toolkit-t3546293 and use the file stock\z00a\223\boot.img
This is stock unsigned boot.img file for M .223
http://www.mediafire.com/file/rw73099svgbv0kv/boot.img
timbernot said:
boot.img file for M .223
http://www.mediafire.com/file/rw73099svgbv0kv/boot.img
Click to expand...
Click to collapse
Is there any way to check from TWRP or using fastboot, or otherwise find out what version of the rom I have (had)?
I am definitely still on LolliPo... I think I am one or two official updates from the switch to MarshMallow... But how can I be sure?
WW_ZE551ML_2.20.40.139_sal358-amtech.vn
Last year sometime I ran into a similar problem, where I had to flash raw firmware in order to unbrick the phone... This is the firmware that I downloaded and flashed then.
However, within this .raw-file there is no boot.img ...? There are a couple of .img-files, but none named boot.
On a side-note: When I bricked it last year and had to flash this raw firmware, which I did with Asus Flash Tool, if I am not mistaken... However, whichever way I did it, I managed to flash and then boot as usual. The phone then updated all apps, and I was just blessed with this wonderful sight of "my phone" with all the apps, files and data still intact.
And this problem, which resulted in the same boot issue, came from trying to apply an official OTA update, just after rooting and unlocking the bootloader (forgot myself for just a moment there), which to me seems like a way more serious screw-up than what I just managed to do today...?
@dustylambo
You still boot to TWRP ?
Simple questions
check date of back ups , course you won't be able to restore but title will have builds.
What twrp build ?
Then....
Select reboot in twrp then power off in twrp .
Wait 15 seconds...
Power plus vol+ , you can now boot to bootloader.
What IFWI version ?
0094.0177 or .0173 is LP
0094.0183 is M
Flash relevant raw , without ticking wipe data in AFT.
Check my unbrick thread in my signature for AFT and links to raws
Enjoy
timbernot said:
@dustylambo
You still boot to TWRP ?
Simple questions
check date of back ups , course you won't be able to restore but title will have builds.
What twrp build ?
Then....
Select reboot in twrp then power off in twrp .
Wait 15 seconds...
Power plus vol+ , you can now boot to bootloader.
What IFWI version ?
0094.0177 or .0173 is LP
0094.0183 is M
Flash relevant raw , without ticking wipe data in AFT.
Check my unbrick thread in my signature for AFT and links to raws
Enjoy
Click to expand...
Click to collapse
Yes, I still boot into TWRP.
I can't find my old backup for some reason, but after flashing the previously mentioned raw firmware I never up- or downgraded the ROM, so it MUST be that version. It's the only one I've ever downloaded and flashed.
IFWI version is 0094.0183
But so you are saying I could basically just flash [correct version FW].raw via AFT, without wiping data, and all should be good?
I am on your unbrick thread aws.
I will def bookmark it.
But I already have AFT and the same FW... so I could just go-go-go, right? Or is the IFWI version being M an issue?
Also, I downloaded the official Asus FW from their ZF2 website. In that .zip is in fact a "boot.img" - can I flash this via fastboot you think?
Thanks again for all your help!
You are unbelievable!
@dustylambo
0094.0183 is M
So flash a M raw.
You must've upgraded bootloader since flashing the last raw .139 which is LP to get to M bootloader .0183
In bootloader .0183
You flash raw for M, these have just been added by realyoti
drop him a thanks .
Flash without ticking wipe data in AFT
Damnit! I don't like where this is going... But it's late and I'm dumb
I never upgraded to M because I read that there were several apps that would lose support, MUSIC in particular, but there were others as well.
Will an M raw-file flash and still boot with all my old apps?
@dustylambo
It's simple really , what is the twrp build number ?
You never said
0094.0177
Is locked 5 LP bootloader.
.0173 is 5 unlocked bootloader
.0183 is M
What twrp build is yours ?
Ps , I don't think it matters which version raw you flash , only that it may fail and might have to wipe data to succeed which is better than what you have and are struggling with right now
gnite , enjoy
---------- Post added at 11:45 PM ---------- Previous post was at 11:30 PM ----------
Pls , remember the reason you installed twrp initially ?
For backing up
Sounds like you didn't only update Magisk Manager, you update Magisk itself. A non-signed Magisk update will always result in bootloop.
adobrakic said:
Sounds like you didn't only update Magisk Manager, you update Magisk itself. A non-signed Magisk update will always result in bootloop.
Click to expand...
Click to collapse
To be corrected: Not the Magisk, but the repacked boot.img. ?
Sent from my Redmi 3 using XDA Labs
Hi guys, I've faced this error when entering recovery mode. Look at the Error E. Why is that happening? And how to solve it? My phone is Samsung A3 2017 Nougat. Sorry if my post is messed up. I edited + posted from phone. Thanks.
EDIT: The screenshot isn't mine. I saved from other source
hafidhrisvieardhian said:
Hi guys, I've faced this error when entering recovery mode. Look at the Error E. Why is that happening? And how to solve it? My phone is Samsung A3 2017 Nougat. Sorry if my post is messed up. I edited + posted from phone. Thanks.
EDIT: The screenshot isn't mine. I saved from other source
Click to expand...
Click to collapse
Ignore it, it's an erroneous warning.
ashyx said:
Ignore it, it's an erroneous warning.
Click to expand...
Click to collapse
I hope like so. But as I remembered, I've ever failed to install .zip from sd card via recovery. It said something like "Can't access" or "No media detected". IDK for sure since I've already forgotten 'cus it was a looong time ago. Thanks for replying anyway!
hafidhrisvieardhian said:
I hope like so. But as I remembered, I've ever failed to install .zip from sd card via recovery. It said something like "Can't access" or "No media detected". IDK for sure since I've already forgotten 'cus it was a looong time ago. Thanks for replying anyway!
Click to expand...
Click to collapse
You cannot install anything custom with stock recovery.
You need TWRP.
ashyx said:
You cannot install anything custom with stock recovery.
You need TWRP.
Click to expand...
Click to collapse
Well, that makes a sense. Thank you very much for your time and your explanation.
Hi, I have following problem:
I have lineaegeOS on my chiron, device is unblocked.
System doesn't respond - I can put my 4 digits code but nothing happens, I still see begining page with the lock.
I can still have TWRP on the phone, but (I don't know how) partition is coded, even if I put my 4 digits unlocking code (information is: wrong code).
Is there any way to make my phone live? using usb otg can help here?
Please help me and sorry for my language - I don't know this technical words...
If this is wrong place to posat this question, please let me know as well.
You should ask your question in the thread of the ROM you installed.
leszekk said:
Hi, I have following problem:
I have lineaegeOS on my chiron, device is unblocked.
System doesn't respond - I can put my 4 digits code but nothing happens, I still see begining page with the lock.
I can still have TWRP on the phone, but (I don't know how) partition is coded, even if I put my 4 digits unlocking code (information is: wrong code).
Is there any way to make my phone live? using usb otg can help here?
Please help me and sorry for my language - I don't know this technical words...
If this is wrong place to posat this question, please let me know as well.
Click to expand...
Click to collapse
ya, buy another phone...iphone for example, dont die never
straciatella said:
ya, buy another phone...iphone for example, dont die never
Click to expand...
Click to collapse
Any help? please...
leszekk said:
Any help? please...
Click to expand...
Click to collapse
ok man. your phone is encrypted, bicoz that u see ur partition "kfIengEOgfmkeigm3" like that; doesnt matter;
that method will delete all your data from internal storage
1. Boot to Twrp Recovery
2. Do a Factory Reset
3.WIpe everithing
4. Reboot to Recovery Again and copy Rom,gapps,etc
---------- Post added at 03:03 PM ---------- Previous post was at 03:00 PM ----------
fotocreaman said:
You should ask your question in the thread of the ROM you installed.
Click to expand...
Click to collapse
what reason have to ask in thread rom , if that is a generaly question? or u dont know how to help him? :silly:
straciatella said:
ok man. your phone is encrypted, bicoz that u see ur partition "kfIengEOgfmkeigm3" like that; doesnt matter;
that method will delete all your data from internal storage
1. Boot to Twrp Recovery
2. Do a Factory Reset
3.WIpe everithing
4. Reboot to Recovery Again and copy Rom,gapps,etc
---------- Post added at 03:03 PM ---------- Previous post was at 03:00 PM ----------
what reason have to ask in thread rom , if that is a generaly question? or u dont know how to help him? :silly:
Click to expand...
Click to collapse
But the problem is that internal storage is coded...
leszekk said:
But the problem is that internal storage is coded...
Click to expand...
Click to collapse
u tryed what i said? if doestn work, u have alternative to FORMAT DATA . that will delete everithing from ur device.
straciatella said:
u tryed what i said? if doestn work, u have alternative to FORMAT DATA . that will delete everithing from ur device.
Click to expand...
Click to collapse
Including internal storage, I will not have access to the rom
So you should format everything instead of just wipe
And use the newest version of TWRP (for me it changed much)
and then install ROM from OTG pen
Wywern.pl said:
So you should format everything instead of just wipe
And use the newest version of TWRP (for me it changed much)
and then install ROM from OTG pen
Click to expand...
Click to collapse
ya ma frend...if u didnt answer more faster, he can try everithing...so stay here and help him, not giving answer to me :laugh:
he can try also what u said if have an otg. if not, factory reset is solution
install the rom via sideload with twrp
straciatella said:
ya ma frend...if u didnt answer more faster, he can try everithing...so stay here and help him, not giving answer to me :laugh:
he can try also what u said if have an otg. if not, factory reset is solution
Click to expand...
Click to collapse
Currently I'm waiting for OtG, I will let you know of results.
your encryption of your data(internal storage) is corrupted. only way to solve it is factory reset where it will erase data and internal storage. either way your data is long gone.
i have bricked many of my phones cause of encryption. nothing could save it(had all my data got messed up.)
gsser said:
your encryption of your data(internal storage) is corrupted. only way to solve it is factory reset where it will erase data and internal storage. either way your data is long gone.
i have bricked many of my phones cause of encryption. nothing could save it(had all my data got messed up.)
Click to expand...
Click to collapse
I see. Which partitions should I wipe to be sure that coding is gone?
leszekk said:
I see. Which partitions should I wipe to be sure that coding is gone?
Click to expand...
Click to collapse
) man, ...everithing u must delete from your device; idk if installing from sideload or otg are real solution (try them before doing final alternative), but if thats doesnt work u must wipe EVERITHING. My advice for u is to factory reset and wipe everithing if otg and sideload doesnt work... i wanted to help u with an opinion about otg or sideload, but i dont know nothing about thats...search in XDA and see if another persons had this problem... myself i had that, but i deleted everithing unfortunately.... good luck and dont be scarr...that problem have solution
straciatella said:
) man, ...everithing u must delete from your device; .that problem have solution
Click to expand...
Click to collapse
OK. After wiping data, phone started working (with some bugs...) , but still have problem with coding data in TWRP - access code to the phone doesn't work. But as I said - phone works, I'm on nightly lineageos which was put to the phone few days ago. Currently I have problem with refreshing new OS, putting new version, without errors.
leszekk said:
OK. After wiping data, phone started working (with some bugs...) , but still have problem with coding data in TWRP - access code to the phone doesn't work. But as I said - phone works, I'm on nightly lineageos which was put to the phone few days ago. Currently I have problem with refreshing new OS, putting new version, without errors.
Click to expand...
Click to collapse
is impossible to be your data coded if u reset ur phone and wiping everithing. try flashing .img file from orange fox zip and install orange fox (that if u already dont use it). twrp from wight and others have some bulshets included idk what, coz too me also doesnt work...try with orange fox and see...
straciatella said:
is impossible to be your data coded if u reset ur phone and wiping everithing. try flashing .img file from orange fox zip and install orange fox (that if u already dont use it). twrp from wight and others have some bulshets included idk what, coz too me also doesnt work...try with orange fox and see...
Click to expand...
Click to collapse
As I said, storage is coded. I currently don't have USB OTG to try orange fox...
leszekk said:
As I said, storage is coded. I currently don't have USB OTG to try orange fox...
Click to expand...
Click to collapse
only format data and caches. no need to touch vendor boot system etc.
be sure to use "format data" where it will ask you to confirm by typing yes
leszekk said:
As I said, storage is coded. I currently don't have USB OTG to try orange fox...
Click to expand...
Click to collapse
u have an computer? if u, then download zip of orange fox,unrar and flash via fastboot image file...
I'm on the latest Pie Stable 10.3.1 and wanted to know what to do first after unlocking my bootloader, since my unlock timer runs out in 5 hours. I want to go for an AOSP based Rom and I'm unsure if I'm allowed to wipe the internal storage or not, since I read somewhere that I should never wipe the internal storage.
xell75 said:
I'm on the latest Pie Stable 10.3.1 and wanted to know what to do first after unlocking my bootloader, since my unlock timer runs out in 5 hours. I want to go for an AOSP based Rom and I'm unsure if I'm allowed to wipe the internal storage or not, since I read somewhere that I should never wipe the internal storage.
Click to expand...
Click to collapse
When you unlock the bootloader your internal storage will be wiped anyway, so do backup everything before unlocking.
As for doing it on your own later, there is no harm wipping it, if that's what your concern is, and it should keep the encryption, unless you format the /data partition.
Anyway, if I'm mistaken somebody correct me please. Also do try to find tutorial in Guides & News section, just to be sure.
Cirra92 said:
When you unlock the bootloader your internal storage will be wiped anyway, so do backup everything before unlocking.
As for doing it on your own later, there is no harm wipping it, if that's what your concern is, and it should keep the encryption, unless you format the /data partition.
Anyway, if I'm mistaken somebody correct me please. Also do try to find tutorial in Guides & News section, just to be sure.
Click to expand...
Click to collapse
Okay then, thanks for the help.
Wiping internal storage is not harming as per my information. Good luck mate for unlocking your Whyred. Keep updating us. I am on 89h watch now.
Awais Malik said:
Wiping internal storage is not harming as per my information. Good luck mate for unlocking your Whyred. Keep updating us. I am on 89h watch now.
Click to expand...
Click to collapse
I will and good to hear. Just one last question, can I directly boot twrp with fastboot after unlocking and install it or do I have to let boot the stock system after unlocking once?
xell75 said:
I will and good to hear. Just one last question, can I directly boot twrp with fastboot after unlocking and install it or do I have to let boot the stock system after unlocking once?
Click to expand...
Click to collapse
There is a thread over here "unlock bootloader without wiping storage" not the exact name but something like that. I read over there which says if you let your mobile boot after unlocking bootloader, all of your data will be wiped. But if you follow the instructions given in that thread you might save your data. Just search for that thread. I am gonna send u the link if u can't find.
I asked since the Guy who provided an all in one unlock and root Guide, mentioned that internal storage Thing.
Unlocking was successful!
xell75 said:
Unlocking was successful!
Click to expand...
Click to collapse
Congratulations!! Phew!! What's next? Did you let the boot to wipe your data? What rom you are going to install? 10.0 ? I will install PE after the unlocking. Can't have any buggy rom as it's for my daily use device.
Awais Malik said:
Congratulations!! Phew!! What's next? Did you let the boot to wipe your data? What rom you are going to install? 10.0 ? I will install PE after the unlocking. Can't have any buggy rom as it's for my daily use device.
Click to expand...
Click to collapse
I installed the Android 10 Q DP4 Rom, was a bit buggy at first but since I know what's causing the bugs, I just avoid them. Stable enough for daily use for me now and smooth as butter. I just shouldn't turn on Dark Mode, or phone will be non responsive while trying to wake the phone up. I will tell about battery life within the next few days.
xell75 said:
I installed the Android 10 Q DP4 Rom, was a bit buggy at first but since I know what's causing the bugs, I just avoid them. Stable enough for daily use for me now and smooth as butter. I just shouldn't turn on Dark Mode, or phone will be non responsive while trying to wake the phone up. I will tell about battery life within the next few days.
Click to expand...
Click to collapse
Looks super hot ? can't wait to get my hands dirty on this. ??
Awais Malik said:
Looks super hot ? can't wait to get my hands dirty on this. ??
Click to expand...
Click to collapse
Indeed, this is a nice piece of an Android Q Rom. And Magisk is working too btw.
xell75 said:
Indeed, this is a nice piece of an Android Q Rom. And Magisk is working too btw.
Click to expand...
Click to collapse
How did you root and installed magisk? Can you please guide me the procedure? I am on latest PE build.
Awais Malik said:
How did you root and installed magisk? Can you please guide me the procedure? I am on latest PE build.
Click to expand...
Click to collapse
I just downloaded the newest zip from the Magisk thread and after installing the Rom, just install the Magisk zip., Simple as that.
xell75 said:
I just downloaded the newest zip from the Magisk thread and after installing the Rom, just install the Magisk zip., Simple as that.
Click to expand...
Click to collapse
Thank you just installed now. I was supersu user 2 years ago. So just wanted to make sure before installing this. As this is my first time exp to install magisk.
Awais Malik said:
Thank you just installed now. I was supersu user 2 years ago. So just wanted to make sure before installing this. As this is my first time exp to install magisk.
Click to expand...
Click to collapse
Same but I'm glad I managed that. Btw. Can you or anyone tell me if this is a Rom Bug? On Call the Microphone works flawlessly without any problems, but when I wanna do a voice message in Whatsapp for example any mic recording app, it doesn't work at all, thats weird.
xell75 said:
Same but I'm glad I managed that. Btw. Can you or anyone tell me if this is a Rom Bug? On Call the Microphone works flawlessly without any problems, but when I wanna do a voice message in Whatsapp for example any mic recording app, it doesn't work at all, thats weird.
Click to expand...
Click to collapse
Just tried it now on WhatsApp and it worked without any problem. Clear cut recording.
Awais Malik said:
Just tried it now on WhatsApp and it worked without any problem. Clear cut recording.
Click to expand...
Click to collapse
Yeah, but your on another Rom, I'm on the Android 10 one.
Edit: Same now, disabling Google Voice Match fixed ALL of my microphone issues. That's so weird. XD
Damn I feel lucky now that I did not have to even wait a second to unlock my bootloader.