Develop Bugs

Bricked or not bricked?

I had an issue with my phone a couple of weeks ago where I'm only able to the bootloader screen and the fastboot screen. Fortunately, I got a replacement EVO 3 days later but I'm still trying to get my old phone up and running. But after trying everything I can find, still nothing.
So my question is, when do I say that the phone is officially bricked?
Sent from my PC36100 using Tapatalk

If you can get to the bootloader screen, then you be able to flash an image to get you phone working again.
Sent from my Decked Out HTC EVO with Tapatalk!

dwelder said:
If you can get to the bootloader screen, then you be able to flash an image to get you phone working again.
Sent from my Decked Out HTC EVO with Tapatalk!
Click to expand...
Click to collapse
Believe me, I've tried everything, from using amon ra PC36IMG.zip in the bootloader. It updates successfully then still no recovery.
I've tried the ruu via bootloader, it updates successfully. It still bootloops continually.
I ran Football's recent 4.54 ruu in fastboot successfully and still nothing.
Everything I try, it continues to bootloop.
Sent from my PC36100 using Tapatalk

Were you using CM7 before your phone started bootlooping?

Concordium said:
Were you using CM7 before your phone started bootlooping?
Click to expand...
Click to collapse
10/14 miui with tiamat 4.1 sbc.
Sent from my PC36100 using Tapatalk

andygu3 said:
10/14 miui with tiamat 4.1 sbc.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Well CM7 is the ROM typically being run when phones enter the bootloop of death. However, I've heard that there have been a couple of MIUI ROMs that have entered the bootloop of death as well. If you've flash a recovery and still cant enter it and tried to fully unroot then you might have to take it to Sprint. I'd make sure that you're fully unrooted before doing so. I would also recommend removing your SD card so that they cant try to deny you based on rooting the phone. Just a precaution.

andygu3 said:
Believe me, I've tried everything, from using amon ra PC36IMG.zip in the bootloader. It updates successfully then still no recovery.
I've tried the ruu via bootloader, it updates successfully. It still bootloops continually.
I ran Football's recent 4.54 ruu in fastboot successfully and still nothing.
Everything I try, it continues to bootloop.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Have you tried flashing the images via fastboot?

Concordium said:
Well CM7 is the ROM typically being run when phones enter the bootloop of death. However, I've heard that there have been a couple of MIUI ROMs that have entered the bootloop of death as well. If you've flash a recovery and still cant enter it and tried to fully unroot then you might have to take it to Sprint. I'd make sure that you're fully unrooted before doing so. I would also recommend removing your SD card so that they cant try to deny you based on rooting the phone. Just a precaution.
Click to expand...
Click to collapse
Fortunately, I already got a new phone but the reason I didn't take it into Sprint was because it still was S-off. Since I can't get to recovery, how would I get s-on?
And now that I ran stock ruu's, is it a possibility that the PC36IMG.zip's won't be recognized anymore?
I'd love to get this phone running again and let my 7 year play some games on it but I'm afraid I may be sol!!
Sent from my PC36100 using Tapatalk

teh roxxorz said:
Have you tried flashing the images via fastboot?
Click to expand...
Click to collapse
Please elaborate! Not sure what to flash in fastboot?
Sent from my PC36100 using Tapatalk

andygu3 said:
Please elaborate! Not sure what to flash in fastboot?
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Well you said you tried flashing via PC36IMG, and it 'worked' but it didn't stick, i.e it didn't 'work'. What you can do is extract the boot.img from the rom / ruu, place it in your adb tools folder. Then boot the phone to the bootloader, select fastboot, connect to your pc via usb cable, open up command prompt, navigate to you adb tools folder and type:
fastboot flash boot boot.img
fastboot reboot
That will flash the boot image to the correct partition, then reboot the phone, and see if it boots up.

andygu3 said:
Fortunately, I already got a new phone but the reason I didn't take it into Sprint was because it still was S-off. Since I can't get to recovery, how would I get s-on?
And now that I ran stock ruu's, is it a possibility that the PC36IMG.zip's won't be recognized anymore?
I'd love to get this phone running again and let my 7 year play some games on it but I'm afraid I may be sol!!
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Here you go
http://forum.xda-developers.com/showpost.php?p=18399552&postcount=2

