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.
Ok I need some help. As of right now my tab is dead, the only thing it does when powered on is loads to the Asus splash screen and that's all. I can not get it into Fastboot mode at all and Adb cant find it either. I have already tried Sp Flashtools to no avail. I have all the Vcom drivers installed, every where I searched the one driver that people talked about was the mtk6585 driver ( I think that's what it is ) , the one for me that popped up and went away really fast was a driver called CLOVERVIEW. So needless to say I cant get SP Flash tools to work, and without fastboot mode im really stuck. Ever since I first came across this site a few years back I have rooted, and put custom roms on countless devices, I would call myself an experienced flasher. Well this tab has me feeling like a real noob, I can not figure it out. So if someone can help me it would be greatly appreciated. Thank you XDA world.
Try this: http://forum.xda-developers.com/android/help/instructions-reviving-me170c-me170cx-t3017466
It worked for me.
silviu74 said:
Try this: http://forum.xda-developers.com/android/help/instructions-reviving-me170c-me170cx-t3017466
It worked for me.
Click to expand...
Click to collapse
Wont work for me. Like I said, I cant get into droidboot.
Downloading android studio and all sdk tools, hopefully something in this will help. I will post updates on any progress.
zMILWAUKEE said:
Downloading android studio and all sdk tools, hopefully something in this will help. I will post updates on any progress.
Click to expand...
Click to collapse
I just got myself into the same situation. If you can get to a point where CLOVERVIEW comes up, that can be fixed (I actually just added a howto to the general section). However, I don't know how to get out of the stuck splash screen, since it's an awkward medium between download and fastboot. I'm not even sure what I did to cause this; I had just flashed boot.img and splashscreen.img and issued a fastboot reboot-bootloader.
The device does indeed pop up in download mode for about a second while booting; doesn't seem long enough for a flash. I would really like to find out if there is any way to force this device to boot into download mode.
Was having wifi issues, found a tutorial on flashing firmware via usb, BUT downloaded an old firmware that made the whole device go to hell.
Has anyone managed to recover their device, or am I the only soul who was dumb enough to put myself in this situation.
I cannot get into fastboot, recovery, etc. booting leads to a blank screen.
Cheers
You will have to flash the stockrom files via Odin i am afraid
Sent from my SM-N920C using Tapatalk
Do you have any sort of instructions.
I'm sorta familiar with Odin, but I thought that fastboot was a requirement?
jewnersey said:
Was having wifi issues, found a tutorial on flashing firmware via usb, BUT downloaded an old firmware that made the whole device go to hell.
Has anyone managed to recover their device, or am I the only soul who was dumb enough to put myself in this situation.
I cannot get into fastboot, recovery, etc. booting leads to a blank screen.
Cheers
Click to expand...
Click to collapse
Hey were you able to fix this issue? I am having a similar issue currently and would appreciate any help.
jewnersey said:
Was having wifi issues, found a tutorial on flashing firmware via usb, BUT downloaded an old firmware that made the whole device go to hell.
Has anyone managed to recover their device, or am I the only soul who was dumb enough to put myself in this situation.
I cannot get into fastboot, recovery, etc. booting leads to a blank screen.
Cheers
Click to expand...
Click to collapse
Turns out i did the exact same and now i am in similar situation.
https://forum.xda-developers.com/google-glass/help/glass-wont-fastboot-mode-t3990575
did you manage to fix the problem?
Don't think it's fixable ?
[/COLOR]
jewnersey said:
Don't think it's fixable
Click to expand...
Click to collapse
I was able to make some progress. Whenever i tried to fastboot a device would popup for a second on the computer and then disappear. At first I thought it was fastboot interface but looking closely at the device "OMAP4430" with vid 0451 and pid D00F, turns out it is an interface used to flash new first stage and main bootloaders on various devices such as galaxy nexus and galaxy tab 2 along with pandaboard and certain lg phones. There are utilities such as OMAP flash (by Texas instruments) and OMAP4BOOT (unofficial open source) that could talk to the device using this protocol. People have made scripts around these utilities to unbrick other devices mentioned above. I have played with these tools and i am able to push first loader called MLO or " xloader" by TI, fortunately google provides xloader with XE23 but i am not been able to push the main bootloader perhaps someone with more experience can help write configuration scripts for these tools that would work on glass so that i can get to fastboot and restore my device.
I purchased the H811 off ebay last week because I am finally sick of my old Note 5 with no service at home. The G4 did great until I decided to flash it. The phone was on H81120i.
No big deal unlocking bootloader or installing TWRP. I flashed Lineage OS 14.1. About a minute after booting up, the phone got the error Camera stopped working. After checking more stuff on the device, nothing seems to work - i.e. - The accelerometer, speakers, microphone, flashlight, etc are dead. I installed a sensor test app and it doesn't detect any of the sensors.
After that, I downloaded LGUP and the stock KDZ file to flash back to phone hoping to fix it. Unfortunately, LGUP doesn't recognize the phone. It says unknown model but shows the com port, h81120i on the right hand side. I also tried LG FlashTool to see if that would work but it crashes about 26% into the it.
I have searched the forums up and down and have googled the crap out of this. I did find a thread from last month with a very similar issue a moment ago, https://forum.xda-developers.com/tmobile-g4/help/camera-stopped-audio-flashing-lg-g4-t3620516, and perhaps I should post in that thread, but my issue is that LG Bridge gives me an error stating it can't detect the software version.
If I were using Samsung, I don't think I would have this problem because I have unbricked several Samsung devices. The issue here is I am new to LG and have no idea if files are corrupt, if hardware was screwed, or what the situation is. I would hate to think that it was a $100 wasted.
Any help would be greatly appreciated.
x3n0n907 said:
I purchased the H811 off ebay last week because I am finally sick of my old Note 5 with no service at home. The G4 did great until I decided to flash it. The phone was on H81120i.
No big deal unlocking bootloader or installing TWRP. I flashed Lineage OS 14.1. About a minute after booting up, the phone got the error Camera stopped working. After checking more stuff on the device, nothing seems to work - i.e. - The accelerometer, speakers, microphone, flashlight, etc are dead. I installed a sensor test app and it doesn't detect any of the sensors.
After that, I downloaded LGUP and the stock KDZ file to flash back to phone hoping to fix it. Unfortunately, LGUP doesn't recognize the phone. It says unknown model but shows the com port, h81120i on the right hand side. I also tried LG FlashTool to see if that would work but it crashes about 26% into the it.
I have searched the forums up and down and have googled the crap out of this. I did find a thread from last month with a very similar issue a moment ago, https://forum.xda-developers.com/tmobile-g4/help/camera-stopped-audio-flashing-lg-g4-t3620516, and perhaps I should post in that thread, but my issue is that LG Bridge gives me an error stating it can't detect the software version.
If I were using Samsung, I don't think I would have this problem because I have unbricked several Samsung devices. The issue here is I am new to LG and have no idea if files are corrupt, if hardware was screwed, or what the situation is. I would hate to think that it was a $100 wasted.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
maybe you got a frankenphone .. a supposely H811 and its not .. why not open it and see the actual motherboard and see wich variant you really have .seems like its not a h811 or try uppercut LGUP. see what it finds and downloads.
raptorddd said:
maybe you got a frankenphone .. a supposely H811 and its not .. why not open it and see the actual motherboard and see wich variant you really have .seems like its not a h811 or try uppercut LGUP. see what it finds and downloads.
Click to expand...
Click to collapse
Uppercut found nothing... I opened the phone and found this though... EAX6658501_H810_MAIN_1.0
Of course, the tag on the inside of battery compartment says H811 with a date of 02/2016. Would it be a refurb or what? Anyway, I may be on the right track now.
x3n0n907 said:
Uppercut found nothing... I opened the phone and found this though... EAX6658501_H810_MAIN_1.0
Of course, the tag on the inside of battery compartment says H811 with a date of 02/2016. Would it be a refurb or what? Anyway, I may be on the right track now.
Click to expand...
Click to collapse
maybe yes .. cover h811 and so software easy to edit.. but the only way is that take the motherboard and read the variant.
h810 is att?
I checked out the AT&T forum and found nothing other than stock that, obvious under my current situation, I can't flash because lgup with uppercut nor lg flash tools can flash.
LGUP gives an error code in the log file. PACKET_ERROR code = 1460
The phone internet still works. It has downloaded an update from t-mobile that's 460+MB that I can't install because I'm rooted with TWRP. Is it possible to update the phone with adb and TWRP? If I could find stock recovery, I would flash that and using autoprime's bootloader flash it back, even remove root if the update may revive the device.
After a week, a thought occurred to me and i tried it. I backed up a working h811 ( minus efs partition) with twrp with 20o firmware to an sd card then restored that version to this phone. I immediately wiped and flashed G4 20o with root zip file. It unbricked the phone and I'm currently using it.
Thanks raptorddd for replying and helping me. It seems that somewhere in the flash process something was corrupted and this fixed it.
x3n0n907 said:
After a week, a thought occurred to me and i tried it. I backed up a working h811 ( minus efs partition) with twrp with 20o firmware to an sd card then restored that version to this phone. I immediately wiped and flashed G4 20o with root zip file. It unbricked the phone and I'm currently using it.
Thanks raptorddd for replying and helping me. It seems that somewhere in the flash process something was corrupted and this fixed it.
Click to expand...
Click to collapse
youre welcomed but then phone is H811? or H810 i know that what ever the motherboard says thats your variant. am glad you have back up and running. :good:
It is crazy because the board said 810 but it had h81120i official when i got it. It worked but i have always used custom roms. Oh well, I'm going to stay stock with root. Just need to debloat now.
I made a vid so I can show exactly what it's doing.. Its only like 15 seconds
https://youtu.be/And3oxigBnM
Redacted Kaos said:
I made a vid so I can show exactly what it's doing.. Its only like 15 seconds
https://youtu.be/And3oxigBnM
Click to expand...
Click to collapse
Tfat has to be frustrating, I don't want to waste your time, but hate to see someone with a dead device, so you've already tried qfil and lgup, and fastboot commands? And you've also attempted to get into EDL again I'm assuming, and have you looked to see what your device is named in device manager in this state, meaning I'd it labeling it a modem or ADB device.? I'm just throwing some stuff out there because if it's fixable, and I'm sure it is, you have to get it into some other mode. I get that screen too but it boots and everything. If these guys can't get you hooked up than that vlad dude can do remote work and I think he knows LG very well. Just a thought.
Can you describe what you have done to get to this point? I was in a similar situation last week that took about 12 hours of troubleshooting but eventually got it fixed and set up the way I want.
I made a mistake somewhere and flashed something or failed to flash something that got me in a similar state.
I will just throw out what worked for me. I had lost every bootable mode except for 9008 (edl?). So I tried using QFIL to flash Pie laf_a and laf_b or the Oreo version. This gets you LG Download mode back. From here I recommend using a KDZ to get back to stock and boot in to make sure you can. My first attempt at this point was flashing a Pie KDZ US unlocked (I have AT&T ). Would not boot. So I tried flashing the Oreo KDZ US unlocked… lo and behold it booted all the way up. From here I was able to start over and follow the guide to get Lineage OS.
Anyway hopes this helps you.
Thank you guys for answering me I will basically I've got magisk installed bootloader unlocked rooted and I was just my phone will boot up and stuff but you know what happens whenever I want to go into download mode or go into sucking whatever you know.. I went through all this trouble got this phone unlocked and rooted and stuff 90% of the s*** that I can use what does rooted phone requires a custom recovery which is the one sucking thing I guess you can't do so I'm thinking about just flashing back stop because I don't have this kind of irritated cuz there's so many modules I want to use and stuff and I can't because there's no way to flash custom recovery whatever seed wrmn whatever