Gonna cut a long story short, first time poster but long time flasher
I managed last night to accidently over right my .nv_data.bak Backup just after i realised i had accidently deleted the one from the /efs folder, result was either corrupt imei or No service, actually no service either way.
Was in the middle of trying to get it back running (sgs tools reported my backup attempts as ok but were deleated on reboot due to permission probs)
When the 2.2 appeard in kies (hacked reg) so i though whats to lose, froyo got me into this mess to start with.
Ran the update and everything is now working almost perfect!
The one problem i have is Internal SD card apears not mounted? But Camera you name it writes to it no problem, Windows has full access to it.
Steph_1973 said:
Gonna cut a long story short, first time poster but long time flasher
I managed last night to accidently over right my .nv_data.bak Backup just after i realised i had accidently deleted the one from the /efs folder, result was either corrupt imei or No service, actually no service either way.
Was in the middle of trying to get it back running (sgs tools reported my backup attempts as ok but were deleated on reboot due to permission probs)
When the 2.2 appeard in kies (hacked reg) so i though whats to lose, froyo got me into this mess to start with.
Ran the update and everything is now working almost perfect!
The one problem i have is Internal SD card apears not mounted? But Camera you name it writes to it no problem, Windows has full access to it.
Click to expand...
Click to collapse
Seams like you got lucky this time! Remember to be more careful next time
Related
i have followed the guide for rooting sprint hero to a letter
when it tells me to do back up in recovery mode (step 8) i press home button and i get this error Run nandroid-mobile.sh via adb!
i searched and searched this forum for answer to no avail.
so can you please help me with this?
thanks!
try downloading the Fresh Kitchen and attemp to use it to do a backup. I have run into this a couple times and for some reason however the kitchen gets you into the recovery seems to get things to work properly.
The "with Google" phones have issues rooting straight to 1.5.2. Try 1.2.3., then update.
bossyman15 said:
i have followed the guide for rooting sprint hero to a letter
when it tells me to do back up in recovery mode (step 8) i press home button and i get this error Run nandroid-mobile.sh via adb!
i searched and searched this forum for answer to no avail.
so can you please help me with this?
thanks!
Click to expand...
Click to collapse
I ran across this issue recently myself. There was something wrong with my storage card. I manually backed up the storage card, formatted it, then I put the files back. After that, nandroid backup worked like a charm! ...and I have a "with Google" phone. Hope this helps...
Veldetta said:
I ran across this issue recently myself. There was something wrong with my storage card. I manually backed up the storage card, formatted it, then I put the files back. After that, nandroid backup worked like a charm! ...and I have a "with Google" phone. Hope this helps...
Click to expand...
Click to collapse
thanks that worked! expect i had to delete most of my stuff off my SD card.
I've had that a few times. I found that plugging my phone to the charger solves it every time.
I got that error once, and it was because I had renamed my Nandroid backup. Just rename it back to the original, and it'll be ok.
Also confirming that this worked, thanks alot.
Just a theory on why this might not work:
How much space do you have left on your SD cards?
Maybe there is not enough room to expand the zip file while it is restoring it.
bossyman15 said:
i have followed the guide for rooting sprint hero to a letter
when it tells me to do back up in recovery mode (step 8) i press home button and i get this error Run nandroid-mobile.sh via adb!
i searched and searched this forum for answer to no avail.
so can you please help me with this?
thanks!
Click to expand...
Click to collapse
I only got this error once when my sdcard did not have enough space for the backup. I would put money on that being your problem.
theresthatguy said:
I only got this error once when my sdcard did not have enough space for the backup. I would put money on that being your problem.
Click to expand...
Click to collapse
I can confirm that... make a space on your SD card to continue...
I just got this error and freeing up space on the SD card didn't work for me. I formated and everything. Still getting the same error. I am just gonna ruu and start over...
i was getting this error yesterday.fixed it though,the night before i changed the names of the backups...i renamed them back to somewhat the original name n it worked.
Just got this error message. Checked the size of my backups...about 181MB...checked the free space I had...about 101MB. Deleted 3 of the backup files I had to free up space, then it worked. So, for me...it was a space problem.
space problem
I was getting the run nandroid via adb error also... like you said... "not enough space..." that fixed it for me. so simple... thanks
I have the same error message...
My sdcard is empty... i have not a space problem...
I only get the error when my batter is below 40 percent or so and not on the charger. I believe its a safety measure to make sure your phone doesnt die and brick in the process.
I just had this same error, and read through the solutions. None were relevant.
However, I changed my spaces to underscores in my file names and now it works.
Hope this helps someone else. Just make sure everything is in "one word".
I had this issue about an hour ago. I had changed the names of my back ups (So I could remember what the heck they were backing up). I'm fairly certain that changing the name is what caused the issue. I had enough space on my SD card and I even tried plugging it into the charger (as reccommended in previous posts).
Putting underscores instead of spaces fixed this for me. Thank you kingkeld! I'm glad I never ran into this issue sooner, otherwise I would have been screwed (since you only posted this 4 days ago).
all you need to do is plug your phone in and restore
just had that issue and it's a fail safe to ensure no bricking in case your phone dies
well, i got the dreaded "can't mount /dev/block/mmcblk0p1" error, and decided to try some stuff i learned since i had some important photos/videos from a recent trip on there. turns out it worked, and figured i'd share with anyone (although it seems this error is fixed with the latest software). i recovered everything off my phone, totalling to approximate 1.7gig.
flash a adb recovery ROM with SU (can't remember if the SU is necessary, but there are pre-rooted roms out there, i just used one). also make sure all the drivers for the phone are installed on your computer
adb shell
su
echo /dev/block/mmcblk0 > /sys/devices/platform/s3c-usbgadget/gadget/lun1/file
with winhex, open drive. a directory browser will show your file structure, and right click-->recover/copy whichever files you want. i went a step further created an full image so i can send in the phone. now i have a complete backup i can go back too at any time in case i forgot something i needed.
i tried re-flashing this phone with jg8/jh2/jk3/jl2 with different PITS trying to bring it back and nothing. tried force mounting it and some other commands, but in the end, this worked.
somebody should give this a try.
great work
i could've really used this had it been a month ago, before i sent it in and lost everything
hey Ziostilon, when you had your phone fixed last month, did they mail you a new phone, or did you bring it in for repair? these Bell guys are breaking my balls and saying samsun can recover all my data, and i have to send it in for repair for a month
edit: it looks like this worked because the data on the partition is still intact, just the partition table is messed up. i wonder if a program like partition magic can repair the partition in it's current state? it might be something to look into for people without a warranty.
After a ridiculous snafu on Sprint's part involving upgrading my wife's HTC Hero to a Nexus S, which has resulted in a long winded complaint to the BBB concerning Sprint's idiocy, I encountered a problem with my phone. In the upgrade process, the dumbass as the Sprint store decided he needed to deactivate my phone for a few mins to do some voodoo magic (?) and then accidentally reactivated it to the old Hero, rather than my Epic (I was not at the store when this all went down). Needless to say I was unable to reactivate my my phone by updating the profile even, so I spent an hour on the phone with Customer Care trying to get my Epic working again, and SOMEWHERE in that whole process the CWM backup files and the CWM folder the resided in on my SD card were erase. I had done a factory reset right after a backup this morning since the EF02 ROM I was running, which was just the basic deodexed with the screen off animation and overscroll flashed in, would force close every time I tried to go to Settings > About Phone > System Updates. So back on factory EF02 I was and though the System Updates worked I couldn't get the profile to update since the MSID got all messed up. The Customer Care rep had me perform a RTN reset from the dialer, but that is about it, and now all my data is just gone... I'm trying in earnest to recover the back .img files, but am having little success so far (trying TestDisk on my Ubuntu laptop). I took a raw image of the SD card immediately, before trying any sort of recovery efforts, so if anyone has ANY advice, tips, trick, or ideas for me to get my CWM .img files back, I would love you for forever.
cant be much help,
but i recommend you start using titanium backup to backup stuff so u can go from phone to phone
davidrules7778 said:
cant be much help,
but i recommend you start using titanium backup to backup stuff so u can go from phone to phone
Click to expand...
Click to collapse
I figured the backups in CWM would be good enough, but I guess not...
gremlyn1 said:
...so if anyone has ANY advice...
Click to expand...
Click to collapse
Not directly related to solving your problem but will prevent it in the future... Make a backup and/or remove SD card prior to giving to tech (same applies w/ the hard drive in your laptop, ps3, toaster, etc.).
machx0r said:
Not directly related to solving your problem but will prevent it in the future... Make a backup and/or remove SD card prior to giving to tech (same applies w/ the hard drive in your laptop, ps3, toaster, etc.).
Click to expand...
Click to collapse
I had the phone and was walking through this with the Sprint Customer Care rep on the phone, and there was nothing I did that should have had any effect on specifically the CWM directory on the SD card... just doesn't make sense.
Check your LOST.dir folder? perhaps they got corrupted and ended up there?
Sent from my SPH-D700 using XDA Premium App
I use EASEUS Data Recovery Wizard Professional 4.3.6 on HDD & Flash media all the time & have had good luck with it. WinXP I have recovered pics from sdcards out of 3 Epics & a Ton of data from mine when my sdcard got all FUBAR
Sorry to hear that, but wht I do is make 2 nand backups when I do a backup, save both on the phone, and then save those 2 on my pc.
Help support autism awareness,it only takes 2 seconds to help make a difference...
http://picketfenceblogs.com/vote/3616
Sent from MyEF02 using XDAPA...
Hello !
I am feeling really down today after been trying to get my phone working again.
There is a huge problem currently, I am really annoyed that it doesn't work at all.
First thing, my phone won't start after update it just boot loops and never seem to end it.
First thing I noticed /boot, /cache /system and most things are gone, I can load up recovery but nothing more. I have no idea what happened but the whole image folder was wiped and I had to myself put in the CWM recovery.
I can't do an upgrade "again" as it will be stuck @ the unpacking part without starting it at all.
I been trying with 2.3 V2 and with B133(My stock rom I got).
If anyone has a solution that can solve this problem please help out if you could. Also if you are about to tell me get this and that, please most cases I haven't seen any of the Firmware roms in @modaco wiki links work. Means I can't download them, so if you happen to have spare copy please upload it and link it to me. I have been googling and looking through this section twice, nothing really worked out.
Thanks in advance !
If you didn't erase the .cust_backup partition which contain the image folder with all system' s .img files, then maybe it' s damaged. I had some problems with this partition before and when I checked it with windows check disk it repairs it and I had no problems from then. So, try this, and if you still haven' t any file on image folder, you can find the original folder on X5' s forums. Is definately here, but I don't remember where is the link and I don't gonna search it for you. If you cannot find it, you can allways reflash the original rom. If you fix the partition(if this is the problem), I don't think that you'll have problems with update any more.
dancer_69 said:
If you didn't erase the .cust_backup partition which contain the image folder with all system' s .img files, then maybe it' s damaged. I had some problems with this partition before and when I checked it with windows check disk it repairs it and I had no problems from then. So, try this, and if you still haven' t any file on image folder, you can find the original folder on X5' s forums. Is definately here, but I don't remember where is the link and I don't gonna search it for you. If you cannot find it, you can allways reflash the original rom. If you fix the partition(if this is the problem), I don't think that you'll have problems with update any more.
Click to expand...
Click to collapse
Hello, thanks for the reply.
I have no idea about this .cust_backup partition and how I am supposedly to access it via windows. Also the thing you said about fixing partition within Windows, the check disk thing. I am not sure about that part either as I can load CWM and it can read the partitions but they are empty. Also there is nothing in this forums that contains original things, only way for me to fix this if someone have extra copy and can guide me on how and where to place the all needed files. I am pretty sure it's only things that are missing and I can't get a grip out of this.
So to sum up what my problem is.
I did an upgrade from 2.2 to 2.3 with official firmware, it worked out normally but after a reboot my phone became stuck in an endless loop, I can't do anything and it will not I repeat it will not allow me to "re flash" any firmware I tried so far, the 2.3 V2 and B133.
I am begging someone in this forum section, please if you have the knowledge about this problem care to help?
I can't get a refund out the phone warrenty is off and I do not have that much spare money.
Thanks in advance !
If you can get to recovery, wipe cache and data. It should be possible in stock recovery.
The cust partition has all the images for bootloader, recovery etc. You can get to it with the pink screen. Reformatting and then reinserting the images and files could help, but try that when nothing else works.
I can't give you good help via phone, but try wiping data first. Also, try if you can use some other sd card.
Sent from my U8800 using Tapatalk
Blefish said:
If you can get to recovery, wipe cache and data. It should be possible in stock recovery.
The cust partition has all the images for bootloader, recovery etc. You can get to it with the pink screen. Reformatting and then reinserting the images and files could help, but try that when nothing else works.
I can't give you good help via phone, but try wiping data first. Also, try if you can use some other sd card.
Sent from my U8800 using Tapatalk
Click to expand...
Click to collapse
The most common things I have already done, but do enlighten me what this "custom" parition is. Because in windows I do not see such partition I see a removable partition which I have now added a folder called image with these containing files.
http://forum.xda-developers.com/showthread.php?t=1370960
EDIT ** Also regarding to first person who said about Windows partition manager. The thing is I see a lot of partitions and there is no labeling for them, might be because they are ext2/3 or even something else? In anycase I can't do so much I just find it really odd I have many duplicates and I am guessing that must be errors... Because I am seeing the main recovery partition which has no label too... its at 240 MB where 135MB is used. Lastly there is my internal SD card empty and healthy still I can't reach it within Windows if I do not mount it...And can't now without going into the android OS. I Have loads of free space "partitions I don't understand why they are there".
**
Thanks for helping out, it feels not good to have a half dead phone, it's still not solved :'-(
The .cust_backup is the mount point on android for this removable partition with image folder. In windows haven' t this name. I didn't mean to use the windows partition manager, just to use windows explorer, right click on the partition and choose properties, then tools and then check disk. Of course you can use partition manager too, but because as you found there are all no labeled other partitions there and is a bit confused.
As you mentioned, you found the original image folder and you replaced the files. Did you tried to do the update again after that?
Also you can see and the internal sd partiton, but you need linux system. This partition is not fat32, so windows cannot see it.
dancer_69 said:
The .cust_backup is the mount point on android for this removable partition with image folder. In windows haven' t this name. I didn't mean to use the windows partition manager, just to use windows explorer, right click on the partition and choose properties, then tools and then check disk. Of course you can use partition manager too, but because as you found there are all no labeled other partitions there and is a bit confused.
As you mentioned, you found the original image folder and you replaced the files. Did you tried to do the update again after that?
Also you can see and the internal sd partiton, but you need linux system. This partition is not fat32, so windows cannot see it.
Click to expand...
Click to collapse
I have placed all things that I got from here.
http://forum.xda-developers.com/showthread.php?t=1370960
And I can't run the upgrade firmware, it gets stuck at first stage which is to unpack the the update.app thing.
It just stays like that not blinking and frozen.
Did you tried now that you have the original files, to go to recovery mode and wipe data etc?
Also when you try to do the upgrade do you have the device connected with the cable?
I had this problem once and I think that when I disconnected the cable(or maybe wasn' t connected and I connected it, I don't remember well), the proccess bar starts to moving after a while and the upgrade completed successfully.
dancer_69 said:
Did you tried now that you have the original files, to go to recovery mode and wipe data etc?
Also when you try to do the upgrade do you have the device connected with the cable?
I had this problem once and I think that when I disconnected the cable(or maybe wasn' t connected and I connected it, I don't remember well), the proccess bar starts to moving after a while and the upgrade completed successfully.
Click to expand...
Click to collapse
You are not understanding me :-(, I have wiped already millions of times in millions of different ways just to get it work. And no, I don't have the device connrected when I upgrade, it won't work properly then, I have tried to wait for the progress bar to "start" move it won't happen the battery will die, and nothing happened.
I can't go in with normal Recovery mode, can only go in with CWM, the normal recovery mode is really small, I mean only 3mb, while the froyo version is 5mb. Now I am asking if you have the time to upload the image files from 2.3 V2, the ones in forums are for V1. Which I don't know might conflict.
Thanks again for trying to help me out, this is really frustrating to get it to work.
**EDIT**
I worked it out !
I think I understood what you meant, I did as you told I started first with pluggin in the charger forced it to upgrade and now it's upgrading, thank you so much dancer_69. I was going to go tomorrow to buy a new 2nd hand smartphone. But now I can save my money for other things !
**EDIT of EDIT **
I seem to have downgraded to B133, I will try now with B158 2.3 V2 again and hopefully it will work now.
Yes, wasn't clear because I don' t remember what I've done and solve it. But I think that I did it like you discribed too.
Anyway I'm glad that was helpful(kind of)..
And don' t give up so soon with smartphone' s bricks, I've faced brick kind of problems many times and if the device it' s not completely dead, there is something you can do. Maybe need more search or many tries(sometimes the same things) but at the end(and of course If there isn't a hardware problem) device can unbrick.
first of all this is a "google translate" cant spell english. sorry
problems (large) rooting, backup.
I think is crazy. began a few days ago would put a backup made of CWM. made it 10-20 times before, but now the fun starts all goes as normal until the "sys" folder should be written as saying "telefonhel ** tet" is not possible to write "sys" folder .... then freezes the whole phone. going to start but stops at the first botbilden. must then put the phone in download mode, the drive into new ics via odin. Unless otherwise works to move up. do I add something else I'll just when to choose the Language for which locks up the phone. Does anyone know what happened, there may have been something wrong with your memory card or what??????
(when I've added new ics and rooted it, put in tx new rocketrom so the phone works as normal. tried to make a backup of CMW is Axa excellent. but cure me and trying to put it back so obvious the same thing happens.)
hope I have made myself a little understood in all cases.