Develop Bugs

No working ROM for my P8000

Hi,
2 weeks ago I got my P8000 from the german elephone distribution, it came with android 6. It seems to be an other version of the phone, the fingerprint sensor has moved up near the camera.
So my problem is, that I can't find a working rom for this device. I tried to root the phone and after that it did not boot anymore, so I tried to flash the 6.0 stock rom but the screen is white with moving stripes.
Where can I get a working rom for my phone?

Nobody with a new version phone who could take a dump for me?

flo1k said:
Nobody with a new version phone who could take a dump for me?
Click to expand...
Click to collapse
I think you should ask elephone (on facebook or some other social medias) for a dump, I don't see any chances that there are many people out there that own the 2016 version... :/

I wrote to the elephone facebook contact but they just pointed me to the BBS with the not working 'old' Rom file.
So if I could get another new P8000 would it be easy to take a dump oft it and flash it to my phone?

flo1k said:
I wrote to the elephone facebook contact but they just pointed me to the BBS with the not working 'old' Rom file.
So if I could get another new P8000 would it be easy to take a dump oft it and flash it to my phone?
Click to expand...
Click to collapse
I think you won't have to buy a new device, just point out to them that, that rom on the forum is for the old version and it's not working for your's. I hope they'll provide it for you.

Hey!
I just received this version and would be willing to take the dump, but I don't know how.
MTKDroidTools says unknown rom structure and doesn't allow me to do it.
Any tips?
Emile

Hey Emileh these are great news! I cannot help you with this, but surely someone here can!
Many thanks,
Flo

flo1k said:
Hi,
2 weeks ago I got my P8000 from the german elephone distribution, it came with android 6. It seems to be an other version of the phone, the fingerprint sensor has moved up near the camera.
So my problem is, that I can't find a working rom for this device. I tried to root the phone and after that it did not boot anymore, so I tried to flash the 6.0 stock rom but the screen is white with moving stripes.
Where can I get a working rom for my phone?
Click to expand...
Click to collapse
install niew rom

vagca said:
install niew rom
Click to expand...
Click to collapse
Sorry, I don't understand

I have at least two P8000(B) - and bricked one of them see this post:http://forum.xda-developers.com/elephone-p8000/help/stock-rom-p8000b-t3434477
The good news are: I still have a working one and could use this as a source to generate a firmware file... if someone could tell me how
I think I have to do the procedure with the SP Flashtool because the display of the faulty phone is not usable

FrauHofrat said:
I think I have to do the procedure with the SP Flashtool because the display of the faulty phone is not usable
Click to expand...
Click to collapse
Same as mine. The display controller seems to be another one.

I'm guessing thats just a kernel problem, right? The drivers in the kernel?

FrauHofrat said:
I have at least two P8000(B) - and bricked one of them see this post:http://forum.xda-developers.com/elephone-p8000/help/stock-rom-p8000b-t3434477
The good news are: I still have a working one and could use this as a source to generate a firmware file... if someone could tell me how
I think I have to do the procedure with the SP Flashtool because the display of the faulty phone is not usable
Click to expand...
Click to collapse
P8000B is almost impossible to brick. If you install SP flash, and download the correct recovery (like TWRP), and the correct version ROM's with scatter.txt you can recovery the phone in just about any circumstance. I put the P8000B recovery files on my PC, Formatted whole flash and bootloader. After that, the phone was bricked, and wouldn't turn on. Loaded the P8000B system recovery scatter.txt, and SP flash installed it perfectly. Booted fine. With SP flash it's almost impossible not to be able to restore the P8000B as long as you have proper files,

kgoerbig said:
P8000B is almost impossible to brick. If you install SP flash, and download the correct recovery (like TWRP), and the correct version ROM's with scatter.txt you can recovery the phone in just about any circumstance. I put the P8000B recovery files on my PC, Formatted whole flash and bootloader. After that, the phone was bricked, and wouldn't turn on. Loaded the P8000B system recovery scatter.txt, and SP flash installed it perfectly. Booted fine. With SP flash it's almost impossible not to be able to restore the P8000B as long as you have proper files,
Click to expand...
Click to collapse
This is mainly correct, but....
With SP flash it's almost impossible not to be able to restore the P8000B as long as you have proper files,
Click to expand...
Click to collapse
there is no Stock ROM, no scatter file and I think not even a TWRP or Philz Recovery available for the 'new version' of the P8000 - I call it P8000(B) because it is written on the box of the phone.
Emileh made a good description of the problem here: http://forum.xda-developers.com/elephone-p8000/general/2016-version-fingerprint-scanner-t3436270
But you could help us if you can provide the necessary files....

Is it the us version? It's the same one I have. I'll post a video how to soon
******EDIT******
FrauHofrat, sorry I did not realize that there was a "Rev.2" out for the P8000 US Version. I am surprised Elephone hasn't released a flash-able version for SPflash yet. Honestly, it would be in their best interest to ship any Rev of their US versions w/ TWRP and freely distributing flash-able images/scatter.txt, so if it gets bricked during a failed OTA update, folks would not have to send their phones back to be fixed. I have the Rev 1 of that phone.
Any word on the Elephone forum regarding the Rev. 2 version for images/scatter.txt? I will keep an eye out. Is there any specific model related info that shows up in About Phone, or written on the box/battery?
Sent from my p8000 using Tapatalk

We're not talking about the P8000-B here, which I believe has different LTE bands so it's better suited for the USA
We're talking about P8000 6.0, which is the newer version of the phone that's currently being shipped in Europe. It has some small technical changes and stock Android 6
Edit: by the way, the box does say P8000(B), but I don't really trust that description

