Develop Bugs

[Q] About to install ARHD. Please check my process....

Hi all,
I'm looking at flashing ARHD. I've read through the instructions at least 20 times but I'm unsure of just a few things and want to be 100% before trying this as there are a heaps of people who seem to have bricked by not following instructions properly.
As I understand, the process is as follows.......
1. Download super wipe zip and place it on SD card.
2. Download rom and place on SD card.
3. Download firmware package and un-rar.
4. Download 'Official Clockworkmod Touch Recovery 5.8.3.1'
5. Disable antivirus protection on PC.
6. Ensure ADB drivers are installed correctly on PC.
7. Unlock Bootloader via HTC-dev
8. Boot phone in to bootloader and enter Fastboot Mode
9. Install "recovery-clockwork-touch-5.8.3.1-endeavoru.img" via fastboot
command in ADB console.
10. Boot in to the newly installed recovery and perform a nandroid backup.
11. Reboot phone into bootloader and enter Fastboot mode.
12. Run "install-boot-windows.bat' as administrator to install the new firmware
13. Reboot and enter recovery mode.
14. Using the newly installed recovery, flash the
"Android_Revolution_HD_Super_Wipe_One_X.zip" on the SD card.
15. While still in recovery, flash the Android Revolutipn ROM zip.
16. Reboot and enjoy.
Have I missed anything there and is this in the correct order?
At what point does the PJ46IMG.zip need to be installed? The instructions for this are unclear.
Also, in the event something goes wrong and the phone doesn't boot (but i can get into recovery mode), can I just flash the backup file? Or does the fact that I've overwritten the boot.img via Fastboot mean that I can't restore the backup without flashing a stock boot.img via fastboot first?
Thanks and sorry to be a n00b. I'm just finding the order a little mismatched moving between various threads and want to be 100% sure.
Cheers.

You'll be fine. Both Firmware 1.26 and 1.28 is OK with arhd.
On going back to your nandroided stock rom, flash your stock boot.img then restore stock nandroid.
Sent either from my Arc or One X using xda premium

Remember to flash boot.img before the rom
I got my One X yesterday, did all you did BUT, after step 11. nandroid backup, I did these: Nandroid -> Super wipe -> Flash boot.img -> Flash ARHD 3.1.0 and everything works fine

Nubzori said:
Remember to flash boot.img before the rom
I got my One X yesterday, did all you did BUT, after step 11. nandroid backup, I did these: Nandroid -> Super wipe -> Flash boot.img -> Flash ARHD 3.1.0 and everything works fine
Click to expand...
Click to collapse
Did you flash the PJ46IMG.zip firmware file?

Rycon33 said:
You'll be fine. Both Firmware 1.26 and 1.28 is OK with arhd.
Click to expand...
Click to collapse
Does that mean I don't need to flash PJ46IMG.zip?

Sentinel196 said:
Does that mean I don't need to flash PJ46IMG.zip?
Click to expand...
Click to collapse
No need for firmware files

HTC One X and maXimus V2.2 - stuck in Boot Loop

Hi guys, first time poster here, hope i've got the right sub-forum.
So i've ran into some issues whilst attempting to flash the maXimus v2.2 custom rom to my HOX. Here's what i've done so far:
Unlocked bootloader via HTCdev
Installed Clockwork Mod + SuperSU
Created a Backup using Nandorid, as well as a Titanium apps backup.
I then attempted to flash to maXimus v2.2 by doing the following:
Copy ROM zip file onto HOX
Boot into Clockwork Mod Recovery
wipe data factory reset
wipe dalvik cash
Install zip from SD card
All seemed to go okay, but i'm now stuck in a boot loop. I think the problem is that I didn't copy boot.img to my phone before the flashing process, as I was over-reliant on the tut I was using and it didn't mention this.
to rectify the situation, i've tried rebooting into bootloader and sending the fastboot erase cache and fastboot reboot-bootloader commands, but still stuck in the bootloop.
My question is two part - firstly, how do I escape this situation? Secondly, when I go to reflash my HOX, where do I get the boot.img file from?
Thanks in advance, i've tried to be as detailed as possible but this is my first time flashing a custom ROM so if I missed anything out please let me know!

