Database Develop

[Q] Custom Rom/Recovery w/o tampered message?

Hello.
I just got my One, upgraded from the One X
I am very skilled regarding rooting, flashing custom roms, recoveries, etc. I just have a quick question.
Is it possible to install custom rom, custom recovery and turn the phone S-OFF - WITHOUT getting the tampered message?
- If no, tell me that
- If yes, read on
Second case: Does this RRU match my M7?
First of all, what have i done myself:
- Unlocked bootloader
- Installed TWRP
- Made a nandroid backup
- Relocked bootloader because i want to flash [ROM] Android Revolution HD 3.2 Google Edition | High Quality & Performance | Android 4.3 Jelly Bean | 2.14.1700.15
- Flashed latest firmware for my phone - 2.24.401.1 (the thread above states that its not needed but recommended)
- Got the TAMPERED message and wants to get rid of that (and return from HBOOT 1.54 to original HBOOT 1.44)
In order to get rid of that message, this guide state i must use "method 2", and as part of that method 2, i must find the correct RRU.
The following is the output of getvar all before firmware update:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.16
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: REMOVED
(bootloader) imei: REMOVED
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 3980mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.043s
Click to expand...
Click to collapse
And this is getvar all after firmware update:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: REMOVED
(bootloader) imei: REMOVED
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 4010mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.043s
Click to expand...
Click to collapse
Will this RRU be for my phone: RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed.exe
- I found it here: http://www.androidruu.com/index.php?developer=M7
I chose it as its the RRU for the M7 Europe model that gets closest to my original main version (1.29.401.16 vs 1.28.401.7), also the radio in that RRU is just a tad older than my own original radio.
Also, is it possible to downgrade like that (im quite certain it is, just want to be sure).
Kind Regards
TwinAdk

Wait, you was in 1.44 hboot and now you're on 1.54?
If yes, you can't get the s-off.
The tools for the S-OFF are working only in 1.44 hboot, and, i if read right, now you have the 1.54 and you can do nothing...

****, you are kidding me, right? And RUU downgrade is not an option? That will downgrade my RUU too.
Aside from S-OFF being down the toilet, are there any other downsides to Hboot 1.54?

TwinAdk said:
****, you are kidding me, right? And RUU downgrade is not an option? That will downgrade my RUU too.
Aside from S-OFF being down the toilet, are there any other downsides to Hboot 1.54?
Click to expand...
Click to collapse
You can't downgrade with any ruu if you don't have the S-OFF...
Nope, but now you can't remove the ****Tampered**** line and you can't get the S-OFF...

Guich said:
You can't downgrade with any ruu if you don't have the S-OFF...
Nope, but now you can't remove the ****Tampered**** line and you can't get the S-OFF...
Click to expand...
Click to collapse
God dammit.. Well, are there any downsides regarding custom roms, to having the 1.54 hboot? Also, is it likely S-OFF will ever be avail. with 1.54?

TwinAdk said:
God dammit.. Well, are there any downsides regarding custom roms, to having the 1.54 hboot? Also, is it likely S-OFF will ever be avail. with 1.54?
Click to expand...
Click to collapse
No, you can flash all rom, kernel, mod, theme that you want.
For the S-OFF, no, devs said that they will work on the tool for the S-OFF when the new update form htc will come with the 1.55 hboot

Guich said:
No, you can flash all rom, kernel, mod, theme that you want.
For the S-OFF, no, devs said that they will work on the tool for the S-OFF when the new update form htc will come with the 1.55 hboot
Click to expand...
Click to collapse
So when 1.55 hboot arrives, work will start for S-OFF for that HBOOT? Any ETA on 1.55?

TwinAdk said:
So when 1.55 hboot arrives, work will start for S-OFF for that HBOOT? Any ETA on 1.55?
Click to expand...
Click to collapse
Atm there are some leaks of android 4.3 and new hboot 1.55, but this isn't the update that we will get.
For the question, yes

Guich said:
Atm there are some leaks of android 4.3 and new hboot 1.55, but this isn't the update that we will get.
For the question, yes
Click to expand...
Click to collapse
Okay, thanks
Now that i booted the phone, my storage is not available and wifi does not turn on (it says enabling, but thats all) - great start! Any idea why?
Ill look into it tomorrow my self, im off to bed now... Guess the One X will be in service for a few more days...
EDIT: Im on a firmware thats NOT for the android version i have, i think thats the problem. I guess ill have to sideload the custom rom running 4.3, and get it running that way.
Freaking hell, no S-OFF!

You relocked your bootloader after the flash of the rom?
If yes, you have to unlock this, reflash the rom and the kernel, and do a wipe of cache and dalvik-cache...

Guich said:
You relocked your bootloader after the flash of the rom?
If yes, you have to unlock this, reflash the rom and the kernel, and do a wipe of cache and dalvik-cache...
Click to expand...
Click to collapse
I cannot flash the rom as my SD is unavail... Is it an option to sideload the ROM?

TwinAdk said:
I cannot flash the rom as my SD is unavail... Is it an option to sideload the ROM?
Click to expand...
Click to collapse
Flash the stock recovery and then do a factory reset in bootloader, this will fix your sd.
After flash a custom recovery and try to use the sideload

