I need some additional minds; transferring file between phones - Nexus 6P Q&A, Help & Troubleshooting

I've got a 6p running mostly stock, and I need a way to get a file to a 5x that's bootlooping. I'm in San Francisco for a.. Um.. Holiday today. And I don't have my laptop. I found a few threads that had an adb/fastboot binary that you could run on a terminal emulator on Android but of course they're not compiled for arm64. I've got the USB c cable, so I can connect the phones physically but I can't seem to find a way mount either as otg. The 5x has twrp, sadly no backups. Trying to fix it for a friend. If anyone has any ideas, I've gone through just about everything I can think of. We're not going to be home until way late tonight and my friend is really sad about not having a phone for our holiday trip.

Morganmachine91 said:
I've got a 6p running mostly stock, and I need a way to get a file to a 5x that's bootlooping. I'm in San Francisco for a.. Um.. Holiday today. And I don't have my laptop. I found a few threads that had an adb/fastboot binary that you could run on a terminal emulator on Android but of course they're not compiled for arm64. I've got the USB c cable, so I can connect the phones physically but I can't seem to find a way mount either as otg. The 5x has twrp, sadly no backups. Trying to fix it for a friend. If anyone has any ideas, I've gone through just about everything I can think of. We're not going to be home until way late tonight and my friend is really sad about not having a phone for our holiday trip.
Click to expand...
Click to collapse
If it's a file on the actual device as in not part of an app, couldn't you just flash a rom to it, then you'll have access.
Then send it via the device.
If they've got TWRP on the device then i'm assuming that they have rom's on there too.
To be honest all you need is any computer / laptop to mount it from within TWRP, go to an internet cafe, library, computer shop.
It's going to be a lot easier with a computer, I'm sure San Francisco has internet cafes.

I have a similar issue with a dead USB port on my N6P. I received my RMA I have been beating my head against the walk trying to figure out how to return the old one back to stock. However, with TWRP you can ADB which is a good thing! In the latest version of TWRP you should be able to mount OTG under the mount options. Although the version of ADB i've found don't support arm64 the versions of fastboot included DO work. So reboot to bootloader and try that. I would suggest AFTER downloading the factory img for the 5x.

Related

Epic stuck in ClockworkMod v2.5.1.0 and won´t connect to pc

