Gm 5 plus root problem - General Mobile GM 5 Plus Questions & Answers

Hello.I can't root my gm 5 plus android one phone.I'm using twrp 3.0.2. I opened cmd and flashed twrp 3.0.2.When ı load on my phone phone gives me error The error is
E:footer is wrong
E:Signature verification failed.
I cannot root my phone with adb.How can I root my phone
Android version : 6.0.1
Build Number :M3D62B
Baseband version: MD-MSM8952-14.15
Android Security Patch Level :1 june 2016
Ps: Sorry for bad language

MeLiqq_41 said:
Hello.I can't root my gm 5 plus android one phone.I'm using twrp 3.0.2. I opened cmd and flashed twrp 3.0.2.When ı load on my phone phone gives me error The error is
E:footer is wrong
E:Signature verification failed.
I cannot root my phone with adb.How can I root my phone
Android version : 6.0.1
Build Number :M3D62B
Baseband version: MD-MSM8952-14.15
Android Security Patch Level :1 june 2016
Ps: Sorry for bad language
Click to expand...
Click to collapse
There is no twrp compiled for our device at the moment how did you flashed it?

root
u can root it via kingroot

sarcastica said:
u can root it via kingroot
Click to expand...
Click to collapse
You can't, If you have may patch.

sarcastica said:
u can root it via kingroot
Click to expand...
Click to collapse
I tried but I couldn't

MeLiqq_41 said:
Hello.I can't root my gm 5 plus android one phone.I'm using twrp 3.0.2. I opened cmd and flashed twrp 3.0.2.When ı load on my phone phone gives me error The error is
E:footer is wrong
E:Signature verification failed.
I cannot root my phone with adb.How can I root my phone
Android version : 6.0.1
Build Number :M3D62B
Baseband version: MD-MSM8952-14.15
Android Security Patch Level :1 june 2016
Ps: Sorry for bad language
Click to expand...
Click to collapse
Everybody there is No TWRP for Android One 3rd Gen/GM5Plus.
He's thinking STOCK RECOVERY as TWRP I think he's new.
That error only comes in STOCK RECOVERY.
---------- Post added at 05:52 AM ---------- Previous post was at 05:52 AM ----------
Equal1zer said:
There is no twrp compiled for our device at the moment how did you flashed it?
Click to expand...
Click to collapse
You said you will provide me stock recovery but you didn't.

Related

Issue upgrading ZE551KL to Marshmallow

