Develop Bugs

completely messed up my evo please help!!!!!

i decided that rooting my phone would be a great idea, so i got into it and looks as if the pc image was older than my current therefore it couldnt update or something idk even know. the radio_v2 it said fail-pu. when i tried to boot the phone up it gave me a red sign with an explantation point then i decided to clear storage and that didnt even work cuz the phone doesnt boot its frozen on the htc evo 4g screen, im currently downloading the stock pc image do i just put that into my sd card and down volume boot it? please help i just got the phone today and i already messed it up thank you!!!

stav816 said:
i decided that rooting my phone would be a great idea, so i got into it and looks as if the pc image was older than my current therefore it couldnt update or something idk even know. the radio_v2 it said fail-pu. when i tried to boot the phone up it gave me a red sign with an explantation point then i decided to clear storage and that didnt even work cuz the phone doesnt boot its frozen on the htc evo 4g screen, im currently downloading the stock pc image do i just put that into my sd card and down volume boot it? please help i just got the phone today and i already messed it up thank you!!!
Click to expand...
Click to collapse
Wrong forum, also, you just got it today... you shouldn't be rooting until you absolutely know what you're doing. I'd tell you how to fix it but I think you should read more. Good luck.

dude
AssassinsLament said:
Wrong forum, also, you just got it today... you shouldn't be rooting until you absolutely know what you're doing. I'd tell you how to fix it but I think you should read more. Good luck.
Click to expand...
Click to collapse
Wow thats cold!

AssassinsLament said:
Wrong forum, also, you just got it today... you shouldn't be rooting until you absolutely know what you're doing. I'd tell you how to fix it but I think you should read more. Good luck.
Click to expand...
Click to collapse
pls man ive been searching everywhere for a solution i honestly cant find a fix, and my friend convinced me to do it. i know i had no idea what i did but can u please guide me to resolve this? i need this phone in the morning and withoutsomeone helping me ill be stuck. please and thank you!

?
stav816 said:
i decided that rooting my phone would be a great idea, so i got into it and looks as if the pc image was older than my current therefore it couldnt update or something idk even know. the radio_v2 it said fail-pu. when i tried to boot the phone up it gave me a red sign with an explantation point then i decided to clear storage and that didnt even work cuz the phone doesnt boot its frozen on the htc evo 4g screen, im currently downloading the stock pc image do i just put that into my sd card and down volume boot it? please help i just got the phone today and i already messed it up thank you!!!
Click to expand...
Click to collapse
What did you use to root ur phone?

kevinniven said:
What did you use to root ur phone?
Click to expand...
Click to collapse
unrevoked is wat i used

