Database Info

[Q] Ubuntu Installation help

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?

Droid 2 Global root CD for .629 (not necessary to brick phone)

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

HP Slate 7 2800 [HOW-TO ROOT AND INSTALL CWM RECOVERY]

This guide will teach you the easiest method to root and install CWM on your HP Slate 7 2800! These instructions are for Linux, but you should be able to do this on Windows with the correct drivers instead of the android.rules files.
HP Slate 4600: I need someone to test this with the 4600!
DISCLAIMER: This was successfully tested on my HP Slate 7 2800 on Linux Mint 17. THIS COULD POTENTIALLY BRICK YOUR TAB IF SOMETHING GOES WRONG!!! Proceed at your own risk!
How to Root:
1. Download Cydia Impactor from http://www.cydiaimpactor.com/ and install it.
2. Download and install adb. There are multiple ways to do this. One way is to install the Android SDK from http://developer.android.com/sdk/index.html and install adb through the SDK manager.
3. Download the android.rules.zip from https://sites.google.com/site/jrc2swebsite/downloads/hp-slate-7-2800 and extract the .zip file.
4. Move the two **-android.rules files to /etc/udev/rules.d and mark as executable. Restart your computer.
5. Enable USB Debugging in Developer Options on the tablet. Connect it to the computer.
6. Open the Terminal Emulator on your computer and change the directory to the path where adb is located like this: cd insert/path/for/adb/ (hit enter)
7. Start adb and scan for devices by running sudo ./adb devices (hit enter.) You should see a serial number with the word device next to it.
8. Minimize adb and start Cydia Impactor. Make sure it says "# drop SuperSU su to /system/xbin/su." Click "Start." If you get a no device found error, click "Bridge" > "Connect" and then click start again.
9. Reboot your tablet. Download Root Checker from the Play Store to make sure you are rooted. Follow the tutorial in the next post for installing CWM Recovery and the SuperSU app to control which apps are granted root access.

DISCLAIMER: This was successfully tested on my HP Slate 7 2800 on Linux Mint 17. THIS COULD POTENTIALLY BRICK YOUR TAB IF SOMETHING GOES WRONG!!! Proceed at your own risk!
How to Install CWM Recovery and SuperSU:
Download CWM Recovery for the Slate 7 2800 from http://forum.xda-developers.com/showpost.php?p=49165523&postcount=1 and install following the instructions in the post.
Install SuperSU:
Download the latest SuperSU from http://download.chainfire.eu/supersu and flash in CWM Recovery.

Credits:
@Chainfire (SuperSU)
@rjwil1086 (CWM Recovery)
www.cydiaimpactor.com (Cydia Impactor)
Android/Google (Android SDK)
@jrc2 [me] (android.rules files)
Whoever taught me how to make the android.rules
If I left you out (I promise it was an accident,) please send me a PM and I will add you to this list.

Useful links:
CWM Recovery
SuperSU Thread
JB-SlateROM
Source Code for this tab (Thanks @tommyboy76!)
Restore Image (How-to install is on the same page as the image)
CWM Flashable Stock ROM
My Website

reserved

Bump

Bumping this so more will see this thread

Cydia is not working anymore with fw version 1.05.17, has anyone found a way to root the new fw? or to mount /system as rw? please let me know if you guys have anything

math_green20 said:
Cydia is not working anymore with fw version 1.05.17, has anyone found a way to root the new fw? or to mount /system as rw? please let me know if you guys have anything
Click to expand...
Click to collapse
Did the slate 7 have a software update? I will have to check that out. Just to make sure, what is your model number?

it is a 2800. I've tried some of the one-click root apps, scripts, and nothing seems to do it, Hp did a nice job at patching this stuff
---------- Post added at 01:54 AM ---------- Previous post was at 01:53 AM ----------
if you have any old update.zip from 1.05.14 or 1.05.10 and can send it to me you'd make my day

math_green20 said:
it is a 2800. I've tried some of the one-click root apps, scripts, and nothing seems to do it, Hp did a nice job at patching this stuff
---------- Post added at 01:54 AM ---------- Previous post was at 01:53 AM ----------
if you have any old update.zip from 1.05.14 or 1.05.10 and can send it to me you'd make my day
Click to expand...
Click to collapse
I'll post the link if I have it. Do you know what Android version this update is?
jrc2

