Related
Hi guys,
UK G1 (Dream) phone recently updated to the 1.6 build, all working fine.
Yesterday I tried installing the free app Shop Savvy. the phone resetted itself after install and sat on the G1 boot screen permanently.
Now phone will pass this boot screen (Tmobile G1)
Tried:
Recovery mode - will not work at all
Quick boot - brings up the multicolour screen but does nothing after.
**PHONE IS NOT ROOTED**
looks like I have had the phone JUST over a year, not looking good...
Any ideas?
You can boot in to the SPL/bootloader so thankfully you haven't bricked
If you're on a contract with tmo you could take it back to the store and they should give you a replacement, but where's the fun in that?
If you want to fix the problem yourself, all you need to do is downgrade to firmware 1.1, then accept the OTA update to 1.6.
Here's the procedure:
1)Put the phones SD card in to a card reader and format as fat32
2) Extract this file and copy it to your SD card as 'DREAIMG.nbh'
3) Put the card back in the phone and hold down power and camera to boot in to the bootloader.
4) Flash it. (Action button is the trackball).
It's a good idea to leave the charger plugged in and have a decent amount of charge in the battery (eg 40%+).
Afterwards the phone will restart and you will need to re-enter your google account info. All your apps and data will be gone, but there's not much we can do about. You can set things up and install apps while you wait for the prompt to update.
Thanks alot AdrianK,
Really appreciate the steps and info, nice one
I have done some flashing on other phones etc so I have no problem with this. However, I am wondering how a normal app such as Shop Savvy could corrupt my ROM and am wondering if it might not be better to get a new phone as this one could have hardware fault?
What do you think?
Silver.
OK,
did exactly as you said Adrian. Phone went through all the flashing routine then, right at the end said press action button to continue (trackball) every time I press the trackball phone returns to the bootloader screen
What now?
SilverfoxUK said:
OK,
did exactly as you said Adrian. Phone went through all the flashing routine then, right at the end said press action button to continue (trackball) every time I press the trackball phone returns to the bootloader screen
What now?
Click to expand...
Click to collapse
I think you can take the battery out restart the phone
Thanks but unfortunately I have already tried that.
Phone just sits on the G1 boot screen as before...
Any other Ideas?
is that ROM you linked for me a UK ROM Adrian?
Once you get to RC7 use these to build back upto 1.6
http://code.google.com/p/official-android-firmware/downloads/list
SilverfoxUK said:
Thanks but unfortunately I have already tried that.
Phone just sits on the G1 boot screen as before...
Any other Ideas?
is that ROM you linked for me a UK ROM Adrian?
Click to expand...
Click to collapse
Yeah that's the RC7 ROM, the UK ROM for 1.1. RC29 is 1.1 for US phones.
This is all very odd, especially that it was an app that caused it, or as you suggested possible hardward failure. Oh well, I guess all you can do now is take it back to tmo.
Hi,
Unfortunatelly I started playing with my I9000 without reading enough and bricked my phone completely (?). If anyone can help please do so.
Description:
1. I tried to flash with Odin new firmware but after flasing and rebooting got message "unable to update media ...." (or something like that) When powering on I got only welcoem screen with phone name
2. I wanted to repeat flashing but Odin could not start reflashing (I still could go into Download mode)
3. I found at xda forum [STOCK ROM] Odin3 One-Click Downloader,
but I didn't notice that it was for Captivate (I thought it is just another name for I9000,now I don't know why)
4. I reflashed my i9000 and after reflashing got only At&t screen turning on and off, without possibility to enter into download mode.
Actually I'm stuck with this situation I feel really stupid, but by mistake I did what I did.
Is there any chance to help ?
Thanx in advance.
according to some users, you might get lucky, and might be able to recover
let your phone stay on on that loop, wait until it turns itself off
then try the 3 button combo again
if all else fail, contact samsung tech support, which will simply send you back to your cell phone place
I'll try but I'm not very optimistic
Waiting doesn't help - I tiried all possible 3 or 2 button configurations unsuccesfully.
Anyone has any other idea if antyhing can be done with the issue ?
The exact same thing happened to me. There is nothing you can do except to bring it back to Samsung. I brought mine back and they have to replace the whole motherboard
what did you tell them? is it going to cost you?
diehard2222 said:
what did you tell them? is it going to cost you?
Click to expand...
Click to collapse
I told them my phone cannot boot. Can they help to reflash the FW and see if it helps. They did and said phone still cannot boot after reflashing. Hence they have to change the motherboard. I asked and they say it's under warranty...
The shop where I had bought my I9000 sent it to Samsung - I will see what they do with it.
I have flashed a vibrant with a i9000S software but the radio did not work quite well. Since the two have different keys, now i cant get it to boot mode. i was able to get into recovery mode via ADB but all i can do is use vol to go up or down and not select an option. the device wont even get out of recovery mode.
Any help will be greatly appreciated.
Same
I did the exact same thing and couldnt get it to go past the AT&T logo i took mine to the samsung authorised repair centre and after 3 days and 49 dollars they fixed it. I dont know how they did it because i couldnt get USB to reconginise or download mode or anything just stuck on white screen but they managed to get it up and running.
So even though it cost 49 dollars to fix it via software method it is better then spending 800 on a new phone or 300 for a new chip which they originaly qouted me. So there is hope with proffessional services
now, the magic usb plug is avaliable in ebay, it can turn your bricked phone into download mode in a few seconds. really good!!!
Hehe... ...the magic is one usb connector an 301 kohm resistor
Br:25011
h***://factoidz.com/how-to-unbrick-your-samsung-vibrant-galaxy-s/
Sad day today....all was well, tried to play around with Swap memory and then the trouble started,
First all the data on my SD card got wiped out !
After that the phone just went dead, no led when connected to charge,screen was dead no light, flicker of any sort, removed battery and tried many times still no luck...
suspected it could be a software problem so connected to to SUT, a phone was detected, tried completing the stock ROM reload, went to certain extent but then resulted in FAIL
Post that now I get a led red light when connected to charger but nothing else. does not go into download mode or battery charging animation.
Tried SUT once again but this time there is no phone detected.....
not sure if it is battery / handset problem....did the core areas in the phone get corrupted while playing with Swap ???
I partitioned using CWM, used Swapper2 app, all went well till I realised that data in SD was wiped clean.
Was on sharp mod...missing the phone badly...any help or guidance will be much appreciated...
Also will visit to service center help now that this phone is completely off SPICE stores ? yes it is still under "Warranty"
had to switch back to blackberry yucksss !!...for sometime I was infact trying to touch the screen
hoping to hear soon from you guys !!!!
First of all very sad to hear, My heartfelt condolences....
At this stage after trying SUT for multiple times, I think a visit to Spice service center is the only solution, please try it and update here
Be ready to part with your phone for a week atleast
BACK in BUSINESS
I got it Back folks.....thanks to SUT & Windows.....was breaking my head on what could be wrong...retraced back all my steps....
checked if the device has been wrongly configured by windows....went to device manager...lo I saw there was "Other Device" with something registered as Qualcomm CDMA. Deleted it...removed the usb and reconnected.....
Windows did a fresh installation of the device...after sometime I could see F drive of the device with image folder and all its contents....
Simply ran SUT once again, even now there was no display, just a gut feel everything will proceed smoothly....and yes SUT detected the device went through the installation. At one step it also asked if it could format F drive....I went ahead pressing OK....SUT finished successfully...after few anxious moments saw the familiar battery charging icon ......My day was made....and after few more anxious moments....I pressed power button to see SHARP Loading....my device is reborn again !
lesson learnt.....Don't play with SWAP mem, let the dev folks figure out and guide us...
If in any trouble keep SUT and preferrably Stock NB0 file handy.
Back in business folks !!
well done bro, was following your situation closely, so glad your phone is back to normal.
Sent from my SH8188U using xda premium
Glad that it works
Great job done
Sent from my Desire HD using xda premium
I will note your experience. Because I am a newbie who tend to do stupid things may be experiencing the same thing. Glad you can solved it and thanks for sharing.
Device still bricked
Hi, I have the same problem. My device (spice mi-410) suddenly stopped working. screen is blank, without power. It wont start in recovery or download mode. It wont charge. Only red led when connected to charger. That red led comes even when battery is not placed in the device and charger is connected. When i connect it to pc, windows detect it as HUAWEI Mobile Connect - Bus Enumerate Device in USB controllers. F disk is not visible nor can SUT detect it. Guess I am struck. This thing happened without me doing anything. It was working properly till night, just saw the device in the morning in this state. I had flashed official .nb0 few months back and the device was working flawlessly till now. Sending it to repairs to spice service centre is out of question (as it is out of warranty), nor those idiots know anything, they just gave me an estimate of INR 9k for repairs without seeing the device.
Any help appreciated.
9K OMG without looking at the phone
ya that idiot has fu***-up my phone earlier too. few months back my glass cracked, although the phone kept working fine. he changed the glass and returned the phone 2 months later, with all signs of ra**e been committed on phone. they never knew anything about the phone and were surprised to see such a huge device from spice. so they tried all there *tools* to pry it open before realizing that what damage they have done. my gps stopped working since then, they refused to fix it saying that as the phone has been *opened* (ra**d by them) it is out of warranty, although it was still under warranty.
And now this has happened.
Mod edit : dont use any abusive words its against the forum rules if u do need to use them i have edited ur post OK
forthe said:
Hi, I have the same problem. My device (spice mi-410) suddenly stopped working. screen is blank, without power. It wont start in recovery or download mode. It wont charge. Only red led when connected to charger. That red led comes even when battery is not placed in the device and charger is connected. When i connect it to pc, windows detect it as HUAWEI Mobile Connect - Bus Enumerate Device in USB controllers. F disk is not visible nor can SUT detect it. Guess I am struck. This thing happened without me doing anything. It was working properly till night, just saw the device in the morning in this state. I had flashed official .nb0 few months back and the device was working flawlessly till now. Sending it to repairs to spice service centre is out of question (as it is out of warranty), nor those idiots know anything, they just gave me an estimate of INR 9k for repairs without seeing the device.
Any help appreciated.
Click to expand...
Click to collapse
Hi Pretty similar to the problem I had, try and do the following
Try to use the newer SUT (1.8) version, search in this forum and you will get the link. If you are on it great.
Keep the nb0 file of any original rom - Spice GB on .32 kernel or Sharp GB on .35 kernel
connect the device with battery (hopefully charged well) to your computer, let windows detect it, launch your SUT, if you see a phone connected you are in luck !...just proceed with the next steps of by selecting the nb0 file, and selecting erase all user data.
SUT will prompt that your F disk is gone bad and do you need to reinstall it, select yes and let SUT do its stuff.
This will 100% load the ROM and F disk stuff and device will boot into the ROM once you finish.
In case SUT is not showing A phone is connected, restart your computer, ensure no other application is running, clear all earlier recognized devices in Device Manager and start fresh by connecting the device again.
vijayar said:
Hi Pretty similar to the problem I had, try and do the following
Try to use the newer SUT (1.8) version, search in this forum and you will get the link. If you are on it great.
Keep the nb0 file of any original rom - Spice GB on .32 kernel or Sharp GB on .35 kernel
connect the device with battery (hopefully charged well) to your computer, let windows detect it, launch your SUT, if you see a phone connected you are in luck !...just proceed with the next steps of by selecting the nb0 file, and selecting erase all user data.
SUT will prompt that your F disk is gone bad and do you need to reinstall it, select yes and let SUT do its stuff.
This will 100% load the ROM and F disk stuff and device will boot into the ROM once you finish.
In case SUT is not showing A phone is connected, restart your computer, ensure no other application is running, clear all earlier recognized devices in Device Manager and start fresh by connecting the device again.
Click to expand...
Click to collapse
hi
this is just my exp i had to use the old sutL3 which is the old 1.7.3
to flash the original India update of the 2.3 it did not work on the 1.8
this is based on my experience when i flashed back the orignal to sell the same and get the one V . I could be wrong do correct me if so but i did this just around 2 weeks back:laugh:
haree said:
hi
this is just my exp i had to use the old sutL3 which is the old 1.7.3
to flash the original India update of the 2.3 it did not work on the 1.8
this is based on my experience when i flashed back the orignal to sell the same and get the one V . I could be wrong do correct me if so but i did this just around 2 weeks back:laugh:
Click to expand...
Click to collapse
You could be right, if I recollect I infact flashed directly Sharp Stock ROM when I was facing the same problem. ....
btw how is HTC ONE V....you could have invested in a device with more RAM If I am not wrong this is with 512
vijayar said:
You could be right, if I recollect I infact flashed directly Sharp Stock ROM when I was facing the same problem. ....
btw how is HTC ONE V....you could have invested in a device with more RAM If I am not wrong this is with 512
Click to expand...
Click to collapse
hi
its ok budget buddy i didnt have much money and only the spice guy was giving me the buy back :laugh:
Phone not detected
I tried all the methods mentioned above on two different PC's. The Problem is that the phone is detected as "USB Input Device". The driver is provided by SUT. When it says device driver installed it shows as "usb input device" and the red notification LED glows. This happens whether or not battery is inserted. I charged the battery externally too.
Any Solutions?
Hello Everyone, My name is Zeeshan Khalid and i am new and post my problem first time, if i am not clear with my problem or if done something wrong then sorry in advance,
I have bought Z1 in used 2days ago. it was working fine there but when i arrived home it was not shutting down hanged on "shutting down".
Things are happening with my Z1:
i) when i am charing it taking a lot of time to get some juice almost 6 hours and it is 52% only. using iPhone 5s's charge.
ii) when its on it is not showing my IMEI number, ie "null"
iii) it says turning wifi on but wifi is not getting on
iv) getting hot from back top to top 40% area.
v) NFC, Blue tooth sim card not working when it is saying turning on wifi.
it only turned on wifi once after i have put it 24 hours on charging and all the phone worked like a charm and battery stopped on 38% all the night (i was not using that 12 hours) after that i restarted to change my sim card it goes again dead.
can anyone help me out?
Best Regards.
zeeshan.khalid said:
Hello Everyone, My name is Zeeshan Khalid and i am new and post my problem first time, if i am not clear with my problem or if done something wrong then sorry in advance,
I have bought Z1 in used 2days ago. it was working fine there but when i arrived home it was not shutting down hanged on "shutting down".
Things are happening with my Z1:
i) when i am charing it taking a lot of time to get some juice almost 6 hours and it is 52% only. using iPhone 5s's charge.
ii) when its on it is not showing my IMEI number, ie "null"
iii) it says turning wifi on but wifi is not getting on
iv) getting hot from back top to top 40% area.
v) NFC, Blue tooth sim card not working when it is saying turning on wifi.
it only turned on wifi once after i have put it 24 hours on charging and all the phone worked like a charm and battery stopped on 38% all the night (i was not using that 12 hours) after that i restarted to change my sim card it goes again dead.
can anyone help me out?
Best Regards.
Click to expand...
Click to collapse
Have you tried flashing firmware ftf file
abdo.war said:
Have you tried flashing firmware ftf file
Click to expand...
Click to collapse
Yes i have FTF = "C6903_14.3.A.0.757_UK Generic (1276-0875).ftf"
and after that it is doing the same and plus it is always bring the language selection screen and terms and condition every time i restart.
zeeshan.khalid said:
Hello Everyone, My name is Zeeshan Khalid and i am new and post my problem first time, if i am not clear with my problem or if done something wrong then sorry in advance,
I have bought Z1 in used 2days ago. it was working fine there but when i arrived home it was not shutting down hanged on "shutting down".
Things are happening with my Z1:
i) when i am charing it taking a lot of time to get some juice almost 6 hours and it is 52% only. using iPhone 5s's charge.
ii) when its on it is not showing my IMEI number, ie "null"
iii) it says turning wifi on but wifi is not getting on
iv) getting hot from back top to top 40% area.
v) NFC, Blue tooth sim card not working when it is saying turning on wifi.
it only turned on wifi once after i have put it 24 hours on charging and all the phone worked like a charm and battery stopped on 38% all the night (i was not using that 12 hours) after that i restarted to change my sim card it goes again dead.
can anyone help me out?
Best Regards.
Click to expand...
Click to collapse
Find out your device model number
See box or pull tray under simcard slot for model number
Flash ftf for that device
Or just take phone to sony's service centre. The device is new so they will replace it free of cost..!! AND also dont bother telling them about flashing and all...
kathanpatel1001 said:
Find out your device model number
See box or pull tray under simcard slot for model number
Flash ftf for that device
Or just take phone to sony's service centre. The device is new so they will replace it free of cost..!! AND also dont bother telling them about flashing and all...
Click to expand...
Click to collapse
Yes i have used correct FTF.
Sony is not launching mobiles officially in Pakistan, there is no warranty, and service centre for mobiles
It will be stupid idea from me
But stupid ideas may works
You said no warranty
So unlock ur bootloader and try installing cm rom or rr
And see if from software or hardware problem
Note: 1.backup your ta before unlock
2. If your device have LTE then your model is c6903
If not try to find your model in the setting
If the UK version of FTF doesn't work on your Z1 try other one,anyway don't worry try the other version or use the global version 14.6.A.0.270.
abdo.war said:
It will be stupid idea from me
But stupid ideas may works
You said no warranty
So unlock ur bootloader and try installing cm rom or rr
And see if from software or hardware problem
Note: 1.backup your ta before unlock
2. If your device have LTE then your model is c6903
If not try to find your model in the setting
Click to expand...
Click to collapse
Yes mine is c6903 and how i can do this stuff, do you have any link that can help.
U can unlock your bootloader from
Doomlord thread here follow the steps correctly or you could brick your device ....but u must backup your ta if you want to get back your DRM keys
And then download cm12.1 from the official site
here
After download
1. Open flashtool
2.connect your phone in fastboot by press vol. Up after connect
3.copy cm12.1 to ur pc and open zip file and extract boot.img
4. Click on lighting button in flashtool then click fastboot mode
5.under doomlord word you will find select kernel to flash click and select boot.IMG file...
Don't close the window without checking the log that everything is okay
6.open your device in recovery mode by pressing vol. Down
7.wipe factory reset and cache then install update from internal memory the find the cm12.1 zip file and install it
.....
Hit thanks if that help you
did you know if the phone was repaired? like for a broken screen?
when i broke mine, and after fixing it, i experimented really low wifi signal. After a second trip to the technician the problem was fixed. It really has to do with the re-ensemble of the phone.
abdo.war said:
U can unlock your bootloader from
Doomlord thread here follow the steps correctly or you could brick your device ....but u must backup your ta if you want to get back your DRM keys
And then download cm12.1 from the official site
here
After download
1. Open flashtool
2.connect your phone in fastboot by press vol. Up after connect
3.copy cm12.1 to ur pc and open zip file and extract boot.img
4. Click on lighting button in flashtool then click fastboot mode
5.under doomlord word you will find select kernel to flash click and select boot.IMG file...
Don't close the window without checking the log that everything is okay
6.open your device in recovery mode by pressing vol. Down
7.wipe factory reset and cache then install update from internal memory the find the cm12.1 zip file and install it
.....
Hit thanks if that help you
Click to expand...
Click to collapse
Thanks for the replay, I have downgrade the ftf and face the same issue after spending a lot of time on this i have went to the repair shop they tell that its "base ground is short".
Hi, can anyone please point me to the correct method for booting in recovery? All the volume up/down+power key combinations do not work for me.
Thanks.
gbmolina said:
Hi, can anyone please point me to the correct method for booting in recovery? All the volume up/down+power key combinations do not work for me.
Thanks.
Click to expand...
Click to collapse
Hi how are things.
do you have root?
Magisk?
if you have magisk, from there you can start.
No root, obviously, otherwise there is a ton of apps for booting in recovery.
gbmolina said:
No root, obviously, otherwise there is a ton of apps for booting in recovery.
Click to expand...
Click to collapse
I understand that the equipment must be turned off.
1.connect usb cable to pc.
2.connect cable to s20 fe.
(wait for the battery percentage to appear.
3. press volume + and power at the same time (it will turn off after 2 seconds, keep pressing, until the s20 logo appears
4. done.
Thank you, worked like a charm. This is new, I mean, the connection to the PC. Thanks again.
gbmolina said:
Thank you, worked like a charm. This is new, I mean, the connection to the PC. Thanks again.
Click to expand...
Click to collapse
If you want to be root at some point.
Magiks application has the option to reboot in recovery mode.
excellent day .
Hi guys, I have the exact same problem (no root, Android 13 update from 1st of March) and your solution doesn't work. It doesn't want to go into recovery or download mode whatever combinations I try. Do you have any advices?
yabol708 said:
Hi guys, I have the exact same problem (no root, Android 13 update from 1st of March) and your solution doesn't work. It doesn't want to go into recovery or download mode whatever combinations I try. Do you have any advices?
Click to expand...
Click to collapse
if your team is business, it will not work.
There are variants that are blocked by companies.
If that's your case, you can't this way.
Several teams have already passed with that detail.
mezacorleehone said:
if your team is business, it will not work.
There are variants that are blocked by companies.
If that's your case, you can't this way.
Several teams have already passed with that detail.
Click to expand...
Click to collapse
No, it is and it was a personnal one. Unless you mean blocked by mobile operator.
yabol708 said:
No, it is and it was a personnal one. Unless you mean blocked by mobile operator.
Click to expand...
Click to collapse
There are teams that your work gives you. (companies, corporations, etc.)
They send to ask for the equipment with Samsung, they block the access to recovery and download.
In my repair shop, Samsung equipment arrives with that block.
In your case, you say that it is not business, I don't know what causes your problem.
yabol708 said:
No, it is and it was a personnal one. Unless you mean blocked by mobile operator.
Click to expand...
Click to collapse
keep trying
I put the cable into the PC, halfway plug the cable into the phone while it's turned off. then I start holding volume up plus power for recovery and then push the cable all the way into the phone immediately after.
Ok. Thank you both for the help. I'll try this method as well.
Found out why the recovery mode didn't want to turn on. The cable was just for charging :/ Plugged in another one and it worked like a charm. Thanks for all the help guys.
I just joined. I can not see where I start a new thread to ask a question.
Can someone direct me?
BTW - My problem is I installed Fire Toolbox, It ran once and now only open a gray box on the sceen and freezes. Rebooted , uninstalled - reinstalled, tried diff versions...?