I did some tricks (like I did before on XT1033->XT1032 variant) and it worked like a charm!!! I'm uploading at this time a flashable zip. I'll post instructions after upload.
There's some screenshots attached.
[]'s
Installation steps:
1) Flash RETUAWS_XT1064_4.4.4_KXB21.85-17_cid9_CFC without flashing fsg.mbn (if you're on another firmware, you'll get errors on install process)
Important: Do not flash fsg.mbn or you will have NO SIGNAL after installation and need to flash XT1068/XT1069 fsg.mbn back after the process to get signal back.
2) Install custom recovery (CWM, TWRP, etc...)
3) Download and install update_nofsg.zip via recovery.
4) Wipe cache/data.
5) If you doesn't get any error message at install process, reboot and wait... (it's around 5 minutes first startup)
update-nofsg-working.zip - https://drive.google.com/open?id=0B3o5NziVM8e5UU9QRjNaYzJQeG8&authuser=0
(I bring back this file because someone said to me that this is working and sent to me screenshots.)
Problems with file permissions. When I get home, I'll fix this.
Magically it's working again. =O
Buglist:
1) no sim selector activity, you need to select a single sim for voice calls (I'm working on this)
Working receive calls from both SIMs
Finally lollipop for xt1058!!
Thanks so much for sharing this.
However, since you can't upload the file right now, would you be able to give a short step by step (I'd gladly take bullett points without long descriptions just as a guideline).
Also: Does it require root? Unlocked phone?
Thanks again!
ffosilva said:
I did some tricks (like I did before on XT1033->XT1032 variant) and it worked like a charm!!! I'm uploading at this time a flashable zip. I'll post instructions after upload.
There's some screenshots attached.
[]'s
PS: See my reputation before saying that this trick is fake. =P
PS2 - AND IMPORTANT! You need to flash RETUAWS_XT1064_4.4.4_KXB21.85-17_cid9_CFC without fsg.mbn image. (keep stock fsg image)
OK:
I can't upload right now the flashable zip (i'm using 3G right now). The trick is adding these lines to end of /system/build.prop file:
persist.radio.multisim.config=dsds
persist.multisim.config=dsds
And flashing back fsg.mbn from stock firmware.
[]'s
Click to expand...
Click to collapse
eagerly waiting
Will there be any drawbacks in installing this ROM? Maybe more battery drain or something?
Use your head, search and read, don't just ask. You're a Senior Member!! Use google to search Project Volta.
Hey, I'm Brazilian too! Parabéns, cara, haha! What have you done? Flashed 4.4.4 image from xt1063 into xt1068, upgraded to lollipop and then just edited the build.prop?
Will Mobile Network eventually work in Europe? Since I'm still waiting for Lollipop to arrive on my XT1068
@samcortez after that, you must flash your original (mean from your original stock KK software) fsg.mbc using mfastboot.
Step by step or a zip file would be awesome, I might try this later
cant wait you upload zip file :good:
Adaho0 said:
Use your head, search and read, don't just ask. You're a Senior Member!! Use google to search Project Volta.
Click to expand...
Click to collapse
Jesus. Jump the gun much? I asked if installing this rom would have some drawbacks. Learn english and then come back to me.
nqddnwhb said:
cant wait you upload zip file :good:
Click to expand...
Click to collapse
Uploading right now.
I have rooted the phone. Please included the steps to flash a rooted XT1068.
Thanks
Great work! É DO BRASIL! hahaha
The flashable file...I have to root my device and flash through recovery, or I can just sideload it via adb?
thx!
ffosilva said:
Uploading right now.
Click to expand...
Click to collapse
So we can falsh it from recovery like a ROM ? Thanks for your great work!
ffosilva said:
I did some tricks (like I did before on XT1033->XT1032 variant) and it worked like a charm!!! I'm uploading at this time a flashable zip. I'll post instructions after upload.
There's some screenshots attached.
[]'s
PS: See my reputation before saying that this trick is fake. =P
PS2 - AND IMPORTANT! You need to flash RETUAWS_XT1064_4.4.4_KXB21.85-17_cid9_CFC without fsg.mbn image. (keep stock fsg image)
OK:
I can't upload right now the flashable zip (i'm using 3G right now). The trick is adding these lines to end of /system/build.prop file:
persist.radio.multisim.config=dsds
persist.multisim.config=dsds
And flashing back fsg.mbn from stock firmware.
[]'s
Click to expand...
Click to collapse
Thnx for u r effort buddy :thumbup:
Can u tell me how to downgrade from KXB21.85-23 to 21.85-17.
And is downgrade possible because i tried to downgrade to 85-17 earlier for retaildsdsall.en03.retin. It kept giving me errors while downgrading.
Because i m currently on the KXB21.85-23 build.
As u have told that we need to flash The
RETUAWS_XT1064_4.4.4_KXB21.85-17_cid9_CFC. That means its a downgrade to a US firmware.
Plzz provide the steps
I will be grateful to you..
I can't imagine that the AWS version of the USA firmware would be the only one that this could be used with. I'd think that the global GSM variant would be a better fit for non USA owners, in fact:
"Blur_Version.21.11.17.titan_retuglb.retuglb.en.US"
(glb = global)
Thoughts?
I got no signal issue. Solving before send another zip. Wait some minutes.
Where do i need to edit the build.prop ???
On the RETAILAWS or after flashing Lollipop update zip.
I m very much confused...
Plzzz give step by step instructions..
Related
[guide] install at&t kitkat e980 stock flash + root + recovery - complete wipe !
FOR AT&T LG E980:
Basically, from my experience I put together this guide for anyone who wishes to flash a complete stock AT&T KitKat from .TOT file and the root and add recovery.
All the steps are what I have gathered from around the forums, SO I WILL GIVE CREDIT FOR STEPS THAT ARE OUTLINED BY OTHERS. These people helped by their postings.
FLASHING TOT FILES:
1. The BEST - I think a lot of us can agree - thread for the LG E980 flashing with STOCK firmware is this by HYELTON http://forum.xda-developers.com/showpost.php?p=44983841&postcount=1
STOP OVER THERE AND GIVE THE MAN SOME LOVE AND THANKS !!!!
.TOT files and .Kdz files for all versions can be found at Hyelton's thread above. Also, more details for flashing .TOT vs .Kdz files there. Below is some tips from my experience.
Here is the exact TOT file I used: http://www.mediafire.com/download/djjmck2eost77e3/BIN_LGE980AT-00-V20g-ATT-US-APR-28-2014+0.tot
SOME OF MY TIPS: FROM MY EXPERIENCES
2. The only hitch is getting LGFlash Tools and hacking it. I tried the links on Hyelton’s thread but some are now too new to be hackable. For example, one must find the reg key for the new version of LGTools he links to. Megalock.dll is hit-or-miss. There are other ways for sure but I did not bother further.
3. I found that lower versions of LG Flash Tool (v 1.4.1330R) works just fine.
EDIT: The latest version of LG Flash Tools is here http://www.mediafire.com/download/6g1uyoz2zsiqq1c/LG+Phone+Flash+Stuff.rar
And it contains the DLL to be used during flashing. I STRONGLY SUGGEST USING THIS. You MUST -MUST- TURN OFF INTERNET WHEN USING FLASH TOOLS. This pack contains the full software, and dll files. I have flashed using just this package >10 times at least while testing roms
a.Connect phone and let Windows install drivers. In my case, Windows 8 default were just fine.
b.Put your phone in download mode.
c.Connect it to your computer. In case of windows 8 the windows default drivers work fine.
d.Follow Hyelton’s steps.
EDIT: See posts #32and #33 in this thread. Do not go back to download. But wait for fastboot to install. See post #33 for this. Just wait patiently, the phone will reboot to full normal mode/setup screen, then the LG tools will say pass. BE VERY PATIENT.
ROOTING AND RECOVERY:
ROOTING:
THANKS TO jarari2:
1.This method here works just fine: http://forum.xda-developers.com/showthread.php?t=2699067
Simple bat file method. Turn ON USB Debugging before trying.
2.RECOVERY:
THANKS TO hoangnova AT http://lgviet.com/forum/threads/moi-thu-ve-lg-g-pro-4-4-2-root-recovery-kdz.14841/
** Download and move following file to phone.
** https://docs.google.com/file/d/0B4vSbKccbcIOV1NjMDlqWUdmVm8/edit?pli=1
OR
** https://onedrive.live.com/redir?resid=1F371A0EDB2BC3A6!107
** Run apk. Done.
You should have a full stock KitKat + Rooted + Recovery… Enjoy!!
If this guide helped you, you can buy me a beer/coffee or any such wonderful drink.
chappatti said:
FOR AT&T LG E980:
...
If this guide helped you, you can buy me a beer/coffee or any such wonderful drink.
Click to expand...
Click to collapse
The download on the google drive says it's non-existent.
Nice guide. Thanks!
jdk2 said:
The download on the google drive says it's non-existent.
Edit: Here's the file: http://forum.xda-developers.com/attachment.php?attachmentid=2715141&d=1398757138
Click to expand...
Click to collapse
THANKS ! Fixed !!
Where can I find the .TOT file?
ducktat said:
Where can I find the .TOT file?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=44983841&postcount=1
ducktat said:
Where can I find the .TOT file?
Click to expand...
Click to collapse
I decided to just link directly to the actual TOT file I used.....!
Link in OP.
Roots Perfectly
Upgraded to KK 4.4.2 via OTA and rooted follow the directions contained here and every worked perfectly! Thanks for gathering the information!
MDMTahiti said:
Upgraded to KK 4.4.2 via OTA and rooted follow the directions contained here and every worked perfectly! Thanks for gathering the information!
Click to expand...
Click to collapse
No Problem.
To do the OTA I guess you went back to complete stock ? Yeah, that is a good option too....! Only, it requires one extra flash (going back to stock!)
Just for info, can you please add the steps to your post.
Thanks.
Where to download AT&T kitkat upgrade ?
lchen5 said:
Where to download AT&T kitkat upgrade ?
Click to expand...
Click to collapse
In the OP and in my thread
hyelton said:
In the OP and in my thread
Click to expand...
Click to collapse
Hey, hyelton, thanks for visiting,,!
The steps
chappatti said:
No Problem.
To do the OTA I guess you went back to complete stock ? Yeah, that is a good option too....! Only, it requires one extra flash (going back to stock!)
Just for info, can you please add the steps to your post.
Thanks.
Click to expand...
Click to collapse
I went back to pure stock and no custom recovery, then did the 10p update - I found that the update to 10p would not work with other than stock recovery. I then just used the settings query for OTA update, downloaded and installed - all my programs and data were intact after the update, except apps requiring root would not run correctly. I then followed your steps to root. I still have the stock recovery at this point. KitKat runs great.
MDMTahiti said:
I went back to pure stock and no custom recovery, then did the 10p update - I found that the update to 10p would not work with other than stock recovery. I then just used the settings query for OTA update, downloaded and installed - all my programs and data were intact after the update, except apps requiring root would not run correctly. I then followed your steps to root. I still have the stock recovery at this point. KitKat runs great.
Click to expand...
Click to collapse
So when going back to complete stock the 10p, how did you keep apps, settings if you used odin.? Just interested in your procedure since obviously OTA on stock will retain programs and settings.
It just worked...
chappatti said:
So when going back to complete stock the 10p, how did you keep apps, settings if you used odin.? Just interested in your procedure since obviously OTA on stock will retain programs and settings.
Click to expand...
Click to collapse
Honestly, I don't know. I had been flashing lots of different ROMS and then went back the total day 1 stock. I then updated OTA to 10p a couple of months ago and rooted but did not flash a custom recovery. I then heard that 4.4.2 was available, checked via the about link and downloaded. All the apps and data stayed in place. I then rooted and have yet to flash a custom recovery. I'm sorry I can't give you more detail. But I can tell you that I seem to have better battery life, and I had to pair my phone to my car again. Good luck.
i miss network connection
hi, i follow your steps, and it worked, i have KK now on my e980.
but... sometimes i lost my network connection, and it returns in a minute or two
any ideas?
With the recovery installed from this thread. Can we flash non stock custom roms or just stock roms.
Sent from my HTC One using XDA Premium 4 mobile app
Problems flashing.
Hey! I can't flash the .TOT, the Flash Tool doesn't recognize port COM41, or any other. I go to device administrator, and there's my phone as port 41, but the Flashing Tool doesn't. Any ideas?!
Ink Rampant Wolf said:
Hey! I can't flash the .TOT, the Flash Tool doesn't recognize port COM41, or any other. I go to device administrator, and there's my phone as port 41, but the Flashing Tool doesn't. Any ideas?!
Click to expand...
Click to collapse
Here is the detailed thread for using Lg flash tool. Http://forum.gsmhosting.com/vbb/f17...flashv141-free-no-need-b2b-user-pass-1628819/
I guess you changed yiu computer date and time before using it as mentioned in OP??
Also what Rom are you coming from? Is your bootloader unlocked/lokified?
Can you guys help me out? I already rooted using towelroot. Is it possible to just install the apk for recovery without doing the other steps?
Sent from my Nexus 5 using Tapatalk
Jacob030 said:
Can you guys help me out? I already rooted using towelroot. Is it possible to just install the apk for recovery without doing the other steps?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I have not used towelroot ever. BUT, I do not see why you cannot add a recovery irrespective of root method. I have done this mtself.
Sent from my GT-N8013 using XDA Free mobile app
Hi,
I am just writing these steps to help those who want to downgrade from KK to JB due to any reason. Please use these steps at your own risk.
Some Background:
Recently I updated my Razr M to KK, it was Locked and Unrooted, but with the help of Twelroot and Motopocalypse I rooted and unlocked the BL.
Now somehow I didn't like the KK and wanted to go back to JB 4.1.2 because I was now having unlocked BL and rooted phone so it was easy but need to follow some steps to successfully downgrade to JB. So an unlocked BL and rooted with KK is must.
Prerequisite:
USB drivers for Razr M must be installed before proceeding.
Steps:
1. download the firmware file [Android 4.1.2
Blur_Version.98.30.1.XT907.Verizon.en.US] from http://sbf.droid-developers.org/phone.php?device=8
2. extract the above archive and replace the XML file with the one in attachment.
3. put the phone into fastboot mode and flash the firmware with RSD Lite (attached)
4. reboot and now you have JB 4.1.2
If you want to install root application again and also want to flash custom recovery then please follow the Post#5 [ATTACK] (thanks ATTACK)
Note : for custom recovery you will need the fastboot.exe if you don't have it then install minimal_adb_fastboot_v1.1.3_setup.exe(attached).
Put the phone in fastboot mode, copy the recovery to c:\ and execute the below command :
fastboot flash recovery [Path to recovery image]
If it help you then don't forget to press Thanks button !
Forgive my ignorance but this won't downgrade the kernel will it? I'm hoping it's possible to go from the newest OTA to the stable CM11 but I'm guessing this is new kernel JB. Either way thanks if I can't go to stable CM11 I'll stick with rooted 4.1.2.
Once you have a unlocked bootloader, you do not need to use "root programs". All you need to do is flash a custom recovery via Mfastboot / fastboot then flash SuperSU / Superuser.
In dhacker29's folder there are 2 different recoveries.
"msm8960" is for 4.1.2
"KITKAT" is for 4.4.2
ATTACK said:
Once you have a unlocked bootloader, you do not need to use "root programs". All you need to do is flash a custom recovery via Mfastboot / fastboot then flash SuperSU / Superuser.
In dhacker29's folder there are 2 different recoveries.
"msm8960" is for 4.1.2
"KITKAT" is for 4.4.2
Click to expand...
Click to collapse
thanks ATTACK, can you please point out that which recovery is specially for 4.1.2 because there are a lot of recoveries with msm8960 in Dhacker29's folder.
One more thing if you have flashable Su and busybox zip then please attach it , i will update the OP.
thanks alot.
DHACKER29's FOLDER
- LINK
JELLYBEAN 4.1.2 RECOVERIES
- CWM-6.0.4.6-swipe-moto_msm8960
- TWRP-2.7.0.0-moto_msm8960-hdpi
KITKAT 4.4.2 RECOVERIES
- CWM6049-RAZR-HD_M-KITKAT
- TWRP2710-RAZR_M-KITKAT
SUPERUSER - I'm just going to link to Chainfire's thread, Direct people to download from there.
http://forum.xda-developers.com/showthread.php?t=1538053
BUSYBOX
https://play.google.com/store/apps/details?id=me.timos.busyboxonrails
Could you go back to KK when you've downgraded to JB? Just asking this question early before the CM11 M8 release and the transition occurs.
TheForceUnleashed said:
Could you go back to KK when you've downgraded to JB? Just asking this question early before the CM11 M8 release and the transition occurs.
Click to expand...
Click to collapse
Yes.
ATTACK said:
Yes.
Click to expand...
Click to collapse
So just by flashing the KK firmware in RSD without any changes to the xml? Sorry for the noob questions, I realize how easy this phone can be bricked and I want to avoid it.
TheForceUnleashed said:
So just by flashing the KK firmware in RSD without any changes to the xml? Sorry for the noob questions, I realize how easy this phone can be bricked and I want to avoid it.
Click to expand...
Click to collapse
I see don't why you would need to. It would be just like restoring stock firmware via RSD Lite.
When I try to flash this, I get Failure on 2/20, sbl1
jrk190 said:
When I try to flash this, I get Failure on 2/20, sbl1
Click to expand...
Click to collapse
Did you replace the XML file included in attachment?
Sent from my ME173X using Tapatalk
Sure did. I can't even restore to 4.4.2, I'm stuck on a broken system with no wifi or signal. This sucks...
reply
is this sure it works? i read the feedback so,me user try it failed?
jrk190 said:
Sure did. I can't even restore to 4.4.2, I'm stuck on a broken system with no wifi or signal. This sucks...
Click to expand...
Click to collapse
Can you please post the error that is displayed in RSD Lite ?
The steps are tested by my 2 times, and there shouldn't be any problem. Make sure you have installed the correct drivers.
Please ensure that your bootloader is unlocked and shows BL unlocked status code 3 on BL screen.
I was also able to successfully flash back to JB with House of Moto via fast boot and full data wipe. It would not work with Universal or Keep Data, had to do full data wipe. Just another alternative :good:
xKroniK13x said:
I was also able to successfully flash back to JB with House of Moto via fast boot and full data wipe. It would not work with Universal or Keep Data, had to do full data wipe. Just another alternative :good:
Click to expand...
Click to collapse
I have used my method two time successfully, just follow the steps described in OP.
reply
Thanks You Its a Success Downgrade From 4.4 stock > CM11 > Stock rom 4.1 Thank you so much !!!
For those undergoing the downgrade process in RSD Lite and it takes forever for it to finish and the system ends up without data/signal, you need to RSD Lite flash again in order to regain signal. I believe the flashing was sluggish due to the jump from 4.4.2 to 4.1.2 and the many changes that were reflashed.
Sent from my DROID RAZR M using XDA Free mobile app
We have a wiener!
Thank you so much for the guide. After a lot of trial and error (mostly error), I thought that I had bricked my lovely XT907. I finally restored KitKat by flashing the 4.4.2 firmware with the edited XML file (deleting lines with "Getvar", "var" and "oem" in them), then followed your guide to the letter and found myself with a perfectly functional phone once again. No more sticky fastboot loops or audio-related crashes for me!
Lovely guide - thanks again! :laugh:
---------- Post added at 11:05 PM ---------- Previous post was at 10:59 PM ----------
What functionality does Busybox add? The description on the Play page is woefully sparse.
Thanks!
ATTACK said:
I *DON'T see why you would need to. It would be just like restoring stock firmware via RSD Lite.
Click to expand...
Click to collapse
*EDIT
I don't know why this posted as a new reply
Has anyone got, or able to flash for me, the boot.img from stock N2506EX_23_150108?
Many gratitude points if you could upload for me ?
Thanks.
2nd
babelmonk said:
Has anyone got, or able to flash for me, the boot.img from stock N2506EX_23_150108?
Many gratitude points if you could upload for me
Thanks.
Click to expand...
Click to collapse
Hey I am also looking for this....on a side note are you looking for this because of wifi issues? has anyone found a fix?...pretty bummed wifi is not working on this thing
Could you install the dumps in http://forum.xda-developers.com/oppo-n3/help/looking-dump-boot-img-t2998030 Post #5, then unroot and run the OTAs to get you back up to current?
...
Lum_UK said:
Could you install the dumps in http://forum.xda-developers.com/oppo-n3/help/looking-dump-boot-img-t2998030 Post #5, then unroot and run the OTAs to get you back up to current?
Click to expand...
Click to collapse
I doubt that any stock rom will flash with twrp recovery....in the past with oppo phones (n1, 7a) its always needed stock recovery to flash stock roms...I guess we just play the waiting game until someone can upload the boot image from the updated rom. I'm pretty sure flashing that alone will get wifi back up and running. 07 Or if someone has the stock recovery they could upload....I am unsure if you can just rip it directly out of the rom and flash it....Also on oppo forums they have posted the rom for 5207 I am also unsure if you can flash that to the 5206.
The zip in that thread is images to flash in fastboot?
...
I would think you would have to flash each image individually.... system, boot, recovery ....unless if we start by flashing only the unmodified boot.img to see if it will fix wifi....but i doubt it because i suspect the wrong boot image is what screwed up wifi in the first place...someone please correct me if im wrong
c0dysm1th said:
I would think you would have to flash each image individually.... system, boot, recovery ....unless if we start by flashing only the unmodified boot.img to see if it will fix wifi....but i doubt it because i suspect the wrong boot image is what screwed up wifi in the first place...someone please correct me if im wrong
Click to expand...
Click to collapse
Yes, you're right; the boot image is not compatible with the upgrade; so downgrade to get root. I'm working on trying to upgrade again with the OTA upgrade and then getting the new boot.img and rooting that. More soon I hope!
FYI I tried your images, Lum_UK and found that I couldn't flash boot.img with fastboot, BUT I could dd them from within recovery, so I got myself up and running again.
Yes you'd have to flash all the images by hand one after the other.
edit: Replied before seeing babelmonk's response, please ignore this post.
steps?
babelmonk said:
Yes, you're right; the boot image is not compatible with the upgrade; so downgrade to get root. I'm working on trying to upgrade again with the OTA upgrade and then getting the new boot.img and rooting that. More soon I hope!
FYI I tried your images, Lum_UK and found that I couldn't flash boot.img with fastboot, BUT I could dd them from within recovery, so I got myself up and running again.
Click to expand...
Click to collapse
Can u please list the steps u took I'd like to get back up and running but don't want to screw this phone up any more ....(dd from recovery ) I'm not familiar with this if it is a command
babelmonk said:
Yes, you're right; the boot image is not compatible with the upgrade; so downgrade to get root. I'm working on trying to upgrade again with the OTA upgrade and then getting the new boot.img and rooting that. More soon I hope!
FYI I tried your images, Lum_UK and found that I couldn't flash boot.img with fastboot, BUT I could dd them from within recovery, so I got myself up and running again.
Click to expand...
Click to collapse
I can't get the OTA to work even after downgrading, but I do have a working system running 141228 with that hacked kernel, root and non-broken wireless.
Anyone want a nandroid of it? It's a slight upgrade at least
please
Lum_UK said:
I can't get the OTA to work even after downgrading, but I do have a working system running 141228 with that hacked kernel, root and non-broken wireless.
Anyone want a nandroid of it? It's a slight upgrade at least
Click to expand...
Click to collapse
please hook it up with that nandroid that i can flash in twrp
c0dysm1th said:
please hook it up with that nandroid that i can flash in twrp
Click to expand...
Click to collapse
Here you go, sorry it's taken so long
http://lum.uk/n3/files/N5206EX_23_141228_root_nocd.7z
Extract it into the TWRP backups folder and then restore like any other nandroid.
THANK YOU
Lum_UK said:
Here you go, sorry it's taken so long
http://lum.uk/n3/files/N5206EX_23_141228_root_nocd.7z
Extract it into the TWRP backups folder and then restore like any other nandroid.
Click to expand...
Click to collapse
Thank you how can i buy you a beer paypal?
c0dysm1th said:
Thank you how can i buy you a beer paypal?
Click to expand...
Click to collapse
Don't worry about it
Seems there's only about 4 or 5 people actively working on this phone here, so I'm sure we'll all end up helping each other at some point.
Lum_UK said:
Here you go, sorry it's taken so long
http://lum.uk/n3/files/N5206EX_23_141228_root_nocd.7z
Extract it into the TWRP backups folder and then restore like any other nandroid.
Click to expand...
Click to collapse
Thanks for that, though I haven't tried it yet. Can I ask what it changes? Is it worth the upgrade? My original firmware +root seems to work pretty well already so I may well leave it alone until L or CM comes out.
babelmonk said:
Thanks for that, though I haven't tried it yet. Can I ask what it changes? Is it worth the upgrade? My original firmware +root seems to work pretty well already so I may well leave it alone until L or CM comes out.
Click to expand...
Click to collapse
I have no idea what it changes as it's the firmware my International N5706 was shipped with when it was released last week. It may be different to the US model (though I believe the only difference between the two is the baseband) and is definitely different to the N5707 for Chinese users.
Dude, thanks!!! You saved my life!
I got wifi back AND root!
sivxo said:
I got wifi back AND root!
Click to expand...
Click to collapse
Hi ! when the zip file is downloaded, what is steps to install it please ?
thanks
marakud said:
Hi ! when the zip file is downloaded, what is steps to install it please ?
thanks
Click to expand...
Click to collapse
Sorry. Missed this. Did you manage?
Oppo neo 7 a33f custom recovery plzzz send me
Could somebody provide full untouched fastboot firmware with build number NPPS25.137-93-14 for DualSIM Moto G5 (XT1676) with reteu software channel and 3GB RAM/16GB ROM, please? Thanks in advance.
https://forum.xda-developers.com/g5/development/official-stock-moto-g5-cedric-firmware-t3733897
I have been looking for it during several weeks too, no success until now. I found 137-92-14, which is built for other software channels. It works well in my XT1685 (Dual sim 3GB/32GB reteu).
Still looking for 137-93-14... Regards.
Doesn't XT1685 equal G5 Plus?
Andrej_SK said:
Doesn't XT1685 equal G5 Plus?
Click to expand...
Click to collapse
Yes.
Enviado desde mi Moto G (5) Plus mediante Tapatalk
Andrej_SK said:
Could somebody provide full untouched fastboot firmware with build number NPPS25.137-93-14 for DualSIM Moto G5 (XT1676) with reteu software channel and 3GB RAM/16GB ROM, please? Thanks in advance.
Click to expand...
Click to collapse
How can I provide you with fastboot firmware as I am having same build version with untouched fastboot firmware.but I am having xt1677 with same specs.
I'm also looking for NPPS25.137-93-14 (or NPPS25.137-93-12)... I only need the stock recovery.img file of either of the two...
Ok I will update recovery for you. Which varient it is if amzin one link will be uploaded at evening. Just let me know. Waiting for reply?
Aaric leo's el drigo said:
Ok I will update recovery for you. Which varient it is if amzin one link will be uploaded at evening. Just let me know. Waiting for reply?
Click to expand...
Click to collapse
Mine is retail. Either *-12 or * -14 recovery.img will be ok.
Thanks.
Sent from my Moto G5 using XDA Labs
Ok I will upload it. As fast as possible
---------- Post added at 04:38 AM ---------- Previous post was at 03:42 AM ----------
Because I can't fine firmware online to download, or I don't have retail varient so I can't help you. But if you have laptop, pc. I can help let you know how you can download firmware. Let me know if you need guide as fast as possible.
leohussey said:
I'm also looking for NPPS25.137-93-14 (or NPPS25.137-93-12)... I only need the stock recovery.img file of either of the two...
Click to expand...
Click to collapse
You can flash older recovery without bricking the phone. However, don't do that if you are running CustomROM. In my case, when I wanted to revert to fully updated stock, I flashed NPPS25.137-93-8 firmware without gpt, bootloader (that's what would brick the phone if flashed) and erase modem commands, updated it to NPPS25.137-93-12, then to NPPS25.137-93-14 using stock recovery and these files https://drive.google.com/drive/folders/1BkpfHvgQ477NViLYvzgv88Fgq3SSt5Py. No issues at all and my phone (XT1676, 3/16, DualSIM, reteu) is still working fine.
In the attachment, I'll put recovery.zip (with recovery.img inside of it) of the NPPS25.137-93-8. Use at your own risk, if you are interested.
Andrej_SK said:
You can flash older recovery without bricking the phone. However, don't do that if you are running CustomROM. In my case, when I wanted to revert to fully updated stock, I flashed NPPS25.137-93-8 firmware without gpt, bootloader (that's what would brick the phone if flashed) and erase modem commands, updated it to NPPS25.137-93-12, then to NPPS25.137-93-14 using stock recovery and these files https://drive.google.com/drive/folders/1BkpfHvgQ477NViLYvzgv88Fgq3SSt5Py. No issues at all and my phone (XT1676, 3/16, DualSIM, reteu) is still working fine.
In the attachment, I'll put recovery.zip (with recovery.img inside of it) of the NPPS25.137-93-8. Use at your own risk, if you are interested.
Click to expand...
Click to collapse
Thanks.
But thing is: I'm currently on NPPS25.137-93-12 with TWRP and Magisk. As a proof of concept I want to go to *-14 via OTA to see if it is possible... And if so: to make the oreo jump when available for my channel (XT1671, 2 sim, retla). I want to avoid losing all my data or any long task that would keep me offline for a long time... Daily driver both work and personal...
Uninstalling Magisk reverts boot.img to stock.... but I still need the stock recovery.img to be in 100% stock state (but unlocked). That's the theory.
Tried yesterday using other recovery.img versions, but failed: /cache/recovery/last_log shows the Blur* OTA file updater-script explicitly checks recovery version to be either source or destination versions... So *-12 or *-14.
After that, updater-script checks boot, system and oem. Those are (will be, supposedly) stock since Magisk only patches boot.img and I'll uninstall it .... should work...
The longer path of flashing other version and do the OTAs is also possible... But I'd have to be on vacation or something...
Thanks again.
Sent from my Moto G5 using XDA Labs
leohussey said:
Thanks.
But thing is: I'm currently on NPPS25.137-93-12 with TWRP and Magisk. As a proof of concept I want to go to *-14 via OTA to see if it is possible... And if so: to make the oreo jump when available for my channel (XT1671, 2 sim, retla). I want to avoid losing all my data or any long task that would keep me offline for a long time... Daily driver both work and personal...
Uninstalling Magisk reverts boot.img to stock.... but I still need the stock recovery.img to be in 100% stock state (but unlocked). That's the theory.
Tried yesterday using other recovery.img versions, but failed: /cache/recovery/last_log shows the Blur* OTA file updater-script explicitly checks recovery version to be either source or destination versions... So *-12 or *-14.
After that, updater-script checks boot, system and oem. Those are (will be, supposedly) stock since Magisk only patches boot.img and I'll uninstall it .... should work...
The longer path of flashing other version and do the OTAs is also possible... But I'd have to be on vacation or something...
Thanks again.
Sent from my Moto G5 using XDA Labs
Click to expand...
Click to collapse
Try one more time with file in the attachment of this reply. Although you will get "Image signed with key bad key" (because it's simply extracted from NPPS25.137-93-14), it should flash just fine. In my case, I've tried to flash it with fully updated phone to NPPS25.137-93-14, no issues at all. However, you should be more careful if you are running .12 firmware - this is stock and newer recovery (recovery of .14 firmware). .
Okay, so there are already 2 files in the attachment, first one contains recovery.img of .12 firmware, second one of the .14 firmware. You can recognize them by name of the file. With each of them, you will still get "Image signed with key bad key" message when flashing, but they flash just fine and everything seems to be working flawlessly on my phone with coresponding firmware version (means .12 recovery for .12 firmware, .14 recovery for .14 firmware). Once again, you are doing it at your own risk if you decide to.
Andrej_SK said:
Try one more time with file in the attachment of this reply. Although you will get "Image signed with key bad key" (because it's simply extracted from NPPS25.137-93-14), it should flash just fine. In my case, I've tried to flash it with fully updated phone to NPPS25.137-93-14, no issues at all. However, you should be more careful if you are running .12 firmware - this is stock and newer recovery (recovery of .14 firmware). Once again, you are doing it at your own risk.
Click to expand...
Click to collapse
Thanks. I'll test tonight.
"Bad key" is no problem... Got it twice already by testing with other versions I was able to get.
As for it being from *-14, it should work if I believe the updater script checking for either *-12 recovery (source) or *-14 recovery (target)... We'll see.
Sent from my Moto G5 using XDA Labs
---------- Post added at 06:31 PM ---------- Previous post was at 06:28 PM ----------
Andrej_SK said:
Try one more time with file in the attachment of this reply. Although you will get "Image signed with key bad key" (because it's simply extracted from NPPS25.137-93-14), it should flash just fine. In my case, I've tried to flash it with fully updated phone to NPPS25.137-93-14, no issues at all. However, you should be more careful if you are running .12 firmware - this is stock and newer recovery (recovery of .14 firmware). .
Okay, so there are already 2 files in the attachment, first one contains recovery.img of .12 firmware, second one of the .14 firmware. You can recognize them by name of the file. With each of them, you will still get "Image signed with key bad key" message when flashing, but they flash just fine and everything seems to be working flawlessly on my phone with coresponding firmware version (means .12 recovery for .12 firmware, .14 recovery for .14 firmware). Once again, you are doing it at your own risk if you decide to.
Click to expand...
Click to collapse
Hm... By the time I quoted to answer, you updated. Cool.
Then I'll test directly on 12. Thanks.
Another question: are you extracting them from your own phone? If so, how? Untill now I only found possible by rooting, but rooting means changing recovery in first place... So... Hen and egg...
Sent from my Moto G5 using XDA Labs
leohussey said:
Another question: are you extracting them from your own phone? If so, how? Untill now I only found possible by rooting, but rooting means changing recovery in first place... So... Hen and egg...
Sent from my Moto G5 using XDA Labs
Click to expand...
Click to collapse
Yes, I rooted my phone by Magisk and used app called Flashify to backup recovery. However, to root, I didn't install TWRP permanently by "fastboot flash recovery twrp.img" command, I just booted into it by "fastboot boot twrp.img", so I was able to root my phone and keep stock recovery installed.
Andrej_SK said:
Yes, I rooted my phone by Magisk and used app called Flashify to backup recovery. However, to root, I didn't install TWRP permanently by "fastboot flash recovery twrp.img" command, I just booted into it by "fastboot boot twrp.img", so I was able to root my phone and keep stock recovery installed.
Click to expand...
Click to collapse
Thanks. I had been reading about it and some posts were misleading saying it was no longer possible and others said it was. Had not gotten down to test it yet. So now I know it works, I'll do it. Thanks again.
Sent from my Moto G5 using XDA Labs
Update: tested.
good: Recovery image -12 worked without issue and updater-script check passed.
bad: it failed while validating boot.img.
Apparently, Magisk uninstall did not restore the boot partition to stock. I also had a TWRP backup from when I had just unlocked. Restored boot. No luck. Maybe I took the backup *after* rooting.
well... I guess I will have to wait until I have some free time to do the long way: full flash
EDIT: @Andrej_SK: would you by any chance have the boot.img of *-12 too?
thanks!!
I am reading this tread form more then 2 days. I already told you I can help but it seems no one want know what I am saying. But it's now seem a serious tread so I will tell in anyway if someone is interested or not.
Guide to repair Moto Lenovo models.
Note: pc, laptop required.
1. Download latest driver for moto device.
2. Download Lenovo Moto smart assistant.
3. Enable usb debugging in developer options.
4. Click on Flash button on top of your tab bar.
5. Click on rescue.
6. Get into bootloader , fastboot.
7. Download your current varient latest firmware.
And all done.
Now you have your firmware with latest security patch.
You can relock bootloader and whatever you like.
Have fun enjoy.
Thanks a lot. This tool won't work if you have lost your IMEI, but it allows you to download the latest firmware (in my case 137-93-14). Using this full stock firmware I have been able to recover the IMEI following the steps explained in other topic in this forum.
Regards.
leohussey said:
EDIT: @Andrej_SK: would you by any chance have the boot.img of *-12 too?
Click to expand...
Click to collapse
I might give it a try, if you give me some time.
Hey guys, more and more Roms are coming out for our beloved OnePlus 9 pro. I had a 6 and 7tp before and there were stock oos Roms, which you could easily flash via Fastboot and have OOS back.
It's just more convenient to simply have one file instead of flashing all images and so on
It'll be so great if any developer could try to create one, since it shouldn't be so difficult (at least that's what I guess haha)
I created one (11.2.7.7.BA), it should work, but need testers. Ofc, Use it on your own Risk, but we have MSM Tool
Test_EU_11.2.7.7.zip
drive.google.com
Extract the Zip and Run "Flasher"
Sconny said:
I created one (11.2.7.7.BA), it should work, but need testers. Ofc, Use it on your own Risk, but we have MSM Tool
Test_EU_11.2.7.7.zip
drive.google.com
Extract the Zip and Run "Flasher"
Click to expand...
Click to collapse
thanks for this bro much appreciated
fastboot -w not correct work
d:\Software_Tools\Multimedia\Handy-Taplet\Handy\Backup\Download\Rom\Payload Dumper 64 bit\payload_output>fastboot -w
Erasing 'userdata' OKAY [ 1.960s]
CreateProcess failed: Das System kann die angegebene Datei nicht finden. (2)
fastboot: error: Cannot generate image for userdata
I owe you a beer Sconny, you brought me back from the brink! I didn't exactly use all of your files, so I'm not sure if I count as a tester, but I was able to use your fastboot commands from Flasher.bat and turn that into a shell script. I ran it not really knowing it was going to work, so I ended up not wiping beforehand but it looks like it turned out fine. Oh and I didn't use your zip, used my own and dumped the payload myself. Thanks again Sconny!
Sconny said:
I created one (11.2.7.7.BA), it should work, but need testers. Ofc, Use it on your own Risk, but we have MSM Tool
Test_EU_11.2.7.7.zip
drive.google.com
Extract the Zip and Run "Flasher"
Click to expand...
Click to collapse
Tested and it worked for me as well other than shows the same userdata wipe error as mentioned. Curious to ask if you could make a flashable zip to include just the latest firmware?
erad1 said:
Tested and it worked for me as well other than shows the same userdata wipe error as mentioned. Curious to ask if you could make a flashable zip to include just the latest firmware?
Click to expand...
Click to collapse
Maybe I should implement another command or manual wiping should work. Isn't that the latest FW?
Sconny said:
Maybe I should implement another command or manual wiping should work. Isn't that the latest FW?
Click to expand...
Click to collapse
yep that is the latest
Sconny said:
Maybe I should implement another command or manual wiping should work. Isn't that the latest FW?
Click to expand...
Click to collapse
Yes but for flashing custom Roms you only need need some of the images flashed to the other slot prior to flashing the custom ROM zip. The system IMG and vendor IMG and some others are not needed. Comes in handy when moving from one custom ROM to another.
https://t.me/havoc_oneplus8/23372
This is an example of it for OnePlus 8...
erad1 said:
Yes but for flashing custom Roms you only need need some of the images flashed to the other slot prior to flashing the custom ROM zip. The system IMG and vendor IMG and some others are not needed. Comes in handy when moving from one custom ROM to another.
Click to expand...
Click to collapse
erad1 said:
https://t.me/havoc_oneplus8/23372
This is an example of it for OnePlus 8...
Click to expand...
Click to collapse
Never mind though as this was inaccurate on my part, vendor img is needed...my bad. This method just lets you flash to latest fw after you're already on a custom rom. So to say if a newer fw came out after you could update to it.
I will take a look on it when I've got more time, sorry guys. I need to test it on myself in order to provide this variant of restoring our devices, but I'm working much as hell atm and family stuff etc. Is more important. But I promise I will try to provide a fully functional package for all versions. System, ODM and Vendor is still buggy, but I have some ideas how to fix it
do u think this could work for AA?
Libra420T said:
do u think this could work for AA?
Click to expand...
Click to collapse
There should be the same bug with wiping. But I have an idea, I gonna download AA and will upload here. 1 hour needed
Uploading right now.
Here is the AA Version. Wipe Manually, i have to figure out why its not working, for me it does (Maybe cable, usb port?)
I am not a Developer, i'm just doing this for fun and testing when i have time. As always, use at your own risk.
I disabled Verity for the 3 Partitions, maybe that will help. If you guys have some Ideas, please let me know.
Once it is working flawlessly, i will create a thread and update the "tool" for BA/AA/DA Devices.
Test2_AA_11.2.7.7.zip
drive.google.com
Gonna update to 11.2.8.8 soon, all versions. Waiting for all zips to download
Sconny said:
Gonna update to 11.2.8.8 soon, all versions. Waiting for all zips to download
Click to expand...
Click to collapse
I'm rooted on T-Mobile stock 11.2.5.5 would I be able to flash 11.2.8.8 via fastboot? Or would I need to convert to EU first?
Pain-N-Panic said:
I'm rooted on T-Mobile stock 11.2.5.5 would I be able to flash 11.2.8.8 via fastboot? Or would I need to convert to EU first?
Click to expand...
Click to collapse
Just follow the tutorial in this forum