The reason I ask is that mine is still buggered.
I had an xt1039 originally, drove over it in a 44 tonner and broke the digitiser. 2 new screens later and neither worked.
Bit the bullet and bought a used xt1039 one off eBay. Tesco version, already unlocked, but it was already upgraded to 5.02. Soft bricked it trying to restore to stock 4.3, sorted that by reinstalling stock 4.4.4, downgraded that to 4.4.3 but couldn't find a 4.4.2 Rom before I tried 4.3 again. Flashed different fsg and HLOS-NON files clearing the two modem files each time but to no avail. I have hunted high and low trying to get to the bottom of this reading through various threads on here, and I found theories along the lines of it only happens to those with O2 or Vodafone Sims or those networks who piggyback on them.
I did find a useful snippet that if I selected 2g I would at least get a stable phone signal which has worked fixing that, but I am on talktalk mobile(Vodafone) paying for 4 gig internet every month but ATM not using anywhere near that obviously. Vodafone's 3g coverage of the motorway network sucks anyway but something is better than nothing.
Before I give up and rip the motherboard out of my old one, is there any definitive to fix this? I am quite happy to supply any required information and answer any questions, and obviously any assistance would be greatly appreciated.
Ta muchly.
Lennie
Sent from my Hudl 2 using Tapatalk
Trying to find out which exact model I had, just though maybe it wasn't an xt1039, but in the regulatory information it says xt1039 but the information is for india! How does this relate to the UK? Do all of them say SAR information for India or is this country specific?
Just trying to find a way forward peeps.
Cheers
Lennie
Sent from my Hudl 2 using Tapatalk
If I install cyanogenmod and cwm or twrp will this cure the problem?
Sent from my Hudl 2 using Tapatalk
XT1039 is the model sold in UK / EU. What does: Settings > About phone say?
lost101 said:
XT1039 is the model sold in UK / EU. What does: Settings > About phone say?
Click to expand...
Click to collapse
Model Number: Moto G
Android Version: 5.1
Baseband Version: M8926_309101.02.03.14r TESCOGB_CUST
Kernel Version: 3.4.42-geb8cd52e-00003-g52c4c71 [email protected] #1 Mon May 11 05:31:09 CDT 2015
System Version: 23.21.17.peregrine_tescogb.tescogball.en.GB tescogb
Build Number: LPB23.13-17
I had just tried flashing a 5.1 Tesco Rom to see if it worked, but it is just doing the same. Was originally trying to get 4.3 Tesco rom for the 4g, but I am not sure what the LTE version on Tesco was originally released on, 4.3 or 4.4.x.
Thanks for the reply
Lennie
With Moto G Falcon - Motorola made it impossible to boot 4.3, after upgrading to KitKat. It's probably the same case here. I would be careful with the file: motoboot.img (Bootloader) - it's unnecessary and dangerous to repeatedly flash it.
Provide a fastboot log of what happens when you try to flash the 5.1 Firmware Image. You can flash either Tesco or Retail GB from here:
http://forum.xda-developers.com/showpost.php?p=60793911&postcount=2
lost101 said:
With Moto G Falcon - Motorola made it impossible to boot 4.3. It's probably the same case here. I would be careful with the file: motoboot.img (Bootloader) - it's unnecessary and dangerous to repeatedly flash it.
Provide a fastboot log of what happens when you try to flash the 5.1 Firmware Image. You can flash either Tesco or Retail GB from here:
http://forum.xda-developers.com/showpost.php?p=60793911&postcount=2
Click to expand...
Click to collapse
Hi lost101
This is the firmware I just tried this morning, took two full flashes and a force shutdown before it booted properly. First time it got stuck and fell into dead android screen for recovery. Rebooted into bootloader again and reflashed, then it booted past the changing planet pic to the blue M, then hung there. Forced restart and it booted to optimizing apps and started fine. Turned it off, then restarted and deleted all the apns, installed the one I got in a text from Talktalk, selected network, and restarted again. Unfortunately, unless I select 2g in the preferred network types, it just keeps dropping signal.
Should I try the retail version rather than the Tesco Version?
Cheers
Lennie
Show me a fastboot log. The tool is in no way user-friendly - it can fail to flash completely, yet still appear as if everything was an amazing success.
lost101 said:
Show me a fastboot log. The tool is in no way user-friendly - it can fail to flash completely, yet still appear as if everything was an amazing success.
Click to expand...
Click to collapse
By Fastboot Log, do you want me to reflash and post the results that show in the command prompt, or what appears on the phone, or am I getting mixed up?
Thanks
Lennie
Jalipero said:
By Fastboot Log, do you want me to reflash and post the results that show in the command prompt, or what appears on the phone, or am I getting mixed up?
Click to expand...
Click to collapse
Yes, reflash the firmware image files. Do the commands manually, one at a time. Copy and paste the entire process into a post here. Try to skip flashing motoboot.img.
lost101 said:
Yes, reflash the firmware image files. Do the commands manually, one at a time. Copy and paste the entire process into a post here. Try to skip flashing motoboot.img.
Click to expand...
Click to collapse
OK Will do, I will skip the partition and the motoboot and start at logo. Both these files flashed fine allegedly, but I will go through the rest again and post them up.
Thanks
Lennie
Hi lost101
I have listed below the log as requested:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
F:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (295 KB)...
OKAY [ 0.047s]
writing 'logo'...
OKAY [ 0.078s]
finished. total time: 0.125s
F:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.361s]
writing 'boot'...
OKAY [ 0.780s]
finished. total time: 1.141s
F:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash recovery recover
y.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 0.374s]
writing 'recovery'...
OKAY [ 0.811s]
finished. total time: 1.186s
F:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash system system.im
g_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (257455 KB)...
OKAY [ 8.416s]
writing 'system'...
OKAY [ 12.951s]
finished. total time: 21.367s
F:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash system system.im
g_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (257669 KB)...
OKAY [ 8.426s]
writing 'system'...
OKAY [ 12.008s]
finished. total time: 20.434s
F:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash system system.im
g_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (261644 KB)...
OKAY [ 8.534s]
writing 'system'...
OKAY [ 17.718s]
finished. total time: 26.252s
F:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash system system.im
g_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (189917 KB)...
OKAY [ 6.336s]
writing 'system'...
OKAY [ 10.529s]
finished. total time: 16.864s
F:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash modem NON-HLOS.b
in
target max-sparse-size: 256MB
sending 'modem' (60232 KB)...
OKAY [ 2.012s]
writing 'modem'...
OKAY [ 2.075s]
finished. total time: 4.087s
F:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.031s]
finished. total time: 0.031s
F:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.031s]
finished. total time: 0.031s
F:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (517 KB)...
OKAY [ 0.109s]
writing 'fsg'...
OKAY [ 5.276s]
finished. total time: 5.385s
F:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.125s]
finished. total time: 0.125s
F:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 0.468s]
finished. total time: 0.468s
F:\Program Files (x86)\Minimal ADB and Fastboot>
Any of this any use to you?
Thanks
Lennie
@Jalipero - The log is incomplete - are you flashing 4 sparsechunk files? in the correct order: sparsechunk.0, sparsechunk.1, sparsechunk.2 and sparsechunk.3?
lost101 said:
@Jalipero - The log is incomplete - are you flashing 4 sparsechunk files? in the correct order: sparsechunk.0, sparsechunk.1, sparsechunk.2 and sparsechunk.3?
Click to expand...
Click to collapse
Sorry about that copied and pasted the whole thing into notepad then only pasted the 2nd half like a tube.
I have edited the original list to include it all now.
Apologies for the stupidity.
Thanks
Lennie
Did the phone boot into Android without problem after this re-flash?
lost101 said:
Did the phone boot into Android without problem after this re-flash?
Click to expand...
Click to collapse
Yes it did, oddly. Took an age, but I remembered seeing somewhere that it can take up to 8 minutes for it to initialise after flashing, so I left it at the planet with the M in it, and it booted up to start procedure fine. I was just about to restart it, then erase the cache again and reboot to clear it out if that is ok?
Lennie
You should not need to do anything else.
lost101 said:
You should not need to do anything else.
Click to expand...
Click to collapse
No problem I will leave it as it is then.
Thanks
Lennie
I was looking for the APN utility Tweakker but appears to no longer exist. There area alternatives on Google Play - if you want to try to make sure your APN info is correct.
Yes the biggest problem I have is that if I select anything other than 2g it just keeps dropping signal. Other than that the phone is great. I will have a look for a similar app to tweakker and see if there any changes to be made.
Ta muchly
Lennie
Hey guys, i tried to install a new rom and i deleted my OS. i unlocked the bootloader but when i tried to flash TWRP said me:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
target reported max download size of 471859200 bytes
sending 'recovery' (26982 KB)...
OKAY [ 0.767s]
writing 'recovery'...
FAILED (remote: partition length get error)
finished. total time: 0.780s
C:\Program Files (x86)\Minimal ADB and Fastboot>
If i try to flash anything else Said me ''Command not allowed'' and i think it's cause i did not turn on the Oem Unlock in development options (cause i don't have OS, obviously)
Anybody can help here please? is urgent and i'm dying :crying: :crying: :crying:
Hi all,
somehow my sons' D6603 messed up and didn't boot anymore. Had an old CarbonROM installed before, but that failed for no reason I can pinpoint.
OK, to recover I tried to reflash the ROM - but boot process got stuck in boot animation for hours (until battery ran out).
OK, so I fired up flashtool and tried to install an FTF - but all FTFs I tried to retrieve failed to unpack.
OK - one more try - got me a stock ROM that was supposed to be flashed through recovery.
Now I get Sony splashscreen, then display turns black and stays like that forever. Only sign of something happening is that the notification LED blinks occasionally.
I tried to enter recovery - wouldn't work at all: never saw any change in boot process.
I can put the phone into flash mode and into fastboot - so I tried to flash a new TWRP:
Code:
[email protected] ~/temp/TWRP-z3 $ fastboot flash FOTAKernel recovery.img
target didn't report max-download-size
sending 'FOTAKernel' (15904 KB)...
OKAY [ 0.502s]
writing 'FOTAKernel'...
OKAY [ 1.056s]
finished. total time: 1.558s
[email protected] ~/temp/TWRP-z3 $ fastboot flash recovery recovery.img
target didn't report max-download-size
sending 'recovery' (15904 KB)...
OKAY [ 0.501s]
writing 'recovery'...
OKAY [ 1.055s]
finished. total time: 1.556s
But still the mobile won't boot into recovery
OK, there's a different TWRP available - but I can't flash it to FOTAkernel:
Code:
[email protected] ~/Downloads $ fastboot flash FOTAkernel twrp_z3_2018-03-28.img
target didn't report max-download-size
sending 'FOTAkernel' (10808 KB)...
OKAY [ 0.342s]
writing 'FOTAkernel'...
FAILED (remote: Command not allowed)
finished. total time: 0.345s
[email protected] ~/Downloads $ fastboot flash recovery twrp_z3_2018-03-28.img
target didn't report max-download-size
sending 'recovery' (10808 KB)...
OKAY [ 0.342s]
writing 'recovery'...
OKAY [ 0.721s]
finished. total time: 1.063s
Can anyone help me to get stuff working again? I'm lost for options right now - TWRP won't come up, and I can't get an FTF via flashtool to my harddrive. Any other ways to unbrick the phone?
Got a recent LinuxMint 19.x here as my machine right now. Getting a Windows up and running would be an obstacle (although I might get a hand to one).
Hey guys,
I recently flashed HAVOC OS on my 1+7 Pro.
I got to TWRP by using the boot command, however now I cannot boot to TWRP. When using the command:
Code:
fastboot flash recovery twrp.img
I get the following error:
Code:
sending 'recovery' (31440 KB)...
OKAY [ 0.697s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 0.733s
Then when I try:
Code:
fastboot boot twrp.img
I get the following error:
Code:
downloading 'boot.img'...
OKAY [ 0.698s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.728s
Is anyone able to help?
Why not try installing TWRP via magisk?? Its easier that way
/\ agree /\
:angel:
lawrence_craig said:
Hey guys,
I recently flashed HAVOC OS on my 1+7 Pro.
I got to TWRP by using the boot command, however now I cannot boot to TWRP. When using the command:
Code:
fastboot flash recovery twrp.img
I get the following error:
Code:
sending 'recovery' (31440 KB)...
OKAY [ 0.697s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 0.733s
Then when I try:
Code:
fastboot boot twrp.img
I get the following error:
Code:
downloading 'boot.img'...
OKAY [ 0.698s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.728s
Is anyone able to help?
Click to expand...
Click to collapse
Make sure you are using the latest TWRP img.
Never flash recovery. Always boot recovery and then install TWRP zip. Have you not read the instructions?
As others mentioned, easier way to recover TWRP is to flash a magisk patch boot.img and flash TWRP zip in magisk.
Thanks for the tips guys, all sorted!
Hello everyone !
I was trying to put a LineageOS on my OP7P with this rom.
I unlocked the bootloader, boot onto the TWRP image (this one), flashed the ROM and then I got into troubles.
When I flashed the ROM, I didn't see any "go back" button, so I just pressed the "reboot system" one.
I came back to recovery, only of course to see that I have the "basic" recovery menu. So I got into the bootloader mode and tried to fix this, nothing I did fixed it...
I tried and got :
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot twrpop7pro.img
downloading 'boot.img'...
OKAY [ 0.692s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.692s
I have no idea why is it not working. I tried the fastboot oem unlock, but it tells me it's already unlocked.
Then, by seaching, I tried but got this :
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp-3.3.1-74-guacamole-unified-installer-mauronofrio.zip
target reported max download size of 805306368 bytes
sending 'recovery' (17872 KB)...
OKAY [ 0.389s]
writing 'recovery'...
FAILED (remote: (recovery_a) No such partition)
finished. total time: 0.405s
Which seemed logical to me as the OP7P has 2 slots, but when I searched alternative to this answer it only brought me back to the first answer.
So now I don't know what to do to boot again on a TWRP and fix all this. Thankfully, I can boot on my main system and my LineageOS is working. But I still want to root it with Magisk and use the NanoDroid installer.
Anyway, if anyone here has any idea to help me, I would be very grateful