Trouble updating to 4.3 - AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin

I'll apologize in advance for not trading the entire 41 page thread about the update. I started to read through it and saw discussion about a lot of stuff not pertinent to the upgrade.
I just gave my daughter an S4 for Xmas and trying to update from 4.2.2 to 4.3 (AT&T) before she starts customizing (I will factory reset after the update). I've kicked off the update a few times - message has popped each time about phone being up to date in the middle of the download, but download would continue. Then it would eventually freeze.
The really weird part is that the update says it's a 728MB update, but twice I've gone beyond that size (last time was almost 900MB/125% before it died).
What the heck is going on???
I read there was an update after the original 4.3 update and thought maybe it was actually downloading 2 updates. But I also wonder if I'm downloading the 728MB update twice somehow.
Anyone have any tips/pointers/suggestions?
Thanks
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2

Check your Baseband number if end with MF3......follow my thread ATT-MK2-Update.zip to upgrade to Android 4.3 MK2 Firmware or there is another thread 4.3 Att official Upgrade http://forum.xda-developers.com/showthread.php?t=2498897 .....To check your Baseband number go to Menu>Settings>More>About Device .....let me know if u need more help and if i help u anyhow.....hit that thanks button......
Swyped from BlueICESense_JBE

I'm MF3
The official thread hurts my eyes, trying to sift through 1,200 posts for pertinent information to my situation.
This might be the part where I get in trouble - asking/saying things I might not supposed to on a dev site. But when you start talking about rooting, sideloading - while those are things I could probably do if I put the effort in (I have rooted and put a ROM on one of my tablets), I'm not going to at this time as I think it's ridiculous that I'm unable to update a brand new never been used phone via either OTA or Kies. I'll return the phone unused before I have to do something to it that should be available without a workaround
I'd really appreciate it if someone can comment on how/why I seem to be downloading more than the stated file size.
Thanks

Just downloaded Kies to your computer, plug it in, and update it through there.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

LZLandingZone said:
Just downloaded Kies to your computer, plug it in, and update it through there.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
Tried Kies - told me that the phone version is updatable (or something like that) via Kies.
Just tried OTA updating for about the 8th time - popped up around 500MB that there's an update available and closed the window I was watching the update download on. Hit update and it acted like the download was still in process - picked up saying it was already at 500MBish. Then download went past 728MB AGAIN, and a short time after told me the phone was up to date (no forced restart to install the update). Now it just popped up that it's downloading an update again - shows 754MB/103%, and it's not increasing.
Getting pissed that I've spent about 5 hours on this thing so far today. Giving up and downloading the file Ted posted and figuring out how to flash the update, since that sounds like I won't technically be rooting or flashing a custom ROM.