Guich said:
Flash the stock recovery and then do a factory reset in bootloader, this will fix your sd.
After flash a custom recovery and try to use the sideload
Click to expand...
Click to collapse
Hello.
I flashed the stock recovery, and factory reset the phone. It rebooted during factory reset (of course), and booted normally afterwards. Wifi and storage did however still not work.. From within android im told that the storage is "Unavailable" (ill post screenshots later) - and from TWRP, i am told that i have "Internal storage" of 28xxx mb available (not sure about the excact size, around 28 gb) - but i cannot mount it and make it available from windows.
I can see the phone in windows, as a HTC media unit, and browse the content (storage -> legacy -> more folders -> root of SD card with folders like "downloaded" etc - default folders). But when i get there i cannot create folders or files, i can only view the content.....?
1. I cannot downgrade with RRU, since im S-ON
2. My Wifi and storage SEEMS broke (i suspect its because i flashed the firmware mentioned earlier, and my android version is not happy with that firmware - someone with more insight are welcome to comment on my guessing here)
3. Sideloading the rom i want to use (based on android 4.3) seems to be the only option - but can i sideload when my SD is not available in recovery?
Starting to worry a bit here
And thank you for all your help so far :good: I didnt get to say that last evening.. Appriciate!
Kind Regards

Hello sir,
first of all, let me say you screwed up already when not researching XDA before doing an update. Since i have done so myself numerous times, let me advise you to make it a habit, when buying a new phone to specifically research downsides of updates before accepting any.
Particularly in the HTC world, it has become a common thing to only gain S-OFF while the phone is in early software states and loose this ability towards later releases. Until now, many HTC phones i have had to deal with, had issues with disabling security on later firmwares.
Then, the storage problem you describe could possibly be related to something i have seen a fair few times. What Guich told you to do is usually the ultimate trick to get it back working. But let me ask this first: were you able to access storage from windows normally before the update? Or could you also face a driver issue?
OK. Guich's comment did not help. You flashed the stock recovery from the firmware you run. Then you ran Factory Reset from within Bootloader? Or from within android? If the latter, try the first...
I will be putting up stock recoveries from different RUU's soon on my thread here: http://forum.xda-developers.com/showthread.php?t=2316726 but you also find them on the forum already by searching. Try different stock recoveries and factory reset from Bootloader.
Then, if that doesn't help, try to run the OTA 2.24 (which already runs on your phone!) again by booting into bootloader, then picking "Fastboot" there (use volume down and up to navigate and power to confirm) and then going to your adb/fastboot with a command window. Oh, connect phone to PC of course
Lets say you have adb and fastboot plus the dll files in C:\Android. Open a CMD window and do "CD C:\Android" to go there.
there, run "fastboot oem rebootRUU" (type exactly as i do here, omit the quotes though).
then, copy and paste the OTA file (obtain HERE) to the same folder (C:\Android).
For easier typing in CMD, rename the OTA to something short and simple like test.zip or whatever.
then go back to your CMD Window and type in "fastboot flash zip test.zip"
Since its the same hboot and firmware in the OTA like you have on phone and since this package is official and signed, your phone ---should--- accept the flash. If not (maybe because you got the wrong model ID or wrong CID) i wouldn't really know how to proceed. But you DID accept that OTA before so it MUST be for your phone or else it wouldn't have flashed in the first place.
If it flashes fine, boot your phone up and check if it fixed everything.
If not, run the check for software update in Settings/Info/ and see if there is already an official OTA for your phone available that brings you past the 2.24. If not, download one of the inofficial OTA's and --- hope --- that you can flash it. Like 3.18 or 3.22. The first is for Asia/Taiwan though and will almost certainly NOT flash on your phone and the second is BrightstarUS and for the DEV edition and will also almost certainly not flash. But its worth a try.
beyond that, i have no more valuable tips. Only thing I would try is to flash CWM and do a clear storage, wipe data, wipe everything there. But be sure to have your nandroid ready if you do that. CWM uses a slightly different formatting method so it could possibly correct issues. In the past, i have read about screwed up SDcards related to CWM formatting more often than those that got screwed up by TWRP though. So its not exactly ideal to play with CWM on a phone that has already issues with its partition. But if i was desperate, i would do it anyway.
If that doesnt help or make it worse, do the very same thing on TWRP, pick the "wipe Data" option which prompts you to type "yes" into an input line. This will once again format your SD with a different method. It could possible correct this problem.
DO NOT attempt to screw around with the SD Partition using tools like MiniTool or EASUS if you can access the sd from them at all!
The SD Card is an EXT4 file system and cannot be formatted with FAT or NTFS from windows. If you do that, the phone wont work at all anymore. The exact parameters to format the partition externally are not known to me and i doubt you can address the partition from within windows at all. Maybe it works under linux...
Sorry. Cant be much help here. If that all doesnt work, just flash stock recovery back and restore your stock nandroid and send it in for repair. Them service dudes will have the right RUU and fix it for you.
[EDIT]
Oh and before i forget: if you can fix it with these tips, you owe me one
You have to flash Team Venom's ViperOne then instead of ARHD! :laugh:

Aroma installer is running now!! So excited to see the result! I sideloaded the zip, via adb sideload Nice short article on it here: http://teamw.in/ADBSideload
Will return with outcome :highfive::fingers-crossed::fingers-crossed::fingers-crossed:
EDIT: Its back! Running custom rom with sd card avail and wifi working! Pew, saved by adb sideload, increddible!

[Q] Restore to Stock ROM and Lock BL

Hi Everyone,
Okay so I have spent the last 3 hours following various guides in order to restore my ViperOne ROM HTC One M7 to a stock HTC ROM along with locking the bootloader again, everything I've tried has failed though. I'm wondering if anyone here can help me as I need to sell this phone ASAP but can't do that until I restore to stock.
Anyway, the bootloader was unlocked using the HTCDev website and I then installed the custom ROM after that. The Bootloader version appears to be 1.57, not sure if that actually matters.
I tried locking the bootloader which worked and then tried to restore using the O2 UK RUU which failed (The app just crashes at the same point every time).
So I'd really appreciate any help from you guys
Thanks in advance

