Related
ok so my HTC Vivid is unlocked and rooted.
i have s-on
HBOOT - 1.85.0024
microp - 0360
and i have the ics recovery which is the wcxrecovery.
now i want to get ICS. how do i do that? i tried using the RUU but that keeps saying error
and i dont thnk there is an actual ICS rom out there.
you can download the stock ics ruu from htc to use it you have to relock your bootloader
im on a stock vivid rom i dont have any custom roms on my phone
like if i relock it, i dont think itl matter cuz ill still be able to use the stock rom
are you on gb wanting to go to ics if so stock or custom if you want custom go to wildchilds site if stock relock bootloaders hook your phone up to your computer in fastboot mode and run the ruu
http://www.wcxxperia-nce.com/index.php
you need to register to see vivid roms
http://www.htc.com/us/support/vivid-att/downloads/
no i am on a stock vivid rom that i used from an update of an ruu. i dont have any of those like reumraider holikaked, none of those.
so you want stock ics or custom ics
can you provide me a link with both? i would really appreciate it thank you very much!
for now i will do the update that is on my phone apperently there is an update on it. ill see what happens with that and if you can still put the stock and custom ics links please
4th post down and you might want to check but i think the bootloader has to be locked to do the ota update. wildchild has a video in the op in his vivid section ics rom that walks you through all the steps to install his rom
---------- Post added at 02:08 PM ---------- Previous post was at 02:06 PM ----------
also the ruu will wipe your phone and make it like out of box
jerrycoffman45 said:
so you want stock ics or custom ics
Click to expand...
Click to collapse
custom ics !!!
efrommel said:
custom ics !!!
Click to expand...
Click to collapse
4th post down you will find the link
Hey guys, today I was determined to change my CID in order to get the 4.2.2 update as fast as possible. So, I was running 4.1.1 Rooted on a deodexed stock rom. In order to make the CID change, tried to flash with the HTC RUU. Since there is no RUU for O2 germany, I looked my radio version up and downloadaded the European RUU. The Bootloader had to be relocked, and then is when the TRAGEDY happened. I got stuck in Bootloop. I tried everything and every RUU(errors 151, 150, 131 etc) that is out there without any luck. Finally, after about 12 hours of continious trying and screaming, i found the solution.
1) flashed cwm recovery ( did nor recognize my internal storage )
2) flashed TWRP recovery and formated the internal storage (still bootloop)
3) pushed via AIO Tool sideload the latest CM10
4) cryed for about 15 min of happiness.
I am just making this post in order to help other noobs like me who do not want to go to experts that will charge you hundrets of euros/dollars/yens what ever, and make a fool out of you. I hope this helps you. After this I donated a considerable amount of money to the TWRP, CM and AIO developers, since they have done an amazing job creating these tools and they should be rewarded. Think about it and appreciate effort of others.
ps: I am swiss, so pardon my english
any cronstructive criticism, comments are welcome
Why didn't you just flash a 4.2.2 rom and update your firmware? Much simpler than trying to force an OTA.
iElvis said:
Why didn't you just flash a 4.2.2 rom and update your firmware? Much simpler than trying to force an OTA.
Click to expand...
Click to collapse
I am fan of the stock htc version. and correct me if i am wrong, but there is no 4.2.2 out yet that you can flash with custom recovery.
upsch2000 said:
I am fan of the stock htc version. and correct me if i am wrong, but there is no 4.2.2 out yet that you can flash with custom recovery.
Click to expand...
Click to collapse
You're wrong. There are plenty in the Development section. Here's one:
http://forum.xda-developers.com/showthread.php?t=2348502
iElvis said:
You're wrong. There are plenty in the Development section. Here's one:
http://forum.xda-developers.com/showthread.php?t=2348502
Click to expand...
Click to collapse
lol, thanx , i did not see it.
Htc Pico software issue
upsch2000 said:
Hey guys, today I was determined to change my CID in order to get the 4.2.2 update as fast as possible. So, I was running 4.1.1 Rooted on a deodexed stock rom. In order to make the CID change, tried to flash with the HTC RUU. Since there is no RUU for O2 germany, I looked my radio version up and downloadaded the European RUU. The Bootloader had to be relocked, and then is when the TRAGEDY happened. I got stuck in Bootloop. I tried everything and every RUU(errors 151, 150, 131 etc) that is out there without any luck. Finally, after about 12 hours of continious trying and screaming, i found the solution.
1) flashed cwm recovery ( did nor recognize my internal storage )
2) flashed TWRP recovery and formated the internal storage (still bootloop)
3) pushed via AIO Tool sideload the latest CM10
4) cryed for about 15 min of happiness.
I am just making this post in order to help other noobs like me who do not want to go to experts that will charge you hundrets of euros/dollars/yens what ever, and make a fool out of you. I hope this helps you. After this I donated a considerable amount of money to the TWRP, CM and AIO developers, since they have done an amazing job creating these tools and they should be rewarded. Think about it and appreciate effort of others.
ps: I am swiss, so pardon my english
any cronstructive criticism, comments are welcome
Click to expand...
Click to collapse
My htc pico cannot run any custom rom.
I have unblocked it by htcdev but have S-on
cid : htc__102
I also cannot revert back to stock because i cannot find any ruu matching my cid
also cannot s-off or change my cid .
I did alot but couldn't find the solution.
Please help me ... I'll be very thankful to u
saiqhussain said:
My htc pico cannot run any custom rom.
I have unblocked it by htcdev but have S-on
cid : htc__102
I also cannot revert back to stock because i cannot find any ruu matching my cid
also cannot s-off or change my cid .
I did alot but couldn't find the solution.
Please help me ... I'll be very thankful to u
Click to expand...
Click to collapse
copy ur custom rom in sd card then flash it via recovery all will be ok
---------- Post added at 06:22 PM ---------- Previous post was at 06:16 PM ----------
http://forum.xda-developers.com/showthread.php?t=1911242 here you can download recovery
lasertec_06 said:
copy ur custom rom in sd card then flash it via recovery all will be ok
---------- Post added at 06:22 PM ---------- Previous post was at 06:16 PM ----------
http://forum.xda-developers.com/showthread.php?t=1911242 here you can download recovery
Click to expand...
Click to collapse
I did it . I flashed many custom roms but my phone cannot run them properly means android UI cannot be displayed properly like with patches on the screen i can hardly see the options . and after some time i gets hang.
saiqhussain said:
I did it . I flashed many custom roms but my phone cannot run them properly means android UI cannot be displayed properly like with patches on the screen i can hardly see the options . and after some time i gets hang.
Click to expand...
Click to collapse
XPERIA aokp_pico_milestone-6-build-7 try this with astest google apps ans wipe data and cache will work
If I created a custom recovery file using CWM when the phone was on FW 4.3, if I then updated to 4.4.2 and say I didn't like it.
Could I restore the phone back to 4.3 by using the recovery file I created before updating ?
Thank you.
0-0-0 said:
If I created a custom recovery file using CWM when the phone was on FW 4.3, if I then updated to 4.4.2 and say I didn't like it.
Could I restore the phone back to 4.3 by using the recovery file I created before updating ?
Thank you.
Click to expand...
Click to collapse
hmm, that's interesting, but
1- why?
2- you definitely need to be S-Off
3- i think/believe, you can only have firmware parts which can be flashed using normal bootloader mode (such as boot.img and recovery.img), not RUU mode.
4- don't try to include hboot plus other stuff; as you probably know flashing firmware in ruu mode, requires two consecutive flashes, the first is the hboot pre-update, the second flashes the remaining firmware part.
but I wouldn't risk it to be honest, you can't be sure what's writable or not during custom recovery, and what could get corrupted and give you a hard brick.
firmware is (and should be) flashed in "fastboot oem rebootRUU" mode, and there's a reason for that... I wouldnt risk trying to flash a firmware package in custom recovery, imho.
PS: not to mention, you don't know how the custom recovery will "interpret" the contents of your zip... and where it would possibly flash stuff.... i guess you'd have to write a script to "dd" the partitions, and hope that works.... too dangerous in my opinion!!
.
---------- Post added at 07:24 PM ---------- Previous post was at 07:16 PM ----------
0-0-0 said:
If I created a custom recovery file using CWM when the phone was on FW 4.3, if I then updated to 4.4.2 and say I didn't like it.
Could I restore the phone back to 4.3 by using the recovery file I created before updating ?
Thank you.
Click to expand...
Click to collapse
EDIT: wait are you talking about firmware or just your nandroid backup
... maybe my previous post was a bit too quick and only focused on your title "Downgrading FW Using Custom Recovery ?"
Thanks for the reply.
I'm S-Off.
Yes, I'm talking about both, Android JG 4.3 to KK 4.4, plus the Nandroid backup created when the phone is using 4.3.
I don't understand some of your other comments (hboot & RUU etc), they are above my skill level.
But, I understand the basics of creating/restoring backups.
0-0-0 said:
Thanks for the reply.
I'm S-Off.
Yes, I'm talking about both, Android JG 4.3 to KK 4.4, plus the Nandroid backup created when the phone is using 4.3.
I don't understand some of your other comments (hboot & RUU etc), they are above my skill level.
But, I understand the basics of creating/restoring backups.
Click to expand...
Click to collapse
I think I moved/answered a little too fast....
If you want to try a 4.4 ROM go ahead, no problem (you need the correct recovery for 4.4 ROMs... TWRP 2.6.3.3+ is recommended at the moment for m7_u/ul models).
The nandroid (backup in recovery) will include everything except many parts of the firmware, which are really not needed at the moment; and do not get overwritten by installing a 4.4 ROM!!
Basically what I'm saying, is you do not need to upgrade firmware to run a 4.4 ROM, nor do you need to downgrade it to restore a 4.3 ROM.
in a simple view (at least on the M7): ROM = kernel, system and data partitions ... and at this point in time is not dependent on firmware
yes upgrading firmware to be inline with the ROM can have advantages, but it's not necessary.... some people are running 4.4.2 ROMs (including the Sense 6 ports) on firmwares as old as 1.xx
I hope that sort of answers your question :angel:
Thanks again for the reply.
I actually wanted to update from 4.3 to 4.4.2 via OTA updates (I should have mentioned that, sorry).
But, from your reply, I will find a custom 4.4.2 stock ROM and install that.
Then I can return to 4.3 with the CWM recovery file (after I swapped from TWRP to CWM) if I want to.
The reason I want to "test" 4.4.2 first, is because the Firewall I use "NoRoot Firewall" isn't supposed to fully work with 4.4 and above.
I like it, because it offers the user "prompts" when an app connects online. And all the others I've tried don't.
0-0-0 said:
Thanks again for the reply.
I actually wanted to update from 4.3 to 4.4.2 via OTA updates (I should have mentioned that, sorry).
But, from your reply, I will find a custom 4.4.2 stock ROM and install that.
Then I can return to 4.3 with the CWM recovery file (after I swapped from TWRP to CWM) if I want to.
The reason I want to "test" 4.4.2 first, is because the Firewall I use "NoRoot Firewall" isn't supposed to fully work with 4.4 and above.
I like it, because it offers the user "prompts" when an app connects online. And all the others I've tried don't.
Click to expand...
Click to collapse
taking an OTA update won't prevent you from going back with your Nandroid backup. however being able to take the OTA update means returning your phone to Stock / no custom recovery. which alot of times means totally wiping the phone with a RUU to take the OTA
Thank you for your reply.
I've just installed a custom 4.4.2 ROM and even NoRoot Firewall works
- This thread can be closed is necessary, Thank you all -
Let's not get into the whole debate that millions of others have about sunshine.
Anyway, I have seen conflicting information, and am somewhat confused. Many say you can still install custom roms with S-On and even install custom recoveries, while others say you can't install some roms unless you are S-Off.
Now, I know I can't flash a custom radio while S-On, or "convert" it into a play or dev or whatever edition.
I am fine with that (I assume I can still flash official radios released for it?), I don't want to convert it into a different type of M8 or switch carriers or anything. I just want to have rooted custom roms.
In that regard, just what would I be limited to exactly? Again, half the posts say you can still flash custom and rooted roms with S-On, and others say you need S-Off for custom roms, do they mean custom roms that are for dev/play/etc editions would require S-Off? Or are there custom roms designed for a regular Sprint M8 that would still need S-Off? Or am I even limited to only stock versions/mods of the Sprint rom? What about installing recoveries?
S-off isn't required to flash a ROM, but in some cases you have to flash the kernel separately from the ROM.
Do you mean that I won't be able to flash a kernel separately with S-on? I don't get that, won't roms flash the kernel and other key files to the system partition (which I assume you need to format first before flashing the rom) anyway?
Cyber Akuma said:
Do you mean that I won't be able to flash a kernel separately with S-on? I don't get that, won't roms flash the kernel and other key files to the system partition (which I assume you need to format first before flashing the rom) anyway?
Click to expand...
Click to collapse
Hit the second link in my sig and read the section pertaining to S-on kernel flashing.
I don't understand, what do you mean that you can't write to the /system partition permanently if you are S-On? Wouldn't you need to be able to write to the system partition in order to flash a custom rom your phone?
Cyber Akuma said:
I don't understand, what do you mean that you can't write to the /system partition permanently if you are S-On? Wouldn't you need to be able to write to the system partition in order to flash a custom rom your phone?
Click to expand...
Click to collapse
Meaning any changes that you make are only temporary and won't survive a reboot.
Though again, changes like installing a custom ROM? Or do you not need access to /system to install a custom rom?
It certainly helps to have S-OFF, but I haven't found it all that necessary. I'm currently on the ViperOneM8 3.2.1 with S-ON, and I'm not having any issues. Nothing that cannot be fixed anyway. At one point, I had ran into some trouble when I installed Sense 6 Toolbox (Xposed Mod), played with some settings and then uninstalled it. The trouble was with Venom Tweaks, it just wouldn't run. Thankfully I had a back-up, loaded it up, and it's all good. Other than that, no problem. And I'm not even sure if S-ON was the problem, but I'm assuming that the reason why Venom couldn't boot up was because it had no permission to overwrite some stuff that the xmod sense 6 toolbox left behind. I'm just guessing of course, I'm probably wrong.
But yeah, I would give ViperOneM8 a try, though be careful. Make sure you have all the right firmware installed BEFORE you start doing any rooting. It will save you a lot of headache.
Amer28 said:
At one point, I had ran into some trouble when I installed Sense 6 Toolbox (Xposed Mod), played with some settings and then uninstalled it.
Click to expand...
Click to collapse
Amer28 said:
I'm assuming that the reason why Venom couldn't boot up was because it had no permission to overwrite some stuff that the xmod sense 6 toolbox left behind. I'm just guessing of course, I'm probably wrong.
Click to expand...
Click to collapse
Sorry to keep going on about this, but I am still confused. If you can't permanently write to the /system partition, how were you able to install tools that modify system files? You mentioned that you think the reason was that the Toolbox software you installed left some modified files behind, if S-On means you can't permanently modify those files then how did they survive a reboot?
Would I be able to install a security application like avira onto the system partition with S-On? It has an option to install itself, and it's settings, into a rooted phone so the application (and it's settings) cannot just be wiped from a factory reset. Wouldn't it need to write to the system partition in order to do that?
Come to think of it, I know you can install another bootloader and/or recovery once you are rooted, but wouldn't you also need to be able to access the system partition in order to be able to do that?
I don't get what this unable to permanently write to the system partition while S-On entails since it seems like many things do permanently write to it still.
Cyber Akuma said:
Sorry to keep going on about this, but I am still confused. If you can't permanently write to the /system partition, how were you able to install tools that modify system files? You mentioned that you think the reason was that the Toolbox software you installed left some modified files behind, if S-On means you can't permanently modify those files then how did they survive a reboot?
Would I be able to install a security application like avira onto the system partition with S-On? It has an option to install itself, and it's settings, into a rooted phone so the application (and it's settings) cannot just be wiped from a factory reset. Wouldn't it need to write to the system partition in order to do that?
Come to think of it, I know you can install another bootloader and/or recovery once you are rooted, but wouldn't you also need to be able to access the system partition in order to be able to do that?
I don't get what this unable to permanently write to the system partition while S-On entails since it seems like many things do permanently write to it still.
Click to expand...
Click to collapse
I'm not hundred percent sure on this. I don't do any modding or anything myself, but it is my understanding that you actually 'can' write to the system partition. Just not 'some' stuff. It's essentially like having safe mode on, it just ensures that you don't completely brick the phone.
Again, please do not quote me on any on this. I'm merely humoring the subject, not an expert in any sense of the word.
You can flash virtually any custom ROM with S-On as long as you unlock your Bootloader at HtcDev... I can explain details later on, I am just busy atm...
---------- Post added at 11:09 PM ---------- Previous post was at 10:19 PM ----------
Some more details:
Basically you have 2 options to enable Custom Roms on the HTC One M8
1. Unlock bootloader at http://www.htcdev.com/bootloader/
2. Gain S-Off
For 99% of the ROMs it makes no difference which way you go. You can flash a custom recovery with both ways and you can flash custom ROMs with both ways. There is no such thing as a limitation during writing /system.
The difference is that with S-Off you can change your device IDs (e.g. CID) and in consequence you can flash firmware (like radio firmware, adsp firmware, etc.) that is not meant for your device. So playing with S-Off is quite "risky" you can "easily" achive a brick.
With S-On, you can only flash firmware which is signed for your device.
I would give the recommendation as follows: If you decide to go with S-On (which I would do if you have no specific reason for S-Off) then after flashing a custom recovery, take a backup of your stock ROM. Then, when you need a update of the firmware components, you can restore that backup, flash stock recovery, relock bootloader and use stock OTA to update all firmware components consistently.
elandroido said:
Then, when you need a update of the firmware components, you can restore that backup, flash stock recovery, relock bootloader and use stock OTA to update all firmware components consistently.
Click to expand...
Click to collapse
Wait, so I can't flash an updated radio if I am on a custom rom even if that radio was officially released for my device? I thought even with S-On you would still be able to flash a radio if it was officially released and signed for your device?
Well you can flash a radio which is signed for your device. But the safer way imho is to go the OTA way, because that really dates up everything. There might be other firmware components that can receive an update and when you go OTA everything stays consistent. But oft course you can also take the manual way, if you find a proper firmware zip.
Cyber Akuma said:
Wait, so I can't flash an updated radio if I am on a custom rom even if that radio was officially released for my device? I thought even with S-On you would still be able to flash a radio if it was officially released and signed for your device?
Click to expand...
Click to collapse
You can flash the full, signed firmware such as what OMJ provides in his RUU thread, but you cannot flash unsigned firmware to your device while S-on. You can still update your radios, you just have to jump through a few more hoops to do so, unlike those who have S-off.
You might want to take a look at the first post in the thread linked below for more info:
http://forum.xda-developers.com/showthread.php?t=1680928
Hi i am trying to install a custom rom to my HTC one M7 BUT i have windows 10 and nothing i have done will get fast boot to work at all so i cannot get my oem token identifier and the phone currantly has NO OS i have tried to load ViperOne+9.0.0-fix rom with an OTG stick and all that it does now is boot straight into TWRP v2.6.3.3 been trying for 2 weeks now i have:
downloaded the 15 second adb
full sdk
turned off driver signing in windows
activated develpoper mode in windows
followed 30+ videos
read 100's of posts
is my phone buggered or is there a way to fix it?
*EDIT* phone originally came with android HD revolution but i prefer viper....
*NEW EDIT*
finally got a rom installed viper 6.2 currently flashing permanent root to prevent any future issues and hopefully have a easier time with custom roms in future...
A BIG thanks to monrokhoury for suggesting a different download
The phone came with a custom rom right? then why do you want to unlock the bootloader? You can't flash a custom rom unless you have s-off or an unlocked bootloader.
please post a pic of your bootloader screen.
monrokhoury said:
The phone came with a custom rom right? then why do you want to unlock the bootloader? You can't flash a custom rom unless you have s-off or an unlocked bootloader.
please post a pic of your bootloader screen.
Click to expand...
Click to collapse
the phone does have s-off (cant post a pic right now) i just dont know what else to do other than try and unlock the boot loader nothing is working to get a rom to run after install
Boot Loader screen
rumrunner
M7_UL PVT SHIP S-OFF RH
CID-HTC__001
HBOOT 1.54.555
RADIO-4A.21.3263.04
OpenDSP-V32.120.274.0909
OS-2.24.401.1
eMMC-boot 2048MB
*recent attempt*
placed viperone.zip on otg
moved rom from otg to internal memory
install rom making selections as i go through the aroma installer
tap install and wait
phone reboots right back into recovery every single time
consider hurling phone at wall...
restart process with complete format...
Maybe it's a problem with the particular rom you're attempting to flash. Or maybe the zip file is corrupt. Try flashing another rom like crdroid 6.0.1 or a sense 7 based rom. Both worked for me.
Wipe cache dalvik/art cache data and system before installing. You can flash the rom zip directly from the otg, it worked for me.
And make sure you're on the right twrp version. I'm on 3.0.0 and it works great.
good luck
---------- Post added at 05:54 PM ---------- Previous post was at 05:53 PM ----------
Edit: twrp 2.6.x is outdated, flash 2.8.5+. 3.0.0+ is recommended.
monrokhoury said:
Maybe it's a problem with the particular rom you're attempting to flash. Or maybe the zip file is corrupt. Try flashing another rom like crdroid 6.0.1 or a sense 7 based rom. Both worked for me.
Wipe cache dalvik/art cache data and system before installing. You can flash the rom zip directly from the otg, it worked for me.
And make sure you're on the right twrp version. I'm on 3.0.0 and it works great.
good luck
---------- Post added at 05:54 PM ---------- Previous post was at 05:53 PM ----------
Edit: twrp 2.6.x is outdated, flash 2.8.5+. 3.0.0+ is recommended.
Click to expand...
Click to collapse
currantly on twrp 2.6.3.3 will be updating to latest once i can install a rom since i cannot use fastboot(thanks! Windows 10) will try a different rom and see if it works
last HTC One M7 i had(chewed by a puppy)was easy to flash this one is a nightmare.
most of the newest custom ROMs require twrp 2.8.5+.. But you can try a different ROM first if you want.
monrokhoury said:
most of the newest custom ROMs require twrp 2.8.5+.. But you can try a different ROM first if you want.
Click to expand...
Click to collapse
He also need a 7.xx.xxx.xx firmware to run most new custom roms based on Sense. That + a recent version of twrp will make all roms working correctly.
Btw fastboot should work fine on window 8 and 10 as long as bootloader isn't 1.44 (1.54 is fine) so most likely a drivers/usb problem here.
Sent from my HTC One using XDA Labs
@alray I was on nusenseven sense 7 rom.. kept it for like a week without fishing any firmwares and it worked fine but then I noticed a massive big with the phone's microphone so I switched to 6.0.1.
BTW I myself have a question for you Sir . I made a cwm backup when I was on 4.4.3. If I flash it will the touchscreen work? then I wanna restore the preload data and the stock recovery and upgrade to the latest official lollipop with all the bug fixes and make a nandroid backup of that. will it work?
thanks man and sorry for going off topic.
---------- Post added at 10:29 AM ---------- Previous post was at 10:22 AM ----------
I'm on s-on
monrokhoury said:
@alray
BTW I myself have a question for you Sir .
Click to expand...
Click to collapse
No need to use "Sir" with me
I made a cwm backup when I was on 4.4.3. If I flash it will the touchscreen work?
Click to expand...
Click to collapse
Yes it should work fine, the touchscreen problem was happening on older version (when restoring a very old version on a phone running a newer firmware version). Does the software versino of your backup match your firmware version?
then I wanna restore the preload data and the stock recovery and upgrade to the latest official lollipop with all the bug fixes and make a nandroid backup of that. will it work?
Click to expand...
Click to collapse
If evertyhing in /system and /data/preload is stock and your software version match with your firmware version, your stock recovery version also match then it should work, not the fastest and easiest way to update but it should work. I would simply flash a RUU to update and then extract your important files from your CWM backup.
@alray I was just kidding dude. I haven't flashed any firmware since I got the phone (that's a looong time BTW), I'll post my getvar all screen shortly. Also, I plan on extracting the recovery img from the ota zip file and flashing it via fastboot. Should take care of the recovery issue don't you think?
Sadly, there ain't no recent ruu for my particular device. I'm on aosp based 6.0.1 dirty unicorns and I think it's considerably better than the stock lollipop ROM. however, I just wanna keep a twrp nandroid backup handy on an otg just in case things go south.
Thanks a lot man.