Related
I have a Wind Mobile Motorola XT720 and I was following this tutorial to install Dexter's Froyo for XT720:
youtube . com / watch?v=KvU1CptOe14
I was at the 10:40 mark when it prompted to wipe all the data. I was not ready to do that yet, so I skipped that step and proceeded to Reboot the device. Now, when the phone turns on, it goes to the Dexter's XT720 Froyo loading screen and it says loading for 5 seconds and then the screen goes black for a few seconds and then the loading screen pops up again. It stays like that forever. I need a way to get out of this. I can access the Boot Loader menu but thats about it.
hjutt said:
I have a Wind Mobile Motorola XT720 and I was following this tutorial to install Dexter's Froyo for XT720:
youtube . com / watch?v=KvU1CptOe14
I was at the 10:40 mark when it prompted to wipe all the data. I was not ready to do that yet, so I skipped that step and proceeded to Reboot the device. Now, when the phone turns on, it goes to the Dexter's XT720 Froyo loading screen and it says loading for 5 seconds and then the screen goes black for a few seconds and then the loading screen pops up again. It stays like that forever. I need a way to get out of this. I can access the Boot Loader menu but thats about it.
Click to expand...
Click to collapse
Hold the volume up while powering on, that should take you back to open recovery. From there you have to do a wipe data / factory reset.
I did that but it gives me a screen with a yellow Exclamation mark inside a white triangle with a picture of a phone in front
Edit: Well Open recovery popped up! Ill see if wiping the data fixes it.
EDIT 2: Thanks alot! worked like a charm!
hello, a few days ago I checked into this forum, just bought an XT720, and these days I've been reading about changing the ROM, and I need your help. I am a rookie with all this in adb and codes. Right now I have some doubts, I hope I can help and not cause inconvenience.
To change the ROM need my phone is in the following conditions
Factory Refurbished (yes or not)
Partitioned SD card (yes or not)
then do the following
1. root access
2. install OpenRecovery
3. Restart phone
4. Nandroid copy the folder to the root directory of the SD (which is the root directory?)
5. the SD mode is NOT part of Mass Storage space
6. OpenRecovery run
7. Installing a Recovery (how?)
8. Recovery Boot Press
9. Restore backup "stock22xxxx" (I guess it's a file that I have to download called Stock221v13-bugfix-1)
10. Clean factory reset
11. Restart
Doing all this, my phone already have 2.2.1 running Froyo
Another question I have is whether to funcioanr all applications, for example, gps, telephone, 3g, HDMI, cameras, sensor, etc.
my phone details are as follows:
Version S / W STR_U2_01.1E.0
Firmaware version of the 2.1-update 1
GAS_ASIA_USAS config firmware version and various numbers
Kernel version 2.6.29-omap1
be compatible with this ROM?
I have to make some modifications to ADB codes?
Thank you all and sorry for so many questions
Greetings from Guatemala
(Google Translate)
Someone can confirm me?
no need to partition the sd card
just watch the tutorial video
http://forum.xda-developers.com/showthread.php?t=943368
Factory Refurbished -Yes
Partitioned SD card - it's not necessary unless you want to use the apps2ext feature
then do the following
1. root access
2. install OpenRecovery
3. Restart phone
4. Nandroid copy the folder to the root directory of the SD (which is the root directory?) the top directory of the sdcard
5. the SD mode is NOT part of Mass Storage space
6. OpenRecovery run
7. Installing a Recovery (how?) Run the install option in the System Recovery app
8. Recovery Boot Press - Another option in the System Recovery app
9. Restore backup "stock22xxxx" (I guess it's a file that I have to download called Stock221v13-bugfix-1) - If in step 4 you if you copied the Nandroid folder to your sdcard this is the option you'll see in Nandroid >> Restore
10. Clean factory reset
11. Restart
Doing all this, my phone already have 2.2.1 running Froyo
Another question I have is whether to funcioanr all applications, for example, gps, telephone, 3g, HDMI, cameras, sensor, etc. - I believe the only two (minor) issues are that the gallery button (next to the shutter release) doesn't work & the volume buttons don't function in the FM Radio.
Thanks! will initiate the changes, I think the volume buttons on the radio does not matter, I've never used, the gallery button does not matter.
One more question, sorry for so much trouble, you can make a nandroid bacukp my original ROM 2.1 and if something fails or was not happy, I can return to the original eclair 2.1?
Tavinsky said:
Thanks! will initiate the changes, I think the volume buttons on the radio does not matter, I've never used, the gallery button does not matter.
One more question, sorry for so much trouble, you can make a nandroid bacukp my original ROM 2.1 and if something fails or was not happy, I can return to the original eclair 2.1?
Click to expand...
Click to collapse
Yes. When you go into Nandroid >> Backup you'll want to select all the partitions except Baseband, Bootloader, Logo & Device Tree & then backup selective.
Yes. When you go into Nandroid >> Backup you'll want to select all the partitions except Baseband, Bootloader, Logo & Device Tree & then backup selective.
Click to expand...
Click to collapse
ok, Thanks for the help, already done. In theory it means that I have saved my Eclair 2.1 ROM if I wanted to return to it?
After backing up nandroid gave me the following message:
cdrom: Generating MD5 ... done
ext2: skiping
Now I have a question, do I have to uncheck Baseband, Bootloader, Logo & Device Tree.
Greetings!
Friends Thanks for your help! Already installed Dexter's ROM V 1.3, I will start with its use and I will be discussing. It really is not difficult, it is the first time I do something similar, but with the help of you and what I've read in the forum and the tutorials I was not complicated.
Greetings!
Yes. When you go into Nandroid >> Backup you'll want to select all the partitions except Baseband, Bootloader, Logo & Device Tree & then backup selective.
Click to expand...
Click to collapse
Why should not make these choices? could someone help me? I am about to upgrade to the second patch for the Rom of Dexter's v.1.3, stock221v13-bugfix-2_signed http://forum.xda-developers.com/showthread.php?p=12152371 # post12152371 , and I want to nandroid back if something does not work, in order to restore the phone after the first installation of the ROM v.1.3
Tavinsky said:
Why should not make these choices? could someone help me? I am about to upgrade to the second patch for the Rom of Dexter's v.1.3, stock221v13-bugfix-2_signed http://forum.xda-developers.com/showthread.php?p=12152371 # post12152371 , and I want to nandroid back if something does not work, in order to restore the phone after the first installation of the ROM v.1.3
Click to expand...
Click to collapse
Open Recovery will error out on those partitions. I haven't had any problems restoring a nandroid with out them.
Sent from my XT720 using XDA Premium App
Open Recovery will error out on those partitions. I haven't had any problems restoring a nandroid with out them.
Click to expand...
Click to collapse
Thanks! I encourage her to do this backup, update with the second patch, and hopefully not have problems.
Initial phone stats: DS Mod 1.55.531.3, hboot 1.45.0013, s-on/unlocked via HTC unlocker.
I'm trying to update my own phone to 1.63.531.2 via the PG59IMG.zip file found here, http://forum.xda-developers.com/showpost.php?p=17424340&postcount=24 , but I'm running into problems applying this update and keeping it after restoring a Nandroid backup. It would be a huge amount of work to set up my phone from square one, and I'd like to avoid the process if at all possible.
The steps I've followed (twice, now, with no joy) are the following:
* apply the update through the PG59IMG.zip
* flash CWM 5.0.2.7
* flash Superuser
* restore most recent Nandroid backup
* flash 1.63.531.2 boot image (for wi-fi fix)
And this puts me back at my starting point, with the 1.63.531.2 update not applied.
I know I'm going about this the wrong way, but I can't figure out the correct method to make this work. The fact that I flashed the DS Mod 1.55.531.3 ROM back after unlocking might have something to do with this, however, I just can't nail down why. Really could some help to make this work.
TIA for any suggestions --
--
KingCheetah
hey, real quick, after flashing the 1.63.531.2 update, instead of restoring your full nandoid of 1.55.531.3, go to 'advanced restore', choose that nandroid, and choose only 'restore data'. that will put all your apps and data onto the new update, rather than flashing you all the way back to what you had before.
you could also backup and restore your data with an app called Mybackup Root, or some people use Titanium Backup. I personally like using the advanced data restore in CWM, or else Mybackup.
Yogi, I thought your suggestion would be a smoking gun. However, I'm having the same problem as described in this thread: http://forum.xda-developers.com/showthread.php?p=25431819#post25431819
Might you have any suggestions for addressing the md5 problem? I'm coming up empty...
Thanks for your help --
--
KingChetah
yeah, come to think of it, I've had that problem before as well. did you try what xmc suggested? also, perhaps try the Modaco 4.0.0.9 version of CWM to do the advanced data restore... if my memory serves me, I have had more success overall with that version. unfortunately that's about all I got!
the other sugestion would be to flash your full nandroid, then use Mybackup Root to back everything up. then after updating, DL the app again and restore.
good luck and keep us posted!
yogi2010 said:
yeah, come to think of it, I've had that problem before as well. did you try what xmc suggested?
Click to expand...
Click to collapse
Yes, and for the backup I want to restore, all the md5s are the same between the files and what is listed in the nandroid.md5 file. So, the method XMC suggested really doesn't do anything.
yogi2010 said:
also, perhaps try the Modaco 4.0.0.9 version of CWM to do the advanced data restore... if my memory serves me, I have had more success overall with that version. unfortunately that's about all I got!
Click to expand...
Click to collapse
Hmm, okay, I'll give that a try. Weird that CWM 5.0.2.7 has this problem. Also frustrating.
yogi2010 said:
the other sugestion would be to flash your full nandroid, then use Mybackup Root to back everything up. then after updating, DL the app again and restore.
Click to expand...
Click to collapse
I'll keep this as the last resort, because I'd rather not have to download an app for just this purpose. Nandroid backups have served me fine so far. Call me a minimalist.
I'll try Modaco and see what happens. Thanks much for the idea to try.
--
King Cheetah
Sadness
Using Modaco didn't work. Although the Advanced Restore sees the file and appears to run successfully, it says it can't find a data.img file and an Android.img file, so it doesn't restore the info.
So, I guess it's down to trying Mybackup Root and see what happens. Getting tired of redoing this process over and over.
Why can't things "just work" in these situations?
--
KingCheetah
check the other thread....problems with restoring backup
---------- Post added at 05:11 PM ---------- Previous post was at 05:08 PM ----------
or actually...just flash the data.img through fastboot....its ten times easier
but the data.img in the same directory as adb and fastboot....then run the two commands with your phone in the bootloader
fastboot erase data
fastboot flash data data.img
xmc wildchild22 said:
or actually...just flash the data.img through fastboot....its ten times easier
but the data.img in the same directory as adb and fastboot....then run the two commands with your phone in the bootloader
fastboot erase data
fastboot flash data data.img
Click to expand...
Click to collapse
The problem with this is the file "data.img" doesn't exist in a Nandroid backup. As I stated in my previous message, the Advanced Restore process tossed up a message that the file didn't exist (which is correct).
The files within a given Nandroid backup folder are the following:
.android_secure.vfat.tar
boot.img
cache.ext4.tar
data.ext4.tar
nandroid.md5
recovery.img
system.ext4.tar
From the Advanced Restore problem thread (http://forum.xda-developers.com/showthread.php?t=1624319):
xmc wildchild22 said:
then take the system.img from the 1.63 update and put in replace of the nandroids one....then redo the md5 checksum for the system.img like i had showed before
Click to expand...
Click to collapse
I would love to try this, but since the 1.63 update is a PM59IMG.zip, I can't open it with a zip file manager--it throws up a "central directory not found" error. Unless there's another program besides 7zip that's needed to handle this type of zip file...
Edit: I just realized that, as you can see from the file list above, a Nandroid backup also doesn't have a "system.img" file--it has a "system.ext4.tar," but not "system.img." So being able to pull anything from a PM59IMG.zip file is a moot point at this juncture.
Banging one's head against the keyboard does little constructive good, but it's really tempting at this point --
--
KingCheetah
just try opening it with a plain windows explorer
xmc wildchild22 said:
just try opening it with a plain windows explorer
Click to expand...
Click to collapse
Using the "Explore" option from the right-click context menu in Windows Explorer gives the following error: "The Compressed (zipped) Folder is invalid or corrupted." (Since archive files on my laptop are associated with 7zip, this is the only method by which I can access Win XP's native archive file handling.)
This has been the case with all PM59IMG.zip files--they don't register as normal zip files.
Thanks for the suggestion, though --
--
KingCheetah
hmm...maybe tht zip is corrupted because it works for me....DL this --> http://tinyw.in/Mzg2
Nope, not corrupted because it works just fine to update my phone to 1.63 (as stated before, I've done this twice now). Also, that's the exact same source from whence I downloaded my copy of the file. The PM59MG.zip for 1.55.531.3 gives exactly the same error, and I used that without difficulty as well.
KingCheetah said:
Nope, not corrupted because it works just fine to update my phone to 1.63 (as stated before, I've done this twice now). Also, that's the exact same source from whence I downloaded my copy of the file. The PM59MG.zip for 1.55.531.3 gives exactly the same error, and I used that without difficulty as well.
Click to expand...
Click to collapse
Use winrar to open the PG59IMG.zip files - that's what I used to make all the custom ones with, and also what I used to open the leaked ones we started from.
You won't be able to edit existing leaked ones, because they are locked and have an HTC signature.
Sent from a digital distance.
Thanks for the pointer, Blue, and I'll keep this in mind. But as I added to my previous post (#8), I realized that a Nandroid backup doesn't have a "system.img" file--it has a "system.ext4.tar," but not "system.img." So being able to pull anything from a PM59IMG.zip file is a moot point at this juncture.
I think I'm going to have to wait for a 1.63 ROM that can be installed through CWM rather than the PM59IMG.zip method. The DS Mod 1.55.531.3 worked well for me, and all apps/data were just there after I flashed it. Maybe I just got lucky with the process I followed previously, who knows? (http://forum.xda-developers.com/showthread.php?t=1508406&page=4 post #39)
At any rate, I've got a truly mean headache from working on this all day. Time for a break with a bit of ice on ye old cervical vertebrae.
Thanks again for chiming in --
--
KingCheetah
No prob, didn't read through and shot from the hip on the last post I saw, out at dinner and skimming the forums on smoke breaks
Sent from a digital distance.
does anyone know the deal with the implementation of tar backups? I think that came into play at some point, and I wonder if that has anything to do with anything.
I just checked a backup I made with the Modaco CWM, and the files in it are all .img files, including data. and I know for a fact I have done backups and advanced data restores with that recovery. it would be a hassle, but if you get re-energized you might make the backup and do the restore with Modaco. definitely would be a hassle if it didn't work, but you could also make a backup with Mybackup, and have that ready too, as well as probably have a data.img to try and flash thru fastboot like xmc suggested.
anyway, hopefully we'll get this all sorted out. take it easy!
well .tar are used ever since cwm started working with ext4....maybe imgs are only ext3 or lower or its just inefficient
On that note, I did use the modaco 4.0.0.9 recovery to make the nandroids I pulled the system images from to get the bases from which I de-odexed, and when finished I uploaded to my host and they are the de-odexed bases I posted in dev.
I am pretty sure I went with modaco recovery for that because cwm 5.0.2.7 output tar files and it just saved a step in the process.
If you are working with the .tar files then jump on linux to unarchive them if that's what you are trying to do.
I just ran the deodex process using windows, because the first working deodex tool I found was a windows tool.
Generally I use modaco .9 for nandroids I want to work with in windows, and cwm 5 for nandroids I want to work with in linux.
We're probably leaving the restaurant soon, if we split up I'll actually read back through the thread when I get home and see if I have anything else to add.
Sent from a digital distance.
Yogi, you're brilliant!
yogi2010 said:
I just checked a backup I made with the Modaco CWM, and the files in it are all .img files, including data. and I know for a fact I have done backups and advanced data restores with that recovery.
Click to expand...
Click to collapse
[facepalm] Of course! This is why my Advanced Restore attempt with Modaco failed--because I used the CWM 5.0.2.7 backup, which did not have the files Modaco would have referenced. Duh! I wasn't even thinking along the lines of a file type mismatch between the two recoveries. Baka baka baka...
yogi2010 said:
it would be a hassle, but if you get re-energized you might make the backup and do the restore with Modaco. definitely would be a hassle if it didn't work, but you could also make a backup with Mybackup, and have that ready too, as well as probably have a data.img to try and flash thru fastboot like xmc suggested.
Click to expand...
Click to collapse
At this point, not a hassle, but the best chance to accomplish this thing with a minimum of fuss and bother. I'll give this a shot right after a bit 'o java. Thank you, Yogi, for highlighting something that should have been obvious to me when Modaco gave the error message that "data.img" didn't exist. Oy!
However, this still leaves unanswered the question of why CWM 5.0.2.7 is tossing up the md5 mismatch error when one tries to use Advance Restore, and that files aren't seen by CWM via Advance Restore until one accesses regular Restore. Paperskye is having the exact same problem in this thread: http://forum.xda-developers.com/showthread.php?t=1624319 . Should this be brought to the attention of the CWM devs? It really seems like a rather show-stopping error for CWM...unless Advanced Restore isn't really used with 5.0.2.7 and the MT4GS. There just doesn't seem to be a good reason for the observed behavior.
Many thanks for your encouragement. I'll report back with results on the next try with Modaco --
--
KingCheetah
It's a beautiful thing!
Using Modaco for my backup prior to the update, then Advanced Restore of data afterward = perfect restore of my phone environment with 1.63 on board. Done with as little fuss as I was hoping to encounter. Yogi, you get the prize. The only thing I had to manually put back was my custom boot animation, but that's trivial.
I think I'll just leave Modaco on as my recovery for now, since AR is functional with it and CWM 5.0.2.7 is not. Makes me wonder, from just an everyday backup standpoint, is there any real advantage of CWM over Modaco? I wish there was more information on how the recovery module functions on the CWM website--I'd like to read up on it for educational purposes. Guess I'll do a Google to find more.
So ridiculously happy right now. In a stew of things going wrong, at least something went right.
Big rumbling purr of gratitude --
--
KingCheetah
What is it? Because I want to download the mokeeOS, but the installation is confusing me, so I wanna know if the efs matters
Sent from my SGH-T959V using XDA
1. Yes efs matters a lot
2. I don't know a whole lot but it holds the network info, imei number, and alot of other really important things
Sent from my SGH-T959V using xda premium
Although there is a way to make sure you have a backup, flash this file in cwm
sourceforge.net/projects/teamacid/files/fb/cwm/cm7-efs-backup.zip/download
And there will be two files in the root of your sd card
Efs-backup.tar and efs-backup.tar.md5 ( I suggest save it to your computer, it saved my ass )
And you can restore this backup at anytime by flashing this
sourceforge.net/projects/teamacid/files/fb/cwm/cm7-efs-restore.zip/download
Good luck
Sent from my SGH-T959V using xda premium
Efs is the files system that holds the unique identifiers for your device. Without it, your phone is basically useless. You won't be able to connect to any network properly do things like phone calls, internet, texting, are all degraded, if they even work at all... Make sure you know what you are doing before messing with it. Fb created a vet good guide on the wiki. Follow it to a T!
Sent from my SGH-T959V using XDA
I would suggest using a root browser to copy the EFS folder to somewhere safe on your PC and copy a 2nd back-up to your SD card. I lost IMEI going from CM7 to moKeeOS but was able to easliy restore it with a back-up and a root browser.
The flashable EFS back-up/restore from FB should still be used, but with EFS/IMEI I don't think you can be too careful and backing it up manually as previously stated is a good idea.
Yeah, I keep multiple copies of it on my PC. The reason being is that I copy it whenever I do a backup before a flash. So I have a directory with the date with 3 folders: efs, nandroid, and sdcard. I used adb to copy them:
Code:
cd efs
adb pull /efs/
Probably overkill, but better to be safe than sorry, eh?
Ok, but once you lose IMEI and don't have a backup (I received this phone for repair), then what can I do?
serialteg said:
Ok, but once you lose IMEI and don't have a backup (I received this phone for repair), then what can I do?
Click to expand...
Click to collapse
It's pretty much screwed without the OEM Samsung/Tmo software. You would have to send it to Samsung for repair, or you might get lucky and get an engineer to hook you up, but that is unlikely...
thomas.raines said:
It's pretty much screwed without the OEM Samsung/Tmo software. You would have to send it to Samsung for repair, or you might get lucky and get an engineer to hook you up, but that is unlikely...
Click to expand...
Click to collapse
thanks for the answer. that OEM software isn't available in the forums or anywhere else for us? because I swear I flashed something OEM'ish without root with heimdall.
also, the imei is on the battery part of the phone, can't i fix it?
i read somewhere that you could use a phone just fine without imei on the about phone.
you can use the phone without imei, but it doesn't function as well as it would with it. Also, i was using titanium backup and it said my device's id was changed, and it showed my actual imei. If i were to restore it, would that fix the imei?
EFS help on the SGH-T959V
Basically, I've had a hell of a time with some EFS drama this weekend, made a total noob mistake, but in a stroke of luck I was able to "recover" so to speak my EFS even after it was supposedly "wiped."
After some thorough research and READING and bit of thought, I realized that the PIT mapping layouts between BML and MTD are indeed different, and that in theory if one remaps to BML (in layman's terms a stock partition map) then the EFS data originally on the phone gets correctly remapped (at least in my case it did).
To reiterate:
1. I did a nandroid backup. Basic ****. I hope to god you at least did this step too.
2. I used the cm7-efs-backup.zip script to backup my EFS. This was my first mistake. In my case, I don't know why I'm still researching, this script failed to make a backup .tar on my sdcard or anywhere else for that matter. It didn't throw any error messages either on the screen in the process. Not trying to attack the authors of that script, I'm just saying it didn't work for me this time.
3. I pushed the TWRP boot.img with Heimdall
4. I used the cm7-efs-restore.zip script which also "succeeded" but did nothing to restore any sort of EFS obviously because there was no backup to begin with.
5. I flashed R11 unofficial cm7 and booted up. Everything was fine but the IMEI was corrupted and I confirmed that the new MTD EFS partition was empty. On T-Mobile I could place no calls and only got sporadic and intermittent data access.
It was at this point I was sure I had ruined my phone.
After some more careful reading I realized that the original EFS was still present on the firmware, however the new MTD layout I flashed (wisely) stores its EFS partition in a different physical location. In theory, I thought if I reverted to BML and a stock ROM then I would recover the original EFS. In my case, this was successful.
1. I accessed the most recent "boot.img" file from my most recent nandroid and pushed that back to the device with Heimdall
2. At this point you have to flip your USB drivers back to USB Composite Device.
3. I then used a Heimdall one click to return to a rooted stock KJ6 "Gremlin Remover"
4. Upon restart, everything was fine (sigh of relief)
At this point, I'm still trying to determine why my EFS cannot be backed up with a few automatic tools. I made a backup of the file structure, but even lyriquidperfection's EFS Pro 1.4.7 can't make a backup of the EFS. It can access the ADB Server, but the backup 'fails'.
I'll check back in after I figure out why.
Hopefully this info will help anyone else who has switched to MTD and has a missing EFS.
nick.tansy said:
At this point, I'm still trying to determine why my EFS cannot be backed up with a few automatic tools. I made a backup of the file structure, but even lyriquidperfection's EFS Pro 1.4.7 can't make a backup of the EFS. It can access the ADB Server, but the backup 'fails'.
I'll check back in after I figure out why.
Hopefully this info will help anyone else who has switched to MTD and has a missing EFS.
Click to expand...
Click to collapse
I had similar issues yesterday. If your trying to install the twrp and then downgrade to the version with wifi dont flash the boot.img with heimdall. Follow the instructions for installing via cwm.
Just install the zip that has twrp in it. But follow the directions for normal cwm installation.
Also when trying to make a backup of your efs, make sure system is mounted. I initially did not have any problem but I was on antonx's kernel and when you flash with that recovery it would mount properly. What is happening is system isnt getting mounted. So its making a null backup.
The most important thing to do is when you are trying to make a backup of your efs is mount system!
Hi have you tried the updated EFS Pro v1.7.13? It can now automatically detect the mount point of the '/efs' folder for back up and restore. Also many many bug fixes and new code to communicate with adb.exe alot more quickly and efficiently.
Head over to the forum and check it out.
I already solved this problem, but this would seem useful other people with the same problem. But what forums are you exactly referring to?
Sent from my SGH-T959V using XDA
mierkat09 said:
I already solved this problem, but this would seem useful other people with the same problem. But what forums are you exactly referring to?
Sent from my SGH-T959V using XDA
Click to expand...
Click to collapse
This one.
http://forum.xda-developers.com/showthread.php?p=18524176
Hi,
i will receive n5 in few days and want to know is there any good practices to start with.
I've read stickies and i don't mean that type of stuff, i mean something like backing up:
- all partitions (http://forum.xda-developers.com/showthread.php?t=2517503)
- backing other things like /efs (i see it can be done via TWRP : http://www.droidviews.com/how-to-backup-and-restore-efs-data-on-nexus-5/ , but what about other partitions?)
- complete NV backup?
Also should i backup these things after first boot, or that doesn't matter? (for ex. usage of stock rom for few days)
Thanks in advance
Not sure what you want to back up on a new device but what I did was put a custom recovery on and then made a nandroid of it while it was new. I also backed up the efs in twrp and stored it off the device. That'll pretty much cover everything
With the exception of the /efs I don't see any reason to back up anything, especially at first boot.
Google provides full factory images for each release. https://developers.google.com/android/nexus/images#hammerhead
Thanks for comments :highfive:
El Daddy said:
With the exception of the /efs I don't see any reason to back up anything, especially at first boot.
Google provides full factory images for each release. https://developers.google.com/android/nexus/images#hammerhead
Click to expand...
Click to collapse
Agreed.
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.