Related
just did a clean install v20d via lgmdp and then rooted it, thus loosing all the custom recovery (CR)
now here the problem arises...
installed ROM manager and found that it isn't showing the CR for new baseband (BB), just shows for the old one
installed goo manager and found that it still isn't compatible with our device
i found a file "twrp-thunderg-2.0.0alpha1.img" on internet while searching for device compatibility
now what should I do to install custom recovery?
all i have is .img files for both clockwork and twrp. I don't trust twrp coz they still aren't showing official status for our device
update -
i flashed recovery via lgmdp tool
but still, whats with the recovery mess?
Not sure. Possibly not supported anymore.
You can also use shinobisofts recovery flash tool.
I had done same as you and used it to flash cwm.
savagephoenix said:
Not sure. Possibly not supported anymore.
You can also use shinobisofts recovery flash tool.
I had done same as you and used it to flash cwm.
Click to expand...
Click to collapse
He figured out he could also flash a recovery with LGMDP.
---------- Post added at 11:46 PM ---------- Previous post was at 11:41 PM ----------
van_helsing_80 said:
update -
i flashed recovery via lgmdp tool
but still, whats with the recovery mess?
Click to expand...
Click to collapse
The recovery is a mechanism to repair or restore the devices OS. It is also utilized to install ROMs and updates.
sorry, what I meant was regarding the incompatibilities with the recovery. That was kind of you to explain what recovery is.
Installed CWM 6.0.1.0 and rooted this device then installed a 10.1 nightly, wiped dalvik and all but now device boots straight into recovery after samsung 10.1 logo.. I've already tried flashing back to the stock rom using Odin, flash went fine but now it just boots into stock recovery instead of CWM.. also a bit of weirdness to it.. when i click on reboot system it just turns the device off instead of "rebooting", i've tried wiping everything and nothing seems to work.. was for sure the stock rom from sammobile would do the trick but nope ... any suggestions? Thanks.
Perhaps flashing v6.0.3.3 might work. :beer:
http://forum.xda-developers.com/showthread.php?p=41159669
dynospectrum said:
Perhaps flashing v6.0.3.3 might work. :beer:
http://forum.xda-developers.com/showthread.php?p=41159669
Click to expand...
Click to collapse
Thanks for the help but this didn't work either flashed with odin just keeps going to recovery when booted ...
Neoborn1 said:
Thanks for the help but this didn't work either flashed with odin just keeps going to recovery when booted ...
Click to expand...
Click to collapse
Did you ever figure this out?
I have a 5113 doing the exact same thing. I posted a thread on here but i dont think anyone has an answer.
---------- Post added at 07:59 PM ---------- Previous post was at 07:46 PM ----------
http://forum.xda-developers.com/showthread.php?t=2404899
Above is the thread that details what is happening with mine. Sounds like the same issue to me.
Hello all,
I have been going slightly mad today trying to get my mate 7 2GB back from CWM to stock recovery. The main problem is that I do not have a stock recovery image. But after being shown where to find one, I noticed that I could not get it successfully flashed either.
Since I do not really know how to do this, I used flashify, but that did not work and either returned me to the CWM or sent me to rescue.
Can someone help me to a) get a stock recovery image for the Mate 7 version MT7-L09 and b) show me how to properly flash it?
Find stock recovery is easy.. only a question why flashify don't work for you? It work fine for me... your device is rooted?
djzero86 said:
Find stock recovery is easy.. only a question why flashify don't work for you? It work fine for me... your device is rooted?
Click to expand...
Click to collapse
Hi @dzjero86, my device is rooted and I am on the B137SP03 version atm, using CWM. Don't know why Flashify is not working for flashing a recovery image. It works fine to flash a CWM recovery. Maybe I have the wrong stock recovery... If you can find it, can you send me the link or add it as an attachment here?
Please guys help me to . i have that same problem i have been trying to flash the stock recovery again but i couldn't even with flashify after i flash i takes me to bootloader screen and it shows me a fun_error message
I have a tl-10 device
dekraan said:
Hi @dzjero86, my device is rooted and I am on the B137SP03 version atm, using CWM. Don't know why Flashify is not working for flashing a recovery image. It works fine to flash a CWM recovery. Maybe I have the wrong stock recovery... If you can find it, can you send me the link or add it as an attachment here?
Click to expand...
Click to collapse
A way to find the stock recovery is : download the whole B137SP03 Rom from the Huawei site , and use a tool called "Firmware unpacker for Huawei" whit this tool you can extract the recovery.img from the Rom and try to flash it using flashify
Firmware unpacker
http://forum.xda-developers.com/mate-7/development/firmware-unpacker-huawei-t2879754
Rom
http://forum.xda-developers.com/mate-7/general/firmware-huawei-ascend-mate-7-b137sp03-t3041629
Pd : I am not a developer or anything similar but I have some years of experience rooting and etc ...
---------- Post added at 10:12 AM ---------- Previous post was at 10:00 AM ----------
Ali_adel_medo said:
Please guys help me to . i have that same problem i have been trying to flash the stock recovery again but i couldn't even with flashify after i flash i takes me to bootloader screen and it shows me a fun_error message
I have a tl-10 device
Click to expand...
Click to collapse
You have a unlocked bootloader???
Yes i have unlocked and rooted the phone using the cwm recovery and now a i can't flash the stock recovery any more
Ali_adel_medo said:
Yes i have unlocked and rooted the phone using the cwm recovery and now a i can't flash the stock recovery any more
Click to expand...
Click to collapse
Do you tried flash via fastboot ?
fastboot flash recovery recovery.img
Or try to use this tool
http://forum.xda-developers.com/mat...custom-recovery-tool-mt7-l10-l10-mt7-t3022424
This should work.
The fast boot just stucks at waiting for device
And the tool you send says that the stock recovery works only on tl_09 and my device is tl_10
djzero86 said:
A way to find the stock recovery is : download the whole B137SP03 Rom from the Huawei site , and use a tool called "Firmware unpacker for Huawei" whit this tool you can extract the recovery.img from the Rom and try to flash it using flashify
Firmware unpacker
http://forum.xda-developers.com/mate-7/development/firmware-unpacker-huawei-t2879754
Rom
http://forum.xda-developers.com/mate-7/general/firmware-huawei-ascend-mate-7-b137sp03-t3041629
Pd : I am not a developer or anything similar but I have some years of experience rooting and etc ...
---------- Post added at 10:12 AM ---------- Previous post was at 10:00 AM ----------
You have a unlocked bootloader???
Click to expand...
Click to collapse
Ok, I couldnt access your firmware unpacker, but I did manage to use the tool you suggested.
I have a different recovery screen, but is this the right one? It has EMUI large in centre screen and the options reboot system now, wipe data/factory reset and wipe cache partition.
If this is the correct one, and I am already on the D137SP03 ROM, I should be able to locally update right?
I tried this, and got a lot further this time, but my phone gave an error message during the update. Do I need to flash the original B137SP03 rom again, even though I am already on it?
I think you maybe can flash using adb commands and also you need adb drivers working
---------- Post added at 11:23 AM ---------- Previous post was at 11:15 AM ----------
dekraan said:
Ok, I couldnt access your firmware unpacker, but I did manage to use the tool you suggested.
I have a different recovery screen, but is this the right one? It has EMUI large in centre screen and the options reboot system now, wipe data/factory reset and wipe cache partition.
If this is the correct one, and I am already on the D137SP03 ROM, I should be able to locally update right?
I tried this, and got a lot further this time, but my phone gave an error message during the update. Do I need to flash the original B137SP03 rom again, even though I am already on it?
Click to expand...
Click to collapse
Ok.... you have the stock recovery now???
djzero86 said:
I think you maybe can flash using adb commands and also you need adb drivers working
---------- Post added at 11:23 AM ---------- Previous post was at 11:15 AM ----------
Ok.... you have the stock recovery now???
Click to expand...
Click to collapse
I think so. If stock looks like I described: black screen, large EMUI logo, and the options reboot system now, wipe data/factory reset and wipe cache partition?
That's right... you have stock recovery... sometimes the update fail if the UPDATE.APP is on the internal storage.. try to flash from a micro sd card or re-download the update ....
English is not my first language...
djzero86 said:
That's right... you have stock recovery... sometimes the update fail if the UPDATE.APP is on the internal storage.. try to flash from a micro sd card or re-download the update ....
English is not my first language...
Click to expand...
Click to collapse
Great, thank you for your fantastic help!
I will get a new micro-sd card tomorrow, and will try it right away!
Good luck... come back to report
djzero86 said:
Good luck... come back to report
Click to expand...
Click to collapse
No luck so far.... I've downloaded the update.zip, put it in my mnt/ext_sdcard/dload folder and start the local update. It begins OK, as the progress bar moves along. But after about 25% it shoots to the end, and then I get an update failed screen with a red exclamation mark.
What could I try to get it to work??
dekraan said:
No luck so far.... I've downloaded the update.zip, put it in my mnt/ext_sdcard/dload folder and start the local update. It begins OK, as the progress bar moves along. But after about 25% it shoots to the end, and then I get an update failed screen with a red exclamation mark.
What could I try to get it to work??
Click to expand...
Click to collapse
Ok, I just reinstalled the B137P03 version from the how to install lollipop thread, and that went successful. Now going to try the update.zip! Keep you posted
Ah, now we're talking It seems to have worked. Phone is now showing 'Android is upgrading' and 'optimising app.....'
Great! It does seem strange I had to reinstall the B137SP03 rom, but that did the trick!
after trying to flash with twrp merlin .img file my phone is stuck on the warning bootloader unlocked screen . please help me as this is the only device that i have right now.
Merlin is the codename for Moto G Turbo, is that your device?
siredux said:
Merlin is the codename for Moto G Turbo, is that your device?
Click to expand...
Click to collapse
yes that is . motorola g turbo. what am i supposed to do now with my phone stuck on warning screen??
Are you hit ok when twrp ask to install supersu? If yes , restore your twrp backup and install supersu by your own , supersu 2.62.3 has no bootloops.
antonyjude30 said:
Are you hit ok when twrp ask to install supersu? If yes , restore your twrp backup and install supersu by your own , supersu 2.62.3 has no bootloops.
Click to expand...
Click to collapse
the only thing my phone does it stops on the bootloader screen i can only access only the recovery mode somehow and nothing else. it shows the teamwin screen. i dont knw wat to do after that. it was the latest supersu zip and i dont know wat went wrong.
flash the stock recovery or flash stock firmware.
xlr8sonic said:
the only thing my phone does it stops on the bootloader screen i can only access only the recovery mode somehow and nothing else. it shows the teamwin screen. i dont knw wat to do after that. it was the latest supersu zip and i dont know wat went wrong.
Click to expand...
Click to collapse
Did you make a TWRP back up before flashing SuperSU?
MrTooPhone said:
Did you make a TWRP back up before flashing SuperSU?
Click to expand...
Click to collapse
no i did not.
what can i do now
HelpMeruth said:
flash the stock recovery or flash stock firmware.
Click to expand...
Click to collapse
how can i do that ?
xlr8sonic said:
no i did not.
what can i do now
Click to expand...
Click to collapse
Without a backup, your only option is to re-flash stock firmware.
xlr8sonic said:
yes that is . motorola g turbo. what am i supposed to do now with my phone stuck on warning screen??
Click to expand...
Click to collapse
If I were you I would download stock firmware and flash it via fastboot to avoid any further inconviniences
I recommend flashing your factory firmware, which can easily be found on the forums here
siredux said:
If I were you I would download stock firmware and flash it via fastboot to avoid any further inconviniences
Click to expand...
Click to collapse
its is showing baseband error .. will it be gone if if i flash its firmware
xlr8sonic said:
its is showing baseband error .. will it be gone if if i flash its firmware
Click to expand...
Click to collapse
Sorry man , baseband errors normally result in no mobile network and ability to make phone calls :/. When I flashed marshmallow on my phone , it said not found next to baseband. You may want to fully flash MM then when it gets to bootloader unlocked screen , wait a few minutes. If it does nothing, try flashing twrp recovery and flashing a lollipop custom rom.
---------- Post added at 12:47 PM ---------- Previous post was at 12:47 PM ----------
xlr8sonic said:
its is showing baseband error .. will it be gone if if i flash its firmware
Click to expand...
Click to collapse
Also what baseband error are you getting ?
therealduff1 said:
Sorry man , baseband errors normally result in no mobile network and ability to make phone calls :/. When I flashed marshmallow on my phone , it said not found next to baseband. You may want to fully flash MM then when it gets to bootloader unlocked screen , wait a few minutes. If it does nothing, try flashing twrp recovery and flashing a lollipop custom rom.
---------- Post added at 12:47 PM ---------- Previous post was at 12:47 PM ----------
Also what baseband error are you getting ?
Click to expand...
Click to collapse
i attatched the imafe of the screen . i dnt knw exactluy wat baseband error it is
xlr8sonic said:
i attatched the imafe of the screen . i dnt knw exactluy wat baseband error it is
Click to expand...
Click to collapse
i also tried to flash the firmware .. but that showed zip signature varification. i also attatched the image for that
xlr8sonic said:
i also tried to flash the firmware .. but that showed zip signature varification. i also attatched the image for that
Click to expand...
Click to collapse
I had that error when flashing a new logo, I simply unchecked "check zip signature" in TWRP. All flashed OK.
MrTooPhone said:
I had that error when flashing a new logo, I simply unchecked "check zip signature" in TWRP. All flashed OK.
Click to expand...
Click to collapse
it says could not find ,META-INF/com/google/android/update-binary, int the zip file
error installing zip file xt1557_merlin_ritasia_6.0
Mate , no one noticed that you are trying to flash the ota zip in recovery. you are not meant to do that. Flash it using Fastboot. Go download Motorola device manager to get the right drivers, and get minimal adb and fastboot, when you have done that, come back here !
---------- Post added at 10:21 PM ---------- Previous post was at 10:20 PM ----------
xlr8sonic said:
i also tried to flash the firmware .. but that showed zip signature varification. i also attatched the image for that
Click to expand...
Click to collapse
You do realise you are trying to flash firmware files via recovery right..?
You are meant to extract the zip on the pc and then flash the files using fastboot commands
---------- Post added at 10:22 PM ---------- Previous post was at 10:21 PM ----------
MrTooPhone said:
I had that error when flashing a new logo, I simply unchecked "check zip signature" in TWRP. All flashed OK.
Click to expand...
Click to collapse
that trying to flash ota firmware files in twrp . that's why it failed
xlr8sonic said:
i also tried to flash the firmware .. but that showed zip signature varification. i also attatched the image for that
Click to expand...
Click to collapse
Try using mfastboot instead of fastboot, go with 6.0 firmware, make sure you flash all sparsechunks included. Baseband should be restored
I had the brilliant idea to format everything via TWRP...
TWRP is still there and I can transfer files on my phone but other than that I can do nothing else, I tried to flash 3 different roms, but none is flashing, always giving an 'error executing binary in zip /sd card' or something.
What can I do? Also tried sideloading with ADB but my computer is a ***** and never recognizes adb devices, in CMD at least.
Why don't you try rsd lite to flash stock rom? I think there are tutorials for that
Zakaria.R said:
Why don't you try rsd lite to flash stock rom? I think there are tutorials for that
Click to expand...
Click to collapse
Just downloaded and installed it.
It does not recognize my device, nothing shows up.
My computer is retarded like that. :/
coolkingler1 said:
Just downloaded and installed it.
It does not recognize my device, nothing shows up.
My computer is retarded like that. :/
Click to expand...
Click to collapse
I could recommend you to flash a cm recovery img through twrp to install a cm rom as I read in some threads (not for this device) that cm recovery helped install cm rom when twrp wouldn't, but then again if that fails you would lose twrp and end up with a crappy recovery, that's risky
Zakaria.R said:
I could recommend you to flash a cm recovery img through twrp to install a cm rom as I read in some threads (not for this device) that cm recovery helped install cm rom when twrp wouldn't, but then again if that fails you would lose twrp and end up with a crappy recovery, that's risky
Click to expand...
Click to collapse
I managed to fix my situation. My pc recognizes ADB devices again.
But not RSD Lite, that doesn't recognize my Xplay
coolkingler1 said:
I managed to fix my situation. My pc recognizes ADB devices again.
But not RSD Lite, that doesn't recognize my Xplay
Click to expand...
Click to collapse
You owe your pc some apologies haha, anyway hope you can manage to fix things up, good luck
Zakaria.R said:
You owe your pc some apologies haha, anyway hope you can manage to fix things up, good luck
Click to expand...
Click to collapse
Think i need to flash firmware first? Sideloading with CMD only got to 5% then stopped.
Tried a lot of things but I think it's simply 'bricked' if not hard then at least softbrick.
God, how am I going to explain this to my family, ruined a 330 euro device by tinkering.
coolkingler1 said:
Think i need to flash firmware first? Sideloading with CMD only got to 5% then stopped.
Click to expand...
Click to collapse
Hey buddy,
Look through these forums for a thread about TWRP flashable stock images for the X Play by dev>null. That thread SAVED me when I first got my X Play and was stuck in a bootloop.
You can push that file to your phone and then flash it with TWRP. Then you will have a stock 6.0 or 6.0.1 image with root on your phone. You can then go about reinstalling your apps and Xposed modules.
I hope this helps. Good luck, dude.
EDIT: Found the thread - http://forum.xda-developers.com/moto-x-play/general/rom-xt1563-brasil-stock-6-0-twrp-t3272979/page26
if adb recognises the device then flash the stock firmware though adb.
bablu048 said:
if adb recognises the device then flash the stock firmware though adb.
Click to expand...
Click to collapse
Doesn't work because adb only recognizes it sometimes. When I do start flashing stuff it goes <waiting for device>
EDIT: I can flash a rom maybe via fastboot but it says bootloader denies permission.
since you have twrp, why not flash (restore) those twrp specific roms?
pijes said:
since you have twrp, why not flash (restore) those twrp specific roms?
Click to expand...
Click to collapse
I didn't make one... only in titanium backup did I make a backup, for the rest I just didn't care.
The problem is that permission is denied when I try to flash via CMD/fastboot.
I got the stock EU rom, but it won't flash because permission is denied, also in TWRP it just says Failed
coolkingler1 said:
I didn't make one... only in titanium backup did I make a backup, for the rest I just didn't care.
The problem is that permission is denied when I try to flash via CMD/fastboot.
I got the stock EU rom, but it won't flash because permission is denied, also in TWRP it just says Failed
Click to expand...
Click to collapse
could you share with us some screenshots on your twrp restore attempt?
pijes said:
could you share with us some screenshots on your twrp restore attempt?
Click to expand...
Click to collapse
I can't ;( don't really have a camera to do that.
I can tell you that it looks like this with other roms:
https://www.google.nl/search?hl=nl&...mg..0.6.431.HJmBnci0L6A#imgrc=tt83t9W9pU7wmM:
and that it looks like this with the stock rom:
https://lh5.googleusercontent.com/-...09-h848-no/Screenshot_2013_12_13_13.17.49.png
Download a twrp backup from the forum put it on sdcard and restore. I think kernel won't be there in the twrp backup so install squid's
bablu048 said:
Download a twrp backup from the forum put it on sdcard and restore. I think kernel won't be there in the twrp backup so install squid's
Click to expand...
Click to collapse
I can install kernels, so squid should not be a prob.
Where can I find these backups?
coolkingler1 said:
I can install kernels, so squid should not be a prob.
Where can I find these backups?
Click to expand...
Click to collapse
Here http://forum.xda-developers.com/moto-x-play/general/rom-xt1563-brasil-stock-6-0-twrp-t3272979
---------- Post added at 04:18 AM ---------- Previous post was at 04:16 AM ----------
What OS are you running on PC ?? For RSD it must be windows 7/8 or lower , windows 10 isn't working
I linked to that thread on the previous page. No one cares about what I post!!!
bablu048 said:
Here http://forum.xda-developers.com/moto-x-play/general/rom-xt1563-brasil-stock-6-0-twrp-t3272979
---------- Post added at 04:18 AM ---------- Previous post was at 04:16 AM ----------
What OS are you running on PC ?? For RSD it must be windows 7 or lower , windows 10 isn't working
Click to expand...
Click to collapse
Windows 10 hehe. Will try out the backups.
EDIT: I can't, there is no EU version for the backups.