Related
Hello, i have Z_v04b_A2SD with me and plan to install it after rooting the phone. My phone is on 1.34.720.6. CAn anyone tell me how to install this rom on phone?
Thanks
download rom manager from the market. use it to flash clockworkmod recovery. install the .zip file from the recovery
next time...
1. Post in the General thread not developer
2. Look around before you post. This is one of those things that's been answered a billion times.
Boot into ClockworkMod recovery, hit "install zip from sdcard," hit "choose zip from sdcard," and select the zip file.
Thanks a miilion guys, will try and post results
Just one more question, when i boot into recovery mode, it shows red traingle icon and doesnt go beyond it
just flash clockworkmod recovery again, for some reason it takes twice sometimes to get recovery installed
Viltran said:
just flash clockworkmod recovery again, for some reason it takes twice sometimes to get recovery installed
Click to expand...
Click to collapse
Do i need to turn s-off, if so how to do it?
Yes you need S-OFF to flash a custom recovery. See the Wiki on how to use gfree for this. But this really doesn't belong in this forum
Well i permrooted my phone and turned s-off also, but when i select and install file from sd card i get error. I think Z_v04b_A2SD file is corrupted. Can you guys point me out to a basic rom that can put russian language in the phone also?
Are you sure, it has russian language in it?
This thread has been closed. Please try searching before creating a new thread. These questions have been asked countless times before.
p.s. all questions should be posted in Q&A section. I've moved this thread as its not related to rom development
Hi... I just found that Clockwork Recovery has new version from their website but in zip format. Try to install it through ROM Manager and recovery mode but it is just temporary recovery. Every time I enter recovery mode by pressing power and vol down and choose recovery it is back to old recovery.
Does anyone try this new recovery and how to make it permanent or is it available in img format so I can flash it using Android Flasher.
for your reference please find it here :
hxxp://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.0.0-bravo.zip (please change hxxp into http)
*** sorry for my horrible English and grammar
it is cause you use the fake-flash method, launching CWM 5.0.0 by flashing a .zip file from your current recovery.
in order to permanently change your recovery you would have to be S-OFF and have a .img file of the new recovery
My HTC Desire already S-OFF but where to find this img file of new CWM Recovery?
I have search over Google and this forum but did not found. Is it possible to change this zip file into img file?
The file:
http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.0.0-bravo.img
Md5Sum:
http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.0.0-bravo.img.md5sum.txt
davebugyi said:
The file:
http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.0.0-bravo.img
Md5Sum:
http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.0.0-bravo.img.md5sum.txt
Click to expand...
Click to collapse
Thank you very much... how can I missed that
davebugyi said:
The file:
http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.0.0-bravo.img
Md5Sum:
http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.0.0-bravo.img.md5sum.txt
Click to expand...
Click to collapse
You are smart
CWM website folder can browse
got it
http://download.clockworkmod.com/recoveries/
recovery-clockwork-5.0.0.0-bravo.img 30-Aug-2011 23:25 3106816
recovery-clockwork-5.0.0.0-bravo.img.md5sum.txt 30-Aug-2011 23:25 92
Easier just to look here:
http://www.clockworkmod.com/recovery_images.html
EddyOS said:
Easier just to look here:
http://www.clockworkmod.com/recovery_images.html
Click to expand...
Click to collapse
Yes but not all file available.
like HTC Bravo only latest recovery in zip format only.
Thanks
Yeah, but as this thread is for v5.0.0.0 then people will want the newest will they not?
someone already did some test?
for example backup the current rom (maybe one with ext partition), then flash an other rom (just for test), and then restore the backup (and see if boots and everything ok)?
i will try later anyway, but of course will be nice to already know if its work or have some problems
Has any one had the edify script error with CWM 5.0.0.0 recovery ?
I flashed CWM 5.0.0.0 today via fastboot and it works fine - however I tried flashing Cool 3D V9 Rom and then when i flashed the boot loop fix & got the edify scripting error does any one know of a work around ??? I did a search and i found some code by coolexe and baadnews but not sure if there is a way to fix this ?
-Dan
danw1million said:
Has any one had the edify script error with CWM 5.0.0.0 recovery ?
I flashed CWM 5.0.0.0 today via fastboot and it works fine - however I tried flashing Cool 3D V9 Rom and then when i flashed the boot loop fix & got the edify scripting error does any one know of a work around ??? I did a search and i found some code by coolexe and baadnews but not sure if there is a way to fix this ?
-Dan
Click to expand...
Click to collapse
ask the dev to update the script in the flashable zip or flash a 2.x recovery (amend script is no more supported from 3.x and up, only edify is supported)
anyone have a changelog? cant find one anywhere!
andQlimax said:
ask the dev to update the script in the flashable zip or flash a 2.x recovery (edify script is no more supported from 3.x and up)
Click to expand...
Click to collapse
Thanks for the advice will do.
sjknight413 said:
anyone have a changelog? cant find one anywhere!
Click to expand...
Click to collapse
follow koush or clockworkmod on twitter..5.x has faster backups (now it used .tar files) and preserve the file system of each partition (if ur sd-ext is ext3, it will be backup and restore as ext3, if u have ext4 it will be ext4, etc..with previous cwm recoveries the sdext was restored always as ext3)
also a new color sheme..now is blue light
edit: new recovery seems available 5.0.1.0 http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.1.0-bravo.img
I read from a koush twit :
"Desire and Desire CDMA users: I have just switched you to real flashing rather than fakeflash. You will need to S-OFF. with unrevoked."
so, out of curiosity, how Rom Manager can flash the recovery for real?
I always use fastboot, and i though there was no other way than that and the PB99IMG.zip method..
Someone know how that works (i mean the flashing through an app)?
i'm fine with 4.xxxx
andQlimax said:
I read from a koush twit :
"Desire and Desire CDMA users: I have just switched you to real flashing rather than fakeflash. You will need to S-OFF. with unrevoked."
so, out of curiosity, how Rom Manager can flash the recovery for real?
I always use fastboot, and i though there was no other way than that and the PB99IMG.zip method..
Someone know how that works (i mean the flashing through an app)?
Click to expand...
Click to collapse
Well there have always been another way just not on desire, since s-on users couldn't write to system or recovery while system was booted. But with s-off using a flash_image script will work just fine, which is pretty much what rom manager does(i assume).
So I asked koush on twitter to change us to native recovery flashing since s-off have been around for quite some time for desire
edit: so for everyone s-off that means: to update just install/open rommanager and press "flash clockworkmod recovery"(tested and working just fine)
mortenmhp said:
Well there have always been another way just not on desire, since s-on users couldn't write to system or recovery while system was booted. But with s-off using a flash_image script will work just fine, which is pretty much what rom manager does(i assume).
So I asked koush on twitter to change us to native recovery flashing since s-off have been around for quite some time for desire
edit: so for everyone s-off that means: to update just install/open rommanager and press "flash clockworkmod recovery"(tested and working just fine)
Click to expand...
Click to collapse
Thanks to ur tips, i found how it works!
from the terminat emulator on the phone:
Code:
flash_image recovery /sdcard/recovery.img
that should flash the recovery (even other partition i though), without use fastboot and without use the pc! thats nice!
On AOSP roms the flash_image utility is already included on /system/bin..in other roms (like stock ones) it should be downloaded and placed on the phone and used in the same way
that probably what rom manager does
So there is no way to get the latest version of ClockworkMod Recovery if we are on S-ON ?
ok im truely frustrated after trying to figure this out in past 2 days and reading more than 60 threads/websites.
Problem:
my one x was running 4.0.4 rooted +supre user+CWM, till i got the notification for 4.1 update. i pressed install now and downloaded around 380 MB, during the update phase a red exclamation icon appeared and phone rebooted into 4.0.4.
relocked bootloader, flashed stock recovery and downloaded it again and this time copied the OTA file before pressing install. so i installed and same issue.
uninstalled Avast AV (android) and ran through the same process again, same thing, started up into 4.0.4 again.
unlocked the bootloader, flashed CWM 5.8.4, copied ota file into phone and renamed it to update.zip. ran it from recovery menu and got status 7 error.
downloaded and ran JBFWTOOL21 and followed the instructions, during one of the steps i encountered an error and after restarting the phone i was stock at "HTC One x" with "beatsound" logo at bottom.
NOW NOTHING WORKS
what ive tried so far:
relocked loader and flashed stock recovery and tried Factory Reset, no luck.
unlocked loader and flash CWM and tried wiping cache and wiping disk. nothing.
relocked loader,flashed recovery and ran stock RUU "RUU_ENDEAVOR_U_ICS_40_HTC_ARA_1.28.415.9_Radio_1.1204.103.14_release_25679_signed" but it doesnt work, give an error related to version numbers or something.
extracted system.img, boot.img from RUU temp folder ROM.zip and tried to flash but cant flash system.img (918mb). something about not enough HEAP i think.
from the OTA JB zip extracted recovery.img, boot.img and recovery.img and flashed them. nothing.
downloaded "One_X_All-In-One_Kit_v2.1" and tried kernel flash, nothing.
clearing cache via fastboot command also doesnt work
really appreciate any helpful input guys, im really frustrated. thanks
Oh my.. First, stop unlock and relock of bootloader. Do you have a cwm backup from before all this started? Flashing cwm and restoring that backup will get you far.
The first ota attempt failed due to cwm, always return to stock recovery (recovery.img from your cwm backup image) before applying ota update!
Kind Regards
TwinAdk
unfortunately, no. no backup.
since it all started from the official update i didnt make any backups.
Stop trying flash randomly. Run the following command:
fastboot getvar version-main
it wasnt just random flashing, i starting reading different posts and so tried them all one-by-one to see which works, anyway the output:
version-main: 3.16.415.4
woomera said:
it wasnt just random flashing, i starting reading different posts and so tried them all one-by-one to see which works, anyway the output:
version-main: 3.16.415.4
Click to expand...
Click to collapse
Well that's why the older RUU wouldn't work. You have the latest.
You'll need to go to the ROM backups thread and see if you can get a backup and flash its boot.img and restore it from CWM.
Actually, reboot your PC and try to flash system.img and boot.img again. You will probably need to be locked.
but isnt that the boot.img from "OTA_ENDEAVOR_U_JB_45_S_HTC_ARA_3.16.415.4-2.17.415.2_release_304331jrfus698taf4vm1x"?
cause i have already tried it, didnt work. i have the OTA file.
Modified my post. Look up.
i have boot.img from firmware with hboot 3.16 and 3.19, which one to use?
and the system.img is from stock RUU which is "RUU_ENDEAVOR_U_ICS_40_HTC_ARA_1.28.415.9_Radio_1.1204.103.14_release_25679_signed", will that work?
the OTA JB is a zip file and doesnt have system.img.
Err.. 1.39?
yes
the firmware included in "JBFWTOOL21" is 1.36 which is used by many to manually upgrade to JB but the firmware inside the OTA file itself is 3.19 which is also the version i updated to since i thought its the reason the update doesnt work.
the Hboot version on my phone is 1.39 at the moment.
Hmmm. Looks like you'll have to find a backup in the backups thread and flash it.
BenPope said:
Hmmm. Looks like you'll have to find a backup in the backups thread and flash it.
Click to expand...
Click to collapse
i dont understand, a backup of what? the system.img?
Something similar happened to me....my phone was bootlooping. I flashed a custom rom and it booted up fine... did u try flashing a custom rom?
sridheepan said:
Something similar happened to me....my phone was bootlooping. I flashed a custom rom and it booted up fine... did u try flashing a custom rom?
Click to expand...
Click to collapse
I thought about suggesting that too, but I'm new to flashing so I didn't feel confident enough to do it..
But off the top of my head, a custom rom, complete with boot.img and everything should work..
I'm using http://forum.xda-developers.com/showthread.php?t=2013506, it's super great and support all hboot versions.
No guarantees it will work though.
Kind Regards
TwinAdk
sridheepan said:
Something similar happened to me....my phone was bootlooping. I flashed a custom rom and it booted up fine... did u try flashing a custom rom?
Click to expand...
Click to collapse
guess it worth a try even though i'd rather fix the problem in hand in another fashion.
gonna give it a try and post the results.
k so i downloaded the Blade rom and it worked, thanks "TwinAdk".
so now about JB. should i just use "JBFWTOOL21" or better if i do it manually?
and is this the right order to do it manually: ?
-unlock bootloader
-flash CWM
-flash boot.img
-install from zip in CWM
woomera said:
i dont understand, a backup of what? the system.img?
Click to expand...
Click to collapse
A nandroid backup, like what Clockworkmod recovery makes.
woomera said:
k so i downloaded the Blade rom and it worked, thanks "TwinAdk".
so now about JB. should i just use "JBFWTOOL21" or better if i do it manually?
and is this the right order to do it manually: ?
-unlock bootloader
-flash CWM
-flash boot.img
-install from zip in CWM
Click to expand...
Click to collapse
NP, glad it worked! So now you have a phone that can actually boot up and make phone calls.. Not on the stock rom you wanted, but it's better than when you started this thread
From this point on, you can use a "return to stock" thread for the HOX.
1. Make a NANDROID backup via CWM (so you can get back to what you have now!)
2. Move the backup to your computer, to avoid anything happening to it
3. See this tutorial ([TUT] Getting back to stock after flashing custom roms [Noob friendly])
NOTE: The thread says the following in the top:
NOTE: These instructions require that you have one of the ICS hboot versions in order to work (1.12.0000 or lower). If you have one of the new JB hboots 1.28, 1.31 or 1.33 there is currently no way to return to stock until a JB ruu is released for your device.
Click to expand...
Click to collapse
The "new jb hboots" also refers to 1.39.
I have the 1.39 myself, and i believe i am able to return to stock via my CWM backup of my stock phone, from before i flashed a custom rom the first time.. Is that assumption wrong? Someone more experienced than me to the rescue, please
Kind Regards
TwinAdk
BenPope said:
A nandroid backup, like what Clockworkmod recovery makes.
Click to expand...
Click to collapse
thanks for the clarification
TwinAdk said:
NP, glad it worked! So now you have a phone that can actually boot up and make phone calls.. Not on the stock rom you wanted, but it's better than when you started this thread
From this point on, you can use a "return to stock" thread for the HOX.
1. Make a NANDROID backup via CWM (so you can get back to what you have now!)
2. Move the backup to your computer, to avoid anything happening to it
3. See this tutorial ([TUT] Getting back to stock after flashing custom roms [Noob friendly])
NOTE: The thread says the following in the top:
The "new jb hboots" also refers to 1.39.
I have the 1.39 myself, and i believe i am able to return to stock via my CWM backup of my stock phone, from before i flashed a custom rom the first time.. Is that assumption wrong? Someone more experienced than me to the rescue, please
Kind Regards
TwinAdk
Click to expand...
Click to collapse
i have read the same thing, also "BenPope" mentioned it. so with this version of Hboot (1.39) i cant restore unless its a nandroid backup.
but i dont wanna go back to stock ICS! i wanna finish what i was trying to do in first place, Upgrade to JB.
but no matter what i do i get the "status 7 error". i have tried it with the OTA my phone downloaded and also downloaded it again directly from HTC website via a link from one of the threads in forum.
so status 7 apparently is related to CRC error but how can that be? and what is my option right now to do the upgrade? also bear in mind that before all these happened the normal upgrade process via the "system update" also failed with a red icon error.
Hello
I own Ouya for the month but most of time I use it as media-box for TV (watching movies, etc)
I have already rooted it and installed play market but i hate the stock UI and obsolate android
I saw a video in youtube with CM11 and ouya (android 4.4) and started to google the solution
I already know that it is based on Eternity Project kernel.
I found the way to install bootloader http://www.eternityproject.eu/topic/1114365-eternityproject-tpl-bootloader-for-ouya/ and it is clear
The next step is to install kernel http://www.eternityproject.eu/topic/1114362-eternityproject-kernel-3437-for-ouya-cpu-2ghz-gpu-650mhz/ but it is unclear for me about fastboot command
The next step as I understand is to install CM11 from the CWM
Is it possible to install KitKat without EP kernel?
So If someone have detailed steps or howto on installing CM11 on ouya please give it to this thread
Thanks in advance
I think this is what you're looking for. I'm not sure the EP boot loader is compatible but I'm sure its mentioned in the thread somewhere. Or in the bootmenu thread anyway.
http://forum.xda-developers.com/showthread.php?p=51332165
Sent from my Nexus 5 using XDA Premium 4 mobile app
This is the order you need to go:
Upgrade to newest clockwork mod from milaq in your recovery.
Then install the failsafe bootloader.
Then install cm11 from the new recovery, along with gapps he posted in the same thread Make sure to wipe all the stock stuff.
Thats it.
quepaso said:
This is the order you need to go:
Upgrade to newest clockwork mod from milaq in your recovery.
Then install the failsafe bootloader.
Then install cm11 from the new recovery, along with gapps he posted in the same thread Make sure to wipe all the stock stuff.
Thats it.
Click to expand...
Click to collapse
Can you put that in a bit more laymans desperate for a guide,you say wipe all stuff,do i backup my ouya in recovery first do i erase every thing and how please?
Sorry to be a pain [email protected] it up once and had to unbrick already spent 48hrs repairing my ouya and put a guide up on how on here,because nobody puts it laymans online for this.I downloaded all files ready to download folder mate.
PHYSC-1 said:
Can you put that in a bit more laymans desperate for a guide,you say wipe all stuff,do i backup my ouya in recovery first do i erase every thing and how please?
Sorry to be a pain [email protected] it up once and had to unbrick already spent 48hrs repairing my ouya and put a guide up on how on here,because nobody puts it laymans online for this.I downloaded all files ready to download folder mate.
Click to expand...
Click to collapse
Its hard to lay it out, you need to go to the threads where the info is already layed out.
Do you already have a custom recovery installed like clockwork? Great, then go to the failsafe thread to get a newer version of the recovery, and the failsafe installer. If you do not, you need to go to the custom recovery threads as there are multiple, and get any type of custom recovery installed. Then from there, install the newer custom recovery from the failsafe thread, then the failsafe itself from within the new custom recovery, then from there you can install cm11 using the cm11 thread following the instructions.
quepaso said:
Its hard to lay it out, you need to go to the threads where the info is already layed out.
Do you already have a custom recovery installed like clockwork? Great, then go to the failsafe thread to get a newer version of the recovery, and the failsafe installer. If you do not, you need to go to the custom recovery threads as there are multiple, and get any type of custom recovery installed. Then from there, install the newer custom recovery from the failsafe thread, then the failsafe itself from within the new custom recovery, then from there you can install cm11 using the cm11 thread following the instructions.
Click to expand...
Click to collapse
Just realized cwm is removed,can't install using oneclickrecovery tool either fails says cannot find img etcetc,yet its all there no problems adb is fine and works.Fastboot driver i can't get running although listed yellow exclamation,any ideas?
Fixed it managed to get fastboot going downloaded the required missing dll files and win_usb.inf set up and used ouyatoolbox 1.0.0.0 to rewrite recovery,found i can no longer add the newer 6.0.4.8 recovery zip in update from zip in 6.0.3.2 recovery though? Used to be able to do that. Any way tmore to the point is can someone tell me the step by step process to add cm11 firmware so i don't have to read a load of [email protected] that doesn't end up giving less than nothing in terms of having a clue how,someone in the thread writes about erasing stuff and what oreder but that doesn't tell you how to install or what erase process is or anything detailed and the net has exactly the same misguided tutorials on how to do it.Tellinng a newbie to erase stuff means they will erase all the wrong stuff in all fairness it's good to have a slightly better idea by reading that but it doesn't go in depth or step by step.
All i have found is sites pointing back to the xda pages that do not explain it,it's like your expected to know everything before you have been taught and fill in the gaps off the top of your head.
quepaso said:
This is the order you need to go:
Upgrade to newest clockwork mod from milaq in your recovery.
Then install the failsafe bootloader.
Then install cm11 from the new recovery, along with gapps he posted in the same thread Make sure to wipe all the stock stuff.
Thats it.
Click to expand...
Click to collapse
Exactly what he said, I just did these same steps on a 3rd new ouya yesterday and it went off without a hitch. The cm11 thread is long but honestly all the information you need is in the first few posts. If you were able to connect the ouya to USB and run oneclickroot then you're ready to get started.
Q&A for [RECOVERY][nozomi] TWRP 2.8.5.0 touch recovery [2015-02-12]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [RECOVERY][nozomi] TWRP 2.8.5.0 touch recovery [2015-02-12]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
locked bootloader
m1st3r1 said:
for cwm, there is cwm (and twrp also) for locked bootloader, but it cant flash any kernel (due to locked bootloader). in summary you stuck with stock kernel (that can only be flashed with flashtool or similar tools (if any ) with locked bootloader.
Click to expand...
Click to collapse
Sorry, I'm a bit beginner...
Does this mean that
1. if I use the procedure on page http://teamw.in/project/twrp2/144 in section Download - Stock Kernel:
2. then I can install any ROMs? For example this one? http://forum.xda-developers.com/xperia-s/s-development/rom-naosprom-xperia-s-t2958516
?
Mickey8881 said:
Sorry, I'm a bit beginner...
Does this mean that
1. if I use the procedure on page http://teamw.in/project/twrp2/144 in section Download - Stock Kernel:
2. then I can install any ROMs? For example this one? http://forum.xda-developers.com/xperia-s/s-development/rom-naosprom-xperia-s-t2958516
?
Click to expand...
Click to collapse
Flashing TWRP would require unlocked bootloader. First unlock Your bootloader, then follow the procedure from here.
From Your other post, it turns out You cannot unlock bootloader, so You can flash only sock based ROM's which work on Stock kernel.
Why is there no version 2.8.6.0 for Xperia S?
Hello guys,
I'm just download and install TWRP manager from google play and i'm trying to install the recovery. I'm choosing device name as LT26i but no recovery file is detected.
If i choose device name as "nozomi" i can find everything but my original device name is LT26i.
What to do? Are you suggest to try with nozomi and install the recovery?
Captainlag said:
Hello guys,
I'm just download and install TWRP manager from google play and i'm trying to install the recovery. I'm choosing device name as LT26i but no recovery file is detected.
If i choose device name as "nozomi" i can find everything but my original device name is LT26i.
What to do? Are you suggest to try with nozomi and install the recovery?
Click to expand...
Click to collapse
Nozomi is the code name for LT26i/LT26ii, so You can use it with no problems.
Unable to recovery
I can't flash any recovery file !!!
While I'm trying to install it returns this:
Something is wrong
------------------------
Flashing recovery was
unsuccessful.Either you already
have this recovery installed or
another error has occured.Would
you like to attempt rebooting to
recovery now?
NO YES
Captainlag said:
I can't flash any recovery file !!!
While I'm trying to install it returns this:
Something is wrong
------------------------
Flashing recovery was
unsuccessful.Either you already
have this recovery installed or
another error has occured.Would
you like to attempt rebooting to
recovery now?
NO YES
Click to expand...
Click to collapse
Which method are You following? Try the method from here.
Thank you for your help Mirhawk, but it doesn't work
Captainlag said:
Thank you for your help Mirhawk, but it doesn't work
Click to expand...
Click to collapse
What error are You getting?
Mirhawk said:
What error are You getting?
Click to expand...
Click to collapse
There is no error but I'm trying to reboot in recovery mode and it's immpossible
Captainlag said:
There is no error but I'm trying to reboot in recovery mode and it's immpossible
Click to expand...
Click to collapse
Hope You are pressing volume up button 2-3 times when Sony appears while booting the phone. Also, what ROM are You on?
Mirhawk said:
Hope You are pressing volume up button 2-3 times when Sony appears while booting the phone. Also, what ROM are You on?
Click to expand...
Click to collapse
Of course I'm pressing volume up button 2-3 times ....
My phone is on 6.2.B.1.96 stock with unlocked bootloader
Captainlag said:
Of course I'm pressing volume up button 2-3 times ....
My phone is on 6.2.B.1.96 stock with unlocked bootloader
Click to expand...
Click to collapse
I just wanted to clarify the first point since I have come across some people who didn't follow correct procedure. Glad You are doing it properly.
Ah yes, that is the problem. This method doesn't work on stock firmwares. Use the method from here to get recovery.
Mirhawk said:
I just wanted to clarify the first point since I have come across some people who didn't follow correct procedure. Glad You are doing it properly.
Ah yes, that is the problem. This method doesn't work on stock firmwares. Use the method from here to get recovery.
Click to expand...
Click to collapse
I suppose that i have to follow "method 2", right?
And what to do with the .zip file?
Captainlag said:
I suppose that i have to follow "method 2", right?
And what to do with the .zip file?
Click to expand...
Click to collapse
Method 1. You need recovery for method 2. If You have unlocked bootloader, You can simply flash the DoomKernel too. You can find it here. Use the blue "Download Now" button, and the file has .elf extension. You can flash it via flashtool, it consists of CWM and TWRP and works with stock ROM.
@Mirhawk: Many many thanks !!! :victory:
Finally , I have recovery with Doomkernel.
Thanks a lot and keep moding
I think I messed up my S
Hi
Trying to root my S and install nAOSProm I followed the instructions in the main thread. I successfully unlocked the bootloader and got the device rooted (SuperSU installed and updated in play store), but when attempting to use the TWRP manager to install TWRP I just got an error message that it wasn't successful. I then did this as I read earlier in this thread: fastboot flash boot 2.8.4.1.img. When I started the phone, it immediately boots into the TWRP but I can't get anywhere from there. Impossible to continue to the OS. When I connect it to the computer I just get an exclamation point in the device manager and I can't seem to find the correct drivers (I've installed the FlashTool Xperia Driver Pack). The phone worked perfectly in windows in both normal mode and fastboot previously. Since the phone doesn't have an external memory card, and since I can't transfer any files to it from Windows, I'm stuck in TWRP.
Is it bricked or can I get out of here?
nielsen81 said:
Hi
Trying to root my S and install nAOSProm I followed the instructions in the main thread. I successfully unlocked the bootloader and got the device rooted (SuperSU installed and updated in play store), but when attempting to use the TWRP manager to install TWRP I just got an error message that it wasn't successful. I then did this as I read earlier in this thread: fastboot flash boot 2.8.4.1.img. When I started the phone, it immediately boots into the TWRP but I can't get anywhere from there. Impossible to continue to the OS. When I connect it to the computer I just get an exclamation point in the device manager and I can't seem to find the correct drivers (I've installed the FlashTool Xperia Driver Pack). The phone worked perfectly in windows in both normal mode and fastboot previously. Since the phone doesn't have an external memory card, and since I can't transfer any files to it from Windows, I'm stuck in TWRP.
Is it bricked or can I get out of here?
Click to expand...
Click to collapse
Flash stock firmware ftf using flash mode in flashtool and then follow the instructions from here.
Or else:
Boot Your phone into recovery. Connect it to PC. Right click on the device in Device Manager, select update drivers, "browse my computer", then "let me pick from list" then select the driver similar to "Sony a0109 ADB drivers" (number may vary). Then You will be able connect to phone via adb. Then use following command to push the ROM and gapps to the phone internal memory:
Code:
adb push ROM.zip /sdcard/
adb push gapps.zip /sdcard/
This will copy the the ROM and gapps to phone which You can flash via recovery easily then.
worked perfectly! thanks for your time and help, much appreciated!