Related
My gf got a Nexus S last month and loves it! She just needs BLN to work... so we unlocked the bootloader and installed a custom Kernel (Matr1x I believe). Will the OTA come through? If so, will it wipe out anything like CWR or the unlocked bootloader? I saw Matr1x already released a ver for ICS so it would be an easy install...
Sent from my XT860 using xda premium
danifunker said:
My gf got a Nexus S last month and loves it! She just needs BLN to work... so we unlocked the bootloader and installed a custom Kernel (Matr1x I believe). Will the OTA come through? If so, will it wipe out anything like CWR or the unlocked bootloader? I saw Matr1x already released a ver for ICS so it would be an easy install...
Sent from my XT860 using xda premium
Click to expand...
Click to collapse
No it wont update.
Sent from my Nexus S using xda premium
thegtfusion said:
No it wont update.
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
How would I go about updating the device? She's pretty excited for ICS.
It will fail the verifying stage of the update. All the original files of the previous version of the update your flashing needs to be there.
snandlal said:
It will fail the verifying stage of the update. All the original files of the previous version of the update your flashing needs to be there.
Click to expand...
Click to collapse
So if I restore the Kernel (I'm not sure how I would go about doing that though, can someone provide instructions? ) would it apply the update at that point? Or do I need to re-lock the bootloader? Relocking would be a pain........
danifunker said:
So if I restore the Kernel (I'm not sure how I would go about doing that though, can someone provide instructions? ) would it apply the update at that point? Or do I need to re-lock the bootloader? Relocking would be a pain........
Click to expand...
Click to collapse
If you have a nand backup of stock restore it, Otherwise download one of the stock roms from here and flash it in recovery.
http://forum.xda-developers.com/showthread.php?t=1063664
snandlal said:
It will fail the verifying stage of the update. All the original files of the previous version of the update your flashing needs to be there.
Click to expand...
Click to collapse
That depends on what kind of update it will be ... The update from 2.3.3 to 2.3.4 on my i9023 nexus was a full rom and could be flashed without a problem.
Verstuurd van mijn Nexus S met Tapatalk
Go back to latest available stock version. (Rooted with Superuser.apk in /system/app is OK) & Keep your Custom Recovery or reflash it.
Put a Superuser flashable zip on your sdcard.
When you have the OTA update.zip somewhere on your sdcard ( Copied from /cache) boot into custom recovery
Flash update.zip manually and directly after it flashes, flash the Superuser.zip right on top of update.
Wipe /cache
Reboot
Download Joeykrim's flash_image gui from the market.
Place custom-recovery.img on root of sdcard. (Rename it to recovery.img)
Flash custom recovery in flash_image gui
Change permissions of /system/etc/install-recovery.sh & /system/recovery-from-boot.p to "000"
I would just wait till ics is out and then youll find a flashable .zip here on xda and you can just flash that like you did with the matr1x kernel... not shure if full wipe would be nescesary but if yes then you can backup your apps through titanium or sth similar!
Sent from my Nexus S using XDA App
Edit: what i actually wanted to say that theres no need to go back to stock now because you can get the update over xda and just flash that!
while we're on the topic....would editing the build.prop keep an OTA from installing? For example, LCD density??
Why not just wait like one day for someone to post a rooted stock ICS rom? I am sure one of our wonderful devs here will be all over it. It will probably show up in one of those REF threads pretty quickly. Then you don't have to mess around with setting root up again. That's what I always did with my EVO Shift so I'll probably do it with this phone as well.
If you hadn't modified your build.prop or removed system apps, you'll just need to flash the stock kernel. Theres no need to flash the whole stock Rom.
What if your bootloader is unlocked and nothing else. Will it get the OTA?
Question since we on the subject when will ics be released for our phones or is it still unknown as to when is gonna be released?
Sent from my Nexus S 4G using Tapatalk
cpaixao said:
If you hadn't modified your build.prop or removed system apps, you'll just need to flash the stock kernel. Theres no need to flash the whole stock Rom.
Click to expand...
Click to collapse
That's exactly what I was looking for... but where would I find the stock Kernel and can I overwrite it while the system is in use? I downloaded the entire stock ROM for her phone so I should have the file somewhere in one of the IMG files (yes, I have mounted them before in Windows)
Sent from my XT860 using xda premium
danifunker said:
That's exactly what I was looking for... but where would I find the stock Kernel and can I overwrite it while the system is in use? I downloaded the entire stock ROM for her phone so I should have the file somewhere in one of the IMG files (yes, I have mounted them before in Windows)
Sent from my XT860 using xda premium
Click to expand...
Click to collapse
boot.img is the kernel.
How do I apply just boot.img?
Sent from my XT860 using xda premium
Fastboot flash boot boot.img
Sent by breaking the sound barrier
Hi, I'm new here. I've searched but I think there's no answer to this question. This is my first xda thread.
So, here is the question: how should I root ns with official ICS rom?
I was using CM7 build for quite a few days. Just two hours ago, I went back to official 2.3.6 and upgraded to 4.0.3. My ns model is i9023.
I used fastboot to flash 5.0.2.0 CWM recovery to ns, and I was able to use the CWMr. Then I installed su.zip (from clockworkmod.com). After reboot I can see SuperUser there now, but still get no root access.
I think I should use a newer version of su.zip? I viewed one Galaxy Nexus rooting tutorial, in that tutorial they used the same su.zip and it worked. Any one can help?
you need to use the fastboot method as on the sticky
Sent from my SGH-T989 using xda premium
AllGamer said:
you need to use the fastboot method as on the sticky
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
I think the regular rooting process is:
1.Unlock the device (already unlocked)
2.Use fastboot to flash CWM recovery
3.Boot into recovery and flash su
I did all of these, so maybe su package is the problem?
Same thing here.
AllGamer said:
you need to use the fastboot method as on the sticky
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
The regular root process doesn't seem to work for ICS. Depending on which version of the su package installed, you would get different error messages on the terminal when you execute $su.
this update sucks. now im stuck with a slow nexus with no root no color correction hack and no root. the nexus is now another pos phone. ot happy with this BS
You are not stuck with nothing. Your phone has a unlocked boot loader. Flash what you want.
Sent from my Nexus S using XDA App
vabeachfc3s said:
this update sucks. now im stuck with a slow nexus with no root no color correction hack and no root. the nexus is now another pos phone. ot happy with this BS
Click to expand...
Click to collapse
Grow up.. Idiot.
Try this su installer. Seems to have worked for a guy over there.
http://forum.xda-developers.com/showthread.php?t=1396703
Ok everyone. Horrible question I know but here goes. I want to be right so please excuse a question I am sure has been asked many many times.
Situational info:
HTC one s s4 boot loader 1.06
No regular PC access.
Extensive knowledge and experience rooting and flashing G1 and G2X
Goal: unlock boot loader and open root access to enable flashing of roms via recovery while remaining PC independent
Steps I plan to execute:
1) unlock bootloader on htcdev site
2)grant root access following instructions(or all in one tool - your input here is appreciated)
3)instal CWM
4)download rom and kernel of choice
5) boot into boot loader, enter recovery, wipe, flash, boot
If I have any of this wrong please advise.
Again I apologize for the redundancy of this thread. Mods please delete after my process is verified to keep board clean. I only have one crack at this (PC access extremely limited) and I want to get it right.
Sent from my HTC VLE_U using xda app-developers app
Looks correct. First install HTC drivers & HTC Sync software (in order to unlock bootloader, I believe HTCdev site will instruct this).
I recommend (as well as many others, I believe) TWRP over CWM. ESPECIALLY if you do not have computer access. The 1S does not have S-OFF, which makes it very hard for us to flash kernels & radios. Well, not hard, but you need a PC if using CWM. Using TWRP, you can usually flash these things from your device. So definitely use TWRP for your situation.
You can't root without a PC. It's impossible. You are required to get a token that you can only get from a command prompt on the computer. Sorry, but you're out of luck. But when/if you get a PC the steps you wrote were mostly right
1) Correct
2) FLASH RECOVERY (use TWRP, CWM is not good on this device)
3) Then root by flashing a SuperSU zip in RECOVERY (that's why #2 and #2 are switched)
4) Yep
5) Always always always BACKUP YOUR ROM. Then wipe system, data, cache, and dalvik cache. then flash the ROM. If you have extra time you should fastboot your kernel if your hboot is below 1.13 (meaning 1.13 is NOT able to flash the kernel.)
Hope I helped. If I did press thanks
OP did mention that he will have limited PC access to perform the unlock process, so he will be able to do it initially.
Here's the link for TWRP: http://forum.xda-developers.com/showthread.php?t=1677670 (make sure to use this one, the other link in the forums is for the S3 processor)
Ok so I can flash recovery as soon as I unlock boot loader and use twrp check.
The supersu, that's just a zip to flash in recovery to grant root access?
What is fasbooting kernel?
Thanks guys, appreciate the help. Will be performing this within the next two hours. Just trying to be ready so it goes off smooth. Once I get this done I need to do my friend's G2(condition for PC time lol)
Sent from my HTC VLE_U using xda app-developers app
TWRP is a recovery. You will use that instead of CWM, not in addition to.
If you're going to flash a custom rom then you don't have to worry about rooting first. The rom will be rooted already.
Fastbooting kernel is a method of using a pc + command prompt to flash the kernel on your phone. Because HTC hasn't completely "unlocked" the 1S, we need workarounds like that to do certain things. However. TWRP will allow you to flash most things, including most kernels. If you use TWRP and yout hboot is low (which yours is) you shouldn't have too many issues.
Brief note here, I won't have adb access on this pc....will I be able to flash twrp without adb? I see there is an app in the market for it but seems to require root first. Thanks again for the input
Also, downloaded roms and kernels will need to reside on my SD card. This will become an issue if pre install format/wipe kills my SD card. Please advise. Roms and kernels will need to always be installed from SD card via recovery
Sent from my HTC VLE_U using xda app-developers app
briandresstoyota said:
Brief note here, I won't have adb access on this pc....will I be able to flash twrp without adb? I see there is an app in the market for it but seems to require root first. Thanks again for the input
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
You need adb access. That's how you flash recovery, using command prompt on the PC.
Not sure about this app, what's the name of it? To my knowledge you need adb to flash recovery on this phone.
If this isn't possible, you will still be able to root, just not have a custom recovery or flash roms. I don't believe you need to unlock the bootloader to root...not 100% sure but I believe you can root without it, which should be pretty simple.
On twrp website there is an option to install recovery via an app called goomanager. In the app store goo manager states root required. Should I revise my steps to this:
1)unlock bl
2) root using supersu img
3)goomanager install twrp
4)use twrp to flash roms and kernels
I would really love to avoid flashing radios btw. I just feel like it might be safer to let it be. Radios always made me nervous on previous devices
Sent from my HTC VLE_U using xda app-developers app
You could download goo manager from the play store then install open recovery script from menu..then flash the SuperSU zip. You wouldn't require ADB then.
invasion2 said:
You could download goo manager from the play store then install open recovery script from menu..then flash the SuperSU zip. You wouldn't require ADB then.
Click to expand...
Click to collapse
This is correct. I forgot about goomanager.
As for the radios, there isn't really too much risk on the 1S. I remember it was always a scary issue on the HD2 because of EU vs. US radios, which could cause a brick. On the 1S you can flash EU radios with no prob. Actually, some people report better performance in the US with EU radio. So yeah, don't be worried about it, it's pretty safe on this device - with normal precautions and proper flashing of course.
HOWEVER:
Make sure to only use S4 radios/roms on S4 processor. There is an S3 version of the 1S as well, and you cannot switch any roms/kernels/radios between the two.
Hey hey!!! Made it work. Flashed aokp. Running sooooo amazing. Anyone know how to make home screen and app store rotate?
Sent from my HTC One S using xda app-developers app
Can't make home screen. But turn on auto-rotate in settings and it should rotate the store.
So I am a happy rooted owner. No sound in music apps or YouTube.
Sent from my HTC One S using xda app-developers app
Soo started with aokp then cm10. No sound on either except in power amp. So weird
Sent from my HTC One S using xda app-developers app
Try flashing official CM10
http://get.cm/?device=ville
If you prefer a stock look try TrickDroid or Viper
Sent from my HTC One S using xda app-developers app
Actually flashed most recent cm10 nightly after my go with AOKP. Still no dice. I've posted the issue on both ROM dev forums so hopefully it will get resolved. I feel like it is operator error but I have flashed each ROM twice with a full wipe before each install. I understand the process for flashing so I hope its something small I missed.
Sent from my HTC One S using xda app-developers app
briandresstoyota said:
Actually flashed most recent cm10 nightly after my go with AOKP. Still no dice. I've posted the issue on both ROM dev forums so hopefully it will get resolved. I feel like it is operator error but I have flashed each ROM twice with a full wipe before each install. I understand the process for flashing so I hope its something small I missed.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Do you have no sound from the speaker or do you have headphones or something plugged in?
I am tempted to go back to a regular sense 2.1 stock rooted ROM and attempt the upgrade even though I know I might not be able to root again for a while. I rooted through revolutionary. What is the worst, likely thing that could happen? Will I boot back up to all of my data on the stock Thunderbolt ICS?
Sent from my Sense 4 ICS Thunderbolt with Tapatalk 2
arizonaomnia said:
I am tempted to go back to a regular sense 2.1 stock rooted ROM and attempt the upgrade even though I know I might not be able to root again for a while. I rooted through revolutionary. What is the worst, likely thing that could happen? Will I boot back up to all of my data on the stock Thunderbolt ICS?
Sent from my Sense 4 ICS Thunderbolt with Tapatalk 2
Click to expand...
Click to collapse
You have to fully unroot to take the ota.
arizonaomnia said:
I am tempted to go back to a regular sense 2.1 stock rooted ROM and attempt the upgrade even though I know I might not be able to root again for a while. I rooted through revolutionary. What is the worst, likely thing that could happen? Will I boot back up to all of my data on the stock Thunderbolt ICS?
Sent from my Sense 4 ICS Thunderbolt with Tapatalk 2
Click to expand...
Click to collapse
You, of course, need to fully unroot before you flash back to the stock ROM and take the OTA. If you do not fully unroot, taking the OTA will brick you since it contains a new encrypted hboot. I would just wait for the rooted version of the OTA to be released, which should be posted within the next few days.
It would suck to unroot and take the OTA and then have to wait however long before you can root again.
However, if you're talking about flashing an old stock ROM backup that you may have made a long time ago, it wont have any complications. You will be able to receive the OTA then, but do not install it without fully unrooting first.
Buy fully on rooting, does that include the option to on route that is found in the Super SU settings?
Sent from my Sense 4 ICS Thunderbolt with Tapatalk 2
arizonaomnia said:
Buy fully on rooting, does that include the option to on route that is found in the Super SU settings?
Sent from my Sense 4 ICS Thunderbolt with Tapatalk 2
Click to expand...
Click to collapse
I wouldn't trust it.
Just download the files and go through command prompt to unroot. Not sure if it can be done with trter10s tool or not. I rooted mine with the same method and when I ran trter10s tool and hooked up my phone, it basically was saying it was interrupted. So I had to unroot the old manual way through command prompt.
If you can use his tool though, by all means, use it. It will definitely save you time.
arizonaomnia said:
Buy fully on rooting, does that include the option to on route that is found in the Super SU settings?
Sent from my Sense 4 ICS Thunderbolt with Tapatalk 2
Click to expand...
Click to collapse
No, that only removes superuser. Fully unrooting means flashing everything back to stock (aka tbolt tool)
Hboot has to be stock as well.
Sent from my ADR6400L using Tapatalk 2
Bummer. Thought about how I could do this without redoing the setup and all that.
Sent from my Sense 4 ICS Thunderbolt with Tapatalk 2
disconnecktie said:
Hboot has to be stock as well.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
Nope. I am running Revolutionary Hboot 6.04.1002 and I flashed the stock 2.3 rom and just finished setting up and installing apps after the 4.0.4 ota update.
johndddd said:
Nope. I am running Revolutionary Hboot 6.04.1002 and I flashed the stock 2.3 rom and just finished setting up and installing apps after the 4.0.4 ota update.
Click to expand...
Click to collapse
We are talking about taking the new ICS OTA and the consequences of installing that OTA with your current hboot.
Don't try it.
RBarnett09 said:
We are talking about taking the new ICS OTA and the consequences of installing that OTA with your current hboot.
Don't try it.
Click to expand...
Click to collapse
Isn't that what he was talking about? Sounds like he was rooted with s-off, flashed a stock rooted rom and then updated via the OTA. Sounds like he didn't apply the stock locked bootloader and the OTA applied just fine. Wouldn't the OTA just overwrite the bootloader with the new locked one?
Looks like the only problem you'd have doing it that way is waiting for a new root method.
Sent from my ADR6400L using xda app-developers app
---------- Post added at 04:03 PM ---------- Previous post was at 03:59 PM ----------
johndddd said:
Nope. I am running Revolutionary Hboot 6.04.1002 and I flashed the stock 2.3 rom and just finished setting up and installing apps after the 4.0.4 ota update.
Click to expand...
Click to collapse
What version is your bootloader now?
Sent from my ADR6400L using xda app-developers app
Nate14 said:
Isn't that what he was talking about? Sounds like he was rooted with s-off, flashed a stock rooted rom and then updated via the OTA. Sounds like he didn't apply the stock locked bootloader and the OTA applied just fine. Wouldn't the OTA just overwrite the bootloader with the new locked one?
Looks like the only problem you'd have doing it that way is waiting for a new root method.
Sent from my ADR6400L using xda app-developers app
---------- Post added at 04:03 PM ---------- Previous post was at 03:59 PM ----------
What version is your bootloader now?
Sent from my ADR6400L using xda app-developers app
Click to expand...
Click to collapse
Possibly. I figured you'd probably have to return the bootloader to stock before taking the OTA to prevent a brick.
If you can work around it that way, that is definitely a good thing to know.
Sent from my ADR6400L using xda premium
Sent from my ADR6400L using xda app-developers app
I was previously on the most up-to-date version of gingerbread, and used HTC Thunderbolt tool v1.0.1 to S-off/root the device.
I flashed stock recovery 2.11.605.9 to the device. I downloaded the following RUU_Mecha_GINGERBREAD_S_VERIZON_WWE_2.11.605.9_Radio_0.01.78.0916w_3_NV_8K_1.41_9K_1.64_release_226879_signed, pulled the rom.zip from it, and renamed it to PG05IMG.zip to flash it to the device. The device then updated itself to the most up-to-date gingerbread version. I then performed the update for ICS, it installed itself just fine, and the device booted up into ICS. I checked the bootloader, it says that I am S-off Hboot-6.04.1002, and Radio-2.02.00.1117r.
After restarting the device, I started HTC Thunderbolt tool v1.0.1. It asked if I wanted to install SU, I said yes, and it proceeded through it. Once the program finished its installation, I had the SU app in the app drawer, and downloaded ROM Manager so that I could install the recovery, it asked for SU permission to install it. I then restarted just fine into recovery to double check that it was there.
GMPOWER said:
I was previously on the most up-to-date version of gingerbread, and used HTC Thunderbolt tool v1.0.1 to S-off/root the device.
I flashed stock recovery 2.11.605.9 to the device. I downloaded the following RUU_Mecha_GINGERBREAD_S_VERIZON_WWE_2.11.605.9_Radio_0.01.78.0916w_3_NV_8K_1.41_9K_1.64_release_226879_signed, pulled the rom.zip from it, and renamed it to PG05IMG.zip to flash it to the device. The device then updated itself to the most up-to-date gingerbread version. I then performed the update for ICS, it installed itself just fine, and the device booted up into ICS. I checked the bootloader, it says that I am S-off Hboot-6.04.1002, and Radio-2.02.00.1117r.
After restarting the device, I started HTC Thunderbolt tool v1.0.1. It asked if I wanted to install SU, I said yes, and it proceeded through it. Once the program finished its installation, I had the SU app in the app drawer, and downloaded ROM Manager so that I could install the recovery, it asked for SU permission to install it. I then restarted just fine into recovery to double check that it was there.
Click to expand...
Click to collapse
So you pulled the OTA and it flashed fine with the Revolutionary Hboot and stock recovery? I have stock .19 recovery and the same hboot as you have there, running rooted stock, and the OTA failed for me. It tried to run and then failed about 1/3 of the way through.
Tiezane said:
So you pulled the OTA and it flashed fine with the Revolutionary Hboot and stock recovery? I have stock .19 recovery and the same hboot as you have there, running rooted stock, and the OTA failed for me. It tried to run and then failed about 1/3 of the way through.
Click to expand...
Click to collapse
I plan on testing this some time in the next hour - I'm currently downloading the RUU. If I get to it tonight I'll update with the results.
GMPOWER said:
I was previously on the most up-to-date version of gingerbread, and used HTC Thunderbolt tool v1.0.1 to S-off/root the device.
I flashed stock recovery 2.11.605.9 to the device. I downloaded the following RUU_Mecha_GINGERBREAD_S_VERIZON_WWE_2.11.605.9_Radio_0.01.78.0916w_3_NV_8K_1.41_9K_1.64_release_226879_signed, pulled the rom.zip from it, and renamed it to PG05IMG.zip to flash it to the device. The device then updated itself to the most up-to-date gingerbread version. I then performed the update for ICS, it installed itself just fine, and the device booted up into ICS. I checked the bootloader, it says that I am S-off Hboot-6.04.1002, and Radio-2.02.00.1117r.
After restarting the device, I started HTC Thunderbolt tool v1.0.1. It asked if I wanted to install SU, I said yes, and it proceeded through it. Once the program finished its installation, I had the SU app in the app drawer, and downloaded ROM Manager so that I could install the recovery, it asked for SU permission to install it. I then restarted just fine into recovery to double check that it was there.
Click to expand...
Click to collapse
That's great. I'm about to try myself, will report back if it works for me as well. Thanks!
Backing up current ROM now.. have the RUU on SD ready to flash.. Looks like RUU in trter10's sig has stock recovery in it, so going to try flashing RUU with 4ext and nusensex currently installed.
backup done.. formatting all except SD to be safe (ext3)
Loading PG05IMG.zip in bootloader...
Updating.. it says it Bypassed the bootloader... excellent... all others updated OK including recovery and radio..
rebooting.. seems to be starting up ok. Signed in to google, will check for OTA in a moment.
Found 395.638MB update (ICS) Downloading now.. appears to have enabled 3g to download even though i'm on wifi.. this my take a bit. not sure why it's not 4g at the moment.
hmm, ics loaded, when trying to root with the thunderbolt tool, phone reboots itself into the bootloader. any ideas? ok, had to choose the bootloader option, and then choose the fastboot option to go back in and it took. weird.
installed busybox and updated 4ext to the latest, looks like im in business.
Actually, all you have to do is download the stock Rom. Then you can do the ota without unrooting. That is what I did.
Sent from my ADR6400L using xda app-developers app
---------- Post added at 05:53 AM ---------- Previous post was at 05:45 AM ----------
I originally unlocked my boot loader through HTCDev. I installed root and clockwork recovery. Clockwork recovery prevented tho ota. So, I installed the stock Rom via recovery which overwrite clockwork recovery AMD unrooted the phone. I then did the ota. So now I have ics with unlocked bootloader. I should say that I spent half a day reading numerous web pages outlining complicated directions on unrooting and ways to remove clockwork recovery. In the end it was quite easy as stated above.
Sent from my ADR6400L using xda app-developers app
trunkamonkey said:
Actually, all you have to do is download the stock Rom. Then you can do the ota without unrooting. That is what I did.
Sent from my ADR6400L using xda app-developers app
---------- Post added at 05:53 AM ---------- Previous post was at 05:45 AM ----------
I originally unlocked my boot loader through HTCDev. I installed root and clockwork recovery. Clockwork recovery prevented tho ota. So, I installed the stock Rom via recovery which overwrite clockwork recovery AMD unrooted the phone. I then did the ota. So now I have ics with unlocked bootloader. I should say that I spent half a day reading numerous web pages outlining complicated directions on unrooting and ways to remove clockwork recovery. In the end it was quite easy as stated above.
Sent from my ADR6400L using xda app-developers app
Click to expand...
Click to collapse
Do you have a link to the file you used?
dante020 said:
Do you have a link to the file you used?
Click to expand...
Click to collapse
ruu is in trter's sig.. either way is easy. ruu will do radios, rom wont. only difference is you flash one in recovery on the other in the bootloader.
Just picked up a used inspire to replace my old xperia x10. I'm not new to rooting or flashing ROMs. I began rooting it using the easy tool posted on here; I've unlocked the bootloader and installed touch CWM, but I can't get the SU package to install. CWM doesn't see the zip, or any for that matter. I've tried reformatting (through CWM, and the phone) but no difference. Even changed the package to update.zip thinking that would get me by, but no dice. Suggestions?
Sent from my Desire HD using xda app-developers app
A little update; tried running RUU again, but now it's saying my ROM version isn't supported? Yet when I check the HBOOT version, it's 0.85.0024 and says my BL is unlocked. RUU says I have image 2.47 and the update is 2.52; yet if I let it run through the easy ace tool, it says it's 2.52 (but the easy ace tool sees 2.47). Is this my problem?
RadRacer said:
A little update; tried running RUU again, but now it's saying my ROM version isn't supported? Yet when I check the HBOOT version, it's 0.85.0024 and says my BL is unlocked. RUU says I have image 2.47 and the update is 2.52; yet if I let it run through the easy ace tool, it says it's 2.52 (but the easy ace tool sees 2.47). Is this my problem?
Click to expand...
Click to collapse
Unlocked bootloader does not allow to flash a RUU. Renaming the SU package to update.zip will not help. Or your sdcard is borked or the file is not there...when you say that is not seeing it, what does that mean?
When I select choose a zip or apply update.zip through cwm, it says no files found
Sent from my Desire HD using Tapatalk 2
I had see same problem but fixed that by replacing the touch version with the non-touch version. But now after flashing cm10.1 I'm stuck at the white HTC screen lol.
Sent from my SAMSUNG-SGH-I747 using xda premium
But also in case you run into the same problem with the HTC boot screen just flash the boot.img of your rom via fastboot and that will also fix that.
Sent from my SAMSUNG-SGH-I747 using xda premium
I'll look into that; I mainly want root to debloat this phone. Way too much unnecessary crap on here!
Sent from my Desire HD using Tapatalk 2
Thanks for that tip; downloaded the latest non-touch CWM (the one listed for the DHD) and flashed it and it worked! Now I'm tempted to start flashing some ROMs