Database Develop

CWM Recovery problem

Hi, I followed the guide to install CWM and it seemed to go fine, but when I power on the phone and tap the vol-down key nothing happens, I do get the vibrations as I'm doing it though. Is CWM really necessary to install a custom rom? Cos I might just skip it.

You can't flash a custom rom without cwm recovery.
Sent from my C2104 using XDA Free mobile app

karthikys1 said:
You can't flash a custom rom without cwm recovery.
Sent from my C2104 using XDA Free mobile app
Click to expand...
Click to collapse
O lol, I guess I need to solve this then. I thought I just used FlashTool to flash the rom and viola, rom is on.
Does anyone have any ideas what I might be able to try to figure out why CWM isn't working? Any way to see if CWM is actually on my phone? (Maybe it's just not there, rather then not working).
Edit: Rom Manager seems to think I have CWM installed, also I did a Nandroid Backup which seemed to be configured to use CWM so I don't know if it's there or not, or working or not

Which guide did you follow? And how did you make a Nandroid Backup?

I followed this guide.
I downloaded Nandroid Backup Root, it created the backup without rebooting the phone, so it never needed to boot into CWM.

Astralogic said:
I followed this guide.
I downloaded Nandroid Backup Root, it created the backup without rebooting the phone, so it never needed to boot into CWM.
Click to expand...
Click to collapse
That's what I thought. The fact that it can create a backup doesn't mean it has a recovery installed, it doesn't use a recovery to create it. If the LED is lighting up at boot, and it is vibrating, and it doesn't get back in, I don't know what the problem would be. I'd try reinstalling CWM, and FYI, you should use V8; V9 has issues.
At the very least, if it really is installed, you should have a "recovery.tar" and "chargemon" file in /system/bin/.

Antiga Prime said:
That's what I thought. The fact that it can create a backup doesn't mean it has a recovery installed, it doesn't use a recovery to create it. If the LED is lighting up at boot, and it is vibrating, and it doesn't get back in, I don't know what the problem would be. I'd try reinstalling CWM, and FYI, you should use V8; V9 has issues.
At the very least, if it really is installed, you should have a "recovery.tar" and "chargemon" file in /system/bin/.
Click to expand...
Click to collapse
I don't have those files so CWM is not installed. I can't find v8 of CWM for Xperia T but I found this file "CWM4XperiaT_v8i_JB.zip", is that it?

Astralogic said:
I don't have those files so CWM is not installed. I can't find v8 of CWM for Xperia T but I found this file "CWM4XperiaT_v8i_JB.zip", is that it?
Click to expand...
Click to collapse
It clearly says "Xperia T" in the name of that file... yes, that's it. Now I'm wondering what you installed, if you didn't install that one, or V9.

Antiga Prime said:
It clearly says "Xperia T" in the name of that file... yes, that's it. Now I'm wondering what you installed, if you didn't install that one, or V9.
Click to expand...
Click to collapse
V8 works perfectly, it's installed fine.
I am going to follow this guide to install cyanogenmod, do I need to obtain a bootloader unlock code? Or should I just skip right to installing the ROM?
Edit: Oops forgot the link: http://wiki.cyanogenmod.org/w/Install_CM_for_mint

Astralogic said:
V8 works perfectly, it's installed fine.
I am going to follow this guide to install cyanogenmod, do I need to obtain a bootloader unlock code? Or should I just skip right to installing the ROM?
Edit: Oops forgot the link: http://wiki.cyanogenmod.org/w/Install_CM_for_mint
Click to expand...
Click to collapse
First of all, yes, you need an unlocked bootloader. You can't flash custom kernels on a locked bootloader. Secondly, I've never tried that tutorial (I have a TX), but I'm assuming it should work fine, but, personally I'd either go with FXP, or one of the OMNI builds here in XDA, since, as far as I know, developers here have more fixes than what I've seen on FXP and/or CM.
Also, there are a easier ways to flash your ROM, since you already have a custom ROM. I don't think it's necessary to have to fastboot the kernel first.
Edit: The Carbon ROM I'm on also has a T version. The reason I'm on this ROM (and previously OMNI) was because FXP/CM roms have/had a battery drain that was never fixed, something that was fixed here on XDA.

Antiga Prime said:
First of all, yes, you need an unlocked bootloader. You can't flash custom kernels on a locked bootloader. Secondly, I've never tried that tutorial (I have a TX), but I'm assuming it should work fine, but, personally I'd either go with FXP, or one of the OMNI builds here in XDA, since, as far as I know, developers here have more fixes than what I've seen on FXP and/or CM.
Also, there are a easier ways to flash your ROM, since you already have a custom ROM. I don't think it's necessary to have to fastboot the kernel first.
Edit: The Carbon ROM I'm on also has a T version. The reason I'm on this ROM (and previously OMNI) was because FXP/CM roms have/had a battery drain that was never fixed, something that was fixed here on XDA.
Click to expand...
Click to collapse
There's a problem My bootloader is not unlockable... does this mean I've been wasting my time?
Edit: There is this guide, it makes no mention of unlocking the bootloader so it might work?

Astralogic said:
There's a problem My bootloader is not unlockable... does this mean I've been wasting my time?
Edit: There is this guide, it makes no mention of unlocking the bootloader so it might work?
Click to expand...
Click to collapse
No, that tutorial won't work. Never follow a guide for flashing ROMs that wasn't meant for your phone. Your phone didn't even exist yet when that guide was written.
If you can't unlock your bootloader then there is no way you'll ever be able to flash a custom ROM, because, like I mentioned earlier, custom ROMs have custom kernels, and custom kernels need an unlocked bootloader.
I wouldn't consider it a waste, it's always useful to have a recovery installed; with it you can at the very least backup and restore, flash deodexed/zipaligned stock ROMs, such as this one, flash files, and even have access to ADB if your phone doesn't boot up, which can save you from having to wipe everything, etc., so not a complete waste of time.

Antiga Prime said:
No, that tutorial won't work. Never follow a guide for flashing ROMs that wasn't meant for your phone. Your phone didn't even exist yet when that guide was written.
If you can't unlock your bootloader then there is no way you'll ever be able to flash a custom ROM, because, like I mentioned earlier, custom ROMs have custom kernels, and custom kernels need an unlocked bootloader.
I wouldn't consider it a waste, it's always useful to have a recovery installed; with it you can at the very least backup and restore, flash deodexed/zipaligned stock ROMs, such as this one, flash files, and even have access to ADB if your phone doesn't boot up, which can save you from having to wipe everything, etc., so not a complete waste of time.
Click to expand...
Click to collapse
Ok, well, I learned a bit in the process, and I still have an Xperia SP bootloader to unlock, then flash cyanogenmod, so I'm in a better position to handle that now, thanks for all the help guys.

Wifi Connection Issue .108 + .118

So as Im sure everyone here knows, new firmware updates have rolled out...
For some odd reason, though, I cannot enjoy them. I came from iHackers 4.1 ROM and attempted to update to the Criskelo .118 ROM. All went okay, except the wifi kept saying "turning on."
Then, amongst other problems, I tried to go to just a stock .108 by downgrading... Still, "turning on wifi."
I'm not sure if there is any relevance, but I had Phil/TWRP dual recovery installed. The Criskelo ROM instructions said I had to have CWM if on a locked bootloader, but I am unlocked. Perhaps I misunderstood and it has to be CWM for both? I did notice that despite many efforts to get my dual recovery back, I was stuck with CWM (I did get dual back though eventually).
So could the problem have been with the conflicting recoveries? And perhaps it didn't install the kernel or ROM properly?
Thanks in advance for any replies.

ShadowTech13 said:
So as Im sure everyone here knows, new firmware updates have rolled out...
For some odd reason, though, I cannot enjoy them. I came from iHackers 4.1 ROM and attempted to update to the Criskelo .118 ROM. All went okay, except the wifi kept saying "turning on."
Then, amongst other problems, I tried to go to just a stock .108 by downgrading... Still, "turning on wifi."
I'm not sure if there is any relevance, but I had Phil/TWRP dual recovery installed. The Criskelo ROM instructions said I had to have CWM if on a locked bootloader, but I am unlocked. Perhaps I misunderstood and it has to be CWM for both? I did notice that despite many efforts to get my dual recovery back, I was stuck with CWM (I did get dual back though eventually).
So could the problem have been with the conflicting recoveries? And perhaps it didn't install the kernel or ROM properly?
Thanks in advance for any replies.
Click to expand...
Click to collapse
The recovery has nothing to do with the functionality of wifi or anything in the ROM for that matter. Did you do a full wipe before installing the Criskelo ROM?
Other than that, make sure you're using the right baseband for .118. (if it even has changed)
If that all fails, make a backup of everything on your phone (also your internal 'sdcard') and do a full re-install of the official .118 ROM using flashtool.

