Does anyone else have this problem or a solution? When I clean flash the rom I can't even restore an old backup.
I've been on xiaomie.eu beta(now 9.9.6) the past weeks usually after a couple days ona new room th backup now button works.
It never works here and using all the adb commands (which I've successfully used before to backup) are giving me "transport error".
I used " bmgr backup now --all' a million times, wiped transports switched transports, nothing works.
I changed tons to a pie aosio rom last night and I was able to restore an old backup.
Related
About a week ago, I received an update to 22.121.1.victara_retgb.retgball.en.GB retgb. Since then, I've been having multiple random reboots every day. ..
I've tried formatting cache, still reboots. Tried running in safe mode to see if it were external apps, still reboots. Tried a factory reset yesterday and downloaded my apps again, still reboots.
Are there more people experiencing these reboots? Is there a way I can rollback the ota (I don't have a backup)?
And another small thing. I noticed how it says GB all over my FW version name. However, I'm Dutch, bought my phone retail in The Netherlands, shouldn't the version be something like nl.NL, or eu.EU ?
Try doing a factory reset, but don't install your apps. If it does not reboot when your apps are not there, it means that one of your apps is causing the reboot. To figure out which app install apps 1 by 1 to see if it reboots. Repeat until you find the app that causes the reboot.
As far as the version GB. Have you flashed any firmware? If not, then GB is fine, it does not change by itself which means you are on the correct firmware.
Sent from my XT1095 using Tapatalk
AGISCI said:
Try doing a factory reset, but don't install your apps. If it does not reboot when your apps are not there, it means that one of your apps is causing the reboot. To figure out which app install apps 1 by 1 to see if it reboots. Repeat until you find the app that causes the reboot.
As far as the version GB. Have you flashed any firmware? If not, then GB is fine, it does not change by itself which means you are on the correct firmware.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
I was hoping there would be an easier solution, but I'll do another factory reset this evening and install 1 app per day (if i'm still without crashes). I did sideload the OTA to 5.0 when it became available a couple of months back, but I think that was a link to a french OTA.
I will update this thread when I know more...
So, I've tried several things now...
- Factory Reset with backup restore
- Factory Reset without backup restore and only install Whatsapp
- Factory Reset without backup restore and no apps installed except for pre-installed apps.
In between all resets I also cleared the cache, just to be sure...
But none of all the options have any effect. I had contact with Motorola support and they told me there is absolutely nothing wrong with the update and they've never heard of this before and I should wait for the 5.1 through the official notification and not attempt to flash any other firmware or sideload any other OTA.
The GB firmware is because I returned my device due to a broken headphone input and they probably just switched the phone out with another one which so happened to have GB firmware...
I really hope I can update to 5.1 soon and the issues will be gone as this is not something desirable for retail firmware...
hi, my friend called me on a different fone to walk them thru the process of rooting/twrp'ing an h811 using this as a guide ( https://www.youtube.com/watch?v=epcXXkMPRWk ).
and it booted up fine and the touchscreen worked. so i suggested they also try cyanogenmod (11.12.2015 nightly). they booted into twrp and did a backup then factory wipe and installed the cm-12.1...zip.
they booted into cyanogenmod and the touchscreen worked. but the t-mobile lte internet wasnt working so they wanted to go back.
good thing they created a backup first...
so they did a factory wipe then restored their image. when they rebooted the got a message process system not responding and the screen doesnt acknowledge any touch.
we tried going into twrp and doing wipe dalvik/cache ... we tried re-rooting using the steps outlined in the youtube video ... but the same problem persists.
after playing around with twrp and wiping random stuff the fone eventually allowed them to unlock the screen but there was no t-mobile service and after about a minute the screen stopped responding while they were scrolling thru the app-drawer.
i think as of now the only os where the touch-screen works is cyanogenmod; is it possible that cyanogenmod/twrp broke the touchscreen or lte modules in android ?
i thought they were two different os's that used different software/firmware ?
suggestions ?
thanks,
It's possibly a corrupt backup file. I would use TWRP to flash the stock ROM & see what happens.
i assumed re-rooting would clean everything since it uses the send-command program (essentially dd's the whole disk) but i guess not.
we also tried installing the rooted stock rom using twrp but still no joy.
Re-rooting doesn't do anything to the rom or drivers unless you're doing the easy root using a system img file. Then you're pretty much replacing your rom with one that has superuser already on it. That being said, did you upgrade to the 10n firmware/bootstack? The easy root is for 10h firmware/bootstack so that could be the source of your issues.
schneidz said:
hi, my friend called me on a different fone to walk them thru the process of rooting/twrp'ing an h811 using this as a guide ( ).
and it booted up fine and the touchscreen worked. so i suggested they also try cyanogenmod (11.12.2015 nightly). they booted into twrp and did a backup then factory wipe and installed the cm-12.1...zip.
they booted into cyanogenmod and the touchscreen worked. but the t-mobile lte internet wasnt working so they wanted to go back.
good thing they created a backup first...
so they did a factory wipe then restored their image. when they rebooted the got a message process system not responding and the screen doesnt acknowledge any touch.
we tried going into twrp and doing wipe dalvik/cache ... we tried re-rooting using the steps outlined in the youtube video ... but the same problem persists.
after playing around with twrp and wiping random stuff the fone eventually allowed them to unlock the screen but there was no t-mobile service and after about a minute the screen stopped responding while they were scrolling thru the app-drawer.
i think as of now the only os where the touch-screen works is cyanogenmod; is it possible that cyanogenmod/twrp broke the touchscreen or lte modules in android ?
i thought they were two different os's that used different software/firmware ?
suggestions ?
thanks,
Click to expand...
Click to collapse
I relatively had the same problem where I flashed CM and did not like it because it was buggy and so I restored an nandroid and the once working nandroid was plagued with errors of the touchscreen not working, the phone would freeze, system crashes... It ended up being caused by the fact that I did not flash the 10N bootstack update before hand. After I flashed the new firmware and then flashed CM; all of CM's bugs disappeared. I haven't gone back to stock LG software since CM works flawlessly and is now my dailydriver so I cant say for sure if it will fix the stock rom but It probably will since it cleared up all my bugs like the camera not working, videos now playing...
btw to get data working in CM go to settings/mobile networks/Access point Names/ then scroll down and click "T-Mobile US LTE IPv6" and that should fix the internet issues you have since it fixed it for me.
they didnt do anything with the 10n bootstack (i dont know what that is).
maybe cyanogenmod automatically does the 10n thing (how to manually go back to 10h) ?
i assumed re-loading the 5 gb .img file would bring us back to square-1 but i guess not.
also, how to know what bootstack they are running. i told them to check about fone but they told me nothing in there mentions 10n or 10h.
About phone > Software Info > software version will will say h81110n if on 10n.
Same here on Stock...
I have this running stock H81110n software, which I flashed using a KDZ. However, it only freezes up occasionally, and turning the screen on and off once or twice always gets rid of the problem. It's not bad enough for me yet to warrant any factory resets or tweaking so far, but the problem is there...
Well this thread is for users on limited data who can't download more than 1 update per day and are rooted. I live in a place where network only gets worse . So the thing is for some reason the Oneplus updater shows different versions at different times. I noticed this when I was trying out Custom ROMs and restored my default OOS 3.5.3 backup a number of times.
The procedure I followed will WIPE your personal data, so take necessary backup prior to start.
So I got this update named OnePlus3TOxygen_28_OTA_029-039_patch_1701140132_8ffdc05d9c.zip of 920.60 MB when I was on OOS 3.5.3 . But when I kept installing it via TWRP it failed. I even tried with stock recovery, but still no luck. So I backed my app data from ES file explorer and did a factory reset. This time the updater was starting to download the entire 4.0.2 ROM of 1.5 GB . I had to cancel it and wiped my entire ROM. Then I flashed stock recovery and flashed OOS 3.5.3 . I started the device, completed the initial setup and upgraded locally from the Updater app using the aforementioned OTA zip. That worked and now I have Nougat up and running without having to download the entire OOS 4.0.2 ROM again.
To my understanding the ROOT was probably the issue for OTA failure while updating. Also I faced quite grave heating issues in daily usage and no gaming, which apparently got sorted out in Nougat. Do share your opinion cuz I'm still new to this device and have a lot to learn and thanks for reading.
Hi all guys,
yesterday i updated my Mi5 to miui 10 but after rebooting to system i got an annoying bluetooth problem so it just didn't work at all.
So i repeated the same procedure (uploaded another .zip via usb, rebooted to TWRP installed the zip) and as a poor dumb i checked wipe data..
And i don't have any recent backup
So i'm trying to get my data back because there they are, i found two softwares that promise to do the job (minitool and Gihosoft) but both get stacked asking me to root my phone (which i remember i already did). Anyway i followed xda guide about magisk and installed from TWRP, so now i have the app installed but the software still stacked.
Can anybody help me please?
I really need to get those data back.
Ps. now the bloody bluetooth works
Pps. i found this topic and i'm now trying the other software.. Still if anyone has better option they will be more than welcome.
Hi. I got an unknown CSC unlocked N960F/DS from ebay sometime back in late 2019. As soon as it arrived, I dumped lineage on it and was mostly happy with it for a while. Various features eventually went and broke(bluetooth most of the time, photo uploads in any apps basically) and yesterday I decided to upgrade my rom. I went and downloaded one of the lineage builds and sideloaded it through adb. That's where the story begins. My phone didn't make it past the brightness reloading part of the bootloader screen. I went through some other builds but that was obviously hosed so I grabbed the ONEUI2 STABLE rom and devbase rom from the exynos section here. I flashed devbase and while my phone worked, I had no cellular, my launcher was constantly crashing to the point where I couldn't use it, and bluetooth was also constantly crashing. I did the same with the ONEUI 2 STABLE rom only to be stuck at the SAMSUNG + blue/cyan LED screen after optimizing apps.
I don't really know where to go from here, but I guess I really don't want to trash my userdata. There's a lot of **** there that I can't really get back if I wipe it(avid user of signal).
Note for all you folks in back:
This wasn't actually a EFS related problem. I had a CP/BL vs. system mismatch and the firmware i was using simply didn't use the baseband. I flashed back to stock, BRI CSC and was perfectly fine. I'll probably restore my data partition from a backup in a few hours.
Obvious PSA that saved me a lot of time:
BACK UP YOUR EFS!!!!!!!