Haven't been able to find any root method that will work on a Mac. Tried Heimdall but it doesn't work with recent devices, tried actually downloading and installing Windows in Virtualbox but Windows and driver issues are a nightmare. Hoping someone out there can come through with a root method that will work on Mac. I did read somewhere that you could flash cf-auto-root with fastboot somehow does anyone know if that would actually work?
Have you tried boot camp? I know it's annoying having to dual boot just to root but Mac doesn't play nice with androids and if hiemdall isn't working I can't think of anything else really
Fuzzi99 said:
Have you tried boot camp? I know it's annoying having to dual boot just to root but Mac doesn't play nice with androids and if hiemdall isn't working I can't think of anything else really
Click to expand...
Click to collapse
yes, i was in boot camp ... i've done rooting before on windows and mac with htc and samsung .... but this is the first time i've struggled with boot loop, i know all the different procedures for clean wipe (cache, dalvic, etc.,) ... i just wondered if my note 4 on the 3 network was somehow bootlocked to stop it having roms put on ... it's frustrating when i've been able to do it on other phones ..... thanx for your reply
Related
I bricked a brand new verizon galaxy tab! It isn't even mine. it's my brothers and he's going to be pissed if i can't fix it
here is what i did:
i rooted it using z4root from this post: http://forum.xda-developers.com/showthread.php?t=833953
no problems.
then i downloaded sgs kernel flasher from the market and flashed this file http://gunsforgeeks.com/Tab/kernel/KhasMek.Voodoo.plus.CDMA.Tab.v4.OC.zImage
which i got from this post: http://forum.xda-developers.com/showthread.php?t=941781
it auto re-booted when done and is now stuck on samsung logo forever! **** me! i can't reboot into recovery, but i can reboot into download mode.
only problem is i have an old mac ibook running osx 10.4 which is too old for hemidall and too mac for odin. for christs sake i can't even get bootcamp or parallels to work on that old of a mac so i can run windows and thus odin.
what can i do? i'd really like to fix this without having to ask my brother to use his newer mac that should let me run hemidall, cause if i bricked his tab he ain't gonna want me touching his computer.
any suggestions? pleeeeeeease
Get rid of your ****ty mac and get a windows based PC/laptop instead obviously, then flash using odin etc.
Also use the search function, there is an endless amount of topics on this exact issue so no need to create a new one just because you are scared your bro is gunna kick your arse.
Oh btw, your device isnt "bricked", I wish people would not use that term so loosely.
You're gonna have to beg, borrow, buy, or otherwise get yourself a machine that'll run Heimdall... don't think there's any other way around it...
Once you do that, do this: http://forum.xda-developers.com/showthread.php?t=967175
crisis averted
sorry ya'll. you'll have to excuse a noob. crisis has been averted. i borrowed a windows laptop and successfully restored to stock via hemidall. guess i have more reading to do before i attempt to flash a rom on this thing again. didn't think i was such a noob as i've never had such problems flashing all kinds of roms on my vibrant. different devices. chalk it up to a learning experience.
tkirkable said:
sorry ya'll. you'll have to excuse a noob. crisis has been averted. i borrowed a windows laptop and successfully restored to stock via hemidall. guess i have more reading to do before i attempt to flash a rom on this thing again. didn't think i was such a noob as i've never had such problems flashing all kinds of roms on my vibrant. different devices. chalk it up to a learning experience.
Click to expand...
Click to collapse
Good to hear you solved the problem. Just out of curiosity what happened when you tried to run Heimdall on your mac? Theoretically the universal binaries I redistribute should run on 10.4+ with any processors architecture supported by OS X (i.e. x86, AMD64 and PPC).
Heimdall requires osx 10.5?
Apparently. That's what it says when i try to open the .pkg file. it says this package type requires osx 10.5 I can run it in windows 7 though. I had to three times yesterday cause i kept soft bricking my device if that's the right way to put it. read read read. i must be missing something. I had clockworkmod recovery and ext. 4 for a second but then froze on the samsung logo at reboot again. had to heimdall my way back and lost it all. back to the drawing board
I've managed to install Firefox OS (V1.0) on my ZTE Pulse (ZTE T790, locked to Telstra).
I used Cydia Impactor to root my phone, then adb and fastboot to unlock the bootloader and install a CWM recovery.
I was looking for an Android Rom to flash but only found roms for the V790 (similar phone, dual SIM). One or two worked but none could see the SIM card.
While looking around I found a couple of zip files for Firefox OS. The first one booted but touch didn't work. The second zip booted and runs well.
Everything seems to work except for the 4 soft buttons; two work but with the wrong function and two don't do anything. Bluetooth doesn't see other devices although other devices can see the phone. Some screen flicker in some apps.
I haven't been able to update the OS. Most update zips won't install using recovery; I'm still playing with them using adb.
Here is the download link for the FirefoxOS I used.
I should mention that installing this ROM via SD card changes your recovery to CWM V6.0.3.6
Update: Bluetooth works
Thanks, where did you find it?
elkedra said:
I've managed to install Firefox OS (V1.0) on my ZTE Pulse (ZTE T790, locked to Telstra).
I used Cydia Impactor to root my phone, then adb and fastboot to unlock the bootloader and install a CWM recovery.
I was looking for an Android Rom to flash but only found roms for the V790 (similar phone, dual SIM). One or two worked but none could see the SIM card.
While looking around I found a couple of zip files for Firefox OS. The first one booted but touch didn't work. The second zip booted and runs well.
Everything seems to work except for the 4 soft buttons; two work but with the wrong function and two don't do anything. Bluetooth doesn't see other devices although other devices can see the phone. Some screen flicker in some apps.
I haven't been able to update the OS. Most update zips won't install using recovery; I'm still playing with them using adb.
Click to expand...
Click to collapse
Thanks allot mate! How long ago did you manage to do this? I have been looking for a rom for a while now but not gone as far as editing a ZTE V790 to fit the T790.
Please let me know the download link of the Firefox OS that worked (with some bugs)
and if you manage to work the bugs out please keep us posted!
Btw this capcha is killing me, maybe, maybe I am not Human?
phillipdi said:
Thanks allot mate! How long ago did you manage to do this? I have been looking for a rom for a while now but not gone as far as editing a ZTE V790 to fit the T790.
Please let me know the download link of the Firefox OS that worked (with some bugs)!
Click to expand...
Click to collapse
I didn't have to edit anything...it just worked. I'm not a developer, just a fiddler.
I've put the download link in the first post.
Thanks allot mate, but
Thanks allot mate, just to clarify you are saying that you managed to make phone calls from your device?
When you flashed the phone was it locked or unlocked?
I cannot get reception/sim registration on my T790 that I flashed with the rom you found and one annother person found, It could be me but I thought I better check
phillipdi said:
Thanks allot mate, just to clarify you are saying that you managed to make phone calls from your device?
When you flashed the phone was it locked or unlocked?
I cannot get reception/sim registration on my T790 that I flashed with the rom you found and one annother person found, It could be me but I thought I better check
Click to expand...
Click to collapse
Phone was locked to Telstra when I started. I assume it was still locked after rooting although where I live only has Telstra so I couldn't get a different SIM to check. The Telstra SIM worked fine for calls and data.
elkedra said:
I've managed to install Firefox OS (V1.0) on my ZTE Pulse (ZTE T790, locked to Telstra).
I used Cydia Impactor to root my phone, then adb and fastboot to unlock the bootloader and install a CWM recovery.
Click to expand...
Click to collapse
Can you tell us as to which version of CWM did you initially install in your Zte pulse Testra T790 and in some steps as to how did you successfully did it????? I just want to install CWM in my ZTE Pusle T790.
THanx
Mabboseg said:
Can you tell us as to which version of CWM did you initially install in your Zte pulse Testra T790 and in some steps as to how did you successfully did it????? I just want to install CWM in my ZTE Pusle T790.
THanx
Click to expand...
Click to collapse
Sorry, can't remember which CWM recovery I used initially. (I've since bricked that phone.) There are recovery files with instructions here https://ztev790support.wordpress.com/instructions/instructions-for-flashing-recovery/and here http://v790.blogspot.com.au/. These recovery files are for the V790 but they worked fine on my T790.
As in the first post use Cydia Impactor to root the phone, then adb and fastboot to unlock the bootloader.
do we have porting option for Samsung?
Do we have porting option for samsung devices or it'll be available in the future....
First off. I'm pretty much a layman at this. Anyone that can solve my issues, I'll gladly pay via PayPal or whatever...
Two months ago, I bought a used LG G2 . It was rooted and running Lollipop.
Sadly, I was a PokemonGo junkie, so when the M'F'ng Niantic a**holes put a block on rooted phones, I attempted the Magisk workaround and ended up bricking my device.
Fortunately I found a solution via You Tube and was able to restore to the factory KitKat / AT&T.
THE CURRENT problem is that yesterday I re-rooted the device, installed TWRP, but did something wrong to where it will not fully reboot and I'm stuck in TWRP. I've watched and read about 20 "fix it" instructionals, which rely on using a PC. I'm using a laptop running XP and every time I have downloaded, installed, and tried to update the damn LG USB driver, it won't f*ing update. I'm going mad and ready to jump off a bridge.
Supposedly, this is the place to go. for answers, so ...CAN ANYONE HELP?!! Again, I'm a layman. I need VERY simple, step by step solutions, that account for ANYTHING that might go wrong, since so far, it always does.
Thank you, if you read this.
Ok Can you access to twrp ?
(Sorry for my english i'm french)
If you are in the TWRP, just download some other kk rom, transfer it to your phone and install, one question, what TWRP is it ? 2.8.7.0. ?
Kornelije23 said:
If you are in the TWRP, just download some other kk rom, transfer it to your phone and install, one question, what TWRP is it ? 2.8.7.0. ?
Click to expand...
Click to collapse
Agreed. Also, if there's no communication between PC and device, you may need an OTG to flash from.
Sent from my Nexus 6 using XDA-Developers mobile app
R2MIR2MI said:
Ok Can you access to twrp ?
(Sorry for my english i'm french)
Click to expand...
Click to collapse
Thanks for the reply. Yes, I can access TWRP. I just don't know what to do with it.
Dork6243 said:
Agreed. Also, if there's no communication between PC and device, you may need an OTG to flash from.
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
It's TWRP 2.7.0. I kind of know in theory what needs to be done, but I don't know how to do it. I thought I backed everything up using Titanium and TWRP, but maybe the KK ROM is gone? I dunno... I was actually hoping to install Lollipop
What model do you have?
If it is d802, then there is an easy-to-flash rom here: http://forum.xda-developers.com/lg-g2/development-d802/rom-pure-stock-lg-google-apps-t3477635/page1
To transfer it to the phone, you can use OTG as Dork said: put the rom on a usb-stick and connect it to the phone with an OTG cable. Most versions of twrp support OTG.
Another way is to get linux for your PC. You're really better off with linux than XP, but you can also just boot with a live-cd. In linux, USB generally just works, though sometimes you have to be root because ordinary users may not have permission.
Thanks for the replies, but being very new at all this, I don't know how to do any of the things suggested. I ended up finding a you tube video which walked me through downloading lg flash tool and some .dll file, and on my work computer with windows 7, I was able to install the usb drivers & change the port number which allowed LG flash to work. The crappy XP didn't have that option on the device manager menu and wouldn't install the drivers.
Anyway, I got it restored to ATT stock KitKat. I wanted Lollipop and Magisk, so I tried installing TWRP with AutoRec, then got stuck in TWRP and bricked again. So I did the whole lg flash to KitKat process again. Now Im sick of messing with it and bricking my phone. I cant find any super simple step by step tutorial that makes sense to a layman like me, or that doesn't leave out steps, or provide expired links, or account for anything that could go wrong. I had hoped this was the place to come, but no luck so far. I know its time consuming for someone to make up a truly easy to follow guide for an older device, using layman terms that my grandma could follow, and I work 2 jobs and dont have hours to try to thoroughly learn OS programming, so I guess Ill just leave well enough alone and live with KitKat and without the ability to mask my root.
davizzyus said:
Thanks for the replies, but being very new at all this, I don't know how to do any of the things suggested.
Click to expand...
Click to collapse
Do what everybody here has done: read. And when you say "I can access TWRP. I just don't know what to do with it." you havn't even read the basics.
Just read the provided solutions properly. The Knowledge will grow. Here's a list of methods:
http://forum.xda-developers.com/showpost.php?p=63327417&postcount=4
Jan Philipp said:
Do what everybody here has done: read. And when you say "I can access TWRP. I just don't know what to do with it." you havn't even read the basics.
Just read the provided solutions properly. The Knowledge will grow. Here's a list of methods:
http://forum.xda-developers.com/showpost.php?p=63327417&postcount=4
Click to expand...
Click to collapse
I have tried reading a lot of different threads. As I said before, I don't understand the "tech talk" for lack of a better word. When I'm reading "bootload" this, and " sideboot" that, and kernels, and loki, and CM, and mods, and .kdz and ATD,....I don't know what all that means, & there's no OS dictionary to translate. I can't seem to find any threads that explain it for newcomers trying to learn.
Im an accountant. I can prepare corporate tax returns with my eyes closed, but cell phone programming is Greek to me.
I started this thread: (https://forum.xda-developers.com/axon-7/help/help-loss-root-twrp-t3781054)
a while back and ended up never solving my issue, eventually giving up and living with an unrooted phone.
Anyhow I've been trying again to get to the bottom of the issue and after another day of fruitless research here I am hoping to bring it back to your attention.
Does anyone around here regularly use a mac to perform adb commands? I'd love to get some help trying to get fastboot working again.
Should I just give up and find a Windows computer to do this?
Thanks for reading
alajoy said:
I started this thread: (https://forum.xda-developers.com/axon-7/help/help-loss-root-twrp-t3781054)
a while back and ended up never solving my issue, eventually giving up and living with an unrooted phone.
Anyhow I've been trying again to get to the bottom of the issue and after another day of fruitless research here I am hoping to bring it back to your attention.
Does anyone around here regularly use a mac to perform adb commands? I'd love to get some help trying to get fastboot working again.
Should I just give up and find a Windows computer to do this?
Thanks for reading
Click to expand...
Click to collapse
That guy was horribly wrong and sorry you had to live with an unrooted phone for so long. But in newer versions of Nougat (i think B32 or B35) they removed fastboot and you could not boot into it. I have a way of being able to install TWRP here without fastboot (assuming you're on an Oreo bootstack, otherwise you can do almost everything in that thread except use a TWRP for Nougat instead). I haven't tried this, but if you have stock recovery, try downgrading to Nougat B19 by using an official SD card update and using apply update from SD card in stock recovery. Haven't found an official SD card update for you but I've only done a little bit of searching.
edit: ive only found B19 Nougat full image , but here: https://mega.nz/#F!kYtRAJjJ!5tD1zPpo0nw2tJwhANA9pQ!tNsQhD5Y
download A2017U-7.1.1-B19-Full-326200B1901A2017UV1.1.0B19.zip and extract it and put update.zip in your sd card. boot into stock recovery and use apply update from sd card and select it. hopefully it works and it will downgrade
Teet1 said:
That guy was horribly wrong and sorry you had to live with an unrooted phone for so long. But in newer versions of Nougat (i think B32 or B35) they removed fastboot and you could not boot into it. I have a way of being able to install TWRP here without fastboot (assuming you're on an Oreo bootstack, otherwise you can do almost everything in that thread except use a TWRP for Nougat instead). I haven't tried this, but if you have stock recovery, try downgrading to Nougat B19 by using an official SD card update and using apply update from SD card in stock recovery. Haven't found an official SD card update for you but I've only done a little bit of searching.
edit: ive only found B19 Nougat full image , but here: https://mega.nz/#F!kYtRAJjJ!5tD1zPpo0nw2tJwhANA9pQ!tNsQhD5Y
download A2017U-7.1.1-B19-Full-326200B1901A2017UV1.1.0B19.zip and extract it and put update.zip in your sd card. boot into stock recovery and use apply update from sd card and select it. hopefully it works and it will downgrade
Click to expand...
Click to collapse
Thank you so much for responding.
So I finally went out and bought an sd card yesterday to try this and I am having no luck.
I tried unzipping the file, but it just creates a duplicate zip file so I simply tried installing the whole package.
Wether I try and install via sd card or via sideload/adb I get the same "installation aborted" message.
This is so frustrating. All I want is to root again! I'm trying to get this phone to last me as long as I can before replacing it.
Doing this all on a Mac, fyi. Not sure if that changes things. Since we're not using EDL or Axon7toolkit I assumed it doesn't matter, but there is a lot that I don't know.
Thanks for any help that you're able to provide!
alajoy said:
Thank you so much for responding.
So I finally went out and bought an sd card yesterday to try this and I am having no luck.
I tried unzipping the file, but it just creates a duplicate zip file so I simply tried installing the whole package.
Wether I try and install via sd card or via sideload/adb I get the same "installation aborted" message.
This is so frustrating. All I want is to root again! I'm trying to get this phone to last me as long as I can before replacing it.
Doing this all on a Mac, fyi. Not sure if that changes things. Since we're not using EDL or Axon7toolkit I assumed it doesn't matter, but there is a lot that I don't know.
Thanks for any help that you're able to provide!
Click to expand...
Click to collapse
If it's saying that error then it's probably not letting you downgrade.
Also this might be slightly more difficult since you're in a Mac. Can you get access to a windows machine at all? This is why I hate macs
Teet1 said:
If it's saying that error then it's probably not letting you downgrade.
Also this might be slightly more difficult since you're in a Mac. Can you get access to a windows machine at all? This is why I hate macs
Click to expand...
Click to collapse
So what would be the reason that it wouldn't let me downgrade?
I've always used a mac and always managed to find an answer. Sure, toolkits don't work, but using fastboot and adb and doing it that way always has. Now suddenly no fastboot and I'm screwed... I don't really have access to a windows pc.
I just find it hard to believe that it's simply not possible on a mac.
alajoy said:
So what would be the reason that it wouldn't let me downgrade?
I've always used a mac and always managed to find an answer. Sure, toolkits don't work, but using fastboot and adb and doing it that way always has. Now suddenly no fastboot and I'm screwed... I don't really have access to a windows pc.
I just find it hard to believe that it's simply not possible on a mac.
Click to expand...
Click to collapse
Yeah fastboot screen was removed in newer versions. But that's at a software level of the phone. On your computer, the adb and fastboot commands are universal. It's usable on Mac, Linux and windows. The tools used for the phone like miflash or axon7tool are made for windows though and you kinda need those to fix bricked phones. There's a way to force push the twrp image into the recovery partition via adb but I don't know what the name of the recovery partition is
@alajoy: You can give yourself access to a fake Windows on your Mac. It's called a virtual machine. VirtualBox is one free software that can do this. Pretty easy to use, you install a virtualized Windows that you can boot into. Then you can run all Windows-based tools out there. It's also easy to share a USB port with the VM. Then flashing tools can access it. I run Linux as my main OS on a Sager gaming laptop, this is how I flash my A7 and Samsung phones. It just works, and reliably. I do also have a real Windows 10 installed on a partition on the same PC, but that is only for gaming and I never, ever allow it to connect to the Internet.
@Teet1: The literal name of the recovery partition is exactly that, recovery. And that is what most Android devices call it, regardless of manufacturer. It doesn't matter whether it is TWRP or ZTE stock recovery, the name is the same. It can be accessed via the paths:
/dev/block/platform/soc/624000.ufshc/by-name/recovery
/dev/block/bootdevice/by-name/recovery
/dev/block/sde14
On other devices the path may be different (but the 2nd example above will work for most), but the name is usually the same.
AnonVendetta said:
@alajoy: You can give yourself access to a fake Windows on your Mac. It's called a virtual machine. VirtualBox is one free software that can do this. Pretty easy to use, you install a virtualized Windows that you can boot into. Then you can run all Windows-based tools out there. It's also easy to share a USB port with the VM. Then flashing tools can access it. I run Linux as my main OS on a Sager gaming laptop, this is how I flash my A7 and Samsung phones. It just works, and reliably. I do also have a real Windows 10 installed on a partition on the same PC, but that is only for gaming and I never, ever allow it to connect to the Internet.
@Teet1: The literal name of the recovery partition is exactly that, recovery. And that is what most Android devices call it, regardless of manufacturer. It doesn't matter whether it is TWRP or ZTE stock recovery, the name is the same. It can be accessed via the paths:
/dev/block/platform/soc/624000.ufshc/by-name/recovery
/dev/block/bootdevice/by-name/recovery
/dev/block/sde14
On other devices the path may be different (but the 2nd example above will work for most), but the name is usually the same.
Click to expand...
Click to collapse
By name i meant the path, are you sure that's the path for our device? I tried that once and it was not that. Either way he is able to do it
@Teet1: Yeah, I'm sure, but not on all 3 paths. /dev/sde14 may be correct or not, depending on firmware/boot stack that is installed (or the presence of a vendor partition, which might change the paths). But the other 2 should be as I listed.
Just open a root file manager and see for yourself. I use Total Commander, which also shows symbolic links (the one with "bootdevice" in the path is really just a symlink to 624000.ufshc). Getting the recovery path from the example with "bootdevice" in the name should also work on almost any device running Android, and will generally point to the recovery partition. You can see the paths in TWRP too, but TWRP doesn't show symlink (but you should be able to see them if you use the right commands in any terminal, like TWRP's terminal).
hi im trying to root my phone on android 9 and i have tried 10 different wayds and all of them show error problem i can actually root it but no wifi and if i flash it along with BTS files it boot wifi works but no freaking idea what going on i tried solution that says that fix that but in vain nothing seems to work for me and im bout to drop again and forget rooting again because it look easy but i cannot do it nobody seems to have the same problem and it make me angry what can i do guy i really need some help there i have BTS files i replace stock with patched magisk_patched.img but as i said wifi wont work ...why???? i dont get why it is so hard...so i really need any help because i dont know what to do now...
i really just want to root no twrp as twrp always lock me from touch input no otg and wont get one is there anyone that can help me ?
Conker27 said:
hi im trying to root my phone on android 9 and i have tried 10 different wayds and all of them show error problem i can actually root it but no wifi and if i flash it along with BTS files it boot wifi works but no freaking idea what going on i tried solution that says that fix that but in vain nothing seems to work for me and im bout to drop again and forget rooting again because it look easy but i cannot do it nobody seems to have the same problem and it make me angry what can i do guy i really need some help there i have BTS files i replace stock with patched magisk_patched.img but as i said wifi wont work ...why???? i dont get why it is so hard...so i really need any help because i dont know what to do now...
Click to expand...
Click to collapse
Hope this is nothing to do with an update blocking root, I want to root when out of warranty. At least for me it's months away & hope someone finds a method by then. Hope you find an answer to your problem