B1nny said:
The recovery has nothing to do with the functionality of wifi or anything in the ROM for that matter. Did you do a full wipe before installing the Criskelo ROM?
Other than that, make sure you're using the right baseband for .118. (if it even has changed)
If that all fails, make a backup of everything on your phone (also your internal 'sdcard') and do a full re-install of the official .118 ROM using flashtool.
Click to expand...
Click to collapse
Yup, I made sure to do a full wipe before I installed it. I did do a backup of my internal and external SD cards just in case something managed to go wrong somehow... Im pretty sure I used the correct baseband, but I will double-check and also try your suggested method using flashtool. I'll let you know how it goes, and thanks for the response!

ShadowTech13 said:
Yup, I made sure to do a full wipe before I installed it. I did do a backup of my internal and external SD cards just in case something managed to go wrong somehow... Im pretty sure I used the correct baseband, but I will double-check and also try your suggested method using flashtool. I'll let you know how it goes, and thanks for the response!
Click to expand...
Click to collapse
Still nothing... I did more wipes/factory resets with this phone than I have ever done. lol

ShadowTech13 said:
Still nothing... I did more wipes/factory resets with this phone than I have ever done. lol
Click to expand...
Click to collapse
You had better bring your phone to the service if you don't want WiFi module dies.

Forgive me for asking, but what would be wrong with the module? Wouldn't it not work at all of that were the case? It's working right now...
Sent from my C6903 using xda premium

ShadowTech13 said:
Forgive me for asking, but what would be wrong with the module? Wouldn't it not work at all of that were the case? It's working right now...
Sent from my C6903 using xda premium
Click to expand...
Click to collapse
Alright so it's definitely not the module. I just flashed PAC's 4.4.4 Beta ROM. The wifi successfully turns on and I am able to view networks, as well as connect to them. So why then, can I not seem to get wifi working on stock based 4.4.4 or .108/.118 ROMs? Any ideas?

[HELP] Can not write any custom roms.

I can no longer write any custom roms to my N6. Started with PURE 3.5 but now effects any rom i try to flash. I have brought my N6 back to factory state multiple times even relocking it. Only thing I can do is Fastboot flash N6 image from google manually piece by piece. I do have working 5.01 and phone works. Roms either hang or have errors. or just write the boot.img file. TWRP works other wise i can backup and restore, I am using 2.8.3.1. I have searched all over for a fix....

There used to be some weird mounting stuff that would make roms not boot. Thought that was worked out in pure shamu 3.1 ish.
Where do the roms hang? Did you ever fix permissions using twrp? Any kind of log you can pull?

dipstik said:
There used to be some weird mounting stuff that would make roms not boot. Thought that was worked out in pure shamu 3.1 ish.
Where do the roms hang? Did you ever fix permissions using twrp? Any kind of log you can pull?
Click to expand...
Click to collapse
I had no problem updating Pure for over a month from like 2.0 to 3.4.
they all hang when writing to system as far as i can tell. happens regardless of Pure....from a fresh clean image of 5.0 or 5.01 i can not flash any roms. driving me nutzo....i can no longer flash pure 3.4 either but i can restore the phone from a nandroid backup i had on my pc and run Pure 3.4 just fine.

Did you wipe everything except internal storage first? I had this issue earlier until I realized that I forgot to do that when coming from the stock ROM.

Pilz said:
Did you wipe everything except internal storage first? I had this issue earlier until I realized that I forgot to do that when coming from the stock ROM.
Click to expand...
Click to collapse
yes and both cache.....
also made sure system not mounted.
very frustrating.

