Database Users

Updated to ICS -- Slightly Laggy Help

I have updated to ICS via OTA.
Now, if i open keypad to dial it first shows grey screen for 2seconds and then the numbers appears... Same with contacts.
I also got couple of times black screen as if phone frooze.
Once, even i got scrambled green images on screen which got corrected by pressing Home button multiple times.
Apart from this, Phone seems to be running fine.
So, how can i myself solve this problem now OR Do i have to go to Samsung service centre and let them reinstall ICS?
PS:
I am using Indian official ICS Baseband Ver. LP4 & Build Number LP8.
I have never rooted and was on Stock GB before the urgrade.
I fear if i try to fix this ICS problem myself i will run into bricking problem.
UPDATE
See post 7 & 13 Below

I had this issue but after i wired data using code *2767*3855# everything worked smoothly.
You can try this at your own risk as it might brick if yor device has emmc bug. I have already done it over 15 times and no issue
Sent from my GT-N7000 using XDA

olivespin said:
I have updated to ICS via OTA.
Now, if i open keypad to dial it first shows grey screen for 2seconds and then the numbers appears... Same with contacts.
I also got couple of times black screen as if phone frooze.
Once, even i got scrambled green images on screen which got corrected by pressing Home button multiple times.
Apart from this, Phone seems to be running fine.
So, how can i myself solve this problem now OR Do i have to go to Samsung service centre and let them reinstall ICS?
PS:
I am using Indian official ICS Baseband Ver. LP4 & Build Number LP8.
I have never rooted and was on Stock GB before the urgrade.
I fear if i try to fix this ICS problem myself i will run into bricking problem.
Click to expand...
Click to collapse
I rooted my Note after about two days so not sure if this will work on non-root....
Reboot into recovery (Power+Vol Up + Home) then clear cache and clear Dalvik cache. Reboot then see if lag continues. Clearing caches and reboot seems to get rid of lags and gives phone a new life

Today again phone got frooze on homescreen for 5mins and got back to life again after pressing Home key numerous times
So yes, something is wrong with this ICS update.
Plz provide a solution and also mention if tht solution can lead to bricking bug..

BUMP.