Hi guys,
I was just looking at the elephone forum and found this: http://bbs.elephone.hk/thread-11929-1-1.html#.V7WrLDWbfSY . There's the stock rom link for the 2nd revision of the P8000, so hope you can get it working properly again.

@ardrift
Thank you for this information - the ROM works and the phone is alive again!
But there is still one thing to do: because of flashing the wrong firmware my phone lost the IMEI. This should'nt be a problem on rooted devices but the stock ROM resists all attempts to be rooted

FrauHofrat said:
@ardrift
Thank you for this information - the ROM works and the phone is alive again!
But there is still one thing to do: because of flashing the wrong firmware my phone lost the IMEI. This should'nt be a problem on rooted devices but the stock ROM resists all attempts to be rooted
Click to expand...
Click to collapse
Can you try dialing *#*6813#*#* in the stock dialer app? Someone on the elephone forum has written this as a solution, altough I don't know if it works, or how would it work... If you are stuck you can upload a screenshot, I can look at it
PS: Your IMEI numbers should be sticked on your battery, you can see them if you remove the phone's back.

Change IMEI on P8000
@ardrift:
first I thought this is a joke but actually it worked :victory:
with *#*#6813#*#* entered on the stock dialer you can acess the "IMEI-Tool" which allows you to enter a new IMEI for both SIM cards. The new IMEI stay permanent even after reboot and this also works on 'old' P8000.
Sometimes life can be so easy

How To Get Working Apn + Hotspot After Upgrade to NCQ26.69-64+ or With SPerry XT1766.

You Need From firmware.center / firmware / Motorola / Moto%20E4 / Stock / XT1766 /
SPERRY_SPRINT_NCQ26.69-48_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip Which Is Not For The XT1766 if You Flash This You Will Loose The Baseband And SoftBrick The Phone .
And From firmware.center / firmware / Motorola / Moto%20E4 / Stock / XT1766 /
XT1766_SPERRY_SPRINT_7.1.1_NCQ26.69-56_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip This One Have The Ratio And Modem And FsG images Of Your Phone Thats Why We Need It .
Lets Begin , if You Have This Phone You Had Noticed That After Upgrade To The Last Version The Ability To Add Apn And Modify Them And The Hotspot Wont Work Any More This Is Because The Locked Everything Up For No Reason Well Money Is the Reason , We need to Extract XT1766_SPERRY_SPRINT_7.1.1_NCQ26.69-56_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip in a folder and SPERRY_SPRINT_NCQ26.69-48_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
in other folder , you must know your way to flash servicefile.xml on linux or windows no details here and bootloader unlocked , well that is easy , now we have to put the files : the 2 OEM files , the 4 System Files , boot.img ,
{{{ bootloader "NO NEED" This Work Before Just Because v48 and v56 have the same bootloader version }}} , recovey.img from SPERRY_SPRINT_NCQ26.69-48_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip inside the folder that have the XT1766_SPERRY_SPRINT_7.1.1_NCQ26.69-56_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip firmware and replace those files , optional for rooting you can replace recovery.img with the Squid2 TWRP recovery.img file and The boot.img Patched Fixed F2FS kernel which is based in the stock firmware kernel sources that we are going to flash here and then flash supersu inside twrp , Well Thats It after Flashing This Downgrade Custom stock you will have back the ability to ADD apn's Again And Use The Hotspot included in the Stock Firmware , Cheers , Thanks To All The People Involved in the development for Perry Moto E4 Thanks Everybody i hope this help somebody with the XT1766. :laugh:
EDIT HELLO
Things Have Changed Dont Try To Downgrade Bootloader or The Phone Will Get Hard Bricked , Why well bootloader versions on new firmwares have been upgraded please check all the information on the Bootloader/Fastboot
MODE Of The Phone Which Version You Have , Now For Example If You Are On Version NCQS26.69-64-5 you will need SPERRY_SPRINT_NCQS26.69-64-5_cid50_XT1766-SS_7.1.1_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml full package then extract and now you will need SPERRY_SPRINT_NCQ26.69-48_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml extract it too , Now Just Move The 2 Oems Images And 4 System Images And Boot Image To SPERRY_SPRINT_NCQS26.69-64-5_cid50_XT1766-SS_7.1.1_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml Folder Next Look for RSD_Lite_Motorola_XML_To_Batch_Script on Google Download it And Watch The Video Of Rootjunky on how to use it. Very Simple Wish All Of You Luck And im Not Responsible Of Any Damage Of Your Phone Use This Guide On Your Own Terms.