Bignoze73 said:
yes and both cache.....
also made sure system not mounted.
very frustrating.
Click to expand...
Click to collapse
That is very odd, did you try reflashing TWRP or using a different version.

Pilz said:
That is very odd, did you try reflashing TWRP or using a different version.
Click to expand...
Click to collapse
mutiple times......tried all versions of TWRP too.
I can write a custom kernal like elementalx no problem.....just not roms.

Bignoze73 said:
mutiple times......tried all versions of TWRP too.
Click to expand...
Click to collapse
It doesn't make sense considering you also flashed back to stock. Have you also tried to flash a ROM from your PC rather than from your phone? There has to be some reasonable explanation for why it's not working.

Pilz said:
It doesn't make sense considering you also flashed back to stock. Have you also tried to flash a ROM from your PC rather than from your phone? There has to be some reasonable explanation for why it's not working.
Click to expand...
Click to collapse
how do you do that? the custom roms dont have system.img file like N6 image. The Pure 3.92 is in .dat format, another rom is folders. I also get checksum errors when extracting.
I also noticed in the last 24 hours there are 2 other threads with people have almost the same issues flashing roms. I think it has something to do with TWRP but no matter becuase no version works for me.

Bignoze73 said:
how do you do that? the custom roms dont have system.img file like N6 image. The Pure 3.92 is in .dat format, another rom is folders. I also get checksum errors when extracting.
I also noticed in the last 24 hours there are 2 other threads with people have almost the same issues flashing roms. I think it has something to do with TWRP but no matter becuase no version works for me.
Click to expand...
Click to collapse
If you restore your stock recovery on your phone you could try this.
Make sure TWRP is not installed on your phone and that the stock recovery is installed and working:
Have TWRP in your platform tools folder named however you want
Then use "fastboot boot recovery 'whatever you named TWRP' "
This will boot TWRP without installed it. Then try to flash the ROM using TWRP. You can also use the"adb push" to sideload the ROM onto your phone so you can find it via TWRP.

nope did not work.....roms just hang or flash new boot.img only.
i even tried erasing recovery partion and reflashing stock than twrp 2.8.3.1......that did not work either....something is stopping TWRP from writing to system.
thanks for your help

Bignoze73 said:
nope did not work.....roms just hang or flash new boot.img only.
i even tried erasing recovery partion and reflashing stock than twrp 2.8.3.1......that did not work either....something is stopping TWRP from writing to system.
thanks for your help
Click to expand...
Click to collapse
You're welcome, have you tried to contact some of the devs here to see if maybe they could help? I think the worst case scenario would be to RMA the phone.

Pilz said:
You're welcome, have you tried to contact some of the devs here to see if maybe they could help? I think the worst case scenario would be to RMA the phone.
Click to expand...
Click to collapse
RMA the phone??? ?What are you gonna tell them?? ? That you can't flash any custom Roms through TWRP?? ?