sheppy1 said:
Hi Everyone,
Okay so I have spent the last 3 hours following various guides in order to restore my ViperOne ROM HTC One M7 to a stock HTC ROM along with locking the bootloader again, everything I've tried has failed though. I'm wondering if anyone here can help me as I need to sell this phone ASAP but can't do that until I restore to stock.
Anyway, the bootloader was unlocked using the HTCDev website and I then installed the custom ROM after that. The Bootloader version appears to be 1.57, not sure if that actually matters.
I tried locking the bootloader which worked and then tried to restore using the O2 UK RUU which failed (The app just crashes at the same point every time).
So I'd really appreciate any help from you guys
Thanks in advance
Click to expand...
Click to collapse
Post a fastboot getvar all with the imei and serialno removed. I am guessing that the RUU you ran was for an earlier version and unless you are S-OFF you can only run RUUs that are same OS version or higher.
You will need to use this guide to return to stock.

majmoz said:
Post a fastboot getvar all with the imei and serialno removed. I am guessing that the RUU you ran was for an earlier version and unless you are S-OFF you can only run RUUs that are same OS version or higher.
You will need to use this guide to return to stock.
Click to expand...
Click to collapse
Hi! Sorry for the late reply, please find below the output that you requested:
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4T.27.3218.14
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno:
imei:
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: HTC__001
battery-status: good
battery-voltage: 3811mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-e47fb74b
hbootpreupdate: 11
gencheckpt: 0
You were correct, I was trying to boot a lower version. I heard that people have had luck using Firewater to S-OFF with CM11 installed. It didn't help me though. Anything you might be able to suggest would be a massive help! Thanks

sheppy1 said:
Hi! Sorry for the late reply, please find below the output that you requested:
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4T.27.3218.14
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno:
imei:
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: HTC__001
battery-status: good
battery-voltage: 3811mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-e47fb74b
hbootpreupdate: 11
gencheckpt: 0
You were correct, I was trying to boot a lower version. I heard that people have had luck using Firewater to S-OFF with CM11 installed. It didn't help me though. Anything you might be able to suggest would be a massive help! Thanks
Click to expand...
Click to collapse
Based on your getvar all you have a Int'l (.401) phone not an O2 UK branded phone. You will need to follow the directions of this site for stock rom 5.11.401.10 and you should be back whole. You can get the stock firmware if you need it from this site: http://xda7.androidrevolution.org/db_mirror/Firmware/index.php?dir=HTC%2FHTC_One%2F401%2F Just select the 5.11.401.10 firmware.
For S-OFF, you need to be as close to stock as you can. If you are getting "whelp not able to S-OFF" then you might look at Sunshine S-OFF, but there is a price use it.

I realised that I had the international version shortly after posting my information back to you in this thread. Okay so I'm not really interested in getting S-OFF, I only wanted it to be able to use the RUU to restore to stock. So if I just follow method 1 from the post you linked me too, will I be back to get back to stock sense? I assume that I would still see "relocked" and "tampered" in my bootloader?
Thanks for all your help so far!
That worked a charm!!! I'm back on stock FW!!! Thank you! One thing though, will the person I sell the phone too be able to get software updates in future?

sheppy1 said:
I realised that I had the international version shortly after posting my information back to you in this thread. Okay so I'm not really interested in getting S-OFF, I only wanted it to be able to use the RUU to restore to stock. So if I just follow method 1 from the post you linked me too, will I be back to get back to stock sense? I assume that I would still see "relocked" and "tampered" in my bootloader?
Thanks for all your help so far!
That worked a charm!!! I'm back on stock FW!!! Thank you! One thing though, will the person I sell the phone too be able to get software updates in future?
Click to expand...
Click to collapse
If you have stock rom, stock recovery & stock firmware, he/she should be able to get OTA assuming you did not put a custom recovery or root after flashing the stock fw.

majmoz said:
If you have stock rom, stock recovery & stock firmware, he/she should be able to get OTA assuming you did not put a custom recovery or root after flashing the stock fw.
Click to expand...
Click to collapse
That's great news! Would the fact that I ran the stock FW recovery zip from your link mean that I no longer have TWRP on my phone or do I have to do something else to get rid of that too?

sheppy1 said:
That's great news! Would the fact that I ran the stock FW recovery zip from your link mean that I no longer have TWRP on my phone or do I have to do something else to get rid of that too?
Click to expand...
Click to collapse
Yes, you will have stock recovery, stock radio and stock hboot.

majmoz said:
Yes, you will have stock recovery, stock radio and stock hboot.
Click to expand...
Click to collapse
Thanks for all your help!

Should my bootloader still say "tampered"?

sheppy1 said:
Should my bootloader still say "tampered"?
Click to expand...
Click to collapse
Yes, you would have to be S-OFF to reset it.

Okay thank you! Was just thinking that something sill wasn't back to stock so thought I'd check

[Q] Unable to go STOCK or flash other ROMs, adb shows device as offline

Hello xda members.
I'm having some trouble with my device, I did search around this past week but still didnt success in fixing it, hope someone can point me in the right direction.
So I was S-ON with 4.3 - 4.4 on ViperOne for a long time, most of the things worked fine but my 3G was a bit slow/disconnected from time to time.
I though giving a shot to a Lollipop version Sky Dragon. I downloaded and installed Sky Dragon and used it fine for some months, but then when I wanted to use Android Studio for a project my device was not recognized. I manually run adb devices and it would not show my device (debuggin on), tried some search on google but without success.
I though moving back to ViperOne / ARHD (I really missed SENSE) would solve my problem, so downloaded the rom and tried to install but it would always stuck in "formatting partition" process.
I manually put my device in fastboot and run getvar all which resulted in BLANK version-main, very strange.
I did some search but had only few similar cases, I tried to go to STOCK by re-lockocking bootloader, flashing stock firmware but the RUU.exe would always stop at 5% and show "fastboot_htc.exe has stopped working", again did some research but could not find a solution.
When I try to flash custom firmware through fastboot flash zip I will always get "(bootloader) Read zipped android_info fail FAILED (remote: 99 unknown fail)".
I then found a tool to write a version-main into the emmc and after flashing it in TWRP I got a 1.00.000.0 version-main. Tried all of above again with the same results. My device will be recognised as "offline" in adb devices.
Luckily I have some backups (viperone 4.3 and skydragon) that work fine except that I cant update and cant connect via adb.
I have outputted my getvar all, let me know if you need further info for my case.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.00.000.0
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxx
(bootloader) imei: xxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3976mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
What can you suggest me?
Thanks a lot guys, and sorry for the long story!

