I should mention that this phone is not mine and it was brought to me to fix. It could not get past the samsung bootup animation screen.
So I installed TWRP 2.8.6.0 and wiped everything. Then the first rom I flashed was [ROM][5.1.1][AOSPA] ParanoidAndroid 5.1 (5/21/2015) Then flashed gapps 5-22-15 from euroskank/banks. I wiped dalvik & cache (Is this necessary?) and rebooted.
The intro screen did not let me skip the wifi connecting part (I thought it was a bug in that version) and it told me to turn on wi-fi to connect.
So I tried the same thing with the version before that and it let me skip. After that I managed to turn it on once? But it the phone crashed and soft rebooted.
I tried other 5.1 roms and the wifi doesn't work still. It doesn't let me turn it on. Same with 4.4.4 with cm11. Also, the Wi-Fi MAC address says unavailable. Don't think that's supposed to happen?
Does anyone have a fix?
Edit: I took out the SIM card to see if that did anything. Then all of a sudden the grayed out On button turned blue and wifi networks appeared... But I couldn't do anything else since it made me restart. It stopped working after a reboot :/ Tried it several more times and couldn't get it to do the same thing..
stevenx37 said:
I should mention that this phone is not mine and it was brought to me to fix. It could not get past the samsung bootup animation screen.
So I installed TWRP 2.8.6.0 and wiped everything. Then the first rom I flashed was [ROM][5.1.1][AOSPA] ParanoidAndroid 5.1 (5/21/2015) Then flashed gapps 5-22-15 from euroskank/banks. I wiped dalvik & cache (Is this necessary?) and rebooted.
The intro screen did not let me skip the wifi connecting part (I thought it was a bug in that version) and it told me to turn on wi-fi to connect.
So I tried the same thing with the version before that and it let me skip. After that I managed to turn it on once? But it the phone crashed and soft rebooted.
I tried other 5.1 roms and the wifi doesn't work still. It doesn't let me turn it on. Same with 4.4.4 with cm11. Also, the Wi-Fi MAC address says unavailable. Don't think that's supposed to happen?
Does anyone have a fix?
Edit: I took out the SIM card to see if that did anything. Then all of a sudden the grayed out On button turned blue and wifi networks appeared... But I couldn't do anything else since it made me restart. It stopped working after a reboot :/ Tried it several more times and couldn't get it to do the same thing..
Click to expand...
Click to collapse
Hope you had read the posts, it should had said the Rom is not "stable"
If your friend are going use their phone for daily driver, then I recommend you not have the 5.1 Roms for now because it's not really suitable for that right now.....
I'm not sure the CM11 you have flashed is unoffical or is offical. Offical onces are still work in progress and have most of the things broke (I think)
Here is a Kitkat Rom for SGH-T989
If your friend really wanted to have a Lollipop running on his/her phone, then I will recommend this one. Make sure you read the instruction CAREFULLY if you do wanted to install this one since it's a bit complicated with it's "virtual partition"
Or, if you wanted it to be just stock. Odin it back to normal, here is a instruction (with video too).
This is all the possible way to fix your friend's phone that I can think of, if you have encounter any error or have anymore question, feel free to reply :fingers-crossed::good::highfive:
P.S: yes, wiping dalvik & cache is a way to prevent any error caused by another old Rom if you decided to flash a new one. It's a good way to prevent error during Rom flash process
Thanks! I'll try the 4.4.4 rom you sent me. I'll post an update when I get to it.
Uh and about the 5.1 you linked. For the virtual repartition part in his post, I couldn't open the phone's internal storage on the computer after formatting it to ext4. So I'm confused about that step.
stevenx37 said:
Thanks! I'll try the 4.4.4 rom you sent me. I'll post an update when I get to it.
Uh and about the 5.1 you linked. For the virtual repartition part in his post, I couldn't open the phone's internal storage on the computer after formatting it to ext4. So I'm confused about that step.
Click to expand...
Click to collapse
For the virtual partition, it's best for you to have it on the External SD card. Since TWRP transporting file to Internal Storage after that seems bugged (not working)
I've been trying to update my firmware all day, I'm running TWRP2.8.7.2, updated to the newest bootloader, and tried 6 different ROMs, nothing will boot, except the alpha AOSP Marshmallow, but with that play services keeps crashing as soon as I try to set up my google account, and I can't get past the first run wizard. I've wiped my cache and data and internal storage a couple times now, and nothing is working. could someone give me an idea? I've never had so much trouble flashing a device before.
try going back to 100% stock by flashing stock firmware on ODIN. Next root and twrp.
sarreq said:
I've been trying to update my firmware all day, I'm running TWRP2.8.7.2, updated to the newest bootloader, and tried 6 different ROMs, nothing will boot, except the alpha AOSP Marshmallow, but with that play services keeps crashing as soon as I try to set up my google account, and I can't get past the first run wizard. I've wiped my cache and data and internal storage a couple times now, and nothing is working. could someone give me an idea? I've never had so much trouble flashing a device before.
Click to expand...
Click to collapse
I have a t700 and had the same problems you have installing marshmallow. What worked for me was advanced wipe in twrp, everything except internal storage and sd card. From there hit the home key, and flash the marshmallow rom, then reboot into recovery, next flash su 2.5x, then reboot into recovery. Lastly, flash the benzo gapps, and reboot system. My play store started working after i installed in that sequence on t700. Ive heard a few others have had to do that process 2 or 3x before it works, and some, it doesnt work at all. Worth a try though. Good luck.
New to the world of Custom ROMs. A week ago I installed CM 13 which took great courage on my part and wanted to share my experience, issues and discuss possible solutions.
My phone had the latest lollipop on it. And McCafee locked. The steps that worked for me where
1) Did a factory reset and bumped into mccafee.
2) Tried download mode but kill switch was enabled.
3) Rebooted the phone to face mccafee, tried 123465 pin which worked.
4) Disengaged McCafee but not before transferring ownership to my email.
5) Tried rooting didnt work with any method.
6) Rolled back to d software version stock lollipop.
7) Rooted with PurpleDrake
8) Replaced with CM recovery didnt work.
9) Replaced with TWRP and rebooted directly to recovery
10) Installed CM and gapps mini. Worked fine. Voila!
Issues:
1) No Custom recovery sticks, whenever I flash with a custom recovery like TWRP or Clockwork. I have to reboot into recovery immediately or the custom recovery is replaced by stock. It happens on every second reboot.
My concern is here if I get stuck into bootloop and dont have a custom recovery I might not have any other option than the stock ROM which does a full reset. How can make TWRP stick forever?
2) After installation of Custom ROM there have been random reboots, I suspect there is something here with phone app or voice. So far the reboots have been when I try to call using fb messenger, appear.in and phone app itself.
Is there a guide that tells me how to track this down?
Can I install a newer Nightly and hope this get fixed?
How can I retain my apps and data when installing a newer nightly? since all guides ask to wipe everything :S
I have a backup of system and data partitions, can I use that with other ROMs.
What ROMs have a better chance of fixing this issue?
Coudnt find Stock M for D850. Why arent those available?
Should an Official ROM be more reliable than CM for this?
3) Bad signal reception so far. It may be a generic g3 issue.
Can I hope that this issue be fixed with a different ROM or updates from Cynogen?
Someone said you may have to flash the radio partition. My question is where can I get a brief understanding of what partitions there are in android and which are risky. Which ones can be replaced, backedup and replaced back.
4) Whenever the phone reboots, it gets stuck into bootloop unless I remove the SIM card. Then I power off and install SIM Card and reboot and it boots fine.
I am already tracking CM changelog for something important. Cant post urls as of now :S
Hi, I have the latest CM12 installed in my tablet, but I have a lot of issues, especially when installing multiple apps or if I try to change the Launcher. It gets into boot loop and there is nothing one can do but re-flash the rom, which is pretty annoying. It has happened to me already 3 times in a short while and I am thinking of flashing LineageOS. However, I hear it is still very buggy, especially the issues with wifi. So I would like to ask which is the least buggy Rom for 7.0 v410 or if there is a way to avoid CM12 from getting the problem with boot loop.
Boot loop has been caused when trying to change Launcher (because trebuchet regularly crashes), when installing x-plore file manager and in a clean flash when I attempted to install multiple apps at the same time. In all cases it got stack in boot loop, or would start only to restart after a while, endlessly.
Finally, I opted for LineageOS 14.1.
I had the 11-11 Nightly for some time and seemed fine. Today I updated to 25-11 Nightly. It feels maybe slightly laggy, but still checking it.
I have also installed "Best WiFi Keeper" app from play store and it generally keeps me connected. However, if connection is lost (e.g at restart or if I get out of range), I have to reconnect manually. I tried few apps for reconnecting but nothing worked. It appears that although the WiFi network is seen, the tablet cannot really re-establish the connection automatically.
I found Nothing stable yet.. In last few days, I have installed CM 12.1, same trouble.. I installed Tipsy and Tesle, unable to install apps from playstore. Tried CM 13 and Lineage OS latest build as you, Wifi Teathering and USB teathering not working and same problem with wifi connectivity. Keed posted if you find something better.. I shall too...
Tesla works great for me. I'm running a lollipop version that's still on androidfilehost; I'm not sure if GZR ever got updated beyond 5.1 for V410.
I've had CM 14.1 (long enough ago it was still CM and not LOS) on the tablet, and it felt like it would get laggy. That could just be from junk my kid installs though, but I don't seem to have that problem with Tesla.
I installed Tesla (Tesla-v410-5.1.1.High_Voltage.2.2.1-Release-20150902.zip from https://androidfilehost.com/?fid=24052804347807214) with open G apps but getting errors while installing apps from Play store(Some error code 963 - tried cleaning cache of playstore, play services download manager, removing google account and adding again - Nothing works). Same situation with tipsy. Any help?
kingzones said:
I installed Tesla (Tesla-v410-5.1.1.High_Voltage.2.2.1-Release-20150902.zip from https://androidfilehost.com/?fid=24052804347807214) with open G apps but getting errors while installing apps from Play store(Some error code 963 - tried cleaning cache of playstore, play services download manager, removing google account and adding again - Nothing works). Same situation with tipsy. Any help?
Click to expand...
Click to collapse
That is probably what I'm running, I don't have my tablet right now. I think I flashed it with opengapps nano. I didn't have to do anything unusual to get play store to work.
Tipsy uses the same base as Tesla and Validus. Since it is persisting across multiple flashes and roms, consider formatting the internal storage if it isn't too much hassle, the TWRP wipe where you have to type "yes" to confirm. Sometimes some remnants in userdata that aren't touched by the normal system/data/cache/dalvik wipe cause problems like this and can persist the way you're describing.
Just make sure you have rom and gapps on an external SD or you have confirmed you can push files to the tablet in TWRP over usb via mtp or adb before you blank the internal storage.
jason2678 said:
That is probably what I'm running, I don't have my tablet right now. I think I flashed it with opengapps nano. I didn't have to do anything unusual to get play store to work.
Tipsy uses the same base as Tesla and Validus. Since it is persisting across multiple flashes and roms, consider formatting the internal storage if it isn't too much hassle, the TWRP wipe where you have to type "yes" to confirm. Sometimes some remnants in userdata that aren't touched by the normal system/data/cache/dalvik wipe cause problems like this and can persist the way you're describing.
Just make sure you have rom and gapps on an external SD or you have confirmed you can push files to the tablet in TWRP over usb via mtp or adb before you blank the internal storage.
Click to expand...
Click to collapse
can you tell me if hotspot and usb tethering is working on tipsy? Thanks.
xdause said:
can you tell me if hotspot and usb tethering is working on tipsy? Thanks.
Click to expand...
Click to collapse
I'm on Tesla, but it has the same base as Tipsy. I don't have data on the tablet so it isn't a 100% conclusive test, but it doesn't seem to work. The switch for USB tethering never turns on. Wifi turns on but never connects properly. My laptop does briefly show connection then disconnects with both USB and wifi tethering. It could be because there is no data connection on my tablet, but looking through dmesg on the laptop gives me the impression that something on the tablet isn't working right.
kingzones said:
I found Nothing stable yet.. In last few days, I have installed CM 12.1, same trouble.. I installed Tipsy and Tesle, unable to install apps from playstore. Tried CM 13 and Lineage OS latest build as you, Wifi Teathering and USB teathering not working and same problem with wifi connectivity. Keed posted if you find something better.. I shall too...
Click to expand...
Click to collapse
I'm on lineageOs 14.1 which is alright though the wifi issue is still there. However, someone may have found a solution, but I don't know how to implement it. Check posts 207, 210 and 215 in this thread: https://forum.xda-developers.com/g-...eageos-14-1-v400-lg-g-pad-7-0-t3583952/page22
nicospanas said:
I'm on lineageOs 14.1 which is alright though the wifi issue is still there. However, someone may have found a solution, but I don't know how to implement it. Check posts 207, 210 and 215 in this thread: https://forum.xda-developers.com/g-...eageos-14-1-v400-lg-g-pad-7-0-t3583952/page22
Click to expand...
Click to collapse
Would you (or anyone who sees this) please tell me is it possible to flash TWRP if I'm on 5.0.2? Or must I downgrade first?
I'm rooted already. TBH stock is pretty solid and if the custom roms have too many bugs I might pass. But I would like to flash Viper4Android and don't think I've ever installed it without a custom recovery. Many thanks in advance.
KLit75 said:
Would you (or anyone who sees this) please tell me is it possible to flash TWRP if I'm on 5.0.2? Or must I downgrade first?
I'm rooted already. TBH stock is pretty solid and if the custom roms have too many bugs I might pass. But I would like to flash Viper4Android and don't think I've ever installed it without a custom recovery. Many thanks in advance.
Click to expand...
Click to collapse
I made the same question more or less, over a year ago here: https://forum.xda-developers.com/android/development/help-installing-cm-t3483074
You cannot flash another rom over lollipop and I've never seen twrp for android 5.0.2 for v410. I am not 100% sure because my question was a bit different, but I assume from the replies, that probably not.
nicospanas said:
I made the same question more or less, over a year ago here: https://forum.xda-developers.com/android/development/help-installing-cm-t3483074
You cannot flash another rom over lollipop and I've never seen twrp for android 5.0.2 for v410. I am not 100% sure because my question was a bit different, but I assume from the replies, that probably not.
Click to expand...
Click to collapse
Thanks. That's more or less what I thought. From what I'm hearing there are some bugs in the roms that no doubt aren't being maintained at this late stage so I think I'll stick with stock (would be nice to have a custom recovery though.)
Not that it matters (a year later) but lots of people root with Kingroot when there isn't another option and there's several ways to remove all the bits left behind and switch it to supersu.
Thanks again!
Well, I have a work around to stop wifi from disconnecting in lineage os. After that I did not know when wifi got disconnected and reconnected.
Just download E-Robot from playstore.
https://play.google.com/store/apps/details?id=com.bartat.android.robot
And set it to settings as per screen shot.
kingzones said:
Well, I have a work around to stop wifi from disconnecting in lineage os. After that I did not know when wifi got disconnected and reconnected.
Just download E-Robot from playstore.
https://play.google.com/store/apps/details?id=com.bartat.android.robot
And set it to settings as per screen shot.
Click to expand...
Click to collapse
It works! Thank you so much! It seems the LOS developers have stopped trying to fix the wifi issue but it is important. The workaround even works at restart, with some delay, but it works!
Just to clarify to newbies like me, where ssid you have to put the name of the network you want to connect. I wonder if one can add more networks, so it can connect to any saved network according to where you are. You think that's possible?
nicospanas said:
It works! Thank you so much! It seems the LOS developers have stopped trying to fix the wifi issue but it is important. The workaround even works at restart, with some delay, but it works!
Just to clarify to newbies like me, where ssid you have to put the name of the network you want to connect. I wonder if one can add more networks, so it can connect to any saved network according to where you are. You think that's possible?
Click to expand...
Click to collapse
That would be great.. I shall try.. if successful, I shall post results.
I have a uk410, the US Cellular variant of the v410. I tried the CM12.1 "stable" release cm-12.1-20151117-SNAPSHOT-YOG7DAO1K5-v410.zip found here (archive.org/download/cmarchive_snapshots), along with Open GApps nano for 5.1 (opengapps.org/?api=5.1), and quickly got the infinite rebooting issue.
I then switched to the Telsa ROM mentioned earlier in this thread (Tesla-v410-5.1.1.High_Voltage.2.2.1-Release-20150902.zip) found at androidfilehost.com/?fid=24052804347807214, again with Open GApps nano for 5.1 (build open_gapps-arm-5.1-nano-20180922.zip), and have been running it with no issues for two days. My wifi is connected, and stays connected (tested two different routers), Play Store and apps have been working fine, and no crashes so far.
I'm using TWRP 3.1 (twrp-3.1.0-0-v410.img).
Thanks for mentioning Tesla, @jason2678 !
So like all of you I was looking for a rom to install on this v410 7" tablet, and it looks like I should just give up or stick with 4.4.2 stock if I want to go through the rooting process.
Basically all the development roms end with the same problems, wifi dropping, hostspot not working, no ir blaster, volume problems, bluetooth errors, and several hundred posts about lolipop memory leaks crippling the tablet because of only 1gb mem.
So, I am asking all of you, is there any real reason to root it, besides going back to stock 4.4.2?
And lastly, is the stock 4.4.2 kdz image that is floating around a test version, and if so is there an actual official kdz image somewhere that isn't a test image?
Thanks...
CrDroid by far in my opinion. Lineage based, 7.1.2.
Also, e/ os has been unofficially released. No Google anything...an entirely new Google list operating system by lineage. It's lightning fast and runs magisk perfectly. It's basically like nothing you've ever seen before and if you look under LG g pad 7.0 on Android file host, go to the second page and click on the last user who goes by the name anonymous and you'll find the ROM there. I had no idea what it was until my g pad boot it up and I saw the e logo. I pretty much **** myself in excitement
Hey,
some days ago i went from 7.1.2 to 8.1. I haven't had any issues whatsoever.
For some reason tho it seems like there's something wrong since my bug isn't listed as known.
The first ROM i tried was RR 6.0, and i tried it 2 times with this ROM. Same bug, just like with crDroid 4.1 which im running now. I even performed a COMPLETE wipe and made sure to flash the latest twrp recovery.
Whenever I setup a displaylock (PIN/Pattern/.. except swipe which is default) the device freezes immediatly afterwards, becomes totally unusable so im forced to pull out the battery. Rebooting then takes me to the lock that was just setup but entering the code just freezes the phone again. There's no workaround so far - everytime it happend i had to go back to factory settings.
Since i need to setup a displaylock to install a certificate I could really need your help. Im thanking in advice :good:
Regards,
furi
furiify said:
Hey,
some days ago i went from 7.1.2 to 8.1. I haven't had any issues whatsoever.
For some reason tho it seems like there's something wrong since my bug isn't listed as known.
The first ROM i tried was RR 6.0, and i tried it 2 times with this ROM. Same bug, just like with crDroid 4.1 which im running now. I even performed a COMPLETE wipe and made sure to flash the latest twrp recovery.
Whenever I setup a displaylock (PIN/Pattern/.. except swipe which is default) the device freezes immediatly afterwards, becomes totally unusable so im forced to pull out the battery. Rebooting then takes me to the lock that was just setup but entering the code just freezes the phone again. There's no workaround so far - everytime it happend i had to go back to factory settings.
Since i need to setup a displaylock to install a certificate I could really need your help. Im thanking in advice :good:
Regards,
furi
Click to expand...
Click to collapse
Same problem
i delete /data/system/locksettings.db with twrp file manager to get rid of this problem but i can not lock because all lock types freezes.