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?
To outline my situation, I have installed CWM to my phone, and flashed version 2.5.1.2 of Galaxy S i9000 (but the recovery boot doesn't show as CWM) on a Samsung InFuse 4G (this part I managed to find by scouring the forums) with Firmware version 2.2.1, Kernel 2.6.32.9, with Build FROYO.UCKH1. This is as far as I have gotten because I cannot seem to get a backup of my phone's ROM made. So, my question is can someone explain (without jargon, I haven't quite learned it yet) in simple steps how to resolve this issue and help me continue my way to flashing a custom ROM? I've checked and read so many other guides, but they are confusing because the steps aren't (sad to say) dumbed down for me. Here's an example of what I read:
1: dl CWM (actually had to go look this up and figure out what it was)
2: flash CWM (my phone model wasn't on the list, but after an extensive search found out that I could use the Galaxy S i9000 [supposedly])
3: boot into CWM Recovery (can't do it, for some reason it won't load on my phone.)
4: perform backup with CWM (as before, can't do it, read I could use Titanium backup but no depth was given)
5: dl a rom and place it on your sd card (this one is understood, short and to the point)
6: boot into CWM and flash rom
Unfortunately, when I start out on a new OS (already owning Windows and getting good at Linux) I tend to not even understand these so-called "Dummies Guides." I need something filled with minimal jargon that is short and sweet. Any information would be helpful
Also, I would like to know the likelihood of bricking my phone (based off of its specs) if it is possible to find out...
I'm a little bit confused here. How come you've flashed an i9000 (Galaxy S) firmware onto an Infuse? I think we can work out your backup problems though
I mean that I flashed the Galaxy S i9000 version of CWM Recovery to my phone because there wasn't an InFuse option. (according to one thread, it said that the i9000 version was compatible with the InFuse)
However, I flashed the Recovery, but when I booted into recovery mode, I was still in the stock recovery. Any explanation for this and everything else?
I don't really know anything about the Android system yet, but I hope to be good enough to become a developer one day.
DeltaOps said:
I mean that I flashed the Galaxy S i9000 version of CWM Recovery to my phone because there wasn't an InFuse option. (according to one thread, it said that the i9000 version was compatible with the InFuse)
However, I flashed the Recovery, but when I booted into recovery mode, I was still in the stock recovery. Any explanation for this and everything else?
I don't really know anything about the Android system yet, but I hope to be good enough to become a developer one day.
Click to expand...
Click to collapse
Gotcha. Sounds like the recovery hasn't flashed properly. Did you have the phone rooted before flashing the recovery?
Here is an awesome thread with video guides on just about everything you could need. Here is another. I take it you've already followed at least one of these to get the recovery flashed, so it might pay to try the 3E recovery instead and see if that works.
You may need to go right back to stock and start over. If you do, AdamOutler has got you covered right here.
I'll stay subscribed in case you need anything else, best of luck mate
My phone was rooted with SuperOneClick. Superuser was still intact. I read on a thread that the CWM Recovery could "fake flash" and that it would still be accessible by selecting "boot into recovery" but it doesn't show.
It says 3E in my recovery mode, is that the modified or is it actually stock?
I downloaded CWM from the market (method 2) but for some reason have update.zip on my phone (method 1). Any explanation? I don't exactly remember downloading a .zip file...
DeltaOps said:
My phone was rooted with SuperOneClick. Superuser was still intact. I read on a thread that the CWM Recovery could "fake flash" and that it would still be accessible by selecting "boot into recovery" but it doesn't show.
It says 3E in my recovery mode, is that the modified or is it actually stock?
I downloaded CWM from the market (method 2) but for some reason have update.zip on my phone (method 1). Any explanation? I don't exactly remember downloading a .zip file...
Click to expand...
Click to collapse
It may have 'fake flashed' and not worked at all. Both stock and modified recovery will say 3E, the difference is in the version numbers although I can't picture them off the top of my head. If CWM had worked, you would not be seeing 3E, you would see the typical array of CWM options. The modified 3E does not give you the same options CWM does, it just gives you the option to flash an 'unsigned' image from Recovery.
I have never had any luck with ROM Manager personally, although a lot of people swear by it. I found it especially flaky flashing recoveries to any device, very hit-and-miss. I personally prefer, and recommend, flashing recoveries manually via ADB. A little trickier, but a lot more trustworthy.
That said, try flashing recovery through RM again before taking any further steps. Flashing a recovery over a recovery won't hurt
I've tried three separate times to install the CWM recovery, but all were unsuccessful. What's this about ADB? I remember seeing the ADB Daemon in the SuperOneClick rooting process. And how tricky is it exactly, does it require code?
I have the Titanium Backup app on my phone, and I have backed up all the system and app data, but they are all separate files instead of a single (what, .md5?) file. I remember reading another thread that said you could back up a ROM via TB but I can't find a back up ROM option. Is there a particular way to do this or do I have to have the Premium/Pro version of TB? Or have I pretty much done all I can do with TB?
DeltaOps said:
I've tried three separate times to install the CWM recovery, but all were unsuccessful. What's this about ADB? I remember seeing the ADB Daemon in the SuperOneClick rooting process. And how tricky is it exactly, does it require code?
I have the Titanium Backup app on my phone, and I have backed up all the system and app data, but they are all separate files instead of a single (what, .md5?) file. I remember reading another thread that said you could back up a ROM via TB but I can't find a back up ROM option. Is there a particular way to do this or do I have to have the Premium/Pro version of TB? Or have I pretty much done all I can do with TB?
Click to expand...
Click to collapse
ADB is a command-line interface between your PC and your phone. You enable USB debugging and connect the phone via USB to the computer. Once you have the correct drivers installed, you can then use ADB (part of the Android SDK available for download) to send commands to your phone, as well as push and pull files. This requires full root, which you already have.
For example you can grab the recovery.img for CWN on the Infuse and tell ADB to 'flash recovery recovery.img' and actually ensure it flashes.
There are some excellent ADB tutorials floating around, this one in particular got me started. Make sure you do a bit of reading first though: the wrong command can royally screw you.
After you're familiar, you should be able to use ADB to push a recovery to your phone, whether it be unsecured 3E, or CWM.
I'll stay subscribed for any queries you may have
How close is the ADB interface to other command-line interfaces like Linux or Windows? I use both operating systems on my laptop and I have familiarized myself with both of them (mostly). What am I supposed to be expecting when I use it? Also, I can't seem to find the recovery.img file, what folder would that be under?
DeltaOps said:
How close is the ADB interface to other command-line interfaces like Linux or Windows? I use both operating systems on my laptop and I have familiarized myself with both of them (mostly). What am I supposed to be expecting when I use it? Also, I can't seem to find the recovery.img file, what folder would that be under?
Click to expand...
Click to collapse
Don't know about Linux, but ADB works through a Windows command prompt so its pretty much the same. You will need to have ADB, Fastboot plus whatever you wish to flash (recovery.img) in a 'working' directory, then run a command prompt from that directory.
You will probably need to download the recovery.img file.from XDA. It may be zipped up (they usually are).
Sent from my Galaxy Note using XDA Premium
I've successfully got ADB started in the command prompt (not that bad :]) but when I try to pull the directory map from my phone, it says: remote object "xxxxxxxxx" does not exist. And what's this about Fastboot? Edit: Did a bootloader command test, worked just fine. No success on pulling directory
Command I used: "adb pull -s xxxxxxxxxxx C:\"
DeltaOps said:
I've successfully got ADB started in the command prompt (not that bad :]) but when I try to pull the directory map from my phone, it says: remote object "xxxxxxxxx" does not exist. And what's this about Fastboot? Edit: Did a bootloader command test, worked just fine. No success on pulling directory
Command I used: "adb pull -s xxxxxxxxxxx C:\"
Click to expand...
Click to collapse
I don't think that's the correct format to pull directory structure. I'll have to read up on that one
Fastboot is another tool you can use to flash bootloaders, radios, recoveries etc through the command prompt.
Sent from my Galaxy Note using XDA Premium
You're right, tried using the <remote> variable as a file instead of the device serial. Typed:
adb pull .. files
prompt skitzed out after that. I know it won't damage anything since it's a copy procedure but I'm looking for the file and it's not there. it said it's pulling everything after skipping "special files"
Edit: It just finished, said it couldn't create the file because for some reason it was trying to copy the files from the phone to the phone
DeltaOps said:
You're right, tried using the <remote> variable as a file instead of the device serial. Typed:
adb pull .. files
prompt skitzed out after that. I know it won't damage anything since it's a copy procedure but I'm looking for the file and it's not there. it said it's pulling everything after skipping "special files"
Edit: It just finished, said it couldn't create the file because for some reason it was trying to copy the files from the phone to the phone
Click to expand...
Click to collapse
Yeah, you'll have to give it a target directory, I think it's like this '.\sdcard' to write them to the SD card?
Sent from my Galaxy Note using XDA Premium
If that's the case, then how do I make the file copy to my HDD? The drive doesn't show up on my computer (does it)?
DeltaOps said:
If that's the case, then how do I make the file copy to my HDD? The drive doesn't show up on my computer (does it)?
Click to expand...
Click to collapse
I'm sure that with the correct command, you will be able to pull the structure to your hard drive. I'm not sure if it's .\C:/ or not, I'll have a look when I'm on a proper rig and can do a proper search
Sent from my Galaxy Note using XDA Premium
Thanks! You've been great so far
That noob video was right, XDA is full of awesome people!
Edit: Got it Thanks for the pointers. Now I need to find out how to back up the entire ROM... :/
DeltaOps said:
Thanks! You've been great so far
That noob video was right, XDA is full of awesome people!
Edit: Got it Thanks for the pointers. Now I need to find out how to back up the entire ROM... :/
Click to expand...
Click to collapse
Glad you got it and glad to help. There are a hell of a lot of good people here If there's anything else you need, feel free to PM me.
Good luck buddy!
Sent from my Galaxy Note using XDA Premium
Is there perhaps any way to perform a ROM backup with ADB?
DeltaOps said:
Is there perhaps any way to perform a ROM backup with ADB?
Click to expand...
Click to collapse
Ooh good question. I don't think so, but I'm not sure. I know you can pull directories like /system/ and whatnot, but as for repackaging them into a working backup, that may be a bit more involved. I would use ADB to.push a working CWM and do it that way, but it sounds.like you're a bit better at the command-line stuff than I so you may be able to work it!
Sent from my Galaxy Note using XDA Premium
Hey guys
I screwed up my vold.fstab trying to get "_ExternalSD" back.
Unfortunately! I did not run a nandroid before I made the change.
Now, I can dirty flash my rom on top, or go back to a nandroid from a few days ago, but I'd really just like to recover and go on my merry way. And maybe learn something in the process.
Only thing is, I can't figure out how to access the phone other than the External SD card through CWM.
Can I mount the internal /system and access through USB? Is there some facility to copy a file from one point to another? Any other methods? I guess the phone has to be up to run ADB, right?
I don't know how to generate a flashable zip but I could extract the original version of the file from the original rom. I assume that its non trivial to create a flashable zip, but maybe someone can comment? It looks like there is signing and certificates involved..
thanks for any ideas
bluenote73 said:
Hey guys
I screwed up my vold.fstab trying to get "_ExternalSD" back.
Unfortunately! I did not run a nandroid before I made the change.
Now, I can dirty flash my rom on top, or go back to a nandroid from a few days ago, but I'd really just like to recover and go on my merry way. And maybe learn something in the process.
Only thing is, I can't figure out how to access the phone other than the External SD card through CWM.
Can I mount the internal /system and access through USB? Is there some facility to copy a file from one point to another? Any other methods? I guess the phone has to be up to run ADB, right?
I don't know how to generate a flashable zip but I could extract the original version of the file from the original rom. I assume that its non trivial to create a flashable zip, but maybe someone can comment? It looks like there is signing and certificates involved..
thanks for any ideas
Click to expand...
Click to collapse
this is why i hate it when people make those guides.
messing with the vold.fstab is dangerous (even though its only a few lines) if your trying to recover your data, give up. its not going to happen. (sorry)
when you edit the vold.fstab it messed up the partitions on your internal SD card and most likely did the equivalent of wiped your /system partition. (or another important one.) your actually lucky it did not completely brick your phone.
your post was a little vague, but if you can, just restore an older nandroid, or wipe everything and install another ROM. (you can try dirty flashing but i dont think itll work)
if you cannot access CWM, then follow the steps in This guide. it should get you back up on your feet. after you follow that guide flash a gingerbread ROM (any gingerbread rom will do fine) then you can reboot and flash any ROM you want. (it needs this to fix a quirk in that script)
Hope you get it fixed
EDIT: re read your post, if your feeling adventurous and want to give it a shot, boot into CWM and connect it via usb. you can now get into an ADB shell on your phone by typing 'adb shell' if you have adb all setup and working. (im working from memory here so dont quote me on any of this)
now, you should be able to access your /system folder from that shell. be very careful though, i dont have much experience right here, and if i remember correctly you might not be in the full root directory yet)
if you can get into it try replacing your vold.fstab with a stock one,
if you dont have a stock one lying around, make a nandroid of the current state of the rom, then flash another rom, pull the vold.fstab, then re-restore back to the broken one and restore it (id upload mine but my phone is OOC right now )
after that just reboot and hope it resolves itself, if not then just follow my advice above
and keep that guide i linked to handy, messing around in CWM has the ability to brick your phone, if it does, then just follow that guide.
Klathmon said:
this is why i hate it when people make those guides.
messing with the vold.fstab is dangerous (even though its only a few lines) if your trying to recover your data, give up. its not going to happen. (sorry)
when you edit the vold.fstab it messed up the partitions on your internal SD card and most likely did the equivalent of wiped your /system partition. (or another important one.) your actually lucky it did not completely brick your phone.
your post was a little vague, but if you can, just restore an older nandroid, or wipe everything and install another ROM.
if you cannot access CWM, then follow the steps in This guide. it should get you back up on your feet. after you follow that guide flash a gingerbread ROM (any gingerbread rom will do fine) then you can reboot and flash any ROM you want. (it needs this to fix a quirk in that script)
Hope you get it fixed
Click to expand...
Click to collapse
How bout adb and pushing the file back in? Or cant you access the phone via adb?
Sent from my LG-P970 using XDA
N00BY0815 said:
How bout adb and pushing the file back in? Or cant you access the phone via adb?
Sent from my LG-P970 using XDA
Click to expand...
Click to collapse
re read your post and updated my last post right after you posted
after dealing with noobies all day, i forget sometimes people want to try big things
Thanks guys. The info I was missing was there's no special trick to attaching adb while in CWM! Just plug in!
My phone is back up and running and partitions are fine as far as I can see after just booting up.
Hi there! I messed up with the vold.fstab filfe on my tablet – I replaced it with a downloaded file with the intention to transfer apps to my external SD card.
Now my tablet is only showing the startup logo and won’t continue loading. I can access recovery mode. Now I want to restore the original vold.fstab file.
My questions:
1. Using the Android SDK, the file explorer does not show any files, though my tablet is recognized.
2. Using adb push, it yields an error: permission denied, how to successfully push the original vold.fstab and replace the existing vold.fstab?
3. If I dump an image of my tablet and edit the dumped image, would this be easier compared to the steps above?
Thanks!
http://forum.xda-developers.com/showthread.php?t=1646108
Try this.
If this doesn't help you should ask in the section for your tablet to get more specific advice.
TwitchyEye said:
http://forum.xda-developers.com/showthread.php?t=1646108
Try this.
If this doesn't help you should ask in the section for your tablet to get more specific advice.
Click to expand...
Click to collapse
Thanks, I will try it later when I got home. My tablet is not found here. I have a Skyworth S71(3G) with RK3066 chipset.
BryanF said:
Thanks, I will try it later when I got home. My tablet is not found here. I have a Skyworth S71(3G) with RK3066 chipset.
Click to expand...
Click to collapse
You need to do an adb remount before you can push. Was it rooted before?
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
Mansa_noob, yes, my tablet is rooted. I followed some instructions about adb but had an error saying access denied, and also no files are displayed at file explorer. See my posts above. I also mounted it successfully. I will post some sreenshots later.
Please if you have some instructions, I am willing to try.
---------- Post added at 07:06 AM ---------- Previous post was at 07:02 AM ----------
TwitchyEye said:
http://forum.xda-developers.com/showthread.php?t=1646108
Try this.
If this doesn't help you should ask in the section for your tablet to get more specific advice.
Click to expand...
Click to collapse
Hi twitchyEye, it did not work. It attemps to install (using the install update from ext sd card) but then says installation aborted.
Any more suggestions? Thanks
What recovery are you using? I suck with adb so I got nothing on that front.
It was the stock recovery from my Tablet. I don't have it on hand right now, I will post later. The chipset is RK3066. My problem is my tablet has no official support on the internet (maybe becaue it's still new). Model is Skyworth S71(3G).
I see. Yeah this is over my head man. I thought for sure you were running a custom recovery and it was an easy answer. I'm actually struggling right now with adb myself with a similar issue something about permissions whenever I try to do anything to my phone. So I guess right now would be a perfect time for somebody to chime in with a smarter answer!
TwitchyEye said:
I see. Yeah this is over my head man. I thought for sure you were running a custom recovery and it was an easy answer. I'm actually struggling right now with adb myself with a similar issue something about permissions whenever I try to do anything to my phone. So I guess right now would be a perfect time for somebody to chime in with a smarter answer!
Click to expand...
Click to collapse
Are you doing adb remount and still getting permission denied?
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
mansa_noob said:
Are you doing adb remount and still getting permission denied?
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
Click to expand...
Click to collapse
Yes, I did adb remount and still access denied
BryanF said:
Yes, I did adb remount and still access denied
Click to expand...
Click to collapse
This is strange. A properly rooted phone would adb remount to r/w system. Something is fishy. Is it rooted+
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
mansa_noob said:
This is strange. A properly rooted phone would adb remount to r/w system. Something is fishy. Is it rooted+
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
Click to expand...
Click to collapse
I am sure it is rooted, because I downloaded an application from Google play to check it it is rooted or not. It is really rooted. I alvo confirmed this as I can now fully backup and restore my apps using Titanium backup before the tablet is messed up.
BryanF said:
I am sure it is rooted, because I downloaded an application from Google play to check it it is rooted or not. It is really rooted. I alvo confirmed this as I can now fully backup and restore my apps using Titanium backup before the tablet is messed up.
Click to expand...
Click to collapse
OK. Odd or not, it is what it is. Is it possible for you to load a custom recovery?
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
mansa_noob said:
OK. Odd or not, it is what it is. Is it possible for you to load a custom recovery?
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
Click to expand...
Click to collapse
I want to try, but the stock recovery is my last hold as I have no stock ROM. If I overwrite the stock ROM, I cannot reinstall it as I don't have a copy of it.
So why not flash cwm with nvflash and then make a backup of your current stock rom? I did exactly that.
Sent from my LG-P999 using xda premium
I need a stock recovery image for the Coby Kyros 7022 build 20120106 (previous builds will not work). I tried to flash clockworkmod recovery on my tablet without making a backup of the stock image, only to find that cwm recovery doesn't work with the new build of my tablet. Can anyone give me a stock recovery image for this tablet? Any help would be greatly appreciated!
Same Problem.
I have yet to find a solution since 02/2012.
Maybe you can try this?
stock recovery image for Coby 7022
same probleme right here
Coby 7022 20120106 build
I ended up with no recovery after trying to install clockwork. Recovery didn't work (it bypassed recovery when using the proper keys) and I had no good backup. Flashing older firmware in the 11 2011 timeframe led to boot loops. I've not been able to find a stock Coby 7022 firmware from 20120106. However, I did find another post here regarding a different tablet using the same tcc8803 chipset with the same build date. dub dub dub dxtremeDOTcom.au/forum/viewforum.php?f=15 (remove spaces insert correct www etc...) So I gave it a try. I'm actually able to get the 7022 booted using this firmware and system but the touchscreen is not working, so I'm guessing that driver is not exactly correct.
Completely a noob but wanting to learn. BTW I did not use the FWTool as I read posts this kills the TS
So my ask is, does anyone know of a way to get the drivers for the 7022 build dated 20120106?
---------- Post added at 09:58 AM ---------- Previous post was at 09:51 AM ----------
coolhof said:
Maybe you can try this?
[dub dub dub androidtablets.netSLASHforumSLASHcoby-generation-2/28212-7022-help-cant-restore-2.html#post183680"]stock recovery image for Coby 7022[/URL]
Click to expand...
Click to collapse
This restore didn't work on my system. The 7022 from 20120106 seems to be a rare animal and little info on it yet.
Same problem here, I tried to flash a previous CWM/Stock Recovery and nothing... just bootloop when I try to enter recovery mode. So, does anyone have the stock recovery for the 20120106 build yet? Thank you in advance for the one who can help
20120106 stock lk.rom & MTD file
MostroXxX said:
Same problem here, I tried to flash a previous CWM/Stock Recovery and nothing... just bootloop when I try to enter recovery mode. So, does anyone have the stock recovery for the 20120106 build yet? Thank you in advance for the one who can help
Click to expand...
Click to collapse
After reading a bit, it seems what we need are two files that could be copied off a working stock machine of the proper build date or later. In our case on or after 20120106. The problem for me seems to be the lk.rom file. The ROM I used for the DExtreme pad boots but no touch screen function due to the DExtreme being a 5 touch capacitance screen and the Kyros 7022 being but 2.
There may be other problems with the DExtreme files like the camera being different or even the network adapter but no way of telling without the stock boot file. Anyway, I've resigned myself. My 7022 is a paper weight until I find the stock files.
If anyone comes across this looking to root and clockwork mod your 7022 and it's build date is on or after Jan 6 2012, please stop and use ADB to pull a copy of your stock OS off it first. Not only will you be able to help us out, but you'll be able to restore when things go horribly wrong.
chiefcrewdog said:
After reading a bit, it seems what we need are two files that could be copied off a working stock machine of the proper build date or later. In our case on or after 20120106. The problem for me seems to be the lk.rom file. The ROM I used for the DExtreme pad boots but no touch screen function due to the DExtreme being a 5 touch capacitance screen and the Kyros 7022 being but 2.
There may be other problems with the DExtreme files like the camera being different or even the network adapter but no way of telling without the stock boot file. Anyway, I've resigned myself. My 7022 is a paper weight until I find the stock files.
If anyone comes across this looking to root and clockwork mod your 7022 and it's build date is on or after Jan 6 2012, please stop and use ADB to pull a copy of your stock OS off it first. Not only will you be able to help us out, but you'll be able to restore when things go horribly wrong.
Click to expand...
Click to collapse
Well, I'm expecting another 7022 to arrive next week (kind of a late Mother's day gift), I assume it will be same build, so, I'll try to pull a copy of that unit and see if I can restore it on te semi-dead one. I will post again when it arrives to tell if it worked (or if I have two bricks xD). If it works, I'll upload a copy.
Stock 20120106 Kyros ROM
MostroXxX said:
Well, I'm expecting another 7022 to arrive next week (kind of a late Mother's day gift), I assume it will be same build, so, I'll try to pull a copy of that unit and see if I can restore it on te semi-dead one. I will post again when it arrives to tell if it worked (or if I have two bricks xD). If it works, I'll upload a copy.
Click to expand...
Click to collapse
Any Luck?
chiefcrewdog said:
Any Luck?
Click to expand...
Click to collapse
Neh, It's an international shipment and got delayed. I was supposed to receive it today, but now I'll have to wait 'til monday or tuesday. I'll post when I get them to tell if it worked.
Edit: what I could do was root it. It was quite easy using SuperOneClick, but still no recovery...
chiefcrewdog said:
Any Luck?
Click to expand...
Click to collapse
ehmmm... BAD luck the one that arrived is a previous build (September 2011).
So, for now, we are pretty much screwed :/
I just got a 7022 that has a build date of 20120106. I am new to android so I have no idea what I am doing but if someone gives me step by step instructions I can try to get it off the tablet for you. Good thing I found this forum, I was about to try and root it.
nduke416 said:
I just got a 7022 that has a build date of 20120106. I am new to android so I have no idea what I am doing but if someone gives me step by step instructions I can try to get it off the tablet for you. Good thing I found this forum, I was about to try and root it.
Click to expand...
Click to collapse
That's great!
first, is it rooted, or have you done any MOD?
---------- Post added at 01:05 AM ---------- Previous post was at 12:21 AM ----------
nduke416 said:
I just got a 7022 that has a build date of 20120106. I am new to android so I have no idea what I am doing but if someone gives me step by step instructions I can try to get it off the tablet for you. Good thing I found this forum, I was about to try and root it.
Click to expand...
Click to collapse
1) You need to install the Android SDK, instructions can be found HERE, but basically you need to:
-) Download the .exe and install it
-) Locate the folder where you installed it and run as administrator “SDK Manager.exe”
-) Check (if unchecked) the boxes for SDK Tools, SDK Platform Tools and Google USB Driver Package. You can check any others if you want, but for now, you only need those.
2) You (may) need the specific drivers for the device. You can use the Motorola drivers, which work very nice with the Cobys, you can install the drivers from HERE. Just download and install.
3) You need to root your device, for that, I recommend using SuperOneClick, which can be found HERE. Too root your device:
-) Make sure you have “USB Debugging mode” activated. In your tablet, go to settings -> Applications -> Development and check (if unchecked) the USB Debugging mode.
-) Connect your device to your PC, if it’s the first time you connect it, you need to wait a little while the drivers get configured.
-) When your device is connected and correctly configured, run SuperOneClick as administrator, and click on “Root”. Now wait a little while it gets rooted.
4) Last step, backup recovery image. For this, you’ll need a terminal emulator. You can download “Android Terminal Emulator” from 1mobile.com or any other app market. To do the backup:
-) Open the terminal emulator on your tablet.
-) Request SuperUser Permissions, to do this, write
Code:
su
and hit enter/return, you’ll be asked if you want to grant SuperUser rights to the app Android Terminal Emulator, click “Allow”.
-) Write this line and hit enter/return:
Code:
dd if=/dev/mtd/mtd6 of=/sdcard/recovery.img bs=4096
-) Now, a file named “recovery.img” should be automatically created on your /sdcard folder. THAT, my friend, is the file we so desperately need to revive our tablets, now zip it and uploaded to any server. (Please )
Now that you are rooted, you can do things such as installing the Google apps. There are a lot of tutorials over the internet, but, let me know if you have any trouble so I can help you
WARNING: Don’t, I repeat DON’T try to install ClockWorkMod using ANY of the tutorials found over the internet. Those tutorials work ONLY for builds previous to 20110106, and if you try to do it on your device, you are going to semi-brick it (just like we did xD).
I just got it as a replacement under warranty today and have not done anything to it. I am busy studying for finals now but when I get a chance(prob friday morning) I will follow the steps and upload the recovery.img file
nduke416 said:
I just got it as a replacement under warranty today and have not done anything to it. I am busy studying for finals now but when I get a chance(prob friday morning) I will follow the steps and upload the recovery.img file
Click to expand...
Click to collapse
Well, no problem. If you do that we'll be EXTREMELY thankful
This might be a stupid question but bear with me, I don't know anything about this. Does personal info get stored on the recovery.ing file? Should I remove apps like the amazon app store or other ones that I have to log in with?
Old build no bueno...
MostroXxX said:
ehmmm... BAD luck the one that arrived is a previous build (September 2011).
So, for now, we are pretty much screwed :/
Click to expand...
Click to collapse
Bleh
---------- Post added at 04:51 PM ---------- Previous post was at 04:46 PM ----------
MostroXxX said:
That's great!
first, is it rooted, or have you done any MOD?
---------- Post added at 01:05 AM ---------- Previous post was at 12:21 AM ----------
1) You need to install the Android SDK, instructions can be found HERE, but basically you need to:
-) Download the .exe and install it
-) Locate the folder where you installed it and run as administrator “SDK Manager.exe”
-) Check (if unchecked) the boxes for SDK Tools, SDK Platform Tools and Google USB Driver Package. You can check any others if you want, but for now, you only need those.
2) You (may) need the specific drivers for the device. You can use the Motorola drivers, which work very nice with the Cobys, you can install the drivers from HERE. Just download and install.
3) You need to root your device, for that, I recommend using SuperOneClick, which can be found HERE. Too root your device:
-) Make sure you have “USB Debugging mode” activated. In your tablet, go to settings -> Applications -> Development and check (if unchecked) the USB Debugging mode.
-) Connect your device to your PC, if it’s the first time you connect it, you need to wait a little while the drivers get configured.
-) When your device is connected and correctly configured, run SuperOneClick as administrator, and click on “Root”. Now wait a little while it gets rooted.
4) Last step, backup recovery image. For this, you’ll need a terminal emulator. You can download “Android Terminal Emulator” from 1mobile.com or any other app market. To do the backup:
-) Open the terminal emulator on your tablet.
-) Request SuperUser Permissions, to do this, write
Code:
su
and hit enter/return, you’ll be asked if you want to grant SuperUser rights to the app Android Terminal Emulator, click “Allow”.
-) Write this line and hit enter/return:
Code:
dd if=/dev/mtd/mtd6 of=/sdcard/recovery.img bs=4096
-) Now, a file named “recovery.img” should be automatically created on your /sdcard folder. THAT, my friend, is the file we so desperately need to revive our tablets, now zip it and uploaded to any server. (Please )
Now that you are rooted, you can do things such as installing the Google apps. There are a lot of tutorials over the internet, but, let me know if you have any trouble so I can help you
WARNING: Don’t, I repeat DON’T try to install ClockWorkMod using ANY of the tutorials found over the internet. Those tutorials work ONLY for builds previous to 20110106, and if you try to do it on your device, you are going to semi-brick it (just like we did xD).
Click to expand...
Click to collapse
nduke416 said:
This might be a stupid question but bear with me, I don't know anything about this. Does personal info get stored on the recovery.ing file? Should I remove apps like the amazon app store or other ones that I have to log in with?
Click to expand...
Click to collapse
Will the recovery img work or do we need complete lk.rom and mtds.rom? I was thinking the latter/ You can use ADB to get these files? Still pretty much a noob myself, otherwise I wouldn't be using my 7022 as a coaster.
well I think I did everything right. let me know if this didn't work. link to recovery.img below
depositfiles.com/files/tc8gfx8hr
chiefcrewdog said:
Bleh
---------- Post added at 04:51 PM ---------- Previous post was at 04:46 PM ----------
Will the recovery img work or do we need complete lk.rom and mtds.rom? I was thinking the latter/ You can use ADB to get these files? Still pretty much a noob myself, otherwise I wouldn't be using my 7022 as a coaster.
Click to expand...
Click to collapse
For the recovery, no. You just need to reflash the stock recovery using fastboot. Let's see if this works...
---------- Post added at 01:04 AM ---------- Previous post was at 01:01 AM ----------
nduke416 said:
This might be a stupid question but bear with me, I don't know anything about this. Does personal info get stored on the recovery.ing file? Should I remove apps like the amazon app store or other ones that I have to log in with?
Click to expand...
Click to collapse
Negative, the recovery.img file contains only information about the recovery partition, which is used mostly to restor the tablet to factory defaults
---------- Post added at 01:16 AM ---------- Previous post was at 01:04 AM ----------
IT WORKS!!!! IT FREAKING WORKS!!!
Dude, nduke416, thank you VERY MUCH. You have definitely provided a solution no one did. So, again thank you very much!!!!
for chiefcrewdog:
to reflash it, you just need to enter fastboot mode in your tablet (power + vol down), copy the recovery.img file to your platform-tools directory on your android sdk folder and from there on a cmd:
Code:
fastboot flash recovery recovery.img
and that's it, you have your recovery back on your 7022!!
nduke416 said:
well I think I did everything right. let me know if this didn't work. link to recovery.img below
depositfiles.com/files/tc8gfx8hr
Click to expand...
Click to collapse
Man, is there a possibility you could upload a backup of the boot.img too? the procedure is the same, just changing the dd command to:
Code:
dd if=/dev/mtd/mtd0 of=/sdcard/boot.img bs=4096
I could really appreciate it, that way there is the possibility to have custom ROMs on our builds
Thank you!
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Download links
Last version can be found here:
Asus Transformer Prime TF700T (tf700t)
http://goo.im/devs/philz_touch/CWM_Advanced_Edition
Click to expand...
Click to collapse
Phil3759 said:
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Download links
Last version can be found here:
Click to expand...
Click to collapse
Will give it a test run.
After using this on my phone, I'm excited to see this for my tablet as well. So far the only thing that I have found not working was the mounting the SD card through the recovery doesn't seem to work, it was connected to the computer when I mounted it but my computer couldn't see it. It also seems that the recovery is a bit slower on my tablet than on my phone, d2spr, though it might just be the tablet itself.
Frostbiter said:
After using this on my phone, I'm excited to see this for my tablet as well. So far the only thing that I have found not working was the mounting the SD card through the recovery doesn't seem to work, it was connected to the computer when I mounted it but my computer couldn't see it. It also seems that the recovery is a bit slower on my tablet than on my phone, d2spr, though it might just be the tablet itself.
Click to expand...
Click to collapse
mount usb storage relies on device tree, kernel and rc files
Without the device or repo maintainer fixing it, it is hard
Phil3759 said:
mount usb storage relies on device tree, kernel and rc files
Without the device or repo maintainer fixing it, it is hard
Click to expand...
Click to collapse
Ah okay, well so far that's the only bug in the recovery I noticed, and I wouldn't have even noticed it if I had remembered to put the kitkat gapps on my device before wiping it. Haha
Really nice job though, I'm glad you brought it over since I've had issues with plain cwm in the past and twrp doesn't seem to be getting updated at the moment I thank you for bringing this to my tablet.
Thank you so much for this nice tool and give us choices. I flashed it and the UI is just beautiful. Now I'll go test all its functions.
:good:
Nice
Nice recovery, It the best Ive ever come across. I Dev for CMB ROMS, I have made a flashable zip, so you can flash it from your current recovery.... I have this posted in the Download tab of my ROM forum... Its not my recovery, all credits will be given to Phil3759 It can be linked and given away as any open source recovery, I only say this on the ok of Phil3759, If he would like me to remove it, I will... Untill I here from him.. Here is a nice and easy way to install the best recovery to date for our beloved 700... Thx as always lj
lj50036 said:
Nice recovery, It the best Ive ever come across. I Dev for CMB ROMS, I have made a flashable zip, so you can flash it from your current recovery.... I have this posted in the Download tab of my ROM forum... Its not my recovery, all credits will be given to Phil3759 It can be linked and given away as any open source recovery, I only say this on the ok of Phil3759, If he would like me to remove it, I will... Untill I here from him.. Here is a nice and easy way to install the best recovery to date for our beloved 700... Thx as always lj
Click to expand...
Click to collapse
Just tried this out using your zip to install. Works great. Recovery is nice and easy to navigate. Thanks to Phil and LJ.
i feel a bit silly but the file in the tf700t download folder is a .img and i can't figure out how to flash it...
Thank you so much Philz!
I was dreaming about this, is not a joke, I've been using your amazing recovery in my jfltexx since always because it's the best.
I would be glad to help you.
Lord_Towers said:
i feel a bit silly but the file in the tf700t download folder is a .img and i can't figure out how to flash it...
Click to expand...
Click to collapse
Write this in the terminal:
su
dd if=/sdcard/download/philz_touch_6.08.9-tf700t.img of=/dev/block/mmcblk0p4
Reboot your tablet and that's it.
You could rename as you wish, also, I'm running CM 11 so the file directory might be different.
Or you can flash the zip that lj made.
Sent from my ASUS Transformer Pad TF700T using Tapatalk
soyusado said:
Write this in the terminal:
su
dd if=/sdcard/download/philz_touch_6.08.9-tf700t.img of=/dev/block/mmcblk0p4
Reboot your tablet and that's it.
You could rename as you wish, also, I'm running CM 11 so the file directory might be different.
Or you can flash the zip that lj made.
Sent from my ASUS Transformer Pad TF700T using Tapatalk
Click to expand...
Click to collapse
Thanks, i used the zip. I didn't even realize there were download tabs across the individual forums.
Lord_Towers said:
Thanks, i used the zip. I didn't even realize there were download tabs across the individual forums.
Click to expand...
Click to collapse
LOL, i remember when i discovered that too face palm.
Is Philz touch coming to a 701t Near you?
HI.... can someone explain how to get to the flashable version ? I don't understand what is meant by " I have this posted in the Download tab of my ROM forum "
Thanks
---------- Post added at 07:51 PM ---------- Previous post was at 07:29 PM ----------
Nevermind... I found it
SlappyWag said:
HI.... can someone explain how to get to the flashable version ? I don't understand what is meant by " I have this posted in the Download tab of my ROM forum "
Thanks
---------- Post added at 07:51 PM ---------- Previous post was at 07:29 PM ----------
Nevermind... I found it
Click to expand...
Click to collapse
Open Terminal Emulator and enter this command
su
dd if=/storage/sdcard0/download/philz_touch_6.19.3-tf700t.img of=/dev/block/mmcblk0p4
Link is dead !
Another link ?
bump
Anyone got another link to this please?