I´m not sure...
Where is the difference to that ROM: http://www.firmware-team.com/showthread.php?t=294
Same filename, same size etc... This is not signed
I´m not sure...
Where is the difference to that ROM: http://www.firmware-team.com/showthread.php?t=294
Same filename, same size etc... This is not signed
D
dashiell.cano
Guest
So I don't know what's the difference, but with this post ROM the bootloader can be relocked.
Sent from my XT1032 using Tapatalk
Not working for me. Bootloader relock not possible.
During fastboot commands I get the message, that the ROM is not signed.
Do you use a tool or do you flash via command line?
Did you also get some errors while flashing? For example Recovery can't flash?
Sent from my XT1032 using xda app-developers app
You should get warnings, but not errors. As long as at the end of each process it says "[OKAY]", you're good to to. If it says "[FAILED]", you have to try again.
According to Play Store the GPE supports the European bands.
https://play.google.com/store/devices/details/Moto_G_Google_Play_edition_8GB?id=moto_g_8gb&hl=en
Someone from Europe that flashed this complete Firmware to confirm that 3G is working?
Sent from my Nexus 5
Last edited:
flashed it as my phone decided to bootloop after battery ran out completely and charged... working a-ok! (i'm in england btw)
I think there are two one US Global that does support the Europe bands and one US only that supports T mobile USA bands
I think AT&T uses 850Mhz and 1900Mhz and T-Mobile 1700Mhz & 2100Mhz.
According to Play Store the GPE doesn't have support for 1700Mhz.
For AT&T there is no problem.
Anyway its all a confusion....two possible scenarios...
A ) There are 2 GPE phones. (Just like you said).
B ) All GPE versions are XT1032 and fu%& off with the 1700Mhz band...
Sent from my Nexus 5
Think this is right
....They all provide HSPA+, only the bands are different.
For XT1032 (global): UMTS 850/900/1900/2100 For XT1034 (US GSM): UMTS 850/1700/1900
EDIT
Would you believe it it was nothing to do with the Bands!
It was my KitKat APN this can not be read by this Rom once I downgraded it to JellyBean APN it works fine. The APN changed significantly between JB &KK especially if, or perhaps only if, you use a Virtual Carrier i.e. one that uses some one else's network. This is quiet common in the UK. This may help others I hope as I have read many connection problems.
Last edited:
I'am getting error while I'm flashing boot and recovery
my moto g is 8gb from uk, and i haven't got any of this errors while i'm flashing stock de firmware
any help ??
my moto g is 8gb from uk, and i haven't got any of this errors while i'm flashing stock de firmware
any help ??
Same log at me. ROM seems to work perfect. The only thing is, that I cannot relock the bootloader as the error messages seems to say, that this ROM is not signed. Don´t know if a OTA update will be possible, when Google releases one.
In that case. I think the OTA is going to check if the target to update is properly signed. And probably will fail too.
I don't know the Moto G GPE, but the Nexus's OTAs are very cautious, specially with the /system partition (the one that is always updated), they sometimes update the bootloader too.
I don't know the Moto G GPE, but the Nexus's OTAs are very cautious, specially with the /system partition (the one that is always updated), they sometimes update the bootloader too.
So at what point when you flash does userdata partition get reformatted to ext4. Just flashing a ROM does not mean your partitions get reformatted to use a different filesystem as far as I know?
At the end of the XML flash script one of the last things it does is erase userdata, this would not be needed if any of the earlier flash commands formatted userdata.
Jst because you flash gpe over non-gpe doesn't mean userdata becomes an ext4 filesystem.
Happy to be proved wrong though.
Also just for everyones info. The bootloader for non-gpe KitKat is exactly the same as gpe KitKat (at least for UK retail XT1032 non-gpe phone). I ran a binary diff on the motoboot.img files and both are exactly the same.
Last edited:
Good question, in theory it should be ext4, but who flashed this can in easy way to see if data is still to f2fs or ext4 in terminal emulator with mount command. Probably .bat keeps data in f2fs because it was thought for gpe version already in ext4, and so on. It can be. The "erase userdata" command can support your thinking.
The "Impossible. Read cwm phliz thread." has nothing to do wit "ext4". Can you delete it from quote? Thanks
The "Impossible. Read cwm phliz thread." has nothing to do wit "ext4". Can you delete it from quote? Thanks
Last edited:
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
3
I think it must be the gpt file as this is the first file flashed perhaps you could check? I've a UK Moto G and just checked mine is also ext 432
http://xdaforums.com/showthread.php?p=50570527
---------- Post added at 01:38 PM ---------- Previous post was at 01:27 PM ----------
Also here http://xdaforums.com/showthread.php?p=505424652I recently went from 4.3 to this ROM on XT1032. Regarding the flashing errors mentioned earlier in the thread; I recall trying effectively 3 different versions of fastboot.exe - the standard one, mfastboot.exe and one provided by Paul O Brien back in November: fastboot-moto-windows.exe. I think it was the last of those that gave no errors. Something worth considering if people are having problems.2
I think AT&T uses 850Mhz and 1900Mhz and T-Mobile 1700Mhz & 2100Mhz.
According to Play Store the GPE doesn't have support for 1700Mhz.
For AT&T there is no problem.
Anyway its all a confusion....two possible scenarios...
A ) There are 2 GPE phones. (Just like you said).
B ) All GPE versions are XT1032 and fu%& off with the 1700Mhz band...
Sent from my Nexus 5
New posts
-
Features disabled on fastboot and bootloader. How do I enable them?- Latest: mayberandomparable
-
Question Fingerprint Sensor Not Working after unbricking phone
- Latest: heartbreakkid58
-
