[Q] From one rom to another - AT&T HTC One (M7)

So I'm a bit of a newb. I installed cm10.1 witht eh nightlies, but I want to go back to stock using TrickDroid. Should I do a full wipe, or will that brick my system?

KohansMusic said:
So I'm a bit of a newb. I installed cm10.1 witht eh nightlies, but I want to go back to stock using TrickDroid. Should I do a full wipe, or will that brick my system?
Click to expand...
Click to collapse
You should do wipe cache/dalvik/factory reset and you should be fine. One thing I do recommend is doing a nandroid backup before you do that. If something goes wrong you can restore your phone from it.
Sent from my HTC One using xda app-developers app

Fail
PPPeterP8nts said:
You should do wipe cache/dalvik/factory reset and you should be fine. One thing I do recommend is doing a nandroid backup before you do that. If something goes wrong you can restore your phone from it.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
So did what you said, and installed the rom. But my Recovery says the installation failed, while the aroma installers says it was successful. I tried booting and it just stays at the HTC one screen?

KohansMusic said:
So did what you said, and installed the rom. But my Recovery says the installation failed, while the aroma installers says it was successful. I tried booting and it just stays at the HTC one screen?
Click to expand...
Click to collapse
Did you do a nandroid backup. If you did. Reboot in recovery and restore you phone. Or rinse repeated the process for a different ROM. Try clean ROM first just to make sure everything is fine.
Sent from my HTC One using xda app-developers app

Related

Nandroid Restoring problem

Hey guys, I have the twrp recovery (non touch screen version) and a lot of the times when I try to restore to sense (from miui) it just shuts off half way during the restore. Btw this is with more than 50% of battery life. Has anyone else been having issues with this
Sent from my PG86100 using xda premium
Try wiping before restoring
Sent from my PG86100
There are two versions of twrp, each can only restore backups that were made with that version
sent from my EVO 3D via XDA app
dannyboyex said:
Try wiping before restoring
Sent from my PG86100
Click to expand...
Click to collapse
i wipe everything before restoring
z50king said:
There are two versions of twrp, each can only restore backups that were made with that version
sent from my EVO 3D via XDA app
Click to expand...
Click to collapse
so id need to flash the sense rom and then restore it??
Idk what you mean. If you made a nand with the old version of twrp you need to flash that version them flash the nand, then flash the new twrp and nand it. Then you would have a band that could be flashed with the current 1.1.xxx twrp
sent from my EVO 3D via XDA app on ViperROM
I think what he's saying is that if you made a back up using the old 1.0.3 version of twrp it won't work on the 1.1.1 version which was the latest one before the touch interface recovery.
Sent from my PG86100
I have twrp v1.0.0. Whenever I flash miui and then decide to restore back to my sense rom through nandroid restore, it would just shut off.
Then I'd have to reflash the sense rom and start over..
To get sense to fully restore without my phone just shutting off halfway through should I flash sense, reboot the phone, then reboot to recovery and restore??
I hope this makes sense guys.
Sent from my PG86100 using xda premium
Try it. I had a similar issue, except it didn't shut off. Mine would just stop half way through restart. I ended up having to wipe and start over because somehow my nandroids got corrupted.
Comcastrated
u might want to try to flash recovery again. I had this issue with twrp. Some backups would not restore. I went back to cwm.
This happened to me also it ended up being how I renamed the backup.
ElJimmy said:
This happened to me also it ended up being how I renamed the backup.
Click to expand...
Click to collapse
Same thing happened to me on the OG Evo. At the time, did not know that renaming them would not let them restore properly.

Quick Q, dual boot

Quick question I have been unable to get a rom to install on slot 1 of boot manager i was close but at the end I got error: unable to create new boot.img... So close. I am running 3.14.605.10 firmware, s off, viperrez. I on boot manager I have small image selected, screen force on, and ext4 selected any help would be appreciated. Oh and I tried doing cm9 and also neomax roms on slot 1
Sent from my ADR6425LVW using xda app-developers app
Bump
Sent from my ADR6425LVW using xda app-developers app
Squirrel1620 said:
Bump
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
Same problem here. I don't know what is causing the problem but I read somewhere that a work around for the boot manager problem is to restore nandroids to each slot. Just make a nandroid of your current ROM, wipe device, install new ROM, set it up and make a nandroid of the new ROM. Do this for each ROM you want to use in boot manager. Once that is done restore whatever ROM you want to be the phone ROM using regular recovery. Once that boots open boot manager (follow instructions) and restore each nandroid to adifferent slot. I'm trying now.
motenak said:
Same problem here. I don't know what is causing the problem but I read somewhere that a work around for the boot manager problem is to restore nandroids to each slot. Just make a nandroid of your current ROM, wipe device, install new ROM, set it up and make a nandroid of the new ROM. Do this for each ROM you want to use in boot manager. Once that is done restore whatever ROM you want to be the phone ROM using regular recovery. Once that boots open boot manager (follow instructions) and restore each nandroid to adifferent slot. I'm trying now.
Click to expand...
Click to collapse
Yeah. That was my last resort lol ill try it out also, good luck!
Edit: no dice still get the error building boot.img
Sent from my ADR6425LVW using xda app-developers app

Tried to upgrade to CM10 Now im stuck in a bootloop

