Related
I bought it yesterday from some guy on craigslist with a dead battery, but after chrarging it with my carger it would not boot, just the G1 screen. i can not enter the recovery menu, but the boot loader menu does work. Is there anything I can do? I tried reloading the rc29 Dreaimg.nbh, but won't boot. It has the pvt 32b and seeing as how that one is easier to root, I am hoping it's a random issue and not a rooting brick.
As a side note, I have searched. through millions of forums, google, and even my attic for answers. there is always people who get no recovery and no Boot loader screen, then there are those who can access both, but I have not heard of one who can access one witout the other.
did the guy tell u if it had been rooted? if so you can flash a custom recovery image
do you know how to use fastboot? if not have a look around and then try this:
try flashing cyanogens recovery image found here:
http://forum.xda-developers.com/showthread.php?t=523558&highlight=recovery
hopefully this will allow you to do a wipe and flash a new image
if you cant do this give me a shout and il think of something else
The guy did not tell me it wouldn't work, he said it worked fine and then this happened. i traded him an old PSP I had laying around for it, so no big loss on my side. I have emailed him, but no response. Well, How would I type in those commands? Through the phone, or the PC? Thos directions are pretty unclear.
what happened when loading the Dreaimg.nbh
Did it successfully do it? It could take a while to boot afterwords so be patient.
find a guide to setting up fastboot.if ur running windows i cant help but if u run ubuntu or some other linux i can....
after setting up fastboot
boot into the spl by holding camera+power with the usb plugged in
and type the commands in on the computer (again just follow instructions on using fastboot)
its the 2nd set you should use, the ones with "fastboot clear...." etc
Oh thanks. I have jaunty installed on my other pc will see how that goes. The dreaimg.nbh file worked. No errors. Do I just restart with green+menu+red, or was I supposed to wait?
restarting should have been fine...
http://forum.xda-developers.com/showthread.php?t=537508
you may find this useful when trying to set up fastboot in jaunty....
remember when you first plug the phone in to type "sudo adb enable-server"
then "adb devices" to make sure it is detected
the first command needs to be sudo whereas the other doesnt otherwise your device wont be detected
adding the line to bashrc didnt work for me so i tend to do it from within
~/androidsdk/tools/
and it works perfect
good luck
if u dont get a reply here i may not be looking at my computer, so u can email me or gtalk me on [email protected] and il always get it (tnx to my g1 )
I was successful in running all the fastboot/adb files in Windows, but while doing some more research, I don't think this phone was rooted. I am not getting the fastboot menu when I hit back button and my PC won't read the phone.
Last night I found out that after leaving it on for like 15-20 minutes it restarts, but after the second restart the phone died. It had been charging all day as I was using it. Seeing as how it was plugged into the PC. I am heading to a t-mobile store and am going to see if I can get a hold of an extra battery, not buy one mind you just ask "politely" to see one. Seems crazy, but I have a hunch it might be that my battery has gone dead. None of the nbh files I tried did anything except the rc30, that one caused my phone to start restarting, before it would stay on the g1 one for more than thirty minutes without a restart.
Sounds like its unrooted and stock but somehow has a corrupted rom.. It should be recoverable. Try the goldcard method to get RC30 on there:
http://forum.xda-developers.com/showthread.php?t=485364
I have been reading through that thread, but I have no idea how to actually use the goldcard that was generated. Anyone can help me through it seeing as I can not enter commands from my phone.
Ok I went to my Mac because dd command does not work under cygwin that well for me( I'm more familiar with terminals from ubuntu and OS X) Well I can't get the goldcard.img onto my micro sd card. I have been reading and no one seems to have any troubles other than actually generatiiong the gold card. I will report back after I finish the whole thread. Also they suggest an allocation size of 4096, but my sd card only gooes to 100* something.
ok, bad news, I just finished the gold card instaallation and put my sd card into my phone. Now it won't go to the bootloader. Too bad.
Good news. Yesterday I tried to boot it while placing the phone in a drawer and it booted to the recovery menu! I did not have an as card at all so there was nothing I could do so I tried to wipe everything and it finished, but it went back to where it was. I had left it in blue light mode all night. So last night I left it to try and redo what I had done, but it did not work. Atleast it goes back to the bootloader. Gold card did not work but I blame it on the CID number. I can't seem to get the right one. I'm looking though.
I realized what I did. I did not mess with it. I took the battery out last night an did not touch it till just now and it booted to the android screen then froze and restarted and went back to the G3 screen I'm going to leave it like this and see if it gets fixed by tomorrow. Than while booting try to get to the recovery menu. Hopefully it will fix the problems. I seriously think it might be the battery. Tmobile store did not have a spare one though.
Just a suggestion, may or may not work.. I got a new G1 the other day, and have rooted it, etc.. Mine did the same thing, on the G1 screen for hours, never left it.. Take the SD card out of it, and try to start it.. Mine would not load due to the partitioning, I had a 47mb ext2, a fat32, and another ext2 partition, which caused it to hang on the G1 screen.. If no luck there, this site is what helped me root mine, gives the files, and the steps.. http://www.getyourdroidon.com/wiki/index.php5?title=How_to_Root_your_G1
Just take the sd card and put it on your computer via an adapter or something to copy the files (Make sure it's formatted fat32)
If by some reason, my explanation above did work, use partition manager 9 to fix the card.
I booted it withoutth sd card, but same deal. Left it without the battery last night and got it to the recovery menu but would not find the update file. Ended up freezing on me so I went ahead and rebooted. Same deal. I guess I will try again tomorrow.
Phone booted up, was entering my log in info and it froze.... I'm still trying to fix this.
At this point, I would try to go completely back to a fresh OEM install, which I'm not sure you've done since you started to get access to Recovery.
Download the original T-mobile bootloader. Rename it to update.zip and copy it along with dreaimg.nbh to the SD card. Enter Recovery and alt-s to install the bootloader... reboot using Home+Back. It will probably lock up at some point as it's been doing. Turn off the phone and get into bootloader to flash dreaimg.nbh.
Report back after you do this.
Hello, I am having some issues and I've tried all of the fixes on several different forums including this one.
I wanted to root my phone so I followed Amon's guide and successfully went from the Tmobile released 1.6 to the rooted 1.5 in the guide. I then wanted to update to the rooted 1.6 but was having issues with trying to install the update. While in the safe mood I asked it to extract update.zip about 3 times before it finally opened it and it extracted everything really quickly!
I then tried to reboot the phone but it stayed at the green MyTouch 3G splash screen without going anywhere. I've tried all the tricks of taking out my battery, unplugging the USB, any form of combination I could.
I'm told my phone isn't bricked, only stuck but my computer isn't picking up the phone either. It doesn't say it can't read the USB device and fastboot still says waiting for devices.
Can some one please help me with my problem?
Thank you,
Difinitus said:
Hello, I am having some issues and I've tried all of the fixes on several different forums including this one.
I wanted to root my phone so I followed Amon's guide and successfully went from the Tmobile released 1.6 to the rooted 1.5 in the guide. I then wanted to update to the rooted 1.6 but was having issues with trying to install the update. While in the safe mood I asked it to extract update.zip about 3 times before it finally opened it and it extracted everything really quickly!
I then tried to reboot the phone but it stayed at the green MyTouch 3G splash screen without going anywhere. I've tried all the tricks of taking out my battery, unplugging the USB, any form of combination I could.
I'm told my phone isn't bricked, only stuck but my computer isn't picking up the phone either. It doesn't say it can't read the USB device and fastboot still says waiting for devices.
Can some one please help me with my problem?
Thank you,
Click to expand...
Click to collapse
What do you mean by safe mode? Which donut ROM are you trying to flash? Which recovery image do you have? How long was it stuck on the splash screen. You need to give more details for us to be able to help out. What radio and spl do you have?
I meant safe mode by where you select the option to extract update.zip.
I was trying to flash Amon's 1.6 32A Rom. Even though my phone states 32B I followed his instructions on how to Root the Mytouch and he was using 32A stuff so I figured if it worked OK, I was now running on 32A instead of 32B.
I was using RAv1.2.0H.img from his original guide. I dont know what radio and spl I have. There wasn't really a guide on updating ROMs so I just tried the same basic steps.
I hope this is more helpful, I am doing my best to learn everything, I am still fairly new to modding a phone. (my last phone was a Blackberry 8100).
Difinitus said:
I meant safe mode by where you select the option to extract update.zip.
I was trying to flash Amon's 1.6 32A Rom. Even though my phone states 32B I followed his instructions on how to Root the Mytouch and he was using 32A stuff so I figured if it worked OK, I was now running on 32A instead of 32B.
I was using RAv1.2.0H.img from his original guide. I dont know what radio and spl I have. There wasn't really a guide on updating ROMs so I just tried the same basic steps.
I hope this is more helpful, I am doing my best to learn everything, I am still fairly new to modding a phone. (my last phone was a Blackberry 8100).
Click to expand...
Click to collapse
I'm not sure what you mean by extract update.zip. I think you are talking about fastboot there. Have you tried to flash the rom in the recovery image? you know, by pressing power and home to get to the recovery, then flashing it through there. go into fastboot by pressing power and back and it will tell you what radio and spl you have. once you have that, write that so we can further get a grasp as to your problem. if in fact you still have the 32A configuration, you might want to flash over the 32B radio and and try to flash a 32B rom.
That is my problem, I can't get past the "MyTouch 3G" green screen. I've tried the Home button, Back button, Vol Down button and holding them for several minutes with no result, it stays at the very first screen when it turns on.
I've tried flashbooting from adb but it says "waiting for devices" and my computer isn't picking up any kind of device.
I'm having the exact same problem except im stuck on the vodafone screen. I also tried flashboot form adb but "waiting for devices" is shown and pc wont detect the device.
Did this before.
If you can get into recovery mode, Hold Home button while powering on, you can restore a nandroid backup, if you took one, or put the sappimg.nbh file or the correct items to flash whatever rom.
I had a stock 1.5 Mytouch. I wanted to root and get the 1.6 version of cyanogen, forgot to flash the HTC_ADP_1.6_DRC83_rooted_base as part of the process and had got stuck in the neverending mytouch logo.
If you can get into recovery:
wipe, then put the update.zip files directly on the card.(use a SD adapter, ...)
Choose apply any update from SD
Choose the base files, then the rom if its a newer version
Once those two updates run, reboot the phone.
My never ending logo disappeared, and the phone booted. Newb mistake on my part.
Wait at least a minute or two once this is done.
since the phone is stuck on the original logo and isnt responding to buttons when loading up... do we manually remove and reinsert the battery while holding the home button?
I have tried getting into recovery mode, but it doesn't do anything past the splash screen. Holding the home button while trying to power on the device won't do much.
hey difinitus keep me updated if u somehow get it to work
Even when you take the battery out for a significant time it turns on immediately to the logo screen. Whats the longest you have left the phone sitting at the logo screen.
A small thought, since it was trying to load a rom you had on your memory card, try taking the battery out, and removing the memory card, and then turn it on and wait a bit and see if you get a different result. Its a thought.
If that doesnt work put the memory card back in and turn it on and once its on remove the memory card.
Perhaps the rom on your memory card is corrupt and it is unable to continue to load it, you could even try putting the rom on again using your memory card reader and your computer, thus erasing the existing one.
try plug usb in to phone
take battery out
prees and hold home button
re-insert battery while still holding button
let go after about 3-5 sec
have you tried getting into fastboot by holding back and powering on the phone once you took out the battery? cuz fastboot doesn't initialize after the splash screen, it just pops up as soon as you hit back and power
@Tech no boy; I have tried using several different update.zip and a .nbh and also tried reformatting.
@sitimber; have tried that before, the splash screen still pops up. It just vibrates once and goes to the logo, with any combination of buttons and steps.
@tazz9690; Yes, no matter what I do it still goes to the splash screen. I've been saying that for several posts now.
you might have a bricked phone then. call up t-mobile and get it returned under warranty. if you are 100% positive that you will not be able to get past your splash screen, then the return center will not be able to prove that you have modded your phone, and they will send you another phone.
you might have a bricked phone then. call up t-mobile and get it returned under warranty. if you are 100% positive that you will not be able to get past your splash screen, then the return center will not be able to prove that you have modded your phone, and they will send you another phone.
my phones rooted and I have the Regaw mod ROM load on there, and its been good for a couple days now. Last night I went to sleep and forgot to charge my phone so figured the battery died. I plugged in it for about 10-15mins or so to turn it on and all it does is hang on the HTC bootscreen!!!! then I try to boot into recovery and all I get is at the bottom of the screen it says "Build : RA-HEROC-v1.5.2"!!!! Does this mean my phone is bricked!!!???
Remove the battery. Put it back in. Try to boot.
There are other solutions. As long as it turns on there should be a way to unbrick. Try RUU as well.
i tried the battery pull a couple times im trying the RUU now but what the hell could have bricked my phone over night?
I think what the guy in the 2nd post is trying to say, is that if it is booting, it isn't bricked.
It would be bricked if you couldn't do anything with it, then its like a brick.
I know it is probably a bit scary but ify ou can boot it at all, you most likely can fix it.
Did you make any changes (remove any files?) yesterday at some point, and this would have been the first restart?
I don't know, it could be a number of things.
It is probably not bricked. I bricked my G1 so I have some experience in that area. If you can boot into recovery it is not bricked. When I bricked my G1 I couldn't even get to recovery. let it charge a bit. Th battery is probably just dead. OR. take the battery out and plug it in and try to boot. Let it boot for about 15 mins or so.
no i didnt change anything at all, except my sd card said it was corrupted after unplugging it from my PC improperly. and I didnt reformat it right away. I just tried to RUU and i got an Error 170 a USB connection error
BAttitude7689 said:
no i didnt change anything at all, except my sd card said it was corrupted after unplugging it from my PC improperly. and I didnt reformat it right away. I just tried to RUU and i got an Error 170 a USB connection error
Click to expand...
Click to collapse
Where does the recovery image read from? I know we put it in the root folder of the SD, but does it actually boot from there? Could be your issue...
are you runnings apps2sd or whatever it is called?
yes that possibly could be my issue!! how can i fix my sd card or what should I do?
no I am not running apps to SD
BAttitude7689 said:
yes that possibly could be my issue!! how can i fix my sd card or what should I do?
Click to expand...
Click to collapse
BAttitude7689 said:
no I am not running apps to SD
Click to expand...
Click to collapse
I'm not so sure. I am pretty green when it comes to all this rooting stuff. I'm just trying to help figure it out.
Maybe try booting without the SD card in the phone? Could help to narrow down the issue.
I'm sure someone with more knowledge could help.
yea im booting it now with NO SD and its still hangs at the HTC screen
BAttitude7689 said:
yea im booting it now with NO SD and its still hangs at the HTC screen
Click to expand...
Click to collapse
Can you try plugging it into your USB connection and getting into the ADB shell (in CMD) to see if you can access the phone even though it seems stuck.
I know I did this and was able to monitor the logcat when I thought it was stuck, but it was really just doing a whole bunch of stuff.
Just an idea....again, I'm just fishing here trying to help you out.
it tells me error: device not found
i went to (CMD) then cd C:\android-sdk-windows\tools and then adb devices
you might have to manually rewipe your recovery partition in cmd. I had to do that after the official ruu messed up my phone- it wouldn't boot at all, I had to use the fastboot command: fastboot oem boot, then using my nandroid backup restored my recovery.
Sent from my HERO200 using the XDA mobile application powered by Tapatalk
im kinda of a noob at some of this so kinda need to explain it out lol ...I just booted to recovery and pressed *vol up* and got me to Fastboot Mode then it says press <Menu> to reset device, should I do that option?
okay i pressed menu and all that got me was it hanging again at the HTC screen.. should i do all of this with my SD card in or out of the phone?
When you boot it and it gets into the "partial" recovery mode, does the PC see the phone? Can you put RA-Heroc-1.6.2 onthe SD card from there? If so, I'd try flashing the new recovery from ADB...very easy...and see if that gets you a bit further along.
You might also try cheating a bit. See if you can pull a nandroid from the SD card (might have to do this with a card reader), then get Flipz's Kitchen and restore the Nandroid after you boot into recovery.
Just a couple of things I'd try....from experience...
S
okay this is what happens i press vol down and power then is load where the androids are on skateboards and it says press <HOME> for recovery along with a Fastboot mode and Simlock option. I press home and then I see the HTC screen for about 30 secs and then where I normally would see the recovery menu with all the green writing i see all black except at the bottom is says
Build : RA-heroc-v1.5.2
sfox said:
When you boot it and it gets into the "partial" recovery mode, does the PC see the phone? Can you put RA-Heroc-1.6.2 onthe SD card from there? If so, I'd try flashing the new recovery from ADB...very easy...and see if that gets you a bit further along.
You might also try cheating a bit. See if you can pull a nandroid from the SD card (might have to do this with a card reader), then get Flipz's Kitchen and restore the Nandroid after you boot into recovery.
Just a couple of things I'd try....from experience...
S
Click to expand...
Click to collapse
To follow this and break it down a bit more for you:
1. Plug in USB with phone off
2. Turn on phone and get it to the "blank" recovery screen.
3. Run through the flashing of the recovery rom image again (see HERE) but start at step 13 or so.
Try doing the above post..
I have a (formerly) rooted G1 that I've attempted to revert to stock RC29 by following the "Full Downgrade Guide" at the CyanogenMod wiki.
My device had HBOOT-1.33.2005, so I used the suggested fastboot command to roll it back to HBOOT-1.33.2003 from the g1boot.zip file linked on that page. This seemed to go well, after which I rebooted into the fastboot (which was still the skateboarding androids screen) again and saw the new (old) HBOOT in the information.
Powered off the phone, inserted the SD card loaded with the DREAIMG.nbh linked in the page, and reflashed the phone. Rebooted with Send+Menu+End, and the phone kept rebooting at the T-Mobile G1 logo screen.
So, I attempted the flash again from the bootloader menu, which is now the "rainbow" style, and shows HBOOT-0.95.(something). It immediately picked up the DREAIMG.nbh file on the SD card and asked if I wanted to flash, chose yes. Same result again: a boot loop at the G1 logo.
I redownloaded the DREAIMG.nbh file without the download accelerator I'd used before, placed it on the SD card, and booted into the bootloader again, flashed, and still the same looping.
So, I attempted to access the "recovery mode" by pressing and holding menu while powering on. I got the G1 logo, then a black screen... pressing Alt-L showed "Android system recovery utility", and nothing else.
Now, the phone will do nothing BUT Android system recovery utility, regardless of what buttons I press or do not press, and I have to remove the battery to turn the damn thing off. Pressing Alt-S, Alt-W, Alt-X, or anything else does nothing.
Where should I look to try to figure out how to recover this thing?
Is a simcard in the phone? Can you get into recovery and wipe incase the partitions are confused?
(Edit, the hint was the sim card)
There's no SIM in the phone at the moment. I can't do anything at the system recovery, except turn the log on or off with Alt-L (which I guess means it's not frozen).
It isn't recognized by ADB anymore, since it has some bastardized version of the stock T-Mobile image that has USB turned off (right? I'm new at this. ).
A bit more info:
I can get into "blue light" mode, and the light is amber/green when plugged into a charger. Sometimes, when I plug the charger in the phone will turn on immediately; but not always.
When I start the phone up and it boots into the broken recovery console, Windows does see an "HTC Dream" device, but ADB doesn't see it.
ezterry said:
(Edit, the hint was the sim card)
Click to expand...
Click to collapse
Should I, or should I not have the SIM in? For what its worth, the phone behaves exactly the same either way.
Thanks for the help.
I just had this exact experience; have you made any progress, goatlordbob?
same happened to me.
cant fastboot, loop at G1 screen, and all i can see in recovery is: Android system recovery utility
some1 find some solution?
why doesnt there seem to b any help for this matter, smh
bull.. s**t
I'm in the exact same boat now. I followed those directions *to the letter* and it put my G1 in this state. Thanks to the wiki maintainer for such wonderful attention to detail. /s
Is there NO way to recover from this?
try to flash this nbh file.... http://www.4shared.com/file/9izdCbvo/DREAIMG.html
ldrifta said:
try to flash this nbh file.... http://www.4shared.com/file/9izdCbvo/DREAIMG.html
Click to expand...
Click to collapse
How? None of the key commands work. Like the OP I can hit Alt+L and it shows ""Android system recovery utility" but that's as far as it goes.
Anyone bothered booting using home + power?
shadowch31 said:
Anyone bothered booting using home + power?
Click to expand...
Click to collapse
Yes - T-Mobile G1 logo, then blank screen forever.
I hope someone can help me. I've been scouring the blogs but couldn't find anything that could help me and I'm stuck. I have a mytouch 3g slide and all of a sudden it keeps rebooting and won't turn completely on...it just keeps rebooting non-stop. I tried taking out the battery overnight and putting it back in, held the volume down button + power button which brought me to the HBOOT screen and only showed FASTBOOT, RECOVERY, CLEAR STORAGE & SIMLOCK. When I tried clicking on RECOVERY it just reboots my phone and does it over and over again, same thing when I do CLEAR STORAGE. I've tried this both with the SD card in and out and it would still not take me to where there's the red triangle...just keeps rebooting. Everything else I've seen on forums tells me to unroot/reroot, reformat, flash etc but since whatever I do it just reboots I can't do it. Other details of my phone are the following:
EXPRESSO PVT SHIP S-ON
HBOOT-1.02.0000
MICROP-0620
TOUCH PANEL-SYNT0102
RADIO-7.07.35.02S
Nov 26 2010, 20:43:01
CM7
I'm sorry but I'm pretty new to this and I get lost with the terms so I'm trying to be as detailed as I can. I really do hope someone can help me
ka-dork said:
I hope someone can help me. I've been scouring the blogs but couldn't find anything that could help me and I'm stuck. I have a mytouch 3g slide and all of a sudden it keeps rebooting and won't turn completely on...it just keeps rebooting non-stop. I tried taking out the battery overnight and putting it back in, held the volume down button + power button which brought me to the HBOOT screen and only showed FASTBOOT, RECOVERY, CLEAR STORAGE & SIMLOCK. When I tried clicking on RECOVERY it just reboots my phone and does it over and over again, same thing when I do CLEAR STORAGE. I've tried this both with the SD card in and out and it would still not take me to where there's the red triangle...just keeps rebooting. Everything else I've seen on forums tells me to unroot/reroot, reformat, flash etc but since whatever I do it just reboots I can't do it. Other details of my phone are the following:
EXPRESSO PVT SHIP S-ON
HBOOT-1.02.0000
MICROP-0620
TOUCH PANEL-SYNT0102
RADIO-7.07.35.02S
Nov 26 2010, 20:43:01
CM7
I'm sorry but I'm pretty new to this and I get lost with the terms so I'm trying to be as detailed as I can. I really do hope someone can help me
Click to expand...
Click to collapse
It sounds as if your phone is toast... however, you could try going to the HTCdev.com site and doing the unlock procedure (which is going to require you to enter fastboot, so if that's not working, you're truly toast).
Once you've got that done, you can then flash a new recovery, like clockworkmod, and see if you can then use that to clear storage, or flash a new ROM.
Alternatively, you could try to just reinstall the froyo update from T-Mobile/HTC.
Thanks
jonnycat26 said:
It sounds as if your phone is toast... however, you could try going to the HTCdev.com site and doing the unlock procedure (which is going to require you to enter fastboot, so if that's not working, you're truly toast).
Once you've got that done, you can then flash a new recovery, like clockworkmod, and see if you can then use that to clear storage, or flash a new ROM.
Alternatively, you could try to just reinstall the froyo update from T-Mobile/HTC.
Click to expand...
Click to collapse
Thanks for the help, jonnycat26. I really appreciate it. It does seem my phone is pretty much toast I tried unlocking it as you said but you're right, it won't let me enter fastboot and my PC couldn't detect the phone since it won't turn on.
I was wondering though, would you happen to have any idea what caused this? It would be good to know so I don't make the same mistake next time around. Thanks again!
Wait! Your phone isn't toast! Download the RUU from the htc website, run it on windows, take the rom.zip from %TEMP%, rename it to ESPRIMG.zip and put it on your sdcard, then boot into Hboot, and it'll reflash the system.
Hitorijanae said:
Wait! Your phone isn't toast! Download the RUU from the htc website, run it on windows, take the rom.zip from %TEMP%, rename it to ESPRIMG.zip and put it on your sdcard, then boot into Hboot, and it'll reflash the system.
Click to expand...
Click to collapse
Thanks, Hitorijanae! I'll try that and let you know how it goes.
Hi Hitorijanae,
Okay I'm not sure if I did it right. I saved it to my sdcard as ESPRIMG.zip as you said and then did the volume down + power thing and it brought me to the screen with the 3 androids (sorry not quite sure if that's the HBOOT page that you were talking about). Anyway it did the SD checking. Does it make a difference if it says [ESPRDIAG.zip] no image or wrong image? Anyway it loaded up the ESPRIMG.zip and then asked me if I wanted to update it and I said yes. After that it asked if I wanted to reboot and when I said yes it just rebooted over and over again like my previous problem. I tried also choosing no and it brought me back to HBOOT and my only options were FASTBOOT, RECOVERY, CLEAR STORAGE & SIMLOCK. Choosing FASTBOOT just brings me to reload bootloader, etc.; choosing RECOVERY my phone just reboot loops again and same if I choose CLEAR STORAGE.
I'm not sure if I'm doing it wrong or just screwing it up even more. Sorry for all the questions but I keep getting stuck. I would appreciate all the help I can get.
ka-dork said:
Hi Hitorijanae,
Okay I'm not sure if I did it right. I saved it to my sdcard as ESPRIMG.zip as you said and then did the volume down + power thing and it brought me to the screen with the 3 androids (sorry not quite sure if that's the HBOOT page that you were talking about). Anyway it did the SD checking. Does it make a difference if it says [ESPRDIAG.zip] no image or wrong image? Anyway it loaded up the ESPRIMG.zip and then asked me if I wanted to update it and I said yes. After that it asked if I wanted to reboot and when I said yes it just rebooted over and over again like my previous problem. I tried also choosing no and it brought me back to HBOOT and my only options were FASTBOOT, RECOVERY, CLEAR STORAGE & SIMLOCK. Choosing FASTBOOT just brings me to reload bootloader, etc.; choosing RECOVERY my phone just reboot loops again and same if I choose CLEAR STORAGE.
I'm not sure if I'm doing it wrong or just screwing it up even more. Sorry for all the questions but I keep getting stuck. I would appreciate all the help I can get.
Click to expand...
Click to collapse
When it's booting up, go into the command prompt, cd to the directory with adb and then do adb logcat.
Hitorijanae said:
When it's booting up, go into the command prompt, cd to the directory with adb and then do adb logcat.
Click to expand...
Click to collapse
When I do that it only says -waiting on device- and nothing else. I tried doing the unlock bootloader thing but when it comes to the part after I type in fastboot oem get_identifier_token it just says waiting on device as well. Any other suggestions? I'm not really a dev so I'm not very confident if what I'm doing is right and I get lost sometimes with what you ask me to do but I try to look it up online to get a better understanding of it and then try it before I ask too many questions. I appreciate your patience with me though and for all your help, Hitorijanae and jonnycat26. I'd like to go on if there's still hope for my phone :crying:
ka-dork said:
When I do that it only says -waiting on device- and nothing else. I tried doing the unlock bootloader thing but when it comes to the part after I type in fastboot oem get_identifier_token it just says waiting on device as well. Any other suggestions? I'm not really a dev so I'm not very confident if what I'm doing is right and I get lost sometimes with what you ask me to do but I try to look it up online to get a better understanding of it and then try it before I ask too many questions. I appreciate your patience with me though and for all your help, Hitorijanae and jonnycat26. I'd like to go on if there's still hope for my phone :crying:
Click to expand...
Click to collapse
Alright, go into HBOOT, then hit power button to go into fastboot. Plug it up, and type fastboot devices in the command prompt.
Thanks!
Hitorijanae said:
Alright, go into HBOOT, then hit power button to go into fastboot. Plug it up, and type fastboot devices in the command prompt.
Click to expand...
Click to collapse
Hi, Hitorijanae!
Sorry for the late reply and things got a bit crazy over here. I had my phone checked and it was a hardware problem so they had to open it up and stuff and now it's all good but I have to be extra careful not to drop or accidentally hit my phone or else it's screwed again. I just wanted to thank you for all your help though
Do you know what was the issue? (Loose cable, failed component, etc)
GoPadge said:
Do you know what was the issue? (Loose cable, failed component, etc)
Click to expand...
Click to collapse
The guy said it was a hardware issue. Something broke off inside and damaged the memory (I accidentally dropped my phone a few days before my phone went bonkers on me). I wish I could explain it better but for the life of me I can't remember the things the guy said right now but he had to open it up and weld the broken bit back together.
ka-dork said:
The guy said it was a hardware issue. Something broke off inside and damaged the memory (I accidentally dropped my phone a few days before my phone went bonkers on me). I wish I could explain it better but for the life of me I can't remember the things the guy said right now but he had to open it up and weld the broken bit back together.
Click to expand...
Click to collapse
Solder, not weld, but I understand completely. I had to replace the power button and digitizer on mine.
GoPadge said:
Solder, not weld, but I understand completely. I had to replace the power button and digitizer on mine.
Click to expand...
Click to collapse
LOL! Yeah, goes to show you how much I know about this stuff I just have to be extra careful with my phone...I hope it holds up for a bit longer.