Hello fellow Android users,
I am here to ask for your help.
Just to be clear, my phone is an HTC Desire 601 locked with FIDO, use to have Android 4.4.2, Zara_UL, Unlocked bootloader, S-ON and no OS installed.
My HTC Desire 601 has had a rough week.
Everything went well for unlocking the bootloader, rooting, installing new recovery.
Then I wanted to go S-OFF, but Firewater told me the current kernel was blocking the exploit.
So I decided to flash KofilaKernel for my device and try again. The install went well,
only problem was I wiped my cache and system and now, NO MORE OS INSTALLED and still S-ON.
Couldn't use Firewater anymore...
So I tried installing custom ROM and also tried going back to stock, miserably failing.
A. I tried flashing InsertCoin custom ROM wich failed because of S-ON (forgive noobishness)
B. I tried using "fastboot boot" command that made possible flashing custom ROM with S-ON.
I was counting on this one, but had problems too : Most recoveries wouldn't boot (ClockWorkMod several versions, TWRP several versions) except one TWRP recovery wich booted, but the touch screen WAS NOT ACTIVATED. Tried using side buttons with no luck, and power button just locked the screen. I have heard that Google has changed the fastboot boot for newer android versions and that you had to add something to the command like :
"fastboot -c "lge.kcal=0|0|0|x" boot recovery.img"
This example is for Nexus 4 I think, but I don't know the one for Desire 601... I tried it and it wouldn't boot.
C. I have tried "fastboot flash system system.img" with stock image. Had an error saying not enough memory available.
I wiped everything with TWRP and with CLCKWRKMOD : System, cache, dalvik cache, etc... tried again to flash system with no luck.
D. I have tried the Telus RUU.exe file. Told me I had the wrong RUU for my phone and to find the right one, wich doesn't exist for Android 4.4.2 as far as I know.
E. I have tried flashing several versions of 4EXT recovery to get SmartFlash, but it is not compatible with HTC Desire 601.
There I am.
Please help a brother with unusable new phone LOL.
Thanks a bunch for any help.
black-venomz
black-venomz said:
Hello fellow Android users,
I am here to ask for your help.
Just to be clear, my phone is an HTC Desire 601 locked with FIDO, use to have Android 4.4.2, Zara_UL, Unlocked bootloader, S-ON and no OS installed.
My HTC Desire 601 has had a rough week.
Everything went well for unlocking the bootloader, rooting, installing new recovery.
Then I wanted to go S-OFF, but Firewater told me the current kernel was blocking the exploit.
So I decided to flash KofilaKernel for my device and try again. The install went well,
only problem was I wiped my cache and system and now, NO MORE OS INSTALLED and still S-ON.
Couldn't use Firewater anymore...
So I tried installing custom ROM and also tried going back to stock, miserably failing.
A. I tried flashing InsertCoin custom ROM wich failed because of S-ON (forgive noobishness)
B. I tried using "fastboot boot" command that made possible flashing custom ROM with S-ON.
I was counting on this one, but had problems too : Most recoveries wouldn't boot (ClockWorkMod several versions, TWRP several versions) except one TWRP recovery wich booted, but the touch screen WAS NOT ACTIVATED. Tried using side buttons with no luck, and power button just locked the screen. I have heard that Google has changed the fastboot boot for newer android versions and that you had to add something to the command like :
"fastboot -c "lge.kcal=0|0|0|x" boot recovery.img"
This example is for Nexus 4 I think, but I don't know the one for Desire 601... I tried it and it wouldn't boot.
C. I have tried "fastboot flash system system.img" with stock image. Had an error saying not enough memory available.
I wiped everything with TWRP and with CLCKWRKMOD : System, cache, dalvik cache, etc... tried again to flash system with no luck.
D. I have tried the Telus RUU.exe file. Told me I had the wrong RUU for my phone and to find the right one, wich doesn't exist for Android 4.4.2 as far as I know.
E. I have read about 4EXT recovery and SmartFlash, but the only way to get 4EXT recovery seems to be through app and I don't have any OS so it's impossible.
There I am.
Please help a brother with unusable new phone LOL.
Thanks a bunch for any help.
black-venomz
Click to expand...
Click to collapse
I'd just reinstall a rom based off of your current firmware and then you need to copy the boot.img out of it and flash in bootloader. The command you'll want to use is:
fastboot flash boot boot.img
Be cautious trying to run KK roms on JB firmware as you'll have issues with the radio and touch, bare minimum. Only ways to update firmware are via being S-Off and doing a firmware update of just the essentials or find a KK RUU for your phone, if it is available.
es0tericcha0s said:
I'd just reinstall a rom based off of your current firmware and then you need to copy the boot.img out of it and flash in bootloader. The command you'll want to use is:
fastboot flash boot boot.img
Be cautious trying to run KK roms on JB firmware as you'll have issues with the radio and touch, bare minimum. Only ways to update firmware are via being S-Off and doing a firmware update of just the essentials or find a KK RUU for your phone, if it is available.
Click to expand...
Click to collapse
So a ROM based on my current firware wouldn't need S-OFF to be installed ? Can I install stock ROM via recovery even if S-ON ?
Do you know where I could find such thing ?
Many thanks.
black-venomz
black-venomz said:
So a ROM based on my current firware wouldn't need S-OFF to be installed ? Can I install stock ROM via recovery even if S-ON ?
Do you know where I could find such thing ?
Many thanks.
black-venomz
Click to expand...
Click to collapse
Correct, you can install a rom while S-On, as long as you install the boot.img separately. You can install a rom based off of stock, but you won't be able to do the official RUU type rom from it unless there is an RUU zip for your phone (some HTCs have this, but most are just via an exe of a PC) but that would actually go through the bootloader instead of recovery.
es0tericcha0s said:
Correct, you can install a rom while S-On, as long as you install the boot.img separately. You can install a rom based off of stock, but you won't be able to do the official RUU type rom from it unless there is an RUU zip for your phone (some HTCs have this, but most are just via an exe of a PC) but that would actually go through the bootloader instead of recovery.
Click to expand...
Click to collapse
Ok great !
So I have access to a stock ROM apparently. I can't post links yet, but if you look up on Google "htcdesire 601 stock rom" you will find a google docs page with the stock ROM for desire 601 4.4.2.
Would you be king enough to walk me through the steps to achieve this ? There are many .img files in this folder and I am far from an expert.
Thanks again.
black-venomzz
I did :
1. Copy whole .zip file on sd card found when searched "htc desire 601 stock rom" on google in google docs pasge (can't post link yet).
2. Install .zip with TWRP.
- Failed (still bootloop) -
The tried :
1. fastboot flash boot boot.img (boot.img was found in the .zip file)
2. Copy whole .zip file on sd card
3. Install .zip with TWRP
- Failed (still bootloop) -
I'm probably missing something here...
You might not have the correct zip for your variant of 610. They make a few and could depend on the carrier as well. Should also factory reset in TWRP.
es0tericcha0s said:
You might not have the correct zip for your variant of 610. They make a few and could depend on the carrier as well. Should also factory reset in TWRP.
Click to expand...
Click to collapse
Still need help guys ! I believe I have the right one.
Could you check it out ? It looks legit.
**drive**.google.**com/folderview?id=0B6WBFlAKqe30ZG1wOGk2T0xwTkE&&tid=0B6WBFlAKqe30TjRLa2Qxa0toYlU
(I still can't post links on threads because I'm new...)
I tried Installing ROM from zip in TWRP (successful) and then fastboot flash boot boot.img but still didn't work !
My phone is still bricked.
Any help would be appreciated.
black-venomz said:
Still need help guys ! I believe I have the right one.
Could you check it out ? It looks legit.
**drive**.google.**com/folderview?id=0B6WBFlAKqe30ZG1wOGk2T0xwTkE&&tid=0B6WBFlAKqe30TjRLa2Qxa0toYlU
(I still can't post links on threads because I'm new...)
I tried Installing ROM from zip in TWRP (successful) and then fastboot flash boot boot.img but still didn't work !
My phone is still bricked.
Any help would be appreciated.
Click to expand...
Click to collapse
Couldn't find that page, even after taking out the asteriks. But you'll need to boot to the bootloader and run this command:
fastboot getvar all
to find out your exact model/region/carrier/etc.
es0tericcha0s said:
Couldn't find that page, even after taking out the asteriks. But you'll need to boot to the bootloader and run this command:
fastboot getvar all
to find out your exact model/region/carrier/etc.
Click to expand...
Click to collapse
I ran the command. See attachment. I don't know how to compare it to ROM.
Here is the link again :
**https**://**drive.**google.**com/folderview?id=0B6WBFlAKqe30eUh3WXB4eURwRjQ&&tid=0B6WBFlAKqe30TjRLa2Qxa0toYlU
If it still fails (wich truly shouldn't) I access it by searching "htc desire 601 stock ROM" on Google and it's the first one, the page is called "Firmware"
Thank you for your help !
Edit : I know why the link fails. It seems xda adds a space somewhere in the link. Need to remove it for the link to work.
black-venomz said:
I ran the command. See attachment. I don't know how to compare it to ROM.
Here is the link again :
**https**://**drive.**google.**com/folderview?id=0B6WBFlAKqe30eUh3WXB4eURwRjQ&&tid=0B6WBFlAKqe30TjRLa2Qxa0toYlU
If it still fails (wich truly shouldn't) I access it by searching "htc desire 601 stock ROM" on Google and it's the first one, the page is called "Firmware"
Thank you for your help !
Edit : I know why the link fails. It seems xda adds a space somewhere in the link. Need to remove it for the link to work.
Click to expand...
Click to collapse
I'll look around for it later, but real quick, you probably want to take down the picture since it has your IMEI and Serial Number of the phone listed, for safety's sake.
es0tericcha0s said:
I'll look around for it later, but real quick, you probably want to take down the picture since it has your IMEI and Serial Number of the phone listed, for safety's sake.
Click to expand...
Click to collapse
Ok I'll wait ! Thanks for the tip. If you need it for the info, I'll post it again without IMEI/Serial.
black-venomz said:
Ok I'll wait ! Thanks for the tip. If you need it for the info, I'll post it again without IMEI/Serial.
Click to expand...
Click to collapse
Ok, I think we might be on the right track now...
According to the read out from getvar, you were on 4.2.2. It's also listed as a Rogers phone (I'm assuming there's a direct connection between Fido and Rogers, though being an American, I'm not 100% up to date with Canadian carriers...) so I found the RUU for 4.2.2 (system 1.10.631.8 which you can see in the getvar list) http://www.htcdev.com/devcenter/downloads/P510 (it won't let me do a direct link for some reason) and pick the Rogers one for 1.10.631.8
This should get you back up and running.
Make sure to relock the bootloader before you run it or it'll fail. You can re-unlock afterwards. Should be able to do "fastboot oem lock" then when ready to unlock again then "fastboot oem unlock" should work since you've already used the bootloader key.
es0tericcha0s said:
Ok, I think we might be on the right track now...
According to the read out from getvar, you were on 4.2.2. It's also listed as a Rogers phone (I'm assuming there's a direct connection between Fido and Rogers, though being an American, I'm not 100% up to date with Canadian carriers...) so I found the RUU for 4.2.2 (system 1.10.631.8 which you can see in the getvar list) http://www.htcdev.com/devcenter/downloads/P510 (it won't let me do a direct link for some reason) and pick the Rogers one for 1.10.631.8
This should get you back up and running.
Make sure to relock the bootloader before you run it or it'll fail. You can re-unlock afterwards. Should be able to do "fastboot oem lock" then when ready to unlock again then "fastboot oem unlock" should work since you've already used the bootloader key.
Click to expand...
Click to collapse
Your a life saver thanks !
I'll make sure to relock.
The only thing is I have no clue how to use this RUU. It's not like a ".exe" that you execute.
The .zip file contains a .tar.gz file, wich contains another .tar file, wich contains binaries I believe.
The readme.txt file talks about using Linux commands but I'm far from an expert.
I'll do a little research on my own since you helped me a lot already, but if you have any tips feel free to share !
Thanks again,
black-venomz
BTW for information purposes,
Fido is indeed a subsidiary brand of Rogers.
black-venomz said:
BTW for information purposes,
Fido is indeed a subsidiary brand of Rogers.
Click to expand...
Click to collapse
Ah shoot, I didn't realize it at the time, but that's like the source code, as in, if you wanted to compile a rom for your phone. That actually isn't what we need. :/ I'll have to keep looking...
es0tericcha0s said:
Ah shoot, I didn't realize it at the time, but that's like the source code, as in, if you wanted to compile a rom for your phone. That actually isn't what we need. :/ I'll have to keep looking...
Click to expand...
Click to collapse
****e. How do people build RUU.exe in the first place ? Can't we build one with these binary files ?
Edit : Did some reading and found out only vendors can make RUU's.
Tried this, found on another thread.
"The RUU is your normal, executable program and does everything for you. The ZIP is an RUU but you have to set the phone up to flash it by using fastboot commands. the process is:
1. Connect phone in fastboot mode
2. Run the command 'fastboot oem rebootRUU'
3. Once the phone is at the HTC screen, you run the command 'fastboot flash zip name_of_zip.zip'
4. It will flash the first part and then give an error and you run the same command as above a second time straight away
5. Once the second flash sequence has finished, you the type 'fastboot reboot' and it will reboot the phone and finish the installation"
It failed, but I didn't relock bootloader yet. Will try that now.
Edit : Also failed with relocked bootloader.
Fastboot error message was :
"(bootloader) signature checking
FAILED (remote : 12 signature verify fail)"
black-venomz said:
Tried this, found on another thread.
"The RUU is your normal, executable program and does everything for you. The ZIP is an RUU but you have to set the phone up to flash it by using fastboot commands. the process is:
1. Connect phone in fastboot mode
2. Run the command 'fastboot oem rebootRUU'
3. Once the phone is at the HTC screen, you run the command 'fastboot flash zip name_of_zip.zip'
4. It will flash the first part and then give an error and you run the same command as above a second time straight away
5. Once the second flash sequence has finished, you the type 'fastboot reboot' and it will reboot the phone and finish the installation"
It failed, but I didn't relock bootloader yet. Will try that now.
Edit : Also failed with relocked bootloader.
Fastboot error message was :
"(bootloader) signature checking
FAILED (remote : 12 signature verify fail)"
Click to expand...
Click to collapse
You can flash RUUs like that, but that zip does not house the files you would need. RUUs have to be signed with HTC's special key or it won't work. That's why it was only a 99MB file...
---------- Post added at 12:16 AM ---------- Previous post was at 12:00 AM ----------
http://forum.xda-developers.com/desire-601/help/rogers-ruu-available-t2836217
https://drive.google.com/folderview...RFdlTWc&tid=0BzrP5DWIlpplWkNROHh6Y3o4UHc#list
es0tericcha0s said:
You can flash RUUs like that, but that zip does not house the files you would need. RUUs have to be signed with HTC's special key or it won't work. That's why it was only a 99MB file...
Click to expand...
Click to collapse
Thanks for looking around. Unfortunately the RUU failed (see picture).
I think my phone was updated with Android 4.4.2 when I bought it (recently) so it might be what's causing the error.
I wanted to try with a Telus RUU for 4.4.2 but it's not there..........
I'm starting to lose hope here.
Related
I AM PLAYING WITH MY REZOUND FROM LAST 1 MONTH YESTERDAY I THOUGHT I HAVE TO UPDATE IT TO ICS(RUU FROM ANDROIDPOLICE) AND FLASHED RUU FROM HEREhttp://www.androidpolice.com/2012/08/02/exclusive-download-htc-rezound-ice-cream-sandwich-ruu-for-final-ota-3-14-605-12/
AFTER FLASHING RUU PHONE STARTS REBOOTING ,NO APPS DOWNLOAD FROM PLAY STORE ,
NOW I WANTS TO GO BACK TO GINGERBREAD OFFICIAL ROM
PLZ SOMEONE HELP ME SO I CAN FLASH GB OFFICIAL RUU ON MY REZOUND
DETAILS OF MY REZOUND-
TAMPERED
****RELOCKED***
VIGOR PVT SHIP S-ON RL
HBOOT -2.25.0000
RADIO-1.22.10.0421R/1.22.10.0424R
OPENDSP-V13.6.0.7611.00.0104
EMMC-BOOT
APR 12 2012,16:47:46
PLZ SUGGEST ME TO GO BACK TO GB OR ANY FIX TO STOP ALL RANDOM REBOOTS.
In order to downgrade you need to S-OFF, then flash one of the old RUU's.
Did you factory reset after installing the ICS?
I would also try installing the new 4.3.605.2 RUU from Android Police... factory default, flash twice (if you flash an RUU, ALWAYS do it twice), then factory default again.
acejavelin said:
In order to downgrade you need to S-OFF, then flash one of the old RUU's.
Did you factory reset after installing the ICS?
I would also try installing the new 4.3.605.2 RUU from Android Police... factory default, flash twice (if you flash an RUU, ALWAYS do it twice), then factory default again.
Click to expand...
Click to collapse
+1 I would try the factory reset before anything. then follow the steps above.
if you are 100% sure you want to go back to GB then you would need s-off
you need s-off to go back to gingerbread. try flashing the new 4.3.605.2
Thnx for all replies can someone confirm Ruu 4.3.605.2 is stable and working fine ?
Sent from my SGH-T999 using xda app-developers app
I have searched google but not able to found any valid link for latest ruu can someone plz post latest ruu link for download ?
Sent from my SGH-T999 using xda app-developers app
sanchitgrover said:
I have searched google but not able to found any valid link for latest ruu can someone plz post latest ruu link for download ?
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
It is completely stable, and fixes way more issues than the changelog mentions...
http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/
And select AP Mirror #1 which is hosted on beta.androidfilehost.com, a very reliable and (usually) speedy server, it takes about 3 minutes for me to download it ( I have done it lots of times, people keep saying doesn't work), just click the link, then the green circle with a down arrow to download it (to the left of the filename), MD5 matches every time. If that one give you trouble, go to the same link and on the right hand side there are mirrors of that server, they work equally well.
And like every ROM, VERIFY the MD5 before flashing... if it don't match, don't flash!
It looks like your RUU didn't install completely. Flash it *several* times, until you get the screen where all items are listen as "OK" and it says to reboot.
If that still doesn't work, try flashing it through fastboot:
install HTC Sync (this will install drivers for adb and bootloader debug). Somehow obtain fastboot.exe (pretty sure it comes with HTC Sync. If not, download the Rezound All In One Toolkit. Open a command prompt and change the directory to the same one that fastboot.exe is in (use the command "cd" then the full folder location, ex "cd c:\users\yourname\desktop\fastboot folder").
Next, you'll want to take out your phone's SD card. Power on the phone, holding power and volume down to boot into the bootloader. Then, choose fastboot. Connect your phone to your PC at this time. Now use the command "fastboot oem rebootRUU". Your phone will reboot to a black screen with a silver HTC logo. Next, drag the RUU file you downloaded (doesn't matter what it's named) to the same folder as fastboot.exe. Use the command "fastboot flash zip <ruu name>", replacing "<ruu name>" with the name of the file, obviously. Once the command prompt says it's done, you can safely turn off your phone, or do a battery pull if necessary.
I highly recommend you do not revert to Gingerbread, because it requires a firmware downgrade and the S-Off procedure is necessary. Things can go horribly wrong with S-off especially if you don't know what you're doing.
scy1192 said:
It looks like your RUU didn't install completely. Flash it *several* times, until you get the screen where all items are listen as "OK" and it says to reboot.
If that still doesn't work, try flashing it through fastboot:
install HTC Sync (this will install drivers for adb and bootloader debug). Somehow obtain fastboot.exe (pretty sure it comes with HTC Sync. If not, download the Rezound All In One Toolkit. Open a command prompt and change the directory to the same one that fastboot.exe is in (use the command "cd" then the full folder location, ex "cd c:\users\yourname\desktop\fastboot folder").
Next, you'll want to take out your phone's SD card. Power on the phone, holding power and volume down to boot into the bootloader. Then, choose fastboot. Connect your phone to your PC at this time. Now use the command "fastboot oem rebootRUU". Your phone will reboot to a black screen with a silver HTC logo. Next, drag the RUU file you downloaded (doesn't matter what it's named) to the same folder as fastboot.exe. Use the command "fastboot flash zip <ruu name>", replacing "<ruu name>" with the name of the file, obviously. Once the command prompt says it's done, you can safely turn off your phone, or do a battery pull if necessary.
I highly recommend you do not revert to Gingerbread, because it requires a firmware downgrade and the S-Off procedure is necessary. Things can go horribly wrong with S-off especially if you don't know what you're doing.
Click to expand...
Click to collapse
So this will work with out S-off? I am on Venom Rom on ICS. Great Rom but when I plug my headphones in the phone reboots. I want to get back to Stock ICS.
Thanks
duvious said:
So this will work with out S-off? I am on Venom Rom on ICS. Great Rom but when I plug my headphones in the phone reboots. I want to get back to Stock ICS.
Thanks
Click to expand...
Click to collapse
Without S-OFF you can only go same version or newer, not backwards, but you will have to relock your bootloader... You should then be able to flash the 4.3.605.2 RUU with no problem.
scy1192 said:
It looks like your RUU didn't install completely. Flash it *several* times, until you get the screen where all items are listen as "OK" and it says to reboot.
If that still doesn't work, try flashing it through fastboot:
install HTC Sync (this will install drivers for adb and bootloader debug). Somehow obtain fastboot.exe (pretty sure it comes with HTC Sync. If not, download the Rezound All In One Toolkit. Open a command prompt and change the directory to the same one that fastboot.exe is in (use the command "cd" then the full folder location, ex "cd c:\users\yourname\desktop\fastboot folder").
Next, you'll want to take out your phone's SD card. Power on the phone, holding power and volume down to boot into the bootloader. Then, choose fastboot. Connect your phone to your PC at this time. Now use the command "fastboot oem rebootRUU". Your phone will reboot to a black screen with a silver HTC logo. Next, drag the RUU file you downloaded (doesn't matter what it's named) to the same folder as fastboot.exe. Use the command "fastboot flash zip <ruu name>", replacing "<ruu name>" with the name of the file, obviously. Once the command prompt says it's done, you can safely turn off your phone, or do a battery pull if necessary.
I highly recommend you do not revert to Gingerbread, because it requires a firmware downgrade and the S-Off procedure is necessary. Things can go horribly wrong with S-off especially if you don't know what you're doing.
Click to expand...
Click to collapse
acejavelin said:
Without S-OFF you can only go same version or newer, not backwards, but you will have to relock your bootloader... You should then be able to flash the 4.3.605.2 RUU with no problem.
Click to expand...
Click to collapse
That is great news. I will relock and flash!
htc rezound hboot 2.25.0000 can flash global verizon rom?
want to flash global verizon rom , hboot version 2.25, s-on , locked, please help, want to use on gsm services
u can flash gb rom with patch to fix sdcard mounting problem
unlock ur device
install recovery
flash the rom & patch
flash the kernel via fastboot or hboot
then power it on normally
or
flash stock gb only the rom.zip and boot.img via hboot
root
patch ur device manually
basheerbr said:
want to flash global verizon rom , hboot version 2.25, s-on , locked, please help, want to use on gsm services
Click to expand...
Click to collapse
just download it from android police and flash, flash twice followed with a factory reset. should b in good shape after.
basheerbr said:
want to flash global verizon rom , hboot version 2.25, s-on , locked, please help, want to use on gsm services
Click to expand...
Click to collapse
For the global RUU - http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/
Feel free to open a new thread vs using an 8 month old one that isn't related to your problem if you can't find what you're looking for also.
basheerbr said:
want to flash global verizon rom , hboot version 2.25, s-on , locked, please help, want to use on gsm services
Click to expand...
Click to collapse
mike7728 said:
just download it from android police and flash, flash twice followed with a factory reset. should b in good shape after.
Click to expand...
Click to collapse
Also, make sure you allow it to fully do its thing, don't pull battery or anything in the middle of it. The screen will go black for a second or two, just wait it out. It will leave you in bootloader when it's done iirc.
Ok, so I tired to dabble in custom roms and I got burnt!!!
First things first,
HTC One X+ (International)
Version Main: 1.17.708.1
CID: HTC_622
S-On
HBOOT: 1.35.0000
Radio: 3.1204.168.32
I'm trying to RUU the device back to the stock and then never tinker again!
Can someone please step me through this, all the links I'm finding are dead or the RUU doesn't run.
Many thanks =)
Get hasoons20000 one x+ toolkit it has a link for ruu
Gave this a shot, I cannot find the appropriate RUU for my device.
****...
CJMilsey said:
Gave this a shot, I cannot find the appropriate RUU for my device.
****...
Click to expand...
Click to collapse
What country did you buy it from and what is your CID?
I bought it online (from Asia) The CID is 622 as above.
Addicted2xda said:
What country did you buy it from and what is your CID?
Click to expand...
Click to collapse
Bump
CJMilsey said:
Bump
Click to expand...
Click to collapse
Refer to the posting rules. You should not bump a thread within 24 hours...
You can download the RUU (ENRC2B) from this :
http://forum.xda-developers.com/showthread.php?t=2094118
you need to relock your bootloader before running the RUU
http://www.androidfiles.org/ruu/get...Radio_3.1204.168.32_release_299722_signed.exe
I'm sorry, I must have missed that one :/
I Tried this before but the RUU used didn't work, but I'll try to re-download and go from there.
(RUU_ENRC2B_U_JB_45_hTC_Asia_WWE_1.17.707.1_Radio_3.1204.168.32_release_299722_signed.exe)
Will it be a problem that my phone is 1.17.708.1 and that this is 1.17.707.1 (0.0.001 lower)?
Also, do I need to flash the stock recovery. And If so where would I go about getting it?
You will only have to relock the bootloader again and then (while in fastboot) run the RUU. Remember that you will lose everything on the device.
To relock the bootloader use Hansoon's toolkit. It has all the commands build in for easy use.
"Wrong CID" I'm not sure why this is wrong. 662 came back from fastboot getvar cid, and does indeed correspond to Hong Kong.
What would you advise from here dear sir?
CJMilsey said:
"Wrong CID" I'm not why this is wrong. 662 came back from fastboot getvar cid, and does indeed correspond to Hong Kong.
What would you advise from here dear sir?
Click to expand...
Click to collapse
Are you sure it's a generic HK CID? And not an operator locked one? Maybe you need the RUU from a particular operator.....
Sent from my HTC One X+ using Tapatalk 4 Beta
AndroHero said:
Are you sure it's a generic HK CID? And not an operator locked one? Maybe you need the RUU from a particular operator.....
Sent from my HTC One X+ using Tapatalk 4 Beta
Click to expand...
Click to collapse
I looked up the CID and it's just for HK, the phone came unlock so I doubt it needs a locked RUU. But hey, I've been wrong before.
Is there any reason the phone would not accept the correct RUU?
Okk,
This might seem a bit weird but I had the same issue with my Intl HOX+ and I have given it to hTC and they asked me to shell out aroun 18K to change the motherboard! (Which of course we all know is not required since this is a software issue).
So here is what I did:
1. I relocked the boot loader (I hope you have the unlock_code.bin with you, else get it from hTCDev)
2. Of course it started giving relocked security warning.
3. Again unlocked the boot loader and voila - it booted straight in to Elegancia!
This essentiially happens because unlocking the bootloader formats all the partitions except system and boot (I guess, because my media files were gone...).
See if this gets you through.
But DO IT AT YOUR OWN RISK!
I am talking about International HOX+, I do not know if ATT works in a different way.
Unfortunately that hasn't worked and I'm still stuck with the stall during boot :/
I think my best bet will the RUU, but I just can't get one that will work.
Do you know a ROM that I could side-load onto my device and just use it with that?
Thanks
Addicted2xda said:
Okk,
This might seem a bit weird but I had the same issue with my Intl HOX+ and I have given it to hTC and they asked me to shell out aroun 18K to change the motherboard! (Which of course we all know is not required since this is a software issue).
So here is what I did:
1. I relocked the boot loader (I hope you have the unlock_code.bin with you, else get it from hTCDev)
2. Of course it started giving relocked security warning.
3. Again unlocked the boot loader and voila - it booted straight in to Elegancia!
This essentiially happens because unlocking the bootloader formats all the partitions except system and boot (I guess, because my media files were gone...).
See if this gets you through.
But DO IT AT YOUR OWN RISK!
I am talking about International HOX+, I do not know if ATT works in a different way.
Click to expand...
Click to collapse
I had a small bootloader problem and was just surfing this section.I used your method of relocking and again unlocking and my problem was solved.I found it obligatery for me to thank you.
---------- Post added at 10:30 AM ---------- Previous post was at 10:21 AM ----------
CJMilsey said:
Unfortunately that hasn't worked and I'm still stuck with the stall during boot :/
I think my best bet will the RUU, but I just can't get one that will work.
Do you know a ROM that I could side-load onto my device and just use it with that?
Click to expand...
Click to collapse
I have unbricked mine by efforts of two long days and nights from about same problem. Provide the details and I will try to help you out,
1. can you boot to recovery.
2. If yes.which recovery you use.
3. what were you doing when this happened.
faandrabi said:
I have unbricked mine by efforts of two long days and nights from about same problem. Provide the details and I will try to help you out,
1. can you boot to recovery.
2. If yes.which recovery you use.
3. what were you doing when this happened.
Click to expand...
Click to collapse
1. No recovery works, and by mistake I performed a full erase with TWRP (don't ask me how, I honestly don't know why I did this) so despite all that they don't even exist anymore.
3. I flashed to Boot File as I couldn't get CM10.1 (Lior's HOX+ plug) to install and considered that my solve it. (I was wrong)
From this stuff I'm pretty sure it's broke, but I can get to the boot loader and recovery. Though I ran the appropriate (so I thought) RUU and it didn't work due to CID which stumped me.
CJMilsey said:
1. No recovery works, and by mistake I performed a full erase with TWRP (don't ask me how, I honestly don't know why I did this) so despite all that they don't even exist anymore.
3. I flashed to Boot File as I couldn't get CM10.1 (Lior's HOX+ plug) to install and considered that my solve it. (I was wrong)
From this stuff I'm pretty sure it's broke, but I can get to the boot loader and recovery. Though I ran the appropriate (so I thought) RUU and it didn't work due to CID which stumped me.
Click to expand...
Click to collapse
flash twrp through fasboot as only twrp provides side load option.
when twrp is flashed ,boot to recovery.side load incertcoin rom through hasoons toolkit.
don't worry about 707 or 708 etc.Mine was 707.1 but i am using incertcoin which is 401.3
after falshing incertcoin if it is again in boot loop then
use this command from adb
adb shell
wipe data
and reboot
you will be done.
CJMilsey said:
1. No recovery works, and by mistake I performed a full erase with TWRP (don't ask me how, I honestly don't know why I did this) so despite all that they don't even exist anymore.
3. I flashed to Boot File as I couldn't get CM10.1 (Lior's HOX+ plug) to install and considered that my solve it. (I was wrong)
From this stuff I'm pretty sure it's broke, but I can get to the boot loader and recovery. Though I ran the appropriate (so I thought) RUU and it didn't work due to CID which stumped me.
Click to expand...
Click to collapse
I hope you are on TWRP 2.5? If not update it...
And then use adb sideload
Hi,
I have the exact same problem.. I can get to TWRP recovery and HBOOT and my PC only detects the phone if its in recovery.
my CID is HTC__001.
I am trying to find a working RUU to run..
I tried this one: RUU_ENRC2B_U_JB_45_hTC_Asia_TW_1.14.709.17_Radio_3.1204.167.31_release_291089_signed.exe
(But that didn't work)
Any suggestions?
Thanks in advance.
rmuruga said:
Hi,
I have the exact same problem.. I can get to TWRP recovery and HBOOT and my PC only detects the phone if its in recovery.
my CID is HTC__001.
I am trying to find a working RUU to run..
I tried this one: RUU_ENRC2B_U_JB_45_hTC_Asia_TW_1.14.709.17_Radio_3.1204.167.31_release_291089_signed.exe
(But that didn't work)
Any suggestions?
Thanks in advance.
Click to expand...
Click to collapse
download incertcoin rom from hox+ android development & hasoon toolkit v2.4
boot in recovery
connect to pc
run onex+.exe and side load the rom
after it is done flash boot.img inside rom through fasboot command
and you will be done
So I've explored different options on XDA's site for returning to stock and I guess this is why I'm here. I screwed the hell up. I posted this on Phaded's How-To page, but I figured it would also be best to post this in the general Help & Troubleshooting page.
Here's the best way I can explain my issue. Someone please help.
1. My phone is COMPLETELY formatted. No OS now. Zero data.
2. TWRP is installed as my recovery.
3. I can fastboot and adb (only from the recovery obviously)
4. I moonshined the phone in order to S-Off
5. I tried the method to remove S-Off by Phaded
adb devices (verify device ID is listed)
adb shell
su
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
exit
Click to expand...
Click to collapse
When I ran the RUU, I got that error 158 problem. I couldn't flash the HBOOT. downloaded it several times and tried.
6. I flashed it with an AOSP rom and tried the RUU again. No luck.
Now I'm stuck. u_u I tried
adb push "file name" "file directory"
Click to expand...
Click to collapse
so I can drop a zip file in the phone, but it seems to not work. Idk if I did it right. I was hoping to flash a ROM by doing that. smh.
Let me know if there's any other info I can provide. Considering the phone still turns on and I can still get to fastboot and adb, I don't think I'm a lost cause.
Thanks everyone!
UPDATE
I sideloaded a ROM (Carbon) and now I'm up and running. But I still can't RUU it! Figured this detail will help.
I'll keep reading and researching, posting my progress.
Thanks!
Its ok that your'e formatted the main concern would be 1. To be able to turn the phone on and 2. Boot into bootloader and recovery . It sounds like you are able to do both so the term "bricked" doesn't apply here.Okay so first obvious question did you obtain s-off also what bootloader are you on. Also what are you trying to achieve moving forward, going to stock or staying with custom roms, sense or aosp. There is only 1 ruu available for DNA and you need to be relocked to run and have fastboot drivers installed ala HTC sync manager.
Sent from my HTC6435LVW using Tapatalk 4 Beta
xlxcrossing said:
Its ok that your'e formatted the main concern would be 1. To be able to turn the phone on and 2. Boot into bootloader and recovery . It sounds like you are able to do both so the term "bricked" doesn't apply here.Okay so first obvious question did you obtain s-off also what bootloader are you on. Also what are you trying to achieve moving forward, going to stock or staying with custom roms, sense or aosp. There is only 1 ruu available for DNA and you need to be relocked to run and have fastboot drivers installed ala HTC sync manager.
Sent from my HTC6435LVW using Tapatalk 4 Beta
Click to expand...
Click to collapse
1. I obtained s-off with moonshine. I used the above command suggested by Phaded and when I put in
fastboot oem lock
Click to expand...
Click to collapse
(or something like that) it says my phone is locked.
2. What do you mean what bootloader? I guess moonshine, cause that's what comes up when I go to my bootloader screen.
3. I trying flashing the ruu and I get this (see image attached) which the suggested fix for error 158 was to flash the hboot 1.15 (or something). But I can't seem to flash it correctly. I can't even find straight forward instructions on how to do it.
Thanks for responding.
The reason I asked about the bootloader version and I'm not 100% sure about this so someone else may need to chime in is that when you ruu you are flashing firmware which includes hboot so if you upgraded hboot before doing s-off or otherwise went up a version then I'm pretty sure the ruu won't downgrade your hboot airgo the error message. Again this might not be true. At this point all that matters is that your s-off and NOT bricked so instead of toying with an ruu I would choose a stock Rom .zip to flash if its truly stock that you want. Your firmware should be up to date if you took 2.06. There is no ruu for 2.06.
Sent from my HTC6435LVW using Tapatalk 4 Beta
What is s-off?
Sent from my Galaxy Nexus using xda premium
93fuelslut said:
What is s-off?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
It means you can write to any partition of your nand (internal memory). This means customs roms, kernels, splash screens, firmware, etc. When you are s-on it is more difficult, I can't get into why too many words it just is. If you're not s-off and you like flashing stuff look into it.
---------- Post added at 12:51 AM ---------- Previous post was at 12:41 AM ----------
xlxcrossing said:
It means you can write to any partition of your nand (internal memory). This means customs roms, kernels, splash screens, firmware, etc. When you are s-on it is more difficult, I can't get into why too many words it just is. If you're not s-off and you like flashing stuff look into it.
Click to expand...
Click to collapse
I'm not finding a solid explanation for error 158 which is disheartening - the best offerings are to change USB ports or restart the ruu. Like I said before you are fine on the software end, you can verify you have up to date firmware by comparing the latest below with what you have.
Baseband (radio) 1.01.04.0308
PRI 2.44_002
As for the hboot, how are you trying to flash it? In recovery?
The hboot needs to match the RUU. You need to find the original hboot . It is in a thread with hboot versions and radio versions.
Link to HBOOT please? and answering your questions
Could someone provide a link for the hboot instructions and flashing?
I think my problem is that moonshine screwed up my phone. I relocked my phone, but when trying to run moonshine again, it doesn't unlock the phone. It just says "WTF: What are you dong" and then it just stops and tells me to hit Enter to exit and the phone is still locked, hence why I think I can't flash HBOOT.
I try and flash HBOOT through recovery. I tried doing fastboot to flash it. Recalling from memory, I think the command was:
fastboot flash "file name.zip"
Click to expand...
Click to collapse
and then it says it can't open the file, unknown error. But I can't find any help guides or how-to's that explain the fix for this.
Thanks! Keep asking questions, cause I don't know what info is relevant.
ibthevivin said:
Could someone provide a link for the hboot instructions and flashing?
I think my problem is that moonshine screwed up my phone. I relocked my phone, but when trying to run moonshine again, it doesn't unlock the phone. It just says "WTF: What are you dong" and then it just stops and tells me to hit Enter to exit and the phone is still locked, hence why I think I can't flash HBOOT.
I try and flash HBOOT through recovery. I tried doing fastboot to flash it. Recalling from memory, I think the command was: and then it says it can't open the file, unknown error. But I can't find any help guides or how-to's that explain the fix for this.
Thanks! Keep asking questions, cause I don't know what info is relevant.
Click to expand...
Click to collapse
Moonshine isn't working because you are still s-off.
My thread has the original hboot and instructions to flash it. You do not flash in recovery. You do not put it on your phone at all. Do not push the file in recovery. Read and follow the instructions in the stock thread.
---------- Post added at 02:04 PM ---------- Previous post was at 02:02 PM ----------
You're doing the command wrong or you renamed it PL83IMG.zip.zip
Please, go in my thread, read each step perfectly and follow. It's really quite simple.
Difference
Is s-off/s-on and being locked/unlocked two different things?
Screenshot
Also here Phaded. I tried different variants of flashing the hboot. I renamed it from PL83IMG.zip to HBOOT.zip. It's not HBOOT.zip.zip cause I know Windows 8 automatically appends the end of the file name with the type extension. As you can see, I boot to fastboot, then run rebootRUU, then I'm trying to flash from there. I got frustrated and tried different things, even unpacking the .zip and trying to flash the .img file.
Thanks for your contribution to the community Phaded.
ibthevivin said:
Could someone provide a link for the hboot instructions and flashing?
I think my problem is that moonshine screwed up my phone. I relocked my phone, but when trying to run moonshine again, it doesn't unlock the phone. It just says "WTF: What are you dong" and then it just stops and tells me to hit Enter to exit and the phone is still locked, hence why I think I can't flash HBOOT.
I try and flash HBOOT through recovery. I tried doing fastboot to flash it. Recalling from memory, I think the command was: and then it says it can't open the file, unknown error. But I can't find any help guides or how-to's that explain the fix for this.
Thanks! Keep asking questions, cause I don't know what info is relevant.
Click to expand...
Click to collapse
Strike.
From my S-Off BadSeed DNA
ibthevivin said:
Also here Phaded. I tried different variants of flashing the hboot. I renamed it from PL83IMG.zip to HBOOT.zip. It's not HBOOT.zip.zip cause I know Windows 8 automatically appends the end of the file name with the type extension. As you can see, I boot to fastboot, then run rebootRUU, then I'm trying to flash from there. I got frustrated and tried different things, even unpacking the .zip and trying to flash the .img file.
Thanks for your contribution to the community Phaded.
Click to expand...
Click to collapse
You need to cd to the directory the file is in, which should be where fastboot.exe is
So if it's in say C:\sdk\
Type cd C:\sdk\
Then run command to fastboot
BOOM!
Alright. Worked. I'll keep you all posted. No one really mentioned in any of the tutorials and how-to's that it is VERY important to make sure to CD to the directory. Like there are developers who say just add it to the PATH in Environment Variables. I figured it was enough, but hey, I was wrong.
Live and learn right?
Thank you Phaded.
So basically my problem was, calling the hboot.zip file is not included under Environmental Variables. I have to intentionally CD to that directory.
Hmm, I must have missed putting in the cd step for the hboot. I'll go edit it.
Hi,
I have a Sprint CDMA HTC EVO 3D. I tried root and get S-OFF for it. Unfortunately I failed and now the phone fail to boot.
Below is what I did from which you might be able to diagnose it and give me suggestions.
(1) The original status of mu phone is:
Stock rom, I never root it before.
HBOOT-1.58.0000
Android Version: 4.03
HTC Sense version: 3.6
Software version: 2.95.651.6.710RD
(2) My root procedures:
I followed this post: http://forum.xda-developers.com/showthread.php?t=1813818
I successfully unlocked phone with HTCDev, successfully Flashed 4EXT recovery, and successfully installed Superuser-3.1.3-arm-signed.zip. I also booted into sytem, everything worked well.
However I failed in next step of JuopunutBear's Wire Trick (S-OFF). When I ran ControlBear.exe, it finally hanged there.
Current status of my phone:
Unfortunately I did not make a backup to my original ROM, so there is no way to revert back by restoring backup.
Now the phone is in unlocked status, I was able to boot to HBOOT and also enter 4Ext recovery, however I am not able to boot into Android. If I try to boot into Android, it always hang at black screen.
I am able to boot to fastboot (USB) mode, I tried to flash some stock ROM (listed at http://forum.xda-developers.com/showpost.php?p=24268786&postcount=209), but I failed. For example, I ran a RUU of 2.89.exe, it detected my phone version is 2.95, and further update RUU failed.
Looks like my partition is ruined, but I might be wrong.
ANyone can help me to restore my phone to working status? At least I need the phone to be able to boo to Android.
Here are also some tries that I ever did:
(1) I ever put the PG86IMG.zip file (downloaded from http://forum.xda-developers.com/showpost.php?p=21593454&postcount=564) to my sdcard, still failed.
(2) I ever formatted all partition from 4EXT recovery
lsdyna said:
Here are also some tries that I ever did:
(1) I ever put the PG86IMG.zip file (downloaded from http://forum.xda-developers.com/showpost.php?p=21593454&postcount=564) to my sdcard, still failed.
(2) I ever formatted all partition from 4EXT recovery
Click to expand...
Click to collapse
EDIT:
Okay. I've got some questions.
1. You're stuck on some black screen as you said. It boots past the white HTC splash and then it's stuck on that black screen, right. Do you mean the juopunutbear "arrow screen" - juopunutbears boot.img?
2. I think if you had flashed the original boot img everything would have been fine.
3. The easiest way is to flash to stock, so lets try to figure out why it doesn't flash.
MrJyrks said:
Okay. So from what I understood, you are stuck on the black juopunutbear screen, right?
Click to expand...
Click to collapse
Yes, after I was stuck with black juopunutbear screen, I took battery out, reboot again, never was able to root to Android. I am only able to boot to HBoot.
lsdyna said:
Yes, after I was stuck with black juopunutbear screen, I took battery out, reboot again, never was able to root to Android. I am only able to boot to HBoot.
Click to expand...
Click to collapse
And you can boot to recovery, right?
EDIT:
One more thing. Which ruu were you trying to run
Edit2:
What's your CID? Use "fastboot getvar cid" or "fastboot oem readcid" (without quotes).
Edit3:
BTW, this was on the wire trick page... http://unlimited.io/jbtroubleshooting.htm - TROUBLESHOOTING There was everything you needed to know when you failed at something. Remember that page. You may need it the next time you try to do the wiretrick.
Q: Were you using a linux distro for the wire trick and did you use the appropriate files for wire trick since GB and ICS have separate tools?
If you want I may assist you in gaining s-off if we get this thing functional again.
Yes, I am able to boot to recovery.
I tried ROM's here
http://forum.xda-developers.com/showpost.php?p=24268786&postcount=209
and
http://forum.xda-developers.com/showthread.php?p=22519105#post22519105
I tried 2.17, 2.89, unfortunately none of them worked
My CID is SPCS_001
MrJyrks said:
And you can boot to recovery, right?
EDIT: One more thing. Which ruu were you trying to run
Edit2: What's your CID? Use "fastboot getvar cid" or "fastboot oem readcid" (without quotes).
Click to expand...
Click to collapse
lsdyna said:
Yes, I am able to boot to recovery.
I tried ROM's here
http://forum.xda-developers.com/showpost.php?p=24268786&postcount=209
and
http://forum.xda-developers.com/showthread.php?p=22519105#post22519105
I tried 2.17, 2.89, unfortunately none of them worked
My CID is SPCS_001
Click to expand...
Click to collapse
Aw man, I'm completely sorry I didn't see this: Software version: 2.95.651.6.710RD
That means, no RUU for you cause htc/sprint wasn't kind enough to provide the ruu. Also FYI you can't flash a ruu lower than your current one.
So your best bet is to flash the most stock 2.95 cdma rom you could find and right after, flash the stock cdma evo 3d kernel through fastboot or 4ext (I think 4ext smartflash does the same thing). Try to find something that's COMPLETELY STOCK - with no mods whatsoever or if you couldn't find any, try something that's almost* stock. That should get you booting and you can try s off again.
Edit: This shall work. http://www.negalite.com/index.php?topic=21.0 Try it and report back!!!
Now I only want to revert my phone to stock, not considering root at present time.
I searched 2.95 ROM, unfortunately the highest version that I can find is 2.89. Does this mean I have no way to revert my phone to live? Thanks a lot.
MrJyrks said:
Aw man, I'm completely sorry I didn't see this: Software version: 2.95.651.6.710RD
That means, no RUU for you cause htc/sprint wasn't kind enough to provide the ruu. Also FYI you can't flash a ruu lower than your current one.
So your best bet is to flash the most stock 2.95 cdma rom you could find and right after, flash the stock cdma evo 3d kernel through fastboot or 4ext (I think 4ext smartflash does the same thing). Try to find something that's COMPLETELY STOCK - with no mods whatsoever or if you couldn't find any, try something that's almost* stock. That should get you booting and you can try s off again.
Click to expand...
Click to collapse
I ever run a RUU 1.13...exe for mmy phone, it said my device is having 1.000, and it tried to update to 1.13. However, the update procedure always failed at some point, some at beginning, some failed at 'wring signature'...
MrJyrks said:
Aw man, I'm completely sorry I didn't see this: Software version: 2.95.651.6.710RD
That means, no RUU for you cause htc/sprint wasn't kind enough to provide the ruu. Also FYI you can't flash a ruu lower than your current one.
So your best bet is to flash the most stock 2.95 cdma rom you could find and right after, flash the stock cdma evo 3d kernel through fastboot or 4ext (I think 4ext smartflash does the same thing). Try to find something that's COMPLETELY STOCK - with no mods whatsoever or if you couldn't find any, try something that's almost* stock. That should get you booting and you can try s off again.
Click to expand...
Click to collapse
lsdyna said:
I ever run a RUU 1.13...exe for mmy phone, it said my device is having 1.000, and it tried to update to 1.13. However, the update procedure always failed at some point, some at beginning, some failed at 'wring signature'...
Click to expand...
Click to collapse
This shall work. http://www.negalite.com/index.php?topic=21.0 Try it and report back!!!
Flash like a normal rom and don't forget to flash the boot img because that's what's really causing you problems right now. I'd choose the deodexed one from there.
My HBoot screen shows below:
SHOOTER XC SHIP S-ON RL
HBOOT-1.58.000
RADIO-1.09.00.0108
OpenADSP-v02.6.0.2226.00.0217
DO you think I still have chance to save my device? Thanks a lot.
lsdyna said:
I ever run a RUU 1.13...exe for mmy phone, it said my device is having 1.000, and it tried to update to 1.13. However, the update procedure always failed at some point, some at beginning, some failed at 'wring signature'...
Click to expand...
Click to collapse
lsdyna said:
My HBoot screen shows below:
SHOOTER XC SHIP S-ON RL
HBOOT-1.58.000
RADIO-1.09.00.0108
OpenADSP-v02.6.0.2226.00.0217
DO you think I still have chance to save my device? Thanks a lot.
Click to expand...
Click to collapse
If you have access to the recovery, most likely, yes.
Hello MrJyrks,
Thank you so much for the link! I am eager to try that. Before I do that I think I shall ask two questions to avoid further mess up the device:
Question #1: To install the deodexed rom, which is the correct way:
(1) Rename the ZIP file to PG86IMG.ZIP, put to root of sdcard, then boot, letting the Bootloader to do the update.
(2) In 4EXT recovery, enable smartflash, enable script asserts, then install the zip from the root of sdcard.
Question #2: You said I shall flash boot image, can you tell me how to do this? I mean, where shall I get the boot image file? Flash it with 4EXT? SHall I do it before or after install ROM zip file?
Thank you very much for your helps!!!
MrJyrks said:
This shall work. http://www.negalite.com/index.php?topic=21.0 Try it and report back!!!
Flash like a normal rom and don't forget to flash the boot img because that's what's really causing you problems right now. I'd choose the deodexed one from there.
Click to expand...
Click to collapse
I tried install the stock ROM from your link (using 4EXT with smartflash enabled and script asserts enabled.) . Amazing that installation completed successfully (indeed this is the first ROM zip that I was able to install successfully since I mess up the device). When I exit After that, it did some further update which I guess is the boot.img that you mentioned.
4EXT it said 'a pending update for your boot partition is detected' and I think it was doing the boot image flash that you mentioned, right?
Unfortunately when I boo the device, I still got black screen.
Now I am unlocked and also rooted (since I successfully installed superuser in 4EXT). DO you think I shall lock the devioce before installing the stock ROM? If so, one possible issue is that if I relock the device, I found 4EXT is not available. In that case, how shall I install the ROM zip file?
Thanks.
MrJyrks said:
This shall work. http://www.negalite.com/index.php?topic=21.0 Try it and report back!!!
Flash like a normal rom and don't forget to flash the boot img because that's what's really causing you problems right now. I'd choose the deodexed one from there.
Click to expand...
Click to collapse
Further update:
I flashed boot image by: fastboot flash boot boot.img which is included in the stock ROM zip file.
The flash went successfully. However, I am still not able to boot to Android. WHat I have is the device hang there, alternatively displaying logo with white background, and black screen.
MrJyrks said:
This shall work. http://www.negalite.com/index.php?topic=21.0 Try it and report back!!!
Flash like a normal rom and don't forget to flash the boot img because that's what's really causing you problems right now. I'd choose the deodexed one from there.
Click to expand...
Click to collapse
I wiped cache and Dalvic, then re-flash the ROM, now I am able to boot as normal.
MrJyrks, you are my life save!!!
Your helps are sincerely appreciated !
lsdyna said:
I wiped cache and Dalvic, then re-flash the ROM, now I am able to boot as normal.
MrJyrks, you are my life save!!!
Your helps are sincerely appreciated !
Click to expand...
Click to collapse
You're welcome! I'm glad I could help!
---------- Post added at 12:02 PM ---------- Previous post was at 11:16 AM ----------
Oh, and if, in the future, you do try the wire trick and get stuck at some point you can revert the changes with ControlBear -r or ControlBear -f from command line. And you may also PM me if you need any help. Cheers!
MrJyrks, thank you so much!!!
MrJyrks said:
You're welcome! I'm glad I could help!
---------- Post added at 12:02 PM ---------- Previous post was at 11:16 AM ----------
Oh, and if, in the future, you do try the wire trick and get stuck at some point you can revert the changes with ControlBear -r or ControlBear -f from command line. And you may also PM me if you need any help. Cheers!
Click to expand...
Click to collapse
Similar problem, can't return to stock
I have a problem similar to lsdyna's, and am hoping that even though this post is old, MrJyrks or someone might be able to help me.
I am unsuccessfully trying to return my phone to stock. First a bit of history.
I had 2.95.651.6.710RD s-on hboot 1.58 Android Version: 4.03 HTC Sense version: 3.6 on my phone, and wanted root. I didn't need s-off, just wanted to root so could do some tweaking (stop some apps from autostarting, stop some form getting network access, etc.) so loaded 4EXT Recovery Touch, and got root (fastboot oem get_identifier_token method), got superuser in there, and happily began tweaking. Famous last words... I didn't make a backup right away (learned my lesson!) and suddenly found a 'overtweaked' sluggish phone on my hands.
Thought best thing would be to lose the root & return to stock & start over, carefully, making backups.
So I used Fastboot (fastboot oem lock) to lock it (worked) and proceeded to try to load RUU_Shooter_ICS_35_S_Sprint_WWE_2.89.651.2_Radio_1.09.00.0706__NV_NV_SPCS_1.43_release_271101_signed.exe into it [via my computer], but didn't realize until reading MrJyrks post that a lower RUU couldn't be used.
I now am relocked (phone does boot up, but can tell the system tweaks are still slogging it), lost the recovery, and wondering what to do... do I try putting recovery back in & using the Negalite 2.95 stock deodex ROM MrJyrks mentioned? If so, how do I use that zip file method verses the exe one I tried thru my computer?
Thanks for the help
You had issues with the RUU because your main version is higher than that contained in the RUU.
Unlock, flash recovery again. Boot into recovery and flash this zip: https://copy.com/wlVvwssXXNN00Pe
That will lower your main version. Relock the bootloader, put the phone into fastboot USB mode, then run the RUU while in fastboot USB mode.
Should be back to stock after that.
Q&A for [ROM][4.4.4_r2][OFFICIAL][GPL] LiquidSmooth v3.2 - vigor - 10|12|14
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
bunchies said:
Final KitKat build coming soon, Lollipop was released this morning :thumbup:
Let's see if the Rezound can run android 5.0
Click to expand...
Click to collapse
Let's hope so!
I'm thinking of trying this ROM out coming from Cyanogen mod and I am S-On. If I follow the instructions in the OP should I be ok? I see I will have to flash the boot.img separately.
catcher8587 said:
Let's hope so!
I'm thinking of trying this ROM out coming from Cyanogen mod and I am S-On. If I follow the instructions in the OP should I be ok? I see I will have to flash the boot.img separately.
Click to expand...
Click to collapse
Yeah, you will be fine
s-on users flash boot.img in fastboot
Last Build
I set the last build and at once found an error. If to come Settings - the Mobile network - Settings of the operator you give out an error: "In application of "com.android.phone" there was an error..." At all so? I quickly discharge the battery for some reason!
Crash video playing
added small problem... When I want to view video sometimes issues the error message. Video doesn't play...
re:chrome floating windows
Just uninstall and download an older version of chrome. Then, don't accept the update. You can't turn off the floating windows. Very annoying
HTC Rezound Liquidsmooth 3.2 ROM install failure
I used this link (theunlockr.com/2013/10/22/how-to-root-the-htc-rezound/) on my stock HTC Verizon Rezound to unlock the bootloader, installed TWRP, and SuperSU to gain access to root.
Then I downloaded LiquidSmooth 3.2 11/5/14 R2 -- Android 4.4.4 and Gapps 4.4.4 Build 8.1 (not Build 7 on this site) I used TWRP to flash both files in the same flash event to the phone. I had placed the files on the INTERNAL SD in the DOWNLOAD directory. Wiped before and after the flash. Phone came up to HTC screen, Blinked, and returned to HTC screen. Waited 10 minutes or so and had to pull battery . Tried another boot with same results. Restored. Repeated same results.
Downloaded the LS v3.2 file again. Downloaded an md5 checker program to my computer. Both files passed. Repeated using second v3.2 file with same results. Downloaded the 8/21/2014 version of the file, md5 checked it, and repeated with same results.
Then downloaded the final LS v2.9 JB4.2.2 file and the appropriate GAPPS file and md5ed it. Repeated with same results.
I am now back to my rooted but stock ROM. I would like to get this LS v3.2 KitKat ROM installed, but am at my wits end.
I also used this link (android.wonderhowto.com/how-to/ultimate-guide-using-twrp-only-custom-recovery-youll-ever-need-0156006/) to troubleshoot. That is why I did a wipe in advance of the first install attempt and I think most of the others as well, although I couldn't tell it helped. I tried the Fix Permissions hint several times but it failed each time.
The only think I have ever read about on HTC phones is S-On or S-Off, but I don't think this applies as neither link source I referred to mentioned S-ON.
Any help would be appreciated. Thanks in advance.
When you are S-ON you have to manually flash the boot.img via Fastboot after flashing the ROM image in recovery... or boot recovery with fastboot not from the phone... in order to boot successfully. When an HTC device is S-ON, the boot partition is write protected from recovery if it is booted from the phone.
Thanks a Million or perhaps 10 million!!!
acejavelin said:
When you are S-ON you have to manually flash the boot.img via Fastboot after flashing the ROM image in recovery... or boot recovery with fastboot not from the phone... in order to boot successfully. When an HTC device is S-ON, the boot partition is write protected from recovery if it is booted from the phone.
Click to expand...
Click to collapse
I'll not bore you with the details, but I just now found you had replied to my question. I refreshed myself on fastboot (I used it in the unlock process a few days back), extracted the boot.img file, and flashed it.
Guess What? It worked.
Thanks a lot. I do think it would be great if people would include a brief statement on HTC ROM installation Instructions, "If you are not S-OFF you must use fastboot to flash the boot.img file (extract from ROM zip) after flashing the ROM. If you do not know what that means, Google it!"
BTW, if for some reason I every wanted to go back to my stock ROM, I assume that I would have to do the same thing (Flash ROM following by Fastboot Flash boot.img file) after restoring or would my Nandroid backup work? I doubt it would for the same reason. It will be hard to find that file (unless it is contained in the backup) since the ROM was by OTA programming.
Thanks again,
Terry
xdatsellers said:
I'll not bore you with the details, but I just now found you had replied to my question. I refreshed myself on fastboot (I used it in the unlock process a few days back), extracted the boot.img file, and flashed it.
Guess What? It worked.
Thanks a lot. I do think it would be great if people would include a brief statement on HTC ROM installation Instructions, "If you are not S-OFF you must use fastboot to flash the boot.img file (extract from ROM zip) after flashing the ROM. If you do not know what that means, Google it!"
BTW, if for some reason I every wanted to go back to my stock ROM, I assume that I would have to do the same thing (Flash ROM following by Fastboot Flash boot.img file) after restoring or would my Nandroid backup work? I doubt it would for the same reason. It will be hard to find that file (unless it is contained in the backup) since the ROM was by OTA programming.
Thanks again,
Terry
Click to expand...
Click to collapse
Most general tutorials on flashing ROMs on HTC devices includes this information, although most devs will say their ROMs are for S-OFF devices only, it is assumed with a little fastboot trickery most ROMs will work fine, but devs usually make the assumption you know what you are doing.
I would HIGHLY recommend you go S-OFF... if something catastrophic happens and you are S-ON there is often no method of recovery, since all current RUU (HTC's proprietary ROM restoration image) files are prior to current, so do downgrade and restore to stock you must be S-OFF. Rumrunner makes the S-OFF process pretty painless if you are on a custom ROM already.
The boot image, or more accurately the /boot partition, cannot be written to under normal recovery well S-ON, so that affects a nandroid restore as well, you would have to extract the boot image and flash it manually as well to restore a nandroid. BUT, if you boot the recovery image via fastboot it gets around the /boot write restriction even when S-ON... this is a key difference, essentially you are taking the recovery image and telling the phone "this is your new kernel, start it like a ROM" which gets around some of the S-ON restrictions.
Grey network bars
Hello bunchies
I really enjoyed using this rom except this problem my network bars are grey but i can make and receive calls and use the 3g on slow speed (the problem when i call the customer service centre i can't press numbers)
I've checked hboot radio and recovery they are updated
Sorry for my bad English and thanks in advance
Need help to install liquidsmooth
Hi I have a verizion htc rezound s-on that is unlocked with amon ra recovery ics rooted super su . What do i need to do to install liquid smooth
Thank you
Sent from my SM-N900 using XDA Free mobile app
edwardnizz said:
Hi I have a verizion htc rezound s-on that is unlocked with amon ra recovery ics rooted super su . What do i need to do to install liquid smooth
Click to expand...
Click to collapse
Assuming you are on current Hboot & radios, upgrade to latest TWRP, flash ROM ZIP and Gapps, fastboot flash boot.img, then reboot and enjoy.
Hello i'm just asking if there wont be any problems with rom update such as recovery boot loop or Freeze or crashes .....etc kthnxbai
can't send SMS or ssd with liquidsmooth 3.2
Hi. As the title says , i cant sens SMS nor use ussd codes. Another issue is that i can't play music. Any help would be appreciated.