I have been running Lollipop stock on D800, rooted but not installed TWRP yet and I have also not run Titanium Backup. I will be losing a lot of data in case there's no solution to this without a full flash. *sigh*
Well, what I did was that I tried to enable Tethering on my phone using this guide:
http://forum.xda-developers.com/att-g2/help/enable-tethering-att-lollipop-using-t3088431
I followed the instructions exactly as written and made sure I did it right; but as soon as I replaced the original "settings.db" file with the edited one; the phone restarted itself and stuck at ATT logo. The led on top keeps changing colour but ATT logo stops rotating and is stuck.
Please help... Could this be due to permission issue? I had thought of checking permission of the .db file but the original tutorial made no mention of it so I thought it should be no big deal. I don't know what else could have went wrong. I only changed the value of "tether_entitlement_check_state" to 0.
PRINCE2013 said:
I have been running Lollipop stock on D800, rooted but not installed TWRP yet and I have also not run Titanium Backup. I will be losing a lot of data in case there's no solution to this without a full flash. *sigh*
Well, what I did was that I tried to enable Tethering on my phone using this guide:
http://forum.xda-developers.com/att-g2/help/enable-tethering-att-lollipop-using-t3088431
I followed the instructions exactly as written and made sure I did it right; but as soon as I replaced the original "settings.db" file with the edited one; the phone restarted itself and stuck at ATT logo. The led on top keeps changing colour but ATT logo stops rotating and is stuck.
Please help... Could this be due to permission issue? I had thought of checking permission of the .db file but the original tutorial made no mention of it so I thought it should be no big deal. I don't know what else could have went wrong. I only changed the value of "tether_entitlement_check_state" to 0.
Click to expand...
Click to collapse
Sorry to hear. Since you didnt have TWRP installed and you didn't take any sort of backups, you are bound to lose your data. I can't think of a way except a full reset or a re-flash of firmware. The real issue is data. Phones can be bought again but data can't be recovered. I hope you had at least google backup service enabled. Sometimes, the factory reset fixes the stuck at LG logo but that itself is not guaranteed and even if you are able to bring your phone back to life, your data will be reset *sigh*
Related
Ok, I'm having some major issues here and hope someone can help. I seem to be "soft-bricked." My Maxx will boot up, gets to the droid graphic (right before it normally gets to the unlock screen), screen dims and capacitive buttons light up, then it just pulses brighter every 10 seconds or so. Once, after sitting for a while, a voice said "Loss of service."
History:
1. Was rooted, unrooted to get the OTA, re-rooted. Everything was fine.
2. Got tired of the wireless charging sound, so I applied the fix noted here - http://forum.xda-developers.com/showthread.php?t=2450085&page=3
3. Also had Xposed installed with NFCUnlock and GravityBox.
4. Was running into issues with apps randomly losing root access, and the wireless charging sound would come back, so I downgraded Xposed to the previous version as recommended in another thread.
5. Also was using DelayedUnlock app, so I disabled USB Debugging as recommended.
6. Still faced issues with apps losing root access, so I decided to restore the apk I replaced in #2 with the backup I made. Rebooted phone and am soft-bricked (I guess).
7. Downloaded the latest FXZ (http://sbf.droid-developers.org/obake/list.php) and used HouseofMoto (http://forum.xda-developers.com/showthread.php?t=2450702) to flash it, no help. Deleted the <step operation="getvar" var="max-download-size" /> line as recommended in another thread (http://forum.xda-developers.com/showthread.php?t=2416478&page=6) and flashed again, still doesn't work.
I posted this in another thread in General, but was afraid it would get lost in the thread and wasn't sure that thread was appropriate for my request for help. Any help would be greatly appreciated!
Nevermind, impatience got the best of me and I factory reset my phone, so I'm back up and running again. Hated to do it as I didn't want to lose all my stuff, but hopefully I can get it re-rooted and restore my TB backups. A little worried about re-rooting, though.
osucowboy96 said:
Nevermind, impatience got the best of me and I factory reset my phone, so I'm back up and running again. Hated to do it as I didn't want to lose all my stuff, but hopefully I can get it re-rooted and restore my TB backups. A little worried about re-rooting, though.
Click to expand...
Click to collapse
Just in case anyone else has similar issues and reads this, I believe after trial and error I found the culprit. The DelayedLock app seems to be the issue causing my brick. Will be avoiding this paid app, sure wish I could get a refund on it.
I updated my Oneplus One manually to the newest Version of CM12s. While flashing it, my Recovery (TWRP) chrashed. So to be sure I installed my freshly performed Nandroid Backup. But nothing helped. I couldnt connect with the Wifi, no SIM Cards were found, no Bluetooth Connectivity and it had Random Reboots. So i decided to flash back to Stock CM11s (the first ever released). But the Problems were the same afterwards. I flashed the Stock image via ADB and, after I found out nothing changed, via the Oneplus One Toolkit, but the Problems were still there. I also made a video on Youtube to show what happens and i hope that i can repair it and must not send it back to repair, because a repair would cost me up to 300€. So pls tell me a way to fix this Problem, because I really like this Phone:crying::crying::crying:
For the video search "Oneplus One not working" by the User "axel thegamer"
AxelWexel said:
I updated my Oneplus One manually to the newest Version of CM12s. While flashing it, my Recovery (TWRP) chrashed. So to be sure I installed my freshly performed Nandroid Backup. But nothing helped. I couldnt connect with the Wifi, no SIM Cards were found, no Bluetooth Connectivity and it had Random Reboots. So i decided to flash back to Stock CM11s (the first ever released). But the Problems were the same afterwards. I flashed the Stock image via ADB and, after I found out nothing changed, via the Oneplus One Toolkit, but the Problems were still there. I also made a video on Youtube to show what happens and i hope that i can repair it and must not send it back to repair, because a repair would cost me up to 300€. So pls tell me a way to fix this Problem, because I really like this Phone:crying::crying::crying:
For the video search "Oneplus One not working" by the User "axel thegamer"
Click to expand...
Click to collapse
Can't find your video, can you paste the link as text?
gsmyth said:
Can't find your video, can you paste the link as text?
Click to expand...
Click to collapse
i cant, because i made a new account here.
just search "oneplus one not working", then set "filter" on today and you will find it
AxelWexel said:
i cant, because i made a new account here.
just search "oneplus one not working", then set "filter" on today and you will find it
Click to expand...
Click to collapse
Ok found your vid, I see you have flashed the stock image files via ADB, have you done a full factory reset (wiping data) from the phone/TWRP? Its a bit worrying that flashing the stock image files didnt sort the issue. As it seems to be WiFi on/off that causes the reboot it would make me think it was to modem/radio but this should have been written again when you flashed the stock images.
@AxelWexel can you check in your Settings>About phone menu if your IMEI number is showing? Just in case your EFS has become corrupted. It definitely sounds fixable as if something has corrupted and needs wiped fresh.
EFS fix:
http://forum.xda-developers.com/oneplus-one/general/fix-people-corrupt-efs-mobile-data-t2836389
Also worth a shot, fixing corrupt partitions guide in ADB:
http://forum.xda-developers.com/oneplus-one/general/guide-identifying-fixing-corrupted-t2993500
gsmyth said:
Ok found your vid, I see you have flashed the stock image files via ADB, have you done a full factory reset (wiping data) from the phone/TWRP? Its a bit worrying that flashing the stock image files didnt sort the issue. As it seems to be WiFi on/off that causes the reboot it would make me think it was to modem/radio but this should have been written again when you flashed the stock images.
@AxelWexel can you check in your Settings>About phone menu if your IMEI number is showing? Just in case your EFS has become corrupted. It definitely sounds fixable as if something has corrupted and needs wiped fresh.
EFS fix:
http://forum.xda-developers.com/oneplus-one/general/fix-people-corrupt-efs-mobile-data-t2836389
Also worth a shot, fixing corrupt partitions guide in ADB:
http://forum.xda-developers.com/oneplus-one/general/guide-identifying-fixing-corrupted-t2993500
Click to expand...
Click to collapse
Thx for the Links and i tried to watch on my phone and there is no imei number. I also did a full wipe after i found the issues. I also tried it via the Toolbox to flash the stock rom back but it hadnt change anything. But I will look the links you postet and reply if anything has changed. But now thx again:good:
P.S: I renamed the Video to "Oneplus One not working (23.06.2015)" to find it more easily
Edit 1: The Second Link with fixing corrupt partitions via adb wont work for me because i dont have root but my bootloader is unlocked. so i cant find the root acsess for adb in the developer options
Edit 2: I installed color os like the link said, done everything it said, but still no wifi, bluetooth and no sim card detection:crying:. Luckily the random reboot stopped Could you again help me further more because it seemed to help
Edit 3: I went back to cm11s, because in color os when i turned the phone off it turned on again, the connectivity was not there. After the install it became worse with the random reboots. I think i must send it to repair and pay 300€:crying::crying::crying::crying:
Hi there! I have a Stock kitkat d80020y, made root with stumproot but without custom recovery, it's running stock right now.
First of all let me tell that I have in my computer nandroid backup of it (TWRP & CWM) made with OnlineNandroid and one LGBackup made with system restore menu.
Here's the trouble:
I am about to sell my phone so i was backing up some stuff yesterday when i realized it was not syncing contacts with google, after researching a bit I deleted the "com.android.providers.settings" folder which it was situated into "data\data" and rebooted device.
Then, sync problems gone but some another problems came up, couldn't get into some settings just as language, swipe down settings didn't work neither, home button didn't work at all, etc; when tried to use that things, phone just did nothing or stayed one second and got back to home screen. Read something that factory reset would definitely solve my issue, well it did solved it at a glance, home button was functional again but, things like language submenus were still not working.
So then, I try to install an LG Backup using the system app, could restore settings and appeared to be solved, but after another factory reset, remember I'm about to sell it, the whole issues came up again.
As I have nandroid backup I've recently checked the clockworkmod folder and find the deleted folder.
Considering that i could manage to get that LGBackup installed again, could it be possible to paste "com.android.providers.settings" back into "\data\data" folder then?
Should that be the definitely fix? Or I'll have to reflash all nandroid even though I don't wanna take that risk because is just those problems, apparently related to that specific deleted folder, the other things of the phone are intact and work great.
In case of need reflashing, could you tell me about any easy tutorial on how to do it, including custom recovery installation for my stumprooted device?
I don't actually know how to ADB any android device, if you could also help me with the right tutorial and drivers for this phone so i have everything ready just in case of needing CMD to fix this device it would be great.
Hope I get some answers soon so i can quickly fix the device, any ideas are welcomed and will be utterly appreciated.
Sorry for the long text but i wanted to be as clear as i could.
Regards!
lautta10 said:
Hi there! I have a Stock kitkat d80020y, made root with stumproot but without custom recovery, it's running stock right now.
First of all let me tell that I have in my computer nandroid backup of it (TWRP & CWM) made with OnlineNandroid and one LGBackup made with system restore menu.
Here's the trouble:
I am about to sell my phone so i was backing up some stuff yesterday when i realized it was not syncing contacts with google, after researching a bit I deleted the "com.android.providers.settings" folder which it was situated into "data\data" and rebooted device.
Then, sync problems gone but some another problems came up, couldn't get into some settings just as language, swipe down settings didn't work neither, home button didn't work at all, etc; when tried to use that things, phone just did nothing or stayed one second and got back to home screen. Read something that factory reset would definitely solve my issue, well it did solved it at a glance, home button was functional again but, things like language submenus were still not working.
So then, I try to install an LG Backup using the system app, could restore settings and appeared to be solved, but after another factory reset, remember I'm about to sell it, the whole issues came up again.
As I have nandroid backup I've recently checked the clockworkmod folder and find the deleted folder.
Considering that i could manage to get that LGBackup installed again, could it be possible to paste "com.android.providers.settings" back into "\data\data" folder then?
Should that be the definitely fix? Or I'll have to reflash all nandroid even though I don't wanna take that risk because is just those problems, apparently related to that specific deleted folder, the other things of the phone are intact and work great.
In case of need reflashing, could you tell me about any easy tutorial on how to do it, including custom recovery installation for my stumprooted device?
I don't actually know how to ADB any android device, if you could also help me with the right tutorial and drivers for this phone so i have everything ready just in case of needing CMD to fix this device it would be great.
Hope I get some answers soon so i can quickly fix the device, any ideas are welcomed and will be utterly appreciated.
Sorry for the long text but i wanted to be as clear as i could.
Regards!
Click to expand...
Click to collapse
Finally solved flashing stock again with a guide on htcmania forum, this guide is really great for spanish speaking guys like me and many others,(xda doesn't allow me put the link); theres also an english guide here on xda.
I used autorec to install recovery just in case you wanna know
See you!
I have a Note-4 T-Mobile variant(N910T), I have been using Xenon HD and then CM 12.1. After a while when I wanted to go back to stock, and when I flashed stock rom back, the phone was really laggy at first and during setup, there was a popup which said that Factory mode is enabled and I have to switch back to User mode before using it and after a few seconds it disappeared, this happens every time i reboot while in Stock Rom. Somehow after a few minutes, I get the WiFi on again but the keyboard gets stuck after a few presses and phone gets real laggy. After the setup I googled the problem and found out something regarding the EFS Folder, so I rooted it once again and installed ES File explorer and went into EFS and found that it was empty. I tried placing a phone call and it went through and I was also able to use LTE, but when I went to about phone to see IMEI, i saw that the IMEI was wrong, I even tried to setup fingerprints, but it kept saying me to reboot as something was wrong with the fingerprint sensor. Now the weird thing here is that when I am in a Non-touchwiz based Custom Rom, I do not find any lag and the IMEI is correct. I have tried these things already:
Going to EFS and switching Factory mode on, but as i told EFS folder is empty.
Backing up EFS from the custom and restoring when I'm in Stock.
If anyone knows how to fix this, could you please help me?
Thanks!
Hello,
Welcome to XDA.
Try posting your question in the forum linked below.
http://forum.xda-developers.com/note-4/help
The experts there may be able to help.
Edit: Solved, see bottom
ROM (D6633_Customized HK_1290-5630_23.4.A.0.546_R6C_HK_SuperSU2.46_XZDR2.8.21-signedv2)
Bit of a dumb move on my part. It all started when my snapchat stopped working, I updated, and then Titanium Backup wouldn't restore the data properly (giving me "parse error"). I was trying to fix that and read online that sometimes this is caused by improper permissions, so I booted into recovery mode, couldn't find the option, but somehow decided "hey, maybe my root permission (?) is wrong slash it's 6am and I just watched a wild 2016 election end" and I hit the button. Now my phone is stuck in a bootloop.
So my question:
1) What exactly does re-root phone do (in CWM), and why would that have messed me up? Is it because I have a pre-rooted rom?
2) I wiped cache and delvik and it doesn't help
3) How do I fix this? I was thinking of loading a SuperSU zip on the SD card from my computer and flashing that, assuming somehow a corrupted root is at fault. I can't seem to get the thing in ADB mode as a side note.
3b) If that seems like a good idea, does it matter what one I use?
4) If I reflash the ROM, it should keep my apps and stuff, ya? I don't actually care if my phone is crippled, I just need it to work long enough to properly back up some media, and mainly get my whatsapp over to my new SIM card. If I can't get in it's forever stuck on my old number which I don't have the SIM for anymore.
Any help would be GREATLY appreciated.
Edit: I don't know how to delete this. Anyways, with other resources I found out that because I used a pre-rooted ROM, there were issues with using CWM to try to do the rooting with its built in functions, softbricking the phone. Reflashing the original pre-rooted ROM worked fine.