Hey,
I think I´ve got a little problem.
I wanted to restore a backup with the Recovery (RA v. 1.7x) but since about 45min my phone does nothing... only the full stops are going to be more and more and now my screen is full of them...
So as a conclusion: Since 45min my phone tries to restore my backup.
So what shoukd I do?
I´m afraid to brick my phone if I remove the battery or do sth. during restore...
EDIT: Problem solved...
Noticed that adb commands are working during restore and so it was possbile to reboot my phone...
Reposting this here…
Hi, all!
My Samsung Galaxy Ace (S5830) running under a custom ROM The Ultimatum (I've been using this custom firmware for a few weeks now, with no real problems up until now), is bootlooping with no apparent reason. On a rare occasion, most apps on the phone stopped responding and would crash upon opening, and would require a restart before they worked again. Well this happened to me a few hours ago, so I decided to reboot my phone. After coming back to check my phone, I had found it was still booting. This has gone on for several hours now, and I've tried turning it on and off, removing batteries and everything. It's stuck in bootloop. I found this was odd, as I have had no dramas with the firmware I've been using. I have not made ANY recent changes to the phone whatsoever, so I can hardly believe it would be my fault.
Now, my question is; how do I fix this without wiping all data and installing a clean ROM? I have a lot of stuff in the internal storage I can't afford to lose, and it's really important to me. A full wipe of all data would not be ideal. I can access recovery mode.
I have tried a suggestion a user here made and made a nandroid backup, did a full wipe, reinstalled the ROM (which allowed me to get out of the bootloop) and then restored the data from the backup (which stuck me back in a bootloop). Still no idea and I really don't want to lose this data. If it's too much effort to fix the loop, is it possible to extract the data from the backups on a PC and manage to restore it to a clean wipe?
Thanks in advance!
Fixed my problem by doing a clean installation, and using Titanium Backup to extract the data from my nandroid backup. It was quite a simple solution, really. No idea why no one seemed to suggest it, though.
Oh well, my problem is solved.
I've left my phone with 60% charge yesterday night.When I woke up the battery was at 0%.I charged it to 100%, rebooted and the phone was stuck at LG loading screen.I got CM11 nightly 26.
Then I restored 2 diff nandroid backups after a full wipe.It did not work and I finally decided to use lg mobile support tool.It successfully downloads, installs the firmware but somehow the phone is stuck at bootanimation.
I've tried to reinstall USB drivers; flashed the KDZ about 5 times now and I really am hopeless.
I haven't dropped my phone; haven't done any physical damage to it and as far as I know if it was just corrupt internal storage I could get over the problem by wiping the partitions.What could be causing this problem?
Weird part is; when this happened I wouldn't even get to see CM boot animation but after attempting to unbrick the phone with mobile support tool, I got to see the bootanimation but it didn't boot (waited approx 30 mins)
Has anyone faced such annoying brick before? What could be causing it? Any solutions/recommendations?
EDIT : According to logs the s/w upgrade completes successfully.No errors nothing, but the phone won't go thru the boot animation.
Mobile support tool .KDZ flashing logs
EDIT2[SOLVED] : Seems like I've found the issue and solved it.The O/S crashed somehow during the night; damaging the TWRP date file(s).As specified in this post (under warning title) it led to a softbrick which can only be recovered after flashing a firmware and wiping data/cache partitions afterwards.I actually had TWRP 6.3.0 and was made by a different user but issue seems to persist.Guess I'll stick with CWM.
I hope this helps someone if they face the same issue later on.
Hi all
My GT-N7000 phone, running (it seems to remember) official Android 4.1.2 some days ago suddenly reset, driving me into the configuration procedure like the first time I switched on.
The following day it reset again, and went into bootloop on Samsung screen. I tried the following:
wipe cache data - no result
reset to factory data - no result
flash via Odin the N7000XXLT9_N7000ITVLT3_ITV Kernel - no result
When I went into recovery mode before reflashing kernel, I got the "can't mount /efs" error. After reflashing kernel, I installed PhilZ recoverty with Aroma, and discovered that the EFS folder is here, but it is EMPTY, and in fact I can't mount it even in PhilZ.
Another strange thing is that all my custom data are still on the telephone, despite the factory reset I have done.
I have searched a lot, but I can't find a way to solve my problem so I am asking you to help me
Thanks in advance
Paolo
Corrupted /efs partition on GT-N7000 causing bootloop
PaoloUrsini said:
Hi all
My GT-N7000 phone, running (it seems to remember) official Android 4.1.2 some days ago suddenly reset, driving me into the configuration procedure like the first time I switched on.
The following day it reset again, and went into bootloop on Samsung screen. I tried the following:
wipe cache data - no result
reset to factory data - no result
flash via Odin the N7000XXLT9_N7000ITVLT3_ITV Kernel - no result
When I went into recovery mode before reflashing kernel, I got the "can't mount /efs" error. After reflashing kernel, I installed PhilZ recoverty with Aroma, and discovered that the EFS folder is here, but it is EMPTY, and in fact I can't mount it even in PhilZ.
Another strange thing is that all my custom data are still on the telephone, despite the factory reset I have done.
I have searched a lot, but I can't find a way to solve my problem so I am asking you to help me
Thanks in advance
Paolo
Click to expand...
Click to collapse
Any help?
The only things I found on internet are two tools that assert to rebuild your EFS nv_data.bin file (RIFF box and Zx3 box), but I don't want to spend money because the /EFS get corrupted by itself, without any attempt to flash or modding or whatever else.
I think that reflashing kernel will not solve my problem, because (I think) the information are hardware related, and not software related. If needed, I am able to manually change the file reflecting the IMEI and S/N on my cell box, but I need a generic file and some references about positions...
Please guys help me... even if you have only bad news
Thanks in advance
Paolo
Was you phone rooted with a custom recovery before the issue started? Check in the clockworkmod folder in internal storage for efs backups like efs.img...
nokiamodeln91 said:
Was you phone rooted with a custom recovery before the issue started? Check in the clockworkmod folder in internal storage for efs backups like efs.img...
Click to expand...
Click to collapse
nokiamodeln91, thank you for the reply.
Unfortunately not, my phone wasn't rooted before the issue, and, strange enough, I didn't do anything particular on the device other than calling and browsing...
Now I installed PhilZ and have a complete backup, perhaps it's later
PaoloUrsini said:
nokiamodeln91, thank you for the reply.
Unfortunately not, my phone wasn't rooted before the issue, and, strange enough, I didn't do anything particular on the device other than calling and browsing...
Now I installed PhilZ and have a complete backup, perhaps it's later
Click to expand...
Click to collapse
Hi, friend of mine ask for help yesterday with his N7000 and he has the same problem as yrs.
I rooted the phone to have a look at the efs folder and it was empty.
As the factorymode was in OFF, I thought of creating an imei folder with root explore, lo and behold as soon as i saved it it received an a sms message.
Iopen the folder and there were the nv.data folder there.
Baseband was restored but the imei was a generic one 00000049 with the serial number at 0000000 but the consolation was he is able to use the phone normally with all services from telco and even package data was working.
My friend was so happy that he was able to use the phone and was willing to live with it not wanting me to try any further.
So maybe you can try this to get the phine working and like my friend live with it haha.
One more thing if ut works for u save the efs folder and try n restore it.I dont have the chance to try as my friend dont want to bugger it agian.
Also if you swich off the phine u may have to do it again. Cheers
Edit: Phone was in bootloop too, I went to recovery and it cant mount efs.I did a wipe twice and it started up that was how i was able to access the efs folder after rooting it. Cheers
ndmuni said:
Hi, friend of mine ask for help yesterday with his N7000 and he has the same problem as yrs.
I rooted the phone to have a look at the efs folder and it was empty.
As the factorymode was in OFF, I thought of creating an imei folder with root explore, lo and behold as soon as i saved it it received an a sms message.
Iopen the folder and there were the nv.data folder there.
Baseband was restored but the imei was a generic one 00000049 with the serial number at 0000000 but the consolation was he is able to use the phone normally with all services from telco and even package data was working.
My friend was so happy that he was able to use the phone and was willing to live with it not wanting me to try any further.
So maybe you can try this to get the phine working and like my friend live with it haha.
One more thing if ut works for u save the efs folder and try n restore it.I dont have the chance to try as my friend dont want to bugger it agian.
Also if you swich off the phine u may have to do it again. Cheers
Edit: Phone was in bootloop too, I went to recovery and it cant mount efs.I did a wipe twice and it started up that was how i was able to access the efs folder after rooting it. Cheers
Click to expand...
Click to collapse
Thank you ndmuni,
I don't understand very well what you did; consider that my phone is in bootloop, so I am not able to read an eventyually SMS, but I can accesso to file system with Aroma tool in PhilZ recoverty tool. Have I to create a special folder under root in my N7000? With what name?
Thank you in advance
Paolo
Hello there.
I have a Huawei P9 (EVA-L09) with an unlocked bootloader and a custom ROM.
Since a few days I started experiencing something completely weird.
Every time I happen to turn off my phone (often only because the phone had gotten quite warm and I want it to cool down then) I then land in the boot animation and get stuck there. After forcefully rebooting the phone from there (about half of an hour) I held the Volume Up key for three seconds during the warning screen and eRecovery told me about the Data Partition to be badly damaged and it would be recommended to recover it.
There are two ways I can do from here (and also did):
First way is to let it recover using eRecovery, connect to my wireless connection, however the phone always tells me that there was a problem getting the package info for my phone. (Does Huawei stopped supporting the P9 eventually?)
The second way is to run TWRP and reinstall the custom ROM (In my case RROS 5.8.5 for my P9) and to never turn my phone off again. However this isn't always possible to keep it on since it also could happen that I'm not at home and my battery suddenly died.
Installing the stock ROM (or a custom ROM based on a stock ROM) however doesn't work. The stock ROM itself simply won't get installed, neither over the dload method or TWRP or fastboot and a custom ROM based on the stock ROM results in having my phone simply getting a black screen when locking it and then I need to reboot it to use it again.
What can I do? Could it be that my flash memory could be corrupted or something could have happened with one of the partitions of the phone?
Greetings.
EDIT: I managed to install a stock firmware using this link right here.
After the stock firmware was installed, doing a factory reset and wiping the cache every problem I mentioned above this edit vanished.