Database Users

[TUT] How To Create DUMP out of Stock Rom ( UP NOW )

Hello .
Posting a tutorial on how to create a dump out of your stock rom, in case you delete some apps or modify some settings.
ALRIGHT LETS START:
STEP ONE:
Alright, so you want to make a backup of your phone software, but dont know what to do. Its simple, download the package the Android SDK from google and copy it to C:\ drive. Once you have download it, make sure you have Java installed in your system or else it will not work. After everything is done, open the program and install these two packages:
1. Android SDK Tools, revision 6
2. USB Driver package, revision3 ([COLOR="Red"IMP: Its important that the USB driver installed shows up as Composite Android Debug Device, else it wont work. ][/COLOR]
What Android SDK ?? Read about it here: [url]http://developer.android.com/sdk/index.html[/url]
Why Android SDK ? Because: it has the [COLOR="red"]android debug shell[/COLOR] which you require before communicating with your android phone. So download it ! From here:
STEP TWO:
Download Busybox from here : http://rapidshare.com/files/407238531/busybox What is Busybox ?? Read about it here: http://www.busybox.net/
MD5 Signature: C5B76280434EEF49310AD8F1810B10B2
STEP THREE:
One you have downloaded busybox, copy it to the C:\ drive of your computer and then follow the next step. The next step is to open the Command Prompt ( type cmd in the Run prompt ) if using Vista right click on "Run as Administrator".
Assuming you are the root of C:\
Type: C:\cd android-sdk-windows
-> then
Type: C:\android-sdk-windows\ cd tools
-> if you have android debug shell and USB drivers properly installed
Type: adb devices
Now your device will show up as a binary number .. Success ! if it doesn't show up you need to install the drivers again or something else is wrong.
STEP FOUR:
Now once your device shows up, we will need to download the busybox from the computer to the phone. Since we can write anything in the /data/local portion of the android system we will copy the busybox file to the android device.
Type: adb push busybox /data/local/busybox
Once it has been copied to your device issue this command.
Type: adb shell This coomand is issued to go to your mobile's terminal where you can issue commands internally to the phone.
--> then
Type: cd /sdcard This command is given inorder to go to the sdcard ( i.e the internal storage of your phone )
--> then
Type: chmod 755 /data/local/busybox This command is issued to set user -rwxrwxr-x permissions to the file.
--> then
Finally, issue this command.
Type: /data/local/busybox tar cvf Samsung.tar /system This command is given to copy and tar the system folder where all the stock applications and programs are and to create a dump of that system folder.
STEP FIVE:
Job Done !!
The Samsung.tar file can be copied to the computer now. Have fun.

this is perfect, as i want to create a dump of my original ROM

A dump is simply a backup of your original ROM right?

thats good news if it is indeed a a backup of the stock firmware.
i want to back up my warranty firmware!

OrionTC said:
thats good news if it is indeed a a backup of the stock firmware.
i want to back up my warranty firmware!
Click to expand...
Click to collapse
it is only a backup of your stock apps and driver if so however it doesnt convert the files into a flashable rom version.

is there a way for us to backup the firmware?? (not just stock apps)

tids2k said:
it is only a backup of your stock apps and driver if so however it doesnt convert the files into a flashable rom version.
Click to expand...
Click to collapse
So this is not a tutorial of how you back up your stock rom but how you back up your stock apps and stock drivers?

droidwi said:
So this is not a tutorial of how you back up your stock rom but how you back up your stock apps and stock drivers?
Click to expand...
Click to collapse
Correct. We most likely won't be able to actually perform a complete backup until Nandroid works on the handset.

Too bad, the title was very promising but what you show is just an backup archive of the system.
BTW, there is no guarantee that restoring it will produce a usable phone, because kernel, datas, modem baseband etc won't be restored too !
But this can be useful to restore some file after a mistake done on /system files.

supercurio said:
Too bad, the title was very promising but what you show is just an backup archive of the system.
BTW, there is no guarantee that restoring it will produce a usable phone, because kernel, datas, modem baseband etc won't be restored too !
But this can be useful to restore some file after a mistake done on /system files.
Click to expand...
Click to collapse
im working on creating a stock rom ... may be some happy results and happy faces. who knows . keep sticked !

uploading dump again .. please wait.

So, Can i just select this dump in Odin and it will recover to stock firmware. Quite confused here.
The file size is 275 megs , so is it only for apps? Have you flashed with this dump. Nice work so far. THanks.
Edit: Just realised the dump option in Odin is for dumping my rom , not loading one.
So stuck with this until Samsung update. Huh!

Is this the same procedure as making a backup /efs?
I've been searching the forum for hours and this is the only thing I could find that looked anything like it.

This won't work
No, no and no !!
This procedure will not backup your stock ROM.
A complete rom consists in:
- a primary bootloader.
- a secondary bootloader.
- an initrd image with the kernel.
- a rootfs (the /system partition).
- an efs partition.
- a binary radio firmware.
There is no known method to backup all the flash partitions and transform them into proper files that can be reflashed with Odin or Heimdall.

Plinn said:
No, no and no !!
This procedure will not backup your stock ROM.
A complete rom consists in:
- a primary bootloader.
- a secondary bootloader.
- an initrd image with the kernel.
- a rootfs (the /system partition).
- an efs partition.
- a binary radio firmware.
There is no known method to backup all the flash partitions and transform them into proper files that can be reflashed with Odin or Heimdall.
Click to expand...
Click to collapse
+1.. The thread is misleading.. This doesn't accomplish anything! You really think people in the "Android Development" section don't know about tar?

Did anyone already managed to get the built-in dump function from Odin working?
With Odin v1.3 there was the possibility to decide whether to dump AP RAM or AP NAND (followed by an ID).
With Odin v1.52 you can't choose this anymore. It will only dump AP NAND.
But my first attempts were unfortunately not very promising

[Q]How to extract CPUID from bricked A500

My partner has a bricked A500. It will NOT boot so any utilities utilising adb/dmesg fail. I can boot into fastboot mode (v0.03.11-ICS) but fastboot returns USB write errors stating invalid partition format "." So, I assume I have to use nvFlash to re-write the partition table but this still requires the SBK that I can not generate as I do not know what my CPUID is.
I have read so many threads all offering tweaked variations of the same process but I haven't found as yet a definitive how-to on re-creating your CPUID/SBK on a bricked device as they all assume you either know your CPUID or the tablet stills boots so you can retrieve it easily.
Does anyone have any links to resources to assist? I currently can boot into fastboot and APXmode. Attempts to factory reset seem to kick off OK but then fail with errors erasing data/cache etc... I have both windows/linux and the tablet is recognized in APX/fastboot mode on both OS's.
Thanks

1- download the attached file
2- go to linux
3- install GCC , lsUSB , Libusb-1.0.x , libusb-1.0-dev (from “Ubuntu software center” )
4- drag and drop the APX.c file in your desktop
5- connect your tablet to the computer (through mini USB) and put it in APX mode
6- Now on computer fire up “Terminal” and type this code
Code:
cd Desktop
sudo su
gcc apx.c -o apx -lusb-1.0
7- a new file should appear in your desktop
8- keep typing :
Code:
./apx
it will return to you the UID (AKA: CPUID)
DONE

Error: Failed to open device
Dr.GM said:
1- download the attached file
2- go to linux
3- install GCC , lsUSB , Libusb-1.0.x , libusb-1.0-dev (from “Ubuntu software center” )
4- drag and drop the APX.c file in your desktop
5- connect your tablet to the computer (through mini USB) and put it in APX mode
6- Now on computer fire up “Terminal” and type this code
Code:
cd Desktop
sudo su
gcc apx.c -o apx -lusb-1.0
7- a new file should appear in your desktop
8- keep typing :
Code:
./apx
it will return to you the UID (AKA: CPUID)
DONE
Click to expand...
Click to collapse
Many thanks for the walkthrough.. n sorry for being such a noob!
My A500 is bricked, and not flashing through update.zip method.. dint have my cpuid so decided to follow your guide.. installed Ubuntu on my windows pc, installed all the additional packages you just mentioned, but after the last command of ./apx it returns with Error: Failed to open device !!!
Now What? can there be ANY way or ANYTHING i can do to get over with this LLAAAST step? pretty pretty please!?
Thanks in Advance!

dishoom said:
Many thanks for the walkthrough.. n sorry for being such a noob!
My A500 is bricked, and not flashing through update.zip method.. dint have my cpuid so decided to follow your guide.. installed Ubuntu on my windows pc, installed all the additional packages you just mentioned, but after the last command of ./apx it returns with Error: Failed to open device !!!
Now What? can there be ANY way or ANYTHING i can do to get over with this LLAAAST step? pretty pretty please!?
Thanks in Advance!
Click to expand...
Click to collapse
Put your device in APX mode, manually. Then get it.
Sometimes, if you leave it in what you think is APX mode, for a certain amount of time, you may not be able to connect to it. So do it fresh.

Moscow Desire said:
Put your device in APX mode, manually. Then get it.
Sometimes, if you leave it in what you think is APX mode, for a certain amount of time, you may not be able to connect to it. So do it fresh.[/QUOTE
Hmm thanks.. Meanwhile I did the code tweak as digested here: http://forum.xda-developers.com/showthread.php?t=2331151
And got my cpuid as 0x00000042dfd497
Hope this is what I needed? Although the characters are 14 if I exclude 0x?
Thanks again mate!
Click to expand...
Click to collapse

dishoom said:
Moscow Desire said:
Put your device in APX mode, manually. Then get it.
Sometimes, if you leave it in what you think is APX mode, for a certain amount of time, you may not be able to connect to it. So do it fresh.[/QUOTE
Hmm thanks.. Meanwhile I did the code tweak as digested here: http://forum.xda-developers.com/showthread.php?t=2331151
And got my cpuid as 0x00000042dfd497
Hope this is what I needed? Although the characters are 14 if I exclude 0x?
Thanks again mate!
Click to expand...
Click to collapse
Well, if I'm not mistaken, it should be 16. You can try it either way.
Click to expand...
Click to collapse

SUCCESS!!
I finally managed to unbrick my tab, SPECIAL thanks to @Moscow Desire, @eppeP, @civato and @srbeen.. here's what i did, thought it might help someone else like me!
Booted my PC in Ubuntu, to extract the CPUID, as i didnt have it saved. for that i used instructions from this post: http://forum.xda-developers.com/showthread.php?t=1751978
Nevertheless, i couldnt completely follow it till unbricking, as somehow things didnt quite work out as expected. Expecially, the UID i recovered was as i quoted above, filled with many zeroes.. i got the correct one after tweaking with apx.c file as advised here: http://forum.xda-developers.com/showthread.php?t=2331151 because i later realized i was using a 32-bit system.
After recovering my UID, downloaded the "V8-UNL-ICS-HC-bootloader-MULTI-cwm.zip" thing, given here: http://forum.xda-developers.com/showthread.php?t=1622425 .. its a simplified form of nvflash, and is easier to operate for less techno ppl like me. Booted to windows, downloaded and extracted it, and edited the v8.bat file to remove any cls commands and see what this thing does. Then, opened the command prompt with Administrative rights, and run the V8.bat file... Once my tab was unbricked, i could easily flash any update.zip package i wanted!!
Sounds easy! but believe me, its easier said than done! took me over a week to complete the whole process as i tried almost EVERYTHING as anyone suggested in ANY post to unbrick my tab! but nevertheless, got the result finally and thats what matters!
Guys, the devs at xda, You ROCK!! :good::good:

dishoom said:
I finally managed to unbrick my tab, SPECIAL thanks to @Moscow Desire, @eppeP, @civato and @srbeen.. here's what i did, thought it might help someone else like me!
Booted my PC in Ubuntu, to extract the CPUID, as i didnt have it saved. for that i used instructions from this post: http://forum.xda-developers.com/showthread.php?t=1751978
Nevertheless, i couldnt completely follow it till unbricking, as somehow things didnt quite work out as expected. Expecially, the UID i recovered was as i quoted above, filled with many zeroes.. i got the correct one after tweaking with apx.c file as advised here: http://forum.xda-developers.com/showthread.php?t=2331151 because i later realized i was using a 32-bit system.
After recovering my UID, downloaded the "V8-UNL-ICS-HC-bootloader-MULTI-cwm.zip" thing, given here: http://forum.xda-developers.com/showthread.php?t=1622425 .. its a simplified form of nvflash, and is easier to operate for less techno ppl like me. Booted to windows, downloaded and extracted it, and edited the v8.bat file to remove any cls commands and see what this thing does. Then, opened the command prompt with Administrative rights, and run the V8.bat file... Once my tab was unbricked, i could easily flash any update.zip package i wanted!!
Sounds easy! but believe me, its easier said than done! took me over a week to complete the whole process as i tried almost EVERYTHING as anyone suggested in ANY post to unbrick my tab! but nevertheless, got the result finally and thats what matters!
Guys, the devs at xda, You ROCK!! :good::good:
Click to expand...
Click to collapse
Speaking for the rest of the mentions, you are most welcome.

Kobo Arc Development

So I was randomly flying around on Google today, and I noticed that someone had claimed to root the Kobo Arc, and gave written instructions here -- http : // www . mobileread . com / forums / showthread.php?p=2584491 (Remove the spaces, XDA won't let me post an actual link, since I don't have 10 posts yet). After running through this myself, I went on the Google Play store and used root checker. Much to my surprise, it worked, and my device now has root access. I even tested with Root Explorer, and mounted the system partition as R/W, and I can move things in and out of it. I'm currently working on trying to get a custom ROM working, but I'm worried that I will cause a brick, since Cyanogen doesn't support the Arc. (yet...)

ThunderBird2678 said:
So I was randomly flying around on Google today, and I noticed that someone had claimed to root the Kobo Arc, and gave written instructions here -- http : // www . mobileread . com / forums / showthread.php?p=2584491 (Remove the spaces, XDA won't let me post an actual link, since I don't have 10 posts yet). After running through this myself, I went on the Google Play store and used root checker. Much to my surprise, it worked, and my device now has root access. I even tested with Root Explorer, and mounted the system partition as R/W, and I can move things in and out of it. I'm currently working on trying to get a custom ROM working, but I'm worried that I will cause a brick, since Cyanogen doesn't support the Arc. (yet...)
Click to expand...
Click to collapse
confirmed, was just going to post this but was beaten to it.
http://www.mobileread.com/forums/showthread.php?t=218928
ive attached the file but please go to that website and pay homage to whoever did this work...now to the next stop, a ROM
Device now has a working custom recovery see post 15
Sent from my Arc using xda app-developers app

dazza9075 said:
confirmed, was just going to post this but was beaten to it.
http://www.mobileread.com/forums/showthread.php?t=218928
In terms of a ROM do we not need a compatible boot loader that will allow unsigned ROMs?
ive attached the file but please go to that website and pay homage to whoever did this work...now to find a man about a ROM
Sent from my Arc using xda app-developers app
Click to expand...
Click to collapse
i have absolutely no idea what im doing but I think I have dumped 12 partitions using
dd if=/dev/block/mmcblk0p10 of=/sdcard/p10.img
is there anyone around that fancies a challenge? im in a position where bricking this thing isn't really much of a problem so if someones up for a challenge and wants to help im willing to lend myself and the device to this

Warning : Block of Text Ahead.
dazza9075 said:
confirmed, was just going to post this but was beaten to it.
In terms of a ROM do we not need a compatible boot loader that will allow unsigned ROMs?
ive attached the file but please go to that website and pay homage to whoever did this work...now to find a man about a ROM
Sent from my Arc using xda app-developers app
Click to expand...
Click to collapse
Haha. As soon as I found a thread called "root the Kobo Arc" on Google, I posted it here right away. Sorry if I deprived you of the satisfaction! *troll*
Joking aside, I'm not too sure about the bootloader. I think it's pretty locked down (since I put a nexus 7's cyanogenmod onto the data partition and rebooted. It tried to updated, but said validation failed, or something of that sort). I can't install any custom recoveries either, since I have no idea how to do it in the first place, and there's none made for the Arc.
Also, I analyzed the Arc with the "Droid Examiner" App from the play store (That is a really great app, just so you know), and found that it uses a board called "zeus". The funny thing, though, is that one of Sony's Xperia phones, also has a board called "Zeus", and there's Cyanogenmod for that (albiet not the latest version). However, these two devices have nothing in common. The closest thing to an Arc that has Cyanogenmod is the Nook HD/HD+, which uses the exact same chip (OMAP TI 4470).
If someone is smart enough (not me) to analyze the Cyanogenmod files for the Nook, and see how they work, that may lead into flashing the Arc.
Anyway, I'm resetting the Arc, since I'm having weird cases where the Arc would freeze after booting it from sleep mode, and I'd have to turn it off and on again. I think that was something else I did, since it happened before the root, but neh, I might as well try this all from factory default settings.
Sorry for the block of text, guys!
P.S. Using the stock Jelly Bean boot animation on the Arc looks amazing!:laugh:

Haha, its cool, like yourself I just happened to Google kobo arc root and for once my googe fu was up to the task and the root appeared
I've been looking at starting my own recovery mod branch but its no simple task by the looks of it, if their are similar devices we can use all their data and tweak it to ours which would help a lot!
Oh I think we have fast boot, I held vol down and pushed power on, it just sat at the kobo arc screen, I used the nexus 7 driver from the universal adb/fastboot driver I found on here and it connected up http://forum.xda-developers.com/showthread.php?t=2263822
I stumbled on some to good to be true program on Xda dev that apparently can root anything and unlock any bootloader once your in fastboot mode. I have tried that part and it said it was successful but i have no idea how to test this out yet, the program does a bunch of other stuff too, the adb stuff worked as did apk sending, and the rooting options knew i was rooted, it also has flashing functions, I'll be damed if I can find it now I'm at home though , I'll have another look.
I don't mind doing leg work but if someone can read the map it would be very helpful!
Edit, found it
http://forum.xda-developers.com/showthread.php?t=2399385
http://www.mediafire.com/?vwxpq62pa927s9c
Sent from my Arc using xda app-developers app

dazza9075 said:
Haha, its cool, like yourself I just happened to Google kobo arc root and for once my googe fu was up to the task and the root appeared
I've been looking at starting my own recovery mod branch but its no simple task by the looks of it, if their are similar devices we can use all their data and tweak it to ours which would help a lot!
Oh I think we have fast boot, I held vol down and pushed power on, it just sat at the kobo arc screen, I used the nexus 7 driver from the universal adb/fastboot driver I found on here and it connected up http://forum.xda-developers.com/showthread.php?t=2263822
I stumbled on some to good to be true program on Xda dev that apparently can root anything and unlock any bootloader once your in fastboot mode. I have tried that part and it said it was successful but i have no idea how to test this out yet, the program does a bunch of other stuff too, the adb stuff worked as did apk sending, and the rooting options knew i was rooted, it also has flashing functions, I'll be damed if I can find it now I'm at home though , I'll have another look.
I don't mind doing leg work but if someone can read the map it would be very helpful!
Edit, found it
http://forum.xda-developers.com/showthread.php?t=2399385
http://www.mediafire.com/?vwxpq62pa927s9c
Sent from my Arc using xda app-developers app
Click to expand...
Click to collapse
Um... Okay. I've installed the drivers (I think I installed them correctly), and I booted my device using "volume down + power". I have it connected to my System, but whenever I try to use one of the options in the Android Root Toolkit, it tells me it's waiting for the device. I don't know what I did wrong, but something's clearly not working.
As far as the recovery goes, I think that looking at the Nook Tablet from TWRP would work quite nicely. It runs on a similar processor ( I believe it's a OMAP TI 4430 ), and it seems to be quite similar in specs to the Arc. If only I was a bit better at programming...

ThunderBird2678 said:
Um... Okay. I've installed the drivers (I think I installed them correctly), and I booted my device using "volume down + power". I have it connected to my System, but whenever I try to use one of the options in the Android Root Toolkit, it tells me it's waiting for the device. I don't know what I did wrong, but something's clearly not working.
As far as the recovery goes, I think that looking at the Nook Tablet from TWRP would work quite nicely. It runs on a similar processor ( I believe it's a OMAP TI 4430 ), and it seems to be quite similar in specs to the Arc. If only I was a bit better at programming...
Click to expand...
Click to collapse
im usig the generic android adb driver and the bootloader driver for fast boot
im dumped all partitions and mapped them all out, see below for file system details
But again I'm blindly stabbing in the dark and most tutorials are a bit lacking in depth or not relevant to the kobo :/
Sent from my Arc using xda app-developers app

127|[email protected]:/ # blkid
/dev/block/dm-2: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/dm-1: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/dm-0: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/mmcblk0p12: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/mmcblk0p11: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/mmcblk0p10: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/mmcblk0p4: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
[email protected]:/ #

Okay, so I can't even push apps to the Arc using ADB. I think you have to boot into recovery (power + volume up). I don't know how to use the terminal at all (I'm lost, I know D: ), so I don't have that installed on the Arc. I remember being able to do ADB even with my Sony Reader (First gen, PRST1), so I'm not sure why the Arc isn't quite working. I have both drivers installed, BTW.
As for the recovery, I can't even find a method to flash it. I'm still trying everything I can, though. :\
Sent from my Arc using xda app-developers app

ive mapped out the following partitions and any info ive found about each of them, im not in a position to help at the moment, got a big day at work tomorrow, as mentioned above ive used several tools,
SuperSU,
ROM toolbox pro
busybox
remount
Below is a list of all the available partition names and numbers
/dev/block/mmcblk0p1 xloader
/dev/block/platform/omap/omap_hsmmc.1/by-name/xloader
348KB
/dev/block/mmcblk0p2 bootloader
/dev/block/platform/omap/omap_hsmmc.1/by-name/bootloader
1.50MB
/dev/block/mmcblk0p3 cypto
/dev/block/platform/omap/omap_hsmmc.1/by-name/crypto
Completely empty
64KB partition size
/dev/block/mmcblk0p4 EFS
Mounted as /FACTORY
/dev/block/mmcblk0p4:UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/platform/omap/omap_hsmmc.1/by-name/efs /factory ext4 ro,relatime,barrier=1,data=ordered 0 0
20MB
/dev/block/mmcblk0p5 misc
/dev/block/platform/omap/omap_hsmmc.1/by-name/misc
Completely empty
128KB partition size
/dev/block/mmcblk0p6 Bootlogo
/dev/block/platform/omap/omap_hsmmc.1/by-name/bootlogo
Contains kobo arc picture
4MB partition size
/dev/block/mmcblk0p7 Logos
/dev/block/platform/omap/omap_hsmmc.1/by-name/logos
contains the battery charge logo
28MB partition size
/dev/block/mmcblk0p8 recovery
/dev/block/platform/omap/omap_hsmmc.1/by-name/recovery
data contains a GZ file, when decompressed we get a 8.5MB file of unknown type, exact same as in boot
5MB of data
16MB partition size
/dev/block/mmcblk0p9 boot
/dev/block/platform/omap/omap_hsmmc.1/by-name/boot
data contains a GZ file, when decompressed we get a 8.5MB file of unknown type, exact same as n recovery
4.5MB of data
8MB partition size
/dev/block/mmcblk0p10 CACHE
Mounted as /CACHE
/dev/block/mmcblk0p10: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/platform/omap/omap_hsmmc.1/by-name/cache /cache ext4
rw,nosuid,nodev,noatime,errors=panic,barrier=1,nom blk_io_submit,data=ordered 0
0
768MB partition size
/dev/block/mmcblk0p11 SYSTEM
Mounted as /SYSTEM
/dev/block/mmcblk0p11: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/platform/omap/omap_hsmmc.1/by-name/system /system ext4
rw,relatime,barrier=1,data=ordered 0 0
910MB partition size
/dev/block/mmcblk0p12 USERDATA
Mounted as /DATA
/dev/block/mmcblk0p12: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/platform/omap/omap_hsmmc.1/by-name/userdata /data ext4
rw,nosuid,nodev,noatime,errors=panic,barrier=1,nom blk_io_submit,data=ordered 0
0
12GB partition size

Watching with interest. The root works. No frills CPU installed and working. There may be hope for this thing yet:good:

Moved to new thread and more appropriate forum - keep up the good work guys

im not sure that's going to work you know, ive had some permission errors with adb which suggests the root isn't full, terminal on the device works fine, but adb just has some problems, adb shell and the su seems to fix them.
http://www.gadgetsdna.com/android-terminal-adb-shell-command-list/1168/
http://www.addictivetips.com/android/make-nandroid-backups-on-android-without-booting-into-recovery/
im busy today but ive found these useful
i think Clockwork Recovery should be our focus at this point or if you have dumped your partitions(?) attempt to construct a rom for later use
or this should work too
Install any Custom Recovery with flash_image:
Just like the previous method, this method also requires following advanced steps and is not recommended if the first method is working for you. flash_image is a tool for Android devices that lets you rewrite your phone’s system partitions with partition image files and installing it to your device requires ADB. If you don’t already have ADB installed, check out our guide on installing ADB. Once you have ADB installed, flash the custom recovery image as follows:
WARNING: It is very important that the recovery image that you use in this method is compatible with your device. Else it will not work and flashing it could possibly brick your device.​
Download flash_image and extract it from the zip file to a location on your computer. We extracted it to the main C drive (not in any folder) and will use that in the next steps.
Copy the recovery image for your phone to a convenient location on your computer, preferably with a short path. We will be placing it on the C Drive directly (not in any folder) and using that in the next steps.
Note: The recovery image should have .img extension. If it is in a zip file, extract the .img file from it.
Enable USB debugging mode on your device from Menu > Settings > Applications > Development.
Connect your device to your computer via USB.
Open a Command Prompt window on your computer and enter the following commands: adb push c:\flash_image /sdcard/adb push c:\recovery.img /sdcard/adb shellsumount -o remount, rw /systemcp /sdcard/flash_image /system/bincd /system/binchmod 777 flash_imageflash_image recovery /sdcard/recovery.imgThis will first transfer flash_image and recovery.img to your phone. Then it will copy flash_image to the /system/bin folder of your Android device and make it executable. Finally, it will flash the custom recovery image to your device using flash_image.
Note that we used c:\flash_image and c:\recovery.img in the first two lines as we had these files extracted at the root of our C drive. If you extracted the files elsewhere, use the appropriate paths and if your recovery image has a different name, use the appropriate name.
Reboot your device once the process is finished and you’re done. You may exit adb and the Command Prompt window on your computer by entering ‘exit’ thrice.

dazza9075 said:
im not sure that's going to work you know, ive had some permission errors with adb which suggests the root isn't full, terminal on the device works fine, but adb just has some problems, adb shell and the su seems to fix them.
http://www.gadgetsdna.com/android-terminal-adb-shell-command-list/1168/
http://www.addictivetips.com/android/make-nandroid-backups-on-android-without-booting-into-recovery/
im busy today but ive found these useful
i think Clockwork Recovery should be our focus at this point or if you have dumped your partitions(?) attempt to construct a rom for later use
or this should work too
Install any Custom Recovery with flash_image:
Just like the previous method, this method also requires following advanced steps and is not recommended if the first method is working for you. flash_image is a tool for Android devices that lets you rewrite your phone’s system partitions with partition image files and installing it to your device requires ADB. If you don’t already have ADB installed, check out our guide on installing ADB. Once you have ADB installed, flash the custom recovery image as follows:
WARNING: It is very important that the recovery image that you use in this method is compatible with your device. Else it will not work and flashing it could possibly brick your device.​
Download flash_image and extract it from the zip file to a location on your computer. We extracted it to the main C drive (not in any folder) and will use that in the next steps.
Copy the recovery image for your phone to a convenient location on your computer, preferably with a short path. We will be placing it on the C Drive directly (not in any folder) and using that in the next steps.
Note: The recovery image should have .img extension. If it is in a zip file, extract the .img file from it.
Enable USB debugging mode on your device from Menu > Settings > Applications > Development.
Connect your device to your computer via USB.
Open a Command Prompt window on your computer and enter the following commands: adb push c:\flash_image /sdcard/adb push c:\recovery.img /sdcard/adb shellsumount -o remount, rw /systemcp /sdcard/flash_image /system/bincd /system/binchmod 777 flash_imageflash_image recovery /sdcard/recovery.imgThis will first transfer flash_image and recovery.img to your phone. Then it will copy flash_image to the /system/bin folder of your Android device and make it executable. Finally, it will flash the custom recovery image to your device using flash_image.
Note that we used c:\flash_image and c:\recovery.img in the first two lines as we had these files extracted at the root of our C drive. If you extracted the files elsewhere, use the appropriate paths and if your recovery image has a different name, use the appropriate name.
Reboot your device once the process is finished and you’re done. You may exit adb and the Command Prompt window on your computer by entering ‘exit’ thrice.
Click to expand...
Click to collapse
I've already tried that recovery method (I spent about two hours just googling), and it doesn't work with the Arc. The ADB won't let me push the image over.
As for Cyanogenmod, I tried something yesterday. A person on the Mobileread forums (apparently a Kobo employee) put out an update.zip file for the Kobo Arc. The file was quite old, and it's really just the 4.1.1 update that (I hope) we're all running. He said that as long as you put it on the root of the data partition, the Arc will flash it immediately. When I tried taking a Nexus 7's Cyanogenmod file and sticking it in the same place, the Arc started flashing it, but then just said there was an error with the update. So I personally think that you do require a properly signed ROM.
However, if you open up Kobo's update.zip using Winrar, a sidebar pops up that says "signed by SignApk". I don't know too much about this, but couldn't we use this "signapk" to sign our own ROMS and flash them?
Just a thought.

​
ThunderBird2678 said:
As for Cyanogenmod, I tried something yesterday. A person on the Mobileread forums (apparently a Kobo employee) put out an update.zip file for the Kobo Arc. The file was quite old, and it's really just the 4.1.1 update that (I hope) we're all running. He said that as long as you put it on the root of the data partition, the Arc will flash it immediately. When I tried taking a Nexus 7's Cyanogenmod file and sticking it in the same place, the Arc started flashing it, but then just said there was an error with the update. So I personally think that you do require a properly signed ROM.
However, if you open up Kobo's update.zip using Winrar, a sidebar pops up that says "signed by SignApk". I don't know too much about this, but couldn't we use this "signapk" to sign our own ROMS and flash them?
Just a thought.
Click to expand...
Click to collapse
I think there is a problem with the setup, I just flashed a CW recovery image and it worked, or didn't rather! but the concept did, transferred, flashed using adb, I had to replace it though as it was totally borked and kept restarting, apparently the touch based recovery methods can be like that, ill have some good time tomorrow night (UK time) if your about, and ill keep at it tonight if I get a chance!
copy recovery to adb location
adb push recovery.img /sdcard/
adb shell
su
cat /sdcard/recovery.img > /dev/block/platform/omap/omap_hsmmc.1/by-name/recovery
exit adb shell and type
adb reboot recovery
fixed it by holding power button and vol down to boot to fastboot recovery
then ran
fastboot flash recovery inputrecovery.img
inputrecovery being my original recovery file taken from partition 8!
ive updated the partition map on the post above with my progress, but it looks like we can flash to them my name so its probably less relevant now
oh ive ditched the drivers I was using and reinstalled the drivers from the official SDK, generic android adb for within android and android bootloader for fastboot
EDIT
Yaaas!! recovery replaced
ok, deleting or renaming /etc/install-recover.sh appears to have stopped custom recovery being changed back to stock after reboot, I used the recovery builder to make a build from partition 8, which it did without error, flashed using the above commands.​
Still don't know what im doing though, but progress is progress ​
ill post a link to the custom recovery ive made soon, we need to make up some fstab file listing all the mounts etc, i tried one but it must be borked as recovery couldnt see anything​
​

ok i have a working recovery http://jenkins.cyanogenmod.com/job/recovery/35325/artifact/
its not quite done, i need to mount the sdcard, its physical location is mounted, ie /data, but its virtual mount isn't /storage/sdcard
I have asked for some help so hopefully someone can help be on this, I think it needs to be symlinked
im going to need some help soon, so if your reading this with a kobo arc, I need you! im needing a hand folks! if your stuck getting this far let me know and we can PM to get it working
oh and recovery is also now persistant by deleting or renaming /etc/install-recover.sh"

Sorted folks!
I have made a stable and thus far, a working custom recovery.
its mounting everything and backing up / restoring works as it should, unless anyone can find any issues I consider this step in building a complete ROM completed,
you must have root, download arctic.apk and install on your tablet, you will need to enable unknown sources In dev options first
you must have android and java sdk also installed, you will need to add the google usb drivers in the android sdk, you will find them in the "extras"
Enable usb debug on the arc and install the generic google adb usb drivers
Delete or rename /etc/install-recover.sh this will make the custom recovery persistent
Copy the recovery.img to the SDCard, either by using drag and drop in windows ( to root of "internal storage") or by adb push, if you use adb push then remember to copy recovery.img to the same folder as adb
adb push recovery.img /sdcard/
The next job is to open up a command window and navigate to adb folder, type the following exactly, even better copy and paste them!
adb shell
su
cat /sdcard/recovery.img > /dev/block/platform/omap/omap_hsmmc.1/by-name/recovery
exit adb shell (ctrl+C) and type
adb reboot recovery
and bobs your uncle, one happy new recovery

Thanks for your hard work. Everything works quite well.
Sent from my Arc using Tapatalk 4

cancuck said:
Thanks for your hard work. Everything works quite well.
Sent from my Arc using Tapatalk 4
Click to expand...
Click to collapse
that's the easy bit, I have a feeling I need to make a couple of changes to the recovery.img but noting major, just a couple of other mounts I may have missed
I probably would like some help with the next bit however.
im just trying to build a development platform, I have a loathing for Linux as a desktop so will need to re educate myself without throwing my laptop out of the window, after that "challenge" the ROM should be easy

Well, I've just done it, and it works. Everything seems to be in order for the time being. I'm going to muck around with the new capabilities, and see what I can do.

Unofficial linux support thread

So i noticed while searching around to fix things on my device there was a lack of linux support in general, and almost none for the S5, so I thought I would make a support thread for any linux users. This thread will be mainly for posting how-to's for linux but can also be a place to ask any questions you have.

HOW-TO'S:
How to install adb
I'm on linux mint, and this tutorial is based off of how to threads for linux mint, but there shouldn't be much difference in commands other than filenames.
To start you'll need to download the sdk, then run these commands one at a time.
Code:
cd ~
tar -zxvf ~/[download path here]/android-sdk_r23.0.2-linux.tgz
mv android-sdk-linux android
Then we need to update the SDK.
Code:
cd ~
android/tools/android
This should bring up the android SDK manager, the ones you'll want to update/install are:
-Everything under "Android 4.4.2 (API 19)
-Under the tools dropdown, check "Android SDK tools", "Android SDK Platform-tools" and "Android SDK Build-tools" revision 20
Once all that is done you'll need to set your path to include adb.
Code:
cd ~
gedit .bashrc
In the text editor that opens paste the following then save and exit
Code:
export PATH=${PATH}:~/android/sdk/platform-tools
Then we need to make it executable
Code:
cd ~
chmod a+x .bashrc
Then you need to setup device rules
Code:
cd ~
sudo gedit /etc/udev/rules.d/51-android.rules
There is a list of vendor IDs on the android dev website, but for this case Samsung's ID is 04e8 so just paste the following then save and exit.
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0666"
Then we need to make the rules executable
Code:
cd ~
sudo chmod a+x /etc/udev/rules.d/*
Then you should be able to use adb from terminal once you plug your phone in and just do "adb devices" and a prompt should come up on your phone, if it doesnt make sure you have USB debugging enabled on your phone, if it is then unplug your phone and run
Code:
adb kill-server
adb start-server
Then plug your device back in and do "adb devices".
If you are having issues with the server not starting with sufficient permissions you need to add the full path to adb start-server to rc.local, this can be done with the folowing commands.
Code:
cd ~
sudo gedit /etc/rc.local
Then you will need to paste the following above exit 0
Code:
/home/[path]/android/platform-tools/adb start-server
Make sure to replace [path] with the actual name of your home directory then save and exit and reboot your computer, you should be able to use adb properly now.
How to flash odin image files
UNTESTED ON S5
If you have no windows computer available or do but would like to flash on linux, you can try heimdall, but apparently it doesnt fully support the s5 by default and would need to have a patch made to support the new protocol, it may work I havent had a chance to test it though. Another option is jOdin, that has a more familar interface but it has a heimdall backbone afaik so you still need a patch, so for now until said patch is made by the dev or by someone in the community, or it is tested, the only option is get to a windows computer. This section will be updated once one of the two is done.

Thanks so much, I can't believe there isn't more activity in here. I'm about to set my brand new s5 up (root, recovery) using ubuntu, so I'll post what I've learned in here : )

skorasaurus said:
Thanks so much, I can't believe there isn't more activity in here. I'm about to set my brand new s5 up (root, recovery) using ubuntu, so I'll post what I've learned in here : )
Click to expand...
Click to collapse
Nice, tell us how you doing, if you can flash a Firmware with Linux.
ice [N]ation

There is a gs5 pull request on the heimdall github, this could be good....
Sent from my SM-G900P using XDA Free mobile app

I am still getting a handshake error, is it working for anybody else?

miked63017 said:
I am still getting a handshake error, is it working for anybody else?
Click to expand...
Click to collapse
I got it to output my pit file, will test flashing tomorrow and maybe do a pull request or fork if it works.

Users of Debian Wheezy must install libusb-1.0-0-dev from wheezy-backports before compiling Heimdall (apt-get -t wheezy-backports install libusb-1.0-0-dev). I had no luck using it to get anything useful out of my S5.
My experiences in rooting my phone are detailed here: http://forum.xda-developers.com/gal...-build-date-june-3-2014-t2891621/post55826720. I suppose that once Heimdall is modified to talk fluently with the S5, then http://forum.xda-developers.com/att-galaxy-s5/general/g900and3tong3keeprootota-zip-t2862299 should make for a good model for this guide.

dgriffi said:
Users of Debian Wheezy must install libusb-1.0-0-dev from wheezy-backports before compiling Heimdall (apt-get -t wheezy-backports install libusb-1.0-0-dev). I had no luck using it to get anything useful out of my S5.
My experiences in rooting my phone are detailed here: http://forum.xda-developers.com/gal...-build-date-june-3-2014-t2891621/post55826720. I suppose that once Heimdall is modified to talk fluently with the S5, then http://forum.xda-developers.com/att-galaxy-s5/general/g900and3tong3keeprootota-zip-t2862299 should make for a good model for this guide.
Click to expand...
Click to collapse
Yes heimdall will work once it can talk to the s5. However, i have ran into that same problem with the tar that was mentioned in that second link. I have noticed that some files i download from the rogerwilco sites give me that issue, the all in ones from there work fine though. Did you download that tar from the rogerwilco site? Other times it has happened to me was because of a bad download, and redownloading fixed my problem. If the tar is corrupt, even heimdall wont help.
BTW i used libusb-1.0 source from github, heimdall source from github and modified heimdall source in a few places based on the simple usb logger output i got when flashing with odin. I dont think my patches would ever be merged in because it might break compatibility with other models since i had to change the buffer size. Also, i work on opensuse 64bit 13.1, in case anybody ends up trying to follow along. I plan on trying a flash a little later today.

miked63017 said:
Yes heimdall will work once it can talk to the s5. However, i have ran into that same problem with the tar that was mentioned in that second link. I have noticed that some files i download from the rogerwilco sites give me that issue, the all in ones from there work fine though. Did you download that tar from the rogerwilco site? Other times it has happened to me was because of a bad download, and redownloading fixed my problem. If the tar is corrupt, even heimdall wont help.
BTW i used libusb-1.0 source from github, heimdall source from github and modified heimdall source in a few places based on the simple usb logger output i got when flashing with odin. I dont think my patches would ever be merged in because it might break compatibility with other models since i had to change the buffer size. Also, i work on opensuse 64bit 13.1, in case anybody ends up trying to follow along. I plan on trying a flash a little later today.
Click to expand...
Click to collapse
I downloaded from sammobile.com.

Well flashing was a no go, and i cant get consistently working setup ATM. Maybe i will poke around some more throughout the week.

No way,
*with libusb
*with kernel compiled with 32 and 64 bits,
*Debian, LMDE and Ubuntu 14.04.1 (I'm using the latter).
*with jodin3 from my notebook and from the web all with negative results.
Might as well try to flash with heimdall from TTY?
ice [N]ation

Not much progress other than learning a lot about libusb, anybody else have any luck?

miked63017 said:
Not much progress other than learning a lot about libusb, anybody else have any luck?
Click to expand...
Click to collapse
I don't think so :/
ice [N]ation

Any news?
ice [N]ation

As i said, i discusssed it with miked63017, and he informed me there needs to be a modification to get heimdall to work with the s5, this was also mentioned earlier in the thread, jOdin fram what i can tell is a java front end for heimdall so same situation. As was also mentioned a fork was made of heimdall mentioning the s5, that may be worth testing, otherwise something needs to be worked on, privately or as a group.
Sent from my SM-G900A using Tapatalk

Well, I'm willing to help in my humble place
ice [N]ation

Rakuu said:
As i said, i discusssed it with miked63017, and he informed me there needs to be a modification to get heimdall to work with the s5, this was also mentioned earlier in the thread, jOdin fram what i can tell is a java front end for heimdall so same situation. As was also mentioned a fork was made of heimdall mentioning the s5, that may be worth testing, otherwise something needs to be worked on, privately or as a group.
Sent from my SM-G900A using Tapatalk
Click to expand...
Click to collapse
I tested the fork with no luck. Then the thought crossed my mind to rewrite it in ruby, because I am alot better with it than I am with c++. I started, only got as far as finding the device, but it is really ambitious and will take a long time to complete. If anybody thinks they can help I will put it on githib, but be warned it is in really early stages. Let me know otherwise I will keep it to myself until its further along.

Was anyone ever able to get heimdall working on your S5 in Linux? I have been having similar problems getting it to run in Xubuntu 14.10 with my Note 4.
I compiled Heimdall with the S5 patch, even installed the latest libusb, no luck whatsoever. I am getting the following error:
Code:
Initialising protocol...
ERROR: Failed to receive handshake response. Result: -7
ERROR: Protocol initialisation failed!
I just came across this, but didn't try it out yet.

DieHappy said:
Was anyone ever able to get heimdall working on your S5 in Linux? I have been having similar problems getting it to run in Xubuntu 14.10 with my Note 4.
I compiled Heimdall with the S5 patch, even installed the latest libusb, no luck whatsoever. I am getting the following error:
Code:
Initialising protocol...
ERROR: Failed to receive handshake response. Result: -7
ERROR: Protocol initialisation failed!
I just came across this, but didn't try it out yet.
Click to expand...
Click to collapse
Never got it working but might try your link tomorrow if i have time
Sent from my SM-G900P using XDA Free mobile app

Install Custom Recovery, Bootloader and Modem for S5 (g900f) using LINUX

Hey there,
I'd like to install a custom recovery as well as Update my S5's modem and bootloader under linux. How do I do that? The thing I actually find is that I could use Heimdall - but that's one is pretty old and doesn't work out. I'd really like to avoid using Windows since it annoys me any time I use it. >.<
I'm pretty sure some of you might know where I could find propper information. Please be so kind and provide me a few links on where to search!
Thank you!

Hey guys! Actually I did manage getting a custom recovery up and running using Heimdall under linux by following this guide:
If anyone else is having this issue, this solution worked for me running Fedora 22 x64 with kernel version 4.0.5-300 and heimdall-1.4.1-2.fc22.x86_64 installed from the repo.
1) Uninstall Heimdall if you've installed from a repo, download the master branch and build it following the instructions, then navigate to the build/bin folder.
2) Put your phone into download mode and use the command line to detect it:
sudo ./heimdall detect
use the command line and not heimdall-frontend because the latter will fail even if you run it as root. Whatever was causing the error for me, it had something to do with using the frontend.
if you've previously attempted to download the pit and failed, Heimdall will continue to fail until you've disconnect, reconnected, and detected your phone.
3) Using the command line, download your pit file:
sudo ./heimdall download-pit --output mypit.pit
4) Using the command line, flash whatever it is you're trying to flash:
sudo ./heimdall flash --recovery myrecovery.img --pit mypit.pit
EDIT by cRaZy-biScuiT (based on "CavemanNinja"s post) : It's better to use:
sudo ./heimdall flash --RECOVERY myrecovery.img --pit mypit.pit --no-reboot
This way you could boot into the recovery once you've flashed it. Otherwise it may be overwritten.
Hope that helps.
Click to expand...
Click to collapse
source: user "moismailzai" and user "CavemanNinja" .
https://github.com/Benjamin-Dobell/Heimdall/issues/209