math_green20 said:
it is a 2800. I've tried some of the one-click root apps, scripts, and nothing seems to do it, Hp did a nice job at patching this stuff
---------- Post added at 01:54 AM ---------- Previous post was at 01:53 AM ----------
if you have any old update.zip from 1.05.14 or 1.05.10 and can send it to me you'd make my day
Click to expand...
Click to collapse
HP has updated their website and only has the new update.zip there. The only thing I know of is a CWM flashable version of the old update.zip. You can find that at http://forum.xda-developers.com/showthread.php?t=2608181
Looking at other threads, the OTA does make rooting no longer possible.
jrc2

jrc2 said:
I'll post the link if I have it. Do you know what Android version this update is?
jrc2
Click to expand...
Click to collapse
It is still 4.1.1, I'm back on 1.05.6(The stock CWM flashable one), Idk how I did this but i've been able to get CWM back on my device without rooting, I tried to modify boot.img to disable the install-recovery.sh script, this got me stuck in a bootloop but allowed me to flash CWM and the old firmware back in, I guess I got lucky
I got the stock kernel and the Rk30_sdk one to compile but I don't understand how to repack it in boot.img, bootloop everytime.
Thanks for the help anyway buddy.
We should make an all-in-one post for this device with firmwares, CWM, rooting options and stuff

math_green20 said:
It is still 4.1.1, I'm back on 1.05.6(The stock CWM flashable one), Idk how I did this but i've been able to get CWM back on my device without rooting, I tried to modify boot.img to disable the install-recovery.sh script, this got me stuck in a bootloop but allowed me to flash CWM and the old firmware back in, I guess I got lucky
I got the stock kernel and the Rk30_sdk one to compile but I don't understand how to repack it in boot.img, bootloop everytime.
Thanks for the help anyway buddy.
We should make an all-in-one post for this device with firmwares, CWM, rooting options and stuff
Click to expand...
Click to collapse
I sort of started that in the 2nd or 3rd post here, titled "Useful Links".

I simply can't root this device.
Cydia Impactor responds with "signature bugs unavailable" and all this Chinese 1-click root stuff doesn't work at all.
Tried on Linux Mint and Windows 7 (both x64).
The problem might be my firmware, which is v1.05.18_user.
This is the stock firmware that was preinstalled on my tablet.
How can i downgrade the firmware?