mindxpert said:
Hello xda members.
I'm having some trouble with my device, I did search around this past week but still didnt success in fixing it, hope someone can point me in the right direction.
So I was S-ON with 4.3 - 4.4 on ViperOne for a long time, most of the things worked fine but my 3G was a bit slow/disconnected from time to time.
I though giving a shot to a Lollipop version Sky Dragon. I downloaded and installed Sky Dragon and used it fine for some months, but then when I wanted to use Android Studio for a project my device was not recognized. I manually run adb devices and it would not show my device (debuggin on), tried some search on google but without success.
Click to expand...
Click to collapse
Update your driver to latest HTC drivers
Update you android SDK to latest version
I though moving back to ViperOne / ARHD (I really missed SENSE) would solve my problem, so downloaded the rom and tried to install but it would always stuck in "formatting partition" process.
Click to expand...
Click to collapse
What recovery version is installed on the phone?
I manually put my device in fastboot and run getvar all which resulted in BLANK version-main, very strange.
Click to expand...
Click to collapse
Not really, its a normal issue everyone get when using some twrp versions.
I did some search but had only few similar cases, I tried to go to STOCK by re-lockocking bootloader, flashing stock firmware but the RUU.exe would always stop at 5% and show "fastboot_htc.exe has stopped working", again did some research but could not find a solution.
Click to expand...
Click to collapse
Make sure to uninstall HTC Sync from your computer. Keep the drivers installed but uninstall HTC Sync. You are not giving any info about what ruu you are trying to flash but afaik, there is none you can use for this phone with s-on.
When I try to flash custom firmware through fastboot flash zip I will always get "(bootloader) Read zipped android_info fail FAILED (remote: 99 unknown fail)".
Click to expand...
Click to collapse
You can not flash custom firmware when S-ON...
I then found a tool to write a version-main into the emmc and after flashing it in TWRP I got a 1.00.000.0 version-main. Tried all of above again with the same results. My device will be recognised as "offline" in adb devices.
Click to expand...
Click to collapse
Having the version-main blank is not an issue preventing your phone to work properly, its only an aesthetic issue. The version-main can be restored by flashed the stock firmware back.

alray said:
Update your driver to latest HTC drivers
Update you android SDK to latest version
Click to expand...
Click to collapse
Already have the latest SDK version.
alray said:
What recovery version is installed on the phone?
Click to expand...
Click to collapse
I'm using TWRP 2.8.5.0
alray said:
Make sure to uninstall HTC Sync from your computer. Keep the drivers installed but uninstall HTC Sync. You are not giving any info about what ruu you are trying to flash but afaik, there is none you can use for this phone with s-on.
Click to expand...
Click to collapse
I found from my CID that this might be compatible RUU_M7_UL_K44_SENSE55_MR_Rogers_WWE_4.19.631.9_Radio_4A.23.3263.28_10.38r.1157.04L_release_351317_signed_2.exe
alray said:
You can not flash custom firmware when S-ON...
Click to expand...
Click to collapse
So should I go S-OFF before? I'm not sure if I can downgrade and S-OFF in the current condition.
alray said:
Having the version-main blank is not an issue preventing your phone to work properly, its only an aesthetic issue. The version-main can be restored by flashed the stock firmware back.
Click to expand...
Click to collapse
Thank you for the clarification

mindxpert said:
Already have the latest SDK version.
Click to expand...
Click to collapse
And latest HTC drivers? Your phone should be visible from "my computer" when booted in twrp 2.8.5.0 cause twrp now have mtp support.
Code:
I found from my CID that this might be compatible RUU_M7_UL_K44_SENSE55_MR_Rogers_WWE_4.19.631.9_Radio_4A.23.3263.28_10.38r.1157.04L_release_351317_signed_2.exe
Not with s-on. 4.19.631.9 is a downgrade, you need s-off to downgrade.
So should I go S-OFF before? I'm not sure if I can downgrade and S-OFF in the current condition.
Click to expand...
Click to collapse
You can go s-off using sunshine s-off but it cost 25$ or you can flash other roms by fixing your adb issues.

alray said:
And latest HTC drivers? Your phone should be visible from "my computer" when booted in twrp 2.8.5.0 cause twrp now have mtp support.
Click to expand...
Click to collapse
Yes my device is visible when in recovery.
alray said:
I found from my CID that this might be compatible RUU_M7_UL_K44_SENSE55_MR_Rogers_WWE_4.19.631.9_Radio_4A.23.3263.28_10.38r.1157.04L_release_351317_signed_2.exe
Not with s-on. 4.19.631.9 is a downgrade, you need s-off to downgrade.
You can go s-off using sunshine s-off but it cost 25$ or you can flash other roms by fixing your adb issues.
Click to expand...
Click to collapse
I used sunshine to s-off my device. Currently downloading files from your signature post which had a case with my CID and MID to return stock then update firmware/rom,
Thanks, will report back tomorrow.

Softbrick Going From CM12.1 to Stock

