Database Users

[Q] eLocity just quit...won't boot up

I have been running my a7 with dexter's mod 1.4 for about 1 1/2 weeks...everything has gone well. This afternoon I turned on the device and it failed to complete boot. The word Android would come up and then nothing. I tried to reboot, reset, but device would do neither...nor would it turn off completely. I kept trying to take it into recovery mode and then after several tries was able to wipe, do update again, and get everything back as before. What would cause this and should I look for this to happen again? deepmagic
My a7 was running well for about a week since it quit...but today when I booted up device, it failed to recognize sd card...same card used for updating to mod 1.4...same card I've been using to listen to my music, etc...but now won't recognize...I've tried two different micro sdhc cards..formatted, reformatted, but device continues to display mount sd card...all else works fine! Does anyone have any new ideas? I can't even reinstall mod since a7 can't read my cards. Thanks for any input that would be helpful. I understand these issues are ongoing for many out there...what to do?

deepmagic said:
I have been running my a7 with dexter's mod 1.4 for about 1 1/2 weeks...everything has gone well. This afternoon I turned on the device and it failed to complete boot. The word Android would come up and then nothing. I tried to reboot, reset, but device would do neither...nor would it turn off completely. I kept trying to take it into recovery mode and then after several tries was able to wipe, do update again, and get everything back as before. What would cause this and should I look for this to happen again? deepmagic
Click to expand...
Click to collapse
Mine has hung on a black screen on me. Seemed that it didn't fully come out of sleep mode.
I was able to recover by holding the power button for 15 seconds to hard power down. No data loss.

deepmagic said:
I have been running my a7 with dexter's mod 1.4 for about 1 1/2 weeks...everything has gone well. This afternoon I turned on the device and it failed to complete boot. The word Android would come up and then nothing. I tried to reboot, reset, but device would do neither...nor would it turn off completely. I kept trying to take it into recovery mode and then after several tries was able to wipe, do update again, and get everything back as before. What would cause this and should I look for this to happen again? deepmagic
Click to expand...
Click to collapse
Exact same thing happened to me this morning. Tried to reset - not happening. Hard powered down. Don't have time to try anything else right now. I'm new to the forums and new to android. Wish me luck! I've been loving my A7, and much appreciation to Dexter and all the other knowledgeable hackers/modders/posters.

hey the same thing happened 2 me twice. Once the first day after i got it, since i had only had it for 1 day i wiped it reinstalled dexter's mod 1.41 and it worked. First app i installed was backup root. Now, a week later the exact same thing is happening. This time i dont want to wipe it because of all of the apps i have installed, games ive played etc. Any ideas? Could we just try reinstalling dexter's md without wiping? Or wiping reinstalling and recover from a backup?
Also have you installed busybox? I had just installed it both times before it failed to turn on. Maybe its just coincidence but you never know..
-D
Thanks to anyone who can help! and also thanks Dexter for all your hard work as well as everyone else that has contributed to the elocity, im lovin it! (when it works )

success!!!!
I got it to work! I don't have a permanent fix but if it happens again just boot into recovery and reinstall the dexter's mod update 1.41 and it works again! No wiping required. This isn't a permanent fix but it will work until we find one
-Dylan

Hasn't happened to me (yet) but I didn't upgrade to the newest ROM. I'm still using 1.3and it has been very stable. Only issue I've had was when I tried to use Killswitch to go to sleep mode when the cover is shut (great idea) but it didn't work and froze all except the live wallpaper. Weird.
Good luck, guys.

in the event it does happen to you, you might want to check out my apx thread for reflashing the factory firmware if you can't get your tablet unstuck. theres alternatives if you don't want to get stuck again.

The method you outline seems so complex...way above my abilities, but makes me wish I had followed though on some early programming training opportunities. That was the road not travelled.

okantomi; while i wouldn't encourage others to follow thru with procedures they fear would cause more harm, i would mention that if you google up my nick you'll find i've been able to do much w/ android software and devices while not knowing anything about programming. if i can do it, anyone can. i just wanted some themes for my phone.
i'm just an android hobbyist by night (and when i get a chance during the day), and a computer tech by day. no programming expertise, but i can reasonably reverse engineer and port software and components using simple file managers like ztreewin(trialware).
don't be mistaken that the folks out there providing you solutions necessarily know anything about programming or software development. just how to chef up files at different levels. i understand this doesn't go for everybody.

