Related
Hi guys, from that morning i have some great problem with my desire...
I had DeFrost 0.8 FroYo Rom on it, but due to some problem with usb tethering on my windows vista PC i decided to go back on pays eclair rom.
During the flash i had an error, and when phone rebooted it would show me only 1st HTC white screen and then reboot infinite times.
I tried Wipe , install stock ROM .zip from recovery but even when i succeded install stock 1.405.21.2 ROM it keeps rebooting on HTC white screen.
Sometimes it succeed in booting but the phone cannot read SD card nor SIM card, and if i power it off here we go again with the infinite reboot thing....
I'm desperate, help me someone plz....
If it boots, and doesn't read the SD card then I'd say you are bricked. It's a fairly simple fix now. Just take a look at the sticky about usb bricks in this forum.
i was thinking on doing that' but installing stock ROM means my desire is no more rooted now and when i connect it to my pc they won't talk eachothers (windows xp keeps asking me to installa qualcomm drivers even if i already installed with HTCsync)... For the USB brick fix you need to be rooted...
There has been a good fix for this problem for quite some time already. I don't mean to be rude, but please take more effort in finding a solution to your problem yourself instead of fully relying on your friends here at XDA.
http://forum.xda-developers.com/showthread.php?t=691639
You should be able to do step 1 after which you are rooted again. Did you try it yet?
I already seen that post, it's just that i was thinking without step 2 you had no root (i am able to do step 1 but on step 2 in recovery PC don't see my phone).
Thx a lot
ash1684 said:
I already seen that post, it's just that i was thinking without step 2 you had no root (i am able to do step 1 but on step 2 in recovery PC don't see my phone).
Thx a lot
Click to expand...
Click to collapse
Do step 1. Then apply the usb fix, then your all set to go again.
ash1684 said:
I already seen that post, it's just that i was thinking without step 2 you had no root (i am able to do step 1 but on step 2 in recovery PC don't see my phone).
Thx a lot
Click to expand...
Click to collapse
Step 1 is enough. Did you succeed?
Ok my phone is DEAD! Yes I have have read alot of posts and used my mate "Google" but they are all saying or pointing to the threads saying flash with the .sdf files with RSD which I have done Infact i've tried most .sdf images. I work in ICT so I know to do research first before posting but I'm not getting anywhere. I just hope i'm being a numpty and missed something.
I have an unbranded UK one original version 2.21 and I had successfully flashed with the available roms on here and others by following the steps, but last night I flashed it with PAYS rom and it was fine but then it all went pear shaped when I tried to flash it back to the original 2.21 rom via RSD Lite but it's just a black screen and when plugged in I get a charge light. The Battery is fully charged.
I can not enter Bootloader and when I enter system recovery it does not respond when pressing the bottom right hand corner.
RSD does see the phone connected and it runs through the process of flashing it but then it goes to re-boot and nothing. RSD says it's finished, it does not go through the process of re-booting the phone.
In RSD on the phone properties this is all I get:-
IMEI/ESN/MEID: N / A
Technology: N / A
Software Version: N / A
Flex Version: N / A
Bootloader Version: v0x000910
DRM Version: N / A
AP Die ID: 1e600209036f60010000d8ff0100
BP Die ID: 0000000000000000000000000000
AP Public ID: a9e56c008df05759e72a50cf0e4ce907eea6c0de
Please, please somebody help me!
Simple way to start off is to start with original UK 2.51 sbf. Forget 2.2 now and start from beginning. I bricked mine trying Pays too.
Sent from my MB525 using XDA App
chaihg said:
Simple way to start off is to start with original UK 2.51 sbf. Forget 2.2 now and start from beginning. I bricked mine trying Pays too.
Sent from my MB525 using XDA App
Click to expand...
Click to collapse
Hi,
I have tried flashing the 2.51.sbf even tho it has the problems with downgrading. It does the same as the the other 5 or 6 i've tried.
Thanks for your suggestion tho.
I'm no expert, but is this where the touch all four corners going clockwise starting is upper left comes in?
Thought I read something about doing that when touching the single corner didn't work to get into recovery.
I could have misremembered (don't even know if it was in this forum), but it couldn't be that hard to try and it doesn't sound like you have much to lose.
maybe search four corners or something to figure out more.
Maybe time for factory repair
ABC_Universal said:
Maybe time for factory repair
Click to expand...
Click to collapse
I think it may be time to call Motorola. Thanks for the tips guys.
Just tried the battery hack to charge it but nothing, even uninstalled everyting and downloading fresh .sbf files from work and still DEAD!
RIP Moto Defy, it was only one week old!
On a life experience tho, my first even bricked device......woooohoooooooo!
I've had quite a few phones that I have customized from here, top effot guys. There are many greats minds on here.
Think as i've just lost it, it could be time to retire and go (dare I say it!) mainstream, run of the mill Nokia.....GULP!
In the future it would be better to post these issues in the thread of the ROM you are having issues with. More people who may have had similar issues may be able to help you and it helps the dev know what issues you're having.
it_ferret said:
I think it may be time to call Motorola. Thanks for the tips guys.
Just tried the battery hack to charge it but nothing, even uninstalled everyting and downloading fresh .sbf files from work and still DEAD!
RIP Moto Defy, it was only one week old!
On a life experience tho, my first even bricked device......woooohoooooooo!
I've had quite a few phones that I have customized from here, top effot guys. There are many greats minds on here.
Think as i've just lost it, it could be time to retire and go (dare I say it!) mainstream, run of the mill Nokia.....GULP!
Click to expand...
Click to collapse
Did you send it away?. You sounded like a bright guy we could have solved this together though . Ultimate thing you could have done was to flash one of the leaked original UK froyo sbf. If you still have not sent it then do this. BTW what is the bootloader version when you put it on vol up+ power ?
Have the same problem
The phone is briked. Only RSD is working but wathever sbf I flash, at the end i get the same black screen. I can not do anything. Please could someone help us?
If someone send their phone to service, please share the result.
The only sbf file that start the phone is
JRDNEM_U3_3.4.2_117-002_BLUR_SIGN_SIGNED_USAJRDNEMARAB1B8RTGB035.0R_USAJRDNFRYORTGB_P003_A002_HWp3_Service1FF.sbf
but is working hard, the market is not working, everything i want to download is say that is downloading and nothing hapends.
Could someone tell me how to go back to original software?
The recovery mode is not working, when the android face is showing, i tap all corners and all display area but nothing hapend.
For recovery mode, you should click both vol up and vol down simultaneously. They changed the recovery button function with the new bootloader.
it_ferret said:
Ok my phone is DEAD! .....
Please, please somebody help me!
Click to expand...
Click to collapse
I had the same problem, but with luck i had read this thread :
http://forum.xda-developers.com/showthread.php?t=940647&highlight=market
and i succeded to restore my "brick" into one working phone.
Try it.
Many thanks to : adlx.xda
Edit: http://forum.xda-developers.com/showpost.php?p=11226369&postcount=5 works for me
Umm... I just bricked mine (HK version 2.51.0) as well.
I used ClockWorkMod Recovery for Defy to install 3.4.2 131-003 Orange Deblur. When the recovery finished, I found a tiny yellow line "E: can't open /cache/recovery/command" on the bottom of screen. Not sure if it was there before the recovery. When rebooted the phone showed the M logo for a minute, turned black for a second, and showed the M back again in loop.
Then I installed RSDlite 4.8 to flash the sbf directly. RSDlite finished and showed a "Pass". The phone was turned off automatically but couldn't be turned on again. The battery was fully charged before I started the update so it's not likely the battery charge problem.
Weudel said:
In the future it would be better to post these issues in the thread of the ROM you are having issues with. More people who may have had similar issues may be able to help you and it helps the dev know what issues you're having.
Click to expand...
Click to collapse
I did post in the thread.
Heys guys thanks for all the comments, but last night it came alive.
I used 3 different computers and in the end the last pc I used was a WIN 7 x64 machine and it managed to complete the .sbf install which was a 34.4 version then i applied my previously nand backup to 34.4.4 US T-Mobile version which is Jboogie3 rom.
Keep up the good work guys and gals. This is an excellent community to be in.
ABC_Universal said:
Edit: http://forum.xda-developers.com/showpost.php?p=11226369&postcount=5 works for me
I tried this install but that aswell failed.
Click to expand...
Click to collapse
im a newbie at this and did pays flash but had probs couldnt dial out ect ect so went to recovery but could not get bottom left hand screen work so after half day of trying i clicked both bottom -vol and top+ vol and restart button on top and it worked!!! but thought id give the rom one last go so did factory reboot flashed cash ect restarted signed into blur and now works great pleased i stuck with it...cheers pays
So here is what happened...
I am on the 2.2.2 Nordic sbf and Installed CM7 5.1 on it...
I used it for now 1 week.
But when the phone was booting, the green LED appeared while the Red M was displayed (due to the 2nd-init)
But I accidentally removed the battery at this moment and now my phone don't want to boot anymore........
I tried to reboot again but it was in a boot loop....
Then I wiped data by stock recovery and when I reboot,
It stays on the Red M logo and nothing......
I tried everything!
Go to system recovery and wipe data
Went to Custom Recovery and Restore
Re-installed the fixed Nordic sbf...
STILL NO LUCK :"(((((((((((((((((((
Please help me guys.....
please....
I'm gonna cry if it's bricked...
EDIT: Flashed 3.4.3-11 it boots but stuck in a boot loop... :'(
WIIstpM said:
So here is what happened...
I am on the 2.2.2 Nordic sbf and Installed CM7 5.1 on it...
I used it for now 1 week.
But when the phone was booting, the green LED appeared while the Red M was displayed (due to the 2nd-init)
But I accidentally removed the battery at this moment and now my phone don't want to boot anymore........
I tried to reboot again but it was in a boot loop....
Then I wiped data by stock recovery and when I reboot,
It stays on the Red M logo and nothing......
I tried everything!
Go to system recovery and wipe data
Went to Custom Recovery and Restore
Re-installed the fixed Nordic sbf...
STILL NO LUCK :"(((((((((((((((((((
Please help me guys.....
please....
I'm gonna cry if it's bricked...
Click to expand...
Click to collapse
Did you reinstalled it with RSD Lite?
AkkiandDefy said:
Did you reinstalled it with RSD Lite?
Click to expand...
Click to collapse
Yes I reinstalled Nordic sbf with RSD Lite but didn't work....
Now I tried with the 3.4.3-11 One and it Boot with the Blur animation but it's STILL in a boot loop :'(( :\ ....
WIIstpM said:
Yes I reinstalled Nordic sbf with RSD Lite but didn't work....
Now I tried with the 3.4.3-11 One and it Boot with the Blur animation but it's STILL in a boot loop :'(( :\ ....
Click to expand...
Click to collapse
Sorry for off-topic but at this point I would cry, too
AkkiandDefy said:
Sorry for off-topic but at this point I would cry, too
Click to expand...
Click to collapse
what do you mean............
Is it bricked then?................
WIIstpM said:
what do you mean............
Is it bricked then?................
Click to expand...
Click to collapse
I would say, yes
but it could be that somebody has a way to make it functional again.
PS.: I would post this to the Defy Development topic, because the activity there is muuuch higher.
AkkiandDefy said:
I would say, yes
but it could be that somebody has a way to make it functional again.
PS.: I would post this to the Defy Development topic, because the activity there is muuuch higher.
Click to expand...
Click to collapse
Gosh it Booted FINALLY!!
I went to system recovery and wiped data again... Phew... I was about to commit suicide... lol
I wonder If I can still go to Nordic again and install CM7....
Did you wipe date/factory reset in stock recovery?
Edit: ok, glad to got it back
What did you do to make it work?
Just a question when you flashed as example the 3.43.11 Rom , did the M-Logo appear??
spryte said:
i had a similar problem, but i wasn't able to flash my device any more.
Try to wipe and afterwards install beta 5.0, for me it worked.
Otherwise try this rom and flash it. This is the one i use as base rom.
Finally, as long as you are still able to power up your phone with the charger it should be possible to find a solution for your problem.
Click to expand...
Click to collapse
What do you mean by flash?? a SBF or a ROM??
What happened when you tried to flash another??
Phew... I'm so relieved now... I'm now definitely more careful with my phone!!
WIIstpM said:
Gosh it Booted FINALLY!!
I went to system recovery and wiped data again... Phew... I was about to commit suicide... lol
I wonder If I can still go to Nordic again and install CM7....
Click to expand...
Click to collapse
When it boots and gets stuck in a bootloop the phone is not, and I repeat, NOT bricked. Apparently there was clearly a software problem but as long as the device turns on, the display works and you manage to get to the bootloader then there is very little need to worry. So you know for the next time: suppress your panic, breathe and just keep trying.
Even when the screen doesn't turn on it isn't necessarily a bricked phone. This happened to me a few months ago because I was so stupid to flash an older sbf. It turned out that the device actually still functioned up to the bootloader. RSD lite detected the phone and I managed to revive it completely by flashing the original sbf. The Defy really is almost unbrickable mostly thanks to the locked bootloader, a blessing in disguise.
AgentSmith said:
When it boots and gets stuck in a bootloop the phone is not, and I repeat, NOT bricked. Apparently there was clearly a software problem but as long as the device turns on, the display works and you manage to get to the bootloader then there is very little need to worry. So you know for the next time: suppress your panic, breathe and just keep trying.
Even when the screen doesn't turn on it isn't necessarily a bricked phone. This happened to me a few months ago because I was so stupid to flash an older sbf. It turned out that the device actually still functioned up to the bootloader. RSD lite detected the phone and I managed to revive it completely by flashing the original sbf. The Defy really is almost unbrickable mostly thanks to the locked bootloader, a blessing in disguise.
Click to expand...
Click to collapse
The same I asked, if he saw the M-Logo because then it's normal that it needs more time (5-10 minutes)
AkkiandDefy said:
Did you wipe date/factory reset in stock recovery?
Edit: ok, glad to got it back
What did you do to make it work?
Just a question when you flashed as example the 3.43.11 Rom , did the M-Logo appear??
Click to expand...
Click to collapse
Yes everything appeared as normal (white M-logo though)..
When I flashed 3.4.3-11 I got a boot loop then I went to system recovery and wipe Data and it works again..
Do you know if I still can flash other sbf or rom??
I want to go back to CM7... I also have a CWM backup but I'm afraid to restore this...
WIIstpM said:
Yes everything appeared as normal (white M-logo though)..
When I flashed 3.4.3-11 I got a boot loop then I went to system recovery and wipe Data and it works again..
Do you know if I still can flash other sbf or rom??
I want to go back to CM7... I also have a CWM backup but I'm afraid to restore this...
Click to expand...
Click to collapse
Then it maybe wasn't a bootloop, because if you flash a new sbf, its normal that it can take 10 minutes to boot
AgentSmith said:
When it boots and gets stuck in a bootloop the phone is not, and I repeat, NOT bricked. Apparently there was clearly a software problem but as long as the device turns on, the display works and you manage to get to the bootloader then there is very little need to worry. So you know for the next time: suppress your panic, breathe and just keep trying.
Even when the screen doesn't turn on it isn't necessarily a bricked phone. This happened to me a few months ago because I was so stupid to flash an older sbf. It turned out that the device actually still functioned up to the bootloader. RSD lite detected the phone and I managed to revive it completely by flashing the original sbf. The Defy really is almost unbrickable mostly thanks to the locked bootloader, a blessing in disguise.
Click to expand...
Click to collapse
lol I panicked because I tried almost everything!
weird bootloop (after M-logo, black screen)
bootloader -> didn't work
custom recovery -> didn't work
stock recovery -> didn't work
CWM Backup -> didn't work
Different sbf -> bootloop
Finally Stock recovery again -> worked!
hi, i have a similar problem to yours (i made my own thread about it and still no ideas) but RSD Lite doesn't discover my phone, it just doesn't appear there. How can i try to make it appear in RSD LitE? My prhone also doesnt load the system, just hangs in Motorola logo moment. I can go to recovery and boot menu etc...
please help me, i feel like crying as well.... (
AkkiandDefy said:
Then it maybe wasn't a bootloop, because if you flash a new sbf, its normal that it can take 10 minutes to boot
Click to expand...
Click to collapse
no it was, after some minutes the animations froze and it started all other again. the first few secs of booting are laggy as it used to, and it repeated..
your_login said:
hi, i have a similar problem to yours (i made my own thread about it and still no ideas) but RSD Lite doesn't discover my phone, it just doesn't appear there. How can i try to make it appear in RSD LitE? My prhone also doesnt load the system, just hangs in Motorola logo moment. I can go to recovery and boot menu etc...
please help me, i feel like crying as well.... (
Click to expand...
Click to collapse
Install the drivers
You will ask where to download them?
Google it
Click to expand...
Click to collapse
@AkkiandDefy
@spryte
@AgentSmith
THANK YOU FOR EVERYTHING!!
You were quick, helpful, and helped me to stay calm
Really I thank you!
:")
But could you please help @your_login too??
He got more severe problems than me apparently...
WIIstpM said:
@AkkiandDefy
@spryte
@AgentSmith
THANK YOU FOR EVERYTHING!!
You were quick, helpful, and helped me to stay calm
Really I thank you!
:")
But could you please help @your_login too??
He got more severe problems than me apparently...
Click to expand...
Click to collapse
He just need to install the Moto-Drivers, and RSD-Lite will recognize it
AkkiandDefy said:
He just need to install the Moto-Drivers, and RSD-Lite will recognize it
Click to expand...
Click to collapse
I have the drivers already installed, i managed to flash the nordic sbf a few days ago without any problem maybe its my computers fault that it fails to see the phone now..? i reainstalled them anyway and still no luck. However, i forgot to mention it earleier - when i connect a turned off phone via usb to my computer the phone itself turns on, hangs at motorola logo and on my computer i can hear 'device plugged' sound and MotoHelper windows appears on my computer, so it is being recognised to some extent. However, in RSD Lite there is still no device in the list and i can't try with flashing another sbf ((((
Hello,
Yesterday, I buy my new i8150 Galaxy Wonder and i root my phone
I install the rom Black Notes Chapter 2 with ClockworkMod.
I used V6 Supercharger with scrip manager.
After the restart everything worked normally and I just installed Viber app.
Being tired, I have not verified if the scrip was properly installed
I go to bed and getting up several hours later, my i8150 galaxy displays a black screen with
RAMDUMP mode
<null>
I will restart my phone and there's only the Samsung logo that flashes every second.
No more access to Clockwormod, the logo flashes too.
The only thing I know to do is put it into Download Mode or RAMDUMP Mode > cause: force upload
So I try flashed an original rom (W I8150XXKK1 Galaxy (EUR)) into Download Mode with Odin Multi Downloader v4.43.
Every step is going well, but when it restarts automatically at the end of the process, the Samsung logo blinking again.
I also tried to reinstall ClockworkMod with Odin Multi Downloader, but still the stage proceeds successfully, always the same problem of flashing samsung logo on startup and no access to ClockworkMod
Help me please, it's been over 5 hours I'm looking for a solution.
THANK YOU
I'm not completely new to android, I trained for over a year with my ZTE Blade with different Rom (CyanogenMod)
(My text is translated with google, my maternal language is French. I understand English, but do not know much to write)
Please post in appropiatte section
Thread moved
Sent from my GT-P1000 using Tapatalk
Oh2.. This is interesting r u sure no access to CWM ? If possible best to wipe all system folder making the phone fully wiped.
Have you tried to flash stock recovery ?
Sent from my GT-I8150 using xda premium
I tried so many different ways to repair my Galaxy W, that I totally bricked ...
Thank you anyway, I tried the after sale service, but I have hopes that I can exchange :-(
johndfl said:
I tried so many different ways to repair my Galaxy W, that I totally bricked ...
Thank you anyway, I tried the after sale service, but I have hopes that I can exchange :-(
Click to expand...
Click to collapse
Just doing independent research
From 1:10 wonder has this problem...
No kidding, but the characteristic for the phone that possible have a boot loop are always have FORCE CLOSE app and doing RESTART itself
It can fixed but only if we get stock firmware with wipe and boot loader to fix this issue
I will bring this issue to new tread
Im having this problem too. Any solutions for it.
Used perfectly for a day and 2nd day when i woke up the samsung logo keeps flashing..
Rio Saputro said:
Just doing independent research
From 1:10 wonder has this problem...
No kidding, but the characteristic for the phone that possible have a boot loop are always have FORCE CLOSE app and doing RESTART itself
It can fixed but only if we get stock firmware with wipe and boot loader to fix this issue
I will bring this issue to new tread
Click to expand...
Click to collapse
This is EXACTLY what happened yesterday..and just now I wiped everything in the phone and turned it on. It worked first, but there was a FC on the start or something..and the screen goes black. But I notice that I'm still in the custom ROM I was using (GingerICE). Then I turned it off and and went to CWM. I tried reboot system now, but I was stuck in the samsung logo. Can someone help?
I have the backup of the stock ROM. Is it safe to make the backup?
needya said:
This is EXACTLY what happened yesterday..and just now I wiped everything in the phone and turned it on. It worked first, but there was a FC on the start or something..and the screen goes black. But I notice that I'm still in the custom ROM I was using (GingerICE). Then I turned it off and and went to CWM. I tried reboot system now, but I was stuck in the samsung logo. Can someone help?
I have the backup of the stock ROM. Is it safe to make the backup?
Click to expand...
Click to collapse
if you could boot into Recovery screen, you could try:
wipe factory/system, wipe cache, advanced > wipe dalvik.
[careful] i usually format my /system if i get bootloops.
then reflash the ROM. reboot.. in my cases, those steps always worked.
edit: you should checkout the GingerICE with non OC version, the OC may work on some device and some don't, IMO if you're using your droid for daily use, i recommend using the non OC
im facing same issue too here... but i couldn't even access to download mode... tried many times, still failed... help plss...
Same thing happen to me ...today. I can get into download mode, but after flash the with odin it is still the same, boot loop on samsung logo.... help !!!
can you get to recovery mode?
follow my steps 3 post before this post
Hi..
If you can't go to recovery mode
Go to this tread..
http://forum.xda-developers.com/showthread.php?t=1506765
It not discuss about fixing but i want the user be aware of this issue
Regards
Twiq said:
can you get to recovery mode?
follow my steps 3 post before this post
Click to expand...
Click to collapse
No.. I can't.... only download mode
sgilmans said:
No.. I can't.... only download mode
Click to expand...
Click to collapse
Most probably it won't work but try to flash only the stock recovery, than give it a try(recovery mode).
Instruction and files (Scroll down to Other)
greets
THE-E
Check out Rio's thread above!!!!
You nay need to return under warranty!!
Unfortunately!!
Sent from my SGW GT-I8150 using Tapatalk!!
sgilmans said:
No.. I can't.... only download mode
Click to expand...
Click to collapse
hi, im just try bringing the idea , search the thread usb jig solution .it might help to hard reset ... .peace
Hello,
Recently I've flashed Arco's CM9 version. It all went well for a couple of weeks until today. When I booted my phone, suddenly all apps started crashing and then it rebooted. But, the problem is, it is now stuck on a flashing Samsung logo.
Before I've started this thread, I've read many many similar threads about this, and started a 'rescue operation' by my own by using the tutorials for flashing back a stock rom with ODIN and other possibilities.
Unfortunately, after I've tried twice using ODIN, my phone is still stuck in the Samsung logo loop. I also can't enter Recovery mode, but am able to enter Download mode, as you've probably noticed.
As this is my first Android phone, I've always carefully read the tutorials and disclaimers about possible failures. I'm aware that the maker of the rom is not responsible for this.
Since I tried to flash back to stock android 2.3.6 from CM9 kernel, I've read that this could give some problems. My question is:
- Would flashing CM9 back worth a shot, or totally useless?
I hope you can help me, and if there isn't a solution, I hope the shop can cover this as I've got warranty for one year and 9 months.
Care to share how you had flashed it at first...
And you can still boot to recovery rite ?
Sent from my GT-I8150 using xda premium
countdown93 said:
Hello,
Recently I've flashed Arco's CM9 version. It all went well for a couple of weeks until today. When I booted my phone, suddenly all apps started crashing and then it rebooted. But, the problem is, it is now stuck on a flashing Samsung logo.
Before I've started this thread, I've read many many similar threads about this, and started a 'rescue operation' by my own by using the tutorials for flashing back a stock rom with ODIN and other possibilities.
Unfortunately, after I've tried twice using ODIN, my phone is still stuck in the Samsung logo loop. I also can't enter Recovery mode, but am able to enter Download mode, as you've probably noticed.
As this is my first Android phone, I've always carefully read the tutorials and disclaimers about possible failures. I'm aware that the maker of the rom is not responsible for this.
Since I tried to flash back to stock android 2.3.6 from CM9 kernel, I've read that this could give some problems. My question is:
- Would flashing CM9 back worth a shot, or totally useless?
I hope you can help me, and if there isn't a solution, I hope the shop can cover this as I've got warranty for one year and 9 months.
Click to expand...
Click to collapse
it happened to my friends phone also, he can go to DL mode but not recovery mode, he flashed a stock rom via odin, but that didnt help, he was still stuck at samsung logo, and about flashing CM9 again, i guess u cant bcoz u cant go to recovery mode, if youve flashed a stock rom again and that didnt work for you too, i guess u need to send to samsung for repair, i remember my friend said it was a hardware problem, good luck
vanir29 said:
it happened to my friends phone also, he can go to DL mode but not recovery mode, he flashed a stock rom via odin, but that didnt help, he was still stuck at samsung logo, and about flashing CM9 again, i guess u cant bcoz u cant go to recovery mode, if youve flashed a stock rom again and that didnt work for you too, i guess u need to send to samsung for repair, i remember my friend said it was a hardware problem, good luck
Click to expand...
Click to collapse
I've read elsewhere that it was a hardware problem that appeared on 1:10 Wonders... I'm really disappointed since this was my first smartphone...
A small question though: Since I've (tried to) flash it back to stock rom, if I bring it back to the shop where I bought it, would they notice that there was another rom, which could give them a reason that I've void the warranty? I really don't want to pay another amount of cash for this (faulty) phone.
Also in reply to andynroid: I've flashed CM9 the first time with CWM, as adviced by Arco68.
Can you still go to recovery ?
Sent from my GT-I8150 using xda premium
countdown93 said:
I've read elsewhere that it was a hardware problem that appeared on 1:10 Wonders... I'm really disappointed since this was my first smartphone...
A small question though: Since I've (tried to) flash it back to stock rom, if I bring it back to the shop where I bought it, would they notice that there was another rom, which could give them a reason that I've void the warranty? I really don't want to pay another amount of cash for this (faulty) phone.
Also in reply to andynroid: I've flashed CM9 the first time with CWM, as adviced by Arco68.
Click to expand...
Click to collapse
well in my friend's case, samsung accept it and repair it, if the stock rom is flash successfully, i think they wont notice that you've flash i custom rom, good luck though
Am I being dense.... but what is 1:10 Wonder???
I saw this also mentioned by Rio S. (I think)....but did not think anything about it.... but, is it HW version??
Where can I see it on device.
Andy....
Guy says in OP...
can't get Recovery!!!
:banghead:
Sent from my GT-I8150 using Tapatalk
irishpancake said:
Am I being dense.... but what us 1:10 Wonder???
I saw this also mentioned by Rio S. (I think)....but did not think anything about it.... but, is it HW version??
Where can I see it on device.
Andy....
Guy says in OP...
can't get Recovery!!!
:banghead:
Sent from my GT-I8150 using Tapatalk
Click to expand...
Click to collapse
Hi...
I wrote in this thread
http://forum.xda-developers.com/showpost.php?p=25616419&postcount=17
The only solution seems to be to flash an Asian rom with multi package.
Sent from my GT-I8150 using Tapatalk
when you try to enter recovery mode, what is the image you first see? is there an image that look like an android? i cant remember the exactly image but if you see that image, i think you must reflash the CWM via odin. Because every time i reflash the stock rom, my recovery mode will gone. So try to reflash CWM via odin. Nothing wrong if you give it a try
irishpancake said:
Am I being dense.... but what is 1:10 Wonder???
Click to expand...
Click to collapse
i think it is one(1) out of ten(10) or 1 is to 10 sgw has a hardware problem, i guess thats what he meant, but isnt it kinda high
Experienced this as well. Just sent it for warranty and they swapped out the motherboard.
alidsd said:
The only solution seems to be to flash an Asian rom with multi package.
Sent from my GT-I8150 using Tapatalk
Click to expand...
Click to collapse
I've heard and read about that, I thought that Rio did that, but it wasn't succesful.
tomatoman23 said:
when you try to enter recovery mode, what is the image you first see? is there an image that look like an android? i cant remember the exactly image but if you see that image, i think you must reflash the CWM via odin. Because every time i reflash the stock rom, my recovery mode will gone. So try to reflash CWM via odin. Nothing wrong if you give it a try
Click to expand...
Click to collapse
I wished I could enter Recovery mode, but the problem is: I can't
. But I also didn't know that if I flash back to stock rom, the recovery would be gone too. Maybe I should reflash CWM via odin. Nice advice.
vanir29 said:
i think it is one(1) out of ten(10) or 1 is to 10 sgw has a hardware problem, i guess thats what he meant, but isnt it kinda high
Click to expand...
Click to collapse
Jup. One out of ten => 10%. Such an error rate may not appear for such a great brand. That is ridiculously high. Even 1% is too high in my opinion.
Deathmax said:
Experienced this as well. Just sent it for warranty and they swapped out the motherboard.
Click to expand...
Click to collapse
Yeah, but what I've heard from others in the Netherlands: they will say that your device has been damaged by water, which isn't protected by warranty. And the bill is equal to a new device, or even more expensive. I hope they're in 'good mood', otherwise I maybe have to search for another device.
Hey Bro... this happen to me a while ago.... but covered by warranty , just simply told them at the SSC that you do an update via Kies and sxxt happen , coz in my place there are cases that the phone hang after update via Kies not only this model , it happen to others model too.
I suggest that you flash it back to stock before you send it back to SSC , without CWM .
cheers
vanir29 said:
i think it is one(1) out of ten(10) or 1 is to 10 sgw has a hardware problem, i guess thats what he meant, but isnt it kinda high
Click to expand...
Click to collapse
My friend!!!
I think you have solved the mystery of 1:10......
but can Rio S. confirm??
I don't have bricked phone....
but I try to understand what is causing these, so to be of some help....
and 1:10 was a puzzle to me, so thank you...
Sent from my GT-I8150 using Tapatalk