Trying to upgrade my ZE551KL to Marshmallow but I've hit an issue. I'll recap all the steps I went through today and then the error I'm getting:
Started the day with firmware 763
Took a backup with TWRP
Updated FW to 1106, 1234 and 1531 in sequence in order to prepare for update to Marshmallow
Took one more backup with TWRP
Attempted update to MM using download from ASUS, manually initiating from recovery, got the error below
Attempted update to MM again using the notification prompt after booting phone with update file on SD card (per ASUS' instructions), got the same result, below.
The error text is this:
Code:
Can't install this M package (Tue May 17 23:05:50 CST 2016)
L less than 20160426 build (Tue Dec 1 17:16:17 CST 2015)
E:Error in /sideload/package.zip
(Status 7)
E: fota_return_code 409
It seems this error typically means that the current Lollipop version is old and needs to be updated to the latest before trying to update to MM. I've validated in the About screen that my firmware version is indeed 1531 so I'm not sure what else I need to do.
I apologize if this question has been answered elsewhere. I hunted around for a while on this forum and using Google and didn't find anyone that seemed to be in this same situation.
Thank you for the help!
did you try with the stock recovery.img of 1531?
I had the exact same problem the only thing worked with TWRP was to use the back2stock method.
http://forum.xda-developers.com/zen...50kl-ze551kl-zd551kl-ze600kl-ze601kl-t3333482
murat124 said:
did you try with the stock recovery.img of 1531?
I had the exact same problem the only thing worked with TWRP was to use the back2stock method.
http://forum.xda-developers.com/zen...50kl-ze551kl-zd551kl-ze600kl-ze601kl-t3333482
Click to expand...
Click to collapse
Well I never actually flashed TWRP, I just booted it using fastboot each time I needed it. Does flashing the OTA updates update the recovery or do I have to do that manually?
I got the exact error you are getting with original recovery or TWRP. The only difference is that I was using MM and deleted the OS by mistake so I could not reflash official MM . back2stock method was the only way. Now I have TWRP, official MM via back2stock and root at the same time.
I am sure more expert members can give you better advice.
murat124 said:
I got the exact error you are getting with original recovery or TWRP. The only difference is that I was using MM and deleted the OS by mistake so I could not reflash official MM . back2stock method was the only way. Now I have TWRP, official MM via back2stock and root at the same time.
I am sure more expert members can give you better advice.
Click to expand...
Click to collapse
Does back2stock require a full wipe? I was hoping not to have to do that...
bennettj1087 said:
Trying to upgrade my ZE551KL to Marshmallow but I've hit an issue. I'll recap all the steps I went through today and then the error I'm getting:
[*]Updated FW to 1106, 1234 and 1531 in sequence in order to prepare for update to Marshmallow
Click to expand...
Click to collapse
Worked in my case when I updated to latest lollipop firmware available.
(Actually I never installed the complete firmware, just flashed
Code:
boot.img
and
Code:
recovery.img
for the latest lollipop firmware available and marshmallow FW installed like a charm, though I'd suggest you install the complete lollipop framework)

Root for Galaxy A7 SM-A700H on Android 5.0.2

Hello Guys,
I am unable to root my Galaxy A7 SM-A700H dual SIM phone. I am running on Android 5.0.2. I tried the CF Auto Root from Chainfire but it always puts the phone in a "boot loop" (stuck on the SAMSUNG logo). I will put details of my phone down below. So please can anyone help me in rooting this device.
Device Info
Model - SM-A700H
Baseband - A700HXXU1BOF7
Build Number - LRX22G.A700HXXU1BPB2
Android version - 5.0.2
Android Patch Version - 2016-03-01
Kernel Version - 3.10.49-6156462 / [email protected] #1 / Wed Feb 24 21:11:06 KST 2016
The root I tried to use - CF-Auto-Root-a73g-a73gxx-sma700h.zip
Thank you in advance.
Tamrat
Same here !
You can read my post here Patch your kernel.
Or u can use my kernel was patched here !
MAKE YOUR BACK UP FIRST!
1. make sure your security police is not up to date.
2. extract the boot.tar.zip to boot.tar.md5 And flash the boot.tar.md5 via Odin ( or TWRP : extract boot.tar.md5 to boot.img )
huynhlam said:
Same here !
You can read my post here Patch your kernel.
Or u can use my kernel was patched here !
MAKE YOUR BACK UP FIRST!
1. make sure your security police is not up to date.
2. extract the boot.tar.zip to boot.tar.md5 And flash the boot.tar.md5 via Odin ( or TWRP : extract boot.tar.md5 to boot.img )
Click to expand...
Click to collapse
Oh thank you very much bro. I just flashed the file ("kernel"?) you attached via Odin, then flashed CF Auto Root after that. Now my A7 is rooted. Thank you very much again.
TamratAK said:
Oh thank you very much bro. I just flashed the file ("kernel"?) you attached via Odin, then flashed CF Auto Root after that. Now my A7 is rooted. Thank you very much again.
Click to expand...
Click to collapse
Glad I hear it work for you ! Yes it is kernel (kernel is untouch only sepolicy is patched for allow superSU working, do not update security policy and disable auto-update (Settings > Security > Security policy updates : uncheck automatic updates )
Quick update. My phone now won't start (boot loop once again). It happened after I did a random restart. So I had to reflash the OS to get it back. Maybe it updated the security policy update.
TamratAK said:
Quick update. My phone now won't start (boot loop once again). It happened after I did a random restart. So I had to reflash the OS to get it back. Maybe it updated the security policy update.
Click to expand...
Click to collapse
yes it is update and cause boot stuck again !
huynhlam said:
yes it is update and cause boot stuck again !
Click to expand...
Click to collapse
you should update to Android 6.0.1, then root with CF Auto Root (my case i used version CF-Auto-Root-a73g-a73gxx-sma700h.tar), it will be fine
imgur[dot]com/jd2gWFn.jpg

Can't sideload stook 7.0.0 (NRD90U) over stock 6.0.1 (MTC20L)

Hello!
i tried to sideload the OTA zip from google but at around ~25% i get an error:
E3003: can't install this package (wed aug 17 23:11:29 utc 2016) over newer build (Mon Aug 29 19:46:52 utc 2016)
E: unknown command [log]
E: error in /sideload/package.zip (Status 7)
installation aborted.
I re-downloaded the ota zip but i still get the same error.
Any solutions?
Thank you !
Really? You didn't see the other Android 7 threads? You had to create another?
angelossssss said:
Hello!
i tried to sideload the OTA zip from google but at around ~25% i get an error:
E3003: can't install this package (wed aug 17 23:11:29 utc 2016) over newer build (Mon Aug 29 19:46:52 utc 2016)
E: unknown command [log]
E: error in /sideload/package.zip (Status 7)
installation aborted.
I re-downloaded the ota zip but i still get the same error.
Any solutions?
Thank you !
Click to expand...
Click to collapse
Unlock the bootloader (if you haven`t allready) and flash the individual firmware img`s in fastboot.
gee2012 said:
Unlock the bootloader (if you haven`t allready) and flash the individual firmware img`s in fastboot.
Click to expand...
Click to collapse
I'm full stock and i don't want to unlock it if not necessary. there's no other way ?
angelossssss said:
I'm full stock and i don't want to unlock it if not necessary. there's no other way ?
Click to expand...
Click to collapse
I had the same issue you had, didn`t look for a fix to be honest but flashed the img`s
gee2012 said:
I had the same issue you had, didn`t look for a fix to be honest but flashed the img`s
Click to expand...
Click to collapse
I just don't want to re-install all my apps and stuff again :crying:
If you are stock why don't you just sign up for the Nougat beta program and take the OTA update to 7.0 ??
That's what I did a lot easier
https://accounts.google.com/Service...://www.google.com/android/beta?u=0&authuser=0
Sent from my Nexus 6P using Tapatalk
scoot0073 said:
If you are stock why don't you just sign up for the Nougat beta program and take the OTA update to 7.0 ??
That's what I did a lot easier
https://accounts.google.com/Service...://www.google.com/android/beta?u=0&authuser=0
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Is that the NRD90U ?
What i'm trying to do is to not wipe my phone. I'm fully stock so i can't really backup the apps with titanium
NRD90M is what the OTA installed
Sent from my Nexus 6P using Tapatalk

[GUIDE][ROOT][UNIVERSAL] FORCE INSTALLING STOCK OTA UPDATES WITH SToCK RECOVERY

Since lollipop there is no manual update option in huawei updater and even the huawei stock recovery has no or less interface which has no adb sideload option. This became a crunch to flash the update which your friend got and which u dont.
This Method is Universal for all huawei devices
In order to apply ota update using this method , root access is a major requirement so be sure your device is rooted.
If u had twrp recovery , at first flash SuperSu package to root your device (Try systemless root only) .
After successfull root ,flash stock recovery from twrp and reboot system.
Step 1:
In my case b370 is the last ota i found for kiw-l22 which vsriram92 posted here . Thanks to him for posting the update before 99% users got their update :good:
Download the relevant update package (ota) which you need a relevant base package to install it on . Ex: b360 as base for b370 update
step 2:
just remember the path where u downloaded the package . Install Flashify from playstore or From Here
Select Zip file which is the third option in flashify .
step 3 :
Navigate to the path where u downloaded ota package select the update.zip (ota package).
flashify starts downloading the package to its path asks you for root access .
Grand Su permissions , Select Cwm recovery if flashify asks as the next option.
Now the phone reboots to recovery and starts flashing.
After the ota update , your device will be unrooted . so take a backup of your stock recovery by following below guide.
Enable Usb debugging and connect ur phone to pc.
navigate to adb folder and place twrp.img or recovery.img in adb folder ,open command window from the same folder and type
Code:
adb reboot bootloader
Now type
Code:
fastboot boot recovery.img
or what_ever_its_name.img
now it temporarily boots twrp , take a backup of your stock recovery and then flash twrp for permanent install and then reroot ur device.
Happy flashing :laugh::good:​
it gets zip signature verification failed....the method is similar to installing the zip file directly from the recovery but that doesn't work unless zip signature is verified
rbtrai said:
it gets zip signature verification failed....the method is similar to installing the zip file directly from the recovery but that doesn't work unless zip signature is verified
Click to expand...
Click to collapse
You might have installed a zip which is not stock ota update . i haven't posted this without trying . I installed b370 with this method and made this live here .
i downloaded from the link provided above which vsriram92 posted...
rbtrai said:
i downloaded from the link provided above which vsriram92 posted...
Click to expand...
Click to collapse
Were you in b360 before doing this ?
Thanks again Gopi. Another great contribution.
vsriram92 said:
Were you in b360 before doing this ?
Click to expand...
Click to collapse
yes ofcourse
This only for rooted phone ?
I'm having honor 4x unroot and I don't know how to install the ota file. Is there any way for upgrading a phone without root option and in my phone there is no local update option
Ajith san said:
This only for rooted phone ?
I'm having honor 4x unroot and I don't know how to install the ota file. Is there any way for upgrading a phone without root option and in my phone there is no local update option
Click to expand...
Click to collapse
Nope. It was there in EMUI 3 previously. Now, we can't unless it has only update.app.
so b370 is only for the ones who gave root access to their phones?
Like your contribution. Perfectly updated to B370.
rajibie said:
Like your contribution. Perfectly updated to B370.
Click to expand...
Click to collapse
great
Hello together, I tried flashing the B360 update for my L21 with this method but unfortunately I did not succeed. I followed every step but when flashify reboots to the stock recovery nothing happens. Just nothing.
I used the file for the L21 that I linked to in this post.
Any suggestions how to get it to work?
Zacki06 said:
Hello together, I tried flashing the B360 update for my L21 with this method but unfortunately I did not succeed. I followed every step but when flashify reboots to the stock recovery nothing happens. Just nothing.
I used the file for the L21 that I linked to in this post.
Any suggestions how to get it to work?
Click to expand...
Click to collapse
Are you on B350D0003 or some earlier firmware? I'm on stock B350, just rooted with Magisk+phh's superuser, and it doesn't want to flash that big file at all; tried flashing OTA update (200MB file) and it failed at 80%, causing a damn bootloop. Gah, I thought my old phone was pain in the ass...
ShadySquirrel said:
Are you on B350D0003 or some earlier firmware? I'm on stock B350, just rooted with Magisk+phh's superuser, and it doesn't want to flash that big file at all; tried flashing OTA update (200MB file) and it failed at 80%, causing a damn bootloop. Gah, I thought my old phone was pain in the ass...
Click to expand...
Click to collapse
I'm on B350D003. After I tried the OTA instead of the full package I came across the same problem with the stock recovery, but when flashing it from TWRP it did flash it, but exited with an error.
No bootloop but as a file was missing for the full update process wifi (and probably bluetooth) are not working.
If you are interrested to solve it, have a look here. It looks like there is a way to fix the problem and we are currently investigating.
Zacki06 said:
I'm on B350D003. After I tried the OTA instead of the full package I came across the same problem with the stock recovery, but when flashing it from TWRP it did flash it, but exited with an error.
No bootloop but as a file was missing for the full update process wifi (and probably bluetooth) are not working.
If you are interrested to solve it, have a look here. It looks like there is a way to fix the problem and we are currently investigating.
Click to expand...
Click to collapse
TBH, I'm on a verge to start building LOS or PAC/Slim/whatever is properly maintained and fast for my own needs and ditch EMUI completely....
I'm searching for other firmwares now via FirmwareFinder, there is a probability that one is a leaked test or something like that, because it simply doesn't want to flash. If I find out something, I'll continue on thread you've linked, to avoid flooding this one.
Hi. Thanks for your guide.
I need to update my phone with several ota updates. I just need to repeat this guide's procedure until updated to the last ota or there is a better way to do that?
Can't update.. Its fake i think.. I m still in B360
---------- Post added at 08:39 PM ---------- Previous post was at 08:37 PM ----------
rajibie said:
Like your contribution. Perfectly updated to B370.
Click to expand...
Click to collapse
How to update step by step.. Mention it plz
Tapan Patel said:
Can't update.. Its fake i think.. I m still in B360
---------- Post added at 08:39 PM ---------- Previous post was at 08:37 PM ----------
How to update step by step.. Mention it plz
Click to expand...
Click to collapse
Just because you can't do it, that doesn't mean it's fake.
Tapan Patel said:
Can't update.. Its fake i think.. I m still in B360
---------- Post added at 08:39 PM ---------- Previous post was at 08:37 PM ----------
How to update step by step.. Mention it plz
Click to expand...
Click to collapse
Just follow the procedure and you will be done

CEDRIC_NPPS25.137-72-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip

Download full fw.
BUILD REQUEST INFO:
SW Version: cedric-user 7.0 NPPS25.137-72-4 4 release-keysM8937_11.16.02.51R
MBM Version: B8.23
Modem Version: M8937_11.16.02.51R
FSG Version: FSG-8937-02.65.05
Build Fingerprint: motorola/cedric/cedric:7.0/NPPS25.137-72-4/4:user/release-keys
VERSION INFO FOUND UNDER 'ABOUT PHONE' SCREEN:
System Version: 25.246.4.cedric.retail.en.US
Model number: Moto G (5)
Android Version: 7.0
Baseband Version: M8937_11.16.02.51R
Build Number: cedric-user 7.0 NPPS25.137-72-4 4 release-keys
Build Date: Fri Aug 4 04:22:37 CDT 2017
OTHER MISC VERSION INFO:
Subsidy Lock Config: slcf_rev_d_default_v1.0.nvm
Regulatory Info (eLabel): regulatory_info_default.png
Blur Version: Blur_Version.25.246.4.cedric.retail.en.US
Version when read from CPV: cedric-user 7.0 NPPS25.137-72-4 4 release-keys
CEDRIC_NPPS25.137-72-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
What is that?
Sent from my Moto G (5) using Tapatalk
fxdRoiD said:
What is that?
Sent from my Moto G (5) using Tapatalk
Click to expand...
Click to collapse
It's the last available fw for XT1676. NPPS25.137-72-4
https://forum.xda-developers.com/g5/help/stock-rom-moto-g5-xt1676-3-16-dualsim-t3696622
Haven't seen it anywhere untill now when I got a link that was valid for just a few hours, so I thought I should download it and share it.
Is this rom work for moto g5 model XT1677 Indian varient Amazon exclusive ?? If yes voLTE is working or not ??
Anyone have NPPS25.137-79-3 for the XT1670?
Sent from my Moto G5 using Tapatalk
It can relock bootloader?
When I try to install this from TWRP I'm getting an "Invalid zip file format!" error and it refuses to.
Any thoughts on why this could be? Would it be a bad idea to use fastboot to execute all the instructions in flashfile.xml?
I'm trying to install this to rid myself of a stubborn TWRP bootloop (wasn't fixed by e.g. reflashing twrp) and to do an OEM update before trying to restore TWRP, no-verity, Magisk, and my nandroid backup.
My XT1676 currently has TWRP and Magisk. Its settings indicate build number NPPS25.137-72-4, software channel reteu, and baseband version M8937_11.16.02.51R CEDRIC_EMEADSDS_CUST.
macho_ said:
When I try to install this from TWRP I'm getting an "Invalid zip file format!" error and it refuses to.
Any thoughts on why this could be? Would it be a bad idea to use fastboot to execute all the instructions in flashfile.xml?
I'm trying to install this to rid myself of a stubborn TWRP bootloop (wasn't fixed by e.g. reflashing twrp) and to do an OEM update before trying to restore TWRP, no-verity, Magisk, and my nandroid backup.
My XT1676 currently has TWRP and Magisk. Its settings indicate build number NPPS25.137-72-4, software channel reteu, and baseband version M8937_11.16.02.51R CEDRIC_EMEADSDS_CUST.
Click to expand...
Click to collapse
To start off with this is a stock firmware - stock firmware is flashed via fastboot and not twrp using fastboot commands
secondly - if you are talking about your phone booting into twrp instead of booting to system you obviously didn't read the FAQs on my TWRP thread as the answer is there
How to flash stock firmware
https://forum.xda-developers.com/g5/development/official-stock-moto-g5-cedric-firmware-t3733897
twrp thread
https://forum.xda-developers.com/g5/development/official-twrp-3-1-1-0-moto-g5-t3699737
This is great: my searches hadn't previously led me to either of those threads, thanks.
The TWRP bootloop solution seemed to work, although after I tried do the Nov OTA update, I got back into the bootloop and the update failed. Presumably I could have just repeated the fix again.
But instead of doing that, I flashed the stock image above using fastboot. On rebooting I initially got a scary robot-with-its-front-panel-open error that just said "Error!" When I tried to reboot to recovery I got the same robot with "No command". But then weirdly it soon just booted normally on its own. From there the most recent (November) OTA update finally installed without issue, then I restored twrp, magisk, no-verity-opt-encrypt, and finally the data partitions of a backup I made before starting everything above.
I'm really happy about this: these problems had been plaguing me for a while. Thanks again.
macho_ said:
This is great: my searches hadn't previously led me to either of those threads, thanks.
The TWRP bootloop solution seemed to work, although after I tried do the Nov OTA update, I got back into the bootloop and the update failed. Presumably I could have just repeated the fix again.
But instead of doing that, I flashed the stock image above using fastboot. On rebooting I initially got a scary robot-with-its-front-panel-open error that just said "Error!" When I tried to reboot to recovery I got the same robot with "No command". But then weirdly it soon just booted normally on its own. From there the most recent (November) OTA update finally installed without issue, then I restored twrp, magisk, no-verity-opt-encrypt, and finally the data partitions of a backup I made before starting everything above.
I'm really happy about this: these problems had been plaguing me for a while. Thanks again.
Click to expand...
Click to collapse
The robot is stock recovery - hold Vol up & press power button I think to access its menu but all you can really do is a factory reset
Can i install this on 1675 variant?
My bootloader is locked
can I flash stock ROM - with the same patch but another channel (from retin to retus) on a device with a locked bootloader?
if yes, how can I do that? from adb fastboot? RSD lite?
TheFixItMan said:
To start off with this is a stock firmware - stock firmware is flashed via fastboot and not twrp using fastboot commands
secondly - if you are talking about your phone booting into twrp instead of booting to system you obviously didn't read the FAQs on my TWRP thread as the answer is there
How to flash stock firmware
https://forum.xda-developers.com/g5/development/official-stock-moto-g5-cedric-firmware-t3733897
twrp thread
https://forum.xda-developers.com/g5/development/official-twrp-3-1-1-0-moto-g5-t3699737
Click to expand...
Click to collapse
My phone is Moto g5 cedric with NPP25.137-72 android 7.0 this flash update but I want to flash oreo directly, you know about this???
rosel11078 said:
My phone is Moto g5 cedric with NPP25.137-72 android 7.0 this flash update but I want to flash oreo directly, you know about this???
Click to expand...
Click to collapse
Oreo firmware images have not been leaked/released - only the soak ota for a specific firmware - see dev section
TheFixItMan said:
Oreo firmware images have not been leaked/released - only the soak ota for a specific firmware - see dev section
Click to expand...
Click to collapse
OK so, I have to flash latest offcial stock and apply update oreo then???
TheFixItMan said:
Oreo firmware images have not been leaked/released - only the soak ota for a specific firmware - see dev section
Click to expand...
Click to collapse
Do you know what is the lastest flashable firmware for moto g5 cedric 32gb 2ram xt1670 NPP25.137.72????
That will allow me to upgrade Oreo????
CEDRIC_NPPS25.137-93-2-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml

Categories

Resources