loz_the_guru said:
Hi guys, first time poster here, hope i've got the right sub-forum.
So i've ran into some issues whilst attempting to flash the maXimus v2.2 custom rom to my HOX. Here's what i've done so far:
Unlocked bootloader via HTCdev
Installed Clockwork Mod + SuperSU
Created a Backup using Nandorid, as well as a Titanium apps backup.
I then attempted to flash to maXimus v2.2 by doing the following:
Copy ROM zip file onto HOX
Boot into Clockwork Mod Recovery
wipe data factory reset
wipe dalvik cash
Install zip from SD card
All seemed to go okay, but i'm now stuck in a boot loop. I think the problem is that I didn't copy boot.img to my phone before the flashing process, as I was over-reliant on the tut I was using and it didn't mention this.
to rectify the situation, i've tried rebooting into bootloader and sending the fastboot erase cache and fastboot reboot-bootloader commands, but still stuck in the bootloop.
My question is two part - firstly, how do I escape this situation? Secondly, when I go to reflash my HOX, where do I get the boot.img file from?
Thanks in advance, i've tried to be as detailed as possible but this is my first time flashing a custom ROM so if I missed anything out please let me know!
Click to expand...
Click to collapse
Enter to HBOOT in the Bootloader
Unzip the Android_Fastboot KIT V2.2.zip and run the Install Boot.img.bat after you get OK, Reboot your HOX and it will not be in bootloop

Hero! All sorted now, many thanks!
Quick question - do I have to run install boot.img.bat every time I flash, or is my phone now good to just go via install Zip from SD card each time?

flash everytime until we are s-off

Phone keeps rebooting randomly, not charging

Help me please.
I was previously on ARHD ICS and i decided to try CM10. I did a wipe and flashed paranoid cm10 in CWM, then flashed the boot.IMG and then cleared cache etc.
However, the phone starts up, boots in to cm10...but doesn't charge anymore. It also reboots randomly when i use it and it get s stuck in a loop for a while and then it boots into cm10 fine again.
I've tried loads of different rome and its doing the same thing. PLEASE help.
Hboot is 1.12

Desperate here anyone,?
Sent from my GT-S5830 using xda app-developers app

Did you do a full wipe before flashing (/system, /data and /cache)?

Yep. Numerous times. I have no idea what it's doing. It will boot into the android system, I'll use it for 5 minutes or so without issue, then all of a sudden the 'shutting down' dialog appears with Android System in written at the top in the background..This is on all the roms i tried.

Very Easy To Fix This Problem
First You Must Unlock Your HOX ....
Flash Stock Recovery .... Then Do Factory Rest From BootLoader .
Now Extract "boot.img" From The Rom You Want To Flash ( use winrar/7-Zip )
Flash "boot.img" You Extracted From Fastboot By THis Command
Fastboot Flash Boot.img
Fastboot erase cache
Now Flash ClockModRecovery And Open It
Mount Use Storage From Recovery then Copy Your rom.zip To HOX .
Do Full Wipe From Recovery
And Now Install The Rom From The Recovery ........ and restart your phone
if your HOX stuck on first boot just reboot the phone and wait ...
sorry for bad english ...

I've already flashed the boot.img. This isn't the first time i've flashed a rom

Ok ..... do you try factory rest ?
Your Must Do Factory Rest And The Stock Recovery Only Can Do That
Flash The Stock Recovery ( Download From Attachments "StockRecovery.Zip" )
Fastboot Flash Recovery rstock.img
Then Back To HBOOT Menu And Do "FACTORY REST"
Now Flash "Boot.Img" For Your Custom Room " Must Flash Boot.Img First Then Flash The rom As I Know "
And The Other You Know
The Trick Here Is Format Your SdCard Completely By "Factory Rest"

ahmedaljaf said:
Ok ..... do you try factory rest ?
Your Must Do Factory Rest And The Stock Recovery Only Can Do That
Flash The Stock Recovery ( Download From Attachments "StockRecovery.Zip" )
Fastboot Flash Recovery rstock.img
Then Back To HBOOT Menu And Do "FACTORY REST"
Now Flash "Boot.Img" For Your Custom Room " Must Flash Boot.Img First Then Flash The rom As I Know "
And The Other You Know
The Trick Here Is Format Your SdCard Completely By "Factory Rest"
Click to expand...
Click to collapse
Ok guys - the phone charges but i still have the same issue of 'Shutting down' after 10 mins use.
I have flashed stock recovery, relocked bootloader and installed the RUU back to stock.
Same issue!!
Help

Out of ideas now. Could this be a hardware fault?

installing custom rom

i have rooted my htc one x
every time when i tries to install any custom rom into it and when i boot first time one error continuously shows "unfortunately com.android.phone stopped" i have also tried to reboot it again but the same problem remains
i have tried cm 10.1 RC5 and jellybam stable and many more roms , but the same problem remains always ..
help me plz

