Related
Ok so I used to have a Samsung Captivate and knew how to root and flash ROMs, was pretty used to it.
I tried to do the same on my HOX, but ran into a bootloop and subsequently I think I've deleted everything on my phone. I used Hasoon2000's All in one kit and unlocked my bootloader, flashed TWRP v 2.3.3.0, but my problem arose after I tried to flash the kernel. It stayed in bootloop so I figured I'd back out and just restore back to the backup I made before flashing the kernel. However, after "successfully" restoring back I was still stuck in bootloop somehow. I know this isn't supposed to happen, it's supposed to restore back to the exact state of your phone at the time.
Anyways, I thought maybe I just needed to wipe things. I looked around and found a source that said to wipe cache, dalvik, factory reset, and system. Wipe those 4, but not external storage or android secure. So I wiped those 4 and I intended to try the backup again but it turns out that cleared everything on my phone. Now when I hit "restore" there is nothing to select. I also used to have a custom rom on the virtual sdcard, but that's gone too.
When in TWRP and I go into "install" the only thing in /sdcard is now TWRP. After looking around, it looks like my only option is to mount the phone to my computer via TWRP and somehow download the standard OS for my One X again. Also in the Mount menu it lists "mount system, mount data, mount cache, mount sd card" I can only check the first 3 options and when I do my computer asks me if I want to format it. I guess I can't mount the sd card because I deleted everything?
If anyone has the time to help me out that would be AMAZING. Right now I don't even care about being able to flash my custom ROM, I just want to get my phone back to functionality. I would love a conversation and would be willing to gmail chat if willing.
Also my phone is the ATT version, 2.20 (or I guess it was before I deleted everything).
Thank you in advance for any help.
I guess the fastest way to get your phone working again is using RUU file, you ll find how to do it here (method 2) or here
It stayed in bootloop so I figured I'd back out and just restore back to the backup I made before flashing the kernel. However, after "successfully" restoring back I was still stuck in bootloop somehow. I know this isn't supposed to happen, it's supposed to restore back to the exact state of your phone at the time.
Click to expand...
Click to collapse
Restoring backup doesnt restore kernel ( boot.img ), you have to flash it manually with fastboot.
Dude. U think htc offers same freedom as Samsung . U are WRONG. If u flash a rom or restore a backup. U also need to flash boot.img separately from pc. Use fastboot flash boot boot.img. i assume you know the basics. Htc don't have s-off , so writing to nand protected system storage is restricted. If u read a little you might have got this. This will solve boot loop prob
Sent from my HTC One X using Tapatalk 2
Fixed
Thanks Yasounet. I managed to flash viper in the end.
Hi,
I have Note 4 DE that I've installed custom recovery (TWRP) and then flashed a SU.zip. Everything went smooth so I started installed my apps.
I also created a backup from TWRP (pre- and after root) and also full partitions backup using EFS Professional as described in this post so I should also have a phone-specific aboot partition backed up.
Today I booted up into recovery to show friend of myne how it looks like, then rebooted the phone and now it is stuck on Verizon red logo screen with slow blinking blue light. My attempt to hook up the cable and fire up EFS Pro ended up with error message saying that I do not have permanent root.
What should I do now? If there is no way to fix this and keep all installed apps, Is there a way to restore the phone to factory (while still keepping unlocked bootloader)?
Thank you in advance.
inseek said:
Hi,
I have Note 4 DE that I've installed custom recovery (TWRP) and then flashed a SU.zip. Everything went smooth so I started installed my apps.
I also created a backup from TWRP (pre- and after root) and also full partitions backup using EFS Professional as described in this post so I should also have a phone-specific aboot partition backed up.
Today I booted up into recovery to show friend of myne how it looks like, then rebooted the phone and now it is stuck on Verizon red logo screen with slow blinking blue light. My attempt to hook up the cable and fire up EFS Pro ended up with error message saying that I do not have permanent root.
What should I do now? If there is no way to fix this and keep all installed apps, Is there a way to restore the phone to factory (while still keepping unlocked bootloader)?
Thank you in advance.
Click to expand...
Click to collapse
Power your phone off. Pull the battery. Put the battery back in and boot into recovery (volume up, home and power). Wipe cache and delvek. While in TWRP recovery select boot system.
jpcalhoun said:
Power your phone off. Pull the battery. Put the battery back in and boot into recovery (volume up, home and power). Wipe cache and delvek. While in TWRP recovery select boot system.
Click to expand...
Click to collapse
Still on VZW red screen after booting up into recovery, selecting "Wipe", then "Advanced Wipe", checkmarking Dalvik Cache & Cache, wiping them out; and then going to "Reboot" -> System. ..
inseek said:
Still on VZW red screen after booting up into recovery, selecting "Wipe", then "Advanced Wipe", checkmarking Dalvik Cache & Cache, wiping them out; and then going to "Reboot" -> System. ..
Click to expand...
Click to collapse
Hmmm, Ok. Don't worry about your bootloader it is alright, not locked. I recommend you restore your backup, either a rooted backup or a stock backup that you made right after you installed TWRP. This time wipe cache, system and delvek. I'm trying to keep you have having to wipe data, but if this doesn't work then you'll need to do a complete wipe and factory reset and then restore your backup. You may loose root, if so then after restoring your backup flash the SuperSU.zip again to regain root.
jpcalhoun said:
Hmmm, Ok. Don't worry about your bootloader it is alright, not locked. I recommend you restore your backup, either a rooted backup or a stock backup that you made right after you installed TWRP. This time wipe cache, system and delvek. I'm trying to keep you have having to wipe data, but if this doesn't work then you'll need to do a complete wipe and factory reset and then restore your backup. You may loose root, if so then after restoring your backup flash the SuperSU.zip again to regain root.
Click to expand...
Click to collapse
OK, once I wipe Delvik, Chache & System, then I have to do restore from a TWRP backup I did after flashing custom recovery, right?
I have these in the list:
Boot
Recovery
System
Data
Cache
EFS
Modem
TWRP gives me a list of partitions above, which ones should I restore? "System" is probably the one since I've wiped it up already, do I need anything else?
Thanks
inseek said:
OK, once I wipe Delvik, Chache & System, then I have to do restore from a TWRP backup I did after flashing custom recovery, right?
I have these in the list:
Boot
Recovery
System
Data
Cache
EFS
Modem
TWRP gives me a list of partitions above, which ones should I restore? "System" is probably the one since I've wiped it up already, do I need anything else?
Thanks
Click to expand...
Click to collapse
Yes, select restore and then select the backup you made. The backup will contain whatever partitions you selected when you made the backup (the partitions you've mentioned above). You won't be given a chance to select the partitions once you enter restore, only the backup file name.
jpcalhoun said:
Yes, select restore and then select the backup you made. The backup will contain whatever partitions you selected when you made the backup (the partitions you've mentioned above). You won't be given a chance to select the partitions once you enter restore, only the backup file name.
Click to expand...
Click to collapse
It actually gives me an option to deselect any of partitions in the list. Which one(s) should I leave selected for restore?
inseek said:
It actually gives me an option to deselect any of partitions in the list. Which one(s) should I leave selected for restore?
Click to expand...
Click to collapse
Ok, well it's been awhile since I restored anything and maybe that is a new option in the latest TWRP. Anyway, do not deselect anything unless you are worried about your apps then in that case deselect data, then restore.
jpcalhoun said:
Ok, well it's been awhile since I restored anything and maybe that is a new option in the latest TWRP. Anyway, do not deselect anything unless you are worried about your apps then in that case deselect data, then restore.
Click to expand...
Click to collapse
OK, I was able to restore backup to pre-root state (without any apps installed) and then from other backup that has some apps installed. So far, so good, thank you for helping me out.
I still have a question: how do I restore to factory? I guess I need a factory image that was replaced by TWRP, and then I will use Odin to flash it? Did flashing TWRP change the KNOX bit? Is there a way to completely restore N4 DE to factory the way it came from Samsung or once custom recovery is flashed and phone rooted, there is no way back (it is showing me "Custom" every time I turn it on)? I am still in doubt if I want to keep the phone as it is very similar to my rooted N3...
inseek said:
OK, I was able to restore backup to pre-root state (without any apps installed) and then from other backup that has some apps installed. So far, so good, thank you for helping me out.
I still have a question: how do I restore to factory? I guess I need a factory image that was replaced by TWRP, and then I will use Odin to flash it? Did flashing TWRP change the KNOX bit? Is there a way to completely restore N4 DE to factory the way it came from Samsung or once custom recovery is flashed and phone rooted, there is no way back (it is showing me "Custom" every time I turn it on)? I am still in doubt if I want to keep the phone as it is very similar to my rooted N3...
Click to expand...
Click to collapse
The first backup you did after you installed TWRP through ODIN is a factory image with the exception of course of the factory recovery that was replaced by TWRP. Knox will always be part of any backup unless you uninstall Knox using something like Titanium Backup. So installing a custom recovery will not replace or uninstall Knox. I caution you not to flash any factory firmware. There is no factory firmware available for the Developer Edition. If you flash a factory firmware for the Note 4 you will lock your bootloader and what you have left is a very expensive Retail version of the Note 4...locked bootloader and all. The advantage of a Developer Edition is the unlocked bootloader...don't screw that up. As far as "Custom", I don't know how to get rid of that...there is a way I just don't remember how to do it.
I just ordered my Verizon Samsung galaxy note 4.. is there a root method available for the retail version ( non developer edition ) if so can someone point me in the direction .. I'm coming from unlocked rooted note 2.. I've been searching XDA and googling the topic today and all I'm finding is just developer edition is root able .. even searched you tube.. thank you
Sent from my SCH-I605 using XDA Free mobile app
athack said:
I just ordered my Verizon Samsung galaxy note 4.. is there a root method available for the retail version ( non developer edition ) if so can someone point me in the direction .. I'm coming from unlocked rooted note 2.. I've been searching XDA and googling the topic today and all I'm finding is just developer edition is root able .. even searched you tube.. thank you
Sent from my SCH-I605 using XDA Free mobile app
Click to expand...
Click to collapse
Currently no root for Retail/Consumer Edition Verizon Note 4.....
Sent from my SM-N910V / VZW Note 4 DE / Factory Bootloader Unlocked / Rooted / StarKissed / TWRP 2.8.1.1 trltevzw
Thank you...
manbat said:
Currently no root for Retail/Consumer Edition Verizon Note 4.....
Sent from my SM-N910V / VZW Note 4 DE / Factory Bootloader Unlocked / Rooted / StarKissed / TWRP 2.8.1.1 trltevzw
Click to expand...
Click to collapse
Sent from my SCH-I605 using XDA Free mobile app
inseek said:
OK, I was able to restore backup to pre-root state (without any apps installed) and then from other backup that has some apps installed. So far, so good, thank you for helping me out.
I still have a question: how do I restore to factory? I guess I need a factory image that was replaced by TWRP, and then I will use Odin to flash it? Did flashing TWRP change the KNOX bit? Is there a way to completely restore N4 DE to factory the way it came from Samsung or once custom recovery is flashed and phone rooted, there is no way back (it is showing me "Custom" every time I turn it on)? I am still in doubt if I want to keep the phone as it is very similar to my rooted N3...
Click to expand...
Click to collapse
inseek, let me correct a comment I made in a previous post "there is no firmware available for the Note 4". That's not entirely true. It is true that there is not a stock firmware .tar that you can ODIN that returns your phone to stock DE just like it came from Samsung. This thread http://forum.xda-developers.com/not...mware-firmware-kernel-modem-recovery-t2942937 does provide a few stock .tar files that can safely be ODIN on the DE. These files do not provide the "safety net" that we would like in terms of a complete flashing of the DE back to stock, it only provides stock .tar files for several "pieces" of a complete stock ROM and bootloader. Read the OP and post 2 and 3 very carefully before you use any of those .tar files. There is no .tar for the DE aboot/bootloader. The only way you can have a backup of aboot/bootloader is to follow the instructions here: http://forum.xda-developers.com/note-4-verizon/general/guide-vzw-note-4-backup-developer-t2962911
jpcalhoun said:
inseek, let me correct a comment I made in a previous post "there is no firmware available for the Note 4". That's not entirely true. It is true that there is not a stock firmware .tar that you can ODIN that returns your phone to stock DE just like it came from Samsung. This thread http://forum.xda-developers.com/not...mware-firmware-kernel-modem-recovery-t2942937 does provide a few stock .tar files that can safely be ODIN on the DE. These files do not provide the "safety net" that we would like in terms of a complete flashing of the DE back to stock, it only provides stock .tar files for several "pieces" of a complete stock ROM and bootloader. Read the OP and post 2 and 3 very carefully before you use any of those .tar files. There is no .tar for the DE aboot/bootloader. The only way you can have a backup of aboot/bootloader is to follow the instructions here: http://forum.xda-developers.com/note-4-verizon/general/guide-vzw-note-4-backup-developer-t2962911
Click to expand...
Click to collapse
Thank you for this update, jpcalhoun.
I've followed these threads when I first flashed TWRP so I do have a backup made via TWRP (which doesn't include aboot) plus the one created via EFS Professional. I was just wondering if there is a dump of all partitions as they are coming from the factory. I am not a specialist but I was thinking that if I have aboot (which from what I read is unique for my phone), original boot partition + the remaining partitions in my backup then I should be able to restore the phone to factory state.
Is there a way to dump all partitions from a brand new N4 DE that just came from a factory? Obviously, for EFS Professional we need custom recovery + BusyBix + root to work. TWRP is capable of backing up most partitions but not aboot/boot. The way it is now, once we flash custom recovery, there is no way back as if there is something wrong with the phone, Samsung will see that "Custom" sign on the screen and from what I've read, will just re-flash a locked bootloader prior to sending the device back to the owner. I wish I knew all this prior to ordering my N4 DE
inseek said:
Thank you for this update, jpcalhoun.
I've followed these threads when I first flashed TWRP so I do have a backup made via TWRP (which doesn't include aboot) plus the one created via EFS Professional. I was just wondering if there is a dump of all partitions as they are coming from the factory. I am not a specialist but I was thinking that if I have aboot (which from what I read is unique for my phone), original boot partition + the remaining partitions in my backup then I should be able to restore the phone to factory state.
Is there a way to dump all partitions from a brand new N4 DE that just came from a factory? Obviously, for EFS Professional we need custom recovery + BusyBix + root to work. TWRP is capable of backing up most partitions but not aboot/boot. The way it is now, once we flash custom recovery, there is no way back as if there is something wrong with the phone, Samsung will see that "Custom" sign on the screen and from what I've read, will just re-flash a locked bootloader prior to sending the device back to the owner. I wish I knew all this prior to ordering my N4 DE
Click to expand...
Click to collapse
I'm not a Linux guru or a ADB guru, but I think you can do that using command line scripts, but I can't swear to it.
Apparently, TWRP v2.8.6.2 compressed images to external SD cards are damaged, and it wiped my Recovery Mode and part of my previous Stock OS LRX22G.T800XXU1BOE2 installation.
I was able to Odin a Canadian copy of T800XXU1BOCC_T800XAC1BOC4_XAC, but it isn't working properly on my SM-T800.
Can somebody please point me to a US LRX22G.T800XXU1BOE2?
Thanks,
¿GJ?
¿GotJazz? said:
Apparently, TWRP v2.8.6.2 compressed images to external SD cards are damaged, and it wiped my Recovery Mode and part of my previous Stock OS LRX22G.T800XXU1BOE2 installation.
I was able to Odin a Canadian copy of T800XXU1BOCC_T800XAC1BOC4_XAC, but it isn't working properly on my SM-T800.
Can somebody please point me to a US LRX22G.T800XXU1BOE2?
Thanks,
¿GJ?
Click to expand...
Click to collapse
Always check sammobile.com
http://www.sammobile.com/firmwares/download/47566/T800XXU1BOE2_T800XAR1BOC5_XAR/
Ramer said:
Always check sammobile.com
http://www.sammobile.com/firmwares/download/47566/T800XXU1BOE2_T800XAR1BOC5_XAR/
Click to expand...
Click to collapse
Thanks, @Ramer - I checked Sammobile earlier this morning, and it wasn't there. They must have posted it later today.
I can't get to it right now, tho, their website may be having issues. I'll try later.
What do you mean the backup was damaged, what failed and which partition?
You can reflash recovery then just restore system. No need to do a full restore.
ashyx said:
What do you mean the backup was damaged, what failed and which partition?
You can reflash recovery then just restore system. No need to do a full restore.
Click to expand...
Click to collapse
Unfortunately. @ashyx - I'm not sure exactly where now. The recovery failure was almost instant (within the first 5 to 10 steps), and I remember that the error occurred right after a progress comment about EXT4. I lost the capability to boot up, and I lost the capability to get into Recovery Mode. My only option was to stay stuck in Download Mode, and hope that my battery didn't die before I was able to get a Odin image re-installed.
It was nerve-wracking.
I wasn't sure if the tablet would be charging while in Download Mode, and there was no way (that I knew of) to get out of Download Mode. I thought there was a high probability that I was about to permanently lose my brand-new tablet.
I paid for a subscription to Sammobile to get an older image installed until someone was able to get me the more recent stock image.
I'm too nervous to try and restore the image again without need, but I will definitely do it if you want me to. I understand the urgency to make sure that TWRP makes good images 100% of the time, and I am reluctant to do anything future to my tablet if I can't make a reliable back-up.
¿GJ?
Maybe your backup somehow got corrupted.
Which partitions were you actually trying to restore? For future reference if you made a backup of recovery don't restore it. Only restore it if you want to revert to a different version.
Also don't worry about bricking your device. As long as you still get download mode you will always be able to recover. I soft brick my tablet on a daily basis lol.
The only thing you need to flash to get into a bootable state is recovery. From recovery you can usually solve most issues. Even if your battery had died you would have been able to charge it and then power it back on. Also the tablet does charge in recovery mode.
Twrp can be a funny so and so sometimes. You just get the one time when it doesn't t behave as you expect. 99% of the time though its pretty solid.
I always find its good practise to restore a backup immediately after making it to ensure its sound. You don't want to wait until its too late to find out its corrupt.
ashyx said:
Maybe your backup somehow got corrupted.
Which partitions were you actually trying to restore? For future reference if you made a backup of recovery don't restore it. Only restore it if you want to revert to a different version.
Also don't worry about bricking your device. As long as you still get download mode you will always be able to recover. I soft brick my tablet on a daily basis lol.
The only thing you need to flash to get into a bootable state is recovery. From recovery you can usually solve most issues. Even if your battery had died you would have been able to charge it and then power it back on. Also the tablet does charge in recovery mode.
Twrp can be a funny so and so sometimes. You just get the one time when it doesn't t behave as you expect. 99% of the time though its pretty solid.
I always find its good practise to restore a backup immediately after making it to ensure its sound. You don't want to wait until its too late to find out its corrupt.
Click to expand...
Click to collapse
Thanks, @ashyx - Good advice on the partition recovery steps. Normally, I have automatically accepted the three defaults, and swiped. I will not do that anymore.
I have found TWRP to be very reliable in the past: If it's working fine, I always get a good backup. If it's failing on something, I always get a bad backup image, or always can't restore. I haven't had a random corruption yet. There was a problem I saw with TWRP and my Samsung GS3 a few years back where it would corrupt compressed archives, but uncompressed archives were fine. Maybe this is a replay on that problem.
I will backup my current CM12.1 image uncompressed, and then try just restoring my system & data partitions from the previous backup, and let you know what happens.
¿GotJazz? said:
Thanks, @ashyx - Good advice on the partition recovery steps. Normally, I have automatically accepted the three defaults, and swiped. I will not do that anymore.
I have found TWRP to be very reliable in the past: If it's working fine, I always get a good backup. If it's failing on something, I always get a bad backup image, or always can't restore. I haven't had a random corruption yet. There was a problem I saw with TWRP and my Samsung GS3 a few years back where it would corrupt compressed archives, but uncompressed archives were fine. Maybe this is a replay on that problem.
I will backup my current CM12.1 image uncompressed, and then try just restoring my system & data partitions from the previous backup, and let you know what happens.
Click to expand...
Click to collapse
I can assure you compressed backups should work fine. I have done it countless times. Probably just a one off for whatever reason, could be a failing sd card. You may find the backup is fine and will be ok to restore. I wouldn't be afraid to try again. When a backup fails to restore you usually only get an error message not a sudden crash and reboot.
Try making a compressed test backup by just backing up the cache partition then restore.
ashyx said:
I can assure you compressed backups should work fine. I have done it countless times. Probably just a one off for whatever reason, could be a failing sd card. You may find the backup is fine and will be ok to restore. I wouldn't be afraid to try again. When a backup fails to restore you usually only get an error message not a sudden crash and reboot.
Try making a compressed test backup by just backing up the cache partition then restore.
Click to expand...
Click to collapse
Well, as a point of reference, I just tried to restore system & data from my older (apparently corrupted) image.
I saw:
...
Wiping System...
Formatting System using make_ext4s function.
Restoring System...
E:extractTarFork() process ended with ERROR=255
I will follow your suggestion, and try writing a compressed Cache backup to see what happens.
¿GotJazz? said:
Well, as a point of reference, I just tried to restore system & data from my older (apparently corrupted) image.
I saw:
...
Wiping System...
Formatting System using make_ext4s function.
Restoring System...
E:extractTarFork() process ended with ERROR=255
I will follow your suggestion, and try writing a compressed Cache backup to see what happens.
Click to expand...
Click to collapse
Is this backup also encrypted. I have seen that error with encrypted backups in the official twrp. However this was fixed with an update pushed to the twrp repo which I have incorporated into the latest build.
Does your version of Twrp show your model number at the top?
ashyx said:
Is this backup also encrypted?
Click to expand...
Click to collapse
Yes.
ashyx said:
Does your version of Twrp show your model number at the top?
Click to expand...
Click to collapse
No, it just shows Team Win Recovery Project v2.8.6.2. It doesn't show any Samsung model numbers (If that is what you are asking).
I installed it using your All-In-One Root/Recovery tool.
Ok I think you're actually running an earlier build. I have updated builds below.
Install one of the f2s versions from the link below.
http://forum.xda-developers.com/gal...p-2-8-6-1-unofficial-sm-t800-805-807-t3074633
ashyx said:
Ok I think you're actually running an earlier build. I have updated builds below.
Install one of the f2s versions from the link below.
http://forum.xda-developers.com/gal...p-2-8-6-1-unofficial-sm-t800-805-807-t3074633
Click to expand...
Click to collapse
Thanks, @ashyx! I'll download the SM-T800 F2FS version right now.
BTW, I've been really interested in installing F2FS. One thing I have been worried about, though, is that once I go down the F2FS path, it may be easy to really mess things up. For example, if I update a ROM, I would always need to use a F2FS ROM, or I might lose all my data - is that right?
Normally you would only format the data and cache partition to f2fs. There isn't much point formatting system to f2fs.
Also f2fs requires a special kernel. Myself and Tkkg1994(Iron Rom) have been working together to get this working properly. Still testing.
We are almost there.
Once formatted to f2fs you would need to reformat back to ext4 and flash a kernel to return back to normal. You could then flash your backup.
Hi! My first post here (and not a pleasant one).
I bricked my phone by trying to sideload the android 7 september ota update.
I had root and TWRP recovery installed and I thought it would be ok to sideload the update from TWRP thinking that will erase system and recovery. But what I faced was adb sideload to stop to about 30% on pc and the options to go back or reboot system on TWRP.
So being afraid of a brick I didn't reboot and I flashed a nandroid backup (didn't have a vendor backup). After it finished I rebooted system to find out that the phone goes up to 4 dots and reboots.
The next thing I did was to flash a factory image. I flashed both the september and august images by running flash-all.sh with success (no errors) but still the device is in bootloop.
The last thing I tried was this: http://forum.xda-developers.com/nexus-5x/help/fix-nougat-bricked-phones-n6-thread-t3449640
but made things worse and then I could reach up to Google logo. So I flashed back the factory image of Android N August and I can reach again the 4 dots.
The odd thing is that when I flash TWRP I see a supersu folder in /. Do you think it affects anything? But system, boot, cache, sdcard, recovery, vendor are formatted during flashing the factory images.
I have the 32gb model and unlocked bootloader.
This drives me crazy since it's a soft brick and I should be able to recover from this.
Any help will be much appreciated!
Thanks in advance!
adbPush said:
Hi! My first post here (and not a pleasant one).
I bricked my phone by trying to sideload the android 7 september ota update.
I had root and TWRP recovery installed and I thought it would be ok to sideload the update from TWRP thinking that will erase system and recovery. But what I faced was adb sideload to stop to about 30% on pc and the options to go back or reboot system on TWRP.
So being afraid of a brick I didn't reboot and I flashed a nandroid backup (didn't have a vendor backup). After it finished I rebooted system to find out that the phone goes up to 4 dots and reboots.
The next thing I did was to flash a factory image. I flashed both the september and august images by running flash-all.sh with success (no errors) but still the device is in bootloop.
The last thing I tried was this: http://forum.xda-developers.com/nexus-5x/help/fix-nougat-bricked-phones-n6-thread-t3449640
but made things worse and then I could reach up to Google logo. So I flashed back the factory image of Android N August and I can reach again the 4 dots.
The odd thing is that when I flash TWRP I see a supersu folder in /. Do you think it affects anything? But system, boot, cache, sdcard, recovery, vendor are formatted during flashing the factory images.
I have the 32gb model and unlocked bootloader.
This drives me crazy since it's a soft brick and I should be able to recover from this.
Any help will be much appreciated!
Thanks in advance!
Click to expand...
Click to collapse
Just press the volume down and power button at the same time. Should get you into TWRP and then transfer the file you want to install the ROM on and flash it. That should do it. Hopefully this helps.
rpalmon said:
Just press the volume down and power button at the same time. Should get you into TWRP and then transfer the file you want to install the ROM on and flash it. That should do it. Hopefully this helps.
Click to expand...
Click to collapse
I did flash the factory image from fastboot successfully without errors but it doesn't boot. Do you mean a custom rom? Im afraid that may do things worse.
adbPush said:
Hi! My first post here (and not a pleasant one).
I bricked my phone by trying to sideload the android 7 september ota update.
I had root and TWRP recovery installed and I thought it would be ok to sideload the update from TWRP thinking that will erase system and recovery. But what I faced was adb sideload to stop to about 30% on pc and the options to go back or reboot system on TWRP.
So being afraid of a brick I didn't reboot and I flashed a nandroid backup (didn't have a vendor backup). After it finished I rebooted system to find out that the phone goes up to 4 dots and reboots.
The next thing I did was to flash a factory image. I flashed both the september and august images by running flash-all.sh with success (no errors) but still the device is in bootloop.
The last thing I tried was this: http://forum.xda-developers.com/nexus-5x/help/fix-nougat-bricked-phones-n6-thread-t3449640
but made things worse and then I could reach up to Google logo. So I flashed back the factory image of Android N August and I can reach again the 4 dots.
The odd thing is that when I flash TWRP I see a supersu folder in /. Do you think it affects anything? But system, boot, cache, sdcard, recovery, vendor are formatted during flashing the factory images.
I have the 32gb model and unlocked bootloader.
This drives me crazy since it's a soft brick and I should be able to recover from this.
Any help will be much appreciated!
Thanks in advance!
Click to expand...
Click to collapse
If you have your userdata backed up, I suggest you flash everything including letting it factory reset your userdata.
Keep in mind your nandroid backups are on userdata, so move those off the phone first.
One other thing, when you restored nandroid backup, did you use TWRP 3.0.2-1 and did you restore EFS partition? There was a bug in TWRP where it would crash your phone because it overwrote an EFS partition with the contents of another EFS partition due to incorrect filenames.
sfhub said:
If you have your userdata backed up, I suggest you flash everything including letting it factory reset your userdata.
Keep in mind your nandroid backups are on userdata, so move those off the phone first.
One other thing, when you restored nandroid backup, did you use TWRP 3.0.2-1 and did you restore EFS partition? There was a bug in TWRP where it would crash your phone because it overwrote an EFS partition with the contents of another EFS partition due to incorrect filenames.
Click to expand...
Click to collapse
Yes i used TWRP 3.0.2-1 to restore EFS. Was the bug to that version? Is there any way to fix it?
EDIT: I downloaded and installed twrp 3.0.2-2 and when I try to restore the efs it says "efs2 no such file or directory". The previous version of twrp doesn't semm to have backed up this partition. I only find efs1 in the backup folder. @sfhub can you plz help me? How am I going to find the second partition of efs. Can you plz provide me a backup?
adbPush said:
Yes i used TWRP 3.0.2-1 to restore EFS. Was the bug to that version? Is there any way to fix it?
EDIT: I downloaded and installed twrp 3.0.2-2 and when I try to restore the efs it says "efs2 no such file or directory". The previous version of twrp doesn't semm to have backed up this partition. I only find efs1 in the backup folder. @sfhub can you plz help me? How am I going to find the second partition of efs. Can you plz provide me a backup?
Click to expand...
Click to collapse
There is some info about this over on the TWRP thread.
Essentially if you write all zeros into the efs partitions, the phone will recreate the data (if you instead of non-zero data, it will think things are corrupted)
I suggest you read very carefully erverything you can about recovering from the TWRP EFS bug. This post will get you started, but I suggest you read the original thread from the 6p forum that is referenced in this post. I haven't done this myself nor have I read that carefully so don't want to give you bad advice and make your situation worse.
http://forum.xda-developers.com/nex...h-recovery-t3230471/post68595543#post68595543
sfhub said:
There is some info about this over on the TWRP thread.
Essentially if you write all zeros into the efs partitions, the phone will recreate the data (if you instead of non-zero data, it will think things are corrupted)
I suggest you read very carefully erverything you can about recovering from the TWRP EFS bug. This post will get you started, but I suggest you read the original thread from the 6p forum that is referenced in this post. I haven't done this myself nor have I read that carefully so don't want to give you bad advice and make your situation worse.
http://forum.xda-developers.com/nex...h-recovery-t3230471/post68595543#post68595543
Click to expand...
Click to collapse
Thank you very much! I'll read it first thing tomorrow and I'll let you know what happened.
@sfhub thank you so much!!!! That was it! The dd commands fixed my problem. I didn't know that the EFS partitions could be reconstructed by the system. I thought I was done. Thank you for indicating the TWRP bug. I was not aware of it. I couldn't understand what could have possibly went wrong since everything was flashed successfuly from the factory images.
adbPush said:
@sfhub thank you so much!!!! That was it! The dd commands fixed my problem. I didn't know that the EFS partitions could be reconstructed by the system. I thought I was done. Thank you for indicating the TWRP bug. I was not aware of it. I couldn't understand what could have possibly went wrong since everything was flashed successfuly from the factory images.
Click to expand...
Click to collapse
Glad to hear you got things fixed.
I think i have done the same to my EFS Partition
adbPush said:
@sfhub thank you so much!!!! That was it! The dd commands fixed my problem. I didn't know that the EFS partitions could be reconstructed by the system. I thought I was done. Thank you for indicating the TWRP bug. I was not aware of it. I couldn't understand what could have possibly went wrong since everything was flashed successfuly from the factory images.
Click to expand...
Click to collapse
Can you please share the exact command you used for nexus 5x as the link above is for nexus 6p.
saadabbasi said:
Can you please share the exact command you used for nexus 5x as the link above is for nexus 6p.
Click to expand...
Click to collapse
They are the exact same commands as for 6P:
ADB shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst1 bs=16384
and
ADB shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst2 bs=16384
My Question is About Twrp, if i make a Back-up of my system completery, and install a ROM and not liked her or bricked my device (Mi a2 Lite) i can take back again, right? without install a ROM stock? Thansk for Answering ? i make one time but Using a Clockwordmod on samsung Old i bricked the device and i Restore a Backup and Back
Sorry about My english bad
Yes, but use unofficial TWRP from ROM section not the official one.
Backup boot, system image, vendor image and data.
Works for custom ROMs, not sure about stock ROM.
Also backup EFS and persist once in case you lost IMEI or sensors.
Pat750 said:
Yes, but use unofficial TWRP from ROM section not the official one.
Backup boot, system image, vendor image and data.
Works for custom ROMs, not sure about stock ROM.
Also backup EFS and persist once in case you lost IMEI or sensors.
Click to expand...
Click to collapse
I unlocked my bootloader yesterday and my user data and files have not been deleted
but my other question is If i install twrp i lose?
[email protected] said:
I unlocked my bootloader yesterday and my user data and files have not been deleted
but my other question is If i install twrp i lose?
Click to expand...
Click to collapse
I'm surprised that unlocking didn't delete your data, for me it did and it usually does.
For TWRP use fastboot boot <filename>.img to boot it and then flash the zip.
Normally that doesn't delete data, but always backup important data first.
I'm not sure how good TWRP handles encrypted data...I'm always unencrypted.
Before TWRP backup people say to remove pins and maybe fingerprints first (there are zip files for that) because then restoring will work better.
Good luck, happy flashing and first search and read if you are unsure.
Pat750 said:
I'm surprised that unlocking didn't delete your data, for me it did and it usually does.
For TWRP use fastboot boot <filename>.img to boot it and then flash the zip.
Normally that doesn't delete data, but always backup important data first.
I'm not sure how good TWRP handles encrypted data...I'm always unencrypted.
Before TWRP backup people say to remove pins and maybe fingerprints first (there are zip files for that) because then restoring will work better.
Good luck, happy flashing and first search and read if you are unsure.
Click to expand...
Click to collapse
before i Unlock the BL i pressed the button "Down" of sound and not deleted My Data :3