I had exactly the same problems while updating Gb to ICS using OTA update. Anywhow, I never got to fix this. I would try following steps:
Clean the cache of your ICS installations/apps using any Cache-cleaning tool on the Play Store
Reboot your phone like 2-3 times (sometimes this seems to fix some problems with your kernel/rom since they have to settle down.
Update all your apps to their latest versions, since most apps have fixes for ICS installations, and might slow your phone a bit down in some way
Click to expand...
Click to collapse
When you still would have problems with your ICS installations I would recommend installing a custom rom over your stock ICS installation. This did the trick for me eventually.. But depends on if you would like to have a stock or custom ICS rom.

HELP
I tried the above suggestion and done Factory Format via *2767*3855#.
Now, after entering code the device havent rebooted for the next 15mins, so i pressed the power key to reboot manually and then i got the message format failed or sumthing similar which i dont seem 2 recall.
Now, all my Smemo data & camera images is wiped... but phone numbers and messages intact.
and the originally mentioned problem is still there..... So wht is my solution now ?
I want to delete every old system files & Clean-install ICS - So Is it via kies?
Dont know much abt all this so a detailed help would be highly appreciated.

olivespin said:
I have updated to ICS via OTA.
Now, if i open keypad to dial it first shows grey screen for 2seconds and then the numbers appears... Same with contacts.
I also got couple of times black screen as if phone frooze.
Once, even i got scrambled green images on screen which got corrected by pressing Home button multiple times.
Apart from this, Phone seems to be running fine.
So, how can i myself solve this problem now OR Do i have to go to Samsung service centre and let them reinstall ICS?
PS:
I am using Indian official ICS Baseband Ver. LP4 & Build Number LP8.
I have never rooted and was on Stock GB before the urgrade.
I fear if i try to fix this ICS problem myself i will run into bricking problem.
Click to expand...
Click to collapse
Facing the EXACTLY the same problem man.. Feel i have done a mistake by upgrading to ics
Sent from my GT-N7000 using xda premium

androidlover1 said:
Facing the EXACTLY the same problem man.. Feel i have done a mistake by upgrading to ics
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Somebody give us proper solution to this.. HELP!
Sent from my GT-N7000 using xda premium

Flash gingerbread again with odin, then do a factory reset... then upgrade to ics again using odin...

I dont want to go to GB again..... All i want is fresh clean install of ICS on my phone... So how to do tht ? (i dont wana play with my phones warrenty)

You can use pc odin to flash stock ics, not recommended though as you're on ics kernel now. Best to follow previous poster, fladh gb stock kernel first.
please hit thanks if i helped

SpyderTracks said:
You can use pc odin to flash stock ics, not recommended though as you're on ics kernel now. Best to follow previous poster, fladh gb stock kernel first.
Click to expand...
Click to collapse
If i use odin to flag GB first, will i loose my phones warrenty? (And i dont even knw how 2 use it)
Second, can i go 2 samsung service centre and let them delete all old files and install fresh copy of ICS? If i do, will i run a chance of bricking..... Coz i dont want to run into parts replacements and repairs problem...
What is the best solution now.

olivespin said:
If i use odin to flag GB first, will i loose my phones warrenty? (And i dont even knw how 2 use it)
Second, can i go 2 samsung service centre and let them delete all old files and install fresh copy of ICS? If i do, will i run a chance of bricking..... Coz i dont want to run into parts replacements and repairs problem...
What is the best solution now.
Click to expand...
Click to collapse
Since you did nothing wrong that could void your warranty, and you don't know too much about fixing it yourself, save yourself the hassle and let a Service center take cre of it for you .

N7000 Official JB Bootloop - "3x Bombardment Odin Flash" simply works!!

I have first mentioned the problem here
Discussion - Stuck at Sammy Logo Issue on Official Jellybean ROMs
Mates, the problem is there, we should admit that, had it on Galactus rom twice ( reflashed the rom again after full wipes to make sure ), and had it also on the stock LSZ with its stock kernel, and also on Cassie's rom.
Nothing solves the problem apart from wiping data.
Is it the preload ? the kernel ? defective JB from Samsung ? I really don't know.
The only thing I would really like to mention is that on Stock and Cassie's rom, had the issue surprisingly occuring on odd restarts not the even ones ! the first restart gets stuck, the other goes on !
Tried all the tricks in the book (restart to recovery, reinstalling bootloader, overinstalling the same rom, wiping everything keeping data, nothing worked.
Unless data gets wiped, the problem persists.
BTW, I had the same problem on all the previous leaked versions before the official ones.
Click to expand...
Click to collapse
The method was first described here and here by RbbCHan
Then suggested to me by kopitalk
Hi mate, finally I resolved this issue by following http://forum.xda-developers.com/show...postcount=2344 and http://forum.xda-developers.com/show...postcount=2347.
Now no matter I hard reset or reboot from recovery, I got no boot stuck anymore! Cheers mate!!!
Click to expand...
Click to collapse
So here is what I have done " a step by step guide"
1-on a safe kernel, do all wipes+formats 9system,data, and preload".
2-reboot into DOWNLOAD mode.
3-connect your N7000 to PC (I use PC Odin V. 3.04).
4-start PC ODIN, untic "Automatic Reboot"
5-flash stock official LSZ rom
6-when you see the word "PASS", restart into DOWNLOAD MODE ( holding vol down+home+power).
7-reflash again.
8-when you see the word "PASS", restart into DOWNLOAD MODE ( holding vol down+home+power).
8-reflash again (3rd time)
9-restart you phone.
10-let the rom settle down, do your settings.
11-do a couple of restarts (legitimate ones, not by holding power for 7secs).
12-root your rom with the latest PhilZ LSZ kernel
13-restart into recovery, format data only "under mount and storage", then restart your phone.
Installed eybee's rom with mods, restarted automatically after mod3, and right now I am with a JB rom that does not stuck at sammy logo even when I force restart pressing the power button for 7 sec.
If you feel it takes a longer time on Sammy N7000 Logo, just repress power button again for 7 secs and it will boot up.
Hope this helps anyone who suffered bootloops as I did.

Have you taken out the battery while Note was on? That's what causing bootloops, just rebooting not necessarily.

Will try and report...:fingers-crossed::fingers-crossed:
---------- Post added at 01:32 PM ---------- Previous post was at 01:28 PM ----------
on 13rd steep should I wipe data/factory reset or format data under mount and storage?

zai89 said:
Will try and report...:fingers-crossed::fingers-crossed:
---------- Post added at 01:32 PM ---------- Previous post was at 01:28 PM ----------
on 13rd steep should I wipe data/factory reset or format data under mount and storage?
Click to expand...
Click to collapse
mount and storage mate..

the JB bootloader will help and are they missing in ur step?

arinsms said:
the JB bootloader will help and are they missing in ur step?
Click to expand...
Click to collapse
its in step 5 - the official rom has the JB bootloader sbi.bin

though I'm crossing fingers that this will work for everyone, but i doubt....this is completely weird from any logical point of view (especially these 3 flashes in a row...what will be flashed on 2nd or 3rd attempt that wasn't flashed before??)...but hey...if it works, ok

Your forgot step 14: turn around yourself 3 times spitting every turn in your preferred direction.
Sorry but I have to ask: is this still a developer forum with a technical/scientifical approach for problems and solutions?
Superstition reigns...

AW: N7000 Official JB Bootloop - "3x Bombardment Odin Flash" simply works!!
If I would have the bootloop problem (actually I never faced any) I would definitely give this a try. Superstition or not, doesn't matter if it solces the problem, right?
Sent from my GT-N7000 using xda premium

ThaiDai said:
Your forgot step 14: turn around yourself 3 times spitting every turn in your preferred direction.
Sorry but I have to ask: is this still a developer forum with a technical/scientifical approach for problems and solutions?
Superstition reigns...
Click to expand...
Click to collapse
This is really silly of you. We are all trying to figure out a solution even if a temporary one which might help hundreds if not thousands who are trying to use their phones promptly and who regret buying this n7000 with the famous ics brick bug and now the unstable jb roms which are OFFICIAL SAMSUMG RELEASES.
To all, there really should be a 'counter' somewhere, which explains the 'every other restart' that succeeds and does not cause the n7000 to get stuck.
Sent from my GT-N7000 using Tapatalk 2

essentially we are just ensuring the new image sticks
coz there may not be a way to verify which bootloader we actually have even after first flash

ThaiDai said:
Your forgot step 14: turn around yourself 3 times spitting every turn in your preferred direction.
Sorry but I have to ask: is this still a developer forum with a technical/scientifical approach for problems and solutions?
Superstition reigns...
Click to expand...
Click to collapse
Shame on you... We may not know what's behind doing it but it works. I hope you will get this broplem so that you will swallow your saliva back.

I'm not ashamed and I do not feel silly because of my statement.
It's only my point of view and so I still think this is ridiculous.
If any member is positive about the results my comments never will change it.
But that won't stop me from commenting when rationality moves to the far side of the moon.

I don't know if it works; installing the bootloader seems to work too to avoid soft reboot bootloops. But when I take out the battery while the Note is on I get the bootloop.
J, have you taken out the battery to test if it works? That's what I'm interested in right now.

Why does anyone take there battery out while the phone is on!? Can one magically change the batteries without switching off the phone?

dio62000 said:
I don't know if it works; installing the bootloader seems to work too to avoid soft reboot bootloops. But when I take out the battery while the Note is on I get the bootloop.
J, have you taken out the battery to test if it works? That's what I'm interested in right now.
Click to expand...
Click to collapse
Ues, I have just done that replacing my stock battery with my 5000mAh, and it has worked just fine.
Sent from my GT-N7000 using Tapatalk 2

Sometimes you need to take your battery out, e.g. when you have a crash and nothing responds to buttons or touch anymore. I won´t happen too often, but once is enough to get really annoyed, because this always happens when you least expect it.

dio62000 said:
I don't know if it works; installing the bootloader seems to work too to avoid soft reboot bootloops. But when I take out the battery while the Note is on I get the bootloop.
J, have you taken out the battery to test if it works? That's what I'm interested in right now.
Click to expand...
Click to collapse
Yes, I have just done that replacing my stock battery with my 5000mAh and it has worked just fine.
Sent from my GT-N7000 using Tapatalk 2

Ok, so you didn´t first shut off the phone, you took out the battery while it was still on? Now that may be interesting...

dio62000 said:
Sometimes you need to take your battery out, e.g. when you have a crash and nothing responds to buttons or touch anymore. I won´t happen too often, but once is enough to get really annoyed, because this always happens when you least expect it.
Click to expand...
Click to collapse
If a system freeze occurs, you don't have to pull the battery. You can long-press the power button and voila, reboob™ takes place!
How do you guys call this... soft reboot, soft reset...?

Out of Box System Update

FYI, there are two system updates, one as soon as you connect to wifi during setup and then another after you get to the desktop. The second update says it's going to "upgrade your Nexus 7 to Android 4.3" even though it's already on 4.3.
After the first update, I'm on:
Android 4.3
Kernel 3.4.0-g1f57c39, [email protected] #1, Thu June 13 16:35:05
Build JWR66N
After the second update it's:
Kernel 3.4.0-g365a6e0, [email protected] #1, Thu July 18 17:10:40
Build JSS15J
Didn't get the info from it OOB though.

Yeah I had the same thing on mine. One update when I connected to WiFi, it installed and rebooted, then I went to Software Update, and it downloaded and instaleld another ~50meg update. They were all called 4.3

I cannot get mine to update past JWR66N. It rebooted to install the JSS15J update and errored (not a word) in recovery.
Force checking for system update shows it is fully updated
Edit: Went to Apps > All > Google frameworks > Force Closed it back to System update and it showed up again.
Edit 2: Even tried to sideload the update in recovery and it gives me a Status 7 because the sha-1 sums don't match for PrebuiltGmsCore.apk.....even though I haven't altered the system.

I hesitated at first until I already saw it was 4.3 out of the box. If it was 4.2 it would of been easier to root. But no, like Google said, 4.3 out of the box
Sent from my Nexus 7 using Tapatalk 4 Beta

For anyone who wants it, here is the download for JWR66N to JSS15J. Pulled it from logcat.
http://android.clients.google.com/p....signed-razor-JSS15J-from-JWR66N.204daaac.zip

same here.
question about 4.3
not sure how long its been doing these things (been on custom ROM's for a while on my old N7)
CRT screen off animation is in tablets now. i remember 4.2.2 just fading to black. is this new?
and expandable volume controls. tap the volume button and you get alert volume with a settings button next to it to open up both notification AND media volumes. this has been on custom ROM's for a while now, just wondering if stock 4.2.2 had this as well.

Nburnes said:
I cannot get mine to update past JWR66N. It rebooted to install the JSS15J update and errored (not a word) in recovery.
Force checking for system update shows it is fully updated
Edit: Went to Apps > All > Google frameworks > Force Closed it back to System update and it showed up again.
Edit 2: Even tried to sideload the update in recovery and it gives me a Status 7 because the sha-1 sums don't match for PrebuiltGmsCore.apk.....even though I haven't altered the system.
Click to expand...
Click to collapse
I too have the error on that second update . Just android guy laying down with "error". Still stuck on JWR66N.

bobafuzz said:
I too have the error on that second update . Just android guy laying down with "error". Still stuck on JWR66N.
Click to expand...
Click to collapse
Same thing here, and I seem to be missing the wallpaper that is displayed on the box, which seems really weird to me

bobafuzz said:
I too have the error on that second update . Just android guy laying down with "error". Still stuck on JWR66N.
Click to expand...
Click to collapse
It happened to me with the original nexus 7. What helped me was doing factory reset and then upgrading. Let me know it that helped

Definitely take the JSS15J update. It makes the tablet way smoother. I was pretty disappointed with JWR66N (sluggish etc.) and it had a buggy camera app that crashed the whole device.

Dimon1990 said:
It happened to me with the original nexus 7. What helped me was doing factory reset and then upgrading. Let me know it that helped
Click to expand...
Click to collapse
Restored multiple times
Tried the whole wiping with fastboot oem lock/unlock
Wiped /data and /cache in recovery
Nothing for me until they release the stock images...which could be days.

Dimon1990 said:
It happened to me with the original nexus 7. What helped me was doing factory reset and then upgrading. Let me know it that helped
Click to expand...
Click to collapse
Factory reset didn't work for me, even tried it with relocked bootloader still fail. I guess I'll have to wait for the factory image.

What about flashing the OTA through adb using fastboot? I know that with the 4.2.2 stock Nexus 4 image, the ./flash-all.sh script has
Code:
fastboot -w update image-occam-jwr66v.zipam-jwr66v.zip
in it, so maybe we need to do
Code:
fastboot -w update 204daaac1ba01d973567d2fa1d96d82246dd82b9.signed-razor-JSS15J-from-JWR66N.204daaac.zip
Would that work, or is this all above my head?

Mine actually came unlocked out of the box which was weird but w/e. What I need is the tablet HBO go apk to see if it'll sideload
Sent from my Nexus 7 using Tapatalk 4 Beta

turdbogls said:
same here.
question about 4.3
not sure how long its been doing these things (been on custom ROM's for a while on my old N7)
CRT screen off animation is in tablets now. i remember 4.2.2 just fading to black. is this new?
and expandable volume controls. tap the volume button and you get alert volume with a settings button next to it to open up both notification AND media volumes. this has been on custom ROM's for a while now, just wondering if stock 4.2.2 had this as well.
Click to expand...
Click to collapse
Both of those are new on 4.3

Anyone find a solution to this? I'm having the same problem. First update was fine (and instant). Second update continues to fail.
Tried resetting framework and it immediately downloads it and fails again.
First fail allowed me some menu options. Second fail was frozen.

Nburnes said:
Restored multiple times
Tried the whole wiping with fastboot oem lock/unlock
Wiped /data and /cache in recovery
Nothing for me until they release the stock images...which could be days.
Click to expand...
Click to collapse
Try pulling up the logcat, it probably is a kext error. It would be easier with TWRP or other recovery, not sure how to go about it in stock
---------- Post added at 11:47 PM ---------- Previous post was at 11:46 PM ----------
phonic said:
Anyone find a solution to this? I'm having the same problem. First update was fine (and instant). Second update continues to fail.
Tried resetting framework and it immediately downloads it and fails again.
First fail allowed me some menu options. Second fail was frozen.
Click to expand...
Click to collapse
Sounds like the problem with the original nexus 7. Wait for images to be released and reflash the stock, then upgrade

phonic said:
Anyone find a solution to this? I'm having the same problem. First update was fine (and instant). Second update continues to fail.
Tried resetting framework and it immediately downloads it and fails again.
First fail allowed me some menu options. Second fail was frozen.
Click to expand...
Click to collapse
My only solution was going to bestbuy and grabbed a different one. I noticed I was missing that wallpaper, the multi-color diagonal line one. The new one from best buy seems to be flashing fine with no errors, and that wallpaper is also there. I'm guessing someone tripped over a cord when they were flashing a batch of N7.

bobafuzz said:
My only solution was going to bestbuy and grabbed a different one. I noticed I was missing that wallpaper, the multi-color diagonal line one. The new one from best buy seems to be flashing fine with no errors, and that wallpaper is also there. I'm guessing someone tripped over a cord when they were flashing a batch of N7.
Click to expand...
Click to collapse
Hrmmmm.... Mind doesn't have that wallpaper either.
I don't think I'm going to return it unless I absolutely have to. If it's just a bad flash, then a full flash of the factory images (once available) should fix it.

Nburnes said:
I cannot get mine to update past JWR66N. It rebooted to install the JSS15J update and errored (not a word) in recovery.
Force checking for system update shows it is fully updated
Edit: Went to Apps > All > Google frameworks > Force Closed it back to System update and it showed up again.
Edit 2: Even tried to sideload the update in recovery and it gives me a Status 7 because the sha-1 sums don't match for PrebuiltGmsCore.apk.....even though I haven't altered the system.
Click to expand...
Click to collapse
Dimon1990 said:
Try pulling up the logcat, it probably is a kext error. It would be easier with TWRP or other recovery, not sure how to go about it in stock
---------- Post added at 11:47 PM ---------- Previous post was at 11:46 PM ----------
Sounds like the problem with the original nexus 7. Wait for images to be released and reflash the stock, then upgrade
Click to expand...
Click to collapse
No it is as I said there, a sum mismatch on PrebuiltGmsCore.apk.

[Q] Flashed custom ROM, can't boot past battery charging icon

Hey folks,
So I've been fiddling with a few custom ROMs trying to find a stock Android ROM that doesn't drain my battery like crazy. I was quite excited about the one found here:
http://forum.xda-developers.com/showthread.php?t=2341026&highlight=i337
But while it flashes successfully and the battery icon switches from the stock Samsung one to the AOSP one, for whatever reason long-holding the power button boots only to the Samsung battery icon again before it switches back to the AOSP. I can still boot into recovery and switch ROMs, restore, etc., but for whatever reason I can't even boot to the Samsung logo with this ROM.
Is there any specific reason as to why this might happen, and anything I can do short of just trying another ROM?
Thanks.

Also it seems like every time I install a GPE ROM, as soon as I boot the phone and login, Google Play starts IMMEDIATELY downloading and installing all my old apps without me even asking it to. I literally can't stop it unless I force stop and disable Android Download Manager.
Any ideas?
Thanks in advance.

Gentle bump.

cleanup said:
Also it seems like every time I install a GPE ROM, as soon as I boot the phone and login, Google Play starts IMMEDIATELY downloading and installing all my old apps without me even asking it to. I literally can't stop it unless I force stop and disable Android Download Manager.
Any ideas?
Thanks in advance.
Click to expand...
Click to collapse
The reason why that happens is because you signed in to the play stir upon booting up your rom.. When you do that it restores all your apps and stuff...
Sent From My BeastS4
---------- Post added at 11:36 PM ---------- Previous post was at 11:35 PM ----------
cleanup said:
Hey folks,
So I've been fiddling with a few custom ROMs trying to find a stock Android ROM that doesn't drain my battery like crazy. I was quite excited about the one found here:
http://forum.xda-developers.com/showthread.php?t=2341026&highlight=i337
But while it flashes successfully and the battery icon switches from the stock Samsung one to the AOSP one, for whatever reason long-holding the power button boots only to the Samsung battery icon again before it switches back to the AOSP. I can still boot into recovery and switch ROMs, restore, etc., but for whatever reason I can't even boot to the Samsung logo with this ROM.
Is there any specific reason as to why this might happen, and anything I can do short of just trying another ROM?
Thanks.
Click to expand...
Click to collapse
I don't understand this part...
Sent From My BeastS4

cleanup said:
Hey folks,
So I've been fiddling with a few custom ROMs trying to find a stock Android ROM that doesn't drain my battery like crazy. I was quite excited about the one found here:
http://forum.xda-developers.com/showthread.php?t=2341026&highlight=i337
But while it flashes successfully and the battery icon switches from the stock Samsung one to the AOSP one, for whatever reason long-holding the power button boots only to the Samsung battery icon again before it switches back to the AOSP. I can still boot into recovery and switch ROMs, restore, etc., but for whatever reason I can't even boot to the Samsung logo with this ROM.
Is there any specific reason as to why this might happen, and anything I can do short of just trying another ROM?
Thanks.
Click to expand...
Click to collapse
You may have downloaded a corrupted version. Try dowloading again and flashing. My also need latest recovery for 4.3 ROMs to work
---------- Post added at 12:28 PM ---------- Previous post was at 12:27 PM ----------
cleanup said:
Also it seems like every time I install a GPE ROM, as soon as I boot the phone and login, Google Play starts IMMEDIATELY downloading and installing all my old apps without me even asking it to. I literally can't stop it unless I force stop and disable Android Download Manager.
Any ideas?
Thanks in advance.
Click to expand...
Click to collapse
Just go into Play, My Apps and manually stop it downloading there. Shouldn't start up again for that installation.

CyanogenMod experimental official for honami!

I've noticed that on official CyanogenMod download page there are two experimental builds for honami!
Let the party begin!
http://download.cyanogenmod.org/?device=honami

orzech.miron said:
I've noticed that on official CyanogenMod download page there are two experimental builds for honami!
Let the party begin!
http://download.cyanogenmod.org/?device=honami
Click to expand...
Click to collapse
Would you give us some feedback how this rom perfoms?

Cpt.Schaaf said:
Would you give us some feedback how this rom perfoms?
Click to expand...
Click to collapse
I don't have my bootloader unlocked so I can't flash it :/ But I think that there will be a lot of people who will check this out

Look at the thread in the dev section dude
Kali- said:
know issue are:
* camcorder (fixed but not released)
* data (data must be disabled to make call)
* gps
Click to expand...
Click to collapse

orzech.miron said:
I don't have my bootloader unlocked so I can't flash it :/ But I think that there will be a lot of people who will check this out
Click to expand...
Click to collapse
I am new here but I thought we could flash CWM even with a locked bootloader and thus install any ROMs :-S
Sent from my C6903 using XDA Premium 4 mobile app

eightace said:
I am new here but I thought we could flash CWM even with a locked bootloader and thus install any ROMs :-S
Sent from my C6903 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Bootloader has to be unlocked to flash a new kernel. And the recovery doesn't have permissions to overwrite the kernel so you have to boot into flash mode (or fastboot???) which requires an unlocked bootloader.
I am tempted to flash this though but I'm not exactly ready to unlock my bootloader yet

Woo! Now all we need is a non-convoluted way to root 4.3 and we're set.

kantk20111 said:
Woo! Now all we need is a non-convoluted way to root 4.3 and we're set.
Click to expand...
Click to collapse
Convoluted?
Just unlock bootloader -> flash any kernel with recovery -> flash CM

RyokoN said:
Convoluted?
Just unlock bootloader -> flash any kernel with recovery -> flash CM
Click to expand...
Click to collapse
Maybe he means backup TA direct from 4.3?

TheCraig said:
Bootloader has to be unlocked to flash a new kernel. And the recovery doesn't have permissions to overwrite the kernel so you have to boot into flash mode (or fastboot???) which requires an unlocked bootloader.
I am tempted to flash this though but I'm not exactly ready to unlock my bootloader yet
Click to expand...
Click to collapse
Oh it can overwrite the kernel alright, but a locked bootloader will only boot kernels signed with Sonys private key, which we can't get.

Rom is very fast
Camera work lag 3 sec on start
Bt work

RyokoN said:
Convoluted?
Just unlock bootloader -> flash any kernel with recovery -> flash CM
Click to expand...
Click to collapse
Hmm is there an easy way to root 4.3 yet? I mightve missed it.

kantk20111 said:
Hmm is there an easy way to root 4.3 yet? I mightve missed it.
Click to expand...
Click to collapse
No.

My first Test
Tested just a few minutes now ...
Hardware: C6903 with unlocked BL
wiped everything, flashed Cm11 Experimental and it flashed the full system AND a new kernel "3.4.0cyanogenmod-g8402fcb"
flashed no gapps for now, as this is just a quick test ...
First boot without problems, camera works (little bit unstable but works), wifi works, modem works (tmobile de at full signal)
UI themes to be very fast and stable
RAM-Usage / -free : 754MB / 0,92GB
Internal Storage usage / free : 192MB / 12GB
NFC is on but doesnt seem to work, but not enough tested -> need to have a look on it
Mobile Data (3G AND E) is keeping the modem to reset (signal -> 0 (think it's turned off) and then starts up again with full signal, as 3G or E is displayed it turns off again) if i turn wifi on and no mobile data is active, the signal stays constant (taken a call allready, works fine)
So far ... if mobile data is working, this may be a nice build for "nearly daily test usage" ...

Hello, I just unlocked my Z1 3 days ago and Im testing the new experimental ROM.
I would like to support you by letting you know the problems I realized this ROM has:
1.- data traffic doesnt work and also, if activated, makes you cannot send or receive any calls or sms because it makes the network fail. (I think this is the most important bug).
2.- Locator or GPS doesnt work at all.
3.- Camera works but it takes over 3-4 seconds to start working. Also the video cam make it crashes. Video cam doesnt work at all.
4.- Torch doesnt work nor the app neither when making pictures.
5.- I cannot volume down the music when headphones are connected.
6.- The buzz or sound when you push any icon, app, main manu button, etc, crashed once to me and it sounds so horrible, I had to shut the system down and boot it again to sort it out.
7.- There is no option to make our network works as 2G; there is only option to run as 3G.
8.- I got some problems while trying to restore all my contact I had by copying them from the SIM card and from the SD card; I finally achieved it going to the file explorer and running manually the file which contents the backup of my contacts.
9.- There's no options menu into the screen where are shown all the app's in order to sort them as most used, alphabetically, etc.
NEW ADDED: 10.- It doesnt unmount the SD card or seems like it doesnt.
NEW ADDED (2): 11.- There is no option to save the pictures and videos made with the camera directly in the SD Card. Also no option to move the pictures and videos in the internal storage to the SD Card.
I think the 5 first points are the most important, but the most one is the first one. That's my opinion about preferences.
Anyway, thanks for this new great job.
Im just waiting for an update impaciently.
Regards.

Hey,
I unlocked my boot loader recently and have begun testing the experimental roms. After the previous post I waited until the latest one was released to test it out. I can confirm that the data problems have been resolved and have been using this rom for the past few days.
The main problems I have encountered are:
- Videos within apps such as Facebook or trailers on IMDB play however the picture is corrupted.
- Occasionally apps will randomly close most of the time its the internet browser (no error, it just closes)
- The camera still lags and isn't fluid at all however takes pictures fine.
I think overall there is definitely room for improvement however I have been using it fine for the last few days and it seems quite stable overall.
One problem I did have and I don't know if anyone can help me with it was that I flashed the rom with TWRP however upon rebooting into the new version of CM my recovery was CWM.

Rostitute said:
Hey,
I unlocked my boot loader recently and have begun testing the experimental roms. After the previous post I waited until the latest one was released to test it out. I can confirm that the data problems have been resolved and have been using this rom for the past few days.
The main problems I have encountered are:
- Videos within apps such as Facebook or trailers on IMDB play however the picture is corrupted.
- Occasionally apps will randomly close most of the time its the internet browser (no error, it just closes)
- The camera still lags and isn't fluid at all however takes pictures fine.
I think overall there is definitely room for improvement however I have been using it fine for the last few days and it seems quite stable overall.
One problem I did have and I don't know if anyone can help me with it was that I flashed the rom with TWRP however upon rebooting into the new version of CM my recovery was CWM.
Click to expand...
Click to collapse
CM auto installs CWM as this is what it uses instead of TWRP
I have just moved from a HTC One (which I modded and flashed a lot of ROM's) to Xperia Z1 C6903 but unrooted etc atm
I will be checking things out in the next few weeks or so and see whats out there for my Z1

Just a test build, pre-nightly. Do not install. Early in Feb or March we will have update for KitKat from Sony. Just wait and calm down.