Related
I formatted my system on Stock ROM. I found another stock ROM for sprint now i can't get the ROM i want on my phone because the PC won't read the phone (in CWM recovery). My question is...is there a way to get the ROM on the phone through ADB? Im not all that familiar with it. If so...whats the command?
adb push rom.zip /sdcard
nhizzat said:
adb push rom.zip /sdcard
Click to expand...
Click to collapse
says error device not found
Prestige_DOPE said:
says error device not found
Click to expand...
Click to collapse
You might need to go through a different set of instructions just to make sure the devices is recognized on ADB. Here are my instructions for backing up and restoring app data via ADB, and it includes pretty good instructions on setting up your phone with ADB (well, at least I'd like to think so).
DogzOfWar said:
You might need to go through a different set of instructions just to make sure the devices is recognized on ADB. Here are my instructions for backing up and restoring app data via ADB, and it includes pretty good instructions on setting up your phone with ADB (well, at least I'd like to think so).
Click to expand...
Click to collapse
Well. I have my phone right here and connected to the PC with ADB set up and all. The problem is my PC wont recognize my phone. I tried using fastboot and ADB (i guess they're the same) and it keeps saying the error i stated above your post. The plan is to get the ROM on flashed on my phone. I don't know any other way of doing that. I thought fastboot (adb) would be of assistance but i dont know much about it.
Prestige_DOPE said:
Well. I have my phone right here and connected to the PC with ADB set up and all. The problem is my PC wont recognize my phone. I tried using fastboot and ADB (i guess they're the same) and it keeps saying the error i stated above your post. The plan is to get the ROM on flashed on my phone. I don't know any other way of doing that. I thought fastboot (adb) would be of assistance but i dont know much about it.
Click to expand...
Click to collapse
What I noticed on my phone is that I had ADB working fine for my previous phone (HTC Rezound), but that same ADB install didn't work for the X. When I downloaded the Moto X Toolkit, which included its own version of the adb.exe, it worked fine.
So consider trying everything through the toolkit.
Also, just to double check your settings:
- Make sure you have enabled Developer Settings, and Enable Debugging via ADB
- I set my phone to Camera mode, which seems to work a bit better than Media
DogzOfWar said:
What I noticed on my phone is that I had ADB working fine for my previous phone (HTC Rezound), but that same ADB install didn't work for the X. When I downloaded the Moto X Toolkit, which included its own version of the adb.exe, it worked fine.
So consider trying everything through the toolkit.
Also, just to double check your settings:
- Make sure you have enabled Developer Settings, and Enable Debugging via ADB
- I set my phone to Camera mode, which seems to work a bit better than Media
Click to expand...
Click to collapse
Well my phone wont bootup so thats not going to work but im in the moto x tool kit and i selected to push the ROM onto the sdcard now the whole tool kit froze...is that because its doing something or....
Try a different USB port? Then type adb devices.
Have you downloaded the Motorola Device Manager software? It contains all the necessary drivers. How about the Android SDK?
Prestige_DOPE said:
Well my phone wont bootup so thats not going to work but im in the moto x tool kit and i selected to push the ROM onto the sdcard now the whole tool kit froze...is that because its doing something or....
Click to expand...
Click to collapse
I misunderstood you're original question, sorry. I didn't realize it won't boot at all. I have done what you are asking for my Nexus 7 (which I had messed up). Typically, when you're in the recovery and you plug it into a PC, it will install drivers (separate from the ones when Android OS is running).
Maybe consider trying to use RSD Lite to at least get a functional OS back on there? This page lists drivers to use along with RSD Lite. Maybe that would help get things recognized to the point where you can copy over a ROM?
nhizzat said:
Try a different USB port? Then type adb devices.
Have you downloaded the Motorola Device Manager software? It contains all the necessary drivers. How about the Android SDK?
Click to expand...
Click to collapse
Didnt work...the more things that arent working the more scared i become
DogzOfWar said:
What I noticed on my phone is that I had ADB working fine for my previous phone (HTC Rezound), but that same ADB install didn't work for the X. When I downloaded the Moto X Toolkit, which included its own version of the adb.exe, it worked fine.
So consider trying everything through the toolkit.
Also, just to double check your settings:
- Make sure you have enabled Developer Settings, and Enable Debugging via ADB
- I set my phone to Camera mode, which seems to work a bit better than Media
Click to expand...
Click to collapse
Installed RSDLite and literally screamed "What the hell is this". A little help here on how this is supposed to work?
Hi All,
I'm lost, so hope you chaps can help.
Have just purchased a Verizon Moto X developer phone X1060 - its from the USA, I'm in Hong Kong and obviously not using a Verizone sim card - further, I'm a iMac user, so Android is new to say the least to me.
My MX is already "rooted" so want to upgrade to latest 4.4.2, obviously I have to do this via boot loader - big difficulties encountered having download all necessary files and cannot "hard" reboot as getting Andy with Red Triangle - I take it some issue with fast boot or whatever, but after 12 hours effort, absolutely stuck and getting annoyed.
So, time to hit boards and get expert advice me thinks?
I always used OTA updates, but I think that you have to unlock your bootloader, and/or, use RSD LITE like this:
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
Many thanks, but
djlucask said:
I always used OTA updates, but I think that you have to unlock your bootloader, and/or, use RSD LITE like this:
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
Click to expand...
Click to collapse
Thanks for your input, but as I have a developer Moto X from Verizone and am using it with a mobile provider in Hong Kong, I cannot do OTA update, hence struggling, and struggling because I'm on OSX 10.8 and an iMac, most guides being for PC - have managed to crack half the issue, but flashing ROM's is a big pain presently, particularly when using Terminal!
editor1 said:
Thanks for your input, but as I have a developer Moto X from Verizone and am using it with a mobile provider in Hong Kong, I cannot do OTA update, hence struggling, and struggling because I'm on OSX 10.8 and an iMac, most guides being for PC - have managed to crack half the issue, but flashing ROM's is a big pain presently, particularly when using Terminal!
Click to expand...
Click to collapse
Oh i forgot the iMac issue, I never saw tutorials for OSX, maybe the best choice here is to make an Windows VM, or an Linux, that way would be always easy to mod your phone.
Sorry I don't have any other possible solutions for this
Might be easier to read up on how to change the recovery to TWRP (make sure get version 2.7); sounds like you are on the stock recovery still since you get Andy w/ Red Triangle) then use TWRP to flash a rooted, updated rom from the development section. If you are already rooted (not just unlocked) then you can use an app like Recovery manager (?) to flash TWRP while booted into the regular android system.
Or, you can also flash all the update files from the Bootloader using Fastboot. I don't have a MAC, so I don't know if the Motorola Fastboot file is available for Mac though. If you can't use the Motorola fastboot, you will need to use fastboot to flash the TWRP recovery, and then flash the new ROM system image using a ROM zip file in TWRP recovery instead of Bootloader.
Just make sure you are in the Bootloader when you try and use fastboot, not in the Factory Recovery. I believe the Andy icon indicates you are in the Factory Recovery.
One other tip: when in bootloader, the "volume up" key is the "enter" key to select the option that is highlighted (not the power key like other Android devices I have used).
When you flash TWRP, DON"T reboot, instead, use the bootloader option to boot to recovery directly (without rebooting).
Once you have a custom recovery, and have root, you won't ever need to worry about working on a Mac instead of PC.
jasoraso said:
Might be easier to read up on how to change the recovery to TWRP (make sure get version 2.7); sounds like you are on the stock recovery still since you get Andy w/ Red Triangle) then use TWRP to flash a rooted, updated rom from the development section. If you are already rooted (not just unlocked) then you can use an app like Recovery manager (?) to flash TWRP while booted into the regular android system.
Or, you can also flash all the update files from the Bootloader using Fastboot. I don't have a MAC, so I don't know if the Motorola Fastboot file is available for Mac though. If you can't use the Motorola fastboot, you will need to use fastboot to flash the TWRP recovery, and then flash the new ROM system image using a ROM zip file in TWRP recovery instead of Bootloader.
Just make sure you are in the Bootloader when you try and use fastboot, not in the Factory Recovery. I believe the Andy icon indicates you are in the Factory Recovery.
One other tip: when in bootloader, the "volume up" key is the "enter" key to select the option that is highlighted (not the power key like other Android devices I have used).
When you flash TWRP, DON"T reboot, instead, use the bootloader option to boot to recovery directly (without rebooting).
Once you have a custom recovery, and have root, you won't ever need to worry about working on a Mac instead of PC.
Click to expand...
Click to collapse
Thanks for info, I've managed to setup fast boot, its the actual flashing of the ROM via Terminal that's confusing to say the least - basically, in Mac terminal necessary to change inputting details associated with rooting instructions found on PC - side of the equation, hence why I'm stuck. Would be easier to get someone with a PC laptop to lend a hand, most don't do custom jobs on Android though, so, will have to figure it out myself and then hopefully render help to others.
Republic Wireless Moto X Moto G Discount Code Link URL
$25 Republic Wireless credit at checkout with purchase of your phone using this discount link
editor1 said:
Thanks for info, I've managed to setup fast boot, its the actual flashing of the ROM via Terminal that's confusing to say the least - basically, in Mac terminal necessary to change inputting details associated with rooting instructions found on PC - side of the equation, hence why I'm stuck. Would be easier to get someone with a PC laptop to lend a hand, most don't do custom jobs on Android though, so, will have to figure it out myself and then hopefully render help to others.
Click to expand...
Click to collapse
Have you tried this?
Toolkit for Mac OS under development...
Sent from my XT1060 using Tapatalk 2
imparables said:
Have you tried this?
Toolkit for Mac OS under development...
Sent from my XT1060 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for info, I've not tried Toolkit, or heard of it - any links to assist with this?
Basically, you are going to see more Mac users adopt Android over the coming months, and many like me suffer in an all OSX environment when playing about with PC-structured advice - shame I never adopted a duel boot system on my mac, but its always been for DTP, hence always happy with Adobe in Mac.
Now upgraded to 4.4.2
editor1 said:
Thanks for info, I've not tried Toolkit, or heard of it - any links to assist with this?
Basically, you are going to see more Mac users adopt Android over the coming months, and many like me suffer in an all OSX environment when playing about with PC-structured advice - shame I never adopted a duel boot system on my mac, but its always been for DTP, hence always happy with Adobe in Mac.
Click to expand...
Click to collapse
Thanks for the input, after two days of hell, I'm now fully upgraded to KitKat 4.4.2, my Moto X1060 Dev phone is working as it should be, I've unlocked it, am able to do side-loading, have TWRP installed - a bigger pain as caused a continually boot loop, erased, re-installed all from Moto and re-cracked it.
So it works, and I did all this on a iMac and in terminal, which I don't often use!
Not bad for someone fast approaching 50 - and yes, this is a kids game I'm afraid to say.
Hello,
Maybe this has already been answered, but does anyone know if it's possible to flash an updated radio.img, system.img, bootoader.img and boot.img? I'm a bit of a noob, and I want to upgrade my Nexus 6 to 5.1 once the factory images are released (and the modified boot.img to remove encryption). However, I'd like to do this without the use of a computer. I would use the Nexus Root Toolkit, but for some reason my PC no longer recognizes my device (even though I've tried EVERYTHING to fix, including different cables, ports, drivers, restarts etc.). Maybe the 5.1 update will fix, but I think I have a faulty micro usb port on the device.
I don't want to wipe my data or lose root, which is why I would only update the above images. I thought it could be done through Flashify, but the dev said I'd have to flash an entire .zip through TRWP, but I need the files along with the correct commands. I would lose root, but would use the Towelroot apk to get it back.
Please let me know if this is correct or if I'm missing something. Or if there is an easier way (like maybe Nexus Update Checker).
Thanks
ryan4a said:
Hello,
Maybe this has already been answered, but does anyone know if it's possible to flash an updated radio.img, system.img, bootoader.img and boot.img? I'm a bit of a noob, and I want to upgrade my Nexus 6 to 5.1 once the factory images are released (and the modified boot.img to remove encryption). However, I'd like to do this without the use of a computer. I would use the Nexus Root Toolkit, but for some reason my PC no longer recognizes my device (even though I've tried EVERYTHING to fix, including different cables, ports, drivers, restarts etc.). Maybe the 5.1 update will fix, but I think I have a faulty micro usb port on the device.
I don't want to wipe my data or lose root, which is why I would only update the above images. I thought it could be done through Flashify, but the dev said I'd have to flash an entire .zip through TRWP, but I need the files along with the correct commands. I would lose root, but would use the Towelroot apk to get it back.
Please let me know if this is correct or if I'm missing something. Or if there is an easier way (like maybe Nexus Update Checker).
Thanks
Click to expand...
Click to collapse
first off, towelroot doesnt work in android 5.0+. 2ndly, if you are planning on flashing the official 5.1, you need a computer. if you are planning on updating a custom rom, and you have twrp recovery, download the rom and flash it via twrp.
simms22 said:
first off, towelroot doesnt work in android 5.0+. 2ndly, if you are planning on flashing the official 5.1, you need a computer. if you are planning on updating a custom rom, and you have twrp recovery, download the rom and flash it via twrp.
Click to expand...
Click to collapse
Thanks. I don't have a custom ROM. So I guess I'll wait for one to get updated, then install it. Like I said, using a computer is not an option
ryan4a said:
Thanks. I don't have a custom ROM. So I guess I'll wait for one to get updated, then install it. Like I said, using a computer is not an option
Click to expand...
Click to collapse
thats the easiest way. i dont own a computer nor laptop, so i try to do everything from the phone. but its easier to update via recovery anyways. one thing though, since you are on the stock rom, you will have to wipe your data before flashing a custom rom, since the majority are aosp based, and wont flash over stock.
Before you give up, try a different computer (preferably running Linux), or booting the one you have on a livecd/usb.
If the USB plug on the phone is, in fact, broken, try calling motorola. The phone is still under warranty....
doitright said:
Before you give up, try a different computer (preferably running Linux), or booting the one you have on a livecd/usb.
If the USB plug on the phone is, in fact, broken, try calling motorola. The phone is still under warranty....
Click to expand...
Click to collapse
Thanks. I've tried on multiple computers (PC & Mac, but not Linux). Nothing works. I originally thought it was one of the modifications I made to the device, like root, unlock, custom boot.img, custom recovery, modified build.prop, etc. The more I search, the more I think it's hardware. I'd like to not have to warranty it because I'd have to wipe everything, restore to factory settings, unroot, etc. It's just a big hassle. Plus I'd be without a phone until the replacement arrives. I may end up just living with staying on lollipop 5.0.1 forever. It's just super frustrating.
ryan4a said:
Thanks. I've tried on multiple computers (PC & Mac, but not Linux). Nothing works. I originally thought it was one of the modifications I made to the device, like root, unlock, custom boot.img, custom recovery, modified build.prop, etc. The more I search, the more I think it's hardware. I'd like to not have to warranty it because I'd have to wipe everything, restore to factory settings, unroot, etc. It's just a big hassle. Plus I'd be without a phone until the replacement arrives. I may end up just living with staying on lollipop 5.0.1 forever. It's just super frustrating.
Click to expand...
Click to collapse
update your nexus 6 driver, or install the adb driver. your computer cant see your phone until it has one of the drivers installed. if you had it installed, uninstall it and reinstall.
simms22 said:
update your nexus 6 driver, or install the adb driver. your computer cant see your phone until it has one of the drivers installed. if you had it installed, uninstall it and reinstall.
Click to expand...
Click to collapse
For a driver, it isn't a question of seeing it. Its a question of knowing how to talk to it. Further, one of the reasons I suggest he use something that runs linux, is because it avoids this whole driver problem altogether. The other reason is that it is actually consistent, and trivial to determine whether the devices itself actually made a connection, i.e. "dmesg -w", plug it, and see if it says anything.
simms22 said:
update your nexus 6 driver, or install the adb driver. your computer cant see your phone until it has one of the drivers installed. if you had it installed, uninstall it and reinstall.
Click to expand...
Click to collapse
I've deleted and reinstalled the google driver, and installed the ADB driver. No dice. I'm telling you...I've tried everything. That's why I think it's hardware, however unlikely.
ryan4a said:
I've deleted and reinstalled the google driver, and installed the ADB driver. No dice. I'm telling you...I've tried everything. That's why I think it's hardware, however unlikely.
Click to expand...
Click to collapse
when getting adb to work, thats the #1 issue, installing and getting the driver to work. so, i can tell you, many people dont get the driver working without help in manually installing it. it seems those with older windows have less issues then those with newer windows. i really doubt that its a hardware issue.
simms22 said:
when getting adb to work, thats the #1 issue, installing and getting the driver to work. so, i can tell you, many people dont get the driver working without help in manually installing it. it seems those with older windows have less issues then those with newer windows. i really doubt that its a hardware issue.
Click to expand...
Click to collapse
Man I hope you're right. But my PC doesn't even recognize my device. Like it's not even showing up in the device manager. At best, I can sometimes get the PC to recognize it as an "unknown device". When I try to automatically update the driver, it says complete. But nothing changes. What do I do at that point? I haven't been successful in manually updating the driver.
As a matter of fact, I thought my new Turbo charger was broken because it stopped charging my phone. But when I unchecked USB debugging AND unchecked the MTP connection, the charger started working again. Very strange!
ryan4a said:
Man I hope you're right. But my PC doesn't even recognize my device. Like it's not even showing up in the device manager. At best, I can sometimes get the PC to recognize it as an "unknown device". When I try to automatically update the driver, it says complete. But nothing changes. What do I do at that point? I haven't been successful in manually updating the driver.
Click to expand...
Click to collapse
i wouldnt be able to help you there, as i dont own a computer. but there are many that can help out. maybe someone else will see this thread..
ryan4a said:
As a matter of fact, I thought my new Turbo charger was broken because it stopped charging my phone. But when I unchecked USB debugging AND unchecked the MTP connection, the charger started working again. Very strange!
Click to expand...
Click to collapse
Like I said, TRY LINUX.
No drivers required. Everything is built into the kernel.
Fedora even has an "android-tools" package that includes adb. You just install it with "yum install android-tools" -- even on the livecd (it will install to ramdisk).
Quit screwing around with wondoze and TRY IT.
Linux is a mega pita. Nothing is intuitive or easy. All these commands that have to be typed in, yuk. Give me good ol' Windows any day. Lol.
To the OP. Are you on windows 8.1? Have you disabled 'driver signature verification'?
killall said:
Linux is a mega pita. Nothing is intuitive or easy. All these commands that have to be typed in, yuk. Give me good ol' Windows any day. Lol.
To the OP. Are you on windows 8.1? Have you disabled 'driver signature verification'?
Click to expand...
Click to collapse
I'm using Windows 7. Don't think I'll be using Linux either. I'm running out of options for upgrading android versions without a PC. I'm highly considering installing CM12. I'd rather not because it's seems unnecessary on a Nexus device, but don't know what else to do.
There is also about a 5 second delay from the time I plug my device into any charger, to when it actually begins charging. I'm thinking these two issues are related, which leads to believe it's hardware.
Definitely sounding more and more like hardware
ryan4a said:
There is also about a 5 second delay from the time I plug my device into any charger, to when it actually begins charging. I'm thinking these two issues are related, which leads to believe it's hardware.
Click to expand...
Click to collapse
I have the same delay when plugging in a charger. But my PC recognizes my N6 without any problems.
On my Droid Maxx I had driver issues. I asked on XDA and got it figured out. I can't check now but have a look at my posts and you may find your answer.
Back to V-Day.
Hey everyone,
So I bought the Blu R1 HD 16gb/2gb on amazon for 60 bucks, super stoked with its performance and look (although who can complain for the price of a family meal?).
My only problem is that I've been unable to root it. I know that I can easily root it with a computer, but for whatever reason my computer is unable to install any drivers for anything! Does anyone know of a rooting app that is compatible with the phone, or a way to root it with out a computer?
Please don't respond telling me how to install drivers, as I've tried everything; short of upgrading windows, that is.
P.S. Tried a bunch of apps already, none have supported rooting the R1 HD yet. I've tried kingo, king, towel, z4, and a bunch of others.
Thanks in advance!
Dude really? there is no other computer you could use to do it? your brother/sister father/mother some friend anything?... so sad
onlykhaz said:
Dude really? there is no other computer you could use to do it? your brother/sister father/mother some friend anything?... so sad
Click to expand...
Click to collapse
Yeah, they're all mac users, and android doesn't connect to it correctly.
ActuallyAFrog said:
Yeah, they're all mac users, and android doesn't connect to it correctly.
Click to expand...
Click to collapse
i dont (haven't anyway) use mac but @ColtonDRG , who does alot on this forum, uses MACos, so i do beleive there is support for mac
ActuallyAFrog said:
Hey everyone,
So I bought the Blu R1 HD 16gb/2gb on amazon for 60 bucks, super stoked with its performance and look (although who can complain for the price of a family meal?).
My only problem is that I've been unable to root it. I know that I can easily root it with a computer, but for whatever reason my computer is unable to install any drivers for anything! Does anyone know of a rooting app that is compatible with the phone, or a way to root it with out a computer?
Please don't respond telling me how to install drivers, as I've tried everything; short of upgrading windows, that is.
P.S. Tried a bunch of apps already, none have supported rooting the R1 HD yet. I've tried kingo, king, towel, z4, and a bunch of others.
Thanks in advance!
Click to expand...
Click to collapse
You're doing it wrong. We don't use ****ty rooting apps to root, we do it the RIGHT way. You have to install TWRP and flash SuperSU. You can do this the original way using SPFT, or the (more recommended) way of converting to OEM non-Prime, unlocking the bootloader, and using fastboot to flash TWRP.
ActuallyAFrog said:
Yeah, they're all mac users, and android doesn't connect to it correctly.
Click to expand...
Click to collapse
No. No. You could not be more wrong. Android connects to macOS MORE correctly than it connects to Windows. It doesn't even need any drivers! At Google, they don't use Windows, they use macOS and Linux. That said, we don't have any SPFT for Mac, unfortunately, but that's MediaTek's fault, and there's no reason you couldn't use a Linux live USB to do it.
mrmazak said:
i dont (haven't anyway) use mac but @ColtonDRG , who does alot on this forum, uses MACos, so i do beleive there is support for mac
Click to expand...
Click to collapse
I use macOS sometimes, yes, but there is no SPFT for it. I use Linux mostly.
ColtonDRG said:
No. No. You could not be more wrong. Android connects to macOS MORE correctly than it connects to Windows. It doesn't even need any drivers! .
Click to expand...
Click to collapse
Well @ColtonDRG I wasn't really saying that it won't work, I was saying they don't like me fiddling with their computers, cause as a kid I messed up some of their stuff, and they really haven't gotten over it yet.
But say I could use one, those things would be all to root it? I would just get the necessary programs, convert OEM to non-prime, unlock the bootloader (assuming mine is locked), flash TWRP, and then Super SU? I'd be done with it in an hour or two?
ActuallyAFrog said:
Well @ColtonDRG I wasn't really saying that it won't work, I was saying they don't like me fiddling with their computers, cause as a kid I messed up some of their stuff, and they really haven't gotten over it yet.
But say I could use one, those things would be all to root it? I would just get the necessary programs, convert OEM to non-prime, unlock the bootloader (assuming mine is locked), flash TWRP, and then Super SU? I'd be done with it in an hour or two?
Click to expand...
Click to collapse
You might need to convert your phone to the OEM non-Prime version first, but yes. There is no version of SPFT for macOS, so you'll need to use Windows or Linux for that, but the rest can be done on any OS. The whole process only takes me about 10 minutes, but if you don't know what you're doing, it would be reasonable to assume that you could do it in about a half an hour.
EDIT: Also my comment was in direct response to you saying:
"Yeah, they're all mac users, and android doesn't connect to it correctly."
Which implies that Macs cannot manipulate Android devices, which is simply not true.
ColtonDRG said:
You might need to convert your phone to the OEM non-Prime version first, but yes. There is no version of SPFT for macOS, so you'll need to use Windows or Linux for that, but the rest can be done on any OS. The whole process only takes me about 10 minutes, but if you don't know what you're doing, it would be reasonable to assume that you could do it in about a half an hour.
Click to expand...
Click to collapse
So I'll be good using only Mac as long as I don't need to switch my OEM?
ActuallyAFrog said:
So I'll be good using only Mac as long as I don't need to switch my OEM?
Click to expand...
Click to collapse
No. The Prime version of the phone requires SPFT to root, so you will need it either way. You can use SPFT to covert to the OEM version and then root using fastboot, or you can use SPFT to root the Prime version. I personally highly recommend converting.
Niki Kidman said:
Considering you had already cost "big money" to buy the root software. Maybe it's better for you to make good use of it... Try to change a computer...
Click to expand...
Click to collapse
Try Linux, I just got phone yesterday, rooted, unlocked bootloader, removed amazon stuff and compiled kernel.
Sent from my R1 HD using Tapatalk
vampirefo said:
Try Linux, I just got phone yesterday, rooted, unlocked bootloader, removed amazon stuff and compiled kernel.
Sent from my R1 HD using Tapatalk
Click to expand...
Click to collapse
It's been a long time since I rooted any phone or played around with adb or my linux mint (14). Would it be possible for you to tell me which guide you may have used for linux. I am using a windows 10 computer and cannot follow noob friendly guide for the life of me. My computer won't recognize the phone at all and I have disabled driver verification. Any help would be awesome.
Thanks
sid0101 said:
It's been a long time since I rooted any phone or played around with adb or my linux mint (14). Would it be possible for you to tell me which guide you may have used for linux. I am using a windows 10 computer and cannot follow noob friendly guide for the life of me. My computer won't recognize the phone at all and I have disabled driver verification. Any help would be awesome.
Thanks
Click to expand...
Click to collapse
I explained how I rooted in below post.
http://forum.xda-developers.com/showthread.php?p=68477232
If you can't follow it, then you need to stick with Windows method.
Sent from my R1 HD using Tapatalk
On a Mac. Was on an older version of LineageOS (last version of 14.1 that worked before devs made the change to require newer firmware versions). I was able to unlock FRP and bootloader back when I first bought the tablet from Costco. Just lately tried to update to the latest firmware so I can use newer ROMs. Used Heimdall and it seemed to work until the reboot and then system UI and a bunch of my previous apps kept crashing and not allowing me to do the initial set-up. I thought doing the new firmware would wipe everything (and I was okay with that) but it obviously didn't. Was finally able to push the latest TWRP on and wiped all the partitions but now tablet boots to the "Hey something went wrong and you need to try the emergency blah blah with the Samsung software" which, on the Mac, sees the tablet but just sits there. So...
I have lost interest and just want to have someone on a Windows or Linux machine pretty please make the tablet work. Don't care about much except it have the latest Samsung firmware so that I can install some Oreo Rom on it and start fresh.
I am happy to provide more details or answer questions if need be.
If anyone is interested I would be happy to send it to you (in the U.S.) along with a post paid box for return shipping and we could come to some arrangement for beer or food or some $ or something for your time.
Thanks for reading
Racer5 said:
On a Mac. Was on an older version of LineageOS (last version of 14.1 that worked before devs made the change to require newer firmware versions). I was able to unlock FRP and bootloader back when I first bought the tablet from Costco. Just lately tried to update to the latest firmware so I can use newer ROMs. Used Heimdall and it seemed to work until the reboot and then system UI and a bunch of my previous apps kept crashing and not allowing me to do the initial set-up. I thought doing the new firmware would wipe everything (and I was okay with that) but it obviously didn't. Was finally able to push the latest TWRP on and wiped all the partitions but now tablet boots to the "Hey something went wrong and you need to try the emergency blah blah with the Samsung software" which, on the Mac, sees the tablet but just sits there. So...
I have lost interest and just want to have someone on a Windows or Linux machine pretty please make the tablet work. Don't care about much except it have the latest Samsung firmware so that I can install some Oreo Rom on it and start fresh.
I am happy to provide more details or answer questions if need be.
If anyone is interested I would be happy to send it to you (in the U.S.) along with a post paid box for return shipping and we could come to some arrangement for beer or food or some $ or something for your time.
Thanks for reading
Click to expand...
Click to collapse
Wouldn't it just be easier to run a windows VM such as Virtual box on your Mac?
You can download a Windows VM ready to go below.
Just start it up in the VM software.
https://www.virtualbox.org/wiki/Downloads
https://developer.microsoft.com/en-us/microsoft-edge/tools/vms/
ashyx said:
Wouldn't it just be easier to run a windows VM such as Virtual box on your Mac?
You can download a Windows VM ready to go below.
Just start it up in the VM software.
Click to expand...
Click to collapse
I had forgotten about that option as the last time I used VMWare (or virtualbox) was over 10 years ago and it was crap. Have used Parallels in the past too but really have just moved away from the Windows world. Thanks for the suggestion, I will give that a try but, "easy" is mailing something away and getting it returned in working order as opposed to downloading a virtual machine, setting it up, downloading a minimum 4.2GB windows environment and setting up windows and then hoping this 10 minute operation will work in that cludgy environment.