Related
Hi all - the weirdest thing is happening to me and it is definitely something I've done but I haven't the slightest what it is.
I've got CMX right now, and I've tried to go to a couple of ICS ROMs (Task, Sonic). They flash just fine, but on the new system if the screen goes to sleep the video flickers on screen wakeup. I have tried to remedy this by flashing an ICS kernel but haven't had any luck whatsoever. So today I thought I'd go back to my Nandroid backup that I took on CWM 5.0.2.7 way back on the 1st before I rooted my tab. I was on (and prefer) TWRP so I used Odin to re-flash the original recovery, wiped everything (including format /system from the Mounts menu to wipe the ROM) and restored the backup. Everything seemed fine. But to my horror, I locked the screen and woke it up to find the same flickering!!!!
I rebooted back into recovery and flashed TWRP back on so I could restore my CMX backup and I'm back to normal again. But now I feel like I'm stuck here, and the only way I'm going to be able to fix this issue is by using Odin to flash a stock firmware package. I really don't want to have to do that if I don't have to but will if I need to of course...
The one thing I haven't been able to get an answer on is before blowing everything away is what I'm asking now...in thinking about it, I had taken the backup before flashing a bootloader to fix my "rolling recovery screen" issue. Could the cause of this type of problem be a bootloader that the ROM doesn't like, or is this a crazy assumption?
OK I'm going to bump this thread with a simple to-the-point question - hoping for an answer as I work out my theories.
For those of you who have flashed ICS and custom recovery with no "rolling/flickering" issues - are you using an unlocked bootloader?
For the bootloader you just hit the point my friend,the bootloader that we use to fix rolling recovery problem has issues with most kernels except Pershoot's HC or CM9...
For your problem you should think of grabbing the official ICS or HC(just for getting rid of screen flicker),and in addition to flashing it you should extract it's stock bootloader,make a. tar.md5 out of it and keep it for future similar problems...
Note that the bootloader can only be flashed using Odin in PC and CWM or even stock flashing using MobileOdin can't make changes to it(or recover it)
For now there is not a proper fix for that but I think the best way is to have the stock bootloader and use ROMmanager or MobileOdin for flashing(since the recovery rolls with stock bootloader)...
Yeah I flashed stock ICS and rooted yesterday. I am just going to fight through the rolling recovery for now and stick with ICS until we can do more.
Thanks for the response!
some trick:you can rename the zip files you're going to flash so that their name starts with "Z",it's then easy to navigate to them(just press vol down twice)
Yep! That works, and you can also rename files as update.zip and use that option I believe. It's time to think outside of the box a bit with regard to flashing some ROMs...thats the bottom line. i am sure there are a few devs on this site that would appreciate it if we did more of that lol!
guys im really getting the same problem now... and i dont know what to do
would you be able to help me please?
I have a Xperia U blocked bootloader rooted and with CWM installed.
I had an ICS .100 ROM installed and working perfectly but I decided I wanted to test Honami Experience ROM. As I had the terminal rooted I just downloaded the Honami Experience V2 ROM for blocked bootloader device, I copied the file to internal storage, I booted to CWM, I did a data/factory reset, wipe cache, wipe dalvik cache, and finally I installed the Honami_Experience_ST25i_v2_LB.zip from SD card.
After the installation finished I rebooted and as described in installation instructions it took some minutes to boot. After that the phone interface is working very smooth but I have lost many functionality: the sim card is not recognized, wifi is not working, cam not working, when I plug USB it is not recognized saying that the drivers can't be installed (in the windows device manager is shown as ST25i but with a warning under other devices), ... So basically the ROM is pretty smooth but useless this way. I'm not sure if I did something wrong though I think it is correct what I did. It is not important anyway just now.
So, my question is, what can I do to restore the mobile. I have already downloaded st25i_6.1.1.b.1.100 generic - user_sony.zip but the problem is that I don't find the way to put it now on the internal memory as the USB connection is not working. I have tried connecting the mass storage from CWM too but with same problem, windows can't install the drivers and in this case in the device manager shows it as Android instead of ST25i but with same warning.
As USB is not working I can't use flashtool to try to restore either.
I'm going to mention too that no matter if I disable the debug mode on the settings, it looks of on the user interface but when I reboot the phone it comes up with debug mode on always.
Any suggestions appreciated. My last solution would be to use bluetooth that seems it is working on the phone. The problem is just in this very moment I have another bluetooth device to send the data and that's why if possible I would like to know of any other way to solve this issue.
Thanks.
You should download file ftf and flash via flashboot mode
flash mode works
After reading another thread I have realized that flash mode works anyway so I have flashed the stock .100 and seems all is working now again.
So I change the question to, What have I did wrong when I installed Honami Experience ROM? I'm not sure what to do when the big Power Off button and Use Phone button appear on screen. I have waited a lot on that screen but maybe I did something wrong. What exactly I have to look at on that screen to be sure all is fine. When I flash the stock .100 I have no problems.
paulsm said:
After reading another thread I have realized that flash mode works anyway so I have flashed the stock .100 and seems all is working now again.
So I change the question to, What have I did wrong when I installed Honami Experience ROM? I'm not sure what to do when the big Power Off button and Use Phone button appear on screen. I have waited a lot on that screen but maybe I did something wrong. What exactly I have to look at on that screen to be sure all is fine. When I flash the stock .100 I have no problems.
Click to expand...
Click to collapse
I'm not sure, I also installed Honami v2 this morning but my phone is UB and it works normally. Have you followed the instructions in the topic, instructions for Lock Bootloader , your phone is ST25a or ST25i. you can do it again and report to the topic's owner
and power off and use phone button, it depends on you. if you are doing something, you can choose use to continue and turn off later
hungminhon said:
I'm not sure, I also installed Honami v2 this morning but my phone is UB and it works normally. Have you followed the instructions in the topic, instructions for Lock Bootloader , your phone is ST25a or ST25i. you can do it again and report to the topic's owner
and power off and use phone button, it depends on you. if you are doing something, you can choose use to continue and turn off later
Click to expand...
Click to collapse
The phone is ST25i locked bootloader. And on the moment I did the test was rooted, it had stock .100 firmware and CWM Touch 5.5.0.4. Taking that into account I just uploaded the Honami v2 zip file (for locked bootloader), I booted into recovery, wiped everything, I installed the zip from SD and rebooted when installation finished.
The only thing I can't be sure if it is wrong to start from .100 firmware (kernel included). Don't know if that is wrong and I must start with .10 kernel.
Now I have it again with .100 firmware, rooted and with CWM Touch 5.5.0.4 so maybe I can just flash .10 kernel and try again the installation of Honami from CWM.
paulsm said:
The phone is ST25i locked bootloader. And on the moment I did the test was rooted, it had stock .100 firmware and CWM Touch 5.5.0.4. Taking that into account I just uploaded the Honami v2 zip file (for locked bootloader), I booted into recovery, wiped everything, I installed the zip from SD and rebooted when installation finished.
The only thing I can't be sure if it is wrong to start from .100 firmware (kernel included). Don't know if that is wrong and I must start with .10 kernel.
Now I have it again with .100 firmware, rooted and with CWM Touch 5.5.0.4 so maybe I can just flash .10 kernel and try again the installation of Honami from CWM.
Click to expand...
Click to collapse
i think you should follow the instructions, flash the .10 kernel first. In UB, I also have to install another kernel to install this rom
hungminhon said:
i think you should follow the instructions, flash the .10 kernel first. In UB, I also have to install another kernel to install this rom
Click to expand...
Click to collapse
I tried and no way even with .10 kernel same exactly problems, no cam, no wifi, no sim recognized, ... Not sure if I'm going to try anymore. Really the stock .100 is smooth enough.
one more test
I tested once more. Just reread the instructions very very carefully.
- The instructions say that you have to start with 6.1.1.B.1.100 so I was doing it correctly from the beggining.
- The instructions say to root with superuser while I was rooting with supersu so in this last test, though I supposed it was not the problem, I decided to use superuser.
Again, same problems, no wifi, no cam, no sim recognized, ..., so I only can imply that Honami Experience doesn't work on locked bootloader.
If someone has tested too and read this and it is working for him in locked bootloader I would be glad to hear how he did it.
I can't ask for help nor notify it in the developer thread because of the limits imposed by xda-developers forums.
Thanks
Glad I saw this post...
I have a locked bootloader as well, and have been wanting to try various ROMS.
Was thinking about trying this one on the weekend, but now I'm not sure.
Currently using JB eXperience V2, it works well and everything works, but I'm always looking for something new to try.
I'm not savvy enough to fix problems, so would rather flash ROMS with few "bugs"
Sorry I know I didn't answer your question, but it certainly answers mine of if I should flash this ROM or not.
I certainly give credit to all the devs on here though, don;t get me wrong! They work hard!
need to re-flash the 6.1.1.B.1.100 firmware or not?
I wanna try it but have some questions.
Now I am currently on zperience 1.0. Can I install this rom on over it or sould re-Flash the 6.1.1.B.1.100 firmware.
smtsth said:
I wanna try it but have some questions.
Now I am currently on zperience 1.0. Can I install this rom on over it or sould re-Flash the 6.1.1.B.1.100 firmware.
Click to expand...
Click to collapse
The instructions say you have to start with 6.1.1.B.1.100 firmware
Always Flash the 6.1.1.B.1.100 firmware before flashing this ROM, then follow instructions
Click to expand...
Click to collapse
Same problems on LB
I have LB and i had the same problems with this rom, the wifi didn't work, the screen didn´t turn off. In fact, the same problems. The owner of the roms told me that they are bugs of the rom, i think he will fix it in the v3. As i see it works perfectly on UB, but i'm not going to unlock the bootloader.
incry2 said:
I have LB and i had the same problems with this rom, the wifi didn't work, the screen didn´t turn off. In fact, the same problems. The owner of the roms told me that they are bugs of the rom, i think he will fix it in the v3. As i see it works perfectly on UB, but i'm not going to unlock the bootloader.
Click to expand...
Click to collapse
Thanks for the info. In my opinion if the owner of the rom knows about all those bugs he should include the info on the rom thread.
The rom thread shows a list of bugs and if those bugs are only the bugs of the unlocked bootloader version he should have explained better.
When I decided to try I thought it was a full operative rom with just the few bugs that we can read on the thread. But wifi not working, sim not detected, screen not turning off, lock screen not working properly, cam not working, ..., are bugs that can't be ignored. With those bugs, even with only one of those, because all of them are imprescindible features, the rom is useless.
same problem
paulsm said:
The phone is ST25i locked bootloader. And on the moment I did the test was rooted, it had stock .100 firmware and CWM Touch 5.5.0.4. Taking that into account I just uploaded the Honami v2 zip file (for locked bootloader), I booted into recovery, wiped everything, I installed the zip from SD and rebooted when installation finished.
The only thing I can't be sure if it is wrong to start from .100 firmware (kernel included). Don't know if that is wrong and I must start with .10 kernel.
Now I have it again with .100 firmware, rooted and with CWM Touch 5.5.0.4 so maybe I can just flash .10 kernel and try again the installation of Honami from CWM.
Click to expand...
Click to collapse
incry2 said:
I have LB and i had the same problems with this rom, the wifi didn't work, the screen didn´t turn off. In fact, the same problems. The owner of the roms told me that they are bugs of the rom, i think he will fix it in the v3. As i see it works perfectly on UB, but i'm not going to unlock the bootloader.
Click to expand...
Click to collapse
same problem here. I Just tried 2 times but the problem is same... so waiting for v3
Ive been reading about the need and importance to backup the TA Partition. Earlier I had it backed up on my C Drive but later when reverting back to windows 7 i accidentally formatted the backup along with it. So anyways, I had unlocked the booloader which basically wiped out clean all my personal data, then installed TWRP and wiped out the phone and flashed PA Rom to try it out. So later went back to stock using Flashtool app, everything went smooth and all apps are still working as it should. I was able to use Walkman app, Bravia Engine still works, OTA works, etc. So what exactly am I missing by not backing up the TA Partition? Ive come from Nexus line so please excuse me if I come as a bit naive lol. Any response is appreciated.
bushako said:
Ive been reading about the need and importance to backup the TA Partition. Earlier I had it backed up on my C Drive but later when reverting back to windows 7 i accidentally formatted the backup along with it. So anyways, I had unlocked the booloader which basically wiped out clean all my personal data, then installed TWRP and wiped out the phone and flashed PA Rom to try it out. So later went back to stock using Flashtool app, everything went smooth and all apps are still working as it should. I was able to use Walkman app, Bravia Engine still works, OTA works, etc. So what exactly am I missing by not backing up the TA Partition? Ive come from Nexus line so please excuse me if I come as a bit naive lol. Any response is appreciated.
Click to expand...
Click to collapse
pre 4.4 it would break track ID and x-reality, it does look as if Sony have fixed these 'bugs'. A valid TA may/is still needed to get the phone repaired under warranty
blueether said:
pre 4.4 it would break track ID and x-reality, it does look as if Sony have fixed these 'bugs'. A valid TA may/is still needed to get the phone repaired under warranty
Click to expand...
Click to collapse
Don't mean to sound rude but can you please provide a source of this info? I've done searches and this hadnt come up. Also how does one check the validity of the TA?
I unlocked my boot loader the first day I got my Xperia Z Ultra, and destroyed the TA not having made a backup.
I've never missed what I never had. I don't use the Sony music or video service so I can't tell you if they would be broken due to the lack of DRM keys,and I've never had any app complain they're missing.
In the very early days the Sony Camera App would force close, but I switched to A Better Camera app, later versions of the stock ROM didn't have the problem.
Overall then, don't panic, they don't matter.
hey thanks for the reply. Ive got everything still working as it should so as mentioned by the earlier poster id agree its only an issue with pre kitkat roms and perhaps for warranty purpose.
speculatrix said:
I unlocked my boot loader the first day I got my Xperia Z Ultra, and destroyed the TA not having made a backup.
I've never missed what I never had. I don't use the Sony music or video service so I can't tell you if they would be broken due to the lack of DRM keys,and I've never had any app complain they're missing.
In the very early days the Sony Camera App would force close, but I switched to A Better Camera app, later versions of the stock ROM didn't have the problem.
Overall then, don't panic, they don't matter.
Click to expand...
Click to collapse
Hi! I got my Sony Z2 (or Sirius) a bit ago, August. After about two to three weeks of using it, I decided that I didn't like the design, and so I spent a day or two researching everything on it before flashing Cyanogenmod.
I've gone through Cyanogenmod and Carbon ROM. Both excellent ROMs! I miss my high quality camera and my excellent audio though... Although I did end up installing Viper4Audio or whatever its called, the amazing EQ, I do miss Walkman and its superior sound quality.
So, Ive been wanting to revert back to the stock ROM. That's where I'm stuck. I don't know what ROM to flash, or what build etc. I also don't know when I should do my TA Partition restore, after or before the flash? I'm not too tech-savvy android wise.
Thanks guys, love you all and the amazing forums here.
All help appreciated!
(I have attached myI'vebout Phone' section of my settings and proof of my TA backup. The TA backup is on my phone cause I kept a spare copy on my phone incase my computer broke... Luckily I did, cause my PC did break. I've got a new one now so its all good.)
xphiles said:
Hi! I got my Sony Z2 (or Sirius) a bit ago, August. After about two to three weeks of using it, I decided that I didn't like the design, and so I spent a day or two researching everything on it before flashing Cyanogenmod.
I've gone through Cyanogenmod and Carbon ROM. Both excellent ROMs! I miss my high quality camera and my excellent audio though... Although I did end up installing Viper4Audio or whatever its called, the amazing EQ, I do miss Walkman and its superior sound quality.
So, Ive been wanting to revert back to the stock ROM. That's where I'm stuck. I don't know what ROM to flash, or what build etc. I also don't know when I should do my TA Partition restore, after or before the flash? I'm not too tech-savvy android wise.
Thanks guys, love you all and the amazing forums here.
All help appreciated!
(I have attached myI'vebout Phone' section of my settings and proof of my TA backup. The TA backup is on my phone cause I kept a spare copy on my phone incase my computer broke... Luckily I did, cause my PC did break. I've got a new one now so its all good.)
Click to expand...
Click to collapse
you can use flashtool from flashtool.net and a FTF(top of general section) to revert to total stock
just run the script to restore your TA Partition backup, it will relock your bootloader( try looking at the fourm thread you use to backup your TA)
I don't know what version to install, when I got my phone it WAS unlocked, came with a Telstra sim but I use an Optus sim now. I don't know what to do, or what version to download...
Scratch that. I'm just going to use the latest Australian Unbranded version. If I get a ****ed up Kernel again or something, at least I'll know how to fix it this time due to previous trial and error after flashing the wrong thing All praise Doomlord's kernel ahaha
Soft bricked!
Soft bricked my device. (Something in-between hard and soft? Screen doesn't come on like in soft brick, but it isn't hard bricked. I got this after restoring a backup [I did that last time and got the same result].) Great, now I have to flash another kernel over and do the FTF. I can only access fastboot as far as I'm concerned, but that's good, I can at least flash things!
Great! Fixed my phone. Well, partially. When I attempt to restore my TA Partition backup... the CMD window doesn't come up with any options... ? It's as if it's just backing up? I don't know. It doesn't seem to be doing anything at all, neither does it make an actual backup file. All it does is create a few files in the folder the .bat is in, and when it's done deletes them...
Hello dear helpers.
Today I tried to restore my CM11_M12 from a backup I made last night.
That did not work out, saying restoring system and data failed.
At first I though it was just a bad backup, so I flashed .314, restored TA (really dont know why...) and upgraded to .167
Now after unlocking the BL again, I can flash boot.img from CM11, but not boot to it, or boot to system at all.
All the device does is to vibrate slightly, and then nothing else... Is that the sign of soft brick?
Then flashing .314 fw. will bring me back to Stock and working...
It seems like it became what I will name it, Stock-bricked...
A little more info what I did before trying to restore CM:
After backing up my phone last night, I flashed this file, and the device seemed fine. all ex. messaging did not open this morning when I received a SMS
So I though that it messed up and therefore I tried to restore CM, and that causing error...
Hope some one can help me with this, and hopefully fast too, because now I cannot receive any SMS or calls because i forgot the adapter for my SIM-card at home... :crying:
Maybe @Envious_Data?
After some tampering around, I figured I would do the whole progress over again, and that means
-Lock BL
-Flash FTF
-Boot
-Shutdown
-Unlock and now it works. :laugh:
wow didnt see that mention
anyways word of advice
flashtool is your freind