So my Evo LTE is running 2.13.651.1, and is on what I understand to be the newest HBOOT (1.19). Naturally, I have S-ON as a result. This is my first Android device, and I've had it about a week since switching from an iOS device. I have root and the Teamwin recovery, which I used to backup the phone. I understand this is called a nandroid backup?
I plan to flash Cyanogenmod 10, in fact I already tried once. It resulted in a bootloop, and I restored from the nandroid backup. I have since learned I need to flash the boot.img from CM10 using fastboot, Flash Image GUI, or any other alternative. Once I do this, if I want to go back to Sense 4.1 like I have currently, how would I do so? Once I flash the boot.img from CM10, I won't simply be able to restore to my nandroid from teamwin, will I? I assume that if I tried to restore from the nandroid, due to S-ON I would be unable to write to the boot partition from a recovery utility and I would be left in another bootloop. How can I get a boot.img corresponding to my stock Sense 4.1 rom in the event that I want to revert to stock?
In the folder containing my nandroid backup, I see a file called boot.emmc.win and a boot.emmc.win.md5. I understand what the MD5 is for, but is the boot.emmc.win what I will need to undo the effect of flashing CM10's boot.img? If so, how would I use it (I do not recognize that file extension, and Flash Image GUI does not seem to like it either)? If not, where would I get something that will work?
I've done several searches here and on other forums, but I can't seem to find what I need. If someone has already answered this question, could you simply point me in the direction of that thread?
Thanks in advance,
Kristoffer
I have yet to restore a back up but to avoid any issues I would use dumlock. Install it from twrp advanced menu and reboot, open it in cm and it will backup boot and overwrite it with a temporary recovery, you then reboot and go back to dumlock and restore the back up, then you are free to flash the nandroid backup and reboot
When you reboot, do not boot to recovery, the boot partition has been replaced with a temporary twrp and all you need to do is reboot normally
om4 said:
I would use dumlock. Install it from twrp advanced menu and reboot, open it in cm and it will backup boot and overwrite it with a temporary recovery, you then reboot and go back to dumlock and restore the back up, then you are free to flash the nandroid backup and reboot
Click to expand...
Click to collapse
Once I flash CM and its boot, the boot for my Sense 4.1 will have been overwritten, no? I opened Dumlock in my Sense rom (as I have not yet flashed CM successfully), and it gives me a warning to make a backup of boot PRIOR to using the app, then just under that says the app will make a backup of the boot. If I go ahead and run Dumlock, I'm not entirely sure what is going to happen. It seems that it will move my recovery (TeamWin at the moment) onto the boot partition? If this is the case, why is this something that needs to be done? Does moving the recovery onto the boot partition allow the recovery to write to the boot without S-OFF, thereby allowing a simple restore of the nandroid to replace my rom AND boot at the same time, as if I were restoring with S-OFF? Sorry if I'm not making sense, but I don't really know what I'm talking about here, and thats the only thing that makes sense to me.
I see a button in Dumlock that says "restore original boot." If I install CM and the CM boot, will pushing this "restore original boot" button give me back the boot setup for the stock Sense rom? If it does, then I could just push that button, let it do its thing, and then restore my Sense nandroid with my recovery, right?
Thanks for your help, and quick response.
Install HTC dumlock
Open the app and back up boot
Once back up is successful, press execute
Once the phone restarts it will only boot to twrp, you then go to dumlock menu again and restore boot
Now flash a Rom or restore back up and reboot
Sorry to sound ignorant, but will this method will restore the stock boot regardless of what rom/boot combination I'm currently running? Or is this creating a backup of the currently installed boot, and saving it somewhere for future use? Specifically, do I want to follow this procedure before I upgrade to CM so I have a backup of the current boot, or is this something I want to do if/when I want to go back from CM to Sense that will magically put the boot back how it was from the factory?
Yes, its a workaround that gives access to boot partition and will let you flash normally, I would only use it for stuff like nandroids rather normally flashing because it writes to boot 3 times. It's a lot of unnecessary wear and tear
Awesome, thanks alot for your help. I'm excited to go and try my CM10 rom, now I know how to get back to stock if I don't like it.
Thanks again,
Kristoffer
Hmm. Now I don't know what I've screwed up. I flashed the boot.img from the CM10 zip using Flash Image GUI, then rebooted to recovery and wiped the System partition and cleared dalvik/cache. Then I flashed the CM10 zip using twrp, cleared dalvik/cache, and rebooted. Now, I'm stuck at the CM boot animation again, just like last time. This does not seem terribly complicated, and I don't know what I've done wrong.
I understand twrp cannot flash the boot due to S-ON, but I thought flashing the boot from inside my Sense rom using Flash Image GUI would fix the problem. I restored the Sense nandroid like before, rebooted, and then I got the Recovery boot logo (htc logo, with red text underneath). After maybe a minute, that went away, and I got a Sprint logo and then the normal boot screen with only an HTC logo. The phone then restarted, and this process repeated several times. So, apparently whatever I did to the boot sector with Flash Image GUI wreaked whatever was there before, and failed to replace it with something that would play nice with CM.
A factory reset won't fix the boot, will it? All it will do is overwrite my system partition and internal sd with the default files, and I still won't be able to boot. Any idea what I've screwed up, and how I can fix it?
EDIT:
I reflashed the CM10 zip, and it still gets stuck at the CM boot logo (spinning blue thing). What are the chances my CM10 download is corrupt? Is it worth trying to redownload it, reflash boot with fastboot, then move the new zip to the phone and flash that?
What version of twrp are you using, some people have had issues with the older 2.1.8
Ok, progress. I'm on twrp 2.2.1. I wiped everything again (wiped cache and dalvik, Factory Reset, and then wiped System) and reflashed CM10. It booted this time, so I assume the boot partition is fine. Apparently I'm the retard that can't understand a point-and-click system and follow simple directions
Once it boots, however, I instantly see an error "Unfortunately, the process com.android.phone has stopped." Once I click Ok, the error will either pop back up immediately, or wait for an indefinite period and them come back. Possibly this is the result of the CM10 release not being entirely stable as of yet, I don't know.
But thanks again, your help and your fantastic Don't Panic post together fixed the problem. I think I can figure out what is going on with this error popup and fix it. So long as I have voice service in the interim, which I do, all is well in the world.
It's normal, it pops up when you lose signal, its a bug but its technically a feature. If the phone loses signal, normally android is supposed to prompt you so you are aware. I think its for debugging purposes, normally this is disabled. Not sure if its really a bug in cm or they just haven't gotten around to disabling it, but its normal. It's not a real priority either since it doesn't adversly affect the phone
Hmm. This just gets better and better. So CM10 ran nicely for awhile, then last night I rebooted the phone and the internal SD card failed to mount. Both twrp and the actual OS cannot get it to mount properly. Is this something I broke, or does it sometimes occur at random? I read the following, but I don't quite know where to go with it.
om4 said:
You're card is beyond a simple reformat, the physical address linking the card and or entire card is corrupt. Don't panic, you have to start clean. Back up the info on you external or remove it, make sure you have a ROM available on your PC. Go into recovery and repartition your phone, this will wipe all memory. You then load up a working ROM (a bad back up may be responsible or just reintroduce the problem), after you have flashed the ROM (HBOOT 1.15+ must fastboot kernel, unless S-OFF) go ahead and boot into android and restore your apps.
Click to expand...
Click to collapse
Repartitioning seems simple enough; twrp> advanced >partition SD card>swipe (leaving all settings default).
After that, I can flash the new rom and boot using fastboot from my PC, right? I'm confident that my nandroid of the stock rom is clean, because I didn't develop this problem until after I had been using CM10 for awhile. Could I use fastboot to flash the boot, data, and system from the nandroid, and be good to go? If not, is the most current file avalible to download at http://stockroms.net/file/HTCEvo4GLTE/RUU? the appropriate file I would need to restore the phone to its stock unrooted state.?
Also, none of my nandroid files have a .img file extension. Is this normal? It has the normal .md5 files, but everything else has a .win extention. I've never heard of this one. My boot, for example, seems to be backed up as boot.emmc.win, with a boot.emmc.win.md5 corresponding to it. Cache, data, and system backups are named <option>.ext4.win. Does ext4 has something to do with the filesystem of the backed up partition? If this is the case, what is a .emmc? Can I flash these files with their strange (to me, at least) extensions using fastboot as if they were all .img files?
I can't imagine any of this is really as complicated as it seems. I've used a PC and a jailbroken iDevice extensively, and never managed to break something I couldn't fix. I guess Android just doesn't like me, or something.
Thanks again for all your help.
EDIT:
Apparently physically removing the external SD from the phone allowed me to mount the internal SD as a USB device. The phone still refused to allow me to read/write data to the memory, but somehow managed to allow my PC to see it. I formatted the internal SD to fat32 (one of the limited options) using Windows, and rebooted the phone to recovery. Now, it suddenly can detect its internal SD. I was able to wipe everything, and restore my Cyanogen backup and the SD card now works again. Weird...
Since I didn't have to repartition anything, was the "physical address linking the card and or entire card" corrupt, or did I have some other issue? Also, I'm still curious about my above question pertaining to file extensions and restoring a nandroid via fastboot.
Related
I flashed a ROM (InfectedROM) all was working and the phone was up and running until the phone crashed. The phone then went into an endless reboot so I booted into recovery (TWRP) and I restored the nandroid backup I made before I started, but now it goes to the HTC splash with the white background and won't do anything else.
[Edit]
Well I managed to kinda fix the problem. I booted into recovery and selected wipe all data (Factory reset), then I re-flashed InfectedROM and managed to get the phone to boot. Still can't understand why my nandroid backup don't work to make the phone boot.
I would like to revert back to the stock ROM but being able to use my phone is better than not...
My Device:
hboot: 1.5
Unlocked via HTC's method
trm96 said:
I flashed a ROM (InfectedROM) all was working and the phone was up and running until the phone crashed. The phone then went into an endless reboot so I booted into recovery (TWRP) and I restored the nandroid backup I made before I started, but now it goes to the HTC splash with the white background and won't do anything else.
[Edit]
Well I managed to kinda fix the problem. I booted into recovery and selected wipe all data (Factory reset), then I re-flashed InfectedROM and managed to get the phone to boot. Still can't understand why my nandroid backup don't work to make the phone boot.
I would like to revert back to the stock ROM but being able to use my phone is better than not...
My Device:
hboot: 1.5
Unlocked via HTC's method
Click to expand...
Click to collapse
Well when you did this did you fastboot boot recovery.img and wipe and then try the nan? Maybe what you need to do.. Also if you make future ones I would fastboot boot recovery.img and then make a nandroid backup..
reaper24 said:
Well when you did this did you fastboot boot recovery.img and wipe and then try the nan? Maybe what you need to do.. Also if you make future ones I would fastboot boot recovery.img and then make a nandroid backup..
Click to expand...
Click to collapse
Does it make a difference if I fastboot boot recovery.img to wipe before I restore my nan backup? To answer you question, no I did not. Here's what I did form the get go:
1) unlocked my bootloader via HTC's unlock method leaving my phone's bootloader unlocked with s-on
2) I after a while decided to try out anther ROM I went with InfectedROM, So I booted into recovery (TWRP) holding the vol down key while pressing the power key and made a nan backup
3) I rebooted my phone using reboot system from TWRP
4) I then rebooted my phone (adb reboot bootloader)
5) I went into fast boot and booted into recovery (fastboot boot recovery.img)
6) I wiped all data then went into install from zip selected the InfectedROM zip on my sdcard
7) Rebooted via recovery's reboot command
Please bear with me while I am a wiz at using the command line in both Linux and Windows I am a noob when it comes to flashing roms and such.
trm96 said:
Does it make a difference if I fastboot boot recovery.img to wipe before I restore my nan backup? To answer you question, no I did not. Here's what I did form the get go:
1) unlocked my bootloader via HTC's unlock method leaving my phone's bootloader unlocked with s-on
2) I after a while decided to try out anther ROM I went with InfectedROM, So I booted into recovery (TWRP) holding the vol down key while pressing the power key and made a nan backup
3) I rebooted my phone using reboot system from TWRP
4) I then rebooted my phone (adb reboot bootloader)
5) I went into fast boot and booted into recovery (fastboot boot recovery.img)
6) I wiped all data then went into install from zip selected the InfectedROM zip on my sdcard
7) Rebooted via recovery's reboot command
Please bear with me while I am a wiz at using the command line in both Linux and Windows I am a noob when it comes to flashing roms and such.
Click to expand...
Click to collapse
So you are on the latest software? If you want something close to stock just to keep things smooth you could try fresh rom or my rom I did both of these are stock based... If you want just the stock look with stock everything go for the stock rooted copies they have in the dev section..
I never made a nandroid copy of my orignal rom since a ruu will always save you when you have to unroot
Does the nandroid back up cause reboots or a hang... Sometimes it takes a good 3 mins for it to move on depends...
When you made the nan backup were you on the 2.08 software or the 2.17 ? Did you update to the 2.17 after you made a backup in the past?
reaper24 said:
So you are on the latest software? If you want something close to stock just to keep things smooth you could try fresh rom or my rom I did both of these are stock based... If you want just the stock look with stock everything go for the stock rooted copies they have in the dev section..
I never made a nandroid copy of my orignal rom since a ruu will always save you when you have to unroot
Does the nandroid back up cause reboots or a hang... Sometimes it takes a good 3 mins for it to move on depends...
When you made the nan backup were you on the 2.08 software or the 2.17 ? Did you update to the 2.17 after you made a backup in the past?
Click to expand...
Click to collapse
I am indeed running the latest software. Thank you I will check out your ROM!
My nandroid back backs up and restores fine but after I reboot after doing a restore the phone does not boot, it just stays on the HTC logo with the white screen.
I did not do any updates after I did my nan backup.
trm96 said:
I am indeed running the latest software. Thank you I will check out your ROM!
My nandroid back backs up and restores fine but after I reboot after doing a restore the phone does not boot, it just stays on the HTC logo with the white screen.
I did not do any updates after I did my nan backup.
Click to expand...
Click to collapse
the boot.img file you have in your restore set up is invalid... i would try to resave your settings agin and then restore from there...boot.img should write to the boot partition if not through recovery then through manual flashing in fastboot
MeanROM is also pretty nice. It is like FreshRom and CleanRom in the way that it is based around Stock, except that it has some pretty beefy features.
So I have a nandroid backup i made of my stock install just before going to cm9. Due to the impending time limit of .03 I wanted to get back to stock so I could follow the same instructions to install .04. However, I'm not sure where I can put my nandroid backup that CWM will be able to see it. I dont think CWM can restore from internal memory, so i was thinking hot-swapping another SD with the backup on it, but I wanna make sure thats safe before I do it. Thanks in advance.
1. You don't need to return to stock to flash a new rom. You can just flash right on top of whatever you have installed new (presumably cm9 .03 based on what you've said).
2. Nandroid backups are stored at /mnt/sdcard/clockworkmod/backup/[folderwithbackupinit]
3. Clockworkmod can restore from internal. I suggest flashing clockworkmod to internal if you haven't already. You can use indirect's latest app for this. Again, you can use the same path nomenclature for the backup. Except for internal it will be at /mnt/emmc/clockworkmod/backup.
4. My personal suggestion (and what I am doing this very instant) is download the new version of cm9, make a nandroid backup of your current cm9 setup and then flash the new version. There is no need to do a data wipe as it is simply an update to the same rom. If/when they add the 3.0 kernel to it (or make any other "major" changes) however, it will probably be a good idea to do a data wipe.
Thanks a ton, I was under the impressions that flashing CWM to internal was a no no ATM on the 8gb NT. I have another question, often times when I burn the recovery image to my sdcard and go to boot from it, I get an error to like "Unable to boot-bad boot magic" or something, any clue as to the issue with that? Regardless youre post was a ton of help.
I'm guessing you installed CM9 via the version of cwm from sdcard? If you want to go internal, you can use indirect's new app to flash now, it works with both 8GB and 16GB.
I don't know about that error but it sounds like the image is just bad. I'd suggest reimaging the card. Though, once you have cwm recovery running internal, it will be rather irrelevant.
---------- Post added at 12:24 AM ---------- Previous post was at 12:17 AM ----------
Don't forget to reinstall gapps as well, if you are using them, as they will be gone after flashing the update.
Awesome, internal cwm will take a lot of the hassle out of all this. This is just an app I can run from CM9 right? Or are there some other instructions im missing?
Download the app, check the md5 hash (there are apps on the play store you can get to do this), install the app if the md5 is good, run the app, select flash cwm (probably have to give superuser access) and then you should be able to boot into recovery.
I don't recommend booting to recovery from the app though. I would manually power off, power back on, hold n to get to the menu in cyanoboot then go down to boot recovery in the menu.
Gah, got excited a bit too quick. Got the recovery to flash, appeared fine, when I try to make a nandroid backup CWM tells me it can mount backup path. Didnt get any errors or anything while flashing the recovery, boots into the CWM fine, just can seem to mount the SDCard.
Did you try powering off and accessing recovery manually via cyanoboot?
Actually I'm not on CM9 anymore, tried using the CWM Sdcard to install .04 got stuck in a boot loop so it factory resetted. Rooted using wertz 8gb/16gb card and loaded the flasher apk. Tried accesing CWM by holding Power+N but it doesnt seem to want to boot into CWM. Atleast not without using the flasher app to reboot. Oop, just had to take the SD out and reinsert, herp derp.
So you got into cwm internal then with sd mounted?
Yes CWM appears to be working fine, I just cant seem to access it without using the flasher app to boot to it. Kinda paranoid about trying to install CM9 and being locked out of CWM without using the SDcard and (I guess) starting over. I'm just supposed to hold Power+N from off, then let go of power once the black screen pops up right?
Power off. Power on, hold N when you get to black screen (something like that anyway, I haven't done it like that in a long time though, as I am on cm9).
You should not worry though for cm9. With cm9 comes cyanoboot. When you boot up you will be presented with the option to "hold n for menu." Doing so will bring you to a menu where you can select to boot into "emmc recovery," i.e. the internal recovery.
With that said, as a fail safe, I do personally keep a 2gb micro sdcard with cwm flashed to it ready to use and restore a backup, should I need it.
I tried installing CM9 .04 before using a CWM SDcard and it started bootlooping(though it still gave me access to cyanoboot), thus me being back at stock at all. Even if the install borks again and I get a loop I should still have access to Cyanoboot?
I'm not sure, but I don't believe so.
I would try to reflash and make sure to wipe data/cache.
Tried going back to stock recovery, rebooting, reinstalling CWM, still cant seem to boot into it from power off. If i go into CWM and reset then quickly press power and N then let go of power, it reboots into CWM again. Think I may just try and reinstall CM9.
Yeah it can definitely be a bit finicky. If you were running cm9 as your daily though, I would do as you said and continue to push forward with that. Once you have it working, you won't have to worry about the magic button combo.
I got CM9 .03 installed and working just fine, tested booting into CWM with cyanoboot just to be sure, went perfect. Decided to install .04, and I get bootloops, thinking something that was changed with .04 isnt working atm with the 8gb NT.
Well you'll need .04 as .03 will expire. Have you tried wiping data?
My process was install .03 wipe data/factory reset, checked it worked fine, tried .04 wiped data/factory reset boot loop. Just tried it again without installing gapps just in case and still get resets after the cyanoboot screen. I restored and am back on rooted stock atm.
You should really make a backup of cm9 .03 so you don't have to keep restoring to stock
On that note, I'm not sure. I would follow up in the thread for that rom and see what others with the 8gb say.
You might consider redownloading the new version as you could just have a bad download.
Hi, I recently bought an unlocked HTC One X+ from Mobicity, it didn't have UK/US English installed. In HBOOT it states that it's unlocked at the top of the screen.
I then took a full backup that is still on the SD card (as well as a copy on my pc), and then installed OrDroid 3.2.1 - this completed successfully but when I rebooted it just hung at the white HTC logo screen.
I left it there for ages, no joy - everytime I'd reboot same thing. I went into CWM Recovery and restored the backup I previously took. This completed successfully but now when I reboot it just keeps going back into CWM Recovyer (5.8.4.0).
I tried using Hasoon2000's utility and this will flash CWM to a later version (6.0.2.7?) and I then retry the restore but upon reboot, it goes back into the previous version of CWM?
I've searched the forums for an Asia RUU/rom but the links to external sites aren't working any more, basically, I'm stuffed - I'll keep trawling through these forums but I could really do with some clear idea of how to fix this?
Thanks very much...
Make sure you're manually flashing the correct boot.img for your rom (this will need to be done with the "fastboot flash boot" command). If you ever restore from a backup, you'll also need to flash your old boot.img manually (this can be found in the backup folder).
NasaGeek said:
Make sure you're manually flashing the correct boot.img for your rom (this will need to be done with the "fastboot flash boot" command). If you ever restore from a backup, you'll also need to flash your old boot.img manually (this can be found in the backup folder).
Click to expand...
Click to collapse
Hi, thanks very much for the reply - so there should be the correct boot.img in the backup I took on the phone (that I copied to my pc as a precaution)? What are the correct steps to restore the backup - do I need to flash the boot.img before or after the restore, and then do I need to clear any caches? Basically, I'm a little unclear on the correct order - I thought I'd been good by taking a backup first, but I've spent ages trying to restore it but haven't been successful.
The order is not terribly important. Just boot into the bootloader by rebooting the phone and then holding the volume down button. Once there run the "fastboot flash boot boot.img" command where boot.img is from the backup you made. Then boot into recovery and restore from your backup. You could do a Wipe Data/Factory Reset right before restoring, but I don't think it will make a difference because the restore should put everything the way it was regardless (cache and all).
NasaGeek said:
The order is not terribly important. Just boot into the bootloader by rebooting the phone and then holding the volume down button. Once there run the "fastboot flash boot boot.img" command where boot.img is from the backup you made. Then boot into recovery and restore from your backup. You could do a Wipe Data/Factory Reset right before restoring, but I don't think it will make a difference because the restore should put everything the way it was regardless (cache and all).
Click to expand...
Click to collapse
Thanks again, will try that later and let you know how I get on!
NasaGeek said:
The order is not terribly important. Just boot into the bootloader by rebooting the phone and then holding the volume down button. Once there run the "fastboot flash boot boot.img" command where boot.img is from the backup you made. Then boot into recovery and restore from your backup. You could do a Wipe Data/Factory Reset right before restoring, but I don't think it will make a difference because the restore should put everything the way it was regardless (cache and all).
Click to expand...
Click to collapse
:laugh::good:
It's easy when you know what you're doing - I cannot thank you enough NasaGeek, that worked perfectly and now I don't have an irate wife any more!!!!! ARGH!! :silly: Anyway, thanks very much for that info - I flashed the boot.img that was in the backup folder, restored my backup and now have a working phone again!
I accidentally formatted my internal SD card with TWRP instead of factory reseting. I can get into recovery, but loading any ROM hangs at the loading screen. For awhile, TWRP was asking for a password, and then somehow I hit the magic combination of things to make that stop happening. I adb pushed an updated TWRP and reinstalling various ROMs.
All this started from trying to install Hyperdrive RLS8. I was running RLS7 fine, went for a clean install, spaced out and formatted the phone, flashed the ROM, and had a whole slew of stability problems. Things would randomly crash instantly, booted only 50% of the time, when it did, installing things would break it, tried various things to fix it, fixing permissions and wiping cache's and such, and results were unpredictable. Kept re-formatting and reflashing with different options until I finally realized that I was formatting it and that's probably what the whole problem was.
Currently I can't boot into a ROM, it hangs on the boot animation. I tried another clean install with RLS7, and the same thing happens. I'm assuming that I need to get back to stock somehow, but I'm not sure how. Odin has always confused me. I used the all in one tool to root awhile back, and I only used odin to send a kernel tar file. If I download a stock build, it's a zip file... so how can I odin it? Is that what I need to do? I'm imagining at this point that the file structure is messed up and I need to rebuild it somehow. I don't have my nandroid backup on this computer, so I haven't tried that yet.
You can either odin stock. It's about a 1.8gb file.
Or you can get a known working ROM on your sd card, factory reset wipe, wipe preload, wipe system, install known working rom+gapps+whatever, wipe cache and wipe dalvik. Reboot. If it sticks at the samsung logo pull the battery and then try to reboot again. Sometimes first boot can take a while. I'd give it 10 minutes before throwing in the towel lol
I bricked my phone by updating Hyperdrive (which I will never (curse words... lots of them) use again. Can someone tell me where to find this stock file? I've been searching long enough to get frustrated and delete several less diplomatic posts, settling with this one.
hey guys, I am a little confused. I just came to the S4 from a galaxy nexus, and I previously used CWM as my recovery option when doing clean install of new ROMS.
When I rooted my S4, I installed TWRP (via goomananger, version 2.5.0.2) because of people saying its much better (on the galaxy nexus forums). However, I keep reading issues of people being stuck in bootloops for TWRP when wiping data.
My question is -- what is this issue? Are you not supposed to clean flash with TWRP?? Or do you only do "factory reset" option in TWRP and not wipe the data?
As I am a little confused on this issue, is it more safe to just install most recent CWM and use that as recovery instead?
Thanks alot
No worries
uberpippi said:
I accidentally formatted my internal SD card with TWRP instead of factory reseting. I can get into recovery, but loading any ROM hangs at the loading screen. For awhile, TWRP was asking for a password, and then somehow I hit the magic combination of things to make that stop happening. I adb pushed an updated TWRP and reinstalling various ROMs.
All this started from trying to install Hyperdrive RLS8. I was running RLS7 fine, went for a clean install, spaced out and formatted the phone, flashed the ROM, and had a whole slew of stability problems. Things would randomly crash instantly, booted only 50% of the time, when it did, installing things would break it, tried various things to fix it, fixing permissions and wiping cache's and such, and results were unpredictable. Kept re-formatting and reflashing with different options until I finally realized that I was formatting it and that's probably what the whole problem was.
Currently I can't boot into a ROM, it hangs on the boot animation. I tried another clean install with RLS7, and the same thing happens. I'm assuming that I need to get back to stock somehow, but I'm not sure how. Odin has always confused me. I used the all in one tool to root awhile back, and I only used odin to send a kernel tar file. If I download a stock build, it's a zip file... so how can I odin it? Is that what I need to do? I'm imagining at this point that the file structure is messed up and I need to rebuild it somehow. I don't have my nandroid backup on this computer, so I haven't tried that yet.
Click to expand...
Click to collapse
Try using odin to flash to stock. Then re-root and install custom recovery and whichever rom. I had a similar problem posted here with no help from the big brains. Had to trial and error with caution on my own. Kinda disappointing since the answer is quite simple once you connect all the dots. Flashing in odin will fix yer internal storage problem because it redefines everything.
cidorov said:
Try using odin to flash to stock. Then re-root and install custom recovery and whichever rom. I had a similar problem posted here with no help from the big brains. Had to trial and error with caution on my own. Kinda disappointing since the answer is quite simple once you connect all the dots. Flashing in odin will fix yer internal storage problem because it redefines everything.
Click to expand...
Click to collapse
uberpippi said:
I accidentally formatted my internal SD card with TWRP instead of factory reseting. I can get into recovery, but loading any ROM hangs at the loading screen. For awhile, TWRP was asking for a password, and then somehow I hit the magic combination of things to make that stop happening. I adb pushed an updated TWRP and reinstalling various ROMs.
All this started from trying to install Hyperdrive RLS8. I was running RLS7 fine, went for a clean install, spaced out and formatted the phone, flashed the ROM, and had a whole slew of stability problems. Things would randomly crash instantly, booted only 50% of the time, when it did, installing things would break it, tried various things to fix it, fixing permissions and wiping cache's and such, and results were unpredictable. Kept re-formatting and reflashing with different options until I finally realized that I was formatting it and that's probably what the whole problem was.
Currently I can't boot into a ROM, it hangs on the boot animation. I tried another clean install with RLS7, and the same thing happens. I'm assuming that I need to get back to stock somehow, but I'm not sure how. Odin has always confused me. I used the all in one tool to root awhile back, and I only used odin to send a kernel tar file. If I download a stock build, it's a zip file... so how can I odin it? Is that what I need to do? I'm imagining at this point that the file structure is messed up and I need to rebuild it somehow. I don't have my nandroid backup on this computer, so I haven't tried that yet.
Click to expand...
Click to collapse
Yes this would probably be your best bet. I wouldn't say the answer "is quite simple when you connect the dots" though, because with that logic there would be no PC problems, you would just connect the dots and format the harddrive and Windows will redefine everything else for you!
But back to seriousness, you have to download a stock factory image and its actually a tar.md5 file and not a .zip because you cant flash zips through odin. The stock factory images can be found in the development section, and they are usually quite large files (2gb+ when extracted!) and you will have to download odin and make sure you have the latest usb drivers from samsung. Then its pretty straight forward, The threads in the development section have guides for how to use odin. The stock image contains all the partitions within in it and will effectively repartition your device when you flash it so no need to use a pit file.
Surge1223 said:
Yes this would probably be your best bet. I wouldn't say the answer "is quite simple when you connect the dots" though, because with that logic there would be no PC problems, you would just connect the dots and format the harddrive and Windows will redefine everything else for you!
But back to seriousness, you have to download a stock factory image and its actually a tar.md5 file and not a .zip because you cant flash zips through odin. The stock factory images can be found in the development section, and they are usually quite large files (2gb+ when extracted!) and you will have to download odin and make sure you have the latest usb drivers from samsung. Then its pretty straight forward, The threads in the development section have guides for how to use odin. The stock image contains all the partitions within in it and will effectively repartition your device when you flash it so no need to use a pit file.
Click to expand...
Click to collapse
Just to follow up, that's what I ended up doing. I used the "No-wipe" factory image, odin'd it, re-rooted (I don't know if I had to do that step, but I did), and then loaded my ROM of choice and it works perfectly now. Thanks!
Hello, my phone was running slowly so I decided to go back to a previous backup and run very few apps. I restore a Nandroid backup and when I did the phone told me an update was available, I tried to install it but it just kept restarting to recovery and I had to reboot into System manually and it never applied the update.
Someone told me I needed a stock recovery, I thought Well, since I'm flashing something, why not flash a JB file too? I went and downloaded a JB rom, flashed that and the recovery but it didn't boot (probably because my hboot is 1.20) so I tried a different rom, basically I tried different combinations but somehow nothing seemed to work, and now I can't boot my phone. I've read that you can brick your phone if you wipe the EMMC, I don't remember doing that but I tried so many things that I might have wiped it without noticing. Is there a way to verify the EMMC? I can boot into recovery with fastboot, but when I install any rom, it just doesn't boot, it gets stuck in the first HTC screen with the HTC logo and those red letters I got after rooting (this rom is property of HTC...don't distribute outside without written permission...etc etc).
So, do you think this can be an EMMC problem, or just a kernel problem? I tried flashing the boot.img from my Nandroid backup (actually it was called boot.emmc.win but I renamed it to boot.img following some instructions I found online) but even with the Nandroid backup that worked before the phone would not start.
If this is indeed an EMMC problem, is there a way to fix it?
Thank you very much.
You also restored your nandroid backup from stock? As your hboot is 1.20 (which is quite old btw), you cannot flash JB kernels to boot partition so JB ROMs won't work without a workaround. So try to completely restore your stock nandroid backup or else you could try running a RUU if your CID is compatible.
dansou901 said:
You also restored your nandroid backup from stock? As your hboot is 1.20 (which is quite old btw), you cannot flash JB kernels to boot partition so JB ROMs won't work without a workaround. So try to completely restore your stock nandroid backup or else you could try running a RUU if your CID is compatible.
Click to expand...
Click to collapse
Yes I read that you need at least hboot 1.25 to flash JB, that's why after flashing JB and seeing it wasn't starting, I tried to go back to my old ICS backup, but none of them work now, I have a Nandroid backup that was working before,here's what I'm trying to do:
1. Flash my old boot.emmc.win changing the name to boot.img and running "fastboot flash boot boot.img"
2. boot into TWRP-2.4.3.0 and do a Factory Reset, followed by a Restore of my backup, which restores System, Data and Boot, and gives me a "Restore Complete - Successful" message.
3. Install SuperSU right before rebooting
4. Reboot
After that the phone just gets stuck on the first HTC screen, the one with the red letters. I don't know much about android, but I think I'm following all the steps correctly, to restore my old Nandroid backup. Or am I doing something wrong?
My CID is ORANG309, I got a 4.0.1 RUU (at least that's what the person said) and I'm going to try to recover that one. It's not a ZIP file, it's a folder with files inside, so i'll probably have to restore it as a normal Nandroid.
Try flashing the system partition as well before restoring your backup.
dansou901 said:
Try flashing the system partition as well before restoring your backup.
Click to expand...
Click to collapse
You mean formatting the /system partition? I try that too, but it doesn't seem to work. Now that I was into TWRP, I saw the Wipe buttons and there is one called "Wipe internal storage" that I might have pressed before, it kinda rings a bell. So assuming I did press it, does that wipe the EMMC? Is there a way to recover it?
I've been trying to flash using Dumlock because it doesn't seem to work from the normal recovery. Here's then what I do.
1. Boot into normal TWRP recovery.
2. Click Advanced -> HTC Dumlock
3. Inside, I click "Reflash recovery" which supposedly reflashes the recovery into boot.
3. Tap "Reboot" and "System". This should reboot into the Recovery in the boot partition, but it gets stuck in a reboot loop.
So I can't boot into the recovery that should be in the boot part. And now when I enter into normal recovery, whenever I restore a Nandroid, right after doing it if I choose "Reboot", it says "No OS Installed!"
camilou said:
I've been trying to flash using Dumlock because it doesn't seem to work from the normal recovery. Here's then what I do.
1. Boot into normal TWRP recovery.
2. Click Advanced -> HTC Dumlock
3. Inside, I click "Reflash recovery" which supposedly reflashes the recovery into boot.
3. Tap "Reboot" and "System". This should reboot into the Recovery in the boot partition, but it gets stuck in a reboot loop.
So I can't boot into the recovery that should be in the boot part. And now when I enter into normal recovery, whenever I restore a Nandroid, right after doing it if I choose "Reboot", it says "No OS Installed!"
Click to expand...
Click to collapse
I don't know wat you are doing but just restore your nandroid backup in recovery and flash boot with fastboot
GtrCraft said:
I don't know wat you are doing but just restore your nandroid backup in recovery and flash boot with fastboot
Click to expand...
Click to collapse
Yeah, that doesn't work. I restore the Nandroid and then when I go to reboot, TWRP says "No OS Installed! Are you sure you wish to reboot"
Update: Using my old Nandroid, I tried this:
fastboot flash boot boot.img
fastboot flash userdata data.img
fastboot flash system system.img
fastboot flash recovery recovery.img
All of them worked, except for the "data", but the phone does not work. Tried doing the same, then flashing data from inside of TWRP recovery, same thing. Phone is stuck on the HTC screen and it doesn't work.
Any ideas?
Tried Dumlock, but it doesn't seem to be writing the Recovery image to boot. I even went and copied a recovery.img file into "/sdcard/twrp/dumlock/<device>/boot/boot.img" and from the TWRP Dumlock menu, tried to "Restore original boot" to see if Dumlock would assume that "boot.img" was the file to flash into the recovery, but when I restart it's just the HTC screen. I'm using TWRP 2.4, and renamed TWRP 2.6 as "boot.img" because the difference in version number would let me know from where was the recovery being booted, but I can't flash into twrp 2.6, aka the fake boot.img.
Tried downloading some RUUs for Spain, but the recovery process failed.
So is it safe to assume that this phone is bricked? I have S-ON, like all other Desire X devices (I think) so can you brick a phone with S-ON? Is there a way to restore the original stock rom? Or at least a way that I can remove the red letters on the boot animation, the ones that say "This build is for development purposes" so that I can take it to the store and hopefully they won't notice that my bootloader is unlocked and maybe they will fix it under the warranty?
thanks
Nevermind, I flashed a ICS Nandroid with the adequate recovery (nexusrecovery) and it works now
ics nandroid
camilou said:
Nevermind, I flashed a ICS Nandroid with the adequate recovery (nexusrecovery) and it works now
Click to expand...
Click to collapse
Are you using htc desire S I'm also stuck at the HTC screen, I did HTCdev unlocking. On the recovery mode it shows unlocked, but I did not notice that S-ON was still on. Where can I find an ICS Nandroid of htc desire s? Thanks
Take a look at the HTC Desire S forum, this one is just for HTC Desire S. if you don't find it, ask there...