I just keep getting more and more frustrated with this thing.
I went through the effort to download the Android SDK on two different machines (it wouldn't launch the SDK Manager on the first one), than had to mess with installing the Java SDK on the 2nd computer because the SDK wouldn't install without that. I finally got the SDK loaded, made sure ADB is installed and running, downloaded the update.zip from Ted's thread, and...
the freakin' phone won't let me boot into Recovery Mode?!?!?!?!?!
I *think* ADB is installed correctly and recognized the phone - I ran 'adb devices' from the command line and it listed the phone. I have tried entering the bootloader myself, and also with the ADB reboot bootloader command. The phone appears to go into the bootloader, but I don't have the ability to do anything - trying to attach a picture of the screen. At the top is just says 'Odin mode' or something.
And help/direction on how to fully get into the mode I need to in order to flash the update?
Thanks
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

cvail71 said:
I just keep getting more and more frustrated with this thing.
I went through the effort to download the Android SDK on two different machines (it wouldn't launch the SDK Manager on the first one), than had to mess with installing the Java SDK on the 2nd computer because the SDK wouldn't install without that. I finally got the SDK loaded, made sure ADB is installed and running, downloaded the update.zip from Ted's thread, and...
the freakin' phone won't let me boot into Recovery Mode?!?!?!?!?!
I *think* ADB is installed correctly and recognized the phone - I ran 'adb devices' from the command line and it listed the phone. I have tried entering the bootloader myself, and also with the ADB reboot bootloader command. The phone appears to go into the bootloader, but I don't have the ability to do anything - trying to attach a picture of the screen. At the top is just says 'Odin mode' or something.
And help/direction on how to fully get into the mode I need to in order to flash the update?
Thanks
Click to expand...
Click to collapse
Hold your power button for about 10 second till vibrate.....that would take u to recovery mode ...if not pull your battery off and put it back....and use combo button to go to recovery mode [hold VolumeUp+Home key+Power button] together and when it vibrate let go only power button while still holding volume up and home key.....and when u see samsung galaxy s4 splash screen and also on top left u would see small tiny blue text reboot recovery..... and let go both volume up and home key....that would take u to recovery so u can flash the update .zip files or use ADB sideload......BTW U SHOULD ENTER ADB REBOOT RECOVERY ........and u should have downloaded file inside your sd card already before u do anything.....and hit THANK button if people help u ......

ted77usa said:
Hold your power button for about 10 second till vibrate.....that would take u to recovery mode ...if not pull your battery off and put it back....and use combo button to go to recovery mode [hold VolumeUp+Home key+Power button] together and when it vibrate let go only power button while still holding volume up and home key.....and when u see samsung galaxy s4 splash screen and also on top left u would see small tiny blue text reboot recovery..... and let go both volume up and home key....that would take u to recovery so u can flash the update .zip files or use ADB sideload......BTW U SHOULD ENTER ADB REBOOT RECOVERY ........and u should have downloaded file inside your sd card already before u do anything.....and hit THANK button if people help u ......
Click to expand...
Click to collapse
Finally - after about 10 hours working on the update on xmas day, I got it to update and my daughter was able to start playing with her phone.
Thanks, Ted.

Related

[GUIDE] Recover your bricked Bell (or other download mode disabled SGS)

I went and bricked my SGS again and thought great.. time to exchange again right? Wrong.
My Bell SGS is one of those cute ones that has no download mode. I thought all hope was lost. It wasn't.
It's simple, adb reboot recovery works fine. But trying to adb is a pain in the ass. Easy solution.
1) Get the one click root/unroot tool: http://forum.xda-developers.com/showthread.php?t=742403
2) Use the tool--any setting is fine, all we're using this for is getting into recovery mode. I clicked unroot 2.1.
3) Surprise! The tool can communicate with the phone just fine even though the phone is failing to boot. You're now in recovery mode.
4) Wipe the data and the cache on the device, and you're good as new. No flashing of update.zip required.
I guess that:
adb reboot recovery
would also work then?
Mithent said:
I guess that:
adb reboot recovery
would also work then?
Click to expand...
Click to collapse
You know, I have no idea. I'm assuming so since that's what I believe his software calls upon, but I've never actually tried it.
define your "bricked"
did you get this screen of
pc-!-phone ?
because in that screen, the phone is not recognized by windows when you plug in the USB cable
so ADB doesn't work when it's the phone is not listening to the PC
Mithent said:
I guess that:
adb reboot recovery
would also work then?
Click to expand...
Click to collapse
AllGamer said:
define your "bricked"
did you get this screen of
pc-!-phone ?
because in that screen, the phone is not recognized by windows when you plug in the USB cable
so ADB doesn't work when it's the phone is not listening to the PC
Click to expand...
Click to collapse
No, I did not get that screen. For me, it just blacked out and locked on bootup.
scouzer said:
No, I did not get that screen. For me, it just blacked out and locked on bootup.
Click to expand...
Click to collapse
then that is not bricked
that is just a software error
when you are truly bricked the phone will not do anything but show you only that screen
AllGamer said:
then that is not bricked
that is just a software error
when you are truly bricked the phone will not do anything but show you only that screen
Click to expand...
Click to collapse
Well I did not know this, and I doubt many people here do either. So I think it's helpful.
picture here
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
* adding it to wiki
Hope I never see that screen then, so if you see that is it game over....no chance of recovery?
galaxysman said:
Hope I never see that screen then, so if you see that is it game over....no chance of recovery?
Click to expand...
Click to collapse
If your phone is 3 button disabled, no chance of recovery. If you have 3 button recovery enabled, it's no big deal.
Cant you just send it into Samsung to recover it if its under warentee??
Cant you just send it into Samsung to recover it if its under warranty??
d3a said:
Cant you just send it into Samsung to recover it if its under warentee??
Click to expand...
Click to collapse
yes you can
actually i did that to mine the one that had the 3 buttons disabled
the new one i picked up have the 3 buttons working properly
Can the 3 button be enabled through a potential future software update?
Or is it something thats so hard-coded in, that it cannot he ever fixed
Ziostilon said:
Can the 3 button be enabled through a potential future software update?
Or is it something thats so hard-coded in, that it cannot he ever fixed
Click to expand...
Click to collapse
it's called a SPL, it might be possible to be fixed if some developers figures out how to copy a good SPL over the defective SPL, but at the moment there is no fix
When i press "3 button" i go to downloading mod, how to get in recovery ? Except from rom manager...
micri said:
When i press "3 button" i go to downloading mod, how to get in recovery ? Except from rom manager...
Click to expand...
Click to collapse
same 3 button, but use volume up instead of down
see the wiki
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S/Vibrant_GT-I9000M
Someone please help
I was trying to run the DTJG4 with the 512 PITT through ODIN when it failed.
I tried again and it didnt flash, so I tried rebooting the phone.
Now I get nothing... just a black screen.
Plug in the power, nothing, plug in the USB, nothing.
Battery removed several times and tried powering up just with power and battery, and trying 3 button combo that didnt work before, but still nothing.
Any ideas?
Thanks
AllGamer said:
picture here
* adding it to wiki
Click to expand...
Click to collapse
I had I9000M do this, 3 button mode was not working and had to return it. It happened during a kies update, luckly, 20 minutes after I had bought it. So I went to a different store and got my current phone. This phone is the best one of the three I've owned. Either 3 button mode just works, and the g-sensor calibration is much closer to being dead on. So there are good ones out there.
I've had 3 total. Here's a breakdown.
1. Purchased august 6th. First phone sold in the store. Download and Recovery modes worked 25% of the time. G-sensor calibration was horrible. Also could not be unlocked.
2. August 21st. Could not get the phone into either mode with button presses. Phone unlocked, but bricked via kies update. Never got to test the g-sensor. Last phone in same store as first purchase.
3. August 21st. Near perfect phone. 100% sucess gettung into download or recovery modes. Unlocked easily, and G-sensor is just slightly off. No need for calibration, unless using as leveling device. Purchased at a store that got initial stock on august 8th.
So, there ARE good phones out there. But the majority by the sounds of it are less than good. Which is unforunate.
As a former samsung owner as well, this is dissapointing. The original galaxy i7500L is still officially running android 1.5 in canada. I just hope and pray samsung doesn't drop this device from their dev cycles. And better yet.. Can fix all these problems with an update somehow...
Sent from my GT-I9000M using XDA App
So, only that specific screen counts as a brick?
On mine the 3 button combo doesn't work (I can only get to some weird "upload mode"), and the phone is stuck on the "Samsung Galaxy S GT-I9000" screen when I boot it up.
Does that mean I should still be able to use ADB with it? The PC seems to recognize the phone (as "SAMSUNG USB Composite Device"), as well as Odin, but ADB doesn't.