Thanks for the encouragement. I'm impressed with what you've been able to do. It is also nice to read upbeat comments about the A7. There is something sort of special about a device that you really almost have to build yourself... putting so much into it... biting your fingernails to nubs with each ROM flashing. You don't get as attached to any device that is 100 percent complete right out of the box, though of course there would be a lot less aggravation.

[Q] Battery is not recognized

Hi all,
Nasty problem with my 1 month old Motorola Defy+ (MB526)
Last weekend I installed ICS9 from Quarx (20120318 build). I did this using 2ndinit CWM. Made an android backup of my stock setup, I did this over my stock SBF 4.5.1.-134_DFP-74. Used the gapps.zip and battery fix.
The system worked pretty well, but time by time it was unstable. When turned off, it had lots of difficulty to boot up again, lots of reboots and 2-3 battery pulls.
I was planning to flash another ROM when I had the time. Yesterday it worked well, started fully loaded, used it as MP3 for long time, when I went to sleep it was 48% (the accu).
This morning, I stepped in car and phone turned out to be dead. Connected it to my car charger, and it came back to life. However, immediate reboot etc. So I decided to (while driving) put back my stock nandroid backup.
It all turned out well. Stock ROM booted but gave the notice (translation from dutch): "Battery of your device is invalid and cannot be charged. Replace the battery with a battery from your Motorola"
hmm, tried it with my USB cable at the office, and now at home again with the normal charger..
What happened? Any ideas on how to solve this?
The complication is that now my device is rooted and has 2ndinit starter, warranty is more difficult.

Solution: red lens battery fix
I’m not sure it’s exactly the same issue, but my Defy+ totally refuses to charge with Quarx CM9 build 20120318 + CM9 kernel from [1].
Unfortunately I noticed only once the battery was dead empty.
I couldn’t even get it to boot with the USB charger pluged in, and the only way I could get it to boot again was to charge my battery pack in friend’s Defy.
Then I applied the « Battery fix for red lens » provided here [1] which kind of fixed the problem. Now the battery charges again, but it won’t charge over 80/85%.
I had done a « Clean battery stats » from the boot menu after installing CM9 before this whole story, so I don’t know if it had any effect.
If anyone knows better please let me know!
The instability you noticed may be due to the Android debug bug… in CM9 builds. You have to leave Android USB debug (from System params->Debug features, translated from french on, otherwise it will lag like hell most of the time and drain the battery due to the init process eating up the CPU.
[1] http://forum.xda-developers.com/showthread.php?t=1432100

Hi, I installed the battery fix immediatly after flashing the Quarx ROM, so that should not be the problem.
In the meanwhile I have been trying some things with the battery calibration software. That one flawlessy sees that my battery is 100% charged (i did that using the mcguyver method). But, resetting the calibration file on the phone won't help.
In the meantime I have been able to delete all traces (2ndinit boot, titanium backup and unrooted my phone) so I am considering to RMA the phone, no matter the fact how long that is going to take..
Unless, someone here has a last excellent advice..

fokkeh said:
...the mcguyver method...
Click to expand...
Click to collapse
Great! You have just fried your battery (like a few others who tried going McGyver). Get a new battery now and don't use the McGyver method again

From what do you draw this conclusion?
The battery showed more problems BEFORE i used the mcguyver method than after. When the problems started I never even heard of the method. I used it to regain life in my mobile (which I am using atm) and charge the battery, which was succesfull. Charger over USB does not work (because battery is not recognized), but that problem occured before the mcguyver.
So until now for me it did not cause the problem, but it helped me to be able to use my phone again, much better than before. I performed the method very accurately and I am 100% sure it did not make contact with connectors it should not connect to.

fokkeh said:
From what do you draw this conclusion?
The battery showed more problems BEFORE i used the mcguyver method than after. When the problems started I never even heard of the method. I used it to regain life in my mobile (which I am using atm) and charge the battery, which was succesfull. Charger over USB does not work (because battery is not recognized), but that problem occured before the mcguyver.
So until now for me it did not cause the problem, but it helped me to be able to use my phone again, much better than before. I performed the method very accurately and I am 100% sure it did not make contact with connectors it should not connect to.
Click to expand...
Click to collapse
Well now that your phone is alive, then go to stock and reclaim warranty! Do RMA.!

Yes I will, restored everything to stock and deleted trace from MicroSD.
But, I am still annoyed by the fact that my phone will be gone for 3-4 weeks

fokkeh said:
Yes I will, restored everything to stock and deleted trace from MicroSD.
But, I am still annoyed by the fact that my phone will be gone for 3-4 weeks
Click to expand...
Click to collapse
I understand that bro!! Even my phone was away for couple of weeks recently! Just pray they don't flash the latest SBF(BL7_ as they did in mine!

Does flashing a full sbf not work either? like this http://forum.xda-developers.com/showthread.php?t=1574651

Puckying said:
Does flashing a full sbf not work either? like this http://forum.xda-developers.com/showthread.php?t=1574651
Click to expand...
Click to collapse
Hi, this morning everything changed again, I decided to give it one more try with the latest Quarx CM9 nightly (20120330), wiped data, flashed nightly.zip, gapps and kernel but waited with the battery. After that I wiped cache, dalvik and battery stats.
Reboot and battery seems alive? very strange. But I don't want the kind of buggy CM9 builds anymore, so decided to put back my 2 hours old nandroid backup, using Restore.
Strangly, battery problem was back again. ****! Than just for fun I did data/cache/dalvik/battery stats wipe on stock, and that did not help either.
Now I am back on CM9 again, but thats running O.K. (battery is working!) but not stable enough for me. CM7 (cannot remember which build) gave the problem as well.
With the latter in mind I think (and thus agree with you) flashing a fresh SBF will probably solve the problem, but I am not 100% sure. I want to be able to put back my stock setup for possible RMA. My stock is 4.5.1.-134_DFP-74 and I cannot find that one on internet. And I cannot put it back to stock otherwise right?
The one Pranks gave you in your post (4.5.1-134_DFP-1321) is that a deblurred one? Because when I put a new one, I would like it to be a deblurred. I hate all the bloatware.

I have no idea, but I think he said it was from his own defy so I am guessing it the complete original blurred thing.
---------- Post added at 01:57 PM ---------- Previous post was at 01:31 PM ----------
I redid the cm9 flashing too and now at least it is telling me the battery is charging. But it stays stuck at a big battery icon and a red led is on.
Will see if it goes past that screen with a bit more juice.
---------- Post added at 02:06 PM ---------- Previous post was at 01:57 PM ----------
Yessss, it started up!

All is fixed. I flashed the proposed stock non-fixed SBF and now running stock 2.3.6 without any battery problems. Excellent The SBF is rootable.
I removed BLUR by editing build.prop as proposed somewhere on this forum. you have to perform full wipe after editing the build.prop) I am very happy with me new DEBLURRED stock. Titanium can remove other bloatwhere like "cardiotrainer".
Happy