ozmage said:
You Need From firmware.center / firmware / Motorola / Moto%20E4 / Stock / XT1766 /
SPERRY_SPRINT_NCQ26.69-48_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip Which Is Not For The XT1766 if You Flash This You Will Loose The Baseband And SoftBrick The Phone .
And From firmware.center / firmware / Motorola / Moto%20E4 / Stock / XT1766 /
XT1766_SPERRY_SPRINT_7.1.1_NCQ26.69-56_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip This One Have The Ratio And Modem And FsG images Of Your Phone Thats Why We Need It .
Lets Begin , if You Have This Phone You Had Noticed That After Upgrade To The Last Version The Ability To Add Apn And Modify Them And The Hotspot Wont Work Any More This Is Because The Locked Everything Up For No Reason Well Money Is the Reason , We need to Extract XT1766_SPERRY_SPRINT_7.1.1_NCQ26.69-56_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip in a folder and SPERRY_SPRINT_NCQ26.69-48_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
in other folder , you must know your way to flash servicefile.xml on linux or windows no details here and bootloader unlocked , well that is easy , now we have to put the files : the 2 OEM files , the 4 System Files , boot.img , bootloader , recovey.img from SPERRY_SPRINT_NCQ26.69-48_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip inside the folder that have the XT1766_SPERRY_SPRINT_7.1.1_NCQ26.69-56_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip firmware and replace those files , optional for rooting you can replace recovery.img with the Squid2 TWRP recovery.img file and The boot.img Patched Fixed F2FS kernel which is based in the stock firmware kernel sources that we are going to flash here and then flash supersu inside twrp , Well Thats It after Flashing This Downgrade Custom stock you will have back the ability to ADD apn's Again And Use The Hotspot included in the Stock Firmware , Cheers , Thanks To All The People Involved in the development for Perry Moto E4 Thanks Everybody i hope this help somebody with the XT1766. :laugh:
Click to expand...
Click to collapse
I flashed the Sprint firmware and had data working on my XT1766 after it got it's carrier update, the Sprint firmware does not soft brick the phone as I flashed it and can confirm it doesn't soft brick it, so you are incorrect in saying that.

I'm not sure if I did something wrong but after trying this, my phone kept saying, "phone stopped working". I had backed up my phone so I restored it. Any ideas on what might have happened?

dlinderaz said:
I'm not sure if I did something wrong but after trying this, my phone kept saying, "phone stopped working". I had backed up my phone so I restored it. Any ideas on what might have happened?
Click to expand...
Click to collapse
Yeah, don't try to restore system apps. Phone app has some quirks, it's in oem. There are oem hide xml files and so on. Why try to restore phone?

madbat99 said:
Yeah, don't try to restore system apps. Phone app has some quirks, it's in oem. There are oem hide xml files and so on. Why try to restore phone?
Click to expand...
Click to collapse
I restored the entire thing after flashed the indicated files causing the error message.

dlinderaz said:
I restored the entire thing after flashed the indicated files causing the error message.
Click to expand...
Click to collapse
Oh, I never tried this method. I used rsd lite to flash the firmware (the one op says will brick you, it didn't by the way). After flashing new firmware I restored only data, nothing system or boot related, and have had no issues.

madbat99 said:
Oh, I never tried this method. I used rsd lite to flash the firmware (the one op says will brick you, it didn't by the way). After flashing new firmware I restored only data, nothing system or boot related, and have had no issues.
Click to expand...
Click to collapse
Thank you so much for the info. I'll give that a try tomorrow. I appreciate your time and help.

dlinderaz said:
Thank you so much for the info. I'll give that a try tomorrow. I appreciate your time and help.
Click to expand...
Click to collapse
Keep in mind I have the virgin mobile version (sprint xt1766). Don't know which one you have. Some have had trouble with rsdlite on Windows 10, it worked fine for me though.
I used rsdlite from here
The newest one, 6.2.4 I think

Apn Xt1766
I just want to add apn and want to use hot spot again
As the phone is updated on latest build ..
I don't want the root access..
What's should I try then from previous build , can anyone
Guide me easy steps plz.

Xt1766 how to get working apn
Will anyone confirm

danishamini.saifi said:
Will anyone confirm
Click to expand...
Click to collapse
The steps are there. Just don't use the root part if you don't want root. Once you switch the files, flash the service file.xml with rsdlite.

madbat99 said:
The steps are there. Just don't use the root part if you don't want root. Once you switch the files, flash the service file.xml with rsdlite.
Click to expand...
Click to collapse
Thanks, ill try and share the result.

I've tested it.. It worked for me but there is an issue
With this method occurred as well..
While Turing on the phone " BAD KEY" msg pops up on
Black display for 4-5 seconds and then mobile shows Motorola logo...
Now what is suppose to be done to get rid off BAD KEY msg.

danishamini.saifi said:
I've tested it.. It worked for me but there is an issue
With this method occurred as well..
While Turing on the phone " BAD KEY" msg pops up on
Black display for 4-5 seconds and then mobile shows Motorola logo...
Now what is suppose to be done to get rid off BAD KEY msg.
Click to expand...
Click to collapse
That's normal if you unlock the bootloader. Flash the no verity opt encrypt, or magisk, and it will change from bad key to n/a. But there will always be a message if you unlock the bootloader.
I know you said you don't need root, so that bad key message is there to stay.

madbat99 said:
That's normal if you unlock the bootloader. Flash the no verity opt encrypt, or magisk, and it will change from bad key to n/a. But there will always be a message if you unlock the bootloader.
I know you said you don't need root, so that bad key message is there to stay.
Click to expand...
Click to collapse
oh... i got it, thanks...
just one thing more please, if i go towards rooting the phone as well, will this be removed or N/A or something will be there?

danishamini.saifi said:
oh... i got it, thanks...
just one thing more please, if i go towards rooting the phone as well, will this be removed or N/A or something will be there?
Click to expand...
Click to collapse
N/A will be there. But you can flash a new boot logo to kinda hide it. Instead of a black screen, any logo you want, maybe with a white strip at the top to hide it. I'll get you a link.
Here are some good ones. https://forum.xda-developers.com/mo...om-boot-logos-converted-t3759320/post75787882
And here is the guide to make your own
https://forum.xda-developers.com/moto-e4/how-to/replace-n-boot-image-t3687212/post74118155

@madbat99
Everything you shared was perfect I made my own logo to hide bad key apn working ..
Now I want to have thebroot access in my phone XT1766..
TWRP IS ALREADY ISTALLED ON THE PHONE AS I AM FLASHING LOGOS..
WHAT SHOULD I INSTALLED TO GET ROOT ACCESS ..
SUPER USER ETC.. PLZ SHARE WITH ME..
and the main reason to have the root access is, I want to block or disable OTA update ..
Plz confirm, how will it be possible ..as I downgraded to get working APN But phone updated again now.
I want the phone to be stopped from being updated..
Plz help me out fixing this..
Thanks

danishamini.saifi said:
@madbat99
Everything you shared was perfect I made my own logo to hide bad key apn working ..
Now I want to have thebroot access in my phone XT1766..
TWRP IS ALREADY ISTALLED ON THE PHONE AS I AM FLASHING LOGOS..
WHAT SHOULD I INSTALLED TO GET ROOT ACCESS ..
SUPER USER ETC.. PLZ SHARE WITH ME..
and the main reason to have the root access is, I want to block or disable OTA update ..
Plz confirm, how will it be possible ..as I downgraded to get working APN But phone updated again now.
I want the phone to be stopped from being updated..
Plz help me out fixing this..
Thanks
Click to expand...
Click to collapse
Just don't accept the update. You can root by flashing magisk. You will still receive update notification. You'll need to disable the moto update app. I forget which one exactly. But your phone shouldn't be able to do ota updates once you are rooted with twrp installed. The update will fail.
here is the root thread.

madbat99 said:
Just don't accept the update. You can root by flashing magisk. You will still receive update notification. You'll need to disable the moto update app. I forget which one exactly. But your phone shouldn't be able to do ota updates once you are rooted with twrp installed. The update will fail.
here is the root thread.
Click to expand...
Click to collapse
Thank you. I wish I had known this. I had to flash the stock recovery, etc for the updates to work. A little bit of an unnecessary hastle.

dlinderaz said:
Thank you. I wish I had known this. I had to flash the stock recovery, etc for the updates to work. A little bit of an unnecessary hastle.
Click to expand...
Click to collapse
Ota updates will likely always fail if you have twrp, or have modified the system in any way. The ota performs many checks (assert props) to see if the system is clean. If any asserts fail, the ota will fail. Even restoring the stock recovery doesn't guarantee the ota will work.

Moto z play stuck in fastboot

So i kinda ****ed up on trying to install a custom rom, dint make a backup and had wrong bootloader for the rom i had planned. After trying different things to fix it. it went from bad to worse ( i think) and now im stuck in the fastboot menu. TWRP cannot boot up, it has error messages but it go's away fast so i cant see them.
Can i still recover my phone?

Somebodyz said:
So i kinda ****ed up on trying to install a custom rom, dint make a backup and had wrong bootloader for the rom i had planned. After trying different things to fix it. it went from bad to worse ( i think) and now im stuck in the fastboot menu. TWRP cannot boot up, it has error messages but it go's away fast so i cant see them.
Can i still recover my phone?
Click to expand...
Click to collapse
So do you have a backup of stock or anything?
If not, RSD lite latest 7.1.1 stock
https://forum.xda-developers.com/mo...ock-images-t3736767/post75236696#post75236696

KrisM22 said:
So do you have a backup of stock or anything?
If not, RSD lite latest 7.1.1 stock
https://forum.xda-developers.com/mo...ock-images-t3736767/post75236696#post75236696
Click to expand...
Click to collapse
Did not make a backup no, RSD doesnt see my phone though. how would i go about fixing it? Windows does see my phone as fastboost addison s

Somebodyz said:
Did not make a backup no, RSD doesnt see my phone though. how would i go about fixing it? Windows does see my phone as fastboost addison s
Click to expand...
Click to collapse
What version of RSD do you have - it's on the top bar when you stat RSD.

KrisM22 said:
What version of RSD do you have - it's on the top bar when you stat RSD.
Click to expand...
Click to collapse
the version is : RSD Lite v6.2.4 multi-flash / multiflex tool. is that the correct one?

Somebodyz said:
the version is : RSD Lite v6.2.4 multi-flash / multiflex tool. is that the correct one?
Click to expand...
Click to collapse
yes, now try a number of different cables. Make sure your phone is in fastboot mode.

That work?

KrisM22 said:
That work?
Click to expand...
Click to collapse
Tried to find, and failed in, finding other cables since this is the only phone with usb-c. are there other possibilites or should i buy a new cable?

Somebodyz said:
Tried to find, and failed in, finding other cables since this is the only phone with usb-c. are there other possibilites or should i buy a new cable?
Click to expand...
Click to collapse
Only reason I suggested that was because of second post on this thread
https://forum.xda-developers.com/mo...ock-images-t3736767/post75236696#post75236696
I did one a couple days ago with an old A to micro cable and a cheap ($3 for 5) Micro female to C male adapter that I got on ebay. Worked fine. Other than that I have no ideas. Sorry. I understand there may be some need to have cables with 56K ohm resisters if used for charging, but I don't have any of those yet - still using old stuff.

KrisM22 said:
Only reason I suggested that was because of second post on this thread
https://forum.xda-developers.com/mo...ock-images-t3736767/post75236696#post75236696
I did one a couple days ago with an old A to micro cable and a cheap ($3 for 5) Micro female to C male adapter that I got on ebay. Worked fine. Other than that I have no ideas. Sorry. I understand there may be some need to have cables with 56K ohm resisters if used for charging, but I don't have any of those yet - still using old stuff.
Click to expand...
Click to collapse
So i managed to get it to connect with a different cable (yeay), but i was wondering how much the stock rom version affects stuff? since there seem to be of stock roms to choose from. after ****ing it up i dont want to do that again.
moto z play
product/variant: addison xt1635-02 32gb p7
bootloader: c0.14 (sha-9325e5f, 2016-07-11)
Would anyone be able to give any pointers to what specific one i need?

Try to reflash the latest TWRP

mijing said:
Try to reflash the latest TWRP
Click to expand...
Click to collapse
if it try to boot it from cmd or if i try to reflash it, it says: cannot mount /data and unable to find crypto footer. on the top line. RSD Lite sees my phone now though, so do i need to reflash twrp?

Somebodyz said:
if it try to boot it from cmd or if i try to reflash it, it says: cannot mount /data and unable to find crypto footer. on the top line. RSD Lite sees my phone now though, so do i need to reflash twrp?
Click to expand...
Click to collapse
Did you unlock your bootloader before flashing the TWRP?
Twrp reflash is will not be damage our phone you can try it ?

mijing said:
Did you unlock your bootloader before flashing the TWRP?
Twrp reflash is will not be damage our phone you can try it
Click to expand...
Click to collapse
as i said i did try to reflash it and it gave me that message. and yea i did unlock the bootloader first.

Somebodyz said:
So i managed to get it to connect with a different cable (yeay), but i was wondering how much the stock rom version affects stuff? since there seem to be of stock roms to choose from. after ****ing it up i dont want to do that again.
moto z play
product/variant: addison xt1635-02 32gb p7
bootloader: c0.14 (sha-9325e5f, 2016-07-11)
Would anyone be able to give any pointers to what specific one i need?
Click to expand...
Click to collapse
Yay!!! cable!!! Who would have guessed!! Thanks @okaban !!!
Which one you choose depends mostly on which country or area you are in because flashing one from another country will mess things up (wrong radio frequencies). Then choose the latest one - never one earlier than where you were at. So what country/area are you in? and I'll try to help you choose.

KrisM22 said:
Yay!!! cable!!! Who would have guessed!! Thanks @okaban !!!
Which one you choose depends mostly on which country or area you are in because flashing one from another country will mess things up (wrong radio frequencies). Then choose the latest one - never one earlier than where you were at. So what country/area are you in? and I'll try to help you choose.
Click to expand...
Click to collapse
yea had to wait till today for the cables to arive, hence the delay.
But im from the netherlands (europe). and im guessing the one i was at is from 2016-07-11, atleast thats the date at the BL: message

Somebodyz said:
yea had to wait till today for the cables to arive, hence the delay.
But im from the netherlands (europe). and im guessing the one i was at is from 2016-07-11, atleast thats the date at the BL: message
Click to expand...
Click to collapse
Lots of questions for you to answer in here so read till end before start!
Okay. We need an expert (someone in Netherlands who has done it!!!)
I was thinking you were reteu and this post would agree
https://forum.xda-developers.com/showpost.php?p=72013707&postcount=126
though not totally certain.
The only rom I see for reteu is 24-104-25 which if you d/l and expand it (which I did) is 6.0.1 .
- - - - -
I didn't ask - are you able to boot to stock now?
- - - - - - -
Back to first post, you say you got error messages from twrp when you tried to flash a custom ROM. This would be typical if you were still on 6.x bootloader. and trying to flash a custom 8.x ROM.
So:
1) Had you ever updated stock (ota) to nougat?
2) did you go to motorola and unlock bootloader?
if no to update and yes to unlock, let's take @mijing 's idea and reflash TWRP, though I am going to suggest you go back in time a bit and flash this one:
https://androidfilehost.com/?fid=745425885120744582
That one will work for flashing 7.x custom ROMs and is the one I am using at the moment. It will not deal with 8.x custom ROMs but we can easily deal with that later.
To flash TWRP:
boot to fastboot on phone
connect via (good ) cable
On PC in terminal
To temporarily boot this recovery: (substitute actual name of TWRP you downloaded)
Code:
fastboot boot twrp.img
Don't reboot:
use vol up/dn to step to recovery and press power and see if it in fact boots to TWRP.
If it does, then boot back to bootloader and
To permanently flash it: again substitute correct name of img
Code:
fastboot flash recovery twrp.img
If that works that should get you going for flashing 7.x custom ROMs,
though if you want stock you would have to take a CHANCE and RSD that one above. If that works you would still have to flash TWRP. It would NOT affect your bootloader-unlock status.

KrisM22 said:
Lots of questions for you to answer in here so read till end before start!
Okay. We need an expert (someone in Netherlands who has done it!!!)
I was thinking you were reteu and this post would agree
https://forum.xda-developers.com/showpost.php?p=72013707&postcount=126
though not totally certain.
The only rom I see for reteu is 24-104-25 which if you d/l and expand it (which I did) is 6.0.1 .
- - - - -
I didn't ask - are you able to boot to stock now?
- - - - - - -
Back to first post, you say you got error messages from twrp when you tried to flash a custom ROM. This would be typical if you were still on 6.x bootloader. and trying to flash a custom 8.x ROM.
So:
1) Had you ever updated stock (ota) to nougat?
2) did you go to motorola and unlock bootloader?
if no to update and yes to unlock, let's take @mijing 's idea and reflash TWRP, though I am going to suggest you go back in time a bit and flash this one:
https://androidfilehost.com/?fid=745425885120744582
That one will work for flashing 7.x custom ROMs and is the one I am using at the moment. It will not deal with 8.x custom ROMs but we can easily deal with that later.
To flash TWRP:
boot to fastboot on phone
connect via (good ) cable
On PC in terminal
To temporarily boot this recovery: (substitute actual name of TWRP you downloaded)
Code:
fastboot boot twrp.img
Don't reboot:
use vol up/dn to step to recovery and press power and see if it in fact boots to TWRP.
If it does, then boot back to bootloader and
To permanently flash it: again substitute correct name of img
Code:
fastboot flash recovery twrp.img
If that works that should get you going for flashing 7.x custom ROMs,
though if you want stock you would have to take a CHANCE and RSD that one above. If that works you would still have to flash TWRP. It would NOT affect your bootloader-unlock status.
Click to expand...
Click to collapse
i dint make a backup at the start so i lost all OS. i dont think i updated the stock the nougat, and i dint know what it meant so i ignored it (basicly where this mess started)
and i did manage to flash the twrp you sent me.
and i dint really want stock i thought it would be better to go back to it.
i want this rom: https://forum.xda-developers.com/moto-z-play/development/rom-unofficial-cyanogenmod-14-1-t3495644
it says i need a nougat bootloader, do i have that now or do i still need to do stuff to get this rom?
(also a massive thanks for all of your help so far)

Somebodyz said:
i dint make a backup at the start so i lost all OS. i dont think i updated the stock the nougat, and i dint know what it meant so i ignored it (basicly where this mess started)
and i did manage to flash the twrp you sent me.
and i dint really want stock i thought it would be better to go back to it.
i want this rom: https://forum.xda-developers.com/moto-z-play/development/rom-unofficial-cyanogenmod-14-1-t3495644
it says i need a nougat bootloader, do i have that now or do i still need to do stuff to get this rom?
(also a massive thanks for all of your help so far)
Click to expand...
Click to collapse
This has all been re-written:
You're welcome! and thanks to @mijing !!!!!!
Wow - we got much further than I thought! Good work!!!
No, I believe you have a MM B/L,
The problem with the 7.x bootloader mod is that once you apply it I believe you can never RSD lite back to 6.0.1 or you will brick your phone and need to send it to Moto for blankflash. Course you may decide that's a moot point.
I don't know if LinOS 14 (7.x) needs a 7.x bootloader - I think I was wrong - I think it may indeed. LinOS 14 should be a good one for you to play with and should flash fine with that TWRP. I also highly recommend
https://forum.xda-developers.com/moto-z-play/development/rom-aospextended-rom-v4-6-amulyax-t3735010
which I flashed yesterday and love.
Both those should flash fine with the Deh TWRP you have on.
Keep us posted.
---------- Post added at 03:14 PM ---------- Previous post was at 03:05 PM ----------
@somebodyz I just redid the above post - a lot was wrong.

KrisM22 said:
This has all been re-written:
You're welcome! and thanks to @mijing !!!!!!
Wow - we got much further than I thought! Good work!!!
No, I believe you have a MM B/L,
The problem with the 7.x bootloader mod is that once you apply it I believe you can never RSD lite back to 6.0.1 or you will brick your phone and need to send it to Moto for blankflash. Course you may decide that's a moot point.
I don't know if LinOS 14 (7.x) needs a 7.x bootloader - I think I was wrong - I think it may indeed. LinOS 14 should be a good one for you to play with and should flash fine with that TWRP. I also highly recommend
https://forum.xda-developers.com/moto-z-play/development/rom-aospextended-rom-v4-6-amulyax-t3735010
which I flashed yesterday and love.
Both those should flash fine with the Deh TWRP you have on.
Keep us posted.
---------- Post added at 03:14 PM ---------- Previous post was at 03:05 PM ----------
@somebodyz I just redid the above post - a lot was wrong.
Click to expand...
Click to collapse
So adb devices doesnt let me see my device. but adb sideload works. only problem is, is: This package supports bootloaders: 0xc105, 0xC106, 0xC107, 0xC112, 0xC113 and this device has bootloader 0xc014. do i need an older version then or what should i do?
i just found this https://forum.xda-developers.com/showpost.php?p=74069195&postcount=91, is that a good thing for me to do?

PSA: Back Up your EFS and Persist!

Just a reminder to back up your EFS and persist in TWRP to avoid disastrous consequences. These house code that keeps your IMEI and VoLTE working as they should. If you end up losing you IMEI, 4G, or your VoLTE, restoring these will save you. I don't think the official TWRP offers a way to back up persist, so you can back it up using this unofficial image.
IF YOU FLASH STOCK ROM WITH FASTBOOT, YOU WILL LOSE YOUR IMEI!
Don't attempt to go back to stock with fastboot. Instead, use the TWRP flashable stock ROM found at this link. It is not perfect from what I have heard, but it is worth keeping your IMEI and your VoLTE intact.
If you have already lost your IMEI/VoLTE/4G, there is currently NO SOLUTION. The official 8.1 update is nearing us and we can only hope that it will fix this issue.

Good info and thanks for the heads up. I was about to flash Oreo these days. Although I always backup EFS, I don't know if official TWRP has persist backup support, but I found this and thought I'd share it. I haven't tried it yet: https://forum.xda-developers.com/g5-plus/how-to/unofficial-twrp-3-2-1-1-persist-backup-t3775954

Jrhotrod said:
Just a reminder to back up your EFS and persist in TWRP to avoid disastrous consequences. These house code that keeps your IMEI and VoLTE working as they should. If you end up losing you IMEI, 4G, or your VoLTE, restoring these will save you. I don't think the official TWRP offers a way to back up persist, so you can back it up using this unofficial image.
IF YOU FLASH STOCK ROM WITH FASTBOOT, YOU WILL LOSE YOUR IMEI!
Don't attempt to go back to stock with fastboot. Instead, use the TWRP flashable stock ROM found at this link. It is not perfect from what I have heard, but it is worth keeping your IMEI and your VoLTE intact.
If you have already lost your IMEI/VoLTE/4G, there is currently NO SOLUTION. The official 8.1 update is nearing us and we can only hope that it will fix this issue.
Click to expand...
Click to collapse
Thanks man very informative. I was asking from a long time for a way to backup persist partition. One question though, will flashing this twrp will affect my current rom? (Lineage os 15.1)

spandy992 said:
Thanks man very informative. I was asking from a long time for a way to backup persist partition. One question though, will flashing this twrp will affect my current rom? (Lineage os 15.1)
Click to expand...
Click to collapse
Nope! It won't. It only overwrites the recovery partition.

yep seems that i'm the latest statistic, lost imei and now stuck with only 3G at best. Tried everything with no luck so heres hoping that oreo with fix it or the phone is going in the trash and I'm going with Nokia or Sony for the next device. Not the devs fault as this was my doing of trusting a presist file from an xda post, still moto should allow users to rollback firmware succesfully like any other oem ex. HTC.

We should try to promove this: https://forum.xda-developers.com/g5-plus/help/dev-fixing-baseband-t3806064 , So people can help this dev who´s trying to fix this issues

attack11 said:
We should try to promove this: https://forum.xda-developers.com/g5-plus/help/dev-fixing-baseband-t3806064 , So people can help this dev who´s trying to fix this issues
Click to expand...
Click to collapse
I'd love to but i'm really not sure how I can help since I trashed my imei and cant recover it. Been trying anything I can for the past day but nothing sticks. The most I can get is 3G with no imei

Jrhotrod said:
If you have already lost your IMEI/VoLTE/4G, there is currently NO SOLUTION.
Click to expand...
Click to collapse
Actually, there is a fix around which works. I can tell by first hand experience. My VoLTE never worked with my Potter until today. I read this thread thoroughly and I still can't believe it's working :laugh:

When you flash back to stock from Oreo roms or flash stock firmware again you will automatically lose IMEI and network connectivity.
Here's the Persist file linked in my first guide https://forum.xda-developers.com/g5-plus/how-to/moto-g5-xt1687-retus-s-unlocked-retail-t3806954 :
Code:
https://www23.zippyshare.com/v/13MfpRhg/file.html
TWRP recovery needs to be fastboot flashed again after you flash back to the stock firmware.
You need to make an EFS backup in TWRP Recovery to create the EFS folder in your phone storage, after you flash stock rom.
The persist.img backup needs to be restored in TWRP after you place it in your phone storage > TWRP folder > newly created EFS backup folder
Restore persist.img in TWRP after flashing stock firmware, you should not be flashing firmware only. Persist.img is what gives you your LTE network signal and IMEI back.

tuxattack80 said:
I'd love to but i'm really not sure how I can help since I trashed my imei and cant recover it. Been trying anything I can for the past day but nothing sticks. The most I can get is 3G with no imei
Click to expand...
Click to collapse
Yes,I faced that too, you must flash and oreo rom and IMEI should be back, then for 4g you must do in fastboot (with the oreo rom):
fastboot erase modemst1
fastboot erase modemst2
And should be fine, then backup that efs and you can restore in stock rom to get signal, if hoy get an ota you must restore the efs backup again
boype said:
Actually, there is a fix around which works. I can tell by first hand experience. My VoLTE never worked with my Potter until today. I read this thread thoroughly and I still can't believe it's working :laugh:
Click to expand...
Click to collapse
That thread uses a persist backup from a moto g 4, Its a bad idea, some people report greenish/yellowish pictures with camera

attack11 said:
Yes,I faced that too, you must flash and oreo rom and IMEI should be back, then for 4g you must do in fastboot (with the oreo rom):
fastboot erase modemst1
fastboot erase modemst2
And should be fine, then backup that efs and you can restore in stock rom to get signal, if hoy get an ota you must restore the efs backup again
That thread uses a persist backup from a moto g 4, Its a bad idea, some people report greenish/yellowish pictures with camera
Click to expand...
Click to collapse
Yeah that always worked before but not now, if I flash an Oreo rom the best I can get is 3G with 0 as my imei. Thinking my persist partition is corrupted or something similar. In the past I could see baseband version changes with OTA updates but now it stays at the same version number no matter how far back I go with stock, fastboot all the way back to initial with no change. May have to try boype's link as I'm out of options really other than pulling out my e4 and tossing this thing in a drawer till Oreo arrives. Being a US variant if it's even safe to flash the Moto g4 persist file but in this case I don't have to much to lose lol
Tried the Moto g4 presist file with no luck so I give up. 3G for me until Oreo drops or a good deal pops up on Amazon or bestbuy lol

tuxattack80 said:
Yeah that always worked before but not now, if I flash an Oreo rom the best I can get is 3G with 0 as my imei. Thinking my persist partition is corrupted or something similar. In the past I could see baseband version changes with OTA updates but now it stays at the same version number no matter how far back I go with stock, fastboot all the way back to initial with no change. May have to try boype's link as I'm out of options really other than pulling out my e4 and tossing this thing in a drawer till Oreo arrives. Being a US variant if it's even safe to flash the Moto g4 persist file but in this case I don't have to much to lose lol
Tried the Moto g4 presist file with no luck so I give up. 3G for me until Oreo drops or a good deal pops up on Amazon or bestbuy lol
Click to expand...
Click to collapse
Baseband version looks off after flashing different persist files don't remember seeing anything that ended in q before.

