Database Develop

Problem installing kernel - need help!

Hi there.
New to the forum and rooting. I have a Samsung Galaxy S Captivate and also have rooted using z4 root. I tried installing the kernel SuperFast v1.1.23 and now have a big problem. I used Rom Manager to "install ROM using SD" and selected the kernel zip file that I saved onto the external SD card. It appeared to install properly and then started to boot...however it's just stuck there looping between the words "I896" and "SAMSUNG". I got to the Android system recovery <2e> manual screen and "reboot system now" just takes me back to the rotating text.
when i tried "apply sdcard:update.zip", i get a "E:signature verification failed
Installation aborted." but this option will no longer work anyways because my batter is low.
NEED HELP!!

drumega said:
Hi there.
New to the forum and rooting. I have a Samsung Galaxy S Captivate and also have rooted using z4 root. I tried installing the kernel SuperFast v1.1.23 and now have a big problem. I used Rom Manager to "install ROM using SD" and selected the kernel zip file that I saved onto the external SD card. It appeared to install properly and then started to boot...however it's just stuck there looping between the words "I896" and "SAMSUNG". I got to the Android system recovery <2e> manual screen and "reboot system now" just takes me back to the rotating text.
when i tried "apply sdcard:update.zip", i get a "E:signature verification failed
Installation aborted." but this option will no longer work anyways because my batter is low.
NEED HELP!!
Click to expand...
Click to collapse
you need ODIN and to get your phone in download mode....
i dont even know what SuperFast v...... is.
its not a kernel provided here on the captivate forums...so, dont know what to tell you. load up ODIN, put your phone in download mode and flash back the proper kernel

Please take this to the right forum...this is development!

drumega said:
I tried installing the kernel SuperFast v1.1.23
Click to expand...
Click to collapse
Perhaps that is your problem, you installed an htc kernel on a samsung phone...
Use this to get back to stock and stay away from the htc section.
And don't post in the dev section either, its for developers only.

peachpuff said:
Perhaps that is your problem, you installed an htc kernel on a samsung phone...
Use this to get back to stock and stay away from the htc section.
And don't post in the dev section either, its for developers only.
Click to expand...
Click to collapse
wtf!?
to the OP, if you really did try flashing an HTC kernel on your samsung, please do us all a favor:
return your phone and get yourself an iphail.

Thanks for the input everyone. And I will make sure to post in the correct section next time!

Pirateghost said:
wtf!?
to the OP, if you really did try flashing an HTC kernel on your samsung, please do us all a favor:
return your phone and get yourself an iphail.
Click to expand...
Click to collapse
Actually no. It was a kernel for the Samsung Galaxy Fascinate. I accidentally installed it on my Captivate. If you really don't have any useful suggestions, you should go troll other posts instead. thanks.

drumega said:
Actually no. It was a kernel for the Samsung Galaxy Fascinate. I accidentally installed it on my Captivate. If you really don't have any useful suggestions, you should go troll other posts instead. thanks.
Click to expand...
Click to collapse
reading fail
also, i attempted to help you out already and DID NOT tell you you were posting in the wrong location....
i am still trying to fathom why you would attempt to load a kernel like that on your phone. i was responding to someone else who said that the kernel was an HTC kernel....
but on the other hand, congratulations on almost ruining your phone!

Ok...so I was able to restore my Rogers Samsung Captivate (I896) back to its original Rogers settings.
Phone turns on and seems to be working properly.
I reinstalled the Samsung mobile drivers from and used Heimdall to restore my phone using the downloaded file "I896UXJI2-homebinary".
So now I noticed 2 issues:
1. The 3G isn't registering/working.
2. Noticed my internaly SD memory has dropped significantly. Was originally at about 16GB, but now down to 1.5GB.
Any suggestions??

just following up. any suggestions on my issues in the post above?
thanks

TWRP Port to TMO Note

Hi, I would like to port TWRP to the TMO Galaxy Note but since I don't have one I need help from people with the phone. I ported TWRP to the ATT Galaxy Note: http://forum.xda-developers.com/showthread.php?t=1647575.
If someone who has rooted can give me the output of the following commands as root in adb shell or a terminal on the phone:
cat /proc/partitions
cat /proc/emmc
busybox fdisk -l /dev/block/mmcblk0
Thanks!
If anyone is feeling frisky, they can dd this to their recovery partition (/dev/block/mmcblk0p22 at least on the att note)
Don't blame me for borking and make sure that this partition is the right partition. It looks like the cwm touch version in the dev section is a clone of braway's CWM touch so I am guessing they have the same partitions.
Good luck!