Oddy94 said:
I simply can't root this device.
Cydia Impactor responds with "signature bugs unavailable" and all this Chinese 1-click root stuff doesn't work at all.
Tried on Linux Mint and Windows 7 (both x64).
The problem might be my firmware, which is v1.05.18_user.
This is the stock firmware that was preinstalled on my tablet.
How can i downgrade the firmware?
Click to expand...
Click to collapse
Sorry I didn't see your post until now! I do not have the latest firmware on my tablet, so I haven't experienced this problem (I decided not to update after seeing the reports of people being unable to update. @math_green20 somehow managed to get it downgraded, but I do not know exactly how he did it. You might be able to figure out something from the previous posts in this thread.
Have a great day!
jrc2

hi Any new Rom is available for HP slate 7 voice TAB ,Please provide the isntructions

vinaymysore777 said:
hi Any new Rom is available for HP slate 7 voice TAB ,Please provide the isntructions
Click to expand...
Click to collapse
If you are talking about the 2800, then no,, I do not believe so.

jrc2 said:
If you are talking about the 2800, then no,, I do not believe so.
Click to expand...
Click to collapse
hi JRC2,
Im having HP slate 7Voice tab 6102 RA whether this is 2800 or other version

What is the Rom available for this tab

(needed) Developer willing to port custom recovery to the galaxy tab 4 8.0

Hi there are a few version of the Galaxy Tab 4 8.0 that have no support for a custom recovery.
Source files have been found and are ready to be worked with.
The devices we would like to bring support to are the:
T330NU source file:
http://www.4shared.com/zip/UG28maH2ce/SM-T330NU_NA_KK_Opensource.html
T335K source file:
http://www.4shared.com/zip/9Y4qzw1zce/SM-T335K_KK_Opensource.html
T335L source file:
http://www.4shared.com/zip/nZ4xmfNgba/SM-T335L_KK_Opensource.html
T337a source file:
http://www.4shared.com/zip/21kf9dZYce/SM-T337A_NA_KK_Opensource.html
Boot.img dumped from device T330NU:
http://www.4shared.com/file/nOAtJQbCba/boot.html
Recovery.img dumped from device T330NU:
http://www.4shared.com/file/mSkFIM0Bce/recovery.html
If ANYONE is willing or knows someone who could be willing to port a custom recovery to these devices it would be greatly appreciated if you could pass on the message and spread the word. If we all do work together we should be able to get this done.
There are many people who are willing to test the final work. Thanks in advance.

Hey, I am dedicated to get a recovery for this device also. I am pretty good with computers but have never worked on a recovery project. I do have Linux and can help if needed on anything.

There should be a guide on xda

smknutson said:
There should be a guide on xda
Click to expand...
Click to collapse
I tried recovery builder but had no luck. Was not able to download files after building. Says build has been queud or something like that. Was having trouble getting the stock recovery img off of the phone.

Leonidas87 said:
I tried recovery builder but had no luck. Was not able to download files after building. Says build has been queud or something like that. Was having trouble getting the stock recovery img off of the phone.
Click to expand...
Click to collapse
I have my stock recovery.img if needed

pre4speed said:
I have my stock recovery.img if needed
Click to expand...
Click to collapse
Which Galaxy tab version do you have?
And have did you extract your stock recovery img?

Leonidas87 said:
Which Galaxy tab version do you have?
And have did you extract your stock recovery img?
Click to expand...
Click to collapse
I have the 337a and yup pulled recovery.img and boot.img

pre4speed said:
I have the 337a and yup pulled recovery.img and boot.img
Click to expand...
Click to collapse
My last message had a spelling mistake sorry about that. How did you pull those files tho? I've been having trouble on this device

Leonidas87 said:
My last message had a spelling mistake sorry about that. How did you pull those files tho? I've been having trouble on this device
Click to expand...
Click to collapse
In terminal, type su dd if=/dev/emmc/"boot partition" of=/sdcard/recovery.img
I think you need to enter after su. It will save it to your sd. This is assuming root. You enter your boot partition in the quotes. Use this to find your partitions.
https://play.google.com/store/apps/details?id=com.cls.partition

pre4speed said:
In terminal, type su dd if=/dev/emmc/"boot partition" of=/sdcard/recovery.img
I think you need to enter after su. It will save it to your sd. This is assuming root. You enter your boot partition in the quotes. Use this to find your partitions.
https://play.google.com/store/apps/details?id=com.cls.partition
Click to expand...
Click to collapse
Thanks for the help I think I understand. I have terminal ready and the app installed. Just not sure which partition is the one to fill in the quotations in the terminal.
I'm attaching pictures if that helps.
Also I'm sure I do not include the actual quotes when typing in terminal just to save myself from confusion. I do have root by the way
UPDATE:
THESE PICTURE WERE FOR MY GALAXY NOTE 3 DISRAGAURD THESE PHOTOS. My mistake I was on my phone when I read the message and tried to jump right into it

THERE ARE THE PHOTOS FROM MY GALAXY TAB 4.
These would be the correct locations I need clarification so I know which ones are boot and recovery for pulling/extracting in terminal.

These two represent your recovery and boot partitions. So in the quotes you'll put the mmcblk0p15 for recovery.img.
I found that pulling the recovery is that exact code, whereas pulling the boot was a different code, but found easily on the internet. I got the recovery easy, the boot was a little more work, but did get it.

pre4speed said:
These two represent your recovery and boot partitions. So in the quotes you'll put the mmcblk0p15 for recovery.img.
I found that pulling the recovery is that exact code, whereas pulling the boot was a different code, but found easily on the internet. I got the recovery easy, the boot was a little more work, but did get it.
Click to expand...
Click to collapse
Think I am not typing it exactly how it needs to be. Even tried copy and pasting. So close but yet so far lol. I really think we have all been making progress the last few days. This would help if I could get it to work. Would be useful and handy to have a backup for each device variation.

Pic did not upload for me the first time. Backup did not work yet. I must be typing or copy and pasting wrong

I'm trying to remember how I did it. I believe you open terminal, type su then press enter, then type the rest. Let me do it again and see what my steps were.
---------- Post added at 01:26 PM ---------- Previous post was at 01:13 PM ----------
Ok, I'm sorry. The code I gave you is actually for the boot.img not recovery. Here is the right code. Sorry again.
Type it exactly as I did and you'll find the backup on your sdcard (not external). I actually found the correct code in the 7.7" tab thread. Lol http://forum.xda-developers.com/showthread.php?t=1540641

pre4speed said:
I'm trying to remember how I did it. I believe you open terminal, type su then press enter, then type the rest. Let me do it again and see what my steps were.
---------- Post added at 01:26 PM ---------- Previous post was at 01:13 PM ----------
Ok, I'm sorry. The code I gave you is actually for the boot.img not recovery. Here is the right code. Sorry again.
Type it exactly as I did and you'll find the backup on your sdcard (not external). I actually found the correct code in the 7.7" tab thread. Lol http://forum.xda-developers.com/showthread.php?t=1540641
Click to expand...
Click to collapse
I'm just out right now but will give it a try as soon as I get home. Thanks again much help. Will report back.

Leonidas87 said:
I'm just out right now but will give it a try as soon as I get home. Thanks again much help. Will report back.
Click to expand...
Click to collapse
Ok I have got both recovery and boot.img backed up/pulled. Finally lol thanks a lot

I think we have most of the necessary files to get the job done. If you say you have got you boot.img and recovery backed up and so do I. We have source files also. All we need now is for the recovery to be compiled. For a skilled experienced developer to finish up what we started probably would not be too hard. If only we had someone to really take the time with us with some of the next key steps. I am looking up guides and resources all over the Internet but nothing concrete to get the job done ?

Leonidas87 said:
I think we have most of the necessary files to get the job done. If you say you have got you boot.img and recovery backed up and so do I. We have source files also. All we need now is for the recovery to be compiled. For a skilled experienced developer to finish up what we started probably would not be too hard. If only we had someone to really take the time with us with some of the next key steps. I am looking up guides and resources all over the Internet but nothing concrete to get the job done ?
Click to expand...
Click to collapse
Yeh, I hear that. Like I said before, I've got my buddies looking at it, but these devices that they don't own aren't a priority for them. I don't feel right bugging them about it every day. I'll see if there's anything I can find. I'm not a developer and get lost with code, but guides I can help to find if you have the build environment.
http://rootzwiki.com/topic/23903-how-to-compile-twrp-from-source/
http://forum.xda-developers.com/showthread.php?t=1943625
I am so lost with all that[emoji30]

Leonidas87 said:
Hi there are a few version of the Galaxy Tab 4 8.0 that have no support for a custom recovery.
If ANYONE is willing or knows someone who could be willing to port a custom recovery to these devices it would be greatly appreciated if you could pass on the message and spread the word. If we all do work together we should be able to get this done.
There are many people who are willing to test the final work. Thanks in advance.
Click to expand...
Click to collapse
if you are able to install an omnirom build environment on linux i will make you a local_manifest and show how to build.

[SOLVED] Wiko Rainbow Jam seems hard to root: I'm looking for help

Hi all,
I have a Wiko Rainbow Jam (which is provided with the stock rom "Wiko Rainbow Jam version 8", Android Lollipop 5.1 and the latest updates from Wiko), is about a week that I attempt to root my phone, but I am unable to do this operation, since I am totally unable to mount the /system as RW, and furthermore the bootloader is locked.
Firstly I found this method which consist to write/flash the TWRP custom recovery in place of the original one:
Root method 1
(sorry for the Google Translate link, but I cannot find the same how-to in English)
Which seems similar to this how-to
http://forum.xda-developers.com/showpost.php?p=63803008&postcount=5
But seems that these two methods will wipe/erase everything on my phone, and I would avoid this risk.
I also read that by flashing another custom recovery I will be unable to install updates from Wiko.
Then I tried this method using adb which is more simple:
https://f-droid.org/forums/topic/tutorial-how-to-root-an-android-device/
But when I launch the "adb root" command, all that I get is "adbd cannot run as root in production builds"; so I attempted various workarounds to "fix" adb, but all unsuccesfully.
I have to mention the fact that I have some skills in using Linux and the shell commands: maybe there would be a way to place the "su" binary on my Phone using Linux on my computer, by logging on the phone as root user, by acquiring the needed privileges?
Any help/suggestion/hints would be very appreciate! :good:
Kind regards.

I have a mtk6580 phone and also had the root issues, for a while I used kingroot, which rooted fine but I didnt trust it. Then I used supersume to get rid of kingroot which seemed to work but again, wasnt 100% it was all gone. Followed a similar guide to your first link which wasnt working. What worked for me was:
Download the twrp recovery .img file
rename it to recovery.img
open SPflash tools
add your own scatter file from your stock rom
deselect all the boxes except recovery
double click the recovery address box and find the renamed recovery.img
click download
plug your turned off phone in,
let it flash.
reboot into recovery
select reboot system
TWRP will tell you its not rooted and ask to install superSU
swipe for yes
reboot and you are rooted.
NO DATA LOSS

Thank you for this detailed how-to! However, for me, nor kingroot, kingoroot, framaroot and no other apk worked on my phone, so I will attempt to try your method, but first I have some questions:
1): On my phone, under SETTINGS > DEVELOPER OPTIONS, I can see the option “OEM unlocking”: I have to enable this option to permit the flashing of the TWRP img?
2): Is ok to download TWRP from here? dl.twrp.me/i9300/twrp-2.8.6.1-i9300.tar.html
3): "add your own scatter file from your stock rom":
where I can get/grab such file?
4): "TWRP will tell you its not rooted and ask to install superSU":
so TWRP is already provided with the SuperSU utility?
5): To be sure to avoid any risk, here I have a backup of my phone, which was done using "adb backup -apk -shared -all"; in case of emergency I will be able to restore my phone using this backup?
Many thanks for your attention! :good:

