Database Develop

[Q] from maemo/meego to android... wtf???

I just switched over to android from maemo and all I have to say is, wheres the linux???
Anyways, I'm trying to get a few things working and the environment si so different. For example when attempting to run clockwork mod in xterm I type the following:
dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6.backup bs=4096
to which I am returned:
2560+0 records in
2560+0 records out
10485760 bytes transferred in 1.461 secs (7177111 bytes/sec)
So I assume everything is going as planned, then I type:
dd if=/data/recovery.img of=/dev/block/mmcblk0p6 bs=4096
to which I am greeted with:
/data/recovery.img: cannot open for read: no such file or directory
ummmm.... what?
and no apt-get?
Can someone direct me somehere t make this transition less, alien? I was hoping I can try and get a meego style rom going for android but alas, I'm stuck at the baby steps...

ieuo said:
I just switched over to android from maemo and all I have to say is, wheres the linux???
Anyways, I'm trying to get a few things working and the environment si so different. For example when attempting to run clockwork mod in xterm I type the following:
dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6.backup bs=4096
to which I am returned:
2560+0 records in
2560+0 records out
10485760 bytes transferred in 1.461 secs (7177111 bytes/sec)
So I assume everything is going as planned, then I type:
dd if=/data/recovery.img of=/dev/block/mmcblk0p6 bs=4096
to which I am greeted with:
/data/recovery.img: cannot open for read: no such file or directory
ummmm.... what?
and no apt-get?
Can someone direct me somehere t make this transition less, alien? I was hoping I can try and get a meego style rom going for android but alas, I'm stuck at the baby steps...
Click to expand...
Click to collapse
For your error: You need to first push a recovery.img to /data before running: # dd if=/data/recovery.img of=/dev/block/mmcblk0p6 bs=4096.
apt-get indeed does not work in android.
The best I could offer you is Google or searching the forums here on xda. For a basic rundown of the android os here a good place to start: http://developer.android.com/index.html

Thanks, honestly I guess I was just hoping for a much more linux feel to the commands.
I'm assuming I MUST push with ADB? I can't just drag and drop?
Sorry for such a basic question, I just thought at lest a few thigs would be the same if it had the linux kernel. Meh, such is tech.

Wow, so I found designgears thread, followed each step exactly and referred to the dev site and I just don't get it. It seems so simple even.
From what I can tell push should do the exact same as a drop to root sd (or wherever else I specify).
When I push in ADB, it just runs ADB with no signs of any push event happening. Ok I've seen things like that before when working with maemo.
Then if I move forward, I get the same resut as if I had just dropped into my root sd, which I must assume works, because xterm and ADB give the same output. Then I go to flash, and errors galore.
I have all the drivers, and have triple checked the android dev site plus a vast number of searches on google and here.
My mistakes HAVE to be on some basic level. Either wrong directory or wrong pathname. However, I check, recheck, and the triple reference my coding, followed by checking again. If I can't do a simple push and flash I can't even start anything with android.
I'm beggining to think I should have just posted in a different area as my single simple question goes much deeper than I thought....

If you can... post a very detailed run down of exactly what u did and the commands u used... see if we cant isolate the error
Sent from my LG Thrill 4G...

So just to clarify, are you using ADB or xterm ?
And push does the same as drag drop, but with normal sdcard mount, you do not have access to \system, \data etc. you only have access to \sdcard. So its useful to use adb is you want to push files to any of these directories.
ieuo said:
Wow, so I found designgears thread, followed each step exactly and referred to the dev site and I just don't get it. It seems so simple even.
From what I can tell push should do the exact same as a drop to root sd (or wherever else I specify).
When I push in ADB, it just runs ADB with no signs of any push event happening. Ok I've seen things like that before when working with maemo.
Then if I move forward, I get the same resut as if I had just dropped into my root sd, which I must assume works, because xterm and ADB give the same output. Then I go to flash, and errors galore.
I have all the drivers, and have triple checked the android dev site plus a vast number of searches on google and here.
My mistakes HAVE to be on some basic level. Either wrong directory or wrong pathname. However, I check, recheck, and the triple reference my coding, followed by checking again. If I can't do a simple push and flash I can't even start anything with android.
I'm beggining to think I should have just posted in a different area as my single simple question goes much deeper than I thought....
Click to expand...
Click to collapse

