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?
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!
I have assembled a rooting CD for Droid 2 Global phones that have taken the .629 update.
I got the info on how to do this from phifc's post at
http://rootzwiki.com/topic/29930-new-root-method-for-stock-234-621622-found-droid2-r2d2/
so all credit for this method go to phifc, djrbliss, and the others who developed the method.
I have simply taken the method, and assembled the tools for the Droid 2 Global.
Credit for the idea behind the CD method should go to 1KDS, as I have mostly patterned this CD after his method.
Credit should also go to Skrilax_CZ, as without his Motorola Android Firmware (De)packer, we wouldn't be able to have a CD under 50 meg.
I have tested this CD on my phone, and found it to work properly, but I can't guarantee that it will work for others. Others have also found it to work, but I can't guarantee you will have the same results.
You are welcome to try it, and I hope it is helpful to someone, but as with all modifications, you do so at your own risk.
Instructions for using this CD.
Download and burn this image file to CD. (or create bootable USB)
It might be a good idea to do a factory reset before starting this process, but you might be ok without it. My phone had already been rooted, so I had to sbf it back to stock, in order to test the CD, so I have only tried it after a factory reset.
1 Enable USB debugging on the phone,
2 Boot computer off of this CD
3 Hook up phone to computer (phone needs to be on at this point)
4 Start the root process by selecting option 1
5 When it says on the screen that phone needs placed in bootloader, (almost right away, as it only needs to send 1 command before placing in bootloader) power off the phone, and put it in bootloader by holding the up arrow on the keyboard of the phone while powering on.
6 when in bootloader and hooked up to the phone, press enter on the computer to proceed, a preinstall image will be flashed to the phone, providing the exploit that will root the phone.
7 When it has flashed, the phone should reboot. If it hangs when booting, unplug phone, remove battery, replace battery and power back on. When powered on, hook up cable again, and the process will continue (it will immediately reboot again)
8 When the phone reboots, ADB should be root, so it will push the necessary files to the phone, and reboot the phone again. Per Morlok8k, cache should be wiped to avoid bootloop problems, so the phone will be rebooted into Recovery.
9 You will have to press both volume buttons to enter recovery, where you should wipe cache partition and reboot.
If all went well, your phone should be rooted.
If you try it, please verify if it works for you, or gives you trouble.
Hope this helps someone.
I updated the CD (mainly just made it a bit smaller) and uploaded it to Mediafire
http://www.mediafire.com/?394ha4dzjtyqpqb
I also uploaded it to rapidshare,
https://rapidshare.com/files/1105339167/D2G_629-Root_CD-updated.iso
the md5 for the updated CD is
84ff5a572e98c3eb366cc6fec13f99d5
I also previously forgot to mention that this method works fine off a bootable usb drive, a CD is not necessary. I use Unetbootin to create the bootable usb, and it works well for me.
Update
Since there is now a direct rooting method of .629 available, I also put it together with an EzSbf style CD of the full .629 SBF.
One item of note with this CD, it does require at least 1GB of RAM in order to work properly. Also, if you only have 1GB of memory, and you need to both SBF and root your phone, it will be necessary to reboot the computer after flashing the .629 SBF. If you are unsure of the amount of RAM that you have, go ahead and reboot to be on the safe side.
The CD is available at
https://rapidshare.com/files/2650843793/D2G_4.5.629_SBF-and-RootCD.iso
and the MD5 is
579d7d5095fc2560205033456db150a2
So there are two CD's available, both of which work to root .629. The second CD should also work as a recovery CD, as it contains the full .629 SBF
There is also a mirror of these files provided by sd_shadow at
https://docs.google.com/document/d/1-Oj1a1wNZKhZMPUqU_6KzzYzQJ2RKzvvumTx-41f3h4/edit
Cant wait to try this out.
I got a Gnex so since I had to replace my D2G due to a messed up keyboard and got a post 629 back I havn't really messed with it. Mainly just becuase I havn't had time. But I am definently going to have to try this. BTW, I have two D2Gs that I am looking to sell. Thinking I will put them on Swappa. Both are Verizon insurance replacements but becuase of that they are in perfect shape. One is white and one is blue. I hate to just have them sitting here when someone could enjoy them, so hit me up if you want to make a offer. Im pretty open price wise. Not looking to make a killing since they are older devices. I will also throw in a extra battery, two car docks, screen protectors, a couple chargers and....I think thats it.
Worked perfect but I can't figure out how to make a nandroid. Wanna make one so I have a reference point so I can take out bloat. Any help would be great.
sent from thunda down unda
to make a nandroid backup, you need to install Droid 2 bootstrap recovery
It looks like the download isn't available anymore, could anyone please re-upload it? Thanks.
Which file? I think ad_shadow has mirrored the files in another thread.
Sent from my Inspire 4G using Tapatalk 2
bhigham said:
Which file? I think ad_shadow has mirrored the files in another thread.
Sent from my Inspire 4G using Tapatalk 2
Click to expand...
Click to collapse
The one at the end of the post, but I think I found the other thread, thanks for the quick reply though!
mirrors can be found here
magic md5 root for d2, d2g, dx, & dx2
https://docs.google.com/document/d/1-Oj1a1wNZKhZMPUqU_6KzzYzQJ2RKzvvumTx-41f3h4/edit
Sent from my XT862 using xda premium
Thanks for the ISO bhigham, worked like a charm.
What I am having trouble figuring out is how to install cyanogenmod post root. I am following the instructions in the wiki, can't link due to new account but it is the Install_CM_for_droid2we guide.
And when I get down to the line,
Code:
adb push su /system/xbin/
I get a permission denied error.
See while my phone is rooted, the default shell is the non-root shell ('$' vs '#'). Apparently the old root method would give you a default root shell.
Anyone have any ideas how to precede here?
i think root failed, because adb shell should be root
retry
is phone rebooting to android os, twice after flashing in bootloader, or rebooting to bootloader?
if it's rebooting to bootloader, pull usb cable during reboot, reconnect after phone has completed reboot
Sent from my XT862 using xda premium
---------- Post added at 09:35 AM ---------- Previous post was at 09:22 AM ----------
See while my phone is rooted
Click to expand...
Click to collapse
not sure how you could know that, without superuser
Sorry, the vital information I left out is that when I type 'su' I can elevate to the root prompt. I assumed this means my phone was correctly rooted.
The phone did the double reboot into the Android OS and everything looked like it was working correctly.
if phone is rooted, you could try
pete's root tools or motofail, to push superuser
links in my list
sd_shadow's [Collection] of Links: FAQs, Guides, Rooting, SBFs, ROMs... - Google Docs
I actually have the superuser app on my phone already. The Root CD in the OP must have added it.
So if I got to the next step in the wiki, pushing the recovery bootstrap onto the phone,
Code:
adb push bootstrap-1.0.0.5-droid2.apk /system/app/
At first I get a read only file system error, which goes away away when I remount /system using,
Code:
mount -o rw,remount /dev/block/mmcblk1p21 /system
But then I get a permission denied erro when running the push. Again I think this is because the default shell does not have root.
Is there someway to evaluate the privileges of the push command?
i have always found the easiest way to get apks from pc to phone, is
connect phone to pc in mass storage mode, drag apk to sd card
change phone to charge only, use file manager or root explorer
find apk tap on it, select install
---------- Post added at 05:04 PM ---------- Previous post was at 05:01 PM ----------
app will not be a system app, but does not need to be, and on D2G I never installed it as a system app
Ah that sounds like a simpler approach. I just realized I don't even have a sd card on this phone, the person who gave it to me apparently removed it. So I just ordered one for the phone as I don't think it would very useful without one.
ok, not sure why you can't push it as a system app
if you have 3g or wifi available, download apk directly to phone
then use file manager or root explorer
find apk (should be in download folder) tap on it, select install
---------- Post added at 06:13 PM ---------- Previous post was at 05:50 PM ----------
guess you can't download without sd card
So I got my SD card and tried installing cyanogenmod and got stuck on the Motorola screen. Not sure what I did wrong but I am reflashing the SBF to try again.
what file name?
where did you find it?
Sent from my XT862 using xda premium
I can't link due to my newness but it was kind of roundabout where I installed the droid 2 recovery bootstrap but then couldn't figure out how to get into clockwork recovery, so I went on the play store, downloaded clockwork from there and reboot into recover and installed the cyanogen mod from the official site plus the google apps zip. Then I wiped data and cache and rebooted but got stuck on the Motorola logo.
In the process of trying again. This time I got the recovery bootstrap installed and was about to reboot directly into clockwork with no play store needed. I was going to wipe data/factory and then install from zip. I don't see the point in creating a backup as I could find no way to restore.
official cm7 is still flashed on 2.2/2.4.33
---------- Post added at 08:15 PM ---------- Previous post was at 08:14 PM ----------
try Pooka-CM4D2G-GB-20120519 and Pooka-CM4D2G-GB-20120516r
I recently acquired a Photon Q LTE after being an Epic 4G user for years. I've flashed and rooted and beat that Epic 4G to bits over the years, but I can't seem to get CWM installed on this device for the life of me.
I've verified I've unlocked the bootloader and followed the directions in shabby's thread (http://forum.xda-developers.com/showthread.php?t=1856480) and on a couple other sites (http://www.andromods.com/basic-how-...r-user-install-cwm-recovery-photon-q-lte.html and http://www.androidegis.com/how-to/root-and-install-clockworkmod-recovery-on-motorola-photon-q-4g/), but it never seems like CWM wants to stick. Fastboot sends the file fine and says it writes it, but whenever I try to boot into recovery, I get the old school factory recovery with the Red Triangle and the Android System Recovery (3e) header, which is the factory bootloader (right?). Obviously SU isn't going to load in there.
My wife was playing with my new phone before I had a chance to do so (it was a gift), and I think she ran the latest OTA updates before I had a chance to even touch it. Looks like I'm running SW Version 77.8.10.XT897.Sprint.en.US and Android Version 4.0.4, so I don't know if this has been tested with that or if I'll need to revert to a lower version, root, and then upgrade.
Any help would be greatly appreciated.
Thanks!
sometimes stock ROMs have a file in the system folder called recovery-from-boot, which reinstalls stock recovery on boot. if you have flashed SU, try looking in /system, and if that file is there, you can rename it to recovery-from-boot-bak, and that should disable it.
yogi2010 said:
sometimes stock ROMs have a file in the system folder called recovery-from-boot, which reinstalls stock recovery on boot. if you have flashed SU, try looking in /system, and if that file is there, you can rename it to recovery-from-boot-bak, and that should disable it.
Click to expand...
Click to collapse
I haven't been able to get SU installed as I can't get CWM installed. Is there another way to push SU to the phone without CWM?
Running terminal emulator, I can see there's a recovery-from-boot.p file /system, which is probably my issue. So basically, I need to get SU on there somehow to kill it, unless there's a way to kill that file with desktop adb or something.
orty said:
I haven't been able to get SU installed as I can't get CWM installed. Is there another way to push SU to the phone without CWM?
Running terminal emulator, I can see there's a recovery-from-boot.p file /system, which is probably my issue. So basically, I need to get SU on there somehow to kill it, unless there's a way to kill that file with desktop adb or something.
Click to expand...
Click to collapse
ok, i see. damn that's odd, because i haven't seen anyone run into this. i'm trying to think if there
is a way to boot straight into recovery from the bootloader, without booting up the system. i don't think you will be able to modify the file in /system without SU.
---------- Post added at 09:15 PM ---------- Previous post was at 09:11 PM ----------
come to think of it, i think there is a rootkit somewhere here that will install SU without flashing recovery. can't find it atm tho... but i believe it is said to still work on your software version..
actually if i remember correctly, i think it might be Dan Rosenberg's Motofail2Go exploit:
http://forum.xda-developers.com/showthread.php?t=1940594
the other thing you might try is flashing TWRP recovery instead of CWM. i am not sure but maybe TWRP automatically disables the recovery-from-boot file. i used TWRP and i see my file is already renamed and i never consciously did that!
I'll try to get a few minutes tonight and give that a whirl. Will report back as soon as I can.
Thanks!
orty said:
I'll try to get a few minutes tonight and give that a whirl. Will report back as soon as I can.
Thanks!
Click to expand...
Click to collapse
i just posted at the same time as you, so if you didn't see it, perhaps TWRP recovery is worth trying too!
Motofail2go got SU installed, which allowed me to rename that file. Then was able to follow the procedure to install CWM just fine.
Thanks much for the help!
Great, glad you got it working!
Did CWM not stick on my Photon Q ?
What is the key sequence to boot into CWM on a motorola photon Q ? I did an motorola upgrade before I tried any of this so my version nmbers are the same as orty.
SW Version 77.8.10.XT897.Sprint.en.US and Android Version 4.0.4
Here's how it went. - The bootloader unlock seemed to work fine. Things were a little hairy with the CMW install. I am doing this on ubuntu and much like orty I had to make the best guess from various posts. Since I'm not sure of the key sequence to boot for CWM - you can bet I was not holding any buttons when the thing rebooted after downloading CWM. I looked around for a while before I found anything about the key sequence and now if I try a boot holding power & volume up I get an dead android with an red triangle ! in his tummy. I gather this means failure. I did however manage to install Superuser from ChainsDD. Does having Superuser installed mean anything about whether I have CWM installed or not? I am confused! From this post I gather I should try the CMW install again and hold the buttons when it reboots? What do you see to indicate you are in CWM? Some sort of menu?
If I knew how I would try and use the installed SU to look in /system to see if there are any of the mentioned files.
Can somebody give me some clues on next steps I can try at home tonight. Much appreciated!!
penguinpal said:
What is the key sequence to boot into CWM on a motorola photon Q ? I did an motorola upgrade before I tried any of this so my version nmbers are the same as orty.
SW Version 77.8.10.XT897.Sprint.en.US and Android Version 4.0.4
Here's how it went. - The bootloader unlock seemed to work fine. Things were a little hairy with the CMW install. I am doing this on ubuntu and much like orty I had to make the best guess from various posts. Since I'm not sure of the key sequence to boot for CWM - you can bet I was not holding any buttons when the thing rebooted after downloading CWM. I looked around for a while before I found anything about the key sequence and now if I try a boot holding power & volume up I get an dead android with an red triangle ! in his tummy. I gather this means failure. I did however manage to install Superuser from ChainsDD. Does having Superuser installed mean anything about whether I have CWM installed or not? I am confused! From this post I gather I should try the CMW install again and hold the buttons when it reboots? What do you see to indicate you are in CWM? Some sort of menu?
If I knew how I would try and use the installed SU to look in /system to see if there are any of the mentioned files.
Can somebody give me some clues on next steps I can try at home tonight. Much appreciated!!
Click to expand...
Click to collapse
Yeah, sounds like you got into recovery properly by holding volume up while powering on. But it also sounds like your CWM might have gotten overwritten. If you did get SU installed, you can use a file program like Root Explorer or ES File Explorer to look for recovery-from-boot.p in your /system directory, and rename it to recovery-from-boot.bak. then reflash CWM.
smorealt rorer
Ok so a little program to browse for files. I'll load that because I'll blow it away when I redo CWM anyway.
---------- Post added at 11:01 AM ---------- Previous post was at 10:48 AM ----------
Yip there is it - recovery-from-boot.p in /system - so just so I understand - If I rename it now -does this mean it will not be drop-dead necessary to boot straight into CWM after I download CWM onto the phone and it reboots - because the phone won't be setup to undo the CMW anymore.
Also - am I correct that you can make backups using CWM?
penguinpal said:
Ok so a little program to browse for files. I'll load that because I'll blow it away when I redo CWM anyway.
---------- Post added at 11:01 AM ---------- Previous post was at 10:48 AM ----------
Yip there is it - recovery-from-boot.p in /system - so just so I understand - If I rename it now -does this mean it will not be drop-dead necessary to boot straight into CWM after I download CWM onto the phone and it reboots - because the phone won't be setup to undo the CMW anymore.
Also - am I correct that you can make backups using CWM?
Click to expand...
Click to collapse
Yep, correct on both counts you'll see the option 'backup and restore' in CWM.
Well no go on the rename - recovery-from-boot.p cannot be renamed because the file system is read-only.
I installed Total Commander and when I try and remount / as r/w with it I get re-mount error su called failed. Seems my su is not the real thing.
Will it work if I install CWM and boot straight from the download into the CWM - can I rename the file from there somehow?
If you can get adb access in CWM, there should be a command to rename that file, i'm not sure if it would be from adb shell or not... perhaps Google it or someone else will chime in here. You would probably need to flash SU first, then try adb and type su first and see if you get # prompt.
Otherwise you can go thru the full cycle- flash CWM, boot straight into recovery, flash SU, reboot and rename the recovery file, reflash CWM. Using adb in CWM would be the more elegant way, haha.
I am OK with full cycle - just explain this to me --> boot straight into recovery, flash SU,
I think I know how to boot straight into recovery -> but how do I flash SU from there?
Do I have to get the su.zip onto the phone before I boot into recovery? How do I do that?
Which reminds me of another question the http://forum.xda-developers.com/showthread.php?t=2017748 thread says
Bugs:
Usb mass storage isnt working,
Is this still true? Does this mean if you install CWM you can't mount your phone as mass storage in anyway ?
Yeah, load the SU zip onto your phone before going into CWM, since usb storage might not mount. Easiest way might be just to DL the zip on the phone by going to the thread on the phone, then navigate to your downloads folder in CWM to flash it. Otherwise if you have a more recent version of Ubuntu, you might be able to access device storage thru usb to transfer the zip... or else you can do that in Windows(or Mac maybe?).
Edit: flashing CWM won't break usb storage in general, it just doesn't seem to mount in CWM.
Great - so I downloaded the SU.zip from my phone and it is in /sdcard/Download for later. So I assume loading CWM does not erase what is in the download folder ?
And thanks for explaining that CWM just break usb mount in CWM not generally.
Much Much appreciated.
CWM shouldn't erase whats in the download folder. If it does, there's an issue there.
And why not just use MotoFail2Go to push in SU and then use RomManager from the appstore to flash CWM from the OS itself, because that fixes the rewrite issue as well and is a much simpler process?
CMNDR
since I am using ubuntu the word "windows" in the link did not draw me in .... am I missing something?
http://vulnfactory.org/public/motofail2go_windows.zip
penguinpal said:
since I am using ubuntu the word "windows" in the link did not draw me in .... am I missing something?
http://vulnfactory.org/public/motofail2go_windows.zip
Click to expand...
Click to collapse
i always keep a Windows installation around, just for certain programs. but, by doing this the manual way, at least you get to see what is being done, instead of programs doing it for you
Hi All,
I am planning on providing Samsung Galaxy stock debloated ROMs for M series FLOSS or GFS version.
Please contact me here for testing purposes and if anyone is interested.
Few added stuffs maybe given as well, depending on the kind of framework changes, as I will avoid any changes, as the FW breaks a lot.
I do not have any phone, hence all testing will be on the testers, so be sure to keep backups in case you agree to test.
Moreover, OTA is not possible and most probably it will be a decrypted OS. You will need good bandwidth and patience to do it.
Everything that you people do on TG can be done here, needs patience, which is all one should always have.
Share this with others, who wants to join. I will try any other series too, but only android 9 and 10 at the moment. Android 11 is not in my list.
Glad to hear that
TWRP
Nazim navas said:
Glad to hear that
Click to expand...
Click to collapse
So, that TWRP from Christin Koshy work on current version too? (the one released 3 days ago by Samsung?)
twrp_3.4.0_by_nevidimka655.tar
If yes, then I will use it for the build.
vdbhb59 said:
So, that TWRP from Christin Koshy work on current version too? (the one released 3 days ago by Samsung?)
twrp_3.4.0_by_nevidimka655.tar
If yes, then I will use it for the build.
Click to expand...
Click to collapse
I am not sure about the twrp it has some bugs
M21_Testing_20200929.tar
Nazim navas said:
I am not sure about the twrp it has some bugs
Click to expand...
Click to collapse
Have built, and uploading. It is a heavy file, around 4.2 GB (hopefully only one time). Flash with ODIN (in AP). Uncheck auto reboot.
Reboot to stock recovery, format data, mount /system, format data once again, and reboot to DOWNLOAD mode.
Then try each of the following boot methods:
01. Reboot normally (you can keep auto-reboot" checked for this trial) - If fails, try 02..
02. After flashing, reboot to recovery, format data, dalvik/cache, reboot - If fails, try 03..
03. Extract the 3 files, and zip to a .zip extension via 7zip and not WinRAR. Add the META-INF (full folder) folder from the attached zip, to the ROM zip and flash via TWRP (the one available).
-- Unzip the META-INF zip, and unzip the tar file ROM. Copy them all to say desktop and add all 3 files and the META-INF folder to .zip via 7Zip. Resultant file should be a zip file consisting of META-INF folder, boot, system and recovery image (.img) files.
-- The tar file consists of boot.img, recovery.img, system.img. - If fails, try 04..
04. If for any reason you are not able to boot, just replace the boot and recovery with the original/stock boot.img and recovery.img, do not change the system.img I gave. Add all to a tar file (via 7Zip) and flash via ODIN. Please note, do not use any other file. Chances are you will boot.
Please note, booting may take a minimum of 10-15 minutes, so please be patient. Once SAMSUNG logo comes it should ideally boot. I am yet to get a way to make DM-Verity work with ODIN. I will post link of ROM soon.
ROM uploaded. N. B. Testing only. https://cloud.operationtulip.com/s/nb7TjDAskmL47tn/download
Ohh, and in between each try, or failures, you may have to format data (may). At times I have seen for any reason if it fails, clearing or formatting data is needed which is odd on M series, but not always. Probably, trial error mode, but I do recall.
Also, in the 4th option, if you boot with stock boot and recovery, you will not be rooted. I will try and add root to the system, but cannot guarantee as of yet.
Nazim navas said:
I am not sure about the twrp it has some bugs
Click to expand...
Click to collapse
Have built few testing TWRP's. Try them out and let me know what works, what not please.
1. TWRP+Mod - This is a modified version of what I wanted to build out of TWRP. This consists of that old TWRP, but modified to suit the latest builds. - Link
2. TWRP+Stock - This has stock features enabled. Should be good to go anyways. - Link
3. TWRP+vdbhb59 - This I have modified in many many ways, so should be good to go as well. - Link
4. TWRP_20201001_Test - Image/Tar - This I have made from scratch. If you say this one works, then I will load this as Unofficial (until TWRP accepts it) as Android 10 working.
In each let me know, what is working, and what is not.
You should be able to flash DM-Verity through these, post you install the OS I gave. File attached (do not rename the file).
All M21
If you face any issues try flashing twrp+boot via .tar in AP in one file. Then check.
There are telegram groups check thier forums !
prashantp01 said:
There are telegram groups check thier forums !
Click to expand...
Click to collapse
Is anyone working on TWRP? For M21 yet? Android 10
Twrp odin fail
FAILED. does not installed on new firmware one ui 2.1
---------- Post added at 03:52 AM ---------- Previous post was at 03:41 AM ----------
Twrp not installed one ui 2.1 . The last firmware.
Odin failed
ahmad_subqi said:
FAILED. does not installed on new firmware one ui 2.1
---------- Post added at 03:52 AM ---------- Previous post was at 03:41 AM ----------
Twrp not installed one ui 2.1 . The last firmware.
Odin failed
Click to expand...
Click to collapse
Yeah I know. As I mentioned, trial error run and testing to understand what can be done.
Can you post logs?
Nazim navas said:
The twrp not working
---------- Post added at 07:14 AM ---------- Previous post was at 07:10 AM ----------
I rooted m21 through odin
Click to expand...
Click to collapse
Okay, can you try what I mentioned about the ROM through ODIN? I need to know that first. TWRP is not the necessity as of now, but to boot up modified system binary is. Please flash the rom via ODIN, as mentioned in the earlier post. Not with TWRP.
Edit: Also give what ever error you face. Snapshot, in writing, and the stage at which you get the error, etc.,
Check if any of these TWRP work: https://www.androidfilehost.com/?w=files&flid=318632
Nazim navas said:
A51 ported twrp working but internal storage not working not sure about first one
---------- Post added at 02:54 AM ---------- Previous post was at 02:53 AM ----------
The bugs in ported twrp from a51
I checked the twrp last 2 days it is not working perfectly as expected
*unable to backup or restore showing error like key is absent /twrp folder is not found
*error in internal storage may be due to encryption
*error flashing dm verity zip/multi disabler zip (/odm not found )
*unable to flash gsi images as it is not showing system image during flashing it only shows boot,recovery,optics,spectrum and super
*unable to repair /change format in wipe section
*all others like sd card /usb is mounting no issue with that
All this are my personal experience when i tested the twrp hope any developers will fix this soon
Click to expand...
Click to collapse
Okay, these bugs would have been there, as whoever ported they could not get a working one having /superimage and since /odm is not there as separate. ODM is a supra path, rather than individual path. This will take time, else will have to gather latest stock and make it as Pie would be like. Will take time though.
Thanks for testing out mate.
i got m31, ill be happy to test if any m31 develeoping avilible
anilkuruhan said:
i got m31, ill be happy to test if any m31 develeoping avilible
Click to expand...
Click to collapse
Thanks mate. Can you share the latest version and country code details? Also your system details (about) page. It will help me find more information.
Nazim navas said:
Model no SM-M215F/DS
Click to expand...
Click to collapse
The trouble with latest updates is it has superimage. The super unpacker/packer does not work properly. You tested earlier. M21 has that. M31, I have not checked yet. If it has superimage too, then I will have to wait till I get a working one. Will check.
Thanks again.
Nope, superimage. I am having serious trouble with my W10 to run these even with VMUbuntu. Will only be able to work if that acts properly.