Upgraded through KIES to FROYO buts stuck at BOOTING & VIBRATES

I have just upgraded to FROYO through KIES after 3 HOURS of waiting.
But my is stuck at boot screen & vibrates..
i had tried the recovery but no use.
please help me...
Take the battery out, try recovery mode again.
Or you didnt uninstall your lagfix before updating.. If so, do a factory reset in the recovery console.
i did that by VOLUME UP + HOME + POWER.
it went into recovery mode i did every thing NO USE.
did wipe all data, factory, format sd card. Still no use.
i heard about hard reset VOLUME DOWN + (press & release) POWER
then clear storage.
BUT HARD RESET is not working for me..
Donald Nice said:
Or you didnt uninstall your lagfix before updating.. If so, do a factory reset in the recovery console.
Click to expand...
Click to collapse
i haven't installed any lagfix
If you are able to enter to download mode then try reflashing via odin it should work.
dalepraneeth said:
I have just upgraded to FROYO through KIES after 3 HOURS of waiting.
But my is stuck at boot screen & vibrates..
i had tried the recovery but no use.
please help me...
Click to expand...
Click to collapse
i had the same problem and just Vol Up+Home+Power then did a factory reset and then it started up normally.
i had the root & lagg fix when i updated to Android 2.2 Optus
Mr.Hunk said:
If you are able to enter to download mode then try reflashing via odin it should work.
Click to expand...
Click to collapse
how much time would it take through ODIN for flashing???
I got the same issue here. And my SGS can not boot into download mode by hold 3 buttons.
Anyone knows what's the option for me now?
Thanks
Hi
I had the same issue it vibrated and didn't boot up. Remove SD Card, go to recovery via VOL UP + HOME + POWER button when you see boot screen releae all buttons. You are in recovery mode. Vol up down and select wipe data/ factory reset, confirm and your device shall boot.
My SGS booted after this and Yes I had OCLF lagfix installed, device rooted which I didn't remove prior to update. Now its fine again.
Now i tried to flash it through ODIN.
It was taking a long time so i stopped
it is displaying this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[/URL] Uploaded with ImageShack.us[/IMG]
now please help me
dalepraneeth said:
Now i tried to flash it through ODIN.
It was taking a long time so i stopped
it is displaying this
[/URL] Uploaded with ImageShack.us[/IMG]
now please help me
Click to expand...
Click to collapse
From this screen you sholud be able to enter in downloadmode. And, but I'm not sure, from this screen Kies should be able to recover the phone too...
Any way:
Always is a solution.... Search here, on forum, about JIG method to unbrick Galaxy S. You have to made a 301kohms rezistor and connect it on 2 pins from a usb cable. You'll see more pictures, it's easy to made it...
This JIG rezistor will always put the phone in download mode. From here you can reflash with Odin any rom you want.
But, if Odin stopped, there are 2 possibilities: you don't have the phones drivers installed corectly, or (and most important) you don't close Kies from Task Manager before launch Odin. If Kies is runing will take the comm port busy and Odin can't use it to comunicate with the phone.
Always close all Kies applications before flashing with Odin. It's very important.
Good luck.
dentimarius said:
From this screen you sholud be able to enter in downloadmode. And, but I'm not sure, from this screen Kies should be able to recover the phone too...
Click to expand...
Click to collapse
I did not find that recovery.....
does that have to work if KIES pops some recovery of os????
please tell me a way to flash back to
original DDJG4 india firmware...
and is it possible to upgrade to FROYO using KIES after flashing???
have you tried adb search youtube for a tutorial. you can reboot/recovery or download and much much more.
MAKE SURE YOU ARE IN DEBUGGING MODE WITH ADB. and i take out the sim card and ext sd card.
you use commands like c:\androidsdk\tools\adb reboot download
c:\androidsdk\tools\adb reboot recovery
c:\androidsdk\tools\adb reboot
also try apk 3.0 this lets you install apk's via your pc right to your phone, search for z4root apk on this site and use adb to reboot into recovery to apply update.zip
hope this helps, i also have no 3 button combo
dalepraneeth said:
Now i tried to flash it through ODIN.
It was taking a long time so i stopped
it is displaying this
[/URL] Uploaded with ImageShack.us[/IMG]
now please help me
Click to expand...
Click to collapse
Not sure why you would purposly stop Odin while it was running. All you are doing is creating a worse and worse situation for yourself by doing things like that.
It seems to me that you do not know enough about flashing, etc to even be concidering doing so, so... I reccomend that after you finally get your device up and running again that you ONLY flash through Kies and dont do anything else as you will likely end up with one issue after the other...
yiannisthegreek said:
Not sure why you would purposly stop Odin while it was running. All you are doing is creating a worse and worse situation for yourself by doing things like that.
It seems to me that you do not know enough about flashing, etc to even be concidering doing so, so... I reccomend that after you finally get your device up and running again that you ONLY flash through Kies and dont do anything else as you will likely end up with one issue after the other...
Click to expand...
Click to collapse
personally it amazes me when i read some of the horror stories on this site, i find it very couragous that anyone would attempt this without proper research, .
some of the complex hacks i am seeing just aren't needed, yet people risk bricking their phones. Anyway good luck to all who venture in to flashing, you dont learn if you dont try and without mistakes we would not learn as much so thankyou i know no what not to do hi.
I got into the download mode finally by the hairdryer method and load the original optus jg4 rom into the phone, then upgrade to froyo again.
Now everything works fine.
jamyi said:
I got into the download mode finally by the hairdryer method and load the original optus jg4 rom into the phone, then upgrade to froyo again.
Now everything works fine.
Click to expand...
Click to collapse
I searched about the hairdryer method but I don't find anything. Can you help me with a link please?
jamyi said:
I got into the download mode finally by the hairdryer method and load the original optus jg4 rom into the phone, then upgrade to froyo again.
Now everything works fine.
Click to expand...
Click to collapse
I searched about the hairdryer method but I don't find anything. Can you help me with a link please?