fokkeh said:
All is fixed. I flashed the proposed stock non-fixed SBF and now running stock 2.3.6 without any battery problems. Excellent The SBF is rootable.
I removed BLUR by editing build.prop as proposed somewhere on this forum. you have to perform full wipe after editing the build.prop) I am very happy with me new DEBLURRED stock. Titanium can remove other bloatwhere like "cardiotrainer".
Happy
Click to expand...
Click to collapse
Cardiotrainer however for me is one of the most imp app!!

[Q] ParanoidAndroid boot loop

I bought a used Nook Color this spring on ebay, already rooted. It is JellyBean 4.1.2, CM10-20121216-UNOFFICIAL, ParanoidAndroid 2.99. It had Goo Manager, but not TWRP that I could tell.
It's always gone into boot loops, when I asked the seller he said use Goo Manager to look for an update. There has never been an update found. I tried installing TWRP through Goo Manager today, but it tells me no recoveries found. May have managed to install from the computer's Play Store, haven't been able to check yet because it is still looping. (Does not look like it downloaded, many updates were ahead of it.)
The past few weeks it has spent more time rebooting than working. Cyanoboot loads, but the little jellybean guy just glows and the eyes move around on the beans. Sometimes it will load after awhile, sometimes it takes hours. I have it charging the whole time, but it does not charge while it is looping. Once it finally loads and I unlock it, it shows a popup that Process Service isn't responding. If I hit wait, it will load.
The NC did not come with a charger, I bought a non-OEM charger on Amazon that was listed as NC-compatible. It seems to work fine, although doesn't quite keep up when watching video or anything screen-intensive. I normally leave the NC plugged in when I am home, when it comes out of the looping it is usually in the 90 plus percent range. I tried leaving it unplugged overnight while looping once, it ran down fairly low but recharged fully after finally loading.
For a week or two before the constant looping started, two other issues appeared. When I woke it up in the morning, it would not be connected to wifi. The icon is just an outline, and when I check under settings it says scanning for wifi networks. If I reboot, it connects fine.
The second problem is the SD card keeps unmounting. Generally I will get a popup from Evernote that the SD card has changed. Most of the time if I go into settings > storage I can see that the card is unmounted and tell it to mount. Sometimes it says it is mounted, so then I reboot. Today I noticed the internal card was also showing as unmounted. I was able to mount both, at least until the NC rebooted itself again. I'm using a SanDisk Ultra (Class 10) 32 GB card.
It finally loaded, but looks like no wifi again. Battery is at 92 percent. It did finally manually connect after telling me avoided due to poor connection (about 5 feet tops away from the modem).
Would re-rooting or flashing a new ROM work, or is something else wrong? Why can't Goo Manager find any updates?
Thanks for any help!

