I have searched this forum completely and every link I find to the stock system image/backup has been taken down or no longer exists.
I have one that I want to restore to factory, currently has AsteroidOS, and like an idiot, I had a nand backup on an old machine that I gave away and has since been reformatted (already attempted data recovery, no luck)
Thank you!
I need it to
jgreever said:
I have searched this forum completely and every link I find to the stock system image/backup has been taken down or no longer exists.
I have one that I want to restore to factory, currently has AsteroidOS, and like an idiot, I had a nand backup on an old machine that I gave away and has since been reformatted (already attempted data recovery, no luck)
Thank you!
Click to expand...
Click to collapse
If you manage to solve this please tell me, thanks!
Related
I was having issues with space and the most recent update. I decided to back absolutely everything up and do a factory reset then put the new files back on. Somehow the reset wiped everything my backups the OS everything. I have no idea how to get the files on the phone to re-flash. Can anyone please help!
clr_photo said:
I was having issues with space and the most recent update. I decided to back absolutely everything up and do a factory reset then put the new files back on. Somehow the reset wiped everything my backups the OS everything. I have no idea how to get the files on the phone to re-flash. Can anyone please help!
Click to expand...
Click to collapse
This is in the wrong section, and your answer could probably be found easily with a simple search. Just fyi for future reference.
You can use odin to flash back to stop, or what I would do is download whatever ROM on your computer and use ADB Push/ADB Wireless and push the ROM to your phone. Then you can flash and viola!
I have the sigh-i747 withe the debloated factory 4.3 rom found on another thread here. However this seems to apply to both cwm recovery and twrp. When I restore a backup it boots to the AT&T screen and stays there. I've tried everything I can think of and no luck. Needless to say after four or five manual restores I'm hesitant to try anything else. I've googled it extensively and only found the problem mentioned once and no answers, lol. Any help would be appreciated.
Thanx
Greetings,
I would have liked to post this questions, where it belongs to, but I'm new to this forum, so I put it here.
Last September I've updated my DHD following the instructions given in the thread mentioned in the headline and everything was fine. Yesterday in the evening, I got the notification to restart using the recovery mode, because something in the context of the superuser should be updated or modified. Because it was not the first time, I just did it. But this time, after rebooting, the device stopped with the HTC bootscreen (green HTC on white background).
After 10 minutes I took out the battery and restarted again. Again I was able to choose recovery mode, but while starting the DHD got stuck with the bootscreen. I decided to wait and just put it aside showing the boot screen, but the result this morning was that the battery is empty and nothing changed.
Does someone know about that issue and what do I need to do to get the device to work again? Why was this update needed in the first place?
Thanks a lot in advance...
im not sure why
but have you tried re-flashing the ROM?
PHOENIX-9 said:
im not sure why
but have you tried re-flashing the ROM?
Click to expand...
Click to collapse
Not yet. I was afraid to loose all data and maybe exchaning a file would also do the job. I mean, the update of the superuser component has changed something and this could be corrected again.
If you don't wipe your data partition (dirty flash) and you flash the exact same ROM, you shouldn't lose data.
KKrittel said:
Not yet. I was afraid to loose all data and maybe exchaning a file would also do the job. I mean, the update of the superuser component has changed something and this could be corrected again.
Click to expand...
Click to collapse
try to back up your ROM
do a clean install..then restore only the data (advanced restore)..wipe dalvik and cashe
if it didnt boot..you can restore your data using titanium backup pro from the CWM back up
PHOENIX-9 said:
try to back up your ROM
do a clean install..then restore only the data (advanced restore)..wipe dalvik and cashe
if it didnt boot..you can restore your data using titanium backup pro from the CWM back up
Click to expand...
Click to collapse
Tried to make a backup, but it recovering did not work. Doesn't matter. I just flashed the same image again, downloaded 'my' apps and restored the status from before the crash.
Nevertheless the same notification showed up, saying that the superuser kernel needs to be updated and I should use 'recovery mode' again. With a bad feeling, I did it again, but this time it works.
So to sum it up: device was useless for some days, restored it with some effort and now it works again. But I need to get prepared for the next time and to think of an app to backup all apps including app-data.
...but as always, this is a task for laaaaater
Thx,
Karl
Hi, Yes you're probably right I shouldn't have messed around without knowing exactly what I'm doing, but any help would be greatly appreciated, I have tried to search for answers on here, but the forum is running so slowly for me at the moment that searches just time out for me.
Anyway, heres what I did - I rooted via ODIN, (CF-Root) and installed CM12.1 - First though, having read about the EFS risks I thought I was covering my ass by downloading EFS Backup from the Play Store - I then backed up my EFS Partition, there were three options, and I assumed the safest option was to leave as default (tar.gz)
So when I saw I'd lost my IMEI after flashing CM, I reinstalled the app, tried to restore - which directed me to an app "Partition back up", which turned its nose up at my tar.gz files! (thanks for that EFS Back up!)
Can anyone tell me what I need to do with the tar.gz files? and do I need all of them?
Thanks in advance.
Partition backup?
Just use the restore options in EFS PRO. What's inside the archive, images or files?
I've just got a file of tar.gz's Radio, CDMA Radio, EFS, and three named M9kefs1 ,2, & 3
I copied them onto my Mac and managed to open them, which gave me .img files too, Which I've tried restoring on the tablet (using Partitions backup app) It reported success but didn't work.
I'll try this EFS Pro, I had seen it mentioned wasn't sure if thats the way to go, thanks!
I've got to ask, why through all of this you didn't use the one tool that would have solved your problem in minutes. TWRP?
ashyx said:
I've got to ask, why through all of this you didn't use the one tool that would have solved your problem in minutes. TWRP?
Click to expand...
Click to collapse
To back up EFS you mean? Quite simply I didn't think I needed to, I thought I'd done it with the EFS Back up app
zoidster said:
To back up EFS you mean? Quite simply I didn't think I needed to, I thought I'd done it with the EFS Back up app
Click to expand...
Click to collapse
There's nothing better than making a full backup in recovery.
It's your one and all get out clause if your device ever doesn't boot or something goes wrong.
Backup apps rely on a Bootable system.
In fact I would suggest you do it before going any further.
I suppose I wasn't too bothered, as coming from an "empty" tablet with no data loss to worry about, I had in my mind that if all went tits up I could simply flash the stock firmware with Odin. (Which I've now done anyway as EFS Pro wouldn't play ball)
Thanks for you help! Lesson learned on Backups.
zoidster said:
I suppose I wasn't too bothered, as coming from an "empty" tablet with no data loss to worry about, I had in my mind that if all went tits up I could simply flash the stock firmware with Odin. (Which I've now done anyway as EFS Pro wouldn't play ball)
Thanks for you help! Lesson learned on Backups.
Click to expand...
Click to collapse
Stock Firmware does not flash the EFS partition.
If it gets wiped or corrupted it's gone and not recoverable.
You have been lucky.
Well flashing the stock firmware back cured the problem, Must be a CM12.1 issue. That would explain why restoring the EFS .imgs didn't work either then.
Hi, I have a similiar issue with my SM-T705. I have the stock rom installed. My IMEI number seems to be broken. It's a generic imei 00499 number. However, I still have my box laying around which it came in. Is there any way to restore it from that?
haimann95 said:
Hi, I have a similiar issue with my SM-T705. I have the stock rom installed. My IMEI number seems to be broken. It's a generic imei 00499 number. However, I still have my box laying around which it came in. Is there any way to restore it from that?
Click to expand...
Click to collapse
Have you been able to resolve it? I am in the same boat as you
einsteino said:
Have you been able to resolve it? I am in the same boat as you
Click to expand...
Click to collapse
There are dozens of us, DOZENS! Seriously though, if you get a method please share.
Hey, my esf partitions seems to be broken after i flashed unofficial Ressurection Remix and later did a restore of my Oxygen OS 3.2.6 backup, now i do not have an IMEI number anymore. I tried clean flashing stock Oxygen OS in many versions but it never worked. I now switched back to Ressurection Remix and my Mac adress is restored, but still no IMEI. I only found solutions for the Oneplus One but i am not sure wich one would work for the OP3..
I really hope someone can help me, otherwise i learned an expensive lesson.
Looked around and not seen anyone who has managed to get their IMEI back on their OP3, maybe worth contacting OP support to see what they can do for you.
Have you tried the Chamelephon app to restore the IMEI?
podge3 said:
Have you tried the Chamelephon app to restore the IMEI?
Click to expand...
Click to collapse
this is why i said search the forums @Huthi
Not sure why you just made another thread when the problem hasn't changed
I did this remote desktop session with an OP support member but he didnt get it to work and told me i should send in my device.
The Chamelephone app throws out an error "processor type is not MediaTek" and when i proceed it doesnt seem to work, any suggestions?
I searched all forums for over 8 hours now and i am very desperate, i dont find a solution working for me.. I made a second thread because i think the first one wasnt specific enough and it can be deleted
I really hope someone knows a brilliant solution, because i am not able to find one anymore, nothing left to google about in my opinion
Btw when i flash Ressurection Remix i have an mac adress, with OOS not, so may this means my efs partition isnt messed up completely?
Huthi said:
I did this remote desktop session with an OP support member but he didnt get it to work and told me i should send in my device.
The Chamelephone app throws out an error "processor type is not MediaTek" and when i proceed it doesnt seem to work, any suggestions?
I searched all forums for over 8 hours now and i am very desperate, i dont find a solution working for me.. I made a second thread because i think the first one wasnt specific enough and it can be deleted
I really hope someone knows a brilliant solution, because i am not able to find one anymore, nothing left to google about in my opinion
Btw when i flash Ressurection Remix i have an mac adress, with OOS not, so may this means my efs partition isnt messed up completely?
Click to expand...
Click to collapse
you said you wiped all partitions except internal storage, so you also wiped the EFS partition, so i doubt there's a way to recover it without restoring a backup.
really can't think of a way to restore it without sending it into OP
You have learned a potentially expensive lesson BEFORE doing anything always backup EFS without fail.
Yea i guess i did
i thought nandroid backsup everything needed to restore a device 100 %
in twrp wipe the esf partition is not shown under advanced wipe so i thought it wont be wiped
the support said the only way may be a hardware exchange, lets bet on how much it will cost, 200€? naw man
Huthi said:
Yea i guess i did
i thought nandroid backsup everything needed to restore a device 100 %
in twrp wipe the esf partition is not shown under advanced wipe so i thought it wont be wiped
the support said the only way may be a hardware exchange, lets bet on how much it will cost, 200€? naw man
Click to expand...
Click to collapse
if you really did wipe your EFS and really don't have a backup, then there's literally no solution but paying up for a HW exchange, man
i dont think i did wipe it because twrp does not seem to have this option right?
yea i hope it does not cost too much
Huthi said:
i dont think i did wipe it because twrp does not seem to have this option right?
yea i hope it does not cost too much
Click to expand...
Click to collapse
someone correct me if i'm wrong, but im pretty sure that the fact that TWRP lets you backup your EFS partition to begin with means it also lets you wipe and restore it.
2x4 said:
someone correct me if i'm wrong, but im pretty sure that the fact that TWRP lets you backup your EFS partition to begin with means it also lets you wipe and restore it.
Click to expand...
Click to collapse
okay, but why doesnt it work after i restored a backup with working esf.. doesnt make sense to me, maybe my recovery is outdated but i dont think so.. no matter what i pay the bill and learned my lesson, if ever one guy reads this thread in a few weeks with the same issue: pay the bill and learn your lesson, backups are important and check twice if your esf is backed up, you will need it sooner than you think
EFS backup!! I need to do it now!! Sorry for the loss OP. Hope you get it fixed.
Sent from my ONEPLUS A3003 using Tapatalk
I don't own this phone yet(have nexus 6p) but I am buying this soon....usually when this happens to me....I reboot to recovery, wipe cache and reboot and all fixed....or flash back to stock and all fixed
Have you tried reflashing the radio/modem?.. That works on Samsungs so might be the go for you.
Huthi said:
okay, but why doesnt it work after i restored a backup with working esf.. doesnt make sense to me, maybe my recovery is outdated but i dont think so.. no matter what i pay the bill and learned my lesson, if ever one guy reads this thread in a few weeks with the same issue: pay the bill and learn your lesson, backups are important and check twice if your esf is backed up, you will need it sooner than you think
Click to expand...
Click to collapse
Getting confused here, did you actually backup the efs partition or not?
What partitions did you tick when you did the TWRP backup?
If you did do a EFS backup are the file sizes for both efs1 and efs2 around 2mb in size?
daleski75 said:
Getting confused here, did you actually backup the efs partition or not?
What partitions did you tick when you did the TWRP backup?
If you did do a EFS backup are the file sizes for both efs1 and efs2 around 2mb in size?
Click to expand...
Click to collapse
No i did not back them up the android sdk way, i only backed up my phone with twrp and i backed up all partitions shown to me except cache (efs was never listed in twrp) and so i restored my whole backup, wich seems like not including efs
No i did not try reflashing modem/radio but i surely do it before sending it in today
Huthi said:
No i did not back them up the android sdk way, i only backed up my phone with twrp and i backed up all partitions shown to me except cache (efs was never listed in twrp) and so i restored my whole backup, wich seems like not including efs
Click to expand...
Click to collapse
What version of twrp did you use? In the latest official version there is an option to back up efs
slonn said:
What version of twrp did you use? In the latest official version there is an option to back up efs
Click to expand...
Click to collapse
That's what's thrown me it definitely shows efs on TWRP 3.0.2-1
daleski75 said:
That's what's thrown me it definitely shows efs on TWRP 3.0.2-1
Click to expand...
Click to collapse
I recall that TWRP 3.0.2-1 had some problems with restoring efs and there was a warning posted on portal some weeks back. You should be regular on portal bro.
http://forum.xda-developers.com/nexus-6p/help/announcement-twrp-3-0-2-1-fatal-bug-t3453119
Edit: I see you're not the op, but still it is potentially dangerous for you too, to use that recovery's efs backing/restoring if you go ahead to help this guy.