Related
As we now have functional recovery options on our tablets, and people will inevitably mess things up with their device, we need to get a way to get your tablets back to factory condition. But I need your help with this!
What do you want?
Here's my idea: We have all seen various ZIPs floating around, most of them leaked from somewhere. The problem with these is that you can't use OTA updates, and I'm not sure what Acer Service Center thinks of custom ROM installs. What I want is to build a list of software that is officially distributed by Acer, is OTA-updateable, etc. For this reason, I want people that have not yet modified their tablets (except root) to provide image dumps of their /system, /boot, /flexrom, and /recovery partition. It's really easy to do, and you'll help yourself and others when they get into trouble.
Can I help?
Answer all of the following questions. If at one point the answer is "Sorry, you can't help", well... You can't help
Is your device unlocked and rooted? Yes - You can help! / No - You can still help, but you need to unlock and root your device.
Do you have the original Acer ROM installed on your device? Yes - You can help! / No - Sorry, you can't help
Have you received the latest OTA updates for your device? Yes - You can help! / No - You can help as well!
Have you removed any apps or files from the /system or /flexrom partition? Yes - Sorry, you can't help / No - You can help!
Have you installed a custom recovery image? Yes - You can still help, as long as everything else is still original / No - You can help!
Okay, so I can help, now what?
If you can and are willing to help (remember, it could save your own ass one day), follow the instructions below. If you get stuck or simply don't know where to start but are willing to help, let us know in this thread and I'm sure we can all help eachother out.
This will not gather any personal data from you. Personal data is stored on the /data partition, which we don't need, so: No worries!
Root your device, if you haven't already.
Connect your tablet to your computer via ADB
Type the following command: adb shell. You are now logged into your tablet. You can exit at any time by typing exit and hitting ENTER.
Type the following command: dd if=/dev/block/mmcblk0p2 of=/sdcard/boot.img. This will copy your /boot partition to a file called boot.img on your internal storage. This one will be fast, it only has about 8MB to copy.
This step can be skipped if you have a custom recovery! Type the following command: dd if=/dev/block/mmcblk0p1 of=/sdcard/recovery.img. This will copy your /recovery partition to a file called recovery.img on your internal storage. This one will be fast as well, it only has about 6MB to copy.
Type the following command: dd if=/dev/block/mmcblk0p3 of=/sdcard/system.img. This will copy your /system partition to a file called system.img on your internal storage. This one will take a bit longer, it has about 360MB to copy.
Type the following command: dd if=/dev/block/mmcblk0p6 of=/sdcard/flexrom.img. This will copy your /flexrom partition to a file called flexrom.img on your internal storage. This one will take a bit longer as well, it has about 360MB to copy.
Type exit to exit the ADB shell. Copy the four .img files from your tablet (internal storage) to your computer. You might have to reboot your tablet if the files don't show up.
ZIP or RAR these files, and upload them somewhere. If you can't find a place to store them: send me a private message or reply in this thread and we'll arrange something else. If you have uploaded the files somewhere: again, send me a private message or reply in this thread.
So now what?
When I receive your files, I will package them into an update.zip that can be flashed from custom recoveries. This will then restore everything (including the custom recovery) to factory state, which can help you in getting your device back to stock.
What versions do you have already?
Acer_AV041_A510_1.044.00_WW_GEN1 (download links will follow shortly)
Acer_AV041_A510_1.098.00_EMEA_CUS1 (download links will follow shortly)
Acer_AV041_A510_1.099.00_EMEA_DE (download links will follow shortly)
The idea sounds great so far. But I have a small problem to make a complete backup for my a511.
Your linked root tutorial for the procedure is only for a100/a510 and doesn't work for a511, as I understand.
The tutorial for rooting the a511 needs first to flash a CWM.
http://forum.xda-developers.com/showthread.php?t=1729432
So it isn't possible for us to backup the recovery partition, right ?
I have the stock Acer_AV041_511_1.028.00_EMEA_DE on my device.
Is it even possible to backup and recover the baseband ?
I'm very interested in your CWM recovery for a511 too, but since many guys f++++d up their device now, I want to make sure that my device will not goes the same way.
i can help, n my tab is rooted.
but i don understand the first step: Connect your tablet to your computer via ADB
What about if we have removed system apps (such as the antivirus that comes with the tablet). It wouldn't be a complete dump if it didn't include those.
I have root and am happy to provide a dump, but I did uninstall several of the crappier pre-installed apps that came with my tablet.
scorpio16v said:
The idea sounds great so far. But I have a small problem to make a complete backup for my a511.
Your linked root tutorial for the procedure is only for a100/a510 and doesn't work for a511, as I understand.
The tutorial for rooting the a511 needs first to flash a CWM.
http://forum.xda-developers.com/showthread.php?t=1729432
So it isn't possible for us to backup the recovery partition, right ?
I have the stock Acer_AV041_511_1.028.00_EMEA_DE on my device.
Is it even possible to backup and recover the baseband ?
I'm very interested in your CWM recovery for a511 too, but since many guys f++++d up their device now, I want to make sure that my device will not goes the same way.
Click to expand...
Click to collapse
Hi, your device will not brick, I can send you a test A511 recovery if you want. Worst that can happen is that recovery won't boot, but in that case you can simply put back recovery. Send me a private message and we can work something out.
scae said:
What about if we have removed system apps (such as the antivirus that comes with the tablet). It wouldn't be a complete dump if it didn't include those.
I have root and am happy to provide a dump, but I did uninstall several of the crappier pre-installed apps that came with my tablet.
Click to expand...
Click to collapse
Then it's of no use, unless you have a backup of your pre-installed apps. Removing apps from the /system or /flexrom partition is not recommended, and you gain nothing by it: You only gain space on read-only filesystems which you won't use in 99% of situations, and you've now broken OTA's for yourself as well, as OTA's will only install when apps are present unless you start modifying OTA files.
The 'correct' way to get rid of pre-installed apps is simply freezing them, either from the settings menu or with an app like Titanium Backup. This will make it seem like they're not there (so they don't use resources at all), but the APKs don't get removed.
So unfortunately, we can't use your dumps to restore devices to factory state. Unless, ofcourse, you've made a backup of the apps somewhere.
skymario said:
i can help, n my tab is rooted.
but i don understand the first step: Connect your tablet to your computer via ADB
Click to expand...
Click to collapse
Do you have ADB or the Android SDK installed?
NoThrills said:
Do you have ADB or the Android SDK installed?
Click to expand...
Click to collapse
I just learned ADB, n successful install ur CWM, later will try to dump my stock Rom to u.
My stock Rom version 1.073 ww gen1
does it matter if the system apps have been frozen or do they need to be unfrozen first?
I have flashed that remove stock recovery mod so the stock rom doesn't keep overwriting cwm on reboot. Does that disqualify me? If not I'll dump my rom for you when I get home.
I'm on this rom version:
ro.build.pandora.id=Acer_AV041_A510_RV28RC04_PA_CUS1
ro.build.flexrom.id=Acer_AV041_A510_1.076.00_PA_CUS1
I unlocked bootloader,rooted,installed cwm then backed up my stock rom.Could i restore my stock rom then be able to send you those fills
and return to total stock.
NoThrills said:
Hi, your device will not brick, I can send you a test A511 recovery if you want. Worst that can happen is that recovery won't boot, but in that case you can simply put back recovery. Send me a private message and we can work something out.
Click to expand...
Click to collapse
i think he mean that the a511 recovery doesn't work properly....you can flash a zip, but nearly all other options brick the device
i have a a511 too with Acer_AV041_A511_1.028.00.EMEA_DE and can help with testing or something else
I have Acer AV041_A510_1.079.00_PA_CA. (Canada)
I have not done a thing to it because it is a replacement for the Galaxy Note I bricked trying to upgrade from GB to ICS, too early.
I might try again if I was sure I could get back to where I am, using your process.
I assume that your Root link is comprehensive but I also need reassurance on how to ADB.
[email protected]
Sent from my A510
blgblade said:
i think he mean that the a511 recovery doesn't work properly....you can flash a zip, but nearly all other options brick the device
Click to expand...
Click to collapse
No, as I understand, the only working methode to root the a511 is to bootloader unlock, flash the custom recovery and then the root.zip.
Maybe I'm wrong and there is another working way to root the device ?
The problem is simply, that we lost the stock recovery before we have a backup from it.
If we have another root way for a511, the backup of stock firmware is done in a few minutes and from this point we can test the a511 custom recovery from NoThrills.
To the A511 owners: Technically, if you have a install-recovery.sh file on your device, the device will always flash recovery back from the boot.img.
In theory: To test, one could simply overwrite the stock recovery with my Recovery (not the other ones, they will brick your device) and then when you reboot, your device will overwrite the recovery with the stock one again. So you really don't need a backup of the recovery partition.
As long as you don't let your device fully boot (so, stay in recovery) there's plenty of time to test if the recovery works or not. If it doesn't, simply reset your device and it will flash back the original recovery (again: provided there is a install-recovery.sh in your /system partition).
So again, if anyone is willing to test, let me know
NoThrills said:
To the A511 owners: Technically, if you have a install-recovery.sh file on your device, the device will always flash recovery back from the boot.img.
Click to expand...
Click to collapse
I can't find a install-recovery.sh in /system partition on my a511. Search on root-explorer can't find one on the device.
Even NOT on /system/etc like on other devices.
NoThrills said:
So unfortunately, we can't use your dumps to restore devices to factory state. Unless, ofcourse, you've made a backup of the apps somewhere.
Click to expand...
Click to collapse
Ah damn, I did back them up via titanium but it doesn't seem to want to restore them - it just sits there say restoring app.
scorpio16v said:
I can't find a install-recovery.sh in /system partition on my a511. Search on root-explorer can't find one on the device.
Even NOT on /system/etc like on other devices.
Click to expand...
Click to collapse
Yeah, I meant /system/etc... That's weird, I'd figure Acer would use the same system on the A511... Let me check one of the leaked ROMs...
Hello,
I have an stock Acer_AV041_A510_1.098.00_EMEA_CUS1, there we go for the files
Host file is not the stock version, it was edited by AdAway.
Can you make a version without recovery overwritting ?
I thinks a lot of people want to try some roms... just for testing...
Acer_AV041_A510_1.098.00_EMEA_CUS1 boot && system && flexroom:
http :// dl.free.fr/jDEmTNSD4
Have Fun
Hello,
I have the same rom without root or unlocked bootloader or moded recovery so if the above on does not make it I'll upload mine.
Sent from my A510 using xda app-developers app
Hello,
I thought of myself as a pretty experienced user, but you never learn enough!
However, I flashed some roms (lollipop) that, probably due to my mistakes, screwed up my file system, to the point that my recovery (latest PhilZ) wasn't able to find its backup anymore. Eventually I solved the problem as I was able to find my backups and use them to revert my phone to the rom I wanted to run (Carbon 4.4.4). But I was really annoyed by the fact that my file system was a bit off and still I was having problems with the recovery. So I decided to begin investigating the possibility to restore my phone to factory default. Before going with it, I tried the soft approach, i.e. I used the soft factory reset available from the settings menu. It all seemed fine and I re-flashed a lollipop rom that suited me.
Now the problem is that, after all the ordeal, I decided to make a new backup and so I did. It appears all fine, my recovery can actually "see" it, but I cannot identify it using a root browser! It seems to have disappeared unless I open the recovery and then I see it there. It is located in a folder that I can, of course, access, but,when I do so, I can't find the file!
I tried to put on my phone an old backup (always a PhilZ one), but when I try to put it on the phone I can't find the Backup folder in the Clockworkmod folder!
Anyone has any idea of what is going on and can give me a suggestion on how to overcome the problem?
Thanks
Luca
PS An alternative would be suggesting how to do a restore from a sideload: I thought I saw a similar option, but I can't seem to find it anymore within the recovery's options! I tried also restoring via NRT, but although all seem to go fine and the software return no failure notice, I can't find the backup file that should have been pushed (successfully) on my device!
Its not a recovery issue. Its an L issue.
Best thing to do would be to wipe data and storage then fastboot flash userdata.IMG
http://forum.xda-developers.com/showthread.php?t=2938749
rootSU said:
Its not a recovery issue. Its an L issue.
Best thing to do would be to wipe data and storage then fastboot flash userdata.IMG
http://forum.xda-developers.com/showthread.php?t=2938749
Click to expand...
Click to collapse
Thanks a lot for your help.
How can I find the img. file to flash?
Would it be ok to just go ahead and start from 0 using this:
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
How can fastboot flash an image file? I've never done that before! As I said, been doing this for a while, but never done this before...I think!
Luca
Alas, after reading your post on one-click toolkits, I'm afraid I'm one of those who thinks they can do things, but rely on simple tools to do them. However, I never (almost never) forgot to make a nandroid backup before flashing a new rom and, to be honest, I'm not a flashoolic. I never, ever bricked my phone (got a few bootloops). If I find a rom that suits my need, I stick with it for as long as I can.
The changes between KK and L are such that are beyond my comprehension, but I try hard to solve the problems I have without bugging everyone at the first obstacle. But now, after fidgeting with my phone for 2 days, I had to give up. With a few words, you singled out the reason why I couldn't come on top of this: things change and I was not informed of how much they did!
Luca
Problem partially solved..I think! Now I can see the folder and found my backup!!
I used the restorecon command you suggested. I couldn't make it work using terminal emulator (just did not accept the su command: why I don't really know). Then I thought about using adb shell via pc and, I really surprised myself; I was able to pull it through. I'm not totally brain damaged as I felt when I couldn't even reproduce the command you indicated. It is probably the application that doesn't work. It was my first time with adb shell, so a new thing learned.
However, now I would like to ask you: if I place in the proper folder the backup folder I saved on my pc, will I be able to restore the nandroid backup? I just need some data that I forgot (trivial things, such as text messages and a few app data, like passwords and stuff) but it would be useful.
Thanks once more for your help.
Luca
Hello there.
My phone is in a state which is widely being reffered to as "bricked". After hours of reading through hundreds of forums and trying out everything possible/impossible, I came to this - I'm posting here, and desperately asking you guys for help.
I have Moto G XT1032. I converted it to GPE, to install a 5.0.1 ROM few months ago. I used it without any problems. However, today I decided to try out the stock 5.0.2 ROM. But I read that I'll have to change my Data partition to F2FS (from EXT4). I did that (using TWRP v2.8.5.0), and then I did this terrible mistake: I decided to do a clean install, so I wiped everything. I wiped System, and Internal storage as well. Yes, I know that I'm stupid.
Now my phone is stuck at my custom recovery (TWRP) or at bootloader. I can switch between these two, but I can't boot to the system, because I don't have any system installed (because I wiped the /system partition - what an Einstein I am -_-). I thought that it would be easy - I just have to somehow push the zip file of the new ROM to my phone, and then install it from TWRP. The thing is - I can't transfer any files to the phone. I'm probably missing some drivers, but the problem is, that the phone doesn't have any operating system installed (besides bootloader, I guess) - so I can't get any drivers working. My PC is running Windows 7 64bit.
I tried installing Motorola Device Manager, I tried using the drivers from android-sdk, but nothing helped. When I type a command "adb devices" to a command line, it says: "List of devices attached >emtpy line<". When I connect the phone to the PC, it doesn't even try to look for drivers anymore. I tried deleting them (drivers), placing there some new, but again - nothing helped. If anyone can provide any help, I'd be very, very, very glad.
Thanks in advance.
//edit: Nevermind, I made my phone alive again. I just had to use mfastboot tools. Moderators can close or delete this thread, please. I'm sorry for creating it, since it was kinda useless.
temme how to recover the system folder. i have a system folder on my desktop. help me. my phone isnt turing on
If you can get into fastboot and recover you can restore your phone. You just need a complete ROM, and restore it with mfastboot method.
It doesn't matter if you wiped system, you can do that in TWRP, if you reboot it won't boot into the OS (obviously) but go into fastboot mode.
Download mfastboot, a ROM image, and go through the command lines. There is a FAQ on how to restore.
felmaster said:
Hello there.
My phone is in a state which is widely being reffered to as "bricked". After hours of reading through hundreds of forums and trying out everything possible/impossible, I came to this - I'm posting here, and desperately asking you guys for help.
I have Moto G XT1032. I converted it to GPE, to install a 5.0.1 ROM few months ago. I used it without any problems. However, today I decided to try out the stock 5.0.2 ROM. But I read that I'll have to change my Data partition to F2FS (from EXT4). I did that (using TWRP v2.8.5.0), and then I did this terrible mistake: I decided to do a clean install, so I wiped everything. I wiped System, and Internal storage as well. Yes, I know that I'm stupid.
Now my phone is stuck at my custom recovery (TWRP) or at bootloader. I can switch between these two, but I can't boot to the system, because I don't have any system installed (because I wiped the /system partition - what an Einstein I am -_-). I thought that it would be easy - I just have to somehow push the zip file of the new ROM to my phone, and then install it from TWRP. The thing is - I can't transfer any files to the phone. I'm probably missing some drivers, but the problem is, that the phone doesn't have any operating system installed (besides bootloader, I guess) - so I can't get any drivers working. My PC is running Windows 7 64bit.
I tried installing Motorola Device Manager, I tried using the drivers from android-sdk, but nothing helped. When I type a command "adb devices" to a command line, it says: "List of devices attached >emtpy line<". When I connect the phone to the PC, it doesn't even try to look for drivers anymore. I tried deleting them (drivers), placing there some new, but again - nothing helped. If anyone can provide any help, I'd be very, very, very glad.
Thanks in advance.
//edit: Nevermind, I made my phone alive again. I just had to use mfastboot tools. Moderators can close or delete this thread, please. I'm sorry for creating it, since it was kinda useless.
Click to expand...
Click to collapse
Also TWRP/CWM has support for adb, u just need to install the drivers manually. Then you can push whatever you want.
Of course you can try restoring stock as suggested above.
How did u fixed it? :/
As a last resort there is always OTG (this thing has OTG support right?). Life was so much simpler when you could just put your sd card into a card reader and put your zip on there. A quick google search makes me think its got support, but who knows
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.
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.