attack11 said:
That thread uses a persist backup from a moto g 4, Its a bad idea, some people report greenish/yellowish pictures with camera
Click to expand...
Click to collapse
I know, but I have no problems with it whatsoever.

tuxattack80 said:
I'd love to but i'm really not sure how I can help since I trashed my imei and cant recover it. Been trying anything I can for the past day but nothing sticks. The most I can get is 3G with no imei
Click to expand...
Click to collapse
Bro my moto g1 was also trashed 3 years ago when i installed cyanogemmod on it , after that reverted to stock and upgraded to lollipop os. Phone went dead . lesson learnt was never mess up too much with motorola.
---------- Post added at 01:45 PM ---------- Previous post was at 01:08 PM ----------
Jrhotrod said:
Nope! It won't. It only overwrites the recovery partition.
Click to expand...
Click to collapse
Bro just backed up efs. It showed 0 mb size on twrp! And the size of persist backup.sha is 320 kb only! Is this normal?

spandy992 said:
Bro my moto g1 was also trashed 3 years ago when i installed cyanogemmod on it , after that reverted to stock and upgraded to lollipop os. Phone went dead . lesson learnt was never mess up too much with motorola.
---------- Post added at 01:45 PM ---------- Previous post was at 01:08 PM ----------
Bro just backed up efs. It showed 0 mb size on twrp! And the size of persist backup.sha is 320 kb only! Is this normal?
Click to expand...
Click to collapse
.sha is a digest file, meant to verify the backup, not the actual backup.

thedr34m13 said:
.sha is a digest file, meant to verify the backup, not the actual backup.
Click to expand...
Click to collapse
Thanks. I checked persist.ext4.win that is also only 320 kb in size. Is that normal?

spandy992 said:
Thanks. I checked persist.ext4.win that is also only 320 kb in size. Is that normal?
Click to expand...
Click to collapse
Persist is small, and TWRP compresses everything too. So I'd say it's normal.

spandy992 said:
Bro my moto g1 was also trashed 3 years ago when i installed cyanogemmod on it , after that reverted to stock and upgraded to lollipop os. Phone went dead . lesson learnt was never mess up too much with motorola.
---------- Post added at 01:45 PM ---------- Previous post was at 01:08 PM ----------
Bro just backed up efs. It showed 0 mb size on twrp! And the size of persist backup.sha is 320 kb only! Is this normal?
Click to expand...
Click to collapse
Yeah I'm starting to see why they can compete in the budget market. They're cheap for a reason and that reason is ****ty support and software. This my first Moto device since the old school days of the razor flip phones and will more than likely be my last. Either going back to HTC or giving Nokia or Sony a try.
Scratch that the last Moto phone I had was the OG Moto X and that was a real Motorola phone.

tuxattack80 said:
Yeah I'm starting to see why they can compete in the budget market. They're cheap for a reason and that reason is ****ty support and software. This my first Moto device since the old school days of the razor flip phones and will more than likely be my last. Either going back to HTC or giving Nokia or Sony a try.
Scratch that the last Moto phone I had was the OG Moto X and that was a real Motorola phone.
Click to expand...
Click to collapse
Yes motorola has changed drasticaly. Moto g1 was a good phone even for today ultra budget standards. Though i wont recommend nokia if you are into this custom rom and kernel stuff because there are none to very few roms(if any) for nokia.

spandy992 said:
Yes motorola has changed drasticaly. Moto g1 was a good phone even for today ultra budget standards. Though i wont recommend nokia if you are into this custom rom and kernel stuff because there are none to very few roms(if any) for nokia.
Click to expand...
Click to collapse
Yeah I can see your point there but honestly with age I find myself getting to damn OCD for ROMs and only really seem to stick with ones that are close to stock anyways. I think for me it's about having the latest version of Android and not the millions of settings options so if I can find an oem that actually updates there phones more than once in the devices life time is be happy and kind of the reason both Sony and Nokia stand out to me right now

Question My phone is completely effed up now....

Locked my boatloader by mistake now it won't boots I need help ASAP.... I'm losing my mind over here I need someone to help me please for the love of God somebody... Just bought this phone for like $1,000 and now I'm looking at a ****ing brick......

no worries, you technically cant brick it that easily.
Check the MSM thread for your exact model and follow the steps get it back and running again.

^ Yeah an MSM flash will have you right as rain. Just wondering how the you locked the bootloader "by mistake" that seems like a difficult mistake to make.

was trying to restore and forgot how op works lol...i got it fixed now. while your here, how can i flash twrp and flash a rom? having issues with this now..

Anybody have any ideas of how I can ROM my phone? Been sitting here trying to do it for the last I don't know how long now

So I'm not sure about YOUR phone, if you have a recovery partition you can just flash recovery, if you don't have a recovery partition then you need to fastboot boot twrp first. And there are a few ways to flash a rom, my recommendation would be Fastboot Enhance I personally haven't tried it yet but it seems to work pretty good and even though it's in the 8T category it should work fine. Now one thing that is noteworthy with Fastboot enhance though is that it flashes the current slot instead of the inactive slot.

this.guy.lol said:
Anybody have any ideas of how I can ROM my phone? Been sitting here trying to do it for the last I don't know how long now
Click to expand...
Click to collapse
Didn't reply accidently, not the first time I've done that. Read my previous post.

Brandon.Bissonnette said:
Didn't reply accidently, not the first time I've done that. Read my previous post.
Click to expand...
Click to collapse
thx man