Hi, first of all, my English is bad and i'm a noob at installing custom roms
My HOX+ is rooted and i have the TWRP Recovery installed.
So, i downloaded the newest CM11 Nightly for my device (enrc2b) from the Cyanogenmod site.
When i try to flash it with TWRP it says:
Skipping MD5 check: no MD5 file found
Can't install this package on top of incompatible data. Please try another package or run a factory reset
E:Error executing updater binary in zip ' /sdcard/cm-11-20140902-NIGHTLY-enrc2b.zip
Error flashing zip ' /sdcard/cm-11-20140902-NIGHTLY-enrc2b.zip
I also downloaded a Snapshot version of CM11
It says:
Skipping MD5 check: no MD5 file found
set_metadata_recursive: some changes failed
E:Error executing updater binary in zip ' /sdcard/cm-11-20140308-SNAPSHOT-M4-enrc2b.zip
Error flashing zip ' /sdcard/cm-11-20140308-SNAPSHOT-M4-enrc2b.zip
So finally i downloaded the CM10.2.1 Version
I wiped all cache and data and did a factory reset.
After flashing the .zip and rebooting the phone, but i got stuck in a boot loop (i think) because i waited like 20 minutes but the boot animation didn't change (blue guy with the arrow). Did i do something wrong
I just restored my phone to the backup i made (stock rom)
If you need any information about my phone or something just say it.
I also heard about using CWM instead of TWRP but i don't know how to change it.
PLZ HELP :crying:
CWM recovery
Install this recovery for installing CM.
And don't forget to redo your backup after installing the new recovery before installing CM.
[email protected] said:
Install this recovery for installing CM.
And don't forget to redo your backup after installing the new recovery before installing CM.
Click to expand...
Click to collapse
Thx, I will try it
Sent from my HTC One X+ using XDA Free mobile app
I'm working with a Mac so it might take a while before i understand everything but i'll let you know if it worked.
So yesterday i installed the CWM and flashed Cyanogenmod11 Nightlies at 00:10. I got the boot screen with the guy and the arrow spinning, but when i wake up at 7:00 it was still in the Cyanogenmod boot screen wit the arrow (the arrow was lagging).
So i tried flashing the Snapshot version and it also didnt pass the screen with the arrow (lagging)
After that i flashed the CM10.2 and the arrow wasnt lagging anymore but it didnt pass the screen with the arrow
Every time before i installed another version i did a Factory reset in CWM
So am i doing something wrong plz help?
Sent from my HTC One X+ using XDA Free mobile app
Anthony26 said:
So yesterday i installed the CWM and flashed Cyanogenmod11 Nightlies at 00:10. I got the boot screen with the guy and the arrow spinning, but when i wake up at 7:00 it was still in the Cyanogenmod boot screen wit the arrow (the arrow was lagging).
So i tried flashing the Snapshot version and it also didnt pass the screen with the arrow (lagging)
After that i flashed the CM10.2 and the arrow wasnt lagging anymore but it didnt pass the screen with the arrow
Every time before i installed another version i did a Factory reset in CWM
So am i doing something wrong plz help?
Sent from my HTC One X+ using XDA Free mobile app
Click to expand...
Click to collapse
did you flash the boot.img in fastboot before installing the rom?
reaper90 said:
did you flash the boot.img in fastboot before installing the rom?
Click to expand...
Click to collapse
Do you mean with "boot.img" the recovery-clockwork-touch-6.0.4.8-enrc2b.img
This is all i did (i dunno of the screenshot will display i uploaded it as attachment)
I've flashed the recovery.img, thats also the only thing i downloaded on the CWM site.
I also downloaded the Cyanogenmod rom on the CyanogenMod Download site or do i have to download it from the CWM enrc2b Roms?
Edit: I've found out that the boot.img is needed for the device to boot and that i can flash it in recovery.
But is there a special HOX+ boot.img or a Cyanogenmod boot.img or whatever i need? And where can i find it
Anthony26 said:
Do you mean with "boot.img" the recovery-clockwork-touch-6.0.4.8-enrc2b.img
This is all i did (i dunno of the screenshot will display i uploaded it as attachment)
I've flashed the recovery.img, thats also the only thing i downloaded on the CWM site.
I also downloaded the Cyanogenmod rom on the CyanogenMod Download site or do i have to download it from the CWM enrc2b Roms?
Edit: I've found out that the boot.img is needed for the device to boot and that i can flash it in recovery.
But is there a special HOX+ boot.img or a Cyanogenmod boot.img or whatever i need? And where can i find it
Click to expand...
Click to collapse
you can find it inside the rom zip file, just extract it into your adb/fastboot folder and flash it (in fastboot mode) using "fastboot flash boot boot.img". also i recommend (maybe not necessary) using "fastboot erase cache" before and after flashing boot.img.
Also you may need to reflash rom in recovery after flashing boot.img.
reaper90 said:
you can find it inside the rom zip file, just extract it into your adb/fastboot folder and flash it (in fastboot mode) using "fastboot flash boot boot.img". also i recommend (maybe not necessary) using "fastboot erase cache" before and after flashing boot.img.
Also you may need to reflash rom in recovery after flashing boot.img.
Click to expand...
Click to collapse
Thx,
I forgot to unzip the file :silly:
I'll try it and let you know of it worked
reaper90 said:
you can find it inside the rom zip file, just extract it into your adb/fastboot folder and flash it (in fastboot mode) using "fastboot flash boot boot.img". also i recommend (maybe not necessary) using "fastboot erase cache" before and after flashing boot.img.
Also you may need to reflash rom in recovery after flashing boot.img.
Click to expand...
Click to collapse
Alright i did what u said and i have 1 more question;
If i want to go back to the stock rom, do i need to flash a "stock" boot.img?
Edit: Cyanogenmod is working, i only need to install the Google apps (i think).
Stock boot image
You can flash the Nik3r version to come back to the stock boot image.
And you need to flash the GAPPS in recovery for the Google apps
Anthony26 said:
Alright i did what u said and i have 1 more question;
If i want to go back to the stock rom, do i need to flash a "stock" boot.img?
Edit: Cyanogenmod is working, i only need to install the Google apps (i think).
Click to expand...
Click to collapse
If you want to go back to stock completely (including relocked bootloader) you will need everything completely stock and matching your phones CID. Of course you will need to flash the corresponding boot.img for every rom. But as far as i know/tried, nik3rs oxp_kk kernel works for all 4.4 roms and the other version works for all Sense5 based custom roms and maybe stock rom (if you don't need relocked bootloader).
[email protected] said:
You can flash the Nik3r version to come back to the stock boot image.
And you need to flash the GAPPS in recovery for the Google apps
Click to expand...
Click to collapse
reaper90 said:
If you want to go back to stock completely (including relocked bootloader) you will need everything completely stock and matching your phones CID. Of course you will need to flash the corresponding boot.img for every rom. But as far as i know/tried, nik3rs oxp_kk kernel works for all 4.4 roms and the other version works for all Sense5 based custom roms and maybe stock rom (if you don't need relocked bootloader).
Click to expand...
Click to collapse
Thx, i have installed the Gapps and it's working good.
The only thing i notice is the fast battery drain, is it possible to underclock some thing so the battery last longer, and which apps are good for that?
And if i want to go back to the stock rom, i just have to go back to my "stock rom backup" in recovery and flash nik3rs oxp_kk kernel?
Anthony26 said:
Thx, i have installed the Gapps and it's working good.
The only thing i notice is the fast battery drain, is it possible to underclock some thing so the battery last longer, and which apps are good for that?
And if i want to go back to the stock rom, i just have to go back to my "stock rom backup" in recovery and flash nik3rs oxp_kk kernel?
Click to expand...
Click to collapse
no, oxp_kk is just for 4.4 (kitkat) AOSP like roms. there's another non- kk version which works with 4.2.2/sense5 roms, but i don't know about stock roms. There's also a fallback kernel version which should work with all stock and custom 4.2.2/Sense 5 roms.
Related
I bought this 3D used but like new and wanted to flash it to Boost so I was doing some preliminary pre-flash things like rooting and loading a custom recovery and rom. I used the HTC unlock method for the bootloader and flashed Eternity and it stuck at Beats screen (boot animation). I downloaded a different rom to see if it was the rom but that one froze at the animation screen as well. I attempted to do an RUU stock reset on my PC from bootloader but it returned an error saying update failed. I'm basically locked out of this phone. I read everything it said about flashing custom kernels and how you are supposed to flash them from bootloader. I know Eternity has a stock kernel don't know about the other one. My last resort is to download a zip of a stock rom and flash that from recovery. If it freezes on me I'm not sure what I'll do next. Any help is appreciated...
xlxcrossing said:
I bought this 3D used but like new and wanted to flash it to Boost so I was doing some preliminary pre-flash things like rooting and loading a custom recovery and rom. I used the HTC unlock method for the bootloader and flashed Eternity and it stuck at Beats screen (boot animation). I downloaded a different rom to see if it was the rom but that one froze at the animation screen as well. I attempted to do an RUU stock reset on my PC from bootloader but it returned an error saying update failed. I'm basically locked out of this phone. I read everything it said about flashing custom kernels and how you are supposed to flash them from bootloader. I know Eternity has a stock kernel don't know about the other one. My last resort is to download a zip of a stock rom and flash that from recovery. If it freezes on me I'm not sure what I'll do next. Any help is appreciated...
Click to expand...
Click to collapse
Did you follow the root instructions all the way through to install Superuser and the recovery? If so, did you boot into fastboot, connect usb, then do the fastboot boot recovery.img before flashing the rom?
Sent from my PG86100 using XDA App
JayDaKissEP said:
Did you follow the root instructions all the way through to install Superuser and the recovery? If so, did you boot into fastboot, connect usb, then do the fastboot boot recovery.img before flashing the rom?
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
I did not use that method to flash, no. I'm assuming you mean from my PC execute the command. I did follow the instructions to install TWRP which is a custom recovery and I flashed a ZIP from TWRP for Superuser and checked it to be working which it was. (I tested Root Explorer and Terminal Emulator for root)
I was operating off the assumption that custom roms with a STOCK kernel could be flashed by booting into recovery. I went to bootloader then recovery then flashed the rom. Obviously I did something wrong since both roms wouldn't load. I will use your method of PC commands from fastboot into recovery and see where that gets me....pease let me know if this is correct or anything else I need to do....thanks a bunch.
UPDATE : I tried the method of loading recovery from fastboot usb - it worked thank you. The rom loaded. I'm wondering why since it was a custom rom with a stock kernel why I couldn't flash it from recovery.
xlxcrossing said:
UPDATE : I tried the method of loading recovery from fastboot usb - it worked thank you. The rom loaded. I'm wondering why since it was a custom rom with a stock kernel why I couldn't flash it from recovery.
Click to expand...
Click to collapse
While the kernel is stock, Virus has a bunch of binaries and such that will be mismatched without flashing the boot.img properly ... So while some of his builds say "stock" not always completely stock.
ifly4vamerica said:
While the kernel is stock, Virus has a bunch of binaries and such that will be mismatched without flashing the boot.img properly ... So while some of his builds say "stock" not always completely stock.
Click to expand...
Click to collapse
cool cool thanks for the info. So I need to load the recovery.img file from usb fastboot EVERY time I want to flash a rom? Any way to eliminate this hassle....I just assume flash less often if not...thanks
xlxcrossing said:
cool cool thanks for the info. So I need to load the recovery.img file from usb fastboot EVERY time I want to flash a rom? Any way to eliminate this hassle....I just assume flash less often if not...thanks
Click to expand...
Click to collapse
With hboot 1.5, the ONLY way to flash a ROM correctly is with fastboot>recovery.
Twolazyg said:
With hboot 1.5, the ONLY way to flash a ROM correctly is with fastboot>recovery.
Click to expand...
Click to collapse
Not true. You can flash a ROM but if you don't use fastboot it won't touch the kernel. I always change roms with the stock kernel. He must have done something wrong
Sent from my PG86100 using XDA App
JayDaKissEP said:
Not true. You can flash a ROM but if you don't use fastboot it won't touch the kernel. I always change roms with the stock kernel. He must have done something wrong
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
If the kernel is pure stock with no added binaries or stuff it will work. Virus puts lots of little tweaks in that require it. Now if you can load a completely stock kernel and ramdisk then load Eternity (of course some eternity builds did have a completely stock kernel) then you may be onto something.
As far as flashing with hboot 1.50 easiest way to do that without the computer is with joeykrm's flash image gui. I don't have 1.50 but I have used his gui to do partial updates on svn builds in tandem with adb sync and it works great. His post with the apk is in development section. just read the instructions and flash away.
ifly4vamerica said:
If the kernel is pure stock with no added binaries or stuff it will work. Virus puts lots of little tweaks in that require it. Now if you can load a completely stock kernel and ramdisk then load Eternity (of course some eternity builds did have a completely stock kernel) then you may be onto something.
As far as flashing with hboot 1.50 easiest way to do that without the computer is with joeykrm's flash image gui. I don't have 1.50 but I have used his gui to do partial updates on svn builds in tandem with adb sync and it works great. His post with the apk is in development section. just read the instructions and flash away.
Click to expand...
Click to collapse
Yeah I read all about it I'm still stuck on why if I had a stock kernel installed with a stock rom and I do a custom rom flash and as stated it doesn't touch the kernel why the rom wouldn't simply run off the stock kernel - that's what confuses me. I understand the issue of the kernel not being flashed which is obviously what happened with me. I just don't really know where I stand with what kernel to ALWAYS have loaded since if that's the thing with the issue I would want to for purposes of not doing tons of work stay away from flashing kernels and stick to flashing roms when I want to change it up. But if the STOCK kernel won't load with a custom rom which technically it should I guess I'll just have to flash a universal custom kernel and assume any rom I flash will simply use that kernel. Kind of a nightmare compared to my 4G....welcome to the world of the 3D I guess.
I guess going into recovery from hboot with the volume and power buttons wouldn't count - I have to stick with PC commands?
So I thought of installing a new ROM to my XZU today. First I rooted my device using the following guide : https://www.youtube.com/watch?v=BkQT3nX5yWM. (As I had updated my device to Android 4.4.4 and had .108 FW). I successfully rooted the phone and took a TA Backup. Afterwards, I went on to unlock the bootloader and unlocked it successfully as well. As I wanted to install the ParanoidAndroid 4+ ROM, I downloaded it and got the boot.img from the ZIP file, and flashed it using the Flashtool. However, afterwards, when I tried to go the recovery mode, it is stuck on the Sony Logo, and doesn't blink the notification LED in order to do so.
Did I do anything wrong? I am quite a noob when it comes to XZU related stuff..so I would really appreciate if someone can help me out..
Thanks in advance!
EDIT: (Thought of editing this thread rather than deleting it so that it could be an help for someone who faces a similar problem) I was able to make my device up and running again by flashing the FTF found in this thread: http://forum.xda-developers.com/showthread.php?t=2798690.
Now, I have again come to the status where I have installed a recovery successfully and unlocked my bootloader, and I want to install PA 4+ to my device. Would really appreciate if anyone can guide me on how to do this
It doesn't sound like you did any thing wrong.
Do you have [NUT]'s recovery installed now?
Do a nandroid backup if you do, saves the whole flashing a FTF step if something goes wrong
Did you get the correct PA? what date?
PA should install fron [NUT]'s recovery or you could hotboot the boot.img with flashtool (this wont over write you current kernel) this will let you test if it does work
blueether said:
It doesn't sound like you did any thing wrong.
Do you have [NUT]'s recovery installed now?
Do a nandroid backup if you do, saves the whole flashing a FTF step if something goes wrong
Did you get the correct PA? what date?
PA should install fron [NUT]'s recovery or you could hotboot the boot.img with flashtool (this wont over write you current kernel) this will let you test if it does work
Click to expand...
Click to collapse
Thank you. Yes, I read quite a lot yesterday and found out that I have followed the steps properly. So I am wondering if it has got anything to do with the boot.img from the PA ROM?
And yes I did a nandroid backup previously as well, however, I was not aware of how to restore it because I couldn't access the recovery mode. Can I do the restore using the FlashTool? or some other tool in such a scenario?
I downloaded "pa_togari-4.5-BETA1-20140805.zip" available in this link: http://aospal.hostingsharedbox.com/aospal/roms/togari/ . Should I try the last stable release rather than the beta one?
I am sorry for this noobish question, but what exactly is the purpose of "boot.img"? Is it the kernel of the new ROM that I am going to install? or is it something else? I kinda think that the problem might have been with the way I flashed the boot.img previously. I used the option "SELECT SYSTEM TO FLASH" under the fastboot of FlashTool in order to do so. Is it wrong? Should I use the "SELECT KERNEL TO FLASH"?
Thank you again
EDIT: I used the "SELECT KERNEL TO FLASH" option in the Flashtool, to flash the boot.img and I was able to flash the PA 4+ successfully! ..Thank you!
Prabash said:
EDIT: I used the "SELECT KERNEL TO FLASH" option in the Flashtool, to flash the boot.img and I was able to flash the PA 4+ successfully! ..Thank you!
Click to expand...
Click to collapse
Good to hear you got it sorted, but I'll run through what you did wrong...
Thank you. Yes, I read quite a lot yesterday and found out that I have followed the steps properly. So I am wondering if it has got anything to do with the boot.img from the PA ROM?
Click to expand...
Click to collapse
So you now know it wasn't the boot.img :laugh:
And yes I did a nandroid backup previously as well, however, I was not aware of how to restore it because I couldn't access the recovery mode. Can I do the restore using the FlashTool? or some other tool in such a scenario?
Click to expand...
Click to collapse
Normally the way to recover would be to flash a boot.img that works and then enter recovery rand restore, easy when you flash the boot.img correctly
I am sorry for this noobish question, but what exactly is the purpose of "boot.img"? Is it the kernel of the new ROM that I am going to install? or is it something else?
Click to expand...
Click to collapse
The boot image is the kernel and recovery backed into one (it's a Sony thing ) and it belongs on the /boot partition
I kinda think that the problem might have been with the way I flashed the boot.img previously. I used the option "SELECT SYSTEM TO FLASH" under the fastboot of FlashTool in order to do so. Is it wrong? Should I use the "SELECT KERNEL TO FLASH"?
Click to expand...
Click to collapse
I think you have figured that one out now :cyclops:. So what you did was write the kernel and recovery to the /system partition, not to where it belongs ie /boot
You can also use the "select kernel to boot (hotboot)" (or what ever words it uses) to boot a kernel/recovery and not change the one on the /boot partition - can be handy at times
I hope that helps you understand some bits about your new Sony ZU
Yep! thanks a lot for your help! Really appreciate it! :victory:
Device information:
Xperia Z Ultra
Cyanogenmod 11 M12 (togari from offical cm side)
Smartphone is encrypted
Bootloader unlocked
Nothing else changed (kernel etc.)
Hi,
since a few hours i try to get TWRP 2.8.5.0 to work.
After installing it according the offical description and rebooting into the recovery, my z ultra only shows the Sony logo and doesn´t do anything (it took me some time to figure out how to turn it off... Power + vol up).
To get the cm cwm back, i´ve used fastboot to flash boot.img.
The integrated cwm can´t mount the encrypted data partition and is useless for me. To avoid problems on my heavily used z ultra, i tried TWRP first on my old (encrypted) Nexus 7 (2012) tablet, works like a charm and most important, it doesn´t have any problems with encrypted devices.
The installation on the Nexus 7 was not really mentionable, fastboot flash recovery file.img, that´s it.
The Z Ultra is different, the teamwin page says :
Download the above file. Copy the file to /sdcard/fotakernel.img and run the following commands using terminal emulator or in adb shell:
su
dd if=/sdcard/fotakernel.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
It won´t work, the above mentioned problem is the result.
Maybe i need a custom kernel, any suggestions?
Thanks for your help.
CM kernel probably doesnt allow to flash other kernel than it has (cwm). Flash great devs kernel and than twrp. I have it (at least multi rom 2.8.4 one) and it works.
However after screen off it reboots and i dont know what cause it
Thanks for your answear, i try it next weekend.
Code:
Rom: Resurrection Remix® Lollipop v5.3.6 - Togari
Kernel: from rom
Recovery: Dunno where it came from? Perhaps when flashing Candy5 Beta.
Im kind off in the same position, recovery says
Code:
E: Cannot load volume /misc
Finding update package...
Opening update package...
Installing update package...
Package is for device: ...[B][I]bla bla bla you get the thing[/I][/B]
E: failed to install /sideload/package.zip
E: Please take note of ..[B][I]bla bla bla[/I][/B]
Installation aborted.
E: Cannot load volume /misc!
When trying to flash any zip file. When the flash starts I see something like "verification failed" flashing by really quick .....I guess the verify is active which is causing this issue?
BUT this damn recovery has no damn setting to change that! Probably possible to modify some config.txt manually.
Is it possible to change recovery somehow from CM recovery?
I tried by flashing great devs with fastboot. Then it says finished but the same recovery is still present...
Sorry for ranting a bit ..I'm in the middle of some other projects going on with BSD but this one is driving me nuts :silly: I just want to flash TWRP on my device It should not be this difficult
My advice for you is to flash boot.img from resurrection remix - its great devs kernel v2 with twrp - or zombie kernel for 5.0 which has built in twrp.
Both can be flashed using fastboot, so u dont need working recovery for it and they both should work with all 5.0 roms except gpe one.
Im not sure what versions of recovery they have built in, but after that u can flash multirom zip, which has 2.8.4.x one (with mutirom support ofc,but its just addition for "stock" functions it has). I dont think u can use official twrp 2.8.5.0 with nonstock kernel as i tried to flash it to recovery partition and fotakernel and always it doesnt boot (recovery, rom and kernel worked fine, just after pressing vol+, vol- or power when purple light comes up, it changes to yellow and stay like this till i forced reboot).
I tried it with Great Devs KK (v1 + AICP 7.0l) and LP (v2 + RR or AICP 8.0 unofficial build), built in kernel in AICP 8.0 unofficial and Validus.
MultiROM twrp works fine with GD v1 and v2
ch3mn3y said:
My advice for you is to flash boot.img from resurrection remix - its great devs kernel v2 with twrp - or zombie kernel for 5.0 which has built in twrp.
Both can be flashed using fastboot, so u dont need working recovery for it and they both should work with all 5.0 roms except gpe one.
Im not sure what versions of recovery they have built in, but after that u can flash multirom zip, which has 2.8.4.x one (with mutirom support ofc,but its just addition for "stock" functions it has). I dont think u can use official twrp 2.8.5.0 with nonstock kernel as i tried to flash it to recovery partition and fotakernel and always it doesnt boot (recovery, rom and kernel worked fine, just after pressing vol+, vol- or power when purple light comes up, it changes to yellow and stay like this till i forced reboot).
I tried it with Great Devs KK (v1 + AICP 7.0l) and LP (v2 + RR or AICP 8.0 unofficial build), built in kernel in AICP 8.0 unofficial and Validus.
MultiROM twrp works fine with GD v1 and v2
Click to expand...
Click to collapse
....well im stuck. I have tried everything. Even hotbooting. That damn CM recovery is there no matter what!
I'm gonna give it a try tomorrow and start on zero. Either flash a stock rom with flashtool or scrubber port which is not based on cm.
I'll report later with some results
Mybe try to:
- dl your rom and zombie or gd
- open ur roms zip with ie 7zip
- delete boot.img
- unpack kernels zip and move boot.img to roms zip
- copy new zip to device
- flash stock
- flash kernel (zombie or gd)
- using built in recovery (should be twrp( flash roms zip
As there will be built in kernel with twrp it should stay after reboot.
If not do it again but before reboot in the and flash multirom zip
Sent using C6833 - AICP/GreatDevs
Solved the issue.
First I Downloaded
STOCK ROM] [FTF] Xperia Z Ultra 6833 14.4.A.0.118 "SRF FR".
GoogleDrive: Download FTF
Thanks to @dandyqb
Click to expand...
Click to collapse
And Flashtool 9.18.5
But I got stuck with Flashtool prompting me to move content from C:\flashtool\firmwares C:\users\admin\.flashtool/firmwares (??)
Abandoned flashtool and downloaded Flashtool 9.16.1 instead. But this time I hit another issue.
Code:
Flashing system bla bla bla.
Abort..
Error..
Device connected in Flashmode.
Grrrrr..!!
Abandoned the FTF file and downloaded
STOCK ROM] [FTF] Xperia Z Ultra 6833 14.4.A.0.118 "VodaFone UK".
mediafire: Download FTF
Thanks to @Feodorus 4PDA
Click to expand...
Click to collapse
This time it worked out. Flashtool read the FTF and pushed it to the device as it should.
Booted device and transfered files to my device
Code:
cm-Resurrection_Remix_LP_v5.3.6-20150221-togari.zip
gapps-lp-20141109-signed.zip
MultiROM-v30x-180115-UNOFFICIAL-togari.zip
I did the rest manually. Downloaded and opened [email protected]_LRX21P.S3.4201_by_Scrubber.
Took out the file "For_ALL_ZU_5.0_Scrubb_GPE_kernel_initD.img"
Renamed file and flashed it with
Code:
Fastboot flash boot boot.img
Booted into recovery and flashed
Code:
cm-Resurrection_Remix_LP_v5.3.6-20150221-togari.zip
gapps-lp-20141109-signed.zip
MultiROM-v30x-180115-UNOFFICIAL-togari.zip
Turned off device. Booted into Fastboot mode
Renamed "TWRP_multirom-togari_20150201-00.img" to "recovery"
Flashed file with
Code:
Fastboot flash recovery recovery.img
Fastboot reboot
Wooh.. And I reached a very unfamiliar place named Multirom upon boot saying Auto-boot! :good::laugh:
Glad u made it. It strange that u need steps with gpe port, but maybe some devices are different
Multirom lets u boot more than one rom. Its like grub on pc, so its good thing, but take 5-6 secs of additional booting time
And flash older version of flashtool (eg. 0.9.18.2), if u want to keepfirmwares in flashtool/firmwares folder. Devs change somethin and people like me with small system partition or ssd drive, which has limited space will have problems if it keeps that way (or well need to stay with older verions)
Sent using C6833 - AICP/GreatDevs
ch3mn3y said:
Glad u made it. It strange that u need steps with gpe port, but maybe some devices are different
Multirom lets u boot more than one rom. Its like grub on pc, so its good thing, but take 5-6 secs of additional booting time
And flash older version of flashtool (eg. 0.9.18.2), if u want to keepfirmwares in flashtool/firmwares folder. Devs change somethin and people like me with small system partition or ssd drive, which has limited space will have problems if it keeps that way (or well need to stay with older verions)
Sent using C6833 - AICP/GreatDevs
Click to expand...
Click to collapse
I didn't really need scrubbers kernel. I just used it to flash a recovery on to my device as I came from stock rom after flashing the FTF.
Just kind of a "safety first" step instead of jumping right onto flashing the multirom .img file and not knowing if its gonna boot or not. :silly:
Scrubbers gpe port was just the first rom that popped up in my head so its why I used it.
You can use Rashr to replace recovery in current kernel image on the go. I use it all the time to get TWRP - works perfectly. Can backup kernel image before modifying.
You can flash Philz, TWRP (any version, incl. 2.8.5.0) or any other recovery image from sdcard with it on top of AOSP kernel.
https://play.google.com/store/apps/details?id=de.mkrtchyan.recoverytools
What kernel are u using? Im on GreatDevs and after flashing 2.8.5.0 it doesnt boot. I mean its flashed, but after reboot when i press vol+/- like i do with twrp 2.8.4 (multirom one)or before did with cwm it freezes on kernel logo (led color changes from purple to yellow)
Sent using C6833 - AICP/GreatDevs
ch3mn3y said:
What kernel are u using?
Click to expand...
Click to collapse
If this question is for me, I use official CM12.
Its in my forum and tapatalk signatures - Great Devs, KK one.
So maybe its it and cm11 kernel (or only GD) doesnt support 2.8.5+ ??
I can live with 2.8.4 for now (till I move to LP)
B.Maximenko said:
You can use Rashr to replace recovery in current kernel image on the go. I use it all the time to get TWRP - works perfectly. Can backup kernel image before modifying.
You can flash Philz, TWRP (any version, incl. 2.8.5.0) or any other recovery image from sdcard with it on top of AOSP kernel.
https://play.google.com/store/apps/details?id=de.mkrtchyan.recoverytools
Click to expand...
Click to collapse
I have tried this app. And other similar apps I could find on play store. They did not work.
The output in this app showed that it successfully replaced recovery but on reboot CM recovery was still present.
B.Maximenko said:
You can use Rashr to replace recovery in current kernel image on the go. I use it all the time to get TWRP - works perfectly. Can backup kernel image before modifying.
You can flash Philz, TWRP (any version, incl. 2.8.5.0) or any other recovery image from sdcard with it on top of AOSP kernel.
https://play.google.com/store/apps/details?id=de.mkrtchyan.recoverytools
Click to expand...
Click to collapse
the app doesn't work for me either (i'm running slimkat build 9 stock)
i can't get 2.8.5.0 working permanently (at least not after a power down)... it'll work right after a fastboot flash
lame Sony putting kernel and recovery together.... wth... my Note 2 was so much simpler to work with...
anyone got a TWRP theme which is suitable with xperia ultra z?
I accidentally flashed TWRP to the boot instead of recovery. Whenever I turn on the phone it goes straight to TWRP. As it stands the phone is unsuable! AS far I understand it the way to fix this is to flash the phone's original boot.img to the boot. Is this correct? If so my phone is MT2L03 with the 5.1 update. Does anynone know of any link or could anyone PLEASE share their stock boot.img with me. I really need help!
Thank You.
Boot image is part of OS. If you want to install CM12, while you are in twrp, just transfer the cm12 rom and gapp from pc to your sdcard, then flash both. You get complete cm12 with its boot image.
But if you want stock boot image back, you can just flash the stock firmware using the 3 button boot. It is available in the "official stock firmware" section in the INDEX page: http://forum.xda-developers.com/showthread.php?t=3149530
If you have difficulties doing that, let us know. I maybe can find it somewhere, but to be honest, I don't use stock anymore once CM is out.
Thanks. CM12 flash problem
I was able to find a b321 boot.img online so problem solved. The cm 12 flash is not working for me I keep getting an error while flashing TWRP keeps telling me that the cm 12.1mt2 file is specifically for the b322 bootloader but that my bootloader is "unknown" so its unable to flash.
Still haven't figured out what the problem is. I tried to install the specific 2.8.7.0 TWRP for the mt2l03 via the app but it gives me an error. When I try to flash it in recovery it still has no effect on the cm install. Maybe someone would be kind enough to guide me.
fcbfan2k said:
I was able to find a b321 boot.img online so problem solved. The cm 12 flash is not working for me I keep getting an error while flashing TWRP keeps telling me that the cm 12.1mt2 file is specifically for the b322 bootloader but that my bootloader is "unknown" so its unable to flash.
Still haven't figured out what the problem is. I tried to install the specific 2.8.7.0 TWRP for the mt2l03 via the app but it gives me an error. When I try to flash it in recovery it still has no effect on the cm install. Maybe someone would be kind enough to guide me.
Click to expand...
Click to collapse
Try reading the OP for that ROM. It clearly states you have to be in b322.... Reading is key.
Moody66 said:
Try reading the OP for that ROM. It clearly states you have to be in b322.... Reading is key.
Click to expand...
Click to collapse
i do have b322. So the problem is not that. the problem was already there even before i booted with the b321.img. In any case the img is for boot only. It is not the build.
Also twrp, have you install the twrp listed in that same page? other twrp version doesn't work.
Edit, saw you mentioned already that install twrp error using app. So try install the correct twrp in bootloader.
fcbfan2k said:
i do have b322. So the problem is not that. the problem was already there even before i booted with the b321.img. In any case the img is for boot only. It is not the build.
Click to expand...
Click to collapse
If you flashed b321 boot image you are not on b322 boot... And the correct twrp is found in the same OP....
Hi All
I've got a Oneplus X, rooted, unlocked, running TWRP but i accidently wiped System when doing a ROM Flash.
The problem i have now is when i try and flash either 2.1.2 or 2.1.3 i get a flash error saying device unrecognized. ROM for oneplus x device is "."
How the hell do i get round this ? i can't install any ROM's at the moment so i'm left with a phone i can get in to TWRP or Bootloader but can't do anything else with !!
HELP
To flash oxygen agin you have to have stock recovery try flashing stock recovery then flash rom
Sent from my ONE E1003 using Tapatalk
Do you really need stock recovery to flash the Oxygen ROM ??? Where can i grab the latest Stock Recovery and how do i install it, is it flashable ?
If i can use TWRP where can i get the latest supported version of that ?
thesponz said:
Do you really need stock recovery to flash the Oxygen ROM ??? Where can i grab the latest Stock Recovery and how do i install it, is it flashable ?
If i can use TWRP where can i get the latest supported version of that ?
Click to expand...
Click to collapse
Twrp link:-http://forum.xda-developers.com/devdb/project/dl/?id=15364
Rom:- http://ns336247.ip-91-121-110.eu/h2o64/ONEPLUS_OTA/
First download full system dump then otas
And if you cant enable mtp then copy the files to sd card(if you dont have borrow it from somewhere) then flash it
The problem I have now is the phone isn't recognised in fastboot.
If I do adb devices in TWRP is returns the phone ID with phone is not Authorized. Won't allow me to adb sideload either....
any ideas how to force the phone to be authorized ?
ROM link says 404: Website not found
mohammedtabish said:
Twrp link:-http://forum.xda-developers.com/devdb/project/dl/?id=15364
Rom:- http://ns336247.ip-91-121-110.eu/h2o64/ONEPLUS_OTA/
First download full system dump then otas
And if you cant enable mtp then copy the files to sd card(if you dont have borrow it from somewhere) then flash it
Click to expand...
Click to collapse
ROM: Link doesnt work, says ERROR 404: Website not available
tigerkir said:
ROM: Link doesnt work, says ERROR 404: Website not available
Click to expand...
Click to collapse
you can flash it with stock recovery
https://drive.google.com/file/d/0B3AIip-hiOnNb1pBeGNlcUIyYmc/view?pref=2&pli=1
its 2.1.2 full system dump then download the otas through system updates in settings
Here is the last 2.1.3-X full zip
https://www.androidfilehost.com/?fid=24269982087013219
Just flash it via recovery
Sent from my ONE E1003 using Tapatalk
If nothing else works and worse comes to worse. This guide will show you how to make everything stock again. Just e forewarned your data will be erased. so backup in TWRP and then backup that backup on your PC.
http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108