After tinkering with the tablet and trying my best to restore it I finally was able last night to restore it to a clean install using this method. I'm sure there may be other ways to do it as well but this worked for me and was painless.
1. Make sure the tablet is rooted/unencrypted using Vampirefo's guide:
http://forum.xda-developers.com/android/development/root-nextbook-ares-8-twrp-recovery-t3133165
2. Make a backup of your System, Boot, etc. of your current boot-looped ROM with TWRP.
3. With TWRP's file manager, go into the internal storage and delete all the files within the backup folder.
4. Download this backup:
https://onedrive.live.com/?id=19085CD12562E567%21931&cid=19085CD12562E567&group=0&parId=19085CD12562E567%21925&authkey=%21AHmuVovnpuzX0tI&action=locate
5. Extract the files from the zip and copy them over to the backup folder on the internal storage.
6. Go to Restore on TWRP and dance.
After many attempts of trying to restore from an external SD card and from just creating my own TWRP backup folder, TWRP just wouldn't see the backup until I copied and replaced. I'm glad it worked and I hope it helps anyone else who needs a restore.
Credit goes to jmreyesiii for providing the backup files and vampirefo for the rooting.
PhantomOSX said:
After tinkering with the tablet and trying my best to restore it I finally was able last night to restore it to a clean install using this method. I'm sure there may be other ways to do it as well but this worked for me and was painless.
Credit goes to jmreyesiii for providing the backup files and vampirefo for the rooting.
Click to expand...
Click to collapse
An absolutely great post! You need a special thanks because this ability to recover from catastrophe likely will encourage others to move forward with more daring mods. I feel much more secure in playing with a few ideas knowing you have the base Rom and recovery spelled out and that it actually worked (Yes, I knew how, but knowing it worked for sure is huge!)
Thanks,
Freddy999
Now if only some kind hearted dev would release a ROM....
Actually, after you root and decrypt it, and fix the cpu governor and such, and get rid of the google apps that you don't use, with the exception of the lollipop HW overlay flaw it is not a bad ROM to start with. I wiped most of the Google stuff and put in Nova launcher. Now the device is quite manageable and very fast without much further help. Here is a pretty good summary of the device for anyone who has the tools to build a ROM: http://specdevice.com/showspec.php?id=ee2d-39de-0033-c5870033c587 with the exception I can not find that the FM radio exists in the device although the hardware seems to say it is there..........
what do you mean cpu governor?
adamx said:
what do you mean cpu governor?
Click to expand...
Click to collapse
Playstore: No frills CPU control
set it ondemand, noop
You might want to get also CPU spy reloaded to see the effect/
The backup file expired (or something) on OneDrive. Would you mind re-upping it somewhere? Thanks!
PhantomOSX said:
After tinkering with the tablet and trying my best to restore it I finally was able last night to restore it to a clean install using this method. I'm sure there may be other ways to do it as well but this worked for me and was painless.
1. Make sure the tablet is rooted/unencrypted using Vampirefo's guide:
http://forum.xda-developers.com/android/development/root-nextbook-ares-8-twrp-recovery-t3133165
2. Make a backup of your System, Boot, etc. of your current boot-looped ROM with TWRP.
3. With TWRP's file manager, go into the internal storage and delete all the files within the backup folder.
4. Download this backup:
https://onedrive.live.com/?id=19085CD12562E567%21931&cid=19085CD12562E567&group=0&parId=19085CD12562E567%21925&authkey=%21AHmuVovnpuzX0tI&action=locate
5. Extract the files from the zip and copy them over to the backup folder on the internal storage.
6. Go to Restore on TWRP and dance.
After many attempts of trying to restore from an external SD card and from just creating my own TWRP backup folder, TWRP just wouldn't see the backup until I copied and replaced. I'm glad it worked and I hope it helps anyone else who needs a restore.
Credit goes to jmreyesiii for providing the backup files and vampirefo for the rooting.
Click to expand...
Click to collapse
Yes the link to the backup is dead, can OP or anyone else upload another? I wiped the internal storage and now android has no home or back buttons so I cant get out of apps
Uploaded to MEGA https://mega.nz/#!1J4VwDxL!ZvRkBlvD7m-ldc5qQxA_xDWfUiu6WDdJa3nAMvDfhZY
stevemp said:
Uploaded to MEGA https://mega.nz/#!1J4VwDxL!ZvRkBlvD7m-ldc5qQxA_xDWfUiu6WDdJa3nAMvDfhZY
Click to expand...
Click to collapse
Thanks!
stevemp said:
Uploaded to MEGA https://mega.nz/#!1J4VwDxL!ZvRkBlvD7m-ldc5qQxA_xDWfUiu6WDdJa3nAMvDfhZY
Click to expand...
Click to collapse
Thanks Steve you're a true bro
THANK YOU!!!!!!!!!
I rooted and removed the encryption from my ARES 8 but then when messing with an (official) flashing tool I ended up formatting my system partition., So I had NO OS at all., But I did have TWRP., And now thanks to your post I have a living breathing working tablet again., By all your gods (or none at all if that's your thing) I Bless you! Thank you X Infinity! :good::good::good::good::good:
-Eric.
P.S. I got it to work from my SD card but I did have to make a backup with TWRP first, then pop the SD card into the PC delete all the files from the folder and copy your files into the folder that TWRP had created. Otherwise it didn't show up at all... Anyway Thanks again! :victory:
PhantomOSX said:
After tinkering with the tablet and trying my best to restore it I finally was able last night to restore it to a clean install using this method. I'm sure there may be other ways to do it as well but this worked for me and was painless.
1. Make sure the tablet is rooted/unencrypted using Vampirefo's guide:
http://forum.xda-developers.com/android/development/root-nextbook-ares-8-twrp-recovery-t3133165
2. Make a backup of your System, Boot, etc. of your current boot-looped ROM with TWRP.
3. With TWRP's file manager, go into the internal storage and delete all the files within the backup folder.
4. Download this backup:
https://onedrive.live.com/?id=19085CD12562E567%21931&cid=19085CD12562E567&group=0&parId=19085CD12562E567%21925&authkey=%21AHmuVovnpuzX0tI&action=locate
5. Extract the files from the zip and copy them over to the backup folder on the internal storage.
6. Go to Restore on TWRP and dance.
After many attempts of trying to restore from an external SD card and from just creating my own TWRP backup folder, TWRP just wouldn't see the backup until I copied and replaced. I'm glad it worked and I hope it helps anyone else who needs a restore.
Credit goes to jmreyesiii for providing the backup files and vampirefo for the rooting.
Click to expand...
Click to collapse
It's says root only on Linux I have windows xp does anyone know how I can root this on this type of computer thank u
Here is a question, we bought one for the grandson.. How come when you open up the play store, and choose apps, it does not show any that came with the tablet itself, kind of like you see when you go to play store on a smartphone..
really need some help
ericzollman said:
I rooted and removed the encryption from my ARES 8 but then when messing with an (official) flashing tool I ended up formatting my system partition., So I had NO OS at all., But I did have TWRP., And now thanks to your post I have a living breathing working tablet again., By all your gods (or none at all if that's your thing) I Bless you! Thank you X Infinity! :good::good::good::good::good:
-Eric.
P.S. I got it to work from my SD card but I did have to make a backup with TWRP first, then pop the SD card into the PC delete all the files from the folder and copy your files into the folder that TWRP had created. Otherwise it didn't show up at all... Anyway Thanks again! :victory:
Click to expand...
Click to collapse
i am having the same basic problem, i flashed twrp and supersu not sure what i did wrong or if it rooted succesfuly, i do have twrp but wont boot past recovery. twrp says it cant mount data and i cant back up., and have no os. how can i fix this ?
im new to this whole thing so please give me step by step if you can and any links or downloads you can, please help :crying: this tablet is how i comunicate w my daughter... in colorado. i need it up and running
I partitioned my Ares 8 and now it is stuck awaiting fastboot command. Any ideas?
Can someone help me? Why does mine fail when restoring system?
My ares 8 is stuck in DNX mode and will not enter recovery, and is pretty hosed. I need a scatterfile and rom so I can flash it and use it for something besides a paperweight. Thanks 1000 times in advance!
Ahhh, after several hours of reading, I managed to get recovery back, but cannot seem to flash a rom successfully, and also my backup - says it was successful but when I reboot, it goes straight to DnX mode and I have to use a batch file to get back to recovery. But progress has been made and hopefully by today I will have it back up and running an OS
Hi, i have Nextbook Ares 8 after rooing i can't boot the device it has an error says "Your device is unable to start because the Android OS image has failed to verify" please help me to fix this problem.
Related
I have an HTC sensation z7z10a. I purchased this phone to be able to get on AT&T's 3&4g frequencies without having to upgrade my unlimited data plan for non smart phones. So far so good, my phone gets 4g and AT$T is not aware that I have a smartphone.
Naturally after spending enough time in XDA and other phone forums to figure this out I became interested in flashing a custom ROM.
I used the revolutionary method to gain S-OFF, installed CWM, and used CWM to create a backup image. I've managed to fully wipe and then restore to my backup image, so CWM is working.
My problem is whenever I go to flash a custom rom I don't understand which file to select in recovery mode. Every zip I have downloaded, (including the one I need to finally get my phone rooted) opens up to a series of subfolders, none of which contain the files I need. The sub folders are typically : System, Data and META-INF. So I can't get rooted without being able to use the recovery mode to flash.
I used my friend's pc netbook in order to run Revolutionary and install CWM. Now I am using my Macbook Pro to download potential Roms zip files and move them onto my phones SD card. Could this be the problem?
I"ve searched and searched for and answer to this issue to no avail, please help me to figure this out. I'm stumped.
The zip you have to flash is the ROM you download...am I missing something?
You do not need to extract the zip file. Just put it on the SD card and then go to the recovery mode and select the option install zip from sd card and install it. I believe if you flash a custom rom, you would be automatically rooted, so no need to root it separately. Hope this helped
aNYthing24 said:
The zip you have to flash is the ROM you download...am I missing something?
Click to expand...
Click to collapse
Exactly- I don't understand why it won't work.
SickL1408 said:
You do not need to extract the zip file. Just put it on the SD card and then go to the recovery mode and select the option install zip from sd card and install it. I believe if you flash a custom rom, you would be automatically rooted, so no need to root it separately. Hope this helped
Click to expand...
Click to collapse
Thanks for this advice, this is my first time attempting this. I think you are right that most roms come with root access so I may be able to skip that step.
I know what you are saying, don't extract the file, just move the zip over as is. Only on my mac the files are arriving as a folder with subfolders, not a zip package. This HAS to be the problem! I will look harder for Mac info on downloaded zips to see if I can figure out why this is happening. Thanks again.
Update:
So I fixed the folder problem by going into safari settings and unchecking the open safe downloads box. No all the zip files I'm downloading are staying intact as zips.
However I just tried to flash revolution hd with no success. The full wipe zip for this rom was a failure as well. I will now try downloading the root zip again and see if rooting first helps at all.
So now I am rooted. Success!
imru88 said:
Update:
So I fixed the folder problem by going into safari settings and unchecking the open safe downloads box. No all the zip files I'm downloading are staying intact as zips.
However I just tried to flash revolution hd with no success. The full wipe zip for this rom was a failure as well. I will now try downloading the root zip again and see if rooting first helps at all.
Click to expand...
Click to collapse
Ah....Steve Jobs and his desire to prevent the user from doing anything useful strikes from beyond the grave.
This is why I won't touch a Mac. They want to do everything for you, even if it's not what you want or need to be done. On the plus side, at least you only have to push 1 button to get the Mac to do the wrong thing!
Glad you figured it out! Be careful with the ROM flashing though. It quickly becomes a life consuming obsession.
I rooted my S3, changed one file, and am now stuck in the startup screen. I've looked on the forums but I'd like to confirm what my recovery options are.
(1) Since I have no backup*, can I recover from a factory recovery for my model and still keep some of my data, apps and customizations?
It's a N American SIII (Rogers Wireless Samsung SGH-I747M). I can boot successfully into both Odin and CWM Recovery (Clockwork 5.5). BusyBox installed. I do not have a functioning MicroSD.
*I only did one thing:
renamed framework-res.apk to framework-res.apk2 to test permissions. Errors and crash ensued, then I restarted and here I am.
That apk file is part of a fix which is circulating that corrects a bug in the North American models' battery reporting, which requires replacing the apk with a slightly modified version. I thought trying a file rename was a safe small test, prior to backing up. The name "framework" should have tipped me off probably.
(2) Is factory recovery my best option? I would love to get in and just name the file back. But I can't get in.
(3) Was some automatic backup made that I overlooked? Rooting and the learning curve took so many steps I can't remember myself.
(4) Can I just restore the /system directory perhaps?
Yep, relative noob here. Hope my question is placed correctly and I haven't missed another post with the answers I need, if not pls advise.
Copied question to a better thread
It's now in the Android Q&A, see:
http://forum.xda-developers.com/showthread.php?p=28256764
Just getting used to the forum here.
NEVER FEAR find a ROM that you want to install and flash it using Odin or copy it to SD card and flash using clockwork mod And no there is no secret backup BTW once you get your phone working again make a backup then Go to where its stored And label it ALWAYS backup as soon as you root your phone
If you can manage, push a similar framework (taken from someone else) using adb...
Typed using a small touchscreen
How?
jezus101 said:
NEVER FEAR find a ROM that you want to install and flash it using Odin or copy it to SD card and flash using clockwork mod And no there is no secret backup BTW once you get your phone working again make a backup then Go to where its stored And label it ALWAYS backup as soon as you root your phone
Click to expand...
Click to collapse
You can flash a ROM using Clockwork instead of Odin? I totally missed that memo! Tips please
I found that Clockwork required the file to be in the internal SD folder -- I couldn't access the External SD card under any circumstance. There was no way to get a file to the internal file system without a functioning ROM. This is still confusing me. Maybe I had the wrong version of Clockwork or was doing it wrong. Not for lack of trying.
Below are links to full backups that can be restored in TWRP for the H910 after the Dirty Santa exploit. This is useful for restoring a bad install once you have access to TWRP. I will outline three methods for install below that will help in putting back the TWRP backups, a good method for installing it, and a few suggestions I have from restoring my device about 10 times now. So without further ado.
UPDATE: I bricked my device and had to send it off for repair (turns out I can't just flash US996 firmware for funsies) I received my phone back with the still rootable OTA 10L and yesterday I rooted it again and uploaded the new firmware. So if you're an AT&T user who wants the second latest update (10M dropped 04-15 but it isn't rootable as far as I know) then you can grab this and run it along with the stock kernel I made a backup of. I'll update the links below to reflect this. Stock 10L kernel located in tips section. Not flashable, you must extract and install as image and immediately install SuperSU 2.79 or greater or your device won't boot!
How to Install and Restore Stock Images and Boot (Kernel) Image
1.) DOWNLOAD - https://www.androidfilehost.com/?fid=673368273298948069 (Updated to 10L) download the file and verify the MD5sum of the zip matches the file you downloaded. (System image link for devs posted at the bottom)
1a) Download the latest SuperSU 2.79 flashable zip from here: http://www.supersu.com/download
2.) EXTRACT --This is not a flashable zip-- extract the zip file wherever you would like so that it can be copied to the device
3.) COPY - The extracted folder to TWRP > BACKUPS > (paste here) on either the MicroSD card (preferable) or internal storage (This will be wiped when you format data)
4.) REBOOT TO RECOVERY - Once the folders are copied to the backup directory you can reboot to TWRP to begin the restore process.
5.) WIPE - This is getting two sections in order to account for two situations
5a) MICROSD - If you have a MicroSD card and copied the restore files to it wipe everything: Data, Cache, Dalvik/ART, Internal Storage, and System.
5b) INTERNAL STORAGE - If you don't have a MicroSD card installed only wipe the following: Data, Cache, Dalvik/ART, and System.
6.) REBOOT TO RECOVERY - Once you have wiped everything, especially if you wiped internal storage, you should reboot TWRP before you start the restore process
7.) RESTORE - Back in TWRP Choose Restore from the main menu and if you can't see your restore file choose "Select Storage" at the bottom and inside that folder uncheck RECOVERY unless you want to overwrite TWRP (which I recommend against).
7a) I would recommend checking the box "Enable MD5 Verification of Backup Files" which is a little slower but ensures a good restoration
8.) SWIPE - Swipe to begin the operation and it will alert you upon completion. You will need a very large amount of space on your card to do it since the system image is split into 3 packages
9.) ROOT - Do not reboot until you have rooted! The unlocked bootloader will prevent booting on the stock kernel. The stock kernel can be used if it is rooted first, otherwise you will be stuck on the LG Boot logo.
10.) REBOOT TO SYSTEM - The phone will reboot itself! Don't panic, this is part of the standard rooting procedure. Now, see tips at the bottom for best performance.
TIPS!
- This is the 10L update stock kernel made during dirty santa method. This kernel has all features working minus the static on boot being gone, but Wifi calling, comfort view, FM radio, etc are fixed using this kernel. https://www.androidfilehost.com/?fid=817550096634762281 (You must flash SuperSU 2.79 or greater after flashing this kernel before you reboot! Not Flashable, must extract)
- To use the above kernel, download his ROM and extract the boot.img file from that archive. Save it to your device, boot to TWRP, choose Install, Install Image, and click the boot.img file. Then choose the checkbox for "boot" and swipe to flash. Really important to install SuperSU again after installing the custom kernel.
- Boot-up static can be cleared by allowing phone to boot to screen off, placing it face down to turn of second screen, and then flipping it back over. Static will be gone until next boot.
- Using fstrim after wiping in TWRP is good for increasing flash drive performance. Go to TWRP > Advanced > Terminal and type fstrim -v /data/
- You can do fstrim on /system and /cache as well to get all three partitions running clean
- Some of the AT&T apps that you can remove with TiBu are tied to bootup. Be careful what you remove if you like to get past the AT&T logo.
- The button combo to get into TWRP from powered off is Vol Down + Power until the LG Logo appears then let go of power and immediately press power again.
- That button combo boots you to a screen asking it you want to wipe your device. Answering 'yes' to both questions boots you to TWRP.
10L System Image Link for ROM creation (In TWRP emmc format): https://www.androidfilehost.com/?fid=745425885120724506
THANKS!
Google - Because, Android
@me2151 for the unlock and root method (and bricking his phone for us; sorry that happened to your device)
@glitschi667 for the work he did on Dirty Santa with me2151
@jcadduono for getting TWRP ready for us despite not having a V20 at all
@Tilde88 for compiling the kernel sources and creating an excellent ROM for all rooted variants of the device!
@EMSpilot for the debug phone!
@elliwigy for helping everyone troubleshoot and test everything recently
If I forgot you, and believe me a lot of people deserve to be here, let me know and I'll add you
9.) ROOT - Do not reboot until you have rooted! The unlocked bootloader will prevent booting on the stock kernel. The stock kernel can be used if it is rooted first, otherwise you will be stuck on the LG Boot logo. [/QUOTE] What exact method of rooting do you mean, without rebooting? Do you mean just flashing SuperSU? Can you clarify? THANKS for everything! Hoping this gets me out of my semi-brick. No matter what I flash...it keeps reverting back to TWRP.
EDIT: I did this, exactly...and yet again...I'm stuck in the phone autobooting back to TWRP. Any suggestions? Is this bricked?
jreed3786 said:
9.) ROOT - Do not reboot until you have rooted! The unlocked bootloader will prevent booting on the stock kernel. The stock kernel can be used if it is rooted first, otherwise you will be stuck on the LG Boot logo. What exact method of rooting do you mean, without rebooting? Do you mean just flashing SuperSU? Can you clarify? THANKS for everything! Hoping this gets me out of my semi-brick. No matter what I flash...it keeps reverting back to TWRP.
EDIT: I did this, exactly...and yet again...I'm stuck in the phone autobooting back to TWRP. Any suggestions? Is this bricked?
Click to expand...
Click to collapse
If you do a battery pull and can get to TWRP you are not bricked. However, I have no idea what you did to get a bootloop. What kernel did you install: the stock one from TWRP or Tilde88's kernel from his ROM? Either way, if you did this:
Wipe > Restore (Boot and System) > Install SuperSU 2.79 zip > Reboot
then you did the correct steps. The issue of not having SuperSU installed on my device was not booting past the LG logo and never rebooting. However, the method I most recently followed was:
Wipe > Restore (boot and system) > Install Tilde88 kernel > Flash SuperSU > Reboot
and my phone has been running extremely well. I need way more info from you before I can help you further.
AlkaliV2 said:
If you do a battery pull and can get to TWRP you are not bricked. However, I have no idea what you did to get a bootloop. What kernel did you install: the stock one from TWRP or Tilde88's kernel from his ROM? Either way, if you did this:
Wipe > Restore (Boot and System) > Install SuperSU 2.79 zip > Reboot
then you did the correct steps. The issue of not having SuperSU installed on my device was not booting past the LG logo and never rebooting. However, the method I most recently followed was:
Wipe > Restore (boot and system) > Install Tilde88 kernel > Flash SuperSU > Reboot
and my phone has been running extremely well. I need way more info from you before I can help you further.
Click to expand...
Click to collapse
Shoot...I think I followed your instructions in Tilde88's thread....and hit reboot instead of flashing his kernel. I then went back in to TWRP to reflash the entire thing...and the kernel...and I was given crap about encryption. Then, that's when the bootloop started. Right now, I'm sitting on TWRP. I've tried flashing everything, per instructions....but I guess, what I'm asking, is...since I'm on TWRP...and it's bootlooping because of encryption...what would you personally do? Shoot...I'll pay ya if you can fix this! LOL. I just really never dealt with the encryption thing until this phone...never really had problems till now.
---------- Post added at 09:28 AM ---------- Previous post was at 09:12 AM ----------
FLASHED EXACTLY THE WAY YOU DID (WITHOUT THE REBOOTING TO RECOVERY IN THE OP)...NOW, IT GETS TO STATIC, THEN LG SCREEN, REBOOTS ONCE TO STATIC THEN BOOTS UP!!! YAY!!! :good::highfive:
I guess there's no need to REBOOT TO RECOVERY if a person faces encryption issues and is trying to fix their phone. Even after decrypting, I came up with issues. Now let's see if this this asks for my PIN on reboot. THAT was another issue!
IT WORKED!!! THANKS! I'LL now try to go back into TWRP and flash the Tilde's boot.img
So...by flashing your STOCK TWRP backup...per your instructions, I was TOTALLY FIXED...I then didn't even flash Tilde88's kernel...I immediately rebooted back to TWRP, and DID NOT WIPE...but immediately flashed his ROM....and BOOM! Google Now/Always On works flawlessly, zero lag! AWESOME!
So, to all that are having issues with no Google Now/Always On...follow this instructional on this thread and DO NOT wipe after flashing Tilde's rom.
BTW, I shot you a PM, bro! :highfive::good:
jreed3786 said:
So...by flashing your STOCK TWRP backup...per your instructions, I was TOTALLY FIXED...I then didn't even flash Tilde88's kernel...I immediately rebooted back to TWRP, and DID NOT WIPE...but immediately flashed his ROM....and BOOM! Google Now/Always On works flawlessly, zero lag! AWESOME!
So, to all that are having issues with no Google Now/Always On...follow this instructional on this thread and DO NOT wipe after flashing Tilde's rom.
BTW, I shot you a PM, bro! :highfive::good:
Click to expand...
Click to collapse
Nothing like some good news to start the day. I wanted to let you know that the reason this worked is that it is essentially a dirty flash that replaces the stock kernel and adds his ROM tweaks into my stock system. So once it had booted and you flashed over it you were able to keep the stock files needed to get screen off Google Now working while adding his audio tweaks and build.prop because they overwrite the stock files. Since my stock files are odexed and his are not I'm not sure how well all your system files will function since they've been overwritten but if you have no issues then no harm, no foul.
I'm glad this got sorted and to anyone else if you follow this guide and you have any confusion about the instructions just do an @AlkaliV2 and I will do my best to help and I will also fix up the guide so that it is less confusing. Just let me know.
Stuck again....in TWRP.
Delete please
Same issue
i followed it to the letter yet i still keep being returned to team win recovery no matter what i do.
Great step by step instructions. Thanks!
sikiro said:
i followed it to the letter yet i still keep being returned to team win recovery no matter what i do.
Click to expand...
Click to collapse
Try booting into your bootloader (fastboot) and type:
fastboot erase misc
fastboot erase cache
fastboot erase fota
fastboot reboot
See if that helps you at all. Make sure you have a valid ROM flashed correctly though.
im having trouble, i downloaded the file, and i put the extracted folder into TWRP>BACKUPS but when i go to restore on TWRP theres no files to be open, am i supposed to keep the file as a zip or?
prlatorre said:
im having trouble, i downloaded the file, and i put the extracted folder into TWRP>BACKUPS but when i go to restore on TWRP theres no files to be open, am i supposed to keep the file as a zip or?
Click to expand...
Click to collapse
I was having the same issue, do a backup(choose something small) from TWRP. It will create the TWRP>Backups Folder for you and then you can place the extracted zip. from this thread into that folder and it will see it.
ajairola said:
I was having the same issue, do a backup(choose something small) from TWRP. It will create the TWRP>Backups Folder for you and then you can place the extracted zip. from this thread into that folder and it will see it.
Click to expand...
Click to collapse
i've tried what you suggested, and still nothing seems to show up, i made a back up in both internal and micro sd
prlatorre said:
i've tried what you suggested, and still nothing seems to show up, i made a back up in both internal and micro sd
Click to expand...
Click to collapse
So you created a backup of let's say the EFS partition in TWRP. You backed it up once to the internal SD card and once to the external sd card. Then you extracted the zip from step one, placed the folder inside of the backups folder and it does not appear?
how can i use this file if i i'm not rooted? My phone is being weird and i would like to reload the stock software on it.
truwrxtacy said:
how can i use this file if i i'm not rooted? My phone is being weird and i would like to reload the stock software on it.
Click to expand...
Click to collapse
You cant all you can do is factory reset on stock
jerrycoffman45 said:
You cant all you can do is factory reset on stock
Click to expand...
Click to collapse
Does the factory reset to stock also reset the recovery? Want to root phone but will most likely trade in to ATT once I'm eligible for upgrade(with trade in).
Manbot27 said:
Does the factory reset to stock also reset the recovery? Want to root phone but will most likely trade in to ATT once I'm eligible for upgrade(with trade in).
Click to expand...
Click to collapse
right now the root method for the h910 does not allow you to go back to stock
My 8gb sdcard ran out of space during step #8. Can I copy the contents of the sdcard to a bigger card and redo the full restoration from step 1?
---------- Post added at 01:27 PM ---------- Previous post was at 01:06 PM ----------
AlkaliV2 said:
So you created a backup of let's say the EFS partition in TWRP. You backed it up once to the internal SD card and once to the external sd card. Then you extracted the zip from step one, placed the folder inside of the backups folder and it does not appear?
Click to expand...
Click to collapse
Having the same issue. I copied the folder over to the microsd card and the folder I copied over isnt showing up in restore. I cant do anything or wipe anything if I cant see a backup right?
Im going to try and do the internal storage copy. No other choice.
cwis said:
My 8gb sdcard ran out of space during step #8. Can I copy the contents of the sdcard to a bigger card and redo the full restoration from step 1?
---------- Post added at 01:27 PM ---------- Previous post was at 01:06 PM ----------
Having the same issue. I copied the folder over to the microsd card and the folder I copied over isnt showing up in restore. I cant do anything or wipe anything if I cant see a backup right?
Im going to try and do the internal storage copy. No other choice.
Click to expand...
Click to collapse
If you create a backup of anything on the Microsd card before you attempt to put the folder in it, it will create the directories for you and all you have to do is copy and paste at that point.
So I tried my first Nandroid backup today using TWRP and a howtogeek - "How to Back Up and Restore Your Android Phone with TWRP" guide I found off a quick google search.
Basically TWRP, backup(boot,system,data), reboot to android, shut down, twrp-restore then reboot.
When I would reboot after TWRP-restore, it shows the typical bootloader corrupt error msg.
Shuts down again, shows the bootloader msg, then goes into TWRP, asks for my decrypt password, then begins to run an openrecovery script (I think?) of some sort. I then go to reboot my phone again, bang factory reset mode.
I hope I'm not alone here.:cyclops: I'd just really love to be able to backup/image my phone entirely so I can try out a few custom roms, and for general knowledge sake.
thanks!:silly:
mark7807 said:
So I tried my first Nandroid backup today using TWRP and a howtogeek - "How to Back Up and Restore Your Android Phone with TWRP" guide I found off a quick google search.
Basically TWRP, backup(boot,system,data), reboot to android, shut down, twrp-restore then reboot.
When I would reboot after TWRP-restore, it shows the typical bootloader corrupt error msg.
Shuts down again, shows the bootloader msg, then goes into TWRP, asks for my decrypt password, then begins to run an openrecovery script (I think?) of some sort. I then go to reboot my phone again, bang factory reset mode.
I hope I'm not alone here.:cyclops: I'd just really love to be able to backup/image my phone entirely so I can try out a few custom roms, and for general knowledge sake.
thanks!:silly:
Click to expand...
Click to collapse
What version of TWRP have you been using? I understand, RC2 has issues with properly restoring a backup. (RC is release candidate and is not considered fully stable, however, works well enough to flash custom roms and such).
The partitions on the pixel are set up in a more complex way than previously seen on many android phones, which is why there's no perfectly stable version of TWRP yet. You could try using RC1 to see if you get better luck backing up and restoring, however, you should assume that you may run into other issues and be prepared to deal with them should they arise.
exad said:
What version of TWRP have you been using? I understand, RC2 has issues with properly restoring a backup. (RC is release candidate and is not considered fully stable, however, works well enough to flash custom roms and such).
The partitions on the pixel are set up in a more complex way than previously seen on many android phones, which is why there's no perfectly stable version of TWRP yet. You could try using RC1 to see if you get better luck backing up and restoring, however, you should assume that you may run into other issues and be prepared to deal with them should they arise.
Click to expand...
Click to collapse
I'm running 3.1.0-0RC2 so maybe I'll try RC1. Normally I'd just go off and try everything but unfortunately I'm not in a situation I can simply play with my Pixel and potentially brick it leaving me without a phone for who knows how long.
I don't think there would be any harm with playing with RC1 but I'll research a little bit more into it and see what I can find out first. I heard the partitions are split for redundancy(?) for firmware upgrades and dual-booting. That's something all else on it's own as I've REALLY wanted to get my phone ultimately on a Multi-Rom setup but it seems way too complicated for me at the moment to try on my own even though I'm generally good with this stuff..
Thanks exad for the insight. Any other help is greatly appreciated.
mark7807 said:
I'm running 3.1.0-0RC2 so maybe I'll try RC1. Normally I'd just go off and try everything but unfortunately I'm not in a situation I can simply play with my Pixel and potentially brick it leaving me without a phone for who knows how long.
I don't think there would be any harm with playing with RC1 but I'll research a little bit more into it and see what I can find out first. I heard the partitions are split for redundancy(?) for firmware upgrades and dual-booting. That's something all else on it's own as I've REALLY wanted to get my phone ultimately on a Multi-Rom setup but it seems way too complicated for me at the moment to try on my own even though I'm generally good with this stuff..
Thanks exad for the insight. Any other help is greatly appreciated.
Click to expand...
Click to collapse
I would say use RC1 too. I've used it and never had a problem with it other than the occasional failure to decrypt which is no big deal. Just reboot back into recovery. I would add though, instead of backing up system, backup system image. Also vendor image. If you back up system instead of system image you'll more than likely run into battery drain problems. I'm not sure what causes it but it'll cut your battery life down to only several hours. Using system image doesn't cause that problem.
If you should happen to accidentally backup system instead of system image it's not a huge deal to fix it though. If you're on stock just download the factory image that you are currently on, extract the system.img file and flash it using fastboot. If you're on a custom rom, a dirty flash of the rom will fix it.
mark7807 said:
I'm running 3.1.0-0RC2 so maybe I'll try RC1. Normally I'd just go off and try everything but unfortunately I'm not in a situation I can simply play with my Pixel and potentially brick it leaving me without a phone for who knows how long.
I don't think there would be any harm with playing with RC1 but I'll research a little bit more into it and see what I can find out first. I heard the partitions are split for redundancy(?) for firmware upgrades and dual-booting. That's something all else on it's own as I've REALLY wanted to get my phone ultimately on a Multi-Rom setup but it seems way too complicated for me at the moment to try on my own even though I'm generally good with this stuff..
Thanks exad for the insight. Any other help is greatly appreciated.
Click to expand...
Click to collapse
RC1 and backup system image, vendor image, data and boot.
robocuff said:
I would say use RC1 too. I've used it and never had a problem with it other than the occasional failure to decrypt which is no big deal. Just reboot back into recovery. I would add though, instead of backing up system, backup system image. Also vendor image. If you back up system instead of system image you'll more than likely run into battery drain problems. I'm not sure what causes it but it'll cut your battery life down to only several hours. Using system image doesn't cause that problem.
If you should happen to accidentally backup system instead of system image it's not a huge deal to fix it though. If you're on stock just download the factory image that you are currently on, extract the system.img file and flash it using fastboot. If you're on a custom rom, a dirty flash of the rom will fix it.
Click to expand...
Click to collapse
TheBurgh said:
RC1 and backup system image, vendor image, data and boot.
Click to expand...
Click to collapse
Thanks again guys,
I ran a
fastboot boot twrp.zip to boot to what I thought was like a "live cd" version of twrp
with the rc1 .img and .zip in the sdcard directory I installed the .zip
booted my phone and it forces to recovery everytime now.
did I upset something?
I mean at this point, I could factory reset the google pixel all from the very beginning of time. boot/system the whole shabang, but I think this could be a good lesson from me if I could boot back to system out of this..
Okay. I have RC1 on here and have backed up to USB. I'm extremely tired and going to bed. I'll report back on how the restore goes. THANK YOU ALL!!!
mark7807 said:
Thanks again guys,
I ran a
fastboot boot twrp.zip to boot to what I thought was like a "live cd" version of twrp
with the rc1 .img and .zip in the sdcard directory I installed the .zip
booted my phone and it forces to recovery everytime now.
did I upset something?
I mean at this point, I could factory reset the google pixel all from the very beginning of time. boot/system the whole shabang, but I think this could be a good lesson from me if I could boot back to system out of this..
Okay. I have RC1 on here and have backed up to USB. I'm extremely tired and going to bed. I'll report back on how the restore goes. THANK YOU ALL!!!
Click to expand...
Click to collapse
Okay so, I stayed up a little late and tried a restore. I got this error near the end of the restore "extractTarFork() process ended with error: 255" in which resulted in corruption of files and a failed restore. Was I supposed to unmount data? Is there any reason I can't backup all partitions?
mark7807 said:
Okay so, I stayed up a little late and tried a restore. I got this error near the end of the restore "extractTarFork() process ended with error: 255" in which resulted in corruption of files and a failed restore. Was I supposed to unmount data? Is there any reason I can't backup all partitions?
Click to expand...
Click to collapse
Not sure where to direct you at this point. I have always used RC1 and backed up system image, vendor image, data and boot and never had a problem restoring. Someone with better knowledge will come around.
TheBurgh said:
Not sure where to direct you at this point. I have always used RC1 and backed up system image, vendor image, data and boot and never had a problem restoring. Someone with better knowledge will come around.
Click to expand...
Click to collapse
Yeah very strange I did exactly what you told me to do as well. Any changes to partitions I backup if my phone is rooted by chance??
mark7807 said:
Yeah very strange I did exactly what you told me to do as well. Any changes to partitions I backup if my phone is rooted by chance??
Click to expand...
Click to collapse
Not that I am aware of. Mine is rooted and backups have been smooth sailing.
I recently attempted creating a nandroid backup via TWRP on my rooted Pixel and I'm consistently getting an error: 'cannot create [path]\backup file" message from TWRP. Is there a permission issue that I've overlooked here or does anyone have any thoughts as to why my rooted Pixel would be denying TWRP authority to create the backup?
Thanks
What version of twrp ?
I only use rc1, never seen this.
Yep- RC1. I'm thinking it's in 'read only' mode or something because as soon as it attempts to create the folder/file- no-go.
pstgh said:
Yep- RC1. I'm thinking it's in 'read only' mode or something because as soon as it attempts to create the folder/file- no-go.
Click to expand...
Click to collapse
When you boot into TWRP did it ask for your unlock PIN? If it doesn't/didn't, either keep rebooting into recovery or turn the phone off and go back into recovery until TWRP does ask for your encryption PIN. Sometimes TWRP doesn't ask, and without the PIN being entered, it can't write to the internal storage.
If you click "Install" in TWRP and see a bunch of gobbledygook it's because the internal storage is still encrypted so TWRP can't do anything with it.
You could probably use USB OTG through the USB-C connector, though, to do a backup to it, if you need to.
Tried it again and it worked flawlessly.... it seems sort of buggy in that sometimes it presents the 'pattern' security lock that I use and sometimes it doesn't. After booting up in the bootloader and fastbooting the TWRP boot image slowly and methodically, the security pattern came up and all is perfect- thanks.
---------- Post added at 08:37 PM ---------- Previous post was at 08:36 PM ----------
Now I'm wondering how to best move that backup folder (or a copy of it) over to Google Drive? I have root explorer, but not sure if it is capable of mounting to Google Drive.. any thoughts on best practices here would be appreciated.
Thanks
pstgh said:
Tried it again and it worked flawlessly.... it seems sort of buggy in that sometimes it presents the 'pattern' security lock that I use and sometimes it doesn't. After booting up in the bootloader and fastbooting the TWRP boot image slowly and methodically, the security pattern came up and all is perfect- thanks.
---------- Post added at 08:37 PM ---------- Previous post was at 08:36 PM ----------
Now I'm wondering how to best move that backup folder (or a copy of it) over to Google Drive? I have root explorer, but not sure if it is capable of mounting to Google Drive.. any thoughts on best practices here would be appreciated.
Thanks
Click to expand...
Click to collapse
I can't confirm since I've yet to do a successful backup but... Flashify Pro version looks like an option???
also
Anyone know when TWRP 3.1.0-0 will be out for Pixel? Looks like it addresses boot slots which off first glance seems like quite a fundamental feature no?
Thanks... I'm thinking I'll just adb pull the file over to my desktop... not sure.
pstgh said:
Thanks... I'm thinking I'll just adb pull the file over to my desktop... not sure.
Click to expand...
Click to collapse
Root Explorer does have support for Google Drive. In Root Explorer touch the plus sign in the lower right corner and in the menu that opens choose Google Drive tab.
Can get Root Explorer to connect to Google Drive, but when I select all of the backup files from my Pixel's TWRP backup folder, my only choices are to cut or copy them- so I tried both and then RE creates this little clipboard icon that you presumably click on to paste them once you've opened the proper GD folder.... so I tried that and in both cases (cut and copy) it says 'fail'.... ? Thoughts? I've given RE permission to manage folders and files in GD.
pstgh said:
Can get Root Explorer to connect to Google Drive, but when I select all of the backup files from my Pixel's TWRP backup folder, my only choices are to cut or copy them- so I tried both and then RE creates this little clipboard icon that you presumably click on to paste them once you've opened the proper GD folder.... so I tried that and in both cases (cut and copy) it says 'fail'.... ? Thoughts? I've given RE permission to manage folders and files in GD.
Click to expand...
Click to collapse
It sounds like you've got the right idea. Cut will move the files, copy will do just that. You choose one of the two and browse to the Google Drive tab, find the folder you want to use and then use the little clipboard thing to transfer the files to that folder. If that's what you're doing, the only thing I can think of right off the top of my head would be that you don't have enough space left on Google Drive for the size of the files you're trying to transfer. Try a picture or something and see if it takes that. If so, I'd suspect lack of Drive space is the reason it fails.
So ive searched for an answer to this but couldnt find it with google/xda.
I tried to install a custom rom.
My first rom install attempt ever on android
It failed with a signal 11 error
So after lots of trouble shooting trying any "fix" I could find suggested.
I read wiping before a rom install was required.
So I made a twrp backup, placed it on my pc, this is where I messed up and nobody in the countless threads I read said
I deleted the twrp backup on device
Then wiped with twrp, following the era proper directions for device allegedly.
Which was wipe everything but internal storage, also read to format in the many topics I perused.
Then found everything was wiped, including /sdcard, and system/OS
WELL I STILL GOT SIGNAL 11 on rom flash attempt via sideload, since the zip got erased on sd.
I did manage to flash a rom, but wouldnt you know it, its a rom that cant connect to pc through usb.
If I try to push the twrp backup folder, it just says error in cmd while in sideload
Anybody know the proper way to do that? Or is it just a case of murphys law getting a right good laugh at my devices expense.
I did read I could use a micro usb to external storage to mount, but I lack that.
I need to restore twrp because I think I need to pull the vendor directory off device to try to overcome the signal 11 error.
Anyway any advice is appreciated and hopefully can serve others in the future.
Thanks and cheers
Re-flash Stock ROM.
Well I dont think the device in question has a stock rom. Or I cant find one at first glance.
I had to roll back the version to unlock bootloader and root.
But that .bin wouldnt help I think.. hmm
Back to the drawing board I guess.
Perks of a decade old device.
Apparently androidmtk.com has stock roms available, but is that site safe to use?
Sorry for my noobiness.
Edit: actually that bin is the stock firmware apparently. I hope at least.
Will try and report back.
Thanks jwoegerbauer
Edit2: that worked flashing the bin. Was able to mount on pc and add the backup back up.
Did have a stumble as without making a backup there wasnt a backups folder. I tried to manually create one, but twrp couldnt see the folder I made.
Not sure if it was the naming. I tried "Backups" but twrp created "BACKUPS"
I just backed up efs since it was smallest to get twrp to make it.
Cool. Now I can backup vendor for rom comparison. Was overstressed for half the day about it, but the solution was simple and right there in front of me.
Thanks again Jwoegerbauer
what do you mean "it's a rom that can't connect to pc through usb"?
what do you mean "was able to mount on pc"?
you have backup of old ROM on pc. what do you want to do with?
No worries alecxs
Yeah I was able to sideload a custom rom but that rom had broken/missing usb drivers so mtp on pc failed.
That was before I knew I had the stock rom.
I needed stock rom to be able to restore with twrp in order to pull vendor folder off original device.
(I need vendor folder to try to fix that broken custom rom)
Just me being a noob. Sorry again.
you're welcome. just asking for clarity.
you have answered one question, so let me give you hint on guesswork.
you can connect device with usb-debugging from developer options. adb is the recommended way to transfer files. MTP is a faulty implemented Microsoft protocol I wouldn't use for large amount of data (for small files is okay).
Android devices cannot mounted since Android 5.0.1 Lollipop as UMS has been dropped in favour of MTP. /sdcard is no longer separate FAT partition but emulated storage in /data/media.
Bear in mind TWRP backup does not include /data/media so one have to backup pictures manually. this can be done from adb.
Code:
adb pull -a /sdcard
For the same reason you will lose /sdcard every time you format /data.
If you're interested to restore backup to different ROM, you cannot use TWRP. backup of /data can only restored to the exact same ROM.
For restoring backup to different ROM use Migrate.
[APP][ROOT][5.0+][1st Nov 2020] Migrate - custom ROM migration tool
Jumping from one custom ROM to another can be a challenging task. So I decided to make an app to simplify the process. Introducing Migrate! Migrate-GPE (v4.0) is on Google Play It was temporarily suspended. Read more here...
forum.xda-developers.com