Well I would post all of that but as of today the 3d option in video player went missing so I did a factory reset and as the phone rebooted I was in clockwork mod. I can only assume my code was fine and that something is odd with my phone. Might have to get a replacement this weekend.

CM10 development for Kindle Fire HD 8.9"

Hi all!
Without much ado I am presenting you this repo for CM10 that lets you build somewhat functional CM10 ROM for Kindle Fire HD 8.9".
(Obviously this is not end-user friendly yet. If you don't know how to compile CM10 yourself, you are not a target audience for this yet, sorry. Many things don't work to make it viable main ROM yet anyway)
Build instructions (assuming you met all other CM10 build dependencies).
Download code:
Code:
mkdir android/system
cd android/system
curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/repo
chmod a+x ~/repo
repo init -u git://github.com/CyanogenMod/android.git -b jellybean
wget -O .repo/local_manifest.xml https://github.com/verygreen/android_manifests/raw/master/bowser-jb/local_manifest.xml
repo sync -j16
Build:
Code:
. build/envsetup.sh
lunch cm_bowser-userdebug
. vendor/cm/get-prebuilts
mka bacon
In the out/target/product/bowser output dir you'll have two important files generated:
recovery.img and cm-10-XXXXXXXX-UNOFFICIAL-bowser.zip
For the first install only:
Step 0; Connect kindle to your computer, have android sdk installed and adb and fastboot in the path.
Step 1: (very important) Back up raw partitions from kindle responsible for recovery, boot and system.
(this requires root, though root-less installation is also possible, you will need the backups to return to stock!)
Code:
adb shell su -c "chmod 777 /dev/block/*"
adb pull /dev/block/mmcblk0p9
adb pull /dev/block/mmcblk0p10
adb pull /dev/block/mmcblk0p11
[code]
Save these block images.
Step 2: Prepare and run CWM:
[code]
rm -f /tmp/stack; for i in $(seq 1024) ; do echo -ne '\x00\x50\x7c\x80' >>/tmp/stack ; done
adb push /tmp/stack /data/local/tmp/
adb shell su -c "dd if=/data/local/tmp/stack of=/dev/block/platform/omap/omap_hsmmc.1/by-name/boot bs=6519488 seek=1"
adb shell su -c "chmod 777 /cache"
adb push /path/to/cm-10-XXXXXXXX-UNOFFICIAL-bowser.zip /cache/
adb shell su -c "echo 0 > /sys/block/mmcblk0boot0/force_ro"
adb shell su -c "echo -n 3 | dd of=/dev/block/mmcblk0boot0 bs=1 count=1 seek=4104"
fastboot flash recovery /path/to/recovery.img -i 0x1949
This last command will stop waiting for the fastboot device to appear. Do not unplug the kindle from USB.
Now reboot kindle: either power it off and on via it's GUI, or do adb reboot from a different terminal session (do not interrupt fastboot command still waiting!)
You'll see a "fastboot mode" on the screen and fastboot command started earlier will finally finish after writing the image onto the kindle.
Reboot kindle again via fastboot:
Code:
fastboot reboot -i 0x1949
This will reboot you into CWM recovery
Step 3: In CWM recovery, do install from sdcard and install the cm-10...zip file we transferred in the previous step.
the /data/ settings from stock amazon install are not compatible with CM10, but (very important)Do not reformat /data/ and /cache from CWM, this will result in a corrupted filesystem due to 3.0.21 kernel currently used by amazon not having necessary fs features!!!
Instead, clean /data via adb while booted to CWM:
Code:
adb shell "mount /data"
adb shell "rm -r /data/*"
Step 4: Now, installation is complete, you may reboot and it will bring you to your freshly-installed CM10 - enjoy.
(note by default this CM10 install starts with adb disabled, so you'll need to enable it in settings again).
How to reflash back to stock
Step 1: Remember where did you put those backups from step 1 during install.
Step 2:
Code:
fastboot flash recovery /path/to/mmcblk0p9 -i 0x1949
Now either connect a powered off kindle, or reboot an already connected kindle.
(note: I don't remember if stock rom is smart enough to wipe /data in this case or if it bootloops, so you might want to do rm -r /data/* before the final reboot)
once Kindle enters fastboot mode and recovery image is written, write the other two images too:
Code:
fastboot flash boot /path/to/mmcblk0p10 -i 0x1949
fastboot flash system /path/to/mmcblk0p11 -i 0x1949 # This one will take a few minutes
fastboot reboot -i 0x1949
Now you are back to factory stock.
Not so short video on the install starting from somewhere around step 3 for those who cannot perform the steps, but need to ensure this ROM is not for them yet:
Many things don't work yet:
- Sound
- Video playback
- Sensors (no rotation)
- Camera
- BT
- probably some other stuff I have not noticed yet.
Please do send in your patches/fixes.

Very cool, I'm gonna give this a try when I get some time tomorrow.
Thanks!

Neato(tm)!
Sent from my Nexus 4 using xda app-developers app

These are some amazing news!
Thanks a lot, verygreen. You are doing a really importaint thing. In my country no amazon services work, so the stock ROM is the biggest problem with Kindle 8.9.
Looking forward for the next builds!
Best regards.

Sorry if this is a stupid/annoying/heard it a million times please shut up already question, but does this mean anything the 7" variant?

xDecapitator said:
Sorry if this is a stupid/annoying/heard it a million times please shut up already question, but does this mean anything the 7" variant?
Click to expand...
Click to collapse
Eventually, this will translate to the Kindle Fire HD 7" as well. :fingers-crossed:

So, can you tell us what is the status of the build right now? What works fine, what doesn't? When can we see the first build to test?
Thanks for your answers and best regards!

This question belongs in general discussion not Development
Witcher_Kh said:
So, can you tell us what is the status of the build right now? What works fine, what doesn't? When can we see the first build to test?
Thanks for your answers and best regards!
Click to expand...
Click to collapse
I am not the first to answer your question in the following manner and I am sure I won't be the last. These developers spend hours of their free time developing code so that people like you and I can use it without paying unless it is through a donation to the developer. They typically don't have time to answer every person who asks when will the code be ready. so for you and others who are not developers your answer is:
"The next release will be ready when it is released and not until."

Early stages with such promise, hoping for a HD 7" inch variant

I'm assuming that with CM10, you won't be able to use all the special Amazon services like Amazon videos, lending library, etc. Doesn't that take away the whole point of buying a Kindle fire HD?

somdave2005 said:
I'm assuming that with CM10, you won't be able to use all the special Amazon services like Amazon videos, lending library, etc. Doesn't that take away the whole point of buying a Kindle fire HD?
Click to expand...
Click to collapse
Uh, wut?

somdave2005 said:
I'm assuming that with CM10, you won't be able to use all the special Amazon services like Amazon videos, lending library, etc. Doesn't that take away the whole point of buying a Kindle fire HD?
Click to expand...
Click to collapse
No - KF HD is a beautiful piece of hardware at a nice price, crippled by Amazons software. Where I live, almost all Amazon content is blocked anyway, so I won't lose anything. Amazon ebooks are basically the only content available to me, but that's just a matter of installing the Kindle app in CM.

eagerly watching and waiting... i havent got the stones to try it out now but ill test the first alpha! thanks for your work

Very very nice. Just waiting hopefully the developers will completed soon.

What about KFHD 7" ? If CM10 will work for KFHD 8.9", will work for 7" too or not? Sorry my english, please.

I am eager to try working this over to the 7HD but it might be premature. Do you guys think this software will still work with the fire 2 and 7HD?
Sent from my EVO using Tapatalk 2

craby1925 said:
I am eager to try working this over to the 7HD but it might be premature. Do you guys think this software will still work with the fire 2 and 7HD?
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
I thought i ask the same. I have KFHD 7" as well and want to try CM10 on it..

esox_hu said:
I thought i ask the same. I have KFHD 7" as well and want to try CM10 on it..
Click to expand...
Click to collapse
Just to clear this up.
I do not have Kindle Fire HD 7" and so I cannot try.
We've got a volunteer to try this at irc and bootloader unlock works the same way (as expected, but you need a different bootloader binary).
We were not able to get anything to show up on the screen after booting CM10, thought it appears the OS boots and behaves fine, backlight is on too.
Anyway, I'd much rather prefer people to buy Nexus 7, it costs the same as Kindle Fire HD 7, but is a much more open device with much more developer support.
If you need CM10 and further, get Nexus 7 and you'll be soo much more happier. You still can run kindle app on it to read your books if you so desire.
With this out of the way, let's not touch on the 7" device topic here anymore, it's for 8.9" development discussion only. Thank you for your understanding.

Yes, exactly.
verygreen said:
Anyway, I'd much rather prefer people to buy Nexus 7, it costs the same as Kindle Fire HD 7, but is a much more open device with much more developer support.
If you need CM10 and further, get Nexus 7 and you'll be soo much more happier. You still can run kindle app on it to read your books if you so desire.
Click to expand...
Click to collapse
Hear, hear!
The N7 is an amazing deal, has incredible specs with pretty much everything included, AND it's been made easily unlockable by the distributor. To anyone who wants continued access to devices in the future, there's no reason to support closed, locked systems.
So I just want to voice my agreement. If you're in the market for a 7" tablet, N7 > Kindle Fire HD 7".
Pass it on.

fattire said:
Hear, hear!
The N7 is an amazing deal, has incredible specs with pretty much everything included, AND it's been made easily unlockable by the distributor. To anyone who wants continued access to devices in the future, there's no reason to support closed, locked systems.
So I just want to voice my agreement. If you're in the market for a 7" tablet, N7 > Kindle Fire HD 7".
Pass it on.
Click to expand...
Click to collapse
I would have gotten the N7 but I wanted a larger screen.

[Q] Kindle Fire 2 won't turn back on / screen stays black after pushing twrp

I did something stupid.
After spending a whole day on figuring out how to root my kindle fire 2 and install android 4.1, I nailed it by trying to push TWRP to my previously rooted kindle (using the kindle hd method) using:
Code:
adb push u-boot.bin /sdcard/
adb push twrp-blaze-2.0.0RC0.img /sdcard/
adb shell
su
dd if=/sdcard/twrp-blaze-2.0.0RC0.img of=/dev/block/mmcblk0p5
dd if=/sdcard/u-boot.bin of=/dev/block/mmcblk0p2
exit
adb reboot
The screen never went back on and just stays black. It doesn't even seem to get any power at all anymore, no usb-connection, nothing. I tried holding the power-button for a very very long time, but nothing works. I tried charging on different computers and adapters and even praying. Even the light of the power-button doesn't show any reaction whatsover.
While I expected things to go wrong, I didn't expect them to go wrong in such a manner. What kind of most vicious root protection is that? Is there any hope? Does anybody have an idea?
Help would be very much appreaciated.

JohannesJo said:
I did something stupid.
After spending a whole day on figuring out how to root my kindle fire 2 and install android 4.1, I nailed it by trying to push TWRP to my previously rooted kindle (using the kindle hd method) using:
Code:
adb push u-boot.bin /sdcard/
adb push twrp-blaze-2.0.0RC0.img /sdcard/
adb shell
su
dd if=/sdcard/twrp-blaze-2.0.0RC0.img of=/dev/block/mmcblk0p5
dd if=/sdcard/u-boot.bin of=/dev/block/mmcblk0p2
exit
adb reboot
The screen never went back on and just stays black. It doesn't even seem to get any power at all anymore, no usb-connection, nothing. I tried holding the power-button for a very very long time, but nothing works. I tried charging on different computers and adapters and even praying. Even the light of the power-button doesn't show any reaction whatsover.
While I expected things to go wrong, I didn't expect them to go wrong in such a manner. What kind of most vicious root protection is that? Is there any hope? Does anybody have an idea?
Help would be very much appreaciated.
Click to expand...
Click to collapse
Brick its dead tell the shop it won't turn on anymore and you don't know why
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

thanks
dank101 said:
Brick its dead tell the shop it won't turn on anymore and you don't know why
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Thank you, that is exactly what I already did. I still wonder about the technical side of this. They send me a new one. I hope, I dont get any trouble, if they might check the old one....
Do you think, it is an acutal mechanism established by amazon to prevent the device from being rooted and manipulated? g rooted and manipulated?

[Q] Bricked fire, Need help with fire kit

I have a rooted kindle with burrito root 10 months ago and now and tried to install cm10.
thought it went ok but is stuck in bootloop showing splash screen. Brick.
I must have messed up the bootloader because I can't get anywhere with KFU other than the device is online.
I reinstalled drivers, tried to reinstall FFF, twrp. no luck.
i've been reading threads a good part of the day and found fire kit with ubuntu running via USB.
I did that, then ran,
"sudo /cdrom/fk"
then I tried "usb_fix_parts_and_install_fff_twrp"
It failed saying "no such file or directory"
I'm not super familiar with ubuntu or their code.
Please help me unbrick this.

amscomputerpro said:
I have a rooted kindle with burrito root 10 months ago and now and tried to install cm10.
thought it went ok but is stuck in bootloop showing splash screen. Brick.
I must have messed up the bootloader because I can't get anywhere with KFU other than the device is online.
I reinstalled drivers, tried to reinstall FFF, twrp. no luck.
i've been reading threads a good part of the day and found fire kit with ubuntu running via USB.
I did that, then ran,
"sudo /cdrom/fk"
then I tried "usb_fix_parts_and_install_fff_twrp"
It failed saying "no such file or directory"
I'm not super familiar with ubuntu or their code.
Please help me unbrick this.
Click to expand...
Click to collapse
From what you wrote I suppose that you have original Kindle Fire and not Kindle Fire HD...
Anyway you could take a look on this thread.. someone wrote that he was able fix Booting loop with it
http://forum.xda-developers.com/showthread.php?t=1896570
I hope it will help you,
Kerbik

Bricked Kindle Fire in bootloop.
Kerbik said:
From what you wrote I suppose that you have original Kindle Fire and not Kindle Fire HD...
Anyway you could take a look on this thread.. someone wrote that he was able fix Booting loop with it
http://forum.xda-developers.com/showthread.php?t=1896570
I hope it will help you,
Kerbik
Click to expand...
Click to collapse
Yes, I have a original KF. Thanks for the thread.
I downloaded the file called "7.1.5_stock_build.prop.zip".
I don't seem to know as much as I thought I did with command prompt because I can't seem to get it to load.
what directory should stock_build _pro file be in?
I followed the following script:
Code:
# adb shell
# echo 'ro.kernel.qemu=1' > /data/local.prop
I then get the following error:
* daemon not running. starting it now *
* daemon started successfully *
[email protected]:/ $ echo 'ro.kernel.qemu=1' > /data/local.prop
echo 'ro.kernel.qemu=1' > /data/local.prop
/system/bin/sh: can't create /data/local.prop: Permission denied
1|[email protected]:/ $

Wrong forum...
"I downloaded the file called "7.1.5_stock_build.prop.zip"."
I may be wrong, but I think that file is only for the HD, not the Gen 1 model (last year's model). If you jam it on your device you'll likely only make it worse (assuming you can get worse than bricked!)!
You need to get over to the Gen 1 forum as this is one for the HD series and won't be of any help to you.
Link:
http://forum.xda-developers.com/forumdisplay.php?f=1306

no99sqrd said:
"I downloaded the file called "7.1.5_stock_build.prop.zip"."
I may be wrong, but I think that file is only for the HD, not the Gen 1 model (last year's model). If you jam it on your device you'll likely only make it worse (assuming you can get worse than bricked!)!
You need to get over to the Gen 1 forum as this is one for the HD series and won't be of any help to you.
Link:
http://forum.xda-developers.com/forumdisplay.php?f=1306
Click to expand...
Click to collapse
ok thanks.

[Q] [Root] KFHD "7 | HowTo Root on Mac?

I don´t get it managed to root my KFHD "7.
It´s on 11.3.2 and I´m using the stock USB Cable (is factory cable mandatory?). I made chmod 777 for the RunMe.sh and I´m running a MacBook Pro on Mavericks.
"./adb devices" shows my device...
I already found this http://forum.xda-developers.com/showpost.php?p=50985251&postcount=347
I absolutely do not understand, why it won´t work. Of course for some of you it will become absolutely obvious, why it won´t work, when they read this.
This is what I get:
Normal mode enabled!
Checking if i should run in Normal Mode or special Sony Mode
Please connect device with ADB-Debugging enabled now ...
remote object '/system/bin/ric' does not exist
remote object '/system/app/Backup-Restore.apk' does not exist
Normal Mode enabled!
Please connect device with ADB-Debugging enabled now ...
Pushing busybox ...
5178 KB/s (1085140 bytes in 0.204s)
Pushing su binary ...
4653 KB/s (91980 bytes in 0.019s)
Pushing Superuser app
5267 KB/s (996704 bytes in 0.184s)
Pushing ric
26 KB/s (57 bytes in 0.002s)
Making busybox runable ...
Now unlock your device and confirm the restore operation.
Please look at your device and click RESTORE!
If all is successful i will tell you, if not this shell will run forever.
Running ...
Successful, going to reboot your device in 10 seconds!
Waiting for device to show up again ...
Copying files to it's place ...
mount: permission denied (are you root?)
You can close all open command-prompts now!
After reboot all is done! Have fun!
Bin4ry
Click to expand...
Click to collapse
Yes, I´m root user on the Mac.
Thanks for your help!
Ps: These are the threads I already read and I´m looking at...
[ROOT] How To: Root the Kindle Fire 7" HD or 2 with Linux/MAC - Noob (Simple) Version
manual fastboot whitout factory cable... regarding that, the factory cable doesn´t seem to be mandatory for rooting the device?!
[BOOTLOADER] 2nd-bootloader for Custom ROMs on KFireHD 7" [12/09 FREEDOM 7.4.6]
That´s what I want on the KFHD: [ROM-AOSP] Unofficial CM11.0 KFire HD 7 (KK 4.4_r1.2) [03/25 CODEC FIXES]

You can't put custom ROMs on the 2013 HD(which I identified by the 11.x.x os), only root access. On another note I just realized that that rooting thread for the 2013 HD didn't have a Linux/Unix compatible rooting script, only a batch file which is for windows, I assume the script is pretty simple, haven't looked at it yet. How about I convert it to bash and see if it will work for ya? I'll just have to grab the mac location for bash but other than that its pretty straightforward.
Sent from my Amazon Kindle Fire HD using Tapatalk

stunts513 said:
You can't put custom ROMs on the 2013 HD(which I identified by the 11.x.x os), only root access.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
It´s this one: http://www.amazon.de/Kindle-Fire-Zoll-HD-Display-WLAN/dp/B00CTV13Z4/ref=sr_tr_sr_1?s=digital-text&ie=UTF8&qid=1397119675&sr=1-1&keywords=fire+hd

Yea that's a 2013 model, we can't install ROMs on that model, also reread my post, I was editing it when you answered back.
Sent from my Amazon Kindle Fire HD using Tapatalk

stunts513 said:
Yea that's a 2013 model, we can't install ROMs on that model, also reread my post, I was editing it when you answered back.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
I read it now. Thanks, that would be great. Althought I will most probably send it back, because I were not aware of that fact and the stock ROM is slow and ugly ? But nevertheless that would be good for other Mac users too, I think ?

I'll post it tomorrow as I'm going to bed, I don't wanna work on it while I'm half asleep.
Sent from my Amazon Kindle Fire HD using Tapatalk