Database Users

Is a flashable zip kernel possible in play ?

Hi everyone I am new to the xperia play community. .
I was flashing ics on my friend's Samsung galaxy s I9000 and saw that the new kernels were in flashable zip format..
Is it possible for xperia play? because then there would be no need to connect xplay to computer..
Sent from my R800i using XDA App

jaickyt said:
Hi everyone I am new to the xperia play community. .
I was flashing ics on my friend's Samsung galaxy s I9000 and saw that the new kernels were in flashable zip format..
Is it possible for xperia play? because then there would be no need to connect xplay to computer..
Sent from my R800i using XDA App
Click to expand...
Click to collapse
Flashable kernels are not possible on this phone because recovery isn't on a separate partition.
Sent from my R800x using XDA

Ok thanks for quick reply ..
so no possibilities in future kernels a well..
Sent from my R800i using XDA App

How do kernels get flashed when using an ftf?
Sent from my R800i using XDA

I always wondered how other phones that hav locked bootloaders, how u can flash the whole rom and kernel together, but on the play u cant, i just assumed that the kernel and the system parts must be different
Sent from my R800i using xda premium

MilkyJoePD said:
How do kernels get flashed when using an ftf?
Sent from my R800i using XDA
Click to expand...
Click to collapse
To quote myself, how?
Sent from my R800i using XDA

MilkyJoePD said:
To quote myself, how?
Sent from my R800i using XDA
Click to expand...
Click to collapse
Kernel is part of the boot partition. When you flash your phone to stock using an .ftf, it flashes boot, system, and userdata.
Sent from my R800x using XDA

lightningdude said:
Kernel is part of the boot partition. When you flash your phone to stock using an .ftf, it flashes boot, system, and userdata.
Sent from my R800x using XDA
Click to expand...
Click to collapse
So it's possible to flash a kernel? Why only with an ftf file?
I know it's not fastbooting because I can't install the drivers for fastboot again for some reason.
Sent from my R800i using XDA

MilkyJoePD said:
So it's possible to flash a kernel? Why only with an ftf file?
I know it's not fastbooting because I can't install the drivers for fastboot again for some reason.
Sent from my R800i using XDA
Click to expand...
Click to collapse
You can flash a kernel in fastboot by using a boot.img file, but for those with locked bootloaders, only an .ftf can write to boot.
Sent from my R800x using XDA

So it's possible to flash a Kernel?
Sent from my R800i using XDA

MilkyJoePD said:
So it's possible to flash a Kernel?
Sent from my R800i using XDA
Click to expand...
Click to collapse
Yes, through fastboot with an unlocked bootloader.

When you flash an ftf for stock, the software is signed digitally by Sony. If you flash an unsigned kernel when your bootloader is still locked, you'll get a boot loop.
Flash mode, which is what flashtool uses, is meant for applying official updates, so it's really only meant for signed, official software.
Fastboot on the other hand is for developers.
You could try making an ftf with a custom kernel, but it's basically pointless when fastboot is so easy and it won't boot unless you're unlocked anyway.

Exactly..once you have unlocked bootloader,then its just a matter of seconds to change kernel..
I change and try new kernels and roms every second day.
Sent from my Xperia Play using XDA App

lightningdude said:
Flashable kernels are not possible on this phone because recovery isn't on a separate partition.
Sent from my R800x using XDA
Click to expand...
Click to collapse
but i suppose... if we boot the complete kernel with recovery and copy it to the ram memory, we could flash flash the partition where recovery is insatelled...am i wrong??

I can't get into fastboot mode anymore so flashing a kernel in flash mode would be useful. Ftf files flash them in flash mode.
Sent from my R800i using XDA

MilkyJoePD said:
I can't get into fastboot mode anymore so flashing a kernel in flash mode would be useful. Ftf files flash them in flash mode.
Sent from my R800i using XDA
Click to expand...
Click to collapse
If you can't use fastboot I'd recommend checking in the service menu, and making sure the bootloader is still unlocked. If it's not you're just gonna end up with a boot loop.