laureanop said:
RMA the phone??? ?What are you gonna tell them?? ? That you can't flash any custom Roms through TWRP?? ?
Click to expand...
Click to collapse
No obviously not look, but if you have other issues (in assuming you might if you can't flash a ROM) then that's the worst case scenario option.

Pilz said:
No obviously not look, but if you have other issues (in assuming you might if you can't flash a ROM) then that's the worst case scenario option.
Click to expand...
Click to collapse
This is a tough one cause if his factory image works without issues they're gonna have no reason to send him a replacement

laureanop said:
This is a tough one cause if his factory image works without issues they're gonna have no reason to send him a replacement
Click to expand...
Click to collapse
That's true, but there must be something wrong if he can't flash anything else so I'm sure he could find some issues.

Pilz said:
That's true, but there must be something wrong if he can't flash anything else so I'm sure he could find some issues.
Click to expand...
Click to collapse
Is there a tool or command to do a full memcheck of both ram and storage

rgraville said:
Is there a tool or command to do a full memcheck of both ram and storage
Click to expand...
Click to collapse
I'm not sure I've never had the need to do one from adb or fastboot

Pilz said:
I'm not sure I've never had the need to do one from adb or fastboot
Click to expand...
Click to collapse
yeah its pretty nuts....how can I return a phone that works fine other than the fact it wont flash a custom rom?
Must be another way to write a rom but TWRP......
thanks!

Bignoze73 said:
yeah its pretty nuts....how can I return a phone that works fine other than the fact it wont flash a custom rom?
Must be another way to write a rom but TWRP......
thanks!
Click to expand...
Click to collapse
I assume you are also out of the return window. Well if you are unlucky or lucky (depending on how you view it) you could have an issue eventually. They will RMA for burn in, camera issues etc... The camera issue was common in the earlier production models that I had. There should be another method, I would look into it if you have time.

Is there an easy way to unroot?

I'm using chroma ROM and my satellite provider requires it's app to run on an unrooted phone. I'd there an easy way to unroot my Nexus without having to wipe?

slekkas said:
I'm using chroma ROM and my satellite provider requires it's app to run on an unrooted phone. I'd there an easy way to unroot my Nexus without having to wipe?
Click to expand...
Click to collapse
Flash the system image from a factory image. If your kernel is modified, flash the boot IMG as well.

Use wugs toolkit.

Evolution_Tech said:
Flash the system image from a factory image. If your kernel is modified, flash the boot IMG as well.
Click to expand...
Click to collapse
So just to get this straight and I don't screw up my phone. I find the stock rom same version as my chroma which is LMY48B. I extract it and using fastboot I install system.img and boot.img? My phone is unencrypted right now... Will it get encrypted?
And when I need root again I must just install it along with Franco Kernel I'm using?
I appreciate the help...

Nickchapstick said:
Use wugs toolkit.
Click to expand...
Click to collapse
I installed it on my laptop but even though my phone is rooted I don't see an option to unroot... Maybe because I didn't use regular rom and used chroma instead?

slekkas said:
So just to get this straight and I don't screw up my phone. I find the stock rom same version as my chroma which is LMY48B. I extract it and using fastboot I install system.img and boot.img? My phone is unencrypted right now... Will it get encrypted?
And when I need root again I must just install it along with Franco Kernel I'm using?
I appreciate the help...
Click to expand...
Click to collapse
First, why are you trying to unroot?
You would download a factory image form the Google developer page. Extract twice, and grab the system image from there. Yes, match the version your phone is currently on.

Evolution_Tech said:
First, why are you trying to unroot?
You would download a factory image form the Google developer page. Extract twice, and grab the system image from there. Yes, match the version your phone is currently on.
Click to expand...
Click to collapse
I'm trying to unroot because my satellite provider uses an app like sky go that requires your phone to be unrooted... I need to watch a game sometimes when I'm at work.

slekkas said:
I'm trying to unroot because my satellite provider uses an app like sky go that requires your phone to be unrooted... I need to watch a game sometimes when I'm at work.
Click to expand...
Click to collapse
Have you considered multi ROM? You could have your rooted normal set up and a non rooted as well.

Can't you just go into supersu settings and unroot? That way you can stay on chroma

Kreateablaze said:
Can't you just go into supersu settings and unroot? That way you can stay on chroma
Click to expand...
Click to collapse
Depends on how deeply his situation is looking for root files. The unroot feature of SuperSU doesn't remove everything.

Evolution_Tech said:
Have you considered multi ROM? You could have your rooted normal set up and a non rooted as well.
Click to expand...
Click to collapse
My friend I didn't know this was possible with the nexus 6. That would really interest me.... I already have twrp installed. Is there an easy guide you can point out for me?

slekkas said:
My friend I didn't know this was possible with the nexus 6. That would really interest me.... I already have twrp installed. Is there an easy guide you can point out for me?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3074529

Evolution_Tech said:
Depends on how deeply his situation is looking for root files. The unroot feature of SuperSU doesn't remove everything.
Click to expand...
Click to collapse
Tried this keeps telling me that I need to unroot. So i'm about to start the multi rom procedure

Evolution_Tech said:
Have you considered multi ROM? You could have your rooted normal set up and a non rooted as well.
Click to expand...
Click to collapse
How about the encryption? Chroma is unencrypted. If the second rom is encrypted what happens there?
I'm also trying to find a stock rom that is not pre-rooted to install from recovery. Can you show me the latest I can get?

Evolution_Tech said:
Have you considered multi ROM? You could have your rooted normal set up and a non rooted as well.
Click to expand...
Click to collapse
My friend I installed multirom and used an older Chroma rom that wasn't pre-rooted. it worked like a charm.... Now I can just go to this rom and use all my apps that require the phone to be unrooted.... Again thanks for the idea....

Can I just ask what version of chroma wasn't pre rooted? I want to do the same if possible. Thanks

Drefsab said:
Can I just ask what version of chroma wasn't pre rooted? I want to do the same if possible. Thanks
Click to expand...
Click to collapse
well, 2 months ago it was being called older.. anyways, the far majority of roms do not have root. you need to flash the supersu file shen flashing the roms, for root. but, to flash a rom, yoh need an unlocked bootloader and twrp recovery. most apps that check for root will still think that you have root though.

simms22 said:
well, 2 months ago it was being called older.. anyways, the far majority of roms do not have root. you need to flash the supersu file shen flashing the roms, for root. but, to flash a rom, yoh need an unlocked bootloader and twrp recovery. most apps that check for root will still think that you have root though.
Click to expand...
Click to collapse
i must have fell asleep during this development lol
far as i have ever seen, its rare for a rom to not be rooted, however, more frequently devs have had it off by default, and its a treasure hunt to find where to turn it on.
i do always flash the su zip, to avoid this tedious hunting though.

bweN diorD said:
i must have fell asleep during this development lol
far as i have ever seen, its rare for a rom to not be rooted, however, more frequently devs have had it off by default, and its a treasure hunt to find where to turn it on.
i do always flash the su zip, to avoid this tedious hunting though.
Click to expand...
Click to collapse
cm based, probably have root. aosp roms, the far majority do mot have root. you need to grab it if you want it

simms22 said:
cm based, probably have root. aosp roms, the far majority do mot have root. you need to grab it if you want it
Click to expand...
Click to collapse
yup I found that most are pre-rooted, though found cleancore that works great. I've just installed multirom and that booted into it then tested a couple of apps that are blocked on root (Banking app and Sky Go), and happy days they work great.
Its annoying and rather wasteful having have a second rom just to run a couple of apps but at least now I can use the apps on my device if I want to. Thanks
Typical apps block hacking (root) so the work around instead of unrooting is to go deeper with the hacks/mods

Help with custom rom

Good night. Has anyone noticed the flashing of the cell network signal when using custom ROM? Sometimes even the signal disappears completely as if it did not have a chip and does not give a network being that return the operation just by restarting. If someone has already experienced this and has the solution, please report it. I have already used all the customs for the x4 bike and they all stay that way.
appreciate

What custom ROM are you using?
How did you install it?
Did you use the partitions zip before installing the ROM?

dougo007 said:
What custom ROM are you using?
Any custom ROM.
How did you install it?
Boot to TWRP.
Flash copy partition
Swipe to factory reset
Boot back to TWRP recovery
flash Rom + TWRP zip
Boot back to TWRP recovery
Flash GApps
Wipe Cache + Dalvik
Reboot to System
Did you use the partitions zip before installing the ROM?
Click to expand...
Click to collapse
Yes, i do it.

Ok; you're steps appear correct.
A thought occurred to me and this is easier to do than anything else.
Are you having any issue with the SIM card?
Is it making good contact?
Are you using Google Fi by chance?

dougo007 said:
Ok; you're steps appear correct.
A thought occurred to me and this is easier to do than anything else.
Are you having any issue with the SIM card?
R: No.
Is it making good contact?
R: Yes
Are you using Google Fi by chance?
Click to expand...
Click to collapse
R: No

Noslineg said:
R: No
Click to expand...
Click to collapse
Which ROM?

dhinesh_cool said:
Which ROM?
Click to expand...
Click to collapse
Payton PPW29.69-26. I already used itnup tobGoogle FI, but the problem came up.

I suggest trying one of the solutions here: https://www.technobezz.com/fix-no-signal-android/
They recommend to first restore your phone to stock, make sure you get the right variant.

Just try to flash another radio (modem) . I had similar issues with RETBR modem ) Now I`m using FI modem and everything is OK (Havoc 2.1 ROM)