Related
- It has already been confirmed several times, the 2 files are EXACTLY the same (OTA and the 91.14mb file from samsung)
- Performing the update this way did not destroy any of my data, texts, applications, contacts, etc. Everything was exactly the same, except for the new version of Android. You must have a stock phone or the update most likely will not work.
Click to expand...
Click to collapse
"Force OTA"
UPDATE:: IF you cannot for whatever reason load the file to your SD Card, gmail yourself the link (below) and download it using Dolphin HD browser. I just confirmed it works on my phone, however, it does not work with the stock browser. Check the market for Dolphin HD, it's free. Client mode is set to desktop, which is under settings once in Dolphin HD. I was able to download the update.zip to the phone rather quickly over 4G Other browsers may work, I prefer that one though. Doesn't hurt to try. The stock one will not save the file, though will navigate to it.
As I first posted yesterday, there are [now 3] ways of downloading and installing the new EB13 Froyo release. If you have a Windows PC, there is a new utility that Samsung has released to flash the phone via PC. I personally couldn't get it to run on my Win 7 x64 laptop due to the enlarged font I run on my high-res laptop screen. Additionally, the 200MB file will wipe your phone completely clean. If you have a "trouble free" factory install of the current 2.1.1, the update method contained here is your best bet. Trouble free meaning that only bugs of the software are present. If you have issues above and beyond that of all other eclair users, you may want to completely wipe your phone.
The easiest and fastest method is to visit Samsung's Sprint Epic download page here http://www.samsung.com/us/support/downloads/SPH-D700ZKASPR and click the "Software" link (Manuals is the default landing page) and download the 91.14MB File labeled as for MAC OS. You will notice the much larger windows download (200MB) which is not needed, and may not work.
After you download the zip file, copy it over to your SD Card in your phone by either hooking it up and mounting it as you would normally do to copy files to your phone, or as I did, place the Micro SD card into an adapter and insert it into your computer. Copy the .zip file you downloaded onto the SD card; do not place it into any directory.
With your phone powered off, insert the SD Card back into the phone and replace the battery cover. Now, while holding both volume up and volume down rocker buttons (yes, you can push both at the same time), hold the camera button down as well and then press and hold the power on key. You will hold all 4 buttons on the phone until it boots into the flash menu.
Use the volume down button to scroll to..
"Apply SDcard: Update.Zip"
Push the Home key on the bottom of the phone and the update will commence.
Once it's complete, the phone may reboot into the menu again, at which time you select "Reboot" and hit the home key again.
The phone may reboot a few more times after it's first boot, and it may take a few minutes to fully get up and running. If it acts strange for a few minutes, this is normal.
Performing the update this way did not destroy any of my data, texts, applications, contacts, etc. Everything was exactly the same, except for the new version of Android. You must have a stock phone or the update most likely will not work. No ROMS, etc may be installed for the update to work. Before doing the update, go through your applications and uninstall anything you don't want / use.
You may also wait for the OTA update, but it will take a while to download, use up your battery, and you have to wait longer. It has already been confirmed several times, the 2 files are EXACTLY the same (OTA and the 91.14mb file from samsung) DO NOT waste time using a link to another file, there is no point and only risk in obtaining the file from somewhere else.
Before I began, I copied things off of my SD card that I wanted and performed a format on it. If you have apps installed on the SD Card, and you choose to do this, you may need to reinstall them. Once the update was complete, I copied the directories and files back to the SD Card.
(STICKY worthy!) No other post has this info immediately at hand.
Bump. I am seeing new posts answered by this.......
i don't know
http://forum.xda-developers.com/showthread.php?t=963652
It's already been done...
Eh, it's not as concise, and also not borrowed. This is the easy, "don't do anything but update my OS" method. NOTHING is needed except the ability to load the Update.zip to the SD Card.
NoSoMo said:
Eh, it's not as concise, and also not borrowed. This is the easy, "don't do anything but update my OS" method. NOTHING is needed except the ability to load the Update.zip to the SD Card.
Click to expand...
Click to collapse
Personally, I think Whosdaman's version is much more concise. Perhaps you meant yours is more convoluted or wordy? But hey, potato, tomato, right?
NoSoMo said:
Eh, it's not as concise, and also not borrowed. This is the easy, "don't do anything but update my OS" method. NOTHING is needed except the ability to load the Update.zip to the SD Card.
Click to expand...
Click to collapse
Do you know what the word concise means? And what does borrowed mean? Cause you do know I am the one who wrote the article for BriefMobile.com
And thank you to the post above me
Whosdaman said:
Do you know what the word concise means? And what does borrowed mean? Cause you do know I am the one who wrote the article for BriefMobile.com
And thank you to the post above me
Click to expand...
Click to collapse
You're welcome. And I'm guessing he was referring to how you linked to Briefmobile and outside files?
NoSoMo said:
Perhaps you should read the steps and not just do a character count? Personally I wouldn't subject the information on my phone to a that of a file that someone put on a download site.
- Get update file
- Place on SD Card
- Boot phone in flash mode and begin
Odin not required
Absolutely, sure it's full of other info, but it's info that's been asked numerous times.
Click to expand...
Click to collapse
Fair enough about not wanting to DL something that you can't verify the source... On a positive note, those three steps are exceptionally concise!
Does this work on DK28 Froyo? Probably not, eh?
I am on all stock and have clockwork installed. I tried to do the update like you said here, but it aborts the install and says no error message. I downloaded from the link you provided. It says E:Error in /sdcard/update.zip
Firmware version-2.1-update1
Build Number-SPH-D700 ECLAIR.DI18
So is there something I am doing wrong?
mynewepic10 said:
I am on all stock and have clockwork installed. I tried to do the update like you said here, but it aborts the install and says no error message. I downloaded from the link you provided. It says E:Error in /sdcard/update.zip
Firmware version-2.1-update1
Build Number-SPH-D700 ECLAIR.DI18
So is there something I am doing wrong?
Click to expand...
Click to collapse
This has been answered in one of those posts with several hundred replies (if I had the answer on-hand, I would post it). I kept the Epic stock to avoid any issues, so my update was rather simple. A few people have already had to reload their phones a couple of times before everything worked out.
nonzenze said:
Does this work on DK28 Froyo? Probably not, eh?
Click to expand...
Click to collapse
DK28 wasn't official. The latest official release is DI18 - 2.1.1. This updates STOCK 2.1.1 ONLY.
I didn't care to fool with the phone originally due to not knowing the exact release date of froyo. It has been way over due, but I honestly didn't have any reason to mod. Froyo has enhanced the phone, but honestly doesn't provide anything new that would change the way I already use the device. GPS is faster to acquire in google maps, but in GPS Test, it was always fairly instant. It's also reports more accurate, reports being key, it wasn't ever off but by 20 feet anyway, which is about all you can expect on 3D accuracy.
I used the .exe file from Samsung website to flash my phone and works like a champ.
Now some minor quirks with Froyo but will address them in different threads.
Thanks for the help!!
Dakrk
Updated the post, you can download the file directly to the phone. Send yourself the link via gmail....and read the first post of this thread.....
This update worked flawlessly didn't lose any of my settings or anything, Thank you so much!
D623 said:
This update worked flawlessly didn't lose any of my settings or anything, Thank you so much!
Click to expand...
Click to collapse
Glad to hear it
Doesn't work on DK28
Thank you for the clear instructions
I appreciated all the details in your instructions.
I downloaded to a blank xtra SD as you did and it all went very smoothly the first time.
Data, everything is retained.
Thank YOU.
up it goes
Thank you,i got bored waiting for ota.
Sent from Maxwell's shoe.
SAMFIRWARE EH17 Released!
How-To Upgrade video Curtsey of QBKing77 <--- Click Me!
At SAMFIRWARE request please no mirrors... see comment at end of post. If you are unable to download from hotfile, PM me
http://www.samfirmware.com/WEBPROTECT-samsungusa.htm
Free to register (please do, this way they know how many D700 USA Users love their leaks!!!)
Pulled from the above link:
TAKE CARE ROMS SEEMS SMALL D700EH17 2.3.4 DOWNLOAD Extracted with Password samfirmware.com -> Inside D700EH17 folder will be Odin and SPH-D700-EH17-8Gb-REL.tar.md5.7z -> Use 7zip to extract -> Inside is a SPH-D700-EH17-8Gb-REL.tar.md5 that is 290MB
PLEASE DONT MIRROR!
Formula84
@SamFirmware Question with XDA Link I made, another user wants to mirror your file via Dropbox download... are you okay with this?
4 minutes ago
in reply to ↑
SamFirmware
@SamFirmware SamFirmware
@Formula84 Its better for not. We check download stats how lower the downloads no new files comming.
Attached is ODIN 1.85 and instructions thanks to crawrj for the files.
Code:
IMPORTANT: Make sure you have installed the proper XP or Win7 drivers before starting. Also, remove the SD card from the phone (this may not be necessary, but having the SD card installed has caused Odin to fail for a number of people, so might as well just do it).
1. Extract the contents of the zip file to a folder
2. Open odin
3. Put your phone in download mode (Shut it off, wait for lights to all go out, then hold 1 on the keyboard while powering up)
4. connect phone (you should see odin put a Com4 or something like that in the first box. The actual number is NOT important what is important is something popped up there when you connected your device, meaning ODIN can see it)
5. The only box that should be checked is Auto Reboot.
6. You do not need to choose a pit file.
7. In the PDA Section choose the tar file. (Should be the sph-d700-****-8Gb-REL.tar)
8. Hit start. It will do its thing.
9. If it fails than try a new cable.
10. If the phone hangs for any reason take the battery and sdcard out and let it sit for an hour. Put it back together and try again.
Check this quote out...its the available ram from previous epic firmware.
blakealsobrook said:
342 mb ram. I can't wait to flash it tonight.
Click to expand...
Click to collapse
Sweet so this build offers a ram increase of 20 mb in issuable ram, pretty sweet. It reports 362 usable
Good work in changing the title slightly. I was about to make a bug thread as I figured it was going to start at some point in time. I haven't put a single leak on my phone yet, but I might depending on the initial reactions of this one.
Did they strip out the debug stuff? That may be why its so small...dling now
Very nice
Sent from my SPH-D700 using Tapatalk
I'll have a Mirror up soon. :>
I was wondering why my subscribed threads were slow lol
/sig
Avelnan said:
Phones are going to come to life someday. Take note: LG Optimus line. ASUS Transformer. And now the Nexus Prime.
Click to expand...
Click to collapse
Flashing now. Ill report back in a little while. You might want to add to the op that the tar needs to be extracted twice. once to get it out of the folder and once again when you have it on the desktop. If you notice once its extracted the first time it has a .7z extension on the end of it.
You MUST odin this in the PDA slot. It kept hanging at FactoryFS when using Phone slot.
Overstew said:
I'll have a Mirror up soon. :>
Click to expand...
Click to collapse
By having mirror we will not be giving them a true number of following users of their release.
Hotfile is fast and the wait is 15 sec.
Maybe if you are going to this you can keep track of the downloads for the next couple days and give them feedback via twitter.
GituSum said:
Flashing now. Ill report back in a little while. You might want to add to the op that the tar needs to be extracted twice. once to get it out of the folder and once again when you have it on the desktop. If you notice once its extracted the first time it has a .7z extension on the end of it.
Click to expand...
Click to collapse
Already there, lol I was editing after i got the first post in.
poit said:
You MUST odin this in the PDA slot. It kept hanging at FactoryFS when using Phone slot.
Click to expand...
Click to collapse
Phone is only for Modem bins, yes you are correct you must have this in PDA section.
formula84 said:
By having mirror we will not be giving them a true number of following users of their release.
Hotfile is fast and the wait is 15 sec.
Maybe if you are going to this you can keep track of the downloads for the next couple days and give them feedback via twitter.
Click to expand...
Click to collapse
I was going to dropbox it. I'm not sure if there is a way to track the number of downloads that way.
Overstew said:
I was going to dropbox it. I'm not sure if there is a way to track the number of downloads that way.
Click to expand...
Click to collapse
Dropbox will only help people out for about 3 hours until your limit is hit. Might as well put up a mirror somewhere else, IMO.
Overstew said:
I was going to dropbox it. I'm not sure if there is a way to track the number of downloads that way.
Click to expand...
Click to collapse
i'll ask via twitter if they care
hayzooos said:
Dropbox will only help people out for about 3 hours until your limit is hit. Might as well put up a mirror somewhere else, IMO.
Click to expand...
Click to collapse
I don't think the bandwidth is limited, only the amount of storage you can use. I've only added about 200 MB of storage so far, and I've had numerous downloads. Still says I have 4.8 GBs left.
As for bugs. INstalled GPS Status right off the bat and was only getting 2-3 sats locked. Did the cleared the modem memory http://forum.xda-developers.com/showthread.php?t=1226074 when I flashed CWM in Odin and now I'm getting 5 sats.
Nevermind. Busybox did install and showed up after I rebooted.
After flashing Su it looks like I have root. I can't install Busybox even though the installer says I'm rooted.I can delete system apps with Root Explorer and Titaniaum Backup.
Overstew said:
I don't think the bandwidth is limited, only the amount of storage you can use. I've only added about 200 MB of storage so far, and I've had numerous downloads. Still says I have 4.8 GBs left.
Click to expand...
Click to collapse
I just remember the ERA guys put their ROM on dropbox at first, and it got stopped when they exceeded bandwidth. At least, I thought that was the case but I could be wrong.
hayzooos said:
I just remember the ERA guys put their ROM on dropbox at first, and it got stopped when they exceeded bandwidth. At least, I thought that was the case but I could be wrong.
Click to expand...
Click to collapse
We'll find out.
EDIT: As per Samfirmware's request, I will not be mirroring the download. Sorry guys!
PLEASE DONT MIRROR! See Below...
Formula84
@
@SamFirmware Question with XDA Link I made, another user wants to mirror your file via Dropbox download... are you okay with this?
4 minutes ago Favorite Reply Delete
in reply to ↑
SamFirmware
@SamFirmware SamFirmware
@Formula84 Its better for not. We check download stats how lower the downloads no new files comming.
Overstew said:
I was going to dropbox it. I'm not sure if there is a way to track the number of downloads that way.
Click to expand...
Click to collapse
pjree said:
Here's a mirror with just the EH17 tar.
As for bugs. INstalled GPS Status right off the bat and was only getting 2-3 sats locked. Did the cleared the modem memory http://forum.xda-developers.com/showthread.php?t=1226074 when I flashed CWM in Odin and now I'm getting 5 sats.
After flashing Su it looks like I have root. I can't install Busybox even though the installer says I'm rooted.I can delete system apps with Root Explorer and Titaniaum Backup.
Click to expand...
Click to collapse
Overstew said:
We'll find out.
Click to expand...
Click to collapse
pjree said:
As for bugs. INstalled GPS Status right off the bat and was only getting 2-3 sats locked. Did the cleared the modem memory http://forum.xda-developers.com/showthread.php?t=1226074 when I flashed CWM in Odin and now I'm getting 5 sats.
After flashing Su it looks like I have root. I can't install Busybox even though the installer says I'm rooted.I can delete system apps with Root Explorer and Titaniaum Backup.
Click to expand...
Click to collapse
Deposit files is a 60 sec wait and slower than hotfile, i have the direct link posted in OP so you dont have to login to their site.
I am relatively new here, but was reading some threads and a couple people have said that the community hasn't found the 13.3.2.7 update to manually force a rollback. A couple days ago I called Amazon because I had updated to 4.5 and needed to go back to root.
Since then I have been looking around for where the patch was saved to and found the scripts that setup for the OS update and the scripts to run it. The scripts show where it is and what commands are called to do the update, but the actual 13.3.2.7 OS seems to be hidden. I know where it says it should be, but its hidden somehow. If this is something anyone wants copies of my files on let me know, if this isn't something the community needs I apologize, just trying to help get this tablet further along.
Either post here or message me if you want/need what I have.
Why don't you just post your findings so far on this thread?
I was under the impression that OTA files are downloaded to the /cache folder, therefore inaccessible without root.
Either way, updates are still verified (see: /system/app/otaverifier.apk) by the system, so I'm not sure how you'd get around that.
EncryptedCurse said:
Why don't you just post your findings so far on this thread?
I was under the impression that OTA files are downloaded to the /cache folder, therefore inaccessible without root.
Either way, updates are still verified (see: /system/app/otaverifier.apk) by the system, so I'm not sure how you'd get around that.
Click to expand...
Click to collapse
I see, that part is already known then. Other posts I read people were still looking for it, but I was sure if i found it many others have too. I'm still looking around though, I found the verification coding also, thanks for that. I am thinking about updating my tablet again, and having them roll it back again, but this time running a packet sniffer. Might possibly get some really good info about the verification process or at least the steps it takes to make the rollback. I did a search but haven't seen anyone try this, it's probably heavily encoded though.
Another thing I noticed while looking around... They put a kill switch fuse in it? That's pretty rough, and what causes it to activate? Software modification or Hardware like Jtags?
Eclipsys said:
I see, that part is already known then. Other posts I read people were still looking for it, but I was sure if i found it many others have too. I'm still looking around though, I found the verification coding also, thanks for that. I am thinking about updating my tablet again, and having them roll it back again, but this time running a packet sniffer. Might possibly get some really good info about the verification process or at least the steps it takes to make the rollback. I did a search but haven't seen anyone try this, it's probably heavily encoded though.
Another thing I noticed while looking around... They put a kill switch fuse in it? That's pretty rough, and what causes it to activate? Software modification or Hardware like Jtags?
Click to expand...
Click to collapse
once rooted again .it may be possible to modify your build.prop like we were on past firmware to achieve rollback just to initiate download ,it will ultimately fail once it downloaded it and trys to install it will check a few more things it will fail and erase it ...the trick would be not too let the device idle..or to have the battery below I believe 30 percent it may be as high as 40 I'm not sure but I believe under 30 it will refuse to install update delay till charged ,anyway it may buy you time to find it
jimyv said:
once rooted again .it may be possible to modify your build.prop like we were on past firmware to achieve rollback just to initiate download ,it will ultimately fail once it downloaded it and trys to install it will check a few more things it will fail and erase it ...the trick would be not too let the device idle..or to have the battery below I believe 30 percent it may be as high as 40 I'm not sure but I believe under 30 it will refuse to install update delay till charged ,anyway it may buy you time to find it
Click to expand...
Click to collapse
That is actually a very good idea, something I am testing right now is getting the FireOS to run in VMware. I have a standard Android KitKat OS running, but getting the Kindle's OS to run is giving me a few issues. I am very skittish to try this stuff on my actual device as it's brand new and I don't have a backup... But if I can I will give you idea a shot. Might be able to save it before it deletes. Also if I can get it going in VMware it might be possible to use a debugger to examine the ASM code in great detail.
Eclipsys said:
That is actually a very good idea, something I am testing right now is getting the FireOS to run in VMware. I have a standard Android KitKat OS running, but getting the Kindle's OS to run is giving me a few issues. I am very skittish to try this stuff on my actual device as it's brand new and I don't have a backup... But if I can I will give you idea a shot. Might be able to save it before it deletes. Also if I can get it going in VMware it might be possible to use a debugger to examine the ASM code in great detail.
Click to expand...
Click to collapse
I didn't have any problem doing the modifications myself and I'm no Pro that's for sure. Never written a line of code in my life. I just tend to thoroughly research and understand before I attempt things and I've been practicing here for a while if you go to the, rollback .0.1 and safestraped thread there is quite detailed instructions serval times throughout the thread I would skim it.you will just be substituting version numbers and kind of a inverse idea compared to what we were doing there but it should accomplish it. I used rOM Toolbox lite I believe as an editor and saved each timeI didn't have any problems with the permissions getting screwed up while tampering with it rOM Toolbox took care of that issue. I have seen tons of people brick trying to make these modifications. But I don't think they understood completely what they were attempting to do it's actually very simple and as long as you do it thoroughly and get all of them changed I have not seen any problems other than maybe having to repeat the process.there are a couple of lines that only use the last section of your version numbers I even changed those back then.
Eclipsys said:
I am relatively new here, but was reading some threads and a couple people have said that the community hasn't found the 13.3.2.7 update to manually force a rollback. A couple days ago I called Amazon because I had updated to 4.5 and needed to go back to root.
Since then I have been looking around for where the patch was saved to and found the scripts that setup for the OS update and the scripts to run it. The scripts show where it is and what commands are called to do the update, but the actual 13.3.2.7 OS seems to be hidden. I know where it says it should be, but its hidden somehow. If this is something anyone wants copies of my files on let me know, if this isn't something the community needs I apologize, just trying to help get this tablet further along.
Either post here or message me if you want/need what I have.
Click to expand...
Click to collapse
Please upload the file somewhere (preferably to mega). If it doesn't pass the version check we can use my hack to bypass it.
p1gl3t said:
Please upload the file somewhere (preferably to mega). If it doesn't pass the version check we can use my hack to bypass it.
Click to expand...
Click to collapse
https://mega.co.nz/#!wlQl2bZD!Kk-rcWtcMPWxoEH5VcHrtZb7nOsJet9si1pm5FYhT44
5.2 build prop file
The following is the latest version of TWRP compiled for the T-mobile V10 Model H901.
https://androidfilehost.com/?fid=818070582850501883
MD5SUM: b89d341cd61da31a5348d8f6b3c75c97
The heavy lifting was done by the twrpbuilder project who were generous enough to compile TWRP for our device. They also provide their services to see TWRP is available for devices that don't yet have it. I've personally used this version to do a backup and restore but can't guarantee there won't be issues. If there are while you are still in twrp you should go to the advanced section and copy the log to your external sd card. This log will help them diagnose any issues.
The project is located at: https://twrpbuilder.github.io
Their XDA thread is located here: https://forum.xda-developers.com/android/apps-games/twrpbuilder-t3744253
If you already have TWRP installed installation is as follows: Click Install, choose Image file, navigate to where the TWRP img file is located on your external sdcard and flash that img to the recovery partition. Back out to the root dir and you can select reboot then recovery...it should bounce you right back into recovery and you should see the new version loaded. If you have root in the rom and run into issues the app "flashify" can reflash TWRP 3.0 so make sure you also have it's img available.
This is pretty much only for folks who already have twrp to update to the latest. If you are on nougat you are still stuck until an exploit is released that works for nougat the way dirtycow did for marshmallow and below. *update* an exploit to give root to nougat users is now available thanks to @runningnak3d here: https://forum.xda-developers.com/tmobile-lg-v10/general/root-h901-nougat-t3773942
Reserved Post #1
Reserved Post #2
famewolf said:
The following is the latest version of TWRP compiled for the T-mobile V10 Model H901.
https://www.androidfilehost.com/?fid=8180705828505018
MD5SUM: b89d341cd61da31a5348d8f6b3c75c97
Click to expand...
Click to collapse
Looks to me like that URL should read
https://androidfilehost.com/?fid=818070582850501883
[ EDIT ] Yup, confirmed.. The URL I listed works fine.
Thanks for the file!
:laugh::silly:
NYLimited said:
Looks to me like that URL should read
https://androidfilehost.com/?fid=818070582850501883
[ EDIT ] Yup, confirmed.. The URL I listed works fine.
Thanks for the file!
:laugh::silly:
Click to expand...
Click to collapse
You are correct. For some reason a few characters got truncated. I've corrected the url in post #1.
famewolf said:
The following is the latest version of TWRP compiled for the T-mobile V10 Model H901.
https://androidfilehost.com/?fid=818070582850501883
MD5SUM: b89d341cd61da31a5348d8f6b3c75c97
The heavy lifting was done by the twrpbuilder project who were generous enough to compile TWRP for our device. They also provide their services to see TWRP is available for devices that don't yet have it.
Click to expand...
Click to collapse
Just as an aside, this version seems to correct (mostly) the date issue of previous TWRP versions for the V10. Versions before this one used to generate a default date (folder name) for the backup dating back to the 1970s as I recall.
This one has the correct month and day and time and the year is only 1 off - it showed 2017 on my very quick attempt to play with it.
One additional note to those installing it via TWRP itself - after selecting image flash , MAKE SURE you specify RECOVERY partition, not BOOT! Specifying BOOT will most likely have some less than desirable results.. :laugh:
NYLimited said:
Just as an aside, this version seems to correct (mostly) the date issue of previous TWRP versions for the V10. Versions before this one used to generate a default date (folder name) for the backup dating back to the 1970s as I recall.
This one has the correct month and day and time and the year is only 1 off - it showed 2017 on my very quick attempt to play with it.
One additional note to those installing it via TWRP itself - after selecting image flash , MAKE SURE you specify RECOVERY partition, not BOOT! Specifying BOOT will most likely have some less than desirable results.. :laugh:
Click to expand...
Click to collapse
I've passed on the date issue. Uncertain if he'll generate another build though.
famewolf said:
I've passed on the date issue. Uncertain if he'll generate another build though.
Click to expand...
Click to collapse
Seems that either nobody is using this version or nobody knows about it or they just have nothing to say..
Anyway, as you know, I have spent a fair amount of time recently working with this and installing it. A couple of observations that may be worth noting..
I double checked and I did set a screen timeout on TWRP. Previous versions would first, dim the screen, followed by turning it off completely. If you had the device near you on a desk while backing up the screen lighting up again when TWRP completed was a sure signal that it was finished.
This version of TWRP dims the screen but the screen is never turned off completely. A minor annoyance I suppose but something is different from previous versions.
During the /data partition backup I noted a (to me) new display in yellow: "Backups of data do not include any files in internal storage such as pictures or downloads"
Seriously? Is this something new? Certainly the display is but I always kinda relied on all that being backed up with /data and having the ability to restore them. This is a more serious issue for me which may make me consider going backward..
Thoughts?
NYLimited said:
Seems that either nobody is using this version or nobody knows about it or they just have nothing to say..
Anyway, as you know, I have spent a fair amount of time recently working with this and installing it. A couple of observations that may be worth noting..
I double checked and I did set a screen timeout on TWRP. Previous versions would first, dim the screen, followed by turning it off completely. If you had the device near you on a desk while backing up the screen lighting up again when TWRP completed was a sure signal that it was finished.
This version of TWRP dims the screen but the screen is never turned off completely. A minor annoyance I suppose but something is different from previous versions.
During the /data partition backup I noted a (to me) new display in yellow: "Backups of data do not include any files in internal storage such as pictures or downloads"
Seriously? Is this something new? Certainly the display is but I always kinda relied on all that being backed up with /data and having the ability to restore them. This is a more serious issue for me which may make me consider going backward..
Thoughts?
Click to expand...
Click to collapse
I use my v10 as my backup phone now. On my HTC U11 life when I make a nandroid it shows that it is not backing up files on internal storage. I think this is normal now on the latest version of twrp.
NYLimited said:
Seems that either nobody is using this version or nobody knows about it or they just have nothing to say..
Anyway, as you know, I have spent a fair amount of time recently working with this and installing it. A couple of observations that may be worth noting..
I double checked and I did set a screen timeout on TWRP. Previous versions would first, dim the screen, followed by turning it off completely. If you had the device near you on a desk while backing up the screen lighting up again when TWRP completed was a sure signal that it was finished.
This version of TWRP dims the screen but the screen is never turned off completely. A minor annoyance I suppose but something is different from previous versions.
During the /data partition backup I noted a (to me) new display in yellow: "Backups of data do not include any files in internal storage such as pictures or downloads"
Seriously? Is this something new? Certainly the display is but I always kinda relied on all that being backed up with /data and having the ability to restore them. This is a more serious issue for me which may make me consider going backward..
Thoughts?
Click to expand...
Click to collapse
On your last issue this is business as usual...twrp has NEVER backed up the internal SDCARD unless you selected the sdcard entry in the list of sections to be backed up. DCIM (pictures) and the Downloads folder/dir have never been included.
As to the dimming, you can check in settings to see if something can be configured however each person compiling twrp can set their own options as to how they want it to function. There is no guarantee or expectation that Person B is going to use the same options as Person A. You are of course free to compile your own copy configured the way you would prefer it to behave but the process was enough of a pain in the butt I just requested twrpbuilder to generate one as I kept getting errors. The process to compile it also appears poorly documented.
sabresfan said:
I use my v10 as my backup phone now. On my HTC U11 life when I make a nandroid it shows that it is not backing up files on internal storage. I think this is normal now on the latest version of twrp.
Click to expand...
Click to collapse
I kinda suspected that but that is, at best, a questionable choice since I don't even have the option to check or uncheck a selection for it. Not happy..
famewolf said:
On your last issue this is business as usual...twrp has NEVER backed up the internal SDCARD unless you selected the sdcard entry in the list of sections to be backed up. DCIM (pictures) and the Downloads folder/dir have never been included.
Click to expand...
Click to collapse
Not quite. INTERNAL is not the SD Card. Internal is emulated sd on /0. In TWRP if you tap select storage, for example, you can pick "internal" or "SD" for backup destination, as one example.
I keep a fair number of things in /Download - things I grab in my travels, things I save there for later use.. whatever. I'll have to device a Tasker module or something for copying all those to the actual SD card...
NYLimited said:
I kinda suspected that but that is, at best, a questionable choice since I don't even have the option to check or uncheck a selection for it. Not happy..
Not quite. INTERNAL is not the SD Card. Internal is emulated sd on /0. In TWRP if you tap select storage, for example, you can pick "internal" or "SD" for backup destination, as one example.
I keep a fair number of things in /Download - things I grab in my travels, things I save there for later use.. whatever. I'll have to device a Tasker module or something for copying all those to the actual SD card...
Click to expand...
Click to collapse
A fairly recent app/utility created by @kdrag0n called Tipatch brings a long-needed resolution to the table regarding "full backups" of Data using TWRP. In a nutshell, Tipatch installs to your Android device as a basic APK. Within the simple GUI, once root permissions are granted (In-Place Patching) Tipatch will decompile, patch, recompile and flash the patched TWRP to /recovery, effectively patching your TWRP build to backup the contents of Internal Storage (emulated SD card) as part of Data itself, so that backups will now include those Internal Storage contents such as downloads, photos, videos, game data, and other various files. I've tried it on this particular build of TWRP and it works without any issues. There are options to patch TWRP without root permissions as well. There are Windows, Mac & Linux versions available too. If you are patching TWRP on a device with an A/B partitioning scheme, the patched TWRP can be installed on both A & B using a one-click option. Of course, one insurmountable caveat to patching TWRP with Tipatch is that wiping Data now will also wipe Internal Storage (emulated SD card). In short, the utility works on pretty well all device types and chipset platforms (Exynos, Kirin, Snapdragon, MediaTek, etc.). The latest Tipatch update, v1.6, includes support for TWRP builds that use LZMA compression, and removes the now-misleading notification previously listed when backing up Data -- that Internal Storage (/data/media/ path / emulated SD card) contents are not backed up. Anyway guys, here is a link to the Tipatch Discussion & Support thread: https://forum.xda-developers.com/android/apps-games/app-twrp-tipatch-backup-internal-t3831217
The latest Tipatch v1.6 app is also available on the Play Store and many other app & apk repos for Android. Versions for Windows, Mac and Linux can be downloaded using the above link.
Hi I have just got a used NSTG and cannot connect to the Internet with it it seems I need to upgrade to 1.2.2 and when I copy the file to the nook nothing happens and when I reconnect it the zip file is gone.
Please can anyone advice how I force the update.
Peanutmans said:
Hi I have just got a used NSTG and cannot connect to the Internet with it it seems I need to upgrade to 1.2.2 and when I copy the file to the nook nothing happens and when I reconnect it the zip file is gone.
Please can anyone advice how I force the update.
Click to expand...
Click to collapse
Make sure the update zip is in the right place. My recollection of the process is that it happens when it wants to, but more or less after the device appears to go to sleep (so as not to interrupt your reading, etc.). So it may not necessarily boot up to show the update right after copying the file over and restarting. Not sure about the zip file disappearing. That should happen after the update, of course, but there could be stages in which relevant files are copied over and then it waits for sleep.
So....copy the zip to the correct location, disconnect from your computer and let the thing alone for awhile. If that does not work, it's possible the zip file is corrupt, I guess, and you might try downloading it again.
nmyshkin said:
Make sure the update zip is in the right place. My recollection of the process is that it happens when it wants to, but more or less after the device appears to go to sleep (so as not to interrupt your reading, etc.). So it may not necessarily boot up to show the update right after copying the file over and restarting. Not sure about the zip file disappearing. That should happen after the update, of course, but there could be stages in which relevant files are copied over and then it waits for sleep.
So....copy the zip to the correct location, disconnect from your computer and let the thing alone for awhile. If that does not work, it's possible the zip file is corrupt, I guess, and you might try downloading it again.
Click to expand...
Click to collapse
Right so I have finally found solution and hope this helps anyone in the future,
it seems the available 1.2.2 fw is not for UK nooks I have manually switched to a US fw and the update downloads fine as I would expect.