So I flashed a file that was supposedly going to "fix" my rooted G930T. It just bricked it... Luckily however, I made a FlashFire backup and have the files on my SD card. I odined back to stock PD8 (the firmware I was on) and rooted again, installed Flashfire, and tried to restore my files. I didn't know which files to select, so I just selected all and when I booted up, I got a message that said encryption failed... Can anybody help me with how to restore through FlashFire and what options to select after I select the backup file?
Thanks.
Sam
Related
I followed these steps
http://forum.xda-developers.com/showthread.php?t=2046439
I downloaded the SuperSU_bootable_FIX.zip file, unzipped it, and took the three folders that where in there and copied them into my SD card on my phone.
I ran ODIN3.
and PDA the following file VRALEC Bootchain to allow custom recovery [this went fine]
after restarting my system and going into ODIN mode again, I used BOOTLOADER with the following recover: ClockworkMod Touch Recovery 6.0.2.3
After it finished, I unplugged my phone, turned it off,, and took out my battery, restarted my phone into recovery mode.
Once there I clicked on Reboot system and when it asked me if I wanted to disable Disable recovery flash, i clicked YES
the system restarted. and when the phone started, it shows the Samsung logo with a "unlocked" icon at the bottom of it.
Here is where the issues there:
When I try to run SuperSU, I still get "there is no su binary installed and supersu cannot install it" -- Is it possible I did not place the files in the right place? Does it matter where on the SD card I put the files? Or is the issue something else?
I inserted my new Tmobile SIM card, and I still "Non-Verizon SIM" error -- I think this is related to the fact that my phone is not rooted yet? Or did the unlock fail as well? Is there something I need to do to allow for the Tmobile SIM card, or is it because I failed somewhere along the way, following those instructions?
I would really appreciate any help.
Why did you unzip the SuperSU_Bootloader_FIXED zip? That is not in the directions, anywhere. You simply just flash the zip in recovery.
Edit: I'm guessing you're new to rooting. While in custom recoveries (TWRP or CWM), you flash .zip files. While in Odin (for Samsung devices only), you flash .tar or .tar.md5 files.
SlimSnoopOS said:
Why did you unzip the SuperSU_Bootloader_FIXED zip? That is not in the directions, anywhere. You simply just flash the zip in recovery.
Edit: I'm guessing you're new to rooting. While in custom recoveries (TWRP or CWM), you flash .zip files. While in Odin (for Samsung devices only), you flash .tar or .tar.md5 files.
Click to expand...
Click to collapse
THANK YOU SO MUCH! That part was not clear to me at all, I did not understand it, I guess I am as stupid as they come.
Are there .tars inside .zips of the bootunlockwhatever.zip?
Sent from my SPH-D710 using Xparent Skyblue Tapatalk 2
Have a Verizon Samsung Galaxy Note II (SCH-i605). Took the latest OTA update to VRUEMJ9. Have since rooted and installed SafeStrap and was happily running N3BULA ROM, when I decided to explore a bit and tried to flash Alliance ROM. Now I'm stuck on the Samsung boot screen and can go no further. I am able to access Android system recovery, but when I try to 'apply update from external storage' I get 'E:signature verication failed' message. Tried to flash to stock via Odin, but unsuccessful. Shows Added in Odin but nothing happens when I select the .pit file or the .tar file. This is a work issued phone, so any help to get up and running would be greatly appreciated!
Brantosapien said:
Have a Verizon Samsung Galaxy Note II (SCH-i605). Took the latest OTA update to VRUEMJ9. Have since rooted and installed SafeStrap and was happily running N3BULA ROM, when I decided to explore a bit and tried to flash Alliance ROM. Now I'm stuck on the Samsung boot screen and can go no further. I am able to access Android system recovery, but when I try to 'apply update from external storage' I get 'E:signature verication failed' message. Tried to flash to stock via Odin, but unsuccessful. Shows Added in Odin but nothing happens when I select the .pit file or the .tar file. This is a work issued phone, so any help to get up and running would be greatly appreciated!
Click to expand...
Click to collapse
Have you performed a "wipe data" option from the recovery after flashing the alliance ROM (it wipes your user data)?
Because I just visited the alliance ROM thread ( http://forum.xda-developers.com/showthread.php?t=2032447 and in the install instructions its mentioned so.
Better take a little time and properly read the install instructions during flashing..
Sent from my GT-I9070 using Tapatalk
dagger said:
Have you performed a "wipe data" option from the recovery after flashing the alliance ROM (it wipes your user data)?
Because I just visited the alliance ROM thread ( http://forum.xda-developers.com/showthread.php?t=2032447 and in the install instructions its mentioned so.
Better take a little time and properly read the install instructions during flashing..
Sent from my GT-I9070 using Tapatalk
Click to expand...
Click to collapse
I never had that option. I've flashed numerous ROMS before and am pretty meticulous when it comes to following instructions. It appeared to have a custom flash script which allowed me to pick what I did and didn't want to install. I tried to keep it mostly stock and when it completed, it automatically rebooted (didn't give me an option to 'wipe data') and now leaves me stuck on the Samsung Boot Screen. I was able to flash the .pit file via Odin, but keep getting a 'MD5 hash value is invalid' when I try to flash the .tar file.
Brantosapien said:
I never had that option. I've flashed numerous ROMS before and am pretty meticulous when it comes to following instructions. It appeared to have a custom flash script which allowed me to pick what I did and didn't want to install. I tried to keep it mostly stock and when it completed, it automatically rebooted (didn't give me an option to 'wipe data') and now leaves me stuck on the Samsung Boot Screen. I was able to flash the .pit file via Odin, but keep getting a 'MD5 hash value is invalid' when I try to flash the .tar file.
Click to expand...
Click to collapse
You should enter into recovery and then manually wipe data..
Also if that thing doesnt work, then have a look at this thread which explains how to go back to stock rom..
In addition,
A. Why doesnt Odin work?
Did you unextract the tar and pit from the rar/zip so that odin could recognize the files as suggested in dagger's link in section 1b step 2?
Did you install samsung drivers on your computer properly? You may use this toolkit for that
B. Rescue by CWM
Signature verification failed is caused (I think) by stock samsung recovery's choosiness, if you are sure you downloaded the zip correctly. What zip did you exactly try to flash?
So now, you may want to flash a cwm recovery or a kernel that contains cwm inside. Flashing usually uses adb using fastboot. Search "flashing a recovery image" or "flashing a kernel" where your chosen kernel should have cwm inside. cwm usually does not put out that signature verification error.
Remember:
You can access recovery mode through an app or by pressing a button combo when turning your phone on. Device specific.
Stock samsung recovery can wipe data.
CWM can also wipe data, and is the preferred installation method for most/all custom roms. And it can make a nandroid backup.
If ever you do choose to flash, you'll need the toolkit to install adb/fastboot drivers, but maybe since yours in locked bootloader the adb thing might not work.
Hope this helps
I shattered the screen on my Nexus 5, and G was kind enough to send a replacement (refurbished). Since I have TWRP Nandroid backups, I thought it would be an easy matter to unlock/root/TWRP the new replacement phone, copy over the backup files, then restore. However, TWRP does not seem to be working - I get a bootloop, with an android mascot with a red triangle and the words "no command" when I select "Recovery".
My original N5: unlocked, rooted, TWRP, Android 4.4.4
Replacement N5:
- originally with Android 4.4.0
- unlocked, rooted and TWRP installed with Nexus Root Toolkit (NRT)
- system was then upgraded to 4.4.2, 4.4.3, 4.4.4
- went into fastboot, tried to select Recovery....and nothing.
Is this an issue with TWRP? Should I try flashing a different version?
Is this an issue with the process? Should I use NRT to "Return to Stock", THEN let the system update itself to 4.4.4, THEN try unlock/root/TWRP and recovery?
Is this an issue with the root process? Should I use CF Auto Root and try to re-root, re-install SuperSU, etc. on the current system?
TIA
Ed
That's stock recovery. Do yourself a favour and flash recovery properly without using a toolkit.
Thank you - that was absolutely correct. Apparently NRT either didn't install TWRP, or didn't flash an error message saying TWRP install failed (or I missed it).
I downloaded a TWRP flash image, and after some tweaking with drivers, managed to flash it just fine.
I then copied over my original N5 TWRP backup, and restored it. Aside from some minor data location problems (e.g., Evernote detected new SD Card, re-sync'd all notes), it worked fine and the new phone is in the exact same state/configuration as the original phone.
Now to go track down the "TWRP restore to a different device" threads.
Thanks!
The rule really is never restore EFS from another device.
Old device, backup system, boot and data
New device, make a small backup to generate the serial number folder. Then copy the backup from the old device.
I also replaced the /data/media/0/Android folder with the Android folder on my microSD card.
What do I do?
EDIT: FYI, this is the particular NC5 build I was trying to restore:
https://www.youtube.com/watch?v=AIRoQKTLeJQ
I made the backup with SafeStrap, and tried to restore it with TWRP.
Flash the firmware through!
Sent from my Pebble Time
I was trying to revert to Sense today after flashing some of the AOSP roms that were newly released. I downloaded one of the stock Nandroid backups from the RUU thread and tried to restore from it: "System is mounted read-only". Okay, so then I mounted it with write permissions and proceeded to restore. The restore went fine except when it finished I got the error message "could not mount system (Structure needs cleaning)". Now when I try to reboot in twrp, it says I don't have an OS installed. Any idea how to recover from this? I have never encountered this error before :/.
Download the same stock firmware.zip as what was on it before you messed with it. Rename it to whatever it needs to be.. Begins with P.. Not sure what it actually is, and place it on the external sdcard.
Boot to download mode and flash it.
Do not relock your bootloader. Do not s-on.