this is my second note 3. first one rooted it tripped knox warrenty, installed philz cwm anf flashed kitkat 4.4.2. everything was great for a few weeks till I done 2 nandroid backups. I tried to move them to pc which was not a problem, but when I came to delete them from internal memory they would not delete I believe due to the write protection enable. so long story short got phone replaced under warrenty even with knox tripped (lomg story). I just flashed kitkt 4.4 and rooted my device and flashed philz cwm, I came to copy my last nandroid backup to internal memory to do a restore and it wont let me. it says this device is no longer connected. but I can go into any other directory and copy it. can somebody plz help????????????
Didn't learn from first time?
shotgun1976 said:
this is my second note 3. first one rooted it tripped knox warrenty, installed philz cwm anf flashed kitkat 4.4.2. everything was great for a few weeks till I done 2 nandroid backups. I tried to move them to pc which was not a problem, but when I came to delete them from internal memory they would not delete I believe due to the write protection enable. so long story short got phone replaced under warrenty even with knox tripped (lomg story). I just flashed kitkt 4.4 and rooted my device and flashed philz cwm, I came to copy my last nandroid backup to internal memory to do a restore and it wont let me. it says this device is no longer connected. but I can go into any other directory and copy it. can somebody plz help????????????
Click to expand...
Click to collapse
If I were you I would do a nandroid backup onto an external SD, that way in case I can't boot and push files into the phone's internal storage, I will always be able to restore from extSD.
You shod use with the best recovery TWRP
really best
sent from my SM-N900
Your asking for trouble!
Your backup is for a different phone,the hardware will have different id's etc.
In short,don't even bother.
So cause i got a new phone even thou its still a note 3 n9005. It has a diffrent id? When i lot titainium backup it says would you like to restore previous phone id. Would that fix it?
Sent from my SM-N9005 using XDA Premium 4 mobile app
Thats an easy fix. I just copy internal memory to pc and recopy everything but my nandroid backups.
Sent from my SM-N9005 using XDA Premium 4 mobile app
shotgun1976 said:
So cause i got a new phone even thou its still a note 3 n9005. It has a diffrent id? When i lot titainium backup it says would you like to restore previous phone id. Would that fix it?
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Never restore Device A's Nandroid on Device B. It will brick.
You can use a Play Store app to extract parts of a Nandroid to your device without bricking.
Thanks nicholaschum for the good advice. What play store app can I use?
Sent from my SM-N9005 using XDA Premium 4 mobile app
shotgun1976 said:
Thanks nicholaschum for the good advice. What play store app can I use?
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
https://play.google.com/store/apps/details?id=com.h3r3t1c.bkrestore
Apps like these...
Thanks bro
Sent from my SM-N9005 using XDA Premium 4 mobile app
Related
Hi all,
I was hoping someone could shed sime light to my situation. I have a rogers S4 and I rooted it via motochopper and it worked fine. Restored all my apps from Titanium backuoband all was well.
This morning my phone then got stuck at the samsung boot screen and I had to wipe data via the stock recovery to get iy working again...
Can anyone tell me why this is happening? This is thr 3rd time this has happened
Sent from my SGH-I337M using Tapatalk 2
My guess would be the titanium backup. As it can mess things up, once in a while.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
linkin275 said:
My guess would be the titanium backup. As it can mess things up, once in a while.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
I would blame TB mess ups more on old data being restored that causes problems, than TB itself.
OP... Are your app backups from a different ROM? If so, then I would try restoring without data. Or fresh app installs.
Sent from my SAMSUNG-SGH-I337 using xda premium
are you restoring system apps? or just user apps? if you are restoring system apps or something like the messaging storage, will normally cause problems in TB.
best to just connect to wifi and download all the apps again from playstore.
What I would do is odin back to stock do not restore anything for a day or 2, and monitor it. If it never does it again, then it was your backup, keep in mind some apps that worked on the G3, may not work on the G4.
Yes, this is Titanium, it happenned to me too, remember that doing that is like copying everything in the C: Program Files of a PC, formating the computer and restoring that folder, it might work, but you might end up in a lot of trouble overtime since the OS installs different part everywhere. Use Carbon aka Helium, its a much cleaner way to go
I was restoring apps (with data) and the backups were from older ROMs I used in my nexus 4. I am currently trying a non-rooted method for a few days and see if this problem reoccurs
Sent from my SGH-I337M using Tapatalk 2
UPDATE: so far so good... My setup is currently unrooted and I haven't had this issue appear. I'm gonna root in a few days and monitor it again
Sent from my SGH-I337M using Tapatalk 2
cool
Hey all,
Rooted on stock firmware, MJ7 via the URDLV instructions and all was fine.
I flashed TWRP and have made a few back ups while trying out my rom that I have built. After my rom not booting, I have restored my nandroid backup.
This had been working fine, until now. My sdcard is no longer writable, I cannot send pictures that are on my sdcard and apps complain about storage problems. I have enough storage and can prove it.
I would appreciate any help that anyone might have with this. I don't want to format my phone/memory/card or anything really if I dont need to.
Thanks,
Matt
mattmanwrx said:
Hey all,
Rooted on stock firmware, MJ7 via the URDLV instructions and all was fine.
I flashed TWRP and have made a few back ups while trying out my rom that I have built. After my rom not booting, I have restored my nandroid backup.
This had been working fine, until now. My sdcard is no longer writable, I cannot send pictures that are on my sdcard and apps complain about storage problems. I have enough storage and can prove it.
I would appreciate any help that anyone might have with this. I don't want to format my phone/memory/card or anything really if I dont need to.
Thanks,
Matt
Click to expand...
Click to collapse
had that on htc one the only thing what worked was formating sd,data,cache then factory reset then it worked
jaythenut said:
had that on htc one the only thing what worked was formating sd,data,cache then factory reset then it worked
Click to expand...
Click to collapse
Darn, not what I wanted to here... but thanks for the info... If no other responses that would have been my final option anyway....
Sent from my SM-N9005 using XDA Premium 4 mobile app
Sorted from this post - http://forum.xda-developers.com/showthread.php?p=49345484
Sent from my SM-N9005 using XDA Premium 4 mobile app
I have a t-mobile g2 d801, I rooted then backed up my efs with freegee then installed nrg ROM. I decided to see if the restore efs would work so I used freegee to restore it. Then I flashed the latest stock rooted ROM and now I'm getting a reboot about 30 seconds after the Os boots a date my imei is gone. Please help
Sent from my SM-P600 using XDA Premium 4 mobile app
I can't give you specific help to fix this, but, I can advise that you make an extra backup of your EFS. Copy it off of your phone if possible. If not, just copy it to a different partition on your phone, so you have more than 1 copy in more than 1 place.
If you attempt to return to stock with T-Mobile flashing tool all the data on your phone will be erased. So moving a copy of the EFS backup off your phone is the first thing you want to do. If you can use ADB with the phone you can get a copy of it off your phone.
After that, I'd wait for someone with specific knowledge of this problem to assist you in fixing it. Assuming the backup of your EFS file is good, you will be able to fix your phone.
DornoDiosMio said:
I can't give you specific help to fix this, but, I can advise that you make an extra backup of your EFS. Copy it off of your phone if possible. If not, just copy it to a different partition on your phone, so you have more than 1 copy in more than 1 place.
If you attempt to return to stock with T-Mobile flashing tool all the data on your phone will be erased. So moving a copy of the EFS backup off your phone is the first thing you want to do. If you can use ADB with the phone you can get a copy of it off your phone.
After that, I'd wait for someone with specific knowledge of this problem to assist you in fixing it. Assuming the backup of your EFS file is good, you will be able to fix your phone.
Click to expand...
Click to collapse
thanks, i think the backup is still there but i dont know where freegee puts it.i am thinking if i can push the freegee apk to the rom i can restore from there, cane someone post a copy of freegee apk? also can someone tell me where freegee puts the backups. thanks
Ok, i found my where my backups are, any help on how to restore them would be great.
Sent from my SM-P600 using XDA Premium 4 mobile app
Freegee doesnt work, all i get is a blank white or black screen and then a reboot when i launch the app
Sent from my SM-P600 using XDA Premium 4 mobile app
JMM2009 said:
Freegee doesnt work, all i get is a blank white or black screen and then a reboot when i launch the app
Sent from my SM-P600 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm in the same boat. I have my efs1 and efs2 img files, but no idea what to do with them. Any help is sincerely appreciated.
Sent from my LG-D800 using Tapatalk
EDIT: Autoprime listed this method for restoring efs
autoprime said:
If flashable zip wasn't created or to manually restore efs img files run the following commands using adb shell while in recovery:
dd if=/sdcard/EFS_Backup/efs1.img of=/dev/block/platform/msm_sdcc.1/by-name/modemst1
dd if=/sdcard/EFS_Backup/efs2.img of=/dev/block/platform/msm_sdcc.1/by-name/modemst2
Click to expand...
Click to collapse
I tried that, but still have "0" as my imei. Perhaps this method could work for someone else in this thread?
freegee doesnt work, then you probably lost root
also try when wifi on
contact freegee maker with log. you may have found a bug.
try rooting again
Sent from my LG-D802 using xda app-developers app
I did not back up my Efs after rooting my note 3. I did it after I installed x-note rom I now wanna try omega rom but reading a few people having problems with bricking there phone! Have I done anything wrong that can cause me any real problems by not backing up the efs files before rooting?
Sent from my SM-N9005 using XDA Premium 4 mobile app
denny1970 said:
I did not back up my Efs after rooting my note 3. I did it after I installed x-note rom I now wanna try omega rom but reading a few people having problems with bricking there phone! Have I done anything wrong that can cause me any real problems by not backing up the efs files before rooting?
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I used this.
http://forum.xda-developers.com/showthread.php?t=2698639
Sent from N9005 NC2-ROMS
Shouldn't be a problem as long as you can still make phone calls and use mobile data. I believe Omega gives you the option to backup EFS partition again. I do it every time I flash a rom so I have the backup.
Make sure you copy it from internal storage to external storage or the PC before doing a wipe as you may loose your EFS backup otherwise...
Hello Guys,
im facing a problem with my i9505,
I've been using Liquidsmooth Rom for some time,
and yesterday i flashed some roms, and now my sim card isn't recognized anymore, aswell my IMEI and Baseband are missing.
I've had that problem before, so flashed stock rom and restored a TWRP Backup containing only my EFS folder.
This has solved my problems in the past, but now nothing happens.
I have a TWRP backup aswell as a copy of the EFS folder.
Has someone else faced the same problem or knows how to fix it?
Thanks in advance.
No one?
Try to restore efs folder manually with root explorer
Sent from my GT-I9500 using XDA Free mobile app
I'm trying right now, but I am confused because the restore with TWRP doesn't do anything to my EFS folder.
Ok, I copied the EFS folder from my microsd back to the phone but nothing changed :crying:
Have you tried flashing back to stock with Odin? I've heard that can sort out IMEI problems and the sorts.
Even if it doesn't it gives you a clean phone to work with, so you can eliminate any rom problems.
I flashed the stock rom, as well as different modems trough odin, but nothing changed. But I'm wondering why the TWRP restore doesn't show any result.
Sent from my Nexus 7 using Tapatalk
I hope you can recover your phone!
Sent from my GT-I9505 using XDA Free mobile app
kingstark666 said:
I hope you can recover your phone!
Sent from my GT-I9505 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks Mate, I'm still trying. If not, I found a service to repair it for 25 Euros but I hope I will be able to do it myself.
Try to Download another stock rom and before flashing it do a full wipe, including formatting data and cache. Something similar happened to me a few days ago. I've flashed a russian rom and problem solved, but I have the i9500 model.
Sent from my GT-I9500 using XDA Free mobile app
I flashed a 4 Part Rom with full wipe already, but nothing changed.
Sent from my Nexus 7 using Tapatalk
K40S said:
I flashed a 4 Part Rom with full wipe already, but nothing changed.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Not sure if this will work, of it you've tried it already, but have you tried a different version of TWRP?
I did actually, but I'm going to try a older version too and see if it works.
Sent from my Nexus 7 using Tapatalk
Ok, tried restoring with TWRP 2.500 and it shows me failed, contrary to TWRP 2.7.
With TWRP until 2.6.3 it shows me failed, 2.63 and 2.7 show me a succesful message.
LOL it just started working again without me doing anything :highfive::laugh: