Hey guys,
i just started with falshing and those things. So i'm not so familiar with building and unlocking.
I bought a M2 with QUWERTY. I had and still has bootloop problems according to: http://forum.xda-developers.com/showthread.php?t=1457373
While analysing my bootproblem, i just realized, that i have a Fastboot Bootloader installed on this phone, what seems a little special.
Next step may be, to use the fastboot get this phone work, step after, use fastboot for improve this forum . But as i said, i'm new in this deep hardware near software-things, so need all your help for that .
greetz
how strange this in your bootloader, is similar as in the Atrix? So you installed it? I would like to know more about this topic
Looks like you have a dev phone. There are a couple of forum users with dev phones
Does rsdlite recognize it? I think you should try to have a look in Motorola Defy Android Development: there is a thread named ''experimental: trying to unlock the bootloader " (look at pages 60-75) .
I think someone wrote about some particular roms to be flashed in case of unlocked phones....
Does anyone know a way to extract this bootloader??
If so, I believe that lowering the fastboot and giving the command would be possible to unlock the MS2
Fastboot => http://www.mediafire.com/?2zdhukq3ha1qlrd
1) "fastboot oem unlock" to see the Station ID
2) "fastboot oem unlock ID" to unlock the bootloader
Hi everyone,
I'm following a thread about bootloader unlocking on the Defy section and scholbert suggested to make this little experiment:
Code:
dd if=/dev/block/mmcblk1 of=/sdcard/mmcblk1.raw bs=512 count=2048
then zip the raw file and upload it to the thread so that he can compare different dumps of that particular section of the rom, to discover a pattern which might lead to further understanding of how the lock works.
Source:
http://forum.xda-developers.com/showpost.php?p=21885753&postcount=735
Click to expand...
Click to collapse
djlooka said:
Hi everyone,
I'm following a thread about bootloader unlocking on the Defy section and scholbert suggested to make this little experiment:
Code:
dd if=/dev/block/mmcblk1 of=/sdcard/mmcblk1.raw bs=512 count=2048
then zip the raw file and upload it to the thread so that he can compare different dumps of that particular section of the rom, to discover a pattern which might lead to further understanding of how the lock works.
Source:
Click to expand...
Click to collapse
i think you can send PM to MKSilver.
Lutis said:
i think you can send PM to MKSilver.
Click to expand...
Click to collapse
I already did
Anyway I think the more dumps are posted, the better it is!
Hey there,
well I just started to read the experimental thread of the defy section.
Problem may of course be, that my phone here is in bootloop and at the moment I'm back at my old Nokia 6230i
If new Information comes arround I will report it here.
MKSilver said:
Hey there,
well I just started to read the experimental thread of the defy section.
Problem may of course be, that my phone here is in bootloop and at the moment I'm back at my old Nokia 6230i
If new Information comes arround I will report it here.
Click to expand...
Click to collapse
Did you tried simply wipe via moto recovery?
Or flash different sbf.
Have you tried the "fastboot oem unlock" command?
First things first:
at any RSD lite Version my phone is recognized as: "NS Flash OMAP 3630"
I saw, that the behavior of the phone while flashing is different in how i access the bootloader.
I can go into BL through:
A) "X"+"arrow up"
or also
B) "vol+" + "vol-"
while using A) I got a normal bootloader modus.
while using B) I got fastboot modus bootloader.
may someone test this with his phone and post it here?
another special thing: I can only access recovery while pluging the phone into a wallloader and pressing x, with or without the battery.
without the loader pluged in, recovery is not coming.
While access with fastboot and using it:
Code:
C:\where\my\sdk\is> fastboot devices
################ fastboot
-> the # means each a hex sign.
Code:
C:\where\my\sdk\is> fastboot oem unlock
...
FAILED <remote failure>
finished total time: 0.03s
next point while flashing my phone with a SBF_Flash under linux, there was an error with a SBF File, which doesn't throw errors under Windows and RSD.
About the defy forum: still reading, cause i don't want to brick the phone more than it already is, while haven't read all the knowledge.
greetz
MKSilver said:
First things first:
at any RSD lite Version my phone is recognized as: "NS Flash OMAP 3630"
I saw, that the behavior of the phone while flashing is different in how i access the bootloader.
I can go into BL through:
A) "X"+"arrow up"
or also
B) "vol+" + "vol-"
while using A) I got a normal bootloader modus.
while using B) I got fastboot modus bootloader.
may someone test this with his phone and post it here?
another special thing: I can only access recovery while pluging the phone into a wallloader and pressing x, with or without the battery.
without the loader pluged in, recovery is not coming.
While access with fastboot and using it:
Code:
C:\where\my\sdk\is> fastboot devices
################ fastboot
-> the # means each a hex sign.
Code:
C:\where\my\sdk\is> fastboot oem unlock
...
FAILED <remote failure>
finished total time: 0.03s
next point while flashing my phone with a SBF_Flash under linux, there was an error with a SBF File, which doesn't throw errors under Windows and RSD.
About the defy forum: still reading, cause i don't want to brick the phone more than it already is, while haven't read all the knowledge.
greetz
Click to expand...
Click to collapse
Well, I have bootloader 70.12. To get into BL I have 2 options:
1) arrow up
2) Camera + Volume down
Both ways leads to standard BL. Fastboot devices doesn't list my phone, just as before. I never tried to update my BL but I don't think it will do any difference.
I've tried it with bootloader 70.13.
Only option A works to get into Bootloader mode (not Fastboot).
Next "funny" fact.
While Flashing SBF with "normal" bootlaoder modus, everythings works with RSD lite.
While Flashing SBF with "fastboot" bootloader modus, I get an error after creating image files:
"Failed flashing process. Failed flashing process. Phone [0000]: Error getting subscriber unit information. Device API Error: 0xE0000042 Command: RQHW (0x0805041); phone connected"
Then is Result:"FAIL" and the phone stays in bootloader modus (fastboot).
May be I have wrong RSD lite calibration. Will investigate this, how it behaves in linux.
Ok, so googling "unsigned motorola milestone 2 SBF" turned up this as the first
Perhaps if that link is dead you could ask endless7 if he would be so kind as to re-upload it, or perhaps it is available elsewhere.
I say this because I remember reading somewhere that once it's unlocked you can only use unsigned SBF's.. pretty sure it was the bootloader unlock progress thread in the defy forums.. but I'm sure it's been said in our forums too
Just wrote a pm to Endless7. If thats true, it could help me get this device work (even in chinese) and than i can take a look forward, while using adb for example.
Hopefully!
Does anyone else know fo any other unsigned sbf's kickin around the web possibly better than a chinese one?
DreadPirateDan said:
Hopefully!
Does anyone else know fo any other unsigned sbf's kickin around the web possibly better than a chinese one?
Click to expand...
Click to collapse
Dan,
I'm not sure, but I don't think he is limited to flashing only unsigned stuff. The difference from developer phone to production phone, besides fastboot, is that the first one doesn't check signatures during boot chain. Theoretically speaking he is able to flash and boot any Milestone2 ROM he likes. I also suspect that he is able to downgrade from gingerbread to froyo, unlike us. There should be something else preventing him to boot the phone. That's just my opinion and it maybe wrong
Hey guys,
well enough is enough, bought today a second phone for the time the m2 is still dead.
I'm about to finish the defy thread today. Already learned a lot.
Well it is correct that i can flash signed SBFs. While booting into "normal" BL Mode.
But i can also boot into Fastboot and the RSD Lite Name starting with NS seems to show me something special.
So i risk something today and flash a froyo: It worked but still bootloops. The flash was successful and the M Logo turned gray.
At GB it is Red at my M2.
But now it would be great for an unsigned SBF, some more Ideas how to get it boot, or how to manipulate it over fastboot to get it work. Cause without get it into Android we can't go on analyse the bootloader.
PLZ help me. Will also ask a guy from the defy thread, who seems to know a lot about the milestone 1 and bootloaders/OMAP cpus. May he has a great idea what he wrote there was very clever and full of knowledge.
Greetz
Related
I'm sure theres a few of you out there who've bricked their Xoom in the same way I did:
Locking the boot loader after having custom rom and kernal running on it or something similar and come across an error upon boot that says
Failed image LNX 0x0002
RSD mode 2 initiated
or something to that respect
Then tried to do fastboot oem unlock, only to have the Xoom not be recognised.
The solution for me was to make a Motorola Factory cable as per guide here
For some reason, the Xoom would be instantly recognised by my computer and all fastboot commands would work, as well as RSD Lite (Did not do me any good as there is no Xoom Wifi SBF released)
That should fix the booting problem
If it still does not, follow one of the other guides on how to flash using fastboot, another rom now that you have fastboot working again!
Cheers!
mowassasin said:
I'm sure theres a few of you out there who've bricked their Xoom in the same way I did:
Locking the boot loader after having custom rom and kernal running on it or something similar and come across an error upon boot that says
Failed image LNX 0x0002
RSD mode 2 initiated
or something to that respect
Then tried to do fastboot oem unlock, only to have the Xoom not be recognised.
The solution for me was to make a Motorola Factory cable as per guide here
For some reason, the Xoom would be instantly recognised by my computer and all fastboot commands would work, as well as RSD Lite (Did not do me any good as there is no Xoom Wifi SBF released)
That should fix the booting problem
If it still does not, follow one of the other guides on how to flash using fastboot, another rom now that you have fastboot working again!
Cheers!
Click to expand...
Click to collapse
So I went and bought the factory cable from the Black Hat guys, and luckily haven't had the need to use it. Any advice you'd like to give in case I need to at some point?
I guess the only advice I can give is: don't re-lock the boot loader when you have a custom rom loaded
You don't need the cable. I have recovered 4 times myself and walked many others through on irc. We all use the stock cable that came with the device.
Sent from my PG86100 using Tapatalk
bwcorvus said:
You don't need the cable. I have recovered 4 times myself and walked many others through on irc. We all use the stock cable that came with the device.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
It wouldn't recognise any fastboot commands nor the RSD Lite program for me.
But if it does, then thats good.
Merely a heads up for those who were in the same situation I was
bwcorvus said:
You don't need the cable. I have recovered 4 times myself and walked many others through on irc. We all use the stock cable that came with the device.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
you won't care to share how you did it? You have no idea how frustrating it is to see someone say they know how to fix something and leave it it at that.
yaturner said:
you won't care to share how you did it? You have no idea how frustrating it is to see someone say they know how to fix something and leave it it at that.
Click to expand...
Click to collapse
Over the course of a few hours I was able to fix this, so I am going to write this little walkthrough for you using a rom from bwcorvus's page (CLICK HERE) and then used the guide from dirtymindedx -(CLICK HERE)
The reason it took me this long (as well as doing other things) was because I used the wrong set up to unroot my tablet. I was using the Unofficial images that are on bwcorvus's link. Because I didn't read thoroughly enough in his breakdown, I made myself look like a fool...
What you want is NOT
UNOFFICIAL STOCK IMAGES
Click to expand...
Click to collapse
because you will not be able to lock the bootloader (IF you want it to be that way, which I did, and so it gave me a 0x000004 Error, and yes i see that you are having a 0x000002 but somewhere i read this could help that.) I just wanted to get rid of Clockwork Recovery Manager cause it was not working on my 3.2 rooted tablet, and thought that because i messed up teh whole image with playing around and upgrading and seeing how i could break the image without overclocking, i thought i should actually try and make it back to stock too. With this... I needed to do these steps...
1. Upgrade the Motorola drivers while the XOOM was plugged in, so then I would be able to use the Fastboot Correctly.
2. Download the correct roms for my tablet, (Wi-Fi is mine, just grab the one that fits your version and just follow along.)
3. Upgrade my ADB from google because for soem odd reason my fastboot did not like the xoom till i did that...
4. Used the STOCK CABLE. I can Confirm that the STOCK CABLE that allows you to recharge the phones, WILL WORK for this...
5. Once the ADB was set up, I restarted it, aka Hit the red X and then loaded it back up and then closed it again, just to make sure the services were updated somewhat...
6. Opened Command prompt and navigated to the folder that help the zipfile for the fastboot flashing guide (aka dirtymindedx's guide at the top), be using CD (Drive Letter):/location/of/the/folder/that/is/unzipped
7. I then checked over the information in the folder by using dir /a and then proceeded to read through the guide
7-1. A note here... I did the fastboot erase userdata instead, because I wanted to see if it would brick it again... (sorry, I was in a fowl mood with the world last night so I was waiting for it to get bricked so i had a reason to use it as an ice scraper on my car... (not like i would really do it... just wanted a reason for justification haha)
8. ???
9. Profit
This is only to get rid of a "already slightly bricked" device... which I had done after relocking the Rom that was not official to Motorola and now, after a few updates, i now have Android 4.0.3 for the Xoom that was OTA'ed, looking to see how easy it will be to root to reload my rpg game saves that i got caught up in (hence my disappearance from the forums haha...) but I hopefully helped you out in a direction to heads towards... and as long as you don't lock the boot-loader (which someone posted about it before i did...) you should be fine with any changes to the rom after the updates... Also, you can skip steps on this too... you can just flash the image and not the recovery menu and so forth, allowing you to keep other settings that are not part associated to the rom image.
Also sorry for the insanity in my words... I have been up for a good 36 hours with a half hour nap somewhere in there...
So, I like to tinker with my phones. Alot. So much so that even knowing the bootloader is locked, I decided to use
Code:
adb reboot bootloader
to see what it does. I wasn't planning on making any changes yet, just curious as to what it actually gave me. Since this is my first Motorola device, I'm not quite sure what I'm looking at and was wondering if someone could explain it:
Code:
AP Fastboot Flash Mode (S)
0A.65
Battery OK
OK to Program
Transfer Mode:
USB Connected
Now, I'm not a genius, but I'm not an idiot either, and I don't quite get this screen. I see that I'm in fastboot, but from the rest of the screen it almost looks like I could flash something here..... say... custom ROMs..... I only ask because with my old EVO 3d and HBOOT 1.5 we had a method for using fastboot to get around the bootloader, and I was wondering if that was the message my phone is giving me. I know we have the bootstrap for CWM, and I would probably use that for ROMs, but I'm thinking this has potential if I knew exactly what the limits on what I could do here are.
This is for using RSD and flashing the fastboot files (FXZ)
Ah, ok. Thank you for that.
Having been a member on this forum for years I must admit it has been incredible the wealth of information I've gained from it. I've had all sorts of phones/pdas and I'ved used this site to help me get the most out of it and to help m "tame" the device and stop rubbish from the vendors being installed on there when I don't want it.
A couple of years ago I got an HTC Desire. Great phone although limited memory. I was happy with it. Didn't bother to root it or anything. I then got a Motorola Xoom. Didn't bother rooting that either. I got myself an HTC Sensation now. I decided one day that I was going to unlock/root the thing to see if I could do it.
Somehow, I think I managed it. I haven't really noticed a difference but then I haven't put a custom rom on it. On all my old Windows mobiles I always had a custom rom.
Now, going back to the Xoom. It's an original Xoom. I bought it in May 2011. It is running Android 3.2 after Motorola sent out an update. All is good.
However, I would like to have ICS on it. This is where my problems begin. I've tried following so many different how-to's on how to do this unyet none so far have worked. So, either I'm completely stupid or, the guides are not easy to follow or the process (that is always touted as easy) is not very easy.
So I am asking for help. Here is what I understand are the steps that I need to acheive.
1. I need to unlock the device
2. I need to install a recovery image
3. I need to install ICS
Questions: I *think* I have done 1. How do I check? After what I believe is a convoluted process, I have installed the Android SDK. I have the drivers for the device on the [Windows 7 64bit] PC and I can see it listed when I type adb devices.
Why do I need to unlock the device? What does the act of unlocking it do? When I followed this:
http://forum.xda-developers.com/showthread.php?t=1242241
I got to step 3. I typed in the first command:
adb reboot bootloader
After much faffing around I found out from another site I needed USB Debugging enabled. Nobody told me this. No, it isn't obvious that I need this.
The boot screen appeared and gave a message at the top and then I typed in:
fastboot oem unlock
I followed the instructions on the screen. I unlocked the device. It took a while. When it rebooted I found I had to set the device back up again as if it was the first time I'd used it. "Great!" I am thinking, I've lost everything. Thankfully I backed up what I wanted so I am not bothered. Slowly the apps appeared to come back after it synched with Google. I'm assuming stuff gets backed up somewhere.
I typed:
fastboot reboot
It rebooted.I typed:
adb reboot bootloader
It rebooted into the bootloader. Now here is where things started to go off track. I typed the next command:
fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img
I get this:
unknown partition 'recovery-Tiamat-R4c-100611-1150-cwm.img'
error: cannot determine image filename for 'recovery-Tiamat-R4c-100611-1150-cwm.img'
So what now?
I cannot believe the process to unlock and flash a rom is so unbelievably convoluted. I've read dozens of walkthroughs, how-to's and forums and each one seems to be very similar unyet there is always something different on there to what I get on my screen or something doesn't happen quite the same way.
Here is what I am trying to acheive:
I have Android 3.2 on my Xoom and I would like it to be ICS.
We'll assume that I am completely stupid and need serious handholding to get to ICS. Is there anyone that can help with these seemingly simple steps?
One thing I keep reading is about the recovery image file. Is this related to Cyanogenmod? I am assuming as it is called a recovery image file it helps you get back when things go wrong.
Thanks and much love to the person that takes up the reigns and helps me out here.
Hi!
If you are rooted already that's pretty easy. But if not, try using LordAIOTool to root (yea it's mine and I think it's worth a try). After you are rooted flash a new recovery - download from development section - after, rename the recovery to recovery.img and then use the following commands on adb, fastboot and this recovery folder (simultaneously)
adb reboot bootloader
fastboot flash recovery recovery.img
fastboot reboot
Then after keep clicking the vol- after 2s of your tablet appears on Motorola logo. Then keep cycling until appears Android Recovery then press vol+
You are on recovery now, just select install zip from sdcard...
Good luck
Sent from my MZ601 using XDA Premium HD app
If you wanted your xoom rom'd, then you could try wesamothman's guide: http://forum.xda-developers.com/showthread.php?t=1717402 It is great for beginners and the experienced alike.
This is for the wifi only xoom MZ604. There is another guide by him i believe for the MZ602
Do I need to flash a new rom to get root on my MZ604? What is the easiest way to just root the stock 4.0.4 firmware? I have no desire for a different rom. I just want to root it.
Hey there.
If you don't want to flash a custom ROM and only want to root it, try this:
1) unlock your bootloader.
2) thru ADB, flash a recovery image.
3) thru Recovery, flash superuser flashable zip: http://www.4shared.com/zip/g3yzbrIa/...?cau2=403tNull
I ran the first couple of steps to unlocking. That is as far as I have got. As I said, I have tried so many of these walkthroughs and not one of them has all the steps. They all make an assumption somewhere along the line.
For example: xxlordxx replied with:
"If you are rooted already that's pretty easy".
I'm not, that is the problem.
Again:
1. adb reboot bootloader
2. fastboot flash recovery recovery.img <---- This didn't work and gave me the error I pointed out earlier and that is where it all stopped. Noone explains what to do when it goes wrong.
Anything passed this stage is irrelevant until I can sort out the problem above.
yosterwp, you mentioned wesamothmans guide. I will try that one as it looks a bit more "dummies guide-like" and it is for my exact device which is the MZ604 wifi only. I hadn't seen this one as it was only posted a couple of days ago
Just so I know, can someone anser these questions? I'm sure they're very simple but I don't know.
1. Do I need to unlock the Xoom to put ICS or a custom rom on it?
2. Is unlocking the same as setting s-off?
3. If not, what is the difference?
4. I assume the recovery img file is for recovering if things go wrong. Is that correct? Why isn't a recovery app on there for when OTA releases get pushed through? What else does the recovery do for me?
5. What is Cyanogenmod and do I need it or is this another custom rom?
6. There are so many custom roms out there. Everyone says to choose the one that is suited to me but I don't know which ones are suited to me. Does anyone know of a list of the custom ones that are around and why I'd choose one above the other? (I am assuming this is a long shot
Thanks for everything so far. I will let you know how I get on with wesamothmans guide.
Hi Snert.
Answering your queries:
1. Do I need to unlock the Xoom to put ICS or a custom rom on it?
yes.
2. Is unlocking the same as setting s-off?
I don't really understand what you mean by s-off... but unlocking is this: you unlock the bootloader that is considered as a security checkpoint of your device. It is locked by default. when it is unlocked, you can then install recovery image passing thru this checkpoint (allowed). without bootloader being unlocked, no rooting can be done. this is the very first step.
3. If not, what is the difference?
same as above
4. I assume the recovery img file is for recovering if things go wrong. Is that correct? Why isn't a recovery app on there for when OTA releases get pushed through? What else does the recovery do for me?
Recovery explanation details is here: http://www.androidcentral.com/what-recovery-android-z
5. What is Cyanogenmod and do I need it or is this another custom rom?
It is a different ROM based Firmware...
6. There are so many custom roms out there. Everyone says to choose the one that is suited to me but I don't know which ones are suited to me. Does anyone know of a list of the custom ones that are around and why I'd choose one above the other? (I am assuming this is a long shot
Go for the best custom ROM for your MZ604. It is from Team EOS.
Hope I answered your questions
wesamothman said:
Hi Snert.
Answering your queries:
1. Do I need to unlock the Xoom to put ICS or a custom rom on it?
yes.
2. Is unlocking the same as setting s-off?
I don't really understand what you mean by s-off... but unlocking is this: you unlock the bootloader that is considered as a security checkpoint of your device. It is locked by default. when it is unlocked, you can then install recovery image passing thru this checkpoint (allowed). without bootloader being unlocked, no rooting can be done. this is the very first step.
3. If not, what is the difference?
same as above
4. I assume the recovery img file is for recovering if things go wrong. Is that correct? Why isn't a recovery app on there for when OTA releases get pushed through? What else does the recovery do for me?
Recovery explanation details is here: http://www.androidcentral.com/what-recovery-android-z
5. What is Cyanogenmod and do I need it or is this another custom rom?
It is a different ROM based Firmware...
6. There are so many custom roms out there. Everyone says to choose the one that is suited to me but I don't know which ones are suited to me. Does anyone know of a list of the custom ones that are around and why I'd choose one above the other? (I am assuming this is a long shot
Go for the best custom ROM for your MZ604. It is from Team EOS.
Hope I answered your questions
Click to expand...
Click to collapse
You did
Much love!
I downloaded the "Retail Canada (1GB)" firmware as listed in this post:
http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
I went to install it via the guide linked at the beginning of the first post. The command mfastboot flash motoboot motoboot.img didn't complete because no such file (motoboot.img) existed in that archive. The guide said nothing of this, so I continued with the other steps until the end (every other one said 'okay'), finally issuing the reboot command.
Now the phone won't boot up because, I assume, I no longer have a bootloader. I just get a black screen. If I plug in the USB cable to my computer, I can hear the sound of a device being connected, but it just shows as a Qualcomm device in Device Manager. Pressing and holding the power and volume-down keys seems to reboot the device (I hear Windows chime that a USB device was disconnected, then reconnected) but nothing ever comes on the screen. ADB/Fastboot commands just say "waiting for device".
Is the phone done? If so, then that's pretty lousy that the archive for the stock ROM doesn't contain the bootloader file that I apparently need.
Yes, my bootloader was unlocked because I had installed TWRP to try out the CM ROM before deciding to return to the stock ROM.
You didn't flash the bootloader, but didn't erased either. That guide is for older phones and some files are missing or with a different name. I did that flashing and it went well even without flashing motoboot.
Sent from my MotoG3 using Tapatalk
---------- Post added at 11:48 AM ---------- Previous post was at 11:42 AM ----------
Adb will always says waiting for device bc Adb loads only with system. Try typing "mfastboot devices" to see if you can still access fastboot
Sent from my MotoG3 using Tapatalk
@Sevael - Thanks for pointing this out. The motoboot.img is now known as bootloader.img in Osprey firmware images. The motoboot partition is also different, now known as 'bootloader.'
The new command to flash Bootloader file is therefore:
mfastboot flash bootloader bootloader.img
lost101 said:
@Sevael - Thanks for pointing this out. The motoboot.img is now known as bootloader.img in Osprey firmware images. The motoboot partition is also different, now known as 'bootloader.'
The new command to flash Bootloader file is therefore:
mfastboot flash bootloader bootloader.img
Click to expand...
Click to collapse
Will be great to add (if isn't there already) this on the OP of osprey FW post. Thanks!
Sent from my MotoG3 using Tapatalk
nelsonw said:
Will be great to add (if isn't there already) this on the OP of osprey FW post. Thanks!
Click to expand...
Click to collapse
Working on it now.
nelsonw said:
Adb will always says waiting for device bc Adb loads only with system. Try typing "mfastboot devices" to see if you can still access fastboot
Click to expand...
Click to collapse
I tried ADB, fastboot and mfastboot, they all return empty lists. I even tried the qboot solution for older Moto Gs. It doesn't respond to anything. I was on the internet for four hours looking up solutions and trying everything and nothing worked. Best I can tell, the bootloader is corrupted or missing. Since I can't get into the bootloader, I can't reflash anything to fix it.
According to the later pages of this thread, there are software tools out there which would fix this exact problem, but no one on XDA has been able to get their hands on them for the 3rd gen Moto G. Seems that only Motorola and perhaps some authorized repair places have access to the tools.
It wouldn't be such a big deal if this wasn't my only phone. I've previously had Samsungs and LGs and modded the hell out of them and it was always easy to recover from any type of issue via Odin or LG FlashTool. This is my first Motorola and I'm quickly learning that it's a much more fragile beast. I'm thinking that this might be my last Motorola for that very reason. I like to mod but I don't like this kind of fragility. I technically made no mistakes (just followed the guide I was directed to) and now my phone is hardbricked.
I have to go out and buy another phone this morning. The Moto G is an amazing phone for the price, but I'm not sure I want to risk it again.
@Sevael - Are you using Fastboot in Windows or Linux?
Edit: From what you have described, the bootloader hasn't even been touched.
Sevael said:
I tried ADB, fastboot and mfastboot, they all return empty lists. I even tried the qboot solution for older Moto Gs. It doesn't respond to anything. I was on the internet for four hours looking up solutions and trying everything and nothing worked. Best I can tell, the bootloader is corrupted or missing. Since I can't get into the bootloader, I can't reflash anything to fix it.
According to the later pages of this thread, there are software tools out there which would fix this exact problem, but no one on XDA has been able to get their hands on them for the 3rd gen Moto G. Seems that only Motorola and perhaps some authorized repair places have access to the tools.
It wouldn't be such a big deal if this wasn't my only phone. I've previously had Samsungs and LGs and modded the hell out of them and it was always easy to recover from any type of issue via Odin or LG FlashTool. This is my first Motorola and I'm quickly learning that it's a much more fragile beast. I'm thinking that this might be my last Motorola for that very reason. I like to mod but I don't like this kind of fragility. I technically made no mistakes (just followed the guide I was directed to) and now my phone is hardbricked.
I have to go out and buy another phone this morning. The Moto G is an amazing phone for the price, but I'm not sure I want to risk it again.
Click to expand...
Click to collapse
I'll look into that thread and see how i can help you. But some command must be wrong to achieve that king of brick. For sure isn't Motorola issue... Give me some time and look into that.
Sent from my MotoG3 using Tapatalk
lost101 said:
@Sevael - Are you using Fastboot in Windows or Linux?
Click to expand...
Click to collapse
Windows.
I followed all instructions. The files were all in the same folder, I copy/pasted the commands to ensure no typos, I carefully went through line by line. But something is different about the 3rd gen that the tutorial from the first gen just doesn't seem to work.
I know that I had things setup right because I was able to get TWRP flashed no problem. Installed CM, gave it a whirl, decided to go back to stock. Went back into the bootloader (didn't re-lock it at any point, that might have been my mistake), then tried to follow the linked guide to restoring the stock firmware. I even downloaded the firmware archive twice to ensure that it was correct. I extracted it all into the folder with the ADB and mfastboot files.
lost101 said:
Edit: From what you have described, the bootloader hasn't even been touched.
Click to expand...
Click to collapse
That's what I thought, but the phone does not boot into the bootloader under any circumstances. I tried things like holding the power and volume down buttons for two minutes (tried both when plugged into PC and unplugged). I tried just the power button for two minutes. I tried every software solution I could find online (four hours of searching and trying). Nothing worked.
Fortunately, the store rep bought my story when I told him that the phone was like that right out of the box and he gave me a full refund. So I grabbed a different phone.
Thanks for trying to help out guys, I really appreciate it. XDA is always an awesome place. I'm not done with Motorola, but I've picked up a Moto X Play to try for now. Fingers crossed!
Thanks again.
@Sevael - I'm glad you got out of the situation easily.
I've added a new guide for flashing Firmware Images in 'General.'
The only significant difference is the change of name for the 'Bootloader' partition and bin file. Some people have previously posted in the Firmware Images thread that they had successfully restore Stock Firmware - following the old Moto G Tutorial. Maybe all of them skipped the 'fastboot flash motoboot motoboot.img' command.
Since the command failed for you, it doesn't make any sense that it would hard-brick the phone - unless simply by using that command a new partition was created on the phone called 'motoboot' - which conflicted with the existing 'bootloader' partition.
Sevael said:
Windows.
I followed all instructions. The files were all in the same folder, I copy/pasted the commands to ensure no typos, I carefully went through line by line. But something is different about the 3rd gen that the tutorial from the first gen just doesn't seem to work.
I know that I had things setup right because I was able to get TWRP flashed no problem. Installed CM, gave it a whirl, decided to go back to stock. Went back into the bootloader (didn't re-lock it at any point, that might have been my mistake), then tried to follow the linked guide to restoring the stock firmware. I even downloaded the firmware archive twice to ensure that it was correct. I extracted it all into the folder with the ADB and mfastboot files.
That's what I thought, but the phone does not boot into the bootloader under any circumstances. I tried things like holding the power and volume down buttons for two minutes (tried both when plugged into PC and unplugged). I tried just the power button for two minutes. I tried every software solution I could find online (four hours of searching and trying). Nothing worked.
Fortunately, the store rep bought my story when I told him that the phone was like that right out of the box and he gave me a full refund. So I grabbed a different phone.
Thanks for trying to help out guys, I really appreciate it. XDA is always an awesome place. I'm not done with Motorola, but I've picked up a Moto X Play to try for now. Fingers crossed!
Thanks again.
Click to expand...
Click to collapse
It won't help you now, but technically all you needed to do to get back to stock was flash the system image files (and maybe the kernel if CM comes with its own kernel). You didn't even need to attempt to flash anything else. Its OK following guides but be aware that they aren't fool proof.
scott_doyland said:
It won't help you now, but technically all you needed to do to get back to stock was flash the system image files (and maybe the kernel if CM comes with its own kernel). You didn't even need to attempt to flash anything else. Its OK following guides but be aware that they aren't fool proof.
Click to expand...
Click to collapse
I did try reflashing. As I said, the bootloader was gone. No devices detected by ADB, fastboot, mfastboot, qboot, or any other tool I tried. I put in commands and it just sat at "Waiting for device".
I'm glad that you get a Moto X. I can't understand what you did. But that is the past. Good luck and enjoy your phone! Thanks @lost101 for the new guide.
Sent from my MotoG3 using Tapatalk
Sevael said:
I did try reflashing. As I said, the bootloader was gone. No devices detected by ADB, fastboot, mfastboot, qboot, or any other tool I tried. I put in commands and it just sat at "Waiting for device".
Click to expand...
Click to collapse
Hi,I meant for your first attempt at flashing back stock when your bootloader was OK. CM is just a new system image, you didn't need to even attempt to reflash a bootloader.
Even just using twrp to restore the system image alone would have got you back to stock.
scott_doyland said:
Hi,I meant for your first attempt at flashing back stock when your bootloader was OK. CM is just a new system image, you didn't need to even attempt to reflash a bootloader.
Click to expand...
Click to collapse
Yes, that's true. But at the time I didn't know that. There was a thread with links to the stock firmware and a guide how to flash it, so I followed it. Oh well, at least the issues I had have allowed for better information to become available for everyone.
scott_doyland said:
Even just using twrp to restore the system image alone would have got you back to stock.
Click to expand...
Click to collapse
Also true. I didn't take the time to create a backup of stock after first installing TWRP because I am used to Samsung and LG phones where you just download a single file and can restore the stock firmware image under any circumstances with no problems. It didn't dawn on me that a Motorola phone (this was my first) would be more complicated. I had (wrongfully) assumed that all Android phones were as foolproof as those two brands.
Especially Samsung. Odin plus the SamMobile website is like having an unlimited amount of get-out-of-jail-free cards. Why can't all Android phones work like that?
Sevael said:
Yes, that's true. But at the time I didn't know that. There was a thread with links to the stock firmware and a guide how to flash it, so I followed it. Oh well, at least the issues I had have allowed for better information to become available for everyone.
Also true. I didn't take the time to create a backup of stock after first installing TWRP because I am used to Samsung and LG phones where you just download a single file and can restore the stock firmware image under any circumstances with no problems. It didn't dawn on me that a Motorola phone (this was my first) would be more complicated. I had (wrongfully) assumed that all Android phones were as foolproof as those two brands.
Especially Samsung. Odin plus the SamMobile website is like having an unlimited amount of get-out-of-jail-free cards. Why can't all Android phones work like that?
Click to expand...
Click to collapse
I didn't know that about Samsung and LG as I have never had one. So I have also learnt something
Anyone ever figure this out?
I just did basically the same thing as the OP, because I'm an idiot. If there's a way to recover (there's a fix for the 2nd gen model involving qboot, but I'm guessing the images are different) without having to hope Motorola will replace it without noticing the unlocked bootloader that would be awesome. Qboot.exe will recognize it, so if I had the right blank-flash images that would work in principle.
I still don't understand what happened. I skipped the motoboot step because I didn't want to replace the bootloader and now I can't even get the screen to turn on.
@mcrammerdocdoc - It would be helpful if you can provide as much detail about what you did, fastboot commands used etc. It's important to get a clear understanding as to why this is happening.
If you are not touching the Bootloader at all, then it can only be gpt.bin (Partition Table) - creating this situation - as all other fastboot files are benign. The other possibility is that it's not really hard-bricked; perhaps there is a bug suddenly dropping battery life to zero (this occurred with Moto G (1st Gen)) and letting the phone charge will resolve this.
lost101 said:
@mcrammerdocdoc - It would be helpful if you can provide as much detail about what you did, fastboot commands used etc. It's important to get a clear understanding as to why this is happening.
If you are not touching the Bootloader at all, then it can only be gpt.bin (Partition Table) - creating this situation - as all other fastboot files are benign. The other possibility is that it's not really hard-bricked; perhaps there is a bug suddenly dropping battery life to zero (this occurred with Moto G (1st Gen)) and letting the phone charge will resolve this.
Click to expand...
Click to collapse
Yeah, sorry about that. Here's what I tried, ripped directly from Gammerson's stock-restore guide (new user, can't post the actual link apparently):
Code:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img # skipped; no motoboot.img in the zip
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk1
mfastboot flash system system.img_sparsechunk2
mfastboot flash system system.img_sparsechunk3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
The only variations besides skipping the bootloader were the system.img chunks (there were 5 for my device) and the fact that I used plain old fastboot from the Android SDK vs. mfastboot. Right after that "fastboot reboot" command the screen went dead and hasn't done a thing since. Plugging it into a PC will get it listed as "Qualcomm HS-USB QDLoader 9008 (COM8)", which I'm guessing is some kind of emergency serial interface. I guess that means the battery isn't dead? Unless it's just pulling power out of the USB port. I'll try charging it for a bit and see if that helps.
Thanks! Hope some of that is useful. Seems like the thing to do would be dump a bootloader image over that serial link, but I've got no idea how to begin doing that.
@mcrammerdocdoc that's exactly what happened with me.
It wasn't battery-related because it was nearly full when I did the final reboot command and it was dead immediately. I left it plugged in overnight and it didn't change anything.
The qboot thing would be the solution if we had the applicable software for the 3rd gen. There is a thread on XDA (I didn't bookmark it) where they were discussing the black-screen brick and the Qualcomm device showing up in Windows for all three gens of Moto G. The last few pages made it clear that 3rd gen owners with this issue don't yet have a solution.
I think it might have been in the 1st gen Moto G forum. The thread was over 100 pages long and involved all three gens.
Hi there, looks like no one as posted about the Cyprus64 series from Motorola yet.
Although the lastest (E40 came out in october). I'm actualy surprised about that, it looks like no one owns one.
Yet I bought the E40. I can definitely understand why no one has ever been interested in this phone as the Geekbench benchmark suggests; it is average at everything except for the 90hz screen that comes with it.
The why im posting this, is to ask if someone planned to port any custom recovery to it and/or started custom rom ports and/or creations. I'm also getting ''unknown cmd'' issues in fastboot mode with commands such as fastboot oem get_unlock_data etc...
Anyway , thank you for reading me i hope this will start a conversation about these new devices.
Bye y'all.
(this is my first post, sorry for any inconvenience)
E40: https://www.motorola.fr/smartphones-moto-e-40/p?skuId=420
E30: https://www.motorola.fr/smartphones-moto-e-30/p?skuId=418
E20: https://www.motorola.fr/smartphones-moto-e-20/p?skuId=408
I'm having the same problem, not to mention it was a lot of work to find the drivers
vigile said:
Hi there, looks like no one as posted about the Cyprus64 series from Motorola yet.
Although the lastest (E40 came out in october). I'm actualy surprised about that, it looks like no one owns one.
Yet I bought the E40. I can definitely understand why no one has ever been interested in this phone as the Geekbench benchmark suggests; it is average at everything except for the 90hz screen that comes with it.
The why im posting this, is to ask if someone planned to port any custom recovery to it and/or started custom rom ports and/or creations. I'm also getting ''unknown cmd'' issues in fastboot mode with commands such as fastboot oem get_unlock_data etc...
Anyway , thank you for reading me i hope this will start a conversation about these new devices.
Bye y'all.
(this is my first post, sorry for any inconvenience)
E40: https://www.motorola.fr/smartphones-moto-e-40/p?skuId=420
E30: https://www.motorola.fr/smartphones-moto-e-30/p?skuId=418
E20: https://www.motorola.fr/smartphones-moto-e-20/p?skuId=408
Click to expand...
Click to collapse
Roms are definitely needed for Cyprus64 series (Moto E40) since it has already been discarded by motorola within 4 months and its OS is freaking buggy
vigile said:
Hi there, looks like no one as posted about the Cyprus64 series from Motorola yet.
Although the lastest (E40 came out in october). I'm actualy surprised about that, it looks like no one owns one.
Yet I bought the E40. I can definitely understand why no one has ever been interested in this phone as the Geekbench benchmark suggests; it is average at everything except for the 90hz screen that comes with it.
The why im posting this, is to ask if someone planned to port any custom recovery to it and/or started custom rom ports and/or creations. I'm also getting ''unknown cmd'' issues in fastboot mode with commands such as fastboot oem get_unlock_data etc...
Anyway , thank you for reading me i hope this will start a conversation about these new devices.
Bye y'all.
(this is my first post, sorry for any inconvenience)
E40: https://www.motorola.fr/smartphones-moto-e-40/p?skuId=420
E30: https://www.motorola.fr/smartphones-moto-e-30/p?skuId=418
E20: https://www.motorola.fr/smartphones-moto-e-20/p?skuId=408
Click to expand...
Click to collapse
Motorola commands for unlocking does not work I have a moto g20 same soc Unisoc T700. If you want to unlock bootloader you will have to use the command
' fastboot flashing unlock ' remembering to erase all your data
Are there custom roms for the Moto E20?
kamuri said:
Are there custom roms for the Moto E20?
Click to expand...
Click to collapse
Haven't found anything yet?
Kross05 said:
Haven't found anything yet?
Click to expand...
Click to collapse
Nope
Is there a way to go to recovery mode in Motorola moto e40? I have tried pressing power+volume down+assist button or power+volume button, but nothing works.
Guys i think i found a way to unlock the bootloader.......after entering fastboot (holding volume down+google assistant+power key when the phone is turned off then as soon as the screen lights up release the power key after that enter fastboot mode then select reboot to bootloader)
open adb command prompt and type fastboot flashing unlock.....thats it.
Now i need to figure out how to get root access, if anyone knows please tell me.
Kross05 said:
Guys i think i found a way to unlock the bootloader.......after entering fastboot (holding volume down+google assistant+power key when the phone is turned off then as soon as the screen lights up release the power key after that enter fastboot mode then select reboot to bootloader)
open adb command prompt and type fastboot flashing unlock.....thats it.
Now i need to figure out how to get root access, if anyone knows please tell me.
Click to expand...
Click to collapse
not event this way i`m able to unlock...
moto E20. I can access the fastboot mode by pressin down vol.+ power+google assist or vol up + power...
leonardofmed said:
not event this way i`m able to unlock...
moto E20. I can access the fastboot mode by pressin down vol.+ power+google assist or vol up + power...
Click to expand...
Click to collapse
yeah then boot into bootloader through adb or press the keys
Ok so bootloader is unlocked , is a TWRP or other custom recovery available?
Concept48 said:
Ok so bootloader is unlocked , is a TWRP or other custom recovery available?
Click to expand...
Click to collapse
Nah
Concept48 said:
Ok so bootloader is unlocked , is a TWRP or other custom recovery available?
Click to expand...
Click to collapse
Even tried rooting it but it would give write .img failed and if I tried flashing the boot.img on a and b partitions separately it would go into bootloop altho it can be easily recovered using research tool and flashing the rom
┤Mod Edit├┤Adding automated English translation├
I have a moto E40, can you help the developers save our moto E40 so that it can at least gain root access...thank you guys...lucky...google translate Please forgive me
Click to expand...
Click to collapse
Spoiler: Original Post
我有一個 moto E40，你能幫助開發人員保存我們的 moto E40，以便它至少可以獲取 root 訪問權限......謝謝你們......幸運的是......谷歌翻譯請原諒我
vigile said:
Hi there, looks like no one as posted about the Cyprus64 series from Motorola yet.
Although the lastest (E40 came out in october). I'm actualy surprised about that, it looks like no one owns one.
Yet I bought the E40. I can definitely understand why no one has ever been interested in this phone as the Geekbench benchmark suggests; it is average at everything except for the 90hz screen that comes with it.
The why im posting this, is to ask if someone planned to port any custom recovery to it and/or started custom rom ports and/or creations. I'm also getting ''unknown cmd'' issues in fastboot mode with commands such as fastboot oem get_unlock_data etc...
Anyway , thank you for reading me i hope this will start a conversation about these new devices.
Bye y'all.
(this is my first post, sorry for any inconvenience)
E40: https://www.motorola.fr/smartphones-moto-e-40/p?skuId=420
E30: https://www.motorola.fr/smartphones-moto-e-30/p?skuId=418
E20: https://www.motorola.fr/smartphones-moto-e-20/p?skuId=4
Click to expand...
Click to collapse
Hey we have a moto e40 group on telegram. Although there are no custom roms available for e40,however you can flash gsis in this device. All the steps for flashing gsis and unlocking bootloader are given there. If anyone interested can join this channel and feel free to ask any questions there. Here is the link: https://t.me/MotoE40Global . Note: Most of the gsis have bugs but some gsis are absolutely bugless.
Hey guys there's a small group of e40 on telegram. You can join there if you're interested in unlocking your bootloader. There are no custom roms available for this device, but you can flash gsis in this device and give your ui a new look. To know more about how to flash gsis and available gsis for e40,you can join our community on telegram. Here's the link:- https://t.me/MotoE40Global .
Thanking you,
Avik
kamuri said:
Are there custom roms for the Moto E20?
Click to expand...
Click to collapse
Try using GSI Roms they will work but bootloader needs unlocking which isn't actually that hard but a Linux pc is needed if you don't have one but a windows then find a usb and flash a live boot
Yeah can anyone here be able to comply a twrp for the phones I can help abit with the Moto e30 but not alot since I don't have my computer at the moment also I'm too great at coding as I'm a year 10 (UK) student but I have some experience with ADB since I unlocked my old phones bootloader
this is what I get in the fastboot command line
when typing 'fastboot flashing unlock' and all other variations
FAILED (remote: 'Not implemet.')
fastboot: error: Command failed