Develop Bugs

[Q] Possible bricked wonder?

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

[Q] Xperia play bootup problem.

Ok this kind of problem i haven't seen. I've searched the whole interweb for someone with problem like this.
So. I had restored my phone and setting back to factory settings. Then i downloaded a file manager (ASTRO). The application was running and i locked the phone. I tried to unlock but it did not recognize. Then i tried different buttons everything worked, i just couldnt see anything from the screen.So i removed the battery and tried to reboot. it vibrated normally but nothing on the screen. I waited for couple of hours and THERE! it booted. But little later it did it again. When it does it i press the power button to lock it and the screen flashes. it can only be seen in the dark. It did that many times. I've used update service and i have updated the phone like ten times but still the same. I found out the bootloop by booting it and then plugging it to computer. The computer recognizes it but then i hear the usb removing sound. THE PHONE DOESN'T EVEN BOOT TO THE "Sony Ericsson" SCREEN. I've flashed 4.0.2.A.0.58_EnhancedV2.ftf but it has the same problem. then i flashed 4.0.2.A.0.42_Generic_UK.ftf (4.0.2.A.0.42 is stock) but no. phone is rooted and has custom recovery and bootloader unlocked. This is strange.. never seen this kind of problem. I thought it was some application that causes this but flashing wipes all data, right?
Thanks already. You are better with these than me.

what kind of kernel did u used ?
try flash kernel using stock kernel.

jiprudy said:
what kind of kernel did u used ?
try flash kernel using stock kernel.
Click to expand...
Click to collapse
4.0.2.A.0.58_EnhancedV2.ftf. It was the first one i flashed. Is there a link for stock (4.0.2.A.0.42)?

nomad- said:
4.0.2.A.0.58_EnhancedV2.ftf. It was the first one i flashed. Is there a link for stock (4.0.2.A.0.42)?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=24610138&postcount=1:good:

Fifth fw going. well see...
I've tried these:
R800i_4.0.2.A.0.42_Generic
R800i_4.0.2.A.0.42_Generic_UK
R800i_4.0.2.A.0.58_EnhancedV2
R800i_4.0.2.A.0.58_Generic Hong Kong Trade
R800a_4.0.2.A.0.42_North America flashing

nomad- said:
4.0.2.A.0.58_EnhancedV2.ftf. It was the first one i flashed. Is there a link for stock (4.0.2.A.0.42)?
Click to expand...
Click to collapse
Try this link http://forum.xda-developers.com/showthread.php?t=1589399 for stock rom
You misunderstand, i asked about kernel not rom....what kind of kernel did you used now.

jiprudy said:
Try this link http://forum.xda-developers.com/showthread.php?t=1589399 for stock rom
You misunderstand, i asked about kernel not rom....what kind of kernel did you used now.
Click to expand...
Click to collapse
Please read the post! I already posted him the same link above plus he as been flashing stock roms the kernel's are included in the ftf filesAny custom kernel he had will be lost on flashing ftf!

Ok even my friend has tried to deal with the phone but without a result.
I think it is the bootloader. It may be damaged. Any ideas how can I repair it? I found this Medusa thing. doesn't seem to work.

my Tab3 screen flicking = bricked?

after flashing some ROMs....the screen keeps flicking. Can't do anything to bring it back to life. that's it. real brick

Which Tab 3 is it?
If it is SM-T210 or SM-T210R, and screen is flickering?
If the tab is booting into OS, It isnt bricked.
Chances are have the wrong ROM flashed for your kernel build and device model.
Sent via : Galaxy Tab 3 7.0 SM-T210R

voyagerair said:
after flashing some ROMs....the screen keeps flicking. Can't do anything to bring it back to life. that's it. real brick
Click to expand...
Click to collapse
Hi mate,
if the OS is booting, it's not bricked...
@kwood129 reported having a similar issue, he uses my RocketTab ROM with newest kernel MOD now and reported back, that everything is fine now. Head over to RocketTab thread and have a look if this might help solve your problem... Should work on T210 and T210R.
If you have any questions, just drop me a pm.

