Related
I've been at this for a few weeks, and its bugging me.
I've been looking up on how to build/port ROMs for the Milestone (A853), and there is almost nothing that points me in the right direction. I want to be able to install it via OR's update menu.
This is what I've done so far:
Gotten, and set up HTC Android Kitchen by dsixda.
Downloaded the rom I want to port.
Extracted the rom system and boot images.
Replaced the boot.img-kernel with a stock Milestone boot.img-kernel taken from a nandroid backup. (I know all about the locked bootloader)
Rebuilt the kernel
Modified the build.props
Rebuilt the *.zip
Copied to Open Recovery/updates
Applied update.
So here's where it gets sticky. According to the output, the ROM installs fine. No errors nothing. However, after the first reboot, it goes directly to the bootloader screen with an error of: a5,69,4E,00,23 or something like that.
I'm royally stumped and would really like to get this going in the same way CM or Crono's is installed. Any ideas or advice would be GREATLY appreciated.
dynamite1985 said:
I've been at this for a few weeks, and its bugging me.
I've been looking up on how to build/port ROMs for the Milestone (A853), and there is almost nothing that points me in the right direction. I want to be able to install it via OR's update menu.
This is what I've done so far:
Gotten, and set up HTC Android Kitchen by dsixda.
Downloaded the rom I want to port.
Extracted the rom system and boot images.
Replaced the boot.img-kernel with a stock Milestone boot.img-kernel taken from a nandroid backup. (I know all about the locked bootloader)
Rebuilt the kernel
Modified the build.props
Rebuilt the *.zip
Copied to Open Recovery/updates
Applied update.
So here's where it gets sticky. According to the output, the ROM installs fine. No errors nothing. However, after the first reboot, it goes directly to the bootloader screen with an error of: a5,69,4E,00,23 or something like that.
I'm royally stumped and would really like to get this going in the same way CM or Crono's is installed. Any ideas or advice would be GREATLY appreciated.
Click to expand...
Click to collapse
Is that meant to work for the milestone? I dont see milestone listed on supported devices.
Is this the kitchen you are referring to?
ya thats the one i was referring to.
I know its not supported, but I was looking at the outputs of the zips it creates, and comparing them to some ROMs out there (notably CM6.1 and Cronos) and they are pretty much the same. The only thing that I have noticed thats different is that the Milestone doesn't use the updater-script that this particular kitchen generates. So, if I pretty much leave the updater-script alone, it will install, up until I reboot, and I get the error code I mentioned before.
If I let the kitchen generate the updater-script, the installation aborts, usually with a 'Status 4' or 'Status 7' error.
dynamite1985 said:
ya thats the one i was referring to.
I know its not supported, but I was looking at the outputs of the zips it creates, and comparing them to some ROMs out there (notably CM6.1 and Cronos) and they are pretty much the same. The only thing that I have noticed thats different is that the Milestone doesn't use the updater-script that this particular kitchen generates. So, if I pretty much leave the updater-script alone, it will install, up until I reboot, and I get the error code I mentioned before.
If I let the kitchen generate the updater-script, the installation aborts, usually with a 'Status 4' or 'Status 7' error.
Click to expand...
Click to collapse
Sorry buddy. I ain't a developer. Try sending a PM to Luca or Kabaldan or Feeyo ( on cronosproject ) and see if they can help.
The boot.img contains kernel and rootfs with init and its scripts. Nothing in it can be directly changed if you want the Milestone to be able to boot.
The kitchen obviously rebuilds the boot.img - err a5,69,4E,00,23 means that the boot.img signature check failed.
You can't do this on Milestone - that's why the sh-hijack + 2nd-init are used in custom compiled ROMs for Milestone to be able to use customized init scripts.
kabaldan said:
The boot.img contains kernel and rootfs with init and its scripts. Nothing in it can be directly changed if you want the Milestone to be able to boot.
The kitchen obviously rebuilds the boot.img - err a5,69,4E,00,23 means that the boot.img signature check failed.
You can't do this on Milestone - that's why the sh-hijack + 2nd-init are used in custom compiled ROMs for Milestone to be able to use customized init scripts.
Click to expand...
Click to collapse
so I'm a little confused...
it seems to me that I should be compiling the kernal with the 2nd-init attack, which confuses me because of the BL issue. or is the stock boot.img used with a customized system.img?
i've tried the latter part, and gotten the noted error.
Hello my name is P3Droid,
We (TBH) have a lot of experience in Motorola phones and hacking. This experience dates back to the Razr days.
Here is a word of caution. Do no delete apps from the System partition, I would suggest you only rename them to .bak. When Motorola pushes updates each of the files undergoes a hash check, if the file has been manipulated or is missing the entire update will fail.
Until a system only sbf or similar is released, unless you make a back up with bootstrap and recovery, you will eliminate your ability to take updates moving forward.
You can remove many of the stock apps without rooting just by using the built in app manager.
Those apps are in /data it is the apps that are in /system that count.
jimmydafish said:
Hello my name is P3Droid,
We (TBH) has a lot of experience in Motorola phones and hacking. The experience dates back to the Razr days.
Here is a word of caution. Do no delete apps from the System partition, I would suggest you only rename them to .bak. When Motorola pushes updates each of the files undergoes a hash check, if the file has been manipulated or is missing the entire update will fail.
Until a system only sbf or similar is released, unless you make a back up with bootstrap and recovery, you will eliminate your ability to take updates moving forward.
Click to expand...
Click to collapse
i take it that all the apps you can delete through app manager are on /data therefore are safe to delete right?
This should definitely be sticky'd.
franciscojavierleon said:
i take it that all the apps you can delete through app manager are on /data therefore are safe to delete right?
Click to expand...
Click to collapse
Yes anything that you can delete through the application manager is okay to remove, those have no impact on the update process.
And to complete my thought above. When an update is released, and they are coming, then you need to just change the file names back to normal to take the update.
Sound to me like we ned an ap that lets toys select programs to rename and then can change then back when needed. Would make it alot easier. Ill look onto this...also if some one else can confirm this info I might stick it.
Sent from my MB860 using XDA App
I can confirm that what p3droid is saying is true for all recent Motorola devices, but the point is really that you won't know until an OTA update is released how they have written the updater script in the zip file.
We have been through this with releases for every phone since the Droid X and many people got caught out by it and were stuck until we released SBF files that could safely restore the stock configuration and allow updating to official release versions.
This brings up another important point about modding your phone at this stage in the cycle. Without a full SBF to recover with in the event of a problem that renders the phone unbootable or unable to access recovery, or if you haven't made a complete nandroid, you will be again be stuck and have to return your phone to AT&T/Motorola for warranty replacement. This is never good for anyone.
When we mod our phones against the wishes of the carriers and manufacturers, we should really take responsibility for those actions and not produce a mountain of bricked phones whose cost is passed along to everyone in the form of higher ETFs for smartphones and other ways.
So, until a full SBF is released of the current build, people should be very careful what they change or remove from their phone's system and/or NVM and radio.
I also tried to warn users about this in another thread that was locked before p3droid started this thread. We have watched hundreds or even thousands of users destroy their phones in myriad ways and helped many of them recover them by providing SBF files as a safety net. It's not fun and if it can be avoided it is to everyone's benefit to do so and only requires care and forethought.
Is there anyway we could make a backup of this partition for later use? would each user need to make one or would one for all users suffice?
Assuming a bootstrapped custom recovery is possible, and we know Koush is already working on it, then a nandroid backup of at least the system, userdata and cache partitions would be the first and best step to take. Also assuming that the bootloader is locked/signed and true recovery is not possible, then the boot image and kernel will not be able to be backed up or written to by the bootstrapped recovery. It is always best to make your own backup for your device and store it on the sdcard where you have easy access, but users have also been able to use someone else's nandroid backup to restore their device in many cases as well. The recovery will give you the option to restore each partition separately in the advanced options so that you won't be restoring someone else's data to your phone.
We at TBH have also been able to create our own update.zip files and SBF files to help users recover from various mishaps.
This was because we had access to both official and unofficial files and tools to accomplish those things.
We have no idea if that will be the case here and we will not likely have the device ourselves to work with given we are VZW users primarily.
Again, there are many variables here that are yet to be determined and modes of access to the various partitions and radio baseband will be different with this phone as opposed to previous Qualcomm chipset devices.
All of this means that at this stage extreme caution is advised and being overzealous with root access is very dangerous right now.
I suggest everyone that is rooted use TITANIUM BACKUP to deal with their bloatware issues. The pro version, which you will need, is only a few bucks and is worth it. TB allows you to 'freeze' bloatware apps, which to my knowledge just blocks it fro the system, but does not delete it. The apps you choose to freeze are also removed from the app tray - so no more clutter. This way when an update rolls around, you can run down the list and simply touch 'thaw' to bring those apps back to recognition. This seems like a much more efficient and easy way to go back and forth, rather than renaming the .apk's.
I apologize if someone already mentioned TB in this thread - I just skimmed quickly.
I deleted all the bloat apps using the app manager without root. They were gone!
I did a factory reset on the phone and *surprise* the apps were back!
The things that were not part of the system come back during reset. On the other hand, im ****ed because I went crazy and deleted some actual apps that the system will check. Yay me.
pwndrone said:
The things that were not part of the system come back during reset. On the other hand, im ****ed because I went crazy and deleted some actual apps that the system will check. Yay me.
Click to expand...
Click to collapse
Ouch. Might not work, but have you tried a hard reset?
We should make a list of what's safe to remove like we did for the Captivate. Might be helpful.
I did a full factory reset and those apps that weren't part of the system came back but stuff like the help center are still missing.
Hopefully there will be a way to load the stock firmware sometime in the future.
Sent from my MB860 using XDA App
Would an app like "Autostarts" work in this case?
Guys, I can't emphasize this enough: use Titanium Backup to freeze the apps rather than deleting them, it will make your life much easier.
does this apply to using different font files as well? I'd like to use a ttf font that's a little larger than DroidSans. if i rename and use a different font will that impact OTA updates or anything else for that matter? thanks!
before reading about "freezing" apps, i reset my atrix back to factory settings. i need help rooting my atrix again. it keeps me in "Waiting for Device" where before i had no problem rooting. and another thing, when i had reset back to factory settings...i still have superuser installed. do i uninstall superuser in order to gain root access again?
I have not rooted yet. My question is can we use freeze to turn off BlurAccounts or is it fully baked into the Rom?
At last we have the 4.10.708.1 Sense 6.0 update for the HK version.
Unfortunately, this release appears to have some problems with the gallery and blinkfeed apps. For the best results, I recommend installing the previous version (3.06, linked below in this post) and applying the OTA update yourself.
Without further ado, here are the links!
Download link:
http://heh.sk/~johnny64/901S/dlxpul_stock_4.10.708.1_CL344680_release-keys.zip (MD5)
If you are S-ON, after installing the ROM, you also have to unpack boot.img from the zip and flash it using fastboot:
Code:
fastboot flash boot boot.img
Verified to install without a problem on an S-OFF phone using the recovery built by @kairi_zeroblade in this thread.
For each of the available OTA updates, you can also find the actual OTA package, the firmware included within and the stock recovery for that version. If you want to flash the whole firmware package (including recovery, radio, kernel/boot and many other things), just grab the appropriate firmware.zip, rename it to PO68IMG.zip, put it into the root of your external SD card and reboot your phone into the bootloader – the update will be applied automatically.
URL: http://heh.sk/~johnny64/901S/OTA/
Old versions below.
Here's the 3.06.708.3 KitKat 4.4.2 update.
Before installing, take a moment to read this. This update introduces extended filesystem capability flags and SELinux labels. The installer in this ZIP tries to set them in the same way as the OTA update does, but in TWRP this fails, because the recovery doesn't have support for these kinds of metadata. However, setting the medatada is done as the last step, so even if it fails and the installation aborts, the ROM is still installed properly, just without this extra bit.
I repeat:
Read the installer messages. If it says "Done!" and fails afterwards, the installation is complete. If it fails before printing the message "Done!", then the installation is not OK.
The latest CWM Touch should give the best results, although I haven't tried installing it through CWM.
If you are S-ON, after installing the ROM, you also have to unpack boot.img from the zip and flash it using fastboot:
Code:
fastboot flash boot boot.img
Download link:
http://heh.sk/~johnny64/901S/dlxpul_stock_3.06.708.3_CL315079_release-keys_SELinux.zip (MD5)
@Zarboz also made a ZIP of this version of the stock ROM, I'm told it contains some flavor of Superuser preinstalled:
https://drive.google.com/file/d/0B8I81hbg3bIwOWNlZHBMUy1tanc/edit?usp=sharing
-----------------------
Just before Christmas we have a new stock ROM with Android 4.3 and Sense 5.5 available. Same as with previous version, the installer contains all preload apps, in addition, it also contains the HTC Notes app, otherwise it leaves /data as it is, so in case something does not work, remember to wipe data before installing.
Download link:
http://heh.sk/~johnny64/901S/dlxpul_signed_stock_2.21.708.1_CL288207_release-keys.zip (MD5)
-----------------------
This is an image of the stock ROM after installing the 1.23.708.3 OTA update. The installer also contains all preload applications (Flashlight, Calculator, PDF viewer and others). Other than installing / updating all preload apps, the package doesn't touch /data in any other way. If you need to wipe your data partition, do it before installing this ROM, otherwise you'll wipe your freshly-installed preload applications. (Note that some of them have been updated in the OTA, which means they differ from the APKs I posted separately.) Does not contain the Notes OTA update, it should ask after first boot.
Here's the download link:
http://heh.sk/~johnny64/901S/dlxpul_signed_stock_1.23.708.3_CL241753_release-keys.zip (MD5)
-----------------------
Made from a dump taken from my 901S just after unlocking the bootloader, pure preinstalled stock ROM, no root, no mods of any kind. Only contains /system and kernel+initrd, doesn't touch /data, /cache or anything else. If you want a clean state, wipe your phone before or after installing.
Download:
http://heh.sk/~johnny64/901S/dlxpul_signed_stock_1.11.708.1_CL215607_release-keys.zip (MD5 here)
The ROM is also available as a TWRP backup:
http://heh.sk/~johnny64/901S/stock-901s-twrp-backup.tar (MD5 here)
For those interested, I also made a backup of the original internal storage ("sdcard") before unlocking which is available here (MD5). It should be pretty close to the original state, though I did run a few apps there to get a feeling of the device.
Last but not least, there were certain applications preinstalled in the /data partition which gets erased completely when unlocking. I managed to find out which ones they were and back up their APKs. The APKs are located at http://heh.sk/~johnny64/901S/preload/. To install them, create the directory /data/preload on your device and push the APKs in there using adb or something. The apps should appear after a reboot. Most of them are probably not very interesting (since they are for news from the HK area), I was mostly interested in the calculator, flashlight and PDF viewer, but I backed them all up anyway, so suit yourselves.
XDA:DevDB Information
Stock ROM, ROM for the HTC Butterfly S
Contributors
koniiiik
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Based On: Stock Sense 6
Version Information
Status: Stable
Current Stable Version: 4.10.708.1
Stable Release Date: 2014-07-08
Created 2014-07-08
Last Updated 2014-07-07
Thank You for posting this!! Worked perfectly!
Thanks bro
Sent from my HTC One using Tapatalk 4
Any one can help me please
http://forum.xda-developers.com/showpost.php?p=45074137&postcount=35
Solved by sending maxims Rom via sideload.....rgrds
Thanks for sharing it!
Thanks for sharing!!!
Sent from my HTC Butterfly s using XDA Premium 4 mobile app
hi please any help how to restore from this backup.....i already download this file and after that i put it as it is in the folder twrp\BACKUPS\
but when i try to restore from twrp i do not found the backup file to restore....
do i make any fault ......help me please
hasan_abeer said:
hi please any help how to restore from this backup.....i already download this file and after that i put it as it is in the folder twrp\BACKUPS\
but when i try to restore from twrp i do not found the backup file to restore....
do i make any fault ......help me please
Click to expand...
Click to collapse
Well, the file is a tar archive. You have to extract it into TWRP/BACKUPS/<your phone's serial number>. The backup itself consists of multiple files, I just made a single archive for easier downloading.
koniiiik said:
Well, the file is a tar archive. You have to extract it into TWRP/BACKUPS/<your phone's serial number>. The backup itself consists of multiple files, I just made a single archive for easier downloading.
Click to expand...
Click to collapse
thanks for answering
please do you mean by (your phone's serial number) is to rename file after extract bu my serial no?
hasan_abeer said:
thanks for answering
please do you mean by (your phone's serial number) is to rename file after extract bu my serial no?
Click to expand...
Click to collapse
I don't really understand your question, but I'll try again and slower this time. (-;
First, extract the archive on your phone, any decent file manager app should be able to do that. You'll notice the archive contains one directory named 2013-08-22--21-11-59. This directory contains a bunch of files.
Next, look up your phone's serial number in settings -> about -> phone identity. Navigate into TWRP/BACKUPS on your SD card and check if there's a directory with the same name as your serial number. If there's no such directory, create it.
Finally, move the 2013-08-22--21-11-59 directory into the one you just created.
koniiiik said:
I don't really understand your question, but I'll try again and slower this time. (-;
First, extract the archive on your phone, any decent file manager app should be able to do that. You'll notice the archive contains one directory named 2013-08-22--21-11-59. This directory contains a bunch of files.
Next, look up your phone's serial number in settings -> about -> phone identity. Navigate into TWRP/BACKUPS on your SD card and check if there's a directory with the same name as your serial number. If there's no such directory, create it.
Finally, move the 2013-08-22--21-11-59 directory into the one you just created.
Click to expand...
Click to collapse
please im now use maxims rom rooted one , do i need to re lock my phone then restore copy the adapted one as you mentioned above ?or i can restore it now as i am
hasan_abeer said:
please im now use maxims rom rooted one , do i need to re lock my phone then restore copy the adapted one as you mentioned above ?or i can restore it now as i am
Click to expand...
Click to collapse
You can just go ahead and restore the backup.
koniiiik said:
You can just go ahead and restore the backup.
Click to expand...
Click to collapse
but if when i restore over maxim rom i faced a system restore problem?
Okay, now I don't understand your question. Did you try to restore the backup and it failed with an error? If that's the case, then I'm afraid I won't be able to help you. Anyway, you might want to post the exact error message you're getting in case someone else would be able to help you out.
any idea how to backup stock recovery? im about to unlock my phone but not sure if I will be able to backup stock recovery.
shadow071506 said:
any idea how to backup stock recovery? im about to unlock my phone but not sure if I will be able to backup stock recovery.
Click to expand...
Click to collapse
Used search for "stock recovery" and found this thread. contact the OP to confirm it's the stock recovery for the Butterfly S.
Where is your backup hosted at? The download is taking a long ass time?!
Sent from my HTC Butterfly S using XDA Premium 4 mobile app
---------- Post added at 03:17 AM ---------- Previous post was at 03:08 AM ----------
Damn it! I cant get this file to download.
Sent from my HTC Butterfly S using XDA Premium 4 mobile app
zounduser said:
Where is your backup hosted at? The download is taking a long ass time?!
Sent from my HTC Butterfly S using XDA Premium 4 mobile app
---------- Post added at 03:17 AM ---------- Previous post was at 03:08 AM ----------
Damn it! I cant get this file to download.
Sent from my HTC Butterfly S using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It is hosted on a Raspberry Pi sitting on a shelf in my campus room. It should have 100 mbit connectivity. I noticed in the HTTP server logs that a lot of people are using downloaders which open more than 20 connections in parallel, some go even as high as 50. Since it is a really weak machine, I limited it to 5 parallel connections. If you're trying to download with such a tool, try to crank it down a little bit.
cortez.i said:
Used search for "stock recovery" and found this thread. contact the OP to confirm it's the stock recovery for the Butterfly S.
Click to expand...
Click to collapse
can anyone confirm if this is the correct stock recovery? just incase it is needed in the near future (probably OTA and stuff)
shadow071506 said:
can anyone confirm if this is the correct stock recovery? just incase it is needed in the near future (probably OTA and stuff)
Click to expand...
Click to collapse
this is my stock recovery... I got it after s-off in a specialized center.
Had some free time recently so finally got round to opening my OYUA and having a looksy.
ROMCleaner 3.5 works splendid with CWM and OUYA.
Why use it with the OUYA?
Its a fast and easy way to pre-install all your apps and games through a single zip flash in CWM.
No more sideloading Dropbox to download and install everytime you flash a new StockPlus or OTA, have them all ready and waiting for you upon the first boot of the ROM.
If your familiar with ROMCleaner on one of the many devices we ported it to, you'll feel right at home!
As certain design decisions were overlooked with the OUYA and it didt get the following it was expected, I didnt wont make a big deal aout the release but couldnt help playing about with to see what I could get working on it. It worked fine so here we are
Notes
More detaililed guides and instructions can be found in any of the device specific threads for ROMCleaner if you want to have a look at its features but for now Ill leave this little guide for us OUYA users.
I doubt there will be a Aroma version due to its reliance on touch input but will slowly be looking at going through the other individual tools we created before Patrics83 put the Aroma AIO toolkit together.
It starts at v3.5 as this was the last version before moving to Aroma and we kept that consistent across devices.
Any changes will only be visually to the updater-script and the default romcleaner.txt included in the zip as at its core, RC works. I will keep a dated chagelog for you though for any updates to the zip.
Basic Guide
Pre-Requisetes:ClockworkMod Recovery
On your on the root of /sdcard create a (case sensitive) folder structure as so:
Code:
/sdcard/ROMCleaner/FirstBoot/data/app/
/sdcard/ROMCleaner/FirstBoot/system/app/
Place any apks in these folders which you want installed after flashing in the relevent folders
After flashing the ROM, flash ROMCleaner 3.5.zip
Reboot as normal
First boot of the ROM will take extra time due to the apks being sorted by Android when its up and running you will find all the apps in the usual place all ready and waiting!
If you install another launcher I recommend loading OUYA Launcher first and following the setup (wifi, username etc) to get it all sorted before using your preferred launcher.
You can use RC to install other files such as bootanimation.zip (system/media/) as well and are not limited to just apks. I add TwitcyEye's KeyMap mod for example so the mapping is done with no copying files about.
It will set the correct permissions for all the files and folders so dont worry about that.
Cleaning
ROMCleaner has the ability to remove files from the system after the ROM has been flashed, but before first boot, using a text file in a simple user-friendly format.
The default list has not been optimized for OUYA and I have not got round to checking through it yet. I haven't noticed any thing important if it does but you have been warned Ill take a proper look when I get the time.
You have the ability to define a custom list for RC to use by creating a ROMCleaner_user.txt file in /sdcard/ROMCleaner/ and Ive attached a blank one with some detailed instructions on its layour and format. I recommend you use this file until I have time to cross reference the default list with the OUYA files to avoid anything being deleted.
All in all its an easy way to get your apps installed when flashing a ROM be it StockPlus or an official OTA. It requires no special access as its all done in recovery and uses its own busybox.
Anyway, Have a play and let me know how it works for you.
Like a lot of people on XDA I have very little free time these days due to my job and so-called life but will be keeping my eye on this thread and the OUYA in general
#probably for formatted guide
#just in case
Is ROMcleaner able to load any type of complete backups from Titanium Backup or Android Tuner? I'm sure the answer is on your site, but it is probably a question a lot of people will have.
Sent from my SCH-I535 using Tapatalk 4
TadeoNYC said:
Is ROMcleaner able to load any type of complete backups from Titanium Backup or Android Tuner? I'm sure the answer is on your site, but it is probably a question a lot of people will have.
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
Unfortunately thats a completely different thing. All this is done in recovery where as TB etc are app specific done while the OS is up and running.
RC installs (and can remove) the apps before the OS has loaded for the first time.
I have an "almost perfect" stock Nandroid build of 4.06.1540.3. Right now, I have not installed any of my own data, except for Contacts and preferences at the Google Play Store. I have also installed a custom recovery (TWRP 2.6.3.3) and rooted the device.
I think my previous backups may have contain corrupted data, as I got multiple error messages when trying to connect to Google and restore contacts. So, I went back to an earlier backup and restored from there. Everything is working now, and I don't want to "screw up"!
What I would like to learn how to do is to make a reliable - i.e. "no corrupted data"- stock backup with a stock recovery so that I may restore it if necessary. Also, would like to be able to take this Nandroid backup and save to a PC so that I can restore from it later.
Please tell me how to do this! Also, will I need to know how to save the file to the computer - as a zip file or as an image file. Right now, I don't know how to do either of those things! TWRP saves the backups as multiple archives rather than as a single zip file or image. Also, which is the preferable method to save the backup as - zip or image file? I would very much like to make this file available to the Developers on this forum as I know that they do not have this particular OTA Nandroid backup posted and I want to help them out! But I think that they would prefer the zip format of the file with the stock recovery.
Please advise! I would be most appreciative, truly!
gingerlindsey said:
I have an "almost perfect" stock Nandroid build of 4.06.1540.3. Right now, I have not installed any of my own data, except for Contacts and preferences at the Google Play Store. I have also installed a custom recovery (TWRP 2.6.3.3) and rooted the device.
I think my previous backups may have contain corrupted data, as I got multiple error messages when trying to connect to Google and restore contacts. So, I went back to an earlier backup and restored from there. Everything is working now, and I don't want to "screw up"!
how to do is to make a reliable - i.e. "no corrupted data"- stock backup with a stock recovery so that I may restore it if necessary. Also, would like to be able to take this Nandroid backup and save to a PC so that I can restore from it later.
Please tell me how to do this! Also, will I need to know how to save the file to the computer - as a zip file or as an image file. Right now, I don't know how to do either of those things! TWRP saves the backups as multiple archives rather than as a single zip file or image. Also, which is the preferable method to save the backup as - zip or image file? I would very much like to make this file available to the Developers on this forum as I know that they do not have this particular OTA Nandroid backup posted and I want to help them out! But I think that they would prefer the zip format of the file with the stock recovery.
Please advise! I would be most appreciative, truly!
Click to expand...
Click to collapse
your too late the developers already have it
InsertCoin 7.0-6 | Stable | Mods | Performance | Sense 5.5 | Android 4.4 | KUSTOMIZER 1.2.2 | 4.06.1540.3
The Next Chapter! v1.0[4.06.1540.3][APM][HEQS]
SkyDragon v 4.0 4.06.1540.3 ANDROID 4.4 KIT KAT-Live Support!-OTA-SDHUB
if you just want a copy of it for yourself for later just hook to the PC and copy it from TWRP/Backup/HTxxxxxxx/2013-12-xx to your PC
Thank you, very much for the reply, cisA! I really wanted to help out, here! As for backing it up to my computer, how do I save as a zip file? Recompile it into a single image from the multiple archived files and then zip it? Sorry, for being such a noob!