[Q] Battery not recharging after flashing the latest Nameless ROM from OmarEinea - Galaxy Tab 8.9 General

I was running a version from june 2014 Nameless so I decided to upgrade it.
After wiping data, clearing caches I flased the latest version of the ROM.
Now it won't connect to the PC or charge. I already tried using a different adapter and cable.
There is only 5% left now. Please help me fix it, thanks in advance

Royboy510 said:
I was running a version from june 2014 Nameless so I decided to upgrade it.
After wiping data, clearing caches I flased the latest version of the ROM.
Now it won't connect to the PC or charge. I already tried using a different adapter and cable.
There is only 5% left now. Please help me fix it, thanks in advance
Click to expand...
Click to collapse
I encountered this same issue once after flashing cm9. I reverted back to stock ROM via Odin then rooted, installed recovery and reflashed the ROM and it worked fine. But you should explore other options before opting for Odin. Try flashing other ROMs such as omnirom or other nameless versions to see if they will solve the problem. Format system, data, cache etc. And try using the highest available version of cwm or twrp available for your device. Hope you solve your problem.

Related

Boot Loop

Please Help I installed a custum ROM and now I am stuck in a loop a skull comes up and droid and it continues till the battery is dies. I have tried to factory reset and nothing the only way to turn it off is to remove the battery can someone please Help
If the ROM is what's causing the problem, doing a factory reset won't change anything; it'll stil keep the same ROM in place. What you might want to do is download a more popular ROM, like a CM7 nightly, put it on your microSD card (using another phone or a microSD adapter, of course) and boot into recovery and flash that.
If that doesn't work, I dunno then. I got a bootloop the other day after using ROM Manager to flash a new kernel. Turns out it was the kernel because after a factory reset, it booted up fine. So I just chose another kernel and it's all good now.
You just might have a screwy ROM. Try reflashing it if you can. What was the custom ROM, btw?
Yeah I'd agree with the above; install another ROM and make sure to wipe cache and dalvik and if it still doesn't work wipe data as well. Note that wiping data will wipe pretty-much everything on your phones memory (SMS messages, contacts, accounts etc)
when it is cm7 than you should take an other kernel
Please, if you are experiencing random reboots (that involve the M logo) or prolonged screen freezes, you should revert to an older beta kernel that is free of the DSI errors. To do so, replace the boot.img in the update-cm-7...zip package with this one (from 0.04 version): http://code.google.com/p/cyanogenmod4milestone/downloads/detail?name=bootimg0.04.zip
Click to expand...
Click to collapse
Stole that from another Thread:
_Flash with any rom you have
_Milestone will auto reboot after flash done and loop
_Don't worry about that, remove battery in 5s and re-plugin
_Turn on your milestone: hold X and POWER to access Recovery. Select Wipe and reboot
Do you have a Droid or a Milestone? If you have a Milestone, which country is the device from?
I had a boot loop issue too on my UK Milestone when I tried to install CM6.1.2, version 28.01.2011 0.07-11.01.28. (http://android.doshaska.net/cm6)
This is what I did to fix the problem...
- Flashed UK 2.1 SBF file
- Flashed Vulnerability Recovery
- Rooted the phone
- Installed and booted into OpenRecovery
- Installed 15.01.2011 0.06-11.01.15 version (phone booted fine)
- Rebooted into OpenRecovery > Wiped Dalvik Cache
- Applied 28.01.2011 0.07-11.01.28 version
One more thing, you may need to update and/or change your baseband files.
I hope this helps.
Thx for the help guys I,m back up an running. Greatly appreciated
Sent from my Droid using XDA App

can't turn on my bluetooth

I recently upgraded my sgs to 2.3.4 xxjvq and rooted it. but i am facing an issue that I can't turn on my phone's bluetooth. However it works when I restart my device but if I reboot the device then again it stops working for strange reasons. I thought it to be cf-root 3.7 kernel issue and updated my busybox but still it does not help.
Please help!
It's to do with your kernel. Try a different one.
can u suggest the same?
Are you running a stock or a custom ROM?
If you're using a custom and it comes with a kernel, try that.
If you're on stock, give Galaxian a go.
I'll give galaxian a try...thnx for d information!
I'm using CF-Root 3.7 and got the same issue. I wiped Dalvik cache, reboot the phone and now all is working fine.
GARVENAR said:
I'm using CF-Root 3.7 and got the same issue. I wiped Dalvik cache, reboot the phone and now all is working fine.
Click to expand...
Click to collapse
thanks for your input...i will try this before going for custom rom

Problem to install ICSSGS RC 4.1

I try to install but don't work... after that i flash it, the phone lock to logo screen "google" and i can't go to CWM i must use odin to reflash. If install rc3.1 it's all ok.
Where is the problem?
Thanks.
Did you try looking at the help page on the thread in the development section? It's right before the post is finished, there will be a link that will lead you there.
Hope that helps, if not I can try to just copy and paste the instructions hahaha
scheccia said:
I try to install but don't work... after that i flash it, the phone lock to logo screen "google" and i can't go to CWM i must use odin to reflash. If install rc3.1 it's all ok.
Where is the problem?
Thanks.
Click to expand...
Click to collapse
Did you do a full wipe before flashing RC4.1?
kabracity said:
Did you do a full wipe before flashing RC4.1?
Click to expand...
Click to collapse
yes... i try to flash a miui rom first also.
I try to do a full wipe... i try to install a original rom... but when i flash rc4.1 the phone stuck to logo.
Ensure you have backed up your EFS directory; if you don't know how ask.
To be honest, there appears to be some inconsistency in the reliability of the 4.1 RC release (across handsets); I have had persistent WIFI issues and then when the wifi fix was released I found the phone to just be a little laggy.
My advice if RC 3.1 works well for you is to keep it on there for now and wait for the next release they make.
However, if you still wish to flash it, there is no 100% working way - just keep factory reset, dalvik wipe, cache wipe, reset until it starts working! That's what I did as the original instructions did not work for me.
torrentship said:
Ensure you have backed up your EFS directory; if you don't know how ask.
To be honest, there appears to be some inconsistency in the reliability of the 4.1 RC release (across handsets); I have had persistent WIFI issues and then when the wifi fix was released I found the phone to just be a little laggy.
My advice if RC 3.1 works well for you is to keep it on there for now and wait for the next release they make.
However, if you still wish to flash it, there is no 100% working way - just keep factory reset, dalvik wipe, cache wipe, reset until it starts working! That's what I did as the original instructions did not work for me.
Click to expand...
Click to collapse
I agree with you... RC3 was fine for me... fast and all worked... RC4 has some wifi issues... It switch on/off and doesnt stop till i reboot the phone... im thinking about to downgrade to RC3.1 and wait till the next release...
Sent from my GT-I9000 using XDA App
torrentship said:
However, if you still wish to flash it, there is no 100% working way - just keep factory reset, dalvik wipe, cache wipe, reset until it starts working! That's what I did as the original instructions did not work for me.
Click to expand...
Click to collapse
Yes i try it(no backup efs)
If i flash 2 time the rom the phone stuck it and i can't enter in cmw
.. is the only rom that give me this problem... bha...
Hello, have you tried to download the rom again? Maybe it's a bad download..
That's odd, for me i got stats 7 but was because i was flashing the I9000B version and my phone was with the CWM for I9000. Try using odin and flash a sotck rom, after that install the CWM and then the RC4.1.
If anyone want to know the procedure that i do to install the RC4.1 is this:
Starting for CM7 --> flash the ARO 2.3.3 rom to re-write the bootloader (check this option in odin) --> flash the ZTO 2.2 rom to re-partition in original size partitions --> flash the 2.2.1 ARO because it's a nice rom and don't have all the trash that is present in ZTO version --> through kies flahs the ARO 2.3.3 original.
After that the procedure to install the RC4.1 is the standard: flash CWM then install the ROM.
I had problems going from 3.1 to 4.1. Same issue as OP.
Process I followed:
-Flashed CWM through heimdall
-Flashed devil kernel
-Flashed CM7 (had to do this twice in a row)
-Flashed ICSSGS 3.1
-Flashed 4.1 but before I rebooted my phone, I flashed Devil one last time.
Since then, phone has been rocking along just fine!
Sent from my GT-I9000 using Tapatalk
Bena1988 said:
Hello, have you tried to download the rom again? Maybe it's a bad download..
Click to expand...
Click to collapse
Yes... three times.
I'm having the same problem here.
I tried the first point on the Common Issues page but I'm still not able to go into CWM!
I flashed the Speemod Kernel using heimdll but I can't go back to CM7. I'm getting a Stat 7 error.
Also tried the Devils kernel (Devil_1.0_CFS) with no help ....
Any ideas?
Just wondering...
MaesterB said:
I had problems going from 3.1 to 4.1. Same issue as OP.
Process I followed:
-Flashed CWM through heimdall
-Flashed devil kernel
-Flashed CM7 (had to do this twice in a row)
-Flashed ICSSGS 3.1
-Flashed 4.1 but before I rebooted my phone, I flashed Devil one last time.
Since then, phone has been rocking along just fine!
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
why on earth did you flash the CM7 as a part of the process? I always have just downloaded an appropriate kernel (devil, stockplus etc..) + ICS ROM (latest was RC4.1), once I'd rooted my stock 2.3.6 ROM with CF-Root (takes only 5 minutes). ICSSGS' ROMs can be applied straight on top of any previous ROM, the only requirement is that you have root privileges + CWM installed. Flashing CM7 is often frustrating, at least for me. I personally see no point in flashing it before the ICS ROM. If you know better, pleasy enlighten me
Arvokm said:
why on earth did you flash the CM7 as a part of the process? I always have just downloaded an appropriate kernel (devil, stockplus etc..) + ICS ROM (latest was RC4.1), once I'd rooted my stock 2.3.6 ROM with CF-Root (takes only 5 minutes). ICSSGS' ROMs can be applied straight on top of any previous ROM, the only requirement is that you have root privileges + CWM installed. Flashing CM7 is often frustrating, at least for me. I personally see no point in flashing it before the ICS ROM. If you know better, pleasy enlighten me
Click to expand...
Click to collapse
Thats the way I do all went well...
Sent from my GT-I9000 using XDA App

[Q] Help !! My SGN wont Turn on !!!

Hello everyone
My phone isnt working turning on , its stuck on the samsung logo !
I was using Ultimate jb rom when suddenly my phone turned off and it was stuck on the samsung logo , i tired flashing the another rom Angry v3 4.1.2 at first it the phone turned on and then the same happened , after that i tired flashing to stock ICS and now its again stuck on the samsung logo , what should i do now ? Please help asap
Thanks in advance
Have you tried to flash back with Odin PC?
Kortxero said:
Have you tried to flash back with Odin PC?
Click to expand...
Click to collapse
Yeah i flashed stock ICS using pc odin !
xp3rto said:
Yeah i flashed stock ICS using pc odin !
Click to expand...
Click to collapse
You should use a wipe stock ROM when flashing through Odin.
Since struck at logo, battery may be ok, nevertheless as a blind shot, why don't you try with another battery.
Sent from my GT-N7000 using xda premium
after installing the ICS rom, install a safe kernel and do a factory reset, wipe cache and dalvik.
dont you have any nandroid backups?
i have this problem b4
try flash safe kernel (example hydracore), reboot
then go to download mode flash any type of ROM
and do a factory reset, wipe cache and dalvik
pods71 said:
i have this problem b4
try flash safe kernel (example hydracore), reboot
then go to download mode flash any type of ROM
and do a factory reset, wipe cache and dalvik
Click to expand...
Click to collapse
If you install ICS, the its not safe to do a wipe till you install a safe kernel...
Thanks for the help everyone The phone turned on finally after doing this
nokiamodeln91 said:
after installing the ICS rom, install a safe kernel and do a factory reset, wipe cache and dalvik.
Click to expand...
Click to collapse
Thanks everyone
Happy New Year !!
xp3rto said:
Thanks for the help everyone The phone turned on finally after doing this
Thanks everyone
Happy New Year !!
Click to expand...
Click to collapse
having the same issue right now.. i rooted my stock rom, and used speedmod 15 version. This morning the screen started flickering and occasional power offs. Then the battery reading was incorrect - first 60%, then it went to 65%. After a restart it went to 12% after which I just recharged the phone as usual. No problems until this evening again it went bad and couldn't restart. I can however restart in CWM recovery and luckily have a NAND backup and Titanium backup of everything that is important to me.
I also managed to recover the /sdcard partition with adb pull command. Right now the phone will not boot past the startup animation. I already tried CM 10.1 31.12 nightly and also 9.1 stable, and have the exact same issue.
Anyone know how to fix this except for wiping? Because I already wiped everything while trying the CM builds.
First check if the battery is good. Also try a different battery.
Also this time installing the rom, try in cwm, mounts & storage, format/system, format/data, format/cache and then flash the rom
Sent from my GT-N7000 using xda premium
just a quick update, I ran in recovery mode and did an fsck on the 9 and 10 partitions, i got a lot errors that got "fixed" by fsck. After that I just reflashed the CM10.1 nightly and it made it past the boot screen. Not for long though. After restarting it didn't get past the boot screen again.
I gave up yesterday night and just started downloading the latest official GB. This morning I flashed it with odin and it kind of worked, until i got force closes in the wifi settings step of the setup wizard.
Now it boots into android but doesn't get past the wizard screen. I will try flashing the GB rom once more through odin, maybe that fixes some things.
any other suggestions? If it is the battery, would it make any difference if it was plugged into the wall charger while starting the phone?
---------- Post added at 12:27 PM ---------- Previous post was at 12:03 PM ----------
another update: I did a factory reset on the GB rom and am using it while connected to the wall charger. It seems to be working OK like this. So I guess I need to find a battery and try to restore my apps and settings
Another update, I ordered a brand new genuine battery and now it seems to work stable again. I just used it as a mp3 player and to surf for a few hours and no instability issues anymore, boots up perfectly.
Original battery was dated november 2011. The new one (also genuine samsung) is from october 2012 I believe.

[Q] No IMEI after flashing custom ROM

I have read almost all comments and advices but haven't found any working solution.
I started to play with Cyanogenmod ROMs on my Galaxy S I9000. I flashed CM 10.2.1 first and it worked fine. Then I tried to upgrade to CM 11 SNAPSHOT M4, everything fine. I switched back to CM 10.2.1 and repeated going there and back several times. Everything went fine until the phone did not connect to network after flashing CM11 and IMEI was "unknown".
I think I have tried all possible steps I found on the Internet (recovering EFS folder, going back to original firmware etc.), but I am lost in a cycle - I can flash original FROYO (2.2) with repartitioning, and connection to network is fine, IMEI is ok. I can upgrade it to the latest official version using Kies, IMEI ok. I root phone using CWM, everything fine. I flash custom firmware - no connection to network, IMEI lost. I always wipe cache etc between flashes.
Sometimes the lost IMEI reappears when I connect phone to the computer using USB cable, but it is lost again when I reboot. The phone also shows some minor issues like rebooting instead of turning off, showing battery icon when trying to turn it on etc.
Any idea what can cause this behavior?
Thank you!
Did you also wipe system when going back to stock rom? if not then do full wipe including system wipe.
EDIT: flash stock gingerbread 2.3.6 then start from there.
pryerlee said:
Did you also wipe system when going back to stock rom? if not then do full wipe including system wipe.
EDIT: flash stock gingerbread 2.3.6 then start from there.
Click to expand...
Click to collapse
Yes, I always run wipe data/factory reset, wipe cache, wipe dalvik cache, and format /system before flashing custom system.
The phone behaves the same if I flash Gingerberad directly or if I flash Froyo first and then upgrade it to Gingerbread using Kies. The only difference is that flashing Froyo is ok, but flashing Gingerbread with Odin complains about missing dbdata and I have to repair it (see http://forum.xda-developers.com/showthread.php?t=2184403).

Categories

Resources