Got sloppy with a brief return to stock to reprovision my sim card. When going back to a custom rom I managed to run the copy script from the wrong slot. My problem lies with getting a working blankflash. It seems those customer hating folk over at Lenovo keep revoking firehose files. I'm looking for ideas on solutions. Can't get to telegram because my phone is dead. I'm very good with computing but haven't learned how to build a singleimage file yet and how flexible the firehose is for using different models, mine is xt1962-1 (us retail, amazon, in case I'm chasing after the wrong device). Any pointers or links greatly appreciated.
Related
Hi all.
I've asked this question in numerous threads so, to be fair to all the others whose questions I'm getting in the way of, I thought I'd post it here and wait with baited breath for a potential solution.
I very recently bought an XT1684 (3GB/32GB) UK G5 Plus. I installed all the official OTAs and got myself up to firmware version NPNS25.137-33-11. All was well, amazing battery life, but needed root for some apps. The steps I followed are roughly as follows:
1. Unlocked bootloader: I did this the usual way, got my code, chucked it into fastboot etc voila, job done.
2. BOOTED Twrp: I did this so I could attempt to back everything up without modifying, for purpose of returning to stock. It didn't work, I could not back anything up nor could I install magisk or a custom kernel. My Twrp would not read the internal storage and said something about formatting data. I ended up formatting data, which actually formatted the whole damn thing, losing my stock ROM completely.
3. FLASHED Twrp: By this point I had to, as I had limited access to the internet outside of my phone so put a lineage ROM on my phone and some gapps and flashed it.
4. Installed magisk 15.3
5. Installed Alize kernel: I did this because I was looking for improved battery life over the lineageos kernel. It hasn't been better.
So that's where I am. I have two main reasons I need to return to stock:
1. The battery life was better on my stock firmware.
2. Whenever I use lineage, I find my signal not to be as strong, and it seems to randomly lose all signal for a few seconds several times an hour, usually affecting my data more than voice calls. This is absolutely not something that happened on stock. I dunno if it's related to baseband or something, but it happens and I don't like it.
My main issue is I have seen several retUS versions of the firmware above, and lots about many other XT16xx models but nothing about my XT1684 and no fastboot images for retGB. I'm comfortable flashing pretty much anything via Twrp as I have a full backup of all partitions including OEM, system image etc but these were taken after installing lineage. I'm just totally not comfortable fastboot flashing anything except the exact correct firmware, as I've had this phone literally a week.
If anyone can help me locate the right firmware, or advise me how I could possibly return totally to stock, that would be amazing. I can provide any logs or other information required, but may need walking through more obscure commands as I am only technically proficient enough to do a basic fastboot flash, Twrp, etc.
Many thanks for reading and my apologies to all of those whose threads I've muscled in on up to this point.
Filmware is here https://firmware.center/firmware/Motorola/Moto G5 Plus/Stock/
And there is a tool that automates flashing in the development section here..
https://forum.xda-developers.com/g5-plus/development/toolkit-moto-g5-plus-toolkit-root-t3605203
Firmware - https://firmware.center/firmware/Motorola/Moto G5 Plus/Stock/
How to flash - https://forum.xda-developers.com/g5-plus/how-to/solution-to-flash-stock-romfactory-t3691396
?hope it helps.
Thing is, there's no xt1684 version or retgb version. I fear it could be the wrong one, can't afford to replace phone so can't risk hard bricking it.
Could someone confirm that these are safe to flash for me? Thanks for the replies, though.
Your filmware is there yes? Having said that mine is a xt1685 the same filmware number as yours but mine is euret dual SIM. Sold by Amazon UK
My confusion is that I thought they were for US models.
Well US version has no NFC but had a compass.
Has yours?
Mine has NFC and no compass lol!
darkglobe87 said:
Mine has NFC and no compass lol!
Click to expand...
Click to collapse
Seems to be typical for EU G5+ devices, NFC but no compass.
The retail firmwares don't appear to have region restrictions, hence no labelling for retEU/retGB/retUS etc. However, as you may have noticed, flashing the incorrect build for your region causes all sorts of headaches, including loss of SIM network.
That being said, you know what firmware you need (NPNS25.137-33-11) and that particular firmware was only released for EU/UK devices to the best of my knowledge. India/Brazil, US and other territories had different firmware builds released.
So, you should be okay with flashing that particular firmware - but please verify you have the correct firmware downloaded and the correct flashing instructions, and take your time in flashing.
Also, if you choose to re-lock your bootloader, re-locking your bootloader will unfortunately not restore your warranty with Motorola (which is 2 years now for EU/UK users at least). However, UK consumer laws may cover you in the eventuality of hardware repairs, just be careful. Also, re-locking will erase your device and requires firmware of the same build or newer than what is currently on your device.
Good luck whatever you decide.
I have the UK version and have gone back to stock a few times, I used this thread, and the linked firmware is the same as UK one. The guide is for bootloader locking, but ignore that part if you only wish to return to stock.
https://forum.xda-developers.com/g5-plus/how-to/how-to-lock-bootloader-potter-version-t3694952
I have a huge query. I have a ZTE Maven 3 which I bought second-hand, which luckily came blocked from the signal, rather, that I could only have the At & t sim, try to unlock it anyway but fail, I made a guide that is here to root and in the end, when I did it now, the wifi did not work for me, then I tried to flash it, with a firmware that I saw here, but my sister interrupted it when it was in process, and I tried to unravel it, without any success, now, I bought a new phone of the same model but now unlocked, which I want to copy the firmware, to be able to repair the other and recover the money spent having to buy another. Has anyone been able to do it? I know what could be done on other models with the snap dragon processor, putting it in Qualcomm HSDLoader 9006 mode but I don't know how to do it.
I'll keep it point form:
I have a Chinese 6T, and any time I try to use MSM with an OOS ops file, I get "Device not match image".
I got my drivers from Windows Update, they work
I even tried SMT mode
I think the files here would work, but they're gone now
Background:
I cannot access fastboot/adb --only the unlocked bootloader warning screen, then Qualcomm dump screen
I understand the process of turning off the phone, then plugging it in with vol+/- pressed --I am able to get into EDL but that's it
I got my OnePlus 6T a week ago, brand 'new' (never opened), and only used it for a day before fudging it up --this sucks!
I've tried all of the 6T OOS MSM Download Tool versions available on this forum, site-wide. The only thing I haven't been able to find and try is the HOS 6T unencrypted ops file with a corresponding MSM Tool.
Would really really appreciate those files, if anyone has them tucked away.
Sincerest thanks in advance to anyone who can help.
In all my research, and broken links, etc --I really think that OnePlus is forced to keep Hydrogen OS a (state) secret. We can all easily acquire the Oxygen OS decrypted, but no one has the decrypted Hydrogen OS MSM Download Tool anymore, all links lead to 404 pages.
If anyone has a copy of Hydrogen OS but don't want to publicly share it, drop me a DM and we can talk elsewhere. I'm buying another OnePlus 6T for now and putting this one in a drawer.
I'm not in a rush to find a solution, I know these things can take time. Even if you read this in 2022 or hell, even 2023, please assume I still need the HydrogenOS MSM Download Tool for OnePlus 6T. I'd really like to fix my phone one day, even if it isn't as quickly as I'd like.
Thanks in advance to whoever helps me out, one day!
Hello everyone. it's been a week that I work on this problem but I can't solve it myself despite having made numerous attempts. the situation is this: installing lineage os when the system restarted the 6t got stuck in the bootlader. I installed qualcom drivers from here
https://androidfilehost.com/?fid=11410963190603879743
and downloaded msm https://androidfilehost.com/?fid=17248734326145733776
I disabled windows secure boot and installed optional qualcomm drivers on windows... the 6t is correctly recognized as Qualcomm 9008 in the device manager in port 9 but I also tried in the 7 and it is always correct.
I tried other divers (after removing the previous ones) and other versions of msm but I always give the same error : param preload... device not match images.
I have read many discussions and tried many things but I can not solve. someone is willing to help me. Thanks guys.
I also tried uninstalling the drivers and reinstalling these:
QUD.WIN.1.1 Installer-10037.3 Setup.zip | by Dark Nightmare for OnePlus 6T
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
using this version of msm:
6T_MsmDownloadTool_v4.0.58_OOS_v9.0.12.rar | Tool by iaTa for OnePlus 6T
[TOOL] 6T MsmDownloadTool v4.0.58 (OOS v9.0.12) https://forum.xda-developers.com/oneplus-6t/how-to/tool-6t-msmdownloadtool-v4-0-oos-9-0-5-t3867448
androidfilehost.com
the problem is not solved but changed to: (recording dawnload time in red) images do no match with teh phone!
i can't figure out if it's a msm or driver version problem or maybe something else ...
I don't know what the exact problem. If you have installed magisk or modify something to your phone, sometime msm will fail to recognized or flash..
rom
But if your phone can boot into fastboot mode, try to flash fastboot ROM it might help
Fastboot rom.
[ROM][STOCK][FASTBOOT][OP6T] Stock Fastboot ROMs for OnePlus 6T
Things are changing with the advent of project treble and seamless updates. OnePlus will no longer release ROMs flashable via recovery (either stock or twrp) because is no more needed. The updates will be done on the slot not used for example if...
forum.xda-developers.com
hello, thanks for the answer. yes I had installed magisk and yes I can enter the fastboot but from there only to turn it off. now I will read the discussion that linked me. Thank you
sun-k said:
hello, thanks for the answer. yes I had installed magisk and yes I can enter the fastboot but from there only to turn it off. now I will read the discussion that linked me. Thank you
Click to expand...
Click to collapse
if you get a warning in MSM tool: 'images do not match the phone', you are flashing the wrong image. That could happen to a branded phone. So, if you have a T-Mobile branded phone, either convert it to Global first (that tool has 'device check' disabled), or use T-Mobile MSM tool.
Your other option is to contact OnePlus support and they can help you remotely. I got into a similar bind with my 6t a year and ½ ago and nothing I was attempting worked. It was very frustrating. Ultimately I contacted OnePlus and they got me back up and running in no time. I was a little upset that I had to resort to relying on the manufacturer but also relieved to have a working device again and also thankful that it was an option, even if I would've preferred to have fixed it myself. Good luck.
PS - something to be aware of, I'm not 100% sure that it was a result of OnePlus' involvement/remotely flashing the device but somehow I ended up with a new/different IMEI. This created a world of difficulty with my cellular carrier (VZW) - I had finagled a OnePlus 8 out of them by citing manufacturers defect (I had coverage through VZW despite purchasing the phone directly from OnePlus) but they said the OnePlus 6t they received had a different IMEI than what they expected to receive, which makes absolutely no sense and this is the only possible explanation I could come up with. It ultimately saved me from having to pay for retail for the OnePlus 8 but not without a lot of headaches in between. Oh and lemme just say that having a VZW OnePlus with a locker bootloader sucks, I can't wait to get away from this thing and back to something I can root (I only pulled this maneuver in order to buy myself some time as I wasn't thrilled with the 1+9)
Could someone please point me in the direction of a custom ROM that will (or even might) work on Samsung j7 sky pro SM-272VL(GP)
Before anyone suggests, I have already read all of the information out there on rooting, ODIN, TWRP, etc for this phone. It sounds like several have tried, but no one has actually been able to gain root, although there may be hope for that due to security flaw https://www.exploit-db.com/exploits/45379 mentioned in this post #21
SM-S727VL Analysis, Partition Table, and Factory
-- UPDATE #1 (11/05/18) added So I've got myself a Tracfone Variant of the Samsung J7, The "Galaxy J7 Sky Pro" [SM-S727VL] CDMA. As far as I can tell, this variant is sold on both the Tracfone and StraightTalk carriers, and it seems to just run...
forum.xda-developers.com
I have also read all of the only other thread out there on this device on the subject of rooting, or anything really:
SM-S727VL Root and Recovery
I cannot for the life of me get this phone rooted or a recovery installed. Odin always fails and ADB doesn't recognize the device. Does anyone have any info on rooting this device? I really just want to at least be able to update this thing to...
forum.xda-developers.com
However not much was accomplished in these peoples attempts other than a bricked phone or 2, and most of the participants seem to have moved onto other devices.
I however do not have any issue with needing to root as I own the device, and as it is I can boot into a recovery ODIN mode that says that FRP Lock is off, and the screen is showing a "download in progress" background to a console, waiting for me to send the updated firmware/custom ROM/whatever from the USB cable. See attached image.
I run Linux and have for the last 20 years have used too many Distros to count, but can work with most any, but prefer debian based although I have much respect for Gentoo, and their compile everything package management, and have spent considerable time on it as well. l have unlocked and installed custom ROM's of of many types on many phones, and am working with the combined experience of myself, and my friend who has done the same, except even more on more different devices than myself. But neither of us has worked on such an obscure model as this one with so little information posted publicly on the internet for anyone to find as this one. But if there is a way to do it, I'm sure between the two of us, we can and will make it happen.
Can anyone be of any help? I would really like to get something out of the phone for the $100 that it cost me. Things I would like to run would be Kali Nethunter, and/or Andrax or Cyanogenmod/LineageOS or really any other AOSP that is not google f***ed. Basically any custom ROM (whichever, whatever type and version has the best chance of working on this phone, since there are none posted publicly that are specifically made for this device that we can find for this obscure, excessively undocumented model of phone. Just getting TWRP will be a good start, and I'm pretty sure we can handle that. However in the mentioned posts even the the TWRP file that is made for this phone, people are having troubles installing in their experiences, and bricking their phones in the process, so I definitelly would prefer not to have a repeat of what happened there.
Thank you in advanced for any and all information, hints, tips, tricks, etc. I would like to not brick this phone as the only other person who attempted to do anything with this phone unfortunately had done.