teh roxxorz said:
Well you said you tried flashing via PC36IMG, and it 'worked' but it didn't stick, i.e it didn't 'work'. What you can do is extract the boot.img from the rom / ruu, place it in your adb tools folder. Then boot the phone to the bootloader, select fastboot, connect to your pc via usb cable, open up command prompt, navigate to you adb tools folder and type:
fastboot flash boot boot.img
fastboot reboot
That will flash the boot image to the correct partition, then reboot the phone, and see if it boots up.
Click to expand...
Click to collapse
Thanks for the info! I will give this a go.
I keep reading that the NV got corrupted some how, is there any way to correct this or flash something in fastboot?
Again thanks for your input, much appreciated!
Sent from my PC36100 using Tapatalk

andygu3 said:
Thanks for the info! I will give this a go.
I keep reading that the NV got corrupted some how, is there any way to correct this or flash something in fastboot?
Again thanks for your input, much appreciated!
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
No problem.
And if the NV is corrupted, its toast. It was a flaw with the evo when you bought it, and now its decide to tap out. At that point you'd have to take it to sprint, as the NV is part of flash memory and its locked.

Concordium said:
Here you go
http://forum.xda-developers.com/showpost.php?p=18399552&postcount=2
Click to expand...
Click to collapse
Thanks for this, hopefully if I can't get the boot.img working from ruu, I will do this!
Sent from my PC36100 using Tapatalk

andygu3 said:
Thanks for this, hopefully if I can't get the boot.img working from ruu, I will do this!
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Oh crap I forgot you were the one having the issue with the boot.img. If you can't get that to work then the post I gave you will most likely not work either. It's worth a try....but I doubt it.

teh roxxorz said:
No problem.
And if the NV is corrupted, its toast. It was a flaw with the evo when you bought it, and now its decide to tap out. At that point you'd have to take it to sprint, as the NV is part of flash memory and its locked.
Click to expand...
Click to collapse
Well sh**, that's a downer! If this is the case, I'm definitely sol! But hopefully I can get something out of the phone but I seriously doubt it!
Thanks guys for your input, again much appreciated. I will report back if I have any breakthrough!!
Sent from my PC36100 using Tapatalk

Im having the same issue
bootloop and the phone was using CM7. I was able to get to boot loader menu but can not get to recovery.
Tried to add recovery image no dice...now the phone will only charge and not boot

teh roxxorz said:
Well you said you tried flashing via PC36IMG, and it 'worked' but it didn't stick, i.e it didn't 'work'. What you can do is extract the boot.img from the rom / ruu, place it in your adb tools folder. Then boot the phone to the bootloader, select fastboot, connect to your pc via usb cable, open up command prompt, navigate to you adb tools folder and type:
fastboot flash boot boot.img
fastboot reboot
That will flash the boot image to the correct partition, then reboot the phone, and see if it boots up.
Click to expand...
Click to collapse
No luck!
I know someone posted the EVO Brick_fix, I believe cutthroat but since no PC36IMG.ZIP is being recognized on my sdcard. I may officially say my phone is toast.
Any other suggestions are welcome!
Sent from my PC36100 using Tapatalk

Is this normal? I can run any stock ruu and my hboot changes! I was on 2.16 but I ran the froyo ruu and now I'm back to 2.10
Any thoughts?
Sent from my PC36100 using Tapatalk

andygu3 said:
Is this normal? I can run any stock ruu and my hboot changes! I was on 2.16 but I ran the froyo ruu and now I'm back to 2.10
Any thoughts?
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Did you unbrick your EVO
I tried to use unbrick method and now phone will not boot at all
It just stays at black screen and vibrates once after pressing the power button

[Q] unusual bootloop problem

me being the idiot that i am let my younger brother have a mess around with my one x, now i have no idea what he has done (im guessing he has messed with the roms) but it will boot as far as the first lock screen and then reboots.
i know it has less than 30% battery left but i am unable to let it charge because the phone will only stop its loop if i leave it on boot loader
it also fails in recovery mode and goes back into the endless loop
any help would be greatly appreciated

tried factory reset?

just did a stock recovery and now it stays stuck on the htc screen, anybody able to help me resurrect my phone???

Try from your pc
Fastboot erase cache
After putting your phone into fastboot USB mode.
Sent from my HTC One X using xda premium

liston156 said:
me being the idiot that i am let my younger brother have a mess around with my one x, now i have no idea what he has done (im guessing he has messed with the roms) but it will boot as far as the first lock screen and then reboots.
i know it has less than 30% battery left but i am unable to let it charge because the phone will only stop its loop if i leave it on boot loader
it also fails in recovery mode and goes back into the endless loop
any help would be greatly appreciated
Click to expand...
Click to collapse
Endless boot loops is usually 1 of 2 things,
Wrong boot img (or failure to flash it after changing roms)
Unstable overclock/undervolt settings.
Sent from my HTC One X using Tapatalk 2

