Hi, first, thank you for your attention, i wish i could solve this without loosing someone's time, but I'am lost here.
I have nougat with EMUI 5. Unlocket bootloader, TWRP (meticulous). I've tried to install a custom ROM (elitev6) but with no luck. I've made a backup of all partitions, so to revert was pretty straight forward..I've restored and noticed a strange begavior on boot, there was the android logo instead huawei animation, no worries...then after a day I found myself with a phone that have no sound at all and no camera at all...also I've noticed that the radio App was gone (there only package name). I use custom ROMs for a long time, but the last year I've lost that curiosity for trying something new. How can I revert all to stock nougat ROM?
Thank you very much!
Related
Hi all,
Some time ago i asked, and received, some support on these forums on how to properly carry out a nandroid backup... following the sound advice i got, i carried out my backup (using TWRP for the record, with all the options checked), and stored it away for a rainy day... said day came yesterday, when i messed up my system and rendered it instable (i tried to manually delete the dalvik cache directory in order to free up the 2,5GB of space it was taking)... since i knew there was i high chance of this ending in disaster, the last thing i did before the delete was carry out another nandroid, so i could easily return to where i had left off... how wrong i turned out to be
as soon as i the system became instable following my experiment of deleting the d. cache directory, i recovered the latest nandroid (i.e. the one i had made just hours before) and everything seemd to go smoothely until the first reboot... when the following happened:
- first reboot after recovery took ages, much like the first reboot following the flashing of a new rom... not the end of the world, but that was the first sign that all was not well
- the status bar disappeared, and there was no way of making it come back (i.e. nothing to do with the launcher, i typically use apex but i i tried switching to both nova and touchwiz which i also kept up to date but the stats bar was nowhere to be seen)
- even if not having a status bar with all the info on it is acceptable (which of course it isn't, but lets just say), the sytem became completely instable after 5minutes of operation... with each app taking turns to shutting down until i kept getting the message "system UI has closed" over and over, to the point that doing a reboot was challenging since i barely had the time to press on the screen between instances of this bloody error message appearing...
...i did of course try and return to my older nandroid backup, but... lo and behold... exactly same behaviour...
so now i have resorted to formatting the internal memory card and flashing a new rom and basically starting over... just what i hope the nandroid would spare me basically :/
question is: does this sort of error sound familiar to anyone? can someone give me a tip maybe on what i may have done wrong?
any opinion, tips& advice much appreciated
I have the exact same problem. It happens on TW Lollipop ROMs. Haven't found a fix. I'm using Philz Touch Recovery and the old no knox bootloader.
Anyone? I have researched this but cannot find any similar problems reported... it can't just be me and pavelcheto...
Maybe it a recovery fault. Faulty backup or faulty restore.
No problems with my older backups. I restored my KitKat TW backup, working fine. Restoring CM12 backups also works fine. I've looked for a new recovery, Philz is discontinued, CWM hasn't been updated for a year and I really don't like TWRP.
I use TWRP 2.8.3.0 and never have (and hopefully never will) encountered any issues with restoring backups.
Considering i recovered 2 separate backups for a total of 3 times (i tried recovering the first backup twice) i doubt the issue was with the recovery itself... however since pavelcheto had no issues with the kk recovery maybe it could be lollipop related?
Anyone successfully recovered a lollipop nandroid backup?
platypus78 said:
Considering i recovered 2 separate backups for a total of 3 times (i tried recovering the first backup twice) i doubt the issue was with the recovery itself... however since pavelcheto had no issues with the kk recovery maybe it could be lollipop related?
Anyone successfully recovered a lollipop nandroid backup?
Click to expand...
Click to collapse
I recovered my lollipop gpe backup a couple of times without a problem.
Data encryption may cause restoring problems.
I have restored CM12 backups (based on 5.0.2) serveral times, no problem there. I've had issues only with TouchWiz Lollipop ROMs, I have tried different custom roms, all get bugged at restore.
pavelcheto said:
I have tried different custom roms, all get bugged at restore.
Click to expand...
Click to collapse
Just to make sure I understand correctly : you mean all TW custom roms you've restored have had problems?
Wonder if anyone else has managed a bug-free restore of a 5.x TW?
Yes, but only on Lollipop. KitKat TW roms restore just fine. I am using Philz Touch Recovery. I have tried 3 different TW Lollipop roms and they all fail to restore properly. No wallpaper, black wallpaper and no status bar. And after a minute or two System UI starts crashing. If then I do factory reset from recovery and the rom starts normally (welcome guide and stuff) and works fine.
bumping this thread because i cant seem to find a solution for this anywhere.
TheAwesomeBit said:
bumping this thread because i cant seem to find a solution for this anywhere.
Click to expand...
Click to collapse
There's no solution for this as per comments above. TW LP is not restorable. You can flash a new lollipop ROM tho'
Sent from my GT-I9505
I received an update push from Motorolla that installed Nougat. After that, my phone would crash every 3-10 minutes. I did all the troubleshooting I could find online. I contacted support and they wanted me to spend $150 to get it "refurbished." Of course, it sure seems like a software problem, so that wouldn't help me anyways...
I turned to custom. After rooting, installing SuperSU and TWRP, I couldn't get several versions of AICP or Lineage to ever boot (stuck on loading screens). I also tried all the advice from this thread.
I went back and installed the stock Rom using f2fs , and the phone would get to the "hello moto" part of the boot up, then crash and reboot. I tried again using EXT4, and it worked, but just like before I ever begun, my phone was crashing every 3-10 minutes. However, the first crash wasn't until after I made a phone call, and my phone had been crash free for about 20 minutes before that call.
I'm a I.T. guy, but I'm not a "phone" guy. But it seems to me that there must be some other software that was modified during the update that is causing the problems that isn't part of ROMs. Something in the Kernal, or a driver folder or something?
Also, is there a way to get crash reports? So maybe if I at least go back to the default ROM and wait for it to crash, I have some info to work with?
Any help is greatly appreciated, thanks!
Flash full stock 6.0x for your model/region.
Important:
Without bootloader, gpt. Don't try locking BL.
Links you can find in my signature.
Try normal boot and after success any custom.
You cannot allow any ota update after it.
Some customs are only for Nougat modem/radio - don't flash it. @Kaivian
Ok, I got most of that, except I don't know what gpt refers to and am not getting any hits on search.
My signature - flashing stock - without bootloader & gpt.
So, I installed a 6.0 stock ROM and got tons of errors. I tried a 2nd time, still got tons of errors. Needless to say, stock 6.0 didn't boot. I decided, "The heck with it" and tried installing Lineage 7.1 again... and it worked! It finally booted up entirely. However, now I get a "Sim card missing" notification. Can I just reinstall part of something... like the modem? so I can keep this "working" lineage boot? Or am I starting over yet again?
Repeat
from
fastboot flash modem ...
to
...fsg.
dzidexx said:
Repeat
from
fastboot flash modem ...
to
...fsg.
Click to expand...
Click to collapse
This caused it to not boot.
I went back to 6.0 and turned off auto-updates. I'll try again sometime when I have time. I did like the custom rom a lot, just couldn't use it as a phone xD
Hey everybody, I need help. I have a J320P that is stuck in a boot loop, when it was found like this by my friend they came to me and asked if I could help. I have no information on how this happened other than they took a shower and when they came back it was like this. I have tried installing stock firmware 3 times to no luck. I might have an sd card somewhere with the backup for this phone but finding it would take some time so in the mean time I am turning to the forums. If anyone could help that would be amazing. I will provide more information and answer questions as they come.
Steps I have taken:
1. dirty flash of stock latest firmware
1. wiping the phone completely
2. Installing latest stock firmware
3. Still bootlooped
Not solved
So after triple wiping through TWRP and installing the stock firmware again it was still looping so i left to run to the store quickly and when I returned I tried powering it on and it loaded normally and I am still setting it back up.
Leaving the original comment. After coming home from work my friend said it had started doing it again, and it is. This time there was no root and no system anything messed with, does this mean there is a hardware problem?
I have a Samsung s8 snapdragon 950U, T-mobile, running android 7.0, baseband - G950USQU2BQK5, build - nrd90m.G950USQS2BQL1. A couple weeks ago the mic stopped working so that I could not use speech-to-text which I rely on heavily. Nothing fixed it until I reflashed the phone with the same firmware. Before that I performed a ROM backup using clockworkmod and moved the backup files to my computer. I also used Titanium to backup system data like sms messages. After that, just as I was going to restore data, I get TMobile message that I’ve never seen before about a firmware update. I figured if it’s Oreo the update would fail because I have a custom ROM. Stupidly I chose to update and the next thing I know I have Android 8 – NOT rooted. That prevented me from using Titanium to restore settings.
Stupidly again, I decided to go back to the android 7 firmware and proceeded to root and flash the phone as I did before. This time it failed. I tried the SAMPWN and SAMFAIL methods repeatedly without success. Now I have bricked phone that just loops through a screen that says “Installing system update” followed immediately by another blue screen with a defunct android that says “no command.” I can get to download mode which Odin sees, but not to recovery, or anything that Smart Switch(which isn’t so smart) sees.
I have been downloading the Oreo firmware G950USQU4CRE9_G950UOYN4CRE9 for the past 4 hours hoping that I can maybe flash that. HELP! Can I somehow restore the nandroid backup using my computer? What should I do. I just need a working phone or I’m in big trouble.
frankygoes said:
I have a Samsung s8 snapdragon 950U, T-mobile, running android 7.0, baseband - G950USQU2BQK5, build - nrd90m.G950USQS2BQL1. A couple weeks ago the mic stopped working so that I could not use speech-to-text which I rely on heavily. Nothing fixed it until I reflashed the phone with the same firmware. Before that I performed a ROM backup using clockworkmod and moved the backup files to my computer. I also used Titanium to backup system data like sms messages. After that, just as I was going to restore data, I get TMobile message that I’ve never seen before about a firmware update. I figured if it’s Oreo the update would fail because I have a custom ROM. Stupidly I chose to update and the next thing I know I have Android 8 – NOT rooted. That prevented me from using Titanium to restore settings.
Stupidly again, I decided to go back to the android 7 firmware and proceeded to root and flash the phone as I did before. This time it failed. I tried the SAMPWN and SAMFAIL methods repeatedly without success. Now I have bricked phone that just loops through a screen that says “Installing system update” followed immediately by another blue screen with a defunct android that says “no command.” I can get to download mode which Odin sees, but not to recovery, or anything that Smart Switch(which isn’t so smart) sees.
I have been downloading the Oreo firmware G950USQU4CRE9_G950UOYN4CRE9 for the past 4 hours hoping that I can maybe flash that. HELP! Can I somehow restore the nandroid backup using my computer? What should I do. I just need a working phone or I’m in big trouble.
Click to expand...
Click to collapse
update: i was able to flash the oreo firmware basically puts me back at step 2. becasue i backed up when rooted my backups now cannot be restored, or can they, at least in part? Is there any way i can restore some of the data in either the nandroid or titanium backups to my nonrooted oreo s8?
Hey!
So I got the 9.0 pie on my Xiaomi MiA1 and I decided to test it and I was pretty disappointed, so I decided to try to revert back to 8.1 oreo. I unlocked the phone, fastbooted twrp, wiped the data and tried using miflash to install the rom and also tried flashing it through twrp. I have been having this problem for 2 days now, i successfully install the OS but then I get stuck in a boot loop and now I can't even get past the android one logo and it keeps loading there. I didn't do a backup, I regret that. I can't remember how many times I already try flashing different roms but nothing really seems to work, in fact seems like it's getting worse since before it would actually boot until it asked me to put my SIM card PIN but then it would reboot constantly, but as I said before now it wont get past android one screen. Also maybe its worth mentioning that i try using lazyflasher already a few times and that there was a time that it actually worked but it got automatically updated to 9.0 pie again so back to the start and, as i thought that i knew what i was doing, i just tried redoing what i did before to install 8.1 again and disable automatic updates before connecting to the internet. I can go to fastboot mode and I can use twrp doesn't seem like I have a problem there, any help is appreciated!
maybe just can let 9.0 install , looks like is the only way that u have for a dayle phone
Mig979 said:
Hey!
So I got the 9.0 pie on my Xiaomi MiA1 and I decided to test it and I was pretty disappointed, so I decided to try to revert back to 8.1 oreo. I unlocked the phone, fastbooted twrp, wiped the data and tried using miflash to install the rom and also tried flashing it through twrp. I have been having this problem for 2 days now, i successfully install the OS but then I get stuck in a boot loop and now I can't even get past the android one logo and it keeps loading there. I didn't do a backup, I regret that. I can't remember how many times I already try flashing different roms but nothing really seems to work, in fact seems like it's getting worse since before it would actually boot until it asked me to put my SIM card PIN but then it would reboot constantly, but as I said before now it wont get past android one screen. Also maybe its worth mentioning that i try using lazyflasher already a few times and that there was a time that it actually worked but it got automatically updated to 9.0 pie again so back to the start and, as i thought that i knew what i was doing, i just tried redoing what i did before to install 8.1 again and disable automatic updates before connecting to the internet. I can go to fastboot mode and I can use twrp doesn't seem like I have a problem there, any help is appreciated!
Click to expand...
Click to collapse
You can install stock Pie via Mi Flash tool.
Sent from my Mi A1 using XDA Labs