Hey everyone. I read a lot of posts and tutorials on here (love it) and I've done what I can to try and fix my issue, but I've hit a wall. Even a nudge in the right direction would be amazing. I am working with an AT&T HTC One M7 variant (CWS 001). Here are some relevant settings as to where I am now (below them is the progress of why they are what they are):
HBOOT 1.56
S-ON
Bootloader unlocked
TWRP v2.8.7.0 installed
SuperSU BETA 2.94
Android 4.1.2
Software 1.26.502.15
I recently flashed CM12.1 onto my HTC One M7. Prior to doing so, I did an
Code:
adb backup
(which I now assume I should have done a backup through TWRP?). I wanted to go back to official Android, so I did an
Code:
adb restore
to no avail. This worked for me in the past, so either I'm not sure whether it was wrong to begin with, or something went wrong in general. Either way, that's moot point.
Since that failed, I settled on the method laid out at http://www.htc1guru.com/downloads/stock-rom-downloads/ to restore to stock... Believing that it would restore to stock ROM, remove custom recovery and root, and I would be able to take OTA updates and start fresh-ish.
Long story short, I followed the video and ended up with software version "1.26.502.12" as expected... No touch controls, used a mouse to receive OTA update via WiFi. Somewhere along the process of installing the update, I got a message that it failed, was not able to capture the error, and the device rebooted. As a result of that failure, the software was updated to "1.26.502.15" but the WiFi is now broken... Of course meaning no OTA update. Since the touch controls do not work, I can't use the USB internet pass-through, so my device is relegated to mobile data.
I attempted to relock the bootloader (after affirming that the recovery looked to be stock) and run an RUU to update the phone (also unrooted at this point). I started with the official ROM listed on the HTC website, but I get a 155 error (which, as far as I've been able to find, should not be getting as the bootloader was relocked). I tried an RUU from htc1guru for 1.26.502.15, resulting in the same error. So all I can tell is that something is causing any RUU to fail (would there be logs somewhere?)
At this point I went "eff it, I should be able to get back to CM12.1 at least." So I unlocked the bootloader, installed TWRP v2.8.7.0, and initially installed SuperSU BETA 2.94. TWRP fails each time trying to flash CM12.1 now, however. It now also fails to flash the Guru reset from above.
And that now brings me to today... Basically at a complete loss as to next steps. Clearly I've bungled the whole thing and either taken a misstep or (more likely) a bunch of missteps. My device is successfully rooted, as I was able to download Flashify via the Play Store, open it, and see that it was granted permissions. I'm thinking that my next step might be to try flashing a stock recovery from http://forum.xda-developers.com/showthread.php?t=2545227 via Flashify and seeing if that works.
If it doesn't... Man, I could really use the help! Otherwise, I'm using a Lumia 635 indefinitely...

scirto said:
Hey everyone. I read a lot of posts and tutorials on here (love it) and I've done what I can to try and fix my issue, but I've hit a wall. Even a nudge in the right direction would be amazing. I am working with an AT&T HTC One M7 variant (CWS 001). Here are some relevant settings as to where I am now (below them is the progress of why they are what they are):
HBOOT 1.56
S-ON
Bootloader unlocked
TWRP v2.8.7.0 installed
SuperSU BETA 2.94
Android 4.1.2
Software 1.26.502.15
I recently flashed CM12.1 onto my HTC One M7. Prior to doing so, I did an
Code:
adb backup
(which I now assume I should have done a backup through TWRP?). I wanted to go back to official Android, so I did an
Code:
adb restore
to no avail. This worked for me in the past, so either I'm not sure whether it was wrong to begin with, or something went wrong in general. Either way, that's moot point.
Since that failed, I settled on the method laid out at http://www.htc1guru.com/downloads/stock-rom-downloads/ to restore to stock... Believing that it would restore to stock ROM, remove custom recovery and root, and I would be able to take OTA updates and start fresh-ish.
Long story short, I followed the video and ended up with software version "1.26.502.12" as expected... No touch controls, used a mouse to receive OTA update via WiFi. Somewhere along the process of installing the update, I got a message that it failed, was not able to capture the error, and the device rebooted. As a result of that failure, the software was updated to "1.26.502.15" but the WiFi is now broken... Of course meaning no OTA update. Since the touch controls do not work, I can't use the USB internet pass-through, so my device is relegated to mobile data.
I attempted to relock the bootloader (after affirming that the recovery looked to be stock) and run an RUU to update the phone (also unrooted at this point). I started with the official ROM listed on the HTC website, but I get a 155 error (which, as far as I've been able to find, should not be getting as the bootloader was relocked). I tried an RUU from htc1guru for 1.26.502.15, resulting in the same error. So all I can tell is that something is causing any RUU to fail (would there be logs somewhere?)
At this point I went "eff it, I should be able to get back to CM12.1 at least." So I unlocked the bootloader, installed TWRP v2.8.7.0, and initially installed SuperSU BETA 2.94. TWRP fails each time trying to flash CM12.1 now, however. It now also fails to flash the Guru reset from above.
And that now brings me to today... Basically at a complete loss as to next steps. Clearly I've bungled the whole thing and either taken a misstep or (more likely) a bunch of missteps. My device is successfully rooted, as I was able to download Flashify via the Play Store, open it, and see that it was granted permissions. I'm thinking that my next step might be to try flashing a stock recovery from http://forum.xda-developers.com/showthread.php?t=2545227 via Flashify and seeing if that works.
If it doesn't... Man, I could really use the help! Otherwise, I'm using a Lumia 635 indefinitely...
Click to expand...
Click to collapse
Ignore my last paragraph. I completely misread what that file was providing (stock recovery, duh, of course that's what it's providing. Not what I need).

Also, if this helps:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4T.24.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.18.502.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT344W907896
(bootloader) imei: 354439054277373
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3849mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c6bbb6d4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

scirto said:
Also, if this helps:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4T.24.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.18.502.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT344W907896
(bootloader) imei: 354439054277373
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3849mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c6bbb6d4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Hey, just picked up your post in the Unbrick thread. So basically your problem started when you tried to take OTA updates with a Stock rom older than your current firmware.
You can't downgrade firmware while s-on. So when the OTA tried to flash the firmware it failed
The simplest way to get you back to a working stock device will be to use an ruu. You can use this one here http://www.htc1guru.com/dld/ruu_m7_...9_10-26-1718-01l_release_356565_signed_2-exe/
Download it and put it on your pc desktop. Then reboot your device to the bootloader and connect fastboot usb. Because your s-on we need to relock the bootloader or the flash will fail so enter these commands.
Code:
fastboot erase cache
fastboot oem lock
fastboot reboot-bootloader
Once the bootloader reboots check it's relocked and in fastboot usb mode then launch the ruu .exe from your desktop. Follow the instructions on your pc. When the flash is complete your device should be back to stock and boot right up.
Then you can take OTA updates safely before unlocking your bootloader again :good:
Sent from my M7 ARHD 84-Kitkat

Danny201281 said:
Hey, just picked up your post in the Unbrick thread. So basically your problem started when you tried to take OTA updates with a Stock rom older than your current firmware.
You can't downgrade firmware while s-on. So when the OTA tried to flash the firmware it failed
The simplest way to get you back to a working stock device will be to use an ruu. You can use this one here http://www.htc1guru.com/dld/ruu_m7_...9_10-26-1718-01l_release_356565_signed_2-exe/
Download it and put it on your pc desktop. Then reboot your device to the bootloader and connect fastboot usb. Because your s-on we need to relock the bootloader or the flash will fail so enter these commands.
Code:
fastboot erase cache
fastboot oem lock
fastboot reboot-bootloader
Once the bootloader reboots check it's relocked and in fastboot usb mode then launch the ruu .exe from your desktop. Follow the instructions on your pc. When the flash is complete your device should be back to stock and boot right up.
Then you can take OTA updates safely before unlocking your bootloader again :good:
Sent from my M7 ARHD 84-Kitkat
Click to expand...
Click to collapse
First off, just want to say thanks for the response! I'll give it a shot with a different RUU, but I do want to mention that I have tried this process (albeit different RUU) and it failed.
So I first tried with the most recent RUU officially provided by HTC. It failed, which led me research to discover that I needed to relock the bootloader (received error code 155). So I relocked the bootloader, tried the same RUU again but received the same error code. So I have tried this with no success so far, but I will try again with the RUU you linked.
Also, I think I found where the logs get dumped from the RUU process so I will link my progress with the output in the event it does fail. Right now, before I try it, I will mention that I am now running software 1.26.502.10 (restored from a nandroid backup), stock recovery, but I am rooted. Does the RUU remove the root, or will it leave it and then I need to unroot to OTA update?
Anyways, more to come shortly...
EDIT: I will also note that my last attempt with an RUU was with my phone starting on the home screen. Not sure if starting in bootloader/fastboot is better or worse or makes no difference? I'll try that too

scirto said:
First off, just want to say thanks for the response! I'll give it a shot with a different RUU, but I do want to mention that I have tried this process (albeit different RUU) and it failed.
So I first tried with the most recent RUU officially provided by HTC. It failed, which led me research to discover that I needed to relock the bootloader (received error code 155). So I relocked the bootloader, tried the same RUU again but received the same error code. So I have tried this with no success so far, but I will try again with the RUU you linked.
Also, I think I found where the logs get dumped from the RUU process so I will link my progress with the output in the event it does fail. Right now, before I try it, I will mention that I am now running software 1.26.502.10 (restored from a nandroid backup), stock recovery, but I am rooted. Does the RUU remove the root, or will it leave it and then I need to unroot to OTA update?
Anyways, more to come shortly...
Click to expand...
Click to collapse
The problem is because your s-on. The way firmware is flashed is very strict with s-on.
You must Relock the bootloader.
You can only use firmware or ruu's that match your MiD and CiD. And they must be signed by HTC.
You can only flash a signed ruu or firmware that is the same as your current version or one update above.
So you see the earlier ruu will fail because it's to old and classed as a downgrade. There for can't be flashed with s-on even while relocked.
The latest ruu is lollipop 7.x.502.xx. So to flash it your device must be on at least 6.x.502.xx. Or the flash will fail. As your device is on 4.x.502.x you need the ruu I linked in my earlier instructions or a 5.x.502.xx which to the best of my knowledge does not exist :good: It should work as long ad you Relock your bootloader. Let me know how it goes
Sent from my SM-T230 using Tapatalk

deleted

Danny201281 said:
The problem is because your s-on. The way firmware is flashed is very strict with s-on.
You must Relock the bootloader.
You can only use firmware or ruu's that match your MiD and CiD. And they must be signed by HTC.
You can only flash a signed ruu or firmware that is the same as your current version or one update above.
So you see the earlier ruu will fail because it's to old and classed as a downgrade. There for can't be flashed with s-on even while relocked.
The latest ruu is lollipop 7.x.502.xx. So to flash it your device must be on at least 6.x.502.xx. Or the flash will fail. As your device is on 4.x.502.x you need the ruu I linked in my earlier instructions or a 5.x.502.xx which to the best of my knowledge does not exist :good: It should work as long ad you Relock your bootloader. Let me know how it goes
Sent from my SM-T230 using Tapatalk
Click to expand...
Click to collapse
That all makes sense to me and why I was getting two failed RUU's before... One was too old, one was too new. As I type this, I just got a message saying that the ROM update was successful so let's see how it goes from here... Other than that, it had appeared I was following steps for the RUU's perfectly, hence my confusion!
Touch screen ability is back (I knew the old version I was on would cause issues, as warned by htc1guru) and I'm walking through the device setup now... Will update when I get to the OTA process.
Suffice to say, looking good so far and at the very least grateful to be on a DIFFERENT step than I was before!

scirto said:
That all makes sense to me and why I was getting two failed RUU's before... One was too old, one was too new. As I type this, I just got a message saying that the ROM update was successful so let's see how it goes from here... Other than that, it had appeared I was following steps for the RUU's perfectly, hence my confusion!
Touch screen ability is back (I knew the old version I was on would cause issues, as warned by htc1guru) and I'm walking through the device setup now... Will update when I get to the OTA process.
Suffice to say, looking good so far and at the very least grateful to be on a DIFFERENT step than I was before!
Click to expand...
Click to collapse
Good to know. Glad you got it sorted. At least you can start a fresh if nothing else. :good:
Sent from my M7 ARHD 84-Kitkat

Danny201281 said:
Good to know. Glad you got it sorted. At least you can start a fresh if nothing else. :good:
Sent from my M7 ARHD 84-Kitkat
Click to expand...
Click to collapse
Exactly... Might be the software developer in me, but I feel a huge sense of relief as long as I start to see something different happening. OTA is downloading, no root is detected, so the process should complete successfully. Major kudos to you, my friend.

So I was able to accept the OTA update to get up to 4.4.2 and software 5.something.something and am currently updating further... At this point, I think I'm comfortable in saying this issue is resolved. Thanks for the help!!!

scirto said:
So I was able to accept the OTA update to get up to 4.4.2 and software 5.something.something and am currently updating further... At this point, I think I'm comfortable in saying this issue is resolved. Thanks for the help!!!
Click to expand...
Click to collapse
Your Welcome. Enjoy
Sent from my SM-T230 using Tapatalk

Deleted OS with no backup (Solved)

Hello, guys. How you doing?
UPDATE: it's solved, i got back to stock rom after flashing this: https :// fl1.androidfilehost.com/dl/2k6GKx4IJOgIhD09zRzbzw/1441027324/95897840722641610/Reset_rom_6.07.1540.2.zip?
Now I'm going to do a BACKUP haha
I am with a HTC ONE M7 Internation/Unlocked Soft-Bricked, with no OS... Here are some information:
- Using TWRP 2.8.7.0 custom recovery for M7 (latest version)
- Unlocked bootloader
- Rooted (at least I did it before wipping my OS)
- S-ON!
- HBOOT v.1.57
- Already have ADB/Fastboot on my PC
- Modelid: PN0711000
- Cidnum: HTC__332
Here's my tale:
I tried to install RUU M7 Lollipop ROM, from HTC's website. But, at the very beggining of the instalation (4%), the RUU software said it lost my device. I did it while in fastboot mode, because it was the only way RUU recognized my phone. Then I could not install Lollipop ROM by RUU method, so I decided to flash a Lollipop ROM Unlocked Version for One M7.
I knew that for doing it I would need to install some custom recovery on my phone, unlock its bootloader mode and install on my PC ADB and Fastboot. I did all of this; the bootloader unlocked I did from HTC's website guide. So, I put on my phone a ROM in zip extension, boot it on recovery mode. I read that I should wipe data, cache, calvik cache and, maybe, system. And I did it... with NO BACKUP of original ROM --' I know I was stupid...
So I wipe this partitions, entered Install menu and tried to run instalation of the ROM zip file. It didn't work!!! Some error: "E: error executing updater binary in zip..." And I tried to flash different ROMs, all of them showed this error...
Then now I am with a Soft-Bricked HTC ONE M7 which has no OS. Some pics of my status: https: // w w w .dropbox.com/s/ruyen2ikn0u5i0u/Soft-Bricked%20M7.rar?dl=0
I hope you can help me

Please, help me :crying:

Atadie said:
Hello, guys. How you doing?
I am with a HTC ONE M7 Internation/Unlocked Soft-Bricked, with no OS... Here are some information:
- Using TWRP 2.8.7.0 custom recovery for M7 (latest version)
- Unlocked bootloader
- Rooted (at least I did it before wipping my OS)
- S-ON!
- HBOOT v.1.57
- Already have ADB/Fastboot on my PC
- Modelid: PN0711000
- Cidnum: HTC__332
There's my tale:
I tried to install RUU M7 Lollipop ROM, from HTC's website. But, at the very beggining of the instalation (4%), the RUU software said it lost my device. I did it while in fastboot mode, because it was the only way RUU recognized my phone. Then I could not install Lollipop ROM by RUU method, so I decided to flash a Lollipop ROM Unlocked Version for One M7.
I knew that for doing it I would need to install some custom recovery on my phone, unlock its bootloader mode and install on my PC ADB and Fastboot. I did all of this; the bootloader unlocked I did from HTC's website guide. So, I put on my phone a ROM in zip extension, boot it on recovery mode. I read that I should wipe data, cache, calvik cache and, maybe, system. And I did it... with NO BACKUP of original ROM --' I know I was stupid...
So I wipe this partitions, entered Install menu and tried to run instalation of the ROM zip file. It didn't work!!! Some error: "E: error executing updater binary in zip..." And I tried to flash different ROMs, all of them showed this error...
Then now I am with a Soft-Bricked HTC ONE M7 which has no OS. Some pics of my status: https: // w w w .dropbox.com/s/ruyen2ikn0u5i0u/Soft-Bricked%20M7.rar?dl=0
I hope you can help me
Click to expand...
Click to collapse
post the output of "fastboot getvar all" (remove your imei and serialno)

alray said:
post the output of "fastboot getvar all" (remove your imei and serialno)
Click to expand...
Click to collapse
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4T.28.3218.04
version-cpld: None
version-microp: None
version-main: 6.15.599.101
version-misc: PVT SHIP S-ON
serialno: ************
imei: ***************
meid: 00000000000000
product: m7_u
platform: HBOOT-8064
modelid: PN0711000
cidnum: HTC__332
battery-status: good
battery-voltage: 4322mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-6d8a0b9b
hbootpreupdate: 11
gencheckpt: 0

Could not get S-OFF
I tried getting S-OFF by Rumrunner method and didn't work :/
Hep me, guys! I really need my One back to life!!! I'm in pain :crying:

Atadie said:
I tried getting S-OFF by Rumrunner method and didn't work :/
Click to expand...
Click to collapse
You can't use rumrunner to achieve s-off on hboot 1.57, only method is Sunshine
Atadie said:
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4T.28.3218.04
version-cpld: None
version-microp: None
version-main: 6.15.599.101
version-misc: PVT SHIP S-ON
serialno: ************
imei: ***************
meid: 00000000000000
product: m7_u
platform: HBOOT-8064
modelid: PN0711000
cidnum: HTC__332
battery-status: good
battery-voltage: 4322mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-6d8a0b9b
hbootpreupdate: 11
gencheckpt: 0
Click to expand...
Click to collapse
There is not much available for 6.15.599.101 version, you'll probably need to use custom roms or convert to another version. There is a 6.15.599.101 ruu available at irfile.com but you will need an acount to download it (paid account) http://www.ir-file.com/portal/index.php?dir=Firmware/HTC/HTC_Android/M7_U/
Atadie said:
UPDATE: it's solved, i got back to stock rom after flashing this: https :// fl1.androidfilehost.com/dl/2k6GKx4IJOgIhD09zRzbzw/1441027324/95897840722641610/Reset_rom_6.07.1540.2.zip?
Now I'm going to do a BACKUP haha
Click to expand...
Click to collapse
This rom is for the Developer edition version CID BS_US001 and MID PN0712000, By flashing this on your phone, you're far from being stock, you will not get any ota updates and be stuck on this version.

alray said:
You can't use rumrunner to achieve s-off on hboot 1.57, only method is Sunshine
There is not much available for 6.15.599.101 version, you'll probably need to use custom roms or convert to another version. There is a 6.15.599.101 ruu available at irfile.com but you will need an acount to download it (paid account) http://www.ir-file.com/portal/index.php?dir=Firmware/HTC/HTC_Android/M7_U/
This rom is for the Developer edition version CID BS_US001 and MID PN0712000, By flashing this on your phone, you're far from being stock, you will not get any ota updates and be stuck on this version.
Click to expand...
Click to collapse
Oh, thanks :/
So, what is the best path to follow to get Lollipop? Should I pay 25 bucks for Sunshine, change my CID and try to flash correct Lollipop rom? Is there another way to get Lollipop rather that one?
Are there so many new and interesting features on Lollipop or should I stay on KitKat 4.4.3? I don't know so many custom good roms; can you recommend me some?
Sorry for asking so much questions. I know, probably I'm bothering you '-'
PS: Now my system asks for an OTA update to Lollipop, but it's not possible... Probably due to what you said about my flashed rom being Developer edition's one.

Atadie said:
Oh, thanks :/
So, what is the best path to follow to get Lollipop? Should I pay 25 bucks for Sunshine, change my CID and try to flash correct Lollipop rom? Is there another way to get Lollipop rather that one?
Click to expand...
Click to collapse
Either pay for sunshine so you can change your CID / MID to convert your phone to another version using a lollipop RUU or pay for an account at ir-file.com so you can download the .599 ruu and then take all ota updates.
Are there so many new and interesting features on Lollipop or should I stay on KitKat 4.4.3?
Click to expand...
Click to collapse
Many ppl likes lollipop and probably as many ppl doesn't like it. I think its better to try it yourself and see what you prefer. Some ppl likes the new features and other ones are complaining about battery drain and lags.
I don't know so many custom good roms; can you recommend me some?
Click to expand...
Click to collapse
All custom roms are good, it all depends what features you need. The best you can do is to read some rom threads and choose one that fit what you need, try it a few days and if not liking it, flash another one. If you want good battery life and no lag, I would recommend GPE roms, if you need what HTC Sense have to offer, then choose a Sense based rom like ARHD, Maximus, InsertCoin, NuSense ....
PS: Now my system asks for an OTA update to Lollipop, but it's not possible... Probably due to what you said about my flashed rom being Developer edition's one.
Click to expand...
Click to collapse
Because your CID and MID doesn't match the rom version you have flashed. Developer edition is for CID BS_US001 and MID PN0712000, yours is HTC__332 and PN0711000, In order to receive ota updates, you must be 100% stock either be flashing the .599 ruu for HTC__332 / PN0711000 or by achieving s-off, changing your CID / MID and flashing another version ruu e.g: changing your cid to BS_US001, your MID to PN0712000 and flashing a dev edition (.1540) RUU.

alray said:
All custom roms are good, it all depends what features you need. The best you can do is to read some rom threads and choose one that fit what you need, try it a few days and if not liking it, flash another one. If you want good battery life and no lag, I would recommend GPE roms, if you need what HTC Sense have to offer, then choose a Sense based rom like ARHD, Maximus, InsertCoin, NuSense ....
Click to expand...
Click to collapse
I was reading about Android Revolution HD, it seems good. I really like Blinkfeed (Highlights) so I guess I wouldn't flash a ROM which doesn't have it. I think ARHD got Blinkfeed, right?
Can I flash this ROM on my phone? As far as you know about my specs.