voyagerair said:
after flashing some ROMs....the screen keeps flicking. Can't do anything to bring it back to life. that's it. real brick
Click to expand...
Click to collapse
To be real, your device is possibly soft bricked. Repairable, as it boots.
A HARD brick is when your device WON'T BOOT AT ALLL, and needs either JTAG or eMMC repartitioning.

voyagerair said:
after flashing some ROMs....the screen keeps flicking. Can't do anything to bring it back to life. that's it. real brick
Click to expand...
Click to collapse
Happened to me, boot into recovery and install a different rom, everything will be fine

[Q] N7105 board on n7100 screen and body

I already search on google but the thing is i cant find the proper answer,
i have a n7100 broken pcb/mainboard, and n7105 broken screen, can i swap parts and get one working?
thanks.

hackerse7en said:
I already search on google but the thing is i cant find the proper answer,
i have a n7100 broken pcb/mainboard, and n7105 broken screen, can i swap parts and get one working?
thanks.
Click to expand...
Click to collapse
You can try and let us know no harm trying though as both already faulty or N7105 partially faulty. I guess the board layout it's the same though just some minor hardware difference.

frankensteinote2
soralz said:
You can try and let us know no harm trying though as both already faulty or N7105 partially faulty. I guess the board layout it's the same though just some minor hardware difference.
Click to expand...
Click to collapse
Ok, i did that and, it went kind off well, i swap the n7105 board and charging port, to n7100 screen and chassis, and it boots, but my battery was too low, i let it charge all night, today it wont pass n7105 logo but it enters in odin mode(sadly, not in recovery ) later i will flash a firmware via odin and hope to recover him, now i need help from a diferent angle, i dont know the version i was running on n7105 since it was a long time ago, i want to know what should i do before get my hands in custom roms and all of that,
BACKUP EFS
how do i backup everything,
and most important what version should i flash via odin since i dont want to get SDS
Thank you soralz for the answer

hackerse7en said:
Ok, i did that and, it went kind off well, i swap the n7105 board and charging port, to n7100 screen and chassis, and it boots, but my battery was too low, i let it charge all night, today it wont pass n7105 logo but it enters in odin mode(sadly, not in recovery ) later i will flash a firmware via odin and hope to recover him, now i need help from a diferent angle, i dont know the version i was running on n7105 since it was a long time ago, i want to know what should i do before get my hands in custom roms and all of that,
BACKUP EFS
how do i backup everything,
and most important what version should i flash via odin since i dont want to get SDS
Thank you soralz for the answer
Click to expand...
Click to collapse
What if the phone is off and you plug in the charger? Is the battery icon appears on the screen and indicates it's charging?

soralz said:
What if the phone is off and you plug in the charger? Is the battery icon appears on the screen and indicates it's charging?
Click to expand...
Click to collapse
yes, before i begin all i let the grenn battery icon became full, then i flahed stock 4.1.2 from sammobile.
in odin everything went well sucessfuly flashed but when he reboots apears n7105 logo and it shuts right off,
so i tried remove battery and turn on again nothing, it doest enter in recovery mode but it enters in odin mode only and flash counter keeps increasing everytime i flash, so i flashed some recoveries trough odin none of them worked escept philz touch recovery, it enters and i wipe it all reboot and its all the same, tried flash a custom cm11 rom and it says this from is not for your device your device is a "t03g",
now i dont know what to do

Hey, try another recovery, and make sure it's an N7105 one. A common problem, I've had it twice, appearing as a toro, but my phone is maguro. Fixed it by installing the correct recovery, after installing a wrong, a toro recovery.