Mister_Dave said:
3): "add your own scatter file from your stock rom":
where I can get/grab such file?
Click to expand...
Click to collapse
Ok, seems that such file was available in the first link:
s000.tinyupload.com/download.php?file_id=53888272183191245346&t=5388827218319124534686744
is called MT6580_Android_scatter.txt , can you take a look and tell me if is ok?
Many thanks!

1) cant hurt to turn it on, however the phone will be flashed whilst turned off so dont know if its needed, but Im sure I wouldve enabled it.
2) and 3) I dont know what your exact model number etc.. is for your phone, so the twrp you would have to find and check yourself, go here: http://www.needrom.com/category/others/u-v-w-x-y-z/brands-w/wiko/ and you can try to get a twrp from there, and definetely get a stock rom. Use the scatterfile from an 'SP TOOLS FLASHABLE STOCK/UPDATE ROM'
4) yes
5) I dont know, I dont use adb and wouldnt like to say its OK. You can use this: https://play.google.com/store/apps/details?id=com.h3r3t1c.onnandbup&hl=en which will make a TWRP or CWM backup of your entire phone which you can then flash in TWRP or CWM once they are flashed, or get all the data from the backup. I would advise to find this out before trying though, just in case. I personally didnt lose any data, flashed twrp in SPtools, took 5 seconds, rebooted, added SU, rebooted, took 2 minutes and everything was still there.
---------- Post added at 04:43 PM ---------- Previous post was at 04:41 PM ----------
it has to be a scatter file from your exact model of phone, as everything has to match, partitions, nvram...etc... loads of things that can go wrong if the scatter is wrong

