Related
Ok, so I was trying to get my Evo running on the Verizon network, and ended up messing with some NV items that I probably shouldn't have. Long story short it's stuck in a boot loop. I can get to the bootloader just fine, but recovery is a no-go. Also, I was able to do an RUU flash from fastboot, but that didn't fix the boot loop. What should I do?! Please help me!
Sounds like you took a big step and should not have. Next why would you want to go to Verizon? you can not use 4g over there. i think there is a post here or on another android site on getting your phone out of a boot loop with no recovery. Search is your friend
http://lmgtfy.com/?q=stuck+in+boot+loop+without+recovery+android+evo
I found a solution to this exact problem.
Flintr said:
Ok, so I was trying to get my Evo running on the Verizon network, and ended up messing with some NV items that I probably shouldn't have. Long story short it's stuck in a boot loop. I can get to the bootloader just fine, but recovery is a no-go. Also, I was able to do an RUU flash from fastboot, but that didn't fix the boot loop. What should I do?! Please help me!
Click to expand...
Click to collapse
I found a solution to this exact problem after I wrote some nv items from a boost phone. no recovery, evo 4g boot loop over and over till the battery dies and only fastboot commands work. dont even think about saying flashing the boot or system images to fix this thats a no no, it will not work although it wont break the phone either. If anyone is in this same awful position and cant find a fix just pm me or reply to this post and i'll write a full tutorial of what i did. I just dont wanna waste my time and there might be an answer out there already. All i know is that I could'nt find one anywhere and I am literally a part of every mobile forum you can think of. Anyone interested?
marley183rd said:
I found a solution to this exact problem after I wrote some nv items from a boost phone. no recovery, evo 4g boot loop over and over till the battery dies and only fastboot commands work. dont even think about saying flashing the boot or system images to fix this thats a no no, it will not work although it wont break the phone either. If anyone is in this same awful position and cant find a fix just pm me or reply to this post and i'll write a full tutorial of what i did. I just dont wanna waste my time and there might be an answer out there already. All i know is that I could'nt find one anywhere and I am literally a part of every mobile forum you can think of. Anyone interested?
Click to expand...
Click to collapse
i REALLY COULD USE YOUR HELP
need help
I have the same problem, i used a tp2 as a donor, everytihng qorked but data, after copying the needed nv items(CDMA WS 2.7) and still didnt work i copied ALL available items from tp2 to the evo OOOOUCH , now i am at the endless boot loops , the only thing working is fastboot but not adb. i flash all types of roms with no luck, please tell us what you did to get it back running, you help will be appriciated
Need help
I have the same problem, i used a tp2 as a donor, everytihng qorked but data, after copying the needed nv items(CDMA WS 2.7) and still didnt work i copied ALL available items from tp2 to the evo OOOOUCH , now i am at the endless boot loops , the only thing working is fastboot but not adb. i flash all types of roms with no luck, please tell us what you did to get it back running, you help will be appriciated
Please refer to the post below for a fix. This will in no way help you if you started having reboots and then a bootloop while running CM7. It is meant to fix issues that come from corrupted NV items only.
http://forum.xda-developers.com/showpost.php?p=16133086&postcount=54
I am experiencing the boot loop issue also. Really weird, all I have done is root via UnRevoked, use Rom Manager to install CM 6.1.2, and been running this ROM exclusively. I have never overclocked, or even installed or used any task killers in CM 6... I started noticing a couple weeks ago some odd force closes and sync issues with gmail that would come and go. Then, my phone would reboot every once in a while. Sometimes when I was using it, most of the time while it was just sitting on the counter. Then one day it just started the boot loop. Vibrate, white HTC Evo screen for a few seconds, then dark again, over and over. I can't boot into recovery, and have tried a bunch of recovery images (they unpack and update succeeds but attempting to boot to recovery just starts the loop again). I thought about unrooting and bringing the phone back to the store but the instructions I found for unrooting require me to at least get into recovery.... At the time I rooted (Sept '10) I had all the latest OTA... any advice for me to try?
S-OFF
HBOOT-2.10.0001
RADIO 2.15.00.11.19
I made a writeup
Please refer to the post below for a fix. This will in no way help you if you started having reboots and then a bootloop while running CM7. It is meant to fix issues that come from corrupted NV items only.
http://forum.xda-developers.com/showpost.php?p=16133086&postcount=54needed files.
Update
So I never could fix this issue, although I got some really great suggestions and learned a lot from cutthroatamft.
Ended up just deciding to completely brick the phone (in case the Sprint tech might check my bootloader screen for S-OFF). To do this, I just removed the battery while I was flashing an engineering image (while it was updating the radio). After that, not only would the phone not power on at all, but the charging LED wouldn't even light up when plugged in to a power source. They gave me a refurbed Evo.
Haha, I was able to fix my Evo (dont remember what I did) but I have since sold it.
dwreck_ said:
So I never could fix this issue, although I got some really great suggestions and learned a lot from cutthroatamft.
Ended up just deciding to completely brick the phone (in case the Sprint tech might check my bootloader screen for S-OFF). To do this, I just removed the battery while I was flashing an engineering image (while it was updating the radio). After that, not only would the phone not power on at all, but the charging LED wouldn't even light up when plugged in to a power source. They gave me a refurbed Evo.
Click to expand...
Click to collapse
Do you mind pointing me to the image you flashed? I just pulled the battery while flashing a radio, but i'm still booting haha.
You should find it fairly easy if you search Google for eng-pc36img.zip
Looks like the first link.
Sent from my Evo using XDA App
I wish I could, but honestly it's been so long that I dont have any idea.
Thanks cutthroat.
dwreck, at what point did you pull?
I've pulled it twice while it was updating Radio_V2, with the red bar about 1/3 of the way, and nothing about my phone seems to change.
Did you pull a little later? Or did you pull during Radio_Cust? That thing is hard to catch, it updates quickly.
My friend says it took him about a hundred times to fully brick his Evo. Just keep trying I suppose.
Sent from my Evo using XDA App
Sprint was backordered on Evo's. It might take me more than a week to get another one, and it's still 35 bucks. Cutthroat or dwreck, do either of you guys know if it would be safe for me to send my Evo into HTC? I did the battery pull (it took about 20 tries) and the phone doesn't turn on, no led or anything. Will htc know it's rooted regardless?
You should be fine to send it to HTC, my friend has gotten two replaced that exact way. He had no issues with them finding out his were rooted.
Sent from my Evo using XDA App
pthr3e said:
i REALLY COULD USE YOUR HELP
Click to expand...
Click to collapse
Please refer to the post below for a fix. This will in no way help you if you started having reboots and then a bootloop while running CM7. It is meant to fix issues that come from corrupted NV items only.
http://forum.xda-developers.com/showpost.php?p=16133086&postcount=54
I'd just like to take a sec to give props to cutthroat. His guide is GREAT if you've screwed up your NV files (unfortunately that wasn't my problem). Anyways I appreciate you helping me out even after that.
Hey guys, I tried to perma root my wife's G2 last night using Visionary+ r14 but when it tried to reboot it doesn't get past the green and white "HTC" screen, so now I have a couple of questions.
I bought this phone from someone off of Craigslist and it was working great until I tried to root it so it is technically out of warranty do you think I can get it replaced since everything is still stock?
Also I tried to apply the HTC OTA update to fix it and I still have the problem, is there anything I can do to repair this phone? Thanks in advance guys and mahalo!
Okay pull your battery out and put it back in..after dat press power button and volume down button until you get to the recovery screen and do a factory reset..
Sent from my HTC Vision using XDA App
Thanks for the reply jboiii15. I did a factory reset before I flashed the OTA update and I have factory reset several times but still no go. I appreciate you taking the time to help me out.
Did you try this? http://forum.xda-developers.com/showthread.php?t=842495
aznsnake666 said:
Did you try this? http://forum.xda-developers.com/showthread.php?t=842495
Click to expand...
Click to collapse
I haven't tried it because I can't get ADB to work with the phone the way it is, Fastboot works but ADB just shows nothing there while I'm in recovery or the boot screen. Thank you also for the reply. My wife is pissed lol.
Try to extract the ROM from the official RUU and rename it to PC10IMG.zip. Put this on the root of your SD card and boot into bootloader and leave it to work. This should solve your problem Fingers Crossed
JD
do you have s-off??
I don't have S-OFF as I just started the rooting procedure when it decided to take a dump on me, after this I don't think my wife will want me to root any more of her phones although I know she'll miss it after having a rooted G1 running CM and a rooted Slide running Chromatic. Good thing I didn't sell her Slide yet lol.
I'll try to find information on the PC10IMG.zip method now and see what can be done.
Thank you guys for all the help, I really appreciate it all.
itsmekeoni said:
I don't have S-OFF as I just started the rooting procedure when it decided to take a dump on me, after this I don't think my wife will want me to root any more of her phones although I know she'll miss it after having a rooted G1 running CM and a rooted Slide running Chromatic. Good thing I didn't sell her Slide yet lol.
I'll try to find information on the PC10IMG.zip method now and see what can be done.
Thank you guys for all the help, I really appreciate it all.
Click to expand...
Click to collapse
I think the rooting process has corrupted your kernel or rom, it is rare to get a brick from just the visionary process, but i know there has at least been one that this has happened to.
Report back to tell us if the extracted ROM worked for you, there is still hope;')
JD
Oh man this is just getting worse lol. I had the phone sitting here plugged into my laptop while the phone was in the Hboot screen where you can select Fastboot, Recovery and so on. All of a sudden my here Windows give off the noise as if something was connected or disconnected from my computer and I see the screen shut off on the G2 with a red light blinking. Now the phone doesn't power on and the red light blinks while the phone is plugged into the computer but doesn't power on.
As I was typing this the red light came on solid as if it is charging now, maybe it doesn't charge while in that screen and the battery just died I dunno, strange.
JupiterDroid said:
I think the rooting process has corrupted your kernel or rom, it is rare to get a brick from just the visionary process, but i know there has at least been one that this has happened to.
Report back to tell us if the extracted ROM worked for you, there is still hope;')
JD
Click to expand...
Click to collapse
Well I called T-Mobile and they are sending out a new phone, I'm unsure if I should still mess with it or not. I did flash the TMOUSA OTA update and that didn't help, I didn't unpack it to see if it contained a new Kernel but I'm sure it had a new system.img, still think it is one of those that is messed up?
I'm having a hard time finding the things to get the PC10IMG.zip going, work is calling me in different directions and my A.D.D is kicking in lol.
try this http://forum.xda-developers.com/showthread.php?t=855764 i had the same problem like you, steviewevie told me to do it, if you have problem to connect your g2 with sdk download pda net, it works for me and now i have my g2 back with the new root... just do what it said on that link believe me works...
P.D. I am a androidnoober always have a iphone and this was my first time using sdk adb or whatever name is and I did it
Thanks AndroidNoober, I've seen that link in my search for an answer to my problem. One of the issues that is making this harder is that after the phone "bricked" it lost ADB connectivity. I've tried it on two computers that have a properly working ADB (I test it with my N1 and 3G Slide) and it used to work with the G2 but now I can't get it to see the phone, I've heard Recovery has ADB blocked.
semi bricked attempting permaroot
i attempted permaroot and semi bricked my phone. will not boot past htc screen. i can't get adb to work. i am trying to get pdanet installed but it keeps getting stuck on installing on phone. can it install while phone is in recovery mode? i have had no sucess trying to figure this out on my own and phone is not covered with a warranty
i have gotten the phone to read an update.zip file.
it is reading the pc10img.zip as well.
now i just have to get past the htc screen.
i do have s-on as i had just started the process.
any help would be appreciated
yup im deff. bricked i went to install the new synergy and i went to boot phone and it just sticks at white htc evo screen i have tryed to install a new pc36img and it installed then i went to recovery and it still gets stuck at the white htc evo screen and just loops so yea im deff bricked lol i know they say if you can get into hboot then your not bricked but hmmm plz help
well not enough info to help but...can you get into recovery...if so try a full wipe and flash a simple and easy stable rom ...say like fresh 4
Ur not bricked if ur phone powers on. Boot to recovery, do a full wipe, and flash a stock rom n c how that goes
Sent From My Pocket
You're not bricked, I've had this happen before. Back up all your meaningful files to your desktop, go into recovery and format your sd card, do it a couple times, then find a PC36IMG zip and put it on your sd card. Try to find a rooted rom if not, you'll have to re-root your phone. I used a 2.2 rom for an easy root with Unrevoked, then started back flashing. Good luck. Its normal for it to sit on the white screen for up to 5 minutes.
Sent from my PC36100 using XDA App
i cant get into recovery when i try from bootloader it just brings the htc screen back up and then stays on that for a few then screen turns black and then the white htc evo screen lol sooo im lost i have tryed to install the pc36img and it asked me to update and i said yes and then hit recoveryand still nothing
Try running an ruu in exe form from your computer.
Sent from my PC36100 using Tapatalk
how would i do that im not familiar with adb all that well sorry guys
You don't need adb. Download the newest ruu. Its a program run on your pc. It will wipe and replace everything. Its pretty much what htc would use to reflash a phone
We're comin from a pure power source.
to be honest I would surf through this section and General since everyone who phone gets stuck on the white HTC Evo screen first goes its bricked. I think we use that term too loosely in here. I know your not the first person to have this happen to them and I know many others have come out of it. Its just that there are so many different methods. This is where knowing a little adb will help you. If not I suggest learning it quickly.
If you are still S-Off I would try and reflash a recovery preferably Amon and then see if you can get into recovery and you Caulkins format all zip. Hopefully you will be able to do those two functions and if I were you I would load up a stock rooted rom first... Good luck and dont yell bricked till it wont turn on anymore...lol
Evo S3vn said:
yup im deff. bricked i went to install the new synergy and i went to boot phone and it just sticks at white htc evo screen i have tryed to install a new pc36img and it installed then i went to recovery and it still gets stuck at the white htc evo screen and just loops so yea im deff bricked lol i know they say if you can get into hboot then your not bricked but hmmm plz help
Click to expand...
Click to collapse
you are not alone on this issue im currently stuck in the same bootloop and cant get into recovery also. i started the post in general yesterday. hopefully someone will come in and help us both soon.
odie145 said:
you are not alone on this issue im currently stuck in the same bootloop and cant get into recovery also. i started the post in general yesterday. hopefully someone will come in and help us both soon.
Click to expand...
Click to collapse
Yea but I read your post and aren't you looking for Mac fastboot files? If so try this link it has a zip for a Android Metro file I was trying to repair. There are a couple for Mac files in there adb-mac and fastbot-mac.
I will post this in your thread as well
do what playya said and flash amon_Ra recovery through hboot. try and get that back before you run a ruu. look in the dev section for the ra thread and follow the directions to manually flash it and see if it works. It may just be that you lost your recovery.
well i got it to boot but now it stays booted after i ran ruu and now it stays on for about 2 mins then shuts off hahah well i got a new one coming for free in a few days so im good guys ty
what ruu should i use for the evo the one i installed seems to freeze my phone after boot up and then reboots
Evo S3vn said:
what ruu should i use for the evo the one i installed seems to freeze my phone after boot up and then reboots
Click to expand...
Click to collapse
a little more info on the phone you have to use the right one for your radio and Hboot. I would just try and see if you still have s-off and flash a recovery and go from there... Or just say f-it and wait for new phone...
Long story short my friend gave me a T mobile HTC G2 because it didn't turn on. I opened the phone to find the part where the battery connects to the phone came off the mother board so i solder it back on put the phone back together and turned it on. It booted up normal and came to the lock screen nothing worked the touch wasn't responding so i push power button to turn screen off and then again to turn it back on and the screen worked. I tried guessing his pattern five time and it didnt work it asked me to sign in to my Google account when the screen came up the phone rebooted and it kept doing it every time i turned it on. So i looked on xda how to restore it tried it and im not sure if it restored or not but it strated boot looping. I tried the flashing the pc10img.zip from the root of the sd card it usually says something like version to new or to old or something it didn't work. My phone is not rooted and i don't think usb debugging is on. Any info you guys want just ask. What can i do? How can i fix it? Please help
I'm going to take a guess, that if the battery connection to the motherboard 'broke off', then it's possible you have other physical issues such as the ribbon cable connecting the screen/digitizer to the rest of the phone.
If it were me I would have sent the phone into HTC for hardware warranty (which you can't do now since you soldered it.).
Can you provide some specific information about the phone, can you get into the boot loader, and if so what exact information do you have there? (USB debugging would be easily turned on under system settings, if you can get into it via the screen).
kbeezie said:
I'm going to take a guess, that if the battery connection to the motherboard 'broke off', then it's possible you have other physical issues such as the ribbon cable connecting the screen/digitizer to the rest of the phone.
If it were me I would have sent the phone into HTC for hardware warranty (which you can't do now since you soldered it.).
Can you provide some specific information about the phone, can you get into the boot loader, and if so what exact information do you have there? (USB debugging would be easily turned on under system settings, if you can get into it via the screen).
Click to expand...
Click to collapse
Thanks for replying i don't think anything else is wrong with the phone all the cables were fine. To begin with warranty was already finished. "Yes", i can get into the boot loader/H boot. I can turn on usb debugging because the phone doesn't boot all the way in to android. When you say information what exactly are you looking for?
helstonrampersad said:
Thanks for replying i don't think anything else is wrong with the phone all the cables were fine. To begin with warranty was already finished. "Yes", i can get into the boot loader/H boot. I can turn on usb debugging because the phone doesn't boot all the way in to android. When you say information what exactly are you looking for?
Click to expand...
Click to collapse
Mainly the info that shows up on hboot, and which recovery you have (or 'had') so that might be able to advise some additional steps.
helstonrampersad said:
Long story short my friend gave me a T mobile HTC G2 because it didn't turn on. I opened the phone to find the part where the battery connects to the phone came off the mother board so i solder it back on put the phone back together and turned it on. It booted up normal and came to the lock screen nothing worked the touch wasn't responding so i push power button to turn screen off and then again to turn it back on and the screen worked. I tried guessing his pattern five time and it didnt work it asked me to sign in to my Google account when the screen came up the phone rebooted and it kept doing it every time i turned it on. So i looked on xda how to restore it tried it and im not sure if it restored or not but it strated boot looping. I tried the flashing the pc10img.zip from the root of the sd card it usually says something like version to new or to old or something it didn't work. My phone is not rooted and i don't think usb debugging is on. Any info you guys want just ask. What can i do? How can i fix it? Please help
Click to expand...
Click to collapse
when you first had the phone it won't boot right? but when you tried fixing the battery connection thingy (sorry I don't know whats it called )
it booted and ran again?
have you tried doing a factory reset?
Power button+volume rocker down (volume down button) to boot into bootloader mode then do a factory reset maybe that would work ?
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
OR
or sending the phone to HTC would help bud but you have to pay them for that if they get to fix it you got yourself a new toy!
kbeezie said:
Mainly the info that shows up on hboot, and which recovery you have (or 'had') so that might be able to advise some additional steps.
Click to expand...
Click to collapse
This is the boot loader screen that i see
VISION PVT SHIP S-ON
HBOOT-0.82.0000
MICROP-26.13.04.19_M
eMMC-boot
Apr 13 211, 14:51:54
Im pretty sure the phone was never rootded before
The Android Manual said:
when you first had the phone it won't boot right? but when you tried fixing the battery connection thingy (sorry I don't know whats it called )
it booted and ran again?
have you tried doing a factory reset?
Power button+volume rocker down (volume down button) to boot into bootloader mode then do a factory reset maybe that would work ?
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
OR
or sending the phone to HTC would help bud but you have to pay them for that if they get to fix it you got yourself a new toy!
Click to expand...
Click to collapse
Its ok im not certain of what its called either but just to be sure its the part where the battery touches and it has metal prongs like. As for trying to restore it, i already tried didnt work it boot loops when i try that.
I don;t know what to do
helstonrampersad said:
Its ok im not certain of what its called either but just to be sure its the part where the battery touches and it has metal prongs like. As for trying to restore it, i already tried didnt work it boot loops when i try that.
Click to expand...
Click to collapse
ryin
sorry bro I'm no dev so I don't know that much when you were tryin to flash the "stock rom" did you flash the one for the G2 or the Desire Z?
The Android Manual said:
ryin
sorry bro I'm no dev so I don't know that much when you were tryin to flash the "stock rom" did you flash the one for the G2 or the Desire Z?
Click to expand...
Click to collapse
I still appreciate your help bro and i was trying to flash the stock rom for the g2, i made sure of it.
helstonrampersad said:
I still appreciate your help bro and i was trying to flash the stock rom for the g2, i made sure of it.
Click to expand...
Click to collapse
Would probably have to stick to the original Stock RUU update since you're S-ON (would need S-OFF for any kind of custom recovery, kernel, unsigned packages, etc), so would have to use a signed full package from T-Mobile, I don't know much bout that because I usually have my phones rooted and away from stock as fast as I can.
What stock rom did you find before? links?
kbeezie said:
Would probably have to stick to the original Stock RUU update since you're S-ON (would need S-OFF for any kind of custom recovery, kernel, unsigned packages, etc), so would have to use a signed full package from T-Mobile, I don't know much bout that because I usually have my phones rooted and away from stock as fast as I can.
What stock rom did you find before? links?
Click to expand...
Click to collapse
http://shipped-roms.com/index.php?category=android&model=Vision
Thats is the above link i used and i used all the ones that start with "PC10" I rename them to PC10IMG.zip so the phone can recognize it and it did. The only problem is that after it tries to install is say something along the lines of version is older or newer since i tried multiple packages. One package was going through the process and after that it didn't do anything, it didnt say failed or reboot or anything like that. Ive been trying to fix this for like a week and a half now. Ive even flashed custom PC10IMG.zip to see if it could help but nothing the furthest ive gotten is the phone boots for like 2 seconds the screen is blurry and the shuts off and there is an orange light in top right that wasn't lighting up before. Here are the links for the custom packages
http://forum.xda-developers.com/showpost.php?p=10583834&postcount=33
http://forum.xda-developers.com/showpost.php?p=10966727&postcount=63
Cant thank you enough for helping me this is really frustrating
kbeezie said:
Would probably have to stick to the original Stock RUU update since you're S-ON (would need S-OFF for any kind of custom recovery, kernel, unsigned packages, etc), so would have to use a signed full package from T-Mobile, I don't know much bout that because I usually have my phones rooted and away from stock as fast as I can.
What stock rom did you find before? links?
Click to expand...
Click to collapse
If what i explained above is not what you were referring to then let me know your way
helstonrampersad said:
If what i explained above is not what you were referring to then let me know your way
Click to expand...
Click to collapse
You would have to much it to your exact carrier/phone, Just flashing whatever you get your hands on can be very very risky.
For example for me being on T-Mobile with a T-Mobile branded G2, I would grab PC10IMG_Vision_TMOUS_1.19.531.1_Radio_12.21.60.09b_26.02.01.15_M2_release_149459_signed.zip from http://forum.xda-developers.com/showthread.php?t=971109
(noting the *.15 is the original radio my device was shipped with, though I've upgraded to the newer *.19)
I of course have no intention to returning to complete stock, but it's usually the only course of action for most people stuck with S-ON (and then would look into exploiting/unlocking/rooting again from there).
kbeezie said:
You would have to much it to your exact carrier/phone, Just flashing whatever you get your hands on can be very very risky.
For example for me being on T-Mobile with a T-Mobile branded G2, I would grab PC10IMG_Vision_TMOUS_1.19.531.1_Radio_12.21.60.09b_26.02.01.15_M2_release_149459_signed.zip from http://forum.xda-developers.com/showthread.php?t=971109
(noting the *.15 is the original radio my device was shipped with, though I've upgraded to the newer *.19)
I of course have no intention to returning to complete stock, but it's usually the only course of action for most people stuck with S-ON (and then would look into exploiting/unlocking/rooting again from there).
Click to expand...
Click to collapse
I know it can be risky but im desperate for a fix. Ill try the package you linked. I download it and rename it to PC10IMG.zip? Ill get back after im done if you have any other suggestion please let me know.
kbeezie said:
You would have to much it to your exact carrier/phone, Just flashing whatever you get your hands on can be very very risky.
For example for me being on T-Mobile with a T-Mobile branded G2, I would grab PC10IMG_Vision_TMOUS_1.19.531.1_Radio_12.21.60.09b_26.02.01.15_M2_release_149459_signed.zip from http://forum.xda-developers.com/showthread.php?t=971109
(noting the *.15 is the original radio my device was shipped with, though I've upgraded to the newer *.19)
I of course have no intention to returning to complete stock, but it's usually the only course of action for most people stuck with S-ON (and then would look into exploiting/unlocking/rooting again from there).
Click to expand...
Click to collapse
Im confused on which one to flash I have a T-Mobile HTC G2 which one will i flash?
choose the latest one for the g2, reading your thread I feel you will have little luck with this. try logging onto freenode #g2root, you'll get real time help here
Sent from my HTC Vision using xda premium
demkantor said:
choose the latest one for the g2, reading your thread I feel you will have little luck with this. try logging onto freenode #g2root, you'll get real time help here
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
I am new to XDA how can i do that?
helstonrampersad said:
I am new to XDA how can i do that?
Click to expand...
Click to collapse
I'm new so I can't post links, but copy and paste this url: http://webchat.freenode.net/?channels=g2root
EDIT - Oh, I can post links.
eboy_gb said:
I'm new so I can't post links, but copy and paste this url: http://webchat.freenode.net/?channels=g2root
EDIT - Oh, I can post links.
Click to expand...
Click to collapse
Though ideally using an actual IRC client will work much nicer than a web chat one.
Same problem, but desire z S-ON
Hey guys.
I have the same problem with the boot loop /semi brick. Expect I never had any problem before, with the phone. I have tried taking out the sd card, starting it agian. I have tried without simcard. I have tried to flash the ROM with RUU_Vision_Gingerbread_S_HTC_WWE_2.42.405.2_Radio_12.56.60.25_26.10.04.03_M_release_199043_signed
via Hboot Fastboot USB PLUG mode (which was the only mode the aplication was progressing in until it want to restart the phone in bootloader), but the phone frezzes and the aplication on the computer just keep working, without progress.
The factory reset just frezzes the phone.
The only thing reali seem to not frezze the phone is the revocery option. Here the phone react with restart showing a image of a phone with two green arrows bent around, over the phone. then it turns off the display and vibrate 4-5 times, og stays turn off not reacting to anything other then taking out the battery and you can start the phone once again.
VISION PVT SHIP S-ON
HBOOT-0.85.0013
MICROP-26.10.04.19_M
eMMC-boot
Apr 11 2011, 23:36:27
Have no idea but the version of android. I know that usb debugging is NOT on Any hjelp is a big help. I'm a noob, And I have been searching for 3 days for a solution, so I just hope you can help my, otherwise it is going for a repair at the place I bought it.
Thanks
This thread is here to inform people that if they try to flash anything through rom tools of any type they might "brick" or "soft brick" their phone or have a bootloader loop with samsung logo as I do. As of right now I am working on unsoftbricking my phone because I tryed flashing fonts and a bootloading screen. While the chance there is that it will softbrick vs flashing successfully.since I had several flash fonts go off without a problem and just never stuck, I assumed everything was ok. After deleting my current rom and going back to my stock rom i thought back at what steps i took to arrive at my bootloader loop it was after a few apps I downloaded from the market.Oden Flasher (not saying in anyway that was the cause) was one of them (blue android with black lighting down the middle). Now I am unsure if this is the "root" cause (pun intended, for those that think im talking about root access im not its just a joke). I am tyring to load a stock rom ATM via "Samsung Galaxy S3 ToolKit v2.3.0". So far no luck and it still stays at the samsung screen. I can get into Odin mode and get into recovery mode. when i try to manually load a rom i get e: signature verification failed and it aborts install. the only answer i have found was from an s2 device to basically create and load a temp recovery made by adb programing. I beleive i can do it but i havent seen anything on the SIII device for sprint and really dont want to try it unless i know that is the right way to go. Ill keep everyone posted so if they have or had the same problem this might be an answer. I will gladly take advice from someone with the right knowlege please. Thank you.
***UPDATE*** IM STILL LEARNING AND I HAVE CONTINUALLY SEARCHED THESE FORUMS FOR ANSWERS UNSURE OF.
***UPDATE*** INSURE YOUR PHONE!!!
I was finally able to recover a new phone. Sprint was actually the one that suggested this to me...
If you screw up your phone and don’t have insurance to replace the one bricked or soft brick revert back to a prior model phone that you used past before your Samsung galaxy s3. Then activate your old phone. Activate insurance when you complete activation wait a day or two and bring in the one you messed up and have it replaced by acting as if you have no idea what happened. Tell them a friend that used to work for sprint tried to fix the phone and you have no idea if it was rooted or have any clue what root is and that he was using Odin to try and fix it (ONLY if they ask it was ever rooted even then you should act as if you have no clue). They should replace the device. This is not 100% guarantee but it worked for me. For all of you who messed up like I did I hope this information helps you acquire a new or factory refurbished phone. Good luck. I have made sure to back up every aspect of the phone as I was excited to receive this new device I knew nothing about and realized out of my own stupidity I only did a nandroid back up and it would never flash back because of careless mistakes and greedy want to have another cool rom all the time.
Thank you to all of you who devoted some time to help me with my stupidity!
I'm trying to figure out why you were trying to use Rom toolbox to change your boot logo.........
You clearly got this screen before it let you attempt changing it.....which device did you choose???
Rom toolbox is a very noob friendly way of doing small mods and the ONLY thing that is going to brick you under the "interface" menu is going to be the boot logo changer, and you STILL have to intentionally select a device you are not using to do it........
^^^Add that info to your OP so everyone knows you tried to flash it even tho it clearly shows not S3 compatibility
---------- Post added at 01:57 AM ---------- Previous post was at 01:53 AM ----------
Did you notify the app developer of his app shortcomings before attempting to chop into his revenues????
NOT VERY COOL MAN....:what:
---------- Post added at 02:00 AM ---------- Previous post was at 01:57 AM ----------
Did you notify the app developer of his app shortcomings before attempting to chop into his revenues????
NOT VERY COOL MAN....:what:
Put phone in download mode
Flash stock Odin
Done
And don't use the term brick....a brick is a useless lump of mass that has no power.
If you really have to use it...yours would be what some call a soft brick.
Sent from my SPH-L710 using xda app-developers app
I'm fairly certain if you flash anything using anything that can flash, you Might brick your device. Unless you know what your doing and even then **** happens.
Sent from Pluto.
Thanks for the info. It didn't brick my phone, but flashing a font from room toolbox cause my S3 to freeze at the boot logo, and I had to flash my back up
Sent from my SPH-L710 using xda premium
18th.abn said:
I'm trying to figure out why you were trying to use Rom toolbox to change your boot logo.........
You clearly got this screen before it let you attempt changing it.....which device did you choose???
Click to expand...
Click to collapse
no. I did not use that or get that screen. i never had that option and i never would have selected a device that was not of the same origin.
00mred00 said:
Put phone in download mode
Flash stock Odin
Done
And don't use the term brick....a brick is a useless lump of mass that has no power.
If you really have to use it...yours would be what some call a soft brick.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
done that nothing has happend. so when i finally was able to get back into my bootloader (after i have already restored it by flashing a boot image... even though i apperently dont know how to do that) everytime i tryed to manually flash the rom i got a sig ver fail. Im having a hard time trying to get a soft brick (sorry for the confusion im not good on terminologies) ive researched and come up with an answer from the s2 device when it comes to verification but i feel its a bit risky by loading a temp boot and then restoring cwm boot (actually making a temp bootloading program looks fun to me and plausable) but learning how to do all this is fun and experimental since i cant find a single post on what to do about my situation. im not just doing it to do it. i could just go buy a new phone but Im doing all this to learn it. i would appriciate it if people would stop harrassing me and just help me since i am willing to learn.
pitbull292006 said:
Thanks for the info. It didn't brick my phone, but flashing a font from room toolbox cause my S3 to freeze at the boot logo, and I had to flash my back up
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
your welcome. I do appologize since ive used the wrong terms. but that is exactly what happend to me and nothing i have tried or what i have researched has worked. ive tryed to flash my back up and i cant get it to work i just hangs. i tryed flashing a custom flash to get adb access and i still cant flash my backup. Ive flashed a few times using font flashes but everytime i tryed it i always restored my main back up first
Speedin07si said:
I'm fairly certain if you flash anything using anything that can flash, you Might brick your device. Unless you know what your doing and even then **** happens.
Sent from Pluto.
Click to expand...
Click to collapse
yes i am aware. that is why i am about to go into adb on my own and write out manually. I know how to do that. its just i dont know what to do to get it back. this is my problem. but i want to learn this stuff because i like doing it.
How the heck are you guys messing up switching fonts with RomToolbox. Never once had an issue and have changed it about once a week as the rom i'm on updates.
If you ODIN'd back to stock, it should work.
Did you ensure that everything got flashed in ODIN? Make sure you're flashing system, data, user data, boot/kernel etc.
Then repartition in Odin and flash those again.
It should work after rebooting. If it doesn't, I suspect its hardware failure and that you can get it replaced by going into the store.
Sent from my Sprint SGS3
yousefak said:
If you ODIN'd back to stock, it should work.
Did you ensure that everything got flashed in ODIN? Make sure you're flashing system, data, user data, boot/kernel etc.
Then repartition in Odin and flash those again.
It should work after rebooting. If it doesn't, I suspect its hardware failure and that you can get it replaced by going into the store.
Sent from my Sprint SGS3
Click to expand...
Click to collapse
yes. odin even said pass and it was green after all was completed. at this point I was starting to think it was hardware related and was going to reset the counter before turining it in for factory warrenty.
Thread cleaned
A little ribbing and fun when someone screws up is fine
But outright flaming and disrespect will NOT be tolerated
Thank you for your cooperation
Friendly Neighborhood Moderator
kennyglass123 said:
Thread cleaned
A little ribbing and fun when someone screws up is fine
But outright flaming and disrespect will NOT be tolerated
Thank you for your cooperation
Friendly Neighborhood Moderator
Click to expand...
Click to collapse
thank you! most appriciated
VenomousViper said:
yes. odin even said pass and it was green after all was completed. at this point I was starting to think it was hardware related and was going to reset the counter before turining it in for factory warrenty.
Click to expand...
Click to collapse
That seems like a solid course of action. Make sure you play dumb when you bring it into the store - Just say you left it on your nightstand, the charger wasn't plugged in, but it still wouldn't get past the boot screen in the morning.
The regular procedure is that they take out battery, reboot, check water damage, etc. without actually going into Download Mode.
Well... tbh I dont understand nothing. But try to abd install twrp2 instead CWM. And try to flash any ROM you have in your phone.
Sent from my phone...
Pull battery, reinsert, press and hold (in this order) vol (+), physical home button, then power. Hold all 3 until screen blinks a couple times, let off of power button but continue to hold vol (+) and Home. If you have a custom recovery, this should get you there.......
Problem being, if like u said in op you also flashed a boot logo(splash screen)different than boot animation - the boot logo is earlier in the boot process than recovery and when it gets corrupted, recovery options don't apply because the device won't be able to access it since the boot process is corrupted before the recovery
If it was ONLY a font that got you here, then you WILL be able to access recovery. Fonts are flashed to the /system partition, and if there in a problem , /system is the final step in the boot process and CANNOT NO-WAY cause ANY harm early enough in the boot process to prevent you from accessing recovery. So give it a try.
---------- Post added at 06:34 AM ---------- Previous post was at 06:21 AM ----------
The pic shows ROM toolbox font installer- highlighted is the default location for flashing the fonts
Below is root explorer showing the s3 filesystem fonts are in the correct directory as set as default for ROM toolbox.
So like I was saying, if it was just a font this is a very simple fix for you. Boot into recovery, flash a ROM which formats and writes /system, fixing any kind of error that installing a font could have caused
Personally if you have certain fonts you like to flash and after a successful change of fonts with what ever apps you use. I would then create a zip file with your fonts to flash in recovery when changing roms. Its what I have done without issue. I have even added the fonts folder to gapps for easy install
18th.abn said:
Pull battery, reinsert, press and hold (in this order) vol (+), physical home button, then power. Hold all 3 until screen blinks a couple times, let off of power button but continue to hold vol (+) and Home. If you have a custom recovery, this should get you there.......
Problem being, if like u said in op you also flashed a boot logo(splash screen)different than boot animation - the boot logo is earlier in the boot process than recovery and when it gets corrupted, recovery options don't apply because the device won't be able to access it since the boot process is corrupted before the recovery
If it was ONLY a font that got you here, then you WILL be able to access recovery. Fonts are flashed to the /system partition, and if there in a problem , /system is the final step in the boot process and CANNOT NO-WAY cause ANY harm early enough in the boot process to prevent you from accessing recovery. So give it a try.
---------- Post added at 06:34 AM ---------- Previous post was at 06:21 AM ----------
The pic shows ROM toolbox font installer- highlighted is the default location for flashing the fonts
Below is root explorer showing the s3 filesystem fonts are in the correct directory as set as default for ROM toolbox.
So like I was saying, if it was just a font this is a very simple fix for you. Boot into recovery, flash a ROM which formats and writes /system, fixing any kind of error that installing a font could have caused
Click to expand...
Click to collapse
Thank you for your advice. Ill try that before I turn it in. If i dont have insurance they will still replace it if i act dumb right? Just incase I will make sure i have insurance before going in. Thanks for helping me everyone with my screw up i never had this issue with HTC evo's and ive rooted, and flashed 2 of them and other HTC varients with out an issue. this is the first samsung and i cant figure it out on my own!
I continue get e: signature verification failed every time i try to load my recovery image, stock sprint imgs (every official one i can find), and still get the message every time. Ive never had this issue with HTC.