Database Develop

[Q] Stuck at boot (bricked?)

When starting my HTC Dream it stays on the boot splash screen and does nothing. Attempting to go into the bootloader or recovery fails. This happened directly after installing DangerSPL, I believe I might have accidentally messed up when flashing its radio and not have done so at all, although I did downgrade the firmware. Is there any possible solution?

incompatible radio. Thats why its called dangerSPL.

You have bricked your phone, only way is jtag... http://forum.xda-developers.com/showthread.php?t=591048

shadowch31 said:
You have bricked your phone, only way is jtag... http://forum.xda-developers.com/showthread.php?t=591048
Click to expand...
Click to collapse
Yes, I've read of the infamous JTAG fix. I've decided that I could either pay for a fix, probably by someone here since they would probably know what they're doing, as I'm sure I'd mess up in the process since I don't have much experience with soldering small devices or even opening them up. Or if that isn't an option I might just donate it to someone who would like to mess with the bricked thing.

gralco said:
Is there any possible solution?
Click to expand...
Click to collapse
code DOT google DOT com/p/android-roms/wiki/Unbrick
(Sorry, as a new user, I can't post outside links without 8 posts first...) Hopefully no mods see this is a deliberate bypass of their "security" I assure all, I am not a spammer. Honestly trying to help here =P
This looks possible. I mean, with a bricked phone, it's worth a shot? Let me know if anything works out!

DoogleDood said:
code DOT google DOT com/p/android-roms/wiki/Unbrick
(Sorry, as a new user, I can't post outside links without 8 posts first...) Hopefully no mods see this is a deliberate bypass of their "security" I assure all, I am not a spammer. Honestly trying to help here =P
This looks possible. I mean, with a bricked phone, it's worth a shot? Let me know if anything works out!
Click to expand...
Click to collapse
... you should also read the comments of the page you are linking to .
If you have a *real* brick you are stuck at the G1 screen and all software based tricks will not work, JTAG is the only chance for you.

Just cause you have a hard bricked phone, doesn't mean all tips and tricks don't work. My friend had a bricked mytouch slide and couldn't access recovery or anything of the sort, but using my boot.img, and other essentials and adb, we could unbrick the phone. Not saying that link will work... since I hadn't realized recovery was not accesible, but I'm just pointing out that hard bricked does not mean you only have one way out, if that.
Sent from my Sapphire/Dream using XDA App

bionic ... new chalange

Ok guys ... this is the problem ...:crying:
I have (had) a Droid Bionic running ics leak 232 in Brazil (GSM/UMTS ... thanks to xda developers - "bionic in t mobile" thread).
While messing around with the phone connected to linux (baaad idea) at some point I deleted the bootloader ("happy finger" + lack of knowledge os linux).
Now, my phone doesnt power up and RSD Lite doesnt recognize it when connected but, when I connect it to the PC, a green light lits at the top right corner of the phone and Windows recognize it, at the device manager, as a OMAP4430 USB under TI Board tab. This leads me to think that some kind of life still exists down there or, the hardware is alive and waiting for the right software.
After a long quest for a solution, I found this: "forum.gsmhosting.com/vbb/f634/unbrick-dead-samsung-gt-i9250-galaxy-nexus-gt-i9100g-via-usb-cable-freeeeeeeeeeee-1465412/index9.html".
Now I think this is the way out of this mess (is the same hardware, OMAP platform from Texas Instrument), if exists any, but this was made for Samsung, by Samsung technicians, and doesnt apply to Motorola. :crying: again.
So, is there anyone who can help me, or have any idea of what can be done (other than trow it away or use it as a paper weight)?
Any help would be most appreciated.
Regards

I saw you haven't had any replies yet. My roommate had a similar problem, he managed to mount his system partition automatically and thought his SD card was partitioned into 10 or more partitions.
So he reformated the mount and had a dead phone right after, said he only got a small white light on his notification light when plugged in.
I didn't get a chance to check it out before he took it to Verizon for a refurb, so sadly I'm not much help. Just thought I'd input anything I knew since you still had an empty thread. Hope it comes back alive!
Sent from my kitchen toaster.

Have you tried using the command line version of moto-fastboot? It might work, but might not work... I think you need to boot into fastboot mode, but I could be wrong... Either way it's worth a try.
Also, does anything happen when you try to hold down the vol+ and VOL- buttons when powering on the phone?
Sent from my XT894 running ICS

its dead
danifunker said:
Have you tried using the command line version of moto-fastboot? It might work, but might not work... I think you need to boot into fastboot mode, but I could be wrong... Either way it's worth a try.
Also, does anything happen when you try to hold down the vol+ and VOL- buttons when powering on the phone?
Sent from my XT894 running ICS
Click to expand...
Click to collapse
Thank you for your answer danifunker;
The phone is dead. Pressing buttons does nothing. The only thing that happens is to lit the notification green light at the top right corner of the screen WHEN a plug it in my PC and windows keep telling me this is a unknown device. I unsuccessfully used OMAPFlash, but installing the usb drives that came with it, when I plug it to the PC, windows device manager shows me a new device "OMAP4430 USB" under a new tab "TI Board" , whitch is not recognized by RDS lite or adb or fastboot. Is only recognized by OMAPFlash. If you dont know about OMAPFlash, I found it here http://forum.xda-developers.com/showthread.php?t=1701471 , but this procedure is for a Samsung, witch uses the same platform (OMAP4430), but I dont have the right configurations for the Droid Bionic.

Just the same
chrisp6825 said:
I saw you haven't had any replies yet. My roommate had a similar problem, he managed to mount his system partition automatically and thought his SD card was partitioned into 10 or more partitions.
So he reformated the mount and had a dead phone right after, said he only got a small white light on his notification light when plugged in.
I didn't get a chance to check it out before he took it to Verizon for a refurb, so sadly I'm not much help. Just thought I'd input anything I knew since you still had an empty thread. Hope it comes back alive!
Sent from my kitchen toaster.
Click to expand...
Click to collapse
Thank you for your interest.
If you have any further notice about your roommate problem, please let me know.
And, if you manage to post a reply from your kitche toaster, I am sure you will be able to help in this problem. looking forward for that. :laugh:

pjcw said:
Thank you for your interest.
If you have any further notice about your roommate problem, please let me know.
And, if you manage to post a reply from your kitche toaster, I am sure you will be able to help in this problem. looking forward for that. :laugh:
Click to expand...
Click to collapse
Can you explain exactly how you deleted the bootloader off of the Bionic? Knowing EXACTLY (what you ran, what you typed) what you did will help us help you.
As an aside, I had no idea there was a SGSII-OMAP variant, but I am not big on the Samsung phones, just assumed they've only been using their own SoCs for a while now...

Hi podspi.
Sorry for the delay.
As a matter of fact, wasnt me that bricked the phone. A friend o mine tryed to flash a gelly beam version, and did it via Fastboot,, under Linux (of witch I know almost notingh).
He told me that the problem was that he made:
fastboot erase mbm
and then
fastboot reboot bootloader
and so the bootloader was lost. He missed a step.
Any help will be greatly aprecieted.
Regards

IOW, since the mbm has been erased, and the mbmflashable hasn't been flashed, there is no way to get it into the bootmenu sceen anymore, right?
Hmmm. Let me ask some other folks too.
Sent from my ASUS Transformer Infinity Running Tapatalk.

I wonder if a factory cable would work to get it to flash mode? Why would you even mess with the bootloader trying to install ICS? You do that through recovery, not fastboot.

I was on ICS ... This was an attempt to get it to JellyBeen ... I, also, dont know why. I was perfectly happy with ICS working in GSM/WCDMA. This is why I am so sad ... It was a very stupid thing to do ... As a matter of fact, I will get a factory cable, but I dont think this is gonna help. Anyways, I am keeping it by side to remember me not to mess with things that are working fine. I'm kind of losing hope that it can fixed.
Regards

pjcw said:
I was on ICS ... This was an attempt to get it to JellyBeen ... I, also, dont know why. I was perfectly happy with ICS working in GSM/WCDMA. This is why I am so sad ... It was a very stupid thing to do ... As a matter of fact, I will get a factory cable, but I dont think this is gonna help. Anyways, I am keeping it by side to remember me not to mess with things that are working fine. I'm kind of losing hope that it can fixed.
Regards
Click to expand...
Click to collapse
I think we need to figure out how you flash mbm back onto there. Actually, I think it's mbmloader that you need on there...
mbm = Motorola Boot Manager (?) maybe.
After reading this page: http://omappedia.org/wiki/Bootloader_Project
I believe, mbm = uboot, mbmloader = x-loader
Just found this page... http://www.droid-developers.org/wiki/How_to_load_mbmloader_from_SD_card
download the SBF and grab the mbmloader for ICS. See if you can get a little further...

SamuriHL sHouse of Bionic restored mine when all I could get was fastboot.
Sent from my DROID BIONIC using xda premium

It won't help this. It needs to be flashed at the omap level and since moto isn't about to release the configuration files for the Bionic you can consider this one permanently bricked.
Sent from my Xoom using Tapatalk 2

I tend to agree with SamuriHL. I was thinking that the configuration souldn't be so diferent than others (like Samsung) that uses the same platform (omap). I know that it's naive, but what else could I do. Also, I need the signed files for x-loader and u-boot, of witch I think danifunker is right, this means mbm and mbmloader, that I have, but they came in bin format and not image format (.img). I will try to convert them to .img, but I am at the end of my resources (not that they are so many), and will give up shortly. At this point (giving up), I will buy another cellphone AND IT WONT BE A MOTOROLA, Probably a HTC or a Samsung. But I will keep Bionic at my desktop, as a paperweight, to remind me how I liked it, how I mess things up.
Anyways, if I manage to solve this problem, I will post here, and I wish to thank everyone that spare their time to try to help people. If anyone have any suggestion, I'll be glad to follow.

If you modify them in any way they'll no longer be signed and won't work. Someone else already went through several weeks of trying to fix their phone that had similar issues. He's well connected and still couldn't get the necessary files. Don't necessarily give up on Moto, though...it's not their fault we're stuck with locked bootloaders. Blame VZW for that one. Even Samsung was forced to lock the S3 on VZW. Things may change some day. We'll have to wait and see.

You can always get RAZR i with the unlockable bootloader! that might make things a bit easier...

IT'S DONE!!!!!!!!!
IT'S DONE ....... IT IS ALIVE AGAIN :highfive:
Guys. My phone is alive again. Thanks to FRAGULINA and PICGRABBER for their unvaluable help. It is now running GSM with data enabled (3G) with ICS 232, rooted, thanks to FRAGULINA and HTCFlyerX ( http://forum.xda-developers.com/showthread.php?p=31101192&highlight=build+prop#post31101192).
Well, I'm attaching 2 zip files. One is omapflash and the other is "THE FILES", and instructions on the "release_notes.txt". This works on LINUX.
And works like a charm. Took me (much) less than 5 minutes to get me from a dead phone to bootloader fastboot. And the rest is history. Well known procedures.
Thanks to all of you that helped or tryed to help.
Enjoy.
To those who have an interest in new challanges (as I know you are), i'm opening a new quest and would appreciate your thoughts.
I have at hand an atrix 2 and I want to find where in hell is the subsidy code writen at and how can I read it. This new quest will be at the proper location at the atrix 2 forum.
I think we won this challange. Lets go for another.
Any doubts I am available to help.
Regards.

Holy.....uh, well, WOW! I'm in awe here on this one. WELL DONE!!!!!!!

SamuriHL said:
Holy.....uh, well, WOW! I'm in awe here on this one. WELL DONE!!!!!!!
Click to expand...
Click to collapse
Can we use this method to flash any firmware to the phone? Lets say you load the latest ICS, maybe we use this method which restores the most original bootloader to the phone and then flash to any version?
Which version did you fastboot to?

pjcw said:
IT'S DONE ....... IT IS ALIVE AGAIN :highfive:
Guys. My phone is alive again. Thanks to FRAGULINA and PICGRABBER for their unvaluable help. It is now running GSM with data enabled (3G) with ICS 232, rooted, thanks to FRAGULINA and HTCFlyerX ( http://forum.xda-developers.com/showthread.php?p=31101192&highlight=build+prop#post31101192).
Well, I'm attaching 2 zip files. One is omapflash and the other is "THE FILES", and instructions on the "release_notes.txt". This works on LINUX.
And works like a charm. Took me (much) less than 5 minutes to get me from a dead phone to bootloader fastboot. And the rest is history. Well known procedures.
Thanks to all of you that helped or tryed to help.
Enjoy.
To those who have an interest in new challanges (as I know you are), i'm opening a new quest and would appreciate your thoughts.
I have at hand an atrix 2 and I want to find where in hell is the subsidy code writen at and how can I read it. This new quest will be at the proper location at the atrix 2 forum.
I think we won this challange. Lets go for another.
Any doubts I am available to help.
Regards.
Click to expand...
Click to collapse
This is unbelievable. After talking with you on Gtalk, I thought this was a permanent brick. Thanks for the files...I have a guy on gtalk right now who can benefit from these.

[Q] PLS HELP : Can't Turn on my Device

After unlocking my phone using HTCDEV,
I've tried to root it using "HTC_QuickRoot_1.1.13_Release",
and it claimed something like the flash img not compatible
with it and then my phone shut down (!)
now I can't turn it on for a couple of hours (theres no LED btw).
Please Help! (Iv'e searched in the threads for some problems declaimed like mine and found nothing like)
Thanks in advanced guys!

nyg85 said:
After unlocking my phone using HTCDEV,
I've tried to root it using "HTC_QuickRoot_1.1.13_Release",
and it claimed something like the flash img not compatible
with it and then my phone shut down (!)
now I can't turn it on for a couple of hours (theres no LED btw).
Please Help! (Iv'e searched in the threads for some problems declaimed like mine and found nothing like)
Thanks in advanced guys!
Click to expand...
Click to collapse
Well, one word : Service :laugh:

this is the only way huh?

nyg85 said:
this is the only way huh?
Click to expand...
Click to collapse
I guess.......and next time when you wanna root etc. just have the patience and read everything that is written here.
Never the less some phones are more durable in that matter ( i don't know why ). Some phones are like butter, 1st attempt and you are rooted. And with another you sweat like a pig and even then you can't do it right :laugh:

well
Well,
I hope it'll get better
thanx

Before bringing your phone to service you could try:
- a factory reset. Maybe the unsuccessfull rooting attempt has messed up something you can fix this way.
- flashing a RUU and see if the issue remains. This usually sorts out...

[Q] Stuck on Motorola logo help please

Complete newb here, i haven't done any development work or even tried rooting or flashing my phone. Over the last couple of days, apps have started crashing as soon as i open them, and then yesterday i rebooted the device and it won't go past the Motorola logo. I've searched through a few threads and there isn't a simple enough answer or procedure to follow to get this working. Also most similar issues have USB debugging on etc, whereas i have no developer settings on at all. Any help would be greatly appreciated

You didn't search enough for an answer i see. But okey for the lazy i will help you, no offense
Can u access (AP)fastboot and can u boot into recovery from fastboot? Have a look at the link in my signature on how to get in fastboot and then in recovery.

Hazou said:
You didn't search enough for an answer i see. But okey for the lazy i will help you, no offense
Can u access (AP)fastboot and can u boot into recovery from fastboot? Have a look at the link in my signature on how to get in fastboot and then in recovery.
Click to expand...
Click to collapse
Literally my first post mate, how about you cut me some slack. I spent about 4/5 hours searching last night and even took the phone apart. If there is an answer please point me in the direction of it. There are countless threads where the issue is the user has loaded their own ROM or flashed the device already or something like that, which caused the system files to become corrupted. But as i mentioned i have done nothing to the device except for a data wipe a few months back, and there doesn't seem to be any threads where this just happened out of nowhere. I have booted into fastboot, recovery and done the partition cache & data wipe and rebooted, that was my first step.

merculesblud said:
Literally my first post mate, how about you cut me some slack. I spent about 4/5 hours searching last night and even took the phone apart. If there is an answer please point me in the direction of it. There are countless threads where the issue is the user has loaded their own ROM or flashed the device already or something like that, which caused the system files to become corrupted. But as i mentioned i have done nothing to the device except for a data wipe a few months back, and there doesn't seem to be any threads where this just happened out of nowhere. I have booted into fastboot, recovery and done the partition cache & data wipe and rebooted, that was my first step.
Click to expand...
Click to collapse
Hoho, okey, my words have offended you and I am sorry for that.
I can't simply give u an answer if you only said that it doesn't boot and u looked for something to fix it. There are many fixes for many sorts of problems. Also if I knew u have tried to wipe the cache and data I would give u a totally different answer. But u had not mentioned anything about what u had done to try to fix it.
For now, if even a data/factory reset from recovery didn't work I suggest u need to try to reflash the whole stock firmware. See in my signature the link to an index thread about the phone. U can find there the ways to reflash to your stock firmware and hopefully fix your issue.
If u need some more help to flash stock firmware, don't hesitate to ask here.
Hazou
Verstuurd van mijn GT-P5110

Hazou said:
Hoho, okey, my words have offended you and I am sorry for that.
I can't simply give u an answer if you only said that it doesn't boot and u looked for something to fix it. There are many fixes for many sorts of problems. Also if I knew u have tried to wipe the cache and data I would give u a totally different answer. But u had not mentioned anything about what u had done to try to fix it.
For now, if even a data/factory reset from recovery didn't work I suggest u need to try to reflash the whole stock firmware. See in my signature the link to an index thread about the phone. U can find there the ways to reflash to your stock firmware and hopefully fix your issue.
If u need some more help to flash stock firmware, don't hesitate to ask here.
Hazou
Verstuurd van mijn GT-P5110
Click to expand...
Click to collapse
Cheers mate, i'll give it a go, but i've never done anything like flashing before. I'll see how i get on

merculesblud said:
Cheers mate, i'll give it a go, but i've never done anything like flashing before. I'll see how i get on
Click to expand...
Click to collapse
As long as u read everything carefully u will be good to go. Just one reminder, use the latest stock firmware JB(or u can get more problems). And rsd-lite 6.1.x
Verstuurd van mijn GT-P5110

Hazou said:
As long as u read everything carefully u will be good to go. Just one reminder, use the latest stock firmware JB(or u can get more problems). And rsd-lite 6.1.x
Verstuurd van mijn GT-P5110
Click to expand...
Click to collapse
So, this is all brand new to me. I'm using this guide http://forum.xda-developers.com/showthread.php?t=1974568
The firmware is from here - http://sbf.droid-developers.org/phone.php?device=13
- I chose the 4.1.2 UK Retail as i purchased the phone through Virgin Mobile (UK)
Drivers and RSD 6.1.6 are now installed so will try now
Is everything right so far?

Seems to have worked, but it seems a bit different and some apps like hangouts are unavailable now, even though i had them before. The firmware i chose was UK Retail, however i am not 100% that this is the one to use as i bought it through Virgin Mobile (UK).

Hangouts should work just fine. Strange.
But nice that all works fine now
Sent from my XT890 using XDA Free mobile app

After a restart, my moto razr i is stuck on Android is upgrading...
Hazou said:
Hangouts should work just fine. Strange.
But nice that all works fine now
Sent from my XT890 using XDA Free mobile app
Click to expand...
Click to collapse
Hi, I saw above post and happy to read that your problem is solved so I writting with my problem on your post, just getting hope that mine will work too.
Actually I have also ''NIL'' knowledge about all this software/ quote language etc
My issue is; my Moto Razr i is just stuck on '' Android is upgrading '' than shows ''Starting Apps'' thn nothing happen n same things repeats ... couple of hours back it was saying ''finishing boot'' also but now it is just giving this error '' Android is upgrading '' than shows ''Starting Apps'' thn nothing happen n same things repeats
Please I want to request if you are about to guide anything in tough language please consider that I am completely unknown to all the setups and stuff... just if you can help sharing step by step process and also post specific link/software to download (if needed) and how to download and other details in simple guidance plz plz plz.
One more point I tried to chat with Motorola chat service and they suggested me to power off it first but i m pressing vol- and vol + and power button but phone is quickly restarting on its own... i m even unable to go on boot as they suggested me to do so.
Thanks a lot to ''my upcoming angel'' in advance
Hope one can help me at earliest.

opened new thread

Hazou said:
Hangouts should work just fine. Strange.
But nice that all works fine now
Sent from my XT890 using XDA Free mobile app
Click to expand...
Click to collapse
Im having the same issue described on this thread.
My phone doesnt start, it stays at the logo screen. I've tried to recover, factory reset and nothing worked. I have access to the (AP)fastboot screen.
Later then i saw this thread, i've did everything as described at your tutorial, tried all the versions of the RSD Lite (6.1.4, 6.1.5, 6.1.6), it cant detect my phone.
I've tried in two different PCs, tons of different USB ports, running as administrator, compatibility mode...the PC tells me that the USB is connected, but the RSD Lite doesnt recognise it.
I've tried using these two options of motorola drivers:
- motohelper_2.1.40_driver_5.5.0.exe (that i found at your post)
- MotorolaDeviceManager_2.4.5.exe (found another similar tutorial on the internet)
Am i missing something?
I would really appreciate any help.
Thanks!

Mootl3y said:
Am i missing something?
Click to expand...
Click to collapse
did you boot first into Fastboot-mode before you connect to pc?
1. Install Driver + RSD Lite
2. Boot into fastboot + connect USB
3. Start RSD Lite

5m00v3 said:
did you boot first into Fastboot-mode before you connect to pc?
1. Install Driver + RSD Lite
2. Boot into fastboot + connect USB
3. Start RSD Lite
Click to expand...
Click to collapse
Yep. Thats exactly what i did.
I tried only using Windows 8.1. Is it compatible?
I will test on a win7 PC later.
UPDATE:
Worked RSD Lite on Win7, it found my phone. I belive RSD Lite doesnt work on Win 8.1 (at least on my PC and notebook).
I believe my firmware version is this one:
Android 4.1.2 Blur_Version.982.50.29002.XT890.Vivo.en.BR Vivo Brasil 537.6 MiB
Can i use the Retail version without problems? (this one: Android 4.1.2 Blur_Version.982.50.29.XT890.Brasil.en.BR Retail Brasil 532.8 MiB)
Thanks!

Finally got my phone working again!
I got it running RSD Lite 6.1.6 on Win 7 and used the same Firmware version that i had (in my case: Android 4.1.2 Blur_Version.982.50.29002.XT890.Vivo.en.BR Vivo Brasil 537.6 MiB), not the Retail one.
Also used the MotorolaDeviceManager_2.4.5.exe that i got from Motorola website.
My phone now is up and running like charm, no apps or configs lost, everything seems perfect (and also a little bit faster). Not sure what caused my issue, did nothing but normal use.
I hope everyone with the same problem can find this easy solution and follow the right steps (and maybe avoid Win8 to do the process).
Thank you guys for all the information :good:!

Good it is solved. It can happen to anyone. Just a small coruption or miss configuration can take out the android system. Luckily this almost never happens and u were just unfortunate.
Sent from my XT890 using XDA Free mobile app

[Q] Kernel mess up or what?

Hi peep's!
Hope someone can help me. I've been installing lots of roms and found one i liked but then i got too big for my boots (i think). I decided to try the Miui v4 rom yesterday and it was ok apart from swap support so i thought i'd be clever and install the Kernel from "Super Stock". After searching i found it was called "Thunderkernel 2.2". So i installed it via cwm and it booted to a black screen.
I've now tried everything with odin. It detects the phone if i take battery out, hold "vol up + down, home and power and put battery in but it sticks at setup connection. I can even unplug the phone and plug back in and it recognises it after doing the battery trick but still sticks at setup connection. I've tried reinstalling drivers, tried all the odins and shut down everything that may interfere with com's but to no avail. I thought a wrong kernel would at most stop the rom from booting, i never dreamed it would hard brick my phone.
So is this the end of my ace? is it worth me buying a usb jig?

This is pretty much what happened to me last year. I would advise the users to stay away from miui ROM as they may cause problem with some phone. Your device is bricked . jig may fix it but it depends on your luck

Falcon G said:
This is pretty much what happened to me last year. I would advise the users to stay away from miui ROM as they may cause problem with some phone. Your device is bricked . jig may fix it but it depends on your luck
Click to expand...
Click to collapse
I pretty much thought that'd be the case, i suppose i may as well try the jig as they're only cheap. Wish i'd just stuck with super stock. I was actually enjoying the ace for the first time it wasn't just a phone to me, at stock it was very limited. Oh well . Picked up an xperia m now but would be nice to get the ace working for my 3 sim. I'll post if it works or not, incase anyone else runs into the same problem. Thanks for the reply!

Way333 said:
I pretty much thought that'd be the case, i suppose i may as well try the jig as they're only cheap. Wish i'd just stuck with super stock. I was actually enjoying the ace for the first time it wasn't just a phone to me, at stock it was very limited. Oh well . Picked up an xperia m now but would be nice to get the ace working for my 3 sim. I'll post if it works or not, incase anyone else runs into the same problem. Thanks for the reply!
Click to expand...
Click to collapse
Hmm yeah I felt the same way. It really sucks that I installed a bad rom.
All the best though. And yeah do post your results here [emoji6]

Way333 said:
Hi peep's!
Hope someone can help me. I've been installing lots of roms and found one i liked but then i got too big for my boots (i think). I decided to try the Miui v4 rom yesterday and it was ok apart from swap support so i thought i'd be clever and install the Kernel from "Super Stock". After searching i found it was called "Thunderkernel 2.2". So i installed it via cwm and it booted to a black screen.
I've now tried everything with odin. It detects the phone if i take battery out, hold "vol up + down, home and power and put battery in but it sticks at setup connection. I can even unplug the phone and plug back in and it recognises it after doing the battery trick but still sticks at setup connection. I've tried reinstalling drivers, tried all the odins and shut down everything that may interfere with com's but to no avail. I thought a wrong kernel would at most stop the rom from booting, i never dreamed it would hard brick my phone.
So is this the end of my ace? is it worth me buying a usb jig?
Click to expand...
Click to collapse
Where did you find the Thunderkernel 2.2?...
@Falcon G @Way333 AFAIK there is NOT Thundebolt kernel for GT-S5830 but rather GT-S5830i
That means that you flashed an INCOMPATIBLE KERNEL!!! if you flasehd the thunderboltkernel 2.2
Thunderboltkernel is only for GT-S5830i be carefull with it mates!

Viper The Ripper said:
Where did you find the Thunderkernel 2.2?...
@Falcon G @Way333 AFAIK there is NOT Thundebolt kernel for GT-S5830 but rather GT-S5830i
That means that you flashed an INCOMPATIBLE KERNEL!!! if you flasehd the thunderboltkernel 2.2
Thunderboltkernel is only for GT-S5830i be carefull with it mates!
Click to expand...
Click to collapse
Yeah i thought it strange! All things seemed to add up to it being the wrong kernel. Went wrong after kernel flash was fine b4. If the rom wasn't gonna work with a kernel for the device it wouldn't brick the phone would it, the rom just wouldn't boot, unless the kernel is the wrong one for the device. Thanks for clearing that up! I'm usually good with studying first and not making mistakes.Oh well live and learn.

Viper The Ripper said:
Where did you find the Thunderkernel 2.2?...
@Falcon G @Way333 AFAIK there is NOT Thundebolt kernel for GT-S5830 but rather GT-S5830i
That means that you flashed an INCOMPATIBLE KERNEL!!! if you flasehd the thunderboltkernel 2.2
Thunderboltkernel is only for GT-S5830i be carefull with it mates!
Click to expand...
Click to collapse
Hi I didn't flashed the thundrbolt kernel.I just flashed this Rom. http://forum.xda-developers.com/showthread.php?t=2280553&page=25
It gave me an error while flashing. I even wiped completely and then flashed another cm11 Rom. But when I rebooted it just became dead

@Falcon G @Viper The Ripper
Ok I received the jig and It never worked. I tried the standard way and I tried doing all sorts of things but to no avail.
A few days ago I found a guide to a procedure for the s5570 (below) which blames drivers for the "setup connection" error and I thought the same would be applicable to the ace. I know the procedure well now as I've done it so many times and all goes well until the point where the odin drivers are supposed to configure, they never do. The guy who wrote the guide no longer responds as he changed phones.
Several people reported success with their s5570's. I wondered if anyone here may be familiar with the procedure and able to help?
http://androidforums.com/threads/tutorial-unbrick-mini-s5570-bricked-with-black-screen.407866/

Way333 said:
@Falcon G @Viper The Ripper
Ok I received the jig and It never worked. I tried the standard way and I tried doing all sorts of things but to no avail.
A few days ago I found a guide to a procedure for the s5570 (below) which blames drivers for the "setup connection" error and I thought the same would be applicable to the ace. I know the procedure well now as I've done it so many times and all goes well until the point where the odin drivers are supposed to configure, they never do. The guy who wrote the guide no longer responds as he changed phones.
Several people reported success with their s5570's. I wondered if anyone here may be familiar with the procedure and able to help?
http://androidforums.com/threads/tutorial-unbrick-mini-s5570-bricked-with-black-screen.407866/
Click to expand...
Click to collapse
Hi I couldn't even get my phone to get recognized in the devices and printers menu. I don't really think it could be done with samsung drivers.
But hey did your PC recognized your device?

Way333 said:
@Falcon G @Viper The Ripper
Ok I received the jig and It never worked. I tried the standard way and I tried doing all sorts of things but to no avail.
A few days ago I found a guide to a procedure for the s5570 (below) which blames drivers for the "setup connection" error and I thought the same would be applicable to the ace. I know the procedure well now as I've done it so many times and all goes well until the point where the odin drivers are supposed to configure, they never do. The guy who wrote the guide no longer responds as he changed phones.
Several people reported success with their s5570's. I wondered if anyone here may be familiar with the procedure and able to help?
http://androidforums.com/threads/tutorial-unbrick-mini-s5570-bricked-with-black-screen.407866/
Click to expand...
Click to collapse
Ouh!! , I'm sorry mate

Falcon G said:
Hi I couldn't even get my phone to get recognized in the devices and printers menu. I don't really think it could be done with samsung drivers.
But hey did your PC recognized your device?
Click to expand...
Click to collapse
Sorry m8 been real busy. Yeah my pc recognizes it but i have to hold all the buttons down and slip in the battery. Comes up yellow in the coms box in odin and shows in the devices and printers menu without the caution sign. I can do that whole process but it's just the odin drivers part that doesn't happen for me. So still sits on setup connection It was a long shot but worth a try
I wish now i'd never strayed from here. I used google to find that kernel. If i'd have never done that i wouldn't be in this situation!