I was on speed rom 7.5, but i liked the way cm10 looked so I wiped my data and all that and flashed it. My phone hasn't done anything but stay on the cyanogen rotating thing for like 15 minutes. Please help. (Ps. I was dumb and didnt make a nandroid backup -_-)
Ventus_zx said:
I was on speed rom 7.5, but i liked the way cm10 looked so I wiped my data and all that and flashed it. My phone hasn't done anything but stay on the cyanogen rotating thing for like 15 minutes. Please help. (Ps. I was dumb and didnt make a nandroid backup -_-)
Click to expand...
Click to collapse
Im not an expert, but did you create a backup? or try wiping twice over and re-installing.
Need a littlemore information. Are you s-off? What recovery are you using?
Sent from my HTC_Amaze_4G using xda app-developers app
xndabox said:
Need a littlemore information. Are you s-off? What recovery are you using?
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
Im using 4EXT And I am not S-OFF
Wow it bootlooped all night ;(
Ventus_zx said:
Im using 4EXT And I am not S-OFF
Wow it bootlooped all night ;(
Click to expand...
Click to collapse
same thing happened to my phone with CM 10, so i ended up instaling the android revolution rom for the time being.
What recovery are you using? Use 4ext if you aren't, try again, if it loops more than once, you either forgot to wipe before install or you need to flash the kernel manually.
Sent from my SGH-T999 using xda app-developers app
I was on speed rom 7.5, but i liked the way cm10 looked so I wiped my data and all that and flashed it. My phone hasn't done anything but stay on the cyanogen rotating thing for like 15 minutes. Please help. (Ps. I was dumb and didnt make a nandroid backup -_-)
Click to expand...
Click to collapse
I also had a problem when I flashed Speedrom but with versions 6.5 which I had previously working perfectly but then decided to switch to SS3 and then switch back. Now I also had the bootloop issue thing where the thing would just keep spinning. So I re-flashed SS3 with the faux kernel and then just did the two things:
4EXT Recovery btw
Wipe data/factory reset
Clear dalvik cache
Then install the rom and once done, go back to menu and reboot from recovery. It should tell you that the previously used boot.img will be used (that is what I get when I flash my roms and they work perfectly).
+1 is this helped!
Thanks it worked! Though I switxhed back to speed rom lol
Sent from my HTC Ruby using xda premium
Nice! And no problem, just happy your phone's back to normal! =)

help phone will not install rom/zip

ok kind of new at this. i have a gs3. i rooted the phone and installed cmw. i attempt to in stall jellybam zip, but i forgot to back up the phone. nig mistake. no the phone will not get passed the boot up menu. please help not sure what to do.
thank you
atran
Boot to recovery and wipe everything (dalvin, cache,etc) and restart the whole installation.
Sent from my Desire S using xda app-developers app
HacksonX said:
Boot to recovery and wipe everything (dalvin, cache,etc) and restart the whole installation.
Sent from my Desire S using xda app-developers app
Click to expand...
Click to collapse
I ended up unrooting with odin and rebooted to ics 4.0.1? Phone is now back on stock rom. I will root it once more and back up the phone this time. Thanks for the help.

I bricked my friend's S2, please help!

Ok, so I've rooted 2 phones so far with no problem. But when I did it to my friend, the phone won't lauch the rom any more (tried with slimbean).
I used this method before I installed slimbean: http://scientimystic.wordpress.com/...i9100-having-android-4-1-2-official-firmware/
After installing it, it wouldn't load. So I reinstalled my backup that I did after I rooted, and nothing, the phone is just stuck on the galaxy s2 screen and a yellow exclamation triangle below.
I can boot into cwm or download mode, but I can't transfer files on my phone I think.
Please help, if it was my phone I wouldn't be so desperate but I really don't want to screw up my friends phone.
If you can boot into cwm and download mode it aint bricked.
All it is....is a borked OS......I'm guessing that if you were on JB before, that when you backed up, you didn't include the preload partition. If your chosen custom rom zip is still on your phone, boot into cwm and flash it again. Thiss time though, before you reboot the phone post flash, wipe cache, dalvic and data.....then reboot.
Sent from my GT-I9100 using xda app-developers app
keithross39 said:
If you can boot into cwm and download mode it aint bricked.
All it is....is a borked OS......I'm guessing that if you were on JB before, that when you backed up, you didn't include the preload partition. If your chosen custom rom zip is still on your phone, boot into cwm and flash it again. Thiss time though, before you reboot the phone post flash, wipe cache, dalvic and data.....then reboot.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Hey, ok then well I thought bricked meant you can't load the rom.
My backup actually worked now so all is ok, but I can't install any custom rom - every one of them just loops indefinitely at the loading once I flash it, and after that it won't do anything until i revert my backup.
Are you sure you're rooted?
Sent from my GT-I9100 using xda app-developers app
keithross39 said:
Are you sure you're rooted?
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Yes, I used the guide in the link and checked some apps that required root.
Your custom rom installs......are you doing the post install wipes?
Are you waiting long enough for the phone to complete the first boot?
It always takes longer than usual for that initial boot......
Sent from my GT-I9100 using xda app-developers app
keithross39 said:
Your custom rom installs......are you doing the post install wipes?
Are you waiting long enough for the phone to complete the first boot?
It always takes longer than usual for that initial boot......
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Yes, I wiped the cache afterwards and I waited enough.. 15 minutes sure is enough of a wait, is it not?
Yeah....15 minutes is plenty long enough......but when I said wipes....I didn't mean just cache....I meant dalvic and data too.....
Sent from my GT-I9100 using xda app-developers app
Clearly, you haven't wiped data.

Categories

Resources