Are you sure you flashed the boot image and wiped everything properly (as described in most ROM's threads)?
Sent from my HTC One X using xda premium

that problem will mostly occur if you are installling a rom in unclean way..
make sure you do superwipe and before flashing rom flash its boot.img and do- "fastboot erase cache" afterwards
then flash it from recovery

TimeWasterNL said:
Are you sure you flashed the boot image and wiped everything properly (as described in most ROM's threads)?
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
i have followed this link for unlocking boot loader
"http://forum.xda-developers.com/forumdisplay.php?f=1533#root"
and then for rooting i have followed this steps
"http://www.youtube.com/watch?v=80lMHUgxwww"
and for installing custom rom i have follwed this steps
"http://www.youtube.com/watch?v=gxJf8xIVVC0"
plz help me

aseferfan said:
that problem will mostly occur if you are installling a rom in unclean way..
make sure you do superwipe and before flashing rom flash its boot.img and do- "fastboot erase cache" afterwards
then flash it from recovery
Click to expand...
Click to collapse
i am new in ROOT world
so plz tell me how to do it , whatever u have suggested me in your previous reply is not clearly understood by me , so plz make it clear

shivamtarzan said:
i have followed this link for unlocking boot loader
"http://forum.xda-developers.com/forumdisplay.php?f=1533#root"
and then for rooting i have followed this steps
"http://www.youtube.com/watch?v=80lMHUgxwww"
and for installing custom rom i have follwed this steps
"http://www.youtube.com/watch?v=gxJf8xIVVC0"
plz help me
Click to expand...
Click to collapse
most of the people here know the procedures. give us information that will help you solve the problem. like is your phone already rooted. the steps you do when flashing. like what did you really do before that error appears. something like that.

robchongke said:
most of the people here know the procedures. give us information that will help you solve the problem. like is your phone already rooted. the steps you do when flashing. like what did you really do before that error appears. something like that.
Click to expand...
Click to collapse
yes my phone is already rooted . i have also taken the backup of m stock rom . i have tried to install custom rom for 3 to 4 times but every time when i installs custom rom and when i boot it the above problem occurs so i restore my system with the backup , and that original stock rom is working fine
for flashing i have followed this :
1) unlocked bootloader
2) rooted it
3) installed clockwork recovery mode
4) now transfer the custom rom into the internal memory
5) reboot phone into bootloader mode
6) select "recovery"
7) wipe data/factory reset
8) wipe cache partitions
9) wipe dalvik cache
10) install zip from sd card-->choose zip from sd card-->select the rom
11) select yes
12) after installing the rom reboot the phone
and when the phone will rebooted the problem occures when the ui of new rom appears

shivamtarzan said:
yes my phone is already rooted . i have also taken the backup of m stock rom . i have tried to install custom rom for 3 to 4 times but every time when i installs custom rom and when i boot it the above problem occurs so i restore my system with the backup , and that original stock rom is working fine
for flashing i have followed this :
1) unlocked bootloader
2) rooted it
3) installed clockwork recovery mode
4) now transfer the custom rom into the internal memory
5) reboot phone into bootloader mode
6) select "recovery"
7) wipe data/factory reset
8) wipe cache partitions
9) wipe dalvik cache
10) install zip from sd card-->choose zip from sd card-->select the rom
11) select yes
12) after installing the rom reboot the phone
and when the phone will rebooted the problem occures when the ui of new rom appears
Click to expand...
Click to collapse
you do not need to root, flash custom recovery and unlock the bootloader everytime.
you did not flash the rom's boot.img. everytime you flash rom or kernel dont forget to flash boot.img. place the rom's boot.img inside your fastboot folder. then do the command:
fastboot erase cache.
fastboot flash boot boot.img.
then reboot.

robchongke said:
you do not need to root, flash custom recovery and unlock the bootloader everytime.
you did not flash the rom's boot.img. everytime you flash rom or kernel dont forget to flash boot.img.
Click to expand...
Click to collapse
yes i know that i do not need to flash custom recovery , root or unlock bootloader every time , i am just telling from initial stage
once i rooted phone , unlocked bootloader and flash recovery then i just install the rom but before that i am wiping all three things which i mentioned before this reply
and how to flash boot.img whenever i flash rom ?

shivamtarzan said:
yes i know that i do not need to flash custom recovery , root or unlock bootloader every time , i am just telling from initial stage
once i rooted phone , unlocked bootloader and flash recovery then i just install the rom but before that i am wiping all three things which i mentioned before this reply
and how to flash boot.img whenever i flash rom ?
Click to expand...
Click to collapse
yeah. you still have to that. extract the boot.img from the rom. place the boot.img inside your fastboot folder. boot your phone into bootloader. it you see fastboot usb you can now flash the boot.img.
open command prompt. navigate to your fastboot folder or you can just right click on the fastboot folder and select "enter comman prompt here" something like that. then enter this commands.
fastboot erase cache
fastboot flash boot boot.img
that's two different command.

