Please help me I may be in some deep poop here
Hi, I recently tried to root my HTC one X from the latest firmware (jellybean) using this http://ausdroid.net/2012/04/02/how-to-root-the-htc-one-x/ method. Unfortunately it didn't work and instead put the phone into a boot loop. I managed to flash a version of CWM recovery onto it, and I downloaded the viperX http://forum.xda-developers.com/showthread.php?t=1745176 rom and used adb push to put it onto the sd card so I could install it. I installed it and select no custom kernal when it asked me and it had no effect. So i tried installing it again but I ticked custom kernal to see what it did. Big mistake - the phone tries to boot, it has the viperx snake thingy in the boot screen, it gets to the lock screen and is completely unresponsive and crashed. I tied downloading another rom (nocturnal) and installing that but it had no effect.
I've tried using a RUU to fix it but none of the ones I tried work, they get an error, wrong bootloader version. I relocked the bootloader and flashed a stock recovery onto it but still no luck.
Please please help me anyone!!!!
Some info:
CID: VODAP021
S-On
Hboot 1.36.0000 - i believe this coult be the problem why the ruu won't work
CPLD-None
Radio-5.1204.162.29
eMMC-bootmode: disabled
CPU-bootmode; disabled
hw secure boot; enabled\
modem path; off
What custom recovery do you have ? Type and version ?
First, you should be able to mount the sdcard as a usb diskdrive from within the recovery !
Second, you need to flash the boot.img file from the viper.zip (its inside the rom.zip).
Third, you need to perform a FULL wipe in the recovery before installing the actual rom.
Your hboot is not the problem. Its one or more of the things above.
And also check what is on top of your bootloader. Does it say ENDEAVORU ?
First off, thanks for your help. I've unlocked the bootloader again, flashed the boot image from the viperx zip and reinstalled viperx but it still won't boot. How do you perform a full wipe, and also in the installer for the rom it said something about flashing the kernal manually if you don't have s-off (in the botloader it says s-on).
BTW i'm using cwm recovery v6.0.1.9
Oke, first of all download the viper x 3.3.7. The JB version !
A FULL wipe ? You have to delete all data in the recovery. Wipe caches,dalvik cache, wipe data/factory reset. Format cache, data, system. Then install the Rom. And right before you install the rom you unhook the usb cable too.
The boot.img is flashed with a command like this
Fastboot flash boot boot.img
Used that before ?
Ok there's my first problem i had an old version of viperx, it was an ics one and my phone had jb on it.
Yes i'm familiar with using the fastboot flash command, its the only way I managed to get cwm on there
Also, just to be clear, I flash the new boot.img (the one in the viperx folder) before or after I install the new rom?
Yes you flash the new boot.img, perform a full wipe in the recovery, unhook the usb cable ! Then install the new rom.
Select full wipe in the installer, kernel question is answered by pressing viper x delivered.
Ok thanks, i'm trying to put the new rom onto the phone now, I've formatted system, /sdcard, ect in cwm plus cleared the caches, I've mounted sdcard and typed into adb: adb push ViperX3.3.7.zip sdcard, i'm waiting for it to finish pushing, its taking a while
Its done, by viperx delivered you mean viperx supplied right? I used that one, its installing now, fingers crossed..
Its easier to go into the mounts and storage section of the recovery and mount is as a mass storage device (diskdrive) its like inserting a usb stick
OK its booting, it had the viperx snake going across the boot screen, now its displaying the htc one boot screen...
Sucses! Its working again. I'll make sure to install cwm and make a backup straight away.
Thankyou so much for your help, i've sent you a little something for your trouble
Thanks mate, appreciate it ! have fun with Viper X JB !
CASE CLOSED !
Related
Hi All,
Been having issues with my HTC One X for the past week now and haven't been able to solve it via google or searching this forum, so was hoping one of you kind people can assist a bit.
I do apologise if this issue has already been posted and I missed it, if you can link me I'll be eternally grateful.
Basically, had a few issues annoying me with my HTC so wanted to stick a custom ROM on it. Did some searching about, eventually got a plan together to unlock and root it. All went fine, unlocked it (S-On still) got TWRP recovery on it (Chose this as the ROM I was looking at claimed to be not compatible with CWR) and was booted back into my stock droid.
First thing I did after a successful boot was to go back into recovery and make a full backup (I may have not ticked the Cache and _android.secure)
Played about with the phone again a bit, getting some of the apps back on as it had been wiped, then made a second backup (This one I know I ticked all the boxes for)
Next I tried putting CleanROM on, but could get past the white HTC screen boot loop, after various reflashing the Boot.IMG and clearing cache, so fired up TWRP and restored back to my second backup. All back to normal.
Used the phone as normal for a day or so then I tried flashing another ROM (ViperX) same thing as CleanROM (White HTC screen boot loop) and then went on to try Team Baked's ROM. Managed to get this working successfully, however the ROM was not to my liking and decided to go back to my stock backup. Here's where the issue started.
Now, when restoring the backup the phone boots as far as displaying my background and the status bar at the top, however I cannot pull the status bar down and the ring to unlock the phone with doesn't appear. It sits here for a few second and then reboots. Boot loop.
I've tried clearing cache, restoring various different ways and restoring the boot.img (though I'm not sure I have the right one) but nothing works.
The last variation I tried for restoring involved:
1. Clearing the phone via TWRP (System Restore/Clear Cache/Clear Davik/Clear System/Clear SD Card (heard this can cause issues)/Clearing Android.Secure in that order)
2. Reboot into recovery
3. Repeat step 1 (in case of locked files)
4. Reboot into Recovery
5. full restore (With MD5 check enable)
6. Clear Cache and Dalvik (Tried with just cache, also done Fastboot clear cache in another attempt)
7. Attempt to boot into OS.
As I mentioned earlier, I'm not sure if I have the right boot.IMG for my phone Model/kernal/other, to be honest I'm not entirely sure of the requirements. The details of my phone I've collected so far are:
Getvar version-main (Not sure if this is kernal or what) = 2.17.771.3
hBoot = 1.12.0000
radio = 2.1204.135.20H
CID = H3G_001
Basically, as far as I can tell from the masses of reading I've been doing, I won't be able to update to custom JB for a while so want to get back to my stock ICS and then OTA to JB when my carrier releases their version, then maybe sometime in the future when the ROM specific to my phone has been cracked consider switching to a custom.
on a final note, I've tried flashing both my backups, same result. I've also tried restoring the stock recovery and doing a system recovery with that. It appears to go through the motions (phone with green arrows? Also had the red exclamation mark, but only once of the 3 attempts) then reboots and it's still the same issue.
Thanks for reading through, any advice would be much appreciated. Used to love my phone but now can barely stand to look at it.
Cheers,
Sean
Ok, so I've now downloaded a different boot.img which should be for stock ics and after flashing that, then flashing stock recovery and doing a system restore via bootloader I will 50% of the time get the lock screen and when I unlock it I see the white HTC screen of the initial setup, then it sticks there a while and reboots. It also reboots after left at the lock screen.
To me this seems like it's doing a check or looking for a certain piece of software/file that's missing but is required to finish the start-up process. Anyone any ideas?
Even if someone can point me in the right direction for an RRU for my phone as football's RRU's seem to be the only one that has the one I need but as of 5 days before all this happened the site they're hosted on doesn't allow 500+MB downloads for free members
Cheers,
Sean
**EDIT** Just done a full device wipe then restored only the SYSTEM partition and manually flashed the boot, then when I restarted it sat on the white HTC on the device setup but eventually loaded up, allowed me to complete the device setup and then loaded into the OS. All seemed fine aside from the phone being stuck in turning off airplane mode. Rebooted it to see if that would clear it up and now I'm back to bootloops before the lock screen appears (I just get my background and status bar)
So you have a nandroid backup ! Then do this
Wipe all in recovery and i mean ALL except the sdcard obvious ! system,data,caches,dalvik cache...
Then boot back into fastboot usb mode and flash the boot.img from the nandroid. Taken with TWRP the boot.img is called something like
Emmc.boot.win (or at least similar to this)
You can flash this file with fastboot command
Fastboot flash boot name of the boot.img (.win in this case)
Then enter the recovery and full wipe if you didn't o that already !
Restore the nandroid and boot it up :thumbup:
Should work
Perfect! Thanks so much man, I never even thought to flash the .wim, thought it had to be .img. Just successfully booted fully back into my old system. Hopefully will stay stable the next hour or so but looking good!
Thanks again,
Sean
Need help!!!
I'm facing the same problem with my device, i have ulocked bootloader from HTCdev and flash TWRP recovery, was trying to flash Maximus but unfortunately after flashing Maximus in TWRP my device stuck on boot logo.
Hboot: 1.12.0000
CID: HTC__J15
version-main: 2.17.415.2
Please help.
Did you flash boot.img through fastboot?
Sent from my HTC One X
TToivanen said:
Did you flash boot.img through fastboot?
Sent from my HTC One X
Click to expand...
Click to collapse
Yes, the one came with Android_Fastboot_KIT_V12.x
And make sure you flash a 2.17 based ICS rom. You can not run the maximus JB rom on that 1.12 hboot !
Mr Hofs said:
And make sure you flash a 2.17 based ICS rom. You can not run the maximus JB rom on that 1.12 hboot !
Click to expand...
Click to collapse
Then, i have done the mistake there. Now, please guide me what i need to do to get out of this problem.
I have forget to mention my device still S-ON
Please guide, sorry for troubling.
Download a 2.17 ics Rom and copy it to the phone (mount the sdcard within the recovery as a usb disk)
Take the boot.img file from that rom and copy it to the tool you used to flash it
Then enter the recovery and wipe EVERYTHING except sdcard ofcourse !!! (Cache,dalvik cache, system and data)
Then install the Rom.zip
Mr Hofs said:
Download a 2.17 ics Rom and copy it to the phone (mount the sdcard within the recovery as a usb disk)
Take the boot.img file from that rom and copy it to the tool you used to flash it
Then enter the recovery and wipe EVERYTHING except sdcard ofcourse !!! (Cache,dalvik cache, system and data)
Then install the Rom.zip
Click to expand...
Click to collapse
Thank you so much.
No problem mate ! :thumbup:
If you're looking for a Rom, I've got hboot 1.12 as well and tried a few ROMs and only ones I got working were:
Team Baked, based on jellybean though still works with 1.12. No Sense though, and a few things weren't to my liking (to name a couple,backlights on buttons didn't work and multitask button was switched back to menu button like in older devices)
SkyDragon, ics ROM with sense. Only had this a short while but appeared to be an exact stock ROM, everything working the way it should, and with a few added extra improvements.
Good luck
Slaverty said:
If you're looking for a Rom, I've got hboot 1.12 as well and tried a few ROMs and only ones I got working were:
Team Baked, based on jellybean though still works with 1.12. No Sense though, and a few things weren't to my liking (to name a couple,backlights on buttons didn't work and multitask button was switched back to menu button like in older devices)
SkyDragon, ics ROM with sense. Only had this a short while but appeared to be an exact stock ROM, everything working the way it should, and with a few added extra improvements.
Good luck
Click to expand...
Click to collapse
Is there anyway to restore it to the backup i have made with TWRP which is still in the sdcard???
sfawad81 said:
Is there anyway to restore it to the backup i have made with TWRP which is still in the sdcard???
Click to expand...
Click to collapse
Yes.
Copy the boot.img from the backup to your PC (you can mount SD card as USB from TWRP), flash it:
fastboot flash boot boot.img
And restore backup from TWRP.
Yeah, if you follow Mr hofs 1st post on the 1st page he describes all the steps required to restore. Worked perfectly for me
Slaverty said:
Yeah, if you follow Mr hofs 1st post on the 1st page he describes all the steps required to restore. Worked perfectly for me
Click to expand...
Click to collapse
Thanks alot, got it back as it was before.
Need to clear a doubt; will I be able to update my device with the OTA, as my device is unlocked, S-ON & TWRP installed?
I hope so, I'm in the same boat as you. From what I've been reading, it should still be possible as long as you put back the stock recovery and relock the bootloader.
This website offers links to download the stock recovery
http://www.androidauthority.com/one-x-revert-stock-recovery-76854/
As for relocking the bootloader, I think the process is to run this command whilst in Fast Boot USB mode
fastboot oem lock
After it's run there should be a purple "RELOCKED" at the top of your bootloader menu.
Remember to flash the recovery BEFORE you relock the bootloader
You do not have to lock the bootloader, just the stock recovery is needed ....
Stock rom (out of the box stock)
Stock boot.img
Stock recovery
Here is the 2.17 based stock recovery for those who needs it
http://db.tt/U5CK4noo
After a few unsuccessful attempts to flash my HTC One X up to CM10.1, I found out my hboot version was too low, so after much reading, trying and failing etc. I managed to get my hboot up to 1.36 (even after having my phone stuck at the white HTC boot logo for about 2 hours), but I still cant install the version of CM10.1 that I spent hour trying to do at the weekend (cm-10.1-20130312-NIGHTLY-endeavoru.zip) it still fails at the hboot checking point.
My main question is what would be the process that I would need to get the lastest version of CM10.1 to work?
Details from my phone
hboot - 1.36
CID - ORANG001
RUU - 2.17.61.3
I know there is a new boot.img that needs to be flashed after CM10.1 has gone in and was reading earlier about the stable releases, which is fine I have no problem with that, but I just cant figure out why I still cant flash 10.1 even after hboot upgrade which was a pain having to go back to a stock rom after re-locking my bootloader etc.
I know this stuff gets asked so many times, this is probably a repost but I just dont want to have to troll through hundreds of posts if the process is just, flash this, now this... done...
Thanks for reading.
Check for something called "vendor" it needs to be installed after the rom. Dont shoot me for this info....i haven't checked it myself ! But read something about it from the sideline
Go to CM thread in original dev section, in first post you can find a vendor installer zip that you must flash in recovery after flashing the ROM.
This is due to vendor files being taken down (DMCA),that's why latest zips have them missing and can't boot.
Sent from my One X using xda premium
LOL TT the sideline posting ninja !!!
TToivanen said:
Go to CM thread in original dev section, in first post you can find a vendor installer zip that you must flash in recovery after flashing the ROM.
This is due to vendor files being taken down (DMCA),that's why latest zips have them missing and can't boot.
Sent from my One X using xda premium
Click to expand...
Click to collapse
Yeh but thats my problem, how can I flash the vendor installer after the rom when I cant actually get the rom to flash in the first place?
If I grab the lastest nightly from clockworkmod app on my phone, tell it to wipe cache and then install rom, it reboots the phone like normal, I get the ruu replacement screen it does some of it, then flat out fails at the hboot check, I then have to use recovery to reboot the phone and it back on the original rom but I have to setup everything again (install apps and such, connect to my google account for contacts etc)
Bump
The steps are
Make a FULL wipe in the recovery
Factory reset
Wipe cache partition
Advanced - wipe dalvik cache
Mounts & Storage - format cache,data,system
Then install cm10.1, gapps,vendors - DO NOT REBOOT IN BETWEEN AND ALSO NOT AFTER THE INSTALL !
now head back to the bootloader
Adb reboot bootloader
And flash the boot.img from the cm10.1.zip file
Fastboot erase cache
Fastboot flash boot boot.img
Fastboot erase cache
Fastboot reboot
Should be it !
So I've bought my phone secondhand a few months before, rooted and with ARHD 9.X.
Then I decided I want a JB custom ROM and tried to upgrade to ARHD 19.2 (JB), and also Viper X 3.4.0 (JB). - NO LUCK.
I,ve upgraded HBOOT to 1.39 and followed all the steps required for Jelly Bean upgrade (or so I think).
ISSUE
After flashing, my HOX managed to boot the system, even start the start up process, but after a minute or two everything froze up and restarted, again boot, restart... Some kind of a bootloop.
Then I just went to the older version of Viper X 2.7.0.
I really want a new JB custom ROM, but can't have it because I'm obviously missing something.
Please assist...
Here are some screenshoots with software information. cidnum: HTC__032
http://forum.xda-developers.com/attachment.php?attachmentid=1830866&stc=1&d=1364160760
http://forum.xda-developers.com/attachment.php?attachmentid=1830867&stc=1&d=1364160760
Did you flash the boot.img from the new viper rom ? And did you perform a FULL wipe in the recovery before you installed the new rom ?
And for additional info, can you do a fastboot command for me
Fastboot getvar version-main
AW: Can't flash any JB custom ROM
If you didn't flash the the boot img then download it from the ARHD thread. There is a bat. Which do it for you. Very easy
Sent from my HTC One X using xda premium
I did flash boot.img that was on the viperx's thread, also tried with the .bat file when I was trying to flash new ARHD ROM.
Before flashing every ROM I did factory reset/wipe, wiped cache partition and wiped dalvik cache.
Mr Hofs, I did the following command:http://forum.xda-developers.com/attachment.php?attachmentid=1832227&stc=1&d=1364214488
May i suggest you turn to stock first to check its all fine
http://bugsylawson.com/index.php/fi...-r-radio-5120416229-release-302015-signedexe/
Download the ruu, put the phone in the bootloader/fastboot usb mode ....lock the bootloader
Fastboot oem lock
Then right click the ruu and select " run as administrator"
ok, so I just installed the stock rom with your instructions and my HOX froze again... really frustrating.
do U have any more ideas what can I do?
vander4 said:
ok, so I just installed the stock rom with your instructions and my HOX froze again... really frustrating.
do U have any more ideas what can I do?
Click to expand...
Click to collapse
Hey , I have that same problem , HOX branded from Orange , unlocked bootloader , flashed recovery CWM 6.0.9.7 , full wipe , flashed rom :
[ROM] HTC One X *STOCK* ROM | 3.18.401.1 | Jelly Bean | HTC Sense 4+
Flashed boot.img from rom and phone freeze at startup logo ...
I read 61 pages in rom development and see few ppl have that same problem but no one answer nothing usefull ...
please help ...
but I actually manage to get past the startup logo and I am able to enjoy JB for a minute or two..... then freeze.
freemaind, I've read a lot of posts with the same problem as yours, but i didn't find any that actually had the "freeze" within the newly installed ROM.
vander4 said:
but I actually manage to get past the startup logo and I am able to enjoy JB for a minute or two..... then freeze.
freemaind, I've read a lot of posts with the same problem as yours, but i didn't find any that actually had the "freeze" within the newly installed ROM.
Click to expand...
Click to collapse
So you installed the ruu with succes ? If so and it still happends there is something wrong with the phone !
But on a ICS (viper x 2.7) rom you do not have this problem ?
Mr Hofs said:
So you installed the ruu with succes ? If so and it still happends there is something wrong with the phone !
Click to expand...
Click to collapse
Yes, I did.
But if something is wrong with my phone, how can I have ICS ROMs with no problem but not JB?
relock it and run ruu, get update to stock jb and flash the other rom. enjoy
Sent from my HTC One X with ARHD 19.2/XM-Kernel 273/Lyapota ModPack 5.3 with resManager 2.4 using xda premium
pisc3s1203 said:
relock it and run ruu, get update to stock jb and flash the other rom. enjoy
Sent from my HTC One X with ARHD 19.2/XM-Kernel 273/Lyapota ModPack 5.3 with resManager 2.4 using xda premium
Click to expand...
Click to collapse
What are you talking about it IS the jellybean ruu !
And if you would have read the thread you could see he already updated the hboot to be able to run JB roms, and he also did.....he has trouble starting the roms. But ICS roms work fine !
pisc3s1203 said:
relock it and run ruu, get update to stock jb and flash the other rom. enjoy
Sent from my HTC One X with ARHD 19.2/XM-Kernel 273/Lyapota ModPack 5.3 with resManager 2.4 using xda premium
Click to expand...
Click to collapse
Tried that, no go... still freezes.
Vander....
Could please write down ALL the exact steps you take with installing the new rom ?
From boot.img , recovery actions .... all used commands ... Etc etc etc
a few months ago I installed JB RUU and actualy managed to update it via software update.
That just reminded me that I was able to keep stock rom active without freezing when it was on charger. how weird is that?
anyway, this is how I did the software update. but as soon as I jacked the charger out, it froze again.
i don't know what else I can do, except stay with my current ROM. but I'm not happy with that.
any constructive suggestion or ideas would be great. thanks
Mr Hofs said:
Vander....
Could please write down ALL the exact steps you take with installing the new rom ?
From boot.img , recovery actions .... all used commands ... Etc etc etc
Click to expand...
Click to collapse
1.downloaded RUU from your link
2. fastboot mode -> cmd -> command: fastboot oem lock ->phone relocked
3. run RUU as administrator, followed steps as instructed on the installer
4. after a few minutes phone rebooted and loaded stock rom, took me to setup
5. went through setup process, then check software version, browsed through the phone a little and freeze
Sorry ..... I ment when you install a custom rom !
But now it goes well when you keep it on the charger but it goes wrong when you unplug it ?
Mr Hofs said:
Sorry ..... I ment when you install a custom rom !
But now it goes well when you keep it on the charger but it goes wrong when you unplug it ?
Click to expand...
Click to collapse
yes. but that happened only with stock rom. i tried that with ViperX JB and it didn't work.
did you ever hear of such case?
Yesterday i tried Viper X 3.4.0:
1. downloaded ROM and boot.img from http://forum.xda-developers.com/showthread.php?t=2087443
2. put ROM to SD card
3. reboot to fastboot usb mode
4. open CMD in fastboot folder - > entered: fastboot flash boot boot.img -> OKAY
5. unpluged USB from phone, went to recovery in fastboot mode
6. CWM recovery -> wipe data/factory reset -> wipe cache partition -> wipe dalvik cache
7. install zip from SD card, browsed to ViperX 3.4.0 and selected it
8. went through setup process, chosen wipe data in installation (just in case)
9. finished installation
10. HOX loaded ROM successfully, started setup, after few moments FREEZE
Oke try this :
Flash the viper x 3.4.0 boot.img
Fastboot erase cache
Fastboot flash boot boot.img
Fastboot erase cache
Unplug the cable and enter the recovery.....
Factory reset
Wipe cache partition
Advanced - wipe dalvik cache
Mounts & storage - format cache, data, system
Then install the viper x 3.4.0, choose a full wipe in the aroma installer and choose kernel - viper delivered.....
Reboot after install
Mr Hofs said:
Oke try this :
Flash the viper x 3.4.0 boot.img
Fastboot erase cache
Fastboot flash boot boot.img
Fastboot erase cache
Unplug the cable and enter the recovery.....
Factory reset
Wipe cache partition
Advanced - wipe dalvik cache
Mounts & storage - format cache, data, system
Then install the viper x 3.4.0, choose a full wipe in the aroma installer and choose kernel - viper delivered.....
Reboot after install
Click to expand...
Click to collapse
Tried exactly as instructed, no luck. Same problem.
[I have rooted my desire hd using this mobiadas guide:
and got it confirmed that my phone is rooted... But what next?
I downloaded the JellyTime 4.2 R11 zipfile and put it on the root of my sd-card
tried flashing with clockwork...etc
all i got is a red triangel, an when i press vol-up i got the message E:Cant open /cache/recovery/command
with the 4 option
reboot system
Apply update from sdcard
wipe data/factory reset
wipe cache partition
(Android system recovery <3e>)
Can someone please help a noob
Kenny
kennywild said:
[I have rooted my desire hd using this mobiadas guide:
and got it confirmed that my phone is rooted... But what next?
I downloaded the JellyTime 4.2 R11 zipfile and put it on the root of my sd-card
tried flashing with clockwork...etc
all i got is a red triangel, an when i press vol-up i got the message E:Cant open /cache/recovery/command
with the 4 option
reboot system
Apply update from sdcard
wipe data/factory reset
wipe cache partition
(Android system recovery <3e>)
Can someone please help a noob
Kenny
Click to expand...
Click to collapse
what status of your phone bootloader...?
maybe you can try flashing another custom recovery like 4EXT or TWRP
download recovery.img 4EXT or TWRP
place recovery.img file in sdk/ adb folder on your computer
and flashing through FASTBOOT .. with command "fastboot flash recovery recovery.img"
already have 4EXT or TWRP..then you can try wipe/ factory reset before installing rom again...
don't forget to flashing manually boot.img too after installing any custom rom if your bootloader status unlocked but still S-ON..
what du you mean status of your phone bootloader? I have unlocked bootloadern via HTCdev. Thats what you mean?
Havent still figured out if its S-ON. Dont not yet know what Son/off means. Will google it
kennywild said:
what du you mean status of your phone bootloader? I have unlocked bootloadern via HTCdev. Thats what you mean?
Havent still figured out if its S-ON. Dont not yet know what Son/off means. Will google it
Click to expand...
Click to collapse
yap..that's what i mean...
you can see the status of your bootloader when you're turn on your phone with hold volume down + power button then the phone will show up bootloader like locked or unlocked, s-on or s-off, hboot version, radio version, fastboot, recovery etc..
because of your phone unlocked via htcdev unlock..it seems the bootloader is still s-on..
so like what say before about your problem is...maybe you can try flashing another custom recovery like 4EXT recovery tuch or TWRP..choice one
after you have installing new recovery..then you can installing any custom rom but don't forget that you must always flashing manually boot.img too after every installing any custom rom before reboot the rom for the first time...
hopefully this can help..
jizzz... it dosnt seem like i ever gonna get this to work. I did flash the custom recovery 4ext and the cmd-line on the pc did say flash sucsess... But when i tried recovery i just got an white screen with htc-logo. Had to pull out the batteri to boot the mobile up again..
Edit: I got the TWPR working
Now i got installed the custom rom and everething is workin flawlessly (only memory shows 592, shouldnt it be 768?). THX alot for your help
Kenny
kennywild said:
Now i got installed the custom rom and everething is workin flawlessly (only memory shows 592, shouldnt it be 768?). THX alot for your help
Kenny
Click to expand...
Click to collapse
Google a little bit. Part of ram that you don't see is used by android for a kernel to work.
*FIXED*
The problem turned out to be the wrong TWRP version for verizon phones, the correct version is here http://crackflasher.com/openrecovery-twrp-2-7-0-1-m7wlv-img-htc-one-verizon-openrecovery/
Hello, I will not pretend to be an expert in this area but I feel I have most of my bases covered in this case and would appreciate some help.
First, the phone,
Unlocked
M7_WLV PVT SHIP S-OFF RH
CID-11111111
HBOOT-1.56.0000
RADIO-1.13.41.0109_2
OS-3.11.605.1
The Problem:
Whenever I flash the rom via TWRP everything seems to work fine and the install claims it is successful however this is clearly not the case as when i try to boot the phone it bootloops getting only as far as the HTC screen (with the red development only text underneath)
Next, Pre-reqs:
Phone obviously is unlocked S-off and supercid
TWRP 2.7.0.0 is flashed to the phone (when i try 2.6.3.3 the phone only boot loops even recovery loops)
SuperSU installed
Weaksauce installed
Usb-debugging enabled
all htc drivers installed on Pc
adb installed on pc + working
fastboot installed on pc +working
Steps Taken:
I have tried both pushing the Rom.zip and copying the rom.zip to the sdcard on the phone, this has made no difference
I do the factory reset (wipe) before installing
I do the factory reset (wipe) after installing
I have unchecked all the options and made the most basic install I can
I have tried to flash the TWRP version that came on the ROM, this also causes recovery bootloop
I have tried downloading the rom directly to the phone
I have made sure the MD5 codes match
I have tried flashing the boot.img separately via fastboot
My most recent attempts Aroma Log is attached
Any help would be greatly appreciated!!!!!
PblicEnemy said:
Hello, I will not pretend to be an expert in this area but I feel I have most of my bases covered in this case and would appreciate some help.
First, the phone,
Unlocked
M7_WLV PVT SHIP S-OFF RH
CID-11111111
HBOOT-1.56.0000
RADIO-1.13.41.0109_2
OS-3.11.605.1
The Problem:
Whenever I flash the rom via TWRP everything seems to work fine and the install claims it is successful however this is clearly not the case as when i try to boot the phone it bootloops getting only as far as the HTC screen (with the red development only text underneath)
Next, Pre-reqs:
Phone obviously is unlocked S-off and supercid
TWRP 2.7.0.0 is flashed to the phone (when i try 2.6.3.3 the phone only boot loops even recovery loops)
SuperSU installed
Weaksauce installed
Usb-debugging enabled
all htc drivers installed on Pc
adb installed on pc + working
fastboot installed on pc +working
Steps Taken:
I have tried both pushing the Rom.zip and copying the rom.zip to the sdcard on the phone, this has made no difference
I do the factory reset (wipe) before installing
I do the factory reset (wipe) after installing
I have unchecked all the options and made the most basic install I can
I have tried to flash the TWRP version that came on the ROM, this also causes recovery bootloop
I have tried downloading the rom directly to the phone
I have made sure the MD5 codes match
I have tried flashing the boot.img separately via fastboot
My most recent attempts Aroma Log is attached
Any help would be greatly appreciated!!!!!
Click to expand...
Click to collapse
I noticed you said you do the factory reset after you flash Viper? You'll only want to wipe before you flash the rom. I'm guessing that's you're issue if I understood correctly.
Sent from my HTC6500LVW using Tapatalk
brholt6 said:
I noticed you said you do the factory reset after you flash Viper? You'll only want to wipe before you flash the rom. I'm guessing that's you're issue if I understood correctly.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
I see now I might not have been as clear as I meant to be. When I said that i wiped before and after I meant that I performed both wipes seprately from each other and a third time together. I only tried the wipe after flash because it was a suggestion from another developer website. It would seem that this is not the solution, as the bootloop happens regardles of wipe before, wipe after, or wipe before and after or even no wipe at all. Thanks for the reply!
Try this. Download this recovery http://www.androidfilehost.com/?fid=23329332407584851.
Use fastboot to flash the recovery.
Code:
fastboot erase cache
Code:
fastboot erase recovery
Code:
fastboot flash recovery nameofrecovery.img
Code:
fastboot reboot-bootloader
Go to recovery.
In recovery go to wipe - advanced - check boot, system, data, and cache. Proceed with the wipe.
Flash your rom
Boot up.
cmlusco said:
Try this
Use fastboot to flash the recovery.
Code:
fastboot erase cache
Code:
fastboot erase recovery
Code:
fastboot flash recovery nameofrecovery.img
Code:
fastboot reboot-bootloader
Go to recovery.
In recovery go to wipe - advanced - check boot, system, data, and cache. Proceed with the wipe.
Flash your rom
Boot up.
Click to expand...
Click to collapse
Everything went very well except 2 things. 1: when issuing the "fastboot erase recovery" command in fastboot it failed and came back as "not allowed". 2: the rom installation failed and came back as , error: 7. I tried to boot to system regardless of the error message but the boot loop continues
The new error log is attached again. Thanks for the reply! (and the TWRP update!)
Seems to be an issue with the rom. The log shows everything going fine until the very last step where it tries to change the permissions of an apk and fails, therfore aborting the whole install.
Code:
Setting permissions
ApplyParsedPerms: removexattr of /system/app/BasicDreams.apk to 0 failed: Operation not supported on transport endpoint
script aborted: set_metadata_recursive: some changes failed
I would post that in the roms thread.
cmlusco said:
Seems to be an issue with the rom. The log shows everything going fine until the very last step where it tries to change the permissions of an apk and fails, therfore aborting the whole install.
Code:
Setting permissions
ApplyParsedPerms: removexattr of /system/app/BasicDreams.apk to 0 failed: Operation not supported on transport endpoint
script aborted: set_metadata_recursive: some changes failed
I would post that in the roms thread.
Click to expand...
Click to collapse
I would love to but unfortunately I am not allowed to post there until I have 10 posts and have been cleared by a mod. Do you think it could have anything to do with the temproot i installed (weaksauce) because it works by installing a root every time the phone boots up, or would that be deleted when the wipe is performed?
When you wiped before the rom install it should wipe out everything including weaksauce. The reason it wont boot is because you have no or an incomplete rom. I would just flash another rom in the mean time till you can figure out whats up with viper. Or you could do an ruu if you wanted to be stock.
cmlusco said:
When you wiped before the rom install it should wipe out everything including weaksauce. The reason it wont boot is because you have no or an incomplete rom. I would just flash another rom in the mean time till you can figure out whats up with viper. Or you could do an ruu if you wanted to be stock.
Click to expand...
Click to collapse
I really want viper because of the customization, do you know of any other sources that I could acquire viper from? or would it be possible to install an older version and update it?
*UPDATE* I tried to install Android Revolution HD just now to see if it would work and I end up with the exact same error, seems like a phone problem to me. is there anyway to put my phone completely back to the way i got it out of the box and start over?
Yes you can do an ruu to get back to stock. But you need fastboot to do it. You probably dont have the correct drivers installed on your pc. What version of windows you runing?
cmlusco said:
Yes you can do an ruu to get back to stock. But you need fastboot to do it. You probably dont have the correct drivers installed on your pc. What version of windows you runing?
Click to expand...
Click to collapse
Windows 7 64bit. I use fastboot all the time with this phone so I should be able to use it.
Nevermind, i was thinking this was a different thread. Anyways you will need to change your cid back to vzw__001. Then download the ruu from the second post of santods stock rom thread in development section.
fastboot oem rebootRUU
fastboot flash zip ruufilename.zip
(may fail with flush error, do command again)
fastboot reboot
PblicEnemy said:
I really want viper because of the customization, do you know of any other sources that I could acquire viper from? or would it be possible to install an older version and update it?
*UPDATE* I tried to install Android Revolution HD just now to see if it would work and I end up with the exact same error, seems like a phone problem to me. is there anyway to put my phone completely back to the way i got it out of the box and start over?
Click to expand...
Click to collapse
The big problem with Android Revolution is that it isn't made for the Verizon HTC One. Make sure you you're only flashing roms from the Verizon HTC One thread or you've talked to the Dev. Flashing roms meant for other carriers can really screw you up.
Sent from my HTC6500LVW using Tapatalk
Thanks to both of you, good information and helpful, I'm still hoping I can figure out the set_metadata_recursive error, I have another thread going specifically for it!