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.
Related
I'm a tad lost on how to flash a custom ROM/recovery. The only other phone I've done this on is an Aria, which was quite a bit easier, as it's bootloader wasn't signed and such.
I'm trying to put CherryBlur on it, which I guess needs it to be unlocked with a specific recovery image.
This is the thread I found about unlocking
http://forum.xda-developers.com/showthread.php?t=1136261
but there's a few terms I'm unfamiliar with, such as sbf, and I can't really find a guide on what to do.
I'm hoping someone wouldn't mind walking me through unlocking and flashing a ROM to my phone. It's already rooted and it's fully updated.
Thanks.
I came from an aria also, anyways do you already have the bootloader unlocked?
Sent from my MB860 using XDA App
No, that's something that's also throwing me off that I could use some help with. For the Aria, it was all pretty much automated, just had to download a tool, click a button or two and bam.
This seems more in depth, and I'm confused.
EDIT: I did just find this, right above this thread.
http://forum.xda-developers.com/showthread.php?t=1182871
I can follow that. After unlocking the bootloader, what do?
If you want to that you can not sbf back, just letting you know, after you have unlocked the bootloader, you have to flash a clockwork mod recovery, you can use tefaners (the one I use) or you can you the rom manager one (which has some bugs such as not wiping and no sd-ext)
Sent from my MB860 using XDA App
What does it mean that I can't "sbf back"? What is sbf?
Sent from my MB860 using XDA App
Sbf is like the stock rom for the atrix, you flash it through rsd lite on your computer
Sent from my MB860 using XDA App
I gotcha. So once the BL is unlocked, how do I flash the recovery image to it?
WTFsandwich said:
I gotcha. So once the BL is unlocked, how do I flash the recovery image to it?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1179506 may or may not help
WTFsandwich said:
I gotcha. So once the BL is unlocked, how do I flash the recovery image to it?
Click to expand...
Click to collapse
just download Rom Manager from the play store. and then open it and there it will have an option saying flash clockworkmod recovery.
was your BL unlocked to start with, or did you have to use adb or another method?
yahyasaleh said:
just download Rom Manager from the play store. and then open it and there it will have an option saying flash clockworkmod recovery.
was your BL unlocked to start with, or did you have to use adb or another method?
Click to expand...
Click to collapse
this thread is 9 months old...
Hey I have an unlocked boot loader, stock 4.2.1 ROM but running ktoonz kernel. In order to get the next update will I have to re flash the stock kernel, recovery, and re-lock my bootloader? I'm really only familiar with Samsung galaxy devices where you can just ODIN everything
Sent from my SGH-T999 using xda premium
Jms122589 said:
Hey I have an unlocked boot loader, stock 4.2.1 ROM but running ktoonz kernel. In order to get the next update will I have to re flash the stock kernel, recovery, and re-lock my bootloader? I'm really only familiar with Samsung galaxy devices where you can just ODIN everything
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
You will need the stock kernel and your /system partition must be completely unmodified. Bootloader state and recovery don't matter. After accepting an update you will lose your custom recovery and root, so you will have to reflash but that's no big deal.
Sent from my Nexus 7 using Tapatalk HD
Awesome thanks a lot, is there a link for a flashable stock kernel? I don't ry feel like restoring from my old recovery
Sent from my SGH-T999 using xda premium
Jms122589 said:
Awesome thanks a lot, is there a link for a flashable stock kernel? I don't ry feel like restoring from my old recovery
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Download the latest factory images at http:// developers.google.com/android/nexus/images. Open the package, and flash boot.img.
Sent from my Galaxy Nexus using Tapatalk 2
oldblue910 said:
Download the latest factory images at http:// developers.google.com/android/nexus/images. Open the package, and flash boot.img.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Hey can u also help me
I was running CM10.1 then I flashed back the stock image of 4.2 and now I am not able to update it to 4.2.1 it shows me an error when installing.
Please help!!!
udimars30 said:
Hey can u also help me
I was running CM10.1 then I flashed back the stock image of 4.2 and now I am not able to update it to 4.2.1 it shows me an error when installing.
Please help!!!
Click to expand...
Click to collapse
You have to flash both system and boot, plus do a full data and cache wipe. As long as you do that and you don't let root apps modify files on your /system partition, the update should install fine. Also, keep in mind that when you get the OTA notification on your phone, you cannot just select "Restart and Install" if you have ClockworkMod recovery. OTAs will only auto flash if you have stock recovery. If you're using ClockworkMod recovery, you'll have to pull the OTA file out of your /cache folder and put it on internal storage somewhere, then flash it manually in ClockworkMod.
OK so am I flashing the boot image and system image through fastboot? If so how do I do that? If not...how do I flash them?
Sent from my SGH-T999 using xda premium
Jms122589 said:
OK so am I flashing the boot image and system image through fastboot? If so how do I do that? If not...how do I flash them?
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Correct. Just extract system.img and boot.img from the package you download, then plug your tablet into USB, boot it into the bootloader, and do the following two commands:
fastboot flash boot boot.img
fastboot flash system system.img
If you want to wipe data, also do:
fastboot erase cache
fastboot erase userdata
That'll get you back to complete stock.
OK so were am I extracting these files to? Root of mysd card, desktop, etc? Thanks a bunch for your help btw I'm just not experienced at all with flashing outside of recovery or odin
Sent from my Nexus 10 using xda premium
Jms122589 said:
OK so were am I extracting these files to? Root of mysd card, desktop, etc? Thanks a bunch for your help btw I'm just not experienced at all with flashing outside of recovery or odin
Sent from my Nexus 10 using xda premium
Click to expand...
Click to collapse
Extract them to your desktop somewhere, then do fastboot from the command prompt.
oldblue910 said:
You have to flash both system and boot, plus do a full data and cache wipe. As long as you do that and you don't let root apps modify files on your /system partition, the update should install fine. Also, keep in mind that when you get the OTA notification on your phone, you cannot just select "Restart and Install" if you have ClockworkMod recovery. OTAs will only auto flash if you have stock recovery. If you're using ClockworkMod recovery, you'll have to pull the OTA file out of your /cache folder and put it on internal storage somewhere, then flash it manually in ClockworkMod.
Click to expand...
Click to collapse
sorry but i didn't get this part 'As long as you do that and you don't let root apps modify files on your /system partition' and to flash all that i need unlock bootloader??
oldblue910 said:
You have to flash both system and boot, plus do a full data and cache wipe. As long as you do that and you don't let root apps modify files on your /system partition, the update should install fine. Also, keep in mind that when you get the OTA notification on your phone, you cannot just select "Restart and Install" if you have ClockworkMod recovery. OTAs will only auto flash if you have stock recovery. If you're using ClockworkMod recovery, you'll have to pull the OTA file out of your /cache folder and put it on internal storage somewhere, then flash it manually in ClockworkMod.
Click to expand...
Click to collapse
I did all that you said but didn't understand this 'As long as you do that and you don't let root apps modify files on your /system partition' then i tried to update manually and it did again showed me an error like this:
udimars30 said:
I did all that you said but didn't understand this 'As long as you do that and you don't let root apps modify files on your /system partition' then i tried to update manually and it did again showed me an error like this:
Click to expand...
Click to collapse
Did you use the JOP40C factory images downloaded from the Google website somewhat recently? That error is caused when you flash the original set of JOP40C images released when the Nexus 10 first came out. There was a bug in them that Google fixed. They posted new images. You can download them at http://developers.google.com/android/nexus/images or http://www.randomphantasmagoria.com/firmware/nexus-10/mantaray.
Also, what I mean about root apps modifying /system files...so there are a lot of root apps out there that make tweaks to your system...stuff like making changes to your GPS config files for quicker lock-on, you yourself going in and deleting unwanted apps out of /system/app, you or an app making changes to build.prop, installing busybox in the wrong place and having it overwrite system commands with its own...things like that. If you or any app make any change whatsoever to any file anywhere on /system, an OTA will fail every time. It checks the hash of each and every file before applying the update and if a single one of them doesn't match what it expects, the OTA will fail. So just keep that in mind.
But that error you're getting about set_perm is most definitely caused by using the original, bad set of images that Google put out there. Download them again, try again and you should be in business.
oldblue910 said:
Did you use the JOP40C factory images downloaded from the Google website somewhat recently? That error is caused when you flash the original set of JOP40C images released when the Nexus 10 first came out. There was a bug in them that Google fixed. They posted new images. You can download them at http://developers.google.com/android/nexus/images or http://www.randomphantasmagoria.com/firmware/nexus-10/mantaray.
Also, what I mean about root apps modifying /system files...so there are a lot of root apps out there that make tweaks to your system...stuff like making changes to your GPS config files for quicker lock-on, you yourself going in and deleting unwanted apps out of /system/app, you or an app making changes to build.prop, installing busybox in the wrong place and having it overwrite system commands with its own...things like that. If you or any app make any change whatsoever to any file anywhere on /system, an OTA will fail every time. It checks the hash of each and every file before applying the update and if a single one of them doesn't match what it expects, the OTA will fail. So just keep that in mind.
But that error you're getting about set_perm is most definitely caused by using the original, bad set of images that Google put out there. Download them again, try again and you should be in business.
Click to expand...
Click to collapse
Thanks a ton dude but any place where i can talk to you??
like facebook or Google+??
udimars30 said:
Thanks a ton dude but any place where i can talk to you??
like facebook or Google+??
Click to expand...
Click to collapse
I'm on Twitter and G+. Just click on my name over on the left of this post and you can find links to my profiles.
I'm currently trying out a few kernels on my Nexus 4.
I'm currently running Franco's kernel but wanted to give Harsh's kernel a go.
Usually the kernels/roms I download are ZIP files, which work fine with TWRP, however, Harsh's kernel is an img file.
I found a previous thread that stated TWRP is compatible with img files & they can be installed fine - however - I only get the option to install a zip file. TWRP doesnt seem to be able to see an img file.
Am I doing something wrong or missing something?
Thanks.
IMG files are installed using fastboot. The command is:
fastboot flash recovery twrp.img
Sent from my Nexus 4 using xda premium
Thought so...
However, this thread does kinda makes out that flashing an .img through TWRP is possible.
http://forum.xda-developers.com/showthread.php?t=2033052
(different phone, i know - but I thought TWRP worked the same regardless of platform)
El Daddy said:
IMG files are installed using fastboot. The command is:
fastboot flash recovery twrp.img
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
For kernels it's fastboot flash boot boot.img
cmberry20 said:
Thought so...
However, this thread does kinda makes out that flashing an .img through TWRP is possible.
http://forum.xda-developers.com/showthread.php?t=2033052
(different phone, i know - but I thought TWRP worked the same regardless of platform)
Click to expand...
Click to collapse
That's also an HTC phone.
We do not have the capability to flash .img files in recovery.
Sent from my Nexus 4 using Tapatalk 2
Thanks for the correction. I had just woken up and misread the question.
Sent from my Nexus 4 using xda premium
Thanks for clearing it up.
I do a lot of ROM/kernel flashing away from a PC. So its convenient just to TWRP without the need connect it the phone via USB.
Sent from my Nexus 4 using xda app-developers app
oh I'm an idiot!
Just noticed that theres two download links for the Harsh Kernal. Ones a zip (for flashing in TWRP) & the others a .img.
Didnt notice the first link!! :silly:
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.
So i manage to remover the boot failure on from fastboot mode since it has been there everytime it boots up and it didnt boot up fully but after using droid utility to downgrade to 4.1.2 it no more goes to fastboot but now its stuck on a bootloop and my device is unlocked. So my question is. Can i install a rom to get out of this bootloop or is there any other way to get of the boot loop? Please i really need help!!!!
You should follow this to go back to 4.1.2 I would try to rsd back to whatever firmware you were on or just kk... Do you have a custom recovery on there to try and flash the ROM... What update were you on prior to doing what you did
Sent from my XT907 using XDA Premium 4 mobile app
ezknives said:
You should follow this to go back to 4.1.2 I would try to rsd back to whatever firmware you were on or just kk... Do you have a custom recovery on there to try and flash the ROM... What update were you on prior to doing what you did
Sent from my XT907 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I was running 4.4.2 kk but after ive tried to flash a image by using flasify to remove the boot loader unlocked message but it failed and it would start up on fastboot and thats it but after using droid utility to try to go back to 4.1.2 but after the reboot it stays in the bootloader message. but i do have a custom recovery im using twrp
I'm guessing you didn't make a backup before trying to flash the image... Or at all... I would say just restore your back up... If you want you could try to flash a ROM it would have to be comparable with whatever kernel you have and it may not work as you tried to use (I'm guessing) matt's utility... I would rsd the 4.4.2 firmware or use house of moto... If you want rid of the warning boot logo ATTACK just released some.... Always make a backup before attempting anything of that nature...and if you want to go back to 4.1.2 after the restore follow the method linked above
Sent from my XT907 using XDA Premium 4 mobile app
ezknives said:
I'm guessing you didn't make a backup before trying to flash the image... Or at all... I would say just restore your back up... If you want you could try to flash a ROM it would have to be comparable with whatever kernel you have and it may not work as you tried to use (I'm guessing) matt's utility... I would rsd the 4.4.2 firmware or use house of moto... If you want rid of the warning boot logo ATTACK just released some.... Always make a backup before attempting anything of that nature...and if you want to go back to 4.1.2 after the restore follow the method linked above
Sent from my XT907 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yeah well for now on ill try to make a backups more often but is there any stock roms availible for my device
Not recovery flashable....you should also search around for yourself more...
Sent from my XT907 using XDA Premium 4 mobile app
LIKEABEAST said:
Yeah well for now on ill try to make a backups more often but is there any stock roms availible for my device
Click to expand...
Click to collapse
I've managed to fix my phone with house of moto and its really useful also I want to thank you by trying to help me