Related
I was trying to install The paranoid custom rom 6.0.1 to my OPT when I started to running into an issue with boot looping. The phone would run through the bootup animation and then say it way starting up the apps. Once it was done with all the apps it would just start rebooting again. I tried to get into recovery to flash an old rom but I couldnt get in to recovery (holding the volume down and power button just turns the screen on and then back off.) I then tried this firstaid script I found on here that would supposedly install an older twrp and allow me to get into recovery mode, but that has not worked. And now I cannot even get the phone to go to a boot animation, it just sits on the oneplus logo. Adb is not detecting my device on windows or mac, but fastboot is working. At this point I have no idea of what to do, becuase even if I get into recovery I dont have a backup rom stored on my phone. If anyone has any ideas, I please share, I am in desperate need of help here.
Flash fastboot images search and follow naman's unbrick guide, skip the data partition to keep your files
Sent from my ONE A2005 using Tapatalk
1439soccerdude said:
I was trying to install The paranoid custom rom 6.0.1 to my OPT when I started to running into an issue with boot looping. The phone would run through the bootup animation and then say it way starting up the apps. Once it was done with all the apps it would just start rebooting again. I tried to get into recovery to flash an old rom but I couldnt get in to recovery (holding the volume down and power button just turns the screen on and then back off.) I then tried this firstaid script I found on here that would supposedly install an older twrp and allow me to get into recovery mode, but that has not worked. And now I cannot even get the phone to go to a boot animation, it just sits on the oneplus logo. Adb is not detecting my device on windows or mac, but fastboot is working. At this point I have no idea of what to do, becuase even if I get into recovery I dont have a backup rom stored on my phone. If anyone has any ideas, I please share, I am in desperate need of help here.
Click to expand...
Click to collapse
This thread will help you, https://forums.oneplus.net/threads/...wrp-root-nandroid-efs-backup-and-more.345478/
if you use twrp recovery and is not working on the Vol+ "-", try this way : RENAME your recovery file into twrp.img and flash it again.
If is not working,
following this thread first:
http://forum.xda-developers.com/oneplus-2/general/guide-official-op2-stock-reset-to-oos-3-t3402020
Then repeat my rename recovery method.
SOFT brick
You are a happy owner of a SOFTbricked OP2, happends mostly when you corrupt the partions. It easy to recover by Oneplus guide. You can use the link provided above by colleague on oneplus forum or this one XDA http://forum.xda-developers.com/oneplus-2/general/guide-unbrick-recover-oneplus-2-to-t3269543. GO step by step works 100%
Seimus said:
You are a happy owner of a SOFTbricked OP2, happends mostly when you corrupt the partions. It easy to recover by Oneplus guide. You can use the link provided above by colleague on oneplus forum or this one XDA http://forum.xda-developers.com/oneplus-2/general/guide-unbrick-recover-oneplus-2-to-t3269543. GO step by step works 100%
Click to expand...
Click to collapse
Or you could use the updated version by @fareed_xtreme that @qingmui linked to in the post just above yours
Spannaa said:
Or you could use the updated version by @fareed_xtreme that @qingmui linked to in the post just above yours
Click to expand...
Click to collapse
Indeed but i prefer to go back to the previous build as per I know its stable. I like to do rollback and then the update. So I can better isolate any new caused issue
I have searched, found and tested this rom.
It is a beta but it works very well, I leave the links of the original web where all the information of download and installation is.
I hope this humble contribution helps you.
web : http://getbest.ru/doogee_x5pro_nougat_beta.htm
TWRP : https://drive.google.com/file/d/0B3nYb3vN0P9VakpJWVU1Unh1NGc/view?usp=sharing
Flash Tool Firmware x32 : https://drive.google.com/file/d/0B3nYb3vN0P9VVGZvZlVIeEdQcG8/view?usp=sharing
Flash Tool Firmware x64 : https://drive.google.com/file/d/0B3nYb3vN0P9VVGZvZlVIeEdQcG8/view?usp=sharing
Super SU : https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.79-201612051815.zip
Hi, and thank you, I already had downloaded the BETA3 version from needROM.com but it seems this is updgraded
---------- Post added at 06:35 PM ---------- Previous post was at 06:33 PM ----------
Just a question, I have to use the Flashtool to flash the firmware and after that the TWRP and Supersu options?
I've been using beta4 (and beta3 previously) for months and quite like them. Also, since the original factory rom is filled with adaware, isn't as up-to-date with Android's security patches and doesn't pass SafetyNet, you're gaining a lot and not losing anything switching or rooting for that matter.
Though I still prefer magisk over rooting since it's more secure and more than enough for adaway.
juancarloscuba said:
Just a question, I have to use the Flashtool to flash the firmware and after that the TWRP and Supersu options?
Click to expand...
Click to collapse
You can but you don't have to. I had a problem flashing beta4 and twrp at one go but booting the phone once with just beta4 and then powering off and flashing twrp and\or rooting afterwards solved that.
Btw, the dev is developing gesture modules for the kernel (built-in beta4) and an app to go with them: http://getbest.ru/kernel_gesture.htm I didn't find the feature useful enough to keep around but it works as advertised and, once again, magisk was enough.
Overall, the rom is an absolute must as far as I'm concerned and I wouldn't be using this phone if it wasn't available. It would have been nice if the dev could keepup with android's patches better but seeing how he's doing a better job than doogee and for free I can't really complain.
Do the camera and fingerprint work?
Hi. I wish to give my really thanks to the developer of this rom.
It solve my problems:
Stock rom R16:
sim card WIND (IT) poor 4G/LTE reception
sim card VODAFONE (IT) no 4G/LTE reception
(tested switching 1-2, various city zones)
This Rom:
both full 4G/LTE reception!!
M.A.
Hello Maria and thanks for your experience.
What can you say to me about the fingerprint and camera functionality?
Do they work fine on this rom?
****_ve said:
I have searched, found and tested this rom.
It is a beta but it works very well, I leave the links of the original web where all the information of download and installation is.
I hope this humble contribution helps you.
web : http://getbest.ru/doogee_x5pro_nougat_beta.htm
TWRP : https://drive.google.com/file/d/0B3nYb3vN0P9VakpJWVU1Unh1NGc/view?usp=sharing
Flash Tool Firmware x32 : https://drive.google.com/file/d/0B3nYb3vN0P9VVGZvZlVIeEdQcG8/view?usp=sharing
Flash Tool Firmware x64 : https://drive.google.com/file/d/0B3nYb3vN0P9VVGZvZlVIeEdQcG8/view?usp=sharing
Super SU : https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.79-201612051815.zip
Click to expand...
Click to collapse
Can you please assist me with flashing this ROM? (either 32bit or 64bit) - I've tried using the Flash Tool guide, but with 32bit the clean install scatter file does nothing, and with 64bit the clean install scatter file comes up with error: "chip type not match!! target efuse value: 0xa4020000"
I've tried with and without battery, I have installed Android USB driver, and I've followed this guide: https://androidmtk.com/flash-stock-rom-using-smart-phone-flash-tool
Please help!
The Seeker said:
Hello Maria and thanks for your experience.
What can you say to me about the fingerprint and camera functionality?
Do they work fine on this rom?
Click to expand...
Click to collapse
Hi.
My phone (X5pro) hasn't fingerprint reader.
The camera seems to work in normal way.
M.A.
P.S.: May be it depends by my phone, but sometimes touch is not reponsive; I have to push the power button ("stand-by") and push it again to have normal touch response.
---------- Post added at 07:24 PM ---------- Previous post was at 07:19 PM ----------
Racxie said:
Can you please assist me with flashing this ROM? (either 32bit or 64bit) - I've tried using the Flash Tool guide, but with 32bit the clean install scatter file does nothing, and with 64bit the clean install scatter file comes up with error: "chip type not match!! target efuse value: 0xa4020000"
I've tried with and without battery, I have installed Android USB driver, and I've followed this guide: https://androidmtk.com/flash-stock-rom-using-smart-phone-flash-tool
Please help!
Click to expand...
Click to collapse
The flash guide you linked is the right guide.
What exact model of phone you have?
Does the scatter and other files are in the same folder? (unzipped, you know).
Does the flashtool give any error message with the 32bit version?
Regards
M.A.
I tried both the 32bit and 64 bit versions of this rom, it's pretty good for a beta. However I had a problem with the screen going dark while using it and once the screen inverted colours randomly. Has anyone else had this problem with this rom? I'm currently using the android 6 stock rom but would love to get 7.1.1 working perfectly.
installed with SP flash tools x5pro-7.1-x32-BETA4 from a stock kernel 6.0 (R16)
with no luck. At booting snowcatPDA logo shows for a while and continuously reboots.
Flashed from ubuntu linux 16.04:
Download Only option (should I have choosen Firmware Upgrade?)
Scatter-loading File MT6735M_Android_scatter-WIPE-CLEAN_INSTALL.txt (should I have choosen MT6735M_Android_scatter.txt?)
I had the bootloader locked in development options (had it to be open?)
I also had USB debugging ON
Any tips?
xe7um said:
installed with SP flash tools x5pro-7.1-x32-BETA4 from a stock kernel 6.0 (R16)
with no luck. At booting snowcatPDA logo shows for a while and continuously reboots.
.....
Any tips?
Click to expand...
Click to collapse
Hi.
Now I'm at home.
Tomorrow morning, when I'll be at office I'll write down steps by steps I did.
(home... office..., reverse of natural manner, because I do all my mobile hobbies at lunch pause; at home PC is used by others )
Hello, here I am.
The follows are the steps, more or less, that I did.
(maybe you already did some of these)
1-Start from official R16 ROM
2- Developer option
#a. Enable USB debug#b. Enable OEM unlock
3- Security: allow unknown origin installation
4- Unlock bootloader
#a. Connect in fastboot, from ADB command mode:type: adb reboot-bootloader ___ (Wait 1-3 second)type: fastboot devices ___ (verify device is detected)#b. verify bootloader unlock statustype: fastboot getvar all ___ and you get= warranty: yes= unlocked: no#c. unlock bootloadertype: fastboot oem unlock ___ and you get-> start unlock flow---> on screen appear:vol UP=Yes; void warranty, clear ALL datavol DWN=no; no unlockPress Vol UP#d. verify bootloader unlock statustype: fastboot getvar all ___ and you get= warranty: no= unlocked: yes#e. May be phone restart
5- shut down phone ___ AND ___ get out battery
6- Flash phone with
MT6735M_Android_scatter-WIPE-CLEAN_INSTALL.txtas per normal way (You know this , after some trying...)
7- WITHOUT starting phone, ___ Flash TWRP with
MT6735M_TWRPx32_scatter.txt (or the 64, according to the ROM you flashed)
9- Put battery in ___ AND___ start in TWRP recovery
#a. hold Vol Up, press ON button until appear a micro menu, release buttons#b. choose recovery with Vol Up and confirm with Vol Down
10- in recovery, choose wipe, and on bottom of the screen slide for factory reset
11- on TWRP main, choose reboot, power off
12- get out battery for some seconds
13- get in battery and start up (It can take a lot, may be leave the phone connected to main)
This is what I did (if I remember all the single steps...)
Try and report to us.
M.A.
Nope!, in step 9 when trying to start in TWRP recovery I get a continuous bootloop showing SnowcatPDA logo
xe7um said:
Nope!, in step 9 when trying to start in TWRP recovery I get a continuous bootloop showing SnowcatPDA logo
Click to expand...
Click to collapse
Hummmm....
It seems won't go in recovery mode, I think.
Try this:
1- flash entire stock ROM
(may be take this ===http://www.doogee.cc/bbs/viewtopic.php?t=29=== just in case)
2- start phone normal, up to home screen (so the phone is as just brougt)
3- power off and try to enter stock Recovery
If it works (and your bootloader is unloked) then try this
Connect phone to PC in fastboot
and enter
fastboot devices (I do this each time, just in case PC don't detect phone)
fastboot boot recovery.img
where recovery.img is your TWRP
The phone should start in TWRP recovery
The fastboot boot recovery.img command
send recovery (kernel?) image to temp phone folder/ram
and boot from that.
It unaffect normal rom/recovery.
By this step, we check If your phone accept this TWRP and sort out some possible troubles.
M.A.
when doing 'fastboot boot TWRP-3.1.1-X5PROx32.img' I get:
USB transferring...
USB transmission OK
and doesn't reboot into recovery but it boots normally
since I'm doing this from stock kernel R16 I wonder whether it's 32 or 64 bits
However I've found recovery-twrp-3.2.0-git-20171204.img that boots!. But I don't have scatter file, only .img! This recovery is from Lineage 14.1, but since this custom ROM installs from TWRP there is no need of scatter file
I've found another TWRP that boots with fastboot boot img: the TWRP recovery for 6.0 in needrom. This one has a scatter file
xe7um said:
I've found another TWRP that boots with fastboot boot img: https://www.needrom.com/wp-content/uploads/2016/12/TWRP_DG_X5Pro.rar
Click to expand...
Click to collapse
I get this error:
Needrom do not authorizing, the links referred by another website for download the ROMs.
The link must obligatory be clicked from of Needrom.com
Click to expand...
Click to collapse
Can you please link it correctly so we can download it?
The Seeker said:
I get this error:
Can you please link it correctly so we can download it?
Click to expand...
Click to collapse
Hi.
You have to select the file direct from the Needrom site.
www.needrom.com
(up)categories-doogee
on the right, click: Serial X
again, on the right, click: X5pro
and select the TWRP you desire.
(second line, second from left)
(click on "TWRP DG X5Pro (977 dls)")
Regards
M.A.
P.S.: even the link is
https://www.needrom.com/server/download.php?name=/2016/12/TWRP_DG_X5Pro.rar
you have to download from the site.
I'll try all this at the weekend, but my two cents are that it won't work. At first attempt I flashed BETA4 with MT6735M_Android_scatter-WIPE-CLEAN_INSTALL.txt (so no need to enter recovery and wipe cache/Dalvik) with a bootloop result.
My guess is that there are different ROM versions of X5 pro, and newest are incompatible with SnowcatPDA 7.1.1 firmware. Will see in a few days...
As I was suspecting I get a bootloop after logo. Now the question is: Is there a stable custom ROM (7.1 or newer) that I could use daily instead of MM 6.0 (R16) stock ROM?
So, erm, yeah, I made a big mistake...
A few weeks ago I bought an old Nexus 7 2012 (grouper) for just $5 on eBay, that was 'untested.' Long story short, it worked fine but was super slow, as expected, so I unlocked the bootloader, rooted it and installed TWRP. At this point, I was quite proud of myself since I'd never had the balls to root my own device before, so I got the unofficial build of Lineage 14.1 for Nexus 7, and flashed it to the boot in TWRP, which i still suspect i did incorrectly, but panicked when it wasn't booting, so because I'm a massive noob at this I flashed the Lineage boot file to the recovery too, which I later learned you aren't meant to do, so this brings us to the now. The device won't boot past the Google logo unless I press volume down and power, which gets me to the android laying down screen with the options at the side, I tried to enter Recovery mode but obviously because I flashed the boot file to the Recovery it wouldn't boot to TWRP, still on the Google logo. I tried connecting it to my PC but to no avail, as it would be recognised but not as a nexus 7, as a 'removable MP3 device'. I didn't factory reset from TWRP before flashing, not that that matters now. The only potential solution I could think of would be using command line in windows to reinstall the stock Rom or Lineage directly. Thanks in advance, and please can I have the responses in plain English with very simple instructions, as I'm new to all this! Thanks.
David_1276 said:
So, erm, yeah, I made a big mistake...
A few weeks ago I bought an old Nexus 7 2012 (grouper) for just $5 on eBay, that was 'untested.' Long story short, it worked fine but was super slow, as expected, so I unlocked the bootloader, rooted it and installed TWRP. At this point, I was quite proud of myself since I'd never had the balls to root my own device before, so I got the unofficial build of Lineage 14.1 for Nexus 7, and flashed it to the boot in TWRP, which i still suspect i did incorrectly, but panicked when it wasn't booting, so because I'm a massive noob at this I flashed the Lineage boot file to the recovery too, which I later learned you aren't meant to do, so this brings us to the now. The device won't boot past the Google logo unless I press volume down and power, which gets me to the android laying down screen with the options at the side, I tried to enter Recovery mode but obviously because I flashed the boot file to the Recovery it wouldn't boot to TWRP, still on the Google logo. I tried connecting it to my PC but to no avail, as it would be recognised but not as a nexus 7, as a 'removable MP3 device'. I didn't factory reset from TWRP before flashing, not that that matters now. The only potential solution I could think of would be using command line in windows to reinstall the stock Rom or Lineage directly. Thanks in advance, and please can I have the responses in plain English with very simple instructions, as I'm new to all this! Thanks.
Click to expand...
Click to collapse
Hi, David_1276...
Thankfully you didn't flash over the bootloader partition, because if you had, you would have a hardbricked Nexus 7 on your hands!
So, going off your description, you've overwritten the boot partition and/or the recovery partition with something that is not valid for either of those two partitions.
The easiest fix would be to simply reflash the Nexus 7 back to official Google factory stock, using fastboot. And then (perhaps) start afresh rooting it and maybe have another attempt at flashing Lineage. But the first objective would be to just get it booting properly again.
I'm assuming your PC/laptop is running some variant of Windows (I've no idea how any of the following would work with an Apple Mac or on a Linux system), and further, that your Nexus 7's bootloader is unlocked, as indicated by an unlocked padlock symbol at the bottom of the white Google splash screen upon boot.
Google Factory Stock Images
So, to reflash it back to Google factory stock, you'll need to download a factory stock image, which can be found at this link...
Nexus 7 WiFi only
https://developers.google.com/android/images#nakasi
There are two ways you can flash a factory image... You can either: just run the flash-all.bat file, which is part of the factory image, once unzipped... or unzip it (twice), and then flash each partition individually...
eg., this kind of thing...
Code:
fastboot flash bootloader bootloader.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
However, a note of caution...
If your Nexus 7's bootloader is already on v4.23, then I recommend you do not reflash it - reflashing the bootloader is the riskiest part of this procedure, 'cos should the flash fail in some way, eg. as a result of a dodgy USB connection for example, the bootloader could become corrupted and potentially hardbrick the device. The latest and last bootloader version is v4.23 and if your device is already displaying that version number in the bootloader
screen (lower left hand corner), there's really no point in reflashing it again. However, if the version number is lower than v4.23, then you will need to bring it up-to date. The risk isn't huge, and providing you don't nudge or disconnect the USB cable during the 5 seconds it takes to flash it, you should be OK - but if it can be avoided at all, then it should be.
*****
Custom Recovery ~ TWRP
Once you've successfully reflashed your Nexus 7 back to Google factory stock, and should you wish to root it again or flash a custom ROM such as Lineage, you'll first need to flash a custom recovery, such as TWRP. Since at this point you won't be rooted, you'll need to use fastboot for this.
You can find the download links (and instructions) for the Nexus 7 TWRP .img files at this link...
https://twrp.me/asus/asusnexus72012wifi.html
There are two download mirror links at this website, one for Europe and the other for America. Select the one that works best for you.
To flash TWRP, your Nexus 7 should be booted into fastboot mode, and from your laptop/PC, type this command...
Code:
fastboot flash recovery [name-of-twrp.img file]
I usually rename the rather lengthy TWRP .img file to something short, like twrp.img, so the fastboot command is much easier to type, and would look like this...
Code:
fastboot flash recovery twrp.img
*****
Fastboot and ADB
On the subject of fastboot, you'll need the fastboot and ADB binaries for all of the above... That is, if you haven't already got them on your computer.
You can get them from here...
https://www.xda-developers.com/google-releases-separate-adb-and-fastboot-binary-downloads
Unzip the file, and copy these binaries into a folder (eg., Fastboot and ADB tools) on your computer, somewhere on the desktop. Anything you wish to fastboot flash, such as a boot image or a custom recovery image, MUST go in the same folder as these binaries... unless you've added this folder to the Windows PATH variable, then it doesn't matter what folder .img files go in.
--------------------------------------
Well, I think I've covered much of the basics. Sorry I couldn't go into more details right now. There are two reasons for this. First, I haven't flashed anything on my own Nexus 7 for a couple of years, so I'm a little hazy about some of the specifics. The second reason is time - I never seem to have enough of it these days, and because of this, it maybe a few days before I can get around to answering any follow-up questions you may have. So please be patient if I don't immediately reply to you.
--------------------------------------
Anyway, have a read of some of the threads on this Nexus 7 forum which cover some of this stuff in more detail, and perhaps take a look at my own posting history regarding the Nexus 7. I always try to be as exhaustive as possible when responding to XDA members with questions not too dissimilar from yours, so you may be able to glean something that might fill in any blank spots I may have missed.
Good luck, and I hope you get your N7 up and running again soon.
Rgrds,
Ged.
Edit & Additional...
Just remembered - I forgot to include some instructions on how to actually run fastboot commands...
With your Nexus 7 booted into the bootloader (from a powered off state - long press VOL-DOWN and simultaneously press POWER-ON), and connected to your computer, move the Windows mouse pointer over the folder which contains the Fastboot and ADB binaries, and which should also contain any .img files you wish to flash, such as TWRP... Press SHIFT and right mouse click at the same time, then select 'Open Command Prompt Here' from the context menu. A command prompt window should open, and from here you can run fastboot commands as described previously. It's probably a good idea to first run...
Code:
fastboot devices
This command doesn't actually do anything, except to confirm you have a working fastboot connection between your computer and your Nexus 7. It does this by displaying your Nexus 7's unique serial number, so something like this...
019d2424b14050b fastboot
If a serial number fails to appear, you likely have a Windows driver problem, and proceeding with further fastboot commands without resolving it would be pointless. Hopefully this won't happen - let me know if it does...
I hate to barge in on someone else's thread but my searches have been so frustrating and gedblake is so knowledgeable that I could not resist asking a simple question.
I have an old working and rooted nexus 7 with twrp 3.xxxx installed and su. It is still on android 4.4.2 with kernel 3.1.10-g4776c68
I would like to update it to a stable but more recent android. So my question is:
—what is the most recent stable unofficial android available and where do I find the download files?
I am open to lineageos if there is a stable version available for the nexus 7 2012.
Thanks.
maybeme2 said:
I hate to barge in on someone else's thread but my searches have been so frustrating and gedblake is so knowledgeable that I could not resist asking a simple question.
I have an old working and rooted nexus 7 with twrp 3.xxxx installed and su. It is still on android 4.4.2 with kernel 3.1.10-g4776c68
I would like to update it to a stable but more recent android. So my question is:
—what is the most recent stable unofficial android available and where do I find the download files?
I am open to lineageos if there is a stable version available for the nexus 7 2012.
Thanks.
Click to expand...
Click to collapse
Hi, maybeme...
Hehe, flattery will get you everywhere... or so I'm told (just joking), but unfortunately, probably not on this occasion.
My Nexus 7, although it still works, largely just gathers dust these days. Even back in its heyday, 2012-2014, I rarely bothered flashing anything, other than factory stock when needed. I tinkered around with Xposed Framework for a short while and flashed some custom kernels, eg., Franco, but I quit doing all of that when the benefits appeared to be marginal, and then eventually I moved on to newer tablets and phones. So, I'm a little bit 'out of the loop', when it comes to the latest Custom ROMs.
So, I can only suggest you take a look here...
https://forum.xda-developers.com/nexus-7/development/rom-lineageos-14-1-nexus-7-2012-t3530261
And more generally, here...
https://forum.xda-developers.com/nexus-7/development
...if you haven't already done so.
Hope this is of some use to you, and that you find what you're looking for.
Rgrds,
Ged.
maybeme2 said:
I hate to barge in on someone else's thread but my searches have been so frustrating and gedblake is so knowledgeable that I could not resist asking a simple question.
I have an old working and rooted nexus 7 with twrp 3.xxxx installed and su. It is still on android 4.4.2 with kernel 3.1.10-g4776c68
I would like to update it to a stable but more recent android. So my question is:
—what is the most recent stable unofficial android available and where do I find the download files?
I am open to lineageos if there is a stable version available for the nexus 7 2012.
Thanks.
Click to expand...
Click to collapse
Sorry for the OT.
My N7 is running THIS ROM.
I find this ROM to be fluid and fast (well, fast for a N7 anyway). Much much better than the stock.
As Ged said, you will find many others in the link provided by him including LOS.
soliciting support, sorry for long post
never had to ask for help, rooted/cm/lineage/degoogled fdroid since 2012, linux user since 2005, salvaged many different devices for many people over the years using the knowledge base on xda. always been able to solve the problems by reading the forums. right now life is smacking me, and i just dont trust myself to find and recognize the info i need.
been running rooted los on op6 for 1.5 years. att kicked me off the network(volte)(twice, second time after playing the imei game and having volte), bought a used op6t a6013 fajita, figured the phone was so similar itd be easy to transfer. but life fried my brain.
op6t was running oos 10.3.12 when i received it. i fastboot installed twrp 3.5.2 img and installer, magisk 23, rebooted to oos. all good, root, recovery solid with oos 10.3.12
then wrecked my process.
went back into recovery, flashed oos flashable 10.3.5 (a downgrade) twrp 3.5.2, rebooted to recovery. flashed oos 10.3.5, realized i should be using mauronofrios twrp, flashed mauronofrio 3.4.0-11 fajita. rebooted to recovery, flashed oos 10.3.5 and mauronofrios 3.4xxx again. to get it on both slots. then did the same, los 18.1, mauronofrios twrp, on both slots, flashing magisk 23 after the second.
ended up with a soft brick, bootlooping lineageos recovery, which i never installed. phone was not readable in adb or fastboot by my linux box. messed around with virtualbox for awhile, but was unable to easily get it going with windows 10 for msmtools to restore stock. probably because im close to braindead.
decided to do a factory reset in lineage recovery before posting here and continuing with virtualbox config. factory reset, reboot system, what! lineage os 18.1 boots! linux adb and fastboot reads op6t when its in appropriate mode in lineage recovery!
i can now boot stock fastboot from advanced reboot lineage menu, but not with hardware buttons. although ive never been good with that, so its probably just me, i must have tried at least 100 times with op6t today. i can boot to lineageos recovery from advanced reboot.
currently running los 18.1 august 19 nightly, los recovery, on i dont know which slots with i dont know what firmware. terrified to do anything at all. maybe i should just be upgrading to 11. please help. i thought i was capable with the terminal. happy to post any outputs. goal is to run los, twrp and magisk.
on the level, xda has helped me save so many peoples phones over the years, keep them running and out of the landfill, keep them from having to buy a new one. this place is amazing. i never could afford to kick out the cash, but i figured i was doing my part by helping people learn, getting them into linux and cm/lineage, salvaging hardware for people who couldnt afford it.
a great big thanks for all yalls work, the devs especially but the users too. the person at this keyboard has read the words of hundreds of users about at least 20 different devices. an amazing place ;-)
live.edge.biped said:
soliciting support, sorry for long post
never had to ask for help, rooted/cm/lineage/degoogled fdroid since 2012, linux user since 2005, salvaged many different devices for many people over the years using the knowledge base on xda. always been able to solve the problems by reading the forums. right now life is smacking me, and i just dont trust myself to find and recognize the info i need.
been running rooted los on op6 for 1.5 years. att kicked me off the network(volte)(twice, second time after playing the imei game and having volte), bought a used op6t a6013 fajita, figured the phone was so similar itd be easy to transfer. but life fried my brain.
op6t was running oos 10.3.12 when i received it. i fastboot installed twrp 3.5.2 img and installer, magisk 23, rebooted to oos. all good, root, recovery solid with oos 10.3.12
then wrecked my process.
went back into recovery, flashed oos flashable 10.3.5 (a downgrade) twrp 3.5.2, rebooted to recovery. flashed oos 10.3.5, realized i should be using mauronofrios twrp, flashed mauronofrio 3.4.0-11 fajita. rebooted to recovery, flashed oos 10.3.5 and mauronofrios 3.4xxx again. to get it on both slots. then did the same, los 18.1, mauronofrios twrp, on both slots, flashing magisk 23 after the second.
ended up with a soft brick, bootlooping lineageos recovery, which i never installed. phone was not readable in adb or fastboot by my linux box. messed around with virtualbox for awhile, but was unable to easily get it going with windows 10 for msmtools to restore stock. probably because im close to braindead.
decided to do a factory reset in lineage recovery before posting here and continuing with virtualbox config. factory reset, reboot system, what! lineage os 18.1 boots! linux adb and fastboot reads op6t when its in appropriate mode in lineage recovery!
i can now boot stock fastboot from advanced reboot lineage menu, but not with hardware buttons. although ive never been good with that, so its probably just me, i must have tried at least 100 times with op6t today. i can boot to lineageos recovery from advanced reboot.
currently running los 18.1 august 19 nightly, los recovery, on i dont know which slots with i dont know what firmware. terrified to do anything at all. maybe i should just be upgrading to 11. please help. i thought i was capable with the terminal. happy to post any outputs. goal is to run los, twrp and magisk.
on the level, xda has helped me save so many peoples phones over the years, keep them running and out of the landfill, keep them from having to buy a new one. this place is amazing. i never could afford to kick out the cash, but i figured i was doing my part by helping people learn, getting them into linux and cm/lineage, salvaging hardware for people who couldnt afford it.
a great big thanks for all yalls work, the devs especially but the users too. the person at this keyboard has read the words of hundreds of users about at least 20 different devices. an amazing place ;-)
Click to expand...
Click to collapse
Hi,
I somehow bricked my op6t, but managed to recover it with this steps, which i will paste here, these aren't mine, copied to a txt file then here i will help you mate. After this process, you must restore IMEI, and AFTER THIS WHEN YOU WILL LOAD ANY OTHER OOS IT WILL APPEAR A MESSAGE: "INVALID NV's...."
Also i must specify that i had MODEM_A&B, MODEMST1&2 BACKED UP, I RESTORED THEM BUT THE "INVALID NV's...." persisted..... Good luck!
"The only solution is to use smt mode inside msmdownloadtool, which will restore persist partition, but with some disadvantages.
Be aware that you WILL LOSE YOUR IMEIs and WIDEVINE L1, use it at your own risk.
If you decide to do it (remember you WILL LOSE YOUR IMEIs and WIDEVINE L1!) follow this:
1.- Run MSMDownloadTool.
2.- Click on Verify and wait till it says "MD5 Check OK!".
3.- Then click on SMT Mode.
4.- Then click on Start like you would normally do with upgrade mode.
5.- The you need to enter as password "te123" and select your phone's capacity.
6.- If it says something like "Port disabled by user", go to the top left corner and click on "SMT", "COM Setup" and check everything, then click on the left button, and retry steps 4-5.
7.- When the process finishes the phone won't reboot, so you'll need to hold VolumeUP+Power until it powers on, then wait around 5 minutes and your phone will be back to life!!
8.- If you have an IMEI backup, just follow this guide (https://forum.xda-developers.com/oneplus-6t/how-to/guide-oneplus-6t-unlock-bootloader-t3851789) (I don't know if this is the correct way to post links)
I hope you get your phone fixed.
--------------------------------------------------------------------------------------------------
Restoring an EFS Backup?
If by chance you end up with a corrupt EFS partition all you need to do is flash the files back to your device using fastboot.
Boot into fastboot mode (power + volume up) and connect your phone to your PC via usb cable.
Keep modemst1.bin and modemst2.bin (backed up earlier) on your desktop and open command window there.
These fastboot commands will restore the files:
Code:
fastboot flash modemst1 modemst1.bin
Code:
fastboot flash modemst2 modemst2.bin
Reboot your device.
Code:
fastboot reboot
Now disconnect phone from PC. Your IMEI should be back.
------------------------------------------------------------------------------------------------------------------------------------
Making an EFS Backup
?
All too often, we've seen folks who have a corrupted or missing EFS Partition. This results in your IMEI being lost and no cellular activity on the device at all. This can be a royal PITA to fix, and some folks haven't been able to fix it at all. You can take a precautionary measure to safeguard yourself against this by taking a couple of minutes to back up your modemst files.
Download & Open up Terminal Emulator on your phone from here
Once it's open you'll be greeted with a command line prompt, in which you can enter text commands, the first thing you need to do is enable root access by entering this line (press the enter key on your on-screen keyboard after each command to issue it):
Code:
su
If this is the first time you've used Terminal Emulator a Superuser or SuperSU popup will appear, make sure you grant root access.
Now enter these two commands:
Code:
dd if=/dev/block/sdf2 of=/sdcard/modemst1.bin bs=2048
Code:
dd if=/dev/block/sdf3 of=/sdcard/modemst2.bin bs=2048
This will place two files (modemst1.bin & modemst2.bin) on your internal storage.
Make sure you copy them to your PC and Cloud immediately so that you have a backup there to use if you need to restore it in future.
That's it !! In case you ever need to restore Nanroid or EFS Backups, please continue and follow the next post..."
Recently, I purchased a TicWatch Pro 2020 (saw that Kali Nethunter now seems to work on it and I thought it could be a cool device to add).
I have installed nethunter onto several other devices already (Nexus, OnePlus, etc.) and of course ran into issues. Usually I spend a long time on them and it is fun to do it. But I seem to have run into a wall recently with the watch.
When I was first trying to set up the watch, I could send commands with adb to get it into the bootloader menu but then it would not recognize it. I did eventually get the right drivers installed and had my VM recognize the watch with the ADB drivers.
I did manage to complete Step 1 of the tutorial https://www.kali.org/docs/nethunter...-on-the-ticwatch-pro/#1-unlock-the-bootloader
(unlocking it).
I went through to step 2, put it into bootloader again and flashed the vendor and twrp .img files. Once I did this, I tried to switch the device into recovery mode (after it went back to the bootloader menu on its own) as per instructions. But the weird thing is when I initialized recovery mode, it just sent me back to the bootloader menu, all while also not recognizing it on my VM/PC at all. When I tried to start the watch, it just sent the device into a permanent loading loop (after showing the logo and cycling the 4 different colored Google dots around the watch). I can get it back into the bootloader menu by holding both buttons down but I can't get my device to be recognized with a data connection (so it seems effectively bricked).
Normally I look this up myself but since there is not much information regarding this device and this specific rom out there just quite yet, I can't locate anything (compared to troubleshooting the OnePlus 7 Pro). Any ideas or input is appreciated!
Edit: will just let it run over night (drain battery to see if it may or may not help).
Thought I would leave a quick update in case you may be running into this issue yourself.
I let it run over night and run out of power to see if it would do anything. It now seems to be recognized by my pc, but it would not connect. I am installing everything through a VM but it appears that the PC could not recognize the device (I only had drivers installed on my VM, not my main device). When I installed the drivers on my main desktop it began to recognize it again on my VM. Not sure why this was an issue or how it became one or if it was a combination between everything but now at least I can send adb and fastboot commands to my watch again. Will try to flash a stock rom for it and try again to get out of the boot process (still confused as to why it will not go into recovery mode but it instead goes back into boot loader mode when I select it)...
Another update: I managed to find a stock image and some simple instructions. Credit to @sonnettie as it looks like it is working atm (going through setup).
Link: https://forum.xda-developers.com/t/ticwatch-pro-2020-stock-image.4107539/
Going through to try installing nethunter again if it appears to be fully functioning.
Edit: Using the stock image seems to let me now use my watch again. But whenever I try to install Nethunter, I install the vendor and recovery image. Once I do this and try to go into recovery mode, it just seems to bring me back to the boot loader menu. Anyone have solutions or know what is wrong?
i got nethunter and twrp working on the ticwatch 2020, it was a pain finding the right files to use and i soft bricked my watch many times in the process.
https://forum.xda-developers.com/t/...shark-4g-ticwatch-c2-skipjack-9aug20.3821013/ this post has the right vendor.img and twrp recovery image, in particular this mega folder https://mega.nz/folder/cVVBRaxL
1-Vendor-Images-22-Jun-2020.zip unzip this file it is located in TicWatch-Pro-2020(Catfish-ext)/Custom-ROM/ROM/22-Jun-2020 it contains the vendor.img you'll need
tic-watch-pro-2020-twrp.img in TicWatch-Pro-2020(Catfish-ext)/Custom-ROM/TWRP this is the TWRP Recovery.img you'll need
Magisk-v21.0.zip and nethunter-2022.2b-ticwatchpro-wearos-kalifs-nano.zip are both needed from the TicWatch_Pro_NetHunter_files.zip at https://build.nethunter.com/contributors/re4son/catfish/
1) Enable ADB and unlock bootloader then enter these fastboot commands on pc
fastboot flash vendor.img
fastboot format userdata
fastboot format cache
fastboot flash recovery tic-watch-pro-2020-twrp.img
2) Reboot into WearOS and Setup Watch
3) Enable ADB again and reboot into recovery
adb reboot recovery
4) move Magisk-v21.0.zip into the TWRP folder on the watch
install Magisk-v21.0.zip from TWRP recovery (it'll patch the boot.img itself)
5) Enable ADB Sideload from the Install menu in TWRP
adb sideload nethunter-2022.2b-ticwatchpro-wearos-kalifs-nano.zip
6) Reboot into wearOS with kali splash screen, you will have to open the magisk app after you open the nethunter app to give it root as there isn't a proper pop-up screen to give root access
**circle screen does semi cut off a few buttons in the nethunter and magisk apps, touch your watchface close to the "corner" where it is to select it
I hope this all helps! Cheers mate
unidentifieduser said:
Another update: I managed to find a stock image and some simple instructions. Credit to @sonnettie as it looks like it is working atm (going through setup).
Link: https://forum.xda-developers.com/t/ticwatch-pro-2020-stock-image.4107539/
Going through to try installing nethunter again if it appears to be fully functioning.
Edit: Using the stock image seems to let me now use my watch again. But whenever I try to install Nethunter, I install the vendor and recovery image. Once I do this and try to go into recovery mode, it just seems to bring me back to the boot loader menu. Anyone have solutions or know what is wrong?
Click to expand...
Click to collapse
i just realized i typed all the above and didn't reply to your message, it was a mixture of two install methods with leaving out the flashing of the rom file itself