Database Users

[Help] GT-7510 wifi froze after working fine and rebooting continuously

I successfully rooted my Tab from ICS to JB 4.1.2 a few days ago and it has been working fine. It suddenly froze in GMail app this evening. Held down power and attempted reboot. All fine until several revs of the CyanogenMod circle then it froze for a few seconds and then blank screened and rebooted with the Samsung Galaxy Tab 10.1 logo before going back to the CyanogenMod circle. Only stops the looping if I power from the mains. Battery is at about 55% and charging.
I have CWM-based Recovery v6.0.1.5 and I installed JB from cm-10-20121112-EXPERIMENTAL-p4wifi.zip
Can anyone help? I'm new to rooting etc..
Many thanks,
Stuart

Try booting into recovery and doing a full wipe of everything.
Sent From My GalaxyClass StarShip

Thanks
SouthPhilly said:
Try booting into recovery and doing a full wipe of everything.
Sent From My GalaxyClass StarShip
Click to expand...
Click to collapse
Many thanks for the reply SouthPhilly. It didn't work
There seemed to be a problem with formating /data. It just stopped when I tried it. Also stopped if I tried restore. The good news is that I did eventually overcome the problem by following qbking77's excellent info on
How to Unroot / Unbrick the Samsung Galaxy Tab 10.1 - Latest at www dot youtube dot com/watch?v=KYBs98R9rTs with file info at
www dot qbking77 dot com/samsung-galaxy-tab-1012.html
which results in a stock original unrooted GT-7510. From there I rooted back into CWM recovery and reflashed CM10 so I'm back with a working version of 4.1.2
I hope this info may help others unfortunate enough to get stuck like me.
I'm now happy again.
Best wishes to all.
Stuart G3SNA (QTHR)

Well perhaps not quite so happy!
For some strange reason I could not get the USB port to work. It did with my first attempt at flashing to CM 10 - JB 4.1.2 days ago but not now. I have tried all ways several times so eventually I returned to the qbking77 version of the stock 3.2, copied my CWM backups back to the sdcard, then reinstalled CWM recovery and restored from the backup. I now have what appears to be a fully working tab with USB connectivity running 4.0.4 ICS again. I'll stay with this untill JB gets a bit more stable. You never know, pink pigs may fly and Samsung may issue an OTA update :laugh:

Why didn't you flash a nightly instead of a ROM thats dated last month? The latest one runs fine on my p7510
http://get.cm/?device=p4wifi
Sent from my GT-I9100

I didn't know where to find the nightly files when I first did the root and rom flash. I just followed the links I could find using google. The whole thing looked good to start with and I ran it for the best part of a week before it froze up on me. I learned a lot in the last few days and now feel confident in what I'm doing. I did download last night's nightly this morning and flashed the rom. When I connected the usb cable to my pc failed to connect so I reverted to my original zip file thinking the nightly had an issue. Low and behold the usb cable connection failed with this as well. In both cases I did all the wipes and formats just like the first time. After that I gave up and decided to try to put my Tab back to ICS using the CWM backup I made as recommended before I started the first time. I'm no novice as far as computing is concerned but I haven't rooted an android device before.
If you take a look around the forums here you will find I am not the first to fail to find the nightly files. Perhaps a sticky with the link would be useful?

[Q]Boot err:A5,70,00,00,23 fixed

Hallo all.
This is my first post so please have a bit of patience with me.
So I have a Defy MB525 red lens which I had rooted and installed CM 7.1 back when that was cutting edge. As development progressed and updates to CM 9, CM 10 and CM 10.1 became available, I upgraded with no problems.
Last year in Sept messed up a upgrade, compounded the problem and messed up the battery. Order new battery and wall charger for battery. Wait long time for battery (customs problem), at last all is here and fix frozen boot problem. Boot up to installed sbf to find I made more problems by flashing this DEFYPLUS_U3_4.5.1-134_DFP-231_GR_SIGN_UCADEFYEMARAB1B80AA004.0R_PDS03C_USAJRDNGIBRRTCEE_P022_A022_Service1FF.sbf image. So now stuck with BL 7 and nowhere to go. Found this thread http://forum.xda-developers.com/showthread.php?t=1542956 which solved that problem (my thanks to the devs who sat down and found a way around this problem).
So now my Defy is rooted again, lets upgrade to CM 10 or CM10.1..........
Ooooops so what is this???????
Bootloader 09.10 ERR:A5,70,00,00,23
Every time I try to install I get this error. Every timehttp://forum.xda-developers.com/images/smilies/crying.gif. The only way to fix is to start power button and other finger on Vol+, now bootloader is OK, show no errors. The problem is that I have to start the install and root sequence from scratch using RSDlite 6.1.4, it is very time consuming.
I have searched internet and forums and found quite a few other people with the same error. But no understandable explanation for it, or a way to fix it.
I have tried CM 7.1, 7.2, 9, 10, 10.1 with kernel, without kernel, 2ndint, 2ndboot. No joy.
Is there a fix for it? Or a way around it? On one thread MSGinger 2 was mentioned, I have not tried it yet, but will look into it.
Thanks
Edit
Fixed the problem. Downloaded the latest Quarx CM10-2ndboot build and flashed using this guide (had been using all along)
http://forum.xda-developers.com/showthread.php?t=1795647
The previous build - 17.02 - failed during the flashing process, and then on reboot same boot error.
My apologies for this post.
Thanks for all the hard work by all in this community.

[Q] Defy Plus Bricked and no battery

Hi,
I tried to change ROM (from default) ad install googleapps my Defy+ and never got to the point where I saw android load up.
During the hole process everything ran 100%.
On the last system reboot nothing happened.
Now all i get on screen is:
Boatloader 0.9.1
battery low
cannot program
I have read many forum threads ans watch many videos but nothing worked.
I installed RDS Lite but am not sure which SBF to donwdload.
Plus, even if I get the correct sbf I never get to the message needed on the phone.
All I ever see is:
Boatloader 0.9.1
battery low
cannot program
Any ideas how to get the phone back to working condition?
Thanks

Nexus 4 - Bootloop Following Contact With Water? Or recent update?

Bootloop following contact with water? Or recent update?
Hello,
Here is my story : end of last wwek, my phone fall in a small amount of water (1cm) on the top (jack side). I wiped it very fast and use it for the next 30 min, everything is good. and then i let it 2 hours (charging or not i don't remember, i don't know if it can matter). After that i find it bootlooping was there an update, end of last week? Anyway i let it in that state at least 30 min and even more and then tried to restart it not better. I also tried a wipe cache and after that a factory reset, nothing...
Yersterday back to home, i tried to flash the 5.0.1 factory image ( didn't want to take the 5.1, because i feared a possible bad update on the image maybe) nothing better, even worst because after after some time of bootlooping, i've got the red light flashing :/
Same goes for the 4.4 flash but small miracle, it's working 4.2.2... During all those tries, i did some oem lock and unlock before and after each flash.
So my phone is working with the first version of android available, which is not the best.... I also tried the OTA update to the 4.3 and i also got stuck to a bootloop
So after that long story (sorry), I defer to your expertise because i don't know what else to do.
Please help :/

I just installed the lastest version of cyanogen and it's working well...
Still no idea whats happening there?

Seems to be a real big question i ask you there, but i continue my thinking on my side.
I dont like the idea, but it light be a hardware problem... Maybe a failing memory slot, or an unused component until then.
So it brings me 2 questions : how and where could i find logs after a failed update?
And how could i efficiently test my hardware CPU, RAM, as we can do on a computer?
Thanks in advance, any idea, help, joke are welcome

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