Hello everyone,
(Note, I did do a nandroid backup before I did ANYTHING, right after rooting)
I was having some issues with Modaco 1.0 when it was first put out, and like everyone else, got trapped in a reboot loop. Once I saw that the fix was repartitioning to FAT32, I did so, re-flashed the ROM, and I was back in. All was good.
But when 1.1 came out, I really wanted to restore to my backup to start fresh with the new ROM, but it did not work out. When I tried to do so in the recovery console, I got this error - Error: "nandroid-mobile.sh restore" from console! -
What am I supposed to do with that? I went ahead and went through with 1.1, but I am worried I accidentally closed my backdoor at some point. I noticed I lost some things from the basic ROM (such as the default wallpapers, and I had issues with Google Maps), and I am just generally worried something is fishy in there.
Any suggestions?
lorsoblu said:
Hello everyone,
(Note, I did do a nandroid backup before I did ANYTHING, right after rooting)
I was having some issues with Modaco 1.0 when it was first put out, and like everyone else, got trapped in a reboot loop. Once I saw that the fix was repartitioning to FAT32, I did so, re-flashed the ROM, and I was back in. All was good.
But when 1.1 came out, I really wanted to restore to my backup to start fresh with the new ROM, but it did not work out. When I tried to do so in the recovery console, I got this error - Error: "nandroid-mobile.sh restore" from console! -
What am I supposed to do with that? I went ahead and went through with 1.1, but I am worried I accidentally closed my backdoor at some point. I noticed I lost some things from the basic ROM (such as the default wallpapers, and I had issues with Google Maps), and I am just generally worried something is fishy in there.
Any suggestions?
Click to expand...
Click to collapse
Your Nandroid backup was on that SDcard...I don't suppose you saved it before formatting it?
lorsoblu said:
Hello everyone,
(Note, I did do a nandroid backup before I did ANYTHING, right after rooting)
I was having some issues with Modaco 1.0 when it was first put out, and like everyone else, got trapped in a reboot loop. Once I saw that the fix was repartitioning to FAT32, I did so, re-flashed the ROM, and I was back in. All was good.
But when 1.1 came out, I really wanted to restore to my backup to start fresh with the new ROM, but it did not work out. When I tried to do so in the recovery console, I got this error - Error: "nandroid-mobile.sh restore" from console! -
What am I supposed to do with that? I went ahead and went through with 1.1, but I am worried I accidentally closed my backdoor at some point. I noticed I lost some things from the basic ROM (such as the default wallpapers, and I had issues with Google Maps), and I am just generally worried something is fishy in there.
Any suggestions?
Click to expand...
Click to collapse
nah. The happens sometimes. Could be your nandroid backup got corrupted or you are low on battery power. Two most common causes. I would make sure the nandroid backup is on the sd card. if so, simply try plugging it in to a power supply. Let us know if you get it working.
All right... I did not want to admit it but I believe what you said is probably true, and I either corrupted or simply deleted the nandroid backup during all the flashing and repartitioning. I am not seeing it at all when I mount the SD card. It crossed my mind a little too late that I should have pulled it off the card.
What are my options here? On the one hand, it is working fine for now. I had just got the Hero earlier that day (did an exchange due to dead pixels and network issues), so it was not like I lost anything important. Is there an easy way for me to go all the way back, such as flashing the original ROM to the phone, and essentially starting over, like I just opened the box and turned the phone on? That way I can do it right from the very beginning. I just worry that in all my partitioning things got scrambled, and I am not seeing the repercussions from it yet, other than Google Maps.
ftp://xda:[email protected]_Hero_C_Sprint_1.29.651.1_signed_release.exe
if at first you try and fail.... try try agian
Thanks for the link.
Is there some process to this? I mean, I understand the whole update.zip concept of flashing the ROM, but would I also need to do a complete wipe of the SD card to achieve the fresh start I am looking for? Should I partition it at only FAT32, or go ahead and setup the ext2 partition before flashing the original ROM?
lorsoblu said:
Thanks for the link.
Is there some process to this? I mean, I understand the whole update.zip concept of flashing the ROM, but would I also need to do a complete wipe of the SD card to achieve the fresh start I am looking for? Should I partition it at only FAT32, or go ahead and setup the ext2 partition before flashing the original ROM?
Click to expand...
Click to collapse
convert sd card to "SDPART:fat32 only" from custom recovery
et the official RUU wipe your phone
enable USB debugging in settings>applications
reroot your phone using asroot exploit
make any partition changes you want
do a nandroid backup
do a nandroid restore to verify it works
backup on your workstation /sdcard/nandroid
DO NOT TOUCH YOUR SD PARTITION TYPE AT THIS POINT
get to modding in confidence
johnsongrantr said:
convert sd card to "SDPART:fat32 only" from custom recovery
et the official RUU wipe your phone
enable USB debugging in settings>applications
reroot your phone using asroot exploit
make any partition changes you want
do a nandroid backup
do a nandroid restore to verify it works
backup on your workstation /sdcard/nandroid
DO NOT TOUCH YOUR SD PARTITION TYPE AT THIS POINT
get to modding in confidence
Click to expand...
Click to collapse
All right, I am having issues already, from the very beginning.
The RUU ROM .exe will not recognize the HTC Hero. It throws an error 170 at the step where it is trying to pull information from the phone. I think this has something to do with ADB, and the fact the computer did not have the SDK on it. (I originally set up the root with my Mac.)
So, where do I go? I have a Boot Camp partition and another computer both running Windows 7, but my attempts to put the SDK on those computers and then have the phone drivers properly recognized failed on both, and the .exe still cannot complete. Is there something I am missing here, or can I somehow do this on the Mac side? I'll take anything!
Edit: Just cause I can see someone asking, yes, I tried to do this on both of my Windows 7 computers, not the Mac. I recognized that the .exe would not run on OSX pretty quickly.
can you put your phone into fastboot (power+vol down) and get to the point where windows basically sees your phone
what you are looking for is when you type adb devices it shows your hero
fastboot might not work because it's a seperate program but try custom recovery main menu.... enable usb.... or something to that extent
I appologize I don't have my main computer in front of me so I can't tell you EXACTLY where to go
once I do, I'll find which one to hit.... it does work though because I had to do the same thing with my godly preaching of backups :blush:
it's one of the recovery areas though i promise
fastboot will see the hero as the same device as adb will in fastboot
adb will see the hero as recovery device in custom recovery
attempt both of these I'm certain one of these work
if absolutely all else fails.... after you "install" sprint ruu search your computer for rom.zip it should be in your START>RUN>%TEMP% in here somewhere
rename rom.zip it to HERCIMG.ZIP and put it at root of your sd card and boot into hboot and it should automatically find it and press action to flash it
I'll give some of that a shot. I can confirm that adb devices was not showing the hero connected cause I tested that, so I have a feeling correcting that is my primary concern. What happened when I connected the Hero the first time was that it applied the drivers, but it could not find the ADB one, even after I added the SDK. So if anyone knows what that means (Windows 7 doesn't really give you an easy way to point and say, "Hey, I know what you are looking for, it's right here!" apparently, at least I haven't found it) it would be appreciated.
lorsoblu said:
I'll give some of that a shot. I can confirm that adb devices was not showing the hero connected cause I tested that, so I have a feeling correcting that is my primary concern. What happened when I connected the Hero the first time was that it applied the drivers, but it could not find the ADB one, even after I added the SDK. So if anyone knows what that means (Windows 7 doesn't really give you an easy way to point and say, "Hey, I know what you are looking for, it's right here!" apparently, at least I haven't found it) it would be appreciated.
Click to expand...
Click to collapse
go to htc's website and get htc sync under support>sprint hero it has the drivers built in.... should fix driver issue
johnsongrantr said:
go to htc's website and get htc sync under support>sprint hero it has the drivers built in.... should fix driver issue
Click to expand...
Click to collapse
Hey, that did the trick! Currently flashing with the official ROM right now. Thanks for all the help! FINALLY, I will get to do this right!
lorsoblu said:
Hey, that did the trick! Currently flashing with the official ROM right now. Thanks for all the help! FINALLY, I will get to do this right!
Click to expand...
Click to collapse
glad to be of assistance
johnsongrantr said:
glad to be of assistance
Click to expand...
Click to collapse
Actually, I do have one more question.
Following your instructions back on page 1, wouldn't I want to make the nandroid backup BEFORE repartition to fat32+ext2, so I could recover it all the way back to the standard ROM without partition alterations? Or is it necessary for me to repartition before creating a backup?
lorsoblu said:
Actually, I do have one more question.
Following your instructions back on page 1, wouldn't I want to make the nandroid backup BEFORE repartition to fat32+ext2, so I could recover it all the way back to the standard ROM without partition alterations? Or is it necessary for me to repartition before creating a backup?
Click to expand...
Click to collapse
you'd think so.... but from my own experience if you do a backup on a partititon then convert it... it screws with the backup and you can't recover from it.... just in case... do 2 backups.... store the normal fat32 nandroid backup on your workstation (the entire nanddroid folder) and copy it back to sd after you convert it to fat32+ext2 .... you'll see what I'm talking about....
I don't quite understand why it does that... but for me I was only successful in recovering from a partition that I made a backup to not copied to (if that makes any sence)
also if you don't want to experiement yet... just leave it fat32... you can always change it later after you see it working (sorta confidence builder before tinkering)
lorsoblu said:
Actually, I do have one more question.
Following your instructions back on page 1, wouldn't I want to make the nandroid backup BEFORE repartition to fat32+ext2, so I could recover it all the way back to the standard ROM without partition alterations? Or is it necessary for me to repartition before creating a backup?
Click to expand...
Click to collapse
Think about it this way, you do a nandroid backup...it places it on the sdcard.
Then you go and change the format of the sd card (potentially blowing away or corrupting any data on it, including the nandroid backup you just made).
Thus why it's better to do it afterwards (besides, nandroid doesn't back up your sd card, just your phone's OS and such)
solved for me
i had that problem its cuz the back up is brocken get anthoer copy of it if u hav 1 then restore it again it worked for me
Hey guys!
I'm coming to you at the end of a loooong way after trying to upgrade to KitKat.
I started the upgrade to 4.4, on the go, and quite confident. What a mistake ...
The upgrade failed, and my device got bricked. Fortunately, I had the recovery partition. Unfortunately, I destroyed the recovery partition by mistake...
I finally succeed to fix the things, but I have no idea how exactly I did it (I just tried the things as they were coming, messing around with partitions and switching from tutorial to tutorial),
Anyway, I made it.
This was 2 months ago ... then time passed, and today I got a message "no space left on device". Hm, weird. I check and oh damn, my SD card only had 5GB on it ...!!
It looks like I've loaded the *GB version partition scheme at some point ... or just wrongly formatted the partitions ... or I don't know.
I've tried to check using fdisk, but it doesn't help me much.
I also tried some tools like "Partition table" but I still can't find the missing 10GB. it seems like they're just unpartitioned, but not even recognised as it ...
Did anyone ever had this issue? Any process to fix it? Or at least any way to rollback to the original partition scheme.
Many thanks!
Best,
Stop messing with all this crap.
Get the factory images.
Put the phone into fastboot mode and connect to the computer
Your computer needs to have a working fastboot set up. If not fix it.
Run the flash all script include in the factory images. It's the. Bat on Windows and. Sh on osx / Linux.
It fully wipes the phone. Everything gets wiped and flashes the stock images.
If you have anything on the internal storage you want to keep you can remove the - w line from that script and it won't wipe it.
When done you a stock phone with a unlocked bootloader. From there do what you want.. Either run stock. Flash a custom recovery and root or rom etc.
Or just use stock recovery and factory reset. It fix the storage size problem for me. You'll lose everything on your internal though, so make a backup of your pic/music/anything you think important in your phone.
**** it seems like the post subscription didn't work, I've just seen your replies.
Thanks guys, it seems like the right way to do it.
I'll try to do it tonight and let you know the progress.
Cheers!
So I just dropped my Note 3 of 2 weeks on the floor (with a case on it) and although the glass isn't cracked, the LCD and digitizer is definitely junk since its all warped in color and mostly black. Thank the gods I have insurance.
I have it Rooted and Safestrap installed and luckily made a backup before I installed Xposed when all was still well. I'm familar with Clockworkmod and flashing that way but new to Safestrap. What is the best way to get my new phone back to how the dropped one was like? Not sure of what files to copy onto my PC and back onto the new phone once I get a new one. Would it make a difference if the backup is from another phone?
My main concern is getting all my username and passwords out of the OI Safe app so it's the main reason for wanting to flash my old backup to the new phone. Other than that I'm not to worried about the rest of the phone since it's fairly new and didn't have it long enough for lots of pics and getting it set up the way I really wanted it.
Thanks
That should work with the following big caveat: if you were on the MJ7 kernel (or earlier), and the new phone is on MJE, restoring the full nandroid backup probably won't work at all and is not adviseable. (Remember that Safestrap "ROM"s do not replace the stock kernel).
If the two phones are from the identical release, then what I would do is the following:
- Root and install SafeStrap as usual.
- Immediately make a Nandroid of the Stock Slot using Safestrap. Get it copied off the phone someplace safe (and named in a way that you can remember it) too.
- Make a second slot in Safestrap and restore the backup from the previous phone to this alternate/second slot.
( Note if you were using a ton of the userdata partition on the old phone you will need to right-size the 2nd slot when you create it. Of course, if you were a data-pig on the old phone and there is no room for a sufficiently-large 2nd slot, then this method of rescue is not available to you. In this case you could restore the original nandroid backup directly to the stock slot - only if you were 100% positive of the same kernel release being used on both phones - but if something goes wrong here you might be making a trip to Odin to re-flash stock and then going through the rooting process all over again ).
- You can use it this way for a little while if you like to see if things are working, or rescue critical data from individual apps, or perhaps make TiBu backups of individual apps (that can be later restored into a different ROM). If things seem to be going swimmingly, you can certainly repeat this process, restoring to the stock slot and then destroying the alternate/second slot.
Note that there are other means of rescue of individual apps which do not require a full restore; this is because the Nandroid backups are (concatenated) "tar" archives, and with sufficient command-line knowledge, you could manually splice into place the appropriate folders from /data/data/*, /data/app/*, and /data/lib/* for individual market apps you wanted to rescue from the old backups. Essentially you are doing the same thing that TiBu does, but manually using adb with the phone in Safestrap recovery mode and the command line.
I'm not going to document this, as it is too tedious to do so - either you already have the working knowledge to do this or you don't. The only tricky part to it is getting the user/group ownership of the files correct. (The easiest way to do this is to install the app from the market, then record the owner/group information it used for the new install of the app, restore the /data/data/* files into the correct place, and then as root "chown" them to the correct user ID... either that or run the "Fix Permissions" script of the recovery).
good luck
I am about 99% sure it was on MJE, I remeber checking it before rooting and following the newest root method available for the newest kernel among other things such as installing Safestrap and Xposed framework.
I unfortunately don't have any experience using Odin or adb, which is something I should know how to do seeing I'm always tinkering with all the phones I get. I'm pretty good with figuring things out when someone points me in the right direction such as you did by searching and following guides here on xda so I thank you for that! I'll try your idea of rescuing the individual app such as TiBu would do using adb. Or even restoring the ROM into a second slot, grabbing the data I need, then get rid of that rom.
And for anyone else reading this...it's never too early to use TiBu or any other backup app for all your important data. Never expected my brand new phone to break after only 2 weeks of owning it but lesson learned.
Thanks a lot for the help, I'll let you know how things go once my new phone arrives.
I have done, on three S3's now, the same mistake that many have probably done, especially according to all the threads on various sites I have seen. And whatever that mistake is - I still don't know what I have done to cause it - none of the solutions actually work.
I am refering to Bricking my phone, or partially. In my case the phone won't boot properly and will not get past the Samsung logo
The problem I found with all the other threads and solutions is that they all assume:
You can access the phone via a PC, but as you can't boot the PC drivers do not install and it is not recognised, so Odin, and the fantastic Android Toolkit do not work
They are very complicated or even very risky.
And I have yet to find one that works.
I am not an engineer or Android, or any other type of programmer - at all. I simply follow instructions, so whatever I did had to be simple.
So I fixed my S3 and I am sure this will work with ANY device, S3, S4, S5, Sx???? or make. It did assume a second working model and that the phone could at least read a SD Card.
I simply booted my working S3 in to Recovery, in my case TWRP
Made a backup by going in to "Backup" but JUST selected the "BOOT" Partition (I did notice the EFS option too, and that is another problem users have - another day)
"Swipe to Back Up"
I then used "Advanced" and "File Manger" to find the backup and copy it to the SDCard.
May even be able to rename it BOOT IMAGE, but not tried that.
Shut down
I now Booted the faulty S3 in to Recovery
Backed up the Phone as above (I did this to create the BACKUP folder for TWRP): "Backup" selected BOOT partition to backup, "Swip to Back up".
Then used the "File Manager" to find the BACKUP folder, within which is another folder with a long name (4df159e030809f25 (eg)) within which is "THE FAULTY BACKUP", probably called something like "2015-01-30-08--37-18 omni_19300-userdebug4.4.4 KTU...". Take a note of the name of the file or delete it.
Shut Down
Insert the SDCard
Reboot in to Recovery again
Again going in to "Advanced" and "File Manager" find the new backup on the SDCARD and copy it to the location where the faulty backup was/is located. Probably: inside SDCARD - TWRP - BACKUP - 4df159e030809f25 (eg)
Then go into "Restore" again
Select the good file and restore it - "Swipe to Restore". If the file does not appear it is because it is in the wrong location. there is no browse facility in TWRP Restore, sadly.
"Reboot"
All should now reboot in to the OS of your custom ROM.
Hope this helps someone.
Just flash stock rom and start over
I doubt that people have couple of the same devices to recover their s3 that way you described. Why didn't you just flash a clean rom if you can enter recovery?
Restoring backup on different device is maybe some kind of solution but I hope you didn't restore efs also.
If you can't use PC you can still write rom or kernel onto SD card and flash it from there. Of course if there is a custom recovery onboard the faulty device installed. If it enters recovery I suppose you can also run download mode and use Odin instead.
You are clever and recovered your device, but I think this workaround shouldn't be used if there is a chance to make it simply and so called 'classic way' But if it's works than you should be proud of yourself. Good job.
____________________________________________
P3110 / I9300 / I9100 / NEXUS 5 / iPAD2
I had a copy of the ROM on the sdcard and flashed it many times. It would not work. The only way was to build a new boot.
Odin and android tool kit did not work. Tried the stock ROM and that would not load at all even when put on the sdcard.
Sent from my GT-I9300 using XDA Free mobile app
Is anyone else having trouble getting TWRP Recovery to work right? I have literally tried everything with both the L720 models I have owned and I get screwed by TWRP every time... I have the L720-T model right now Running 5.0.1 and both a 64GB and 16GB SD Card. TWRP won't write crap to the 64GB Sandisk SD card... and when I use the 16GB Patriot SD Card, I can write a backup to it, but that's about all I can do...
When I reboot into recovery trying to restore from the backup I have created, the stupid thing just sits there for 15-20 minutes trying to verify the MD5. Finally after that 15-20 minute period, the stupid thing crashes and reboots... I really love TWRP and it worked amazing with my Droid Razr Maxx, but now it appears to be a total waste of space and time... What the crap..... Is anyone else having issues or have any guidance?
I have tried multiple TWRP versions...
2.5.0.0
2.7.0.0 (current)
2.8.7.0
Rooted with....
I should also note that I used KingRoot to root [a crazy Japanese rooting .apk because it was the only one that would work as all other filed for the FreedomPop Firmware, and I actually like it a lot bt dubs because it actually blocks auto start stuff 100% unlike most root tools that say they do, only for you to see it running in the Application Manager, it gives no fukks what the process system or not and says no ]
SD Fix as follows...
I downloaded a program to fix the write permissions, but with my 64GB SD It never would write to sd, so I even went so far as to manually change the platform.xml file myself in root->system->etc->Permissions->platform.xml to change "WRITE_EXTERNAL_STORAGE" to contain sdcard_rw, sdcard_r and media_rw as well as change "WRITE_MEDIA_STORAGE" to contain sdcard_rw and media_rw
I can't do a custom ROM, because FreedomPop just doesn't work as good on any rom other than theirs.
If anyone can help me out, I would love you forever, or if someone can point me away from TWRP with something that works and is easy to backup and restore with, then that works also... I am just tired to getting BURNED by TWRP... I Know Titanium is an option, but I would like something that basically backs it up as a snapshot so that there is no setup crap to deal with later, I can just restore on the go and I am good.
mr.ctt said:
Is anyone else having trouble getting TWRP Recovery to work right? I have literally tried everything with both the L720 models I have owned and I get screwed by TWRP every time... I have the L720-T model right now Running 5.0.1 and both a 64GB and 16GB SD Card. TWRP won't write crap to the 64GB Sandisk SD card... and when I use the 16GB Patriot SD Card, I can write a backup to it, but that's about all I can do...
When I reboot into recovery trying to restore from the backup I have created, the stupid thing just sits there for 15-20 minutes trying to verify the MD5. Finally after that 15-20 minute period, the stupid thing crashes and reboots... I really love TWRP and it worked amazing with my Droid Razr Maxx, but now it appears to be a total waste of space and time... What the crap..... Is anyone else having issues or have any guidance?
I have tried multiple TWRP versions...
2.5.0.0
2.7.0.0 (current)
2.8.7.0
Rooted with....
I should also note that I used KingRoot to root [a crazy Japanese rooting .apk because it was the only one that would work as all other filed for the FreedomPop Firmware, and I actually like it a lot bt dubs because it actually blocks auto start stuff 100% unlike most root tools that say they do, only for you to see it running in the Application Manager, it gives no fukks what the process system or not and says no ]
SD Fix as follows...
I downloaded a program to fix the write permissions, but with my 64GB SD It never would write to sd, so I even went so far as to manually change the platform.xml file myself in root->system->etc->Permissions->platform.xml to change "WRITE_EXTERNAL_STORAGE" to contain sdcard_rw, sdcard_r and media_rw as well as change "WRITE_MEDIA_STORAGE" to contain sdcard_rw and media_rw
I can't do a custom ROM, because FreedomPop just doesn't work as good on any rom other than theirs.
If anyone can help me out, I would love you forever, or if someone can point me away from TWRP with something that works and is easy to backup and restore with, then that works also... I am just tired to getting BURNED by TWRP... I Know Titanium is an option, but I would like something that basically backs it up as a snapshot so that there is no setup crap to deal with later, I can just restore on the go and I am good.
Click to expand...
Click to collapse
Do a factory reset get everything back to pre rooted, then root by flashing SuperSU in twrp, instead of Kingroot
mattzeller said:
Do a factory reset get everything back to pre rooted, then root by flashing SuperSU in twrp, instead of Kingroot
Click to expand...
Click to collapse
I really don't want to do that. Twrp, has permissions and I have never had any Root issues with the KingRoot regarding permissions. It always propts me of any and all requests, and also any problems that may arise, so I am extremely impressed with it. This makes me believe that doing this will not help anything. I also had the same issue on my old L720 using towel root and SuperSU. So again, I don't see how this will do anything for me, other than take away 2-3 hours of my life. If you could give me a little more to go off of as to why you think it is KingRoot, I would consider it, or tell me what you think KingROot ins't doing and how to test that, I would. However, without something to support this suggestion, I am lost.