AssassinsLament said:
Wrong forum, also, you just got it today... you shouldn't be rooting until you absolutely know what you're doing. I'd tell you how to fix it but I think you should read more. Good luck.
Click to expand...
Click to collapse
At least help the poor guy out... ;(
Too bad I cannot help you as I never rooted my phone with unrEVOked, I just did it manually by myself on my PC...luckily, I read carefully before proceeding.

Sounds like u used the like a boss edition 2.02 hboot root if so go to that forum to get the correct answer also try flashing a rom in recovery thats what that red traingle is u need to adb into the recovery look on the thread u find the root at this is wroung section u need q&a
sent from my white w/ red trim Evo

if i can do command prompts from my pc to my phone will i be able to flash the original software onto here?

Yes you will just adb your phone into recovery and should allow flashing a rom
sent from my white w/ red trim Evo

krazydude4g said:
Yes you will just adb your phone into recovery and should allow flashing a rom
sent from my white w/ red trim Evo
Click to expand...
Click to collapse
i actually cant, can anyone help me 4 hrs and no fixes!?

i just have to say this is why people should take time to READ instead of just attempting to root phones ....

stav816 said:
i actually cant, can anyone help me 4 hrs and no fixes!?
Click to expand...
Click to collapse
here ya go
http://forum.xda-developers.com/showthread.php?t=831915

First off is the stock pc36img.img on your root of your sdcard? If so pull the battery out, put it back in and hold down the power and vol down to boot in the bootloader. you should be fine once it installs you should be back with a stock rom. If you don't have the stock pc35img.img you can get it from here http://www.multiupload.com/U27BZXVWWI.
hope this helps

http://www.multiupload.com/U27BZXVWWI
Download that, rename it PC36IMG, put it on your SD card... reboot phone into recovery(while phone is OFF, press and hold volume down, while pressing the power button), it will load, follow onscreen instructions

Have you tried using an ruu. It should be able to return your phone to stock

u should goto the androidforum and read ROOTING FOR DUMMIES thread! u will not f up your ph and it will take u 15 mins to root yah ph give or take a few!
Sent from my PC36100 using XDA App

Sounds like you used an incorrect method to root. Follow the hboot 2.02 S-OFF like a boss thread in this forum. It will have every answer you need.
Sent from my PC36100 using XDA App

AssassinsLament said:
Wrong forum, also, you just got it today... you shouldn't be rooting until you absolutely know what you're doing. I'd tell you how to fix it but I think you should read more. Good luck.
Click to expand...
Click to collapse
ouch...that hurt. but, it made me laugh., but u aint right
stav816 said:
i actually cant, can anyone help me 4 hrs and no fixes!?
Click to expand...
Click to collapse
why cant u use adb??
CheesyNutz said:
i just have to say this is why people should take time to READ instead of just attempting to root phones ....
Click to expand...
Click to collapse
cheesynutz, ur all over the forum with some great informative insight. y-all need to listen to this guy, he appears to be very wise.
Rem3Dy said:
Sounds like you used an incorrect method to root. Follow the hboot 2.02 S-OFF like a boss thread in this forum. It will have every answer you need.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
werd....thats exactly what u need. u follow the "like a boss" thread, n u can be a boss like ricky ross!!

Froyo SBF and Bootloader for Flipside MB508 AT&T USA

Froyo SBF and Bootloader for Flipside MB508 AT&T USA
Bootloader: BL_917B_4G_sageemu_Consumer_replacer.zip
Download BL_917B_4G_sageemu_Consumer_replacer.zip for free on Filesonic.com
SBF Flash :
Android 2.2.2 ------ Blur_Version.2.159.17.MB508.ATT.en.US
SAGE_U3_3.4.2-159.17_SecATT_SIGNATT_USASAGE02B25ND0ATTNA02E.0R_S AGEFRATT_P011_HWp4_1FF.sbf.gz
Download SAGE_U3_3.4.2-159.17_SecATT_SIGNATT_USASAGE02B25ND0ATTNA02E.0R_S AGEFRATT_P011_HWp4_1FF.sbf.gz for free on Filesonic.com
WARNING: ONCE YOU FLASH THE FROYO SBF ANY ATTEMPT TO DOWNGRADE TO ECLAIR MIGHT RESULT IN A HARD BRICK !!!!!
These files are made available as a general courtesy and I assume no responsibilty for your own actions.

Thanks, I was just looking for this.. I did an update from eclair to froyo (2.1 - 2.2) and everything was fine until I did a hard reset and lost service and it kept crashing each time I would go into the settings and wireless/APN options. Wouldn't take ATT and TM sim cards.. Going to try flashing the SBF and see if this resolves it.
Edit: aaand, flashed and all fixed.

Great find, nice to have an option in case we screw something up. I wonder if there's any benefit to flashing the 2.2 sbf instead of flashing a clean 2.1 and updating to 2.2...

OH I HOPE THIS FIXES MY FREEZING ISSUE!!! Im so sick of having to take out the battery 10 or more times a day when this thing freezes, plus Im sure it does damage as hard shutting down a computer does. Ill let everyone know.
How would I flash the bootloader?

pre4speed said:
OH I HOPE THIS FIXES MY FREEZING ISSUE!!! Im so sick of having to take out the battery 10 or more times a day when this thing freezes, plus Im sure it does damage as hard shutting down a computer does. Ill let everyone know.
How would I flash the bootloader?
Click to expand...
Click to collapse
Ya know what...i'm not really sure how to flash it...or why it would be needed as opposed to a regular bootloader...

Got it flashed. Same way as you flash a rom. Like you tho, I havent a clue why. I also flashed the rom. Did NOT help with freezing, in fact seems worse now. Cant use my phone for more than 3-4 minutes before it freezes. Any idea who Id contact at Motorola to get assistance with this, because this is ridiculous. Thanks for posting this.

pre4speed said:
Got it flashed. Same way as you flash a rom. Like you tho, I havent a clue why. I also flashed the rom. Did NOT help with freezing, in fact seems worse now. Cant use my phone for more than 3-4 minutes before it freezes. Any idea who Id contact at Motorola to get assistance with this, because this is ridiculous. Thanks for posting this.
Click to expand...
Click to collapse
Hey check your SD card. My phone wasn't just freezing....it would completely just reboot and stay on the moto screen. I found out that i was my memory card. When I removed it, it worked fine and when I put it back in, it shut down automatically. Found out the problem was the 2nd partition I to use the link2sd...had to change it so that the 2nd partition was set to primary and its been working fine ever since. Not one single freeze or anything.
Dunno if that is going on with you but if it is I hope this helps

How do I set the second partition as primary? I've noticed also when anything gets linked, it goes to the first partition. First partition mem goes down, whereas second stays the same.
Sent from my MB508 using XDA App

I use something called 'EASEUS Partition Master 8.0.1 Home Edition' that I think I downloaded on google (I don't remember) but you can use it to change create and format partitions and you just gotta make sure you set it to 'primary' and not 'logical'. Try to see if you can find it and do it and let me know. If you can't find it let me know and I'll see if I can send you mine. And if you do and you still have trouble, detail to me what is going on and i'll walk you through it. It took me a lil while to figure it out.

So I could use minitool partition as well? That's the one I have. I will try that out. Phone hasn't froze today for a long time, but now that I said that, well you know. Lol I will keep you updated for sure. Thanks.
Sent from my MB508 using XDA App

Yep, that will work just fine.

JBallin4life27 said:
Ya know what...i'm not really sure how to flash it...or why it would be needed as opposed to a regular bootloader...
Click to expand...
Click to collapse
Found out why the need for the updated bootloader. Froyo does not support the Eclair version of the bootloader, so if you need to flash again, you would not be able to unless you update the bootloader. HTH

I'm honestly kinda a noob at this... never messed with anything like a bootloader. Can somebody explain to me how to do this? I'm wanting to flash back to a clean 2.2 and the post before mine sounds like that might be bad without updating boot loader first.
Also the rom, just install it with RSD?

boazjuggalo said:
I'm honestly kinda a noob at this... never messed with anything like a bootloader. Can somebody explain to me how to do this? I'm wanting to flash back to a clean 2.2 and the post before mine sounds like that might be bad without updating boot loader first.
Also the rom, just install it with RSD?
Click to expand...
Click to collapse
You will flash the bootloader the same as the froyo rom in RSD. Do the bootloader first. Then flash the froyo rom. Any questions, don't hesitate.
Sent from my MB508 using XDA App

pre4speed said:
You will flash the bootloader the same as the froyo rom in RSD. Do the bootloader first. Then flash the froyo rom. Any questions, don't hesitate.
Sent from my MB508 using XDA App
Click to expand...
Click to collapse
Phone fully on or update mode or what? For both?
USB Debugging on?
Version of RSD need to be up or still using 4.9?

I'm not 100% of this, as I don't have the MB508 as of the moment, but I believe once you flash the stock 2.2 rom or OTA you will loose root.
Someone correct me if I'm wrong, this is just intended for those who want to know info.

boazjuggalo said:
Phone fully on or update mode or what? For both?
USB Debugging on?
Version of RSD need to be up or still using 4.9?
Click to expand...
Click to collapse
When you flash you will need to go into bootloader mode. Power off phone, the use the proper key funtion (sorry don't remember what it is) to start bootloader. Then flash updated bootloader. When flashing via RSD, it doesn't matter about usb debugging because you aren't fully booted into the phone. I used version 4.9 and had no problems flashing both. Good luck.
Sent from my MB508 using XDA App

kaijura said:
I'm not 100% of this, as I don't have the MB508 as of the moment, but I believe once you flash the stock 2.2 rom or OTA you will loose root.
Someone correct me if I'm wrong, this is just intended for those who want to know info.
Click to expand...
Click to collapse
Yes this is correct. I belive this is the case anytime you flash using RSD. You can gain root again after using the most current version of superoneclick.
Sent from my MB508 using XDA App

This, along with a link to RSD Lite to install it, needs to be stickied! I was trying to upgrade a friend's Flipside following the directions on Motorola's website and it bricked the device. flashing the sbf file saved the day!

links death
any one can reupload the files?
the links are no more alive

Is it easy/hard to brick the Galaxy?

Hi,
1. For a month ago i've learned how to root my galaxy s2, and since then i've flashed new ROM's and kernels almost every week, and thats because almost everyone told me that it was almost impossible to brick the phone.
In 2 days i will recive my new Galaxy Nexus, and i don't know if i will Root it or not, is it worth doing this to this phone?
thanks

People say it's almost impossible.. Just search the threads where people think they bricked their phones

It is EXTREMELY hard to brick the Galaxy Nexus.
And it is definitely worth rooting. There are some amazing ROMs and kernels available

Learning to root and use android from scratch, I bricked this fella at least six times, but mostly due to bad file transfers and user error.
Use a toolkit, wugfresh's makes it excessivlely easy.
Sent from my Galaxy Nexus using xda premium

I did not wipe data out before flashing, my phone could not start. I thought i bricked my phone but after went to recovery mode to wipe data, my phone worked fine.

As far as I know, the only time that you can brick this phone is when flashing bootloaders. For example, the lights go out during the 2 secs required to flash it. But the window of opportunity is so small you have to really be unlucky, and if you have UPS or do it on a laptop, that won't be a problem at all. The more probable scenario is flashing a corrupted image of the bootloader (that's what md5 checksums are for) or, god forbid, a bootloader for a completely different device (that's what intelligence is for). Besides, you shouldn't be flashing bootloaders all the time. Maybe once every time a new version of ICS comes out.

TwilightSparkle said:
I bricked this fella at least six times
Click to expand...
Click to collapse
So what you really mean, is that you didn't actually brick it once?

Lol - interesting thread...
I'll bet that I can brick one in a few minutes, so it can't be that hard... xD

I was under the impression that bricking can also occur by mismatching radios/kernels/roms, not just the wrong bootloader. Like using a 4.0.2 version of one with a 4.0.3 version of another, for instance. I want to upgrade from 4.0.2 to 0.3 or 0.4 but I'm not sure of the correct order of updating everything, since I've customized all of them. Unless I'm just mistaken altogether...

thirtynation said:
I was under the impression that bricking can also occur by mismatching radios/kernels/roms, not just the wrong bootloader. Like using a 4.0.2 version of one with a 4.0.3 version of another, for instance. I want to upgrade from 4.0.2 to 0.3 or 0.4 but I'm not sure of the correct order of updating everything, since I've customized all of them. Unless I'm just mistaken altogether...
Click to expand...
Click to collapse
No. As long as your volume button and power button are not broken, you can start into the bootloader and start over.
Bricking is a very final thing that one can not repeat on the same device. Once bricked, it's only good as a paperweight. If you can revive the device, then it was never bricked in the first place

Wrong radio will brick your device for certain. Kernel and ROM not so much...

danger-rat said:
Wrong radio will brick your device for certain. Kernel and ROM not so much...
Click to expand...
Click to collapse
I thought CWM just gives an error and doesn't complete the flash in that scenario, no..?

danger-rat said:
Wrong radio will brick your device for certain. Kernel and ROM not so much...
Click to expand...
Click to collapse
I thought I remembered reading that in some /r/android comments a few months ago. Thanks for confirming.
So since I'm on 4.0.2 running the leaked 4.0.3 radios, if I wanted to run 4.0.4 everything would you recommend just reverting back to pure stock 4.0.2 via this thread or similar method, and then going from there?

Vangelis13 said:
I thought CWM just gives an error and doesn't complete the flash in that scenario, no..?
Click to expand...
Click to collapse
Not confirmed with this phone, but typically the bootloader will do an md5 type check, but recovery doesn't. If you disable signature verification in recovery, then it's all in your hands...

j.go said:
[snip]
The more probable scenario is flashing a corrupted image of the bootloader (that's what md5 checksums are for) or, god forbid, a bootloader for a completely different device (that's what intelligence is for). Besides, you shouldn't be flashing bootloaders all the time. Maybe once every time a new version of ICS comes out.
Click to expand...
Click to collapse
Not sure if the bootloader flow is the same on the Galaxy Nexus (probably not), but on the Nexus One, the bootloader will not flash a bootloader that is not signed. Period. Unless of course there is no NAND lock (i.e., S-OFF for HTC devices).

Afaik,you have to screw up fast boot to truly brick the device. Not even messed up boot loaders will brick it. You can always go to fastboot and factory restore.
Sent from my Galaxy Nexus

psycho2097 said:
Afaik,you have to screw up fast boot to truly brick the device. Not even messed up boot loaders will brick it. You can always go to fastboot and factory restore.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Dare you to flashable radio from another phone...

danger-rat said:
Dare you to flashable radio from another phone...
Click to expand...
Click to collapse
LOL!!!!!
Sent from my Galaxy Nexus using Tapatalk

I Dare y'all to flash the 4.0.4 update on a GSM phone. ;P
Sent from my Galaxy Nexus using xda premium

Following the wiki guide to return to stock ROM for warranty repair?

OK, I have found the wiki guide to return a phone to stock condition for warranty repair (part of the screen can't touch). I have a few questions...
You need to have radio S-OFF to follow this steps
Click to expand...
Click to collapse
How do I do this?
Please make sure that gfree_verify returns secu_flag = 0 before following this steps!!!
Click to expand...
Click to collapse
Huh?!?
If you main software version is higher than the version of the PC10IMG you want to install (in this case 1.19.531.1) you have to change the main version number in the misc partition.
Click to expand...
Click to collapse
What's the main software version? What's PC10IMG?
In case of the original T-Mobile G2 the stock rom is called PC10IMG_Vision_TMOUS_1.19.531.1_Radio_12.21.60.09b_26.02.01.15_M2_release_149459_signed.zip
Click to expand...
Click to collapse
I have a Desire Z bought from Hong Kong. I suppose I will use:
RUU_Vision_hTC_Asia_HK_CHT_1.84.708.1_Radio_12.28e.60.140f_26.04.02.17_M2_SF_release_168263_signed.exe
as
RUU_Vision_hTC_Asia_HK_CHT_1.34.708.3_Radio_12.28b.60.140e_26.03.02.18_M2_release_154602_signed.exe
is corrupt and won't execute?
Restore the backup of your partition 7.
Click to expand...
Click to collapse
What's partition 7? What does the file look like?
Geez, this guide sure is technical...there is a whole lot more there. It reads like it was written by an expert, as a sort of hand notes for what he did so he can follow it again later. It sure doesn't read like a easy-to-follow guide for novices like me.

well to start you were wondering if you have soff? did you root your phone yourself? do you know what guide you used? most of these steps are just reversed from optaining root and soff
you may want to boot into your bootloader (power on while holding volume down) and check your phone
nipqer also has a guide to follow, search the dev section for that, not @ a computer so can't easily link it to you right now but it is called something like "return to stock with broken digitizer) of course it will work even if your touch screen is fine
Sent from my HTC Vision using xda premium

Help
Some one should please help me. I gave my friend my HTC G2 for a research work. Some days later, he returned it to me pleading that i should forgive him. He mistakenly deleted my G2's Operating System and every other thing in it. Right now the phone is just blank. It boots up to the bootloader and displays the HTC Logo. Please, I am begging for any body with any solution to this. PLEASE I URGENTLY NEED YOUR HELP. THANKS

Were you rooted prior to this? Do you know what was done to make this happen? Can you boot to bootloader at all?
See if this helps at all
http://forum.xda-developers.com/showthread.php?p=33917375
Sent from my SGH-T839 using Tapatalk 2

Help
demkantor said:
Were you rooted prior to this? Do you know what was done to make this happen? Can you boot to bootloader at all?
See if this helps at all
http://forum.xda-developers.com/showthread.php?p=33917375
Sent from my SGH-T839 using Tapatalk 2
Click to expand...
Click to collapse
Yes I can boot to bootloader and the phone was rooted prior to the deleting stuff. It was rooted with super one click. When I opened my sd card, I saw Superwipe+4ext. When I confronted him yesterday, he said he just downloaded the stuff but didn't use it. I suspect he used that Superwipe+4ext to wipe out my phone because when I went online to read about this software, I was convinced that he used it. Thanks

The superwipe is safe to use, can you still boot to recovery?
Sent from my Nexus 7 using xda premium

Help
Yes I can boot to recovery.

Then flash a new rom
Sent from my Nexus 7 using xda premium

OK what? Urch make your own topic. Dont rob other's topics....
gromky, tell us about your phone: Is it rooted? Is it S-OFF? Do you know anything about your phone at all?

Damn...just made a huge mistake. phone bricked?

My son wanted to root his brand new phone. i have rooted 8 phones from different phones before with success..... but this time i f***d up...
Accedently installed this on his phone.
http://wccftech.com/flash-and-root-nexus-5-on-android-6-0-1-mmb29k/
executed flash-all.bat and it flashed the bootloader.
For the wrong phone...
It should have been this one..
http://wccftech.com/flash-and-root-nexus-5x-android-6-0-1/
Missed the X......
Now the phone will not even boot any more at all....cant enter bootloader.......does not power up at all.!!!
Jesus...what have i done.......
It here any chance at all to fix this somehow?

Hello and thank you for using Q/A,
because you can't enter bootloader, you can't do anything. You can try to send the phone to Google. Say: It didn't boot after OTA Update.
Kind regards
Trafalgar Square

Yeah it's most likely a paperweight. Try sending it to Google. Flashing the wrong firmware destroys a phone as you probably already know

well
hopesrequiem said:
Yeah it's most likely a paperweight. Try sending it to Google. Flashing the wrong firmware destroys a phone as you probably already know
Click to expand...
Click to collapse
I am totally aware of that....
but somehow one must be able to flash the bootloader from scratch....
Normally via special software etc.
That´s what i was hoping for....

Only thing I know to use is a riff box to jtag it. Not sure if they have one for 5x.

crowhater said:
I am totally aware of that....
but somehow one must be able to flash the bootloader from scratch....
Normally via special software etc.
That´s what i was hoping for....
Click to expand...
Click to collapse
Your use of the period seems rather condescending. And no, you as the end user cannot fix that. You did one of the few things that is unrecoverable unless you manage to get the bootloader to accept adb commands somehow.

crowhater said:
I am totally aware of that....
but somehow one must be able to flash the bootloader from scratch....
Normally via special software etc.
That´s what i was hoping for....
Click to expand...
Click to collapse
Didn't you say the phone won't turn on? The above scenario is not possible.

Well
bobby janow said:
Didn't you say the phone won't turn on? The above scenario is not possible.
Click to expand...
Click to collapse
Well. the bootloader is flashed into the phone from the beginning aswell during manufacturing. I work with electronics and software and i know there is always a way to reflash the bootloader. All the electronics comes in the beginning with no software at all, one only needs the proper software/hardware. Most probably by jtag....or if they have some other special tool for snapdragon 808.
Stupid of me not to see that the version i flashed was not for nexus 5X...and only for nexus 5
sight...

Good luck. Will Google not rma it?