I can do this when I get back in for the night. Anything to help move along the development section of this device!!

is there any added benefit in doing this?
i've been using twrp 2.2.1 on my TMO note since day one. I used odin flash CWM then CWM to flash the ATT twrp from teamwins website and have experienced no issues at all.
not trying to discourage development in anyway but if it already exists and works correctly what would be the advantage?

pxldtz said:
is there any added benefit in doing this?
i've been using twrp 2.2.1 on my TMO note since day one. I used odin flash CWM then CWM to flash the ATT twrp from teamwins website and have experienced no issues at all.
not trying to discourage development in anyway but if it already exists and works correctly what would be the advantage?
Click to expand...
Click to collapse
Odds are the devices are identical, but this build will give a device name of "quincytmo" instead of "quincyatt" which may be important for zip files. Most ROMs do a check before installing called an assert where they check the device name to ensure that you're installing the correct ROM for your device.
Still, glad to hear that you've been using TWRP without issue.

Really dont have to port it just use twrp in the at&t dev section i been using for a week works flawlessly and im on a native tmobile note
Didnt read prior post my bad
Sent from my SAMSUNG-SGH-I717 using xda premium

Dees_Troy said:
Odds are the devices are identical, but this build will give a device name of "quincytmo" instead of "quincyatt" which may be important for zip files. Most ROMs do a check before installing called an assert where they check the device name to ensure that you're installing the correct ROM for your device.
Still, glad to hear that you've been using TWRP without issue.
Click to expand...
Click to collapse
that's a valid point. like i said i'm not trying to hinder development, but thanks for answering

bigbiff said:
Hi, I would like to port TWRP to the TMO Galaxy Note but since I don't have one I need help from people with the phone. I ported TWRP to the ATT Galaxy Note: http://forum.xda-developers.com/showthread.php?t=1647575.
If someone who has rooted can give me the output of the following commands as root in adb shell or a terminal on the phone:
cat /proc/partitions
cat /proc/emmc
busybox fdisk -l /dev/block/mmcblk0
Thanks!
If anyone is feeling frisky, they can dd this to their recovery partition (/dev/block/mmcblk0p22 at least on the att note)
Don't blame me for borking and make sure that this partition is the right partition. It looks like the cwm touch version in the dev section is a clone of braway's CWM touch so I am guessing they have the same partitions.
Good luck!
Click to expand...
Click to collapse
Here is the result for /partitions
- For /emmc, result is "no such file or directory"
- For busybox, apparently I didn't have that installed, downloading and installing now, but will take a few minutes because I'm throttled. Will update post with results from that after.
While as others have stated, it's not "necessary" to port over since the ATT version works, I'm more than happy to help to have a version for THIS model, as there are obviously differences between the i717 and the T879. This is apparent because not all ROMS for the i717 work on the T879. Having our own version of TWRP just solidifies the 879 as it's own entity, not just an "also ran"

Android Revolution said:
Here is the result for /partitions
- For /emmc, result is "no such file or directory"
- For busybox, apparently I didn't have that installed, downloading and installing now, but will take a few minutes because I'm throttled. Will update post with results from that after.
While as others have stated, it's not "necessary" to port over since the ATT version works, I'm more than happy to help to have a version for THIS model, as there are obviously differences between the i717 and the T879. This is apparent because not all ROMS for the i717 work on the T879. Having our own version of TWRP just solidifies the 879 as it's own entity, not just an "also ran"
Click to expand...
Click to collapse
I went ahead and posted a t879 friendly image in Development forum. I also added it to goo manager. If you guys could test and report back that would be great.

NEXUS 7 3G-"nakasig" - Jelly Bean/KitKat Discussions, Problems and Solutions

NEXUS 7 3G-"nakasig" - Jelly Bean/KitKat Discussions, Problems and Solutions
Hi Nexus 7 "Nakasig" users,
I would like to consider this thread as your one place to chat or anything else related to Jelly Bean on the NEXUS 7 - 3G
I need everyone help to keep this thread somewhat sane, report any trolling or flaming and don't respond to it.
Keep all your posts in this thread polite and make sure you follow The Forum Rules.
I request you to stop posting:
- 'Thanks this helped'
- 'Yeah Me too'
-'+1'
These kind of posts are useless instead use the thanks button to show your appreciation
Click to expand...
Click to collapse
For all your JB needs, go to:
==>[Index] All for NEXUS 7 - "Nakasig" - (GSM/HSPA+)
==>[GUIDE] Unlock and Root a Nexus 7 3G “Nakasig- Tilapia”
==> [GUIDE][BOOTLOADER][4.3] TILAPIA JWR66V - 4.23 Flash Image Instructions - UPDATE
==>[GUIDE]If you need some help for install SDK and ADB drivers in Win 7, you can use this guide which is really good and comprehensive for all of us
It will be better for you to find one thread where we can concentrate all discussions, problems and solutions for the Nexus 7 3G ​

