I have MB525 (SOC model) and I'm using cm-10.1-20130709-NIGHTLY_v2. I seem to be having some bugs:
1. keyboard bug - 3 buttons in the right bottom corner do not work at all.
2. if i activate a model to lock/unlock the screen, the right side of the model doesn`t work.
3. I tried to listen some music in my earphones (they are Nokia earphones), I also activated the bass but when I try to play a song, Apollo stops when the bass is starting.
4. the battery seems to drain pretty quickly (it last for a day with a moderate use of the phone).
Is there any way to fix this issues or do I have to use another ROM? What`s the best custom ROM for a Defy?
XTN89 said:
I have MB525 (SOC model) and I'm using cm-10.1-20130709-NIGHTLY_v2. I seem to be having some bugs:
1. keyboard bug - 3 buttons in the right bottom corner do not work at all.
2. if i activate a model to lock/unlock the screen, the right side of the model doesn`t work.
3. I tried to listen some music in my earphones (they are Nokia earphones), I also activated the bass but when I try to play a song, Apollo stops when the bass is starting.
4. the battery seems to drain pretty quickly (it last for a day with a moderate use of the phone).
Is there any way to fix this issues or do I have to use another ROM? What`s the best custom ROM for a Defy?
Click to expand...
Click to collapse
1. Mostly due to gapps and space issues.
2. I didn't understand?
3. Get a different music player, or clear data and cache of Apollo.
4. The battery is fine for me. Check for wakelocks and alarms with Betterbatterystats.
There is no 'best' custom ROM. You should probably not ask that question as it may lead to conflict between members.
Bugs
hotdog125 said:
1. Mostly due to gapps and space issues.
2. I didn't understand?
3. Get a different music player, or clear data and cache of Apollo.
4. The battery is fine for me. Check for wakelocks and alarms with Betterbatterystats.
There is no 'best' custom ROM. You should probably not ask that question as it may lead to conflict between members.
Click to expand...
Click to collapse
To unlock the phone you can use a model (you have 9 points and you have to unite 3 or more of them with a continuous line), the slide, a pin or nothing. If I try to use a model it works fine when I define the model, but when I practically use it, the right side doesn`t work.
So, if I flash again the ROM with different gapps and wipe all the data it should be fine, no more bugs.
Still having bugs
hotdog125 said:
1. Mostly due to gapps and space issues.
2. I didn't understand?
3. Get a different music player, or clear data and cache of Apollo.
4. The battery is fine for me. Check for wakelocks and alarms with Betterbatterystats.
There is no 'best' custom ROM. You should probably not ask that question as it may lead to conflict between members.[/QUOT
Flashed CM 10.1 again but the keyboard and lockscreen bugs didn`t go away. Before the CM 10.1, I had Android 2.2.2 which also had this bugs. I really need some HELP.
Click to expand...
Click to collapse
XTN89 said:
hotdog125 said:
1. Mostly due to gapps and space issues.
2. I didn't understand?
3. Get a different music player, or clear data and cache of Apollo.
4. The battery is fine for me. Check for wakelocks and alarms with Betterbatterystats.
There is no 'best' custom ROM. You should probably not ask that question as it may lead to conflict between members.[/QUOT
Flashed CM 10.1 again but the keyboard and lockscreen bugs didn`t go away. Before the CM 10.1, I had Android 2.2.2 which also had this bugs. I really need some HELP.
Click to expand...
Click to collapse
If even 2.2 had these bugs, it might your touchscreen which has issues.
Click to expand...
Click to collapse
Bugs
hotdog125 said:
XTN89 said:
If even 2.2 had these bugs, it might your touchscreen which has issues.
Click to expand...
Click to collapse
If the issues are from the touchscreen, how come it only affects these two things, the keyboard and the unlock screen?
Click to expand...
Click to collapse
XTN89 said:
If the issues are from the touchscreen, how come it only affects these two things, the keyboard and the unlock screen?
Click to expand...
Click to collapse
It's weird these problems happen even on stock. I'm not sure what's the cause. You can try pressing harder:laugh:.
You can try CM7 and check whether these problems occur. Download these, put on your SD card, reboot to recovery, flash defy full wiper (preferably aroma wiper), choose ext3 format system data cache, then flash ROM and gapps immediately after wipe.
Aroma wiper - http://forum.xda-developers.com/attachment.php?attachmentid=1862602&d=1365260332 (after ext3 format do not reboot and make sure you select system, data and cache)
ROM - http://get.cm/get/jenkins/2922/cm-7.2.0-jordan.zip
Gapps - http://goo.im/gapps/gapps-gb-20110828-signed.zip
-
hotdog125 said:
It's weird these problems happen even on stock. I'm not sure what's the cause. You can try pressing harder:laugh:.
You can try CM7 and check whether these problems occur. Download these, put on your SD card, reboot to recovery, flash defy full wiper (preferably aroma wiper), choose ext3 format system data cache, then flash ROM and gapps immediately after wipe.
Aroma wiper - http://forum.xda-developers.com/attachment.php?attachmentid=1862602&d=1365260332 (after ext3 format do not reboot and make sure you select system, data and cache)
ROM - http://get.cm/get/jenkins/2922/cm-7.2.0-jordan.zip
Gapps - http://goo.im/gapps/gapps-gb-20110828-signed.zip
Click to expand...
Click to collapse
The thing is I really like Jelly Bean, but I will give it a try.
Isn`t possible to use aroma wiper with CM10.1?
Call mute not working in cm-10.1-20130709-NIGHTLY_v2-mb526
Is there a fix for call mute? I posted on another thread but no reply yet
I'm on mb526, Green Lens.
XTN89 said:
The thing is I really like Jelly Bean, but I will give it a try.
Isn`t possible to use aroma wiper with CM10.1?
Click to expand...
Click to collapse
Aroma wiper just needs a working custom recovery.
hotdog125 said:
Aroma wiper just needs a working custom recovery.
Click to expand...
Click to collapse
And how do I use it?
XTN89 said:
And how do I use it?
Click to expand...
Click to collapse
When you reboot your phone, during the M logo, the LED lights up blue. Immediately when you see the blue LED, press Volume Down button. Most probably custom recovery (TWRP) will open. If not select recovery and then TWRP. There Press install, and choose the aroma wiper zip. A white screen with various options will appear. Select EXT3 and scroll down and select system, data and cache. After it's done, press exit. DO NOT REBOOT. Immediately flash CM7 and then gapps and reboot.
EDIT - Just in case, flash Froyo SBF, root, 2ndinit and then install CM7. When you reboot your phone, during the M logo, the LED lights up blue. Immediately when you see the blue LED, press Volume Down button. Most probably custom recovery (CWM) will open. If not, Then select recovery --> Stable/Custom (don't know which one will be there). Use volume buttons to scroll and power button to select. Choose install zip from sdcard. There Press install, and choose the aroma wiper zip. A white screen with various options will appear. Select EXT3 and scroll down and select system, data and cache. After it's done, press exit. DO NOT REBOOT. Immediately flash CM7, then gapps by again going to install zip from sdcard. First install CM7 zip and then gapps. Then reboot.
Call mute malfunction
RehanMohdKasim said:
Is there a fix for call mute? I posted on another thread but no reply yet
I'm on mb526, Green Lens.
Click to expand...
Click to collapse
Same problem here - call mute does;t work on 10 and 10.1 didn;t try 10.2 yet. Think this one should be a critical. Is there any tweak/fix for it?
DEFY MB525 green lens (T-MOBILE)
hotdog125 said:
When you reboot your phone, during the M logo, the LED lights up blue. Immediately when you see the blue LED, press Volume Down button. Most probably custom recovery (TWRP) will open. If not select recovery and then TWRP. There Press install, and choose the aroma wiper zip. A white screen with various options will appear. Select EXT3 and scroll down and select system, data and cache. After it's done, press exit. DO NOT REBOOT. Immediately flash CM7 and then gapps and reboot.
EDIT - Just in case, flash Froyo SBF, root, 2ndinit and then install CM7. When you reboot your phone, during the M logo, the LED lights up blue. Immediately when you see the blue LED, press Volume Down button. Most probably custom recovery (CWM) will open. If not, Then select recovery --> Stable/Custom (don't know which one will be there). Use volume buttons to scroll and power button to select. Choose install zip from sdcard. There Press install, and choose the aroma wiper zip. A white screen with various options will appear. Select EXT3 and scroll down and select system, data and cache. After it's done, press exit. DO NOT REBOOT. Immediately flash CM7, then gapps by again going to install zip from sdcard. First install CM7 zip and then gapps. Then reboot.
Click to expand...
Click to collapse
Thanks for your advice, but you were right in a previous post: my touchscreen broke down. It works sometimes, but mostly it`s pretty hard trying to enter an app or menu or even answer calls.
Related
Hey guys, I just tried to do the whole NAND android thing on my HD2, but I've hit a snag, I flashed the radio, installed HSPL 2.08 and that Mag thing (the thing with the 12 menu options) and Clockworkmod with 150mb partition and they work all fine, In this guide:
http://forum.xda-developers.com/showthread.php?t=893948&page=147
I got up to:
3. FLASHING A CWM (CLOCKWORK MOD) ROM
1. Connect your phone to your pc via the USB Cable
2. In the Clockwork Mod main menu select 'wipe data/factory reset' and then 'Yes' on the next screen
3. When the data wipe is complete, select 'install zip from sd card' in the main menu
4. Go down to 'choose zip from sdcard' and select
5. Scroll down to your CWM Rom (which you should have copied to the Root of your Storage Card) and select it
6. Select 'Yes' from the options and wait until you get a message saying 'Install from sdcard complete
Note: You can repeat steps 3-5 if you have more zips to install such as gps data or screen mods
7. Once finished press the 'Back' button to get to the previous menu screen
8. Select 'reboot system now' to restart your phone and your Android Rom should boot
9. Once Android has booted and you have gone through the setup screens, LONG PRESS the 'End' button and select reboot to reboot your phone to avoid possible FC (Force Close) problems
NOTE: The first boot of your Rom will take alot longer than subsequent boots so leave it and give it time (15 minutes max)
Click to expand...
Click to collapse
I did the installer through CWM, it asks me to reboot the phone, then it comes up with NAND failed or something, takes me back to the magDLR folder with the 12 selectable things (with tetris which doesnt work)?
I tried installing it a few times, same issue.
I'm trying to install this ROM:
http://forum.xda-developers.com/showthread.php?t=933951
Any help would be greatly appreciated, unfortunately at the moment I'm stuck with a phone with no OS lol.
some help
hi
make sure you have a radio that will play well with android and personally i do not flash cm roms but what you can do is flash the following rom after you clear your device of course (the link to page http://forum.xda-developers.com/showthread.php?t=905060 the link to rom https://sites.google.com/site/nexushd2android/nexushd2-gingerbread/v2-3/download get the dtf and just flash it with the usb flasher lastest version of this rom incase you like it and want the lastest version https://sites.google.com/site/nexushd2android/nexushd2-gingerbread/v2-7/download this one just do through clockwordmod) then it will have clockwordmod already preinstalled and then check out this rom if you like if you rather have cm then turn off the phone then power on but hold the power botton till your at magldr and go to ad recovery then install zip from sd and install droid1.rar i cant promise ill work you can try i personally would just install the rom i have links too and update it and thats it because know somethings arent supported on cm and anything cm has you can install on this rom too
theted said:
hi
make sure you have a radio that will play well with android and personally i do not flash cm roms but what you can do is flash the following rom after you clear your device of course (the link to page http://forum.xda-developers.com/showthread.php?t=905060 the link to rom https://sites.google.com/site/nexushd2android/nexushd2-gingerbread/v2-3/download get the dtf and just flash it with the usb flasher lastest version of this rom incase you like it and want the lastest version https://sites.google.com/site/nexushd2android/nexushd2-gingerbread/v2-7/download this one just do through clockwordmod) then it will have clockwordmod already preinstalled and then check out this rom if you like if you rather have cm then turn off the phone then power on but hold the power botton till your at magldr and go to ad recovery then install zip from sd and install droid1.rar i cant promise ill work you can try i personally would just install the rom i have links too and update it and thats it because know somethings arent supported on cm and anything cm has you can install on this rom too
Click to expand...
Click to collapse
I think its 2.14.50 or something like that, I flashed it because one of the guides suggested to.
theted said:
r lastest version of this rom incase you like it and want the lastest version https://sites.google.com/site/nexushd2android/nexushd2-gingerbread/v2-7/download this one just do through clockwordmod)
Click to expand...
Click to collapse
Can I just put this on my SD card and install it through the CWM I have on my phone at the moment?
Or do I have to completely wipe my device again and start from scratch?
best would be to clear it all the way to prevent any problems
dont worry your radio looks good and the clear and restart is pretty quick
but if you really wanna save time try it through cm first maybe ill work correctly
Thanks mate that one seems to work, but now I've got this flashy X thing on my screen, is that supposed ot happen?
UPDATE:
Yay its working, awesome. I just installed it through clockwork mod, had no issues.
Is there some sort of task manager I can see to terminate programs in this version of Android?
I've got PSX4Droid on it now, I'm trying to play Metal Gear Solid but she's a bit laggy, stuttering sound and slow frame rate.
Anyone else had this issue?
there is task killer on the market
try chainfire might help
I cant post in the thread because I am "new" so I am asking here.
http://forum.xda-developers.com/showthread.php?t=1181486
Post 1 says:
NOTES:
You MUST be on CyanogenMod 7 or .340 Froyo to flash this rom!
Remember to wipe before flash!
On 1.7.22.1: It is on Rom Manager, Click Check for Updates!
You must go into settings and change resolution of MIUI Camera to get it to work.
Do not wipe to install it.
Market apps are fixed!
Post 2 says:
If you haven't heard about this ROM yet then check out the videos in the 2nd post to see it in action!
This is an excellent ROM if for no other reason than it introduces the first non-CyanogenMod/carrier/manufacturer framework overhaul of Android 2.3.4 and boy what an overhaul.
So what version should I have to install it?
I don't want to install and end up in a boot loop because we all know how hard it is to fix a Droid X when that happens
You must be on either CyanogenMod 7 or 340 Froyo. You must flash 1.7.22, not 1.7.22.1, it can be flashed later.
Also, it's not that difficult to fix a bootloop lol.
Sent from my DROIDX using XDA App
Thanks
How do you get out of a boot loop with the Droid X?
I can't get into recovery unless I am in a Rom and run Droid 2 Bootstrapper
Well since I can't post in the real thread I will post here all the bugs I find.
1. Lot's off apps in the market don't work. I am talking a good 40-60 at least. There are a few important ones I use like Noom and Cardio Trainer.
Market shows that the app is incompatible with my device. Ti Backup tries to restore but either says it is successful or fails, it works neither time.
2. When I check Settings>System>About Phone and then click Systems Updates it force closes settings.
Reason I was checking this was because I tried to update using ROM manager but that didnt work.
3. ROM manager works, however it does nothing when I click "Check for ROM Updates"
4. Google Maps was said to be installed, maybe on the next version but since I cant install that I had to install it myself
5. Tethering and hotspots. No hotspot option shown. Also USB tethering did not seem to work. I tried the 4 different settings you can have the phone in when connected to USB but the status says USB not connected (obviously not true since I am able to connect and view my SD card through my computer)
6. ROM fails to load after a reboot. Happened to me twice and I had to SBF it back to stock for it to boot up. This happened when I just did a normal reboot
So for now I am done as I am looking at the Motorola logo even after a wipe of data and cache
curtdragon said:
Thanks
How do you get out of a boot loop with the Droid X?
I can't get into recovery unless I am in a Rom and run Droid 2 Bootstrapper
Click to expand...
Click to collapse
I experienced a bootloop when I was flashing back to froyo 340 (droid logo, droid eye, droid logo, droid eye, and so on).
Here's what worked for me:
1. Power down the phone (battery pull)
2. Put battery back in
3. Hold home key, then hold the power key until the phone turns back on (you should see the M logo)
4. Press the search key when you see the Android next to the triangle
5. Using the volume up/down keys on the side of your phone and the camera button to select, wipe the data and cache (please note: you only need to push the camera button half way to select)
6. Reboot the phone and it should work, at least it did for me.
Maximaniac said:
I experienced a bootloop when I was flashing back to froyo 340 (droid logo, droid eye, droid logo, droid eye, and so on).
Here's what worked for me:
1. Power down the phone (battery pull)
2. Put battery back in
3. Hold home key, then hold the power key until the phone turns back on (you should see the M logo)
4. Press the search key when you see the Android next to the triangle
5. Using the volume up/down keys on the side of your phone and the camera button to select, wipe the data and cache (please note: you only need to push the camera button half way to select)
6. Reboot the phone and it should work, at least it did for me.
Click to expand...
Click to collapse
Yeah I tried that and it works sometimes but not usually.
How did you flash miui? Did you flash it over CM7 or froyo 340?
SBF to stock 2.3.34
Wipe data and cache
Reboot
Install Z4Root and run (reboots on its own)
Install Droid 2 Bootstrapper (Flash recovery/Reboot recovery)
Install MIUI from zip
Reboot
It works fine for a while but after install some apps and fixing settings it wont get passed the Motorola screen.
This happened twice. I miss the OG Droid because if that happened you could just boot into recovery and load your last save and you are good to go
curtdragon said:
SBF to stock 2.3.34
Wipe data and cache
Reboot
Install Z4Root and run (reboots on its own)
Install Droid 2 Bootstrapper (Flash recovery/Reboot recovery)
Install MIUI from zip
Reboot
It works fine for a while but after install some apps and fixing settings it wont get passed the Motorola screen.
This happened twice. I miss the OG Droid because if that happened you could just boot into recovery and load your last save and you are good to go
Click to expand...
Click to collapse
how are you installing the apps? manually from the market? or titanium backup?
Are you referring to post 4? If so I tried both ways. Market won't let me install the ones that I cant get installed. They just don't show up in the search. If I go onto the market website they are there but once I choose my phone it disappears.
Titanium fails when i try to install the apps
It's as if the phone is not broadcasting what model it actually is. So the apps that do work are just "works on any old Android" while the others ones say these devices only
cdexsw said:
how are you installing the apps? manually from the market? or titanium backup?
Click to expand...
Click to collapse
Oh, I see where I mentioned installing apps in the last post. I did the same thing as i mentioned above. A combination of Ti and market installs
Hi guys,
Pretty new to the android scene (came from iOS). After using my Note at stock rom for about 2 months I decided to go ICS. Well.. here is where the pain started. It seems I have really ruined my phone, however I do not understand why.
What did I do?
I rooted my phone with CWM and used ODIN 1.8 to flash a default rom (as the guide told me to) so I could flash ICS afterwards. At the moment I flashed the first rom something strange happend. The phone was clicking itself (I will add youtube links as soon as I can) just at the middle of the screen. For example, if I were to send an SMS (vertically placed) it will press T or G constantly, depending on the rom. <-- Weird right? It actually switches to G or T depending on the rom, which should indicate software problems and not hardware.
As far as I know it has something to do with the way android mounts the SD card. Because as soon as I plug in the USB, the problem is gone. As soon as I unplug its back again. The ''clicking'' seems to be localized on the same place no matter if I go portrait or landscape, must be hardware right?
I've flashed over 50 times. Using different kernals, rockroms, ICS etc. etc. They all show the same problem. Even after ''factory resets'' in CWM, reinstall stock rom etc. I've even deleted everything on the internal SD card (as far as I could see files, not sure about hidden files) but that didn't help either.
Didn't make a backup either (dumb ****ing me) but I figured it wouldn't matter because I had a stock rom from my country zipped anyway.
The fact that it only shows up unplugged, must be an indication it has something to do with the fact that it only occurs during the mount of android to the phone.. but I can't figure out how to solve it.
HELP
Clicking itself? As in, it was registering touches at the center of the screen, without you actually touching it?
Yes, exactly that. It simply registers touches without me touching it.
There is no damage either, screen is clean as can be.
I've seen a few users here on the forum having issues with their touchscreen, and almost all the time the charger/cable is identified as the culprit. Search the general and Q&A forums with "touchscreen", you'll find a few of these posts.
It seems the screen is affected by voltage fluctuations, or incorrect voltages due to use of third-party cables/ chargers. If your Note is connected to the computer and the earthing for your machine is not proper, it can cause issues too. Some people suggest using a different power outlet, or at a friend's place, just to be sure. Also, the screen seems to get damaged that way very quickly, and no software changes seem to solve anything.
I personally haven't experienced a problem like that, but I'd recommend that you flash a stock rom for your country using Odin on the PC, and get the phone replaced.
This may sound dumb... but try taking your s-pen out of the back.
Some users report over sensitive screens, and it wouldn't surprise me if it would go THROUGH the back of the phone.
Give it a shot, let us know.
Just try full flash via odin with .pit file and repartition checked. Maybe it will help you.
Hi Guys,
Thanks for your input!
After the suggestion about voltage it got me thinking. So I charged the battery to 100% using a different power outlet. Problem seemed to be gone for a while, but as soon as the battery hit 80% or so it started again. Seems the voltage regulation is off scale or something like that. Either way, the damage seems to be permanent.
I flashed back to stock rom, gonna mail it to the samsung repair center tomorrow.
arf_cz said:
Just try full flash via odin with .pit file and repartition checked. Maybe it will help you.
Click to expand...
Click to collapse
Any idea where I can find this PIT file? Alot of people are talking about it but I am not able to find it.
EDIT: nvm found it
Its not only the .pit file, you need complete full flash (3 files - code, modem and csc).
For me, when i mess up my gnote trying a lot of different roms/kernels/ics stuff, helped this pack (open eu):
link in attached file (cant post links)
it includes odin and some other unimportant stuff. You need only odin, .pit file, modem file, code file and csc file.
In odin tick re-partition, auto reboot, f.reset time and phone bootloader update.
Put pda, modem, csc and pit files, than start and good luck!
Just chill
Hey there,
First things first, it is very hard to get your android messed up so, just and follow the below steps one-by-one and let me know. Please understand by following this process all your data, apps and settings will be reset.
1. Take a back up of all your data using Titanium or MyBackup.
2. Move the back up file to a location on your PC.
3. Flash a ROM that you can root and get CWM to work.
4. Once flashed and rooted, unplug the device and boot in recovery mode.
5. Once in recovery mode
a. Format Data/Factory Reset
b. Format cache
Under the advanced option in recovery mode select
a. Wipe Dalvik Cache
b. Wipe Battery Stats
Under the mounts option in recovery mode select
a. Format SD/MMC
b. Format System
c. Format Ext SD
Once done, select reboot. Now, the phone will be stuck on the flash screen, hold the power button down for as long as the phone does not turn off.
Now launch Odin, select the ROM of your choice.
Press the Power + Middle (Menu) + Volume down button until you get a warning on updating a new firmware, press the volume up button.
Plug the device and update.
Do check and let me know if this helped. The problem here is of the Battery Stats being clogged by moving from Gingerbread to ICS especially LP1 leak is disastrous and cannot be used as a daily ROM.
Please keep in mind the above steps and follow accordingly whenever you are ready to move a much advanced version of the firmware such as ICS and you will never face a problem.
sunil.inxs said:
Hey there,
First things first, it is very hard to get your android messed up so, just and follow the below steps one-by-one and let me know. Please understand by following this process all your data, apps and settings will be reset.
1. Take a back up of all your data using Titanium or MyBackup.
2. Move the back up file to a location on your PC.
3. Flash a ROM that you can root and get CWM to work.
4. Once flashed and rooted, unplug the device and boot in recovery mode.
5. Once in recovery mode
a. Format Data/Factory Reset
b. Format cache
Under the advanced option in recovery mode select
a. Wipe Dalvik Cache
b. Wipe Battery Stats
Under the mounts option in recovery mode select
a. Format SD/MMC
b. Format System
c. Format Ext SD
Once done, select reboot. Now, the phone will be stuck on the flash screen, hold the power button down for as long as the phone does not turn off.
Now launch Odin, select the ROM of your choice.
Press the Power + Middle (Menu) + Volume down button until you get a warning on updating a new firmware, press the volume up button.
Plug the device and update.
Do check and let me know if this helped. The problem here is of the Battery Stats being clogged by moving from Gingerbread to ICS especially LP1 leak is disastrous and cannot be used as a daily ROM.
Please keep in mind the above steps and follow accordingly whenever you are ready to move a much advanced version of the firmware such as ICS and you will never face a problem.
Click to expand...
Click to collapse
I'm on Imilka's AOSP ICS ROM (GB -> Chinfire repack -> AOSP). If I just delete battery stats via recovery, that should be it, right?
sunil.inxs said:
Hey there,
First things first, it is very hard to get your android messed up so, just and follow the below steps one-by-one and let me know. Please understand by following this process all your data, apps and settings will be reset.
1. Take a back up of all your data using Titanium or MyBackup.
2. Move the back up file to a location on your PC.
3. Flash a ROM that you can root and get CWM to work.
4. Once flashed and rooted, unplug the device and boot in recovery mode.
5. Once in recovery mode
a. Format Data/Factory Reset
b. Format cache
Under the advanced option in recovery mode select
a. Wipe Dalvik Cache
b. Wipe Battery Stats
Under the mounts option in recovery mode select
a. Format SD/MMC
b. Format System
c. Format Ext SD
Once done, select reboot. Now, the phone will be stuck on the flash screen, hold the power button down for as long as the phone does not turn off.
Now launch Odin, select the ROM of your choice.
Press the Power + Middle (Menu) + Volume down button until you get a warning on updating a new firmware, press the volume up button.
Plug the device and update.
Do check and let me know if this helped. The problem here is of the Battery Stats being clogged by moving from Gingerbread to ICS especially LP1 leak is disastrous and cannot be used as a daily ROM.
Please keep in mind the above steps and follow accordingly whenever you are ready to move a much advanced version of the firmware such as ICS and you will never face a problem.
Click to expand...
Click to collapse
Argh, thanks alot for your information.
Unfortunatly I already sent the phone to Samsung for repairs. But your story sounds logical, as well as others did. However I cannot test it at the moment. If Samsung wont fix the problem i'll try your method and get back to this topic.
For those who're insterested, here's a short video of the problem ->
youtube .com/watch?v=_8UV_9jz-Wo <- space between youtube & .com
Thanks alot everyone, will get back to you! cheers
Martijn
bloodyhippo said:
I'm on Imilka's AOSP ICS ROM (GB -> Chinfire repack -> AOSP). If I just delete battery stats via recovery, that should be it, right?
Click to expand...
Click to collapse
This should work, if not take the long route..
Sent from my GT-N7000 using xda premium
Well bloodyhippo,
It turns out you were right. According to Samsung my Note's screen was defective, most likely due to to a lousy/non-grounded power connector.
Which is pretty upsetting as this basicly means I can't charge or flash my phone at 90% of all places im at.
They've replaced the screen, phone works like a charm.
Let this be a warning to all.. The G Note has a REAL sensative screen..!
extreemwisse said:
Well bloodyhippo,
It turns out you were right. According to Samsung my Note's screen was defective, most likely due to to a lousy/non-grounded power connector.
Which is pretty upsetting as this basicly means I can't charge or flash my phone at 90% of all places im at.
They've replaced the screen, phone works like a charm.
Let this be a warning to all.. The G Note has a REAL sensative screen..!
Click to expand...
Click to collapse
Buy a UPS for clean energy and a surge protector.
I am new to posting in the forum but have recently forged ahead into custom ROMs. I went from stock ICS to Pershoot's CM10 10/30 build and now on the latest 11/9 ROM. So far it works pretty good. I documented the process if anyone is interested.
It looks like there are two active JB ROMs (Pershoot's & AOKP) on the Dev thread. Just wanting to get some interaction around this SGT10.1 model.
Thanks to Pershoot. Sorry, can't post in the dev thread yet.
Sent from my SCH-I905 using Tapatalk 2
The only thing about Cm10 builds across the board is battery life due to the way wakelocks seem to be handled. I'm sure that eventually things will work out. For now the degree of battery drain sometimes gets exasperated on our device because of the LTE modem so I have found it best to keep certain things frozen when the tablet is not in use like logging out of Talk, freezing Maps and turning off location services along with enabling airplane mode. I am not a user of other things that require a lot of data during sleep like Facebook, twitter or other instant messaging services so generally I get adequate battery life doing these things though not as good as with HC.
One thing is certain, I have never enjoyed using the tablet as much as I do now with Pershoot's build. The responsiveness and stability is fantastic. This is the way the tablet should have shipped from the start.
Sent from my SCH-I905 using Tapatalk 2
Agreed. Battery depletion seems to be greater on the custom ROMs vs. stock. Turning off location services shuts down the constant Wi-fi activity when the screen is off and tablet idle for a long time. I purchased Better Battery Stats to help figure out where I can conserve battery.
Sent from my SCH-I905 using Tapatalk 2
Thanks for your input recoil1911. I am interested in your documented installation process. Currently I am using the stock rom (rooted) but have been thinking of going to a custom rom.
recoil1911 said:
I am new to posting in the forum but have recently forged ahead into custom ROMs. I went from stock ICS to Pershoot's CM10 10/30 build and now on the latest 11/9 ROM. So far it works pretty good. I documented the process if anyone is interested.
It looks like there are two active JB ROMs (Pershoot's & AOKP) on the Dev thread. Just wanting to get some interaction around this SGT10.1 model.
Thanks to Pershoot. Sorry, can't post in the dev thread yet.
Sent from my SCH-I905 using Tapatalk 2
Click to expand...
Click to collapse
I am interested in seeing your documentation. Do these builds work on OCD 4.0.4?
jsgalaxy said:
I am interested in seeing your documentation. Do these builds work on OCD 4.0.4?
Click to expand...
Click to collapse
Yes. You must be on ICS before installing these ROMs. I am on business travel right now but I should be able to post my notes by end of the week.
Sent from my SCH-I905 using Tapatalk 2
My instructions for installing ClockWorkMod and flashing CM10 on my Verizon SCH-i905. Use at your own risk.
Notes:
• Must be on stock ICS (v4.0.4) before initial flash to CM10 ROM because of the LTE modem• Download ODIN 1.85 for Windowshttp://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&cad=rja&sqi=2&ved=0CDAQFjAA&url=http%3A%2F%2Fforum.xda-developers.com%2Fattachment.php%3Fattachmentid%3D581913%26d%3D1304094576&ei=rY6mUIgfxYPIAbe6gaAB&usg=AFQjCNF7sF0f2yJp0IxHp1ISlP2fzGKhtw&sig2=zgnSfC3HnTTgV_TCWS3NgQ• Download and install Windows USB drivers for SGT10.1http://www.samsung.com/us/support/owners/product/SCH-I905UKAVZW• Download latest Google Apps package for CM10 (zip file)http://wiki.cyanogenmod.org/wiki/Latest_Version#Google_Apps• Download latest CM10 p4vzw ROM zip file and CWM Recovery (recovery.tar.md5)http://droidbasement.com/galaxy/roms/cm10/p4vzw/
ClockWorkMod Recovery Installation:
• Boot tablet and ensure there is enough battery• Turn off USB debugging in the SGT10.1• Connect the USB cable from PC to tablet and copy/paste the latest p4vzw CM10 ROM zip file and CM10 Google apps zip file to the root file system of the SGT10.1• Power down tablet and disconnect USB cable. Power it up by holding down the Power button and Volume Up button (Closest to Power button) simultaneously.• When Samsung Galaxy logo appears release the power button only• Once you see the two recovery/download icons you can release the Volume Up button• The Android icon should be flashing. Press the Volume Down button (Furthest from Power button) to select download mode and Volume Up to acknowledge warning message. It should indicate awaiting for downloading.• Start ODIN (run as Administrator) and connect cable from PC to SGT10.1. You should see yellow highlighted in the COM port and a COM port number.• Browse in the PDA slot to the latest CWM recovery “recovery.tar.md5”. Make sure the only checked options are “Auto Reboot" and “F.Reset Time”• See the next step before proceeding. Click the start button in ODIN. It should quickly complete and show a green “Pass” message and the table will automatically reboot.• When the SGT10.1 reboots and before or during the Samsung Galaxy Tab logo press and hold the Power and Volume Up buttons simultaneously to return to the recovery/download icons. If the SGT10.1 boots up normally you will not be able to boot into CWM recovery.
CM10 ROM and Google Apps Installation:
• With the two recovery/download icons displayed, press the Volume Up button to highlight recovery mode• Press the Volume Down button to select it• The tablet will boot into CWM Recovery (v6.0.1.5)• Make a NANDROID backup (Optional)• Select wipe data/factory reset (factory defaults, doesn’t erase SDCARD/user data). Press power button to enter. Confirm by selecting yes.• Select wipe cache partition. Press power button to enter. Confirm by selecting yes.• Go into Advanced and select wipe Dalvik cache. Press power button to enter. Confirm by selecting yes. Go back to main menu.• Select “Install zip from SD card”. Press power button to enter.• Select “Choose zip from SD card”. Press power button to enter.• Navigate to the CM10 p4vzw ROM zip file and select it. Confirm by selecting yes. This should take about a minute.• Go back to main menu and repeat to "install zip from SD card" and "choose zip file from SD card".• Navigate to the Google Apps zip file and install it. Go back to main menu.• Select “reboot system now”. The startup logo will go for a while and app optimization will proceed..• Finished. You should be Jelly Bean operational.
Observations:
I did have a situation where the tablet would always go into stock recovery instead of CWM after installing CWM. If you run into that same situation let me know and I can provide some direction.
CM10 nightlies can then be installed in the Android System settings "About Tablet" -> "CyanogenMod Updates" section
• Must be on stock ICS (v4.0.4) before initial flash to CM10 ROM because of the LTE modem
Might be a stupid question but, I am already running [ROM] [JB] [P4--P4WIFI--P4VZW] 4.1.2 AOKP for the Galaxy Tab 10.1 Do I still need to be on stock ICS before I flash this? I understand that I do need to update CWM via odin. Thanks!
pcpimpin said:
• Must be on stock ICS (v4.0.4) before initial flash to CM10 ROM because of the LTE modem
Might be a stupid question but, I am already running [ROM] [JB] [P4--P4WIFI--P4VZW] 4.1.2 AOKP for the Galaxy Tab 10.1 Do I still need to be on stock ICS before I flash this? I understand that I do need to update CWM via odin. Thanks!
Click to expand...
Click to collapse
I wouldn't think so. You probably flashed from ICS when you went to AOKP. After updating CWM I suggest factory wiping and clearing both caches before installing CM10. CM10.1 for the p4vzw is out but I would stay with CM10 for this transition.
recoil1911 said:
I wouldn't think so. You probably flashed from ICS when you went to AOKP. After updating CWM I suggest factory wiping and clearing both caches before installing CM10. CM10.1 for the p4vzw is out but I would stay with CM10 for this transition.
Click to expand...
Click to collapse
That's what I thought. Yep I was on stock ICS before flahing AOKP. On AOKP my tablet will not deep sleep. Looks to be a modem lock. I hope CM 10 has better battery life Thanks for the reply!
Observations:
I did have a situation where the tablet would always go into stock recovery instead of CWM after installing CWM. If you run into that same situation let me know and I can provide some direction.
I have run into this and have not figured it out? What did you do?
I'm also looking for the official ICS OTA that I can flash.
Thanks
MichaelMcC said:
Observations:
I did have a situation where the tablet would always go into stock recovery instead of CWM after installing CWM. If you run into that same situation let me know and I can provide some direction.
I have run into this and have not figured it out? What did you do?
I'm also looking for the official ICS OTA that I can flash.
Thanks
Click to expand...
Click to collapse
To fix the CWM boot issue. I did have to install root first by downloading and flashing su from here. http://downloads.androidsu.com/superuser/Superuser-3.1.3-arm-signed.zip
Install "Root Browser Lite" from Google Play
Run "Root Browser Lite" and navigate to the "system/etc" folder
Select the file "install-recovery.sh" and view it. Select "RB Text Editor" to open it..
After the line "#!/system/bin/sh" add a new line and enter "exit 0". Save the file and exit.
Power off tablet, power up into recovery/download mode.
After doing these steps I noticed it still booted into stock recovery. I ODIN'd CWM once more and then it worked fine after that.
Your should have received a firmware upgrade notice when you search for updates.
recoil1911 said:
To fix the CWM boot issue. I did have to install root first by downloading and flashing su from here. http://downloads.androidsu.com/superuser/Superuser-3.1.3-arm-signed.zip
Install "Root Browser Lite" from Google Play
Run "Root Browser Lite" and navigate to the "system/etc" folder
Select the file "install-recovery.sh" and view it. Select "RB Text Editor" to open it..
After the line "#!/system/bin/sh" add a new line and enter "exit 0". Save the file and exit.
Power off tablet, power up into recovery/download mode.
After doing these steps I noticed it still booted into stock recovery. I ODIN'd CWM once more and then it worked fine after that.
Your should have received a firmware upgrade notice when you search for updates.
Click to expand...
Click to collapse
I'll give it a try, thanks.
That did the trick. I was able to root ICS without error for the first time. Before I always had to install HC then root it and then update to ICS via OTA which took days before the ICS OTA would pop up sometimes. Backed up a clean copy of ICS now so I'll not deal with that again.
Thanks.
Verizon sch-i905 factory rom
Does anybody have a working link to get the factory rom for a verizon sch-i905 lte? I will contribute to anyone's beer fund!
Hello, recently there have been a lot of posts requesting help with KitKat on our device. This is why I have created a guide going through the installation, setup, issues and many other aspects of KitKat on our phone.
1. List of KitKat ROMs:
OmniROM
CyanogenMod
ParanoidAndroid
SlimKat
Illusion Roms
C-RoM
SlimSaber
CarbonRom
Dirty Unicorns
MoKee OpenSource
Resurrection Remix
Asylum Omni
2. Installation
If you are on the stock Jelly Bean/ICS Samsung firmware:
-Download Philz kernel and copy it to your SD card
-Download a KitKat ROM and copy it to either your internal or external memory
-Download PA-Google Apps and copy it to either your internal or external memory
-Download Raw Kernel r5 and copy it to either your internal or external memory
-Reboot to recovery by holding down volume up, power and home button at once until you are in recovery mode
-Flash Philz kernel
-Go to "Mounts and Storage" and format /system, /data, /preload
-Reboot to recovery again by going to "advanced", "reboot to recovery" or by holding down volume up, power and home button at once until you are back in recovery mode
-Flash Raw Kernel
-Reboot to recovery again
-Flash your ROM
-Flash PA-Google Apps
-Reboot
If you are on any AOSP based firmware or on any custom TouchWiz ROM:
-Download a KitKat ROM and copy it to either your internal or external memory
-Download PA-Google Apps and copy it to either your internal or external memory
-Download Raw Kernel r5 and copy it to either your internal or external memory
-Reboot to recovery by holding down volume up, power and home button at once until you are in recovery mode
-Flash Raw Kernel
-Go to "Mounts and Storage" and format /system, /data, /preload (formatting /preload may fail, skip if it does)
-Reboot to recovery again by going to "advanced", "reboot to recovery" or by holding down volume up, power and home button at once until you are back in recovery mode
-Flash your ROM
-Flash PA-Google Apps
-Reboot
3. Updating your firmware
Updating your system is very easy, some ROMs (ex. OmniROM) have a built-in updater. Simply go to Settings, About phone and "Update". After that just follow the instructions on screen.
If your ROM doesn't support that option or you want to go old-school:
-Download the updated ROM to your internal/external memory
-Reboot to recovery
-Flash the ROM
-Reboot
4. Bugs, issues
When flashing any KitKat ROM I get a "Status 7 error".
You didn't follow the installation procedure carefully enough. You most probably forgot to flash Raw Kernel or you forgot to reboot to recovery after flashing Philz or Raw Kernel.
Sometimes whilst listening to music, the track freezes and I can no longer access it.
KitKat for our device has a bug in it where this happens. There is NO fix for this. Only a reboot will allow you to access the file again.
Refer to this thread for more information.
UPDATE:
The bug has been fixed however not all ROMs have merged the fix yet. If you are still having this issue then try flashing a kernel with the fixes merged (for example Forest Kernel or Raw Kernel).
Sometimes whilst copying files from my computer, the copying process stops.
This is the same issue as the above one with the music bug. One way to copy files without a problem is to reboot to recovery, go to mounts and storage and go for "mount USB storage". Copying through recovery is stable.
UPDATE:
The bug has been fixed however not all ROMs have merged the fix yet. If you are still having this issue then try flashing a kernel with the fixes merged (for example Forest Kernel or Raw Kernel).
I have battery issues.
This can be caused by many reasons, mainly your apps. Here are a few quick fixes though:
1. If your battery is at least a year old then it may be time to replace it with a new original one
2. Go to Settings, Wi-Fi, menu button, advanced and unmark "Scanning always available"
3. Install Greenify
4. If your ROM supports it, go to App Ops (On CarbonROM: Settings, Privacy, Privacy Guard, menu button, advanced) and disable the permission "keep awake" from as many apps as possible. Do not disable this permission from alarm clocks, email clients etc.
You can also disable other permissions, such as location which will also save your battery life
5. Install Titanium Backup and freeze/uninstall as many un-used apps as possible
6. Install Wakelock Detector to find out what is keeping your device awake
7. If you still have problems, refer to this thread
I haven't got ROOT access.
This usually affects OmniROM users. Download SuperSU zip and flash through recovery mode
I want access to Developer options.
Go to Settings, About phone and tap 7 times "Build number"
I want to change the runtime to ART.
Go To Settings, Developer options and find "Select runtime". Don't forget that the ART runtime is still in development by Google and bug reports shouldn't be filed against ROMs if you experience problems on ART
Every single time I change to the ART runtime, it doesn't change and stays on the current Dalvik runtime.
You have Xposed installed which is stopping you from changing it as Xposed is incompatible with ART. Uninstall Xposed to fix this.
I hope you have found this mini guide useful. If you still have any doubts, please don't hesitate to request more help in this thread.
If you have any suggestions as to what else should be included in this guide, don't forget to drop a line or two.
Nicely done.
Wow u really did a great one there. Hopefully this will be a great help to all "lost sheeps" out there. Well done!
Sent from my GT-N7000 using XDA Free mobile app
Thanks guys
This should be a sticky!
Nice job! Thread stuck.
XxPixX said:
3. Updating your firmware
-Wipe cache
-Go to Advanced, wipe dalvik cache
Click to expand...
Click to collapse
There's no need to wipe anything when dirty flashing updates.
Towle said:
Nice job! Thread stuck.
Click to expand...
Click to collapse
Thank you
chasmodo said:
There's no need to wipe anything when dirty flashing updates.
Click to expand...
Click to collapse
Updated, thanks
Very nice, but I'm sticking with 4.1.2 for several reasons.
One, Samsung hasn't officially (and seriously doubt they will, device is almost 3 years old) released
4.4 to the Note N7000. I usually stick with stock roms (different kernel obviously).
Two, to get kk, you have to jump through some hoops to get it on your device. I'm not above doing it,
it's just too much of a pain, to have to load all the apps, settings etc. Should be a "drag & drop" or
just click, to install.
Three, pretty much every KK rom I've seen, for the N7000, has a glitch here, bug there, battery problem,
BT problem etc. I've heard people flash the same rom to two different N7000's and one works perfect, the
other doesn't.
Four, I've had 4.1.2 on mine, since the day it came out, and, without a doubt, it's been for my usage, pretty
much the most stable rom I've used. When I was younger, back in the 386/486 computer days, it was nothing
for me to spend an evening, tweaking front side buss settings, memory timings, config.sys & autoexec.bat files
to tweak 1-2 seconds of performance from a PC. Today, I'm just after decent performance, and STABILITY.
This device, sadly IS my lifeblood for work. I don't have time for rebooting, lock ups, glitches etc.
I'm shopping around for device...the Note3 was on the list, but the price (I don't do contracts anymore) is a bit
steep, along with getting one to work properly in the USA, means you almost always have to get a LOCKED
down at&t device, with features removed, bloat etc. Got a few on the radar, but I'll just keep going with the N7000.
I'll hate to put her out to pasture, she's been a good ride.
p51d007 said:
Very nice, but I'm sticking with 4.1.2 for several reasons.
One, Samsung hasn't officially (and seriously doubt they will, device is almost 3 years old) released
4.4 to the Note N7000. I usually stick with stock roms (different kernel obviously).
Two, to get kk, you have to jump through some hoops to get it on your device. I'm not above doing it,
it's just too much of a pain, to have to load all the apps, settings etc. Should be a "drag & drop" or
just click, to install.
Three, pretty much every KK rom I've seen, for the N7000, has a glitch here, bug there, battery problem,
BT problem etc. I've heard people flash the same rom to two different N7000's and one works perfect, the
other doesn't.
Four, I've had 4.1.2 on mine, since the day it came out, and, without a doubt, it's been for my usage, pretty
much the most stable rom I've used. When I was younger, back in the 386/486 computer days, it was nothing
for me to spend an evening, tweaking front side buss settings, memory timings, config.sys & autoexec.bat files
to tweak 1-2 seconds of performance from a PC. Today, I'm just after decent performance, and STABILITY.
This device, sadly IS my lifeblood for work. I don't have time for rebooting, lock ups, glitches etc.
I'm shopping around for device...the Note3 was on the list, but the price (I don't do contracts anymore) is a bit
steep, along with getting one to work properly in the USA, means you almost always have to get a LOCKED
down at&t device, with features removed, bloat etc. Got a few on the radar, but I'll just keep going with the N7000.
I'll hate to put her out to pasture, she's been a good ride.
Click to expand...
Click to collapse
Even though it's really off topic, but I will say I do share your sentiments.
Sent from my GT-N7000
I stuck on flashing r5 kernel, after installation complete, I reboot to recovery...my phone was dead, I need connect odin, go Download mode flash back my kernel,only can make my phone alive back..please help
Running 4.0.4 stock rom with rooted kernel
andyshim1989 said:
I stuck on flashing r5 kernel, after installation complete, I reboot to recovery...my phone was dead, I need connect odin, go Download mode flash back my kernel,only can make my phone alive back..please help
Running 4.0.4 stock rom with rooted kernel
Click to expand...
Click to collapse
This is the wrong place to ask your question. Should've gone to troubleshooting section. Your situation might have been caused by ICS kernel. You should've flashed compatible CWM + franco's safe kernel or philz safe kernel n recovery first before flashing anything else in ICS 4.0.4
Sent from my GT-N7000
andyshim1989 said:
I stuck on flashing r5 kernel, after installation complete, I reboot to recovery...my phone was dead, I need connect odin, go Download mode flash back my kernel,only can make my phone alive back..please help
Running 4.0.4 stock rom with rooted kernel
Click to expand...
Click to collapse
After flashing Raw Kernel r5 then you won't be able to boot into your old ROM, only recovery mode and download mode. I'm guessing you chose the wrong reboot option or you didn't follow the instructions properly (rebooting at the proper times for example).
Nice guide mate. Many thanks for your time giving.
Great
Sent from my GT-N7000 using Tapatalk
@XxPixX
Excellent guide, many thanks for taking time to compile this to help others.
Shalom and best wishes, john
Thanks for your guide..!
In the Omni wiki I read.
TWRP is the only recovery officially supported by Omni.
Is this included in the step by step manual?
Thank you
Now with Dirty Unicorns v7.5 !
Nice guide thanks.
Is it possible to flash after cm11, cm10.2 ? Or I have to change kernel or recovery things ?
Thanks
Envoyé de mon GT-N5110 en utilisant Tapatalk
PdroidAndroid said:
Nice guide thanks.
Is it possible to flash after cm11, cm10.2 ? Or I have to change kernel or recovery things ?
Thanks
Envoyé de mon GT-N5110 en utilisant Tapatalk
Click to expand...
Click to collapse
You already will have a superior recovery. So no need.