fastboot mode and recovery mode not working

ok so my gf was on stock 2.1 .
and i wanted to put cust ROM on the phone .. i could not get into fastboot or recovery and found that i need 2.1 with fastboot kdz . so i downloaded that installed via kdz updater . and could still not get into it. so after some searching i found a clockwork rom kdz and downloaded installed that and still cant get into fastboot or recovery ..
here is what my phone is saying in about phone after clockwork kdz flash
gt540
2.1-update1
2.2.29 [email protected] #1 tue oct 5 15:18 edt 2010
gt540-v20a-oct-05-2010
i personally dont think either of the kdz's i flashed worked
also she is rooted
can anyone give me a hand please so i can put cust ROM on her phone
Ok first i need to know what KDZ with fastboot you flashed, second did you check that the KDZ show -- FINISHED -- after 5-10 minutes that takes the process to finish?
What are the combo buttons you're pressing for get in fastboot?
The proper way is CAMERA+POWER BUTTON ( Hold camera button for 1 sec then hold power button without put down camera button, so both buttons needs to be pressed)
The phone will boot , you'll see LG LOGO then after that you should see a dark-blue clean screen (no logo, no letters, NOTHING! just a clean screen). If you get in the mode, congratulations, you are in fastboot now!
Hi IM not on PC at the moment. But I downloaded the 2.1 with fastboot from Modaco (I think) and on the kdz it said all things like param 1-128 call ended and a few other things but noting said fail and then it said finish. I did leave it for about 5 mins after it said finish before I exited and unplugged. I also done camera power and it just boots phone normally.
Sent from my HTC Desire using XDA Premium App
ok i put the v20b 2.1 with fastboot back onto the phone with kdz updater , but i caAN STILL NOT GET IT TO BLANK SCREEN JUST FULL REBOOT TO NORMAL
adz63 said:
ok i put the v20b 2.1 with fastboot back onto the phone with kdz updater , but i caAN STILL NOT GET IT TO BLANK SCREEN JUST FULL REBOOT TO NORMAL
Click to expand...
Click to collapse
ok now that you there try with the KDZ modified by Mur4ik so you get data2system method too...
so follow this:
http://forum.xda-developers.com/showpost.php?p=13620585&postcount=1
Advantages: Its the lates stock 2.1 ROM released in March 2011, it has fastboot and support for recovery as well plus it has been modified for get 238MB of space for install apps.
PS: *When it get stuck at --apram 244 - 245 you done is normal (you wont see -- FINISHED --)
* the process will take 5 minutes, not even 10
* the fastboot screen is blue, more like electric blue with white letters wich is very different than the normal fastboot mode we are used to, so dont panic is normal.
stuck on lg sign after update 2 20e
adz63 said:
stuck on lg sign after update 2 20e
Click to expand...
Click to collapse
get in fastboot do not let it load read carefully the thread because you need to wipe data
fastboot -w
ok got into fastboot on device (i think ) it says suspend reset port change etc .
when running fastboot.exe -w it says waiting for device ..
all drivers are installed correct
adz63 said:
ok got into fastboot on device (i think ) it says suspend reset port change etc .
when running fastboot.exe -w it says waiting for device ..
all drivers are installed correct
Click to expand...
Click to collapse
Is the screen blue with white letters?, if so then you are in fastboot.
What O/S do you have xp, windows 7, 32, 64 bits? you need to install the proper drivers for your pc recognize your phone in fastboot mode
Download Drivers for your computer recognize the phone in fastboot mode. Unzip and put the files inside the folder in C:\android-sdk (take a look of the 3th image)
INSTALL WITH YOUR PHONE PLUGGED:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
... then next and it will install the drivers.
FOR MORE INFORMATION ABOUT HOW-TO PROPERLY FLASH ROMS OR ANY OTHER USEFULL INFO PLEASE CLIC ON FAQ | LG GT540 Reference Thread
Veronica
i already had them installed ... i have it fixed now with cm6 2.2.1with fastboot and recovery ..... am going to update it to 2.3 rom now ...
thanks very much for your help
actually saying that i have no mobile network connectivity
adz63 said:
actually saying that i have no mobile network connectivity
Click to expand...
Click to collapse
you need to configure APN with the one of your cellphone provider in Wireles & Network settings >> Access Point Names >> press menu button >> New APN
Veronica
lavero.burgos said:
you need to configure APN with the one of your cellphone provider in Wireles & Network settings >> Access Point Names >> press menu button >> New APN
Veronica
Click to expand...
Click to collapse
thats fixed she now has cm7 2.3.4 and all working normal.... Thanks once again
Sent from my HTC Desire using XDA Premium App