It 's a tool which is very good if you want to buy a Google Nexus Devices :good:
Google Nexus Devices World Availability Checker

Top man!
Any one got a working recovery and supersu/superuser that works with 4.2?
Since I've heard people losing 3G and stuff when they rooted, and I kinda don't want to have to set my stuff up again

WarningHPB said:
Top man!
Any one got a working recovery and supersu/superuser that works with 4.2?
Since I've heard people losing 3G and stuff when they rooted, and I kinda don't want to have to set my stuff up again
Click to expand...
Click to collapse
You've probably heard that from idiots who don't know what they are doing.
The latest version of TWRP works perfectly fine with 4.2 (3G and not). I'm using it on my 3G without any issues.
And the previous 'su' binaries and apk's should be fine. Neither of them should cause any problems with the 3G functionality as they have nothing to do with it. I installed custom recovery and rooted mine the day I got it. Everything is perfect.
Also, absolute worst case scenario, if you do screw something up, it's easy to revert without losing all of your data.

Hmm...I don't consider myself an idiot but did nothing more sinister than root and flash CWM and lost cellular data functionality completely at random two days later (unknown baseband). Had about 6 Android devices before this going back to HTC Hero, flashed all sorts, and never seen anything like it. Eventually had to flash factory image to get it back. Not especially helpful as inexplicable and not reproduced but worth saying nonetheless.

dave_uk said:
Hmm...I don't consider myself an idiot but did nothing more sinister than root and flash CWM and lost cellular data functionality completely at random two days later (unknown baseband). Had about 6 Android devices before this going back to HTC Hero, flashed all sorts, and never seen anything like it. Eventually had to flash factory image to get it back. Not especially helpful as inexplicable and not reproduced but worth saying nonetheless.
Click to expand...
Click to collapse
FYI, there seems to be a sporadic bug in JB on my GNex where on certain reboots it says Unknown Baseband and IMEI in the About menu, and then on the next reboot it's fine. I am wondering if that same bug is cropping up on the N7, and it's just coincidentally happening on some people's devices after rooting, but it goes away later. On my GNex this issue is particularly noticeable if I gave the phone a full reboot from inside software (e.g. using the app Easy Reboot). Whereas a power off / power on does not as frequently run into this issue.

I'm looking forward to getting mine Ordered today and it shipped today! I'm going to give my 16gb (bought in Aug for $249 so no price mod for me ) to either my GF or my daughter. lol
Sorry for the OT post.. I'm just excited. It will be nice to not have to tether my N7 to my phone. I just switched to the shared data plan on AT&T so it will only cost me $10 to add the N7 to my plan

Just fired up my 3g and will root it tomorrow, is there anything really different in rooting this thing vs the 16gb, anything I should watch out for?

kitsunisan said:
Just fired up my 3g and will root it tomorrow, is there anything really different in rooting this thing vs the 16gb, anything I should watch out for?
Click to expand...
Click to collapse
No, they are identical from a rooting perspective. However, they do run slightly different versions of the image, so if you wind up flashing stock, use the right one.

so first my success, i have managed to get root and a TWRP recovery.
now my question in menus im seeing horizontal lines that move with the landscape. so as the phone rotates the screen, the lines also rotate. maybe its just the background design but it seems really awkward to me that they would intend from these lighter brighter lines to be there

if someone would do me a HUGE favor and get me a stock JVP15S recovery? i flashed over mine with CWM before i could back it up and now i have a 34mg OTA update i cant take because of the custom recovery image

death 90 said:
if someone would do me a HUGE favor and get me a stock JVP15S recovery? i flashed over mine with CWM before i could back it up and now i have a 34mg OTA update i cant take because of the custom recovery image
Click to expand...
Click to collapse
I'm not sure that you will find someone who can give you this file, cause it contains all personal data and apps.

