Related
Hi everyone, i just had my Xperia Arc stuck at the bootscreen after doing these steps.
I previously had the Generic firmware of Xperia Arc S for my Arc, on Ice Cream Sandwich flavor of Android.
Today i started trying to figure out how to flash the CM 9 Rom, because i have it on my Kindle fire, but it failed.
I've did all the steps to Unlock my bootloader, and, even tho my phone is eligible for that ( i checked it on the services menu ), i could not Unlock it.
After retrieving the Key and running the fastboot i had the Message "Remote: oem unlock failed".
After giving up to unlock it, i decided to install "X-Parts" and install the CMW so i could flash the .zip file of the CM9 Right from the SDCard.
Ok, thats what i did:
1. Installed CMW
2. Wiped Data / Factory Reset
3. Wiped Cache
4. Flashed .zip from SDCARD
5. Zip Installed
6. Repeated steps 2 and 3 again
7. Rebooted
Since them, i am stuck at the Bootscreen with the word "Sony" on it, which leads me to think that the rom was not flashed properly, otherwise i would see the cyan / black bootscreen.
Also, i can't manage to boot into "recovery mode" again, i am pressing Power + Volume Down but it is not working.
Any idea of what can i do now ?
How can i install cm9 properly and unstuck my phone ?
Do i need to unlock my BL in order to install CM9 ?
Thanks in advance and sorry about this, but i am sort of desperate this time
Just tried to Flash the "boot.img" file found at the CM9 zip folder using FLASHTOOL, but it says:
"20/016/2012 15:16:27 - INFO - FASTBOOT Output:
sending 'boot' (4916 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.001s"
My device IS rooted, and i can garantee it.
Just extracted the Kernel.sin file from the .ftf Generic Firmware of ICS Android rom and tried to Flash using the Flashtool via Fastboot mode.
Same error saying that my device must be rooted.
marcelloLins said:
Just extracted the Kernel.sin file from the .ftf Generic Firmware of ICS Android rom and tried to Flash using the Flashtool via Fastboot mode.
Same error saying that my device must be rooted.
Click to expand...
Click to collapse
If the problem resides in rooting your phone, try this http://forum.xda-developers.com/showthread.php?t=1653188 remember, SEARCH is a friend!
in order to flash kernels via fastboot you need your bootloader unlocked
it is bootlooping on CM because you arent using right kernel
not too sure why your having issues unlocking it, but this is probably the first thing you need to tackle
all i can recommend is to keep trying
but im sure someone more helpfull will be along soon!!
and just FYI, just because nobody is answering doesnt mean you need to start a new thread in another section, especially development as its hard enough to navigate without usless threads. just search or use google!
firedeimos said:
If the problem resides in rooting your phone, try this http://forum.xda-developers.com/showthread.php?t=1653188 remember, SEARCH is a friend!
Click to expand...
Click to collapse
Do you understand that i can't even boot my phone ?
How am i supposed to Root it if i can't even make it boot ?
Please, any help here is welcome.
By the way, i AM searching, alot, for more than 4 hours already
its also worth noting that when it says device must be rooted, it is in relation to bootloader not being unlocked (as far as im aware)
yo-meister said:
its also worth noting that when it says device must be rooted, it is in relation to bootloader not being unlocked (as far as im aware)
Click to expand...
Click to collapse
So you are saying that i must try to Unlock my bootloader first, even tho i can't seem to make it boot ?
Not trying to be an ass, but i just can't seem to find a way to do it.
I have my IMEI wrote in a notepad file, but, once i try to unlock it's bootloader, it gives me an error. : "Remote: oem unlock failed!"
Not sure why this is happening, i am following the instructions on Sony Website...
to use a rom like CM, you need a custom kernel and to install a custom kernel you need to unlock bootloader
there are a few that dont require unlock but i havent personally tried these as mine is unlocked
its been a while since i unlocked mine but i seem to remember that you leave the last digit off when typing it in, someone confirm?
i was confused when i was putting in the number as it was longer than what was requested
yo-meister said:
to use a rom like CM, you need a custom kernel and to install a custom kernel you need to unlock bootloader
there are a few that dont require unlock but i havent personally tried these as mine is unlocked
its been a while since i unlocked mine but i seem to remember that you leave the last digit off when typing it in, someone confirm?
i was confused when i was putting in the number as it was longer than what was requested
Click to expand...
Click to collapse
I Love You.
Yes, i just did what you said.
We must ignore the LAST digit of IMEI, i was ignoring the first, since it was ZERO i thought that it would not matter.
Now that i have a new Bootloader Code, i used it and it worked.
Thanks a bunch, now, i must try to continue the process.
I will keep you guys updated
Update 1: The Bootloader is unlocked.
I tried to Flash the kernel.sin using the flashtool and seems like it was flashed correctly but i am still stuck in bootscreen.
Also, i still can't manage to boot in Recovery Mode to flash the CM9 from the SDCARD.
Any ideas?
Update 2: Flashed DoomKernel V04 Successfuly now i am trying to get into Recovery mode so that i can Finally Flash the cm9 rom in the sdcard.
wish me luck
Update 3: After booting into recovery mode, and trying to flash the CM9 .zip file, there is an error.
"Assert Failed: getprop..." From what i know of programming, this looks like the rom trying to assert that the values from the build.prop file must match either "LT18a","LT15i","LT15a" or "anzu".
Is there any way i can fix the file in order to make this "assert" directive works correctly ?
ha your welcome
i lost all my contacts when i first started all this, didnt backup with google account lol
now its just a case of...
put rom on SD CARD
BACKUP
wipe
flash kernel
flash rom
flash wifi modules (if required)
BOOT
and this is the first time i feel like i can say this...hit thanks if i helped haha
Just tried to Toggle the Assert Directives OFF from the DoomKernel but it is still checking for the asserts when trying to flash the Rom.
Any suggestions?
Just tried to Connect VIA ADB with the Phone in Recovery mode, and it worked.
My plan was to Pull the Build.prop file so i could edit and them, paste it back to the phone system so that the assert might work.
Here is the command i tried :
adb devices (OK)
adb pull /system/build.prop c:\build.prop
Error Message : remote object 'system/build.prop' does not exist
What can i do now ?
UPDATE 1: On Recovery Mode i just mounted the System and Data And Ext 2 Partitions and i still cannot seem to PULL the Build.prop File.
UPDATE 2: Flashed the Right kernel from the CM9 Pack, which is the FXP Team Kernel.
Tried to Flash again, now without assert verifications and i am receiving an error : E: Failed to Load Keys
marcelloLins said:
Just tried to Connect VIA ADB with the Phone in Recovery mode, and it worked.
My plan was to Pull the Build.prop file so i could edit and them, paste it back to the phone system so that the assert might work.
Here is the command i tried :
adb devices (OK)
adb pull /system/build.prop c:\build.prop
Error Message : remote object 'system/build.prop' does not exist
What can i do now ?
UPDATE 1: On Recovery Mode i just mounted the System and Data And Ext 2 Partitions and i still cannot seem to PULL the Build.prop File.
UPDATE 2: Flashed the Right kernel from the CM9 Pack, which is the FXP Team Kernel.
Tried to Flash again, now without assert verifications and i am receiving an error : E: Failed to Load Keys
Click to expand...
Click to collapse
So did you manage to get it work?
If not,this is what i would do:
1.Reflash stock fw
2.Root it
3.Install CWM
4.Try it,is it working,if yes flashed custom kernel for rom that i'm trying to flash
5.Then go to CWM and install rom and modules
6.Reboot the phone from CWM Menu and that should be it.It has to work.
I think these steps are easy to follow and no need to be a professional with programing to do it.Hope it will work for you.Cheers
pren22 said:
So did you manage to get it work?
If not,this is what i would do:
1.Reflash stock fw
2.Root it
3.Install CWM
4.Try it,is it working,if yes flashed custom kernel for rom that i'm trying to flash
5.Then go to CWM and install rom and modules
6.Reboot the phone from CWM Menu and that should be it.It has to work.
I think these steps are easy to follow and no need to be a professional with programing to do it.Hope it will work for you.Cheers
Click to expand...
Click to collapse
You mean Stock Firmware from Sony Ericson ?
Where can i find it ?
Is this one ?
http://uploaded.net/file/lpdhtmqi/LT15i_4.0.2.A.0.62_Generic Global World.ftf
I will try to flash it and see where i can get.
I just tried another flavor of CM9 (A nightly build) and i had the same error
marcelloLins said:
Just extracted the Kernel.sin file from the .ftf Generic Firmware of ICS Android rom and tried to Flash using the Flashtool via Fastboot mode.
Same error saying that my device must be rooted.
Click to expand...
Click to collapse
Try to flash an entire official firwmare with flashtool in flashmode mode (a 4.0.3 for easy rooting). So you ended with a working phone in a good mood. After that, root, install recovery, check if phone is always unlocked and try again with CM9.
spidermoon said:
Try to flash an entire official firwmare with flashtool in flashmode mode (a 4.0.3 for easy rooting). So you ended with a working phone in a good mood. After that, root, install recovery, check if phone is always unlocked and try again with CM9.
Click to expand...
Click to collapse
I am downloading this one :
http://uploaded.net/file/lpdhtmqi/LT15i_4.0.2.A.0.62_Generic Global World.ftf
Is there any problem with that ?
Update: These steps solved my problems:
1. Flash the 4.0.3 Android ICS Stock Firmware
2. Flash the Kernel from CM9
3. Wipe Factory and Cache
4. Flash the CM9
5. Flash Gapps
Reboot.
Thanks for all the help guys
Hi, question: I failed time and again to get CWM working, but finally got it to work using x-parts. However, x-parts is keen to point out that it is not a fully fledged recovery and that "if you wipe the system partition for any reason, it will be gone!".
Does this not mean that if I boot into recovery and install a new ROM (Going for the FXP CM10 one, if it matters), then when I wipe the phone beforehand I'll also wipe my CWM install, thus completely bricking the device? Would appreciate any thoughts, thanks
Artemicion said:
Hi, question: I failed time and again to get CWM working, but finally got it to work using x-parts. However, x-parts is keen to point out that it is not a fully fledged recovery and that "if you wipe the system partition for any reason, it will be gone!".
Does this not mean that if I boot into recovery and install a new ROM (Going for the FXP CM10 one, if it matters), then when I wipe the phone beforehand I'll also wipe my CWM install, thus completely bricking the device? Would appreciate any thoughts, thanks
Click to expand...
Click to collapse
Yes, if you wipe the system partition there will be no more CWM. For CM10, you need to flash a custom kernel for it to work. This custom kernel will usually come with a CWM recovery so it will not be wiped when you flash a new ROM.
僕のLT18iから送られてきた
Thanks. But, to clarify, once I flash new CM10/Jellybean Kernel, my current Gingerbread install will also completely cease to function right? And I'd need to flash back to something earlier to get it to work, if I so desired?
Artemicion said:
Thanks. But, to clarify, once I flash new CM10/Jellybean Kernel, my current Gingerbread install will also completely cease to function right? And I'd need to flash back to something earlier to get it to work, if I so desired?
Click to expand...
Click to collapse
Is your bootloader unlocked?
And yes you will have to flash GB ftf using flashtool
Sent from my LT18i
Yeah, I unlocked the bootloader and rooted it ages ago, but have since neglected actually updating the ROM, decided I can't live in a GB world anymore though.
So, as I understand it, process would be flash a new GB kernel to get CWM > Wipe Everything > Install the relevant ROM and GApps > Done? Does this ROM installation include the update to JB kernel then? Thanks
Artemicion said:
Yeah, I unlocked the bootloader and rooted it ages ago, but have since neglected actually updating the ROM, decided I can't live in a GB world anymore though.
So, as I understand it, process would be flash a new GB kernel to get CWM > Wipe Everything > Install the relevant ROM and GApps > Done? Does this ROM installation include the update to JB kernel then? Thanks
Click to expand...
Click to collapse
If I am not mistaken the kernel boot img should be inside the ROM zip. Check the ROM zip. Just flash the boot img using fastboot, boot into CWM recovery and flash ROM & gapps.
僕のLT18iから送られてきた
Ah, ok, well this brings me full circle. Because I'm trying to follow the boot instructions to do so, but:
fastboot -i 0xfce flash boot boot.img
doesn't work. I've taken the boot.img out of the ROM, and put it in the platform-tools folder. But whenever I try this line, it says it can't boot it, and quotes "no error" (no longer at home so can't quote the exact error, but it's something like that). I assumed the problem was me lacking CWM, hence was trying to install that first. Fastboot devices DOES show the device, and both fastboot and adb commands work in a terminal, but I just can't get it to boot into the ROM recovery for Cyanogenmod. Driving my crazy! Thanks
fastboot flash boot boot.img, if I'm not mistaken, is the right command. I use flashtool
Sent from my Xperia Arc S using xda premium
Artemicion said:
Ah, ok, well this brings me full circle. Because I'm trying to follow the boot instructions to do so, but:
fastboot -i 0xfce flash boot boot.img
doesn't work. I've taken the boot.img out of the ROM, and put it in the platform-tools folder. But whenever I try this line, it says it can't boot it, and quotes "no error" (no longer at home so can't quote the exact error, but it's something like that). I assumed the problem was me lacking CWM, hence was trying to install that first. Fastboot devices DOES show the device, and both fastboot and adb commands work in a terminal, but I just can't get it to boot into the ROM recovery for Cyanogenmod. Driving my crazy! Thanks
Click to expand...
Click to collapse
You don't need to add -i 0xfce to the command. Just type fastboot flash boot <name of boot image>.img
僕のLT18iから送られてきた
tangosierra_ said:
fastboot flash boot boot.img, if I'm not mistaken, is the right command. I use flashtool
Sent from my Xperia Arc S using xda premium
Click to expand...
Click to collapse
Thanks, I'll give that a go, not going to be able to try for a few days now, but will. FYI, I took the line of code I was trying directly from the Cyanogenmod wiki for Anzu
tangosierra_ said:
fastboot flash boot boot.img, if I'm not mistaken, is the right command. I use flashtool
Sent from my Xperia Arc S using xda premium
Click to expand...
Click to collapse
Ok, so finally got home to try this, still throwing this out: "error: cannot load 'boot.img': No error"
I've got the right boot.img in my platform-fools folder, the relevant CM build on my SD Root along with GApps. Drivers are definitely installed correctly as fastboot devices shows the device, as do adb command when it's on - anyone got any suggestions? Would be immensely grateful if this confounded problem could be solved. Thanks
Artemicion said:
Ok, so finally got home to try this, still throwing this out: "error: cannot load 'boot.img': No error"
I've got the right boot.img in my platform-fools folder, the relevant CM build on my SD Root along with GApps. Drivers are definitely installed correctly as fastboot devices shows the device, as do adb command when it's on - anyone got any suggestions? Would be immensely grateful if this confounded problem could be solved. Thanks
Click to expand...
Click to collapse
What is the name of the .img file? It can't have any spaces inside.
僕のLT18iから送られてきた
popthosegaskets said:
What is the name of the .img file? It can't have any spaces inside.
僕のLT18iから送られてきた
Click to expand...
Click to collapse
Looks to just be "boot.img" to me, no spaces or anything.
Have you tried flashtool?
Sent from my LT18i using xda premium
tangosierra_ said:
Have you tried flashtool?
Sent from my LT18i using xda premium
Click to expand...
Click to collapse
No, guess I'll try that next. As I remember, that's what I used to flash in order to root it ages ago. Thanks
hi,
My phone is soft bricked and stuck at boot logo. I am trying to flash stock recovery/kdz file using flash tool but getting stuck at"low battery" error.
Could you please help how i can bypass this error? I have spend a lot of time online and tried few methods but always getting stuck at this error. I dont have any alternative phone and this is really disappointing.
I am using E988 India model.
CLICK HERE MATE. LET ME KNOW IF IT HELPS. IF NOT USE THE INSTRUCTIONS BELOW
I'm using same phone and have the same problem. I still can't flash stock with the tool but I can tell you how to get out of soft brick. Download madmacks e980 lokified TWRP recovery and also CM 11 latest version. Get in to recovery mode and go to install file (sideload) and flash the recovery first then reboot in to recovery again and sideload CM 11. When I get a definitive solution to flash stock I will let you know mate. If you have problems or don't know what I'm talking about then reply here. You well need adb installed on computer and open a new command window by holding shift and click right noise button at the same time. Make sure you perform this from the same directory as where there files are that your flashing. Once your phone prompts you to sideload type in to the command window adb sideload (the exact file name of the file you want to flash.zip) but without the brackets
uppon2 said:
CLICK HERE MATE. LET ME KNOW IF IT HELPS. IF NOT USE THE INSTRUCTIONS BELOW
I'm using same phone and have the same problem. I still can't flash stock with the tool but I can tell you how to get out of soft brick. Download madmacks e980 lokified TWRP recovery and also CM 11 latest version. Get in to recovery mode and go to install file (sideload) and flash the recovery first then reboot in to recovery again and sideload CM 11. When I get a definitive solution to flash stock I will let you know mate. If you have problems or don't know what I'm talking about then reply here. You well need adb installed on computer and open a new command window by holding shift and click right noise button at the same time. Make sure you perform this from the same directory as where there files are that your flashing. Once your phone prompts you to sideload type in to the command window adb sideload (the exact file name of the file you want to flash.zip) but without the brackets
Click to expand...
Click to collapse
Thank you very much for this help. I have never tried adb. Probably I shall now learn it and then try to do as you suggested. I am not particular about stock ROM. In fact I will be happy if there is stable cm ROM for this phone.
I juts bought this phone two days back. There are too many model numbers n am little scared now about choosing the right ROM. Do you mind sharing link for correct cm11 ROM please?,
Thanks again for your help!
Sent from my GT-I9500 using xda app-developers app
Hi.
As the title says, I have bricked my GPad and am stuck in Fastboot mode. I am able to pull up a command line on my computer and reboot the device from there, but that's about all I've tried. I have read online that there are commands for flashing a boot.img file, but I can't find one and I don't know how to do it. Do I wipe the device from my computer first, or just flash the .img file? Any help would be greatly appreciated.
God Bless, Mark
dadof10 said:
Hi.
As the title says, I have bricked my GPad and am stuck in Fastboot mode. I am able to pull up a command line on my computer and reboot the device from there, but that's about all I've tried. I have read online that there are commands for flashing a boot.img file, but I can't find one and I don't know how to do it. Do I wipe the device from my computer first, or just flash the .img file? Any help would be greatly appreciated.
God Bless, Mark
Click to expand...
Click to collapse
Don't wipe the device! At least I wouldn't. Might not be able to get back in!
Flash recovery and then a ROM.
sleekmason said:
Don't wipe the device! At least I wouldn't. Might not be able to get back in!
Flash recovery and then a ROM.
Click to expand...
Click to collapse
Thanks for the help, Sleek. Which recovery image should I flash and where can I get it?
Sent from my SM-G900V using XDA Free mobile app
dadof10 said:
Thanks for the help, Sleek. Which recovery image should I flash and where can I get it?
Sent from my SM-G900V using XDA Free mobile app
Click to expand...
Click to collapse
double check and make sure it is for your device. Link to Recovery
---------- Post added at 02:09 PM ---------- Previous post was at 02:08 PM ----------
sleekmason said:
double check and make sure it is for your device. Link to Recovery
Click to expand...
Click to collapse
looks like you need loki also. There may be others that would be better suited to answer this question, as I have the Google Play edition. but at least this will point you in the right direction!
sleekmason said:
double check and make sure it is for your device. Link to Recovery
---------- Post added at 02:09 PM ---------- Previous post was at 02:08 PM ----------
looks like you need loki also. There may be others that would be better suited to answer this question, as I have the Google Play edition. but at least this will point you in the right direction!
Click to expand...
Click to collapse
Ok. Thanks, I really appreciate it, take care.
Sent from my SM-G900V using XDA Free mobile app
dadof10 said:
Ok. Thanks, I really appreciate it, take care.
Sent from my SM-G900V using XDA Free mobile app
Click to expand...
Click to collapse
I love it when I see new members breaking theyre devices....lol....because I've been there....lol.....and xda is your friend, we are here to help....anyway....I agree with the previous advice, dont wipe device, how did you get in the situation your in?....flash recovery, and try and find a rom, make sure its for the VK810, other roms (v500 or V510) will only make things worse.... last I checked there are not many VK810 roms out there, let me know how you make out....
mcerk02 said:
I love it when I see new members breaking theyre devices....lol....because I've been there....lol.....and xda is your friend, we are here to help....anyway....I agree with the previous advice, dont wipe device, how did you get in the situation your in?....flash recovery, and try and find a rom, make sure its for the VK810, other roms (v500 or V510) will only make things worse.... last I checked there are not many VK810 roms out there, let me know how you make out....
Click to expand...
Click to collapse
I was rooted, running 4.4.2. I tried to flash 4.2.2 aboot.img with Flashfy, so I could flash TWRP recovery. Didn't work out.
Flashing a recovery is what I don't know how to do in fastboot mode. Can you walk me through it? Also, I don't know which recovery to flash.
Sent from my SM-G900V using XDA Free mobile app
dadof10 said:
I was rooted, running 4.4.2. I tried to flash 4.2.2 aboot.img with Flashfy, so I could flash TWRP recovery. Didn't work out.
Flashing a recovery is what I don't know how to do in fastboot mode. Can you walk me through it? Also, I don't know which recovery to flash.
Sent from my SM-G900V using XDA Free mobile app
Click to expand...
Click to collapse
The directions for installing are in the link I gave you, showing to push (put) the files in the proper places for your device.
You must have ADB installed on your home computer. There is a guide on how to do this in the general section ( second sticky post), or, if using Linux, the first post.
After ADB is installed, both the Loki patch and the recovery.IMG will need to be in the platform_tools folder in the ADB folder. In Linux this would be /opt/adb/platform_tools.
In either case, to install, you must open a terminal (prompt) in the path of the install, meaning you must open the terminal in platform_tools.
Then follow the commands in the recovery post to install both Loki, and the recovery.img
sleekmason said:
The directions for installing are in the link I gave you, showing to push (put) the files in the proper places for your device.
You must have ADB installed on your home computer. There is a guide on how to do this in the general section ( second sticky post), or, if using Linux, the first post.
After ADB is installed, both the Loki patch and the recovery.IMG will need to be in the platform_tools folder in the ADB folder. In Linux this would be /opt/adb/platform_tools.
In either case, to install, you must open a terminal (prompt) in the path of the install, meaning you must open the terminal in platform_tools.
Then follow the commands in the recovery post to install both Loki, and the recovery.img
Click to expand...
Click to collapse
Ok, I got it. Duhhh...I re-read it and it makes sense now. Somehow I had it in my mind that I had to open terminal emulator on my GPad, which I can't do. I'll try it tonight when I get home from work and let you know how it goes. Thanks again.
Sent from my SM-G900V using XDA Free mobile app
sleekmason said:
The directions for installing are in the link I gave you, showing to push (put) the files in the proper places for your device.
You must have ADB installed on your home computer. There is a guide on how to do this in the general section ( second sticky post), or, if using Linux, the first post.
After ADB is installed, both the Loki patch and the recovery.IMG will need to be in the platform_tools folder in the ADB folder. In Linux this would be /opt/adb/platform_tools.
In either case, to install, you must open a terminal (prompt) in the path of the install, meaning you must open the terminal in platform_tools.
Then follow the commands in the recovery post to install both Loki, and the recovery.img
Click to expand...
Click to collapse
OK, Sleekmason, I put everything where it should be, but when I use the "adb" commands (adb push loki_flash...) I get "device not found" in terminal. As I said, I can reboot the GPad using "fastboot reboot" command, so it sees it in fastboot mode, but not in adb mode. I loaded the drivers during the adb install, so I'm pretty sure all of them are there. Is there something I'm missing? Is there a way to push the files to the GPad with fastboot?
dadof10 said:
OK, Sleekmason, I put everything where it should be, but when I use the "adb" commands (adb push loki_flash...) I get "device not found" in terminal. As I said, I can reboot the GPad using "fastboot reboot" command, so it sees it in fastboot mode, but not in adb mode. I loaded the drivers during the adb install, so I'm pretty sure all of them are there. Is there something I'm missing? Is there a way to push the files to the GPad with fastboot?
Click to expand...
Click to collapse
There is an lg recovery tool that is talked about here... But we are now out of my territory lol. maybe somebody else can chime in?
sleekmason said:
There is an lg recovery tool that is talked about here... But we are now out of my territory lol. maybe somebody else can chime in?
Click to expand...
Click to collapse
That's the first thing I tried and it wouldn't recognize the GPad either. I loaded all the drivers, but no luck. Thanks for trying, dude.
dadof10 said:
That's the first thing I tried and it wouldn't recognize the GPad either. I loaded all the drivers, but no luck. Thanks for trying, dude.
Click to expand...
Click to collapse
not saying you should, but you could always try to flash the recovery just to see if it would work.
same problem, but how I fixed it
How I got bootloop'd - I was on a trip and tried to root/flash twrp from a chromebook and as you can tell the process did not work. I ended up trying to flashfly a 4.2.2 boot.img over a 4.4.2 setup. Not the best idea. Once I returned to my windows machine, I was able to flash via adb/fastboot tools. So I found this thread and wanted to help anyone else if they arrived here and read thru the posts.
I was stuck at the fastboot text base screen on my Gpad (VK810). I dl'd the LG tools, the LG driver & tried a KDZ recover, but I was unsuccessful. Fastboot would control my device, reboots worked, but when I run fastboot devices, I only saw a single ? where the device serial number is. After a few attempts at various methods, I ended up guessing which file I had to flash.
After dl'ding a few roms from here and extracting them, it took the boot.emmc.win and flash my boot.img with that. worked with the following code and now I'm up and running.
Code:
fastboot flash boot boot.emmc.win
followed by
Code:
fastboot reboot
this worked for me and could work for you, but I can only say that it worked when I was able to access my tablet via fastboot commands.
Downgrade aboot
dd if=/sdcard/aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
exit
exit[/HTML]
I am not able to do the above after installing Lollipop because can't get root, specifically can't update binaries in supersu and no su. Also Adbd Insecure not working. Now I am able to get into fastboot, strangely thru factory reset. Can I use 'fastboot flash aboot aboot.img' instead. Many thanks.
pakron said:
dd if=/sdcard/aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
exit
exit[/HTML]
I am not able to do the above after installing Lollipop because can't get root, specifically can't update binaries in supersu and no su. Also Adbd Insecure not working. Now I am able to get into fastboot, strangely thru factory reset. Can I use 'fastboot flash aboot aboot.img' instead. Many thanks.
Click to expand...
Click to collapse
Sir or m'am, in the future, you shouldn't post the same thing in two different threads.
FynxSyndct said:
How I got bootloop'd - I was on a trip and tried to root/flash twrp from a chromebook and as you can tell the process did not work. I ended up trying to flashfly a 4.2.2 boot.img over a 4.4.2 setup. Not the best idea. Once I returned to my windows machine, I was able to flash via adb/fastboot tools. So I found this thread and wanted to help anyone else if they arrived here and read thru the posts.
I was stuck at the fastboot text base screen on my Gpad (VK810). I dl'd the LG tools, the LG driver & tried a KDZ recover, but I was unsuccessful. Fastboot would control my device, reboots worked, but when I run fastboot devices, I only saw a single ? where the device serial number is. After a few attempts at various methods, I ended up guessing which file I had to flash.
After dl'ding a few roms from here and extracting them, it took the boot.emmc.win and flash my boot.img with that. worked with the following code and now I'm up and running.
Code:
fastboot flash boot boot.emmc.win
followed by
Code:
fastboot reboot
this worked for me and could work for you, but I can only say that it worked when I was able to access my tablet via fastboot commands.
Click to expand...
Click to collapse
i was having the same issue, get the boot.img file and typed "fastboot flash boot boot.img" after moving the boot.img file into the same folder as adb/fastboot and it worked, thanks bro!
Hey guys, I want Android 4.4.4 on my Xperia S (am running 4.1.2 standard now). But to install another ROM, you need another kernel. Does anyone have the link to the kernel to use for me? I can't find it...
(And is there anything particulair ROM anyone can recommend?)
EDIT: Alright, does anyone have a tutorial with Flashtool too, because I can't figure it out, and its driving me nuts.
Ramshield said:
Hey guys, I want Android 4.4.4 on my Xperia S (am running 4.1.2 standard now). But to install another ROM, you need another kernel. Does anyone have the link to the kernel to use for me? I can't find it...
(And is there anything particulair ROM anyone can recommend?)
EDIT: Alright, does anyone have a tutorial with Flashtool too, because I can't figure it out, and its driving me nuts.
Click to expand...
Click to collapse
The kernel for any ROM is in the zip of ROM itself. The boot.img file is the Kernel. If You flash the any ROM via recovery, it will automatically flash the kernel too, as long as the boot.img file is present in the ROM.zip.
Mirhawk said:
The kernel for any ROM is in the zip of ROM itself. The boot.img file is the Kernel. If You flash the any ROM via recovery, it will automatically flash the kernel too, as long as the boot.img file is present in the ROM.zip.
Click to expand...
Click to collapse
I followed http://forum.xda-developers.com/showthread.php?t=1963961 this tutorial, however, when I click fastboot via ADB, my phone reboots and then the blue flashlight goes on. But then my phone continues to boot, so if I click fastboot via fastboot it doesn't work.
I'm getting: ERROR - This action can only be done in fastboot mode and ERROR - Drivers need to be installed for connected device... Any help you can give?
Ramshield said:
I followed http://forum.xda-developers.com/showthread.php?t=1963961 this tutorial, however, when I click fastboot via ADB, my phone reboots and then the blue flashlight goes on. But then my phone continues to boot, so if I click fastboot via fastboot it doesn't work.
I'm getting: ERROR - This action can only be done in fastboot mode and ERROR - Drivers need to be installed for connected device... Any help you can give?
Click to expand...
Click to collapse
You have not installed the fastboot drivers then. The drivers can be found at inside 'drivers' folder where You installed the flashtool. Install fastboot and flashmode and Sony Xperia S related drivers from the list.
Mirhawk said:
You have not installed the fastboot drivers then. The drivers can be found at inside 'drivers' folder where You installed the flashtool. Install fastboot and flashmode and Sony Xperia S related drivers from the list.
Click to expand...
Click to collapse
Sorry to bother you, but when I check fastboot and fastmode, I get: http://puu.sh/dVUDt/347d16f514.png (Running Windows 10 x64?)
EDIT: Booted with safe mode, to disable something with driver signature, installed the drivers and flashed the kernel. Took me total of 8 hours, but got it all working, thanks a lot for your help!
Does Lollipop 5.0(.2/3?) work properly on Xperia S, and how about the issues with memory, and applications closing itself?
Ramshield said:
Sorry to bother you, but when I check fastboot and fastmode, I get: http://puu.sh/dVUDt/347d16f514.png (Running Windows 10 x64?)
EDIT: Booted with safe mode, to disable something with driver signature, installed the drivers and flashed the kernel. Took me total of 8 hours, but got it all working, thanks a lot for your help!
Does Lollipop 5.0(.2/3?) work properly on Xperia S, and how about the issues with memory, and applications closing itself?
Click to expand...
Click to collapse
Ah yes, Windows 8/10 cause drivers issue. It works properly for daily use. The latest version of nAOSP is not causing Me any force closing f apps now.