I used that ROM for a while, it had some issues, but for the most part I enjoyed it. The SD I mounting issue can usually be solved by formatting it with your computer, and the bootloops can be fixed by reinstalling the ROM. Make a twrp sd card. (There's a thread in here somewhere) and reinstall it, or install other roms if you decide you don't like this one.
---------- Post added at 03:19 PM ---------- Previous post was at 03:19 PM ----------
Also, goo manager simply doesn't work with the pa 2.99 rom. Don't know why.

Mineturtle33 said:
I used that ROM for a while, it had some issues, but for the most part I enjoyed it. The SD I mounting issue can usually be solved by formatting it with your computer, and the bootloops can be fixed by reinstalling the ROM. Make a twrp sd card. (There's a thread in here somewhere) and reinstall it, or install other roms if you decide you don't like this one.
---------- Post added at 03:19 PM ---------- Previous post was at 03:19 PM ----------
Also, goo manager simply doesn't work with the pa 2.99 rom. Don't know why.
Click to expand...
Click to collapse
I can't find any recoveries, finally managed to install ClockworkMod's ROM Manager and it says both ClockworkMod and TWRP recoveries are there somewhere. SD card was unmounted again and while remounting it went into a bootloop again
Off to look for the twrp card thread, thanks!

I think I softbricked, but only CM13 seems to fix on my N7. What did I do/how to fix

Guys,
I'm not even sure where to start with what I'm seeing, but maybe you can help me.
I have had Timur's ROM on my N7 2012 for a couple years. It's been crashing randomly, even though I have few things installed on it, and a good power supply. I took it out of my car and put it on an iPad 2 amp supply, and it still crashed a bunch so I knew I needed to wipe and reinstall. I also wanted to go from 4.2.2 to 5+, which I know takes away a lot of the good features I need (like power on/deep sleep).
I booted into TWRP and wiped my tablet, which appeared to softbrick it (I think I have the usage right from searching). I downloaded the Pure Nexus 6.0.1, CM13, and already had Autodroid ROMs to use. I tried to install Pure through ADB sideload, and got it installed. When I finished and tried to reboot, it said I had no OS. When I rebooted, I got the boot animation, and nothing else.
Long story short, I tried Autodroid and CM13, and using CM13 I got it back going. Unfortunately, every time I try to flash another ROM over it, it will no longer go past the boot screen. With CM13, it boots properly, but doesn't like the gapps pico I tried to install (error message when booted, keeps returning to the same pop up error).
I'm quite sure there's something I'm missing, but I don't know what it is.
Thanks!
Eric

Ok, before anyone goes nuclear on me, I think I better understand what happened. When I got ANYTHING to work, I stopped doing anything. As I understand, it wasn't functioning...it was just in a temporary mode of some sort.
After not being able to get it to work properly, I used this: http://forum.xda-developers.com/showthread.php?t=1781250 to try and restore the system. I followed all the directions, except for using the 5.1.1 version of the ROM, and used the corresponding file name for the zip file used.
After doing so, the bootloader won't go to TWRP, but goes to the pic as seen below. I did reboot the tablet, and after waiting quite a while, the tablet came on, but I don't understand what that picture means.
Thanks!
Eric

Ok...I realized that I lost root. I'm fixing it now. I had read before, but didn't understand what I saw.
Thanks,
Eric

my S7 edge is hard bricked

I had BlackDiamond.N8.PIE.V2.0 over a year on my phone and it was working with no problem.
today I decided to update my phone, first updated the TWRP to the latest version "TWRP-3.4.0-0-hero2lte" updated without any problem,
then I downloaded BlackDiamond N8 Port V10.0, wiped everything (even internal storage), and installed the ROM,
it installed successfully, wiped the caches, reboot to the system, android loaded without any issue,
after loading into android, I added my google account, and I was testing the phone, after 10min of working with the phone,
while I was testing the camera app (it's was a little laggy) my phone freezes and after a couple of seconds, the screen went black! I thought it's gonna reboot, but nothing happened.
I tried to hard reset the phone by pressing "power+volume down+home key", but it didn't work, connecting to the charger is nothing happen, there is no LED light, my phone is completely dead
does anyone have any idea why this happened? installation and booting to android was completely fine, everything worked fine, and suddenly my phone freeze and hard bricked.
you know this is not the first time I'm installing custom ROM, I'm done it before and I've always been careful, never had any issue like this, but this time really I don't know what happened and to be honest, I really love my S7 Edge, I don't want to replace it.

aalireza439 said:
I had BlackDiamond.N8.PIE.V2.0 over a year on my phone and it was working with no problem.
today I decided to update my phone, first updated the TWRP to the latest version "TWRP-3.4.0-0-hero2lte" updated without any problem,
then I downloaded BlackDiamond N8 Port V10.0, wiped everything (even internal storage), and installed the ROM,
it installed successfully, wiped the caches, reboot to the system, android loaded without any issue,
after loading into android, I added my google account, and I was testing the phone, after 10min of working with the phone,
while I was testing the camera app (it's was a little laggy) my phone freezes and after a couple of seconds, the screen went black! I thought it's gonna reboot, but nothing happened.
I tried to hard reset the phone by pressing "power+volume down+home key", but it didn't work, connecting to the charger is nothing happen, there is no LED light, my phone is completely dead
does anyone have any idea why this happened? installation and booting to android was completely fine, everything worked fine, and suddenly my phone freeze and hard bricked.
you know this is not the first time I'm installing custom ROM, I'm done it before and I've always been careful, never had any issue like this, but this time really I don't know what happened and to be honest, I really love my S7 Edge, I don't want to replace it.
Click to expand...
Click to collapse
Possibly a hardware problem. You will have to take some technician for a more accurate analysis.

Dark Stranger said:
Possibly a hardware problem. You will have to take some technician for a more accurate analysis.
Click to expand...
Click to collapse
if it's hardware, why I didn't have any problem before updating the ROM? is it possible updating damaged the phone?

one more thing, I saw some people use a dongle called USB-JIG on dead Samsung phones, that enter phone to download mode and after that flashing with Odin.
do you think it's work on my phone?

aalireza439 said:
if it's hardware, why I didn't have any problem before updating the ROM? is it possible updating damaged the phone?
Click to expand...
Click to collapse
It can occur, despite being very difficult. I already corrupted the xperia bootloader I had, but it never happened on my samsung devices. I even have a s7 edege and I am changing his rom and I never had any problems. As I said, you should take the device to an assistance center to get an idea of what really happened. Perhaps it could be a hidden problem, which was only expressed by changing the rom, or it could give the same problem with the old rom. What I can say is that a simple exchange of rom, would hardly cause a hard brick in a device.
---------- Post added at 12:52 AM ---------- Previous post was at 12:50 AM ----------
aalireza439 said:
one more thing, I saw some people use a dongle called USB-JIG on dead Samsung phones, that enter phone to download mode and after that flashing with Odin.
do you think it's work on my phone?
Click to expand...
Click to collapse
You can also try, because if your device is not completely dead, it can come back to life with this procedure. But I still recommend taking the device in for a technical assistance.

There are 3 cases in this:
1. If you flashed a corrupted/wrong bootloader in twrp/flashfire or anything that doesn't blocks a wrong flash like odin. Your phone is dead for good. Only a usb jig/repair box or a local mobile technician can fix that.
2. Your phone is bugged with black screen. Installing a custom rom can cause weird things. Sometimes hard stuck with screen off/black .. now you need to wait for battery draining itself completely and then plugging in charger and trying to get in download mode. If you could go in download mode then you can reflash through odin and it will be back to normal. Although sudden turn off and then complete deadness is often a hardware failure.
3. If phone after draining completely doesn't shows life when connected to charger and can't go in dl mode then its either hardware failure or bootloader problem like in no.1 point. You will need to take it to a mobile repairer or use a repair box/jig nevertheless.
Sent from my hero2lte using XDA Labs