jonttuv said:
Hey, try another recovery, and make sure it's an N7105 one. A common problem, I've had it twice, appearing as a toro, but my phone is maguro. Fixed it by installing the correct recovery, after installing a wrong, a toro recovery.
Click to expand...
Click to collapse
since then i flashed a n7100 rom and it booted flawesly, no fc's nothing works remarcably well but the problem now is the unknown baseband,i will try flash a n7105 but i dont think it will work cause i do have a nandroid backup from the n7105 from the time when he was working, i restored it and is the same as flash stock n7105 trough odin it gets stucked on n7105 logo.

hackerse7en said:
since then i flashed a n7100 rom and it booted flawesly, no fc's nothing works remarcably well but the problem now is the unknown baseband,i will try flash a n7105 but i dont think it will work cause i do have a nandroid backup from the n7105 from the time when he was working, i restored it and is the same as flash stock n7105 trough odin it gets stucked on n7105 logo.
Click to expand...
Click to collapse
i tried installing n7105 recovery and the result was, stuck on bootloop, it doesnt boot to the rom nor to the recovery, only download mode.
while on n7100 recovery and rom it flashes and boot, i think i will flash n7100 stock trough odin cause he seems more like a n7100 than a n7105, but im scared to brick it (

hackerse7en said:
I already search on google but the thing is i cant find the proper answer,
i have a n7100 broken pcb/mainboard, and n7105 broken screen, can i swap parts and get one working?
thanks.
Click to expand...
Click to collapse
its easy, you must change only Displayframe, LCD with Glasses in other Displayframe ! you takes your broken display n7105 Displayframe and you need your full ok n7100 Display, you take out from n7100 display lcd with glasses and you makes it in n7105 Displayframe, sorry for bad englisch..

links and loop

hi guys, i wrote here because all links are expired. i have a very big problem with my ace 2 because it is in loop at the logo screen. it's happen when i tried to root the phone with odin. i tried and tried with the same file and with other files: rom, kernel etc.. but the result is the same.
someone can help me?

Desmojack said:
hi guys, i wrote here because all links are expired. i have a very big problem with my ace 2 because it is in loop at the logo screen. it's happen when i tried to root the phone with odin. i tried and tried with the same file and with other files: rom, kernel etc.. but the result is the same.
someone can help me?
Click to expand...
Click to collapse
Is it the Android boot screen (i.e. Samsung/Cyanogenmod) or the Bootloader screen, that shows up first thing no matter which ROM you have?
-Bhavesh

bhaveshparajapat said:
Is it the Android boot screen (i.e. Samsung/Cyanogenmod) or the Bootloader screen, that shows up first thing no matter which ROM you have?
-Bhavesh
Click to expand...
Click to collapse
I started with the stock rom, and i didn't be able to install new roms because at the first flash for root permission with odin, my phone restart with the loop. and the new files i flashed with odin gave me the same loop.

now, i think that the only solution is reset all. where is the right link? active link!

Yup
Desmojack said:
now, i think that the only solution is reset all. where is the right link? active link!
Click to expand...
Click to collapse
I think so too. Try using a three part firmware, I can't just provide the .pit because you'll need the modem file too.
Try using a three part firmware if a single file one doesn't work
Odin Single File = i8160XXXXX.tar.md5 which goes in PDA
Odin Three part = Modem, PDA and PIT (This repartitions your device back to factory so you'll lose all data and partition changes you've made!!))
--Bhavesh

yes,this is a good idea..but where i can find the three files for back to factory ?

Desmojack said:
yes,this is a good idea..but where i can find the three files for back to factory ?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2340849
The XXMF1 firmwares might have all three files. I don't know but from what I can collect it seems to be the most likely. The test XXMC8 and MB4 firmwares also contain three files, but, they're test firmwares, so I wouldn't recommend it - and you should flash stable firmware afterwards (after the phone reboots and you see the 'PASS' message on the computer and the phone has started to boot)
Good luck!

i'm very stupid... the only problem was battery low.. tnx anyway!

Desmojack said:
i'm very stupid... the only problem was battery low.. tnx anyway!
Click to expand...
Click to collapse
No problem! Try not to flash if you have less than 70% or so battery left as a general rule