ok. So i continue to get this error
Error failed to initialize protocol!
I do not know what i have done wrong and i have tried many different versions of heimdall with no luck.
i would try to use a VM or something like this but i have no experience and do not know how to start with that. Any info on this would help a lot.
Can anyone point me in the right direction? Has anyone successfully completed root with a mac on a verizon version of the SS3???
Related
Hi,
Trying to root my Wildfire/Buzz 2.2.1 ..... everything looks great until unrevoked3 ends with the message "Error: failed to get root. Is your firmware too new?". Any ideas what to do? Downgrade from 2.2.1 is a mess (I guess) so any ideas are welcome.
Try this: http://www.theprohack.com/2011/04/htc-wildfire-221-root-to-htc-wildfire.html.
Setup.exe has encountered a problem .....
..... and needs to close. This is what I get when trying to run the downloaded "RUU_Buzz_HTC_WWE............." file from the link you posted.
So i have been getting boot loops on every rom i've tried to flash from my sdcard in cwm. I tried using heimdall one-click on my mac but it keeps getting stuck at "claiming interface". I've already searched many threads but found nothing. Any help on how to fix this?
not to many people are giving up information on heimdall with a Mac. I know the web page talks about something called codeless kext but I don't have a Mac and have no idea what that is. my suggestion is to put Ubuntu on it.... jk but heimdall on Ubuntu is stupid easy, getting the video and wifi and cd-rom can be another story depending on your hardware. I think most Mac users are not to savvy or they'd just be running Linux I know osx is a great OS but it seems to lack users that like to tinker. well not totally true but with so few users the guys that really know Macs are hard to come by.
are you getting that message when you are installing one click to mac ?
Any help or advice here would be GREATLY appreciated --
Q: Is it possible to get root on my S3? SCH-I535 running stock android 4.3 (I535VRUCNC1)
First, I am new to rooting so please refrain from ridicule... I have been online literally since this morning trying to find a way to do this, so needless to say I have searched. Tried Motochopper in OS X, and when that didn't work, went so far as to install Windows in VMware to try saferoot and CF autoroot--still no luck. From what I've read, I am I correct in understanding that this may not be possible? Bottom line: All I want is root in order to mount the internal memory to a volume for recovery of deleted files.
Thanks!
You're gonna have to ODIN back to ML1. NC1 has a Saferoot/Safestrap patch... The is thread on it. XDA search is your friend...
Sent from my SCH-I535 using XDA Premium 4 mobile app
Try this:
http://nasirtech.blogspot.com/2014/04/root-i535vrucnc1-android-43-stock.html
Thanks guys, but I've just about given up on this and am not too eager to dig my hole deeper. I'll spare the details as to why I'm doing this, but at this rate I also wonder if my files could even be recovered from internal memory after 2 days anyway.
I tried reverting to ML1 with the method here: [GUIDE Win/Linux/Mac] Debrick 4.3 with Odin or Verizon Utility + PIT [SOFT BRICK]
and had even worse luck as it ended up soft-bricking my phone into Odin/download mode loop that said "firmware upgrade encountered an issue..." Fortunately this morning I gave it one last go assuming nothing to lose and tried repartitioning with just the pit file in Odin 3.07, and that got it to reboot.
@Rushead, I have tried the method in that link to the best of my ability and haven't had any luck. It fails at writing NAND.
I wonder if the fact that I'm attempting this on my mac in a Windows XP x64 virtual machine is part of the problem. I hadn't used it in years and ran a ton of updates, but I've been getting errors to the effect of "Wlanapi.dll is missing" since installing the samsung drivers and Kies. Perhaps I just can't get the drivers to install correctly?
messier42 said:
Thanks guys, but I've just about given up on this and am not too eager to dig my hole deeper. I'll spare the details as to why I'm doing this, but at this rate I also wonder if my files could even be recovered from internal memory after 2 days anyway.
I tried reverting to ML1 with the method here: [GUIDE Win/Linux/Mac] Debrick 4.3 with Odin or Verizon Utility + PIT [SOFT BRICK]
and had even worse luck as it ended up soft-bricking my phone into Odin/download mode loop that said "firmware upgrade encountered an issue..." Fortunately this morning I gave it one last go assuming nothing to lose and tried repartitioning with just the pit file in Odin 3.07, and that got it to reboot.
@Rushead, I have tried the method in that link to the best of my ability and haven't had any luck. It fails at writing NAND.
I wonder if the fact that I'm attempting this on my mac in a Windows XP x64 virtual machine is part of the problem. I hadn't used it in years and ran a ton of updates, but I've been getting errors to the effect of "Wlanapi.dll is missing" since installing the samsung drivers and Kies. Perhaps I just can't get the drivers to install correctly?
Click to expand...
Click to collapse
Try an actual Windows machine before giving up hope bud
Rushead said:
Try this:
http://nasirtech.blogspot.com/2014/04/root-i535vrucnc1-android-43-stock.html
Click to expand...
Click to collapse
There are links to this guy all over. However, I can't get it to work and neither can anybody else as far as I can see. Don't bother.
Thought I would be brave and root my note and then upgrade to android 4.4. So much for easy!
The root worked and when I tried to run the cm-11-20141031-UNOFFICIAL-n8013 zip file it aborted saying that it was for devices including GT-N8013 which is what I have. The zip program is telling me that my device is p4noterf. Also says it has a status 7error.
Saw one thread that started to talk about, but didn't go far. Talking about Philz.
Any help would be greatly appreciated. Not bricked yet but close enough to make me give up for now.
Bill
wmcampjr said:
Thought I would be brave and root my note and then upgrade to android 4.4. So much for easy!
The root worked and when I tried to run the cm-11-20141031-UNOFFICIAL-n8013 zip file it aborted saying that it was for devices including GT-N8013 which is what I have. The zip program is telling me that my device is p4noterf. Also says it has a status 7error.
Saw one thread that started to talk about, but didn't go far. Talking about Philz.
Any help would be greatly appreciated. Not bricked yet but close enough to make me give up for now.
Bill
Click to expand...
Click to collapse
Hi... I'm having the same issue but trying to install CM12... have you been able to get to a solution??
Same problem here.
My device is p4notewifiww, but CWM keeps telling me that it's p4noterf.
I'm googling it, but I can't find anything.
Hey there guys. I bought an HTC One M7 from amazon which came unlocked. Problem was, i couldnt get it to connect to my provider, Koodo. Long story short, i went to flash a Stock Telus Rom to it, no META file in the zip. Already wiped my phone. So now theres no OS. I have TWRP still (thank god for that) but it just sits at the HTC logo and wont boot, as i know thats what happens when you mess up. Fairly familiar with THIS issue, as ive done it to my Samsung Galaxy SIII MANY times before, but had odin to fix it. I have an RUU.exe. Got it from a forum here. Cant connect to my phone (error 171 i believe). Everything is connected properly, and my PC recognizes it, but only as an MTP device. I am gonna try an RUU.zip and flash it with fastboot. See if that method works. But any help at all would be GREATLY appreciated as i dont want to have spent $299 to waste it like betting on the Maple Leafs.
Side note: I cannot get ADB Sideloader to work properly. I have a Custom Rom that i attempted to flash that way, but i got the error that was like ADB version (31) is not up to date with server (36) or something along the lines of that and then it fails to load daemon everytime. Tried some fixes from these forums but none of them were successful. Not familliar with ADB and all that stuff, so if anyone has any fix for the ADB, please dumb it down to kindergardener levels.
Sorry this is so long. Tried to explain everything as detailed as possible for a more acturately helpful response.
UPDATE Got the RUU.zip file to work after a couple hours of messing around with it. Had to fast boot getvar to obtain my model id, and change that in the android-info.txt in the zip file. Is flashing now. HUGE thanks to all of the thousands of XDA forums. Helped me out with everything!
AndyA2098 said:
Hey there guys. I bought an HTC One M7 from amazon which came unlocked. Problem was, i couldnt get it to connect to my provider, Koodo. Long story short, i went to flash a Stock Telus Rom to it, no META file in the zip. Already wiped my phone. So now theres no OS. I have TWRP still (thank god for that) but it just sits at the HTC logo and wont boot, as i know thats what happens when you mess up. Fairly familiar with THIS issue, as ive done it to my Samsung Galaxy SIII MANY times before, but had odin to fix it. I have an RUU.exe. Got it from a forum here. Cant connect to my phone (error 171 i believe). Everything is connected properly, and my PC recognizes it, but only as an MTP device. I am gonna try an RUU.zip and flash it with fastboot. See if that method works. But any help at all would be GREATLY appreciated as i dont want to have spent $299 to waste it like betting on the Maple Leafs.
Side note: I cannot get ADB Sideloader to work properly. I have a Custom Rom that i attempted to flash that way, but i got the error that was like ADB version (31) is not up to date with server (36) or something along the lines of that and then it fails to load daemon everytime. Tried some fixes from these forums but none of them were successful. Not familliar with ADB and all that stuff, so if anyone has any fix for the ADB, please dumb it down to kindergardener levels.
Sorry this is so long. Tried to explain everything as detailed as possible for a more acturately helpful response.
UPDATE Got the RUU.zip file to work after a couple hours of messing around with it. Had to fast boot getvar to obtain my model id, and change that in the android-info.txt in the zip file. Is flashing now. HUGE thanks to all of the thousands of XDA forums. Helped me out with everything!
Click to expand...
Click to collapse
Thread closed as OP fixed his issue