robneymcplum said:
2) and 3) I dont know what your exact model number etc.. is for your phone, so the twrp you would have to find and check yourself, go here: http://www.needrom.com/category/others/u-v-w-x-y-z/brands-w/wiko/ and you can try to get a twrp from there, and definetely get a stock rom. Use the scatterfile from an 'SP TOOLS FLASHABLE STOCK/UPDATE ROM'
Click to expand...
Click to collapse
I went there, but my model is not listed.. As I stated in the subject is a Wiko Rainbow Jam: if i search for Rainbow Jam is such link, no model is displayed..
it has to be a scatter file from your exact model of phone, as everything has to match, partitions, nvram...etc... loads of things that can go wrong if the scatter is wrong
Click to expand...
Click to collapse
I got the scatter file in the first link "Root method 1", where there is the how-to for my exact model.

ah right, in that case, its OK

robneymcplum said:
ah right, in that case, its OK
Click to expand...
Click to collapse
Ok: it was painless differently from what I thought: now, following your advice (I used the TWRP and the scatter file from the first link) my phone is nicely provided with the root access
EDIT: was necessary to activate the “OEM unlocking” option under SETTINGS > DEVELOPER OPTION, without this option activated, I was unable to flash the TWRP recovery img.
Many thanks!
p.s: If a moderator see this post, feel free to add [RESOLVED] to the title of this thread, since I cannot edit the title.

Glad it worked lots of guides I saw also made it excessively complicated, this way took you what? 2 minutes? And am guessing all your data is safe and untouched.

robneymcplum said:
Glad it worked lots of guides I saw also made it excessively complicated, this way took you what? 2 minutes? And am guessing all your data is safe and untouched.
Click to expand...
Click to collapse
Yeah, it took about 2 minutes, just the time to figure out that I needed the USB OTG cable with an usb mouse and to browse to the UPDATE-SuperSU-v2.76.zip file (as I said I used the TWRP posted in the first link, which doesn't work with the touch screen).
I want to say thank you again for your friendly assistance!
EDIT: Yes: all my data is safe and untouched!

Like:good: