Database Info

[Q] What is the meaning of : recovery,flashing,...

I always read this words when viewing some android related topics..
recovery and recovery versions.. official recovery..official ClockworkMod release..
flash in fasboot..
unlocked bootloaders...
superboot..
.
.
and such a things....what this mean??

Stealthy Hunter said:
I always read this words when viewing some android related topics..
recovery and recovery versions.. official recovery..official ClockworkMod release..
flash in fasboot..
unlocked bootloaders...
superboot..
.
.
and such a things....what this mean??
Click to expand...
Click to collapse
That means that you should read more

muamers said:
That means that you should read more
Click to expand...
Click to collapse
fist thank u..
second I am asking so that i read the answer to know more...asking is the first knowledge..

Stealthy Hunter said:
fist that is not polite of u..
second I am asking so that i read the answer to know more...asking is the first knowledge..
Click to expand...
Click to collapse
Belive me brother, that was the best answer you could get ... i can explain that to you, but then you will just be more confused ... thats why i told you that you have to read more ...

As above I'm sorry, sometimes you've gotta get straight to the point and you've definitely got some reading to do
Sent from my HTC One X using Tapatalk 2

marcadam said:
As above I'm sorry, sometimes you've gotta get straight to the point and you've definitely got some reading to do
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
muamers said:
Belive me brother, that was the best answer you could get ... i can explain that to you, but then you will just be more confused ... thats why i told you that you have to read more ...
Click to expand...
Click to collapse
Any good threads can help....
and sorry for the bad behavior of me...

recovery= a "program" that you instal to make changes, backups, formating, wiping etc. to the android base ... you need this to instal updates for your system or change the ROM, Radio, Kernel, or just make backups and restore backups.
recovery versions= there are 2 kinds of recovery versions:
1. Official HTC - stock recovery that are preinstaled on your phone.
2. Unofficial - there are some versions, but the most popular is the ClockWorkMod recovery (or CWM). You need this recovery for instaling custom ROMs.
flash in fastboot = flashing the recovery, the kernel and some more from the CMD prompt... because or device (HOX) is security enabled (S-ON) and we have to take this harder way to flash custom ROMs and kernels.
unlock bootloader = like the name says, thats unlocking the bootloader (powerbutton + volumedown) over HTCdev to be able to instal some custom stuff (like instaling ROM or Kernels).
All that things are there to unlock our HOX and be able to make customizations to it...
---------- Post added at 01:03 AM ---------- Previous post was at 12:56 AM ----------
Stealthy Hunter said:
Any good threads can help....
and sorry for the bad behavior of me...
Click to expand...
Click to collapse
If you want to unlock your OneX and be able to flash everything you want (ROM,Kernel and Root your OneX) then read THIS.
But first read once and then do changes to your phone ... and ALWAYS be sure you have more then 75% of battery (the best is you have it fully charged to be sure) before you do any change to your phone

muamers said:
recovery= a "program" that you instal to make changes, backups, formating, wiping etc. to the android base ... you need this to instal updates for your system or change the ROM, Radio, Kernel, or just make backups and restore backups.
recovery versions= there are 2 kinds of recovery versions:
1. Official HTC - stock recovery that are preinstaled on your phone.
2. Unofficial - there are some versions, but the most popular is the ClockWorkMod recovery (or CWM). You need this recovery for instaling custom ROMs.
flash in fastboot = flashing the recovery, the kernel and some more from the CMD prompt... because or device (HOX) is security enabled (S-ON) and we have to take this harder way to flash custom ROMs and kernels.
unlock bootloader = like the name says, thats unlocking the bootloader (powerbutton + volumedown) over HTCdev to be able to instal some custom stuff (like instaling ROM or Kernels).
All that things are there to unlock our HOX and be able to make customizations to it...
---------- Post added at 01:03 AM ---------- Previous post was at 12:56 AM ----------
If you want to unlock your OneX and be able to flash everything you want (ROM,Kernel and Root your OneX) then read THIS.
But first read once and then do changes to your phone ... and ALWAYS be sure you have more then 75% of battery (the best is you have it fully charged to be sure) before you do any change to your phone
Click to expand...
Click to collapse
because HOX is new some ppl told me that it's dangerous to do this things...
because of the few infos about it>>>as they said..
.
if sth goes wrong we should have safety rope to go back..
.
.
what is ur opinion??

Stealthy Hunter said:
because HOX is new some ppl told me that it's dangerous to do this things...
because of the few infos about it>>>as they said..
.
if sth goes wrong we should have safety rope to go back..
.
.
what is ur opinion??
Click to expand...
Click to collapse
You can read the whole OneX forum and you will not find a single case that someone bricked the OneX ... always can something go wrong, no matter how old the phone is, but we have a great community and almost always there is a way out and there is always someone help you out.
So far the only thing can go wrong is that you get out of battery during the flashing process, but there is also a way out (read THIS)

recovery= a "program" that you instal to make changes, backups, formating, wiping etc. to the android base ... you need this to instal updates for your system or change the ROM, Radio, Kernel, or just make backups and restore backups.
recovery versions= there are 2 kinds of recovery versions:
1. Official HTC - stock recovery that are preinstaled on your phone.
2. Unofficial - there are some versions, but the most popular is the ClockWorkMod recovery (or CWM). You need this recovery for instaling custom ROMs.
Click to expand...
Click to collapse
I couldn't get it clearly...can u provide with article explain that motr

please anyone help FAST !!!

i have been trying to get android jellybean on my nexus s, and i had a custom ics rom, so i flashed the official ics on the nexus, and tried updating to jelly bean from the phone itself, so it finished updating, then it stays stuck on the nexus boot animation for about an hour , so i pulled out the battery and tried entering recovery mode, it just brings up a picture of a android with a red exclamation mark on top of it. and when i do a normal boot it just stays on the boot animation, im new to android hacking, so anyone can tell me what to do plz fast ??????!!!!!

abd3lfatta4 said:
i have been trying to get android jellybean on my nexus s, and i had a custom ics rom, so i flashed the official ics on the nexus, and tried updating to jelly bean from the phone itself, so it finished updating, then it stays stuck on the nexus boot animation for about an hour , so i pulled out the battery and tried entering recovery mode, it just brings up a picture of a android with a red exclamation mark on top of it. and when i do a normal boot it just stays on the boot animation, im new to android hacking, so anyone can tell me what to do plz fast ??????!!!!!
Click to expand...
Click to collapse
U need to flash a custom recovery using fastboot. if u dont know what that is google it up if not I should be able to guide u later (I am busy now)

abd3lfatta4 said:
i have been trying to get android jellybean on my nexus s, and i had a custom ics rom, so i flashed the official ics on the nexus, and tried updating to jelly bean from the phone itself, so it finished updating, then it stays stuck on the nexus boot animation for about an hour , so i pulled out the battery and tried entering recovery mode, it just brings up a picture of a android with a red exclamation mark on top of it. and when i do a normal boot it just stays on the boot animation, im new to android hacking, so anyone can tell me what to do plz fast ??????!!!!!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1785672

RsurNexusS said:
U need to flash a custom recovery using fastboot. if u dont know what that is google it up if not I should be able to guide u later (I am busy now)
Click to expand...
Click to collapse
i dont mean to be annoying or anything, but as i said im new to android hacking, so if you dont mind please guide me through this "fastboot" thing
i tried searching on google but i dont understand anything. thanks in advance .

jayjay3333 said:
http://forum.xda-developers.com/showthread.php?t=1785672
Click to expand...
Click to collapse
nice, but what do u mean on the 4th step ' open command prompt ' when i connect my phone to pc , the phone doesnt show on the pc

abd3lfatta4 said:
nice, but what do u mean on the 4th step ' open command prompt ' when i connect my phone to pc , the phone doesnt show on the pc
Click to expand...
Click to collapse
On pc go to start - run- cmd. Like it says it is assumed you have fastboot working. If you don't know what that means do the rooting guides and get the Android SDK http://forum.xda-developers.com/showthread.php?t=1623481
Sent from my Nexus S using xda premium

jayjay3333 said:
On pc go to start - run- cmd. Like it says it is assumed you have fastboot working. If you don't know what that means do the rooting guides and get the Android SDK http://forum.xda-developers.com/showthread.php?t=1623481
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
I have fastboot installed on my pc but i heard i have to download some kind of drivers so that it can read my phone, do u mind to post the link of these drivers ??

abd3lfatta4 said:
I have fastboot installed on my pc but i heard i have to download some kind of drivers so that it can read my phone, do u mind to post the link of these drivers ??
Click to expand...
Click to collapse
http://wiki.cyanogenmod.com/wiki/Howto:_Install_the_Android_SDK

hi
go find the One Click Root for the nexus s , it comes with all the drivers

UtmostMick0 said:
go find the One Click Root for the nexus s , it comes with all the drivers
Click to expand...
Click to collapse
put a link please for this one click root and tell me what to do with it.

Heyy dude !! well since you said that you used to have a custom ics rom, surely you must already know how to root your phone, flash a custom recovery, and install the custom rom zip?
Because you reverted back to a stock rom, it wiped out ur custom recovery and installed the old stock one, so ur gnna have to flash a custom recovery again and use it to install a custom Jelly Bean rom, and ur good to go .. sorry if this doesnt answer ur question, or tht I have put forward an answer u already knew, let me know what u dnt understand.
---------- Post added at 09:23 PM ---------- Previous post was at 09:07 PM ----------
Oh and just remembered back when I rooted my nexus s, I needed to install a program called PDANet, so tht it could provide my windows 7 with the correct adb drivers, in order for your computer to recognise your phone, when connected by USB and booted up on fastboot mode (make sure phone is fully off first, then hold volume up + power button)
Literally, just follow this guide, google has it all:
okay since im a new user, and not allowed to copy paste website links yet, type in google "root nexus s adb" and click the very top first link
BUT, dnt go beyond the step where it says to install superuser.zip in clockwork mod recovery (so you get to step 3 on part V. Root the Phone), instead just simply mount the phone as storage and transfer the custom rom zip u wanna flash, flash it using clockwork mod and thts all man.
Also, really stupid question, when u turn ur phone on, u see the google logo, and is there an unlocked grey padlock icon at the bottom, or just a fully black background with just the google logo by itself?

DJ180 said:
Heyy dude !! well since you said that you used to have a custom ics rom, surely you must already know how to root your phone, flash a custom recovery, and install the custom rom zip?
Because you reverted back to a stock rom, it wiped out ur custom recovery and installed the old stock one, so ur gnna have to flash a custom recovery again and use it to install a custom Jelly Bean rom, and ur good to go .. sorry if this doesnt answer ur question, or tht I have put forward an answer u already knew, let me know what u dnt understand.
Click to expand...
Click to collapse
what he said.
Install a new recovery, boot to recovery, clean up (wipe and clear cache) Install new JB rom.
If you phone is in fact NOT rooted. type - 1 click root nexus s - into google
Rinse and repeat

Try this
abd3lfatta4 said:
i have been trying to get android jellybean on my nexus s, and i had a custom ics rom, so i flashed the official ics on the nexus, and tried updating to jelly bean from the phone itself, so it finished updating, then it stays stuck on the nexus boot animation for about an hour , so i pulled out the battery and tried entering recovery mode, it just brings up a picture of a android with a red exclamation mark on top of it. and when i do a normal boot it just stays on the boot animation, im new to android hacking, so anyone can tell me what to do plz fast ??????!!!!!
Click to expand...
Click to collapse
I'm pretty sure you can just reflash the CWM Recovery, over the stock so root it, then download the official 4.1.1 and then you should have stock everything. Just type into google code google nexus s 4.1 and it should be the first link. If I am wrong about the flashing part, then can someone please correct me.
Hit The Thanks Button if this helped you.

u guys dont understand. I CANT ENTER RECOVERY MODE, it brings me a picture of a android with a ! mark over it And the phone doesnt boot , its just stuck on the jelly bean boot animation

i've got kinda problem when updating from 4.0.4 to 4.1.1 OTA.
in order to flash succeffuly the OTA package, you must have a stock ICS rom (i was running a custom rom based on IMM76D).
i had to flash a factory image of 4.0.4 from google.
if i don't mistake, there's the 4.1.1 factory image avaible (so you should flash that).
there's a guide here on xda on how to flash a factory image, just look for it.
hope this helps

S1cK94 said:
i've got kinda problem when updating from 4.0.4 to 4.1.1 OTA.
in order to flash succeffuly the OTA package, you must have a stock ICS rom (i was running a custom rom based on IMM76D).
i had to flash a factory image of 4.0.4 from google.
if i don't mistake, there's the 4.1.1 factory image avaible (so you should flash that).
there's a guide here on xda on how to flash a factory image, just look for it.
hope this helps
Click to expand...
Click to collapse
thanks , but i cant find the 4.1.1 factory image here, so if u know where it is plz post a link

DJ180 said:
Heyy dude !! well since you said that you used to have a custom ics rom, surely you must already know how to root your phone, flash a custom recovery, and install the custom rom zip?
Because you reverted back to a stock rom, it wiped out ur custom recovery and installed the old stock one, so ur gnna have to flash a custom recovery again and use it to install a custom Jelly Bean rom, and ur good to go .. sorry if this doesnt answer ur question, or tht I have put forward an answer u already knew, let me know what u dnt understand.
---------- Post added at 09:23 PM ---------- Previous post was at 09:07 PM ----------
Oh and just remembered back when I rooted my nexus s, I needed to install a program called PDANet, so tht it could provide my windows 7 with the correct adb drivers, in order for your computer to recognise your phone, when connected by USB and booted up on fastboot mode (make sure phone is fully off first, then hold volume up + power button)
Literally, just follow this guide, google has it all:
okay since im a new user, and not allowed to copy paste website links yet, type in google "root nexus s adb" and click the very top first link
BUT, dnt go beyond the step where it says to install superuser.zip in clockwork mod recovery (so you get to step 3 on part V. Root the Phone), instead just simply mount the phone as storage and transfer the custom rom zip u wanna flash, flash it using clockwork mod and thts all man.
Also, really stupid question, when u turn ur phone on, u see the google logo, and is there an unlocked grey padlock icon at the bottom, or just a fully black background with just the google logo by itself?
Click to expand...
Click to collapse
yes my boot loader is unlocked.

abd3lfatta4 said:
thanks , but i cant find the 4.1.1 factory image here, so if u know where it is plz post a link
Click to expand...
Click to collapse
alright,
here the images and basically the steps are:
Code:
fastboot flash bootloader bootloader-crespo-i9020xxkl1.img
fastboot reboot-bootloader
fastboot flash radio radio-crespo-i9020xxki1.img
fastboot reboot-bootloader
fastboot -w update image-soju-imm76d.zip
this is an example with the ICS image, check the file names when you do it.
almost forgot: don't get tricked by the "instruction" section of the link, it's only for linux.

abd3lfatta4 said:
u guys dont understand. I CANT ENTER RECOVERY MODE, it brings me a picture of a android with a ! mark over it And the phone doesnt boot , its just stuck on the jelly bean boot animation
Click to expand...
Click to collapse
Try long pressing vol up button and pres power btn shortly when the exclamation nark appears.,then release both
Sent from my Nexus S using xda app-developers app

that doesnt work

[Q] Help About Root & Revolutionary

help me, i have followed the instruction from htcdev.com to unlock my desire s bootloader with HBOOT 2.00.002.. after that i found my bootloader with text UNLOCKED but still it shows S-ON.
And then i continued to try root my desire s, i followed instructions that i found in this forum (thanks ) after finished, i tried to install some apps that need root access but i found that my desire s is not rooted (the apps said that).
The last things that i want to asked is, when i go to fastboot menu, i point to recovery mode and i found my desire with Revolutionary 4.0.1.4. I searched info about that things (revolutionary), i found many people said that if i have success install Revolutionary that means i have successfully rooted my device.
is there anybody could help and explained to me about those problems? i would very appreciate that

Revolutionary 4.0.1.4 is a custom recovery. Installing a custom recovery alone does NOT give you root access.
READ index thread in the forum and you'll have your answers

Thanks Bro ContactFront i will search in index thread
With the condition that i have now, is it possible if i want to return it back to default? I want to try update my desire to ICS using RUU Official uptade that i downloaded from htc website..
Sent from my Anvyn Desire S. Powered by XDA Developers

short answer is yes, you can go back to stock

Don't use the official ics Ruu, it's buggy and unfinished.
My pessimism extends to the point of even suspecting the sincerity of the pessimists.
—Jean Rostand

Alrighty then! Thanks All
But, do i need to root my device if i want to flash a custom rom? or all that i have done is enough to flash a custom rom? as i explained before, this is what i have done to my HTC Desire S :
HTC Desire S ( Gingerbread)
UNLOCKED using HTCDev
S-ON
HBOOT 2.00.0002
Installed Revolutionary 4.0.1.4
Sent from my Anvyn Desire S. Powered by XDA Developers

zidane_argun said:
Alrighty then! Thanks All
But, do i need to root my device if i want to flash a custom rom? or all that i have done is enough to flash a custom rom? as i explained before, this is what i have done to my HTC Desire S :
HTC Desire S ( Gingerbread)
UNLOCKED using HTCDev
S-ON
HBOOT 2.00.0002
Installed Revolutionary 4.0.1.4
Sent from my Anvyn Desire S. Powered by XDA Developers
Click to expand...
Click to collapse
seems like you still have not read the index.... You need root to flash a custom ROM(duh) since I am in a pretty good mood today so....
1.root your device
2 . Download your preferred ROM
3.flash your ROM
4.IMPORTANT!!!find your boot. img extracting it from the rom you downloaded
5.go to fastboot
6. connect your phone to computer
7.open CMD
8.cd to our directory(ensure you have adb and fastboot first)
9.
Code:
fastboot erase boot
10
Code:
fastboot boot boot. img
11.reboot and enjoy
Sent from my supercharged :tank:

1.root your device - not needed if he is going to flash a Custom. They are all rooted anyway. I think step 1 should be: flash a custom recovery
...
10
Code:
fastboot boot boot. img
- this will boot the kernel only, but after a restart of the device it will be gone. The command to use is :
Code:
fastboot flash boot boot.img
11.reboot and enjoy - that is all right

hisname said:
seems like you still have not read the index.... You need root to flash a custom ROM(duh) since I am in a pretty good mood today so....
1.root your device
2 . Download your preferred ROM
3.flash your ROM
4.IMPORTANT!!!find your boot. img extracting it from the rom you downloaded
5.go to fastboot
6. connect your phone to computer
7.open CMD
8.cd to our directory(ensure you have adb and fastboot first)
9.
Code:
fastboot erase boot
10
Code:
fastboot boot boot. img
11.reboot and enjoy
Sent from my supercharged :tank:
Click to expand...
Click to collapse
Thanks before
Now i have read the index, i found many tutorials to root my device there. i followed some.
but i have a problems when i want to root my device, i tried using SuperOneClick apps. I have done every single requirements of that tutorial.
The problem is i think my device is still not rooted. The first time i used SuperOneClick it shows finished & OK, then i reboot my device.
and then i tried to install some apps that needs rooted device, but those apps tell me that my device isn't rooted!
I tried to root my device using SuperOneClick again, but it always stuck in step #7 (Wait for Device).
any solutions for this problems?
Did i missed something to do?

amidabuddha said:
1.root your device - not needed if he is going to flash a Custom. They are all rooted anyway. I think step 1 should be: flash a custom recovery
...
10
Code:
fastboot boot boot. img
- this will boot the kernel only, but after a restart of the device it will be gone. The command to use is :
Code:
fastboot flash boot boot.img
11.reboot and enjoy - that is all right
Click to expand...
Click to collapse
he already has a custom recovery by revolutionary
Sent from my supercharged :tank:
edit: look here
http://forum.xda-developers.com/showthread.php?t=1525100

hisname said:
he already has a custom recovery by revolutionary
Click to expand...
Click to collapse
Well this is pretty outdated.
The attached is the latest 4EXT Recovery, touch edition.
Extract the recovery.img from the zip and flash:
Code:
fastboot flash recovery recovery.img
Then from the bootloader menu reboot to recovery and select backup/restore -> Backup. After the backup is done go back to the main menu, select wipe/format -> Wipe all partitions (except SDcard). When done select Install zip from the main menu and flash the ROM from your sdcard. After that reboot to bootloader from the Power menu and flash the boot.img as described in my previous post

amidabuddha said:
Well this is pretty outdated
Click to expand...
Click to collapse
true, but at least it is still usable till he gets 4ext or something later....
Sent from my supercharged :tank:

@zidane_argun
see my previous post

hisname said:
true, but at least it is still usable till he gets 4ext or something later....
Sent from my supercharged :tank:
Click to expand...
Click to collapse
amidabuddha said:
@zidane_argun
see my previous post
Click to expand...
Click to collapse
okay okay, roger that!
i will try that, thank you bro amidabuddha & hisname :good::good:
brb..

just realised that even my 4ext recovery is also outdated, thanks for the post :thumbup:
Sent from my supercharged :tank:

lol was trying to reply to your pm. don't know if they went through as they don't show up in my "sent item".
anyway you've got plenty of tips from the folks. so happy flashing

ContactFront said:
lol was trying to reply to your pm. don't know if they went through as they don't show up in my "sent item".
anyway you've got plenty of tips from the folks. so happy flashing
Click to expand...
Click to collapse
haha.. thanks to you too bro! now i'm trying to flash EXT4 first since they (the folks ) said that mine is pretty outdated.. LOL
after that, i want to search which rom is the best one for my Desire S.. do you have any idea which one is best ROM that i have to try?
Sent from my Anvyn Desire S. Powered by XDA Developers

zidane_argun said:
haha.. thanks to you too bro! now i'm trying to flash EXT4 first since they (the folks ) said that mine is pretty outdated.. LOL
after that, i want to search which rom is the best one for my Desire S.. do you have any idea which one is best ROM that i have to try?
Sent from my Anvyn Desire S. Powered by XDA Developers
Click to expand...
Click to collapse
there is really no "best" rom. it's all down to your personal preference.
say, I'm a big cm/aosp fan but if you are a sense fanboy then you may not like aosp based rom at all.
so if you see something interesting then just go ahead give it a try and decide for yourself.
---------- Post added at 09:37 AM ---------- Previous post was at 09:30 AM ----------
oh and speaking of 4ext recovery, i'd recommend installing either the free version updater or purchasing the full version from google play.
http://4ext.net/
it's absolutely worth it. one of the best recoverys you can have

[Q] i can't install any firmware on my htc one x

Hi everyone.
i bought a second hand htc one x a month ago and it was working good on jb rom
but the bootloader was already unlocked with s-on
so i thought i could see how the custom rom looks like so i downloaded a lot of Roms and trying to install them but unfortunately none of them worked not just that it's crash and go back to recovery.img witch i also flash a lot until one of them works so after i tried a lot of custom roms like "Android_Revolution_HD-one_x_33" , "HTC_one_x_-_MaximusHD_21.0" , "OTA_ENDEAVOR_U_JB_50_S_HTC_E" , "ViperX_4.0.7".
and i also tried to install the official one which is RUU... doesn't works then in some posts says that i should re-locked the bootloader in order to install the official Rom and i did it
and it also doesn't work
and now i stuck i don't even have a recovery to boot on just the bootloader
i give up and took it the htc servise center and called me after tow days and says they can't fix it
please mates i don't wanna throw my phone
any help will be so appreciate
thanks

You are flashing roms for the hox on the hox xl.....you do not have a hox international, but the dual-core HTC ONE XL. So take it to the correct forum and download recoveries and roms from there !!!
Unlock the bootloader, flash the custom recovery (ment for the HTC one xl) flash the boot.img from the rom, make a full wipe and install the new HTC ONE XL rom

M.Younes said:
Hi everyone.
i bought a second hand htc one x a month ago and it was working good on jb rom
but the bootloader was already unlocked with s-on
so i thought i could see how the custom rom looks like so i downloaded a lot of Roms and trying to install them but unfortunately none of them worked not just that it's crash and go back to recovery.img witch i also flash a lot until one of them works so after i tried a lot of custom roms like "Android_Revolution_HD-one_x_33" , "HTC_one_x_-_MaximusHD_21.0" , "OTA_ENDEAVOR_U_JB_50_S_HTC_E" , "ViperX_4.0.7".
and i also tried to install the official one which is RUU... doesn't works then in some posts says that i should re-locked the bootloader in order to install the official Rom and i did it
and it also doesn't work
and now i stuck i don't even have a recovery to boot on just the bootloader
i give up and took it the htc servise center and called me after tow days and says they can't fix it
please mates i don't wanna throw my phone
any help will be so appreciate
thanks
Click to expand...
Click to collapse
Did you follow the correct procedure to flash a rom ?
1.Flash kernel with boot.img which is available in zip file.
2.Boot into recovery and wipe cache , dalvik cache , system.
3.Flash rom and the gapps.
i guess u have missed the 1st step.
Now all u have to do is unlock the bootloader again , flash appropriate recovery and follow the first three steps again. It doesn't matter if its a custom rom. But be sure to download the appropriate one. Don worry ur fone is not all over. Wait for some expert's opinion. Stay cool.

Why do people repeat the already given answers ? the correct procedure is to download the device specific correct roms !!!

deepakramji said:
Did you follow the correct procedure to flash a rom ?
1.Flash kernel with boot.img which is available in zip file.
2.Boot into recovery and wipe cache , dalvik cache , system.
3.Flash rom and the gapps.
i guess u have missed the 1st step.
Now all u have to do is unlock the bootloader again , flash appropriate recovery and follow the first three steps again. It doesn't matter if its a custom rom. But be sure to download the appropriate one. Don worry ur fone is not all over. Wait for some expert's opinion. Stay cool.
Click to expand...
Click to collapse
You're giving incorrect advice. You failed to notice that the user is flashing Endeavoru ROMs to an Evita phone.
Sent from my Evita
---------- Post added at 08:25 PM ---------- Previous post was at 08:21 PM ----------
M.Younes said:
Hi everyone.
i bought a second hand htc one x a month ago and it was working good on jb rom
but the bootloader was already unlocked with s-on
so i thought i could see how the custom rom looks like so i downloaded a lot of Roms and trying to install them but unfortunately none of them worked not just that it's crash and go back to recovery.img witch i also flash a lot until one of them works so after i tried a lot of custom roms like "Android_Revolution_HD-one_x_33" , "HTC_one_x_-_MaximusHD_21.0" , "OTA_ENDEAVOR_U_JB_50_S_HTC_E" , "ViperX_4.0.7".
and i also tried to install the official one which is RUU... doesn't works then in some posts says that i should re-locked the bootloader in order to install the official Rom and i did it
and it also doesn't work
and now i stuck i don't even have a recovery to boot on just the bootloader
i give up and took it the htc servise center and called me after tow days and says they can't fix it
please mates i don't wanna throw my phone
any help will be so appreciate
thanks
Click to expand...
Click to collapse
All you need to do is unlock your bootloader again, flash an Evita recovery, and flash an Evita ROM. Your main problem is probably that you've been wandering into the wrong device forum. You have the HTC One XL (Evita), not the HTC One X (Endeavoru). Our device main page is here:
http://forum.xda-developers.com/forumdisplay.php?f=1538
Bookmark that page and make sure you stay within it. Don't ever download anything for your phone unless you find out linked within our forum.
Sent from my Evita

timmaaa said:
You're giving incorrect advice. You failed to notice that the user is flashing Endeavoru ROMs to an Evita phone.
Sent from my Evita
---------- Post added at 08:25 PM ---------- Previous post was at 08:21 PM ----------
All you need to do is unlock your bootloader again, flash an Evita recovery, and flash an Evita ROM. Your main problem is probably that you've been wandering into the wrong device forum. You have the HTC One XL (Evita), not the HTC One X (Endeavoru). Our device main page is here:
http://forum.xda-developers.com/forumdisplay.php?f=1538
Bookmark that page and make sure you stay within it. Don't ever download anything for your phone unless you find out linked within our forum.
Sent from my Evita
Click to expand...
Click to collapse
Oops.. Thank you.. But i have learnt that flashing a wrong custom rom could brick the device.. how far is that true..??

deepakramji said:
Oops.. Thank you.. But i have learnt that flashing a wrong custom rom could brick the device.. how far is that true..??
Click to expand...
Click to collapse
Flashing the wrong ROM can definitely brick a device. Some ROMs have checks in the updater script to make sure they're being installed on the right device, some ROMs don't have checks and just brick the device.
Sent from my Evita

thanks guys
first of all thank you guys for your help and sorry for my late reply but in order of 50 kb download what can i do
anyway i tried what you guys told me but unfortunately it didn't work
i re-unlock the device and i downloaded "RegeXL-evita-v2.1" and "UrDroid_Sense_5_JB_4.2.2_Odexed_5" it didn't work so i tried to flash a kernel
"JB_KERNEL_5.08.111.2_Init.d_Support_EVITA_Installer" same problem i don't know why what's wrong with it ?!!
when i was trying to install the ROMs it's says "Skipping MD5 check : no MD5 file found"
and there is another thing but somehow i don't feel it's has nothing to do with my issue: When i start the device under HTC logo with red font "This build is for development purpose......etc." i'm sure you know it guys
any other help i'll be appreciate it
thanks for you all .

M.Younes said:
first of all thank you guys for your help and sorry for my late reply but in order of 50 kb download what can i do
anyway i tried what you guys told me but unfortunately it didn't work
i re-unlock the device and i downloaded "RegeXL-evita-v2.1" and "UrDroid_Sense_5_JB_4.2.2_Odexed_5" it didn't work so i tried to flash a kernel
"JB_KERNEL_5.08.111.2_Init.d_Support_EVITA_Installer" same problem i don't know why what's wrong with it ?!!
when i was trying to install the ROMs it's says "Skipping MD5 check : no MD5 file found"
and there is another thing but somehow i don't feel it's has nothing to do with my issue: When i start the device under HTC logo with red font "This build is for development purpose......etc." i'm sure you know it guys
any other help i'll be appreciate it
thanks for you all .
Click to expand...
Click to collapse
Have you flashed the Kernel (boot.img) from ROM ZIP file in bootloader using following command after flashing the ROM?.
fastboot flash boot boot.img

M.Younes said:
first of all thank you guys for your help and sorry for my late reply but in order of 50 kb download what can i do
anyway i tried what you guys told me but unfortunately it didn't work
i re-unlock the device and i downloaded "RegeXL-evita-v2.1" and "UrDroid_Sense_5_JB_4.2.2_Odexed_5" it didn't work so i tried to flash a kernel
"JB_KERNEL_5.08.111.2_Init.d_Support_EVITA_Installer" same problem i don't know why what's wrong with it ?!!
when i was trying to install the ROMs it's says "Skipping MD5 check : no MD5 file found"
and there is another thing but somehow i don't feel it's has nothing to do with my issue: When i start the device under HTC logo with red font "This build is for development purpose......etc." i'm sure you know it guys
any other help i'll be appreciate it
thanks for you all .
Click to expand...
Click to collapse
When you flashed RageXL did you remember to flag the boot.img via fastboot after flashing the ROM? You're s-on so you need to do that whenever you flash a ROM. Refer to my How-To Guide For Beginners thread in my signature for details.
Also, which version of TWRP 2.6.3.0 are you using? Official or unofficial?
Sent from my Evita

problem solved
Guys thank you for all you've done
the device is now working properly and everything is ok
i really send my regards to xda members
and thank you ms.sathish804 to be honest that was my mistake i was doing wrong command witch is "fastboot flash recovery boot.img"
actually i felt like an idiot for me doing that
but it works after i flashed a Kernel named "JB_KERNEL_5.08.111.2_Init.d_Support_EVITA_Installer"
ms.timmaaa i don't know if TWRP is Official or unofficial but i flashed this one openrecovery-twrp-2.6.3.0-evita
thank you guys again

Good news. You've got the official recovery installed, which is fine for the ROM you flashed (obviously). If you device you want to flash a KitKat ROM you'll need to flash the unofficial version. I'd still recommend you check out the threads in my signature, they're a staple for anyone starting out with modifying phones.
Sent from my Evita

J700P Boot-Loop

Heya. I restored a full backup in TWRP, and I ended up bootlooping. I tried flashing stock firmware, and nothing has changed. I can access downloading mode, and I can flash TWRP and boot into that. Any help? I've tried everything I've came.

I used flashify to get twrp into recovery but it recovery looped and the only way i got out of it was to reflash root with odin. Hope that helps.
Is your device still rooted? I was getting set warranty bit: recovery. It just kept going back to twrp.
Sent from my SM-J700P using Tapatalk

Synz86 said:
I used flashify to get twrp into recovery but it recovery looped and the only way i got out of it was to reflash root with odin. Hope that helps.
Is your device still rooted? I was getting set warranty bit: recovery. It just kept going back to twrp.
Sent from my SM-J700P using Tapatalk
Click to expand...
Click to collapse
I'll try reflashing the root thing. Thanks.
EDIT: Does not work.

No problem, good luck. Let me know if it works, took me a couple times.
Sent from my SM-J700P using Tapatalk

I personally just had to reflash stock boot.img in odin when i got my bootloop and all was well

where can i download the stockl firmware for the boost mobile variant. I am in a bootloop here and have tried everything . I need the stock firmware so i can flash it via odin.