death 90 said:
if someone would do me a HUGE favor and get me a stock JVP15S recovery? i flashed over mine with CWM before i could back it up and now i have a 34mg OTA update i cant take because of the custom recovery image
Click to expand...
Click to collapse
I don't have my N7 yet, but on most Androids the stock recovery images do not vary much or at all between minor upgrades, so any stock recovery should be fine. Try the recovery.img inside the JOP40C image straight from Google. https://developers.google.com/android/nexus/images#nakasigjop40c
Worst case if the update still won't take, flash both system and boot from the stock image too (this will unroot you but so would the OTA, and you can fix that later), and then you'll be stock enough for OTAs to work the next time it prompts.
philos64 said:
I'm not sure that you will find someone who can give you this file, cause it contains all personal data and apps.
Click to expand...
Click to collapse
The recovery partition does not contain any personal data or apps. Everything personal is in /data.

philos64 said:
I'm not sure that you will find someone who can give you this file, cause it contains all personal data and apps.
Click to expand...
Click to collapse
im pretty sure the "recovery" partition doesn't contain any of those things. i don't want a stock rom, i need stock a recovery. twrp allows you to back up certain partitions such as boot, cache, and recovery
cmstlist said:
I don't have my N7 yet, but on most Androids the stock recovery images do not vary much or at all between minor upgrades, so any stock recovery should be fine. Try the recovery.img inside the JOP40C image straight from Google. https://developers.google.com/android/nexus/images#nakasigjop40c
Worst case if the update still won't take, flash both system and boot from the stock image too (this will unroot you but so would the OTA, and you can fix that later), and then you'll be stock enough for OTAs to work the next time it prompts.
The recovery partition does not contain any personal data or apps. Everything personal is in /data.
Click to expand...
Click to collapse
i just downloaded that ill try flashing it now i downloaded the "Google Nexus 7 Toolkit" and while it didn't work for me, it did provide a JRo03d stock recovery which i flashed with fastboot and that recovery did not work. when you nexus 7 arrives i believe it would be possible to recover the stock recovery using "fastboot boot twrp-recovery", ALTHOUGH im not sure when you would execute the "backup recovery" if it would read the phones actual partition or the image you uploaded and booted on

cmstlist said:
The recovery partition does not contain any personal data or apps. Everything personal is in /data.
Click to expand...
Click to collapse
Sorry for my quick answer, I haven't seen the "recovery.img". that's file system.zip or tar which contains apps and data for restore
And if you want the Factory image, go to the thread : [Index] All for NEXUS 7 - "nakasig" - (GSM/HSPA+) , it is on, ready for download

ya i grabbed it thanks. what i don't understand is what the 34mg update is for? any ideas? i uploaded two shots, one settings page showing the build mine shipped with and the other is just the update screen i got showing size. Im about to flash the stock ROM from google now. we'll see how goes

the 34mg update was "signed-nakasig-JOP40C-from-JVP15S". i was able to flash the recovery from the stock ROM JOP40C and use that to patch through android and avoid flashing usuing TWRP

death 90 said:
im pretty sure the "recovery" partition doesn't contain any of those things. i don't want a stock rom, i need stock a recovery. twrp allows you to back up certain partitions such as boot, cache, and recovery
i just downloaded that ill try flashing it now i downloaded the "Google Nexus 7 Toolkit" and while it didn't work for me, it did provide a JRo03d stock recovery which i flashed with fastboot and that recovery did not work. when you nexus 7 arrives i believe it would be possible to recover the stock recovery using "fastboot boot twrp-recovery", ALTHOUGH im not sure when you would execute the "backup recovery" if it would read the phones actual partition or the image you uploaded and booted on
Click to expand...
Click to collapse
Honestly don't try toolkits. Just don't, because you don't know what commands or files they are really flashing, and especially because they were written for the wi-fi version. The stock recovery from the wi-fi version is not guaranteed to be compatible with the 3G version.
philos64 said:
Sorry for my quick answer, I haven't seen the "recovery.img". that's file system.zip or tar which contains apps and data for restore
And if you want the Factory image, go to the thread : [Index] All for NEXUS 7 - "nakasig" - (GSM/HSPA+) , it is on, ready for download
Click to expand...
Click to collapse
System.img is also devoid of personal information because to the standard end user it is write-protected. All the personal stuff is in the data partition.
death 90 said:
the 34mg update was "signed-nakasig-JOP40C-from-JVP15S". i was able to flash the recovery from the stock ROM JOP40C and use that to patch through android and avoid flashing usuing TWRP
Click to expand...
Click to collapse
Glad it worked out for you. I had a feeling it was just going to give you JOP40C anyway.

