Related
I think I need to reflash the android system onto my device, because I uninstalled the wrong files and now so many system features are broken (phone book won't open, fc when I try, gmail app fc on opening email, all user installed keyboards fc, surely many more but this is enough to tell me I need a reflash). Question is, where do my current backups stand? Will I be able to use them?? Please help, thanks.
Pharaoness said:
I think I need to reflash the android system onto my device, because I uninstalled the wrong files and now so many system features are broken (phone book won't open, fc when I try, gmail app fc on opening email, all user installed keyboards fc, surely many more but this is enough to tell me I need a reflash). Question is, where do my current backups stand? Will I be able to use them?? Please help, thanks.
Click to expand...
Click to collapse
Officially, you can't backup anything and all your data will be lost. If you were careful (maybe you did ?), you would use Titanium Backup and xRecovery to do full backups, but now you've messed everything up, it's not even safe to do a backup of a corrupted system...
To reflash, use Pc Companion or SEUS. You can also (not recommended) use custom flashers you can get from developping section...
Hi, thanks for your quick response. I forgot to mention of course I used titanium to fully backup everything, glad to know this can be used. So what do I do, how do I initiate the reflash process???
well, check the top sticky post..
http://forum.xda-developers.com/showthread.php?t=928343
Pierre Duc said:
well, check the top sticky post..
http://forum.xda-developers.com/showthread.php?t=928343
Click to expand...
Click to collapse
LOL you're nasty
Pharaoness said:
Hi, thanks for your quick response. I forgot to mention of course I used titanium to fully backup everything, glad to know this can be used. So what do I do, how do I initiate the reflash process???
Click to expand...
Click to collapse
If you have unistalled any system application,then you do only push that application to phone,after that restore the sytem data by Titenium backup.hope you have schedule backup...
if you have deleted some system files, then reflash ur fone by flash tool....you can only reflash the system.bin.(you need to root again)
hope it will help you......
Thanks everyone, all I had to do was restore my titanium backup (all missing) and I'm good again!!! Sorry I'm a girl that's a little new to this (however I have been following these threads religiously for a while now) so I just kinda freaked out when it all went wrong lol! Thanks
Pharaoness said:
Thanks everyone, all I had to do was restore my titanium backup (all missing) and I'm good again!!! Sorry I'm a girl that's a little new to this (however I have been following these threads religiously for a while now) so I just kinda freaked out when it all went wrong lol! Thanks
Click to expand...
Click to collapse
Don't let a girl do a guy's job but glad you got it fixed
Sent from my X10i using XDA App
Has anyone discovered what's the problem with restoring nanodroid backups with romracer's Recovery?
I see many of us have the same problem, restore work almost fine, it restores the operational system, but does not restore accounts and applications...
Edit:
New information:
I created two new backups as i am trying different ROMs.
I created one for CM7 and tested the restore, everything works perfectly! All apps and accounts...
Also created one for nCrust, this one have the same problem as i reported, the system is there, but it lacks all applications and accounts...
I also noticed that the nanodroid file is 0 bytes for the cases where the error occurs, and 1kb in the case where it worked fine.
Thanks
BTW, i am not using Rom Manager...
I'm not having an issue at all. Did you use romracer's CWM to backup?
Sent from my MB860 using Tapatalk
I used it to backup and restore and it restored everything; apps and accounts included.
LordOfTheSnatch said:
I'm not having an issue at all. Did you use romracer's CWM to backup?
Sent from my MB860 using Tapatalk
Click to expand...
Click to collapse
Yes, i did!
I flashed the last romracer's CWM yesterday, and created the backup next...
There are other users with this problem as well, but i can't find a fix for that anywhere...
luizffgarcia said:
Yes, i did!
I flashed the last romracer's CWM yesterday, and created the backup next...
There are other users with this problem as well, but i can't find a fix for that anywhere...
Click to expand...
Click to collapse
Did you backup webtop (optional)? And upon selecting restore, are you trying to restore webtop?
luizffgarcia said:
Has anyone discovered what's the problem with restoring nanodroid backups with romracer's Recovery?
I see many of us have the same problem, restore work almost fine, it restores the operational system, but does not restore accounts and applications...
Thanks
Click to expand...
Click to collapse
I have backed up and restored twice already with no problems...what issues are you running into?
Swiftks said:
Did you backup webtop (optional)? And upon selecting restore, are you trying to restore webtop?
Click to expand...
Click to collapse
I did not selected webtop when created the backup, and did not selected the webtop upon restore.
I was actualy trying to restore everything i had installed, but i don't use webtop that much, so i decided not to include it...
gpagador said:
I have backed up and restored twice already with no problems...what issues are you running into?
Click to expand...
Click to collapse
The issue is that when i restore the backup, i get a clean Gingerbread, without any of my previously installed applications or accounts!
you aren't doing a wipe cycle after the restore are you?
diedemus said:
you aren't doing a wipe cycle after the restore are you?
Click to expand...
Click to collapse
LOL!!
No
New information:
I created two new backups as i am trying different ROMs.
I created one for CM7 and tested the restore, everything works perfectly! All apps and accounts...
Also created one for nCrust, this one have the same problem as i reported, the system is there, but it lacks all applications and accounts...
I also noticed that the nanodroid file is 0 bytes for the cases where the error occurs, and 1kb in the case where it worked fine.
Any suggestions?
Any ideas? Noone experiencing this issue??
luizffgarcia said:
Also created one for nCrust, this one have the same problem as i reported, the system is there, but it lacks all applications and accounts...
I also noticed that the nanodroid file is 0 bytes for the cases where the error occurs, and 1kb in the case where it worked fine.
Any suggestions?
Click to expand...
Click to collapse
I'm also running piCRUST (v0.7) and romracer's CWM recovery 3.2. I will try this and report back the results.
P.S. would help us if you gave ROM, kernel, and recovery versions, etc. Thanks...
i just now did a backup and restore from within romracer's v3.2 recovery and all my post-piCRUST install tweaks are still in place. WiFi even came right back up with my WPA2 connection as it was before I rebooted for the test.
Of course, if the recovery actually did nothing at all then this behavior is expected.
Seriously, this part of the recovery is probably lifted wholesale from the codebase before romracer got involved, with the exception of being able to choose the external SD card for backup storage. That's what I did this first time. Now for another test, but this time I will backup to the internal card.
BRB...
---------------
No problems either with a backup and restore to/from the internal SD card. I just stepped through the recovery menu and chose all the defaults except for the webtop part.
Looking forward to your report of installed versions OP. When you boot into the recovery the very first line should say:
"CWM-based Recovery v4.0.1.4-atrix3.2"
Is this what you see?
luizffgarcia said:
There are other users with this problem as well, but i can't find a fix for that anywhere...
Click to expand...
Click to collapse
I haven't seen a lot of complaints about this myself, but up until now I've only been monitoring romracer's original post in the dev section. Can you point us to another thread where this is mentioned?
Not doubting you, I'd just like to see if there's some pertinent info about this issue that we're missing. Thanks...
Also, if you are choosing an Advanced Restore, please tell us exactly what options you are selecting, as they are described in the recovery menu itself (e.g. not "accounts", etc.). Thanks again...
Hi,
I've recently upgraded from CheckROM HD 2.0 to 3.1.1 on and every thing seems to be runing great with the exception of the camera.
Whenever I open the camera I get a message pop up that says 'Not enough memory'. This occurs even straight after rebooting or even clearing the memory on the phone.
I have tried reflashing the ROM, installing the camera hack from the kitchen, wiping the cache and anything else I can think of. Anyone else have any ideas?
No such problems myself, i suggest you ask in the CheckRom thread instead of starting a new one.
Can't post in there quite yet
mentasm said:
Can't post in there quite yet
Click to expand...
Click to collapse
why not?
......
Says I need more posts or something.
Anyway, don't think its nessecarily CheckROM now. Flashed back to CRR HD 2.0 and I'm still getting the same error.
Think I might have to do a full wipe which I was hoping to avoid. Time to see how good Sprite Backup and Ti Backup work I guess.
jonny68 said:
why not?
......
Click to expand...
Click to collapse
because he has just 3 posts. you need ten to be allowed to post into development section.
@ thread starter: reflash, maybe with factory reset? it's always good to wipe your device when you switch to another rom.
How embarrasing...
I was just starting to run some backups before doing a full wipe and got a message from Sprite saying it didn't have enough room to store a dropbox backup. Went and cleaned up my last few CWM backups and and some old ROMs and kernels. Just before I jumped into recovery mode I hit the camera and it works fine now. Seems to be that I had run out of space on my internal SD card.
Oh well, problem fixed. Flashing back to 3.1.1 now.
Thanks for the help anyways
mentasm said:
Seems to be that I had run out of space on my internal SD card.
Click to expand...
Click to collapse
mentasm said:
How embarrasing...
Click to expand...
Click to collapse
indeed
hey guys,
My questions is regarding the fast/auto app install on titanium backup, some time ago after flashing a new ROM the Hypershell stopped working, i change ROM quite abit and cant remember which rom (if it was a rom that caused it) it was when the problem started, no matter what i do or which rom i put on my phone i still get the "Fast/Auto app install, NO(Hypershell needed)".
I have unistalled/reinstalled Titanium Backup app, the TB Pro key, Superuser app, Busybox, done wipes, flashed new and different roms but it is always the same, i assumed if i was missing something, a new rom with full wipe would sort it , but i'm obviously wrong, i am obviously missing something but i dont know what, if any of you guys could help it would be much appreciated.
Thanks
SGS3 I9300
Android: 4.2.1
Build: JOP40D.I9300XXUFMB3
BUMP*
gavmac said:
hey guys,
My questions is regarding the fast/auto app install on titanium backup, some time ago after flashing a new ROM the Hypershell stopped working, i change ROM quite abit and cant remember which rom (if it was a rom that caused it) it was when the problem started, no matter what i do or which rom i put on my phone i still get the "Fast/Auto app install, NO(Hypershell needed)".
I have unistalled/reinstalled Titanium Backup app, the TB Pro key, Superuser app, Busybox, done wipes, flashed new and different roms but it is always the same, i assumed if i was missing something, a new rom with full wipe would sort it , but i'm obviously wrong, i am obviously missing something but i dont know what, if any of you guys could help it would be much appreciated.
Thanks
SGS3 I9300
Android: 4.2.1
Build: JOP40D.I9300XXUFMB3
Click to expand...
Click to collapse
Come on someone must have an answer for me.
i had the same problem with another app,
you can check to another sd card ,partition the card ,install the rom ,and install the app,if it work then you must copy your filew of your basic card to the pc,format your card ,partition your card with the "MiniTool Partition Wizard Home Edition",paste your files and thats it .
i hope to work it,
it 's work to me
For anyone suffering from this issue and finding this thread, I'd figured out what to do (once ensuring I have the Pro Key installed properly) go into TB's "Menu->Preferences->App processing mode" and (re-)select "Auto, Direct". Then restart TB, and you're all set!
I think that what happened is I'd tried running TB w/o the ProKey installed and it reset that setting. Since TB saves to your SD Card, it doesn't usually get wiped on a reset, so it'd picked up the old, non-ProKey setting (my TB said "Hypershell YES" and "Fast App install NO (need Hypershell)".
kcrudup said:
For anyone suffering from this issue and finding this thread, I'd figured out what to do (once ensuring I have the Pro Key installed properly) go into TB's "Menu->Preferences->App processing mode" and (re-)select "Auto, Direct". Then restart TB, and you're all set!
I think that what happened is I'd tried running TB w/o the ProKey installed and it reset that setting. Since TB saves to your SD Card, it doesn't usually get wiped on a reset, so it'd picked up the old, non-ProKey setting (my TB said "Hypershell YES" and "Fast App install NO (need Hypershell)".
Click to expand...
Click to collapse
jesus christ thank you. ive been searching for months to get this to work...in the end this is so easy..
:good:
kcrudup said:
For anyone suffering from this issue and finding this thread, I'd figured out what to do (once ensuring I have the Pro Key installed properly) go into TB's "Menu->Preferences->App processing mode" and (re-)select "Auto, Direct". Then restart TB, and you're all set!
I think that what happened is I'd tried running TB w/o the ProKey installed and it reset that setting. Since TB saves to your SD Card, it doesn't usually get wiped on a reset, so it'd picked up the old, non-ProKey setting (my TB said "Hypershell YES" and "Fast App install NO (need Hypershell)".
Click to expand...
Click to collapse
Thank you very much man. it really helped me.
I could not get into that ">App processing mode" setting so I uninstalled the pro key and then reinstalled. TiBu force closed but when I reopened it I had Fast/Auto enabled again.
Hi. I cannot find App Processing Mode in preferences. Do I need the PRO version for Titanium Backup to work properly?
Thank you,
LoriAnn
its pro version feature.
Regionella said:
its pro version feature.
Click to expand...
Click to collapse
I had problem with pro so that's not it. From the last time I fixed it once it was a settings issue I believe....Don't quote me tho.
I have accidentally deleted my TelephonyProvider app and now I can't unlock my SIM card!
I am in urgent need of TelephonyProvider app from a working Huawei Mate 10 Lite.
I couldn't find the stock ROM anywhere so I couldn't fix that by myself
I'm using RNE-L01 model Huawei Mate 10 Lite and RNE-L01C432B130(EMUI 5.1, Android 7.0) is the ROM the phone is running.
I'd really appreciate it if someone could help me and send me theirs...
If you want to copy and send me yours, I have to tell you that the full path is /system/priv-app/TelephonyProvider/ and it will require root to get it from there. (And yes I'm probably going to need the whole folder)
Thanks in advance!
UPDATE: Now phone can't detect my SIM card at all and in status, IMEI number stays unknown... I wonder how did that happen as I only touched that particular apk... plus supersu root and xposed(no modules as I started having problems before I could tend to that.)
UPDATE 2: As I've received and restored the TelephonyProvider apk I'd accidentally deleted, all those problems above are now gone! Thanks again @kilroystyx
thesingular said:
I have accidentally deleted my TelephonyProvider app and now I can't unlock my SIM card!
I am in urgent need of TelephonyProvider.apk from a working Huawei Mate 10 Lite.
I couldn't find the stock ROM anywhere so I couldn't fix that by myself
I'm using RNE-L01 model Huawei Mate 10 Lite and RNE-L01C432B130(EMUI 5.1, Android 7.0) is the ROM the phone is running.
I'd really appreciate it if someone could help me and send me theirs...
If you want to copy and send me yours, I have to tell you that the full path is /system/priv-app/TelephonyProvider/TelephonyProvider.apk and it will require root to get it from there.
Thanks in advance!
Click to expand...
Click to collapse
You can try mine, not from same ROM (RNE-L21C432B120) but should work.
Thanks, I'll try that.
Edit: Seems like it didn't work. Thanks for those though.
thesingular said:
Thanks, I'll try that.
Edit: Seems like it didn't work. Thanks for those though.
Click to expand...
Click to collapse
Factory reset
I obviously tried that as well.... But since I've messed up my system partition, factory reset can't do much for me
thesingular said:
I obviously tried that as well.... But since I've messed up my system partition, factory reset can't do much for me
Click to expand...
Click to collapse
How do you messed up system partition? Just be curious
I was restoring a backup apps etc from a Huawei G8 using Titanium backup. But when I restored them, dialer and messaging apps started crashing whenever I opened them. I had obviously restored my call log and sms messages the wrong way. To fix it without a reset, I tried deleting the data I backed up using the very same app and in the process I happened to delete the apk by accident(which is a system app itself).
thesingular said:
I was restoring a backup apps etc from a Huawei G8 using Titanium backup. But when I restored them, dialer and messaging apps started crashing whenever I opened them. I had obviously restored my call log and sms messages the wrong way. To fix it without a reset, I tried deleting the data I backed up using the very same app and in the process I happened to delete the apk by accident(which is a system app itself).
Click to expand...
Click to collapse
Don't understand then why a factory reset could not fix this issue
Because it basically wipes data,cache and dalvik cache partitions. It does NOT touch system partition at all.
thesingular said:
Because it basically wipes data,cache and dalvik cache partitions. It does NOT touch system partition at all.
Click to expand...
Click to collapse
You could maybe ré install original Rom. Couldn't you?
sonydesouza said:
You could maybe ré install original Rom. Couldn't you?
Click to expand...
Click to collapse
I would've done that already if I could find it. However I can't seem to find it on the Internet as even search engines return very few results containing the build number of the ROM and none of them actually have the ROM. I could only find firmware with build RNE-AL00C00B155(Model RNE-AL00) when I searched for huawei mate 10 lite but the model doesn't match mine(RNE-L01).
thesingular said:
I would've done that already if I could find it. However I can't seem to find it on the Internet as even search engines return very few results containing the build number of the ROM and none of them actually have the ROM. I could only find RNE-AL00C00B155 model firmware when I searched for huawei mate 10 lite but the model doesn't match mine(RNE-L01).
Click to expand...
Click to collapse
Hmm ok
Hope someone here can find a way or your original Rom.
Sorry dude. Wasn't very helpful
It's ok, at least you tried
thesingular said:
It's ok, at least you tried
Click to expand...
Click to collapse
This one come from B130, but again from RNE-L21.
kilroystyx said:
This one come from B130, but again from RNE-L21.
Click to expand...
Click to collapse
Thanks again, let me try that
Edit:
YESSSSSSSSSSSSSSS!
This one worked perfectly! My IMEI number shows up again and it can detect and unlock my SIM card!
You, sir have saved me from having to bring my phone to service(and possibly void my warranty - I also happened to somehow lose the unpatched boot.img, instead it always has SuperSU root in it and because of that, I couldn't even lock my bootloader back without making the phone unusable, though unlocking bootloader again solves that issue.) because of the SIM card function I broke within the very first day I bought this phone. I can't thank you enough for that, seriously. I believe the thank you button will not be enough for this but I'll do the only thing I can to express my thanks and click that anyways.
thesingular said:
Thanks again, let me try that
Click to expand...
Click to collapse
Was enough or do you need some more apk's to restore?
kilroystyx said:
Was enough or do you need some more apk's to restore?
Click to expand...
Click to collapse
No, this is the only apk I had accidentally deleted, therefore the only one I needed to restore the functionality. Thank you once again, you're a lifesaver! At least when it comes to my phone's SIM detection, that is.
thesingular said:
Thanks again, let me try that
Edit:
YESSSSSSSSSSSSSSS!
This one worked perfectly! My IMEI number shows up again and it can detect and unlock my SIM card!
You, sir have saved me from having to bring my phone to service(and possibly void my warranty - I also happened to somehow lose the unpatched boot.img, instead it always has SuperSU root in it and because of that, I couldn't even lock my bootloader back without making the phone unusable, though unlocking bootloader again solves that issue.) because of the SIM card function I broke within the very first day I bought this phone. I can't thank you enough for that, seriously. I believe the thank you button will not be enough for this but I'll do the only thing I can to express my thanks and click that anyways.
Click to expand...
Click to collapse
As I thought our models are sharing the same system.
I'm glad that you fix your device
---------- Post added at 00:45 ---------- Previous post was at 00:43 ----------
thesingular said:
No, this is the only apk I had accidentally deleted, therefore the only one I needed to restore the functionality. Thank you once again, you're a lifesaver! At least when it comes to my phone's SIM detection, that is.
Click to expand...
Click to collapse
So, in that case make a TWRP backup, to avoid this kind of issues in the future.
You're welcome
kilroystyx said:
As I thought our models are sharing the same system.
I'm glad that you fix your device
---------- Post added at 00:45 ---------- Previous post was at 00:43 ----------
So, in that case make a TWRP backup, to avoid this kind of issues in the future.
You're welcome
Click to expand...
Click to collapse
The problem with that is, I'm unable to back up the data partition with that. Somehow I'm getting a createTarFork() ended with ERROR:255 on that.
I was able to successfully backup my boot, vendor and system partitions though and all of this happened after the problem has started and before it was solved.
thesingular said:
The problem with that is, I'm unable to back up the data partition with that. Somehow I'm getting a createTarFork() ended with ERROR:255 on that.
I was able to successfully backup my boot, vendor and system partitions though and all of this happened after the problem has started and before it was solved.
Click to expand...
Click to collapse
Because your data partition is encrypted.
Under my signature you can see what I did to manage this issue.
Root with decrypt option and then decrypt data.