[Q] Brick phone maybe? help me out

So I got a htc mytouch 4g And it has that phone icon with a triangle and exclamtion mark. I dont know anything about this phone since I have a att captivate From what I read is that if you have recovery you might be able to do it.
Also when I plug in the usb I go into recover and I Get a fasboot screen and other sorts of menus i have put a pd15img.zip in my external sd card and it loads installs It I guess but still boots into the same Icon.
from what I also read is that you can fix this by loading a stock rom pushing into your sdcard via adb but make sure is name update.zip but when I do that I get Invalid Operation.
when in recovery I have this message E:cant't open /cache/recovery/command also phone boots right into that icon.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I assume this is a soft brick since I get into recover and the other fasboot menu when I plug in USB any help is appreciated
This is my first time with a phone like this so I'm doing what I would normaly do with a captivate ish
I answered in your other thread here. However, now that you've posted a screenshot, I see that the phone isn't even rooted. I have no idea how you get into a custom recovery without root.
I connect usb while the phoneis off and then press volume up + power and that appears.
chibixzero said:
I connect usb while the phoneis off and then press volume up + power and that appears.
Click to expand...
Click to collapse
Yeah, see where it says "S-ON"? That means the phone isn't rooted. You need to perm root and it install CWM recovery, but with those cache errors you're getting, I'm not sure there's any point since those usually indicate a failed eMMC.
Guess my options are
1. call t-mobile and tell them what happen maybe they will replace it but I didnt buy it with contract I'm att and was going to ask my friend to get me unlock code, But idk if its possible I drop it and theres a crack on the phone
2. sell it for parts...
>.< money down the drain I guess fuggin phone
You're booting into stock recovery by default, that's the "triange". That might happen if you have a VolumeDown key/trackpad stuck.
The error in the recovery is natural - stock recovery expects a command when booted into, but finds nothing.
Check that you're indeed installing a correct PD15IMG that contains a complete system image, and if you are and it still doesn't help - try to shake the phone on the side / upside down, to try and release the possibly stuck buttons. If it doesn't help - the phone needs warranty repair. T-Mobile or HTC directly, your choice. To send it to HTC, you pay the shipping. But in any case it's under warranty, unless it has water damage or something.
download this go into fastboot/bootloader then run the ruu and flash, if after this u still get to recovery than its something else.
http://dl.dropbox.com/u/25823285/RUU_Glacier_Gingerbread_S_Videotron_CA_2.10.1530.1_Radio_12.55.60.25_26.09.04.26_M_release_188466_signed.exe
atifsh said:
download this go into fastboot/bootloader then run the ruu and flash, if after this u still get to recovery than its something else.
http://dl.dropbox.com/u/25823285/RUU_Glacier_Gingerbread_S_Videotron_CA_2.10.1530.1_Radio_12.55.60.25_26.09.04.26_M_release_188466_signed.exe
Click to expand...
Click to collapse
That appears to be the Gingerbread leak from the Canadian HTC Panache, but you might want to describe to the OP what exactly it is. Most people won't blindly flash something to their phone without a little info first. Also, could that be flashed to a non-rooted device?
yes thats the official RUU of panache which is glacier inside.
yes u can flash as its RUU.exe u dont need root.
u can even comeback to official mytouch RUU.zip using this exe later if wanted.
because its exe it will reflash everything boot, recovery, splash, radio every thing, thus fixing any problem thats not hardware.
atifsh said:
download this go into fastboot/bootloader then run the ruu and flash, if after this u still get to recovery than its something else.
http://dl.dropbox.com/u/25823285/RUU_Glacier_Gingerbread_S_Videotron_CA_2.10.1530.1_Radio_12.55.60.25_26.09.04.26_M_release_188466_signed.exe
Click to expand...
Click to collapse
i used this as noted but I get this error
Customer ID error (131) I read on these forums is has something todo with a goldcard?
Edit-
I manage to load a stock rom into a External sd card. it updated it everything pass exept step 8 it skip it and the said finish updateing press power to reboot. Rebooted but the whole (second) mytouch splash was going for a long time. I try to use the RUU.exe and it wont boot into bootloatder just boots and stays on the splash screen.
this is what I get now and is stuck on That screen updating radio
Damn.
That would be the first completely stock Mytouch4G in the forum that has a failed eMMC chip.
Yes, it's bricked, you need to exchange it.
But it's also a good proof that gfree has nothing to do with failed eMMC, extra write cycles of flashing ROMs most probably just speed up the destruction process.
you got one large scratch on screen, how good have you kept your phone? have you droped it badly once or twice?
when you used the RUU.exe when did u get that error, does it go upto where it showed you the rom version?
if u got there than you can try one more time but this time with official mytouch RUU.zip. i'll tell you how to do that, later if u got upto that part.
edit nevermind my post cameback above this
If it shows "Fail-PU" in bootloader - then the eMMC isn't functional anymore. No flashing will help him in this case, only warranty repair.
hmm too bad, feel sorry for him

