Okay, so the other day I decided to convert my HTC One M8 to a Google Play Edition (I mean the full conversion with OTA updates and everything, not just a GPE ROM). It was nice for a few minutes, but I immediately started to miss Sense, and I'm not a big fan of stock Lollipop like I thought I'd be. So, I used an online tutorial to restore back to Sense, except when I tried to install the custom Sense ROM I was using before the conversion (LeeDroid) via TWRP, I got an error during the install in AROMA that said "set_perm: some changes failed". Then the install failed completely. I tried wiping Data, Cache, and Dalvik Cache again, but that didn't help. Then I tried wiping the System partition, but that didn't help either. I also tried other ROMs like Android Revolution HD and SkyDragon, and those installs both returned similar errors. I can flash CyanogenMod without any problems.
I know that converting to Google Play Edition changes the partition sizes (specifically the System partition), but I followed a tutorial and successfully factory reset my phone via the stock Recovery...so the partitions should be back to normal. I also re-flashed the firmware version I had before (4.16.401.10), so that can't be the issue. But just to experiment, I also flashed an older firmware version (specifically 1.54.401.5) and an older version of TWRP (2.7.1.0) and then installed ViperOneM8 v. 1.6.0 (which is over a year old). For some reason, that worked just fine and I can run KitKat and Sense 6...but why won't Lollipop work?
I'm sorry if this is confusing, but in a nutshell, I can't flash any Lollipop, Sense-based ROMs. I get either a "set_perm: some changes failed" or "some symlinks failed" error during installation in AROMA Installer. I really don't know what those errors even mean, which is part of my confusion. Does anyone have any advice?
After you flashed the 4.xx.xxx.x Sense firmware, you need to format data (not wipe).
In TWRP select Wipe then select Format data and type YES to proceed then select reboot, reboot to recovery. Now you can install Sense lollipop ROM without errors.
You need to backup/copy all your important files like photos, musics & etc from internal storage to PC before proceed format data as it will remove/wipe everything
ckpv5 said:
After you flashed the 4.xx.xxx.x Sense firmware, you need to format data (not wipe).
In TWRP select Wipe then select Format data and type YES to proceed then select reboot, reboot to recovery. Now you can install Sense lollipop ROM without errors.
You need to backup/copy all your important files like photos, musics & etc from internal storage to PC before proceed format data as it will remove/wipe everything
Click to expand...
Click to collapse
Oh my God, I love you. That worked! I did format data before, but I guess I did it at the wrong time/in the wrong order. Thank you!
Related
Hi,
I was hoping some of the smart people here might be able to point me in the right direction for a solution to a problem I am having.
As the thread subject says; I've flashed several ROMs based on the official 2.2 release and I end up with a boot loop at the first HTC logo, it never makes it to the quietly brilliant screen, it just re-boots continuously until I pull the battery.
However, ROMs based on 2.1 boot fine, both official ones and modified ones obtained here on the forum. Also, the 2.2 based DeFrost ROM boots fine.
The actual flash process seems to go fine, with no errors being reported.
I've tried wiping/factory reset before I flash, after I flash, but the result is always the same.
I've tried with and without the latest radio installed.
I've tried booting with the SDCard and SIM removed, but no luck.
I've even tried downgrading from bootloader 0.80 to 0.75, again with no difference.
A bit of background info;
My Desire is a generic unbranded model.
Yesterday, I did try to install the OTA 2.2 update, but something messed up during the flash process and I ended up with a corrupted recovery partition and (once again) a boot loop.
Thankfully, I managed to flash an older RUU file and things are back to normal, except for the in-ability to boot any ROM based on the official 2.2 release.
If anyone can help I would be forever in your debt, as this really is driving me crazy.
I had the same problem when I installed the new 2.2 HTC ROM without wiping...
Anyway try to wipe both factory reset and all caches with both amon ra recovery port and clockwork recovery...
Same problem... but fixed I fixed it installing this: http://forum.xda-developers.com/showthread.php?p=7483900
I have same same loop like that
I dont know why? I use r5 modaco custom rom. it seems well. but when I try to use edge/3g, it starts loop booting. if turn off edge/3g, the phone works perfectly.
after that, I tried to flash another ROM, Wipe Factory reset, Wipe Cache, Wipe Dalvik, even wipe ext but it still happens
I put out SIM, the phone boot correctly( maybe just reboot one time). but put SIM in, it reboots.... sometime the phone vibrate 5 time at HTC screen .
somebody can help me?
ps: how to know wipe dalvik work perfectly? I cant see any info about it done
I had the same problem with the first rooted official rom I tried to install, then I restored to my modaco mcr-r5 (2.2) rom, updated to the new radio and then installed the rom from nickiberli via rom manager and it worked.
btw, I selected wipe data in rom manager when prompted, lost all my apps and data but the setup wizard ran when it booted up first time.
Thanks for the suggestions.
I have now tried wiping with both ClockworkMod and AmonRa.
I wiped the following with both, but still the boot loop persists with 2.2 based ROMs.
Wipe Data / Factory Reset
Wipe Cache Partition
Wipe Dalvik Cache
I also tried the MCR-R5 ROM, but it also fails to boot for me. It doesn't loop, but it seems to freeze on the first HTC screen.
As mentioned previously; 2.1 based ROMs boot flawlessly.
I really don't know what else to try.
try http://forum.xda-developers.com/showthread.php?t=741867
Ive had a bit of a shaky day with custom roms, rooting not working etc, first rom i tried failed, but this one worked straight out, wipe cache, default, ext partitions and dalvik, I used mybackup to back everything and wiped the whole phone, works like a charm now
raz2133 said:
Thanks for the suggestions.
I have now tried wiping with both ClockworkMod and AmonRa.
I wiped the following with both, but still the boot loop persists with 2.2 based ROMs.
Wipe Data / Factory Reset
Wipe Cache Partition
Wipe Dalvik Cache
I also tried the MCR-R5 ROM, but it also fails to boot for me. It doesn't loop, but it seems to freeze on the first HTC screen.
As mentioned previously; 2.1 based ROMs boot flawlessly.
I really don't know what else to try.
Click to expand...
Click to collapse
Do you have an ext partition on your memory card for a2sd? If you don't and you try to install a rom with a2sd then I think it might cause this kind of problem. I had a2sd with an ext partition on the card, I booted into clockworkmod recovery and formatted the sd card and the phone wouldn't boot.
I generated a new mcr-r5 without a2sd or a2sd+ and installed and all was ok, if that works then I would try installing the new radio and then the new rom which is what I did.
ratykat said:
try http://forum.xda-developers.com/showthread.php?t=741867
Ive had a bit of a shaky day with custom roms, rooting not working etc, first rom i tried failed, but this one worked straight out, wipe cache, default, ext partitions and dalvik, I used mybackup to back everything and wiped the whole phone, works like a charm now
Click to expand...
Click to collapse
Thanks for the suggestion, but I just tried this ROM and it wont boot for me either.
bakedecake said:
Do you have an ext partition on your memory card for a2sd? If you don't and you try to install a rom with a2sd then I think it might cause this kind of problem. I had a2sd with an ext partition on the card, I booted into clockworkmod recovery and formatted the sd card and the phone wouldn't boot.
I generated a new mcr-r5 without a2sd or a2sd+ and installed and all was ok, if that works then I would try installing the new radio and then the new rom which is what I did.
Click to expand...
Click to collapse
I do have an ext partition on my SDCard and I have tried ROMs with and without A2SD. In fact, the ROM I have used for most of my tests is "Rooted Official HTC Android 2.2 (FroYo) ROM [Market issue fixed]", which I don't think has A2SD.
I have tried booting with 3 different SDCards so far, and of-course I have tried with no card.
I have a Samsung Galaxy Nexus GSM and have been trying to install the Paranoid Android flavor custom ROM, I had 2.22 installed not long ago but managed to screw it up when I updated it without clearing my security settings (I had a 4x4 pattern swipe which I couldn't enter with the update which restored it to 3x3 pattern) so I wiped and restored to stock 4.2. I'm now trying to re-install with any custom ROM but it's not working.
Whenever I install a ROM it seems to install ok but when I get to the boot screen it just hangs on the nexus/PA logo.
I've tried with:
Goo Manager
TWRP 2.2
TWRP 2.3
CWM 6.0.1.5
and with
PA 2.22
PA 2.99.1
PA 2.99.5
PA 2.99.6
PA 2.99.7
and I always get the same error, I've tried wiping all options within TWRP and CWM and going from there but that doesn't seem to work, the strange thing for me though is that if I re-install a stock Google ROM it works perfectly fine.
I'm fairly new so please be gentle.
flash the latest twrp and move the rom and gapps to your sdcard then follow this..
1. factory reset
2. wipe system
3. wipe cache
4. wipe dalvik
5. flash rom
6. flash gapps
7. reboot
if it still freezes at boot animation pull battery reboot to recovery wipe cache/dalvik and reboot
Thanks for the suggestion but that didn't work.
Any other suggestions?
When you say TWRP 2.3 do you mean 2.3.2.1? http://teamw.in/project/twrp2/90
Clockwork 6.0.1.5 is also outdated, newest is 6.0.1.9.
You need to update your recoveries for Android 4.2.X which is what PA 2.99 is based off of.
zephiK said:
When you say TWRP 2.3 do you mean 2.3.2.1?
Clockwork 6.0.1.5 is also outdated, newest is 6.0.1.9.
You need to update your recoveries for Android 4.2.X which is what PA 2.99 is based off of.
Click to expand...
Click to collapse
Yes I did mean 2.3.2.1, I wasn't sure what the whole version number was at the time and I was halfway through resetting up stock on my phone at the time so I didn't bother to check exactly. sorry about that.
Is there a way to completely wipe everything on the phone so that it is bare stock? I was just wondering if I would be able to start from a clean phone if it would make any difference. I'm aware of cache/delvik cache/internal storage/(i think it's called "system partition" or something like that).
Using TWRP, wiping cache, dalvik, and system should wipe everything except the sdcard contents. So doing these wipes should make your phone "bare stock" again as you described
Why don't you try downloading another custom ROM or download the same ROM again because maybe it is corrupted or something
osiris231 said:
Yes I did mean 2.3.2.1, I wasn't sure what the whole version number was at the time and I was halfway through resetting up stock on my phone at the time so I didn't bother to check exactly. sorry about that.
Is there a way to completely wipe everything on the phone so that it is bare stock? I was just wondering if I would be able to start from a clean phone if it would make any difference. I'm aware of cache/delvik cache/internal storage/(i think it's called "system partition" or something like that).
Click to expand...
Click to collapse
RANT: huh..... seriously? you couldn't have browsed around, searching for this COMMON issue (which usually comes down to user "error"), read the STICKIES, before posting?
first, internal storage = /data/media aka /storage/sdcard0/ aka /sdcard/
Please read all of this
http://forum.xda-developers.com/showthread.php?t=1626895
Hi,
I recently rooted my htc desire, unrevoked method, flashed default recovery. Before flashing the stable CM for Desire, I wiped dalvik cache, wiped all data, wiped cache partition. After the installation, I logged into my google account. Problems started when going into settings resulted in going to blank settings page. Same goes for any settings window (system, play store settings). Whats more, after every single CM I install, the phone gets stuck on CM loading screen, after installing the rom, setting everything up and rebooting for the first time. The phone is S-ON. I'll try to upload logs from debugger soon.
Thanks in advance for any help.
http://pastebin.com/Zy6jKANt Log from exact loop during loading
Disregard those settings part above, its non existent now, just the loop.
macolour said:
Hi,
I recently rooted my htc desire, unrevoked method, flashed default recovery. Before flashing the stable CM for Desire, I wiped dalvik cache, wiped all data, wiped cache partition. After the installation, I logged into my google account. Problems started when going into settings resulted in going to blank settings page. Same goes for any settings window (system, play store settings). Whats more, after every single CM I install, the phone gets stuck on CM loading screen, after installing the rom, setting everything up and rebooting for the first time. The phone is S-ON. I'll try to upload logs from debugger soon.
Thanks in advance for any help.
http://pastebin.com/Zy6jKANt Log from exact loop during loading
Disregard those settings part above, its non existent now, just the loop.
Click to expand...
Click to collapse
You should s-off before installing any custom rom. Did you make a backup before installing cm7?
abaaaabbbb63 said:
You should s-off before installing any custom rom. Did you make a backup before installing cm7?
Click to expand...
Click to collapse
Wow, really? Some custom gb seemed to work just fine with s-on. I think I have a backup but I wouldn't count on it, it may have some files missing. I'm not sure now whether unrevoked did s-off on that phone, will check as soon as I get back to it.
macolour said:
Wow, really? Some custom gb seemed to work just fine with s-on. I think I have a backup but I wouldn't count on it, it may have some files missing. I'm not sure now whether unrevoked did s-off on that phone, will check as soon as I get back to it.
Click to expand...
Click to collapse
You don't have to s-off to install custom Rom, only a custom recovery.
However it is much more useful to have s-off than not so it's thoroughly recommended.
For instance, you can change hboot to use your internal memory partition layout and have more space. Currently you are on stock hboot with 250MB /system but your Rom system size is much less, so you are wasting space.
Changing hboot will give you smaller system and more internal memory
S-off will also allow you to change recovery to something like 4ext (see my sig), allowing more reliable and easier partitioning of sdcard.
Regarding your specific problem, not sure you did a proper full wipe before installing? Need to use the wipe data/factory reset option within recovery as a minimum before installing new rom
eddiehk6 said:
Regarding your specific problem, not sure you did a proper full wipe before installing? Need to use the wipe data/factory reset option within recovery as a minimum before installing new rom
Click to expand...
Click to collapse
Every single install, wiping data, cache, dalvik cache as well. Everything done from within recovery. Logs indicate a problem with hw audio decoding, though I might be wrong.
macolour said:
Every single install, wiping data, cache, dalvik cache as well. Everything done from within recovery. Logs indicate a problem with hw audio decoding, though I might be wrong.
Click to expand...
Click to collapse
did you specifically use the "wipe data/factory reset" option within recovery, or only the "format data" option under mounts and storage?
the "wipe data/factory reset" also formats the /system partition, which is just as important /data. cache and dalvik are just temporary files, should get wiped anyway on fresh rom install, but no harm in manually wiping.
haven't had time to look at the logs, not an expert in them anyway. you could try to install a different ROM to see if you have the same issues, or restore a nandoid (hope you made one, you should always do this before wiping/flashing).
eddiehk6 said:
did you specifically use the "wipe data/factory reset" option within recovery, or only the "format data" option under mounts and storage?
Click to expand...
Click to collapse
Wipe data. I'll try to make other roms work.
Hey guys,
So last night I accidentally wiped internal storage in TWRP. I guess that messed up my partitions or something, I don't know. Anyway, I can still access recovery, and I've tried to do a restore (one that I made back when I was on stock 4.4.2 I think) but after that it tries to boot, gets to "Android is upgrading... Optimizing app Y of X." and once that operation completes it shows the lockscreen for about a tenth of a second, and the phone reboots.
I'm stumped. Anyone know what can I do?
Sorry if this has been asked a hundred times. For some reason the search function in the forums isn't working for me. And I've been looking for a solution all morning.
EDIT: FYI when I tried the restore I did only System and Data and not Boot, because I was afraid that'd cause more problems.
Did you try restoring and performing a factory wipe before booting the newly-restored ROM?
It seems that Marshmallow based roms aren't working, but Lollipop ones will boot. Not sure why as I didn't have any problem with the same MM roms in the past.
More info:
MM roms wont flash in TWRP; after the failed attempt, TWRP says system cannot be mounted until I either wipe or install a 12.1 rom.
Tried to install a stock rom (4.4.2) and it failed in TWRP. Just says "Error Flashing"
Are you performing a full wipe (system, Dalvik, cache, data) before installing or restoring a ROM? Is the phone running the latest version of TWRP?
audit13 said:
Are you performing a full wipe (system, Dalvik, cache, data) before installing or restoring a ROM? Is the phone running the latest version of TWRP?
Click to expand...
Click to collapse
Yes to full wipe. TWRP is 2.8.7.0, so yeah I think it's the newest? Not 100% sure.
Wiping internal storage should not affect the partitions. I'm not sure that TWRP even has the ability to change partitions.
Yes, 2.8.7.0 is the latester version of TWRP.
If you are on the nj2 bootloader, try flashing this in TWRP: http://forum.xda-developers.com/galaxy-s3-att/general/rooted-ucufnj1-stock-rom-t2985006
Welp, seems to be all good now. Not sure if I really did anything to fix it or not. I tried to install a stock ROM but it wouldn't boot (stuck on Samsung logo) but after that my CM13 ROM installed properly again. The one CM13 ROM I have still wont install at all - maybe that file became corrupt or something? Not sure if that's even possible.
Either way I'm all fixed up. Thanks for all your help.
Cheers
Glad you got it sorted out. If you do figure out what you did to get it working, post your answer as it may help others that are in a similar situation.
ive installed firstly the latest S.Team S4 Rom also HTC 10 Base, but it ended with a assistant to decrypt my phone so ive done the steps.
have do a factory reset, and nothing has do, it asks again for decrypt my phone, so i tested with other Roms
the same problem was with Leedroid, Skydragon ROM. before i never have encrypted my phone
and i have latest firmware 3.12.401 international
latest hboot bootloader 3.19.xxx sense international bootloader
latest twrp 3.0.2-0 recovery
Let say it's a typo error, your firmware is 6.12.401 and not 3.12.401
In TWRP, select wipe - format data - yes - reboot recovery
then reinstall ROM zip
not worked for me, reinstalled many rom zips like wolla and S.Team Rom and rebooted many times
and it ask for decrypt
I'm having the same issue. is there anyway to get around this on a verizon phone.
Smilex93 said:
not worked for me, reinstalled many rom zips like wolla and S.Team Rom and rebooted many times
and it ask for decrypt
Click to expand...
Click to collapse
ive got fixed but with only one i dont know if it works with other roms or othe rmodels
you must wipe data, system, cache and then reboot the recovery, install rom.zip (Wolla Sense worked, S.Team Rom not) and choose 'perform a ful wipe'
youre done !