Related
I tried to flash my p6 to B512 ROM, and I had changed my recovery, duno what is my recovery version now, but just cant install any new ROM.
Actually this is the first time i hit this problem and I hv really no idea how to proceed, i flashed successfully many times previously using twrp cwm or stock recovery, just dont know what happen this time, I know how to flash a new ROM from recovery anyway, just put dload folder with UPDATE.app inside in FAT32 sdcard, but it just not success during flashing, any expert can guide me, i really appreciate your help, I attached with a photo below, i stuck at here when reboot with USB plug in, and for your information my adb cant read my device
sasadeaunty said:
I tried to flash my p6 to B512 ROM, and I had changed my recovery, duno what is my recovery version now, but just cant install any new ROM.
Actually this is the first time i hit this problem and I hv really no idea how to proceed, i flashed successfully many times previously using twrp cwm or stock recovery, just dont know what happen this time, I know how to flash a new ROM from recovery anyway, just put dload folder with UPDATE.app inside in FAT32 sdcard, but it just not success during flashing, any expert can guide me, i really appreciate your help, I attached with a photo below, i stuck at here when reboot with USB plug in, and for your information my adb cant read my device
Click to expand...
Click to collapse
So first unplug your phone from your pc otherwise it won't work.
Than I had the same as you in the picture with the recovery 'stuck' but for it simply worked if I reboot straight again into recovery via the three buttons.
Hope I could help
hi
taaeem said:
So first unplug your phone from your pc otherwise it won't work.
Than I had the same as you in the picture with the recovery 'stuck' but for it simply worked if I reboot straight again into recovery via the three buttons.
Hope I could help
Click to expand...
Click to collapse
Hi, if i reboot without plug-in the usb, it will also fail like (attached photo124)
hm..tried to use a jb rom (b125/132)..maybe you flashed a jb recovery
blueIBI said:
hm..tried to use a jb rom (b125/132)..maybe you flashed a jb recovery
Click to expand...
Click to collapse
Different stock recovery only can install certain ROM? I tried B125 already cannot. Any other recommend ROM for me to try? I rmb I flashed a quite latest stock recovery
then try the b510 or the b634..
jb recovery can only install jb rom..so do kk recovery only install kk rom as i know..
if nothing brings success try the unicom rom..
blueIBI said:
then try the b510 or the b634..
jb recovery can only install jb rom..so do kk recovery only install kk rom as i know..
if nothing brings success try the unicom rom..
Click to expand...
Click to collapse
hi, my stock recovery is 4.4.2, and I just downloaded B634 ROM and tried to flash it, but the flashing fail......
stuck at this
ro.build.version.release = 4.4.2
ro.product.name = UEDGE
Current build version is not 4.2, dont need move.
USB Update Enter...
HUAWEI SDCARD&USB UPDATE AGENT VERSION 2.0
This phone is secureboot phone.
This phone is UNLOCK state.
sasadeaunty said:
hi, my stock recovery is 4.4.2, and I just downloaded B634 ROM and tried to flash it, but the flashing fail......
stuck at this
ro.build.version.release = 4.4.2
ro.product.name = UEDGE
Current build version is not 4.2, dont need move.
USB Update Enter...
HUAWEI SDCARD&USB UPDATE AGENT VERSION 2.0
This phone is secureboot phone.
This phone is UNLOCK state.
Click to expand...
Click to collapse
You still have your usb cable plugged in. It will NOT work like that. @taaeem has already mentioned that.
What was the previous firmware that you had installed?
If it was a Chinese firmware, you need to try flashing this file first: https://mega.co.nz/#!8kcVADpB!JKeDlX4WQhmAP3mclNTfIzIjVllw5sMhnrj-3KSpSc4
maybe the sdcard causes this error too..had this with a 16gb fuji card..with a 8gb noname it worked..
and unplug your phone before flashing..as mentioned..
miz_pimp said:
You still have your usb cable plugged in. It will NOT work like that. @taaeem has already mentioned that.
What was the previous firmware that you had installed?
hi miz_pimp, if i do not plug in the usb cable, it will directly go into fail as showed in the picture124 i attached below, I do not rmb what firmware i installed previously, but I did a full wipe, I do not think thr is still firmware inside beside stock recovery.
Click to expand...
Click to collapse
blueIBI said:
maybe the sdcard causes this error too..had this with a 16gb fuji card..with a 8gb noname it worked..
and unplug your phone before flashing..as mentioned..
Click to expand...
Click to collapse
I tried with different sdcard without usb plugged in, still giving me fail
very strange..
maybe you do a all again..
starting with flashing a stock boot.img and recovery.img (from the b512 rom..you can extract them by the update extractor from here..just search)..
then try to flash the b512 rom by the force update method (press and hold the buttons until you see the update process starting!)..
id this fails too..well..i don't know how to help then..
if there was a cn firmware on your device (as mentioned) then search for the unicom firmware and read how to flash this and do a eventually downgrade at first)..
blueIBI said:
very strange..
maybe you do a all again..
starting with flashing a stock boot.img and recovery.img (from the b512 rom..you can extract them by the update extractor from here..just search)..
then try to flash the b512 rom by the force update method (press and hold the buttons until you see the update process starting!)..
id this fails too..well..i don't know how to help then..
if there was a cn firmware on your device (as mentioned) then search for the unicom firmware and read how to flash this and do a eventually downgrade at first)..
Click to expand...
Click to collapse
i cant even flash my recovery, when i use adb, it just shows me waiting for device, then no response. I tried most of the ways but no one can help......
hm..what might help is that you install the device drivers again..i had in the beginning a similar problem..after reinstall of the device driver (there is a package by lesscro on this forum) my device was seen even in bootloader mode correct..
blueIBI said:
hm..what might help is that you install the device drivers again..i had in the beginning a similar problem..after reinstall of the device driver (there is a package by lesscro on this forum) my device was seen even in bootloader mode correct..
Click to expand...
Click to collapse
i reinstall the driver setup from lesscro, is still the same, nth works for me, I cannot change recovery cannot flash new ROM, everything just a mess
miz_pimp said:
If it was a Chinese firmware, you need to try flashing this file first: https://mega.co.nz/#!8kcVADpB!JKeDlX4WQhmAP3mclNTfIzIjVllw5sMhnrj-3KSpSc4
Click to expand...
Click to collapse
sasadeaunty said:
i reinstall the driver setup from lesscro, is still the same, nth works for me, I cannot change recovery cannot flash new ROM, everything just a mess
Click to expand...
Click to collapse
Have you tried the file that I linked to above?
I think your problem is that you flashed the incorrect recovery version for the firmware you had on your device.
Unless you used TWRP to completely wipe your device before you flashed your stock recovery (which was not at all necessary), then you should still have a firmware on your device.
miz_pimp said:
Have you tried the file that I linked to above?
I think your problem is that you flashed the incorrect recovery version for the firmware you had on your device.
Unless you used TWRP to completely wipe your device before you flashed your stock recovery (which was not at all necessary), then you should still have a firmware on your device.
Click to expand...
Click to collapse
hi miz_pimp, thank you so muchhhhhhhhhhhhh, I am able to recover my p6 with the firmware u linked to me. Really thank you and thanks for others too for helping me too. Thanks all.
Glad you got it sorted, and you're very welcome. [emoji2]
Hi folks ! i have read a lot but getting confused somehow. Can anyone tell me or guide how to root my HTC 10 on Nougat ?
Unlock bootloader
Flash latest TWRP
Flash latest SuperSU
Beware Unlocking bootloader resets phone
Make sure to Nandroid backup
Better would be to flash Magisk to obtain systemless MagiskSU. This will keep SafetyNet working which is needed for Apps like Android Pay and so on to run and work. On the other hand you can in addition install some miss without even modifying system which would enable you to just flash stick recovery and install official OTAs as soon as they hit.
Sent from my htc_pmeuhl using XDA Labs
5m4r7ph0n36uru said:
Better would be to flash Magisk to obtain systemless MagiskSU. This will keep SafetyNet working which is needed for Apps like Android Pay and so on to run and work. On the other hand you can in addition install some miss without even modifying system which would enable you to just flash stick recovery and install official OTAs as soon as they hit.
Sent from my htc_pmeuhl using XDA Labs
Click to expand...
Click to collapse
Can you provide me a link which can help ? i heard TWRP is not available for nougat . Also, for doing this Bootloader should be unlocked ? i got too many question . Can i flash mods if i get magisk root ?
rajkatiyar07 said:
Can you provide me a link which can help ? i heard TWRP is not available for nougat . Also, for doing this Bootloader should be unlocked ? i got too many question . Can i flash mods if i get magisk root ?
Click to expand...
Click to collapse
Bootloader needs to be unlocked. TWRP is compatible to Nougat - see TWRP thread. Latest Magisk can be found in the Magisk forum. Yes you can flash mods and install root Apps if you flash Magisk as it will flash MagiskSU as well.
All can be found in the respective threads, named above.
Sent from my htc_pmeuhl using XDA Labs
ordeniz said:
Unlock bootloader
Flash latest TWRP
Flash latest SuperSU
Beware Unlocking bootloader resets phone
Make sure to Nandroid backup
Click to expand...
Click to collapse
Flashed latest TWRP, but it won't boot into TWRP. Tried about 15 different TWRP versions, no luck. Any ideas?
TK3950 said:
Flashed latest TWRP, but it won't boot into TWRP. Tried about 15 different TWRP versions, no luck. Any ideas?
Click to expand...
Click to collapse
Detail your steps, please. Exactly what TWRP version are you trying to flash, and where did you get the TWRP (link to it)? Did you check the MD5 hash of the TWRP you flashed? https://twrp.me/, besides supplying all the official versions of TWRP for the HTC 10 "pme", also gives a link to the MD5 hash of each version in small print on the Download page for the version you choose "md5 for twrp-3.2.1-2-pme.img".
How are you trying to get into TWRP once you flash it? On the 10, after holding the Volume Down and Power buttons to boot into Download mode, choose "reboot to bootloader", then from the bootloader choose "boot to recovery mode".
I haven't been on Nougat since 8.0 came out so I can't personally test the latest TWRP with it, but if there's any problem with the latest versions with Nougat I'm sure it'd be mentioned in the TWRP thread here in the HTC 10 Development section. Have you asked about this issue there?
roirraW "edor" ehT said:
Detail your steps, please. Exactly what TWRP version are you trying to flash, and where did you get the TWRP (link to it)? Did you check the MD5 hash of the TWRP you flashed? https://twrp.me/, besides supplying all the official versions of TWRP for the HTC 10 "pme", also gives a link to the MD5 hash of each version in small print on the Download page for the version you choose "md5 for twrp-3.2.1-2-pme.img".
How are you trying to get into TWRP once you flash it? On the 10, after holding the Volume Down and Power buttons to boot into Download mode, choose "reboot to bootloader", then from the bootloader choose "boot to recovery mode".
I haven't been on Nougat since 8.0 came out so I can't personally test the latest TWRP with it, but if there's any problem with the latest versions with Nougat I'm sure it'd be mentioned in the TWRP thread here in the HTC 10 Development section. Have you asked about this issue there?
Click to expand...
Click to collapse
Hey, thanks for the quick reply mate.
Bootloader unlocked through the HTCDev site instructions. DL mode shows device unlocked, software modified, and S-On. SD Card is inserted. Fastboot in download mode to flash every .img listed on twrp and all .img files from the unofficial list. Didn't check the MD5's, thought it was pretty unlikely that all failed, but I'll try that when I'm out of work. Attempting to flash from Download Mode, using "fastboot flash recovery twrp***.img", *** changing per version. From bootloader mode, when I choose "Boot to recovery mode", I get the HTC logo + red disclaimer, then a reboot, more HTC logo + red disclaimer, then back into bootloader mode. Google searches have suggested using unofficial TWRP 3.0.3-6 or 3.0.3-9, but these files are nowhere to be found anymore. DL links here on xda seem to have been removed. 3.0.3-10 and -11 produce the same error as all other .img files. I've tried this on a machine at home and a machine at my job, so that's two different networks as well.
As a secondary, I've also tried "fastboot erase recovery" a few times before flashing TWRP images, same result.
Edit (2/3/18 @ 16:01): Verified the MD5 hashes, everything has downloaded correctly. Even if anyone has a copy of the 3.0.3-6 or -9 .img files, I'd be willing to try those out too.
TK3950 said:
Hey, thanks for the quick reply mate.
Bootloader unlocked through the HTCDev site instructions. DL mode shows device unlocked, software modified, and S-On. SD Card is inserted. Fastboot in download mode to flash every .img listed on twrp and all .img files from the unofficial list. Didn't check the MD5's, thought it was pretty unlikely that all failed, but I'll try that when I'm out of work. Attempting to flash from Download Mode, using "fastboot flash recovery twrp***.img", *** changing per version. From bootloader mode, when I choose "Boot to recovery mode", I get the HTC logo + red disclaimer, then a reboot, more HTC logo + red disclaimer, then back into bootloader mode. Google searches have suggested using unofficial TWRP 3.0.3-6 or 3.0.3-9, but these files are nowhere to be found anymore. DL links here on xda seem to have been removed. 3.0.3-10 and -11 produce the same error as all other .img files. I've tried this on a machine at home and a machine at my job, so that's two different networks as well.
As a secondary, I've also tried "fastboot erase recovery" a few times before flashing TWRP images, same result.
Click to expand...
Click to collapse
EDITING---
santod040 said:
EDITING---
Click to expand...
Click to collapse
Any news mate? Being able to root this phone was a major condition when I bought it.
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.
Hello,
I have seen few requests about providing pre-rooted boot image file for OP7T European version for firmware 10.0.6 so here you go.
Steps :
1) Reboot your phone in bootloader mode (fastboot mode).
2) Execute command fastboot boot magisk_patched.img
3) Reboot the device
4) Install Magisk Manager
5) Click on Install, then direct install and wait the end of the process
6) Reboot the device
Also attaching the stock boot file in case anything goes wrong.
P.S : I don't own European OP7T.
Link : https://www.androidfilehost.com/?w=files&flid=303273
*delete*
Can you do one for the 10.0.6 USA Version? I can't find one anywhere. Thanks so much. I can't even find a copy of the stock 10.0.6 US boot img
Worked well, got my phone rooted yesterday.
Lähetetty minun HD1903 laitteesta Tapatalkilla
click4dylan said:
Can you do one for the 10.0.6 USA Version? I can't find one anywhere. Thanks so much. I can't even find a copy of the stock 10.0.6 US boot img
Click to expand...
Click to collapse
USA version is HD65AA ? Can you send the product code and I will try
Yes, my build number is 10.0.6.HD65AA and model number is HD1905. Thank you so very much! Also, can you show me how you are getting the boot image for these new versions so I can do it myself in the future? Thanks again. SKU on the box says 5011100751
Hi!
Sorry for this question, flashing this boot image will wipe my device?
Thanks.
paulo_snower said:
Hi!
Sorry for this question, flashing this boot image will wipe my device?
Thanks.
Click to expand...
Click to collapse
NO! First time you unlock your bootloader thats wipe your device, not when flashing a boot.img
it's not working for me with Oxygen 10.0.6 HD65BA.
If i try to boot the magisk patched boot image the phone just reboot within fastboot mode, and if i try to normally boot i just can't update magisk.
-----
Update:
I found this surfing the net :
Unlike older OnePlus phones, the current bootloader of the OnePlus 7 Pro doesn’t allow ‘fastboot boot’ (also known as tethered booting) command. The situation is same as Essential PH-1 as well some other phones where you can’t temporarily boot a kernel or recovery.
nicoilboss said:
it's not working for me with Oxygen 10.0.6 HD65BA.
If i try to boot the magisk patched boot image the phone just reboot within fastboot mode, and if i try to normally boot i just can't update magisk.
-----
Update:
I found this surfing the net :
Unlike older OnePlus phones, the current bootloader of the OnePlus 7 Pro doesn’t allow ‘fastboot boot’ (also known as tethered booting) command. The situation is same as Essential PH-1 as well some other phones where you can’t temporarily boot a kernel or recovery.
Click to expand...
Click to collapse
click4dylan said:
Yes, my build number is 10.0.6.HD65AA and model number is HD1905. Thank you so very much! Also, can you show me how you are getting the boot image for these new versions so I can do it myself in the future? Thanks again. SKU on the box says 5011100751
Click to expand...
Click to collapse
zanderzone said:
USA version is HD65AA ? Can you send the product code and I will try
Click to expand...
Click to collapse
Sorry for being late. Please try this : https://forum.xda-developers.com/oneplus-7t/how-to/pre-rooted-boot-image-op7t-global-t4009305
Thanks, I found the instructions on how to do it already and took the Global boot image. I am just booting it with fastboot boot instead of flash. Just being cautious is all.
Same situation over there, trying either boot or flash the image, the phone reboots itself into bootloader. Stock 10.0.6.
Enviado desde mi HD1903 mediante Tapatalk
What is the difference between global and European? And can i still update ota after flashing this?
Hello !
Thanks for the guide !
I successfully installed Magisk, but once I install Riru core and EdXposed, my OP7T also gets stuck and boots only into fastboot. After wiping everything to factory reset, my phone is back to normal.
Is EdXposed working with this version of Magisk ?
(OpenPlus 7T HD65BA 10.0.6)
Thanks for help
Edit : problem solved with this method.
Excellent.
Many thanks @zanderzone
Can i still update ota in settings adter installing this version? Or will i loose root everytime?
karayemis said:
Can i still update ota in settings adter installing this version? Or will i loose root everytime?
Click to expand...
Click to collapse
Most likely you won't get any notifications if there are updates. You won't be able to use incremental updates.
But you can keep root flashing magisk right after the update before rebooting your phone.
could someone help me? I got the european version but if i try to boot the magisk_patched.img i just get stuck in fastboot mode and if i try to flash the patched image i get stuck in fastboot mode and i've to flash again the stock boot.
I also tried the global one but without any results.
Thanks
edit. I have the HD65BA 10.0.6 version
I was able to boot using your magisk_patched.img using "fastboot boot magisk_patched.img", but WIFI doesn't work now. I haven't inserted the SIM yet so I am unable to install magisk (it can't connect to download it). Is it only my case, or did it happen to anyone else? Any fixes?
Or is ir a temporary thing and after installing magisk it will work (WIFI)?
EDIT: with "fastboot boot Stock_boot.img" I get the same WIFI problem. Rebooting normally makes WIFI work again.
EDIT2: I tried it with the SIM on and the process was perfect. Thank you for that patched boot image and the tutorial!!!
Any chance @zanderzone that you could put a 10.0.7 version up?
I lost root with the recent update...
I found the detailed instructions too late.
Detailed instructions here: https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
Many thanks
okay so i am pretty new still to flashing firmwares and using fastboot in general. I have the cricket version of the moto g6 play (forge) and noticed that i could not unlock the bootloader through moto's website . i noticed that the model number for the cricket version of the xt1922-9 was the same as the retail version from motorola . which on the website says has the ability to unlock . so i tried to flash the stock retail firmware for the retail and the most update verision being android pie XT1922-9_JETER_RETUS_9.0_PPPS29.118-68-3_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip and ended up flashing everything succesfully other than the boot.img and all of the system.img files and when i try and reboot the phone to recovery it says failed to pass validation back to fastboot . and the baseband section in fastboot now says not found . can someone help me with how i can flash all the correct files so i can get the phone just to boot up again.
You flashed everything except the boot.img and the system.img files?? That means you mixed up two FWs on one device...
Try flashing this FW for jeter_cricket from mirrors.lolinet.com
https://mirrors.lolinet.com/firmware/moto/jeter/official/Cricket/XT1922-9_JETER_A_CRICKET_9.0_PCPS29.118-63-2_cid1_subsidy-CRICKET_regulatory-DEFAULT_CFC.xml.zip
WoKoschekk said:
You flashed everything except the boot.img and the system.img files?? That means you mixed up two FWs on one device...
Try flashing this FW for jeter_cricket from mirrors.lolinet.com
Click to expand...
Click to collapse
i tried to flash that firmware and still , im only able to succefully flash everything but the system images the bootloader the recovery and the boot image.
jesheesh said:
i tried to flash that firmware and still , im only able to succefully flash everything but the system images the bootloader the recovery and the boot image.
Click to expand...
Click to collapse
What is "not successfully"? Could you explain it more detailed, please? There's always an output message in terminal
jesheesh said:
i tried to flash that firmware and still , im only able to succefully flash everything but the system images the bootloader the recovery and the boot image.
Click to expand...
Click to collapse
You could try LMSA flash rescue option
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my ali using XDA Labs
sd_shadow said:
You could try LMSA flash rescue option
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
i'll download it and try it out
jesheesh said:
i'll download it and try it out
Click to expand...
Click to collapse
I'll also go ahead and copy and paste the output for you here as well.
Sorry it takes me so long to reply . Most of my tinkering time is eaten up with my other phone I have that just so happens to be the only model variant that can't unlock its boot loader hence no root or twrp ... :/
But anyway yeah I'm gonna try the tool and paste those lines of fast boot code for you. One sec.