Having the same problem!
I rooted, flashed twrp, and Xposed successfully and made a complete backup. I got a little excessive with my debloating, so I tried to restore my nandroid backup with twrp.. Been bootlooped ever since. I tried flashing the stock boot, recovery, and rom with odin. Nothing works. The best result I can get is when I use Odin to flash stock firmware, then flash the chainfire autoroot. If I do that, it still bootloops, but it gets all the way to the "optimizing apps" screen... If I don't flash the autoroot, it loops after the virgin mobile logo. If I try to use stock rom, cf autoroot, and twrp, it goes all crazy at the initial Samsung screen and won't even loop. I've tried every combination I can think of. Maybe has something to do with the initial welcome/activation not being active? I would think the stock rom does have it enabled though.. HELP PLEASE! I have the 2016 variant from Virgin, 6.1.1
---------- Post added at 01:39 PM ---------- Previous post was at 01:35 PM ----------
DirtyPISTOLA said:
I personally just had to reflash stock boot.img in odin when i got my bootloop and all was well
Click to expand...
Click to collapse
Do you have the 2016 Virgin mobile variant? I know the 2015s have different firmware and seem to have no problems unbricking. Just curious

uberpyrit said:
I rooted, flashed twrp, and Xposed successfully and made a complete backup. I got a little excessive with my debloating, so I tried to restore my nandroid backup with twrp.. Been bootlooped ever since. I tried flashing the stock boot, recovery, and rom with odin. Nothing works. The best result I can get is when I use Odin to flash stock firmware, then flash the chainfire autoroot. If I do that, it still bootloops, but it gets all the way to the "optimizing apps" screen... If I don't flash the autoroot, it loops after the virgin mobile logo. If I try to use stock rom, cf autoroot, and twrp, it goes all crazy at the initial Samsung screen and won't even loop. I've tried every combination I can think of. Maybe has something to do with the initial welcome/activation not being active? I would think the stock rom does have it enabled though.. HELP PLEASE! I have the 2016 variant from Virgin, 6.1.1
---------- Post added at 01:39 PM ---------- Previous post was at 01:35 PM ----------
Do you have the 2016 Virgin mobile variant? I know the 2015s have different firmware and seem to have no problems unbricking. Just curious
Click to expand...
Click to collapse
You need an adb enabled boot.img and get a logcat on boot to know the reason of this problem

chucksaysblah said:
where can i download the stockl firmware for the boost mobile variant. I am in a bootloop here and have tried everything . I need the stock firmware so i can flash it via odin.
Click to expand...
Click to collapse
http://forum.xda-developers.com/galaxy-j7/how-to/sm-j700p-stock-recovery-stock-boot-t3423314
---------- Post added at 01:58 PM ---------- Previous post was at 01:52 PM ----------
messi2050 said:
You need an adb enabled boot.img and get a logcat on boot to know the reason of this problem
Click to expand...
Click to collapse
OK. Would the boot.img extracted from the stock rom be adb enabled? I'm on my way to work, so I'll have to wait till I get home to try.

uberpyrit said:
http://forum.xda-developers.com/galaxy-j7/how-to/sm-j700p-stock-recovery-stock-boot-t3423314
---------- Post added at 01:58 PM ---------- Previous post was at 01:52 PM ----------
OK. Would the boot.img extracted from the stock rom be adb enabled? I'm on my way to work, so I'll have to wait till I get home to try.
Click to expand...
Click to collapse
No It's not

uberpyrit said:
http://forum.xda-developers.com/galaxy-j7/how-to/sm-j700p-stock-recovery-stock-boot-t3423314
---------- Post added at 01:58 PM ---------- Previous post was at 01:52 PM ----------
OK. Would the boot.img extracted from the stock rom be adb enabled? I'm on my way to work, so I'll have to wait till I get home to try.
Click to expand...
Click to collapse
You need to go to CoffeeNAndroids thread here http://forum.xda-developers.com/galaxy-j7/development/adb-root-access-boot-image-custom-t3431590 to downkoad the adb enabled boot.img

DirtyPISTOLA said:
You need to go to CoffeeNAndroids thread here http://forum.xda-developers.com/galaxy-j7/development/adb-root-access-boot-image-custom-t3431590 to downkoad the adb enabled boot.img
Click to expand...
Click to collapse
Downloaded and flashed the adb-enabled boot.img, now doing the research on how to make it work so i can post my logcat output. ive never done this before so im having to research it(noob, sorry ) i dont want to waste anyones time, ill figure it out, but if someone has time and could post the steps to do it id be grateful. gonna read up on it till i figure out how to work it anyway, but in the meantime someone could be reading my logs.

uberpyrit said:
Downloaded and flashed the adb-enabled boot.img, now doing the research on how to make it work so i can post my logcat output. ive never done this before so im having to research it(noob, sorry ) i dont want to waste anyones time, ill figure it out, but if someone has time and could post the steps to do it id be grateful. gonna read up on it till i figure out how to work it anyway, but in the meantime someone could be reading my logs.
Click to expand...
Click to collapse
np we all were noobs in the beginning here are the steps
-connect your phone to pc
-download mini adb from here :
http://forum.xda-developers.com/showthread.php?t=2317790
-turn on your phone and while it's stuck at sam logo type in mini adb [adb logcat -v long > name of problem.txt}
-u will get a file in the mini adb folder upload it here so i can help you .