now it gets pasts the boot screens and onto the homepage before it reboots itself, i think i have tried everything and i have read hundreds of threads on here and nothing seems to work

Since you don't actually know what has been done to it, full wipe may help.
Sent from my HTC One X using xda premium

eyosen said:
Since you don't actually know what has been done to it, full wipe may help.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
cheers, how would i do that?

Try factory reset from bootloader.
Sent from my HTC One X using xda premium

eyosen said:
Try factory reset from bootloader.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
tried it just now and still looping

Still sounds like a boot img problem,
Flash a new kernel
And it's boot img
Sent from my HTC One X using Tapatalk 2

chrisjcks said:
Still sounds like a boot img problem,
Flash a new kernel
And it's boot img
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
whats the best method of doing this then because i have downloaded so many random zip files and flahed a ridiculous number of .img files im far from sure which one does what

liston156 said:
whats the best method of doing this then because i have downloaded so many random zip files and flahed a ridiculous number of .img files im far from sure which one does what
Click to expand...
Click to collapse
Download a kernel of choice,
It should have a modules zip file & an IMG file.
Push the zip to your phone (you can do this in clockworkmod recovery - mount usb storage, drag zip from pc to phone - unmount)
Install from sdcard from within clockworkmod
Then put phone into fastboot usb, (bootloader) and flash the boot img. (you know how to do this right?)
If not,
You should have android sdk installed on your pc, place the boot img in the same folder as fastboot and adb etc - the folder is platform-tools)
Open cmd on pc when phone is in fastboot usb.
Ie.
CD c:/Android-SDK/platform-tools
fastboot flash boot imagename.img
Sent from my HTC One X using Tapatalk 2

chrisjcks said:
Download a kernel of choice,
It should have a modules zip file & an IMG file.
Push the zip to your phone (you can do this in clockworkmod recovery - mount usb storage, drag zip from pc to phone - unmount)
Install from sdcard from within clockworkmod
Then put phone into fastboot usb, (bootloader) and flash the boot img. (you know how to do this right?)
If not,
You should have android sdk installed on your pc, place the boot img in the same folder as fastboot and adb etc - the folder is platform-tools)
Open cmd on pc when phone is in fastboot usb.
Ie.
CD c:/Android-SDK/platform-tools
fastboot flash boot imagename.img
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
cheers, unfortunately i dont have clockworkmod recovery

liston156 said:
cheers, unfortunately i dont have clockworkmod recovery
Click to expand...
Click to collapse
Here:
http://db.tt/VF9J2eo8
Flash in fastboot, the same way out would a boot.img as I explained above.
Sent from my HTC One X using Tapatalk 2

chrisjcks said:
Download a kernel of choice,
It should have a modules zip file & an IMG file.
Push the zip to your phone (you can do this in clockworkmod recovery - mount usb storage, drag zip from pc to phone - unmount)
Install from sdcard from within clockworkmod
Then put phone into fastboot usb, (bootloader) and flash the boot img. (you know how to do this right?)
If not,
You should have android sdk installed on your pc, place the boot img in the same folder as fastboot and adb etc - the folder is platform-tools)
Open cmd on pc when phone is in fastboot usb.
Ie.
CD c:/Android-SDK/platform-tools
fastboot flash boot imagename.img
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
chrisjcks said:
Here:
http://db.tt/VF9J2eo8
Flash in fastboot, the same way out would a boot.img as I explained above.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
cheers but still no luck

liston156 said:
cheers but still no luck
Click to expand...
Click to collapse
No luck with what?
You can't even flash CWM recovery - why not?
Your phone has an unlocked bootloader right, that's needed for all this.
If it doesn't and your getting boot loop problems on stock with locked bootloader, I don't know what to suggest other than flashing a RUU.
Sent from my HTC One X using Tapatalk 2

chrisjcks said:
No luck with what?
You can't even flash CWM recovery - why not?
Your phone has an unlocked bootloader right, that's needed for all this.
If it doesn't and your getting boot loop problems on stock with locked bootloader, I don't know what to suggest other than flashing a RUU.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
every time i try to flash CWM recovery it fails and then my phone reboots itself, im hoping it is just the battery being too low so im gonna put it back on charge and try again tomorrow and hopefully i have a bit more luck with it

time to try again, not got much hope left tho

