Related
I wanted to start this thread so we can a place where everyone who discovers this issue, comes here and posts on what they did, how they managed to recover from it, and what steps they have taken on preventing this from happening.
I've been lurking around and it seems as if it's the users with the gfree method thats it's only happening too.
I wanna keep track how it happens, as the glacier isn't the only one that suffers from this but it's been happening quite often these past few days. Thanks
Please state how it happen, what rom you flashed and or nandroid backup and if you pulled your battery during a flashing, wiping session.
I can confirm that we're not the only ones that this is happening too. G2 users are also having the same exact problem. There seems to be a really good chance of why this is happening because of different emmc chips and or drivers, i'll be looking through irc logs and put out a summary here for all.
And also, check this out. I know our devices varies from the G2 quite a bit, but then again we're using the same rooting method and exploit so it makes sense to check some stuff from there. http://forum.xda-developers.com/showthread.php?p=13234526
I am sorry if I sound like a nood , but I am a noob:© . I used the gfree mathed to root my phone, didn't run into the problem you are discrubing. Mybe I didn't quite get it.
Sent from my HTC Glacier using XDA Premium App
ummm yea.... happened to me today and after trying basically everything (nandroid restore, flash rom via zip, flash official rom via bootloader etc.) nothing worked
It happened when i was using Virtous Fusion and decided to flash back my Cyanogenmod 7 backup. I has the latest clockworkmod 3.0.2.4, Cleared data / cache and ran the restore... after it was done, i rebooted and noticed that it would not go past the Mytouch splash screen... went back to recovery via the vol down + power combo only to be greeted with...
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
Nandroid backups dont flash, zip roms flash (or it seems) but doesnt boot, i get errors when i try to wipe, flashing official rom via bootloader gives me the dreaded FAIL-PU after most steps, so yea... im boned lol
Apparently there is a chance to restore if u got the engineering bootloader but i did not at the time. I did root via gfree since the visionary method refused to gain s-off
I wonder if it has something to do with restoring after clearing data/cache instead of directly restoring... I've never cleared those before a restore and I have never had an issue. let's get some other people in here to test that theory.
kimbernator said:
I wonder if it has something to do with restoring after clearing data/cache instead of directly restoring... I've never cleared those before a restore and I have never had an issue. let's get some other people in here to test that theory.
Click to expand...
Click to collapse
You should be clearing data and cache before restores. There are a lot of things in /data that do not carry over well when changing ROMs. I wonder if it's something to do with ClockworkMod 3.x recoveries.
here you go this is my experience:
http://forum.xda-developers.com/showpost.php?p=13709837&postcount=22
All the users who had this trouble Were rooted with gfree. Any users with the first s-off method?
_ice_ said:
here you go this is my experience:
http://forum.xda-developers.com/showpost.php?p=13709837&postcount=22
Click to expand...
Click to collapse
Sent from my HTC Glacier using XDA App
mike21pr said:
It happened when i was using Virtous Fusion and decided to flash back my Cyanogenmod 7 backup. I has the latest clockworkmod 3.0.2.4, Cleared data / cache and ran the restore...
Click to expand...
Click to collapse
You know you should do a factory reset via the recovery image prior to flashing any new ROM. ESP when coming from a 2.2 ROM to a 2.3 ROM.
I wonder if that is what is causing the problem. The Clockwork ROM Manager doesn't wipe everything the "factory reset" in the recovery image itself.
neidlinger said:
You know you should do a factory reset via the recovery image prior to flashing any new ROM. ESP when coming from a 2.2 ROM to a 2.3 ROM.
I wonder if that is what is causing the problem. The Clockwork ROM Manager doesn't wipe everything the "factory reset" in the recovery image itself.
Click to expand...
Click to collapse
You don't mean do the "factory reset" on the HBOOT screen do you?
So.. going from say a 2.2.1 stock to 2.3.3, do... (through clockworkmod recovery screen NOT ROM MANAGER APP)
1. wipe data/factory reset
2. wipe cache partition
3. wipe dalvik (optional?)
If you don't use Rom mamaher to load your Roms , would you run in to the same problem.?
Sent from my HTC Glacier using XDA Premium App
h22aboi said:
You don't mean do the "factory reset" on the HBOOT screen do you?
So.. going from say a 2.2.1 stock to 2.3.3, do... (through clockworkmod recovery screen NOT ROM MANAGER APP)
1. wipe data/factory reset
2. wipe cache partition
3. wipe dalvik (optional?)
Click to expand...
Click to collapse
Wipe data factory reset is broken in cwm 3.0.2.4 it hangs when it comes to /data or /cache especially if you have a cooked rom flashed before from an amateur developer.
I noticed that /data or /cache sometimes do not mount properly thus leaving behind corrupted files.
So my advice is to use the advanced format menu in cwm.
1. Wipe dalvik
2.mount /cache, wipe /cache
3. Wait for it, then mount /system, wipe /system
4. mount /data and wipe /data <--- last
Also because some roms come w autowipe feature sometimes when it tries to wipe an already wiped partitions then sectors get corrupted. So if the rom has auto wipe feature built in. You do not need to wipe /system or /data
Sent from my HTC Glacier using XDA App
jdkoren said:
You should be clearing data and cache before restores. There are a lot of things in /data that do not carry over well when changing ROMs. I wonder if it's something to do with ClockworkMod 3.x recoveries.
Click to expand...
Click to collapse
Restoring clears those partitions by itself. I've always been taught that it's only necessary to clear those partitions when you install a new rom, but restoring does it all by itself. I've restored probably more than 15 times without any clearing and it works fine.
Also, I didn't use gfree, and I might not if people get these errors when they do.
Yeah, this is my third mytouch, and this is the only one I used gfree on. I remember with my second one I didn't use the gfree method and I flashed and did everything without any of these risks. Im stilling leaning towards the gfree method being the culprit for the recovery errors.
kimbernator said:
Restoring clears those partitions by itself. I've always been taught that it's only necessary to clear those partitions when you install a new rom, but restoring does it all by itself. I've restored probably more than 15 times without any clearing and it works fine.
Also, I didn't use gfree, and I might not if people get these errors when they do.
Click to expand...
Click to collapse
Sent from my HTC Glacier using XDA App
xdviper said:
Yeah, this is my third mytouch, and this is the only one I used gfree on. I remember with my second one I didn't use the gfree method and I flashed and did everything without any of these risks. Im stilling leaning towards the gfree method being the culprit for the recovery errors.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
yes sir, that could be another factor. gfree is mainly for CID unlock and "true root" but thing is true root isn't required... every other rom flashes -.- gfree also alters your dev block partition which can cause issues.
This thing has me a little worried.
I used the gfree method from the CM Wiki for the Glacier. I have s-off and hboot .85, but I am a bit more hestitant now to flash different roms seeing as how many people are having problems. However, I don't like Rom Manager and never use it. I always go through CWR to flash so is that better? And I am on 3.0.0.6.
FYI, according to trueblue_drew he says to do this as far as wiping your stuff on flashing one of his roms...
This is how you should wipe:
Main Recovery Menu:
1. Wipe data / factory reset
2. wipe cache partition
Advanced Recovery Menu:
3. Wipe Dalvik Cache
Mounts and Storage Recovery Menu:
4. Format System
Sent from my HTC Glacier using XDA
I got the fail PU error a week ago. I was on an miui rom and was restoring a backup I had of cm7. When I rebooted after the restore the phone would not load past the splash screen. I booted back into recovery and noticed the E: Can't mount/cache errors. I tried to flash a new rom but when I would reboot it would not go past the splash screen still. That's when I looked up the problem. I then tried to restore with the PD15IMG, but got the fail PU errors. I then read that you need the part7backup on the sd card if you are going to use the PD15IMG. So I did and stilll got the fail PU errors, but this time it was stuck loading the radio. I pulled the battery. Would not even turn on after that.
I too had rooted with the gfree method and had the engineering bootloader.
I called T-mobile to replace the phone since it wouldn't even turn on anymore. Took 2 hours to get them to send a replacement with free shipping. They accidentally sent me 2. Two separate boxes, same shipping number. At least now I have a backup. I already rooted one. I did not use the gfree method this time.
Since it seems to be a gfree problem, should I go to stock and re-root the phone using another method??
tilt4life2 said:
Since it seems to be a gfree problem, should I go to stock and re-root the phone using another method??
Click to expand...
Click to collapse
Well, that's what I'm probably going to end up doing as well. This is my third replacement and the first method to root didn't stick, so I ended up rooting with gfree. I am going to unroot and try rooting with the first method which is here http://theunlockr.com/2010/12/10/how-to-gain-permanent-root-and-s-off-on-the-t-mobile-mytouch-4g-htc-glacier/ but the thing is, if it doesn't stick, we're back at gfree.
Anyone know any G2 users that have/had this problem? We're using the same rooting method so there should be a couple people who faced this.
Alright well I've been reading logs from G2_Root channel from April 26th and so on, and it looks like the G2 has two different types of the emmc chip. Gfree powers off this chip and then initializes the chip again in order to get around the write protection. I remember before we had root access on the G2 (before I traded for a mytouch) I would lurk around the irc channel and read progress. I remember having to get the chip to power on in order to get around the write protection.
Now it looks like while the phone is being used, or booting up and or trying tto read or write from emmc the chip suddenly dies. This is what causes us to get force closes, freezes and not being able to get past the splash screen and also explains the recovery not being able to mount partitions.
We're going to need people to join in the G2 channel preferably ones who still have their defective phones to get some data off it.
Again, this is a very vague summary of what I've been able to read off the irc logs.
Why the G2? Because we're using the same gfree method to root our phones and with our phones dying it makes sense.
I think, they have already ruled out recovery and the Eng hboot to be culprit but this is just too early in the game to determine.
Here's a thread from the G2 side, if anyone still has this problem with their cache not being to mount please check out post #13.
I'll look.around more and see what I find from the G2 side.
http://forum.xda-developers.com/showthread.php?t=1039504
Sent from my HTC Glacier using XDA App
Hi
I got my DS about two months ago and now I finally wanted to get into flashing some of these awesome Sense 3.5 ROMs that I could see in the dev section. So I read about every guide I could find and I hope I don't make a fool of myself in these forums
So these are the steps I took to install the newest Endymion Sense 3.5 ROM (only 2.0 base without 2.1 update):
- Unlocked (not S-OFF'd) my phone's bootloader with the official HTC Bootloader Unlocker, which worked flawlessly
- Installed 4EXT Custom Recovery via fastboot (Version 2.1.0), also worked like a champ
- Downloaded the ROM and pushed it onto the SD card
- Wiped data and cache using 4EXT
- Finally installed the ROM using 4EXT
So I think I followed all the steps necessary, but apparently the phone now seems stuck on the HTC Bootscreen. I know it can sometimes take longer (about 10 minutes?), but I have left the phone for about 20 mins and it still is stuck on the bootscreen (HTC Logo).
I then rebooted into 4ext and wiped the dalvik cache (which I didn't do the first time, just cache and data, which is what the guide said) but it didn't help. And what is a "full wipe" exactly, and how do I do it in 4EXT? Combination of data/cache/dalvik wipe?
So now I'm kind of out of answers and I hope I can count on your experience. Should I flash the ROM again? Try another ROM?
I would be very glad if you could give some advice! Thank you very much. (Can't post in the ROM's thread in the dev section yet, as this is my first post)
Use the format all partitions except SD card option in 4EXT, manual steps I follow always and never had problems -
1) in wipe format menu - wipe data/factory reset
2) wipe cache
3)wipe dalvik cache
4) format system
5) format data
Reboot recovery
6) flash ROM
7) flash add on in any available/required
8) wipe battery stats
Reboot into your new ROM
HappyEmu said:
Hi
I got my DS about two months ago and now I finally wanted to get into flashing some of these awesome Sense 3.5 ROMs that I could see in the dev section. So I read about every guide I could find and I hope I don't make a fool of myself in these forums
So these are the steps I took to install the newest Endymion Sense 3.5 ROM (only 2.0 base without 2.1 update):
- Unlocked (not S-OFF'd) my phone's bootloader with the official HTC Bootloader Unlocker, which worked flawlessly
- Installed 4EXT Custom Recovery via fastboot (Version 2.1.0), also worked like a champ
- Downloaded the ROM and pushed it onto the SD card
- Wiped data and cache using 4EXT
- Finally installed the ROM using 4EXT
So I think I followed all the steps necessary, but apparently the phone now seems stuck on the HTC Bootscreen. I know it can sometimes take longer (about 10 minutes?), but I have left the phone for about 20 mins and it still is stuck on the bootscreen (HTC Logo).
I then rebooted into 4ext and wiped the dalvik cache (which I didn't do the first time, just cache and data, which is what the guide said) but it didn't help. And what is a "full wipe" exactly, and how do I do it in 4EXT? Combination of data/cache/dalvik wipe?
So now I'm kind of out of answers and I hope I can count on your experience. Should I flash the ROM again? Try another ROM?
I would be very glad if you could give some advice! Thank you very much. (Can't post in the ROM's thread in the dev section yet, as this is my first post)
Click to expand...
Click to collapse
Thank you very much for your fast answer. I'll try that. And while we are at it, I think all the partitions have to be mounted when booting into ROM? Data and System weren't mounted by 4EXT, I thought that was odd. I presume 4ext needs to unmount the partitions to format/wipe them, but shouldn't they be remounted after that?
You do not need to mount/unmount any partitions, it's done automatically.
Please ensure that you format /data as ext4, as endymion installer does not do that for you.
Also, can you provide more details about what hboot version you are running now, and what stock rom you were running before trying to flash custom?
If you have the new hboot (the one that creates a separate /lib partition) you could face some problems, but I can probably help you with those.
Cheers
All 3 partitions (system/data/cache) were formatted as ext4 from the beginning, at least that's what 4ext told me.
I was using the original Stock HTC ROM with the new HTC Sense 3.0 (was an OTA Update a few weeks ago), HBOOT is the new one (2.00.0002)
I now managed to flash Hyperion ROM 2.1 without any problems (just wipe, no format) but I manually mounted data and system before rebooting into ROM, so I don't really know what made the difference but I think it's the ROM.
Don't think mounting made a difference as when you reboot, it gets reset. It worked probably because you went from a sense 3 stock to a sense 3 custom ROM.
As lowveld suggested, format your partitions to ext4 for better performance and ROM support. All three - System, Data, Cache. Leave SD as FAT32.
Try formatting as mentioned and Endymion should boot up just fine. Hyperion is rock solid too!!!
My point is, it's not the ROM.
HappyEmu said:
I was using the original Stock HTC ROM with the new HTC Sense 3.0 (was an OTA Update a few weeks ago), HBOOT is the new one (2.00.0002)
I now managed to flash Hyperion ROM 2.1 without any problems (just wipe, no format) but I manually mounted data and system before rebooting into ROM, so I don't really know what made the difference but I think it's the ROM.
Click to expand...
Click to collapse
You probably don't have enough space on /system partition for endymion. I don't use ext4 recovery, but I know there's a way for it to show your partition map. Can you post it here?
I suppose you can resize your partitions with ext4 recovery. If you're not planning to run the stock htc rom, you would be better off resizing the new /lib partition to the minimum possible, and giving back the freed space to /system.
Cheers
I didn't find anything related to a "partition map" in 4ext, but I can print "partition info" which just lists the three partitions (system/cache/data) and sd card.
PHP:
/dev/block/mmcblk0p27 145 MiB ext4
/dev/block/mmcblk0p26 1175 MiB ext4
/dev/block/mmcblk1p1 7576 MiB fat32
/dev/block/mmcblk0p25 558 MiB ext4
PHP:
partition | fs | capacity | free
system ext4 558 MiB 61.3MiB
data ext4 1175 MiB 872.1MiB
mount: mounting /dev/block/mmcblk0p27 on /cache failed: Device or resource busy
cache ext4 145 MiB 2.5MiB
sdcard fat32 7576 MiB 6.2GiB
partition | fs | capacity | free
system ext4 558 MiB 61.3MiB
data ext4 1175 MiB 872.1MiB
mount: mounting /dev/block/mmcblk0p27 on /cache failed: Device or resource busy
cache ext4 145 MiB 2.5MiB
sdcard fat32 7576 MiB 6.2GiB
I've relocated my query. Do ignore this post thanks.
I have just tried to install another Sense 3.5 ROM (RunnymedeS 3.3a), did wipe and format and flashed the zip file. Same result, gets stuck at the HTC bootscreen.
It appears that Sense 3.0 ROMs seem to work while Sense 3.5 versions don't.
Is it really necessary to resize the partitions? Did any of you have to do this?
Im on hboot 2.00.2002 (upgraded from 0.98) and tried endymion (with 2.1 update, but it booted into 2.0 just fine too) and didnt have to change anything.
Originally i had stock GB + sense 2, then LBC mod, then CM7.1.0...
Which recovery were you using? 4ext or something different?
Sorry I didn't answer sooner. Your partition map seems fine, /system is large enough. I have no idea why you are having problems.
If you are wiling to try it again, capture a logcat of the boot process, so I can see whats going on. I assume you are familiar with adb, if not, there are lots of info around here on how to do it.
Cheers
i have this problem too. i'm on the latest OTA. unlock by htcdev. install cwm recovery,then root. works fine.
but every room i flash stuck at htc bootscreen.
mars_robot said:
i have this problem too. i'm on the latest OTA. unlock by htcdev. install cwm recovery,then root. works fine.
but every room i flash stuck at htc bootscreen.
Click to expand...
Click to collapse
Try installing Hyperion 2.1, its the only ROM that I could flash until now (tried that and two Sense 3.5 ROMs)
And apparently the recovery is also not the problem, since you used CWM, I used 4EXT 2.1.0. Now switching to newest version and try again...
@lowveld
I'll see what I can do. I just backed up my Hyperion set-up, so I can easily switch back to a working ROM (I hope )
EDIT: I just upgraded 4EXT to newest version and tried the whole process again, still no luck, not with Endymion, not with RunnymedeS. And I also couldn't find anything on how to run adb within the bootloader, I don't have any idea how adb could work with the phone not being booted already.
EDIT2: No luck with CWM either...
Ive got the exact same problem!
Hyperion boots though, so thanks alot HappyEmu.
Still need to find out whats wrong :/
I'm also having problem when I try to flash a custom ROM after unlocking with HTCDev. Installing CWM, root and backup is no problem but I get stuck on HTC logo aswell.
I tried something someone in the Evo 3D forum posted could be a workaround when using the HTCDev method but it didnt work either. It pretty much just consisted of using fastboot to launch CWM since that would give it more access. But I have always given up after 4-10 minutes of waiting at the logo. How long can it take?
I have been using a CynaogenMod ROM and have not tested any Sense roms since part of the goal with flashing for me was to try Android without Sense.
I have a untouched factory resetted backup, a backup with most stuff installed and configured and will ofc make another backup before trying anything else. So Im game if anyone want me to try something (unless its to crazy). Im not very used to adb but if I get at least some instructions I can probably search to find what I need.
I will be grateful for any help I can get.
edit: I've heard whispers that this problems could have something to do with the kernel. ROMs whit their own kernels won't work but others that is similar enough will work. But I don't know enough of Android developement to know if this is even possible.
Apparently this is a more widespread problem than I thought.
Am I correct we all have in common that we unlocked our device with the official HTC Unlocker? Do we have problems because we are not really S-OFF (ie radio is still locked)? What HBoot versions were you using? Sense 2.1 or 3.0 before unlocking? Did anyone try another Sense 3.0 ROM? I just know Hyperion works, Endymion 2.0 and RunnymedeS 3.3a don't work. Which ROMs did you test?
I know too little to make any educated guesses here...
HappyEmu said:
Apparently this is a more widespread problem than I thought.
Am I correct we all have in common that we unlocked our device with the official HTC Unlocker? Do we have problems because we are not really S-OFF (ie radio is still locked)? What HBoot versions were you using? Sense 2.1 or 3.0 before unlocking? Did anyone try another Sense 3.0 ROM? I just know Hyperion works, Endymion 2.0 and RunnymedeS 3.3a don't work. Which ROMs did you test?
I know too little to make any educated guesses here...
Click to expand...
Click to collapse
I wasn't aware that you were not S-OFF. Actually, I didn't even know you could unlock through HTCDev, as the device was not listed the last time I checked.
Can you clarify something for me? When you installed Endymion you said you got bootloops. Did you noticed if you actually got from the completely white HTC background to the next one, that says "quietly brilliant" underneath HTC?
If you did, at least the kernel booted at a first stage, and you should be able to get a logcat of the boot process until it dies.
As for kernel issues, at that point it could pretty much only be related to the ramdisk. I went back to your post with the partition info, and saw that there was some kind of error mounting the cache partition, but that could be something with ext4 recovery (the next lines shows the cache partition anyway).
I'll check the ramdisk for potential problems and get back to you.
Cheers
Following situation: I have bought a Nexus S from someone. The previous owner installed Superuser at some point and later on updated to ICS 4.0.3 (and unrooted the phone as well before the update, apparently). For warranty reasons, I want to remove the Superuser application completely, but naturally I can only do that by rooting the phone again (otherwise I will not be able to delete /system/app/Superuser.apk).
I searched around here and other sites around the web and found a few guides, but haven't found anything specifically for the i9023 with ICS 4.0.3, especially for unrooting.
Could someone may be point me in the right direction? Or is there simply no way of doing that currently on an i9023 with ICS 4.0.3?
The best thing to do would be to root, flash a stock image (incl bootloader and recovery). Then relock the bootloader, and you're all done
Also, recently some sort of flash counter resetter has come to light for ICS devices, look it up and check it out before you unroot, it might be worth the probable risk, if you're willing to go the distance to ensure a warranty. I have no clue on how or if it works though, be careful.
One question though, do you actually have any warranty seeing as you bought the device used? If not, why not just reroot it and enjoy that?
Erythnul said:
The best thing to do would be to root, flash a stock image (incl bootloader and recovery). Then relock the bootloader, and you're all done
Also, recently some sort of flash counter resetter has come to light for ICS devices, look it up and check it out before you unroot, it might be worth the probable risk, if you're willing to go the distance to ensure a warranty. I have no clue on how or if it works though, be careful.
One question though, do you actually have any warranty seeing as you bought the device used? If not, why not just reroot it and enjoy that?
Click to expand...
Click to collapse
Nexus S doesn't have a flash counter
Sent from my ice cream powered Nexus S
Erythnul said:
The best thing to do would be to root, flash a stock image (incl bootloader and recovery). Then relock the bootloader, and you're all done
Click to expand...
Click to collapse
I already went ahead and tried that, but I ran into a problem unfortuantely: http://forum.xda-developers.com/showthread.php?p=22599816#post22599816
Other users on a german Android forum reported the same problem, when using this method (the Nandroid backup image and restoring it via CWM). They then tried a different method using Odin.
(Funnily enough, when I reverted to my original ICS 4.0.3 backup image via CWM, my USB Transfer Speed problem got fixed. I only had 1 MiB/sec before, and now after this whole ordeal I have ~20 MiB/sec (or more).)
Erythnul said:
One question though, do you actually have any warranty seeing as you bought the device used? If not, why not just reroot it and enjoy that?
Click to expand...
Click to collapse
I do still have warranty on it. The device was bought on 14th of December 2011 and I have the receipt. According to the seller, he got a Galaxy Nexus on Christmas 2 weeks later, so he simply sold his brand new Nexus S.
I may want to send the phone in, because the phone speaker is a bit bad. It's not completely broken, I can still understand everything, but the quality is rather bad, some frequencies get really distorted etc. I don't know if the Samsung support partner where I'll go to will grant me the warranty here, but I want to try nonetheless. Paid too much money for it to have a bad speaker .
In my opinion, you should never use other people's CWM backups on your own phone. It can mess things up BAD. Especially when they don't say what model they have.
Grab a full ROM from here: http://forum.xda-developers.com/showthread.php?t=1445635 and you'll be good to go. Don't forget to wipe /system, /data, /cache, /boot, dalvik cache and do a factory reset before flashing, assuming you're using CWM.
Good to hear about the warranty, good luck with that!
Erythnul said:
In my opinion, you should never use other people's CWM backups on your own phone. It can mess things up BAD. Especially when they don't say what model they have.
Click to expand...
Click to collapse
Yeah, well, I am thinking the same now . I simply trusted the stickied FAQ . Maybe this should get removed.
Erythnul said:
Don't forget to wipe /system, /data, /cache, /boot, dalvik cache
Click to expand...
Click to collapse
Phew, but for that, I'd need to root it again, right? I am still not sure if any of the rooting guides I found so far also apply to my case, since I have ICS 4.0.3 on it. (As I said superuser is already installed, but the device is not rooted and it seems to be a leftover from before the ICS 4.0.3 update.)
Well, I wouldn't know Try booting into recovery, if it's CWM recovery it's really very easy, and that's all you'll need anyway. doing the full wipe and reflash guarantees that there'll be no traces of the rooting process remaining at all.
If you don't have CWM, but the phone boots up with an unlocked symbol at the Google logo (first indicator of an unlocked bootloader), you can easily flash CWM again and then flash to all-stock. Then relock. Most rooting guides still hold, just make sure you flash the latest CWM (5.0.2.0 (non-touch) or 5.8.0.x (touch)), especially as for what you want to do you don't need SU, just CWM.
Step-by-step quick guide written by me
Install Android SDK if necessary (for adb and fastboot) (plenty of guides for that around)
download recovery file from CWM and rename to recovery.img
Connect phone to computer and reboot into bootloader
fastboot oem unlock
fastboot flash recovery recovery.img
use CWM to wipe everything and reflash
fastboot oem lock
???
Profit!
Alternately, use a one-click root method to flash CWM and then work from there
Good luck
EDIT: The FAQ you mentioned is probably old news by now, but I wouldn't know how to get that updated I'll see if I can get something done about that. I feel linking to a backup, especially with a dedicated full ROM thread (also stickied btw ) around, isn't a good idea at all
Thx for that.
I did look into CWM before you posted it and noticed these wiping options. However, I am unsure what exactly I should use. There is
- wipe data/factory reset
- wipe cache partition
in the main menu of CWM and
- Wipe Dalvik Cache
under advanced. But there is no specific mention of /system and /boot .
Also is this
download recovery file from CWM and rename to recovery.img
Click to expand...
Click to collapse
actually necessary? I searched around a bit and I thought that I simply have to grab one of the full ROMs (e.g. Android 2.3.6/GRK39F/XXKF1 Radio/KA3 Bootloader) and then use
- install zip from sdcard
in CWM.
Ah, I wasn't sure whether you had CWM on there, that makes all this way easier
The format options are under mounts and storage. Be careful not to wipe the SD, and make backups of stuff you want to keep (like SMS messages or apps etc). What I always do is wipe everything (except the sd-card!) under mounts and storage and then do a factory reset, that should also take care of the dalvik cache if I remember correctly. So just skip everything I said before wipe and reflash
Sounds like you have a good handle on the situation now, good luck on the warranty thing!
Erythnul said:
Ah, I wasn't sure whether you had CWM on there, that makes all this way easier
Click to expand...
Click to collapse
Yes, although I have to flash it every time I want to use it (I guess because the stock Android ICS ROM is removing it on every boot?).
Erythnul said:
The format options are under mounts and storage. Be careful not to wipe the SD, and make backups of stuff you want to keep (like SMS messages or apps etc). What I always do is wipe everything under mounts and storage and then do a factory reset, that should also take care of the dalvik cache if I remember correctly. So just skip everything I said before wipe and reflash
Click to expand...
Click to collapse
Aaah ok, so under
- mounts and storage
I do
- format /system
- format /cache
- format /data
- format /boot
and maybe
- format /sdcard
as well, if I don't need anything on it anymore, and then
- wipe data/factory reset
in the main menu of CWM, correct? And after that
- install zip from sdcard
with the aforementioned ROM.
Exactly, but don't wipe the sdcard, as the ROM you're going to flash is on there
and after that, don't forget to relock your bootloader, if it's still unlocked they'll know it used to be rooted
Erythnul said:
Exactly, but don't wipe the sdcard, as the ROM you're going to flash is on there
Click to expand...
Click to collapse
lol, damn, yeah, that would have been stupid
Hi XDA
My device before the procedure : HTC Desire S, unbranded, Bootloader locked,
HBoot 2.00.0002, S-ON, ICS stock rom via HTC RUU tool
I unlocked the bootloader via htcdev.com.
After hours of reading and testing "everything" I found here on xda (great stuff!!),
I finally managed to have a running CM10-alpha.
(http://forum.xda-developers.com/showthread.php?t=1776256 / Version 2012-09-17)
As I am new to this flashing stuff, I first tried to follow the flashing guide
on the CM-website. Was not workable because "Revolutionary" can not be used on hboot 2...
So I continued with flashing CWM-recovery and after a wipe (factory/reset/cache/dalvik),
I flashed CM10.zip and gapps.zip.
It went through without any errors, unfortunately, the device did not boot afterwards.
I found this guide :
http://forum.xda-developers.com/showthread.php?t=1525100 (CustomROM with 4EXT-recovery)
It indicates flashing "boot.img" (from the CM10 zip-file) as a last step.
Probably the most important step for this HTC device ?!
The Desire S booted CM10 without any further problems and is running since.
(I did not flash GApps.zip, just downloaded Maps and Youtube.)
I have 3 questions :
1. Is it possible to update to a newer version of 4EXT-recovery without losing
the CM10-installation ?
(e.g. 4EXT-Touch : http://forum.xda-developers.com/showthread.php?t=1377745)
2. Is it possible to switch from 4EXT to CWM-recovery without losing
the CM10-installation ? I would like to have CWM because I could then use the ROMManager App.
(e.g. http://forum.xda-developers.com/showthread.php?t=1484753)
3. If I would stick with the current 4EXT-recovery,
do I always have to flash "boot.img" as the last step before booting up the device ?
(e.g. after the next CM10-alpha release)
"fastboot flash boot boot.img"
Click to expand...
Click to collapse
Thanks so much !
CM10 is great, so much faster than HTC-stock rom ICS (with Sense 3.6) !!
CU
1) yes
2)yep
3)si
Edit: you only have to flash the boot.img when the kernel changes from cm10 to fallout yes.
Updating cm10 no, if the dev didn't change the kernel.
After a full wipe (in 4ext format everything exept SD-card) you also have to use fastboot. Because that wipes the boot.img
Thanks !
Just to recap, I can flash CWM-recovery and then do a normal bootup (with my existing CM10 installation). No further actions required !?
As the kernel will probably remain at v2.xx with the next CM10-alpha-release of nik111, I only wipe reset/factory/cache/dalvik
and then flash the new cm10.zip.
I do not think that I will format anything. But if I would, I would have to replace boot.img again.
FrolicFrog said:
Thanks !
Just to recap, I can flash CWM-recovery and then do a normal bootup (with my existing CM10 installation). No further actions required !?
As the kernel will probably remain at v2.xx with the next CM10-alpha-release of nik111, I only wipe reset/factory/cache/dalvik
and then flash the new cm10.zip.
I do not think that I will format anything. But if I would, I would have to replace boot.img again.
Click to expand...
Click to collapse
Changing recovery will not touch anything else on your device. But there were some issues reported with CWM on some ROMs.
I think one of them is a lack of /system/lib partition support, which is important if you go from a ROM that has such to a ROM without one (it will end with two conflicting /system/lib directories and the device will not boot.
Also I am not sure that CWM wipes the .android-secure directory on the SDcard which can cause issues if going from AOSP to Sense ROM
For some reason I never changed from cwm to 4ext whilst I owned a ds but I can confirm it does wipe .android-secure on the sd card
pughie said:
For some reason I never changed from cwm to 4ext whilst I owned a ds but I can confirm it does wipe .android-secure on the sd card
Click to expand...
Click to collapse
I have used it about an year ago so it is definitely improved. But there was an user with Bluetooth issues after flashing my kernel and changing the recovery solved it. Also 4EXT has a lot of minor but very useful settings over CWM. Anyway the OP can try both and stick with the one he likes more
Btw Rom Manager can be used to check for updates and ROM downloads with 4EXT if you choose "manual flash override" from the menu
Sent from my HTC Desire S
amidabuddha said:
Btw Rom Manager can be used to check for updates and ROM downloads with 4EXT if you choose "manual flash override" from the menu
Click to expand...
Click to collapse
Ah, will check on this one. Thanks !
FrolicFrog said:
As the kernel will probably remain at v2.xx with the next CM10-alpha-release of nik111, I only wipe reset/factory/cache/dalvik
and then flash the new cm10.zip.
I do not think that I will format anything. But if I would, I would have to replace boot.img again.
Click to expand...
Click to collapse
Nk111 uploaded a screenshot today, that shows kernel v3.0.16
When upgrading cm10 wiping cache & dalvic cache should be enough. If you get any problems, apps fc or something like that, do a full wipe(I use format all partitions except SD card in 4ext, after that don't forget to flash the kernel with fastboot).
Btw wipe and format is the same.
Bug in CM10 Alpha by nk11
Hello XDA,
Sorry if this question is in the wrong thread.
It is regarding the cm10 alpha port by nk111.
I got it working, save one major bug, the speaker does not produce any sound output whatsoever:
This applies to ringtones, alarm tones and music.
The sound is perfectly audible through a pair of earphones.
I followed the steps in the official thread to delete the file /system/lib/hw/audio_policy.msm7x30.so and reboot
but this only aggravates the issue by disabling all audio outputs!!!
I am running clockwork mod v5 with HTC bootlocker unlocked, S-ON.
Any help would be greatly appreciated.
c.m.b said:
Nk111 uploaded a screenshot today, that shows kernel v3.0.16
When upgrading cm10 wiping cache & dalvic cache should be enough. If you get any problems, apps fc or something like that, do a full wipe(I use format all partitions except SD card in 4ext, after that don't forget to flash the kernel with fastboot).
Btw wipe and format is the same.
Click to expand...
Click to collapse
I saw the screenshot of kernel version 3, too. And was quite excited
Thanks for the hint with wiping only cache&dalvik.
I was just wondering what steps I need to take in order to install an updated version of my rom. Currently I use the aokp jb version 4. Want to update to the new milestone. Can someone help me out with the procedure? Will I lose any data?
Sent from my One X using xda app-developers app
dan798 said:
I was just wondering what steps I need to take in order to install an updated version of my rom. Currently I use the aokp jb version 4. Want to update to the new milestone. Can someone help me out with the procedure? Will I lose any data?
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
. First thing you should do is a nand backup in recovery (so you have something to go back to if all else fails)
. backup your SD card
. move your nand backup and sd card backup to your computer (that way if your sd gets corrupted you can reformat and push your backups to your device)
. you can also backup your apps + data with something like titanium backup (although now at least in JB if you have chosen this option Google will restore your apps, does not always work for me though so beware)
! Note that Tibu is quite controversial some people love it and swear by it and some people claim that it creates lots of issues, if you decide to use it, only use it to backup/restore user apps and not system apps. I personally use the pro version since it can sync backups to my Box and Dropbox account.
in addition to all of this I backup my sms, call log and custom launcher settings (but that's just me i'm a bit paranoid and I love redundancy)
When you're staying with the same rom you typically don't have to factory reset/clean install (unless of course the dev recommends it), just wipe cache and dalvik in recovery and flash your new rom.zip (don't forget to fastboot flash the boot.img if you're on the latest hboot) in recovery.
If you do not factory reset/clean install you will not loose data fingers-crossed. if you start encountering a lot of weirdness after a dirty flash well you will have to factory reset/clean install. I like to clean install most of the time so that I don't have to try to troubleshoot a bunch of stuff when s**T goes wrong plus it's easier to get support for obvious reasons.
In this particular case Milestone release of AOKP (milestone is a "stable" release and this is the first one) I would ABSOLUTELY do a clean install and I believe Rohan requires it because of kernel changes and the likes.
Hope all this makes sense and I did not forget anything.
Crappyvate said:
. First thing you should do is a nand backup in recovery (so you have something to go back to if all else fails)
. backup your SD card
. move your nand backup and sd card backup to your computer (that way if your sd gets corrupted you can reformat and push your backups to your device)
. you can also backup your apps + data with something like titanium backup (although now at least in JB if you have chosen this option Google will restore your apps, does not always work for me though so beware)
! Note that Tibu is quite controversial some people love it and swear by it and some people claim that it creates lots of issues, if you decide to use it, only use it to backup/restore user apps and not system apps. I personally use the pro version since it can sync backups to my Box and Dropbox account.
in addition to all of this I backup my sms, call log and custom launcher settings (but that's just me i'm a bit paranoid and I love redundancy)
When you're staying with the same rom you typically don't have to factory reset/clean install (unless of course the dev recommends it), just wipe cache and dalvik in recovery and flash your new rom.zip (don't forget to fastboot flash the boot.img if you're on the latest hboot) in recovery.
If you do not factory reset/clean install you will not loose data fingers-crossed. if you start encountering a lot of weirdness after a dirty flash well you will have to factory reset/clean install. I like to clean install most of the time so that I don't have to try to troubleshoot a bunch of stuff when s**T goes wrong plus it's easier to get support for obvious reasons.
In this particular case Milestone release of AOKP (milestone is a "stable" release and this is the first one) I would ABSOLUTELY do a clean install and I believe Rohan requires it because of kernel changes and the likes.
Hope all this makes sense and I did not forget anything.
Click to expand...
Click to collapse
Sounds excellent!! Yes this helps a ton, I was not sure of what I needed to wipe if anything. Thanks!
dan798 said:
Sounds excellent!! Yes this helps a ton, I was not sure of what I needed to wipe if anything. Thanks!
Click to expand...
Click to collapse
no problem..
Could you define a clean install and the steps?
RC196 said:
Could you define a clean install and the steps?
Click to expand...
Click to collapse
Clean install: The partitions are empty
Proper steps
Wipe System
Factory Reset
Wipe Cache (Optional, Factory reset should have done it already)
Wipe Dalvik Cache (optional, I usually dont wipe and problems dont occur)
RC196 said:
Could you define a clean install and the steps?
Click to expand...
Click to collapse
1.boot into recovery (twrp)
2. go into wipe menu and hit factory reset (DO NOT FACTORY RESET in FASTBOOT) this will wipe everything so backup first (see above post
3. flash the boot.img taken from your rom.zip of choice (this is if you are on latest version of HBOOT)
4. flash your rom.zip
5. reboot in system
Crappyvate said:
1.boot into recovery (twrp)
2. go into wipe menu and hit factory reset (DO NOT FACTORY RESET in FASTBOOT) this will wipe everything so backup first (see above post
3. flash the boot.img taken from your rom.zip of choice (this is if you are on latest version of HBOOT)
4. flash your rom.zip
5. reboot in system
Click to expand...
Click to collapse
Before I did any flashing, I made a backup of my phone of the latest HTC Sense. It was only unlocked and not rooted. That back up is still there. If I wanted I could wipe and restore this backup correct? I would not have to flash anything right?
RC196 said:
Before I did any flashing, I made a backup of my phone of the latest HTC Sense. It was only unlocked and not rooted. That back up is still there. If I wanted I could wipe and restore this backup correct? I would not have to flash anything right?
Click to expand...
Click to collapse
You will have to flash the boot.IMG from your backup and then restore the backup if you want to revert back to it
Sent from my HTC One XL
absolutelygrim said:
You will have to flash the boot.IMG from your backup and then restore the backup if you want to revert back to it
Sent from my HTC One XL
Click to expand...
Click to collapse
How would I get that boot image from the backup on my phone?
RC196 said:
How would I get that boot image from the backup on my phone?
Click to expand...
Click to collapse
You have to extract the boot.IMG to your computer and flash it with fastboot. Then restore the backup
Sent from my HTC One XL
This is what is in the backup folder in TWRP.
RC196 said:
This is what is in the backup folder in TWRP.
Click to expand...
Click to collapse
You can get the boot.IMG from the ruu zip or a 2.20 stock rooted Rom, which is in the one x pinup sticky in the android development section
Edit: boot.emmc.win is the boot.IMG. just rename it to boot.IMG and flash it from fastboot
Sent from my HTC One XL
absolutelygrim said:
You can get the boot.IMG from the ruu zip or a 2.20 stock rooted Rom, which is in the one x pinup sticky in the android development section
Edit: boot.emmc.win is the boot.IMG. just rename it to boot.IMG and flash it from fastboot
Sent from my HTC One XL
Click to expand...
Click to collapse
Oh OK thanks. So I actually didn't screw this part up LOL.:laugh:
absolutelygrim said:
You can get the boot.IMG from the ruu zip or a 2.20 stock rooted Rom, which is in the one x pinup sticky in the android development section
Edit: boot.emmc.win is the boot.IMG. just rename it to boot.IMG and flash it from fastboot
Sent from my HTC One XL
Click to expand...
Click to collapse
yep just rename boot.emmc as boot.img and now you can use this on one xl http://forum.xda-developers.com/showthread.php?t=1963896
makes it a lot friendlier, you don't need to extract the boot.img from the rom.zip, the app does for you and also you don't need a computer, you can do it all from your device