robchongke said:
yeah. you still have to that. extract the boot.img from the rom. place the boot.img inside your fastboot folder. boot your phone into bootloader. it you see fastboot usb you can now flash the boot.img.
open command prompt. navigate to your fastboot folder or you can just right click on the fastboot folder and select "enter comman prompt here" something like that. then enter this commands.
fastboot erase cache
fastboot flash boot boot.img
that's two different command.
Click to expand...
Click to collapse
these things that you have said me should done before installing custom rom of after ?

shivamtarzan said:
these things that you have said me should done before installing custom rom of after ?
Click to expand...
Click to collapse
it does'nt matter it you flash boot.img before of after. but me i always flash boot.img first. because if you flash the rom first. you'll boot your phone to recovery then after you flash rom you'll boot to bootloader, where you will press power button + vol down. while if you flash boot.img first. after that just go to hboot then select recovery then flash rom. well that's just me. hehe.

robchongke said:
it does'nt matter it you flash boot.img before of after. but me i always flash boot.img first. because if you flash the rom first. you'll boot your phone to recovery then after you flash rom you'll boot to bootloader, where you will press power button + vol down. while if you flash boot.img first. after that just go to hboot then select recovery then flash rom. well that's just me. hehe.
Click to expand...
Click to collapse
flash rom means "installing any new custom rom from recovery-->install zip from sd card-->choose zip from sd card-->selecting the zip" am i right here??

shivamtarzan said:
flash rom means "installing any new custom rom from recovery-->install zip from sd card-->choose zip from sd card-->selecting the zip" am i right here??
Click to expand...
Click to collapse
yep. don't forget to wipe cache and wipe dalvik. if you are flashing a different rom.always do a full wipe.

robchongke said:
yep. don't forget to wipe cache and wipe dalvik. if you are flashing a different rom.always do a full wipe.
Click to expand...
Click to collapse
ok got it
now i am going to do this in this manner :
1) flash new custom rom's boot.img as u said
2) wipe all cache & dalvik cache
3) flash new custom rom
am i going on a right path??

shivamtarzan said:
ok got it
now i am going to do this in this manner :
1) flash new custom rom's boot.img as u said
2) wipe all cache & dalvik cache
3) flash new custom rom
am i going on a right path??
Click to expand...
Click to collapse
Don't forget to erase fastboot cache after flashing boot.img...
Also in recovery, you need to wipe data as well if your coming from a different rom...
-Sent from my IceCold One X!

shivamtarzan said:
ok got it
now i am going to do this in this manner :
1) flash new custom rom's boot.img as u said
2) wipe all cache & dalvik cache
3) flash new custom rom
am i going on a right path??
Click to expand...
Click to collapse
yep. and as i said before. if you are flashing different rom. dont forget to full wipe.

vin4yak said:
Don't forget to erase fastboot cache after flashing boot.img...
Also in recovery, you need to wipe data as well if your coming from a different rom...
-Sent from my IceCold One X!
Click to expand...
Click to collapse
how to erase fastboot cache ?

shivamtarzan said:
how to erase fastboot cache ?
Click to expand...
Click to collapse
there are only 2 commands when flashing boot.img via cmd:
fastboot erase cache
fastboot flash boot boot.img
so dont forget that.

shivamtarzan said:
how to erase fastboot cache ?
Click to expand...
Click to collapse
fastboot erase cache
robchongke said:
there are only 2 commands when flashing boot.img via cmd:
fastboot erase cache
fastboot flash boot boot.img
so dont forget that.
Click to expand...
Click to collapse
He needs to erase the cache after flashing the boot.img and not before!

M8s stuck in bootloader

Hello everyone. I got a M8s from a friend wich is stuck in bootloader. The recovery didn't work at the begin, so I flashed twrp-recovery-2.8.6.0-m8s-qlul.img (flashing recovery using htc_fastboot.exe flash recovery theimagename.img) and it worked, then I tried to install a custom ROM Android_Pandora_Rom_1.2_(Discontinued).zip wich went all the steps fine until: Optimizing applications 8 of 204..then phone shat down to black screen. I booted back to bootloader, recovery, wiped and go for a new install, same issue.
After that, I was going to install lineage-13.0-20170715-UNOFFICIAL-m8qlul.zip where the developer of this rom recommends twrp-3.0.2-0-m8ql.img so I tried to flash it (flashing recovery using htc_fastboot.exe flash recovery theimagename.img), then tried to acces recovery, brings me back to bootloader so fast, rebooted bootloader, tried again, same problem. Tried the fasboot erase cache, no help.
The Hboot state is Unlocked and the S is ON. I tried some other recovery images, as stock_signed or 3.0.1, tried the one from M8 ToolKit but all failed and I still can't access recovery, everyting I do, it brings me back to bootloader. I did htc_fastboot boot recoveryfile.img wich works, but useless, the dd if= method to set the recovery permanent load did not work after reboot, /data and /system can't be mountet, it seems the "boot recovery" option is 99% readonly.
Any advice, any help please? It would be much appreciated! Thanks in advance!

Hi McBad,
you could try the following. I also had some problems to access the recovery.
- Again bring the phone into fastboot, flash the 2.8 recovery and access it
- Do a wipe for factory reset, not just only cache
- after that try to flash the twrp-3.0.1-0-m8ql.img version, the other one worked for me neither
- the try to install the custom ROM LOS13
I hope this will help you.
clone

It would be great if that would work, but flashing a recovery does not work. I flash it, success message, try to access it, vibrates and bootloader pops back instantly. That is the problem.

Sorry for double post, but can anyone help me with this? This is the second day I struggle to make it work. Any chance to make the hboot locked again? It didn't work with oem lock command. I would like to lock it so I can put an official zip on sdcard so the hboot to restore it to factory stock, some RUU. Or get it s-off so I can flash a rom from fastboot? The phone does not have any ROM on it, image crc results system 0x0, recovery 0x0. Please, help!

Have you tried sideloading twrp ?

McBad said:
Sorry for double post, but can anyone help me with this? This is the second day I struggle to make it work. Any chance to make the hboot locked again? It didn't work with oem lock command. I would like to lock it so I can put an official zip on sdcard so the hboot to restore it to factory stock, some RUU. Or get it s-off so I can flash a rom from fastboot? The phone does not have any ROM on it, image crc results system 0x0, recovery 0x0. Please, help!
Click to expand...
Click to collapse
Did you use HTC fastboot ?

Yes, I used htc_fastboot. Use sideloading? Like boot the img file directly? Tried that too.

McBad said:
Yes, I used htc_fastboot. Use sideloading? Like boot the img file directly? Tried that too.
Click to expand...
Click to collapse
Is there any way you could flash twrp 2.8 again? Once in that recovery you have sideloading option which you could use to transfer latest recovery onto your device. Are we talking about the same process?

McBad said:
Yes, I used htc_fastboot. Use sideloading? Like boot the img file directly? Tried that too.
Click to expand...
Click to collapse
Sideload as follows ....

McBad said:
Hello everyone. I got a M8s from a friend wich is stuck in bootloader. The recovery didn't work at the begin, so I flashed twrp-recovery-2.8.6.0-m8s-qlul.img (flashing recovery using htc_fastboot.exe flash recovery theimagename.img) and it worked, then I tried to install a custom ROM Android_Pandora_Rom_1.2_(Discontinued).zip wich went all the steps fine until: Optimizing applications 8 of 204..then phone shat down to black screen. I booted back to bootloader, recovery, wiped and go for a new install, same issue.
After that, I was going to install lineage-13.0-20170715-UNOFFICIAL-m8qlul.zip where the developer of this rom recommends twrp-3.0.2-0-m8ql.img so I tried to flash it (flashing recovery using htc_fastboot.exe flash recovery theimagename.img), then tried to acces recovery, brings me back to bootloader so fast, rebooted bootloader, tried again, same problem. Tried the fasboot erase cache, no help.
The Hboot state is Unlocked and the S is ON. I tried some other recovery images, as stock_signed or 3.0.1, tried the one from M8 ToolKit but all failed and I still can't access recovery, everyting I do, it brings me back to bootloader. I did htc_fastboot boot recoveryfile.img wich works, but useless, the dd if= method to set the recovery permanent load did not work after reboot, /data and /system can't be mountet, it seems the "boot recovery" option is 99% readonly.
Any advice, any help please? It would be much appreciated! Thanks in advance!
Click to expand...
Click to collapse
You can't install lineage if you haven't upgraded your device with latest official update. I would try reinstaling twrp 2.8, do a wipe of cache, dalvik cache and system, Sideload CM 12; and see how it goes. As well, while in twrp I would try relocking bootloader but only after an unsuccessful attempt to flash said rom. I don't know what your experience with soft bricked devices is, but sometimes it takes a while, different usb cable or usb slot on your PC, correct files in adb folder, re-download of rom or recovery because it easily gets corrupted while downloading. And obviously a fully charged device. Let us know how it goes.