[Q] Can "see" device in ADB, not in fastboot....

Hey guys,
Bare with me please as I am fairly new-ish to Android but have some experience with Samsungs, HTCs and the beloved LG GT540.....
I appreciate if anyone can help me on my plight.....
My girlfriend was running Cyanogen Mod for the last year or so on her device and decided that she wanted to try out a different ROM on her phone....
I wanted to install the Oxegen ROM....
Originally I was thinking it would be easy and I could put it on through Clockwork Recovery and flash the zip no problem, for some reason when I rebooted to recovery clockwork would not load up on the device.... just blank screen....
Not content with this, bored on a Sunday afternoon I gave it a couple of hours of my time and in the process messed my girlfriends phone up....
What I did was I tried flashing back to stock using the LG KDZ updater, that was fine and the phone rebooted and has since stuck on the Android logo....
According to this thread : http://forum.xda-developers.com/showthread.php?t=1078745&highlight=stuck+on+android+screen I gave all this a go and I can not get the device showing up in Fastboot, I can not enable USB debugging on it either as I can not get into the phone to tick the box....
In my cmd prompt I am seeing this :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
In my device manager when my device is connected and powered on I am seeing this :
When I am connected and the device is in "download mode" my devices are like this :
I understand the steps provided in the link above and I am fairly confident I could do them if I can get the device "seen" in Fastboot....
I have installed and re-installed all the USB drivers in hope that it may be a driver issue, now I am wondering is it maybe my OS? Win7 64Bit Ultimate?
I can try it on XP netbook if thats all thats causing my issues....
I am kinda lost now and wondering have I bricked it? It will be the first phone I have if thats the case....
Any help would be appreciated, thanks a lot guys....
Mods if this is in the wrong area, please feel free to move my post.....
did u go to fastboot (power+camera pressed when booting up).
well, from my experience, if i flash incorrectly (via fastboot or recovery), it will go bootloops or go to clockwork, or if i flash incorrectly via kdz, i've got stuck in LG logo or got linux kernel panic.
it seems to me u've flash kdz incorrectly. flash kdz with fastboot mode via download (or emergency mode).
try this:
http://forum.xda-developers.com/showpost.php?p=13184840&postcount=42
and make sure u already install all LG drivers (u can Google those).
gud luck. if else fails, put a very sad and stupid face, act as u dont know anything, bring the phone to the LG representative in ur town.
idk for 64 bit version as i use 32 bit. u can try find pdanet driver, there is 64 bit driver there and it install fastboot well in PC.
m1st3r1 said:
did u go to fastboot (power+camera pressed when booting up).
well, from my experience, if i flash incorrectly (via fastboot or recovery), it will go bootloops or go to clockwork, or if i flash incorrectly via kdz, i've got stuck in LG logo or got linux kernel panic.
it seems to me u've flash kdz incorrectly. flash kdz with fastboot mode via download (or emergency mode).
try this:
http://forum.xda-developers.com/showpost.php?p=13184840&postcount=42
and make sure u already install all LG drivers (u can Google those).
gud luck. if else fails, put a very sad and stupid face, act as u dont know anything, bring the phone to the LG representative in ur town.
idk for 64 bit version as i use 32 bit. u can try find pdanet driver, there is 64 bit driver there and it install fastboot well in PC.
Click to expand...
Click to collapse
Fastboot and ADB works on Windows 7 Home Premium 64bit. I installed LG Drivers then Google USB Driver. It worked then. But I know I did struggle to finally get it working.
Thanks a lot for the advice and replies guys....
As I said, I think my problem lies in not being able to tick the USB debugging option on the phone as I can not boot into the phone to do so....
Is there a way to enable USB debugging over ADB?
As I said, I can "see" the phone responding to ADB, just not fastboot!
I am in the process of installing everything and starting fresh on the Xp netbook, if this fails I would say its new phone time for my g/f, Sony X8 is 80 euro on our network so if the worst comes to the worst I will get her a new one....
Much appreciated guys and if anyone has anything to the thread I will be all ears...
Cheers!
Ko_Ka said:
Thanks a lot for the advice and replies guys....
As I said, I think my problem lies in not being able to tick the USB debugging option on the phone as I can not boot into the phone to do so....
Is there a way to enable USB debugging over ADB?
As I said, I can "see" the phone responding to ADB, just not fastboot!
I am in the process of installing everything and starting fresh on the Xp netbook, if this fails I would say its new phone time for my g/f, Sony X8 is 80 euro on our network so if the worst comes to the worst I will get her a new one....
Much appreciated guys and if anyone has anything to the thread I will be all ears...
Cheers!
Click to expand...
Click to collapse
i think u got it wrong.
read here: http://android-dls.com/wiki/index.php?title=Fastboot and here: http://wiki.cyanogenmod.com/wiki/Fastboot
first of all, i need to ask u the question (again), can u boot to fastboot (or bootloader) when u pressed power (the reject/red phone button) and camera button altogether? the fastboot screen in the phone will be like black screen, but with a little amount of backlight (u'll notice the difference) or blue screen with texts if u flash a kdz-modified-fastboot. if u cant go to bootloader/fastboot, then u need to flash a kdz with fastboot.
u can try this: when u type adb devices, type: adb reboot bootloader
though im not sure if ur gf's phone has fastboot/bootloader (might be missing during the kdz flashing that u've done).
when u type adb devices
m1st3r1 - if you ever come to Dublin, I will buy you a beer!
After nearly 3 days of pulling what hair I have left on my head out, my problem was I was mistaking Fastboot for Download mode.....
I was connecting the phone holding the volume down so it came up "download mode" now all I did was hold the camera + red button and off it went with the command from the post above....
I feel like an idiot, but im a happy idiot right now.....
Thanks a lot, means a lot to me.... (and my girlfriend!)
LOL welcome to the hackers club

Categories

Resources