I'm having problems with my Galaxy S GT-I9000. First, the history, in case that offers any clues. [I should say, "The history as far as I know it." The phone was given to me from someone's proverbial 'sock drawer'; it could have been there for a reason...]
It was running crap with stock firmware (couldn't delete files or pictures [well, they would delete, but they'd always come back], had a hard time writing files [they would write (sometimes) but then disappear (though not immediately)], tons of 'Force close' messages for apps, couldn't change G-Mail account, etc., etc., etc.). I used Kies to update the firmware to 2.3.6. When this was completed I seem to remember some message about not being able to go back to the firmware I updated from. Unfortunately, I didn't write that message down. I figured the new Samsung firmware would fix things.
However, the problems persisted with the new Samsung / Kies-provided firmware. At that point I decided to try third party firmware, specifically Cyanogen 7.2.0. I followed the instructions at the wiki[dot]cyanogenmod[dot]org/w/Install_CM_for_galaxysmtd site (sorry, apparently I'm not able to post external links as a new user). Heimdall put Semaphore's CWM on just fine, and I can still boot into it no problem. I then tried to flash the ROM from the internal SD card (though it took a few tries to copy it there successfully [see write problems referred to above]). It didn't work... It got to Andy on the blue skateboard, but then just looped. And looped and looped and looped... I then tried install the ROM from an external SD card. This seemed to get farther (Andy hung around longer on the first boot after flashing than previously), but it still ended up looping.
I tried the Troubleshooting instructions in the cyanogenmod site referred to above (basically, a different Recovery version). The new Recovery installed fine, but Cyanogen did not... Same boot loop.
I'd like to try to use ADB to push the ROM back to the internal SD card, but now my computer doesn't install the drivers for Galaxy S when I plug it into USB. I have tried to re-install "SAMSUNG_USB_Driver_for_Mobile_Phones.exe" (v. 1.5.27.0), but it still doesn't get the right driver (Win 7-64). "Galaxy S" shows up in Device Manager, under "Other Devices", when I plug it in, but with a yellow triangle and no valid driver.
I've read a bit about internal memory issues with the Galaxy S. Am I banging my head against the wall with this phone? Does it sound like the internal memory is hooped? Is there any fix if it is? It seems to me that, following the instructions, a flash should work. Since it isn't, I'm beginning to think that it's not able to write/read what it needs to to/from internal memory...
If any of that twigs your memory for a suggestion as to how to proceed, please let me know. I've tried a lot, but probably not everything... Thanks for listening.
knottedknickers said:
but with a yellow triangle and no valid driver.
I'v Is there any fix if it is? .
Click to expand...
Click to collapse
For first issue download win 7 drivers from My Android Collections, also for fixing USB problems follow this as for your basic problem, what you seem to indicate is a corrupted Internal SD card, to solve that you need to use only the External SD card by this method
Check this out! You , YES! you are an " Android ". Not your phone but U.
You Must watch this documentary concerning your privacy Terms & Conditions we had agreed to, by using a PC or Smartphone
How to say Thank you? If you find any post helpful on XDA, click on their Thanks button
{
"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"
}
If you are using XDA App or Tapatalk, long press on the post and select :good: Thanks
Its easier to give "Feedback" in this manner than make an additional post.
Related
Hi all.
So I posted this a few days ago in the Ubuntu Forums, but go no reply, and am completely stuck as to what to do. XDA was the next place I thought of to go to for help, simply because the community has always been really helpful and supportive. Any insight or ideas whatsoever would be greatly appreciated
Thanks,
Liam.
First off, I apologise if this is in the wrong section of the forums, or if I'm otherwise breaking any rules. Please correct me if I am
So, I'll try to keep this as brief as I can.
I've been trying to install Ubuntu 12.04 to my portable external HDD (USB-powered), and have run in to a few issues. The drive is ~931GB, (marketed as 1TB), and I've separated it into five partitions: a 750GB storage partition & a 60GB backup partition, a 110GB Ubuntu partition, a 10GB swap partition, and there's also about 1.5GB of unused, unformatted space.
I went about the installation from a LiveCD, and I seemingly successfully installed Ubuntu to the external HDD. Under the 'Something Else' option during the installation, I made sure to select my external HDD as the location to install GRUB (/dev/sdb), selected my Ubuntu partition (/dev/sdb3) as the location to install Ubuntu itself, and selected my swap partition as well (/dev/sdb4).
After, I tried booting off the external HDD, and was taken to the GRUB rescue menu:
error: unknown filesystem.
grub rescue > _
So, I booted back into my LiveCD and searched around for a bit, and on the way noticed that GRUB had been installed to /dev/sdb3 (my Ubuntu partition), under the folder /boot/grub. From what I understand, this is because GRUB automatically installs where ever Ubuntu does? Maybe not.
Anyway, after going through the Fixing a Broken System and Troubleshooting guides on the Ubuntu website (https://help.ubuntu.com/community/Grub2/Installing, https://help.ubuntu.com/community/Grub2/Troubleshooting), I am still stuck with the same problem, and I'm clueless as to how to fix it.
I wouldn't call myself a Linux/Ubuntu newbie―I've been using it on and off for a few years now―but apart from knowing the basic way around a command line, my knowledge is very limited.
The only thing I can possibly think of is that the partitions need to be at the 'front' of the drive, if that even makes any sense? I've also attached a screenshot from GParted to illustrate the way my HDD is set out.
{
"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"
}
Any advice/help at all would be greatly appreciated.
Thanks for your time, and sorry for the essay
Liam.
It's been a while since I had the time to play with Linux, but have you followed the instructions on the first page you posted and reinstalled GRUB to sdb (with no partition number)?
If you are still struggling then it may be worth your time heading over to the Mint forums http://forums.linuxmint.com/ and having a search there - they also tend to be more friendly and helpful than the Ubuntu guys.
Boot Live CD and try re-installing GRUB.
Re-installing is the easiest solution.
Simon.TS.HTC said:
It's been a while since I had the time to play with Linux, but have you followed the instructions on the first page you posted and reinstalled GRUB to sdb (with no partition number)?
If you are still struggling then it may be worth your time heading over to the Mint forums http://forums.linuxmint.com/ and having a search there - they also tend to be more friendly and helpful than the Ubuntu guys.
Click to expand...
Click to collapse
Yeah I have. A few times actually. No luck
Thanks for the recommendation, I'll head over now and see if I can find any help
Thanks for the reply
suky08 said:
Boot Live CD and try re-installing GRUB.
Re-installing is the easiest solution.
Click to expand...
Click to collapse
I've already given that a shot, but thanks for your help anyway
Hi,,
I have just tried flashing a ROM on the Ascend W1 and I am getting an error, which has oviously rendered my device unusable. It does vibrate when trying to turn it on, but screen is black.
I was working with eMMC Software Download app, activated "Program Boot Loaders" and loaded a XML-file. Then I clicked on Download, as shown in the video of windowsmania.pl and in their instructions. I got the message:"Download completed - no errors detected" and my device is correctly recognized as Qualcomm HS-USB Diagnostics 9006. In the eMMC Software Download app it is listed as Qualcomm MMC Storage USB Device, which should also be correct. Still, the device status is shown simply as "error" instead of "writable". The Download button is not clickable. I have tried it with two different PCs, one with Windows 7 and another with Windows 8.
What am I doing wrong?
What does this mean and could anyone who has experience with this issue please help me out?
{
"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"
}
Thanks in advance!
papalakaka
I found a way to solve this issue, but I have no idea why it worked.
I installed Windows 7 32-bit on my PC, installed the drivers, restarted and it was instantly recognized as Qualcomm (whatever) 9006.
So I started QPST Software Download app and I was able to download it. It seems that I had to use a 32bit operating system and not Windows 8, at least it looks like that. The Download button wasn't clickable and the device status has shown error on Windows 8 64bit and Windows 7 64bit. It was writable in 32bit. Hope this helps someone out.
Right click the eMMC Software Download and choose run as Windows XP Service Pack 2, this should do the trick
papalakaka said:
Hi,,
I have just tried flashing a ROM on the Ascend W1 and I am getting an error, which has oviously rendered my device unusable. It does vibrate when trying to turn it on, but screen is black.
I was working with eMMC Software Download app, activated "Program Boot Loaders" and loaded a XML-file. Then I clicked on Download, as shown in the video of windowsmania.pl and in their instructions. I got the message:"Download completed - no errors detected" and my device is correctly recognized as Qualcomm HS-USB Diagnostics 9006. In the eMMC Software Download app it is listed as Qualcomm MMC Storage USB Device, which should also be correct. Still, the device status is shown simply as "error" instead of "writable". The Download button is not clickable. I have tried it with two different PCs, one with Windows 7 and another with Windows 8.
What am I doing wrong?
What does this mean and could anyone who has experience with this issue please help me out?
Thanks in advance!
papalakaka
Click to expand...
Click to collapse
You need to run as administrator
Huawei W1 does nothing as expected during flashing..
My W1-U00 started having problems with loading apps..whenever I tried to load my photos or weather channel app or whatever it looked like it tried to load the app but it redirected me on home screen. After a few days I had a problem with the space on device and some updates it needed so I tried to uninstall some of the apps but when I did so and restarted the phone the apps where back again. Since that point it's impossible to uninstall any app,impossible to reset the phone from the settings>about>reset phone and impossible to hard reset the device, I tried all the possible ways to do a hard reset but nothing, it just restarts like nothing happened and I get no sprockets logo. So after a few months I decided to reflash my device. Everything went smooth but after I clicked on the download button of the eMMC Software Download app instead make my device recognized by my pc as Qualcomm HS-USB Diagnostics 9006 the device restarts as normal and nothing happens. It's impossible to make it work, I tried all the methods available online but nothing...Any ideas??
jwiena said:
Right click the eMMC Software Download and choose run as Windows XP Service Pack 2, this should do the trick
Click to expand...
Click to collapse
Thanks bro! I was crazy...
Hey guys,
Big thanks to @autoprime for mentioning this info on this in the general G4 forum. Figured I'd sum up the steps and repost in our sub-forum for anybody who may be struggling.
If you're like me, you're waiting on root and don't want to accidentally take that new OTA update that was pushed out about a week ago. This OTA has been found to prevent rolling back to previous versions of android, and may also block some/many of the root methods that the developers are preparing to release to us.
If System Update is constantly bugging you to update, follow the directions below:
1) Enable USB Debugging
-Go to About phone and tap on Build number 10 times to enable Dev Options
-Enter Developer Options and enable USB Debugging
2) Download and Install the Debloater tool (this happens on your computer)
-Windows http://rootjunkysdl.com/getdownload.php?file=Gates/DeBloater/Debloater-setup-v3.85.exe
-OSX http://rootjunkysdl.com/getdownload.php?file=Gates/DeBloater/Debloater.v.3.85.dmg
3) Connect your phone via USB. Make sure to install any drivers needed
4) Watch for pop up requesting ADB Access on your phone
5) Launch the Debloater tool
6) Select OK on the popup
{
"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"
}
7) Click the top left button
8) Find LGDMSClient.apk and put a checkmark next to it. Then select Apply at the top
Congratulations! You no longer have to worry about pocket-updating your G4 and not being able to root down the road!
**A couple people are still getting updates after performing this. Please check here for more things you can try.
Great i took mine 10 minutes ago and just saw this.. oh well guess Im stuck with no root options
kangta05 said:
Great i took mine 10 minutes ago and just saw this.. oh well guess Im stuck with no root options
Click to expand...
Click to collapse
I'm optimistic that the devs will be able to release a root method that will still work for those who took the update. I would still run the above process so that it doesn't receive any more updates.
Tomyk89 said:
Hey guys,
Big thanks to @autoprime for mentioning this info on this in the general G4 forum. Figured I'd sum up the steps and repost in our sub-forum for anybody who may be struggling.
If you're like me, you're waiting on root and don't want to accidentally take that new OTA update that was pushed out about a week ago. This OTA has been found to prevent rolling back to previous versions of android, and may also block some/many of the root methods that the developers are preparing to release to us.
If System Update is constantly bugging you to update, follow the directions below:
1) Enable USB Debugging
-Go to About phone and tap on Build number 10 times to enable Dev Options
-Enter Developer Options and enable USB Debugging
2) Download and Install the Debloater tool (this happens on your computer)
-Windows http://rootjunkysdl.com/getdownload.php?file=Gates/DeBloater/Debloater-setup-v3.85.exe
-OSX http://rootjunkysdl.com/getdownload.php?file=Gates/DeBloater/Debloater.v.3.85.dmg
3) Connect your phone via USB. Make sure to install any drivers needed
4) Watch for pop up requesting ADB Access on your phone
5) Launch the Debloater tool
6) Select OK on the popup
7) Click the top left button
8) Find LGDMSClient.apk and put a checkmark next to it. Then select Apply at the top
Congratulations! You no longer have to worry about pocket-updating your G4 and not being able to root down the road!
Click to expand...
Click to collapse
to add to this, once i did this (I blocked 6 apps in total, instructions from a different post) and once i reset my phone, i still got the notification to update (I dont think it would work if i ran it, but i didnt try), so i long pressed the notification, hit the the little circle with the letter i in it, then disabled notifications from google play services. havent seen it since and im still on ZV4. also before i installed debloater i installed the LG united drivers, not sure i needed to but figured id mention it.
edit: this was the post i originally used. http://forum.xda-developers.com/g4/help/how-to-prevent-updates-g4-t3148650
{
"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 am following a YouTube video letter-for-letter and this is the part I’m stuck at. It doesn’t restart the phone like it’s supposed to. It just says “Sending” and never does anything. I renamed my TWRP img file to: “twrp-payton” since that’s what his YouTube video does and works for him. Tried removing the hyphen as well and re-downloading the img. Kept the original file name and still doesn’t work.
Some others had this issue in the YouTube comments and I tried all of the “possible solutions” but none work.
Any help is GREATLY appreciated.
43t34 said:
I am following a YouTube video letter-for-letter and this is the part I’m stuck at. It doesn’t restart the phone like it’s supposed to. It just says “Sending” and never does anything. I renamed my TWRP img file to: “twrp-payton” since that’s what his YouTube video does and works for him. Tried removing the hyphen as well and re-downloading the img. Kept the original file name and still doesn’t work.
Some others had this issue in the YouTube comments and I tried all of the “possible solutions” but none work.
Any help is GREATLY appreciated.
Click to expand...
Click to collapse
The img file is inside the same folder as fastboot files?
The file need to be in the same folder.
And which version are you using?
abrfilho said:
The img file is inside the same folder as fastboot files?
The file need to be in the same folder.
And which version are you using?
Click to expand...
Click to collapse
If that doesn't work, try using the Moto specific version of fastboot, called mfastboot.
It has something to do with the mainboard usb controller or the drivers, I have the same issue. You have 2 options:
- execute the commands on a older computer, maybe with usb 2.0 ports OR
- do first "fastboot reboot-bootloader" and immediately after that (while the phone is rebooting) "fastboot boot xxx.img"
Both methods will work.
cango123 said:
It has something to do with the mainboard usb controller or the drivers, I have the same issue. You have 2 options:
- execute the commands on a older computer, maybe with usb 2.0 ports OR
- do first "fastboot reboot-bootloader" and immediately after that (while the phone is rebooting) "fastboot boot xxx.img"
Both methods will work.
Click to expand...
Click to collapse
Just saw these replies, but this was the option I used to fix it. Tried an older PC downstairs and it worked.
My only issue now is: I have no 4G/LTE at all. Verizon SIM through StraightTalk. I went into APN settings, but everything is greyed out and can’t be edited, or added. When I go into my network settings and set my Preferred Network Type to “LTE only,” I lose all bars and signal. Is this just a Verizon thing or would it work with ATT SIM? Before I got the phone, I did extensive research to make sure it’d fully work on Verizon/StraightTalk, so I’m clueless right now.
A guy named Frank, with StraightTalk live chat, told me that my device isn’t 4G compatible....like, at all. Wth...? They didn’t seem like they knew what I was talking about, though.
ensure motorola drivers are installed and try different USB 2.0 ports.
cango123 said:
It has something to do with the mainboard usb controller or the drivers, I have the same issue. You have 2 options:
- execute the commands on a older computer, maybe with usb 2.0 ports OR
- do first "fastboot reboot-bootloader" and immediately after that (while the phone is rebooting) "fastboot boot xxx.img"
Both methods will work.
Click to expand...
Click to collapse
Worked for me! Thanks for the great help!
Hello XDA Community,
As a preface, I'm an idiot. I figured I could dabble around with different ROM's and through all of my insightful wisdom appear to have hard-bricked my phone in the process. As seen via the attached photos I at one point was able to boot my phone into Fastboot > TWRP > Flash Rom > Off to the races.
Now the phone will not boot period. When plugged into an outlet the blue indicator atop the camera doesn't even blink a blue color. Moreover, when plugged into my PC it is not found via my PC "Devices & Drives" folder. However, when I open the MiFlash tool the phone reflects as "COM3" whereas before it would show what I assume to be the unique ID for the phone.
I came across another thread titled "[EDL Flash] How to fix your hard brick [Mi 9T Pro/K20 Pro]" but even here it mentions the phone booting and displaying some type of error message.
Anyhow, this is a long shot but figured I'd give it a go and see what comes of it.
Thanks for any insight and for simply taking the time to read my post.
Image of MiFlash reflect COM3:
{
"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"
}
Update 1 - I've tried to flash a ROM and get error message: "Object reference not set to an instance of an object". Here:
RealSykes said:
Hello XDA Community,
As a preface, I'm an idiot. I figured I could dabble around with different ROM's and through all of my insightful wisdom appear to have hard-bricked my phone in the process. As seen via the attached photos I at one point was able to boot my phone into Fastboot > TWRP > Flash Rom > Off to the races.
Now the phone will not boot period. When plugged into an outlet the blue indicator atop the camera doesn't even blink a blue color. Moreover, when plugged into my PC it is not found via my PC "Devices & Drives" folder. However, when I open the MiFlash tool the phone reflects as "COM3" whereas before it would show what I assume to be the unique ID for the phone.
I came across another thread titled "[EDL Flash] How to fix your hard brick [Mi 9T Pro/K20 Pro]" but even here it mentions the phone booting and displaying some type of error message.
Anyhow, this is a long shot but figured I'd give it a go and see what comes of it.
Thanks for any insight and for simply taking the time to read my post.
Image of MiFlash reflect COM3:
Update 1 - I've tried to flash a ROM and get error message: "Object reference not set to an instance of an object". Here:
Click to expand...
Click to collapse
That error message is some sort of program error:
https://stackify.com/nullreferenceexception-object-reference-not-set/
I'm no expert on c# programming so cannot say why that error occurred.
You could try to use adb commands, see if adb picks the device up, when you say it does not power on at all, does the phone go into bootloader mode? (, power and volume down)
MOD EDIT: QUOTE REMOVED
try it under windows 7 computer, preferably laptop with usb 2.0 port. It can recognize the device, if not, and standart unbrick method doesnt work even under w7, then you have to use test points on motherboard, edl account is needed for that, idk how to get it as i tried to get it several times but received only mails in chinese so i gave up, not paid too much to bother so much time on fixing one phone.
There is even modified version of flash tool that is believed to authorize any account logged in bypassin the authorize account error i can provide a link for you but not tested if its actually working.
MOD EDIT: QUOTE REMOVED
i actually did research about this while ago and it might help the guy unless he is willing to pay some russian scammer 60 bucks via teamspeak that is doing this stuff from either stolen or modified authorized account which i can provide link to @RealSykes pm me if u wanna try and give it a go, u can pay russian scammers few bucks in the end if all tries fails there is even command for adb if you have unlocked bootloader that will enter edl without test pin points, but u need to enter fastboot mode first which im assuming u cant from what i have understand.
Kind of important question, what did you do to screw up your phone? So others know what not to do.
https://c.mi.com/thread-2173190-1-0.html follow steps on this site if you already didnt find this by yourself, maybe it can give you and permission to flash, as it appears for some people it actually gave it. tried it myself for you now, and it appears my account is somehow ready to flash (authorized) now, but, i applied some time ago for actually get it, so, it can be different for you.
RealSykes said:
"Object reference not set to an instance of an object"
Click to expand...
Click to collapse
An Object is an instance of a Class , it is stored some where in memory. A reference is what is used to describe the pointer to the memory location where the Object resides. The message "object reference not set to an instance of an object" means that you are referring to an object the does not exist or was deleted or cleaned up. It's usually better to avoid a NullReferenceException than to handle it after it occurs. To prevent the error, objects that could be null should be tested for null before being used.
if (mClass != null)
{
// Go ahead and use mClass
mClass.property = ...
}
else
{
// Attempting to use mClass here will result in NullReferenceException
}
hardbrick and button not press
Need Guideline stepbystep pls.....