bamsbamx said:
but i suppose... if we boot the complete kernel with recovery and copy it to the ram memory, we could flash flash the partition where recovery is insatelled...am i wrong??
Click to expand...
Click to collapse
That sounds plausible to me. Just like you can run some Linux distributions live off a USB drive and then remove (or format the USB drive) - only certain ones like Puppy linux can do this though, they have to run from RAM like you're saying. Another option might be to copy the recovery (or necessary files) to the cache partition (if there is enough room) so that the recovery isn't dependent upon that partition so it can be wiped/reflashed. I'm not familiar enough with this level of Android development to know how hard this might be though - but I think it should be possible.
But it would be dangerous... if something goes wrong and your device fails in the middle of the process, the partition may be hosed, in which case you might not be able to boot at all (not into recovery or normally). You'd be hosed until you get to a computer to flash a firmware or kernel, making flashing away from a computer dangerous anyway.
So it's probably more error-prone and more hassle to implement for such small reward (it just takes one extra step with a computer to flash a kernel).
~Troop

captain67 said:
If you can't use fastboot I'd recommend checking in the service menu, and making sure the bootloader is still unlocked. If it's not you're just gonna end up with a boot loop.
Click to expand...
Click to collapse
It's definitely a PC problem.
Sent from my R800i using XDA

Trooper_Max said:
That sounds plausible to me. Just like you can run some Linux distributions live off a USB drive and then remove (or format the USB drive) - only certain ones like Puppy linux can do this though, they have to run from RAM like you're saying. Another option might be to copy the recovery (or necessary files) to the cache partition (if there is enough room) so that the recovery isn't dependent upon that partition so it can be wiped/reflashed. I'm not familiar enough with this level of Android development to know how hard this might be though - but I think it should be possible.
But it would be dangerous... if something goes wrong and your device fails in the middle of the process, the partition may be hosed, in which case you might not be able to boot at all (not into recovery or normally). You'd be hosed until you get to a computer to flash a firmware or kernel, making flashing away from a computer dangerous anyway.
So it's probably more error-prone and more hassle to implement for such small reward (it just takes one extra step with a computer to flash a kernel).
~Troop
Click to expand...
Click to collapse
Well, but its something... if something gone wrong,
We always are able to reflash an ftf file and restore nandroid backup... i will create a new thread in the developement forum tomorrow , and lets see if developers can make this posible

bamsbamx said:
Well, but its something... if something gone wrong,
We always are able to reflash an ftf file and restore nandroid backup... i will create a new thread in the developement forum tomorrow , and lets see if developers can make this posible
Click to expand...
Click to collapse
You can't restore a nandroid with a phone that won't boot into recovery though. If something went wrong with flashing the kernel, you would be stuck until you get home before you can fix it.

[RECOVERY][4/27/2012] CWM thor 1.7c for A510

Here's an updated version from my earlier patch of thor's 1.7 recovery for the A510. This one has the proper mapping for the data partition (mmcblk0p10). I set the version number as 1.7b.
To recap:
Thor's 1.7 cwm recovery repacked with A510 stock kernel. itsmagic is disabled. overclocking does not work, since it's a stock kernel.
This is exactly the same as the one I repacked for the A200, but with the A510 stock recovery kernel and edited the kernel string to show when it boots. And also changed the fstab for /data to use mmcblk0p10.
You MUST unlock your bootloader before flashing this.
You can rename it to recovery.img and put it on your microsd card and use Acer Recovery Installer to flash it. Or you can use the following command in a terminal emulator or adb shell.
Code:
dd if=thor_recovery17b_A510.img of=/dev/block/mmcblk0p1
Give it a try and see if it works.
***Link Removed***
Cheers!
WARNING: If you downloaded the link I posted earlier that has MD5 of 1ded94b4b4f0522ca14b7070146d9a49, DO NOT USE IT! Download 1.7b above instead.
Edit: Updated to 1.7c to fix some mounting issues.

You MUST unlock your bootloader before flashing this.
please tell me how unlock A510.
thank you

Updated OP with new image to fix some reported mounting issues. Please give this a try. Also remember, that I do not have this device, so I rely on you guys to let me know what doesn't work. So far, the only feedback i've gotten is from NoThrills (Thanks buddy).

Euclid's Brother said:
Here's an updated version from my earlier patch of thor's 1.7 recovery for the A510. This one has the proper mapping for the data partition (mmcblk0p10). I set the version number as 1.7b.
Click to expand...
Click to collapse
This is awesome! Thank you. Will install now.
Dave Burbank

asdf20003 said:
You MUST unlock your bootloader before flashing this.
please tell me how unlock A510.
thank you
Click to expand...
Click to collapse
You must have the ability to send adb commands to the tablet.
adb reboot-bootloader
fastboot oem unlock
Then follow the on screen instuctions very quickly.
Sent from my SPH-D710 using Tapatalk 2

