Related
The instructions for installing ubuntu are not that clear. so what is the ROOTFS and whad do i do with it. also i am trying to make it dual boot with android as the default opearating system. So what kernel do i need and what else do i need to get the touchpad working and wifi working
I'm trying to figure this out myself. I really don't have much time on my hands to figure out all the 1337 lingo surrounding the installation process of the dual boot ability. For once, I'd like someone who's technically literate enough to write down all these instructions in a dummies language... much like my gtab for dummies website in my siggy.
Just remember. If you're going to ask questions here. Make sure you apologize a lot of times. 1337s don't like questions.
goodintentions said:
1337 lingo
.......
1337s don't like questions.
Click to expand...
Click to collapse
What lingo? an example would be good.
And what "1337"?
"Before using this pack back up any data that you may have on your device, this method is destructive to data, and will wipe everything. If you plan on dual-booting with android you will need to download a full system like prime and put the images (system.img boot.img recovery.img) in images/
This package does not include the ubuntu rootfs. You should have already downloaded this from the link located on this forum post located http://rootzwiki.com/showthread.php?...he-transformer or http://forum.xda-developers.com/show...p?p=16097869if you haven't downloaded it yet it is 950MB so start it downloading and grab a coffee. Decompress the gzipped tar to images/
With that taken care of, here are the instructions for use:
1) select whether you want to dual boot, and which OS you want as your default.
2) make absolutely sure that you have backed up your data, everything past this point is going to destroy your data.
3) run the appropriate sh for the choice you have made in step 1
flash-purelinux.sh for a pure ubuntu setup, this is no android recovery is ubuntu single user mode.
flash-linux-android.sh for installing android and linux dual boot with android as the default OS. To boot into linux hold power+vol-down until prompted on screen to press vol-up.
flash-linux.sh for installing android and linux in dual boot with android and linux, linux is the default OS, to boot into android hold power+vol-down until prompted on screen to press vol-up"
From the ubuntu thread's OP, instructions for doing this. Says put rootfs in the /images folder of the flash kit along with the nvflash imgs from the android rom you want to dualboot with. Even shows you the options for which dualboot method you want and how to use it. If you consider this l33tspeak, I'm wondering what you consider basic English. If you can't even understand basic instructions, then don't use it. Too many people come into somewhat advanced technical methods for enhancing tech products and expect people to hold their hands through the methods. Of you want to understand these things, start googling and take some college courses. Xda isn't the place for learning technology.
Sent from my creaky Thunderbolt
i tried to download the rootfs and when i unzip the file all that comes out is ubuntu.img is this normal and if i want to dualboot with android where do i put the files and what kernel is required
yalkowni said:
i tried to download the rootfs and when i unzip the file all that comes out is ubuntu.img is this normal and if i want to dualboot with android where do i put the files and what kernel is required
Click to expand...
Click to collapse
Yes that's normal. And gosh, is reading that hard? "If you plan on dual-booting with android you will need to download a full system like prime and put the images (system.img boot.img recovery.img) in images/"
Gibeon said:
Yes that's normal. And gosh, is reading that hard? "If you plan on dual-booting with android you will need to download a full system like prime and put the images (system.img boot.img recovery.img) in images/"
Click to expand...
Click to collapse
i thought you couldnt load recovery with the ubuntu dual boot, can you now? thats pretty much all ive been waiting for to dual load ubuntu. i want to use revolver 3.2 and clemy's kernel with theme x, but without recovery, or at least the revolver 3.2 nvflash files, it wasnt worth it for me to switch over.
You still cant dual boot in the manner in which you are thinking
thebadfrog said:
You still cant dual boot in the manner in which you are thinking
Click to expand...
Click to collapse
word, thats what i thought, thanks. guess il have to hunt down the revolver nvflash files or bite the bullet and use prime (not that prime is a bad rom at all, im just used to revolver). im sick of decompiline and editing xml's in windows, i get errors all the time., and id rather not use my laptop at all, it shuts off randomly all the time. dual booting ubuntu onto my tf would eliminate my need to use my laptop or windows all together.
well when i tried to start it it said failed didnt find bootloader
I used cuckoopt's windows kit's dual boot option, and it seems to have worked, but it then just booted into android.
How to get ubuntu to boot?
Flash the Linux.zip
Sent from my SGH-T959 using XDA App
Is there anywhere a detailed guide on how to install Ubuntu beside Android I haven't found yet?
What I did:
- I downloaded Ubuntu (950MB) and the linux-flashkit.tar.gz on my PC (my PC is already running Ubuntu)
- Data-backup
- ?
How to move on? Boot Transformer into APX-mode and execute the flash-linux-android.sh?
Thx for the APX-tip in the other thread!
---------- Post added at 08:40 PM ---------- Previous post was at 08:11 PM ----------
So, I executed the *.sh-file, but after some seconds, in termial there is this:
Code:
file not found: ./images/system.img
failed executing command 2147483647 NvError 0x4
command failure: create failed
Where do I get this file from?
---------- Post added at 09:33 PM ---------- Previous post was at 08:40 PM ----------
Ok, I've found the system.img, but where do I get the boot.img? In the first post of the Ubuntu-thread I only find 'abootimg'. Is this the right file?
Lunchbox115 said:
Ok, I've found the system.img, but where do I get the boot.img? In the first post of the Ubuntu-thread I only find 'abootimg'. Is this the right file?
Click to expand...
Click to collapse
The system.img, boot.img, and recovery.img are all from the Android ROM you want to dual-boot Ubuntu with, so either you download them (some ROMs aren't released in nvflash img format, so you'd need to install it and back it up with nvflash first) or you use the images you generated from running your backup.
Source:
Before using this pack back up any data that you may have on your
device, this method is destructive to data, and will wipe
everything. If you plan on dual-booting with android you will need
to download a full system like prime and put the images (system.img
boot.img recovery.img) in images/
Click to expand...
Click to collapse
Sh*t, I read the first post three times and I didn't see that. Time for me to go to bed!
Thank you very much! Now it MUST work.
Another question: is there any chance to hard-brick the TF so that it can't be 'rescued'? Once I read that it's nearly unbrickable cause of NVFLASH. Is that true?
If you have an nvflash-able TF (which you do, or else you wouldn't have been able to perform the backup), you can't brick it. Even if you wipe the entire internal flash, you can still boot into APX mode, which has complete write access to the internal flash.
That's good to hear! I just asked cause the Galaxy S is brickable if you flash a wrong kernel or something like that. So it's nice to have a unbrickable tab.
It comes down to what hardware the phone has and what the community has figured out how to access. Most phones and devices have a hardware-based development interface (like APX mode for the Transformer or whatever RSDLite uses on older Motorola phones). These interfaces are generally burned onto read-only ROMs for the sole purpose of making the device un-brickable.
If the device doesn't have one of these interfaces, or the community hasn't figured out how to access it, you run the risk of bricking.
---------- Post added at 04:46 PM ---------- Previous post was at 04:11 PM ----------
I just made a thread explaining the Transformer boot process:
http://forum.xda-developers.com/showthread.php?p=17888843
I'll expend further on it, but this should help everyone understand where custom ROMs and Ubuntu fit into it.
Thanks a lot! I finally got the dualboot working. Android boots without any problems, in Ubuntu I have to configure the keyboard layout and nothing goes on, so I have to wait...
Thank you for helping me!
Lunchbox115 said:
Thanks a lot! I finally got the dualboot working. Android boots without any problems, in Ubuntu I have to configure the keyboard layout and nothing goes on, so I have to wait...
Thank you for helping me!
Click to expand...
Click to collapse
Excellent news! What do you mean about the keyboard? Do you mean that you type and nothing appears on the screen?
If you are going to flash and ICS ROM after this tool please make sure to first install a GB then ICS otherwise your SD card will not be accessible. I am trying to find a fix but it has been illusive. This statement will be removed once a fix has been found and OP updated.
Now with CWM Touch!
This method uses NVFLASH to recreate all partitions and formats them, thereby getting rid of the file allocation pointers and hence renders data inaccessible without effort.
Note: I have never seen a file come back to life or its data affect other files without effort on the users part or a temporary glitch once the partitions and pointers have been overwritten. Please post a reply with evidence if you have seen it.
Benefits:
The contents of the zip file can be used to super clean G2X before a new ROM flash. This tool recreates all the partitions in the phone so wipes the pointers to all files (everything). The method it employes has existed from before. The files here will stop short of pushing a ROM, so that you can push your favorite ROM.
Prerequisites:
G2X (Will not work on O2X due to different partition table)
Desire to have a clean install of your favorite ROM
Backup your data
*** WARNING ***
This tool will wipe both phone internal memory and internal SD card. External SD card content is safe.
Don't say you haven't been warned!
What to do:
Download the attached Zip file.
Take out the battery (assuming you have backed up your data on external SD card, computer or elsewhere), connect the device via USB while holding VOL+ and VOL- together. Don't let go of the volume buttons until the device is recognized.
(I typically leave Device Manager open to see when it shows up in the list under "USB Controllers").
Launch flash.bat, sit back and wait until the process finishes (generally a good idea to open a command prompt, CD to the directory and then run the file).
Unplug, put battery in, reboot into CWM recovery (pushed by this tool) by holding VOL- first, then pressing and holding POWER).
Flash your favorite ROM.
Enjoy!
I made this package because I could not get the bluetooth to work with G2x GB 2.3.3 (and below). The issue was a disconnect problem where both the phone and headset would still think they were connected but in audio would not be routed for a call or media. After this procedure my phone has not had an issue for almost 3 weeks now. I have tried it with two ROMs and 3 different headsets without any issues.
I guess I will not toss this phone after all .
Putting it out there in the hope that it may help others solve some of their issues as well. I suspect bad data stays in places not touched by other methods.
Your comments are most welcome.
[Update]
Klathmon has made an newer version with CWM 5.0.2.8. RP by Klathmon can be found here:
http://forum.xda-developers.com/showpost.php?p=24768294&postcount=66
I have tested the windows version but linux one is untested. Use at your own risk.
[Update]
Now with CWM Touch!
Thanks to everyone who has contributed on this thread with a drive to positive change! You work/comments/suggestions are very much appreciated.
References:
http://forum.xda-developers.com/showthread.php?t=1248644. This link was the inspiration for the current work.
Link to CWM Touch development thread. I took the image posted there: http://rootzwiki.com/topic/22984-recovery-touch-enabled-cwm-5813/
[EDIT] The zip file should be fixed now. Darn work machine does something to the upload.
was just about to flash the new hellfire rom and saw this tool! will try it out and see how things go
edit: yeah corrupt zip on my end too.
The zip file seems to be corrupt. Could you re-upload plz
worked great on my end, no problems.
khanggle said:
worked great on my end, no problems.
Click to expand...
Click to collapse
The real test is how stable your ROM would stay with this method to wipe than any of the other methods.
I guess only time will tell .
wow this method really blaze hellfire much thanks to your( you) & (rom dev)
Ohh I like this. Thank you for sharing .
This thing is faster than nullifier, and I especially like how you don't need to be in CWM to use it. It just seems like doing it in "update mode" would allow better manipulation of the phone's internals.
so this tool DOES format and nullify in addition to recreating the partitions?
deleting and recreating partitions does not remove data. only by writing over existing data can you get rid of it (like nullifier does)
dodgefan67 said:
so this tool DOES format and nullify in addition to recreating the partitions?
deleting and recreating partitions does not remove data. only by writing over existing data can you get rid of it (like nullifier does)
Click to expand...
Click to collapse
He states in OP that it doesn't write anything, therefor doesn't "nullify". It formats and partitions.
dodgefan67 said:
so this tool DOES format and nullify in addition to recreating the partitions?
deleting and recreating partitions does not remove data. only by writing over existing data can you get rid of it (like nullifier does)
Click to expand...
Click to collapse
Actually you are right. Deleting, recreating and formatting partitions does not get did of the 1s and 0s, so in that sense the data is still there. However the pointers are gone, and hence even though the data is still there it can't be accessed without effort.
What do you think the nand has on it when the device is shipped... I can assure you its not ask zeroes!
Sent from my LG-P999 using XDA
mansa_noob said:
Actually you are right. Deleting, recreating and formatting partitions does not get did of the 1s and 0s, so in that sense the data is still there. However the pointers are gone, and hence even though the data is still there it can't be accessed without effort.
What do you think the nand has on it when the device is shipped... I can assure you its not ask zeroes!
Sent from my LG-P999 using XDA
Click to expand...
Click to collapse
Well no, it has a next to worthless version of android Also, the point he was trying to get across is that it would be better for you to present the script for what it is and not try to compare it to other scripts that do something entirely different. You do kind of imply that you accomplish the same thing as the Nullifier script and more, when in fact you simply do something different.
Some may and probably will prefer your script, at least for specific purposes, while others will prefer the Nullifier script.
MWBehr said:
Well no, it has a next to worthless version of android Also, the point he was trying to get across is that it would be better for you to present the script for what it is and not try to compare it to other scripts that do something entirely different. You do kind of imply that you accomplish the same thing as the Nullifier script and more, when in fact you simply do something different.
Some may and probably will prefer your script, at least for specific purposes, while others will prefer the Nullifier script.
Click to expand...
Click to collapse
Done. OP updated to reflect. Thanks for clarifying that. It was not my intention to state that this tool does anything any other does, or does not.
I think we are all trying to do the same thing... get rid of the issues when swapping ROMs like _____. I can't seem to think of a good analogy here .
thanks for clarifying the OP, that makes much more sense
and no i wasnt trying to say you were reinenting the wheel, just trying to understand what your tool is actually doing
and also i do understand that it would take effort to get data off any type of storage device once the partition has been erased. i deal with wiping hard drives in a data center all the time. we use a DOD wipe tool that writes 1s and 0s over a drive a minimum of three full times to eradicate the data
but with this tool doing it outside of CWM, it sounds like it may do a better job of it
but i must ask, why do you need to push CWM? what if i have a newer version of it already on my phone?
dodgefan67 said:
but i must ask, why do you need to push CWM? what if i have a newer version of it already on my phone?
Click to expand...
Click to collapse
There is no need to push CWM 5.02. As I said in the OP it is a mod of the script found in the reference. In that script it was pushing default recovery. Since the recovery partition is being overwritten as well you will loose existing one and you need a recovery to be able to push a new ROM. Hence the need to push recovery (instead of using super one click).
As long as the recovery is not bigger than the partition that holds it we should be able to push a newer version. However I can't leave it empty or people will look for me with a shotgun (myself included ).
dodgefan67 said:
but i must ask, why do you need to push CWM? what if i have a newer version of it already on my phone?
Click to expand...
Click to collapse
I was thinking the same thing but seems easy enough .. add the cwm img to the dir and edit the .cfg file. Hopefully that should get the new CWM flashed
So would it be benefitial or pointless to nullify to clear the data then run this script for a... super clean?
Sent from my LG-P999 using XDA
mansa_noob said:
There is no need to push CWM 5.02. As I said in the OP it is a mod of the script found in the reference. In that script it was pushing default recovery. Since the recovery partition is being overwritten as well you will loose existing one and you need a recovery to be able to push a new ROM. Hence the need to push recovery (instead of using super one click).
As long as the recovery is not bigger than the partition that holds it we should be able to push a newer version. However I can't leave it empty or people will look for me with a shotgun (myself included ).
Click to expand...
Click to collapse
ahhhhhh now i understand. my eyes have been opened LOL
---------- Post added at 07:36 PM ---------- Previous post was at 07:35 PM ----------
PL0X_Kleiner said:
So would it be benefitial or pointless to nullify to clear the data then run this script for a... super clean?
Sent from my LG-P999 using XDA
Click to expand...
Click to collapse
i think it would be pointless unless you are super paranoid
dodgefan67 said:
ahhhhhh now i understand. my eyes have been opened LOL
---------- Post added at 07:36 PM ---------- Previous post was at 07:35 PM ----------
i think it would be pointless unless you are super paranoid
Click to expand...
Click to collapse
Nobody is twisting any arms here... Use it if you want to, don't if you don't want to.
I saw benefit so posted so that others may benefit as well.
Sent from my LG-P999 using XDA
Ok so question, why are you killing all the data on your internal SD card? Why not just the individual partitions that the phone uses? Your destroying data that don't need to be destroyed before flashing a rom...
Sent from my LG-P999 using xda premium
It does not have to be destroyed. I just haven't had a chance to test without recreating emmc yet.
Next step. Likely tomorrow. Would like to test before release.
Sent from my LG-P999 using XDA
[edit] BTW, I do want to restate that there is some data that needs to be destroyed which is not being taken care of by other methods. I don't believe it is in the emmc, but rather it resides in one of the other partitions. Most methods out there are only working in the /data, /system and /cache domain.
My original problem (bluetooth disconnect) which happens to be a problem for some in the community even now was only completely fixed by this method.
here is the file to the new update. If anyone can make an update.zip out of it, it would be greatly appreciated.
https://www.dropbox.com/s/zkl4rqu4dyc3p8p/dlpkgfile
DroidEris1981 said:
here is the file to the new update. If anyone can make an update.zip out of it, it would be greatly appreciated.
https://www.dropbox.com/s/zkl4rqu4dyc3p8p/dlpkgfile
Click to expand...
Click to collapse
I suggest that you rename it to the file name that recovery will accept and it should flash as normally done with the full firmware (in theory).
Is this for us version?
did you adb pull off the cache?
thanks!
FYI - after renaming this to "US_epad-user-9.4.5.26.zip" and putting it in on the root of my MicroSD. The system detects the update right away, but also fails right away (android guy on his side - red exclamation). After I boot back into .22, I have a message waiting saying the the update failed becuase the update file was older the the current version (which simlply isn't true - I'm on .22 for sure).
The OTA file looks fine to me (manifest inside says it's .26)...
Anyone have any ideas?
EDIT: Here is the update portion of the error log from /cache/recovery (it simply believe's it's the wrong version!):
I:Enable RSA key verification.
Installing update...
Finding update package...
I:Update location: /data/media/US_epad-user-9.4.5.26.zip
Opening update package...
I:1 key(s) loaded from /res/keys
I:comment is 1682 bytes; signature 1664 bytes from end
I:whole-file signature verified against key 0
I:verify_file returned 0
E:check version fail
Installation version error.
I:result_code: 80000013
Check and format /storage to vfat if needed...
Mount /btmac successfully
Done.
Thanks!
All right this patch is for US firmware updating from
asus/US_epad/EeePad:4.0.3/IML74K/US_epad-9.4.5.22-20120615
to
asus/US_epad/EeePad:4.0.3/IML74K/US_epad-9.4.5.26-20120720
And try rename this file to "EP201_768_SDUPDATE.zip" and put it in the microsd, enter the recovery kernel and it should flash in theory(?)
Redefined301 said:
All right this patch is for US firmware updating from
asus/US_epad/EeePad:4.0.3/IML74K/US_epad-9.4.5.22-20120615
to
asus/US_epad/EeePad:4.0.3/IML74K/US_epad-9.4.5.26-20120720
And try rename this file to "EP201_768_SDUPDATE.zip" and put it in the microsd, enter the recovery kernel and it should flash in theory(?)
Click to expand...
Click to collapse
Trying this right now.
E:check version fail
Click to expand...
Click to collapse
clearly this is for .22 only US firmware.
Do you meet this requirement ?
---------- Post added at 02:43 AM ---------- Previous post was at 02:41 AM ----------
Anyone else able to pull this patch file off cache for another region ?
---------- Post added at 02:46 AM ---------- Previous post was at 02:43 AM ----------
eoh7678 said:
Trying this right now.
Click to expand...
Click to collapse
Do let us know if it works or not!
Redefined301 said:
All right this patch is for US firmware updating from
asus/US_epad/EeePad:4.0.3/IML74K/US_epad-9.4.5.22-20120615
to
asus/US_epad/EeePad:4.0.3/IML74K/US_epad-9.4.5.26-20120720
And try rename this file to "EP201_768_SDUPDATE.zip" and put it in the microsd, enter the recovery kernel and it should flash in theory(?)
Click to expand...
Click to collapse
OK, tried this and got the following:
Code:
Finding update package...
Opening bundle update package...
E:Can't open /sdcard/ASUS_BUNDLE.zip
(No such file or directory)
Installing update...
Finding update package...
Opening update package...
E:Cannot find rule
SD Installation aborted.
Also, FYI, I got the OTA update notification and tried running it- it failed because I forgot that I had deleted some things from system/app that I never use (ie. ChromeBookmarkSyncAdapter, GoogleGarbageCrap, etc)
After reflashing the original .22 to replace, OTA insists that there is no update available. Any ideas for a fix there?
Redefined301 said:
clearly this is for .22 only US firmware.
Do you meet this requirement ?
---------- Post added at 02:43 AM ---------- Previous post was at 02:41 AM ----------
Anyone else able to pull this patch file off cache for another region ?
---------- Post added at 02:46 AM ---------- Previous post was at 02:43 AM ----------
Do let us know if it works or not!
Click to expand...
Click to collapse
Correct - I am currently on US .22 (no question about that).
I also tried the other name EP01_768_SDUPDATE.ZIP - same issues an other poster (No rule error),
Could there be an additional file or two that we need from the OTA update??
Very strange (and frustrating)! Not sure why Asus doens't post the full ROM's on thier website right away... Would make this a lot easier!!
eoh7678 said:
OK, tried this and got the following:
Code:
Finding update package...
Opening bundle update package...
E:Can't open /sdcard/ASUS_BUNDLE.zip
(No such file or directory)
Installing update...
Finding update package...
Opening update package...
E:Cannot find rule
SD Installation aborted.
Click to expand...
Click to collapse
Well if you really want to update, you'll need to meet few requirements.
1. Have firmware "US_epad-9.4.5.22-20120615" installed at present.
2. Need to be "root" and put that file back into /cache.
Hopefully it should update?...
Redefined301 said:
Well if you really want to update, you'll need to meet few requirements.
1. Have firmware "US_epad-9.4.5.22-20120615" installed at present.
2. Need to be "root" and put that file back into /cache.
Hopefully it should update?...
Click to expand...
Click to collapse
Have already tried that- correct firmware installed, dlpkgfile for correct region placed in /cache, still no love.
Also, FYI, I got the OTA update notification and tried running it- it failed because I forgot that I had deleted some things from system/app that I never use (ie. ChromeBookmarkSyncAdapter, GoogleGarbageCrap, etc)
After reflashing the original .22 to replace missing and altered apk's and build.prop, OTA insists that there is no update available. Any ideas for a fix there?
Redefined301 said:
Well if you really want to update, you'll need to meet few requirements.
1. Have firmware "US_epad-9.4.5.22-20120615" installed at present.
2. Need to be "root" and put that file back into /cache.
Hopefully it should update?...
Click to expand...
Click to collapse
What should the filename be when putting it in the /cache folder? I haven't gotten that method to see the update yet...
Although, if it does the same "version check", then it'll probably fail as well.
I wonder if the folks that can't update are using a certain model dock or no dock at all? Actaully, I tried to update without the dock too - same issues. I have the dock with the TF700 model number...
jtrosky said:
Correct - I am currently on US .22 (no question about that).
I also tried the other name EP01_768_SDUPDATE.ZIP - same issues an other poster (No rule error),
Could there be an additional file or two that we need from the OTA update??
Very strange (and frustrating)! Not sure why Asus doens't post the full ROM's on thier website right away... Would make this a lot easier!!
Click to expand...
Click to collapse
Well. They pull the patch offline simply because they pulled it offline.
And supposedly if you don't see a firmware at the official support site then it's not officially released yet.
So, only a margin number of devices got updated OTA.
What does this mean?
Maybe they haven't finished with the firmware yet ..?
---------- Post added at 02:57 AM ---------- Previous post was at 02:54 AM ----------
jtrosky said:
Correct - I am currently on US .22 (no question about that).
I also tried the other name EP01_768_SDUPDATE.ZIP - same issues an other poster (No rule error),
Could there be an additional file or two that we need from the OTA update??
Very strange (and frustrating)! Not sure why Asus doens't post the full ROM's on thier website right away... Would make this a lot easier!!
Click to expand...
Click to collapse
Simply put you can't have any of your existing files under /system or any other partition in the firmware except /data modified.
For the patch to work.
---------- Post added at 02:58 AM ---------- Previous post was at 02:57 AM ----------
jtrosky said:
What should the filename be when putting it in the /cache folder? I haven't gotten that method to see the update yet...
Although, if it does the same "version check", then it'll probably fail as well.
I wonder if the folks that can't update are using a certain model dock or no dock at all? Actaully, I tried to update without the dock too - same issues. I have the dock with the TF700 model number...
Click to expand...
Click to collapse
The same file name as it was originally came from.
Redefined301 said:
Well. They pull the patch offline simply because they pulled it offline.
And supposedly if you don't see a firmware at the official support site then it's not officially released yet.
So, only a margin number of devices got updated OTA.
What does this mean?
Maybe they haven't finished with the firmware yet ..?
---------- Post added at 02:57 AM ---------- Previous post was at 02:54 AM ----------
Simply put you can't have any of your existing files under /system or any other partition in the firmware except /data modified.
For the patch to work.
---------- Post added at 02:58 AM ---------- Previous post was at 02:57 AM ----------
The same file name as it was originally came from.
Click to expand...
Click to collapse
Well, not sure what to say - I've even tried starting from a fresh .22 install - still no go. What's REALLY strange is that my tablet *did* see the update automatically this morning, but that original update failed just like it does when I try to do it manually now. Alsomost like once it fails, there is no way to update! Maybe a bug on Asus side?
jtrosky said:
Well, not sure what to say - I've even tried starting from a fresh .22 install - still no go. What's REALLY strange is that my tablet *did* see the update automatically this morning, but that original update failed just like it does when I try to do it manually now. Alsomost like once it fails, there is no way to update! Maybe a bug on Asus side?
Click to expand...
Click to collapse
Same thing here, exactly. After failing the original OTA, it's as though the update stopped existing for my tablet.
I'm trying a full factory reset now- data/cache wipe, reloading .22, etc. Will update.
jtrosky said:
Well, not sure what to say - I've even tried starting from a fresh .22 install - still no go. What's REALLY strange is that my tablet *did* see the update automatically this morning, but that original update failed just like it does when I try to do it manually now. Alsomost like once it fails, there is no way to update! Maybe a bug on Asus side?
Click to expand...
Click to collapse
I think it still fails for you is because you've messed with the /system too much or else where, then the patch file won't match cause it is looking for the correct files to patch.
And I wouldn't know what else you have done to your tablet so, best to wait for the next update.
eoh7678 said:
Same thing here, exactly. After failing the original OTA, it's as though the update stopped existing for my tablet.
I'm trying a full factory reset now- data/cache wipe, reloading .22, etc. Will update.
Click to expand...
Click to collapse
Ha! I'm trying that entire, exact same process one more time too! I'll report my findings as well.
---------- Post added at 03:13 PM ---------- Previous post was at 03:12 PM ----------
Redefined301 said:
I think it still fails for you is because you've messed with the /system too much or else where, then the patch file won't match cause it is looking for the correct files to patch.
And I wouldn't know what else you have done to your tablet so, best to wait for the next update.
Click to expand...
Click to collapse
Yes, but doesn't a fresh install of .22 overwrite /system completely? Plus after that I'm doing a restore to factory defaults - so EVERYTHING should be back to stock...
eoh7678 said:
Same thing here, exactly. After failing the original OTA, it's as though the update stopped existing for my tablet.
I'm trying a full factory reset now- data/cache wipe, reloading .22, etc. Will update.
Click to expand...
Click to collapse
Did you messed with your /system too? If not then version should be correct ?
Redefined301 said:
I think it still fails for you is because you've messed with the /system too much or else where, then the patch file won't match cause it is looking for the correct files to patch.
And I wouldn't know what else you have done to your tablet so, best to wait for the next update.
Click to expand...
Click to collapse
I've just done a complete factory wipe- format /data and /cache, flashed the original US .22 firmware, and still says no OTA is available.
I'm going to try flashing to WW image and see what happens.
jtrosky said:
Ha! I'm trying that entire, exact same process one more time too! I'll report my findings as well.
---------- Post added at 03:13 PM ---------- Previous post was at 03:12 PM ----------
Yes, but doesn't a fresh install of .22 overwrite /system completely? Plus after that I'm doing a restore to factory defaults - so EVERYTHING should be back to stock...
Click to expand...
Click to collapse
Correct then that's for you to find out.
Since the OTA isn't available anymore so there's no point in trying to find out why and how it have gone wrong, does it?
Here my tablet updated earlier yesterday morning it's the TW version.
I'm not really sure what's changed in the kernel but it doesn't feel more responsive too, so guess the update isn't good enough... IMO.
---------- Post added at 03:20 AM ---------- Previous post was at 03:18 AM ----------
eoh7678 said:
I've just done a complete factory wipe- format /data and /cache, flashed the original US .22 firmware, and still says no OTA is available.
I'm going to try flashing to WW image and see what happens.
Click to expand...
Click to collapse
Don't bother because here I've got another tablet and it's not up to date yet checked for update and there's none available, the update was just available ota for few hours.
So let's put it this way, this is a BETA version and not supported.
Redefined301 said:
Correct then that's for you to find out.
Since the OTA isn't available anymore so there's no point in trying to find out why and how it have gone wrong, does it?
Here my tablet updated earlier yesterday morning it's the TW version.
I'm not really sure what's changed in the kernel but it doesn't feel more responsive too, so guess the update isn't good enough... IMO.
Click to expand...
Click to collapse
I'm not following. As far as I know, people are still receiving the update - it's not "pulled" or anything - just not working for a select few as far as I can tell.. I've also heard a lot of users saying that it makes a noticeble performance difference.
I give up - I guess we'll just have to wait for Asus to post the full version (it seems to take a week or so before they post the full firmware)...
I'm concerned with the privacy of my data and I want to avoid any accidental recovery from the flash in my phone once returned for rma.
Is there any way to attempt to make the recovery harder? Something that can overwrite the whole userdata and system partition with 0 or any other pattern?
Thank you
Download an app called forevergone from the play store
sent from my HAMMERHEAD neXus
---------- Post added at 02:51 PM ---------- Previous post was at 02:46 PM ----------
Just realized it's not on the market anymore. Let me see if I have it backed up
sent from my HAMMERHEAD neXus
---------- Post added at 02:57 PM ---------- Previous post was at 02:51 PM ----------
Here you go https://copy.com/UHEjr
sent from my HAMMERHEAD neXus
Thank you
I've done a factory reser and i think it already does a zero fill for the entire data partition. In fact it takes a lot of time and i found someone on internet supporting this behaviour after a checkup in the sources for any evidence.
A factory reset done from the android menus (if you have stock recovery) will wipe everything you put on the device (except system apps).
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
I want only to know if my data is securely deleted. A zero fill makes impossible the recovery without special equipment. So if the android factory reset does also a zero fill I can sell my phone or rma it without privacy issues
CyberPK said:
I want only to know if my data is securely deleted. A zero fill makes impossible the recovery without special equipment. So if the android factory reset does also a zero fill I can sell my phone or rma it without privacy issues
Click to expand...
Click to collapse
A factory reset doesn't go through and obscure the data like that. It removes the table of contents so the files aren't visible to the file system, but the data is still there (as you know). I actually just went through this with my previous phone before I sold it. I formatted all partitions with twrp and also formatted internal storage in Windows but a couple of free recovery programs were still able to find some deleted files.
I just ended up copying my entire music library over to fill up the partition so all blocks were overwritten. After that, the programs weren't able to recover anything. Not very high tech, but effective. You could even make a couple of passes if you want to be extra sure.
Sent from my Nexus 5
CRIME INC. said:
Download an app called forevergone from the play store
sent from my HAMMERHEAD neXus
---------- Post added at 02:51 PM ---------- Previous post was at 02:46 PM ----------
Just realized it's not on the market anymore. Let me see if I have it backed up
sent from my HAMMERHEAD neXus
---------- Post added at 02:57 PM ---------- Previous post was at 02:51 PM ----------
Here you go https://copy.com/UHEjr
sent from my HAMMERHEAD neXus
Click to expand...
Click to collapse
I was looking for an app like this but there's a warning.
DON’T USE THIS APP ON ANDROID 4.3+.
There are some reports that after running this app on Android 4.3, their devices are become slower than usual.
Use at your own risk.
Click to expand...
Click to collapse
http://free-apps-android.com/forever-gone/
Edit - found another app. No idea if it's any good.
http://www.appszoom.com/related-apps/forever-gone-sd-card-cleaner_bxtrf_5#nav=related
https://groups.google.com/forum/#!msg/android-security-discuss/DB6k_hnVk0E/iMR1N_ugPeEJ
CyberPK said:
Is there any way to attempt to make the recovery harder? Something that can overwrite the whole userdata and system partition with 0 or any other pattern?.
Click to expand...
Click to collapse
I would factory reset the device. Pull the sim and go through the normal setup without setting up any networking or accounts. Once the device is running, encrypt the device. Last, factory reset the device and then send it for rma.
Sent from AOSP koeMod 4.4.2 w/ Franco kernel
koe1974 said:
I would factory reset the device. Pull the sim and go through the normal setup without setting up any networking or accounts. Once the device is running, encrypt the device. Last, factory reset the device and then send it for rma.
Sent from AOSP koeMod 4.4.2 w/ Franco kernel
Click to expand...
Click to collapse
Read my previous post, and take a look @ https://groups.google.com/forum/#!msg/android-security-discuss/DB6k_hnVk0E/iMR1N_ugPeEJ
Is it true?
CyberPK said:
Read my previous post, and take a look @ https://groups.google.com/forum/#!msg/android-security-discuss/DB6k_hnVk0E/iMR1N_ugPeEJ
Is it true?
Click to expand...
Click to collapse
I don't know, but I do know that if you do what I suggest, the only data to recover would be encrypted default settings with no personal information.
Sent from AOSP koeMod 4.4.2 w/ Franco kernel
So my Nvidia Shield is in route after a much anticipated wait to finally having some extra funds to purchase one. I recall a while back with the most esteemed certainty when I check on the Nvidia shield tab of my Geforce experience was that the card was compatible with my ASUS G75VW laptop. When I updated my drivers today I looked at the shield tab and it said my PC is not ready for streaming to the shield... Evidently by some genius gesture, nvidia decided to make the card below mine (GTX 660M) and the card above mine (GTX 680M) compatible, yet mine the GTX 670M is not. . . Are there any workarounds to this that I may not be aware of or am I just SOL because of Nvidia's genius?
I was actually sent here from the nvidia forums where an actually moderator mentioned there may be some workaround here. I assume there is a way to bypass it but I am unfamiliar with this so called "rooting" process and if there is a guide some where where I can get this thing working I would really much appreciate it xD.
http://www.mediafire.com/download/oxrryya4ffs4w6u/tr-1.apk
First install any updates for Apps as well as the Shields Firmware if you have not already.
THEN
Download the App in the above link, make sure you have "Unknown Sources" checked in the "Security" section of the "Settings" App, otherwise it won't install, then just tap it in the notification centre or in a file manager, install, open, click "Make It Ra1n", wait for it to finish, wait an additional 20 seconds, then reboot. You'll have Root Access (but NOT an Unlocked Bootloader or a Custom Recovery, so NOTHING WILL BE DELETED!)
If that does not work try downgrading your graphics cards driver, it might have a bug if it worked before.
DISCLAIMER: IT IS POSSIBLE FOR THIS TO BRICK YOUR DEVICE IF YOU ARE NOT CAREFUL BUT THAT IS STILL VERY UNLIKELY TO HAPPEN!!!!
---------- Post added at 10:36 PM ---------- Previous post was at 10:24 PM ----------
Also according to the first post in the topic below, laptop GPU's can't officially stream and nobody can seem to get it to work.
http://forum.xda-developers.com/showthread.php?t=2394478
---------- Post added at 10:46 PM ---------- Previous post was at 10:36 PM ----------
http://forum.xda-developers.com/showthread.php?t=2505510
The above says streaming with a mobile GPU works if you have at least GeForce Experience 2.0 installed on your computer. It also says that sometimes streaming does not work and that a reboot of the computer is needed.
krion64 said:
http://www.mediafire.com/download/oxrryya4ffs4w6u/tr-1.apk
First install any updates for Apps as well as the Shields Firmware if you have not already.
THEN
Download the App in the above link, make sure you have "Unknown Sources" checked in the "Security" section of the "Settings" App, otherwise it won't install, then just tap it in the notification centre or in a file manager, install, open, click "Make It Ra1n", wait for it to finish, wait an additional 20 seconds, then reboot. You'll have Root Access (but NOT an Unlocked Bootloader or a Custom Recovery, so NOTHING WILL BE DELETED!)
If that does not work try downgrading your graphics cards driver, it might have a bug if it worked before.
DISCLAIMER: IT IS POSSIBLE FOR THIS TO BRICK YOUR DEVICE IF YOU ARE NOT CAREFUL BUT THAT IS STILL VERY UNLIKELY TO HAPPEN!!!!
---------- Post added at 10:36 PM ---------- Previous post was at 10:24 PM ----------
Also according to the first post in the topic below, laptop GPU's can't officially stream and nobody can seem to get it to work.
http://forum.xda-developers.com/showthread.php?t=2394478
---------- Post added at 10:46 PM ---------- Previous post was at 10:36 PM ----------
http://forum.xda-developers.com/showthread.php?t=2505510
The above says streaming with a mobile GPU works if you have at least GeForce Experience 2.0 installed on your computer. It also says that sometimes streaming does not work and that a reboot of the computer is needed.
Click to expand...
Click to collapse
Thanks for all the great info, but what exactly does that file do for my shield as far as the purpose of "Rooting" it?