Today i tried to install this crappy Custom Rom http://forum.xda-developers.com/showthread.php?t=1705334&highlight=bootloop Renovate 1.1 i installed 2 other Roms before and all of those was succesfully , then i tested this and i got into a bootloop , so i restored my backup , this bootloops too and the 2 other roms bootloop too , i tried so much things now i can go to bootloader but its Relocked Security Warning what can i do?
go0dlife said:
Today i tried to install this crappy Custom Rom http://forum.xda-developers.com/showthread.php?t=1705334&highlight=bootloop Renovate 1.1 i installed 2 other Roms before and all of those was succesfully , then i tested this and i got into a bootloop , so i restored my backup , this bootloops too and the 2 other roms bootloop too , i tried so much things now i can go to bootloader but its Relocked Security Warning what can i do?
Click to expand...
Click to collapse
Unlock the bootloader, go to adb/fastboot folder and store your ROM's boot.img there. Shift + Right Click within that folder and Open command window (be in fastboot mode on your phone in the meantime) :
fastboot flash boot boot.img
fastboot erase cache
Go to recovery, wipe all except SD (you can if you don't need your files) and flash a fresh ROM. Also, lock the bootloader and never ever flash any custom ROM again if you're going to call it crap whenever you fail.
edit: it isn't that easy to brick the device, and finally, your topic doesn't belong in this subforum.
how to update hboot version? i need 1.31
ok i unlocked now i have hboot 1.12.0000
but i cant install the rom i followed your instruction and get bootloop..
go0dlife said:
Today i tried to install this crappy Custom Rom http://forum.xda-developers.com/showthread.php?t=1705334&highlight=bootloop Renovate 1.1 i installed 2 other Roms before and all of those was succesfully , then i tested this and i got into a bootloop , so i restored my backup , this bootloops too and the 2 other roms bootloop too , i tried so much things now i can go to bootloader but its Relocked Security Warning what can i do?
Click to expand...
Click to collapse
The rom is crap because it didn't work or because you don't have a clue what your doing? It's not nice to say the roms crap when so many people have used without problem and without a doubt the problem will be down to you. People put a lot of time and effort into roms for free so try to be more respectful.
Sent from my Nexus 7 using Tapatalk 2
Agree
As previously said - These guys are all doing soooo much work for us (the community) and it's NOT paid - anyone who makes a ROM, ANYONE - needs to be applauded even for trying, but I'm sure that most ROM chefs test their roms to a point before releasing them and that you've probably missed a step or flashed incompatible zips or something...
Did you extract the boot.img from the roms zip file and "fastboot flash boot boot.img" it? It sounds like you might have been playing with ROMS which all worked on the same kernel and now you've flashed one which uses a different one, resulting in a bootloop like you say - I'm a noob and have done this a few times. Boot into bootloader, fastboot flash your boot.img, then boot into recovery and flash the rom (factory reset / wipe all data / cache / dalvik) and you might be lucky enough to boot into the rom!
These steps MAY not fix your problem if it is something else - but from my experience they are not steps which will brick your device, if you don't think you've flashed the boot.img - then I'd start there.
With our HOX's you ALWAYS need to remember (ALWAYS ALWAYS ALWAYS) to flash (in fastboot mode) your boot.img (which is 99% of the time, included inside the roms ZIP file...
Hope I've helped!
(Hit thanks if I did! )
Before saying those "crappy" words to the rom. Read alot first. All the answers are in the forum. Rom chefs dedicate time to cook a good rom.
Sent from my HTC One X using xda app-developers app
Guys......its not the rom, its not the boot.img.........surprise ! Its his hboot (1.12)
Get that updated otherwise it will never run.
And please loose the attitude towards roms that don't boot. They all boot but check the requirements first
Its your phone/hboot that does not support it
AW: HTC One X brick? Help me
http://m.youtube.com/#/watch?v=wwleOote5M0&desktop_uri=/watch?v=wwleOote5M0&gl=DE
Related
Hi unlocked and rooted OneX with TWRP is it possible to install the latest ? Viper ROM using TWRP or do need to use clockwork if so any walk through showing a new to custom Roms a step by step guide Googled for it and only get reviews of the ROM
Thanks.....
BedrockFred said:
Hi unlocked and rooted OneX with TWRP is it possible to install the latest ? Viper ROM using TWRP or do need to use clockwork if so any walk through showing a new to custom Roms a step by step guide Googled for it and only get reviews of the ROM
Thanks.....
Click to expand...
Click to collapse
It won't make a difference it will be flashable through TWRP.
Just depends what recovery your most comfortable with !
Wilks3y said:
It won't make a difference it will be flashable through TWRP.
Just depends what recovery your most comfortable with !
Click to expand...
Click to collapse
Thanks for that, now is there instructions on how to download and install Viper is it straightforward read on some sites about flashing kernels etc really a bit puzzling to me although I have flashed a ROM on my Nexus 7 tablet it seemed much more straight forward
Sorry for the newbie questions (
BedrockFred said:
Thanks for that, now is there instructions on how to download and install Viper is it straightforward read on some sites about flashing kernels etc really a bit puzzling to me although I have flashed a ROM on my Nexus 7 tablet it seemed much more straight forward
Sorry for the newbie questions (
Click to expand...
Click to collapse
here's the link. you can find instruction there. http://forum.xda-developers.com/showthread.php?t=1745176
robchongke said:
here's the link. you can find instruction there. http://forum.xda-developers.com/showthread.php?t=1745176
Click to expand...
Click to collapse
Thanks for that, little nervous as the last time I installed a custom ROM (other than my nexus 7) I thought I'd bricked my phone took me two days to get it working (HTC Desire)..
So following those instructions will do the job ?
I need to understand the terminology kernels , boot.img , ROMS, RUU but following those instructions and download the ROM extract the boot.img install that on my phone with fast boot on my PC then boot into TWRP and install the ROM and that's it ?
BedrockFred said:
Thanks for that, little nervous as the last time I installed a custom ROM (other than my nexus 7) I thought I'd bricked my phone took me two days to get it working (HTC Desire)..
So following those instructions will do the job ?
I need to understand the terminology kernels , boot.img , ROMS, RUU but following those instructions and download the ROM extract the boot.img install that on my phone with fast boot on my PC then boot into TWRP and install the ROM and that's it ?
Click to expand...
Click to collapse
you need fastboot folders with fastboot files inside. you can find it here in xda. if this is your first time to flash i suggest you watch video tutorials.
robchongke said:
you need fastboot folders with fastboot files inside. you can find it here in xda. if this is your first time to flash i suggest you watch video tutorials.
Click to expand...
Click to collapse
Yes I have fastboot folder and files just downloaded the Viper ROM extracted the boot.img I have connected my phone checked devices in fastboot and the serial number shows so its there
Acording to the Viper instructions I now need to flash the boot.img then fastboot erase cache is that correct
Where are these videos please
BedrockFred said:
Yes I have fastboot folder and files just downloaded the Viper ROM extracted the boot.img I have connected my phone checked devices in fastboot and the serial number shows so its there
Acording to the Viper instructions I now need to flash the boot.img then fastboot erase cache is that correct
Where are these videos please
Click to expand...
Click to collapse
Correct, flash the boot.img with the command fastboot flash boot boot.img
then fastboot erase cache
then boot to recovery and install the rom.zip via recovery.
Thanks so it really is that simple or am I missing something seen lots having problems with boot loops etc is there anything else I need to be aware of
As far as I can see the order and actions I need to do bearing in mind my HTC is already bootloader unlocked and rooted
1Download the ROM copy to phone
2 Extract Boot.IMG from the ROM
3 Boot my phone into boot loader
4 Connect to PC and in fastboot (phone shows fastbootusb) fast boot flash boot boot.img
5 Still in fastboot fastboot erase cache
5 Boot into recovery (connected to PC or not?) Full wipe then install the ROM followed by installing the updates through recovery
Thanks again
BedrockFred said:
Thanks so it really is that simple or am I missing something seen lots having problems with boot loops etc is there anything else I need to be aware of
As far as I can see the order and actions I need to do bearing in mind my HTC is already bootloader unlocked and rooted
1Download the ROM copy to phone
2 Extract Boot.IMG from the ROM
3 Boot my phone into boot loader
4 Connect to PC and in fastboot (phone shows fastbootusb) fast boot flash boot boot.img
5 Still in fastboot fastboot erase cache
5 Boot into recovery (connected to PC or not?) Full wipe then install the ROM followed by installing the updates through recovery
Thanks again
Click to expand...
Click to collapse
1 Download the ROM copy to phone
2 Extract Boot.IMG from the ROM place it inside the fastboot folder
3 Boot my phone into boot loader
4 Connect to PC and in fastboot (phone shows fastbootusb) fastboot flash boot boot.img
5 Still in fastboot fastboot erase cache
6 Boot into recovery (connected to PC or not?) Full wipe then install the ROM followed by installing the updates through recovery. connected or not you can flash the rom. don forget to wipe dalvik cache and wipe cache. you can update your rom OTA or if it doesnt show up you can just download the update ang flash it through recovery. no need to full wipe and flash the boot.img when flashing the update
Thanks for the help guys I'm all done, now on the Viper Rom first impressions its pretty darn good plenty to play around with
The HUB don't seem to do anything when trying to use the various links just get please wait and then a white screen,
Once again big thanks for the help
BedrockFred said:
Thanks for the help guys I'm all done, now on the Viper Rom first impressions its pretty darn good plenty to play around with
The HUB don't seem to do anything when trying to use the various links just get please wait and then a white screen,
Once again big thanks for the help
Click to expand...
Click to collapse
I believe the Venom hub is down at the moment.......
Glad you got it all sorted, it really is painless if you take your time and follow the guides.:good:
craftycarper1 said:
I believe the Venom hub is down at the moment.......
Glad you got it all sorted, it really is painless if you take your time and follow the guides.:good:
Click to expand...
Click to collapse
Certainly is, think all these warnings re briking your phone makes me nervous that and the problems I had on my old Desire took 2 days to get a ROM on that lol
The more I play with Viper the more I like it, its like having a new phone
BedrockFred said:
Thanks for the help guys I'm all done, now on the Viper Rom first impressions its pretty darn good plenty to play around with
The HUB don't seem to do anything when trying to use the various links just get please wait and then a white screen,
Once again big thanks for the help
Click to expand...
Click to collapse
So did you use twrp to flash the ROM or your PC? Is it possible to use twrp?
Dude ....you are bumping a thread from November last year ! What do you expect to hear ! A Rom is always flashed with a custom recovery and the boot.img file with the pc. Always have been like that
Hi!
I installed Miui some months ago, version 2.8.3. The built-in updater says my Miui is up to date but it clearly is'nt. How do I update the best way? i'm not aan experienced developer. What is the step by step "to-do"?
I use the regular One V.
Thanks A lot!
firstly.. there is nothing as regular and irregular one v.. :/
and see in android development section... 3.1.11 is out.. download it and flash via recovery
Sent from my One V
paarthdesai said:
firstly.. there is nothing as regular and irregular one v.. :/
and see in android development section... 3.1.11 is out.. download it and flash via recovery
Sent from my One V
Click to expand...
Click to collapse
Yeah, sorry but not really what I meant by step-by-step. Sorry to bother you but I really don't get this stuff.
The instructions there say:
1. get hellboy kernel cm10 from here http://forum.xda-developers.com/show....php?t=1954967
2. Boot into bootloader
- fastboot flash boot boot.img
- fastboot reboot-bootloader
- fastboot erase cache
3. Boot into recovery - select install zip from sd card..then selct miuiv4.zip
after that reboot again into recovery flash gapps
I do know how to get in recovery, did it before (a year ago), select fastboot, but my computer doesn't do it. I can type fastboot devices but the computer doesn't recognize it. Do I need a program for that?
Also it says: note-fulll wipe is recommended if coming from any rom or else ul get stuck in boot loop. Is this prior to installing the updated ROM or afterwards? Because it is stated afterwards. I also read the WIKI but to me it looks like this is meant for people doing it for the first time, not an update.
Anyways:
I'm not super stupid, managed pretty well last time but I don't get the differences and don't want to mess up my device. I would love some help
Hay guys,
for my Desire HD i use the custom rom Jellytime. I used the r6.2, then i flashed an update.zip to r7.
But then i realized, bluetooth is not working and i'm not connected to my google account. So i decided to downgrade to r6.2, so i flashed the .zip as an update.zip. now my phone freezed after the jellytime bootlogo :/
I tried to get to the recovery but when i press power+ volume down, it vibrates 3 times and nothing happens.
does anybody knows what to do? I have a backup, so are there any possibilities, to restore the backup?
slixx
Ouch, did you flash the ROM as an update.zip or the backup?? And what recovery do you got?
hay,
i flashed the r7 as an update.zip, to update my custom rom from r6.2 to r7. and i also flashed the r6.2 as an update.zip to downgrade
I think this was my fault.
i have the lastes version i think - something like 5.0.1.20.
okay,
i used the adb to boot into the bootloader. with the bootloader i booted into the recovery, know i try to restore my backup.
hope it works!
Report back with your progress.
EDIT: and save yourself some trouble next time by using recovery instead of bootloader for installing ROMs
It worked!
i restored the backup, after this i installed an older version of jellytime, flashed gapps, and restored my personal stuff with google
i didn't flashed the rom with the bootloader. i just forgot to flash gapps, after installing the jellytime update ._.
this was the reason why i was not connected to my google account. and the bluetooth function...hmm i dont care cause i don't use it.
but now everything is okay again.
BTW, if you feel like getting back to jelly time, I recommend using v30, or the last 4.1.2 version of jelly time. I think it was only until v9 that jellytime started getting stable, and v30 should be almost bug free.
Sent from my Inspire 4G using xda app-developers app
black screen after update of Jellytime was installed
I flashed in recovery , formatted and all that and picked up the zip of jellytime all installation steps worked fine and once finsihed and the phone was going to finally reboot it just turned black and didn't continue.
HOw do I resolve this? How can I do my backup ? Right now my phone is useless so appreciate a fast answer
Regards
Toby
ektob said:
I flashed in recovery , formatted and all that and picked up the zip of jellytime all installation steps worked fine and once finsihed and the phone was going to finally reboot it just turned black and didn't continue.
HOw do I resolve this? How can I do my backup ? Right now my phone is useless so appreciate a fast answer
Regards
Toby
Click to expand...
Click to collapse
Do you have an unlock bootloader? If so, have you flashed the boot.img in fastboot?
glevitan said:
Do you have an unlock bootloader? If so, have you flashed the boot.img in fastboot?
Click to expand...
Click to collapse
If you mean I am rooted - yes I am. I had the IceColdSandwich before I tried to flash this CM10 JellyTime. I'm not sure I did the fastboot. I did a clean wipe and selected the update rom zip and then followed the steps, inlcuding selecting Desire S and flash (normal?) . It ran through all the installation steps without problems, but when finsihed and during the reboot it hanged (black screen).
ektob said:
If you mean I am rooted - yes I am. I had the IceColdSandwich before I tried to flash this CM10 JellyTime. I'm not sure I did the fastboot. I did a clean wipe and selected the update rom zip and then followed the steps, inlcuding selecting Desire S and flash (normal?) . It ran through all the installation steps without problems, but when finsihed and during the reboot it hanged (black screen).
Click to expand...
Click to collapse
I didn't ask about root, did I? I made 2 simple questions that have not been answered
glevitan said:
I didn't ask about root, did I? I made 2 simple questions that have not been answered
Click to expand...
Click to collapse
So responding a bit more politely;
Do you have an unlock bootloader? To unlock a bootloader is mlostly resolved by doing a root. That I have done so yes in that case I do have a unlocked bootloader. Please correct me if I am wrong in conclusion.
If so, have you flashed the boot.img in fastboot? I am not sure in this. I think I was give two choices - fast boot and normal boot. I selected normal boot.
ektob said:
So responding a bit more politely;
Do you have an unlock bootloader? To unlock a bootloader is mlostly resolved by doing a root. That I have done so yes in that case I do have a unlocked bootloader. Please correct me if I am wrong in conclusion.
Click to expand...
Click to collapse
You are wrong in your conclusion.
bananagranola said:
You are wrong in your conclusion.
Click to expand...
Click to collapse
OK..fine. Still I'm sure I'm unlocked. Now I acctally got the bootloader working - ACE PVT ENG S-OFF RL . So I read your link - thanks it seemed valuable but I didn't get why I needed to open a terminal window (dos window I assume) secondly it didn't work at all since the usb connection didn't connect properly.. I'm sorry for being such a hassle.. . I did before though un zip the folders so if needed - where should the boot image be in order for it to load from the sd card ?
Thanks for the patience
EDIT: I tried to follow the flashboot steps as best I could, but failed to load the image.
ektob said:
ACE PVT ENG S-OFF RL
Click to expand...
Click to collapse
Then you are not unlocked!! I give up.
bananagranola said:
Then you are not unlocked!! I give up.
Click to expand...
Click to collapse
Whatever - I didn't stop me from installing other ROMs. This case is now closed - I changed ROM to CodefireX - worked fine. But sure I will look into it if its necessary - for sure for Jellytime..
I must say you guys really tried to help but any reasons to why I have to unlock bootloader - is that something that have become necessary over time? Maybe its also bad instructions on the ROMS main pages? Why do I need to search 50 different forums to get a simple answer?
Anyway you can give up on me now because I resolved it on my own. Thanks
Because there are additional steps if you are unlocked...
Hey guys so I'm in boot loop. Yes I know there are many guides all over saying how to fix it but I have tried many of them and they didnt work.
What happens is I start the phone, it shows the boot image and then restarts after a time.
I can boot into the Recovery mode by spamming the back button when the Logo comes. And can install zip files from the SD card.
I also have tried flashtool to restore it to stock but when i try flashing it detects my device "Device connected in flash mode" but when i try toflash it, it gives an error "Error flashing. Aborted".
I tried many many room whit kernels but stuck on bootloop every time, no way. I have never seen this problem before. Maybe bricked bootloader ?
I tried to relock the bootloader but doesnt help either.
Any help?
Ok, since you can boot into recovery can you flash you ROM.zip and try to boot into ROM? I also need some details:
- ROM you were using
- Kernel you were using
- How you got bootloop
Flashtool should work, try to recover using flashtool.
僕のLT18iから送られてきた
popthosegaskets said:
Ok, since you can boot into recovery can you flash you ROM.zip and try to boot into ROM? I also need some details:
- ROM you were using
- Kernel you were using
- How you got bootloop
Flashtool should work, try to recover using flashtool.
僕のLT18iから送られてきた
Click to expand...
Click to collapse
Before this happened i was using Ultimate HD 4.0 and Vengeance kernel ayame. The telephone was crashed and i didnt any backup. I tried to upgrade it to android 4.2 or 4.1 and the probleme begin I relocked the bootloader but doesnt help. I flashed it but doesnt accept any firmware, show Error flash bla bla bla Flash aborted. tried almost roms and kernels but doesnt help. I can install rooms and flash kernels, and boot up to recovery but after that is just stuck on boot animation or bootloop.:crying::crying::crying:
During the upgrade to JB, did you flash the kernel that came with it?
I assume you wanted to update to CM10/10.1? Vengeance Kernel is not compatible with JB. You need to flash UHD4 back to /system partition if you want to stick with UHD or flash the boot.img that came with the JB ROM.zip.
Do a clean install. Your phone should be working again if you do the steps correctly.
If you still have problems, you can reply to this thread or send me a PM if you wish to be more private about it.
Regards, 日焼けさん.
僕のLT18iから送られてきた
popthosega-skets said:
During the upgrade to JB, did you flash e ä'ökernel that came with it?
I assume you wanted to update to CM10/10.1? Vengeance Kernel is not compatible with JB. You need to flash UHD4 back to /system partition if you want to stick with UHD or flash the boot.img that came with the JB ROM.zip.
Do a clean install. Your phone should be working again if you do the steps correctly.
If you still have problems, you can reply to this thread or send me a PM if you wish to be more private about it.
Regards, 日焼けさん.9
僕のLT18iから送られてきた
Click to expand...
Click to collapse
Thank you very much but i need steps . Plzz
Best regards
popthosegaskets said:
During the upgrade to JB, did you flash the kernel that came with it?
I assume you wanted to update to CM10/10.1? Vengeance Kernel is not compatible with JB. You need to flash UHD4 back to /system partition if you want to stick with UHD or flash the boot.img that came with the JB ROM.zip.
Do a clean install. Your phone should be working again if you do the steps correctly.
If you still have problems, you can reply to this thread or send me a PM if you wish to be more private about it.
Regards, 日焼けさん.
僕のLT18iから送られてきた
Click to expand...
Click to collapse
Sorry but i want tell you that the last i tried is this but doesnt help, stuck on boot animation. I gone be crazy.
OBS !!!!!! When i install rom and not working whit me i look on SD on pc if the installation files are there but nothing just the rom zip. I changed the SD but the same happened
Having issues realted to this one. Here's my device info. Hope it helps.
Device:
-> never been modded.
-> all stock rom.
-> stuck on a bootloop due to bluetooth.
It doesn't even have a recovery mod. So I'm pretty much stuck.
Can you help me out? And another thing, sorry for bringing this
old topic back. Haha.
Dear XDA Members,
I currently run stock 5.1.1 (14.6.A.1.236) with no modifications whatsoever and a locked bootloader.
I would like to install a custom rom (PAC-ROM LP-MR1 5.1.1) on my Z1C.
I did some research and these are the steps i came up with:
1. install sdk and drivers
2. unlock bootloader
3. fastboot flash recovery "fota.img" (shouldn't it specify somehow that i need it to be flashed on the fota partition?)
4. factory reset/wipe
5. install custom rom + gapps
Coming from a locked bootloader a fully stock phone is there anything else i need to do like a new bootloader or something?
Also I'll be doing it through Win 10 64bit, I hope that isn't a problem.
Any advice will be highly appreciated.
Thank you very much
ursidae1 said:
Dear XDA Members,
I currently run stock 5.1.1 (14.6.A.1.236) with no modifications whatsoever and a locked bootloader.
I would like to install a custom rom (PAC-ROM LP-MR1 5.1.1) on my Z1C.
I did some research and these are the steps i came up with:
1. install sdk and drivers
2. unlock bootloader
3. fastboot flash recovery "fota.img" (shouldn't it specify somehow that i need it to be flashed on the fota partition?)
4. factory reset/wipe
5. install custom rom + gapps
Coming from a locked bootloader a fully stock phone is there anything else i need to do like a new bootloader or something?
Also I'll be doing it through Win 10 64bit, I hope that isn't a problem.
Any advice will be highly appreciated.
Thank you very much
Click to expand...
Click to collapse
First things first... Root. If you already did that then you're on the right track.
1. If you're not doing major development stuff, don't install the whole sdk. See here - http://forum.xda-developers.com/showthread.php?p=48915118 There may be issues you'll have to work with on newer versions of Windows. I haven't done it on anything later than 7. Keep in mind, though, that you won't need the computer to flash your boot img or rom, but you will need it to unlock the bootloader.
2. -
3. You can do this with an app called Rashr on your phone with root. Just download a recovery img, then open Rashr and follow the instructions.
4-5. Boot into recovery, full wipe, (system data and caches), flash rom zip and gapps zip. Maybe best to not flash more than that at once to start, in case there's a problem and you have no way to figure out what it is.
BTW, PacMan is a great choice. I've been using it for months.
levone1 said:
First things first... Root. If you already did that then you're on the right track.
1. If you're not doing major development stuff, don't install the whole sdk. See here - http://forum.xda-developers.com/showthread.php?p=48915118 There may be issues you'll have to work with on newer versions of Windows. I haven't done it on anything later than 7. Keep in mind, though, that you won't need the computer to flash your boot img or rom, but you will need it to unlock the bootloader.
2. -
3. You can do this with an app called Rashr on your phone with root. Just download a recovery img, then open Rashr and follow the instructions.
4-5. Boot into recovery, full wipe, (system data and caches), flash rom zip and gapps zip. Maybe best to not flash more than that at once to start, in case there's a problem and you have no way to figure out what it is.
BTW, PacMan is a great choice. I've been using it for months.
Click to expand...
Click to collapse
Thanks a lot for your reply.
I was reading on the cyanogen mod wiki how-to for our phone and it doesn't require a prior root.
I did those steps on my xperia m and it worked and i had never rooted it, the only difference is that i flashed cyanogen recovery and install cm12 which basically roots the phone and then flashed fota recovery.
Should i go this way again to gain root or would you recommend an easier root method for my stock build which is the newest.
If you recommend another root method when should it occur? prior unlocking the bootloader or afterwards?
Thanks
If this is your first time unlocking your bootloader, make sure you backup your DRM-Keys! You need to be rooted for that.
They are lost when bootloader gets unlocked. Some features in regards of camera performance are lost for example.
ursidae1 said:
Thanks a lot for your reply.
I was reading on the cyanogen mod wiki how-to for our phone and it doesn't require a prior root.
I did those steps on my xperia m and it worked and i had never rooted it, the only difference is that i flashed cyanogen recovery and install cm12 which basically roots the phone and then flashed fota recovery.
Should i go this way again to gain root or would you recommend an easier root method for my stock build which is the newest.
If you recommend another root method when should it occur? prior unlocking the bootloader or afterwards?
Thanks
Click to expand...
Click to collapse
True, if bl is unlocked, then you can flash the kernel and recovery via fastboot, then flash your rom. You may need the boot.img from your rom zip file. Then use commands 'fastboot flash boot' for the boot img, and 'fastboot flash recovery' for recovery. If you're rooted already, you can just do it on the phone.
levone1 said:
True, if bl is unlocked, then you can flash the kernel and recovery via fastboot, then flash your rom. You may need the boot.img from your rom zip file. Then use commands 'fastboot flash boot' for the boot img, and 'fastboot flash recovery' for recovery. If you're rooted already, you can just do it on the phone.
Click to expand...
Click to collapse
This is fantastic.
Do you think itll be ok to fastboot flash boot boot.img from cm12.1 rom zip then fastboot flash recovery fota.img instead of the cyanogen recovery that comes with cm12.1?
Do you think that might cause an issue?
ursidae1 said:
This is fantastic.
Do you think itll be ok to fastboot flash boot boot.img from cm12.1 rom zip then fastboot flash recovery fota.img instead of the cyanogen recovery that comes with cm12.1?
Do you think that might cause an issue?
Click to expand...
Click to collapse
Should be fine. It's also a 1 second operation to extract boot.img from your rom zip, which you need already downloaded and on your SD card before you flash imgs. You might even be fine without flashing the boot img - can't hurt to try. Just flash the recovery and reboot and see if you get a purple light. Then, volume button changes purple to orange, and you're in recovery. Some recoveries don't work with some kernels, (been my experience).
levone1 said:
Should be fine. It's also a 1 second operation to extract boot.img from your rom zip, which you need already downloaded and on your SD card before you flash imgs. You might even be fine without flashing the boot img - can't hurt to try. Just flash the recovery and reboot and see if you get a purple light. Then, volume button changes purple to orange, and you're in recovery. Some recoveries don't work with some kernels, (been my experience).
Click to expand...
Click to collapse
I now have cm12.1 with cyanogen recovery.
Which recovery is best for our phone, which one do you use?
I can find 2 options:
FOTA TWRP 2.8.6.0 (http://forum.xda-developers.com/sony-xperia-z1-compact/general/fota-twrp-recovery-amami-t2909719)
XZDualRecovery (http://forum.xda-developers.com/showthread.php?t=2647480)
Thanks a lot
ursidae1 said:
I now have cm12.1 with cyanogen recovery.
Which recovery is best for our phone, which one do you use?
I can find 2 options:
FOTA TWRP 2.8.6.0 (http://forum.xda-developers.com/sony-xperia-z1-compact/general/fota-twrp-recovery-amami-t2909719)
XZDualRecovery (http://forum.xda-developers.com/showthread.php?t=2647480)
Thanks a lot
Click to expand...
Click to collapse
I have only used xzdr with stock rom. I think in the past I've had it not work for me on CM, so I just stick to straight twrp by default. I know NUT has always been hard at work and has made steady improvements, so maybe not an issue now. Personally I realized that I only need 1 recovery anyway. There's a newer Twrp here - http://forum.xda-developers.com/crossdevice-dev/sony/twrp-v2-8-6-0-f2fs-z1-z1c-z2-z3-z3c-t3098573
One important fact that has already been probably mentioned is that installing custom roms on your XPERIA will worsen your camera, esp the front one. Keep this in mind.