So, I have been trying to root my 3G tablet (JOP40C), but have no luck. I installed TWRP and unlocked just fine using the Google Nexus 7 ToolKit 3.2. When I use the toolkit to root it seems like it is doing everything fine, reboots, and I do not see any errors during the process. However, when I access Titanium backup, or Root Checker it cannot gain root access. I have tried all the options in the toolkit and nothing is working. Can anyone give me some pointers? Thanks!

spongers said:
So, I have been trying to root my 3G tablet (JOP40C), but have no luck. I installed TWRP and unlocked just fine using the Google Nexus 7 ToolKit 3.2. When I use the toolkit to root it seems like it is doing everything fine, reboots, and I do not see any errors during the process. However, when I access Titanium backup, or Root Checker it cannot gain root access. I have tried all the options in the toolkit and nothing is working. Can anyone give me some pointers? Thanks!
Click to expand...
Click to collapse
Yes - Don't use a toolkit!
Since you already have a custom recovery, put the attached file on your sdcard and install it using TWRP. Then you should be good to go.

[WIP] Building CM 10.1

Granted, it has been a while since I've built CM, and never ported it to a new device, but figure this might give some smarter people a head start or at least provide a place for others to collaborate.
I've not gotten very far past the initial vendor setup per http://wiki.cyanogenmod.org/w/Doc:_porting_intro.
A lot of the work is based off the similar ASUS TF700T, https://github.com/CyanogenMod/android_device_asus_tf700t.
I've not messed with the kernel at all at this point, https://github.com/ouya/ouya_1_1-kernel.
I've uploaded everything so far to github, https://github.com/vinny75/android_device_ouya_ouya_1_1

Packages included with official build:
OUYA Framework, Launcher, and Store
Code:
app\OUYAKeyboard.apk
app\OUYALauncher.apk
app\OUYAOOBE.apk
app\OUYAWallpaper.apk
app\ouya-framework.apk
note: some media files I haven't list
CWiid for Android: http://cvpcs.org/projects/android/cwiid4android and https://github.com/cvpcs/android_external_cwiid[.
Code:
bin\wminput
lib\libcwiid.so
etc\acc_led
etc\acc_ptr
etc\buttons
etc\gamepad
etc\ir_ptr
etc\neverball
etc\nunchuk_acc_ptr
etc\nunchuk_stick2btn
Sixpair for PS3 controllers http://www.blog.kaiserapps.com/2012/10/setting-up-sixaxis-controller-android.html.
Code:
/bin/ps3service
/bin/sixpair

I noticed that the recovery.fstab committed is from the Ouya stock recovery partition. When getting cwm to work properly with the internal sdcard, we ended up having to change the sdcard line.
I made the change and submitted a pull request.
Edit: I saw you merged the change.
Sent from my Nexus 7 using xda premium

mybook4 said:
I noticed that the recovery.fstab committed is from the Ouya stock recovery partition. When getting cwm to work properly with the internal sdcard, we ended up having to change the sdcard line.
I made the change and submitted a pull request.
Edit: I saw you merged the change.
Click to expand...
Click to collapse
Thanks, appreciate the help, hopefully, we'll have a working build soonish

If you need any help with kernel debugging/boot issues, I'll be happy to offer up the assistance of my bus pirate.
I was looking at building CM also, but there was always that step in every tut I looked at for "how to port CM to a new device" that basically said "select your device from the build tree"... well if it was in the device tree it wouldn't really be a "new" device then would it!
Also you may want to look at building 10 instead of 10.1, might have less kernel issues as its 4.1.2 jb... at least so we can get some alternative rom working then go for 10.1 after that.
Good luck!

Vinny75,
What method did you use to create the files?
"Method 1: Use mkvendor.sh to generate skeleton files"
"Method 2: Fork a similar device's git repository"
or "Method 3: create the directories and files manually"

mybook4 said:
Vinny75,
What method did you use to create the files?
"Method 1: Use mkvendor.sh to generate skeleton files"
"Method 2: Fork a similar device's git repository"
or "Method 3: create the directories and files manually"
Click to expand...
Click to collapse
I started out with Method 1 then moved over files and settings from the ASUS TF700T.

professorpoptart said:
If you need any help with kernel debugging/boot issues, I'll be happy to offer up the assistance of my bus pirate.
I was looking at building CM also, but there was always that step in every tut I looked at for "how to port CM to a new device" that basically said "select your device from the build tree"... well if it was in the device tree it wouldn't really be a "new" device then would it!
Also you may want to look at building 10 instead of 10.1, might have less kernel issues as its 4.1.2 jb... at least so we can get some alternative rom working then go for 10.1 after that.
Good luck!
Click to expand...
Click to collapse
Yes, building the new device tree has been... uhm... educational... and I am still learning. If I don't make any headway on 10.1, I might drop back to 10 - at least most of the legwork will be done.

