Related
Hello guys
I need your help here. So I flashed this new ROM, and the Google Push service seemed to have stopped working completely.
1. Gmail not pushing.
2. K9 push not working
3. Google play store not pushing as well
I have played around (sync on,etc) but I can't seem to find what's wrong with it. So I tried to restore a previous Nandroid backup, but the md5 checksum was mismatched!
I then tried to wipe everything, reflash new ROM etc, and yet the Google Push services aren't working as well.
Can anyone help? I am stuck, I can't go back due to md5 checksum error, and I can't move forward because I don't get Google Push services
budisuharto said:
Hello guys
I need your help here. So I flashed this new ROM, and the Google Push service seemed to have stopped working completely.
1. Gmail not pushing.
2. K9 push not working
3. Google play store not pushing as well
I have played around (sync on,etc) but I can't seem to find what's wrong with it. So I tried to restore a previous Nandroid backup, but the md5 checksum was mismatched!
I then tried to wipe everything, reflash new ROM etc, and yet the Google Push services aren't working as well.
Can anyone help? I am stuck, I can't go back due to md5 checksum error, and I can't move forward because I don't get Google Push services
Click to expand...
Click to collapse
go to settings , accounts , Google delete it , then log in again
Yup, done that, still doesn't work. Plus k9 push isn't working either, it seems that the whole push function is completely broken
Sent from my GT-I9300 using xda app-developers app
Push seems an issue with XXDLI8 (at least in HyperGalaxy 1.8), just revert back to XXDLI7.
Yup I read about that too. The thing is I'm still on ICS, and I have never flashed a jb rom before. The error happened when I flashed hyper galaxy 0.7, which is a ics build.
I have given up on that rom, and I'm not on other rom and the push problem persists. I'm not sure what I did wrong, it's like the problem sticks despite me wiping cache, and everything else.
Sent from my GT-I9300 using xda app-developers app
Maybe you can supply some more info, like what ROM and version are yiu using now, which baseband and what install procedure did you follow exactly?
j0ep0 said:
Maybe you can supply some more info, like what ROM and version are yiu using now, which baseband and what install procedure did you follow exactly?
Click to expand...
Click to collapse
Sure, here it goes. I have been flashing ROMs etc since 2010, so I am quite familiar with the concept, but this baffles me, before I can't seem to wipe everything clean and restart from point zero, because the problem sticks even after a new ROM is flashed. Is there more to this? Like modem/baseband etc? Thanks in advance for your help!
Baseband I9300XXLH1
Kernel Siyah s3 v 1.5 beta 4
Build no IMM76D.I9300XXBLG9
WanamLite ROM XXBLG V2.2
Thank you!!!
Ok I got it figured out already.
Previously I was on a full feature rom, then I flashed to a stripped down rom. I was short of a few apps, so i flashed additional apps, extracted from titanium etc, without checking their compatibility etc.
When I flash a new rom after that, I'll restore all system data via titanium, and that's why the problem persists. If I flash a new rom without restoring system data, then it's fine.
It's strange though, you'd think that titanium would be able to pick up on that if they aren't compatible.
Anyway problem solved and thanks for your kind assistance!
Sent from my GT-I9300 using xda app-developers app
well happy that you found out a solution. generally titanium backup is used only for restoring apps not for system settings
jaidev.s said:
well happy that you found out a solution. generally titanium backup is used only for restoring apps not for system settings
Click to expand...
Click to collapse
Yea I realised that with SGS 3. With HTC Desire on Froyo/GB, the issue was nearly non existent, I never had a single issue, be it from Sense to AOSP, back to Sense etc.
Flashing is quite a pain then, if system apps can't be restored via Titanium, having to re apply settings like ringtones, widgets etc?
u can make a nandroid backup and restore
do kernels affect push ?
sorry to bring up an old thread, but i didn't want to open a new one just for this
i've recently flashed Perseus 24.2 over Omega 27.2 and noticed that Push notifications dont work when the phone is sleeping.
to get it working, i have to open up the app (eg. Whatsapp, hotmail) and i get all of them at once.
did a nandroid rollback to stock kernel and it was working fine
Q. is there a specific setting to kernels that may affect push?
probably Android ID problem
i didn't want to open a new thread for same kind of problem.
Problem occured when i fresh install DLIB (with wipes and everything). After installation complete, i've restored apps + systemdata with titanium. While restoring, it asked me to whether use new android id or restore the old one in backup. I choose to restore old one. then problems started.
- I can't use Google Play on the web. It says "there is no phone connected to this google account"
- none of my notifications are working. and i assume it is about android id. (today using Titanium i switched to new android id but nothing changed)
any guesses?
Ok so i was having some laggy issues w the x2 and all the sudden i started getting process not working for things like nova laucher and such. SO i went into BSR to wipe cache and fix the permissions. Did that and now the phone sits on the Big M boot screen. Why wont it boot up. I didnt wipe dat or try to flash anything. Any way to get the phone up and runnig again w/ o SBF'g
jeff5347 said:
Ok so i was having some laggy issues w the x2 and all the sudden i started getting process not working for things like nova laucher and such. SO i went into BSR to wipe cache and fix the permissions. Did that and now the phone sits on the Big M boot screen. Why wont it boot up. I didnt wipe dat or try to flash anything. Any way to get the phone up and runnig again w/ o SBF'g
Click to expand...
Click to collapse
Well what ROM are you using for starters.
that might be important right.. .sorry.. its aokp 6
Ok. Well if you can get back into BSR, try and wipe the dalvik cache in the advance settings. I never use the fix permissions option. Maybe that did something to your device.
did that too. Still on the boot logo. is a sbf in order
jeff5347 said:
did that too. Still on the boot logo. is a sbf in order
Click to expand...
Click to collapse
Well I wouldnt see why it would do that if you just wiped cache and fixed permissions. Did you have any other mods on there? Were you using the patched CM7 BSR and not the original one?
i was using the motodx2_bootstrap_signed.apk. Not sure if the cm7 or not. Ive used this on eclipse and aokp
jeff5347 said:
i was using the motodx2_bootstrap_signed.apk. Not sure if the cm7 or not. Ive used this on eclipse and aokp
Click to expand...
Click to collapse
That one is fine to use on Eclipse. But pretty much any other ROM we have (CM7, CM9, CM10, AOKP, Paranoid Android and I think even MIUI), you need to use the CM7 BSR named "MOTODX2_Bootstrap-CM7-signed.apk" which is found in the CM7 thread. That may have been the problem.
really... damn. i dl'd it so when i flash cm10 but did not install it for thw aokp. Just off your thoughts is the cm10 stable enough now to install. i have no prob putting aokp back on but im nott looking for stability problems. If cm10 isnt stable yet i van wait
jeff5347 said:
really... damn. i dl'd it so when i flash cm10 but did not install it for thw aokp. Just off your thoughts is the cm10 stable enough now to install. i have no prob putting aokp back on but im nott looking for stability problems. If cm10 isnt stable yet i van wait
Click to expand...
Click to collapse
I think CM10 is more stable than any of the ICS ROMs. But with the stability, there comes other small issues that the ICS ROMs dont have. Its a trade off. Main issues of CM10:
1. Messing with bluetooth may cause phone to crash durring calls. Reboot fixes it until bluetooth is messed with again. (Might be fixed with an update)
2. Storage is in a different location. Not really an issue but its also swapped back to the original 4gigs for the internal. All your files will be flipped after using other ROMs for so long. (not a huge deal)
3. Due to the storage being moved around, apps that are stored on the SD card will disappear after reboot. (will probably be fixed in the future)
4. Flashing ROMs in recovery wont work. If any update comes out, you have to either SBF and update or nandroid back to ICS and update. (again, not a huge issue)
Other than that, I cant really think of any bad stuff. Its faster and I have no random reboots. I recommend it if you can live with the issues I mentioned which are honestly not bad.
Also, with the BSR files, in case you dont know already. When you are on stock 2.3.4, you first use the original BSR. Then when you flash CM10, you install the CM7 BSR.
Thanks JS
1. I never use blue tooth so then i should be all set then.. correct?
2. didnt aokp have that. I know the eclipse rom had the flip flop in it to read right but aokp i had to move my music and such so wouldnt i still be in the same boat or is it different than oakp?
3. i have some apps.. such as thems i have downloaded off of xda. So once installed they will work but rebooting will make them dissapear? is there a way to put these on the phone memory? Also curious i have google drive and have some of these installed on the drive. Will they still work or do they just dl to the sd and still not work?
4 i dont have a problem sbf'g but wondering if i nandroid the a2, will i be able to sbf, install root, a3 ect and do a data restore to get my info back?
also i will take the cm7 bsr and remeber that. Thanks
jeff5347 said:
Thanks JS
1. I never use blue tooth so then i should be all set then.. correct?
2. didnt aokp have that. I know the eclipse rom had the flip flop in it to read right but aokp i had to move my music and such so wouldnt i still be in the same boat or is it different than oakp?
3. i have some apps.. such as thems i have downloaded off of xda. So once installed they will work but rebooting will make them dissapear? is there a way to put these on the phone memory? Also curious i have google drive and have some of these installed on the drive. Will they still work or do they just dl to the sd and still not work?
4 i dont have a problem sbf'g but wondering if i nandroid the a2, will i be able to sbf, install root, a3 ect and do a data restore to get my info back?
also i will take the cm7 bsr and remeber that. Thanks
Click to expand...
Click to collapse
1. I use bluetooth every now and then but I never turn it off. It seems that toggling the bluetooth on and off or visa versa triggers the issue and a reboot fixes it again.
2. I forget what Eclipse had. Its been so long. But ever since CM7, the flip flop mod has been included in all the ROMs which meant you got your SD card (which the droid X2 comes with 8GB) as internal storage and the actual 4GB internal storage was turned into the "external storage." CM10 reverted back to the original 4GB internal and 8GB external.
3. Everything you download and install on your phone will usually be installed on the internal storage. I think if you have apps over a certain size (which isnt very many. Mostly games), they are installed on your SD card. Those are the ones the system has a problem reading after a reboot. the actual files you have downloaded from XDA will still be there. Just installed apps might disappear.
4. Not really sure what you are asking here. But if you get A2 installed and up and running and A3 comes out, You will pretty much need to start over. But for me, thats fine. I use Titanium Backup and restore everything after a wipe anyway. What data are you referring to?
ok so this is the gapps md5
MD5sum: f62cfe4a827202899919fd932d5246d7
and gapps-jb-20120726-signed.zip
is this correct
jeff5347 said:
ok so this is the gapps md5
MD5sum: f62cfe4a827202899919fd932d5246d7
and gapps-jb-20120726-signed.zip
is this correct
Click to expand...
Click to collapse
Honestly, I dont even know what MD5sum means. I'm not that tech smart. lol. I know thats the right file name though. And if you got it from here: http://goo.im/gapps you should be fine.
hahaha neither do i lol yea thats where i got it.. again thank you
No problem. If you have any other issues, just reply here and I'll help out.
one last th. sbf'd. trying t oroot with petes like i always have but it wont recognize the phone i enables debugging and unknown sources. Am i forgetting something. havent done this in a bit
jeff5347 said:
one last th. sbf'd. trying t oroot with petes like i always have but it wont recognize the phone i enables debugging and unknown sources. Am i forgetting something. havent done this in a bit
Click to expand...
Click to collapse
Pete's can be a PITA... If usb debug is enabled and unkown sources is checked just keep trying. I've had to "one click" 5 or 6 times before it works right. Close the program between tries. Also make sure your phone isn't in PC charge mode or anything.
Sorry for not updating this. After trying for 2 hrs I started trying everything. It turned out I had to use the cable that came w the dx2. No other cables worked
Sent from my MB870 using xda premium
Ah, my bad I should have read the time stamp. Anyway yea, the cable is a big deal (even though that sounds crazy.)
---------- Post added at 10:54 PM ---------- Previous post was at 10:43 PM ----------
Lol oh and btw MD5 checksums are
"The MD5 checksum for a file is a 128-bit value, something like a fingerprint of the file. There is a very small possibility of getting two identical checksums of two different files. This feature can be useful both for comparing the files and their integrity control."
Hi,
My EVO 4G LTE is S-OFF. I've been running FreshROM 5.3.1 since it was released without issue. Last Thursday I started getting a lot of backround app crashes. Not a big deal, I wiped, reloaded the ROM, then restored everything via Titanium Backup pro. All was well for a couple of days.
Yesterday, my battery died within about 3 hours. Normally, I go over 16 hours. After some investigation and I found a process 'flush-179:0' eating CPU (and battery). I've wiped, flashed again, even flashed different ROMs. It's still there; every time.
I found one post on XDA where someone said it was caused by a performance tweak app (http://forum.xda-developers.com/showthread.php?t=2016993). Their fix was to flash stock, radios, etc. then root again. I haven't used any apps to tweak anything. So, if it's a similar cause...data/config corruption?
Has anyone else seen this? Does anyone know of a fix?
Thanks!
I'm not familiar with this specific issue but you mentioned that you restored everything using titanium backup. If you are experiencing problems I would strongly recommend NOT restoring all data as you may be restoring that very same issue. If you don't want to have to start all over then at least only restore just apps and data. Never system data.
Sent from my EVO using Tapatalk 2
eddy0090 said:
I'm not familiar with this specific issue but you mentioned that you restored everything using titanium backup. If you are experiencing problems I would strongly recommend NOT restoring all data as you may be restoring that very same issue. If you don't want to have to start all over then at least only restore just apps and data. Never system data.
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
Of course, the problem is that it's there when I wipe and flash a new ROM (Fresh, Rejuvenated, etc.). Even before I load my data via TB.
zisix said:
Hi,
My EVO 4G LTE is S-OFF. I've been running FreshROM 5.3.1 since it was released without issue. Last Thursday I started getting a lot of backround app crashes. Not a big deal, I wiped, reloaded the ROM, then restored everything via Titanium Backup pro. All was well for a couple of days.
Yesterday, my battery died within about 3 hours. Normally, I go over 16 hours. After some investigation and I found a process 'flush-179:0' eating CPU (and battery). I've wiped, flashed again, even flashed different ROMs. It's still there; every time.
I found one post on XDA where someone said it was caused by a performance tweak app (http://forum.xda-developers.com/showthread.php?t=2016993). Their fix was to flash stock, radios, etc. then root again. I haven't used any apps to tweak anything. So, if it's a similar cause...data/config corruption?
Has anyone else seen this? Does anyone know of a fix?
Thanks!
Click to expand...
Click to collapse
u should try mean rom 6.5 ICS.. if your still on the old base.. or flash new firmwear and radio in bootloader then flash a new jelly bean rom if u want to try the new base out
evo401 said:
u should try mean rom 6.5 ICS.. if your still on the old base.. or flash new firmwear and radio in bootloader then flash a new jelly bean rom if u want to try the new base out
Click to expand...
Click to collapse
I think I will; this seems to fit with the latest info I just figured out.
I flashed Fresh again, and suddenly started getting the warning about the SD card being damaged and to format it (as we know, that's not the external SD card). No matter how many times I format it, the error comes back. From some other searching, the 'flush-179:0' process seems to have something to do with storage, maybe because it can't read that partition it's causing issues.
I updated the firmware and radio, still no luck.
So I tried loading another ROM (I went with Mean Bean). That fixed the issue with the SD Card partition being unreadable/unformatable. Maybe that was caused by multiple flashes
But, the flush-179:0 process is still eating CPU and battery.
zisix said:
I updated the firmware and radio, still no luck.
So I tried loading another ROM (I went with Mean Bean). That fixed the issue with the SD Card partition being unreadable/unformatable. Maybe that was caused by multiple flashes
But, the flush-179:0 process is still eating CPU and battery.
Click to expand...
Click to collapse
?? i never heard of that flush-197:0?? could it be an app u downloaded maybe.. if u flash meanbean over abd dont install any app does is that flush-179 still there or it it there after u install yoir apps?
evo401 said:
?? i never heard of that flush-197:0?? could it be an app u downloaded maybe.. if u flash meanbean over abd dont install any app does is that flush-179 still there or it it there after u install yoir apps?
Click to expand...
Click to collapse
As far as I can tell, it's part of Fresh 5.3.1 and other ROMs I had on my SDCard that are based on the old OTA. The latest Mean Bean doesn't have the same issue after wipe & flash.
I emailed flipz (the Fresh dev), though who knows if/when he'll get back to me. For now, I'm thinking about running MeanBean for a while.
You really can't go wrong with mikeyxda and his mean series of ROM's. That man consistently puts out quality work. No doubt about it.
zisix said:
I flashed Fresh again, and suddenly started getting the warning about the SD card being damaged and to format it (as we know, that's not the external SD card). No matter how many times I format it, the error comes back. From some other searching, the 'flush-179:0' process seems to have something to do with storage, maybe because it can't read that partition it's causing issues.
Click to expand...
Click to collapse
You nailed it. I was having issues with the flush-179 system process taking up 100% of my CM10's (JB) CPU time. It got so bad that I couldn't even reboot or shutdown without pulling the battery, which of course caused other problems. Initially I thought the "System" process was just out in the weeds, but by using OS Monitor and unchecking "Hide System Process", I was able to find the flush-179 culprit.
My first clue that it might be SD card-related was obtained after opening a terminal window and typing 'mount'. The line for /mnt/sdcard showed (paraphrased):
# mount
...
/dev/block/vold/179:65 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,...
...
Realizing that a "flush" process probably had something to do with filesystem caching and seeing the "179" in the mount output, I focused on my SD card. After pulling the card, backing it up, formatting, and restoring it in Windows, I am happy to report that my little Android has been fast, snappy, and problem-free for several days now.
- Dave
Flashed My wife and I's OG's with CM 10.2. She was coming from stock 4.0.1 I was coming from 4.1.2
My has no problems. Hers wouldnt connect to wifi even though it could pick up the signals.
Last night her Kernel crashed. I figured maybe I didnt fully wipe her files clean so I rebooted her into recovery and did a factory wipe,
cleaning Dalvik, etc. and reinstalled.
Still no wifi connectivity.
Is this a driver, antennae, modem issue? Please help, I've run out of ideas.
Did you flash the correct radio?
Sent from my Optimus G using Tapatalk 4
Hmmmmm
Dr0!dFreek said:
Did you flash the correct radio?
Sent from my Optimus G using Tapatalk 4
Click to expand...
Click to collapse
I just used the one that came with CM.
Do you think since she was coming from 4.01 and I from 4.1.2 that I had the correct radio already that's why I have no issues?
And she still is running the 4.01 radio which is incompatible with android 4.3 which is what CM is running?
brionbey said:
I just used the one that came with CM.
Do you think since she was coming from 4.01 and I from 4.2 that I had the correct radio already that's why I have no issues?
And she still is running the 4.01 radio which is incompatible with android 4.3 which is what CM is running?
Click to expand...
Click to collapse
Roms for the OG don't contain modems, your wife's phone would still have ICS modem. If you had the ota to 4.1 on your phone it will have jb modem.
brionbey said:
I just used the one that came with CM.
Do you think since she was coming from 4.01 and I from 4.2 that I had the correct radio already that's why I have no issues?
And she still is running the 4.01 radio which is incompatible with android 4.3 which is what CM is running?
Click to expand...
Click to collapse
Yes, given that you avoided bricking your phone not having the rpm/tz partitions from the ota update, she would also have the ics modem, which hopefully is the only thing wrong, and is an easy fix.
matter of fact I'm not aware of anyone trying the ics modem on 4.3, or using 4.3 without the updated partitions
Still, (as a purely personal preference) I would restore the backup from before you flashed her to CM 10.2, then call up AT&T and make them push the OTA update, then backup again and reflash CWM.
-edit- this is of course, if you are on AT&T
also, you can probably make a nandroid of CM 10.2, restore to stock, get the OTA, and restore CM 10.2 and you wouldn't lose anything, since it only restores kernel,system,data,cache, etc it would be unaffected by the OTA.
technically this remains true for the LGNPST/teenybin route, but i haven't used lgnpst, i prefer forcing at&t to provide the OTA update since if it bricks then, they owe you a phone
[r.]GimP said:
Yes, given that you avoided bricking your phone not having the rpm/tz partitions from the ota update, she would also have the ics modem, which hopefully is the only thing wrong, and is an easy fix.
matter of fact I'm not aware of anyone trying the ics modem on 4.3, or using 4.3 without the updated partitions
Still, (as a purely personal preference) I would restore the backup from before you flashed her to CM 10.2, then call up AT&T and make them push the OTA update, then backup again and reflash CWM.
-edit- this is of course, if you are on AT&T
also, you can probably make a nandroid of CM 10.2, restore to stock, get the OTA, and restore CM 10.2 and you wouldn't lose anything, since it only restores kernel,system,data,cache, etc it would be unaffected by the OTA.
technically this remains true for the LGNPST/teenybin route, but i haven't used lgnpst, i prefer forcing at&t to provide the OTA update since if it bricks then, they owe you a phone
Click to expand...
Click to collapse
Just like to pass on a little info I learned recently, both Shellnutt2's cm10.2 and dvhexer's "alternate" cm10.2 use an e975 kernel.and can be flashed to phones without updating partitions.
adfurgerson said:
Just like to pass on a little info I learned recently, both Shellnutt2's cm10.2 and dvhexer's "alternate" cm10.2 use an e975 kernel.and can be flashed to phones without updating partitions.
Click to expand...
Click to collapse
Yeah I considered that, still terrifying to me though, but it would explain still having the ics modem.
How does this sound?
[r.]GimP said:
Yeah I considered that, still terrifying to me though, but it would explain still having the ics modem.
Click to expand...
Click to collapse
Ok, Just got back from work.
Today, Device crashed twice. Once a kernel error, once something about watchdog.
The kernel crash occurred when using the CM 10.4 camera. The same thing happened to my wifes device.
What I'd like to do it flash the Stock Rom Back with Stock modems to both phones.
Unfortunately, my backup didnt take because of lack of space or something, so I need to find the stock 4.1.2 rom.
I need action steps if possible.
I'm assuming I need:
4.1.2 Stock Rom for my device.w/ google apps
4.0.1 Stock for my wifes's./w google apps
I'm also assuming that I'd follow the same steps:
factory reset, flash the rom + apps reboot.
I'm using TWRP
If all that goes well I'd attempt to have at&t push the update to my wife's phone ( would I need to reset her bootloader?)
Then Reflash CM 10.2 with appropriate modems, and google apps.
Please catch any errors in this logic. Also Links to stock Rom's would be appreciated.
If anyone has any suggestions to a better custom rom then CM 10.2 I'm open to suggestions. I have not found it to be as stable as I would of liked...
FYI to make things worse, now my pc won't recognize that my device is attached.... trying not to panic.
brionbey said:
Ok, Just got back from work.
Today, Device crashed twice. Once a kernel error, once something about watchdog.
The kernel crash occurred when using the CM 10.4 camera. The same thing happened to my wifes device.
What I'd like to do it flash the Stock Rom Back with Stock modems to both phones.
Unfortunately, my backup didnt take because of lack of space or something, so I need to find the stock 4.1.2 rom.
I need action steps if possible.
I'm assuming I need:
4.1.2 Stock Rom for my device.w/ google apps
4.0.1 Stock for my wifes's./w google apps
I'm also assuming that I'd follow the same steps:
factory reset, flash the rom + apps reboot.
I'm using TWRP
If all that goes well I'd attempt to have at&t push the update to my wife's phone ( would I need to reset her bootloader?)
Then Reflash CM 10.2 with appropriate modems, and google apps.
Please catch any errors in this logic. Also Links to stock Rom's would be appreciated.
If anyone has any suggestions to a better custom rom then CM 10.2 I'm open to suggestions. I have not found it to be as stable as I would of liked...
FYI to make things worse, now my pc won't recognize that my device is attached.... trying not to panic.
Click to expand...
Click to collapse
Don't panic, you can always load onto the SD card externally, with a microsd to SD adapter or through TWRP/CWM with "mount usb storage" mode. Failing both of those things I'm fairly certain one of your two phones will be enough to load the SD card for the other phone if needed.
I'm thinking everything you need is going to be the LGNPST route now anyway, and that being said you may as well just flash them both to stock 4.1.2 in that case. First things first, you definitely want to backup before anything gets out of hand, if twrp isn't getting it then pull with adb. Quick breakdown of that below.
The universal drivers straight off the LG site work just fine, but in my experience to get the adb part happy you need to click on your devices, and find your phone, whether it says LG/Nexus4/MTP, doesn't matter. Open it and click on the hardware tab, it should list 3 devices.
unknown (or adb if you're lucky)
Your phone
USB Composite Device
If the top isnt some variation with ADB in the name, double click it, then change settings, it may say drivers not loaded, so on the driver tab we're going to give it one.
Update driver, and it will ask how, the option on the bottom is "browse my comp for driver software" and after that the bottom option again is "let me pick from a list..." I think then it shows a split list, the device type should be ADB something, and if you installed the LG universal drivers then near the bottom you will have "LGE Mobile Sooner Single ADB Interface" windows will complain because it couldn't figure out that its the right driver, confirm you want to use it and it will then show "this device is working properly" go ahead and close all those windows and it will update on the first one with the three devices listed the next time you open it.
At this point you need the adb application itself, I usually just download the whole android SDK personally, but where you get it from doesn't matter. If you're booted in android, make sure adb has root access in developer settings, and debugging is enabled.
open a command promt, for the sake of easy navigate to the folder where you put adb, in windows, or in the SDK example, /android/sdk/platform-tools/ hold shift and right-click on an empty space and select "open command window here"
If android is running, type "adb root" without quotes
and adb will inform you its restarting, if in twrp you will already be root.
Type "adb devices" and as long as its not blank you should be good
again, for the sake of easy "adb backup -shared -all"
and let it do its thing, it should start creating a default file named "backup.ab" it's bound to take awhile as -shared should grab all the sd card contents just to be safe.
Disaster recovery aside, I would use a combination of Titanium backup root, and "backup your mobile" - especially add the second option in addition to titanium, thats one of the only free backup apps that can get MMS as well as SMS, and restore them.
Again, if you're having issue with the computer normally seeing the device, these are still good tools, save to external sd card, remove card and transfer manually to your computer.
ok.. now that all your stuff is *hopefully* now redundantly backed up, depending on the stock image you find, you can either push it via fastboot commands or flash with lgnpst. I know the images are in our forum, most likely in the lgnpst thread. just follow through that and read well ahead before performing each step, you'll be ok.
I believe fastboot can relock your bootloader in all off one command, i don't have the answer if its necessary or not to receive the OTA, but having skimmed the lgnpst thread in the past, I'm positive people have done the flash and then had the OTA pushed from AT&T so they could get up to 4.1.2 for the official JB and partitions. Like I said in the beginning, your call if you want to skip that and just lgnpst to 4.1.2 since you're there anyway. Also, keep an eye out for one of the recent restore to stock / RPM/TZ partition threads, I think shellnutt making a cwm/twrp flashable zip to do the same thing lgnpst teeny bin would without even needing lgnpst.
So, barring a complete hardware failure, dont be scared. Get your data for now, then on to the next step.
Best xda technical support post I have seen in a long time. Thanks, gimp.
Sent from my Optimus G using XDA Premium 4 mobile app
DeathmonkeyGTX said:
Best xda technical support post I have seen in a long time. Thanks, gimp.
Sent from my Optimus G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Agreed.
Sent from my Optimus G using Tapatalk 4
I agree also! feels great to have some help with this. attempting fixes I'll report back.
Sent from my LG-E970 using XDA Premium 4 mobile app
I got stuck on the adb driver part. Through searching I found the backup I made for her. Can I restore her backup. Flash the jellybean rom to it, creating the neccessary. Partitions in the process, along with the correct radio, and then reflash Cm? My main concern is getting her wifi up. She's racked up 6gigs in 2 days herself! Were on the 4.gig shared plan. Or possibly just flash the radio...
Sent from my LG-E970 using XDA Premium 4 mobile app
brionbey said:
I got stuck on the adb driver part. Through searching I found the backup I made for her. Can I restore her backup. Flash the jellybean rom to it, creating the neccessary. Partitions in the process, along with the correct radio, and then reflash Cm? My main concern is getting her wifi up. She's racked up 6gigs in 2 days herself! Were on the 4.gig shared plan. Or possibly just flash the radio...
Sent from my LG-E970 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
yes that sounds fine, in that case I would just make the apps and messages backups with titanium/backup your mobile
I'm not 100% if the lgnpst flash to JB wipes user data or not, but after that you can flash pretty much ANY rom for our device, then just download titanium/backup your mobile from the app store and point it to the directories on the sd card, and restore selectively.
For the most part you can move everything from /sdcard to /external_sd and move it back over when you're done, I think the JB radio (or modem, both terms apply) works very well for everything I've used (and yes they play a significant part in wifi and gps also), and I was a pretty hardcore flash-a-holic for a really good while, still haven't tried the hybrid modems and people rave about how well they work. Sounds like a good plan you got going, once you're up with the partitions and the JB modem from 4.1.2 you really should have no issues, and once you have that freedom, and she will as well to try out all manner of ROM's, you'll find you get really good at backup/restore out of necessity. Happy flashing.
If you need any specifics, aside from the step by steps of the other threads I'm glad to lend advice, just let me know
-edit- you can make multiple backups with each program by the way, titanium and backup your mobile.
Titanium free says only one backup per app, but in reality just hit the batch button on the top right, looks like a check mark, have it get all apps and system settings, then just move the whole folder you set for titanium off of the device for safe keeping. This way you can backup everything running right now, then if you want to restore the other one, you could even do it again, if you just wanted to cherry pick some stuff, then flash, etc. Titanium free wont let you make multiple copies of the same app, but it also WONT delete extras if you already have them, so if you dump a few titanium folders into eachother and merge them, you can then choose any of the backup files or data or both from each date.
The reason I use both programs is as I said earlier, backup your mobile handles SMS/MMS very efficiently, and occasionally I'll let it grab a few user apps, and system apps, because when it restores them, it restores for example, flash player from LG stock rom, as a user app, and it continues to work flawlessly. Titanium can't get over it being a system app, and sucks at restoring flash.
However, titanium is GREAT for also saving user data, not just the program itself. ie.. savegame states for any app you have that doesnt explicitly sync online, or the login data for facebook, or adfree with the most current hosts so you dont have to redownload or even type your logins, very convenient.
My personal order of operations before I flash a new rom, or even upgrade to a new version with a clean flash instead of a "dirty" is to fully backup all apps/system data with titanium, then hit ByM for contacts/sms/mms/bookmarks/user dictionary/apps
then a nandroid backup, since it is basically a perfect snapshot itself, just like turning the phone off, and back on.
after rom flash / gapps, I boot, setup google real quick, goto app store and cancel the 5 million downloads, except for titanium/ByM
after those download I roll my messages/user dictionary/contacts/ selective apps I know i'll use, and the same with a few from titanium.
This way I'm less bloated with crap I probably don't use everyday, and if i need it, its a few taps away. It's a very painless process and a lot of peace of mind having everything safe, and allows you to try alot of unstable crap knowing how easy you can always roll your CWM/TWRP backup over to the device like you never left.
Sorry, I'm a fan of ranting. Pics for adb driver steps explained in previous post, and the backup part, for reference if you ever need them.
View attachment 2263477
View attachment 2263478
Ok, I'm keepin cool but it seems to be one thing after another
I made the backup before the original flash.
I see it in the folder. When I restored it, it is the same rom that I'm on CM 10.2
I'm not sure how that happened.
Thanks for the images, that really helped unstuck me.
Question: I've checked the threads looking for the stock [ROM] 4.1.2 and Gapps for E970 and can't find them anywhere.
At this point I just need a doOver. I have to get my wife her phone back, ASAP and if I brick by some chance, I'll never hear the end of it.
EVER.
Or how about just flashing the radio? Can I do that to at least get her Wifi?
Here is the flashable jellybean radio by g33k3r.
http://forum.xda-developers.com/showthread.php?t=2220048
I recommend still updating her to the jellybean partition layout when you get a chance, but this should get you working WiFi at the very least.
Sent from my LG-E970 using xda app-developers app
Flash the Radio
Thanks SnowLeopard.
So all I need to do is just boot into recovery using TWRP and Install the radio, or should I factor reset and install the radio at the same time as the rom?
Thanks Again Guys. (or gals)
Lgnpst doesn't touch the /data partition.
Sent from my Optimus G using XDA Premium 4 mobile app
the modem work great.
Sent from my LG-E970 using XDA Premium 4 mobile app
At gimp, followed instructions exactly, computer recognize device, only thing left to do is run teeny bit, but getting error path not found
Sent from my LG-E970 using XDA Premium 4 mobile app
I'm not the developer but kitkat nightly is out.
ROM download: http://download.cyanogenmod.org/?type=nightly
gapps download: http://wiki.cyanogenmod.org/w/Gapps
Change log: http://changelog.bbqdroid.org/#/t0lte/next
You might experience problem with twrp so it might be better to use CWM.
Also I believe it'll be a full wipe installing the ROM the first time. Good luck.
ps. if the cm dev wants to create a new thread for this ROM, please do so and I'll ask a moderator to close/delete this one.
here are the results of my trials earlier today. ROM is working nicely now. at least on the apps I've tried it on. Still using dalvik though.
-------------------------
some tips (all my testing was done using official CWM 6.0.4.1):
1. Definitely do not use TWRP unless there's an update to 2.6.3.7. (seems TWRP could work if one use the modified version. see message below. I haven't tested this myself.)
2. using CWM and exFAT is a hit and miss. A fresh install and the ROM can't see sdcard. The only time the sdcard was detected was after a nandroid restore.. Since all the files in my SDcard is < 4GB, I can use FAT32.
3. nandroid restore = no mobile connection for me. this was fixed by reflashing the even if it's the same nightly (example: say I made a nandroid backup of 17-Dec nightly ROM. due to having messed up stuff, I decided to restore my backup. as said above, this will result in no mobile connection. but if I reflashed the zip file for 17-Dec nightly, this will fix the problem)
4. the hangouts included in the gapps (See link above to CM wiki) resulted in FCs when trying to make a video call. this was fixed by uninstalling hangouts using titanium and reinstalling it via the playstore.
5. I believe all official recoveries need updating to support 4.4 properly.
---------------------------------------------------------------------------
original message is below. you can see the problems I've encountered during testing.
just flashed the nightly for t0lte using TWRP 2.6.3.7 and somehow it can't see my SIM. Will be flashing again using latest CWM (6.0.4.1 as of now).
initial observations:
1. NTFS work on SD cards
2. 2 launchers are present (launcher and launcher3)
3. looks better than Jb (it could be placebo effect because kitkat is new)
update: definitely use CWM at least for t0lte. ROM has recognized my SIM.
update2: been playing around with the ROM and when I tried to access my NTFS-formatted SDcard, it cannot see. I had no problems at all with my SDcard using TWRP. I can even browse the folders inside it using file manager. I also had a problem with the built-in hangouts and video chat. I'm getting FCs.
update3: restoring from CWM nandroid backup = no cellular/mobile connect. Can't even call anyone.
update4: update to update3. I did lose cellular/mobile connectivity (phone can't find sim) BUT it can recognize my NTFS-formatted sdcard now!
update5: removing hangouts via titanium and then reinstalling the playstore version, I can make a video call.
update6: restore from nandroid (which gives me a working NTFS-formatted sdcard) and then reflashed the ROM. I got mobile signal but no sdcard. I guess I can always format it at as FAT32 which I'm doing now.
mrjayviper said:
update3: restoring from CWM nandroid backup = no cellular/mobile connect. Can't even call anyone.
update4: update to update3. I did lose cellular/mobile connectivity (phone can't find sim) BUT it can recognize my NTFS-formatted sdcard now!
Click to expand...
Click to collapse
Keep us posted. Would love to know how to sort out the data connection/sim issues before I flash.
Cheers.
Sheikx800 said:
Keep us posted. Would love to know how to sort out the data connection/sim issues before I flash.
Cheers.
Click to expand...
Click to collapse
gave up on making an NTFS-formatted sdcard work on a new flash. I'm formatting my sdcard now to FAT32. It'll probably be fixed down the road.
and I think flashing the ROM after restoring from nandroid backup will bring back mobile signal. At least that's my conclusion. But I do get a signal only if I use CWM.
Yea twrp 2.3.6.7 is buggy. Look for twrp 2.3.6.1, it's modified and will work with cellular signal. Keep us posted.
The modded twrp is linked on one of the last pages in the beanstalk thread iirc
Sent from my GT-N7105 using XDA Premium 4 mobile app
updated 2nd post to give some tips on how to install ROM properly. seems to be working nicely now. That said, I don't have much app/games installed on my phone compared to my tablet (50-60 apps on the phone compared to 90+ on the tablet. mostly games).
a sample list of apps installed on phone are dashclock, lightflow, dynamicnotifications, various messaging. various Google apps and 1 game.
Installed with latest CWM and Data works great, no issues with Calls / LTE etc.
ROM seems really good so far, using Google's OK Google is fun but does tend to drain the battery faster, that said I will switch to a different kernel as I miss Viper so will most likely go with Devil, hopefully it helps with the battery.
I've never had an issue with CWM, I upgraded to the latest version using ROM Manager.
My tip for flashing is to always wipe perform a full wipe plus Cache, Davlik and System before flashing and Cache, Davlik after.
Miss some features / tweaks from other Roms but I know that CM is the best stock experience out there so no problems there.
IMO no issues running as a daily driver.
Proximity sensor not working. Is it just me or...?
Tapatalk-kal küldve az én GT-N7105-el
I had problems to are you running any other kernels or are you on the stock one?
Sent from my GT-N7105 using XDA Premium 4 mobile app
CWM 6.0.3.1 Touch (I think!) doesn't work, got bad flash error 7 (I think!) every time.
ROM manager update to 6.0.4.1 to non-touch* worked like a charm.
(*because I'm both tight and lazy)
---------- Post added at 10:14 PM ---------- Previous post was at 10:04 PM ----------
richyy74 said:
Proximity sensor not working. Is it just me or...?
Click to expand...
Click to collapse
Definitely not working on a clean install, with a few apps installed.
According to a test app the light sensor is responding but the prox is not.
Camera app is buggy, useless in fact. 3rd party camera is fine temporary replacement.
Facebook edit post doesn't allow cursor placement, facebook app 4.4 problem I assume.
Is anyone able to successfully set the DPI to another value in build.prop? Mine always defaults to 320 after each reboot.
Update:
I seem to be able to edit/save build.prop changes fine in 12/07/13 nightly.
Had the same flash error 7 corruption had boot loop into recovery and had to use a nand backup to get back. Did a clean install, and the process went well. Only issues so far are my Microsd can't be seen. And can't manage to get the 'Ok google' stuff working. A few random crashes but overall working well so far.
So would love some help with the Microsd issue as this is quite important?
Sent from my GT-N7105 using Tapatalk
leebag said:
Had the same flash error 7 corruption had boot loop into recovery and had to use a nand backup to get back. Did a clean install, and the process went well. Only issues so far are my Microsd can't be seen. And can't manage to get the 'Ok google' stuff working. A few random crashes but overall working well so far.
So would love some help with the Microsd issue as this is quite important?
Sent from my GT-N7105 using Tapatalk
Click to expand...
Click to collapse
my NTFS-formatted sdcard can be seen when I use TWRP 2.6.3.7. not so with CWM 6.0.4.1.
I'm running the modified TWRP mentioned in page1 but my sdcard is still FAT32. I'll format my sdcard and see if it works.
I'm going back to CWM. just noticed all sorts of problems on my phone running the modified TWRP. :/ sucks!
No radio signal when flashing with TWRP 2.6.3.7. Flash again with CWM 6.0.4.1 radio is back. No problem with the external SD card (FAT32).
AkiraBBQ said:
No radio signal when flashing with TWRP 2.6.3.7. Flash again with CWM 6.0.4.1 radio is back. No problem with the external SD card (FAT32).
Click to expand...
Click to collapse
@mrjayviper Wasn't twrp 2.6.3.7 a bugged and accidental upload?
(At least people kept telling me a short while ago. )
Try the modded twrp 2.6.3.1 been linked a few days ago in the beanstalk tread
Sent from my GT-N7105 using XDA Premium 4 mobile app
Updated to the latest nightly and running Agni kernel and all running well.
Battery life is great, loving this ROM so far!
is anyone been able to successfully make a video call on hangouts? it's been FCing on me. using cwm and twrp.
I just tried the PA full gapps and no luck with that. thanks