Related
Long story short;
its dead. Its refusing to charge (the charge screen comes on when its off, but it doesnt actually charge)
Not going into download, or recovery, or turning on at all.
Managed to get into download mode after trying to charge it but my PC isnt recognising it.
I tried out Honeycomb, followed the steps to flash back, tried out Overcome Hermes, no problem. Flashed CM7, no problem. Tried to restore my nandroid for CM7, thats when this started.
Any advice?
And apologies if there has been a similar thread to this, I searched but i couldnt find any threads quite like this.
GANJDROID said:
Long story short;
its dead. Its refusing to charge (the charge screen comes on when its off, but it doesnt actually charge)
Not going into download, or recovery, or turning on at all.
Managed to get into download mode after trying to charge it but my PC isnt recognising it.
I tried out Honeycomb, followed the steps to flash back, tried out Overcome Hermes, no problem. Flashed CM7, no problem. Tried to restore my nandroid for CM7, thats when this started.
Any advice?
And apologies if there has been a similar thread to this, I searched but i couldnt find any threads quite like this.
Click to expand...
Click to collapse
omg Gang i'm really sorry for this to happen to u ..
did you re-installed Kies in your pc , ? then odin will recognize your tab
hey Gang .. did you re-install the kies or no ? ? ? can you pls update ? ? ? ?
I think its more a problem with my Tab than the PC.
As the PC isnt recognising the Tab at all then the driver install doesnt see anything it needs drivers for. If that makes sense..
what you gonna lose if you tried ? ? ? uninstall the damn kies and install it again , and make sure , then you can say its not making any sense
Kies installs drivers for devices it connects, if my pc isnt connecting then there isnt any point. Yesterday it was fine, since my Tab ****ed up, nothing is happening.
Edit: Nevermind, while charging i went into download mode again, but this time it connected.
*massive sigh of relief*
GANJDROID said:
Kies installs drivers for devices it connects, if my pc isnt connecting then there isnt any point. Yesterday it was fine, since my Tab ****ed up, nothing is happening.
Edit: Nevermind, while charging i went into download mode again, but this time it connected.
*massive sigh of relief*
Click to expand...
Click to collapse
congrats , glad to hear that ... you better watchout next time
k0sh said:
congrats , glad to hear that ... you better watchout next time
Click to expand...
Click to collapse
You say that, but i didnt do anything wrong..
I returned from Honeycomb to OVercome without issues. I went to CM7 without issues. I restored the nandroid using the same recovery i used to do the backup. The backup was fine as id used it before.
GANJDROID said:
You say that, but i didnt do anything wrong..
I returned from Honeycomb to OVercome without issues. I went to CM7 without issues. I restored the nandroid using the same recovery i used to do the backup. The backup was fine as id used it before.
Click to expand...
Click to collapse
i mentioned it before , that the nandroid bakcups and restoring after updating to gingerbread is not working well ... i don't even do any backups anymore . just titanium bp .. anyways i'm really happy that you got your tab a life again
True, but i think one issues people have is you need to use the same recovery version you used to backup and to restore.
But thanks anyway dude.
GANJDROID said:
True, but i think one issues people have is you need to use the same recovery version you used to backup and to restore.
But thanks anyway dude.
Click to expand...
Click to collapse
+1 . even though it will be a risky ..
no need for the thanks i didn't do anything though
just keep your lovely boy safe
Before ppl start asking me, this is what happened. I gave my Cappy to my daughter and after months of running Dlev Rom, I decided to upgrade to ICS. She was not happy with the rom and wanted to go back to gingerbread. I tried downgrading via recovery but had issues with the downgrade. Long story short....ignorant me, I used Odin and end it up with eclair.
Now here is where the problem started. The phone was succesfully flashed with eclair but button combo wasnt working at all. So, I rooted first and then with adb, I adb reboot download, then once in download, I flashed ginger bootloaders and thats how i end it up with the infamous phone /!\ comp. soft brick. Since originally i had no button combo working, I cant get into download mode. My comp just wont recognize the Cappy.
I have searched for hours and tried all ways possible to get into DL mode but "nada"! Even with Odin opened or heimdall, batt out, batt in, all combinations of buttons...nada (nothing), no luck. Also tried the program by Adam to unbrick the Cappy (that I've found searching) but still nada! I have windows 7 with java and that program by Adam just wont work on my comp.
Can someone try to help me on what can I do without sending my daughter's Cappy to a shop...lol?
Edit: In this post I explain what got "me" out of the softbrick after 2 days of trying! It might not work for who ever falls in a similar situation and even mayb is not a proper way of doing things, but it worked on my end!!! http://forum.xda-developers.com/showpost.php?p=26305016&postcount=23
You can use that screen as a download mode.
Remove Java. And then go download Java JRE.
Java JRE 32 bit
Java JRE 64 bit
Try going and grabbing the Heimdall KK4 1 click. Or you could try any of the Gingerbread Heimdall packages in the OneClick Master Collection
I think you'll be fine to run Heimdall after the Java reinstall.
Red_81 said:
Try this:
Take out battery
Plug in usb cable
Hold volume+ and volume-
Pop in battery
This should take you straight into download mode. Just have to flash a new ROM/Stock Image
This came from another post about 10 down from yours.
Click to expand...
Click to collapse
Lol....Trust me, I've done that and all ways possible. At least the phone isnt hard bricked. All i need is DL mode and I should be good! Thx sweety!
Baby Liz Sandra said:
Before ppl start asking me, this is what happened. I gave my Cappy to my daughter and after months of running Dlev Rom, I decided to upgrade to ICS. She was not happy with the rom and wanted to go back to gingerbread. I tried downgrading via recovery but had issues with the downgrade. Long story short....ignorant me, I used Odin and end it up with eclair.
Now here is where the problem started. The phone was succesfully flashed with eclair but button combo wasnt working at all. So, I rooted first and then with adb, I adb reboot download, then once in download, I flashed ginger bootloaders and thats how i end it up with the infamous phone /!\ comp. soft brick. Since originally i had no button combo working, I cant get into download mode. My comp just wont recognize the Cappy.
I have searched for hours and tried all ways possible to get into DL mode but "nada"! Even with Odin opened or heimdall, batt out, batt in, all combinations of buttons...nada (nothing), no luck. Also tried the program by Adam to unbrick the Cappy (that I've found searching) but still nada! I have windows 7 with java and that program by Adam just wont work on my comp.
Can someone try to help me on what can I do without sending my daughter's Cappy to a shop...lol?
Click to expand...
Click to collapse
The [Phone /!\ Computer] screen is another method of Download Mode. You should still get Odin to recognize the phone. If Odin recognizes the phone, you should flash KI2 from This thread, since it has CWM injected. Once you have CWM, you have a clean slate to install any ROM you desire.
If Odin does NOT recognize you phone no matter which USB port you connect the phone to (as it happened to me once), you could try what I did. I downloaded Windows installer for Ubuntu Desktop, and that got me Linux. Once I had Linux, flashed KB2 from the ROM thread linked above. Why Linux? Because I never got Heimdall to work on Windows, but I did on Linux. After my phone was completely stock, I followed the instructions on TRusello's Guide to Flashing ANY ROM to get my phone set up the way I wanted.
I'm sure there are faster ways than the one I just gave you, but I can vouch that my method works, and you might get your phone sorted out while you wait for a better response. Good luck!
That will teach me to edit my post without refreshing first!
kafepuya said:
The [Phone /!\ Computer] screen is another method of Download Mode. You should still get Odin to recognize the phone. If Odin recognizes the phone, you should flash KI2 from This thread, since it has CWM injected. Once you have CWM, you have a clean slate to install any ROM you desire.
If Odin does NOT recognize you phone no matter which USB port you connect the phone to (as it happened to me once), you could try what I did. I downloaded Windows installer for Ubuntu Desktop, and that got me Linux. Once I had Linux, flashed KB2 from the ROM thread linked above. Why Linux? Because I never got Heimdall to work on Windows, but I did on Linux. After my phone was completely stock, I followed the instructions on TRusello's Guide to Flashing ANY ROM to get my phone set up the way I wanted.
I'm sure there are faster ways than the one I just gave you, but I can vouch that my method works, and you might get your phone sorted out while you wait for a better response. Good luck!
Click to expand...
Click to collapse
Yeeee....finally someone with a good heart and willing to share knowledge!!! And BTW, yes I tried all usb ports. The difference between your comp and mine is that I can run heimdall but like I said, way i plug the usb, my comp nor heimdall and/or Odin recognize the phone after the brick.
I'm not home at the moment but thank you from the bottom of my heart for your info. I'll get home kind of late tonight but I will follow your info to the tee and keep u post it...if u dont mind!
Thx and a kiss for you sweety!
Sent from my SGS II 4G using XDA Premium App
Heimdall and odin use different drivers, Once you install Heimdal and use your phone on a USB port, that USB port will only work with Heimdall. Odin will no longer work on that USB port, Until you uninstall the heimdall drivers
TRusselo said:
Heimdall and odin use different drivers, Once you install Heimdal and use your phone on a USB port, that USB port will only work with Heimdall. Odin will no longer work on that USB port, Until you uninstall the heimdall drivers
Click to expand...
Click to collapse
Short and sweet...i installed ubuntu last night on my pc and I thought i lost windows. Did some search and I can choose when my pc start up either W7 or ubuntu. Went to bed at 4am trying to install java to ubuntu with no luck. To b honest, i'm about to quit trying to get this phone in DL mode. My daughter hates me and my husband told me, u messed it up...u fix it! Agh!!!!! I'm trying again but if I cant get it to work I rather just buy my kid a new phone....and thats a shame because that Cappy has been a warrior!
Any other method to get DL mode??? PLEASE...SOMEONE????
Once you're at that screen, it is download mode. You could try a jig. You can build one or buy one.
Did you reinstall java on Windows 7 and then try Heimdall?
Red_81 said:
Once you're at that screen, it is download mode. You could try a jig. You can build one or buy one.
Did you reinstall java on Windows 7 and then try Heimdall?
Click to expand...
Click to collapse
Yes I did and pc still not recognize device. Tried all ports and different usb cable...still no go!
Did device manager not recognize it or Odin/Heimdall not recognize it? I know my system wouldn't show it was connected but Odin/Heimdall still would.
Red_81 said:
Did device manager not recognize it or Odin/Heimdall not recognize it? I know my system wouldn't show it was connected but Odin/Heimdall still would.
Click to expand...
Click to collapse
Neither one recognize the device. With Odin you're supposse to see the yellow light meaning its connected...but nothing, and with heimdall clearly says disconected. I am sooo exausted looking for an answer as to what to do to get this phone on DL mode! I've used both programs in the past but the phone just dont want to come alive!
I understand how frustrating it can be to get a phone to respond.
I went back to your first post to make sure I didn't miss anything and I realized what the issue might be. Since the phone was upgraded to ICS it wouldn't be using the standard captivate drivers any more.
Let's try this:
Download and install the Android SDK
Add the Google USB Driver
Try ODIN/Heimdall again.
I think I had a similar issue when I was reverting a phone from CM7 back to Stock captivate.
Red_81 said:
I understand how frustrating it can be to get a phone to respond.
I went back to your first post to make sure I didn't miss anything and I realized what the issue might be. Since the phone was upgraded to ICS it wouldn't be using the standard captivate drivers any more.
Let's try this:
Download and install the Android SDK
Add the Google USB Driver
Try ODIN/Heimdall again.
I think I had a similar issue when I was reverting a phone from CM7 back to Stock captivate.
Click to expand...
Click to collapse
Oookkkk...will give this a try! Thank you.
Baby Liz Sandra said:
Oookkkk...will give this a try! Thank you.
Click to expand...
Click to collapse
I think it will work. Sorry it took so long for me to realize it. I actually had to do the same procedure within the last week but less sleep + work + cold is making me a little foggy.
Red_81 said:
I think it will work. Sorry it took so long for me to realize it. I actually had to do the same procedure within the last week but less sleep + work + cold is making me a little foggy.
Click to expand...
Click to collapse
Just finished installing both...restarting pc now and will report back. Thank you yet again!
Baby Liz Sandra said:
Just finished installing both...restarting pc now and will report back. Thank you yet again!
Click to expand...
Click to collapse
Ok...thats it! That did not work either. I connected my SGS II just to see if my pc would recognize the phone, and indeed my pc picked up the device as well as my husband's Sensation. So thats it! Just called Radio Shack for a jig and the guy never heard of that...lmao! You guys should see my daughter's look at me....awh!
Anyway...I'm subscribed to this thread so if anyone has another bright idea I'll give it a shot. Thanks again!
Sorry that didn't work either. Here's another thread about connection issues to the computer. I hope this helps
http://forum.xda-developers.com/showthread.php?t=1351224
Red_81 said:
Sorry that didn't work either. Here's another thread about connection issues to the computer. I hope this helps
http://forum.xda-developers.com/showthread.php?t=1351224
Click to expand...
Click to collapse
Well...thank you! Don't know if i should keep DLing stuff to my pc. Now I have ubuntu, sdk manager, hemidall, dont know how many odins, etc. My husband just ask me for a new pc because he tried to uninstall ubuntu and he was unsuccesfull at it. Now this softbrick is gonna cause me some major issues family wise. This really sucks! But hey, me been a female, I just learned that nothing is impossible for us. If my hubbie dont wanna help me...I'll get it done one way or another. I will see my daughter smile....believe that!!!!!
Thank you!
I have a 2.5 year old daughter and would do anything to see her smile.
Here is a guy here on XDA who makes the jigs. However, I still believe you just have a driver issue. At this point I can only say to take off all the drivers, odin, and heimdall and start fresh.
http://forum.xda-developers.com/member.php?u=500006
I used his kindle fire cable and it was great.
Hello guys.
I really need some help. Im going away for 2 weeks on 4 June. And after i come back ill be ghone after 2 days again for 2 weeks and i need my phone!
My story:
I saw an update for my phone to ICS. So i plugged on my laptop and put the update on with KIES 2.1.3.
At about 64% the update didnt go ferther and it gave an error report.
The program KIES shut down, and my phone turned off.
I putted everything back on. But now my phone says this:
''Firmware upgrade encountered an issue. Please select recovery mode in KIES & try again.''
KIES doesnt see my phone anymore. And the recovery mode i found on the internet.
Volume button up, home button+ power button doesnt work.
It keeps going to this screen.
My phone was 2.3.6 standard, non rooted etc etc.
How can i fix this fast?
I tried rooting and flashing, but i just cant do anything with my phone exept this screen i explained.
Thanks in advance.
Mitchell
Can you get your phone into download mode.
Device off>vol-down+home+power ?
Belfia said:
Can you get your phone into download mode.
Device off>vol-down+home+power ?
Click to expand...
Click to collapse
I didnt knew about this mode.
Yes it worked.
Seems a little bit like hope for me?
Thanks.
damitch300 said:
I didnt knew about this mode.
Yes it worked.
Seems a little bit like hope for me?
Thanks.
Click to expand...
Click to collapse
Just download ODIN app for Windows, get right stock firmware from development thread ( Dr. Ketan's post ) and flash it with ODIN. It's as simple as clicking select file and start. Everything is described in the thread with firmware downloads.
Yes. Then there is hope. Now I recommend you to try flashing one of the stock roms from dr.ketans thread in development section.
Its not very complicated. But feel free to ask if you need more help.
I just cant explain how happy i am with this forum.
Brings so much luck into live
Thanks.
Ill see if i need more help. Hopefully not.
Is there any dutch ICS rom?
Or should i stick with a basic english?
I got exactly the same problem. Called T-Mobile's helpdesk. With everything I asked, the girl said, it's in the manual. Finally, the best she had to offer was for me to send my Note to Samsung.
So then I started looking for a solution myself and found it here.
Solved it with the said solution. Flashing with Odin is a piece of cake. Thanks for the expertise folks.
Good thing we can help. Wouldnt call myself an expert though
damulder said:
I got exactly the same problem. Called T-Mobile's helpdesk. With everything I asked, the girl said, it's in the manuel. Finally, the best she had to offer was for me to send my Note to Samsung.
So then I started looking for a solution myself and found it here.
Solved it with the said solution. Flashing with Odin is a piece of cake. Thanks for the expertise folks.
Click to expand...
Click to collapse
Well i searched for hours to. My sister had her S2 upgraded with KIES. That worked, but the ICS update itself was plain suck.
I fixed it thanks to XDA forum. Nothing found on the internet exept sending to help desk.
Same with what i got now.
But now it is fixed and im thankfull to the ones helping.
Now i am willing to try ICS without KIES.
Lol in kies you have recovery mode you missed an option
Good thing you got it fixed
Sent from my GT-N7000 using Tapatalk 2
baz77 said:
Lol in kies you have recovery mode you missed an option
Good thing you got it fixed
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Like i said, KIES didnt see my phone. Neither did windows.
So it wasnt an option.
Glad its fixed
Sent from my GT-N7000 using Tapatalk 2
BTW, after getting my Note up and running again, I used KIES again for updating to ICS and this time I had no problem at all.
damulder said:
BTW, after getting my Note up and running again, I used KIES again for updating to ICS and this time I had no problem at all.
Click to expand...
Click to collapse
For me this didnt work. KIES had an upgrade, but seems like it still doesnt do the job right.
Ran some tests. Now i am back at the issue.
Now Odin doesnt want to continue updating like KIES always does.
I wish i didnt do the tests...
damitch300 said:
Ran some tests. Now i am back at the issue.
Now Odin doesnt want to continue updating like KIES always does.
I wish i didnt do the tests...
Click to expand...
Click to collapse
what tests are you referring to?
and i'm guessing you're on Mac? and having trouble with kies identifying your device?
ngocdao said:
what tests are you referring to?
and i'm guessing you're on Mac? and having trouble with kies identifying your device?
Click to expand...
Click to collapse
W7 Ultimate N
And trying out different KIES versions.
Well at the 2nd update 2.3.6 to 4.0.3 it ran stuck again.
And now Odin doesnt do anything to aswell. Keeps saying ''Failure'' after some time.
Now ODIN is stuck at syaing ''BOOT'' above ID:COM.
How can i fix this?
Well seems like the Dutch roms aint working.
I did an European right now wich worked.
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.
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!