liston156 said:
time to try again, not got much hope left tho
Click to expand...
Click to collapse
If you've managed to charge your phone, here shouldn't be any issues.
Sent from my HTC One X using Tapatalk 2

[Q] NEED HELP! rooted g2 wont load any rom or backups

I have had my g2 rooted for over a year with no problems running some form of cyanogen mod the whole time and yesterday my phone was acting up and I restarted it and it wont get past the cyanogen mod boot animation. I have tried flashing back up imgs and other roms but none will successfully load and I have wiped before trying to load any thing new and tried factory reset. Can anyone help me get my phone back in action?

post a logcat of the booting and also write down everything on your hboot screen
Sent from my HTC Vision using xda premium

demkantor said:
post a logcat of the booting and also write down everything on your hboot screen
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
I have android sdk on my computer but I have never used it and am not to sure how to go about getting the logcat but I am working on figuring it out but in the mean time here are some pics of the hboot screens if that helps with anything.

once sdk is installed then you need to run it and download at least all the platform tools, then well here : SEE POST THREE for more info on setting up adb and fastboot
the command prompt is
adb logcat
anyway, it looks like you should have true radio s-off with the g2 engineering hboot, this is good as long as its not a fried emmc youll be just fine
which recovery do you have? if you have 4ext then go and reformat all partitions, then flash a known stable rom like cm7.
if you have clockwork flash THIS, after it reboots to recovery flash cm7
let me know what happens

demkantor said:
once sdk is installed then you need to run it and download at least all the platform tools, then well here : SEE POST THREE for more info on setting up adb and fastboot
the command prompt is
adb logcat
anyway, it looks like you should have true radio s-off with the g2 engineering hboot, this is good as long as its not a fried emmc youll be just fine
which recovery do you have? if you have 4ext then go and reformat all partitions, then flash a known stable rom like cm7.
if you have clockwork flash THIS, after it reboots to recovery flash cm7
let me know what happens
Click to expand...
Click to collapse
This is what it said after I ran the SuperWipeG2. Not sure I went right what next?

No it crashed, try just wiping everything you can from clockwork and then reinstall rom, if it still won't run you'll need to get adb and fastboot working to keep going
Sent from my HTC Vision using xda premium

foroudi9 said:
I have android sdk on my computer but I have never used it and am not to sure how to go about getting the logcat but I am working on figuring it out but in the mean time here are some pics of the hboot screens if that helps with anything.
Click to expand...
Click to collapse
you can try the tool at my signature(AIOlog) to get the logcat easily

demkantor said:
No it crashed, try just wiping everything you can from clockwork and then reinstall rom, if it still won't run you'll need to get adb and fastboot working to keep going
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
That link didn't help much b/c I have a mac :/

demkantor said:
No it crashed, try just wiping everything you can from clockwork and then reinstall rom, if it still won't run you'll need to get adb and fastboot working to keep going
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
maybe the sdcard has given up?

PNuT. said:
maybe the sdcard has given up?
Click to expand...
Click to collapse
I can still add and remove things from the sd card if I put it in my computer or does that not mean anything?

