In this tutorial I will inform you on three different soft bricks, and how to fix them.
You must be able to boot into TWRP and/or Odin/Download mode!
1.) Verification Failed.
Method #1
This method will work with people whom can't reset their device, due to an unmountable /data partition, and those whom experience this error, who can reset but have valuable items, applications, videos, or photos that they don't want to lose. Must be able to boot into Odin/Download mode. (Volume Down+Home+Power)
The solution is actually pretty simple. Boot into Odin/Download mode. This has to be done correctly, not from TWRP recovery. When the prompt for "Volume Up = Continue" and "Volume Down = Cancel (Restart)" press volume down. You should no longer see verification failed, but instead be sitting on the T-Mobile logo. This is normal, and could take 30 seconds to 10 minutes, depending on the amount of data.
This method works all because of Knox. Knox is what Samsung uses to void your warranty. Companies are not allowed to void a warranty when rooting, installing roms, or recovery, unless they have direct evidence. Knox will trigger this when it isn't sure. It will try forcing you to bring it to Samsung, and they can directly find out why it was caused. This happens when it thinks that you cancelled.
Method #2
This one will require you to lose all your data, but is mainly intended for those whom cannot reset their device. Download the stock firmware from the links below. Open Odin (Jodin3 will not work! It is not fully functioning, do not try it.) and boot device into Download/Odin mode. On your computer, you should see 'Added' in the logs. If this does not show up download the Samsung USB Drivers. Select AP and then select the stock firmware. Now flash it. This can also be done through TWRP
For bootloop and frozen Android/Carrier logo just do Method 2. You usually will keep all your data.
FOR 'VERIFICATION FAILED' YOU CANNOT RESTORE FROM A BACKUP!
FOR BOOTLOOPS AND FROZEN STARTUP SCREEN, YOU CAN!
Downloads:
Samsung USB Drivers
7.1.1 Stock Firmware
Odin3 v3.12.10
Post any bricks below that you have encountered!
I'm interested in how many variations there are, and how common they are.
One weird error I'm getting all of a sudden is "Custom binary blocked by FRP Lock" when I tried to reboot my phone. Any ideas?
Hovo said:
One weird error I'm getting all of a sudden is "Custom binary blocked by FRP Lock" when I tried to reboot my phone. Any ideas?
Click to expand...
Click to collapse
Please describe this issue in further detail. Has this been happening out of nowhere, or did you just try flashing something via Odin/Download mode or TWRP.
Also, before flashing did you enable OEM unlock
This also happens when something flashed via Odin/Download mode is incompatible.
Are you still able to boot into the default system partition? If not safe mode?
TechNash said:
Please describe this issue in further detail. Has this been happening out of nowhere, or did you just try flashing something via Odin/Download mode or TWRP.
Also, before flashing did you enable OEM unlock
This also happens when something flashed via Odin/Download mode is incompatible.
Are you still able to boot into the default system partition? If not safe mode?
Click to expand...
Click to collapse
I should have updated my post, I'm not sure what happened but I flashed stock through Odin and the problem went away, after that I was able to flash twrp and root/install other roms.
It's still weird that the problem happened out of nowhere, not sure what triggered it.
It goes away when u log in to google with the last account that is associated with the phone
Hovo said:
I should have updated my post, I'm not sure what happened but I flashed stock through Odin and the problem went away, after that I was able to flash twrp and root/install other roms.
It's still weird that the problem happened out of nowhere, not sure what triggered it.
Click to expand...
Click to collapse
Probs OTA. It happened to me my first 3 tries. Ended up factory reseting, and installing fresh via Odin, didn't fix it.
I just turned off auto reboot on Odin, and then pulled my battery on my J7. Booted up straight to Recovery from there.
TechNash said:
Probs OTA. It happened to me my first 3 tries. Ended up factory reseting, and installing fresh via Odin, didn't fix it.
I just turned off auto reboot on Odin, and then pulled my battery on my J7. Booted up straight to Recovery from there.
Click to expand...
Click to collapse
It would make sense if it was an OTA update TY
Hi, I tried to root my phone and I got this error, I don't mind restarting the phone, but isn't there a way for me to backup my data (photos mainly) first?
Nightwinter said:
Hi, I tried to root my phone and I got this error, I don't mind restarting the phone, but isn't there a way for me to backup my data (photos mainly) first?
Click to expand...
Click to collapse
Sorry I didnt respond.
Looks like you didnt flash encryption breaker. Keep this on your SD Card as its a great way to recover from these errors, and you will need it when you flash ROMS.
Just boot in recovery, flash ashix no verity no encrypt, then reboot into system. You shouldnt have this error.
TechNash said:
Sorry I didnt respond.
Looks like you didnt flash encryption breaker. Keep this on your SD Card as its a great way to recover from these errors, and you will need it when you flash ROMS.
Just boot in recovery, flash ashix no verity no encrypt, then reboot into system. You shouldnt have this error.
Click to expand...
Click to collapse
Keep what in the SD card? the is no file in your quote.
Nightwinter said:
Keep what in the SD card? the is no file in your quote.
Click to expand...
Click to collapse
He's referring to the encryption breaker file ("no-verity-no-encrypt_ashyx.zip") in his first sentence. That is assuming you already had it and should be keeping it on your SD card all the time for flashing ROMs
graevon said:
He's referring to the encryption breaker file ("no-verity-no-encrypt_ashyx.zip") in his first sentence. That is assuming you already had it and should be keeping it on your SD card all the time for flashing ROMs
Click to expand...
Click to collapse
Thanks for explaining that to him.
TechNash said:
Thanks for explaining that to him.
Click to expand...
Click to collapse
how to remove Verification Failed or root in the TWRP file manager without losing data
Mujeeb64 said:
how to remove Verification Failed or root in the TWRP file manager without losing data
Click to expand...
Click to collapse
Flash ashyx-no-verity-no-encrypt.zip in twrp.
Reboot
TechNash said:
In this tutorial I will inform you on three different soft bricks, and how to fix them.
You must be able to boot into TWRP and/or Odin/Download mode!
1.) Verification Failed.
Method #1
This method will work with people whom can't reset their device, due to an unmountable /data partition, and those whom experience this error, who can reset but have valuable items, applications, videos, or photos that they don't want to lose. Must be able to boot into Odin/Download mode. (Volume Down+Home+Power)
The solution is actually pretty simple. Boot into Odin/Download mode. This has to be done correctly, not from TWRP recovery. When the prompt for "Volume Up = Continue" and "Volume Down = Cancel (Restart)" press volume down. You should no longer see verification failed, but instead be sitting on the T-Mobile logo. This is normal, and could take 30 seconds to 10 minutes, depending on the amount of data.
This method works all because of Knox. Knox is what Samsung uses to void your warranty. Companies are not allowed to void a warranty when rooting, installing roms, or recovery, unless they have direct evidence. Knox will trigger this when it isn't sure. It will try forcing you to bring it to Samsung, and they can directly find out why it was caused. This happens when it thinks that you cancelled.
Method #2
This one will require you to lose all your data, but is mainly intended for those whom cannot reset their device. Download the stock firmware from the links below. Open Odin (Jodin3 will not work! It is not fully functioning, do not try it.) and boot device into Download/Odin mode. On your computer, you should see 'Added' in the logs. If this does not show up download the Samsung USB Drivers. Select AP and then select the stock firmware. Now flash it. This can also be done through TWRP
For bootloop and frozen Android/Carrier logo just do Method 2. You usually will keep all your data.
FOR 'VERIFICATION FAILED' YOU CANNOT RESTORE FROM A BACKUP!
FOR BOOTLOOPS AND FROZEN STARTUP SCREEN, YOU CAN!
Downloads:
Samsung USB Drivers
7.1.1 Stock Firmware
Odin3 v3.12.10
Click to expand...
Click to collapse
I have a samsung j700t ud that had the 7.1.1 update installed from tmobile or samsung and it caused the to remain in a continual reboot loop until the battery of the phone dies. Will the methods above repair the issue?
Stuff I've tried:
1. Wipe cache
2. Called samsung and tmobile
3. Used samfirm to download firmware to use with odin that was successfully done but the reboot loop still remains.
smirk24 said:
I have a samsung j700t ud that had the 7.1.1 update installed from tmobile or samsung and it caused the to remain in a continual reboot loop until the battery of the phone dies. Will the methods above repair the issue?
Stuff I've tried:
1. Wipe cache
2. Called samsung and tmobile
3. Used samfirm to download firmware to use with odin that was successfully done but the reboot loop still remains.
Click to expand...
Click to collapse
Was the update sent out to you, or did you download it from SamMobile?
If the update was sent out to you I'm afraid I cannot help, but if you flashed it from SamMobile use an older version like Marshmallow or Lolipop.
EDIT: Make sure you factory reset device and wipe cache after installing from SamMobile.
TechNash said:
Was the update sent out to you, or did you download it from SamMobile?
If the update was sent out to you I'm afraid I cannot help, but if you flashed it from SamMobile use an older version like Marshmallow or Lolipop.
EDIT: Make sure you factory reset device and wipe cache after installing from SamMobile.
Click to expand...
Click to collapse
Id love to but i dont know how to get the marshmallow software and install it to the phone but id like to learn how.
How to recover from Verification Failed without losing data ?Does installing TWRP via Oddin Works and does it able me to transfer my data after installing TWRP ? I dare not try doing it as i have never did it b4
Related
Hello, when I TWRP it asks for a password to decrypt data and if I don't input the password it won't let me access the emulated sdcard. I've never put any password though =/
Is there any way to restore twrp without flashing the stock image/wiping data?
Please search next time...
The password is as follows: (type or exactly as written below)
default_password
Pilz said:
Please search next time...
The password is as follows: (type or exactly as written below)
default_password
Click to expand...
Click to collapse
I typed it as you wrote it with the underscore and no uppercase letters but it gives me Password Failed, Please Try Again
I actually made a quick search before posting and I tried this password before.. Another solution is to wipe data/factory reset but if possible I'd like just to re-install TWRP or remove the password somehow
you missed a step initially. after unlocking the bootloader, you MUST reboot first before flashing TWRP.
to fix this, you'll need to hit cancel at the password screen, then go into wipe and do a factory reset. next, go back into wipe and press the format data button. you have to type yes to continue.
this isnt a fun process, as you have to re-setup your device again, but you've just learned something.
xBeerdroiDx said:
you missed a step initially. after unlocking the bootloader, you MUST reboot first before flashing TWRP.
to fix this, you'll need to hit cancel at the password screen, then go into wipe and do a factory reset. next, go back into wipe and press the format data button. you have to type yes to continue.
this isnt a fun process, as you have to re-setup your device again, but you've just learned something.
Click to expand...
Click to collapse
I assumed he already did this, but in which case we have all been here at one point. I learned the hard way twice now...
kal eh said:
Hello, when I TWRP it asks for a password to decrypt data and if I don't input the password it won't let me access the emulated sdcard. I've never put any password though =/
Is there any way to restore twrp without flashing the stock image/wiping data?
Click to expand...
Click to collapse
No need to fear, Theskillfultroll is here! :good:
To fix your issue, download NEXUS ROOT TOOLKIT by WugFresh, after doing so, you need to open it up and choose your correct device (DO NOT MAKE A MISTAKE HERE OR ELSE YOU CAN BE HARD BRICKED) if you have already unlocked the OEM, then good for you, but what i wanna focus here is on the main window, right hand side* there is a button labeled 'FLASH STOCK + UNROOT' depending on your situation , if you are soft bricked select so, if not click device on. if soft bricked it will tell you what to do, and vice versa on other option, AFTERWARDS, attempt to stock flash and unroot, now if it fails godforbid, you have to go to options and ENABLE FORCE FLASH *WARNING IF YOU DID NOT CHOOSE CORRECT DEVICE AND YOU PICK THIS, YOU WILL BE HARD BRICKED* and go through with that. and bam done. i got in a soft loop when i accidentally flashed a boot.img over a rom which made my phone unusable . i had to go through with the soft bricked option AND force flash, it was scary but dont worry man! any more questions ? feel free to PM me
TheSkillfulTroll said:
No need to fear, Theskillfultroll is here! :good:
To fix your issue, download NEXUS ROOT TOOLKIT by WugFresh, after doing so, you need to open it up and choose your correct device (DO NOT MAKE A MISTAKE HERE OR ELSE YOU CAN BE HARD BRICKED) if you have already unlocked the OEM, then good for you, but what i wanna focus here is on the main window, right hand side* there is a button labeled 'FLASH STOCK + UNROOT' depending on your situation , if you are soft bricked select so, if not click device on. if soft bricked it will tell you what to do, and vice versa on other option, AFTERWARDS, attempt to stock flash and unroot, now if it fails godforbid, you have to go to options and ENABLE FORCE FLASH *WARNING IF YOU DID NOT CHOOSE CORRECT DEVICE AND YOU PICK THIS, YOU WILL BE HARD BRICKED* and go through with that. and bam done. i got in a soft loop when i accidentally flashed a boot.img over a rom which made my phone unusable . i had to go through with the soft bricked option AND force flash, it was scary but dont worry man! any more questions ? feel free to PM me
Click to expand...
Click to collapse
wow. seems like a whole lot of work and worry, especially when compared to simply performing 2 wipes in recovery to solve this problem. no extra software required.
OP, stay away from toolkits.
xBeerdroiDx said:
wow. seems like a whole lot of work and worry, especially when compared to simply performing 2 wipes in recovery to solve this problem. no extra software required.
OP, stay away from toolkits.
Click to expand...
Click to collapse
Op said he doesn't want to wipe data and he doesn't have access to recovery (I think) saw your post about manual flashing though, pretty good
Sent from my Nexus 6 using XDA Free mobile app
ok, so i have this same problem. i have tried the "default_password" thing and the steps in post #4. after performing steps in post #4 everything worked great. but for some reason weeks later the problem has returned. is it possible i'm tripping or could the problem have returned? i know it seems highly unlikely but...
i have also been advised to redo the entire root process, is that a viable option as well?
sinceg1 said:
ok, so i have this same problem. i have tried the "default_password" thing and the steps in post #4. after performing steps in post #4 everything worked great. but for some reason weeks later the problem has returned. is it possible i'm tripping or could the problem have returned? i know it seems highly unlikely but...
i have also been advised to redo the entire root process, is that a viable option as well?
Click to expand...
Click to collapse
could be a twrp bug? are you on the latest version? you can try just updating the recovery, via fastboot or app(like flashify). if that doesnt work you can try wiping out the recovery partition(via fastboot) then reflashing the recovery.
yes i am on the current version via rashr app. i'm not sure how to wipe the recovery partition in fastboot....but it seems time i learn.
again, any thoughts to repeating the root process?
sinceg1 said:
yes i am on the current version via rashr app. i'm not sure how to wipe the recovery partition in fastboot....but it seems time i learn.
again, any thoughts to repeating the root process?
Click to expand...
Click to collapse
why? all that is is flashing supersu or removing it? that had nothing to do with your recovery. you dont need root to have a custom recovery.
ok, so it seems the next thing to try is wipe recovery partition then reflash recovery. i'll begin looking into how to do that. thank you again.
Had this problem last night, if you have a pattern password try using this:
1 2 3
4 5 6
7 8 9
I had an upper case L and it translated to 2589 and that's what unlocked it for me. Hope this helps someone
Ok, I was also asked for a password a couple of days ago for the first time ever, even though I had accessed TWRP several times before to flash roms, kernels etc so I don't think the reason was that I had forgotten to reboot after bootloader. In my case, I didn't even think of trying to enter any PWD so I selected "cancel" and from what I saw I thought my SD was wiped so I re-flashed stock from Bootloader and re-set the device, rather painfull (now I keep a nandroid backup). The thing is though, before I decided to flash stock I just tried exiting recovery and restarting the system and it wouldn't boot by any means. Just sat on the Google logo for ages heating up. And all this happened after a normal shutdown of the device, not after some fancy flashing/modding...
mclisme said:
Ok, I was also asked for a password a couple of days ago for the first time ever, even though I had accessed TWRP several times before to flash roms, kernels etc so I don't think the reason was that I had forgotten to reboot after bootloader. In my case, I didn't even think of trying to enter any PWD so I selected "cancel" and from what I saw I thought my SD was wiped so I re-flashed stock from Bootloader and re-set the device, rather painfull (now I keep a nandroid backup). The thing is though, before I decided to flash stock I just tried exiting recovery and restarting the system and it wouldn't boot by any means. Just sat on the Google logo for ages heating up. And all this happened after a normal shutdown of the device, not after some fancy flashing/modding...
Click to expand...
Click to collapse
Are you encrypted?
i was wondering if that made a matter. i didn't want to sound crazy mentioning it....yes, i am encrypted. do we believe that will make a matter?
sinceg1 said:
i was wondering if that made a matter. i didn't want to sound crazy mentioning it....yes, i am encrypted. do we believe that will make a matter?
Click to expand...
Click to collapse
Absolutely. If your storage is encrypted, TWRP cannot access it without you entering a password. If you don't enter the password, your storage would appear to be blank to recovery.
I personally prefer to wipe my entire device and keep a kernel that does not enforce encryption. Encryption (in my opinion) makes life difficult for rooted users.
seems to be the answer here. i have seen "how to's" on decrypting.... i will decrypt the device, will i have to do anything additional from that point? reflash recovery perhaps? sounds like it would be a good step, but i guess we won't know until i decrypt.
sinceg1 said:
seems to be the answer here. i have seen "how to's" on decrypting.... i will decrypt the device, will i have to do anything additional from that point? reflash recovery perhaps? sounds like it would be a good step, but i guess we won't know until i decrypt.
Click to expand...
Click to collapse
I'm new to the N6 so I am not sure about decrypting as a process. I just did a full wipe, flashed a kernel that doesnt force encryption .
ok, I think I know the answer, but checking for any other ideas. For some reason my phone was trying to unlock in my pocket, and of course it failed 10 times, and says it is going to wipe phone. It reboots to recovery, but fails dm verification, I assume because it is rooted. I select reboot and it goes back to welcome, says sd card is removed, and it is going to wipe phone because of failed login, and reboots again. Question is best way to get out of this loop. If I do factorey reset from system recovery, will I lose root? Can I get it again? or do I need to refresh my brain and remember how to odin and install a rooted stock rom? any ideas on what would be easiest?
Just did factory reset, kept root, even kept all my blacked out apps
Just run repair assistant
joe12401 said:
ok, I think I know the answer, but checking for any other ideas. For some reason my phone was trying to unlock in my pocket, and of course it failed 10 times, and says it is going to wipe phone. It reboots to recovery, but fails dm verification, I assume because it is rooted. I select reboot and it goes back to welcome, says sd card is removed, and it is going to wipe phone because of failed login, and reboots again. Question is best way to get out of this loop. If I do factorey reset from system recovery, will I lose root? Can I get it again? or do I need to refresh my brain and remember how to odin and install a rooted stock rom? any ideas on what would be easiest?
Click to expand...
Click to collapse
Just did factory reset from the computer, just run repair assistant, Its a very easy way.
Reggards
Rooted, Bootloader unlocked, TWRP installed, Xposed Running. 5.0 - I did not yet update or press update ever, If I have ever accidentally allowed it to begin downloading I kill the download by deleting the file using SDMaid.
I got home, had problems with other devices, phone was on about 40% at this point. I remember hearing the phone reboot, I noticed it went into TWRP, which was strange, I restarted system > powered up > lockscreen > restart to twrp with no interaction. Phone is now getting low 21%ish. Fix permissions - because used to be the all out fix on my other devices.
Same thing again > straight into twrp.
I notice that some scripts have been ran in the twrp console. Something along the lines of Victara_en_US.zip Some red scripts I assume saying failed to update.
I assume the phone is now too low to power up.
It shows no sign of charging since leaving the last twrp reboot.
Green light in top speaker shows when attempting to power up with usb charger plugged in > nothing else happens.
With charger unplugged from phone I see my modified logo screen and the moto planet spinning before phone turns off completely. This process now repeats.
Anyone have any idea what the hell is wrong with my phone?
EDIT UPDATE:
Managed to get into the fastboot menu:
Battery Low (RED)
Device is UNLOCKED status code 3 (YELLOW)
Software status modified (YELLOW)
As normal aside from Battery...
THE-M1GHTY-BUKO said:
EDIT UPDATE:
Managed to get into the fastboot menu:
Battery Low (RED)
Device is UNLOCKED status code 3 (YELLOW)
Software status modified (YELLOW)
As normal aside from Battery...
Click to expand...
Click to collapse
Get your phone into TWRP and connect it to your charger and let it charge to at least 70% Use Advanced Wipe in TWRP, select Cache and wipe that. Then see if your phone will start normally. Somehow you have downloaded the update file and it is trying to run automatically. Since your phone is modified, the update fails (and nothing is updated or changed.) The update file is in /cache so wiping that should correct the problem. You should go ahead and update to the Stagefright patched version of your ROM so you aren't having to deny the factory update all the time.
mikeoswego said:
Get your phone into TWRP and connect it to your charger and let it charge to at least 70% Use Advanced Wipe in TWRP, select Cache and wipe that. Then see if your phone will start normally. Somehow you have downloaded the update file and it is trying to run automatically. Since your phone is modified, the update fails (and nothing is updated or changed.) The update file is in /cache so wiping that should correct the problem. You should go ahead and update to the Stagefright patched version of your ROM so you aren't having to deny the factory update all the time.
Click to expand...
Click to collapse
Attempting this now....
Phone still boots to a black screen. I don't understand why it would download the update let alone attempt to install it, I religiously deny the update. Also why would it have booted up normally then forced itself into TWRP? :S
What can I next? I dont mind wiping using fastboot as I managed to take all my files off the phone via twrp.
This happened to me a couple times but wiping the cache AND the dalvik cache fixed it. If it still doesn't work, I hope you have a backup because you are going to have to wipe the system and data next. Sometimes these updates like to link themselves to all the phone's partitions, and in that case you should wipe everything and restore your full system and data backup in recovery.
TyNote3Krill said:
This happened to me a couple times but wiping the cache AND the dalvik cache fixed it. If it still doesn't work, I hope you have a backup because you are going to have to wipe the system and data next. Sometimes these updates like to link themselves to all the phone's partitions, and in that case you should wipe everything and restore your full system and data backup in recovery.
Click to expand...
Click to collapse
I wiped both the first time I tried it :-/
I don't have a system backup as a far as I am aware, need to check main pc for something like that. I had a lot of trouble with no signal after changing my phone to x1095 so I could root it etc. Just hope I don't have the same trouble again. Can i reinstall the system through twrp? Or do I need to flash via fastboot?
Whats my best option, system files wise, for fixing this?
THE-M1GHTY-BUKO said:
I wiped both the first time I tried it :-/
I don't have a system backup as a far as I am aware, need to check main pc for something like that. I had a lot of trouble with no signal after changing my phone to x1095 so I could root it etc. Just hope I don't have the same trouble again. Can i reinstall the system through twrp? Or do I need to flash via fastboot?
Whats my best option, system files wise, for fixing this?
Click to expand...
Click to collapse
If you dont have a backup, at this point, I don't see any other options besides formatting your data or flashing the stock firmware. Of course, don't just take my word for it, but in the future just make sure you have a working backup available.
TyNote3Krill said:
If you dont have a backup, at this point, I don't see any other options besides formatting your data or flashing the stock firmware. Of course, don't just take my word for it, but in the future just make sure you have a working backup available.
Click to expand...
Click to collapse
Am I able to flash anything other than the stock 5.0? Last I checked I had converted whatever I had to the x1095. I remember everything being easier on other phones...
Yes, you can, just make sure you have the right file for the job. They are usually about 2 gigs, and they take forever to flash. Note that once you flash the file, your phone will be as if you just bought it from the store, but it always will boot if you have the corresponding build.
THE-M1GHTY-BUKO said:
Attempting this now....
Phone still boots to a black screen. I don't understand why it would download the update let alone attempt to install it, I religiously deny the update. Also why would it have booted up normally then forced itself into TWRP? :S
What can I next? I dont mind wiping using fastboot as I managed to take all my files off the phone via twrp.
Click to expand...
Click to collapse
In TWRP, make a backup now even though it may not be useful depending on what the problem is. Then, use advanced wipe in TWRP and wipe data. If the phone will boot now, something got corrupted in data and you'll just need to set your phone up again. If the problem continues, you'll have to flash your system image. How to do this varies with the model of your phone; some models have TWRP images, others need to use fastboot files. After you flash the new system image, you can either just continue to clean setup the phone, or you can try to restore only data from the backup you made previously.
TyNote3Krill said:
Yes, you can, just make sure you have the right file for the job. They are usually about 2 gigs, and they take forever to flash. Note that once you flash the file, your phone will be as if you just bought it from the store, but it always will boot if you have the corresponding build.
Click to expand...
Click to collapse
Does that include 5.1 roms? I can never seem to find x1095 5.1 roms, or anything for that matter, they are all titled with every other version.
mikeoswego said:
In TWRP, make a backup now even though it may not be useful depending on what the problem is. Then, use advanced wipe in TWRP and wipe data. If the phone will boot now, something got corrupted in data and you'll just need to set your phone up again. If the problem continues, you'll have to flash your system image. How to do this varies with the model of your phone; some models have TWRP images, others need to use fastboot files. After you flash the new system image, you can either just continue to clean setup the phone, or you can try to restore only data from the backup you made previously.
Click to expand...
Click to collapse
I tried wiping data to no avail.
Im trying to download stock 5.0 for now but the download is taking decades for some reason. Do you, or anyone else, recommend any roms which I can easily flash without having to worry about modem files?
THE-M1GHTY-BUKO said:
Does that include 5.1 roms? I can never seem to find x1095 5.1 roms, or anything for that matter, they are all titled with every other version.
Click to expand...
Click to collapse
Hopefully this could provide more information for your situation?
http://forum.xda-developers.com/moto-x-2014/development/rom-xt1095-flashable-stock-rom-t3185945
Thank you for your help, as well as anyone else who helped me. I now have a running phone on 5.1.
How do I gain root from here? My superuser app updated and now tells me I have no binary, despite telling me to flash something only 5 minutes prior.
Sent from my XT1095 using XDA Free mobile app
So you don't have root? I would suggest rooting using towelroot. Go online and search "towelroot" click on the first result, click on the lambda to download the apk, and install it. You can then open the app, and press "make it ra1n" to root your device without any reboot needed.
I had root prior to wiping and installing the 5.1 update that was linked to me. Towelroot gives me the phone not supported message.
Sent from my XT1095 using XDA Free mobile app
Towel root does not work in 5.1.
To root just flash TWRP. Start TWRP. When you exit TWRP it will ask you if you want to root it. Simple.
Sent from my XT1095 using Tapatalk
I'm still in the "phone not responding" phase.. how did you manage to get in the bootloader from there? Tnx!
I found a chainfire autoroot IMG that rooted my phone. Found xposed too. I'm back at a fully working phone now, thank you to all who helped me.
Gotta say, the battery life on 5.1 is a hell of a lot better.
Sent from my XT1095 using XDA Free mobile app
As in you can't get it to fastboot?
I left it to charge for a while, then took about 5 minutes attempting the power button volume button combo to restart and get it into fastboot.
I believe that it's something like:
Power + vol down until the phone screen flashes/green light goes off
Then
Still holding the power and volume down
Hold the vol up too
Then release the power still holding the vol up and down.
That's what worked for me. It's literally the most awkward phone I've had go button combos.
I think vol up from powered off works too.
If you mess up just hold the power and vol down again.
Sent from my XT1095 using XDA Free mobile app
This is my backup phone so I don't care for the data that is on it and just want it working again. It was rooted before and I needed it unrooted in order to download an app that was blocked by root detection. I tried uninstalling the root using Super SU in its settings, when I restarted my phone it just freezes at the AT&T white screen.
I'm still able to go into the boot recovery menu, I tried putting on the I537UCUCOC7 (5.0.1) firmware found here (https://forum.xda-developers.com/showthread.php?t=2629093). I downloaded it, extracted the zip, and renamed the file "update.zip" and put the file on a microSD then in the recovery boot menu I went to install from external and selected the update.zip. It sorta kinda looked like it accepted it but I get a red error message about the sideloader and I'm still stuck at the white screen when it boots.
What else can I do from here?
P.S. I already tried wiping the cache and data/factory restore options and that didnt work.
Is there anything else that can be done?
I restored my phone to 4.4.2. How can I install 5.0.1? When I search for software updates it says theres nothing available even though I know it can go to 5.0.1 cause thats what I had before it bricked.
Please share how did you restore when I only able to boot into recovery and clearing cache and factory reset does not help. Phone just stack on boot loop
RemixDeluxe said:
I restored my phone to 4.4.2. How can I install 5.0.1? When I search for software updates it says theres nothing available even though I know it can go to 5.0.1 cause thats what I had before it bricked.
Click to expand...
Click to collapse
alex4cta said:
Please share how did you restore when I only able to boot into recovery and clearing cache and factory reset does not help. Phone just stack on boot loop
Click to expand...
Click to collapse
https://forum.xda-developers.com/galaxy-s4-active/general/guide-update-to-i537-att-firmware-t2835481
So I tried to mod my phone (with this, if you're interested https://forum.xda-developers.com/gal...creen-t3759567) but I did something stupid. I thought TWRP was working properly but I'd installed Oreo and didn't wipe data. Well I installed the zip anyway. At the end, an error showed up (could not mount /data or something similar) and my phone will now not boot.
If I try to boot the phone, it just vibrates and stays black. Volume Down + Power + Bixby gets the phone out of this state and the charging screen shows again. I can't boot into TWRP at all. I can boot into download mode but Odin keeps failing when I try to reflash the XEF Oreo firmware (screenshot is in the attachment, it says passed but doesn't attempt to flash the files). I managed to flash TWRP which worked but since I can't boot into it it didn't help. Anthing else I can flash with Odin, or can anybody tell me what's going on / if it's unrecoverable? (I've tried a couple of different versions, they all exhibit the same behaviour)
chemeleon said:
So I tried to mod my phone (with this, if you're interested https://forum.xda-developers.com/gal...creen-t3759567) but I did something stupid. I thought TWRP was working properly but I'd installed Oreo and didn't wipe data. Well I installed the zip anyway. At the end, an error showed up (could not mount /data or something similar) and my phone will now not boot.
If I try to boot the phone, it just vibrates and stays black. Volume Down + Power + Bixby gets the phone out of this state and the charging screen shows again. I can't boot into TWRP at all. I can boot into download mode but Odin keeps failing when I try to reflash the XEF Oreo firmware (screenshot is in the attachment, it says passed but doesn't attempt to flash the files). I managed to flash TWRP which worked but since I can't boot into it it didn't help. Anthing else I can flash with Odin, or can anybody tell me what's going on / if it's unrecoverable? (I've tried a couple of different versions, they all exhibit the same behaviour)
Click to expand...
Click to collapse
There is a newer version of odin, are you using that? You will need that to flash Oreo. Can get it in the link below. Odin v3.13.1
https://forum.xda-developers.com/galaxy-note-8/how-to/official-stock-firmware-update-odin-t3677072
Doh! Had it already, was the only one I didn't try. It's flashing now. Many thanks