messi2050 said:
np we all were noobs in the beginning here are the steps
-connect your phone to pc
-download mini adb from here :
http://forum.xda-developers.com/showthread.php?t=2317790
-turn on your phone and while it's stuck at sam logo type in mini adb [adb logcat -v long > name of problem.txt}
-u will get a file in the mini adb folder upload it here so i can help you .
Click to expand...
Click to collapse
ok, so, every way i try this it isnt working. i flashed twrp so i could do a total wipe. then flashed the stock rom/firmware(J700PVPU1APB7.tar.md5). i flashed the adb-enabled boot.img and tried the logcat, it says waiting on device while the phone bootloops... when i flash cfautoroot and adb boot.img after rom flash, same thing. What am I doing wrong? Device drivers and adb drivers installed 2 weeks ago.
so, i just flashed stock rom:cfautoroot:adb boot.img:stock recovery, and it started to boot properly, ie: android updating apps to android starting, and a bunch of other stuff, then rebooted to bootloop.. farther than ive gotten so far.
---------- Post added at 11:07 PM ---------- Previous post was at 11:06 PM ----------
uberpyrit said:
ok, so, every way i try this it isnt working. i flashed twrp so i could do a total wipe. then flashed the stock rom/firmware(J700PVPU1APB7.tar.md5). i flashed the adb-enabled boot.img and tried the logcat, it says waiting on device while the phone bootloops... when i flash cfautoroot and adb boot.img after rom flash, same thing. What am I doing wrong? Device drivers and adb drivers installed 2 weeks ago.
so, i just flashed stock rom:cfautoroot:adb boot.img:stock recovery, and it started to boot properly, ie: android updating apps to android starting, and a bunch of other stuff, then rebooted to bootloop.. farther than ive gotten so far.
Click to expand...
Click to collapse
trying to recreate the process now...

uberpyrit said:
ok, so, every way i try this it isnt working. i flashed twrp so i could do a total wipe. then flashed the stock rom/firmware(J700PVPU1APB7.tar.md5). i flashed the adb-enabled boot.img and tried the logcat, it says waiting on device while the phone bootloops... when i flash cfautoroot and adb boot.img after rom flash, same thing. What am I doing wrong? Device drivers and adb drivers installed 2 weeks ago.
so, i just flashed stock rom:cfautoroot:adb boot.img:stock recovery, and it started to boot properly, ie: android updating apps to android starting, and a bunch of other stuff, then rebooted to bootloop.. farther than ive gotten so far.
---------- Post added at 11:07 PM ---------- Previous post was at 11:06 PM ----------
trying to recreate the process now...
Click to expand...
Click to collapse
You didn't did anything wrong , it's coffenandroid adb enabled is not working correctly , now try to flash stock recovery as i heard that twrp cause bootloop on j700p

messi2050 said:
No It's not
Click to expand...
Click to collapse
Hey messie,
I have somehow switched the variant of my boost j7 when I was rebuilding it with wifi tethering anyways since I did that my phone is on xas which is Australia I believe and it was working fine even on that variant until I put twrp on it and not even the stock boost firmware has fixed it I do have a backup before the variant was changed that was made with FlashFire but the twrp backup FlashFire makes by default doesn't work and all it does it boot loop over and over and sometimes it will say it is optimizing apps sometumes but doesn't ever load it just reboots and repeats the same thing I tried doing a complete wipe in twrp and tried ur debloated firmware which was very similar to the project I was working on as well as a cm port. I can't go any further on my projects until I can get functionality outta the phone again is there maybe a way I could load FlashFire in twrp as I have root and adb working fully or it there other stuff I could do in adb to fix this I even tried Making the csc only for BST instead of XAS but no go it had no effect

Starchild2k said:
Hey messie,
I have somehow switched the variant of my boost j7 when I was rebuilding it with wifi tethering anyways since I did that my phone is on xas which is Australia I believe and it was working fine even on that variant until I put twrp on it and not even the stock boost firmware has fixed it I do have a backup before the variant was changed that was made with FlashFire but the twrp backup FlashFire makes by default doesn't work and all it does it boot loop over and over and sometimes it will say it is optimizing apps sometumes but doesn't ever load it just reboots and repeats the same thing I tried doing a complete wipe in twrp and tried ur debloated firmware which was very similar to the project I was working on as well as a cm port. I can't go any further on my projects until I can get functionality outta the phone again is there maybe a way I could load FlashFire in twrp as I have root and adb working fully or it there other stuff I could do in adb to fix this I even tried Making the csc only for BST instead of XAS but no go it had no effect
Click to expand...
Click to collapse
Hi
Although a logcat is needed to solve the problem , i believe that this happens because of the kernel security , i think that a permissive kernel is included in this file
http://www.mediafire.com/?u6skqbc4x5bo73p
If it's there flash it and you should have successful boot proces , good luck!

messi2050 said:
Hi
Although a logcat is needed to solve the problem , i believe that this happens because of the kernel security , i think that a permissive kernel is included in this file
http://www.mediafire.com/?u6skqbc4x5bo73p
If it's there flash it and you should have successful boot proces , good luck!
Click to expand...
Click to collapse
Thanx Messi I am going to try it now

messi2050 said:
np we all were noobs in the beginning here are the steps
-connect your phone to pc
-download mini adb from here :
http://forum.xda-developers.com/showthread.php?t=2317790
-turn on your phone and while it's stuck at sam logo type in mini adb [adb logcat -v long > name of problem.txt}
-u will get a file in the mini adb folder upload it here so i can help you .
Click to expand...
Click to collapse
im still working on getting the logs, nothing seems to make the phone readable to logcat. it just says waiting for device..

Starchild2k said:
Thanx Messi I am going to try it now
Click to expand...
Click to collapse
np , tell me if it works for you
---------- Post added at 06:41 PM ---------- Previous post was at 06:39 PM ----------
uberpyrit said:
im still working on getting the logs, nothing seems to make the phone readable to logcat. it just says waiting for device..
Click to expand...
Click to collapse
I'm going to make one and upload it