Related
The last time I flashed a custom rom to my phone was CyanogenMod-7.1.0-RC1-N1.
I'd really like to get ICS on it, but the process seems just so much more confusing this time around. If anyone give me a breakdown of what I'd need to do, or even if they could just point me in the right direction, I'd be grateful.
i never messed with that as they are always a lil buggy i like sense better ^_^ try asking people in that thread im sure they be happy to help you bro
sorry i couldn't help
Mintyass said:
The last time I flashed a custom rom to my phone was CyanogenMod-7.1.0-RC1-N1.
I'd really like to get ICS on it, but the process seems just so much more confusing this time around. If anyone give me a breakdown of what I'd need to do, or even if they could just point me in the right direction, I'd be grateful.
Click to expand...
Click to collapse
There are at least 3 ICS ROMs with 2 are in the working progress and the other we don't know what is the status of it. Spend some time to read first to gain some knowledge and procedures. They are in the Development section of Nexus One. And, remember, once you have Ice Cream Sandwich you don't want to have Gingerbread
u can flash this miui ics as like anyother roms before
http://forum.xda-developers.com/showthread.php?t=1479348
but for other ics roms u need to partition /system. for that first u need to know abt blackrose.
http://forum.xda-developers.com/showthread.php?t=1270589
Sent from my Nexus One using Tapatalk
The process is actually easier than the process you went through to root your phone and install CM7.
First, download the ICS firmware zip file to your phone's sdcard.
Next, make your backup using TitaniumBackup.
For most ICS firmware, you'll need to repartition your hboot. Google for blackrose-manual_120216.zip, download to your computer, unzip and look for the hboot_brcust-220-10-206.nb0 file. This one is pre-configured with the right partition sizes. Follow the instructions in the README file, which are basically:
Update your recovery firmware, by downloading to your computer and then using fastboot from your computer. I used the Amon-RA recovery for CM and stayed with it for ICS.
On the phone, enable USB Debugging in the CM Developer settings menu.
Boot the phone into the bootloader and go to FastBoot mode. It'll tell you what HBOOT you currently have. Read the instructions in the blackrose README to see which (if any) of the goXX.lol files you need. Then, on the computer:
Code:
fastboot flash recovery goXX.lol
fastboot flash recovery recovery-RA-passion-v2.2.1.img
Next, flash the new hboot:
Code:
fastboot flash hboot hboot_brcust-220-10-206.nb0
The blackrose-manual zip contains fastboot binaries for Linux, Mac and Windows. If you need a fastboot for FreeBSD, send me a PM.
Then boot into recovery, do a Nandroid backup, then a full wipe, then install the ICS firmware zip you put on the sdcard earlier.
That should be all. Once the new system is booted, you'll use Titanium again to restore your apps.
For what it's worth, the BCM firmware is based on CM with all the CM additions you're used to, so things will be pretty familiar. It's running well for me.
Jaiy said:
The process is actually easier than the process you went through to root your phone and install CM7.
First, download the ICS firmware zip file to your phone's sdcard.
Next, make your backup using TitaniumBackup.
For most ICS firmware, you'll need to repartition your hboot. Google for blackrose-manual_120216.zip, download to your computer, unzip and look for the hboot_brcust-220-10-206.nb0 file. This one is pre-configured with the right partition sizes. Follow the instructions in the README file, which are basically:
Update your recovery firmware, by downloading to your computer and then using fastboot from your computer. I used the Amon-RA recovery for CM and stayed with it for ICS.
On the phone, enable USB Debugging in the CM Developer settings menu.
Boot the phone into the bootloader and go to FastBoot mode. It'll tell you what HBOOT you currently have. Read the instructions in the blackrose README to see which (if any) of the goXX.lol files you need. Then, on the computer:
Code:
fastboot flash recovery goXX.lol
fastboot flash recovery recovery-RA-passion-v2.2.1.img
Next, flash the new hboot:
Code:
fastboot flash hboot hboot_brcust-220-10-206.nb0
The blackrose-manual zip contains fastboot binaries for Linux, Mac and Windows. If you need a fastboot for FreeBSD, send me a PM.
Then boot into recovery, do a Nandroid backup, then a full wipe, then install the ICS firmware zip you put on the sdcard earlier.
That should be all. Once the new system is booted, you'll use Titanium again to restore your apps.
For what it's worth, the BCM firmware is based on CM with all the CM additions you're used to, so things will be pretty familiar. It's running well for me.
Click to expand...
Click to collapse
Restore apps from GB backup might bring FC. It is better to download them from the Google Play
taodan said:
Restore apps from GB backup might bring FC. It is better to download them from the Google Play
Click to expand...
Click to collapse
While, in theory, you are correct, I restored my GB apps using TB because it is very fast to do so. In practice, they all appear to be working just fine. I believe I have run every one of them to make sure.
But I agree that a better general procedure would be to restore the apps themselves from the Play Store then restore your former app data using TB.
Jaiy said:
The process is actually easier than the process you went through to root your phone and install CM7.
First, download the ICS firmware zip file to your phone's sdcard.
Next, make your backup using TitaniumBackup.
For most ICS firmware, you'll need to repartition your hboot. Google for blackrose-manual_120216.zip, download to your computer, unzip and look for the hboot_brcust-220-10-206.nb0 file. This one is pre-configured with the right partition sizes. Follow the instructions in the README file, which are basically:
Update your recovery firmware, by downloading to your computer and then using fastboot from your computer. I used the Amon-RA recovery for CM and stayed with it for ICS.
On the phone, enable USB Debugging in the CM Developer settings menu.
Boot the phone into the bootloader and go to FastBoot mode. It'll tell you what HBOOT you currently have. Read the instructions in the blackrose README to see which (if any) of the goXX.lol files you need. Then, on the computer:
Code:
fastboot flash recovery goXX.lol
fastboot flash recovery recovery-RA-passion-v2.2.1.img
Next, flash the new hboot:
Code:
fastboot flash hboot hboot_brcust-220-10-206.nb0
The blackrose-manual zip contains fastboot binaries for Linux, Mac and Windows. If you need a fastboot for FreeBSD, send me a PM.
Then boot into recovery, do a Nandroid backup, then a full wipe, then install the ICS firmware zip you put on the sdcard earlier.
That should be all. Once the new system is booted, you'll use Titanium again to restore your apps.
For what it's worth, the BCM firmware is based on CM with all the CM additions you're used to, so things will be pretty familiar. It's running well for me.
Click to expand...
Click to collapse
This is great! I found blackrose_manual_120216.zip, but the only .nb0 file in it was hboot_blackrose.nb0. Will this work, or do I need to keep looking?
Mintyass said:
This is great! I found blackrose_manual_120216.zip, but the only .nb0 file in it was hboot_blackrose.nb0. Will this work, or do I need to keep looking?
Click to expand...
Click to collapse
The instructions are in the Blackrose thread in the Development section, you don't need to use the manual if you're using Windows.
I would read the blackrose thread so you understand what you are doing and why. Easier to get out of trouble and harder to get into it. You probably did same for CM7. The blackrose hboot is not easy to work with without knowing what you are doing. The backrose thread has pre requisites in OP, like install of drivers if you don't have them.
You guys sure the fastboot command for the exploit has the word "recovery" in it or should be:
fastboot boot go.lol
where go.lol is exact name of exploit from the actual blackrose binary folder depending what version of blackrose you are fastbooting. could be "fastboot boot go2.lol" etc
just a suggestion--
So I was able to use blackrose to repartition my system cache, but now I've got a problem. In the bootloader, when I select "Recovery" the phone hangs on the Nexus "X" logo, and I'm unable to get my phone to reboot into anything but the bootloader.
you probably lost recovery and need to re fastboot it
i once had to fastboot erase system before the recovery would flash
all these issues are in the thread
Would this be the correct thing to do? http://forum.xda-developers.com/wiki/HTC_Nexus_One/Recovery_Images
good info but if you have sdk and know fastboot do this
Copy recovery-RA-passion-v2.2.1.img to a location where fastboot can find it. Usually tools folder.
Boot your phone into fastboot mode (power on while holding the trackball)
Connect your phone via usb to your pc
type fastboot devices (to make sure that fastboot "sees" your phone)
type fastboot flash recovery recovery-RA-passion-v2.2.1.img or whatever exact name your recovery is
I was able to get into recovery, but now when I select "Flash zip from sdcard", I get an error saying that there was No Signature and that the Verification Failed.
Mintyass said:
I was able to get into recovery, but now when I select "Flash zip from sdcard", I get an error saying that there was No Signature and that the Verification Failed.
Click to expand...
Click to collapse
You need to disable the signature verification in the recovery and then flash the ROM
Thanks so much for everyone's help! I've got ICS up and running now thanks to you.
Since this forum account is too new to post in the BCM thread, I guess I'll try asking a question here instead.
So far there's two problems I've encountered that would be dealbreakers for BCM. I saw on the BCM thread that voice search is currently broken, but it seems like it's kind of unexpected and will likely be fixed. The other issue I have, that I can't find anyone else complaining about, is that I don't seem to have the Car Home app anymore. Has anybody else run into this issue, or know a fix? I use my phone in my car pretty much every day in my car dock, and make extensive use of both the car home app and the voice search feature for getting navigation directions.
If there's a better place to post these questions, feel free to let me know!
Thanks
audio has been ab issue for me and others on ics and sense roms lately, don't know why. i am back on CM7 Kangs atm bc of it. hope it is found and fixed. the current remedies don't work for me
glad you are up and running, all these roms have issues of some type for a few at least. goes with the territory--
someone should be able to get you a car home apk you can install or push thru adb--i always delete mine as i don't use--sorry. might be able to find it thru search/google
posting here is perfectly fine--it a couple general threads for a "meaningful" post and you will be to ten real quick
enjoy rom
ken
Mintyass said:
This is great! I found blackrose_manual_120216.zip, but the only .nb0 file in it was hboot_blackrose.nb0. Will this work, or do I need to keep looking?
Click to expand...
Click to collapse
Sorry, I wasn't watching this thread over the weekend and I see you have already moved past this. But to answer the question...
I thought the pre-partitioned blackrose-220-10-206 was in that zip, but I see now that I found it on the Evervolv ROM thread in the Nexus One development forum. Sorry for not remembering to mention that.
---------- Post added at 12:08 PM ---------- Previous post was at 11:58 AM ----------
Mintyass said:
Thanks so much for everyone's help! I've got ICS up and running now thanks to you.
Click to expand...
Click to collapse
You're welcome.
So far there's two problems I've encountered that would be dealbreakers for BCM. I saw on the BCM thread that voice search is currently broken, but it seems like it's kind of unexpected and will likely be fixed. The other issue I have, that I can't find anyone else complaining about, is that I don't seem to have the Car Home app anymore. Has anybody else run into this issue, or know a fix? I use my phone in my car pretty much every day in my car dock, and make extensive use of both the car home app and the voice search feature for getting navigation directions.
Click to expand...
Click to collapse
BCM Version RC3.3Ux has very broken voice input. Many folk (including me) have commented that no VoIP apps work with it. Hopefully this will be fixed soon. BCM3.2U2 works fine, so I have reverted to that version for now.
You can install the CarHome app from the Play Store; it doesn't seem to be included in the BCM zip file.
My question is similar to 'nikpmr's troubles but different enough I think they deserve a separate post.
The Problem as UnderstoodI was trying to root my device following the guide at this website. It's so simple it's a wonder I messed up. I think my failure was that I thought the drivers installed when I connected the phone were enough so I skipped that step. Then when running fastboot flash recovery.img the install failed. So I saw on some forum that it was supposed to be fastboot flash boot recovery.img of course now I know if anything it ought to have been "recovery" not "boot".
What I've Tried & Partial SolutionAt first I was just stuck in a boot loop and selecting "sideload" from the CWM recovery failed to allow me to connect with ADB or fastboot. i.e. Running "fastboot devices" and "adb devices" both returned as having no devices connected to my computer. So I installed the HTC Sync and promptly uninstalled the non driver parts of the app. Then I installed USBdeview and used it to uninstall all the USB devices associated with my HTC First. After doing that I learned booting into HBOOT allowed me to connect to the computer using fastboot and after then booting to the CWM Recovery I was able to connect using ADB to do a sideload. So I guess I'm about halfway there. Unfortunately after looking up the newest RUU and attempting to sideload it using "adb sideload OTA_MYST_UL_1.08.502.1-1.08.502.4.zip" the sideload failed. After selecting "- install zip from sideload" I get a message twice of "failed to open driver control: No such file or directory". It also failed when I attempted it with a similar fastboot command. So from all that I surmise my ROM is ruined and just needs to be replaced.
QuestionSo how do I go about replacing this ROM and boot partition? And, which ROM should I use? Is the one I got from the RUU site suitable? And what about the radio? I just need my phone to work. I can worry about rooting later. At this point I think I know what's happened but I don't know where to begin reading to figure out how to fix it myself.
Thanks for reading,
Relevant HBOOT text:
Code:
*** TAMPERED ***
*** UNLOCKED ***
MYSTUL PVT SHIP S-ON RL
HBOOT-2.00.0000
RADIO-1.15.40.00.13_2
OpenDSP-v9.2.0268.1214
eMMC-boot
Mar 22 2013,21:29:50:1682
1. you had to type in fastboot flash recovery recovery.img NOT fastboot flash boot recovery.img
Well there was an actual all in 1 tool to get cwm/twrp & root with a click for this specific device somewhere around these threads.
1) what exactly is the problem? (Sorry it was just so many words)
I don't think side loading the RUU would work bc I haven't heard its possible to flash it in the phone itself.
2) why don't you just sideload an existing pre-rooted ROM instead of the RUU file?
3) I see you're s-on, did you try flashing just the boot.IMG from the ROM you've got on it?
BTW I've only had luck with twrp on having it successfully detected when wanting to sideload
abrahammmmmmm_ said:
Well there was an actual all in 1 tool to get cwm/twrp & root with a click for this specific device somewhere around these threads.
1) what exactly is the problem? (Sorry it was just so many words)
I don't think side loading the RUU would work bc I haven't heard its possible to flash it in the phone itself.
2) why don't you just sideload an existing pre-rooted ROM instead of the RUU file?
3) I see you're s-on, did you try flashing just the boot.IMG from the ROM you've got on it?
BTW I've only had luck with twrp on having it successfully detected when wanting to sideload
Click to expand...
Click to collapse
1) The issue is I did "fastboot flash boot recovery.img" rather than "fastboot flash recovery.img" now I don't seem to have a boot mount point.
2) That sounds best. I didn't realize the RUU want a flashable ROM. More I just have to find the updated stable stock ROM.
3) I didn't have a ROM on it. I was just trying to root stock. Seems like I'm pretty close once I find that ROM.
Thanks y'all! Between your answers I think I have enough to go on. Feel free to point me to your preferred stable ROM. I'm content with stock but it would be nice to have Tiranium BU.
bnjo said:
1) The issue is I did "fastboot flash boot recovery.img" rather than "fastboot flash recovery.img" now I don't seem to have a boot mount point.
2) That sounds best. I didn't realize the RUU want a flashable ROM. More I just have to find the updated stable stock ROM.
3) I didn't have a ROM on it. I was just trying to root stock. Seems like I'm pretty close once I find that ROM.
Thanks y'all! Between your answers I think I have enough to go on. Feel free to point me to your preferred stable ROM. I'm content with stock but it would be nice to have Tiranium BU.
Click to expand...
Click to collapse
Right now our most stable stock ROM is our rooted stock ROM
http://forum.xda-developers.com/showthread.php?t=2287811
We currently have 2 very able recognized devs working on CyanogenMod. You can expect something new in the near future but until then what I've showed you is the best.
Have any problems just come back to the thread
Success!
abrahammmmmmm_ said:
Right now our most stable stock ROM is our rooted stock ROM
http://forum.xda-developers.com/showthread.php?t=2287811
We currently have 2 very able recognized devs working on CyanogenMod. You can expect something new in the near future but until then what I've showed you is the best.
Have any problems just come back to the thread
Click to expand...
Click to collapse
Thanks guys I know I always like to know when something I said was successful in helping someone. I just wanted yall to know after sideloading the most recent Odexed ROM then pushing it to memory after it wouldn't boot I succeeded after taking abrahammmmmm's advice of flashing the boot.img from HBOOT. After a longer boot than I'm used to I was able to get into my phone again. I wasn't able to use my TitaniumBU to restore but that just meant I had to spend a few minutes selecting apps to install.. And restoring a data backup for the only important app that doesn't keep the primary data off the phone.
Thanks again!
tl;dr Flashing the Odexed ROM boot.img fixed my issues. Thx!
bnjo said:
Thanks guys I know I always like to know when something I said was successful in helping someone. I just wanted yall to know after sideloading the most recent Odexed ROM then pushing it to memory after it wouldn't boot I succeeded after taking abrahammmmmm's advice of flashing the boot.img from HBOOT. After a longer boot than I'm used to I was able to get into my phone again. I wasn't able to use my TitaniumBU to restore but that just meant I had to spend a few minutes selecting apps to install.. And restoring a data backup for the only important app that doesn't keep the primary data off the phone.
Thanks again!
tl;dr Flashing the Odexed ROM boot.img fixed my issues. Thx!
Click to expand...
Click to collapse
Great! glad to hear I could help. Yes it's always nice knowing when something I've said has helped someone in any way
bnjo said:
Thanks guys I know I always like to know when something I said was successful in helping someone. I just wanted yall to know after sideloading the most recent Odexed ROM then pushing it to memory after it wouldn't boot I succeeded after taking abrahammmmmm's advice of flashing the boot.img from HBOOT. After a longer boot than I'm used to I was able to get into my phone again. I wasn't able to use my TitaniumBU to restore but that just meant I had to spend a few minutes selecting apps to install.. And restoring a data backup for the only important app that doesn't keep the primary data off the phone.
Thanks again!
tl;dr Flashing the Odexed ROM boot.img fixed my issues. Thx!
Click to expand...
Click to collapse
i think what happened, when you typed in "fastboot flash boot recovery.img" is this
boot, is also known as kernel in aosp and rom building terms, because if you look inside a rom.zip, you will see that the kernel is the boot.img
so what happened is you flashed a recovery as kernel, and duh it wont boot cause if the kernel doesnt work, the os doesnt either
so what YOU did is you simply reflashed the stock kernel, usually after changing a kernel, it takes a while to boot cause...well you get it right?
the kernel is what android is based off of, kind of like ubuntu, its a linux os based on the original linux kernel.
russian392 said:
usually after changing a kernel, it takes a while to boot cause...well you get it right?
Click to expand...
Click to collapse
Yes I get it.
russian392 said:
i think what happened, when you typed in "fastboot flash boot recovery.img" is this
boot, is also known as kernel in aosp and rom building terms, because if you look inside a rom.zip, you will see that the kernel is the boot.img
so what happened is you flashed a recovery as kernel, and duh it wont boot cause if the kernel doesnt work, the os doesnt either
so what YOU did is you simply reflashed the stock kernel, usually after changing a kernel, it takes a while to boot cause...well you get it right?
the kernel is what android is based off of, kind of like ubuntu, its a linux os based on the original linux kernel.
Click to expand...
Click to collapse
That's what I thought happened. If I had stopped to read the help on fastboot before running "fastboot flash boot recovery.img" I wouldn't have made that mistake because I would have seen I wanted to flash recovery. One thing I *did not* know, which I'm glad to know, was that the boot.img contains the kernal. I was thinking Android was more similar to IBM style PCs than it is and therefore the boot.img was analogous to a bootloader like grub or lilo.
So the one thing I don't get is how is partitioning done? I take it Androids have some reserved partition for boot and the boot.img takes care of all system partitioning and mounts /sdcard/ for everything else. i.e. userland; appdata, media, and files. Am I guessing correctly?
bnjo said:
So the one thing I don't get is how is partitioning done? I take it Androids have some reserved partition for boot and the boot.img takes care of all system partitioning and mounts /sdcard/ for everything else. i.e. userland; appdata, media, and files. Am I guessing correctly?
Click to expand...
Click to collapse
in a nutshell yes, the boot.img uses the fstab
btw 10 posts you'll be "verified"
So the one thing I don't get is how is partitioning done? I take it Androids have some reserved partition for boot and the boot.img takes care of all system partitioning and mounts /sdcard/ for everything else. i.e. userland; appdata, media, and files. Am I guessing correctly?
Click to expand...
Click to collapse
Yep that's correct.
The name correlation is booting up requires kernel there for kernel is called beet.IMG
Thing about custom kernels, they aren't like that and simply contain modded files and pretty much an in packaged kernel.
Sent from my HTC first using xda app-developers app
stock recovery
please can anyone send me the stock recovery.img
when i try to get it from RUU it says archive is corrupted
astrit1995 said:
please can anyone send me the stock recovery.img
when i try to get it from RUU it says archive is corrupted
Click to expand...
Click to collapse
here:
http://androidfiles.org/getdownload.php?file=MystUL/Stock_Roms/stockrecovery.img
if you help, press thanks!!
Serupo said:
here:
http://androidfiles.org/getdownload.php?file=MystUL/Stock_Roms/stockrecovery.img
if you help, press thanks!!
Click to expand...
Click to collapse
Thank you for your help,i solved my problem yesterday but i think im gona need this sometime...
My friend's phone is stuck in bootloop and I believe it's soft bricked.
It's a stock brand new HTC One M7.
It was updating one day and he said it might have got corrupted because it just shut down and when it booted back up it was stuck at the HTC Screen and wouldn't do anything.
Over the last week I have been trying to unbrick it.
It's LOCKED and S-ON Sprint HTC One M7.
I did a factory reset, wiped cache, dalvic cache, reboot. I tried putting in fastboot and flashing RUU on it but it kept failing because the RUU I had was a lower version of the image than the current one on the phone and I read online that I can only flash backwards if it's S-OFF.
Any help?
Thanks!
technocrat7 said:
My friend's phone is stuck in bootloop and I believe it's soft bricked.
It's a stock brand new HTC One M7.
It was updating one day and he said it might have got corrupted because it just shut down and when it booted back up it was stuck at the HTC Screen and wouldn't do anything.
Over the last week I have been trying to unbrick it.
It's LOCKED and S-ON Sprint HTC One M7.
I did a factory reset, wiped cache, dalvic cache, reboot. I tried putting in fastboot and flashing RUU on it but it kept failing because the RUU I had was a lower version of the image than the current one on the phone and I read online that I can only flash backwards if it's S-OFF.
Any help?
Thanks!
Click to expand...
Click to collapse
if the phone is new (never tampered with) and still under warranty, send it back for repair or replacement
s-off and run the ruu
unlock bootloader, flash a custom recovery and flash a rom or a nandroid backup
post in the sprint htc one forum for more detailed info
So the first step is S-OFF because I don't think k the warranty is on it.
And then custom recovery and what was the part with a custom nandroid backup? Can I run someone else's nandroid?
And if I put S-OFF on it, I can flash an older version of RUU right?
Sent from my HTC One_M8 using XDA Free mobile app
I'm pretty sure that in order to S-off you will need to be booted up first? The good news is that you can flash the full factory RUU with a s-on boot loader locked device so you may need to figure out how to do that first. Do you have an adb/fastboot environment set up? If so you are practically there. On a side note, I have seen no less than 3 m7s fail and softbrick on the first attempt at applying an ota, but it was always after S-off and a conversion to fully stock gpe (these were gsm models). I figured it was just because of the mods but who knows. Anyway, if you can locate and install a fully stock sprint RUU you should be back to where you were before the ota at which point you can proceed with whatever else you want to do.
technocrat7 said:
So the first step is S-OFF because I don't think k the warranty is on it.
And then custom recovery and what was the part with a custom nandroid backup? Can I run someone else's nandroid?
And if I put S-OFF on it, I can flash an older version of RUU right?
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
sorry for the confusion, this was not steps to follow (1-2-3-4) but either 1 or 2 or 3 or 4
if you go for option 2, yes you can flash older ruu.
for option 3, yes you can flash someone else nandroid, but it must be for your phone variant (sprint) and the ideal nandroid backup should be the same OS version.
---------- Post added at 02:34 PM ---------- Previous post was at 02:29 PM ----------
dougeedug said:
I'm pretty sure that in order to S-off you will need to be booted up first?
Click to expand...
Click to collapse
Right, you need a booted rom to s-off. (at least for the M7_UL dont know for the srpint variant)
The good news is that you can flash the full factory RUU with a s-on boot loader locked device so you may need to figure out how to do that first.
Click to expand...
Click to collapse
Not exactly, you can only flash ruu with a s-on device (and locked/relocked bootloader) if the ruu is same of higher version. In that case the OP need to find another ruu (if any available)
Yeah, I have a 4.2 image when loading RUU, therefore I'm not able to use an RUU.
So what else do I need to do?
And I do have an adb and fastboot environment set up, yes.
Should I instead just S-OFF It, put a custom bootloader on it and then flash a custom recovery?
Yes if you can achieve s-off you can put any RUU you want on it and that will rule out software issues.
Okay so I unlocked it.
However I looked online how to do S-OFF and all the articles I found said the phone has to be on an functional to enable USB debugging mode and to run the appropriate programs to make it S-OFF.
Is there any other way to do it?
Now that you are bootloader unlocked, flash a custom recovery and from there a rom. That should get you back to life so you can proceed however you wish.
I have a custom recovery.
TWRP 2.6.0.0 or something. And I loaded into it and my phone got stuck and the touch wouldn't work. It says "slide to unlock" and sliding doesn't work.
What do I do now? I can't even reboot the light keeps flashing and I even tried under a bright light and still nothing.
I'm letting the battery die to restart. When u do restart it, what do I do about the bad bootloader? Can I just put another one on there? I want Philz now after that terrible experience.
technocrat7 said:
I have a custom recovery.
TWRP 2.6.0.0 or something. .
Click to expand...
Click to collapse
This is very alarming! Be double sure you are flashing exactly what you need. The CWM you would need is 6.0.4.8 found on this page. I'm not sure what TWRP version is suitable as I don't use it. I don't dislike it. I have used it and it has worked.
Can I just do the same thing I did before to install a custom recovery?
Will it override the one I have currently?
Thanks!
technocrat7 said:
Can I just do the same thing I did before to install a custom recovery?
Will it override the one I have currently?
Thanks!
Click to expand...
Click to collapse
We will have to see what it does after you let it die. The way your phone is acting is not good. Unfortunately, we must keep in mind that it may be a hardware fault causing all of this from the start. If it will still charge offline, then you'll get a chance to see if you can power it up into the bootloader and get fastbootUSB.
technocrat7 said:
Can I just do the same thing I did before to install a custom recovery?
Will it override the one I have currently?
Thanks!
Click to expand...
Click to collapse
why are you waiting for it to die ? if you want to get out of recovery and tough isn't working, just hold down the power button and the volume down until the lights on the bottom flash 10 to 15 times, when it goes off, release the power button but continue to hold the volume down, you are now in the bootloader, or should be.
and yes, if you flash another recovery it will overwrite the one that's on there, unfortunately, most rom's require TWRP
---------- Post added at 03:28 AM ---------- Previous post was at 03:22 AM ----------
I also just noticed you have the Sprint M7, you cant use the normal recoveries or rom's, they wont work, you need to use the ones built for your phone, which is different to the normal gsm version.
I would try twrp 2.6.3.3 or this http://mdmower.cmphys.com/twrp-m7spr/ a newer custom compiled twrp so your os version dont get wiped on bootloader.
Dang, being with Sprint complicates things?
So will that one be safe to put on my phone? And that means I can't get Philz huh?
technocrat7 said:
Dang, being with Sprint complicates things?
So will that one be safe to put on my phone? And that means I can't get Philz huh?
Click to expand...
Click to collapse
No it doesn't complicate things, it's the same procedure, it's like with anything, you just have to make sure you get the right files. Your phone is cdma not gsm.
---------- Post added at 04:28 AM ---------- Previous post was at 04:17 AM ----------
http://forum.xda-developers.com/sprint-htc-one?nocache=1&z=1858146956656128
You can find all of those right files there
Okay thank you!
It is unlocked, rooted and had a custom recovery on it!
Now the last thing I need help with is, getting S-OFF because I still can't boot up the phone.
So now I just need to get S-OFF and then flash a custom ROM image on there and flash a custom image on it or something.
All I see when it boots up is the HTC screen.
technocrat7 said:
Okay thank you!
It is unlocked, rooted and had a custom recovery on it!
Now the last thing I need help with is, getting S-OFF because I still can't boot up the phone.
So now I just need to get S-OFF and then flash a custom ROM image on there and flash a custom image on it or something.
All I see when it boots up is the HTC screen.
Click to expand...
Click to collapse
You need a working Rom on it to go s-off, all s-off tools are run from an android booted phone, so download a Rom of your choice, in your case a sense Rom, make sure you get it from the link I supplied earlier for your particular phone, move it to the same folder where your adb and fastboot are on your computer, boot your phone into recovery (main screen only, no sub menus) and plug it into your computer, the type
adb push NAME_OF_ROM.zip /sdcard/
Takes a while so be patient, the command window will let you know when it's done.
Unplug your phone and in recovery select install, select your Rom from the list and follow the instructions
Seanie280672 said:
You need a working Rom on it to go s-off, all s-off tools are run from an android booted phone, so download a Rom of your choice, in your case a sense Rom, make sure you get it from the link I supplied earlier for your particular phone, move it to the same folder where your adb and fastboot are on your computer, boot your phone into recovery (main screen only, no sub menus) and plug it into your computer, the type
adb push NAME_OF_ROM.zip /sdcard/
Takes a while so be patient, the command window will let you know when it's done.
Unplug your phone and in recovery select install, select your Rom from the list and follow the instructions
Click to expand...
Click to collapse
So there's a slight problem.
"ADB Devices" doesn't show anything, it says "Devices not found"
The reason I would say is because it does not have USB Debugging enabled.
And I can't get into the phone to enable it because i'm not at that point yet.
Is there anything else I can do besides "adb push" to get the file on there?
Fastboot stuff works fine.
I went to the link you provided and found CynogenMod 11 I wanted to put on there.
After looking inside of the ZIP I downloaded there's a .img file inside called "boot.img" can I do anything with that?
Thanks!
Hi, Gang... Please be patient as I'm not normally playing at this level...
I recently had a kid kill my TF700 so I bought at TF701 as a replacement. I immediately unlocked it, forgetting to take the latest Asus update OTA beforehand. Anyways, I manually downloaded v11.4..1.17 and put it on a blank microSD and stuck it into the tablet where the update was recognized as available and I set the update in motion... Something went sideways after I walked away to let the update run and now I can't get back into the system and I can't get into recovery.
I have the bootloader up (1.00e as released by 10.14.1.47) and I can communicate with the device via fastboot. Can someone help me wipe and get a recovery.img and/or a full stock image onto this thing. Right now it just keeps rebooting unless I manually force it to the bootloader.
I'm hoping someone more knowledgeable can chastise me for being a moron an point me in the right direction. Ultimately, I was tying to get to the latest ASUS ROM to the the bootloader that goes with it and then move onto a custom ROM.
Many thanx.
Im no help. Dont listen to me. Try using fastboot to run a recovery. "fastboot boot recovery.img" from the bootloader. Maybe with that old bootloader you should be using an old recovery maybe.
---------- Post added at 08:27 PM ---------- Previous post was at 08:19 PM ----------
I wouldnt flash a recovery/bootloader especially the new ones til you can verify an older recovery works. Try booting this one https://www.dropbox.com/s/il2m4rtxlmzjfz9/recovery.img but dont flash til someone else takes a look at this. This is an old philz touch without touch.
Still nothing...
YayYouFixedIt said:
Im no help. Dont listen to me. Try using fastboot to run a recovery. "fastboot boot recovery.img" from the bootloader. Maybe with that old bootloader you should be using an old recovery maybe.
I'm really starting to get frustrated... (understatement)
I've got a copy of the 4.4.2 OTA image (zip and recovery.img). Should I not be able to use ADB to copy the image to the device and then boot the recovery.img? I can get the tablet to respond to fastboot but I can't get it to be recognized by ADB.
I've never had issues with custom ROMs before. This time I'm wading into unfamiliar waters. I'm note even sure how the initial update failed. Is there a way for me to update the bootloader, then add a CWM recovery, then load the ROM?
Again sorry to have to ask but any help would greatly be appreciated.
Click to expand...
Click to collapse
kartman_canada said:
YayYouFixedIt said:
Im no help. Dont listen to me. Try using fastboot to run a recovery. "fastboot boot recovery.img" from the bootloader. Maybe with that old bootloader you should be using an old recovery maybe.
I'm really starting to get frustrated... (understatement)
I've got a copy of the 4.4.2 OTA image (zip and recovery.img). Should I not be able to use ADB to copy the image to the device and then boot the recovery.img? I can get the tablet to respond to fastboot but I can't get it to be recognized by ADB.
I've never had issues with custom ROMs before. This time I'm wading into unfamiliar waters. I'm note even sure how the initial update failed. Is there a way for me to update the bootloader, then add a CWM recovery, then load the ROM?
Again sorry to have to ask but any help would greatly be appreciated.
Click to expand...
Click to collapse
Where did you get the full firmware update you tried to flash?
I can't find a recovery that is compatible with that old bootloader, so your best bet would be to update via Asus firmware.
What happens if you choose RCK in the bootloader menu? Is the stock recovery still working?
What's your SKU?
If the manual stock update doesn't work you may have to flash the system blob in fastboot, but answer above questions first and then we'll see.
If you're getting frustrated, stop and come back to it later. Don't do anything desperate! No reason for it yet.
Click to expand...
Click to collapse
kartman_canada said:
YayYouFixedIt said:
Im no help. Dont listen to me. Try using fastboot to run a recovery. "fastboot boot recovery.img" from the bootloader. Maybe with that old bootloader you should be using an old recovery maybe.
I'm really starting to get frustrated... (understatement)
I've got a copy of the 4.4.2 OTA image (zip and recovery.img). Should I not be able to use ADB to copy the image to the device and then boot the recovery.img? I can get the tablet to respond to fastboot but I can't get it to be recognized by ADB.
I've never had issues with custom ROMs before. This time I'm wading into unfamiliar waters. I'm note even sure how the initial update failed. Is there a way for me to update the bootloader, then add a CWM recovery, then load the ROM?
Again sorry to have to ask but any help would greatly be appreciated.
Click to expand...
Click to collapse
https://www.dropbox.com/s/il2m4rtxlmzjfz9/recovery.img
download this recovery(which is an older one compatable with that bootloader and try fastboot boot recovery.img from your older bootloader.
It should work. If you can determine that it works and all your partitions are intact. The command is" fastboot flash recovery recovery.img" I would think if you can simply get this one to boot it will be ok to flash and you should be able to flash whatever you want. Namely you will want to flash the new bootloader and recovery from the flashable zip that sbdags provides from his optimized asus stock.
If you have to adb sideload a rom from within the recovery. Then download just use the cm11 rom for now because the asus stock is over a gig and and might not sideload. the asus stock sbdags provides in this forum.
Otherwise you might be able to flash things from the microsd card.
Than if you decide to go the cm11 route. just download the asus stock from this forum from inside the rom. Be careful.
Click to expand...
Click to collapse
Fixed!
YayYouFixedIt said:
kartman_canada said:
download this recovery(which is an older one compatable with that bootloader and try fastboot boot recovery.img from your older bootloader.
It should work. If you can determine that it works and all your partitions are intact. The command is" fastboot flash recovery recovery.img" I would think if you can simply get this one to boot it will be ok to flash and you should be able to flash whatever you want. Namely you will want to flash the new bootloader and recovery from the flashable zip that sbdags provides from his optimized asus stock.
If you have to adb sideload a rom from within the recovery. Then download just use the cm11 rom for now because the asus stock is over a gig and and might not sideload. the asus stock sbdags provides in this forum.
Otherwise you might be able to flash things from the microsd card.
Than if you decide to go the cm11 route. just download the asus stock from this forum from inside the rom. Be careful.
Click to expand...
Click to collapse
Managed to fastboot to the older recovery.img. As per instructions, I then flashed the latest bootloader and recovery from sbdags. I'm now good to go with whatever ROM I want. Many thanx! I'd still like to know how the upgrade to the latest Asus update screwed up. I wasn't watching it after setting the update in motion so it's a mystery. All I know is that the unit was plugged in so it wouldn't run out of juice and when I came back to check it, it wouldn't boot to Android, I couldn't get to recovery, and it would just keep rebooting in a loop.
Lucky for me it was unlocked and I had fastboot access to the (albeit out-of-date) bootloader.
All good now. Cheers.
Click to expand...
Click to collapse
kartman_canada said:
YayYouFixedIt said:
Managed to fastboot to the older recovery.img. As per instructions, I then flashed the latest bootloader and recovery from sbdags. I'm now good to go with whatever ROM I want. Many thanx! I'd still like to know how the upgrade to the latest Asus update screwed up. I wasn't watching it after setting the update in motion so it's a mystery. All I know is that the unit was plugged in so it wouldn't run out of juice and when I came back to check it, it wouldn't boot to Android, I couldn't get to recovery, and it would just keep rebooting in a loop.
Lucky for me it was unlocked and I had fastboot access to the (albeit out-of-date) bootloader.
All good now. Cheers.
Click to expand...
Click to collapse
Good to hear. For the Asus updates you just put them in /sdcard and reboot dont you? Its fairly automatic wasnt it? Then unlock after being updated? What went wrong in your case, Hard for me to say i guess because I and others unlocked at or before 4.3.
Click to expand...
Click to collapse
Hi so im new to HTC modding, i bought second handed M7, its complete stock.
I want elementalx kernel (i suppose its best ? ) to have htc logo functional (and also little underclock etc for battery saving).
Is there any step by step guide for do that, with no screw anything ?
(mine is M7_UL)
mmm273 said:
Hi so im new to HTC modding, i bought second handed M7, its complete stock.
I want elementalx kernel (i suppose its best ? ) to have htc logo functional (and also little underclock etc for battery saving).
Is there any step by step guide for do that, with no screw anything ?
(mine is M7_UL)
Click to expand...
Click to collapse
There isn't much more to say about the install process than what's already said in ElementalX thread:
INSTALLATION
1. Install zip from recovery
2. Follow the instructions, if you don't know what to do, use the preselected options
3. Reboot
Click to expand...
Click to collapse
Your bootloader can be unlocked using instructions at www.htcdev.com/bootloader
Twrp recovery is flashed using fastboot in bootloader mode:
Code:
fastboot flash recovery twrp-3.2.1-0-m7.img
fastboot erase cache
fastboot reboot-bootloader
and finally save the correct elementalX version on your phone storage and install with twrp.
ok but in future how i recover stock recovery and kernel ?
@mmm273
mmm273 said:
ok but in future how i recover stock recovery and kernel ?
Click to expand...
Click to collapse
It's very easy. Just go into fastboot mode, switch into RUU mode via "htc_fastboot.exe", install the stock RUU zipfile even via "htc_fastboot.exe" and that's it. In the HTC stock RUU-zips everything is included, even stock recovery, kernel, and so on...
I recommend for ALL fastboot-operations with HTC devices to use the special "htc_fastboot.exe", it works smooth for me.
Code:
htc_fastboot.exe oem rebootRUU
Wait for the silver HTC progress bar, then:
Code:
htc_fastboot.exe flash zip PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.2_Radio_4T.35.3218.16_10.33Q.1718.01L_release_421790_signed.zip
If this step failed after installing "pre-update" hboot, that's normal. Start the flash procedure IMMEDIATELY a second time (or -- as in my case -- it is automagically done by the flash proceeding).
This flash tooks approx. 10 minutes. If you got your windows command prompt back, the final step is (even if the silver progress bar is NOT at the end, that's normal too):
Code:
htc_fastboot.exe reboot
and the system will start like a brand new original M7.
I did this many times with one of my different M7's (one for daily use, several others for testing and experiments), and all the time it worked without any trouble.
(Yet I'm using Slim7-1.17 7.1.2 Nougat with GPE-firmware on all devices, it runs much much better as any stock rom from european HTC Sense).
Happy flashing,
samhhmobil
mmm273 said:
ok but in future how i recover stock recovery and kernel ?
Click to expand...
Click to collapse
If your phone is running the latest version, you won't need the stock recovery anymore so there is no need to backup the stock recovery.
You can backup your stock kernel using twrp "backup" menu. Make a backup of the "boot" partition, this is the kernel. If you need to restore your stock kernel, just restore that backup using twrp "restore" menu. Also, stock recovery and kernel can be extracted from a firmware.zip or ruu.zip matching your phone version if you really need them (someone probably already extracted them and uploaded somewhere, if you can give me the output of "fastboot getvar version-main" I can tell you if your stock recovery and kernel are already uploaded).
You can still flash a ruu to restore your phone back to stock like described above, but flashing a ruu only to restore the stock kernel is a really drastic solution (will reset the whole phone back to stock, rom/recovery/kernel/everything and you'll loose your data).
---------- Post added at 02:14 PM ---------- Previous post was at 01:57 PM ----------
samhhmobil said:
If this step failed after installing "pre-update" hboot, that's normal. Start the flash procedure IMMEDIATELY a second time (or -- as in my case -- it is automagically done by the flash proceeding).
Click to expand...
Click to collapse
If using htc_fastboot.exe you must NOT do the flash command a second time. htc_fastboot.exe will take care of the hboot pre-update itself: will flash the hboot, output the "90 pre-update error", make the phone reboot itself back to ruu mode and flash the remaining partitions without any action from the user. Just so you know it's not magic but how it's intended to work when using htc_fastboot
The second flash was only needed if using the regular fastboot.exe from the sdk-tools for 6.xx.xxx.x RUU and older (7.xx.xxx.x ruu must be flashed with htc_fastboot.exe because of the ruu file size)
thanks all, it working
Well until i tried magisk, can't get safety check pass