Just want to share my personal experience in hopes it may help someone.
I have T-MOBILE version GM1915.
This is only after you have successfully unlocked your bootloader.
I downloaded the twrp from @mauronofrio twrp thread.
fastboot twrp.img then choose recovery while in bootloader. Plugged in USB otg and restarted recovery. Pushed reboot button to change to unmodified slot took a backup of boot system and vendor img files. Then since I had the full ota package for us unlocked/global on my drive I chose to install it. Once done I switched back to original slot and installed it again. Reboot and stock 9.5.3.
Make sure to flash to both slots or you will most likely get Qualcomm crash dump error.
If anyone can please take a backup of the unmodified boot partition and link it here. I have system and vendor but we need stock boot.img to help others and so we can patch it and TMobile users won't have to flash twrp just to root.
twinnfamous said:
Just want to share my personal experience in hopes it may help someone.
I have T-MOBILE version GM1915.
This is only after you have successfully unlocked your bootloader.
I downloaded the twrp from @mauronofrio twrp thread.
fastboot twrp.img then choose recovery while in bootloader. Plugged in USB otg and restarted recovery. Pushed reboot button to change to unmodified slot took a backup of boot system and vendor I'm going files. Then since I had the full ota package for us unlocked/global on my drive I chose to install it. Once done I switched back to original slot and installed it again. Reboot and stock 9.5.3.
Make sure to flash to both slots or you will most likely get Qualcomm crash dump error.
Click to expand...
Click to collapse
This definitely seems promising! Should I order a USB OTG cable to attempt this in the future?
T_VASS said:
This definitely seems promising! Should I order a USB OTG cable to attempt this in the future?
Click to expand...
Click to collapse
The USB otg is only because of decryption.
I bought a SanDisk 128 gb dual USB type-C from Best buy 35 out the door
twinnfamous said:
Just want to share my personal experience in hopes it may help someone.
I have T-MOBILE version GM1915.
This is only after you have successfully unlocked your bootloader.
I downloaded the twrp from @mauronofrio twrp thread.
fastboot twrp.img then choose recovery while in bootloader. Plugged in USB otg and restarted recovery. Pushed reboot button to change to unmodified slot took a backup of boot system and vendor I'm going files. Then since I had the full ota package for us unlocked/global on my drive I chose to install it. Once done I switched back to original slot and installed it again. Reboot and stock 9.5.3.
Make sure to flash to both slots or you will most likely get Qualcomm crash dump error.
Click to expand...
Click to collapse
Tyvm for This I can just wipe the system and flash the global version from my USB flash drive
Exathi said:
Tyvm for This I can just wipe the system and flash the global version from my USB flash drive
Click to expand...
Click to collapse
I can only confirm the 9.5.3 will work.
Also no need to wipe system. After it boots to os you can factory reset to get rid of TMobile apps that we're stored in data
twinnfamous said:
I can only confirm the 9.5.3 will work.
Also no need to wipe system. After it boots to os you can factory reset to get rid of TMobile apps that we're stored in data
Click to expand...
Click to collapse
Sweet thanks I Downloaded the OxygenOS ROM from the OnePlus website is that sufficient?
twinnfamous said:
The USB otg is only because of decryption.
I bought a SanDisk 128 gb dual USB type-C from Best buy 35 out the door
Click to expand...
Click to collapse
I get my unlock token from OnePlus tomorrow afternoon. I've never used an OTG but have this one from my Pixel 3 XL with the flash drive attached you think it will work?
Edit: I just plugged it in and I'm able to explore the files on it so I'm thinking it will work.
bp328i said:
I get my unlock token from OnePlus tomorrow afternoon. I've never used an OTG but have this one from my Pixel 3 XL with the flash drive attached you think it will work?
Edit: I just plugged it in and I'm able to explore the files on it so I'm thinking it will work.
Click to expand...
Click to collapse
This will work I'm going to use that can we also just do an Local update with an unlocked bootloader on the TMobile variant?
Exathi said:
This will work I'm going to use that can we also just do an Local update with an unlocked bootloader on the TMobile variant?
Click to expand...
Click to collapse
TMobile variant software does not support the option for local upgrade.
twinnfamous said:
TMobile variant software does not support the option for local upgrade.
Click to expand...
Click to collapse
I actually got the option to flash from local storage to show by installing the stock apps found around online. This was just me tinkering briefly but it did have issues seeing the files in root, not sure if the T-Mobile one is using a different structure. I do note if you try this method mobile data breaks, I didn't have time to play with it more as I was leaving in vacation and needed a working phone so I factory reset.
I was planning on trying to flash the Android q beta then downgrading to the stock rom. I know it was a folly but was bored.
bp328i said:
I get my unlock token from OnePlus tomorrow afternoon. I've never used an OTG but have this one from my Pixel 3 XL with the flash drive attached you think it will work?
Edit: I just plugged it in and I'm able to explore the files on it so I'm thinking it will work.
Click to expand...
Click to collapse
Yes if u can explore files u should be good
Has anyone else successfully tried this? I'll have my bin tomorrow night but it's been sometime since I flashed or modded a device.
T_VASS said:
Has anyone else successfully tried this? I'll have my bin tomorrow night but it's been sometime since I flashed or modded a device.
Click to expand...
Click to collapse
nope, tried it last night and got the qualcomm error, now I think my device is hosed for a while. I can get into stock recovery and twrp though.
phab3k said:
nope, tried it last night and got the qualcomm error, now I think my device is hosed for a while. I can get into stock recovery and twrp though.
Click to expand...
Click to collapse
Guess you didn't read the part about flashing the 9.5.3 ota to both slots.
I'm Allready on the 9.5.4 now. Also please ask if not sure about something that way we can avoid issues.
twinnfamous said:
Guess you didn't read the part about flashing the 9.5.3 ota to both slots.
I'm Allready on the 9.5.4 now. Also please ask if not sure about something that way we can avoid issues.
Click to expand...
Click to collapse
i did, problem is when I flashed one side, I got an error about the /data partition when I tried to flash either partition. If the error can be overcome, I'm sure flashing the stock image will be possible.
phab3k said:
i did, problem is when I flashed one side, I got an error about the /data partition when I tried to flash either partition. If the error can be overcome, I'm sure flashing the stock image will be possible.
Click to expand...
Click to collapse
The data error doesn't pertain to the system or other partitions Just data.
Also did you use USB otg once you were in twrp.
twinnfamous said:
The data error doesn't pertain to the system or other partitions Just data.
Also did you use USB otg once you were in twrp.
Click to expand...
Click to collapse
yep, I used my otg adapter from my pixel and a flash drive. when I'm in twrp I can browse and select the file and flashing appears to work, but when I first try to flash after switching to non active partition I get an error. I'm using the stock image from oneplus, OnePlus7ProOxygen_21.O.07_OTA_007_all_1905120542_fc480574576b4843.zip, filesize is about 2.1GB.
phab3k said:
yep, I used my otg adapter from my pixel and a flash drive. when I'm in twrp I can browse and select the file and flashing appears to work, but when I first try to flash after switching to non active partition I get an error. I'm using the stock image from oneplus, OnePlus7ProOxygen_21.O.07_OTA_007_all_1905120542_fc480574576b4843.zip, filesize is about 2.1GB.
Click to expand...
Click to collapse
Erase the whole system and flash the ota from your flashdrive through TWRP
I'm waiting for the MSM Tool to make the switch, it's just faster, easier and more safe!
SmileBigNow said:
I'm waiting for the MSM Tool to make the switch, it's just faster, easier and more safe!
Click to expand...
Click to collapse
Will you be able to override T-Mobile sim unlock?
I'm just trying to go around paying for device in full and 40 days.
Related
So this is a bit of a comedy of errors on my part...
I took the OTA update to lollipop and (foolishly) followed the same method as on KK to get root, putting myself in a bootloop. I got myself out of it by clearing the userdata and the cache.
I went about sorting everything and achieved root using the chainfire method, that was fine and I then went about reinstalling the xposed modules I had before. Foolishly, I didn't double check the status of xposed on Lollipop and consequently put myself back in a bootloop (idiot). I redid what had worked earlier, clearing the userdata and the cache to no avail.
Obviously, the problem was not the same as before and I needed to disable xposed, but in clearing the userdata I not only removed the xposed_disable.zip file to do this and also turned off adb so I can't push it.
The bootloader is fine and I can use fastboot, but can't push anything across. I hadn't replaced the recovery but can boot into twrp. However, I cannot flash it because I cannot push it over using adb.
I can't work out exactly how far I need to go back/what exactly I need to flash in order to put this all back together again.
I would be very grateful for any help that people can give on this.
Oh man.... This post made me giggle.
Right first of all what device do you have?
Anyway to connect a flash drive to the USB or a Micro SD and flash a new ROM in recovery?
Sent From N5
All you need is ability to enter fastboot. Using Multitool or manual fastboot flash commands, you should be able to go back to stock KK. From there on you can flash stock L. Root it.
Do not have access to Multitool runme.cmd file at the moment to confirm that all you need is ability to issue fastboot command. adb is not needed. But am almost certain that this is the case.
LiamAtkins90 said:
Oh man.... This post made me giggle.
Right first of all what device do you have?
Anyway to connect a flash drive to the USB or a Micro SD and flash a new ROM in recovery?
Sent From N5
Click to expand...
Click to collapse
It's a 2014 Moto X, the XT1092 (bought straight from Motorola - I think that makes it the pure edition).
prasad.adam said:
All you need is ability to enter fastboot. Using Multitool or manual fastboot flash commands, you should be able to go back to stock KK. From there on you can flash stock L. Root it.
Do not have access to Multitool runme.cmd file at the moment to confirm that all you need is ability to issue fastboot command. adb is not needed. But am almost certain that this is the case.
Click to expand...
Click to collapse
I have tried the Multitool (as in here) but it would always throw me errors and never showed up anything on the fastboot console. I expect I probably need to get the stock image from Motorola (I've requested access to this which is the top option from here) and issue the fastboot commands by hand which seems to work. I'm mostly just unsure about what exact commands I need to give to make sure I don't forget to flash a particular part. I haven't gone this far on other phones and have normally worked from CWM but I can't even flash that/TWRP at the moment.
Thanks for your help guys!
HamRack said:
It's a 2014 Moto X, the XT1092 (bought straight from Motorola - I think that makes it the pure edition).
I have tried the Multitool (as in here) but it would always throw me errors and never showed up anything on the fastboot console. I expect I probably need to get the stock image from Motorola (I've requested access to this which is the top option from here) and issue the fastboot commands by hand which seems to work. I'm mostly just unsure about what exact commands I need to give to make sure I don't forget to flash a particular part. I haven't gone this far on other phones and have normally worked from CWM but I can't even flash that/TWRP at the moment.
Thanks for your help guys!
Click to expand...
Click to collapse
1.Download the latest TWRP recovery. 2.Prepare a SD card with a card reader and format it to ext4,then put Xposed-Disabler-Recovery.zip in it.
3.Boot your phone to ap fastboot mode,then open a cmd prompt and issue: fastboot boot TWRPimgfilename
3.link your phone to the card reader with otg cable and mount the SD card via TWRP advanced menu.
4.Flash the Xposed-Disabler-Recovery.zip via TWRP.
purejoy said:
1.Download the latest TWRP recovery. 2.Prepare a SD card with a card reader and format it to ext4,then put Xposed-Disabler-Recovery.zip in it.
3.Boot your phone to ap fastboot mode,then open a cmd prompt and issue: fastboot boot TWRPimgfilename
3.link your phone to the card reader with otg cable and mount the SD card via TWRP advanced menu.
4.Flash the Xposed-Disabler-Recovery.zip via TWRP.
Click to expand...
Click to collapse
Would it need to be an SD card or just a usb stick formatted correctly?
This sounds the best idea yet, now just to track down a USB OTG cable...
HamRack said:
Would it need to be an SD card or just a usb stick formatted correctly?
This sounds the best idea yet, now just to track down a USB OTG cable...
Click to expand...
Click to collapse
SD card is OK. As USB disk,haven't give a try.
Ok, cheers. I'll get a usb otg cable and give it a go.
HamRack said:
Ok, cheers. I'll get a usb otg cable and give it a go.
Click to expand...
Click to collapse
Normally Xposed installer would put a copy of Xposed-Disabler-recovery.zip under directory /sdcard after being installed. You should check the directory first, moreover, that file was released for those KK users. I have no idea whether it would take effect on lollipop or destroy your system. Take your own risk.
purejoy said:
Normally Xposed installer would put a copy of Xposed-Disabler-recovery.zip under directory /sdcard after being installed.
Click to expand...
Click to collapse
So I found, but because my first reaction to the second bootloop was to erase userdata (as had fixed the earlier one) I lost that.
purejoy said:
1.Download the latest TWRP recovery. 2.Prepare a SD card with a card reader and format it to ext4,then put Xposed-Disabler-Recovery.zip in it.
3.Boot your phone to ap fastboot mode,then open a cmd prompt and issue: fastboot boot TWRPimgfilename
3.link your phone to the card reader with otg cable and mount the SD card via TWRP advanced menu.
4.Flash the Xposed-Disabler-Recovery.zip via TWRP.
Click to expand...
Click to collapse
Hi,
Tracked down a usbotg cable and have booted into TWRP. When I plug in the sd card using the cable, I don't find anything to mount the sd card in the advanced menu of TWRP, but I do find a 'mount' option on the main menu
(as you can see here). Under there is a tick box for 'USB-OTG' which I have ticked, but I can't find where it actually is in the filemanager/when I select 'install'...
Any suggestions?
Realised what I had done, managed to flash the xposed_disabler zip, but it didn't work.
However, I was pointed in the direction of this where I downgraded to KK 4.4.4. That seems to have done the trick at getting me back to a working device. Out of curiosity, does anyone know a reason why I shouldn't get have the Lollipop OTA come through again in due course? When I check for updates it says I am up to date - is the only way I will get L by way of sideloading?
Finally, thanks for all your help, you've been very patient with my dangerous level of knowledge - enough to do plenty of damage but not enough to fix it!
HamRack said:
Hi,
Tracked down a usbotg cable and have booted into TWRP. When I plug in the sd card using the cable, I don't find anything to mount the sd card in the advanced menu of TWRP, but I do find a 'mount' option on the main menu
(as you can see here). Under there is a tick box for 'USB-OTG' which I have ticked, but I can't find where it actually is in the filemanager/when I select 'install'...
Any suggestions?
Click to expand...
Click to collapse
You were expected to use the latest TWRP which is 2.8+,at least 2.7. Anyway,that's not important.
Did you get an error after issuing "fastboot flash motoboot motoboot.IMG"?
Cuz you succeeded in updating, the OTA has upgraded your bootloader. Although you have downgraded your system, the BL can't be,hence when you try to accept another OTA, there will be a verification error.
Now You need flash a custom OTA pack via a 3rd party recovery. Some verifications must be removed from the official OTA zip.
You can also wait for someone to backup and share the images of the new system.
---------- Post added at 01:29 AM ---------- Previous post was at 01:07 AM ----------
HamRack said:
Realised what I had done, managed to flash the xposed_disabler zip, but it didn't work.
However, I was pointed in the direction of this where I downgraded to KK 4.4.4. That seems to have done the trick at getting me back to a working device. Out of curiosity, does anyone know a reason why I shouldn't get have the Lollipop OTA come through again in due course? When I check for updates it says I am up to date - is the only way I will get L by way of sideloading?
Finally, thanks for all your help, you've been very patient with my dangerous level of knowledge - enough to do plenty of damage but not enough to fix it!
Click to expand...
Click to collapse
I think you can have a try to download the .19 OTA zip and put it under /sdcard, then reboot into stock recovery to apply update from SD card or adb sideload. If there's no errors while verifying, you would get lollipop again.
Sorry for not reading all the reply's in this thread before posting (i'm in a bit of a rush)
I got a bootloop while applying the OTA on a brand new XT 1092 right after taking out of the box. After some digging around the forums (you can tell i'm new by the post count) i managed to get an OTA zip for my DE version and pushed it via ADB using stock recovery, with a few hickups:
- had to manually install the driver in windows
- first time the install via ADB push failed with some assert failure on something related to moto.odex
- the second try went ok and got the bootloop sorted.
So definitely give ADB a shot
Good luck!
First, try to recover as much as of your data stored on the device .
Then reflash the old ROM. You'll need a specific program for that - and a PC Surely! ☺
After that to get easier Back-Ups - i recommend unblocking the bootloader.
All the best☻.
purejoy said:
You were expected to use the latest TWRP which is 2.8+,at least 2.7. Anyway,that's not important.
Click to expand...
Click to collapse
I used TWRP 2.8.1.0, I downloaded it that day. Not sure what else it could have been...
Did you get an error after issuing "fastboot flash motoboot motoboot.IMG"?
Click to expand...
Click to collapse
Not sure when I was supposed to do that, couldn't see that in your directions...? Not a really a problem either way as its now sorted.
Cuz you succeeded in updating, the OTA has upgraded your bootloader. Although you have downgraded your system, the BL can't be,hence when you try to accept another OTA, there will be a verification error.
Now You need flash a custom OTA pack via a 3rd party recovery. Some verifications must be removed from the official OTA zip.
You can also wait for someone to backup and share the images of the new system.
I think you can have a try to download the .19 OTA zip and put it under /sdcard, then reboot into stock recovery to apply update from SD card or adb sideload. If there's no errors while verifying, you would get lollipop again.
Click to expand...
Click to collapse
Ok, thanks for the info. Any idea how to remove those verifications? Would this do the required thing?
Also, what exactly do you mean by the .19 OTA zip? You mean the OTA zip with the new bootloader in with it? If it has an error while trying this, would it give problems or just stop and return as before?
Thanks
Sorry, i have stayed up too late last night. You know there is time difference.
i dunno the differences between GB version and EU version, since you have a system of EU, maybe you should refer to this thread http://forum.xda-developers.com/moto-x-2014/general/ota-zip-moto-x-2014-xt1092-5-0-t2970818
Hmm,there is a better choice. Seems that moto has released the stock 5.0 firmware for GB xt1092. http://forum.xda-developers.com/showpost.php?p=57591807&postcount=36
Download it and make a full recovery.
BTW: Please backup your data first.
purejoy said:
Sorry, i have stayed up too late last night. You know there is time difference.
i dunno the differences between GB version and EU version, since you have a system of EU, maybe you should refer to this thread http://forum.xda-developers.com/moto-x-2014/general/ota-zip-moto-x-2014-xt1092-5-0-t2970818
Hmm,there is a better choice. Seems that moto has released the stock 5.0 firmware for GB xt1092. http://forum.xda-developers.com/showpost.php?p=57591807&postcount=36
Download it and make a full recovery.
BTW: Please backup your data first.
Click to expand...
Click to collapse
I'm not sure of the differences either...
So I'm wanting to make sure I do this correctly this time. I know a couple of ways of backing up but after all the faff recently I want to have an ironclad backup before I piss around with anything else (foolish me for not doing so before). Can you clarify the best way to back up my device and how I would do that? I have a feeling I haven't been doing it correctly/the most ideal way before and it would be good to know.
Also, how would I go about putting that backup you've pointed too (thank you for finding that, I don't think I'd been searching for quite the right thing) on to my device? Would I go through a similar series of steps to how I recovered my phone before (ie here)?
I'm going away for xmas/NY and will probably do this when I get back so I don't risk borking my phone when I need it most. Nonetheless, it would be good to have things ready to roll when I get back.
Thanks for your help, you've been great.
It depends on what you plan to backup and i don't konw what app your are using. If you use Google service, Contacts and some app data are normally synced to Google Cloud Servers. You can get them back in lollipop 5.0 via your Google account. As your pictures and videos,you can also directly copy them on your PC. What you need to backup are private app data and private messages. You can use some 3rd party backup apps like TitaniumBakcup to solve this. If there are not so much user data, you can backup like this.
You can also backup and restore your userdata via TWRP. If you get so many data, you can try this.
As the full stock recovery,you can restore your phone via fastboot utility or RSD lite.
1.Download and Unzip the image.
2.Put your phone in AP Fastboot Mode.
3. $ fastboot flash partition gpt.bin
$ fastboot flash motoboot motoboot.img
$ fastboot reboot-bootloader
$ fastboot flash logo logo.bin
$ fastboot flash boot boot.img
$ fastboot flash recovery recovery.img
$ fastboot flash system system.img
$ fastboot erase modemst1
$ fastboot erase modemst2
$ fastboot flash fsg fsg.mbn
$ fastboot -w (Erase userdata. Optional,maybe unnecessary)
$ fastboot reboot
I would advise you to put off erasing data. If you get any issues while rebooting into new system, then you can erase your data.
Hope these help. Good Luck!
Great, thanks for the tip.
I tend to have minimal important data on my phone that isn't covered by either google or evolvesms/whatsapp. Nonetheless, thanks for the tips. I've been using titanium for a long while and have that backed up to dropbox too.
I tried flashing TWRP after I fixed the clusterbadger that was the last few days, but had no luck. I still don't seem to be able to push the image over using adb nor use adb to issue commands while booted into TWRP through fastboot. Have you experienced that? I guess worst case is that I copy the zip to an sdcard and flash it from usbotg by issuing commands in the TWRP shell they give you...?
Thanks for the tip on the userdata too.
Hello people,
I was able to successfully build twrp 3.0 for suzuran (our device, duh!) and thought I'd share the recovery.img so you can test and see what works and what doesn't.
The recovery was built in a CM13 similar environment (PAC), so there might be some issues when working with stock kernel.
Since this is an experimental build (I tested main functionalities and they work, but didn't get down to the nitty-gritty), here's a small disclaimer:
By flashing or booting the attached recovery you're risking damaging you device, or losing the data on your device!
Neither I nor anyone else but YOU is responsible should any bad unintended problems appear!
If you're feeling adventurous then feel free to flash the recovery.img (along with Androplus kernel) and try the sweetness that is TWRP 3.0 :good:
Download link:
April 3, 2016 (3.0.1)
March 25, 2016
March 21, 2016
March 12, 2016
Known issues:
Temperature reading is botched
Crypto might not be working, like AT ALL
usb connection doesn't work (only if you use this recovery with Androplus kernel)
There could be more problems, which is why this is EXPERIMENTAL for now
And now let's get to the sources!
kernel:
[url]https://github.com/oshmoun/kernel/tree/aosp/LA.BF64.1.2.2_rb4.7[/URL]
device sources:
[url]https://github.com/oshmoun/device-sony-suzuran/tree/master[/URL]
[url]https://github.com/oshmoun/device-sony-kitakami/tree/master[/URL]
[url]https://github.com/SonyCM/device-sony-common/commits/cm-13.0[/URL]
And now to thank the people who helped in this endeavor:
TWRP team for the awesome recovery!
@nilezon for the TWRP flags (which I still need to go through to check if I missed/need anything, especially crypto flags...)
FXP team for device sources, Especially @adfad666
All of the Sony AOSP contributors, they're awesome people!
It doesn't work on my Android 6.0 device:crying:
doesn't work on sony mm, stuck at sony logo
iMaeGoo said:
It doesn't work on my Android 6.0 device:crying:
Click to expand...
Click to collapse
tanto124 said:
doesn't work on sony mm, stuck at sony logo
Click to expand...
Click to collapse
Could you tell me if you have E5823 or E5803, I have an E5823 and it's working fine.
Also, are you sure you're not FLASHING the recovery.img? You need to just BOOT it directly from fastboot
oshmoun said:
Could you tell me if you have E5823 or E5803, I have an E5823 and it's working fine.
Also, are you sure you're not FLASHING the recovery.img? You need to just BOOT it directly from fastboot
Click to expand...
Click to collapse
E5823, version 32.1.A.1.163, bootloader unlocked, in fastboot mode, using command "fastboot boot TWRP3.img".
And it stucks at SONY logo.
iMaeGoo said:
E5823, version 32.1.A.1.163, bootloader unlocked, in fastboot mode, using command "fastboot boot TWRP3.img".
And it stucks at SONY logo.
Click to expand...
Click to collapse
this is really weird, did the MM update also change something in the bootloader in an inconvenient way?
Could you try the other recovery.img from nilezon's thread? If that boots using "fastboot boot recovery.img" then we'll know the problem is somewhere in the .img itself
EDIT: oh, also could you please check if your download wasn't corrupt? Here's the md5 hash of the file so you can check
69650eaccdd8b24a3efc0ef1b4bdffb8
oshmoun said:
this is really weird, did the MM update also change something in the bootloader in an inconvenient way?
Could you try the other recovery.img from nilezon's thread? If that boots using "fastboot boot recovery.img" then we'll know the problem is somewhere in the .img itself
EDIT: oh, also could you please check if your download wasn't corrupt? Here's the md5 hash of the file so you can check
69650eaccdd8b24a3efc0ef1b4bdffb8
Click to expand...
Click to collapse
69650eaccdd8b24a3efc0ef1b4bdffb8
The img's MD5 is right.
I'll try to boot Z5C_TWRP_152_v2_nilezon on my device later.
It worked before I upgraded to MM.
oshmoun said:
this is really weird, did the MM update also change something in the bootloader in an inconvenient way?
Could you try the other recovery.img from nilezon's thread? If that boots using "fastboot boot recovery.img" then we'll know the problem is somewhere in the .img itself
EDIT: oh, also could you please check if your download wasn't corrupt? Here's the md5 hash of the file so you can check
69650eaccdd8b24a3efc0ef1b4bdffb8
Click to expand...
Click to collapse
I have no idea.
Z5C_TWRP_152_v2_nilezon doesn't work on MM.
I flash Android 5.1 and try your TWRP3.0, still stuck at SONY logo(with no LED light).
Z5C_TWRP_152_v2_nilezon can work on 5.1.
Now I'm flashing MM again.
iMaeGoo said:
I have no idea.
Z5C_TWRP_152_v2_nilezon doesn't work on MM.
I flash Android 5.1 and try your TWRP3.0, still stuck at SONY logo(with no LED light).
Z5C_TWRP_152_v2_nilezon can work on 5.1.
Now I'm flashing MM again.
Click to expand...
Click to collapse
Thanks! Guess the issue lies in the MM update somewhere.
You just said that nilezon's recovery works on 5.1, but did you try it after flashing 5.1, or are you basing that statement on previous tests?
The issue here might be that you didn't downgrade the bootloader when you flashed 5.1 again, which would mean the issue will persist.
Hello,
I tried booting(didn't flash) with MM and it seemed to boot into recovery fine. Used it to do a cache wipe, but afterwards phone is stuck on boot screen. I can turn it off with power + volume, but it doesn't seem like I can go back to fast boot.
t4656 said:
Hello,
I tried booting(didn't flash) with MM and it seemed to boot into recovery fine. Used it to do a cache wipe, but afterwards phone is stuck on boot screen. I can turn it off with power + volume, but it doesn't seem like I can go back to fast boot.
Click to expand...
Click to collapse
You should be able to go into fastboot mode by turning device off, holding vol+ button, then connecting the device to your computer through usb
oshmoun said:
You should be able to go into fastboot mode by turning device off, holding vol+ button, then connecting the device to your computer through usb
Click to expand...
Click to collapse
Yeah thanks. Took something like 10 tries before it finally went into fastboot. Not sure what went wrong there. Also on my first try I was able to boot into your build of twrp. But afterwards when I try it just gets stuck on the logo again.
t4656 said:
Yeah thanks. Took something like 10 tries before it finally went into fastboot. Not sure what went wrong there. Also on my first try I was able to boot into your build of twrp. But afterwards when I try it just gets stuck on the logo again.
Click to expand...
Click to collapse
This is so freaky what the heck!!!
Could you flash bootloader from 5.1 ftf and see if it works properly then?
I'll (finally) update to MM today , so I'll witness the issues first hand.
oshmoun said:
Thanks! Guess the issue lies in the MM update somewhere.
You just said that nilezon's recovery works on 5.1, but did you try it after flashing 5.1, or are you basing that statement on previous tests?
The issue here might be that you didn't downgrade the bootloader when you flashed 5.1 again, which would mean the issue will persist.
Click to expand...
Click to collapse
I tried nilezon's recovery after flashing 5.1 and it worked.
I use FlashTool to write FTF file to my phone fully, include kernel.
Maybe it's my problem...
Thank you for your patience!
iMaeGoo said:
I tried nilezon's recovery after flashing 5.1 and it worked.
I use FlashTool to write FTF file to my phone fully, include kernel.
Maybe it's my problem...
Thank you for your patience!
Click to expand...
Click to collapse
nope, not your problem, it's everyone's
seems like my twrp version just refuses to boot sometimes.
Was able to successfully replicate the fastboot issue on 5.1 bootloader, so it's definitely this recovery.
Now the question is if it's a TWRP 3 issue, or just in the way I built it
EDIT: I guess this post answers my question
http://forum.xda-developers.com/showpost.php?p=65808636&postcount=137
another twrp 3 recovery is having the same issue
guess I'll have to make this recovery flashable in order for it to work properly
EDIT 2: wow, Androplus kernel seems to go well with TWRP 3. Updated first post with new instructions on how to use this.
oshmoun said:
nope, not your problem, it's everyone's
seems like my twrp version just refuses to boot sometimes.
Was able to successfully replicate the fastboot issue on 5.1 bootloader, so it's definitely this recovery.
Now the question is if it's a TWRP 3 issue, or just in the way I built it
EDIT: I guess this post answers my question
http://forum.xda-developers.com/showpost.php?p=65808636&postcount=137
another twrp 3 recovery is having the same issue
guess I'll have to make this recovery flashable in order for it to work properly
EDIT 2: wow, Androplus kernel seems to go well with TWRP 3. Updated first post with new instructions on how to use this.
Click to expand...
Click to collapse
Can not detect external SD or USB OTG (yet)
Can not detect external SD or USB OTG (yet)
Can not detect external SD or USB OTG (yet)
This will do the job until a proper dev makes a better version.
Maybe I had better wait...:crying::crying::crying:
iMaeGoo said:
Can not detect external SD or USB OTG (yet)
Can not detect external SD or USB OTG (yet)
Can not detect external SD or USB OTG (yet)
This will do the job until a proper dev makes a better version.
Maybe I had better wait...:crying::crying::crying:
Click to expand...
Click to collapse
ummm, my sdcard is getting detected :|
I'll post screenshots soon
EDIT: attached screenshots
oshmoun said:
ummm, my sdcard is getting detected :|
I'll post screenshots soon
EDIT: attached screenshots
Click to expand...
Click to collapse
Can external storages be found in Android system?
iMaeGoo said:
Can external storages be found in Android system?
Click to expand...
Click to collapse
everything concerning external sdcard function is working here as far as i tested (both in Stock mm rom and twrp3)
oshmoun said:
Could you tell me if you have E5823 or E5803, I have an E5823 and it's working fine.
Also, are you sure you're not FLASHING the recovery.img? You need to just BOOT it directly from fastboot
Click to expand...
Click to collapse
it's E5823 running 32.1.A.1.163 . I am sure that I was just booting , downloaded file is okay .
IMPORTANT - READ THIS FIRST:
The Note FE comes with dm-verity check and forced encryption enabled. You will need to remove this extra layer of security for root access. To disable dm-verity and forced encryption you must install TWRP recovery first on your Note FE. Note that disabling forced encryption and dm-verity requires a factory reset from TWRP recovery, so you should backup your data (internal storage) before you begin.
The next stage then will be to root the device by flashing the SuperSU zip via TWRP recovery. SU will also ensure that dm-verity and forced encryption remains disabled. Bear in mind, however, that a factory reset will restore them again.
WHAT YOU WILL NEED:
Download Odin and drivers here: https://build.nethunter.com/samsung-tools/
Download TWRP for Note 7 Exynos: there are two versions: Korean and International:
Korean version: https://dl.twrp.me/graceltekor/
International: https://dl.twrp.me/gracelte/
Download the latest version of SuperSu here: https://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip?retrieve_file=1
You should also download the stock firmware appropriate to your version of Note FE, just in case. Variants S & L can be found on Sammobile, and variant K is available here: https://www.androidfilehost.com/?fid=817550096634784008
ROOTING YOUR NOTE FE:
Read these instructions through carefully before you begin.
(1) Install TWRP Recovery on your Note FE via Odin.
(2) Boot your Note FE into TWRP recovery as follows:
(a) First switch off your device.
(b) Now Press and hold “Home + Power + Volume Up” buttons for a few seconds and as soon as you see your device’s logo on-screen, release the three buttons altogether. Your device will boot into TWRP recovery.
(3) Upon booting into TWRP recovery for the first time, you’ll get a prompt to allow system modifications. You should swipe right to allow this.
(4) On the TWRP main menu, select WIPE then select “Format Data”. You will need to type yes in order to proceed. This will clean wipe the entire internal storage on your Note FE (make sure you have backed-up your important files safe to restore later).
(5) Still in TWRP recovery, you should now connect your Note FE to the PC. (TWRP supports MTP connection so you’ll be able transfer files to the device.) Wait until your Note FE appears on your PC desktop (may take a while first time). You can now transfer the SuperSU zip to your Note FE.
(6) Go back to the TWRP main menu and select “Install” this time. Now you can flash the SuperSU zip.
(7) Reboot your Note FE.
You should now be rooted. Test using an appropriate app.
It would be helpful to others if you reported your experience and the outcome here.
Good luck.
Thanks again for using your device to test this bro!
sent from my Note FE, S8 plus, S7 edge or S6
Thanks alot
thank you very much!
to restore original firmware even if knox counter 01 I need to flash the stock firmware using Odin?
malaccio said:
thank you very much!
to restore original firmware even if knox counter 01 I need to flash the stock firmware using Odin?
Click to expand...
Click to collapse
Yeap just did it.
having a problem booting into twrp after the flash, it stuck on the Samsung logo, Home + Power + Volume Up don't get me anywhere.
any idea will it be the TWRP version, my phone is K version, BTW i can flash stock version back with no problem
iraqgsm said:
having a problem booting into twrp after the flash, it stuck on the Samsung logo, Home + Power + Volume Up don't get me anywhere.
any idea will it be the TWRP version, my phone is K version, BTW i can flash stock version back with no problem
Click to expand...
Click to collapse
Are you letting it boot into system then trying to boot into twrp or trying to boot direct to twrp after it flashes?
sent from my Note FE, S8 plus, S7 edge or S6
I did both and still freeze on the logo screen if I attempt to access recovery. I did it like 40 times still doing the same and flashed the stock and redid again and still the same.
OEM unlock on, and USB debugging on and Odin flash showing successful, not sure what am missing, I did it before in other note 7.
wow N7FE cant use old N7 twrp??
malaccio said:
thank you very much!
to restore original firmware even if knox counter 01 I need to flash the stock firmware using Odin?
Click to expand...
Click to collapse
Yes. Good thing too.
iraqgsm said:
I did both and still freeze on the logo screen if I attempt to access recovery. I did it like 40 times still doing the same and flashed the stock and redid again and still the same.
OEM unlock on, and USB debugging on and Odin flash showing successful, not sure what am missing, I did it before in other note 7.
Click to expand...
Click to collapse
Still in bootloop?
iraqgsm said:
I did both and still freeze on the logo screen if I attempt to access recovery. I did it like 40 times still doing the same and flashed the stock and redid again and still the same.
OEM unlock on, and USB debugging on and Odin flash showing successful, not sure what am missing, I did it before in other note 7.
Click to expand...
Click to collapse
Two possibilities why it's not working for you:
Try flashing TWRP with USB debugging off.
Are you placing the TWRP file in the right slot (AP) in Odin?
The last one is obvious, but it's strange that TWRP doesn't open for you.
kenpaci said:
wow N7FE cant use old N7 twrp??
Click to expand...
Click to collapse
Well, it works. But there may be minor problems. If we get enough reports we should be able to isolate these and see what can be done to correct them.
These are early days with FE so there will be little personal data on them yet. So this is a good time for some experimentation, especially as flashing stock is known to be successful.
zamzenos said:
Two possibilities why it's not working for you:
Try flashing TWRP with USB debugging off.
Are you placing the TWRP file in the right slot (AP) in Odin?
The last one is obvious, but it's strange that TWRP doesn't open for you.
Click to expand...
Click to collapse
I will try with USB debugging and I did place it in the AP slot
---------- Post added at 07:05 PM ---------- Previous post was at 06:13 PM ----------
still no go with usb bugging off,
a question that is the only twrp version that is working for you now right
iraqgsm said:
I will try with USB debugging and I did place it in the AP slot
---------- Post added at 07:05 PM ---------- Previous post was at 06:13 PM ----------
still no go with usb bugging off,
a question that is the only twrp version that is working for you now right
Click to expand...
Click to collapse
I used "twrp-3.1.1-0-gracelte.img.tar".
Are you formatting data? If you are, try flashing without allowing modifications and without formatting data. You won't be able to make use of TWRP in that mode, but try it and see what happens.
One last try: If the above fails, try entering stock recovery after you flash the stock firmware.
Finally, I have the K variant. It might be that the problem occurs because you have a different variant.
You could get the TWRP app (check the TWRP site). There is a specific version for korean telecoms (graceltekor). I've dloaded it and will give it a try tomorrow. But you should test the above suggestions first.
zamzenos said:
I used "twrp-3.1.1-0-gracelte.img.tar".
this version of twrp is newer than the one you have on the first post, it worked perfectly thank you
Click to expand...
Click to collapse
iraqgsm said:
zamzenos said:
I used "twrp-3.1.1-0-gracelte.img.tar".
this version of twrp is newer than the one you have on the first post, it worked perfectly thank you
Click to expand...
Click to collapse
Which version did you use? I've just flashed the korean version myself. No problems. I'm amending the OP to give people a choice.
Glad it worked for you. Hope this will encourage others to take the plunge.
Click to expand...
Click to collapse
zamzenos said:
I used "twrp-3.1.1-0-gracelte.img.tar".
Are you formatting data? If you are, try flashing without allowing modifications and without formatting data. You won't be able to make use of TWRP in that mode, but try it and see what happens.
One last try: If the above fails, try entering stock recovery after you flash the stock firmware.
Finally, I have the K variant. It might be that the problem occurs because you have a different variant.
You could get the TWRP app (check the TWRP site). There is a specific version for korean telecoms (graceltekor). I've dloaded it and will give it a try tomorrow. But you should test the above suggestions first.
Click to expand...
Click to collapse
zamzenos said:
iraqgsm said:
Which version did you use? I've just flashed the korean version myself. No problems. I'm amending the OP to give people a choice.
Glad it worked for you. Hope this will encourage others to take the plunge.
Click to expand...
Click to collapse
the twrp-3.1.1-0-gracelte.img.tar worked.
twrp-3.0.2-1-graceltexx.tar.md5 didnt work
honestly, it was easy thank you
Click to expand...
Click to collapse
iraqgsm said:
zamzenos said:
the twrp-3.1.1-0-gracelte.img.tar worked.
twrp-3.0.2-1-graceltexx.tar.md5 didnt work
honestly, it was easy thank you
Click to expand...
Click to collapse
There's a 3.1.1-0 version of the korean version (graceltekor) too. Use the new link I added to the OP. I've tried both today, now that I have a better idea of what is involved. Both work fine, seems to be no difference between them - I mean, for our purposes.
But it's really good to have full root. Honestly never expected it to be this good.
Click to expand...
Click to collapse
BerndausLB said:
Link is dead.
I have SM-N935K and need the stock firmware please.
Any help (working link) is highly appreciated.
Thank you.
Click to expand...
Click to collapse
Only link I had: http://fixedfirmware.blogspot.ie/2017/07/samsung-galaxy-note-7-fe-sm-n935skl.html.
Try this link (haven't tried this myself): https://www.androidfilehost.com/?fid=817550096634784008
Google for it otherwise. But you may be able to use one of the other variants. There was a discussion here. Not sure of the outcome, though.
These are just the steps I took and not my files and all credit goes to everyone except me.
You need ADB installed on your PC, this guide is assuming you have ADB up and running and know how to flash TWRP or other things to other phones. I don't have time to list all that.
You take full responsibility if something goes wrong.
I used a USB OTG because of TWRP decryption issues.
To start you need to be Sim unlocked from T-Mobile and received your unlock token from OnePlus, once that's done unlock your bootloader.
The files you will need are:
9.5.3 OTA full zip found here: https://forum.xda-developers.com/showpost.php?p=79545506&postcount=3
TWRP found here, I did not end up using the installer: https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322 I always rename it to twrp.img so it's easier/shorter to type in cdm later.
Transfer the 9.5.3 OTA zip to your USB OTG
Once your bootloader is unlocked you will need to boot the OS and enable developer options and USB debubbing,
From command prompt (CMD) on your PC type "adb reboot bootloader"
Once the bootloader loadds type "fastboot getvar current-slot" this will tell you which slot is currently active.
Then change to the inactive slot by typing "fastboot --set-active=a or b" so if your active slot was a then it would look like this "fastboot --set-active=b"
Now type either "fastboot flash boot_a twrp.img" or "fastboot flash boot_b twrp.img" based on which your inactive slot is. Thanks @twinnfamous
Once done TWRP should boot. Once in TWRP unplug from your PC and plug in your USB OTA swipe to allow modifications
Select install
Select storage from bottom
Select USB
Select the 9.5.3 OTA file you saved on your USB OTG, let it run (takes a few minutes) once done DO NOT reboot.
I did have a few errors but it was fine for me
Select the home button, once in the TWRP home screen select reboot and switch slots then back to TWRP home screen.
Select install
Select storage from bottom
Select USB
Select the 9.5.3 OTA file you saved on your USB OTG, let it run (takes a few minutes)
I did have a few errors but it was fine for me
Now you have 9.5.3 installed on both slots, reboot
At this point my phone boot looped back to stock recovery (TWRP was replaced, expected) where I selected English - Wipe data and cache - Erase everything (Music, pics, etc) once done my phone booted into International 9.5.3 OOS.
Again I take no credit for this I'm only posting the steps I took.
Thanks and credit goes to:
@twinnfamous for posting the steps he used and what I followed and this is based on.
@mauronofrio for the TWRP I used
What is the reason for flashing it to both slots? Does TWRP need to be installed or is it just used for initial install and then OnePlus's recovery will be used?
I'll just sit here and wait till the MSM Tool comes out!
TechOut said:
What is the reason for flashing it to both slots? Does TWRP need to be installed or is it just used for initial install and then OnePlus's recovery will be used?
Click to expand...
Click to collapse
it appears he just used it for booting, TWRP is not mandatory for an OS to operate, its just an option. He is flashing to both slots b/c if you get updates u won't get the T-MO update U will get the Global Updates. So when the update comes out it is going to install on the inactive slot so it will overwrite the Global instead of the T-Mo which could cause problems. So overall u want Global on both Slots.
So something weird when I was trying yesterday and not sure if someone came across that.
After I flashed oos rooted and was working just fine, while I was messing with substratum and magisk, the phone would boot, lose TMobile signal, and show the two empty simcards and won't get data.
I am finally back on 9.5.3 running just fine rooted but not sure what that has happened.
Bradl79 said:
it appears he just used it for booting, TWRP is not mandatory for an OS to operate, its just an option. He is flashing to both slots b/c if you get updates u won't get the T-MO update U will get the Global Updates. So when the update comes out it is going to install on the inactive slot so it will overwrite the Global instead of the T-Mo which could cause problems. So overall u want Global on both Slots.
Click to expand...
Click to collapse
Slots b/c? What phone are you using. it's a/b!!
se7ensde said:
Slots b/c? What phone are you using. it's a/b!!
Click to expand...
Click to collapse
"b/c" is a way to abbreviate "because"
se7ensde said:
Slots b/c? What phone are you using. it's a/b!!
Click to expand...
Click to collapse
lol its was short for because lol not the slots
What is the reason for doing this exactly? What benefits are there and specifically what are you hoping to accomplish ? I want to know because I also have the tmobile version.
TechOut said:
What is the reason for flashing it to both slots? Does TWRP need to be installed or is it just used for initial install and then OnePlus's recovery will be used?
Click to expand...
Click to collapse
If you are coming from T-Mobile software and don't flash to both slots you will end up in Qualcomm crash dump error. And not be able to boot
Spewed said:
What is the reason for doing this exactly? What benefits are there and specifically what are you hoping to accomplish ? I want to know because I also have the tmobile version.
Click to expand...
Click to collapse
When updates come out there is no waiting for them. You download from the OnePlus site and do a local upgrade.
Also the ROMs that are based on Magisk modules don't work on T-Mobile software.
matteosaeed said:
So something weird when I was trying yesterday and not sure if someone came across that.
After I flashed oos rooted and was working just fine, while I was messing with substratum and magisk, the phone would boot, lose TMobile signal, and show the two empty simcards and won't get data.
I am finally back on 9.5.3 running just fine rooted but not sure what that has happened.
Click to expand...
Click to collapse
What did you do to get back? I'm on international by another method and have this issue.
Beachbum2049 said:
What did you do to get back? I'm on international by another method and have this issue.
Click to expand...
Click to collapse
I tried a bunch of things, my highlight was the following
flashed twrp on slot A and B using "fastboot flash boot twrp.img"
Then downloaded the oxygen os OS 9.5.3GM21AA
https://support.oneplus.com/app/answers/detail/a_id/4312
Flashed that via twrp and my OTG usb. Regardless of decryption and data, all good.
Then, went to the oxygen os recovery "it flashes itself after you flash the oxygen os firmware instead of twrp" and erased everything and started fresh.
ALSO I am on this one now and it is working fine, and flashed via fastboot. Make sure you know your slots or pay attention to what happens.
" 9.5.4-GM21AA-OnePlus7ProOxygen_21.O.08_OTA_008_all_1905230032_1ef7fd0dc3-FASTBOOT.zip"
https://androidfilehost.com/?w=files&flid=294300
to find out which slot you're in
fastboot getvar current-slot
to change slots
fastboot --set-active=a
or
fastboot --set-active=b
then run to verify.
fastboot getvar current-slot
---------- Post added at 07:18 AM ---------- Previous post was at 07:18 AM ----------
Also, stay away from the firmware with the E in them "assume they are European and by default looks for the 2 sims, could be fixed in the future". happened to me when I was in 9.5.5
---------- Post added at 07:20 AM ---------- Previous post was at 07:18 AM ----------
Also to add after doing the 9.5.4 via fastboot, i flashed the magisk zip no problem. I am even on renovate ice with no problem on the 9.5.4 and flash magisk zip no problem.
https://forum.xda-developers.com/on...vate-ice-oxygenos-tweaks-stables-svn-t3934356
---------- Post added at 07:32 AM ---------- Previous post was at 07:20 AM ----------
Also,
my wifi was broken and flashed skydragon kernel and that fixed it.
matteosaeed said:
I tried a bunch of things, my highlight was the following
to change slots
fastboot --set-active=a
or
fastboot --set-active=b
Click to expand...
Click to collapse
This is where I made a mistake. Thank you for posting this!
Beachbum2049 said:
This is where I made a mistake. Thank you for posting this!
Click to expand...
Click to collapse
UW, let me know if you need more help. It is a little tricky. I believe that I am on Slot A and all working fine. It is nice having twrp to be able to change slots if for some reason I ended up on B.
matteosaeed said:
UW, let me know if you need more help. It is a little tricky. I believe that I am on Slot A and all working fine. It is nice having twrp to be able to change slots if for some reason I ended up on B.
Click to expand...
Click to collapse
Does TWRP stay installed or does it go back to the OnePlus recovery after both slots are flashed
TechOut said:
What is the reason for flashing it to both slots? Does TWRP need to be installed or is it just used for initial install and then OnePlus's recovery will be used?
Click to expand...
Click to collapse
Yes.
You can only flash the active slot.
You need to have twrp installed on both slots.
You want both slots to be on the same OS.
TechOut said:
Does TWRP stay installed or does it go back to the OnePlus recovery after both slots are flashed
Click to expand...
Click to collapse
If you flash OOS via twrp, then you get OOS recovery, you need to fastboot flash boot twrp.img on both slots, then it sticks. I am using the decrypted version.
Will this work if you are on T-Mobile 9.5.6?
likecookies said:
Will this work if you are on T-Mobile 9.5.6?
Click to expand...
Click to collapse
I don't see why not as it replaces the entire OS.
Similar to the previous threads for OnePlus 5, OnePlus 5T or OnePlus 6, here are the necessary packages to unbrick/revive a hard bricked OnePlus 7 Pro.
The following hardware revisions are supported:
GM1910: China
GM1911: India
GM1913: Europe
GM1917: Global/US Unlocked
Download: https://www.androidfilehost.com/?w=files&flid=294744
guacamole_21_H.04_190416_unlocked.zip
After using it, the phone will be restored to HydrogenOS aka Chinese firmware.
Click to expand...
Click to collapse
guacamole_21_E.08_190515_unlocked.rar
After using it, the phone will be restored to OxygenOS 9.5.4.GM21BA aka European firmware.
Click to expand...
Click to collapse
guacamole_21_O.07_190512_unlocked.zip
After using it, the phone will be restored to OxygenOS 9.5.3.GM21AA aka global firmware.
Click to expand...
Click to collapse
In every case, it is possible to upgrade to latest OxygenOS by using full signed zip from this thread via Local Upgrade.
With the device powered off, hold Volume Up & Volume Down buttons to force it to boot to Qualcomm download mode.
Use the most updated signed driver (2.1.2.2 at this moment) to avoid potential issues..
For detailed procedures, please consult the linked threads above. There is no reason to repeat the same thing again.
Make sure the path of the extracted files doesn't contain any non-English character. The tool isn't unicode aware.
Source:
HydrogenOS package: 人艱不拆 (OnePlus China forum thread), @trollavin & @Some_Random_Username for the help in mirroring
OxygenOS (EU) package: @MrVoshel
OxygenOS (global) package: @Lucifer6
Reserved for future.
Thank you for this!!
Doesn't this leave you with a Chinese modem (limited LTE bands and roaming configs?) and critical partitions? Wouldn't an international or European tool be more suitable considering that Oxygen zips may not overwrite everything? Or is this just a temporary guide with what we have?
LLStarks said:
Doesn't this leave you with a Chinese modem (limited LTE bands and roaming configs?) and critical partitions? Wouldn't an international or European tool be more suitable considering that Oxygen zips may not overwrite everything? Or is this just a temporary guide with what we have?
Click to expand...
Click to collapse
Temp? yes and no, I would say. Better than warranty R&D in days no phone for use.
As far as you can revive the phone from QDL9008 back to HOS/OOS, you now have a chance Again to switch over whatever ROM or OS you want later on.
jkyoho said:
Temp? yes and no, I would say. Better than warranty R&D in days no phone for use.
As far as you can revive the phone from QDL9008 back to HOS/OOS, you now have a chance Again to switch over whatever ROM or OS you want later on.
Click to expand...
Click to collapse
Well, that's the perfect explanation.
:highfive:
Can you turn TMobile to int'l with this ?
HtcOnekid said:
Can you turn TMobile to int'l with this ?
Click to expand...
Click to collapse
What he said
When i start MsmdownloadtoolV4.0.exe it says :
Packet image not exist!
Take out the Chinese characters in the file name and then try
joemossjr said:
Take out the Chinese characters in the file name and then try
Click to expand...
Click to collapse
Yep that's i though, but i finaly looking for EU version. Because i think with OTA upgrade to GMBA EU modem will not contain the good modem right ?
---------- Post added at 12:59 AM ---------- Previous post was at 12:27 AM ----------
failed to install on EU model : param preprocessing and stop at 5 ou 7 sec before flashing. I tryed using anothere patched tool and not working :s
Please help me, I failed pretty hard and bricked my phone.
I rooted my phone with stock recovery using a patched magisk boot image and all went fine.
Today, I deviced to temporarily boot into twrp to check it out, so I booted into fastboot and used "fastboot boot twrp.img"
and booted into system. I was confused and rebooted but now I was stuck in stock recovery. So I completely flashed TWRP
on boot_a and boot_b and into TWRP I rooted my device. But even now I am always bootlooping into TWRP and can't
get my phone to boot into system.
I tried using the unbrick tool but my device won't show up on my computer, even with the driver installed.
I'm screwed, can someone help?
Can I somehow reflash the stock recovery and revert back to my patched boot image?
uniQ191 said:
Please help me, I failed pretty hard and bricked my phone.
I rooted my phone with stock recovery using a patched magisk boot image and all went fine.
Today, I deviced to temporarily boot into twrp to check it out, so I booted into fastboot and used "fastboot boot twrp.img"
and booted into system. I was confused and rebooted but now I was stuck in stock recovery. So I completely flashed TWRP
on boot_a and boot_b and into TWRP I rooted my device. But even now I am always bootlooping into TWRP and can't
get my phone to boot into system.
I tried using the unbrick tool but my device won't show up on my computer, even with the driver installed.
I'm screwed, can someone help?
Can I somehow reflash the stock recovery and revert back to my patched boot image?
Click to expand...
Click to collapse
what is your device OOS 9.5.3/4/5/6 ?
flash the co-responding stock boot.img from twrp with magisk zip together, and see if you can boot
uniQ191 said:
Please help me, I failed pretty hard and bricked my phone.
I rooted my phone with stock recovery using a patched magisk boot image and all went fine.
Today, I deviced to temporarily boot into twrp to check it out, so I booted into fastboot and used "fastboot boot twrp.img"
and booted into system. I was confused and rebooted but now I was stuck in stock recovery. So I completely flashed TWRP
on boot_a and boot_b and into TWRP I rooted my device. But even now I am always bootlooping into TWRP and can't
get my phone to boot into system.
I tried using the unbrick tool but my device won't show up on my computer, even with the driver installed.
I'm screwed, can someone help?
Can I somehow reflash the stock recovery and revert back to my patched boot image?
Click to expand...
Click to collapse
You havn't bricked your phone, just put it in fastboot mode and reupload boot image to the correct slot !
Regards,
thebigtross said:
You havn't bricked your phone, just put it in fastboot mode and reupload boot image to the correct slot !
Regards,
Click to expand...
Click to collapse
Thanks for your replies! I was on OOS 9.5.5 and I tried flashing the twrp/magisk zips but that didn't work either. I also tried applying the stock boot.img to the active slot, but still got the recovery bootloop.
So as my last hope, I wiped all data in recovery mode, rebooted to fastboot and sideloaded the complete stock image from here https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
I reconfigured my phone from scratch, rooted with the patched boot image like before and everythings works now. Guess I will not bother with TWRP any time soon.
Added global and EU packages.
Titokhan said:
Added global and EU packages.
Click to expand...
Click to collapse
Will global work for 1911 (India)
Mr.Crucial said:
Will global work for 1911 (India)
Click to expand...
Click to collapse
Yes, the packages are interchangable.
[/COLOR]
Titokhan said:
Yes, the packages are interchangable.
Click to expand...
Click to collapse
But I think that these packages will not work on T-mobile 1915!
When I reboot into edl mode, it recognizes the "Qualcomm HS-USB QDLoader 9008", but then 10 seconds later, the phone automatically boots the the battery display, which disables edl. The same this happens whether I use the vol up+down and plug in, or `adb reboot edl`.
Edit: "How I learned to stop worrying and risk a brick"
Selecting the right COM and hitting start in MSMtool in that 10 second window kept it in edl mode for the duration of the flash.