Ok, so I'm in the middle of a build
Have a vendor tree on my git and I forked Vinny75's device tree, modified it some
Also a kernel tree up there, which is required for my device tree (prefer to build the kernel myself =) I've booted a custom-built kernel on it already, so that shouldn't be an issue)
I'm nervous to flash this though. I did a bit of searching but couldn't come up with a way to get back into recovery should this thing not boot. You guys know of anything?

Other than using adb to reboot to recovery, http://forums.ouya.tv/discussion/1380/recovery-mode is all I've seen so far to force into recovery mode.
Sent from my Nexus 7 using xda premium

mybook4 said:
Other than using adb to reboot to recovery, http://forums.ouya.tv/discussion/1380/recovery-mode is all I've seen so far to force into recovery mode.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Yea, that's what I'm seeing.
So here's my 'solution'
Since we have fastboot, we can boot a boot.img without having to worry about flashing it.
I've successfully booted my cm boot.img, with ro.secure=0 and ro.adb.secure=0, I can adb reboot it when it fails miserably to boot
Quick and dirty script to unsecure a boot.img:
http://pastie.org/8033076
It assume that unpackbootimg and mkbootimg are in your path, you can get them here: http://invisiblek.org/mkbootfs_tools.zip
Getting closer...

THere's a keyboard solution in the Ouya Questions forum in the thread, [Q] Is My Ouya Dead?

dibblebill said:
THere's a keyboard solution in the Ouya Questions forum in the thread, [Q] Is My Ouya Dead?
Click to expand...
Click to collapse
Yeah, I think that is the same solution posted earlier:
mybook4 said:
Other than using adb to reboot to recovery, http://forums.ouya.tv/discussion/1380/recovery-mode is all I've seen so far to force into recovery mode.
Click to expand...
Click to collapse
THis might be another option too:
tylerwhall said:
I started looking into bootloader-level recovery tonight before messing with the file system too much and potentially getting into a bad state. I couldn't find this information anywhere else.
Bootloader strap
On the back of the board in the center, there is an unpopulated button (U33). When jumped while the power button is pressed, this appears to put the bootloader into USB recovery mode. It enumerates with an nvidia vendor id. Presumably nvflash or tegrarcm could be used to unbrick the device.
I haven't done anything with the bootloader recovery since I haven't yet made a backup. I'm not sure how much of the functionality is allowed given the state of the production fuse, but I would think we could use this to at least get back to a stock state.
Click to expand...
Click to collapse