Euclid's Brother said:
Updated OP with new image to fix some reported mounting issues. Please give this a try. Also remember, that I do not have this device, so I rely on you guys to let me know what doesn't work. So far, the only feedback i've gotten is from NoThrills (Thanks buddy).
Click to expand...
Click to collapse
LOL... And there I was fixing it myself this afternoon I think we both noticed that 1 line that was missing in the fstab

After changing tab to use the named devices like the stock recovery, it seemed like it was having even more trouble, so I reverted back to the original fstab and just changed data to mmcblk0p10.
Is it working okay now?

is only for A510 ? if i try for A501 is can be?

euclid, what has changed with the new recovery kernel, i can't get twrp to boot.i sent a gtalk request.

D3v17 said:
is only for A510 ? if i try for A501 is can be?
Click to expand...
Click to collapse
strictly for the A510. It will not work on anything else! The data partition is in a different place.

ibsk8 said:
euclid, what has changed with the new recovery kernel, i can't get twrp to boot.i sent a gtalk request.
Click to expand...
Click to collapse
Who knows. try repacking it with the stock recovery kernel. You'll also need to update the partition device for Data in recovery.fstab

Euclid's Brother said:
You must have the ability to send adb commands to the tablet.
adb reboot-bootloader
fastboot oem unlock
Then follow the on screen instuctions very quickly.
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
Brother,
Is the above applicable to A500 OTA ICS 4.0.3 bootloader?
Sent from my A500 using Tapatalk 2

wcrov said:
Brother,
Is the above applicable to A500 OTA ICS 4.0.3 bootloader?
Sent from my A500 using Tapatalk 2
Click to expand...
Click to collapse
NO
He stated already. JUST for the A510 which is the new Tegra 3 tablet. Replacement for the old 500 series

recovery successfully installed.
and now? what is the next step ;-)
how to help people from there to go further in rom cooking and all that stuff ?
anyway, thanks a lot euclid's brother,

I thought this version of thors recovery was not GPL compliant. If it is not be careful, the angry hordes will decend on this thread and you will get banned. Even mentioning of the name of thor is enough to cause you grief.....oh wait, its recovery, not his rom, so those who have a bone to pick turn a blind eye...carry on.

If this is based on the work of a banned developer then I'm afraid we do not wish for it to be posted here.
I'd suggest taking an alternative recovery to amend.

[Q] Booting into recovery shows "no command"

Hi there,
yesterday succesfully rooted my device using the insecure boot image.
Today booted and also flashed the new CWM recovery image but now, when booting into recovery only get an android logo and the text "no command" ?
Any ideas ? Flashed back to original recovery image but no change either ?
Root remains though and working fine.
Thanks

CMW can't be flashed yet... read the official CMW thread in the N4 Original Development forum for help
Sent from my Nexus 7 using xda app-developers app

n7of9 said:
CMW can't be flashed yet... read the official CMW thread in the N4 Original Development forum for help
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Not true read here again :
UPDATE: There is an official ClockworkMod recovery for Nexus 4 now available directly by Koush, so this should all be easy as pie now and you can now safely install CWM too. I am updating the CWM method with the updated instructions.
Click to expand...
Click to collapse

has anyone reported it working?
Sent from my Nexus 7 using xda app-developers app

It seems tonight clockwork will release a new version with bugfixes which should make recovery working when flashed also.
Sent from my Nexus 4 using xda app-developers app

New clockworkmod recovery 6.0.1.8 had been released and I can confirm myself that it is working perfectly and stays when flashed !
You can download it here and follow the instructions as written here.
Good luck !

excellent, i was waiting for someone to confirm before flashing it myself
(looks like this thread is just a party for the two of us, wooohooo, let's find the hidden alcohol)

n7of9 said:
excellent, i was waiting for someone to confirm before flashing it myself
(looks like this thread is just a party for the two of us, wooohooo, let's find the hidden alcohol)
Click to expand...
Click to collapse
Meanwhile a newer 6.0.1.9 is released as well, which will hopefully also fix the backup being in the wrong location and not usable

CWM is fixed. Read this thread: http://forum.xda-developers.com/showthread.php?t=1995440

6.0.1.9 is the one i flashed and I'm still looking for my backup :s
n7'd from my n7

Disregard this post! It was meant for LBE which is a Virus or acts like one (Newest version that was translated)

I'm having the "no command" message as well. I've flashed CWM 6.0.2.3 no-touch (following this guide), and it doesn't seem to be sticking. It'll work the first time, but then revert to the "no command" screen. I've also tried flashing the stock recovery, and then I receive the same message. I have an unlocked bootloader, and I managed root via the same guide. Anybody have any ideas?

k3nav7 said:
I'm having the "no command" message as well. I've flashed CWM 6.0.2.3 no-touch (following this guide), and it doesn't seem to be sticking. It'll work the first time, but then revert to the "no command" screen. I've also tried flashing the stock recovery, and then I receive the same message. I have an unlocked bootloader, and I managed root via the same guide. Anybody have any ideas?
Click to expand...
Click to collapse
From efrants android 101 sticky:
I just flashed CWM, but every time I try to boot into CWM, I keep seeing the stock recovery. Why?
If you updated your Android build using an OTA update file (either manually or over-the-air), the update placed two files on your device that re-flash the stock recovery every time you reboot your device. These two files are:
/system/etc/install-recovery.sh <== this is the script that installs the patch file
/system/recovery-from-boot.p <== this is the patch
You have to rename (or delete) one or both of them, then re-flash your custom recovery. Now it will stick.
Sent from my Nexus 7 using Tapatalk HD

El Daddy said:
From efrants android 101 sticky:
I just flashed CWM, but every time I try to boot into CWM, I keep seeing the stock recovery. Why?
If you updated your Android build using an OTA update file (either manually or over-the-air), the update placed two files on your device that re-flash the stock recovery every time you reboot your device. These two files are:
/system/etc/install-recovery.sh <== this is the script that installs the patch file
/system/recovery-from-boot.p <== this is the patch
You have to rename (or delete) one or both of them, then re-flash your custom recovery. Now it will stick.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Perfect! Thank you! I had just previously downloaded 4.2.1, and so renaming recovery-from-boot.p did the trick. I had to remount my /system as read/write (used Total Commander, and it worked like a charm.

k3nav7 said:
Perfect! Thank you! I had just previously downloaded 4.2.1, and so renaming recovery-from-boot.p did the trick. I had to remount my /system as read/write (used Total Commander, and it worked like a charm.
Click to expand...
Click to collapse
No problem! Glad to help!
Sent from my Nexus 7 using Tapatalk HD

No Command recovery problem
Hello im using a Canvas Magnus A117 its an amazing phone i rooted it but wanted to install chainfire 3D on it but it didnt work and now my phone is bricked. I tried flashing a custom rom but in recovery when i click on apply update from sdcard it says No command. with a dead android and a red triangle with !. So i cant use any feature in the Recovery mode and my phone is bricked. What do i do?

[Q] Nexus 4 Bricked?

Hi all,
I'm freaking out here. I was trying to install a kernel on my N4 using the Toolkit and somehow it said it was done successfully but then my phone got stuck on the Google screen and was never able to start up again.
I do have a Nandroid back up but unfortunately it's on my computer and not on my phone.
I tried using the toolkit AND adb to push the files to my phone but I get the same message: "failed to copy to sdcard: No such file or directory".
I'm completely stuck now and am panicking. Somebody please help!

And this is why we don't use toolkits.
Read up on how to use fastboot and how to boot into fastboot.
Then read up on where to find stock images and how to flash them in fastboot. Then do it.
Sent from my Nexus 4 using Tapatalk 2

Why would you use a toolkit to flash a kernel ...just download zip go to recovery cwm or twrp and flash...
Can you get into fast boot ??
Sent from my Nexus 4 using xda app-developers app

Might also be helpful if you specified which kernel you flashed. As long as you didn't flash a kernel for a different device (e.g. nexus 7) you can definitely recover. To reiterate what others have mentioned, fastboot is your friend. There are numerous tutorials on his to install and use it. Check the stickies.

Crisisx1 said:
Why would you use a toolkit to flash a kernel ...just download zip go to recovery cwm or twrp and flash...
Can you get into fast boot ??
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Yeah I can get into fast boot and even into CWM. I tried factory resetting in CWM but it still gets stuck on the Google screen.
The reason I used the toolkit and not CWM to flash the kernel is because CWM kept failing to flash the kernel, giving me some error and "(bad)" message. It is the kernel to improve Nexus 4 sensitivity directly from another thread.
Can someone please provide me with specific links or detailed instructions?

Crisisx1 said:
Why would you use a toolkit to flash a kernel ...just download zip go to recovery cwm or twrp and flash...
Can you get into fast boot ??
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
My main problem is I need to get my Nandroid backup onto my phone. For some reason, because it's stuck on the Google screen, it's not able to write to the sdcard. Can someone please help me get my files from my computer to my phone?

Flash stock first.
Follow Efrants guides.
http://forum.xda-developers.com/showthread.php?p=34552123
Sent from my Nexus 4 using xda premium

Unjustable said:
Flash stock first.
Follow Efrants guides.
http://forum.xda-developers.com/showthread.php?p=34552123
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Thanks for your help. I've successfully follows the instructions and got back to Android 4.2.2.
I still want to restore my previous Nandroid though. Although I have placed it in the Clockworkmod backup folder, it's not being seen by CWM recovery. I tried backing up a new nandroid just to test and CWM sees the one it backs up.
Anyone know how I can get CWM to recognize the Nandroid which was done through the toolkit?
Thanks!

darkwolf1789 said:
Yeah I can get into fast boot and even into CWM. I tried factory resetting in CWM but it still gets stuck on the Google screen.
The reason I used the toolkit and not CWM to flash the kernel is because CWM kept failing to flash the kernel, giving me some error and "(bad)" message. It is the kernel to improve Nexus 4 sensitivity directly from another thread.
Can someone please provide me with specific links or detailed instructions?
Click to expand...
Click to collapse
If the kernel wasn't installing in the first place you probably shouldn't of flashed it via toolkit
Sent from my Nexus 4 using xda app-developers app

Crisisx1 said:
If the kernel wasn't installing in the first place you probably shouldn't of flashed it via toolkit
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Yeah I realize that now. But any idea how to get CWM to recognize my Nandroid that I did with the toolkit? Anyone?

joshnichols189 said:
And this is why we don't use toolkits.
Read up on how to use fastboot and how to boot into fastboot.
Then read up on where to find stock images and how to flash them in fastboot. Then do it.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
There isn't really anything wrong with a toolkit for certain things, I just think it's a bit strange he tried to use it for something as trivial as this.

skezza said:
There isn't really anything wrong with a toolkit for certain things, I just think it's a bit strange he tried to use it for something as trivial as this.
Click to expand...
Click to collapse
Ok well to solve the problem I did download the stock images and flash them according to Effrants guide:
http://forum.xda-developers.com/show...php?p=34552123
Then the reason that CWM wasn't recognizing my Nandroids was because I had them in /sdcard/clockworkmod/backups, but they should be in /data/media/clockworkmod/backup.
I recovered everything and I'm back! Thanks for your help everyone.

no boot in to rom, only recovery???

hi,
i am on D802 stock rom rooted and TWRP/CWM installed and last night i had some kind stock update, and now phone don't boot in to rom, all the time boot in to recovery no matter wich type of reebot i use,
i also can install new rom via recowery but does not boot in to rom??
i also can NOT enter download mode...
please help
:crying:

Look around in the here for the commands, but what you will have to do is format the fota and misc partitions using adb shell and the dd cmd. Then phone will boot allowing you to install a working recovery, rom and your off and running
Sent from my VS980 4G using Tapatalk

thanks i am in to it but i am looking for laf.img D802 32gb
thanks for your help!!
P

hi!
can you please help me with dd command for formating fota and misc, i still have data on internal sdcard and i dont want to lose it,
thanks!
Peter
wyrdtrtle said:
Look around in the here for the commands, but what you will have to do is format the fota and misc partitions using adb shell and the dd cmd. Then phone will boot allowing you to install a working recovery, rom and your off and running
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse

Use Terminal in TWRP:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
-Matt

http://forum.xda-developers.com/showthread.php?p=49353878
[FIX] Installed TWRP and now you're stuck after OTA?
This thread has the instructions and the second did cmd if the first one alone doesn't do it. Good luck
Sent from my Nexus 7 2013 using XDA Premium 4 mobile app

I got it thanks to all!!
this helps 100%
you rock!
wyrdtrtle said:
http://forum.xda-developers.com/showthread.php?p=49353878
[FIX] Installed TWRP and now you're stuck after OTA?
This thread has the instructions and the second did cmd if the first one alone doesn't do it. Good luck
Sent from my Nexus 7 2013 using XDA Premium 4 mobile app
Click to expand...
Click to collapse

Glad i could help
Sent from my VS980 4G using Tapatalk

Connect to PC. If ur a Samsung user, download a stock firmware. download Odin.
Next click PDA on Odin and choose the downloaded firmware . extension will be ".tar.md5" . this will take 10 mins. After that your device will be factory reset like a new ones. But its worth it.
Sent from my Nexus 4 using XDA Premium HD app