Sd is probably fine, just do a quick google or xda search for how to setup adb or fastboot on mac
Debugging android is far easier when you have these super important tools at hand
Sent from my HTC Vision using xda premium
---------- Post added at 11:58 PM ---------- Previous post was at 11:52 PM ----------
Oh and one more thing you can try if you just can't get adb/fastboot to work, in the link I sent I did post a dropbox links with some pc10img.zips I made to help people quickly get newer radio,hboot,4extrecovery, I think its post 30
Just grab one (usualy dzhboot is best but it really won't matter much if you don't use sense roms) rename pc10img.zip and put it on root of sdcard (not in any folder) then boot into bootloader and hit yes on the prompt, the phone will probably reboot halfway through update, don't worry, when its all done (you'll know when it is) choose reboot to recovery
From here format all partitions (you'll have 4ext recovery, just play around in there untill you find out where options are) then see if the rom flashing will work
Sent from my HTC Vision using xda premium

demkantor said:
No it crashed, try just wiping everything you can from clockwork and then reinstall rom, if it still won't run you'll need to get adb and fastboot working to keep going
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Okay I got adb and fastboot working and this is where I am at. I'm not exactly sure how to get the logcat now.

Open up a command prompt and type
adb devices
Some things may differ in osx but I'm sure there are guides for this
If you see your serial # good, if not then trouble shoot
Try it in recovery first
once running, in command type
adb logcat
While the phone is booting
If you can get it running, copy and paste the output here (preferably in pastebin)
If you can't get anything while booting try and get your emmc
In adb type
cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc0/mmc0:0001/name
Hope its not the SEM04G as its prone to failure
Sent from my Nexus 7 using xda premium

demkantor said:
Open up a command prompt and type
adb devices
Some things may differ in osx but I'm sure there are guides for this
If you see your serial # good, if not then trouble shoot
Try it in recovery first
once running, in command type
adb logcat
While the phone is booting
If you can get it running, copy and paste the output here (preferably in pastebin)
If you can't get anything while booting try and get your emmc
In adb type
cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc0/mmc0:0001/name
Hope its not the SEM04G as its prone to failure
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Finally got it! I couldn't get pastebin to submit it so I used zerobin. Let me know if that works. Thanks for all your help so far.
http://sebsauvage.net/paste/?efc68f7ab2e5db9c#ZbvCJEEIkOvjIpTQZjiSXxeLHfJ4WkUIuX6On+fuzPE=

well your definitely stuck in a loop and a short one at that. there are some memory read issues but i dont think its a failed emmc.
boot to recovery and try the command i listed above only i forgot the first command to put you in a shell
adb shell
cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc0/mmc0:0001/name
this will tell you which chip you have
also now that you have adb working, i will presume fastboot works too
follow the guide i linked you and flash 4ext recovery via fastboot (commands may differ do to mac) if you get absolutely stuck use the pc10img.zip

demkantor said:
well your definitely stuck in a loop and a short one at that. there are some memory read issues but i dont think its a failed emmc.
boot to recovery and try the command i listed above only i forgot the first command to put you in a shell
adb shell
cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc0/mmc0:0001/name
this will tell you which chip you have
also now that you have adb working, i will presume fastboot works too
follow the guide i linked you and flash 4ext recovery via fastboot (commands may differ do to mac) if you get absolutely stuck use the pc10img.zip
Click to expand...
Click to collapse
well i used the pc10img.zip and it never finished updating on the hboot screen (the progress bar on the right of the screen never finished loading) so it stayed that way for a few hours and I pulled the battery b/c it was completely unresponsive. Now I cant power on to hboot or recovery or anything for that matter. I'm guessing it is bricked... is that a good assumption?

Hopefully not, flashing a pc10img.zip through hboot can be risky when in a situation like yours. Its less risky through fastboot as you can choose not to reboot untill all is fixed. Depending on where the flashing got stuck you could be in trouble as if it flashed an incomplete radio or hboot then its bad news. Hopefully this isn't the case. Battery won't charge in hboot mode so if it is possible batt is dead. Charge it with phone off, does the led come on? If so let it charge until green. If it does that then I'm thinking it will turn on again (hopefully)
if it won't then try leaving the battery out for a day and trying again (don't know why this works but some says it does) let me know what happens
Sent from my HTC Vision using xda premium

demkantor said:
Hopefully not, flashing a pc10img.zip through hboot can be risky when in a situation like yours. Its less risky through fastboot as you can choose not to reboot untill all is fixed. Depending on where the flashing got stuck you could be in trouble as if it flashed an incomplete radio or hboot then its bad news. Hopefully this isn't the case. Battery won't charge in hboot mode so if it is possible batt is dead. Charge it with phone off, does the led come on? If so let it charge until green. If it does that then I'm thinking it will turn on again (hopefully)
if it won't then try leaving the battery out for a day and trying again (don't know why this works but some says it does) let me know what happens
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
The led dosnt come on but i will give it a shot leaving it out. I am sure i remember there being a conformation that the radio did finish but I dont remember what else it said but it was nearly done when it froze. I'll get back to you in a day with the results.

I believe it flashes radio and hboot first, the rest wouldn't cause a brick so if it passed that then ok. Unless your partitions were super curropt and somehow the flash didn't but the phone thought it did.
I guess for now just hope the battery is dead or something like that but I hate to say that no led is a bad sign...
Sent from my HTC Vision using xda premium

[Q] Finally took the plunge and rooted it, but can't do anything else?

Finally rooted the phone today, but when I try to go into an alternate recovery, or install a ROM (which I've never done before) the phone reboots (like it should I'm assuming) begins to load what I told it to do, and then I get an image of my phone with a red question mark above it, and my phone just reboots again.
What's causing this?

R: [Q] Finally took the plunge and rooted it, but can't do anything else?
ghostspectrum said:
Finally rooted the phone today, but when I try to go into an alternate recovery, or install a ROM (which I've never done before) the phone reboots (like it should I'm assuming) begins to load what I told it to do, and then I get an image of my phone with a red question mark above it, and my phone just reboots again.
What's causing this?
Click to expand...
Click to collapse
Did you flash a custom recovery? If no, flash it and try again
Sent from my One V using xda app-developers app

mr_nooby said:
Did you flash a custom recovery? If no, flash it and try again
Sent from my One V using xda app-developers app
Click to expand...
Click to collapse
I tried using ROM manager but I get the exact same results
Sent from my HTC One V using xda app-developers app

Tried using TWR got similar results with the image of the phone with a red triangle and exclamation mark :'(
Sent from my HTC One V using xda app-developers app

How are you flashing the recovery. The description you are describing is the stock recovery to flash a new recovery do it in fastboot (fastboot flash recovery name of recovery here)
Get the all in one tool from the dev section and it will do it for you.
All you need to do is choose which one you want CDMA or gsm, twrp or cwm (i prefer twrp for the one v)
Sent from my HTC One V+ (Because the X+ isn't as bamf as my V+)
If I helped you don't say thanks, click it!!

Tehwafflez said:
How are you flashing the recovery. The description you are describing is the stock recovery to flash a new recovery do it in fastboot (fastboot flash recovery name of recovery here)
Get the all in one tool from the dev section and it will do it for you.
All you need to do is choose which one you want CDMA or gsm, twrp or cwm (i prefer twrp for the one v)
Sent from my HTC One V+ (Because the X+ isn't as bamf as my V+)
If I helped you don't say thanks, click it!!
Click to expand...
Click to collapse
Hey thanks when I get home I'll give it a shot
Sent from my HTC One V using xda app-developers app

'Ok the All in one tool worked. I flashed TWRP, wiped my caches and installed AOKP JB 4.1.2, i've got the "Initiating swagger" screen, how long should this take?It's been about 10 minutes...
So as far as i can tell, the rom install failed because i didnt complete the wipe (because the wipe through TWRP failed...) what causes this?

It will say it failed because the sd-ext didn't wipe (THAT'S A GOOD THING) the /sd-ext is your SD card lol. So did you get into the actual ROM for aokp? So when you clicked swaggerfy it froze? Hmm I'd try a different ROM or different kernel what kernel are u using. I reccomend Jan 3rd super slick (anything newer breaks the camera).
Edit: i noticed you said caches? Do did you click factory reset? I usually do factory and dalvik but i think factory does it all.
Sent from my HTC One V+ (Because the X+ isn't as bamf as my V+)
If I helped you don't say thanks, click it!!

Tehwafflez said:
It will say it failed because the sd-ext didn't wipe (THAT'S A GOOD THING) the /sd-ext is your SD card lol. So did you get into the actual ROM for aokp? So when you clicked swaggerfy it froze? Hmm I'd try a different ROM or different kernel what kernel are u using. I reccomend Jan 3rd super slick (anything newer breaks the camera).
Edit: i noticed you said caches? Do did you click factory reset? I usually do factory and dalvik but i think factory does it all.
Sent from my HTC One V+ (Because the X+ isn't as bamf as my V+)
If I helped you don't say thanks, click it!!
Click to expand...
Click to collapse
I hope I get a fairly quick response to this Followed some advide in that thread, flashed a kernel (I thought) using the All In One Tool, ever since, I've been stuck in a bootloop. Obviously I have access to my bootloader and TWRP (thankfully). My recovery backup returns the same results though.
Im new to this so I'll try toprovide all the info I can.
Followed the TUT on how to Unlock Bootloader and Root 2 days ago.
Yesterday, using the All In One tool, flashed TWRP onto phone.
Was unable to Flash AOKP JellyBean 4.1.2 so I asked for help again (ROM was flashed, but stuck on Initiating Swagger Boot)
Tried using All-In-One to flash (what I thought was) a kernel, since then, my phone just boots continuously or not at all (depending on if I wipe or whatnot)
While at work, I was able to Flash the AOKP rom and Boot into it, but after about 1 minute of use, it reboots.
This is where I'm at now.
My bootloader says
***UNLOCKED***
PRIMOC PVT SHIP S-ON RL
HBOOT- 1.57.0000
RADIO- 1.00.05.0929
eMMC-boot
Jun 18 2012, 10:22:43
I'm using the latest version (2.3.3.) of TWRP
Is there anyway I can find, and delete, the boot.img I flashed with All-In-One, that caused this bootloop?

Found out why: radio is the new version aka .0928
HTC provided a new radio release and it screwed up being able to flash new JB roms. The fixable solution is to find the virgin mobile ruu exe and do that long process to get the old radio: .0521_2(?) back. I'll link you to the ruu thread in a sec let me find it first
Here:
http://forum.xda-developers.com/showthread.php?t=2018518
Sent from my HTC One V+ (Because the X+ isn't as bamf as my V+)
If I helped you don't say thanks, click it!!

Tehwafflez said:
Found out why: radio is the new version aka .0928
HTC provided a new radio release and it screwed up being able to flash new JB roms. The fixable solution is to find the virgin mobile ruu exe and do that long process to get the old radio: .0521_2(?) back. I'll link you to the ruu thread in a sec let me find it first
Here:
http://forum.xda-developers.com/showthread.php?t=2018518
Sent from my HTC One V+ (Because the X+ isn't as bamf as my V+)
If I helped you don't say thanks, click it!!
Click to expand...
Click to collapse
The only problem right now is when I'm in FASTBOOTUSB my computer doesn't recognize my phone.

You get fastboot USB and you're headed in the right direction

mihirengg19 said:
You get fastboot USB and you're headed in the right direction
Click to expand...
Click to collapse
But I'm having a hard time flashing that new RUU because when I'm in my Bootloader, and in Fastboot USB, my computer doesn't see my phone.

WHen I try to enter the fastboot code into the cmd shell, It just says that fastboot is not a recognized command...

That's because you aren't changing the directory to the fastboot folder.

mihirengg19 said:
That's because you aren't changing the directory to the fastboot folder.
Click to expand...
Click to collapse
How do I do that?

ghostspectrum said:
How do I do that?
Click to expand...
Click to collapse
All right do this.
Create a folder as fastboot on c drive of PC(hope you're on windows)
Download fast boot files.
Put in c:/Fastboot
Go in fastboot mode on phone.
It should say fastboot USB.
Open command prompt.
Type cd c:/fastboot/
Hit enter. The prompt should say this address now.
Type your fast boot command you want
Sent from my HTC One V using xda app-developers app

soham_sss said:
All right do this.
Create a folder as fastboot on c drive of PC(hope you're on windows)
Download fast boot files.
Put in c:/Fastboot
Go in fastboot mode on phone.
It should say fastboot USB.
Open command prompt.
Type cd c:/fastboot/
Hit enter. The prompt should say this address now.
Type your fast boot command you want
Sent from my HTC One V using xda app-developers app
Click to expand...
Click to collapse
Ok thank you, I do have that fastboot folder haha, gonna have to let my phone charge over night thought (I assume) so I'll try a crack at it tomorrow.

ghostspectrum said:
Ok thank you, I do have that fastboot folder haha, gonna have to let my phone charge over night thought (I assume) so I'll try a crack at it tomorrow.
Click to expand...
Click to collapse
Do NOT charge it over night. It damages the battery, and this is experience talking to you. Leave your phone charging for 3 hours, and that's sufficient.
Sent from my HTC One V using xda app-developers app

soham_sss said:
All right do this.
Create a folder as fastboot on c drive of PC(hope you're on windows)
Download fast boot files.
Put in c:/Fastboot
Go in fastboot mode on phone.
It should say fastboot USB.
Open command prompt.
Type cd c:/fastboot/
Hit enter. The prompt should say this address now.
Type your fast boot command you want
Sent from my HTC One V using xda app-developers app
Click to expand...
Click to collapse
SCratch that. Completed the process, the program said it did everything, but back in bootloader, it still shows Radio- 1.00.05.0929 :/ and I can't get out of boot loader lol

[HBOOT MOD] Remove the red text

YOU MUST BE SOFF TO USE THIS MOD, IF YOU DONT KNOW WHAT THAT IS YOU DONT HAVE IT. I AM NOT RESPONSIBLE FOR BRICKS DUE TO YOUR NEGLIGENCE. Now lets continue.
You can find the hboot here to download: Download
Once you download this zip, extract all of its contents. You will need to verify the md5 of the mmcblk0p18 so be sure to pull the .md5 as well. Once you have the files, open the md5 in a text editor of choice. Then, put the mmcblk0p18 into your adb folder. If its in your path, I will make the assumption you can modify this to your needs. You will now need to use the code below. Be sure you are booted into android!
Code:
adb push mmcblk0p18 /sdcard/mmcblk0p18
adb shell
su
md5sum /sdcard/mmcblk0p18
#now check the output of this command with the md5 in the file you opened in notepad. If it DOES [U]NOT[/U] MATCH, [U][B]DO NOT[/B][/U] proceed
dd if=/sdcard/mmcblk0p18 of=/dev/block/mmcblk0p18
diff /sdcard/mmcblk0p18 /dev/block/mmcblk0p18
# IF THESE DIFFER DO NOT REBOOT, try the command again. If you are not S-OFF then you will see that the files WILL differ.
Now, you can reboot and the red warning text will be gone! Enjoy!

After you do this, it will look like this (Hboot will show 1.18.9999):
In addition, phone will no longer be recognized in fastboot mode on USB 3.0 ports

kusanagi-sama said:
After you do this, it will look like this:
In addition, phone will no longer be recognized in fastboot mode on USB 3.0 ports
Click to expand...
Click to collapse
Any other side-effects???

rohov said:
Any other side-effects???
Click to expand...
Click to collapse
Just that

kusanagi-sama said:
After you do this, it will look like this (Hboot will show 1.18.9999):
In addition, phone will no longer be recognized in fastboot mode on USB 3.0 ports
Click to expand...
Click to collapse
s-off....how???....
Sent from my One V using xda premium

handryg555 said:
s-off....how???....
Sent from my One V using xda premium
Click to expand...
Click to collapse
I think you have to be one of the lucky ones to have an S-Off phone.

Can I have a more simpler method for noobo like me. Thanks anyway.
Sent from my One V

to_sukanta said:
Can I have a more simpler method for noobo like me. Thanks anyway.
Sent from my One V
Click to expand...
Click to collapse
There isn't any other simpler way than that. If you can't handle a few commands, you shouldn't be modding your phone.

Is it also possible to change the screen to diff boot logo with s-off? Or can i only remove red text?
Sent from a hand.

Snyper0012 said:
Is it also possible to change the screen to diff boot logo with s-off? Or can i only remove red text?
Sent from a hand.
Click to expand...
Click to collapse
You can change the boot animation, but you can't change the boot logo, just remove the red text.

Not entirely true. I know of a utility that converts a 480x800bmp to nbh. From there (with an eng fast boot mod,(I got a friend working on it who will be nameless so you don't all bug him)) fastboot flash splash custom.nbh
Sent from my One V using Tapatalk 2

Can anyone please please confirm if I need to boot into boot loader to run the mode or normal booting into the system would be enough to run the adb commands?? I booted into normal system but adb commands showing that device not found.

You do this in rooted android with USB debugging enabled. If you can't follow the instructions, then you shouldn't be using this mod
Sent from my One V using Tapatalk 2

simonsimons34 said:
You do this in rooted android with USB debugging enabled. If you can't follow the instructions, then you shouldn't be using this mod
Sent from my One V using Tapatalk 2
Click to expand...
Click to collapse
Just asking, are there phones shipped with S-Off?As there is no method to off it by ourselves.If there are, they are indigenous to which countries?Where have they appeared?Or are they development phones?

Steam. said:
Just asking, are there phones shipped with S-Off?As there is no method to off it by ourselves.If there are, they are indigenous to which countries?Where have they appeared?Or are they development phones?
Click to expand...
Click to collapse
Some rare cases are there where the phone is factory s-off.the security is absent by default in such handsets.

Steam. said:
Just asking, are there phones shipped with S-Off?As there is no method to off it by ourselves.If there are, they are indigenous to which countries?Where have they appeared?Or are they development phones?
Click to expand...
Click to collapse
Yeah, most of the cases is when the guy received the phone from HTC as a gift... we've seen-
GB ship s-off
PVT ship s-off
And one more I don't remember
Sent from my One V

After running all the commands successfully, it is still showing there is a file difference. Is there any other way to remove this red text while booting. Please please help somebody. I''m desperate to get rid of this.

>.> learn to read. This is only for s-off phones. If you had an older phone or an unupdated one x you would of just bricked all because you didn't read
Sent from my One V using Tapatalk 2

simonsimons34 said:
>.> learn to read. This is only for s-off phones. If you had an older phone or an unupdated one x you would of just bricked all because you didn't read
Sent from my One V using Tapatalk 2
Click to expand...
Click to collapse
I'm sure my One V is s-off, I've just done it few days back. I'm currently running on PA2.99, how can it be s-off, even I tried to copy the mmcblk0p18 file to the /dev/block folder manually with proper permission. Still no luck. Please help.

You are not soff. Final. Your unlocked. And you don't even know what your talking about at this point
Sent from my One V using Tapatalk 2