I went through from 4.1.1 to 4.1.2, no problems, phone ran fine after update. Then went to 4.3, same thing. The phone was running fine so I booted back into recovery and removed Knox as well as manually rerooted by flashing SuperSU. Rebooted after that and still no problems, phone was running great. I then make a backup so I have a restore point of stock 4.3, rooted, and without Knox. I then go on and try to flash Dandroid and get a status 7 error and the phone was acting up after I rebooted.
At this point I go back to my backup and simply restore it and reboot again. The phone boots up, so that's a good thing. The problem is the GApps will not run and it continuously has a pop-up notification. The phone is rendered unusable like this. I got lucky once and was able to try and launch ROM Manager to see if fixing permissions would work, but it also closed. I tried flashing a 4.3 GApps package with no success and even tried reflashing the 4.3 update but got a status 6 error.
I'm at a loss here, does anyone have any ideas on this?
Not sure if this will help much, but even when plugged in via USB my computer will not recognize the device. The S3 states that it is connected and it does show up in Device Manager, it just won't show up as any kind of readable memory.
Trying to ADB sideload a rooted stock 4.3 ROM now. Any advice at all would be a help.
EDIT: I took a video (https://www.youtube.com/watch?v=tJ-eaQ_9mVI) of the problem so everyone can see what I'm talking about and I also found a fix.
I'm not sure what was causing it, but after a solid day of researching it online the closest thing I got was resetting app preferences and also trying to clear any data of Google apps. This seemed to sometimes slow the popups down for me or create a longer gap before they just came right back in full force. So, going off that small success I had managed to navigate my way over to Settings -> Accounts -> Backup and reset -> Factory data reset and ran that. The first boot after that took a very long time, I'd say a solid twenty minutes but it did work. No more error and everything has been going smooth for me since. A restore of apps with Titanium Backup also did not bring the problem back up again, so the device seems to be good as new again.
I apologize if any of these is out of line, I just thought I would follow up with a solution in case anyone else has this problem and can't seem to fix it. Maybe this will help them.
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)
Hi All,
Having some issues with my Galaxy Note 10.1 which I've had for quite a while now. It's rooted but with Android 5.0 stock rom and a custom kernel.
Just now (like 20mins ago) I tried to enable Adblock plus app, the app said it can't automatically change the settings - even though SuperSU was installed and had no issues with it previously. So like all things thought I'd give it a reboot that ought to clear it out. That didn't work, so tried clearing cache (Dalvik/ART/Cache), Still no joy.
I'm a s/w engineer, but not and android/bootloader expert, so I've tried to grab the dmesg and boot logs which I've attached, I've got some stuff on the internal SD (app data) which I'd like to keep, hence I'm not going for the full wipe.
Please take a look at the logs and see if you can determine how to fix this issue, my initial thoughts were there are some issues with the flash storage (bad sectors/partition table?), if I could grab the image and dd the image again I'd be OK - but I don't know much about about android boot loader/kernel etc so can't say.
Ok it has been fixed by wiping data - but I've lost my data and installed apps!
Is there anyway to find out which file/app is causing the boot loop so I can restore data, delete the offending file?
Well, I shall give a bump to this topic, with a little more info. Though probably not really useful.
First I had stock 5.1.1 deodex pre root etc ROM that, after I tried to insert a nano sim card (mine is a 601 3G model) that got stuck, it entered on a bootloop, I had to open it, take the sim card out, and it was still on a boot loop. Tried to install another image, still bootloop, tried to reinstall the original one I had, still bootloop, wiped data, worked fine.
Then almost 2 weeks later, everything worked fine, went to watch a video, the sound was mute, tried to turn it on but everything looked fine, decided to restart because it would probably fix the problem. Got a bootloop. Wiped the data, everything was fine again.
Now, a little more than 2 weeks later, seems like the wifi is not working, thought all my other devices are, guess it's the same problem, decided to restart it, and bootloop again. I'm currently trying to update my TWRP, and gonna try a different ROM, and wait to see if something like that happens, until then, I wonder what could be happening... I remembered an Asus Device that I had that had different firmware versions for 4.4 and 4.1, so if I tried to flash a 4.4 on a 4.1 firmware it wouldn't work, and for downgrade, the same problem happened, and wondered if Samsung has some difference between versions 4 and 5.
ssj4maiko Let me know if you find a more stable rom - I went back to pretty much stock, but with root as I wanted to use all the Samsung apps, but this constant random bootloops are annoying!
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
EDIT: Apparently this was a result of using the wrong setting for enabling hotspot in PropsConfig. Because all that stuff was set during bootup, deleting apps wouldn't change the situation. Setting worked fine on my Pixel XL, but not here. Changed the setting and all is well.
--------------------------
So, this is a weird issue I was curious about and may have missed on my searching. Every time I reboot the phone, when I got to log in it immediately follows up with a soft reboot. It's been happening for a while, and I'm not sure the source of the issue.
Running stock 12 ROM and rooted, but I disabled SU, modules, and Nova and am still running into the issue.
Might be quicker and easier to back up your required files and just factory reset.
Texan1 said:
Might be quicker and easier to back up your required files and just factory reset.
Click to expand...
Click to collapse
*sigh* I kinda made this post to avoid that step.
somethingsomethingroot said:
*sigh* I kinda made this post to avoid that step.
Click to expand...
Click to collapse
I know, it's just that it sounds like you've already disabled some things that could be causing it, which hasn't helped. If it was me, with something like constant reboots, I'd want to start fresh just to make sure they are eliminated for good
somethingsomethingroot said:
So, this is a weird issue I was curious about and may have missed on my searching. Every time I reboot the phone, when I got to log in it immediately follows up with a soft reboot. It's been happening for a while, and I'm not sure the source of the issue.
Running stock 12 ROM and rooted, but I disabled SU, modules, and Nova and am still running into the issue.
Click to expand...
Click to collapse
I've seen reports of "random" (=not intentional) reboots after
+ booting up the phone
+ using the FP scanner
+ making videos or shooting photo
+ doing a firmware update (I've seen both reports of ppl that "officially" OTAed & used manual flashing)
+ doing nothing
+ doing something
Some were able to fix their issues by factory resetting, some needed replacement devices. Some reported that even after a factory reset, the issue still persisted, but they were able to fix it by NOT using a backup via cable, some reported that even the Google Drive backup "corrupted" their phone (fix after setting up everything by hand from scratch). Some even reported their issues to get fixed via a software update.
So it seems to be connected to hardware (= replacement device) and/or software simultaneously (=fix via reset).
Strange this is since there are also numerous reports of Samsung owners that upgraded to A12 about random reboots. So it might even be something Android 12 related, or it's just Samsung also implementing similar bugs without it being A12 related (unlikely, since the reports seem to be centered around people using the new A12 update).
I also had the random reboot problem (~ 6 times a day, when doing nothing, it just rebooted when the phone layed on the table in idle). I wasn't able to fix it via a reset, so I got a replacement device.
I also have the "random" reboot problem on my Pixel 3 since upgrading to Android 12 (never had any issues all the years I've been using that phone), so that issue is clearly caused by A12, but I haven't troubleshot it/ tried to solve it, since I don't actively use the phone currently.
Aside from trying a factory reset and minding the backup issue (especially backups that you got from phones that did NOT have Android 12), there is not much more that you can do (ofc you could also use the Pixel repair/android flash tool to do a "clean" install of Android on your phone). Next step would be to contact Google.