WARNING: THIS SBF MIGHT HARDBRICK YOUR XT530 AS REPORTED BY ONE OF THE USERS THAT TRIED. I'M NOT RESPONSIBLE OR LIABLE IF YOU HAVE HARDBRICKED YOUR PHONE! YOU HAVE BEEN WARNED.
@zhalx and @inyong1 I made compiled a SBF that contains XT532 Bootloader and Fastboot Mode. In some XT530 threads it claims that it can
Code:
fastboot boot
properly and doesn't have problems with flash huge system.img files to /system partition.
As I don't own a XT530, I need any experienced XT530/XT531 users to test it for me.
When you flash the SBF would anyone give me the screenshot of what the phone says when you flash the XT532 Bootloader and also a screenshot of RSD-Lite when you flash the SBF. Thanks.
I've made two test SBF's to see which one works. Please reply and tell me which test works. For e.g. if Test 1 soft bricks your phone then flash back your XT530/XT531 SBF and try test 2.
Instructions:
1. Download the Test 1 and Test 2 attachments.
2. Unzip the SBF out of the zip file.
3. Make sure all Motorola Drivers are installed.
4. Make sure RSD-Lite v5.6 and above is installed.
5. Power down your device.
6. Put your phone in flash-mode by pressing Power Button, Volume Down and Camera button simultaneously.
7. Now flash the Test SBF using RSD-Lite.
NOTE: You will get errors on your screen when you flash the SBF because it doesn't contain the successive MBN's to flash to the phone. Just disconnect the battery and put it back in. If your phone refuses to turn on then flash back your stock SBF.
I feel happy to know you are still trying for this. I can not try it now because my computer died.
may be suhu @zhalx or some one else.
Btw are you using whatsapp man?
inyong1 said:
I feel happy to know you are still trying for this. I can not try it now because my computer died.
may be suhu @zhalx or some one else.
Btw are you using whatsapp man?
Click to expand...
Click to collapse
Sorry, I don't have whatsapp. If you can try to contact zhalx to go back on XDA, it will be good. Thanks
phone my friend died after trying this idea. now can not be detected by RSDlite.
unable to enter bootloader mode by pressing (and hold) camera, vol(-), and power keys.
can you help him, please.
inyong1 said:
phone my friend died after trying this idea. now can not be detected by RSDlite.
unable to enter bootloader mode by pressing (and hold) camera, vol(-), and power keys.
can you help him, please.
Click to expand...
Click to collapse
I think that battery is worn out? You can't hardbrick due to locked bootloader.
@rootdefyxt320 can you build 2ndboot binary for our fire xt530/531. Please.
,,,,,,,,
by the way, what chat application are you using?. I use whatsapp, Catfiz (nic:2ED3D003F4) and ym (ID: upriecs)
inyong1 said:
@rootdefyxt320 can you build 2ndboot binary for our fire xt530/531. Please.
,,,,,,,,
by the way, what chat application are you using?. I use whatsapp, Catfiz (nic:2ED3D003F4) and ym (ID: upriecs)
Click to expand...
Click to collapse
Also, my main computer has died so I don't have a Linux system up and running.
2ndboot doesn't work for Qualcomm as it targeted for OMAP. The good thing about Qualcomm BP's is that they can be restarted without panicking, so we can use kexec instead. I got to learn how to compile modules first before moving onto this stuff. Sorry, I don't use a chat application.
rootdefyxt320 said:
I think that battery is worn out? You can't hardbrick due to locked bootloader.
Click to expand...
Click to collapse
about my friend phone, still unable to get bootloader mode.
he said before flashing the battery level still 80% remaining.
Now 60% remaining. he checked on his defy mini.
sorry for my english, I hope you understand what I am talking about. hehehe
And I hope you can help my friend.
inyong1 said:
about my friend phone, still unable to get bootloader mode.
he said before flashing the battery level still 80% remaining.
Now 60% remaining. he checked on his defy mini.
sorry for my english, I hope you understand what I am talking about. hehehe
And I hope you can help my friend.
Click to expand...
Click to collapse
*** I never this SBF would hardbrick XT530. The only advice I can tell him is to send it off to the service centre
rootdefyxt320 said:
*** I never this SBF would hardbrick XT530. The only advice I can tell him is to send it off to the service centre
Click to expand...
Click to collapse
maybe you have a tips how to get in to bootloader mode. (before we send it to SC).
inyong1 said:
maybe you have a tips how to get in to bootloader mode. (before we send it SC).
Click to expand...
Click to collapse
Does the phone vibrate when you connect to the computer? If it does means that the phone is soft-bricked and we can flash a SBF to revive it.
This method hardbricks the device. It is advised not to use it. An IC (maybe software one) breaks and becomes liquid upon flashing. Therefore, the only solution to it is motherboard replacement.
Sent from my C1904 using xda app-developers app
Related
Hi
I made a very stupid mistake
I used the tool to root my xoom wifi model
I used the tool in this thread
http://forum.xda-developers.com/showthread.php?t=1011196
I tried to post this issue in the thread but I did not have the permissions.
by mistake I used the root of the 3G model
I followed the steps and everything was ok
I tried the unroot and here is the deadly (hopefully not) mistake
the xoom stops and first screen and refuses to boot
Did I brick my device??
Is there a way to resolve this problem??
Thanks
Yes, you have bricked it. Fastboot won't work at this point, so your only option is probably to return it.
-Jim (who's on his 2nd xoom)
Sent from my Xoom using Tapatalk
nawialkair said:
Hi
I made a very stupid mistake
I used the tool to root my xoom wifi model
I used the tool in this thread
http://forum.xda-developers.com/showthread.php?t=1011196
I tried to post this issue in the thread but I did not have the permissions.
by mistake I used the root of the 3G model
I followed the steps and everything was ok
I tried the unroot and here is the deadly (hopefully not) mistake
the xoom stops and first screen and refuses to boot
Did I brick my device??
Is there a way to resolve this problem??
Thanks
Click to expand...
Click to collapse
what does the first screen say? failed boot image?
BeagleBoy said:
Yes, you have bricked it. Fastboot won't work at this point, so your only option is probably to return it.
-Jim (who's on his 2nd xoom)
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
That's the thing I did not want to hear but expected it.
============================================
znfrazier said:
what does the first screen say? failed boot image?
Click to expand...
Click to collapse
No
I am stuck at the motorola logo and the word dual core technology
When I press Volume up or down (fanrkly I could not get into that menu again) I get a list
it includes the following:
Fast Boot
If I choose it I get
Starting Fastboot protocol support
nawialkair said:
That's the thing I did not want to hear but expected it.
============================================
No
I am stuck at the motorola logo and the word dual core technology
When I press Volume up or down (fanrkly I could not get into that menu again) I get a list
it includes the following:
Fast Boot
If I choose it I get
Starting Fastboot protocol support
Click to expand...
Click to collapse
Can you see the xoom in /fastboot devices? See if you can access you xoom from the computer. I actually did the same thing and got mine in working order.
nawialkair said:
That's the thing I did not want to hear but expected it.
============================================
No
I am stuck at the motorola logo and the word dual core technology
When I press Volume up or down (fanrkly I could not get into that menu again) I get a list
it includes the following:
Fast Boot
If I choose it I get
Starting Fastboot protocol support
Click to expand...
Click to collapse
Try doing this real quick, the best that can happen is that you can turn this around. You may NOT in fact be bricked. I made the mistake of doing this also, but I figured it is just like when I was using the Danger SPL on the G1 and I had to at least find a way.
So, do this real quick if you know how.
1. Power on and press Vol - at the same time
2. Open a command prompt to your ADB file and type in fastboot oem unlock
3. If this lets you in (it may not) go through the regular procedure of pressing Vol -+-+
4. It will format and you should know if it is in fact bricked or not because it won't boot up.
5. ******
6. Profit???
Let us know how it goes.
znfrazier said:
Can you see the xoom in /fastboot devices? See if you can access you xoom from the computer. I actually did the same thing and got mine in working order.
Click to expand...
Click to collapse
Yes I can see it
Thank you
stevenege said:
Try doing this real quick, the best that can happen is that you can turn this around. You may NOT in fact be bricked. I made the mistake of doing this also, but I figured it is just like when I was using the Danger SPL on the G1 and I had to at least find a way.
So, do this real quick if you know how.
1. Power on and press Vol - at the same time
2. Open a command prompt to your ADB file and type in fastboot oem unlock
3. If this lets you in (it may not) go through the regular procedure of pressing Vol -+-+
4. It will format and you should know if it is in fact bricked or not because it won't boot up.
5. ******
6. Profit???
Let us know how it goes.
Click to expand...
Click to collapse
I did that
and it started the format
After the boot, it stopped at the same place
Motorola's Logo and Dual Core
What's next??
thanks
root using the instructions in this thread it should fix your problem
http://forum.xda-developers.com/showthread.php?t=1010568
nawialkair said:
Yes I can see it
Thank you
I did that
and it started the format
After the boot, it stopped at the same place
Motorola's Logo and Dual Core
What's next??
thanks
Click to expand...
Click to collapse
you should try flashing the boot.img used to root i believe its tiamat 1.1.6 and the system.img for wifi. i have the stock system.img if you need it. hopefully that would git ya to boot atleast. MAKE SURE THAT IT IS WIFI ONLY.
Go here and follow the second post I posted. This will help you do this without downloading the files because they are already there.
Give it a shot at least
stevenege said:
Go here and follow the second post I posted. This will help you do this without downloading the files because they are already there.
Give it a shot at least
Click to expand...
Click to collapse
did they fix the boot prob with the one click? i haven't tried it.
znfrazier said:
did they fix the boot prob with the one click? i haven't tried it.
Click to expand...
Click to collapse
Yes, it has all been fixed. There still seems to be an issue with SU rights until you download BusyBox and no clue why.
I have been testing the WiFi one constantly and have not had any major hickups.
stevenege said:
Yes, it has all been fixed. There still seems to be an issue with SU rights until you download BusyBox and no clue why.
I have been testing the WiFi one constantly and have not had any major hickups.
Click to expand...
Click to collapse
good good. ill have to check it out. i still need to try out the pimp my xoom. ill post over there haha. gotta stay on topic.
Thanks ALL
I flashed Tiamat 1.1.6 boot.img
the problem is that when using this command:
adb remount
I get
error: device not found
The xoom is defined in the device manager as
Android adb Interface
nawialkair said:
Thanks ALL
I flashed Tiamat 1.1.6 boot.img
the problem is that when using this command:
adb remount
I get
error: device not found
The xoom is defined in the device manager as
Android adb Interface
Click to expand...
Click to collapse
Sounds like you are probably bricked :-/
Can I get the stock boot image
I just want to try that last option
I flashed the stock img and system img
It works fine
Yaaaaa
Thanks very much
Thanks very much
nawialkair said:
I flashed the stock img and system img
It works fine
Yaaaaa
Thanks very much
Thanks very much
Click to expand...
Click to collapse
Told ya haha, save those files on your computer for next time. I keep them in close reach just incase something happens. if you have any other problems give me a holla. glad everything is working again.
I think I'm more screwed than OP because I was already unlocked and rooted. Then locked my wifi xoom with the 3g one click tool. Yes I know that was very stupid but I was wondering what are my options?
Take it back to Amazon?
Use the following method in this thread?
Wait for SBF?
Thank you your time and sorry if I hijacked this thread.
jarretf said:
I think I'm more screwed than OP because I was already unlocked and rooted. Then locked my wifi xoom with the 3g one click tool. Yes I know that was very stupid but I was wondering what are my options?
Take it back to Amazon?
Use the following method in this thread?
Wait for SBF?
Thank you your time and sorry if I hijacked this thread.
Click to expand...
Click to collapse
It relocked? Yikes... I don't trust those 1-click things. I need to know what's going on step by step. My first Xoom got bricked when I thought I had untainted OEM image files and relocked it. There's really no reason to relock a Wifi Xoom right now.
Anyway, if it relocked, you might have been in the same boat I was where the computer wouldn't recognize the Xoom in Fastboot mode or RSD mode. And I went and got it exchanged at that point.
Oh, if RSD Lite can't see your Xoom in RSD mode, you might be out of luck. SBF won't help if RSD Lite can't see your Xoom. BUT, if it does see it, it sounds like you can flash the 3G/4G SBF from Motorola/Verizon and to get sorta running, then use Fastboot to overwrite the boot and system partitions.
I tried rooting my phone, but when I flashed CWM my Nexus S stopped booting... it freezes on the Google screen in the intro. I can boot into Fastboot, and cwm, but I cant connect the Internal memory to the computer without it booting like it is supposed to. Does anybody know of anything I can do to fix my phone and bring it back to stock??
There are guides for returning to stock stickied in the Nexus S 4G Android Development forum.
Before you do that though, try flashing a different recovery, like the one linked to here or here.
Btw, which guide did you use? You're not the first person to have this problem, and it's really bugging me (though probably not as much as it's bugging you :-o).
Maximilian Mary: I tried to post the link, but since I'm a new member I have to wait 8 posts before I can post a URL.... :/
I will try a different recovery, but how would I flash a rom if I can connect my phone via usb mount?
deadzunehd said:
Maximilian Mary: I tried to post the link, but since I'm a new member I have to wait 8 posts before I can post a URL.... :/
Click to expand...
Click to collapse
What's the title of the thread?
.
I will try a different recovery, but how would I flash a rom if I can connect my phone via usb mount?
Click to expand...
Click to collapse
I'm a little out of my depth here, but I think it's
fastboot flash system system.img.
You don't need to put the rom image on the sdcard. Just put it in the same folder as fastboot.
It was titled "How to Root Nexus S!"
And I will try to flash recovery and try that rom command, thank you )
deadzunehd said:
It was titled "How to Root Nexus S!"
And I will try to flash recovery and try that rom command, thank you )
Click to expand...
Click to collapse
Hmmm. I can't find that exact title. Could you pm me the link?
deadzunehd said:
thank you )
Click to expand...
Click to collapse
There's a button for that.
I got the link. Thanks. I looks like you flashed a boot image that is incompatible with your phone. That guide was for the T-Mobile Nexus S. (Why they're screwing with the boot.img to begin with, I really don't understand.)
Download the attached file, and unzip it to the same folder as fastboot. The md5 sum is d4a9508f9321eb25df3383f00f571e8b. Then
Code:
fastboot flash boot boot.img
You'll probably also want to use one of the recoveries listed above to
Code:
fastboot flash recovery recovery.img
, but leave system alone for now. Flash that only as a last resort.
deadzunehd said:
I tried rooting my phone, but when I flashed CWM my Nexus S stopped booting... it freezes on the Google screen in the intro. I can boot into Fastboot, and cwm, but I cant connect the Internal memory to the computer without it booting like it is supposed to. Does anybody know of anything I can do to fix my phone and bring it back to stock??
Click to expand...
Click to collapse
I had this problem after flashing the wrong ROM onto my phone. I got the phone back to stock using ODIN.
My thread can be found here
http://forum.xda-developers.com/showthread.php?p=14172335#post14172335
hope it helps
Acnescar said:
I had this problem after flashing the wrong ROM onto my phone. I got the phone back to stock using ODIN.
My thread can be found here
http://forum.xda-developers.com/showthread.php?p=14172335#post14172335
hope it helps
Click to expand...
Click to collapse
OMG!! im having the same issue. could you please post the link for ODIN so i can return to stock and take it from there please? I rely on my phone so much and i need it asap thank you.
same problem with me.
but in my case, the phone not only freeze after the google logo before boot. I tried several times to pull the battery and start the phone again, it took several times until the phone can boot normally again.
After that, my nexus s can work as usual. but it only takes 3-4 hour until it freeze/hangs or reboot automatically and show image of green robot lay down with red alert triangle...
sometimes I noticed all application force closed like gmail, gtalk, etc. (its a basic apps instead of 3rd party app)
History :
- root GB 2.37 using superoneclick
- upgrade OTA to ICS 4.04
- problem happens
- root using guide : nexusshacks.com
- unroot using guide : nexusshacks.com
- back to factory setting on GB 2.34
- upgrade OTA to ICS 4.04
- Still got that problem.....
I'm using Nexus S 4G Sprint, pls help me guys...
nexus s won't boot
I had the same problem and read elsewhere that heating the phone with a hairdryer solves the problem.
I must say, indeed it did.
I removed the battery and the SIM card, then heated up the phone (so it really feels warm) put back the battery and sim and simsalebim the phone started again. and is still working since (now already a few day's)
It seems that a component in the phone is heat sensitive, the question in my mind is when will this show again and do I need to consider buying a new phone.
But sofar it works
PS I also tried hard reset factory reset the lot, but in the end only heating up helped.
Good luck, David
I fixed this problem! but I had to wipe all user data by rooting it using nexusrootICS. It finally boots up and the phone works now... that's all I need.
I have a problem with the power button i push it and this is what i get
AP Fastboot Flash Mode (S) (Flash Failure)
0A.68
Battery OK
OK to Program
Connect USB
Data Cable
But with vol-&+&pwr button i choose normal mode and it works just fine.
The problem is tha i cant fix it with rsd lite + InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID285.
So if i want to get an update it will try to reboot and will not start up to setup the update
I have even tried the Blur_Version.55.28.37.MB865.MERetail.en.06.andcrc but still nothing.
Atrix 2 At&t sorry for my english
biupil said:
I have a problem with the power button i push it and this is what i get
AP Fastboot Flash Mode (S) (Flash Failure)
0A.68
Battery OK
OK to Program
Connect USB
Data Cable
But with vol-&+&pwr button i choose normal mode and it works just fine.
The problem is tha i cant fix it with rsd lite + InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID285.
So if i want to get an update it will try to reboot and will not start up to setup the update
I have even tried the Blur_Version.55.28.37.MB865.MERetail.en.06.andcrc but still nothing.
Atrix 2 At&t sorry for my english
Click to expand...
Click to collapse
First of all your phone is fine, since it is booting. You can continue to choose normal power up and be fine.
To fix you need to flash the fxz and replace the files to allow you to do it after being on 2.3.6. see here http://forum.xda-developers.com/showthread.php?t=1396650
unfortunately i cant flash the fxz it says failed all the time, its like its locked, i tried.
biupil said:
unfortunately i cant flash the fxz it says failed all the time, its like its locked, i tried.
Click to expand...
Click to collapse
did you replace the files
Sent from my MB865 using xda premium
yes my friend and this is what it says
biupil said:
yes my friend and this is what it says
Click to expand...
Click to collapse
hmm. Is your phone the AT&T version or one of the international ones? Make sure you are using the correct fxz file for your device, that is most likely the problem with the step it is failing on find a list here: http://sbf.droid-developers.org/edison/list.php
Go to settings- about phone and look at system version. That should tell you what version you are. it will be 55.13.25.MB865.VERSION.... or something like that, you should be able to tell which you are
it is At&t
system version 55.11.16.MB865.ATT.en.US i have downloaded the
InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID285.Zip that is for At&t is that correct?
biupil said:
it is At&t
system version 55.11.16.MB865.ATT.en.US i have downloaded the
InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID285.Zip that is for At&t is that correct?
Click to expand...
Click to collapse
yep that is the correct one. have you ever tried to flash a different one? that may have messed something up.
Try this, it may work. It is just a script that runs the fastboot comands. Extract it and run the stock restore file in it:
https://docs.google.com/open?id=0B_F787JD56X9SjZSUlljQ2ZYdFk
yes i have tried the Blur_Version.55.28.37.MB865.MERetail.en.06.andcrc as i said before. I will try the one that you told me and i will inform you...
biupil said:
yes i have tried the Blur_Version.55.28.37.MB865.MERetail.en.06.andcrc as i said before. I will try the one that you told me and i will inform you...
Click to expand...
Click to collapse
that is probably the problem. there are some files you will have to skip flashing in order to make it work I think. PM jimbridgman (i think thats how you spell it and ask him for help)
nope still the same lets hope that jimbridgman can help
lkrasner thank you for your time.
biupil said:
nope still the same lets hope that jimbridgman can help
lkrasner thank you for your time.
Click to expand...
Click to collapse
he should be able to just link him to this thread and be nice.
I also just replied to your PM, but I wanted to put this here as well, so others can also see it.....
This just a theory, since no one has done this yet, so we might have to try a few things to get it right
my first guess is to do this:
Take the following files from the update that you flashed and replace their counterparts in the 2.3.5 fxz, and update the md5 sums in the xml file, you can google for a windows md5sum executable for windows.
Here is a link to a good place to find the m5sums for windows7:
http://www.walkernews.net/2009/12/26/how-to-check-md5-checksum-in-windows-7/
files you will need from the leak:
cdt.bin
device_tree.bin
lbl
now once you have them in the same folder as the rest of the 2.3.5 fxz, use that exe I told you grab to get their md5 sums, and replace those numbers in the xml file in the 2.3.5 fxz, this should get you back to 2.3.5, in theory.
Jim
wtf my brain hurts already lol. I will try to do it in the morning i will inform you for the results.
i realy understand nothing at all of this. unfortunatly my phone will stay as it is.
biupil said:
I have a problem with the power button i push it and this is what i get
AP Fastboot Flash Mode (S) (Flash Failure)
0A.68
Battery OK
OK to Program
Connect USB
Data Cable
But with vol-&+&pwr button i choose normal mode and it works just fine.
The problem is tha i cant fix it with rsd lite + InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID285.
So if i want to get an update it will try to reboot and will not start up to setup the update
I have even tried the Blur_Version.55.28.37.MB865.MERetail.en.06.andcrc but still nothing.
Atrix 2 At&t sorry for my english
Click to expand...
Click to collapse
download the fxz and replace files from noob thread. extract and replace files, after replacing erase third line
i.e <step operation="flash" partition="mbmloader" filename="mbmloader.bin"MD5="9D1958ED3F5E971FF079B195E338BA86" />
from InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID28 5.xml and flash it using rsd lite it will definetely work as i had the same problem
thanks man i just love u my phone works perfectly
I've got the Canadian Virgin Mobile Moto G, and I recently unlocked the carrier. I am going to unlock to bootloader to flash a rom with more languages, specifically Portuguese.. What rom should I use, I'm looking for the original Moto G software.
Zehmistah said:
I've got the Canadian Virgin Mobile Moto G, and I recently unlocked the carrier. I am going to unlock to bootloader to flash a rom with more languages, specifically Portuguese.. What rom should I use, I'm looking for the original Moto G software.
Click to expand...
Click to collapse
I'm running CM11 and a quick look the phone tells me that it have Portuguese for brazil and portugal, alternatively try any latin american stock rom: http://sbf.droid-developers.org/phone.php?device=14
Z-WolF said:
I'm running CM11 and a quick look the phone tells me that it have Portuguese for brazil and portugal, alternatively try any latin american stock rom: http://sbf.droid-developers.org/phone.php?device=14
Click to expand...
Click to collapse
Oh man, thank you for the link, I just might use that. Just a refresher, to flash It I would first unlock the bootloader, flash a new recovery, wipe, and then flash the new rom?
Zehmistah said:
Oh man, thank you for the link, I just might use that. Just a refresher, to flash It I would first unlock the bootloader, flash a new recovery, wipe, and then flash the new rom?
Click to expand...
Click to collapse
yep, but you don't need to flash a custom recovery for a Stock ROM.
Z-WolF said:
yep, but you don't need to flash a custom recovery for a Stock ROM.
Click to expand...
Click to collapse
Thank you!!! and one more question, the new rom should still be capable of getting OTA updates from whatever carrier's rom I flashed, correct?
Zehmistah said:
Thank you!!! and one more question, the new rom should still be capable of getting OTA updates from whatever carrier's rom I flashed, correct?
Click to expand...
Click to collapse
****. I think I ****ed up. http://forum.xda-developers.com/showthread.php?t=2727965
Zehmistah said:
****. I think I ****ed up. http://forum.xda-developers.com/showthread.php?t=2727965
Click to expand...
Click to collapse
Zehmistah said:
Okay so I unlocked my bootloader for my Moto G, and when It rebooted it said android was updating apps and then all the processes stopped working. It booted into the android startup but I couldn't get any processes running so it wouldnt work. I tried to reboot and now android doesn't even boot up. Should I flash a custom recovery right now and then wipe??? I haven't done anything to the phone other than carrier unlock and bootloader unlock. please help
Should I try this? http://forum.xda-developers.com/showthread.php?t=2542219 , or is it too risky right now? I'm planning to restore it to another stock firmware anyways.
Click to expand...
Click to collapse
First, don't panic.
Second, explain how do you unlock the bootloader, did you use this?
Third, what does the bootloader screen (Power+VolDown) says in the second to last line before the first break (LOCKED/UNLOCKED).
Fourth, if it says UNLOCKED, try to flash the ROM using this, otherwise try to unlock the bootloader again with the link i posted in the second point.
And don't worry as long as you can enter fastboot mode (bootloader) you can fix everything, and nothing of the things you are doing affects fastboot mode.
They all want money.
Sent from my GT-N7105 using xda app-developers app
Perry2547 said:
They all want money.
Sent from my GT-N7105 using xda app-developers app
Click to expand...
Click to collapse
Can you elaborate?
You can add more languages without a custom ROM using MoreLocale 2.
Z-WolF said:
First, don't panic.
Second, explain how do you unlock the bootloader, did you use this?
Third, what does the bootloader screen (Power+VolDown) says in the second to last line before the first break (LOCKED/UNLOCKED).
Fourth, if it says UNLOCKED, try to flash the ROM using this, otherwise try to unlock the bootloader again with the link i posted in the second point.
And don't worry as long as you can enter fastboot mode (bootloader) you can fix everything, and nothing of the things you are doing affects fastboot mode.
Click to expand...
Click to collapse
I used that webstie to unlock the bootloader, and when I went to fastboot it did say UNLOCKED status code: 3.
I left it plugged into my PC last night because It wouldn't turn off, and I think it wasn't charging because now it's off and won't turn on. I'm going to plug it into a wall charger and wait a few to check if it's on.
After that, I'll try the method you said.
EDIT: Seems like charging doesn't work either, weird... because it said it was connecting to my PC last night in Fastboot
Zehmistah said:
I used that webstie to unlock the bootloader, and when I went to fastboot it did say UNLOCKED status code: 3.
I left it plugged into my PC last night because It wouldn't turn off, and I think it wasn't charging because now it's off and won't turn on. I'm going to plug it into a wall charger and wait a few to check if it's on.
After that, I'll try the method you said.
EDIT: Seems like charging doesn't work either, weird... because it said it was connecting to my PC last night in Fastboot
Click to expand...
Click to collapse
That's weird, doing the steps in that page don't make changes big enough in the phone to make something like that happen.
What does it says in the line below UNLOCKED, USB CONNECTED or CONNECT USB DATA CABLE while you had it connected to your pc/wall?
Why don't you try to use another cable?
Z-WolF said:
That's weird, doing the steps in that page don't make changes big enough in the phone to make something like that happen.
What does it says in the line below UNLOCKED, USB CONNECTED or CONNECT USB DATA CABLE while you had it connected to your pc/wall?
Why don't you try to use another cable?
Click to expand...
Click to collapse
I don't remember what it said.
I've tried a few different wall chargers and cables. They seem to charge my other phones but not this one. I'm going to wait an hour and then maybe put it in the freezer for a few minutes
Zehmistah said:
I don't remember what it said.
I've tried a few different wall chargers and cables. They seem to charge my other phones but not this one. I'm going to wait an hour and then maybe put it in the freezer for a few minutes
Click to expand...
Click to collapse
That's a... unorthodox approach, but reading around it just might work.
I can only recommend you to put it in a sealed container and having a rice bag at hand afterwards, just in case.
Now if you can get it to fastboot mode, try to restore a backup (if you did one) or flash a ROM, im assuming that if you can connect a cable and send commands to fastboot it is charging the phone. BTW at this point if you can send commands and are tired trying to fix it, you can execute
Code:
fastboot oem lock
and you can claim the warranty, that behaviour is not normal, maybe something in the hardware side broke but until we test it more we can't be sure.
Now while we wait in for the phone to become a popsicle, can you detail how you unlocked it?
Z-WolF said:
That's a... unorthodox approach, but reading around it just might work.
I can only recommend you to put it in a sealed container and having a rice bag at hand afterwards, just in case.
Now if you can get it to fastboot mode, try to restore a backup (if you did one) or flash a ROM, im assuming that if you can connect a cable and send commands to fastboot it is charging the phone. BTW at this point if you can send commands and are tired trying to fix it, you can execute
Code:
fastboot oem lock
and you can claim the warranty, that behaviour is not normal, maybe something in the hardware side broke but until we test it more we can't be sure.
Now while we wait in for the phone to become a popsicle, can you detail how you unlocked it?
Click to expand...
Click to collapse
Ok, so I bought the phone and got it carrier unlocked, then yesterday I decided to flash a new rom to get the languages so I went to https://motorola-global-portal.cust...e/bootloader/unlock-your-device-a/action/auth. Unlocked the bootloader and when the phone was about to restart from cmd it said "FAILED" but rebooted anyways. It went into fastboot again and ti said it was Unlocked, when I selected Normal Reboot, it started up with the bootloader logo and continued on normally. It was then that it displayed the android startup page (Where you select language, sign into google, connect to wifi etc.) like I haven't used the phone before. Shortly after a popup came and said " Android is updating # of apps out of 137", once that was over every single process on the phone crashed.
Now I'm where I am now.
One more thing, I booted it into recovery before I unlocked the bootloader, accidently. Do you think it maybe could've wiped the original OS on the device?
Zehmistah said:
Ok, so I bought the phone and got it carrier unlocked, then yesterday I decided to flash a new rom to get the languages so I went to https://motorola-global-portal.cust...e/bootloader/unlock-your-device-a/action/auth. Unlocked the bootloader and when the phone was about to restart from cmd it said "FAILED" but rebooted anyways. It went into fastboot again and ti said it was Unlocked, when I selected Normal Reboot, it started up with the bootloader logo and continued on normally. It was then that it displayed the android startup page (Where you select language, sign into google, connect to wifi etc.) like I haven't used the phone before. Shortly after a popup came and said " Android is updating # of apps out of 137", once that was over every single process on the phone crashed.
Now I'm where I am now.
One more thing, I booted it into recovery before I unlocked the bootloader, accidently. Do you think it maybe could've wiped the original OS on the device?
Click to expand...
Click to collapse
As far as i know, you can't wipe the system with a stock recovery and with a "blank" OS your phone still connects to PC.
i forgotted this existed, at this point you can't lose anything in trying it. i dont recomend the bootloader bricker part for your case.
Z-WolF said:
As far as i know, you can't wipe the system with a stock recovery and with a "blank" OS your phone still connects to PC.
i forgotted this existed, at this point you can't lose anything in trying it. i dont recomend the bootloader bricker part for your case.
Click to expand...
Click to collapse
The phone isnt't being detected when I plug it in.
I've read that leaving the phone 24 hours untouched could also help the battery. I'm going to try that\
EDIT: GOT IT TO TURN ON!!!
Ok, so I got it working. The thread you told me first helped!! It works fine now with the Brazilian software. Thank you very much, you're a life saver.
Now... I've got another moto G to do the same to
Zehmistah said:
Ok, so I got it working. The thread you told me first helped!! It works fine now with the Brazilian software. Thank you very much, you're a life saver.
Now... I've got another moto G to do the same to
Click to expand...
Click to collapse
You had me worried there, i though it was a goner. in the end everything turned out okay.
Happy to be of service.
Sorry for posting this, but please just try to understand me and help solve my problem. I know there is Threads for this, Please... I am just nowhere, my phone just treason me when I needed it most, It is very hard Bricked, nothing working, contacted support and they told me it need Replace (but I can't send to service #close this question)
My Story:
Constant restart loop, on Motorola logo. It can go in Bootloader when press Vol Down and Power Button, but that's it, (actually when going in recovery it goes to Broken Android sign, but than restart again)... so how it happened?? I do not know as u do not, I am just normal user, never done anything to crash system, never Rooted, even not installed any kind Launcher, nothing, just some normal Apps and only two game, and lot of music listening, that's it that's all (also physically it's like new, never ever droped or water splashed even). and one day come home, plug in for charging in my PC as always and boom, some strange app crashes and it restarted for EVERRR, wtf is this just do not understand, WHYY?????? so disappointed and so bored...
Question:
so Can it be Helped? Unbricked? I do not care Contacts or any kind Data, just work again....And if it can please step by step I will follow, and do not redirect me to other thread, just help me out here please
And if it cant be Helped, just say frankly and I will capture video how I am splashing it on REAL BRICK wall and will post it on this thread...this will be closing and **** sending of Motorola
My Spec:
Moto G (16GB Global GSM, no SD card slot, single SIM) - KitKat 4.4.4 (it bricked so I cant see Falcon version or other spec, but I have original Box)
I searched everywhere and seen lot, but all of them are 4.4.2 or 3 and also US versions, strange languages and so on. also here on XDA but as I'm Noob I do not know if it will work for me, and before destroy it completely I wanted to know from people who knows much more then me, what can do and what not, so please be patient for my Noobety, Thanks and Sorry...
help_me_if_u_can said:
Sorry for posting this, but please just try to understand me and help solve my problem. I know there is Threads for this, Please... I am just nowhere, my phone just treason me when I needed it most, It is very hard Bricked, nothing working, contacted support and they told me it need Replace (but I can't send to service #close this question)
Click to expand...
Click to collapse
Do you use Windows, Linux, Mac?
EDIT: Have you tried this yet? http://forum.xda-developers.com/showthread.php?t=2542219
StrangerWeather said:
Do you use Windows, Linux, Mac?
EDIT: Have you tried this yet? http://forum.xda-developers.com/showthread.php?t=2542219
Click to expand...
Click to collapse
I have Windows 8 x64, I did not tryed anything yet, want to know what would be clever and correct to do in my situation...which one should I download ???? from here
have no idea, all I know is before It bricked it was on 4.4.4 and I do not have US version, it is GLOBAL GSM
and it is Locked, never Unlocked Bootloader
help_me_if_u_can said:
I have Windows 8 x64, I did not tryed anything yet, want to know what would be clever and correct to do in my situation...which one should I download ???? from here
have no idea, all I know is before It bricked it was on 4.4.4 and I do not have US version, it is GLOBAL GSM
and it is Locked, never Unlocked Bootloader
Click to expand...
Click to collapse
Dual sim or single sim? What region?
StrangerWeather said:
Dual sim or single sim? What region?
Click to expand...
Click to collapse
Single Sim, Georgia (not in US)
help_me_if_u_can said:
Single Sim, Georgia (not in US)
Click to expand...
Click to collapse
Ok, is it XT1032?
Don't worry, we'll get there...
StrangerWeather said:
Ok, is it XT1032?
Click to expand...
Click to collapse
I do not remember, is there any way to check it? I will do that if so, thanks
help_me_if_u_can said:
I do not remember, is there any way to check it? I will do that if so, thanks
Click to expand...
Click to collapse
Not sure. Just one thought, why don't you try a factory reset? https://www.youtube.com/watch?v=LoTAsuPey_E
StrangerWeather said:
Not sure. Just one thought, why don't you try a factory reset?
Click to expand...
Click to collapse
Remember with Support Team I already did that, but not worked.
I will try again as in this video after couple hours and share results quickly.
StrangerWeather said:
Not sure. Just one thought, why don't you try a factory reset?
Click to expand...
Click to collapse
so, I can reach to wipe manu and wiped it also wipe cache from there but not like in this video, my device is laggin on every step and after I wiped it steel when restart it normaly stuckes on Motorola
one thing to add, my device is not Power Off, it constatnly restating, if I will try to power off it will power on again
help_me_if_u_can said:
so, I can reach to wipe manu and wiped it also wipe cache from there but not like in this video, my device is laggin on every step and after I wiped it steel when restart it normaly stuckes on Motorola
one thing to add, my device is not Power Off, it constatnly restating, if I will try to power off it will power on again
Click to expand...
Click to collapse
Ok, don't worry, just follow the tutorial to reflash stock firmware and it will work again.
You need this: http://www.filefactory.com/file/1dw..._4.4.4_KXB21.14-L1.40_36_cid7_CFC_1FF.xml.zip
The only thing to say is that when you reach:
Code:
mfastboot flash system system.img_sparsechunk1
mfastboot flash system system.img_sparsechunk2
mfastboot flash system system.img_sparsechunk3
you may have to try this instead if it doesn't work:
Code:
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
Let us know how it goes!
okey I will try it right now, thaanks
StrangerWeather said:
Let us know how it goes!
Click to expand...
Click to collapse
I tryed but no result, I think because that my bootloader is locked....here I made screenshot of whole process and every command gives me [OKEY] but after that is failure....it I think is permissions problem because locked bootloader
So, I need to unlock it right?????? I already have key from motorola, just get... I will wait your answer...
StrangerWeather
??????????????
help_me_if_u_can said:
StrangerWeather
??????????????
Click to expand...
Click to collapse
Oops, sorry, I forgot... It's up to you about unlocking bootloader. If you do, you can't send your phone back for them to sort out the problem. However, if you root your phone, you'll be able to install a custom recovery such as TWRP, sideload a rom, and hopefully all will work. But of course I can't guarantee that it will work, so it's a risk. If it were me, I would send it back as you haven't rooted it and really it shouldn't brick itself on its own for no reason.
StrangerWeather said:
Oops, sorry, I forgot... It's up to you about unlocking bootloader. If you do, you can't send your phone back for them to sort out the problem. However, if you root your phone, you'll be able to install a custom recovery such as TWRP, sideload a rom, and hopefully all will work. But of course I can't guarantee that it will work, so it's a risk. If it were me, I would send it back as you haven't rooted it and really it shouldn't brick itself on its own for no reason.
Click to expand...
Click to collapse
tell me, if I want to install this stock firmware I need to unlock bootloader??? and because it not installing? or my device is problematic and it can be installed on locked bootloader?
help_me_if_u_can said:
tell me, if I want to install this stock firmware I need to unlock bootloader??? and because it not installing? or my device is problematic and it can be installed on locked bootloader?
Click to expand...
Click to collapse
This what the op says:
I have only tested this on a UK Retail Moto G with an unlocked bootloader, however as these are the original stock signed image files from Motorola it should work on all devices.
[. . .]
Edit: tkm89 reports that he was able to use this guide to restore Stock Retail British firmware on a bootloader locked Tesco-mobile Moto G
Click to expand...
Click to collapse
StrangerWeather said:
This what the op says:
Click to expand...
Click to collapse
I unlocked BOOTLOADER but steel geting Fail after OKEY, what could be reason? can I do something??? any ****ing thing to start this device working??
help_me_if_u_can said:
I unlocked BOOTLOADER but steel geting Fail after OKEY, what could be reason? can I do something??? any ****ing thing to start this device working??
Click to expand...
Click to collapse
I'm not sure what the reason is but if I were you I would now try to root my device, install TWRP, sideload a rom, and hope for the best.
To root, use: http://www.theandroidcop.com/how-to-root-motorola-moto-g/
Hope it goes well!
no help....
on every step, I am getting Fails....What could be Problem??? drivers??? or what?????? ANYONE????????
Unlocked Bootloader