I spent all day yesterday trying to fix my Epic with no progress and feeling a little sol.
Yesterday I decided I needed a new ROM/kernel because I was averaging only 4hrs of battery life with Supernova and wanted to try Nebula ROM with EXT4. I backed up everything on my laptop and did a Nandroid backup as well. I also have Titanium backup backed up on my pc. I always always back up. I started fresh by flashing to stock and starting over. I rooted with 1 click, flashed DK28, and where I believe I screwed up is I didn´t upgrade to Clockwork 3 (looking back I don´t know wtf I was thinking by proceeding the following way), instead I went to advanced, reboot recovery and ended up rebooting my system into 2.5.1.2. I rebooted my phone and all was good, powered off, 3 fingered and I still had 2.5.1.2 so like a dumbass I figured I was good to go ahead and flash Nebula. LOL so what happened? the Rom installed, I finished like I always do and when I went to boot up my phone I flashed into v2.5.1.0 and thats where my phone stays. If I try to do anything it gives me E: Can´t open/cache/recovery/log
I tried to restore of course and I get this message. I have tried to Odin back to stock but my phone will not connect to a pc.
Heres my situation. I live in a house with 6 computers that I have attempted to connect to with no luck, 5 of these have adb and the Android SDK, several drivers (including the Epics) installed and the C drives have literally no more space. The other pc has Windows 2000 so I wondered if it won´t install the drivers or pick up my phone because its so old??? My main laptop is running Ubuntu and Im not understanding how or even if I can Odin my phone on it, besides I think this laptop won´t connect to my Epic because of the USB port and I dont have a clue how to detect or fix that. My mom has a brand new PC with Windows 7 thats never had anything connected via USB yet that I thought was worth giving a shot at. I only have the stock USB cable though and I was wondering if I bought a new cable if it would be more likely that my phone would connect.
I am not very educated on Android or computers so I prob shouldn´t have done as much flashing as I have to begin with. If I understood file systems better I would prob figure it out.
Thanks for any help or advice. If I over looked the answer in front of my face I am sorry it is because I am retarded and don´t understand computer lingo.
Are you connecting the proper way to odin?
Step 1: open odin with phone Disconnected from PC (if you dont open it first it may not recognize your phone, so i hear)
Step 2: hold 1 on keypad and power on phone --> download mode
step 3: connect phone to PC
step 4: Flash rom
if odin still isnt recognized I would suggest taking out your microsd card and put it in another phone or a microsd card reader and put a basic dk28 rom/dl18 (maybe the acs one that includes modem) rom on there then put the sdcard back in your phone and flash that in clockworkmod and see if it'll boot (wide data/cache/dalvik before doing this)
Also search the forum i'm pretty sure theres an RFS formatter somewhere that'll format your /system/data/cache back to RFS, you probably need to do that before flashing back the other rom...
So, if I understand the OP correctly, you accidentally flashed an ext4 only rom on rfs with 2.5.1.0?
This thread had a flashable reRFS conversion, just in case you need it.
This thread has a cwm flashable di18 and modem.
Those should get you up and going again with cwm 2.5.1.0. If they don't, Odin is really the answer and I don't know what to tell you.
So I tried both of your ideas and I am so pist off. I am now stuck in download mode and cant get 7 freaken computers (one literally brand new with Windows 7, one with Vista, one with XP, 3 with Linux, 1 with 2000 out of being desperate with 5 different usb cords to connect. Clearly my phone is the problem because the sd reader can read my sd just fine and my mom, sister and gramps connect o the same computers just fine. Ive accepted that I am ****ed at this point. I have never got this phone to stay connected to a pc and I think I hate it.
It is starting to sound like it is time to head to a sprint store.
Erica8123 said:
I am now stuck in download mode and cant get 7 freaken computers (one literally brand new with Windows 7, one with Vista, one with XP, 3 with Linux, 1 with 2000 out of being desperate with 5 different usb cords to connect.
Click to expand...
Click to collapse
Have you tried to just pull the battery out? Then, put it back in the phone and boot into CWM? Or pull the battery, then boot into recovery? I personally hate going to the Sprint store and I try every possible option before going.
If you can get another USB cable it will probably work. I use an evo cable. Also for future reference there are no custom kernels on dk28.
Sent from my Evo Killer!!!
Hey, I just wanted to update.
I had tried several usb cables to connect btw including a new one I just bought. No luck. I had tried literally everything to fix my Epic and I was super pist during my last post lol. I finally had to cave and take the block walk (literally) down to Sprint and thank God I insured my phone. He was hella cool about it, just laughed and said he doesn't want to bother with it and replaced it. I am still trying to decide what I wanna do as rooting goes (besides getting rid of pretty much every app they put on there).
Thanks again everyone

Need root without computer, bootloader unlocked...

I have checked at least hundred threads now, but my problem seems unique! (First time this happened to me )
When I connect my N7 (WiFi, 32 GB) to my laptop (Win 8.1), it says "USB device not recognized - The last USB device you connected to this computer malfunctioned, and Windows does not recognize it." In Device Manager, it is like the image attached, no other recognition for the device. Upon selecting Properties, It says "Code 43" in status, also says "A request for the device descriptor failed". That happened with 2 computers; I used 2 cables (both worked previously). So it means N7's USB port is somehow malfunctioning. But it gets charged as well as ever!!
This started after I tried an OTA update of 4.4 earlier (the download had not completed, but a prior small update (1-3 MB) was installed).
Now, I have Android SDK (latest version) and installed those google USB driver and platform-tools. I have NRT 1.7.9 (which worked for me previously). But I cant get my N7 to answer to ADB requests. [highlight]Upon connecting USB, it says "Charging (USB)" but no option regarding PTP or MTP appears.[/highlight] I have developer tools installed. I followed the instructions given in NRT about ADB installation to the letter but still no progress. I have tried a factory reset too.
BTW, I dont have a custom recovery flashed. It vanished along with the precious root privilage.
Now the N7 is in Android 4.3 (JWR66Y), bootloader is unlocked, SuperSU is Installed (but do not work due to having no root access and I cant even Uninstall it for the same reasons!!!). Now the OTA update also do not work mysteriously (it downloaded the 4.4.2 update and went on to install it, but as the bar started filling, it only said "error" and stopped!!! no explanations whatsoever!!!!). I will be very happy any of the followings:
[highlight]1. root without computer (wireless ADB is also welcome),
2. working OTA, or anyhow the 4.4.2 update
3. working ADB connection with my laptop.[/highlight]
Any help will be very helpful... Thank you in advance...
If you can not communicate via USB hardware, then using fastboot is not an option (obviously). And so therefore the lock state of your bootloader is quite irrelevant, too.
Even if you were to get adb over tcp (WiFi) working, that doesn't get you much, as an adb login shell on a stock ROM is just an unprivileged user; it's not much different from using a terminal emulator app (from a privilege escalation point of view).
The only other thing left is an exploit (privilege escalation) method that runs under the stock ROM. Something similar to that Motochopper exploit from some time ago. I suppose that particular hole was plugged; whether or not a new exploit exists, I can't tell you.
You could always just send the tablet back for repair. Seems like not having a working USB port is pretty crippling to someone who wants to root, flash ROMs, copy backups off the tablet, etc.
Thank you for the replying...
Actually I lack warranty as I bought this from eBay weeks before it was officially available in India. Therefore I kept that repair thing as a last resort. I am now trying it through Linux. And being a noob there, its going too slow. However I have got the ADB working and detecting the device, so its not a port issue (I dont know why the hell windows was so adamant on that point!)... But I am yet to figure out how to flash the image... thank you for the tip over wi-fi, i was actually hoping to wait for it...
Aaron061992 said:
Thank you for the replying...
Actually I lack warranty as I bought this from eBay weeks before it was officially available in India. Therefore I kept that repair thing as a last resort. I am now trying it through Linux. And being a noob there, its going too slow. However I have got the ADB working and detecting the device, so its not a port issue (I dont know why the hell windows was so adamant on that point!)... But I am yet to figure out how to flash the image... thank you for the tip over wi-fi, i was actually hoping to wait for it...
Click to expand...
Click to collapse
Well that is very different than having a broken USB port.
You probably noticed in your search that this forum is littered with thousands of reports from users complaining about their Windows drivers. It gets pretty old, frankly. (No drivers are needed at all for Linux or Mac OS/X).
Here is a suggestion that I made in another thread just a few days ago about using fastboot under Linux - in your case, you will be on your way after installing a recovery, e.g.
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.1-grouper.img
I even attached the most recent version of the (Android SDK Linux) fastboot to that post.
Note that you don't even need a dual-boot PC or PC with a semi-permanent Linux install; you can do the whole thing with one of those "Live CD" boots and a USB stick.
good luck

[Q][Answered] Have I screwed up? (Fastboot not seeing the Tablet)

Okay, I bought a Nexus 10 off someone, and they had already rooted the device. Bootloader is unlocked and whatnot. That's where my problems start. I can not for the life of me get fastboot or adb to see this thing.
Here's my info:
Google Nexus 10 (Samsung)
ClockworkMod Recovery 6.0.4.3
Bootloader Version: MANTALJ12a
Windows 8.1 Pro x64
Full Android SDK
Samsung drivers installed (I rooted my Galaxy Nexus without issue).
USB has a direct connection
Before I decided to format and try to install a stock .zip, I could access the tablet as a media (That's how I got the .zip on the device).
Steps to how I got here:
Flashed Cyanogenmod 10.2 or whatever. Didn't want JB, wanted Lollipop.
Pushed the (what I thought was correct) .zip to /sdcard
Booted into recovery
Formatted /system, /cache, /data, /factory
Reflashed the .zip
Failed. Miserably.
I named the .zip as something simple and just overwrote it. I wouldn't have this issue if it wasn't for that. I know I did a bad there.
But still, nothing I can do will get fastboot/adb to see the device. It makes the sounds that it's connected when I plug it in. I'm using an elevated prompt as well, but it will not pull the device. How do I get myself out of this hole? If I could push a new .zip to somewhere on /sdcard I could at least use the recovery to reflash.
Wrong device ? [emoji14]
Khaon said:
Wrong device ? [emoji14]
Click to expand...
Click to collapse
No, I was going to put it in the general help thread, may be better here since this may not be a simple question (Please prove me wrong).
Some additional things I've tried:
The NExus Root Toolkit. Removing all drivers etc. Still getting to fastboot by PWR+ VOL+ + VOL-.
Still nothing. Should I go to my wife's computer and try it there? I might do that anyways.
gothmog1065 said:
Some additional things I've tried:
The NExus Root Toolkit. Removing all drivers etc. Still getting to fastboot by PWR+ VOL+ + VOL-.
Still nothing. Should I go to my wife's computer and try it there? I might do that anyways.
Click to expand...
Click to collapse
You don't have access to have os then? How did you push your zip if you don't have access to adb?
I have seen people who couldn't get adb and fastboot working on their windows and switching to another computer solved the issues.
Ok, make sure to make a full clean of your drivers. Wug toolkit explain how to. Then install proper samsung driver and this
If it is not a hardware's problem, you should have access to fastboot & adb. You might try on another computer if possible. A clean one would be the best (i.e. never used any droid devices, etc.).
Another workaround would be to use and otg cable and an usb drive with any zip of your liking.
Another one, I had an issue long time ago, similar, I had to flash through odin in downloading mode to fix my problems.
BUT did you really deleted /factory partition? It contains various proprietary files needed for the device to work. Well concerns more devices with imei and stuff to allow 3g connection and co. Might have no incidence tho on your device's behavior.
Khaon said:
You don't have access to have os then? How did you push your zip if you don't have access to adb?
Click to expand...
Click to collapse
Sorry if I wasn't clear on this, I have 100% access to my computer. I have the Android SDK installed, and adb/fastboot commands working in command prompt. They're just not seeing the tablet.
Ok, make sure to make a full clean of your drivers. Wug toolkit explain how to. Then install proper samsung driver and this
Click to expand...
Click to collapse
Yeah, that's one of the steps I did. Followed the Wug toolkit and removed everything. Still not seeing the tablet.
If it is not a hardware's problem, you should have access to fastboot & adb. You might try on another computer if possible. A clean one would be the best (i.e. never used any droid devices, etc.).
Click to expand...
Click to collapse
Yeah, seems to be doing the same on my wife's computer (Win 7 HP, never had my phone/tablet hooked to it). I get adb/fastboot loaded and working in the command prompt, and it registers when I plug in, but neither command will "see" the tablet.
Another workaround would be to use and otg cable and an usb drive with any zip of your liking.
Another one, I had an issue long time ago, similar, I had to flash through odin in downloading mode to fix my problems.
BUT did you really deleted /factory partition? It contains various proprietary files needed for the device to work. Well concerns more devices with imei and stuff to allow 3g connection and co. Might have no incidence tho on your device's behavior.
Click to expand...
Click to collapse
It's a Wifi tablet, no cellular data and IMEI etc.
edit: As a side note, I've been thinking about reformatting my computer, though it'll be a huge pain to get it back to here as I've got to go from 7 - 8.0 - 8.1 on the upgrade paths to get it back here again.
gothmog1065 said:
Sorry if I wasn't clear on this, I have 100% access to my computer. I have the Android SDK installed, and adb/fastboot commands working in command prompt. They're just not seeing the tablet.
Click to expand...
Click to collapse
From my own experience, having similar issue with the windows drivers for adb, but eventually I fixed it. I really doubt you are screwed.
adb version output ? 1.0.32 is latest.
Yeah, that's one of the steps I did. Followed the Wug toolkit and removed everything. Still not seeing the tablet.
Click to expand...
Click to collapse
Installed universal adb drivers? Nothing shows up in the device manager?
Yeah, seems to be doing the same on my wife's computer (Win 7 HP, never had my phone/tablet hooked to it). I get adb/fastboot loaded and working in the command prompt, and it registers when I plug in, but neither command will "see" the tablet.
Click to expand...
Click to collapse
You might try odin.
Usb mtp doesn’t work from recovery?
Khaon said:
From my own experience, having similar issue with the windows drivers for adb, but eventually I fixed it. I really doubt you are screwed.
adb version output ? 1.0.32 is latest.
Installed universal adb drivers? Nothing shows up in the device manager?
?
Click to expand...
Click to collapse
Android Debug Bridge version 1.0.32, yep latest.
I just feel like I'm missing something, maybe something stupid. HOWEVER, I'm now getting my nexus 10 to show up in device manager with a ? on it. Already tried the direct Samsung drivers, the universal drivers in the Wug toolkit.
gothmog1065 said:
Android Debug Bridge version 1.0.32, yep latest.
I just feel like I'm missing something, maybe something stupid. HOWEVER, I'm now getting my nexus 10 to show up in device manager with a ? on it. Already tried the direct Samsung drivers, the universal drivers in the Wug toolkit.
Click to expand...
Click to collapse
Did you deleted all samsung vendor, etc from the usb program, you know what i am talking about?
You can force to install drivers from device maanger, don't remember how, when installing manually, you must do some step , install from floppy or file, get inf files or so, you will get a prompt telling you it might be harmfull and it will force installation. Might be the solution?
The culprit is definitely software-sided.
Does the mount internal storage (mtp) work?
Would this be easier in Linux? I could pop open my Ubuntu VM and do this if it'd be easier?
Beyond that, are you telling me to try and install the drivers from the driver files created by the Samsung vendor .exe?
I have tried to 'mount USB storage' from recovery, but it doesn't seem to do anything. /system /cache /data /factory are all mounted ATM and nothing is showing.
You've already got more advanced advice than I can offer but when I tried to update to 5.0.1 from 4.4.4, I couldn't get my windows computer to see my device. I was trying the adb fastboot but it I couldn't get it to work.
Wug's toolkit got it all straightened out (http://forum.xda-developers.com/showthread.php?t=2015467)[*]. There was an option on his interface that asked whether the device was working properly or not (a!most missed it as a choice). Checked that box and it went through much of the process I had done (installing adb, updating drivers etc). Long story short, it worked.
Where did you see this option? The only thing I see is the Soft Brick/Bootloop option where it will install the factory again. Was it that or somewhere else?
I swear to the Android droid that I tried that before. That seems to be doing what needs to be done, holy crap thanks!
e: I would like to know, however, why fastboot/adp wouldn't work but this would without doing any of the other stuff?
gothmog1065 said:
Where did you see this option? The only thing I see is the Soft Brick/Bootloop option where it will install the factory again. Was it that or somewhere else?
I swear to the Android droid that I tried that before. That seems to be doing what needs to be done, holy crap thanks!
e: I would like to know, however, why fastboot/adp wouldn't work but this would without doing any of the other stuff?
Click to expand...
Click to collapse
You're right. I confused the heading but choosing that option got my computer and my Nexus "talking." After installing the factory image I think you can then push a cusom ROM to you Nexus (http://forums.androidcentral.com/go...acks/264619-wugs-nexus-toolkit-questions.html).
gothmog1065 said:
Where did you see this option? The only thing I see is the Soft Brick/Bootloop option where it will install the factory again. Was it that or somewhere else?
I swear to the Android droid that I tried that before. That seems to be doing what needs to be done, holy crap thanks!
e: I would like to know, however, why fastboot/adp wouldn't work but this would without doing any of the other stuff?
Click to expand...
Click to collapse
Problem solved ? I always had less issues with fastboot and adb on Linux you can install a ppa that install for you adb and fastboot
Hovewer if you are using 2.8.2.0 you will need 1.0.32 and the ppa includes 1.0.31 so only adb sideload fails.
Sent from my nexus 10

hard, or possibly soft bricked sm-t230 tab 4 7.0. please help!

Hi y'all, i recently within the last month 2 months taken up a very unsual craving for delving deeper into my technology, with that being said. my tab 4 7.0 sm-t230 i Downloaded an app called "lucky patcher" was messing with it, been reading about deoxe(ing) my tablet,it gave me the option to do it for me (usually i enjoy the challange of using a emulated terminal and what not) but every file etc would take too long, and it worked, my daughter ot well over 150 million score on subway surfers etc. i notice my phone sluggish even bein over clocked, I/Os that i did myself, running max cpu and performance i could blabber forever since my 3 kids arnt interested in my newly found hobbie and my husbands a truck driver, i'm getting it out here (i'm sorry but i do need help) so anywyas i decided to kick her into recovery and begin to just manually delete all the dex copied files through TWRP went good till i wetn to reboot after staring at my screen for 3 hours and got threw up on twice from sick babies and i was boot looped. i decide to restore a previous freshly flashed rom/root backup. well they were deleted too. and all i could do was a master re format i think is what i read it was called, and excited to get back and re download everything i notice i now have no OS and no recoveries and TWRP fulll of emptiness. i can play through TWRP i've changed file permissions i've tried everything ive read and tried everything i learned and experianced to fix this issue, and yet stillno idea how to fix this issue..
Now the fun part is my set up. the only pc i have means and access too is my samsung Chromebook, and my tablet, that's it, no phone because my tablet handles everything my little heart can desire.
needless to say, i need some kinda recovery tool kit i can use via my chromebook, that'll allow me to use ADB for chrome (which another question i have is how do i enable my tablets USB debugging if i can't get into the phone?) so toolkit for chromebook for a ADB side load if possible. or some way to do it through my emulated terminal in TWRP,. my minds rushing, i'm confused and my over emotionally stressed female head is killing me without my tablet. (drive to any town where i could use anything but my chrome book. 3.5 hours.
sorry i pray this post doesnt get deleted. I need help because my tablet is my main source of income being in real estate when i'm back in town once a month. never made a page or a forum or anything like this usally google magic does it. but 3 days and countless mind numbing forums i've given in.. please help me! i'll donate pay something idc at this point. -a pissed off irish southen woman on the verge of pms and a meltdown thanks in advance i'll try to reply as fast as humanly possible, ill be up for awhile tonight going through more posts.
0well with a little more tinking around, i think i have found the issue as too why no matter what i do i'm unable to boot a rom/os. mt EXT3 wil not mount my system i'm clueless as to how to fix that at all threw TWRP, anyone have an idea of any kind please? i'm for anything, even if after more attempts and countless hours, i'll record me skipping it across my lake, and we'll all take guesses as too how many skips it'll do. hopefully my dog will fetch it if i throw at the wrong angle. (completely dumb jokes are the only thing keeping me from returning Sain.) we all cant be too serious. please very interested on how to fix this issue tho.
s,
you need to get a custom rom zip onto an sdcard, check development section.
in twrp, flash the rom,
if the rom still doesn't boot, then reboot to twrp again and use the format data option, then reflash rom and try again.
twrp terminal sucks, you can try flashing aromafm https://www.androidfilehost.com/?fid=95916177934547314
this is for the marvell variant, it may work for the msm/qcom variant.
stop using lucky patcher.
m
moonbutt74 said:
s,
you need to get a custom rom zip onto an sdcard, check development section.
in twrp, flash the rom,
if the rom still doesn't boot, then reboot to twrp again and use the format data option, then reflash rom and try again.
twrp terminal sucks, you can try flashing aromafm https://www.androidfilehost.com/?fid=95916177934547314
this is for the marvell variant, it may work for the msm/qcom variant.
stop using lucky patcher.
m
Click to expand...
Click to collapse
Hi, that's where another problem lies within, I have no way of communicating with the phone or being able to do much, considering the only pc/laptop i have access too is my chromebook, and this thing is a ssteaming pile of regurgitated dog bile. if theres one regret in life.. buying this thing.. even dual booted i still can't process the zips or compile them properly, maybe i need to find out how to build a zip file from scratch and comepile the corresponding stuff myself in small hopes it'll work on this chromebook
and yes, never again will I use that. it worked don't get me wrong. but then it decided to deodex my system to oblivion.
s,
hey that rhymed !
your alternative is to use a usb thumbdrive and an otg cable , else nada.
m
moonbutt74 said:
s,
hey that rhymed !
your alternative is to use a usb thumbdrive and an otg cable , else nada.
m
Click to expand...
Click to collapse
I'm gla you have a sense of humor, thank you hun. looks like i'm tabletless until i go back into town in two weeks ): i suppose till then i will tinker with it some more and unlock the universe, or find a way to convert zips that are made for windows or mac and be able to convert it to be able to be used and transfered unto the phone. Chromium os or chrome now has ADB for chrome as an extension but very iffy, has 3 options to screen record/screenshot and terminal. i was able to use vitural box for about 2 hours and force odin to pretend i was on a widnows enough to orignally root, then it crashed my chromebook. Maybe i've gotta achieve 88 mph first to get this thing to work? lol my chromebook "overclocked" 810 mghz.... maxx.... frequency says it can go to 2100... i think if i even try that i'd recreate the "hydrogen bomb"

Most Recent Magisk update won't allow me to boot up phone

My phone is root with magisk and TWRP. Some other downloads from the repositories within Magisk but I don't think that's relevant. Anyways, around 9:10 pm (EDST) on Sunday the 15th I got a notification that the latest version of magisk was available and ready for download. I downloaded and installed. It booted to fastboot with the typical menu to start, restart bootloader, turn off, or boot into recovery. I thought this was weird as it has never happened before and the phone has been loaded with both since at least July. At first I thought it was just a one off and started the phone. It came back to Fastboot mode and will not let me do anything besides restart and once it does that it's back in fastboot mode. ADB is not recognizing and like I said I cant get any farther than the phone booting into fastboot mode. I'm a full time student with no money for another phone and I was dumb enough to do all this on my daily driver. I am not well versed in phone modding, just enough to be dangerous. Is there any recourse or action I can take to get it back to working order or am I just screwed? Any suggestions welcome as long as they are productive. Thanks
I have the same exact problem going on with my phone. I'm in the process of trying to unbrick it as we speak. If I see any success, I'll be sure to share what I did to remedy the issue.
PS - my problem might be slightly different, as initially I could get to TWRP recovery but I made the mistake of wiping the entire device, which seemingly included all partitions, OS and all. So now I don't even have TWRP and can only get to the fastboot screen. When I try to boot the TWRP.img I get an error... I'm rather new to dealing with a bricked device so this is definitely a learning process
You will lose your data, but this guide should get you both up and running.
https://forum.xda-developers.com/oneplus-6t/how-to/tool-6t-msmdownloadtool-v4-0-oos-9-0-5-t3867448
Yeah, you guys shouldnt be too scared about your phone being bricked but data loss could be an issue. MSMDownloadTool will almost always save your phone and if you are able to boot into fastboot you could just flash a factory image straight from the OnePlus website. If you want to recover files on the phone maybe try booting a twrp image in adb and if the encryption key is still intact you may be able to USB file transfer the data off of the phone.
Does the msm download tool work on Linux or does it require Windows? I downloaded it on a Windows laptop but it was one of the newer laptops that had zero internal storage and instead uses OneDrive in lieu of, so I downloaded the tool to a thumb drive but Windows wouldn't open the .rar file. Any help or insight is greatly appreciated. Thanks!
Is it allowing you to boot to recovery from fastboot?
If not you will have to use MSMDownloadTool and lose all data unfortunately
I would recommend using Syncthing for the future. It atomatically backs up your data to a local PC.
AtheonScribe said:
My phone is root with magisk and TWRP. Some other downloads from the repositories within Magisk but I don't think that's relevant. Anyways, around 9:10 pm (EDST) on Sunday the 15th I got a notification that the latest version of magisk was available and ready for download. I downloaded and installed. It booted to fastboot with the typical menu to start, restart bootloader, turn off, or boot into recovery. I thought this was weird as it has never happened before and the phone has been loaded with both since at least July. At first I thought it was just a one off and started the phone. It came back to Fastboot mode and will not let me do anything besides restart and once it does that it's back in fastboot mode. ADB is not recognizing and like I said I cant get any farther than the phone booting into fastboot mode. I'm a full time student with no money for another phone and I was dumb enough to do all this on my daily driver. I am not well versed in phone modding, just enough to be dangerous. Is there any recourse or action I can take to get it back to working order or am I just screwed? Any suggestions welcome as long as they are productive. Thanks
Click to expand...
Click to collapse
Try flashing the Magisk uninstaller ZIP, boot the device and hope it boots, then reinstall Magisk using the ZIP in TWRP.
I'm not at all worried about losing my data. I do have a relatively recent backup on my computer but I really don't care whether or not I need to start from scratch, however I'm still wondering if I'm able to use the MSMdownloadtool on a Linux machine or not. I was led to believe that it needed to be run on a Windows machine but for some reason I wasn't able to run the program on an HP laptop running Windows 10. Not sure whether it's relevant or not but as I mentioned above in a previous post, the device has no internal storage so I saved the program to a thumb drive and when trying to open it windows asked me what program it wanted me to open it with and/or whether I wanted to search the software / application store for a program with which to run it, leaving me to believe that it may not be something that I can run on a Windows operating system after all. Or, is it just the fact that I save it to a thumb drive? I can try to get another windows PC that may have the space internally or if it will run on my Linux PC that would be ideal. I'm just sick of using this old Motorola Droid Turbo POS LOL.
OP - how are you fairing with your issue?
Thanks in advance everybody for your help, I promise to pay it forward if and when anybody else is stuck in a similar pickle where I might be able to offer any advice to remedy their situation.
PS I Love syncthing but ironically stopped using it regularly some time prior to the **** hitting the fan
Problem fixed, thanks for those of you who chimed in!
#MSMdownloadtoolFTW
QneEyedJack said:
I'm not at all worried about losing my data. I do have a relatively recent backup on my computer but I really don't care whether or not I need to start from scratch, however I'm still wondering if I'm able to use the MSMdownloadtool on a Linux machine or not. I was led to believe that it needed to be run on a Windows machine but for some reason I wasn't able to run the program on an HP laptop running Windows 10. Not sure whether it's relevant or not but as I mentioned above in a previous post, the device has no internal storage so I saved the program to a thumb drive and when trying to open it windows asked me what program it wanted me to open it with and/or whether I wanted to search the software / application store for a program with which to run it, leaving me to believe that it may not be something that I can run on a Windows operating system after all. Or, is it just the fact that I save it to a thumb drive? I can try to get another windows PC that may have the space internally or if it will run on my Linux PC that would be ideal. I'm just sick of using this old Motorola Droid Turbo POS LOL.
OP - how are you fairing with your issue?
Thanks in advance everybody for your help, I promise to pay it forward if and when anybody else is stuck in a similar pickle where I might be able to offer any advice to remedy their situation.
PS I Love syncthing but ironically stopped using it regularly some time prior to the **** hitting the fan
Click to expand...
Click to collapse
Used fastboot flash all partitions and got it going again currently on android 10 running Syberia Rom. Turns out that it was flashable even though I wasn't getting any response from the computer as far as identifying the phone. Freaked out after a few days with no responses and purchased the 7 pro ^_^. At present I'm messing with that. Looking at RomAur-V2.0 to upgrade this the 7P to 10 since, for some reason, my international hasn't received the OTA.
AtheonScribe said:
Used fastboot flash all partitions and got it going again currently on android 10 running Syberia Rom. Turns out that it was flashable even though I wasn't getting any response from the computer as far as identifying the phone. Freaked out after a few days with no responses and purchased the 7 pro ^_^. At present I'm messing with that. Looking at RomAur-V2.0 to upgrade this the 7P to 10 since, for some reason, my international hasn't received the OTA.
Click to expand...
Click to collapse
Just use Oxygen Updater app on the Play Store to update your OnePlus 7 Pro to Android 10.
Sent from my ONEPLUS A6013 using Tapatalk
when i had issue with magisk I used the magisk uninstaller in twrp then flashed 19.4 and booted up no issue
ecompton59 said:
when i had issue with magisk I used the magisk uninstaller in twrp then flashed 19.4 and booted up no issue
Click to expand...
Click to collapse
Yup, that's why I always keep a magisk uninstaller zip on my sdcard!

Categories

Resources