Related
long story short. i bought a locked g1. did the factory reset. dont have data but have a sim card. i was trying to do the activation over wifi.
when i press enter type reboot and press enter nothing happens.
every time i downgrade to rc29 everything goes smoothly, until its time to reset it after its complete. I restart it and it always get stuck at the screen with the andriod and it says andriod beside it flashing from time to time.
the only way around this is to next install cupcake which brings me back to the activations screen. but i still cant reboot by typing in reboot
its not taking any commands so i cant never get adb to work.
from my searches I'm the only that has this problem right after downgrading to rc29
any info/ help would be greatly appreciated
Do you mean the screen that says "touch the android to continue"? You might want to do what it says.
Oh, and you might want to also do what this FORUM says... post your questions in the QUESTIONS section.
It appears to me that there is nothing wrong except that you aren't willing to follow the instructions.
prelude91sit said:
long story short. i bought a locked g1. did the factory reset. dont have data but have a sim card. i was trying to do the activation over wifi.
when i press enter type reboot and press enter nothing happens.
every time i downgrade to rc29 everything goes smoothly, until its time to reset it after its complete. I restart it and it always get stuck at the screen with the andriod and it says andriod beside it.
the only way around this is to next install cupcake which brings me back to the activations screen. but i still cant reboot by typing in reboot
its not taking any commands so i cant never get adb to work.
from my searches I'm the only that has this problem right after downgrading to rc29
any info/ help would be greatly appreciated
Click to expand...
Click to collapse
If thats what i meant thats what I would have typed.
lbcoder said:
Do you mean the screen that says "touch the android to continue"? You might want to do what it says.
Oh, and you might want to also do what this FORUM says... post your questions in the QUESTIONS section.
It appears to me that there is nothing wrong except that you aren't willing to follow the instructions blah blah blah.
Click to expand...
Click to collapse
I only found one other person that was having this problem after loading dreaing.nbh and no solution was posted other than he might need to upgrade to rc33
prelude91sit said:
I only found one other person that was having this problem after loading dreaing.nbh and no solution was posted other than he might need to upgrade to rc33
Click to expand...
Click to collapse
You mean you found one other person who couldn't follow directions. You won't get anywhere by sassing lbcoder.
Start by posting the question in the right subforum, then follow the directions on the CM wiki.
Ive tried everything. I followed the directions to the T. Its not rocket science. I done everything over 10 times and still hangs at the flashing andriod boot screen. Never goes to the activation screen. I can do the <enter>reboot<enter> and that works. also was able to sucessfully connect to adb for the first. when i tried it at this screen. i get an error when trying to pull up the wifi settings cause my phone itsnt functioning properly.
anybody???
Maybe try something else like RC7. When I was rooting my G1 I followed a tutorial which was recommending RC7 and RC29 to do telnet stuff. RC7 wasn't working for me so I tried RC29 and everything was OK. Maybe it's the same for you, but in reversed order .
i well try it asap. the only reason i havent tried it yet cause im in the u.s. i didnt think i could use it.
got a not allowed. its funny cause when i first tried it i think the image was messed up. it said not found or something. try it a couple times didnt work stopped and let it power up normal and it worked. i was excited. i was able to register it over wifi and everything.. turned it off swiped sim cards ect. then it just got stuck back on the flashing andriod screen. wtf? so im starting all over again it hangs again at that screen as usual
i would try flashing RC33 first...
I would try posting this in the proper forum. It seems to me you asked a question, however you posted in the Android Development forum, see where I'm going with this?
Is it possible to perm brick your phone? My phone got stuck somewhere in the middle of an Odin flash and I had to pull the plug. Since then I have been stuck at the "Phone...!....Computer" picture.
I can get the downloading "Do not turn off Target!!!" section with the cable plugged in and no battery. I also have it recognized by Samsung PSLite, but when I'm trying to flash the stock rom back on through PSLite it disconnects as soon as it goes to 0%.
Will it make a difference that I have Win7 64bit and the VIA drivers say 32bit on them? I'm pretty sure I have every other driver that's needed.
Any help is GREATLY appreciated. I'm a sad panda without my new phone :-(
Go to the dev section of this forum.
http://forum.xda-developers.com/showpost.php?p=14147928&postcount=3
Follows these directions exactly. Will recovery your phone for you.
Good part is, you are not bricked.
Yeah, I've been following a couple of forums that all show nearly the exact same directions. Been getting stuck on the same area...
I have very little knowledge of any of this other than following instructions (obviously not that well) but something tells me it has to be a driver issue.
The VIA drivers I installed say 32bit and my machine is Win7 64. Also, when I plug the phone in it is recognized by my computer with no errors. Once I start the install and it gets to "VIA download" I get the error - then my computer tells me the device was not recognized. I have to do a full reboot to get my computer to recognize my phone again.
Thanks for the directions
Hey man, if that isnt working for you (which I dont see how.) You can always call tech support and say your phone is not booting, even after you pull the battery out. Just say it stays stuck on the samsung screen. They will send out a new phone. Just saying but it should work regardless. Also try another USB port, see if that solves your issue and make sure you are using the OEM usb cable.
I'm assuming this will work for you. It did for me. I had the same screen.
Download first file.
Odin 1.82
Open Odin then hook up your phone and put into download mode with the battery out. Crucial part here. Put the battery back in. After flash the first file I linked you to but make sure you check the PDA option and do it through PDA only.
Should fix it I do believe.
If you follow that exactly like is says. from start to finish. forgetting that you have ever tried anything before. And still follow it. You will be fine. download everything it says download, and follow the instructions exactly.
Thanks for all the feedback everyone.
I've been trying everything suggested on here except getting a newer version of Odin. When I get in tonight I'll keep trucking along with different tweeks.
The good news is I accepted defeat (Grrr!) and have a warranty replacement on the way. It kills me that I couldn't get this on my own.
I've even installed everything on my laptop with the exact same results. As soon as I get to the downloading portion where it shows 0% the phone disconnects and my computer tells me it is no longer recognized. This was in PSLite. Odin simply says FAIL when I try to flash that method.
I have a week to return the first phone. I'll use that time to get all my drivers in order and get this figured out.
After you put the phone into download mode when it was hooked up to the computer did you put the battery back in? I had the same screen as you and when I tried to use Odin it would just say it failed every time. Put the battery back into your phone after it is in download mode before you try to flash with Odin.
Also for PSLite I had to plug in the phone (in download mode) before starting PSLite (opposite of ODIN).
Odin... OdinOdinOdinOdin!
That was my problem. I was using silly PSLite instead of Odin.
Thanks again everyone for the help! Now to see if I can break her again...
mikepic said:
Odin... OdinOdinOdinOdin!
That was my problem. I was using silly PSLite instead of Odin.
Thanks again everyone for the help! Now to see if I can break her again...
Click to expand...
Click to collapse
Actually PSLite worked for me and not ODIN, but for others ODIN worked. I guess it is good to try both. Too bad both seems so flaky! Rooting on the OG droid was a breeze compared to the charge. The OG droid was indescructible.
elucid said:
Actually PSLite worked for me and not ODIN, but for others ODIN worked. I guess it is good to try both. Too bad both seems so flaky! Rooting on the OG droid was a breeze compared to the charge. The OG droid was indescructible.
Click to expand...
Click to collapse
Then go back to the OG Droid. It takes literally 10 min to root a Droid Charge. If you follow the instructions like we tell you to, its not hard at all.
dragonstalker said:
Then go back to the OG Droid. It takes literally 10 min to root a Droid Charge. If you follow the instructions like we tell you to, its not hard at all.
Click to expand...
Click to collapse
I agree rooting was really easy. Several people have had issues where they needed to restore using and ODIN and it complete fails (this is after using ODIN successfully to flash ROMS, recovery, kernels). See the end of this thread:
http://forum.xda-developers.com/showthread.php?t=1108115
You can blame it on user error, but I can assure you that I didn't do anything that should have caused my /data partiion to not mount. Sometimes things happen and the last thing you want is ODIN failing to flash when you have a brick on your hands.
Hope you fix your phone :] It always pains me to see one of these posts where someone has a bootloop or even a dreadful brick.
I wanted to share my knowledge and experience from the past 2 days. Most of the help came from guides and posts on this forum so I wanted to give that back.
We were trying to root the SGS4G and because we're noobs we made the mistake of thinking it was a Vibrant. Got a Vibrant ROM and tried to flash it though Odin WITH re-partition checked. Everything we read said if you do either one of these things, you will brick your phone.
Sure enough we bricked the phone. It was trying to boot into the Vibrant ROM but was getting stuck on the word 'Vibrant' and then showing a whole lot of weird colored pixels. We then learned we'd made a massive mistake and that the phone wasn't a Vibrant after all.
We got a stock ROM for SGS4G and started trying to push them through Odin. Faced countless FAILS and freezes and finally it took us to the Recovery Mode and we tried the Restore option. It booted into a crippled SGS4G ROM. When it booted, it vibrated every 10 seconds or so and it had a null IMEI and unknown baseband.
We tried following a guide that wanted to change some text in the nv_data.bin but the numbers we were meant to be editing (0018810?) didn't exist in our nv_data.bin. So that didn't work for us.
In the meantime we tried to flash the stock ROM in Odin but kept getting FAILs and Freezes. With this step we lost even the crippled operating system and couldn't reach anything except the 'phone --!-- computer' screen. Luckily, this acts the same as download mode, so not bricked. We kept trying to push the stock SGS4G stock ROM (Froyo 2.2) several times and failing.
At one point we got a completely black screen, wouldn't turn on. Bricked again. We found this post on RootzWiki and it worked for us that time and brought it back from the black screen to download mode http://rootzwiki.com/topic/1820-how-to-unbrick-your-sgs4g/
Somehow we ended up at this guide here on XDA for fixing the "null/null" IMEI http://forum.xda-developers.com/showthread.php?t=1142829
We followed that guide. When you add the PIT file it automatically checks 'Re-Partition' in Odin, we didn't uncheck it. Bricked again. It was stuck on the Samsung logo and when we tried to get to download mode it got stuck on a black screen with the loading circle/lines and 2 computers were giving 'The USB device has malfunctioned' when we plugged it in. The unbrick guide above (RootzWiki) didn't help this time. We tried restarting the computer, let the phone rest without battery for half an hour, held power button for a minute without battery, still nothing.
Finally I accidentally pressed the power button (rather than the volume buttons to get into download mode) and it went to the samsung logo (as expected) and after that I was able to get into download mode. The key to this I think is to keep on trying powering on normally then try download mode over and over and eventually it should get unstuck and the computer should recognize it again.
Once I had it back in download mode, I followed this guide again BUT!!! I made sure to un-check re-partition and I did not check "Phone EFS Clear" (because I had tried that already before it was bricked and wanted to see if a straight ROM would work first). Everything worked perfectly, I got my IMEI and Baseband back, without modifying anything.
I don't know if this was a miracle, or if any of it will work for anyone else, but the moral of the story is don't give up even if you've done the absolute worst possible thing. I don't even think hardbrick exists on this phone after everything we were able to save it from.
Cheers
Hardbricks do exist on this phone but you have to try really hard to do it. A few people have managed it. Way to stick with it and recover your phone. I've done that more times than I can count.
hechoen said:
Hardbricks do exist on this phone but you have to try really hard to do it. A few people have managed it. Way to stick with it and recover your phone. I've done that more times than I can count.
Click to expand...
Click to collapse
I didn't feel like i really hard bricked it until i saw the USB computer connection error "device pluged in malfunctioned" in more than one PC.
Then i really felt like its a hardware BIOS chipset level problem now but man...
That story cracked me up. That is exactly why I spend days reading before I even root my phone. I made the mistake one time on my old G1 and it could not be revived.
Congrats on getting it working. (especially without flooding the q&a with redundant questions that have been described in detail several places )
hani1400 said:
I wanted to share my knowledge and experience from the past 2 days. Most of the help came from guides and posts on this forum so I wanted to give that back.
We were trying to root the SGS4G and because we're noobs we made the mistake of thinking it was a Vibrant. Got a Vibrant ROM and tried to flash it though Odin WITH re-partition checked. Everything we read said if you do either one of these things, you will brick your phone.
Sure enough we bricked the phone. It was trying to boot into the Vibrant ROM but was getting stuck on the word 'Vibrant' and then showing a whole lot of weird colored pixels. We then learned we'd made a massive mistake and that the phone wasn't a Vibrant after all.
We got a stock ROM for SGS4G and started trying to push them through Odin. Faced countless FAILS and freezes and finally it took us to the Recovery Mode and we tried the Restore option. It booted into a crippled SGS4G ROM. When it booted, it vibrated every 10 seconds or so and it had a null IMEI and unknown baseband.
We tried following a guide that wanted to change some text in the nv_data.bin but the numbers we were meant to be editing (0018810?) didn't exist in our nv_data.bin. So that didn't work for us.
In the meantime we tried to flash the stock ROM in Odin but kept getting FAILs and Freezes. With this step we lost even the crippled operating system and couldn't reach anything except the 'phone --!-- computer' screen. Luckily, this acts the same as download mode, so not bricked. We kept trying to push the stock SGS4G stock ROM (Froyo 2.2) several times and failing.
At one point we got a completely black screen, wouldn't turn on. Bricked again. We found this post on RootzWiki and it worked for us that time and brought it back from the black screen to download mode http://rootzwiki.com/topic/1820-how-to-unbrick-your-sgs4g/
Somehow we ended up at this guide here on XDA for fixing the "null/null" IMEI http://forum.xda-developers.com/showthread.php?t=1142829
We followed that guide. When you add the PIT file it automatically checks 'Re-Partition' in Odin, we didn't uncheck it. Bricked again. It was stuck on the Samsung logo and when we tried to get to download mode it got stuck on a black screen with the loading circle/lines and 2 computers were giving 'The USB device has malfunctioned' when we plugged it in. The unbrick guide above (RootzWiki) didn't help this time. We tried restarting the computer, let the phone rest without battery for half an hour, held power button for a minute without battery, still nothing.
Finally I accidentally pressed the power button (rather than the volume buttons to get into download mode) and it went to the samsung logo (as expected) and after that I was able to get into download mode. The key to this I think is to keep on trying powering on normally then try download mode over and over and eventually it should get unstuck and the computer should recognize it again.
Once I had it back in download mode, I followed this guide again BUT!!! I made sure to un-check re-partition and I did not check "Phone EFS Clear" (because I had tried that already before it was bricked and wanted to see if a straight ROM would work first). Everything worked perfectly, I got my IMEI and Baseband back, without modifying anything.
I don't know if this was a miracle, or if any of it will work for anyone else, but the moral of the story is don't give up even if you've done the absolute worst possible thing. I don't even think hardbrick exists on this phone after everything we were able to save it from.
Cheers
Click to expand...
Click to collapse
Wheooooooooowwww,..you just UNBRICKED mine, I know of the Battery pull etc...but the post you referenced
is MAGIC
This was not my first Rom nor Root on this phone, it weirdly happened while doing the GB starter....via ODIN, which i also used before..no clue what went wrong, oh well...
Thank you, thank you "i did"....Yohoooo
Yup i agree i like to read, reread then read as i do. This way i got a pretty good understanding of what I'm doing. Btw i have just started using one click and it is sooooo simple. I love it.
Sent from my SGH-T959V using XDA App
The link for fixing null/null IMEI is not working.
http://forum.xda-developers.com/showthread.php?t=1142829
diavel said:
The link for fixing null/null IMEI is not working.
http://forum.xda-developers.com/showthread.php?t=1142829
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=881162
Im still carrying this phone, stupid baseband unlock for iphone won't come out now I am carrying 2 phones, one as an ipod touch and the galaxy s! Good story, hope it can help others, but I am prepared to jump off of this bandwagon anytime now!
I'm throwing in the towel and posting after looking for help on the threads, IRC, etc.
How can I reset my phone to stock? I no longer want root access, I just want a phone that works.
I have an AT&T HTC One X+ that I was trying to root using Hasson2000's all-in-one for the X+. If I don't push anything, it stays on the HTC simply brilliant screen. I can get to the white boot loader screen, fastboot, etc. Recover does nothing besides reboot, show the HTC screen, then go to a black screen. Factory Reset used to go to a black screen with a green arrow logo, but that doesn't happen any more. I used to be able to get to TWRP but it doesn't seem to like me any more. I've read threads about how you can use ADB PUSH to put a boot file on your phone, but I can't seem to find out where to put it. I got a stock ROM from Scott's ROMs, but I am unable to get my phone to be recognized by windows. Windows thinks it's an empty removable drive that asks me to put a disk in when I click it. I can get SOME adb commands to work, like adb reboot, but if I try to do anything else, it says it can't find the device.
Yes, I'm a noob, yes I screwed things up, but this is my only phone and it's a work phone and it might cost me my job. Lesson learned. I just need to get my phone back to working order. Please, please help.
Alternatively, it does have insurance, so I could let one my kids drop it into the toilet.
I know I'm not giving you much help, but you may want to find the correct forum for the phone you need help with.
It's surprising how the people that can't find the right forum for the phone they tinker with have so many problems!
It's never too early to get your kids involved in fraud because you can't do things right.
Sent from my HTC One XL
I appreciate the suggestion. However, I did not see one specifically for the AT&T HTC One X+. Since this was for the AT&T HOX, I figured this would be the best bet.
edit: Sorry I'm a dumbass. I found the forum for the One X+. Thanks again.
Plaguen0g said:
I'm throwing in the towel and posting after looking for help on the threads, IRC, etc.
How can I reset my phone to stock? I no longer want root access, I just want a phone that works.
I have an AT&T HTC One X+ that I was trying to root using Hasson2000's all-in-one for the X+. If I don't push anything, it stays on the HTC simply brilliant screen. I can get to the white boot loader screen, fastboot, etc. Recover does nothing besides reboot, show the HTC screen, then go to a black screen. Factory Reset used to go to a black screen with a green arrow logo, but that doesn't happen any more. I used to be able to get to TWRP but it doesn't seem to like me any more. I've read threads about how you can use ADB PUSH to put a boot file on your phone, but I can't seem to find out where to put it. I got a stock ROM from Scott's ROMs, but I am unable to get my phone to be recognized by windows. Windows thinks it's an empty removable drive that asks me to put a disk in when I click it. I can get SOME adb commands to work, like adb reboot, but if I try to do anything else, it says it can't find the device.
Yes, I'm a noob, yes I screwed things up, but this is my only phone and it's a work phone and it might cost me my job. Lesson learned. I just need to get my phone back to working order. Please, please help.
Alternatively, it does have insurance, so I could let one my kids drop it into the toilet.
Click to expand...
Click to collapse
i cant help you much .. but .. i can tell you one thing.. if u seeing htc brilliant screen... your phones safe... so just go to right forum and ask the right questions .. and get things right
maybe this is your forum : http://forum.xda-developers.com/forumdisplay.php?f=1814
but make it sure yourself
I know it's close that's the problem with things that are similar but different, sometimes they can get you in big trouble if you aren't careful.
Sent from my HTC One XL
Plaguen0g said:
I'm throwing in the towel and posting after looking for help on the threads, IRC, etc.
How can I reset my phone to stock? I no longer want root access, I just want a phone that works.
I have an AT&T HTC One X+ that I was trying to root using Hasson2000's all-in-one for the X+. If I don't push anything, it stays on the HTC simply brilliant screen. I can get to the white boot loader screen, fastboot, etc. Recover does nothing besides reboot, show the HTC screen, then go to a black screen. Factory Reset used to go to a black screen with a green arrow logo, but that doesn't happen any more. I used to be able to get to TWRP but it doesn't seem to like me any more. I've read threads about how you can use ADB PUSH to put a boot file on your phone, but I can't seem to find out where to put it. I got a stock ROM from Scott's ROMs, but I am unable to get my phone to be recognized by windows. Windows thinks it's an empty removable drive that asks me to put a disk in when I click it. I can get SOME adb commands to work, like adb reboot, but if I try to do anything else, it says it can't find the device.
Yes, I'm a noob, yes I screwed things up, but this is my only phone and it's a work phone and it might cost me my job. Lesson learned. I just need to get my phone back to working order. Please, please help.
Alternatively, it does have insurance, so I could let one my kids drop it into the toilet.
Click to expand...
Click to collapse
Firstly, you need to find the way to unlock your bootloader. After that, you can flash the TWRP and get in to recovery ( The original recovery cant access, dont worry, just flash TWRP after unlock bootloader) Next you will be able to flash the custom roms.
Your phone can boot to briliant screen, so it wasnt brick, dont worry.
SOLVED
Followed the instructions here:
http://forum.xda-developers.com/showthread.php?t=2051032
I'm rock solid with a relatively stock app. Thanks for all posters and for Clonz for writng a badass [HOWTO].
Congratulations, next time please post in the correct forum as noted above.
Thank you,
mf2112
XDA Moderator
Apologies if something similar has already been posted on here already. I have had a look, but can't seem to find anything.
I was trying to root my oneplus one this evening, and was following a very useful link here....
https://forums.oneplus.net/threads/like-a-boss-how-to-root-your-oneplus-one.58493/
....and got to the bit that says "sudo fastboot oem unlock" - waited a minute, and the phone rebooted showing the android and 1+ logo. But before anything else happens it turns itself off, then back on again. And continues to do this indefinitely. I can get it into fastboot mode, but not recovery. When it is in fastboot mode the pc doesn't recognise it. Something obviously isn't right, but I'm not sure what. I'm guessing something is possibly corrupt.
What I think I need to do is firstly, get the pc to recognise the phone somehow. Secondly, install a recovery on to it and thirdly, flash a rom. I've been scratching my head all night trying to work out how to get the phone recognised, and Googling like a teenager who's just discovered porn is available on the Internet.
Is there anybody out there who is familiar with Linux who can possibly walk me through what I need to get my phone working again?
Thanks for taking the time to read this, and for any help that may be offered.