Related
i . ll just start from the beginning. i installed a jesus freke ROM on my G1, i dont remember what version. i think it was 1.41 or something like that. (RC29 or RC33, idr). i downloaded an app or maybe it was an app that came with the ROM that let me know of jesus freke's updates. i hadnt checked it awhile as the G1 is not my primary device. when i checked for it last week, it showed an update and i attempted to install it. i completely forgot the procedure for updating a new image and im prretty i bricked it because it wont go past the android screen, even after waiting about 10-15 minutes, it still wont go past it. so my question is, can somebody please help me unbrick my G1? im in no hurry as im not using it on a daily basis, but id like to get this resolved as soon as possible so i can sell my G1. anyways, id appreciate it if someone could help. if so, can you give some detailed instructions as im not TOO familiar with android. i know a little about it, but too much.
thanks guys,
josh.
if you can access recovery mode, just go and reinstall other rom, i recommend cyanogenmod - user friendly and it got a complete guide on there website to install.
youll have to expand on that a little more, like i said, im not that familiar with android.. i dont have an SD card in there, and i suppose that might pose a problem trying to flash another ROM to it.. can you give me some links and some specific directions when you have a chance..? i'd greatly appreciate it.
josh_prayyforplagues said:
i . ll just start from the beginning. i installed a jesus freke ROM on my G1, i dont remember what version. i think it was 1.41 or something like that. (RC29 or RC33, idr). i downloaded an app or maybe it was an app that came with the ROM that let me know of jesus freke's updates. i hadnt checked it awhile as the G1 is not my primary device. when i checked for it last week, it showed an update and i attempted to install it. i completely forgot the procedure for updating a new image and im prretty i bricked it because it wont go past the android screen, even after waiting about 10-15 minutes, it still wont go past it. so my question is, can somebody please help me unbrick my G1? im in no hurry as im not using it on a daily basis, but id like to get this resolved as soon as possible so i can sell my G1. anyways, id appreciate it if someone could help. if so, can you give some detailed instructions as im not TOO familiar with android. i know a little about it, but too much.
thanks guys,
josh.
Click to expand...
Click to collapse
This right here is why I say don't root if you don't know wtf you're doing. This always happens to people who should have just stayed away. Look:
Power phone completely off. Hold home key and power on. If you get to the recovery screen (the screen with a bunch of options, probably all written in green for you) then you're not bricked. All you need to do is put latest cyanogenmod on your sdcard, wipe your phone, and install it.
Hello,
Tryed to find similar threads, but found none with the correct answer.
When i tryed to unroot/unflash my phone back to stock something went wrong.
Now when i try to turn my phone on i can only see this "G1 t-Mobile" loadingscreen and nothing else happens.
Ive tryed booting with Home+Power, with Camera+Power and a normal booth, nothing works. Replaced the SD-card with an other one (1GB), first formatted FAT32style, didnt work. Afterwards i put the DREAIMG.nbh file on it and tryed it, but still didnt work. Im all out of options.
Can someone please help?
hoipupe said:
Hello,
Tryed to find similar threads, but found none with the correct answer.
When i tryed to unroot/unflash my phone back to stock something went wrong.
Now when i try to turn my phone on i can only see this "G1 t-Mobile" loadingscreen and nothing else happens.
Ive tryed booting with Home+Power, with Camera+Power and a normal booth, nothing works. Replaced the SD-card with an other one (1GB), first formatted FAT32style, didnt work. Afterwards i put the DREAIMG.nbh file on it and tryed it, but still didnt work. Im all out of options.
Can someone please help?
Click to expand...
Click to collapse
I'm afraid you have a hard bricked phone. Only way out is to jtag it.
http://forum.xda-developers.com/showthread.php?t=591048
i have the same problem in my g1 mobile he is dead now please help me
Did you try going to the Root screen? If you can't go to the root screen, then it might be Bricked, I'm not sure though.
Sent from my T-Mobile G1 using XDA App
I have tryed every button combination possible, and none of them worked
So there is no other way to fix this unless i need to adjust the hardware?
hoipupe said:
I have tryed every button combination possible, and none of them worked
So there is no other way to fix this unless i need to adjust the hardware?
Click to expand...
Click to collapse
I'll simply refer you back to post number 2.
shadowch31 said:
I'll simply refer you back to post number 2.
Click to expand...
Click to collapse
Yes, and thank you for that.
Though, im afraid i'm not competent enough to "JTAG" it as i dont understand 50% of the stuff being said in that post
Also i read you need some equipment like a JTAG Adapter, which i dont have..
hoipupe said:
Yes, and thank you for that.
Though, im afraid i'm not competent enough to "JTAG" it as i dont understand 50% of the stuff being said in that post
Also i read you need some equipment like a JTAG Adapter, which i dont have..
Click to expand...
Click to collapse
Your best bet would be to see if anyone in your area/country who can do it for you probably at a lot cheaper cost than buying a new phone.
Can anyone say when galaxy tab p1000 gets hard bricked? Everytime mine gets bricked, its a soft brick
If you try to flash, say a rom from another device and the rom contains a boot loader, you will hard brick it.
Sent from my GT-P1000 using XDA
If I heard right, if 2 files aren't flashed properly in Odin or Heimdall (boot and something else?), you can hard brick that way too.
The 2 files are the first things flashed in Odin if I recall correctly
About the only way to hard brick your Tab is by damaging the Primary boot loader (boot.bin) and the Secondary boot loader (sbl.bin). If these are damaged, you can't get to download or recovery mode anymore, and need extra hardware to be able to flash a ROM again. You can do this for instance by yanking out the cable during a flash, but even then you would have to be unlucky, because these files are small, and will be flashed in seconds. Flashing a ROM with boot loaders for the wrong Tab could do it too I bet.
BTW, it sounds like you are trying to hard brick it, and are frustrated you're not succeeding. Surely I'm wrong about that.
gogol1996 said:
Can anyone say when galaxy tab p1000 gets hard bricked? Everytime mine gets bricked, its a soft brick
Click to expand...
Click to collapse
There is no such thing as a "soft brick", Thats is something n00bs just say when they screwed something up and cant boot into rom, your device is either bricked or it isnt. Its "bricked" when you cant get into download mode/recovery etc and only solution is hardware recovery like JTAG.
What you are referring to as "soft brick" is simply you not installing an OS correctly. Go and read/learn and then you will have no more "soft bricks"
TheATHEiST said:
There is no such thing as a "soft brick", Thats is something n00bs just say when they screwed something up and cant boot into rom, your device is either bricked or it isnt. Its "bricked" when you cant get into download mode/recovery etc and only solution is hardware recovery like JTAG.
What you are referring to as "soft brick" is simply you not installing an OS correctly. Go and read/learn and then you will have no more "soft bricks"
Click to expand...
Click to collapse
i can only confirm.
you can also brick you device by playing with efs partition , i saw this in some samsung devices wich have unock code reading protection .
TheATHEiST said:
There is no such thing as a "soft brick", Thats is something n00bs just say when they screwed something up and cant boot into rom, your device is either bricked or it isnt. Its "bricked" when you cant get into download mode/recovery etc and only solution is hardware recovery like JTAG.
What you are referring to as "soft brick" is simply you not installing an OS correctly. Go and read/learn and then you will have no more "soft bricks"
Click to expand...
Click to collapse
From my readings, "Soft brick" is a very common term that refers to a screen that shows a handset connecting to a computer. A form of DL mode that doesn't show the expected Andy construction sign. This is the only thing that will ever show on the screen until you successfully flash it.
Regarding the OP, if you ever manage to hard brick, check this guy out.
mobiletechvideos.mybigcommerce.com/samsung-galaxy-tab-jtag-brick-repair
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
arachnophile said:
From my readings, "Soft brick" is a very common term that refers to a screen that shows a handset connecting to a computer. A form of DL mode that doesn't show the expected Andy construction sign. This is the only thing that will ever show on the screen until you successfully flash it.
Regarding the OP, if you ever manage to hard brick, check this guy out.
mobiletechvideos.mybigcommerce.com/samsung-galaxy-tab-jtag-brick-repair
Click to expand...
Click to collapse
No, your device is either "bricked" or its not, its as simple as that. If you havent "bricked" it you simply go into download or recovery mode and reflash a rom, simple.
If you need extra hardware to recover your device like JTAG or you need to replace mobo, That is considered a "brick".
Thanks. At last hard bricked my device after deleting the *.bin files from the firmware before flashing.
Well download mode cannot be opened. Device does not light up.
Sent from my GT-P1000 using xda premium
Congrats! Let us know how the JTAG goes, will you?
Peace,
C.
gogol1996 said:
Thanks. At last hard bricked my device after deleting the *.bin files from the firmware before flashing.
Click to expand...
Click to collapse
Why are you trying to brick your device?
My second hand gt-p1000 was used by me for testing rooms before flashing on this one. Now I will try to unbrick it.
Sent from my GT-P1000 using xda premium
Ok
Sent from my GT-P1000 using xda premium
gogol1996 said:
Thanks. At last hard bricked my device after deleting the *.bin files from the firmware before flashing.
Click to expand...
Click to collapse
You are, Sir, very brave, Sir!
All this time I've been trying to avoid even a 'so called soft-brick' (Ok, I know there is no such thing, but I can't find other term) my tab, let a lone to brick it.
I can not imagine that I have to do that "Unbrickable Mod" fix requiring soldering and tweaking hardware.
---------- Post added at 10:28 AM ---------- Previous post was at 10:22 AM ----------
TheATHEiST said:
There is no such thing as a "soft brick", Thats is something n00bs just say when they screwed something up and cant boot into rom, your device is either bricked or it isnt. Its "bricked" when you cant get into download mode/recovery etc and only solution is hardware recovery like JTAG.
What you are referring to as "soft brick" is simply you not installing an OS correctly. Go and read/learn and then you will have no more "soft bricks"
Click to expand...
Click to collapse
May be the correct term is boot-loop or boot failure?
That's one way of looking at it, but it's actually not a bad idea to differentiate between two states of brickedness, and give them different names.
One state, familiar to many who flash their Tabs (which some may not even call a bricked state), is the result of a bad flash: the boot loader is intact, and you can get to download mode. However, if you just try to boot it, it will hang or get into a boot loop. This way it's as useful as a brick if you don't fix it, and many people won't know how to fix it. But more importantly, you'll need software to fix it (special hardware isn't necessary). So I like to think of this as a "soft brick".
In the other state there's something wrong with the boot loaders, and the Tab will not go into recovery mode. And yes, you've guessed it, you'll need special hardware to fix such a Tab, because the software inside a Tab needed to flash a ROM is itself damaged and therefore can't be used to flash a working ROM. It's definitely slightly less useful than a brick if you don't fix it, and even fewer people will have the resources to fix it, but it still can be fixed if you have those. Because it needs hardware I like to think of this state as a "hard brick".
You know it makes sense!
gogol1996 said:
Well download mode cannot be opened. Device does not light up.
Sent from my GT-P1000 using xda premium
Click to expand...
Click to collapse
I'd say you are crazy, but the fact is your post just made me calm when I experienced a boot-loop. Thanks man.
all you have to do is delete the *.bin files (boot.bin & sbl.bin) from the .tar archive before flashing to get a hard brick
Huh?
Didn't someone said removing those files us removing boot loader.
And that us recommended when you get a rom you are not sure of.
Now I am confused.
Sent from my GT-P1000 using XDA
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.
So i have a Moto g xt1072 wich i got second hand.. i got it into recovery mode and eventually got it working, but it was really unstable, so i wanted to reflash the stock rom, because it looked like the current one on the phone was corrupted (i was running android 6.0) (btw i have a xt1068 as my daily driver, but i want this to work again)
So i started flashing http://forum.xda-developers.com/moto-g-lte/general/stock-6-0-marshmallow-europe-reteu-t3338075 <-this
but i had errors and it was failing multiple times.. so i looked up some tutorials, and most of them were unlocking the bootloader at the beginning, so i was unlocking and locking the bootloader trying to get the commands to work,
then i found a tutorial wich coppyd all of the commands at once, so i tried that.. screen went black..
Wont boot into recovery, 3sec method or 120 sec method, and connects to my pc as QHSUSB_BULK
luckily i made a picture of the recovery when i tried to flash:
http://imgur.com/8avCk3T
I think i may need to blank flash, but im not certain..
I would also like to find the firmware for this phone that wont brick it..
Can anyone help?
Need more info?
Please just ask me, i will respond immediately
i dont care what i need to do.. even if i need to hardwire (because im really good at those finicky things)
Thanks for reading XD
Same issue here. I flashed a stock image and something must've gone wrong at some point
hamzahrmalik said:
Same issue here. I flashed a stock image and something must've gone wrong at some point
Click to expand...
Click to collapse
you probably also flashed the vootloader and the bootanimation, these are known to give problems, but ive foubd a test point on the pcb which brings the phone in a les hard bricked state, but ive yet to find a method to unbrick the phone..
ill keep you posted
ora69 said:
you probably also flashed the vootloader and the bootanimation, these are known to give problems, but ive foubd a test point on the pcb which brings the phone in a les hard bricked state, but ive yet to find a method to unbrick the phone..
ill keep you posted
Click to expand...
Click to collapse
Sorry could you please explain. How can a phone be less hard bricked. Thanks
Sent from my A0001 using Tapatalk
hamzahrmalik said:
Sorry could you please explain. How can a phone be less hard bricked. Thanks
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
okay, so there are different types of hardbricks, all act the same, but one is harder to unbrick than the other, there is qh usb bulk and qhas bulk with numbers behind it, search for force unbrick lg g2,
now the problem is, it should be easy to unbrick the phone at thsi point, but im not an expert in that and have no idea what to do now xD so i posted it on xda, but no one answered me.. xD hopefully this clears it up some more
ora69 said:
okay, so there are different types of hardbricks, all act the same, but one is harder to unbrick than the other, there is qh usb bulk and qhas bulk with numbers behind it, search for force unbrick lg g2,
now the problem is, it should be easy to unbrick the phone at thsi point, but im not an expert in that and have no idea what to do now xD so i posted it on xda, but no one answered me.. xD hopefully this clears it up some more
Click to expand...
Click to collapse
Oh ok I get you. Mines USB bulk 9000 or something i can't remmeber now
Sent from my A0001 using Tapatalk
ora69 said:
So i have a Moto g xt1072 wich i got second hand.. i got it into recovery mode and eventually got it working, but it was really unstable, so i wanted to reflash the stock rom, because it looked like the current one on the phone was corrupted (i was running android 6.0) (btw i have a xt1068 as my daily driver, but i want this to work again)
So i started flashing http://forum.xda-developers.com/moto-g-lte/general/stock-6-0-marshmallow-europe-reteu-t3338075 <-this
but i had errors and it was failing multiple times.. so i looked up some tutorials, and most of them were unlocking the bootloader at the beginning, so i was unlocking and locking the bootloader trying to get the commands to work,
then i found a tutorial wich coppyd all of the commands at once, so i tried that.. screen went black..
Wont boot into recovery, 3sec method or 120 sec method, and connects to my pc as QHSUSB_BULK
luckily i made a picture of the recovery when i tried to flash:
http://imgur.com/8avCk3T
I think i may need to blank flash, but im not certain..
I would also like to find the firmware for this phone that wont brick it..
Can anyone help?
Need more info?
Please just ask me, i will respond immediately
i dont care what i need to do.. even if i need to hardwire (because im really good at those finicky things)
Thanks for reading XD
Click to expand...
Click to collapse
So that link to another thread in XDA forum, I think I had a similar experience. I too have the XT1072 as I live in the UK. now here on XDA you have to be careful and ask 3 4 maybe 5 times before someone listens properly. I know it is hard for the devs with so many dumb noobs asking so many dumb questions, I include myself as a noob so no worries. Anyway to get to the point that link is not referring to our phone the XT1072. You should ignore LTE in your search criteria, it will always point you towards the 2015 model and believe you me all roms in my experience area very device specific. You need to simply put Moto G 2nd gen 2014 in search criteria when it comes to searching for custom recoverys and/or stock ROMS. The Titan.IMG is always a safe bet if I remember correctly, dont take my word for it, I have been known to have a memory like a sieve now and again, the problem with getting older, cache gets smaller and smaller, lol! Best of luck!
hamzahrmalik said:
Sorry could you please explain. How can a phone be less hard bricked. Thanks
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Read the beginning on this article: http://rootmyandroid.org/how-to-unbrick-your-android-device-the-ultimate-guide.html/
the bricked term is a common misconception for phones that still turn on..