Some NVidia devices lock access out at the nvflash level unless you've got the manufacturer's key. I believe you get locked out with a 0x4 (nvflash's way of saying "go away").
Using fastboot is probably the quickest, easiest, and safest way to test new kernels.
Sent from my SCH-I535 using xda premium

mybook4 said:
Some NVidia devices lock access out at the nvflash level unless you've got the manufacturer's key. I believe you get locked out with a 0x4 (nvflash's way of saying "go away").
Using fastboot is probably the quickest, easiest, and safest way to test new kernels.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
ah he makes it sound like it puts you in USB recovery mode fo you could ADB in to push an update.

Just wanted to say I'm totally stoked on this guys! Can't wait to see what you do with this. Wish I could help, but I'm really not a developer.

i agree with rebel! but when you guys have it readyish ill test flash it and tell you what happens!!

So, OUYA isn't really as interested in being an open console as they suggest.
I'm keeping a track of how many requests we get relating custom firmware, and from what I'm seeing the user base is not as interested in custom firmware as you might think, which is echoed by this thread (we've shipped 60,000+ units, and less than 10 people have commented in the last month in this thread about getting access to recovery mode).
That doesn't mean that we're shooting the idea down, you need to keep in mind that in terms of priorities this is way down the list as you'd expect from any feature where it's being requested by less than one tenth of one percent of the user-base.
I'm sure @Wajeemba is familiar with CM requests that a very small minority of the user-base are very passionate about, so hopefully you can understand why we're not rushing to work on this.
Click to expand...
Click to collapse
Go to this thread and let them know we want support:
http://forums.ouya.tv/discussion/1380/recovery-mode

That's not even slightly surprising. If every user demanded CM10 they still wouldn't comply, because then they'd lose their one means of profit (ouya store), the fact that "nobody is asking for it" is their excuse, and they'll think of another one if that ever changes.
This is why we just need to proceed without them. I'm on week two of who knows how many weeks away from home on work, so my efforts at porting CM have been put on hold. Have you been able to make any progress? I'd totally loan my Ouya to Fattire or Dalingrin, or another whiz porter if they'd be willing to work on it...

sonofskywalker3 said:
That's not even slightly surprising. If every user demanded CM10 they still wouldn't comply, because then they'd lose their one means of profit (ouya store), the fact that "nobody is asking for it" is their excuse, and they'll think of another one if that ever changes.
This is why we just need to proceed without them. I'm on week two of who knows how many weeks away from home on work, so my efforts at porting CM have been put on hold. Have you been able to make any progress? I'd totally loan my Ouya to Fattire or Dalingrin, or another whiz porter if they'd be willing to work on it...
Click to expand...
Click to collapse
I'd check with invisiblek about how to avoid bricking the OUYA. Apparently his is bricked. It's stuck in nvflash mode. I think it was a kernel written with a bad init.rc that did it. not sure though.
Sent from my Nexus 7 using xda premium

[L5] **** Guide for running CM10.1/CM10.2/CM11 on the Canadian E617G ****

The LG L5 E617G variant can certainly be rooted, have an unlocked bootloader, as well as run CyanogenMod. The Bell variant can use a custom kernel.
Firstly:
- Root the device using the guide in this thread.
- Verify that you have a SuperUser app installed, and you're able to achieve root status. The best way to check is by downloading SuperSU, and updating the binaries.
Secondly:
- Unlock the bootloader by downloading emmc_appsboot_617_truncated.zip in this thread. (Thanks Skellums!)
- Turn on USB Debugging in Developer Options, (if you can't see Developer Options in the settings menu, continuously tap on Build Number in About in Settings).
- When you plug in your device, if you have an SDCard, you should see two storage spaces within the LG L5 MTP. Place the bootloader file in root of the phone storage (which the devices sees as the SDCard). The actual SDCard is the external SDCard which ADB has trouble seeing on occasion.
- Plug in your device to the PC, and make sure its loaded into Android.
- Download the fastboot/adb files here, and extract them to C:/fastboot/. Open the command prompt in windows, and type:
Code:
cd C:/fastboot
then...
Code:
adb devices
...and make sure you see your device, then...
Code:
adb shell
su
dd if=/dev/block/mmcblk0p5 of=/sdcard/emmc_appsboot-backup.bin
dd if=/sdcard/emmc_appsboot_617_truncated.bin of=/dev/block/mmcblk0p5
reboot
- Now, you should have an unlocked bootloader. If you get any "file not found errors", you placed the emmc file in the wrong directory
Thirdly:
- You now need a recovery, so let your phone reboot, and when its back to the main screen, make sure the device is plugged in, open the command prompt, and follow the instructions here.
Fourthly:
- Any CyanogenMod works very nicely on the L5 E617G. You can get CM10.1 along with gapps here or CM10.2 here or the amazing CM11 here. Before heading back to recovery, you will need the CM10.1 ROM, GAPPS, v20 BaseBand, and WakeWithHomeAndPower_signed.zip (Optional) and v10 Baseband (For restore purposes if something goes wrong).
- Copy all those zips to the root of your external SD, and then run the command:
Code:
adb reboot recovery
- Before anything, create a NANDROID BACKUP! Make sure to backup to the external SD, as you probably would have more space to work with.
- Then, factory reset your device in recovery. You can now flash CM10.1, by choosing "install zip from external sd card". Flash the v20 baseband, then the ROM, then gapps, then the wake with home fix.
Done!
- Upon reboot, you should have CM working very well on your LG L5 E617G!
Note: You can also get to recovery with the L5 but holding down Vol Down and Home, while pressing the power button for 2 seconds.
Disclaimer: I wrote this article because I, myself, had quite the experience in getting CM10.1 running on this L5 variant, and I wanted to show that it's certainly possible, thanks to the hard work by all the devs here! Good luck!

Thank you, good sir! I have now installed CM10.1!
I ended up running the recovery twice - after the first time, during the reboot, it just hung at the LG logo so I turned it off and back on and then repeated the recovery install steps and it was fine after the second time (now that I think about it I should've just tried issuing the "adb reboot recovery" command again instead).
Phone definitely much snappier and I haven't had any problems so far! Thank you again!

It's been a couple of days now and all seems to be running smoothly!
The only issue I have with CM on my L5 is that the video seems to cause issues - it'll work the first time but then hangs afterwards and subsequent attempts just give an error. Rebooting is the only cure. Not a huge deal for me though.
The rest of the phone runs great, definitely smoother and snappier than stock.

Now my camera/video recording is working just fine today. Go figure.
Loving the speed vs the stock stuff!

koimr said:
Now my camera/video recording is working just fine today. Go figure.
Loving the speed vs the stock stuff!
Click to expand...
Click to collapse
I've noticed the same thing. Once and a while, the video camera will freeze, and then force close. Reopening it causes "Gallery has stopped.". It's really finicky, but a reboot usually does the trick. Not sure if it's a ROM issue or a E617G issue, but you're not alone!
Pictures seem fine, I would suggest staying away from the video recording for now.

BuffMcBigHuge said:
I've noticed the same thing. Once and a while, the video camera will freeze, and then force close. Reopening it causes "Gallery has stopped.". It's really finicky, but a reboot usually does the trick. Not sure if it's a ROM issue or a E617G issue, but you're not alone!
Pictures seem fine, I would suggest staying away from the video recording for now.
Click to expand...
Click to collapse
I seem to recall having these issues a long time ago with the stock ROM too, now that I think about it. Not a big deal for me, easier to just avoid using the video camera.
I've even gone and flashed the latest (as of today) beta 5 of CM 10.1 as well - works just great as well!

koimr said:
I seem to recall having these issues a long time ago with the stock ROM too, now that I think about it. Not a big deal for me, easier to just avoid using the video camera.
I've even gone and flashed the latest (as of today) beta 5 of CM 10.1 as well - works just great as well!
Click to expand...
Click to collapse
Great! I'm going to try the kernel that was also posted and attempt to overclock.
Sent from my HTC One using Tapatalk 4

BuffMcBigHuge said:
Great! I'm going to try the kernel that was also posted and attempt to overclock.
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
Oh wow! Post your results if it all works out!

koimr said:
Oh wow! Post your results if it all works out!
Click to expand...
Click to collapse
I have successfully flashed lge-e610-v3.4.0-13-08-2013_20-59.zip and overclocked the device to 1000Mhz!

BuffMcBigHuge said:
I have successfully flashed lge-e610-v3.4.0-13-08-2013_20-59.zip and overclocked the device to 1000Mhz!
Click to expand...
Click to collapse
Same here now! Whoohoo!!

Thank you, good sir! I have now installed CM10.1

I've installed beta 6 and now the video is working just fine (no hangs!).
I did find that I wasn't able to boot into recovery - I had to reflash recovery from ROM Manager.
I then tried to flash the custom OC kernel and that resulted in a blank screen, so back into recovery and reflash beta 6 again.
So I've lost the overclock but meh, I'm ok with waiting for an updated kernel.

New kernel was posted, I've flashed and it works - OC is back! :good:

fastboot adb files
Hey is it possible to re up the fastboot adb files i get a "file not found" ....or is it just the general adb install for android, if so i already have it from when i did my atrix. but if i need certain files then it would be great if someone could tell me, thx bunches

spuzzum said:
Hey is it possible to re up the fastboot adb files i get a "file not found" ....or is it just the general adb install for android, if so i already have it from when i did my atrix. but if i need certain files then it would be great if someone could tell me, thx bunches
Click to expand...
Click to collapse
A quick Google search usually gets what you need.
http://d-h.st/5Xy

Thx , searched the forums to see if there were special files or if it was just adb.I found nothing concrete and I already had adb installed so I just ran it and it worked so I know now.
sorry about getting back late to edit the post.

Does this Unlock Network?
My phone is LG E617G It's Canadian phone which locked to Bell Mobility.
Does this ROM work on that model? and does it unlock the network(sim)?

altltkrk said:
My phone is LG E617G It's Canadian phone which locked to Bell Mobility.
Does this ROM work on that model? and does it unlock the network(sim)?
Click to expand...
Click to collapse
It does not unlock the SIM, however, you can get your SIM unlocked by using a service such as this: http://dollarunlock.com/lg-e617g-optimus-l5-unlock-code.html

Good
Inviato dal mio LG-E610 con Tapatalk 2

Thank you, for this how to.
I've been searching everywhere for this info.
--------------------------------------------------------------------
I've installed CM and it seem to be working well, but there's a problem with the gapps install.
com.google.process.location
recherche google
picasa uplauder
google play store
All keep crashing on launch and do not work at all. SO I can't do any search on the phone and google play store isn't working at all.
Is this a know problem or did I do something wrong with the install?
Is there a way to fix this? I've tried to redoanload de gapps and do a factory restor but for now no changes.