Hi all,
Yesterday I tried to flash a mod in twrp, which failed. I changed the files back in twrp but when rebooting van got the message 'your device is corrupted' instead of 'your bootloader is unlocked'.
What can I do now?
superiscch said:
Hi all,
Yesterday I tried to flash a mod in twrp, which failed. I changed the files back in twrp but when rebooting van got the message 'your device is corrupted' instead of 'your bootloader is unlocked'.
What can I do now?
Click to expand...
Click to collapse
Try this: https://forum.xda-developers.com/oneplus-6t/how-to/tool-6t-msmdownloadtool-v4-0-oos-9-0-5-t3867448
drei??? said:
Try this: https://forum.xda-developers.com/oneplus-6t/how-to/tool-6t-msmdownloadtool-v4-0-oos-9-0-5-t3867448
Click to expand...
Click to collapse
I'll check it out. But the phone still works fine, I'm just wondering why I get the message.
superiscch said:
I'll check it out. But the phone still works fine, I'm just wondering why I get the message.
Click to expand...
Click to collapse
oh ok.. never mind then. (It's the last resort method )
superiscch said:
I'll check it out. But the phone still works fine, I'm just wondering why I get the message.
Click to expand...
Click to collapse
From what I've read, most people here are using this msm tool to get rid of that message, not too sure if there's a simpler way. Have you tried a local upgrade?
H4X0R46 said:
From what I've read, most people here are using this msm tool to get rid of that message, not too sure if there's a simpler way. Have you tried a local upgrade?
Click to expand...
Click to collapse
I'm on latest oxygenOs... I will try when new release is de out.
I don't feel like using the toom because it all gets wipet again.
All works fine, even rooted again... All fine
I think I got that message also but the phone booted the OS fine. My solution to get my phone working was to select reboot to bootloader from the power menu on the OS (couldn't seem to boot into fastboot through a button combination when powering up), then boot TWRP through fastboot. I reflashed the TWRP recovery using the installer. In my case I did it through OTG with a USB pendrive. It may work from internal storage also, though I am not sure. I think it had something to do with the recovery getting corrupted. This is no guarantee that it will work for you, but this is what worked for me.
Hope that helps.
Ooms
superiscch said:
I'm on latest oxygenOs... I will try when new release is de out.
I don't feel like using the toom because it all gets wipet again.
All works fine, even rooted again... All fine
Click to expand...
Click to collapse
Well alright, OnePlus seems to be making updates quickly! Also, you could just reflash the same version you're already running. I did that on my device with no issue, it'll just flash your inactive slot with the same build you're already running. Pretty sure this phone has 2 bootloaders too (one for each slot).
From TWRP, go to terminal and run:
Code:
reboot "dm-verity enforcing"
Try this
Striatum_bdr said:
From TWRP, go to terminal and run:
Code:
reboot "dm-verity enforcing"
Try this
Click to expand...
Click to collapse
What does this do? Will it wipe anything?
superiscch said:
What does this do? Will it wipe anything?
Click to expand...
Click to collapse
It will change dm-verify flag to enforcing and you will get rid of the red warning at boot. It doesn't wipe anything
Striatum_bdr said:
It will change dm-verify flag to enforcing and you will get rid of the red warning at boot. It doesn't wipe anything
Click to expand...
Click to collapse
But the red warning at the beginning is nothing else that a message? Like the unlocked bootloader message? My OS is as good as stock?
Striatum_bdr said:
From TWRP, go to terminal and run:
Code:
reboot "dm-verity enforcing"
Try this
Click to expand...
Click to collapse
Thank you so much
I also used the command reboot "dm-verity enforcing". The message at startup is gone now, but I think Google Pay is not working anymore because of that. My device passes the safety net check in Magisk. Could it be, that Google Pay notices that something is wrong with the dm-verity? Is the dm-verity set to enforcing the default status? Or is this just overriding the underlying error?
Related
Hey, I have the recovery mode that I installed from here currently on my phone, but I would like to revert it to the stock recovery mode, because I'll be needing to take my phone to Verizon tomorrow. How can I go about doing that?
Chiggins said:
Hey, I have the recovery mode that I installed from here currently on my phone, but I would like to revert it to the stock recovery mode, because I'll be needing to take my phone to Verizon tomorrow. How can I go about doing that?
Click to expand...
Click to collapse
just flash theOTA (leak v3) it sets the recoveryand everything else back to stock
I downloaded the OTA for 2.1 and tried to install that, but when I did from the recovery mode I have, I got an error saying E:No signature (690 files)
Chiggins said:
I downloaded the OTA for 2.1 and tried to install that, but when I did from the recovery mode I have, I got an error saying E:No signature (690 files)
Click to expand...
Click to collapse
make sure the file is in the root of your sdcard
and instead of pressing up volume press down when powering your phone on
it will take you to the bootloader (h-boot)
use trackball as action button to finish installation =)
Yep, I've done that. Gone through h-boot into the recovery mode, and whenever I tried to install the OTA file that I renamed to update.zip, I get the E:No signature (690 files) error
Chiggins said:
Yep, I've done that. Gone through h-boot into the recovery mode, and whenever I tried to install the OTA file that I renamed to update.zip, I get the E:No signature (690 files) error
Click to expand...
Click to collapse
you have to name it as PB00IMG.zip
otherwise it will look right past it in h-boot
and give you the option to go into the recovery
I got the same error after renaming the file.
Chiggins said:
I got the same error after renaming the file.
Click to expand...
Click to collapse
your pressing volume down + power correct
not power up. power up not your friend in this case we want the bootloader not the recovery.
Well ****, now its doing something in HBOOT. There is a loading bar on the top right doing something.
Chiggins said:
Well ****, now its doing something in HBOOT. There is a loading bar on the top right doing something.
Click to expand...
Click to collapse
awesome now your cookin!
enjoy the OTA again haha
glad we could get you moving along.
and remember the action button is the trackball =)
Well, now when I booted back up, I was back in KaosFroyo.
And the recovery mode was the same.
Chiggins said:
Well, now when I booted back up, I was back in KaosFroyo.
And the recovery mode was the same.
Click to expand...
Click to collapse
did it say installation complete?
you let it run its course not pulling the battery correct? it took my phone about 5-7 minutes to complete
if so mabey the file was the wronge one.
http://www.mediafire.com/?qymwuzug5gl
I didn't see any text saying installation complete, and I didn't touch the battery. This file is a lot bigger than the one that I had. I'll download and give it a try.
Should I do a wipe to factory before I do this?
Chiggins said:
I didn't see any text saying installation complete, and I didn't touch the battery. This file is a lot bigger than the one that I had. I'll download and give it a try.
Should I do a wipe to factory before I do this?
Click to expand...
Click to collapse
no it will wipe everything but your sdcard
All of this will reset my phone to factory settings, right? So when I bring it to Verizon, I'll be under warranty?
Chiggins said:
All of this will reset my phone to factory settings, right? So when I bring it to Verizon, I'll be under warranty?
Click to expand...
Click to collapse
factory yes warranty ehhh thats arguable but with the firmware and rom stock they won't be able to tell at all so your fine to even seal the deal further after you reboot your phone it will promt you to install the new ota update just follow the on screen instructions for that and it will be fully updated and vzw approved
Is there anything else that I should do to ensure that they don't find that I've rooted?
Chiggins said:
Is there anything else that I should do to ensure that they don't find that I've rooted?
Click to expand...
Click to collapse
mabey clear your sdcard of nandroid and any other roms or patches just in case and any other root only folders like titanium or setcpu etc. etc.
The only thing I did was use nandroid, I already deleted my roms. Where is the setcpu folder?
Okay so I have the sprint LG G2 and was being an idiot messing around with the hidden menu and I selected an option fota update test or something and my device rebooted. Now it only reboots into recovery mode. I have TWRP 2.6.3.2. It tells me that it cannot find my backup. The Log file says E:storage partition //twrp/backups not found. I dont know what to do. Ive tried flashing roms, but it just reboots back into recovery every time even when I tell it to reboot bootloader. Any Ideas?
It's fixed! I used the Lg flash tool with the sprint .tot file and she is alive! Thanks all of you I appreciate it.
typow102 said:
Okay so I have the sprint LG G2 and was being an idiot messing around with the hidden menu and I selected an option fota update test or something and my device rebooted. Now it only reboots into recovery mode. I have TWRP 2.6.3.2. It tells me that it cannot find my backup. The Log file says E:storage partition //twrp/backups not found. I dont know what to do. Ive tried flashing roms, but it just reboots back into recovery every time even when I tell it to reboot bootloader. Any Ideas?
Click to expand...
Click to collapse
*sigh*...why do ppl that dont know what the heck they are doing still tinker with the settings? Just don't access the hidden menu and flip switches thinking it will have zero effect.
Sent from my LG G2 LS980 using Tapatalk
ericdabbs said:
*sigh*...why do ppl that dont know what the heck they are doing still tinker with the settings? Just don't access the hidden menu and flip switches thinking it will have zero effect.
Sent from my LG G2 LS980 using Tapatalk
Click to expand...
Click to collapse
Okay i'm asking for help thats all. I know what I did was stupid. I'm trying to sideload the stock rom but it keeps getting stuck at 84%. The problem I think, is the boot partition is all messed up.
typow102 said:
Okay so I have the sprint LG G2 and was being an idiot messing around with the hidden menu and I selected an option fota update test or something and my device rebooted. Now it only reboots into recovery mode. I have TWRP 2.6.3.2. It tells me that it cannot find my backup. The Log file says E:storage partition //twrp/backups not found. I dont know what to do. Ive tried flashing roms, but it just reboots back into recovery every time even when I tell it to reboot bootloader. Any Ideas?
Click to expand...
Click to collapse
This is what you need to do.Dont worry nothing is messed up,the phone will be back after this one
http://forum.xda-developers.com/showthread.php?t=2451696
I did the second option since i find it easier to do.
you can simply use TWRP's awesome "terminal command" option to run the following:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
Click to expand...
Click to collapse
Just be sure you dont type it wrong tho.
woof123 said:
This is what you need to do.Dont worry nothing is messed up,the phone will be back after this one
http://forum.xda-developers.com/showthread.php?t=2451696
I did the second option since i find it easier to do.
Just be sure you dont type it wrong tho.
Click to expand...
Click to collapse
Hey thanks for responding. I tried doing that just now and it still keeps rebooting in recovery. I did the first option though. I cant find where to enter commands on TWRP. It just tells me to pick a folder.
Can anybody help? I'm pretty desperate here. I just dont know why twrp deleted my backup. I had one on there that I used all the time and now it says it cant find it. It just keeps rebooting into recovery mode.
typow102 said:
Hey thanks for responding. I tried doing that just now and it still keeps rebooting in recovery. I did the first option though. I cant find where to enter commands on TWRP. It just tells me to pick a folder.
Click to expand...
Click to collapse
If im not mistaken you dont need to choose any folder,only to push select and then type it up there...
woof123 said:
If im not mistaken you dont need to choose any folder,only to push select and then type it up there...
Click to expand...
Click to collapse
I just tried that same result . Every time I reboot it goes back into recovery its stuck in a recovery bootloop.
If you typed it properly and it doesnt work,then i dont know...I have done what you did before to try it out,since i knew how to fix it.And it worked just fine.
http://forum.xda-developers.com/showthread.php?t=2432476
This fixed it for me ... Was also stuck in bootloop.
Use another memory card..
Send u r backup files in another memory card and go to twrp and restore backup..
I think this works for u..
Sent from my GT-S5830i using Tapatalk 2
amolgosavi said:
Use another memory card..
Send u r backup files in another memory card and go to twrp and restore backup..
Click to expand...
Click to collapse
Hi,
What are you saying
amolgosavi said:
I think this works for u..
Click to expand...
Click to collapse
I don't think...
teneke said:
http://forum.xda-developers.com/showthread.php?t=2432476
This fixed it for me ... Was also stuck in bootloop.
Click to expand...
Click to collapse
are you on sprint? Thats what im on. I tried that method,but got stuck on this part: 4) Now unplug your phone, power off and then go back into download mode again, volUp+USB. It should immediately connect and start flashing.
When I would go to unplug it and reboot into download mode it just wouldn't do anything the app would just say ready.
I somehow got my nandroid back but when Its done flashing it just reboots back into recovery. I dont know whats going on.
Man this is so frustrating. Ive tried all these things and it still only boots recovery even after flashing my nandroid I made awhile back. Im stuck and dont know what to do. Any help would be greatly appreciated
Are you sure that you did the 2nd method properly?Try once more and double check what you type.Why this worked for me when i did the same but it doesnt work for you..Nothing much you can do atm either that,or download a kdz rom and try to upgrade with flashtool.
Thanks for trying to help me out. I got it fixed by using the lg flash tool. I feel like such an idiot. Ive been coming around these forums for awhile I just never registered. I consider myself pretty good with tech but im self taught so their is alot of trial and error and noob mistakes. +1
typow102 said:
Thanks for trying to help me out. I got it fixed by using the lg flash tool. I feel like such an idiot. Ive been coming around these forums for awhile I just never registered. I consider myself pretty good with tech but im self taught so their is alot of trial and error and noob mistakes. +1
Click to expand...
Click to collapse
Glad that it worked,i have soft bricked mine many times till now,on my 1st time i was panicked tho.But after that,i always find a way to put it back lol
teneke said:
http://forum.xda-developers.com/showthread.php?t=2432476
This fixed it for me ... Was also stuck in bootloop.
Click to expand...
Click to collapse
Unfortunately my phone is going directly in to CWM Recovery after showing LG Logo after reboot. I am able to access the Recovery option -> Install Zip. but I am not able to transfer even any custom rom to the phone.
Is there any option of transfer the zip files to the phone right now in my case.
Rgds,
if you are out there @me2151 I could really use your help...
I have gone through all the steps multiple times and when I get to the part to get rid of the static on boot up, specifically when you get here:
*****ALL USERS*****
If you encounter a "Secure Boot" Password then booting the first time you did not Format data properly.
To reiterate: To properly decrypt the device you need to boot into TWRP and go to WIPE->FORMAT DATA and you will be prompted to type "yes" to format and decrypt.
**************
Once you are booted and have proceeded through the setup wizard, re-enable Android Debugging (ADB) if not already enabled.
Type:
Code:
adb reboot bootloader
6) Once inside bootloader, Type:
Code:
fastboot flash boot boot2.img
When it says finished, Type:
Code:
fastboot reboot
The device will boot back into system.
Click to expand...
Click to collapse
Once I reboot from this point I get the repeated phone app crash bug. I even tried the steps beyond this and reflashed SuperSU.zip, did the wipe, and reboot. Still get the phone app crash bug.
What am I missing?
Thanks in advance!
actschp1 said:
if you are out there @me2151 I could really use your help...
I have gone through all the steps multiple times and when I get to the part to get rid of the static on boot up, specifically when you get here:
Once I reboot from this point I get the repeated phone app crash bug. I even tried the steps beyond this and reflashed SuperSU.zip, did the wipe, and reboot. Still get the phone app crash bug.
What am I missing?
Thanks in advance!
Click to expand...
Click to collapse
I am going to assume you are on sprint. In which case you did not properly read the guide. You do not flash boot2 after installing the sprint rom. It specifically says for sprint users to stop right after you install the rom and supersu... Custom kernels will cause the phone crash.
actschp1 said:
if you are out there @me2151 I could really use your help...
I have gone through all the steps multiple times and when I get to the part to get rid of the static on boot up, specifically when you get here:
Once I reboot from this point I get the repeated phone app crash bug. I even tried the steps beyond this and reflashed SuperSU.zip, did the wipe, and reboot. Still get the phone app crash bug.
What am I missing?
Thanks in advance!
Click to expand...
Click to collapse
me2151 said:
I am going to assume you are on sprint. In which case you did not properly read the guide. You do not flash boot2 after installing the sprint rom. It specifically says for sprint users to stop right after you install the rom and supersu... Custom kernels will cause the phone crash.
Click to expand...
Click to collapse
Ok, stopped there. But on your guide it says there will be static on reboots if I stop at that point. I was thinking that I was suppose too follow the remaining steps to get rid of the static boot. Since that is not the case, I take it there is no way to eliminate the static on boot up?
actschp1 said:
Ok, stopped there. But on your guide it says there will be static on reboots if I stop at that point. I was thinking that I was suppose too follow the remaining steps to get rid of the static boot. Since that is not the case, I take it there is no way to eliminate the static on boot up?
Click to expand...
Click to collapse
Not as of now. Just continue to use the proximity sensor fix until further notice.
Mind Absent// said:
Not as of now. Just continue to use the proximity sensor fix until further notice.
Click to expand...
Click to collapse
Ok, thanks for the info @Mind Absent//
@me2151, and all those who worked on this, are freakin rockstars to get us to this point. Static is nothing since it's such an easy fix.
actschp1 said:
Ok, thanks for the info @Mind Absent// @me2151, and all those who worked on this, are freakin rockstars to get us to this point. Static is nothing since it's such an easy fix.
Click to expand...
Click to collapse
Lol, I'm just the messenger. Thank @me2151 and his team for all their hard work and perseverance in something that seemed so impossible only 2 months ago.
I can't find this anywhere. Every guide seems to assume that everyone has a micro SD in their phone. Currently, I don't have one. I'm wondering if an S7 Edge root is possible without an SD card.
diraga said:
I can't find this anywhere. Every guide seems to assume that everyone has a micro SD in their phone. Currently, I don't have one. I'm wondering if an S7 Edge root is possible without an SD card.
Click to expand...
Click to collapse
try this
mashardpro said:
try this
Click to expand...
Click to collapse
I have tried the CF-Auto-Root method twice now, both resulting in being stuck on boot like the other times. However, maybe I needed to wait longer? Next time I attempt a root I will leave the phone alone for at least 15 minutes before I call it a failure. Still, the post you linked seems to be for older firmware. Would you still recommend the method for Nougat? Thanks for the reply.
diraga said:
I have tried the CF-Auto-Root method twice now, both resulting in being stuck on boot like the other times. However, maybe I needed to wait longer? Next time I attempt a root I will leave the phone alone for at least 15 minutes before I call it a failure. Still, the post you linked seems to be for older firmware. Would you still recommend the method for Nougat? Thanks for the reply.
Click to expand...
Click to collapse
then you can try twrp , and use adb sideload if you don't have sdcard
mashardpro said:
then you can try twrp , and use adb sideload if you don't have sdcard
Click to expand...
Click to collapse
I think I've isolated the problem. After using adb sideloader to install magisk and antiroot remover, I'm prompted to reboot. In other guides, there is a further options screen after pressing the reboot button which has a couple checked boxes and a button that says "Do Not Install". I see this screen for maybe a third of a second after selecting Reboot before the device reboots on its own. Just tried this and now I'm stuck on the Samsung boot logo once again.
Note: There are many errors in the adb sideloader log relating to being unable to mount/unmount /data/ and stuff like that that I know are related to having an SD inserted.
Edit: I should also note that I am new to android. Fresh newbee from iOS, but I have been jailbreaking for the past 9 years. Still in over my head I think.
diraga said:
I think I've isolated the problem. After using adb sideloader to install magisk and antiroot remover, I'm prompted to reboot. In other guides, there is a further options screen after pressing the reboot button which has a couple checked boxes and a button that says "Do Not Install". I see this screen for maybe a third of a second after selecting Reboot before the device reboots on its own. Just tried this and now I'm stuck on the Samsung boot logo once again.
Note: There are many errors in the adb sideloader log relating to being unable to mount/unmount /data/ and stuff like that that I know are related to having an SD inserted.
Edit: I should also note that I am new to android. Fresh newbee from iOS, but I have been jailbreaking for the past 9 years. Still in over my head I think.
Click to expand...
Click to collapse
hmmmm, I am a bit confused as well. I am successful with that way. Or read this for other options. But I do not know work or not, because the last link I had never tried
mashardpro said:
hmmmm, I am a bit confused as well. I am successful with that way. Or read this for other options. But I do not know work or not, because the last link I had never tried
Click to expand...
Click to collapse
Still confused... I really don't want to reset my phone for the fourth time today. Please help!
diraga said:
Still confused... I really don't want to reset my phone for the fourth time today. Please help!
Click to expand...
Click to collapse
Well, it seems like all I know already I mentioned, better use of existing first now while waiting for someone who can help you. btw, the root will be used for what?
diraga said:
Still confused... I really don't want to reset my phone for the fourth time today. Please help!
Click to expand...
Click to collapse
Once data is wiped in twrp then reboot back to recovery and connect usb to pc. You should be able to copy SuperSU zip via mtp and your phone should show up on pc. Flash SuperSU zip once copied
mashardpro said:
Well, it seems like all I know already I mentioned, better use of existing first now while waiting for someone who can help you. btw, the root will be used for what?
Click to expand...
Click to collapse
Deleting stock apps, installing adblock, exploring non-Google Play apps, possibly installing custom ROM. I enjoy seeing what my phone can do.
ASHLEY117 said:
Once data is wiped in twrp then reboot back to recovery and connect usb to pc. You should be able to copy SuperSU zip via mtp and your phone should show up on pc. Flash SuperSU zip once copied
Click to expand...
Click to collapse
The phone is recognized on the PC but there are no folders. Any files I try to drag over come up with an error. Furthermore, I could use the stock firmware USB to store the necessary files on it, but I can't seem to navigate to the same storage destination via the TWRP file browser.
diraga said:
The phone is recognized on the PC but there are no folders. Any files I try to drag over come up with an error. Furthermore, I could use the stock firmware USB to store the necessary files on it, but I can't seem to navigate to the same storage destination via the TWRP file browser.
Click to expand...
Click to collapse
You could copy SuperSU zip to a usb flash drive and use the otg adapter that came with the s7? Twrp support otg usb install.
diraga said:
The phone is recognized on the PC but there are no folders. Any files I try to drag over come up with an error. Furthermore, I could use the stock firmware USB to store the necessary files on it, but I can't seem to navigate to the same storage destination via the TWRP file browser.
Click to expand...
Click to collapse
so you have twrp now?
ASHLEY117 said:
You could copy SuperSU zip to a usb flash drive and use the otg adapter that came with the s7? Twrp support otg usb install.
Click to expand...
Click to collapse
That's... a really good idea. Going to try right now!
mashardpro said:
so you have twrp now?
Click to expand...
Click to collapse
I've had no trouble installing TWRP whatsoever. I've done it five times today!
diraga said:
That's... a really good idea. Going to try right now!
I've had no trouble installing TWRP whatsoever. I've done it five times today!
Click to expand...
Click to collapse
seems nice, good luck. maybe lacking some finishing touches you need to do. I remember well my first too so, and the key is I have to format the data in twrp
ASHLEY117 said:
You could copy SuperSU zip to a usb flash drive and use the otg adapter that came with the s7? Twrp support otg usb install.
Click to expand...
Click to collapse
mashardpro said:
seems nice, good luck. maybe lacking some finishing touches you need to do. I remember well my first too so, and the key is I have to format the data in twrp
Click to expand...
Click to collapse
Update: Still stuck on Samsung boot logo after 15+ minutes after successfully loading from usb drive. TWRP still skipped right by the reboot options screen after the install... I have no clue why it's doing that. It's like it's taking the command to reboot after I press the button and processing it while it is going to the next screen. I don't know. Hopefully someone does. It's so close!
EDIT: IT WORKED!!! Had to format and then installing from usb drive worked great! Thank you so much!!
diraga said:
Update: Still stuck on Samsung boot logo after 15+ minutes after successfully loading from usb drive. TWRP still skipped right by the reboot options screen after the install... I have no clue why it's doing that. It's like it's taking the command to reboot after I press the button and processing it while it is going to the next screen. I don't know. Hopefully someone does. It's so close!
EDIT: IT WORKED!!! Had to format and then installing from usb drive worked great! Thank you so much!!
Click to expand...
Click to collapse
I am glad to hear it. Like I said, just need the final touch that you might forget
mashardpro said:
I am glad to hear it. Like I said, just need the final touch that you might forget
Click to expand...
Click to collapse
False alarm! Root checker says my phone is not rooted... I'm lost... At least my phone booted?
diraga said:
False alarm! Root checker says my phone is not rooted... I'm lost... At least my phone booted?
Click to expand...
Click to collapse
so if you have twrp and your phone is booted, then take a look this. quite easy to understand
mashardpro said:
so if you have twrp and your phone is booted, then take a look this. quite easy to understand
Click to expand...
Click to collapse
Currently following this tutorial and awaiting boot past the Samsung logo. Hoping it works. I see no reason why it shouldn't.
Edit: Running a rooted Android. Thanks
!!! I apologize if this is the wrong thread to ask for help and kindly request that a moderator move it, because I don't know where it's supposed to go and my brain is in panic mode right now, thank you. !!!
So, here goes:
DEVICE INFO: SM-J510FN, TWRP, stock ROM, encrypted data partition
ISSUE: Phone does not boot. Powering it on makes it boot to recovery. Selecting "Reboot to system" from inside the recovery, also boots back to recovery. Cannot mount data partition as it is encrypted (but it doesn't at least ask for PIN or anything, just cannot select /data in mount).
HOW IT HAPPENED:
1. I encrypted the phone while it still wasn't rooted.
2. I flashed TWRP (via Odin) and SuperSU (via TWRP)
3. Phone booted to system normally, everything OK. Root access, all good.
4. Reboot to TWRP, flashed some blacked out Google Apps (Team Blackout .zip files). I got no error message, just "cannot mount data" at some points.
5. I selected "wipe cache and dalvik cache"
6. Reboot to system
Reboot to system doesn't work. It boots back into TWRP!
Now I don't know if the flashing of the .zip apps or if the wiping bricked the phone as I don't have that deep of an understanding of how it works. If you can enlighten me , I'd really appreciate it.
FEAR: That the phone is bricked forever and that I won't be able to format the data partition as I cannot even mount it and TWRP needs it mounted in order to wipe it (as far as I know). In short, phone ruined forever because of my stupidity.
HOPE: That someone will tell me a way to re-flash the stock firmware or any ROM so that I get the phone to boot up normally.
I really really need help ASAP because this phone does not even belong to me. My employer gave it to me as a gift, provided I use it for work. That's the reason it's encrypted, he wanted it encrypted in case it gets stolen. Now you're probably thinking "why would you root a company phone??" Well it's not a company phone, it is my main phone, my daily driver. It was given to me by my employer, who said I can do whatever I want with it, as long as it remains functional (at work I use it simply for phone calls, WhatsApp, Skype, mail etc)
I assume that I won't sleep much tonight, will try everything to get the phone to boot. But first I'm going to wait for any piece of advice!
Thank you in advance for any feedback...
Can you get into download mode?
If so, you should flash your stock firmware.
Yes if you boot into download mode you can flash stock rom and all will be good
capsLock1337 said:
Can you get into download mode?
If so, you should flash your stock firmware.
Click to expand...
Click to collapse
pando504 said:
Yes if you boot into download mode you can flash stock rom and all will be good
Click to expand...
Click to collapse
Hello, thanks for the replies.
Yes, download mode works. I will download the stock firmware and flash it via Odin then, yes?
But what happens with the encryption then? Will it remain in place and I will just have to enter my pin to boot as usual?
Can you please explain to me why it does not boot now..? As far as I understand, the boot partition couldn't have been damaged. Aka, stock ROM still in place, only difference is it's rooted.
bi11ie said:
Hello, thanks for the replies.
Yes, download mode works. I will download the stock firmware and flash it via Odin then, yes?
But what happens with the encryption then? Will it remain in place and I will just have to enter my pin to boot as usual?
Can you please explain to me why it does not boot now..? As far as I understand, the boot partition couldn't have been damaged. Aka, stock ROM still in place, only difference is it's rooted.
Click to expand...
Click to collapse
Not sure bout the encryption, if you lose it, you can set it up again.
Something went wrong when you tried to flash the blacked out google apps, I honestly don't have a clue.
Good luck
capsLock1337 said:
Not sure bout the encryption, if you lose it, you can set it up again.
Something went wrong when you tried to flash the blacked out google apps, I honestly don't have a clue.
Good luck
Click to expand...
Click to collapse
Haha I really don't care about the encryption at all! I'm just afraid it is going to interfere somehow but hopefully not.
I'm waiting for the stock firmware to get downloaded from sammobile. I know, I know, I should have done that first before anything else, but I was in such a hurry and I thought "OK, this is routine by now, nothing can go wrong", somehow completely forgetting about the encryption. Oops. In any case, I will post the results here later and will be VERY VERY prepared and organized in the future :'(
bi11ie said:
Haha I really don't care about the encryption at all! I'm just afraid it is going to interfere somehow but hopefully not.
I'm waiting for the stock firmware to get downloaded from sammobile. I know, I know, I should have done that first before anything else, but I was in such a hurry and I thought "OK, this is routine by now, nothing can go wrong", somehow completely forgetting about the encryption. Oops. In any case, I will post the results here later and will be VERY VERY prepared and organized in the future :'(
Click to expand...
Click to collapse
How did it go?
capsLock1337 said:
How did it go?
Click to expand...
Click to collapse
I'm flashing right now Let's see if it boots...
*fingers crossed*
Case solved
bi11ie said:
I'm flashing right now Let's see if it boots...
*fingers crossed*
Click to expand...
Click to collapse
Ahh turns out I almost freaked out for nothing! All good! So, for documentation purposes:
1. I flashed stock firmware through Odin
2. Boot up started normally ("firmware update") - got asked for encryption pin!
3. Decryption took a long time, system booted normally - ALL DATA INTACT
4. No root and No recovery (not even stock recovery)
5. I flashed TWRP through Odin and SuperSU.zip
6. Phone booted normally, TWRP there, SuperSU app there.
The only change is that the bloatware I removed is back
I'm so glad it was nothing after all! I was honestly SO scared that I bricked it ^^;
Thanks and sorry!
bi11ie said:
Ahh turns out I almost freaked out for nothing! All good! So, for documentation purposes:
1. I flashed stock firmware through Odin
2. Boot up started normally ("firmware update") - got asked for encryption pin!
3. Decryption took a long time, system booted normally - ALL DATA INTACT
4. No root and No recovery (not even stock recovery)
5. I flashed TWRP through Odin and SuperSU.zip
6. Phone booted normally, TWRP there, SuperSU app there.
The only change is that the bloatware I removed is back
I'm so glad it was nothing after all! I was honestly SO scared that I bricked it ^^;
Thanks and sorry!
Click to expand...
Click to collapse
No need to apoligize, we all do stupid mistakes sometimes
Glad that it worked!