Related
Hey all. Unfortunately, I can't post in the development forum because this is my seventh post. :crying: Anyways, I had a comment about the verizon root and hopefully somebody can either move this to that sticky or answer... Anyways...
I wanted to see what was done to the modified image to make sure nothing strange was put in it. I downloaded the 'orig' from fus, extracted the image, and ran a md5 check on all the files. I then downloaded your system.img file and ran a md5check on all the files. I found two files were added...
#
330a331
> 65bd72996c68f289c5fa0b81f0874127 app/Superuser.apk
2007a2009
> d1a9de9724c662a50a9a128e48b1fb37 xbin/su
#
When I tried to find the versions of those files and the md5 hashes, they don't match. Here's your version...
65bd72996c68f289c5fa0b81f0874127 app/Superuser.apk
d1a9de9724c662a50a9a128e48b1fb37 xbin/su
I then downloaded 'superuser' from http://androidsu.com/superuser/, which I'm assuming is the source. For the 3.1.3 version, I get this...
MD5 (system/app/Superuser.apk) = e0bc7b7284b68c9539b6ec6b306310e0
MD5 (system/bin/su) = 054c9a22d8900d50ce6172fd56bbf414
For the 3.2-RC2 version, I get this...
MD5 (system/app/Superuser.apk) = d0abb9413f712f2f7dd43ed47df6c2d8
MD5 (system/bin/su) = 96c672c1339da363232f42dd87b4a3cf
As you can see, the md5's are different which make me a little uneasy about it. I was wondering if anybody knew of the source for these. I think I just email'ed invisiblek the same thing, but don't know if it would get to him or not. Maybe somebody else knows the answer.
Thanks!
WTF?
Im confused, I see active topics saying the S3 hasn't got root yet due to the locked boot loader, I also see active topics saying it has been unlocked + rooted..
answer
OK, I still haven't got my s3, so I haven't tried it. But from what I read, you can flash a custom system.img and put su and supervisor.apk on it. This allows you to get 'root' on the device. Here's a reference...
http://forum.xda-developers.com/showthread.php?t=1756885
Verizon Failed on on Odin now stuck at SIII boot screen
wiz561 said:
OK, I still haven't got my s3, so I haven't tried it. But from what I read, you can flash a custom system.img and put su and supervisor.apk on it. This allows you to get 'root' on the device. Here's a reference...
http://forum.xda-developers.com/showthread.php?t=1756885
Click to expand...
Click to collapse
Verizon Failed on on Odin now stuck at SIII boot screen
I tried the procedure with rooted.system.img and Odin 3.07 and it threw root Xmit Write fail. Then it just hung.
I pulled the battery and now it won't boot. I tried doing Vol Up + Home to do a hard reset to no avail.
I also tried Samsung-Updates.com-SCH-I535_VZW_1_20120705143513_fti2qg2lmf file through Odin with no success.
I've rooted phones in the past but never through this method.
I'm hoping I haven't bricked it.
I have a spare 16 GB card if I can recover something that way.
I can't reactivate my old Rezound because now the SIM card is invalid and they are two different sizes so I can't use the new one in the old phone.
1. Bootloader is [still] locked
2. Root has been achieved
Solved the problem. I tried a better micro usb cable and a different usb port.
Everything went great after that. I'm now rooted fully.
daffy113 said:
Verizon Failed on on Odin now stuck at SIII boot screen
I tried the procedure with rooted.system.img and Odin 3.07 and it threw root Xmit Write fail. Then it just hung.
I pulled the battery and now it won't boot. I tried doing Vol Up + Home to do a hard reset to no avail.
I also tried Samsung-Updates.com-SCH-I535_VZW_1_20120705143513_fti2qg2lmf file through Odin with no success.
I've rooted phones in the past but never through this method.
I'm hoping I haven't bricked it.
I have a spare 16 GB card if I can recover something that way.
I can't reactivate my old Rezound because now the SIM card is invalid and they are two different sizes so I can't use the new one in the old phone.
Click to expand...
Click to collapse
..
The answer is that this type of question doesn't belong in the dev threads, but in the S3 Q&A forum. If MD5 doesn't match, then you have a bad download or bad copy, or the posted MD5 is incorrect.
Unable to Root VZW SG3
I have been unable to download the Samsung ADB interface driver for my phone. So I can't root using Debugs ADB root method. Is there something I need to do in order to get ADB installed for my device so it can recognize my phone?
luisdr007 said:
I have been unable to download the Samsung ADB interface driver for my phone. So I can't root using Debugs ADB root method. Is there something I need to do in order to get ADB installed for my device so it can recognize my phone?
Click to expand...
Click to collapse
Download works in Droidstyles guide.
http://forum.xda-developers.com/showpost.php?p=28530394&postcount=1
prdog1 said:
Download works in Droidstyles guide.
http://forum.xda-developers.com/showpost.php?p=28530394&postcount=1
Click to expand...
Click to collapse
thanks, but not sure what you mean. i've clicked on the link but not sure where to go. I see the section for windows OS, but not sure what to download.
luisdr007 said:
thanks, but not sure what you mean. i've clicked on the link but not sure where to go. I see the section for windows OS, but not sure what to download.
Click to expand...
Click to collapse
Here is direct link from Samsung.
http://www.samsung.com/us/support/owners/product/SCH-I535MBBVZW
Click see all downloads>software
prdog1 said:
Here is direct link from Samsung.
Click see all downloads>software
Click to expand...
Click to collapse
thank you. i will uninstall the current drivers, reboot, and install these and see what happens.
prdog1 said:
Here is direct link from Samsung.
Click see all downloads>software
Click to expand...
Click to collapse
I tried installing drivers again, but no avail. i keep getting "There was a problem installing this hardware, SAMSUNG Android ADB Interface. This device is not configured correctly. (code 1)" Not sure what else to do.
Did you reboot the PC
prdog1 said:
Did you reboot the PC
Click to expand...
Click to collapse
I uninstalled, rebooted, and then installed new drivers, and still getting that error. I can't seem to figure out what the problem is. I also installed Kies, and SDK, and still can't get to work.
luisdr007 said:
I uninstalled, rebooted, and then installed new drivers, and still getting that error. I can't seem to figure out what the problem is. I also installed Kies, and SDK, and still can't get to work.
Click to expand...
Click to collapse
Need to reboot PC after drivers are installed and make sure usb debug is turned on in phone settings.
prdog1 said:
Need to reboot PC after drivers are installed and make sure usb debug is turned on in phone settings.
Click to expand...
Click to collapse
ok, I did not reboot after I installed drivers. USB debugging is checked on the phone. Let me reboot PC and I will keep you posted. thank you very much for you help with this. I'm not new to rooting, but I am new to the Samsung phones. I've had the DX for the last 2 years, and never had issues rooting or flashing ROMS.
prdog1 said:
Need to reboot PC after drivers are installed and make sure usb debug is turned on in phone settings.
Click to expand...
Click to collapse
So I rebooted and I'm not getting the error. But adb is still not recognizing my device.
luisdr007 said:
So I rebooted and I'm not getting the error. But adb is still not recognizing my device.
Click to expand...
Click to collapse
ADB shows mine as offline emulator.
hi, ive been having issues rooting this phone.
Ive tried 4 different cables & 2 different laptops.
Have the latest usb drivers + the samsung drivers. I did notice that it cant be found in device manager.
when i click on the bat file in qbkings one click root folder, i get "device not found". <duh
Usb debugging is enabled. Could the phone itself be damaged?
You're better off unlocking the bootloader and flashing custom recovery through adb. The directions aren't difficult to find (I'd link you but I'm on my phone). That way if something goes wrong you know where it failed instead of being dependent on a piece of software.
I wish everybody did it this way. Plus, I 100% agree with your statement. Not only that, you learn a few things along the way
mrmondaynight said:
hi, ive been having issues rooting this phone.
Ive tried 4 different cables & 2 different laptops.
Have the latest usb drivers + the samsung drivers. I did notice that it cant be found in device manager.
when i click on the bat file in qbkings one click root folder, i get "device not found". <duh
Usb debugging is enabled. Could the phone itself be damaged?
Click to expand...
Click to collapse
Before trying to root the phone, did you ever connect to any computer at all?
And what ru on...GB 2.37?
Vs Nexus S 4G
063_XOBX said:
You're better off unlocking the bootloader and flashing custom recovery through adb. The directions aren't difficult to find (I'd link you but I'm on my phone). That way if something goes wrong you know where it failed instead of being dependent on a piece of software.
Click to expand...
Click to collapse
man, im slow. Im having a hard time locating the directions :crying:
vidaljs said:
Before trying to root the phone, did you ever connect to any computer at all?
And what ru on...GB 2.37?
Vs Nexus S 4G
Click to expand...
Click to collapse
Yes.
Same issue. Even with usb storage.
phone is on ICS 4.0.4 via ota update.
http://forum.xda-developers.com/showthread.php?t=1623481
Step by Step Root is here in the sticky. If the phone isn't seen just to see the SD card then the phones USB may be shot and that is a hardware issue.
Can i use the Nexus5 with a MacBook Pro? What about rooting with a Mac? Thanks.
grunt0300 said:
Can i use the Nexus5 with a MacBook Pro? What about rooting with a Mac? Thanks.
Click to expand...
Click to collapse
1) This goes in the Q&A forum.
2) Yes. http://www.phonearena.com/news/How-to-root-Google-Nexus-5_id49014
3) Next time do a Google search. Literally took 15 seconds to find that.
You need AFT to transfer files between your phone and your mac via USB
http://www.android.com/filetransfer/
_MetalHead_ said:
You need AFT to transfer files between your phone and your mac via USB
http://www.android.com/filetransfer/
Click to expand...
Click to collapse
AFT never worked with my SGSIII, and it still doesn't work. I partitioned my Mac because of AFT, so i don't really need it. Just checking to see if that app still sucked, and it does. Thanks anyway.
grunt0300 said:
AFT never worked with my SGSIII, and it still doesn't work. I partitioned my Mac because of AFT, so i don't really need it. Just checking to see if that app still sucked, and it does. Thanks anyway.
Click to expand...
Click to collapse
Hmm works for me on my Mac, no issues.
jawmail said:
Hmm works for me on my Mac, no issues.
Click to expand...
Click to collapse
AFT works here for a couple years now. GN, Note 2, N4 and N5 all work here on 10.6 to 10.8. Try reinstall maybe.
BruceCLin said:
AFT works here for a couple years now. GN, Note 2, N4 and N5 all work here on 10.6 to 10.8. Try reinstall maybe.
Click to expand...
Click to collapse
Running Mavericks 10.9. That may be the problem.
grunt0300 said:
Running Mavericks 10.9. That may be the problem.
Click to expand...
Click to collapse
I'm running 10.9 and AFT works just fine.
Exel said:
I'm running 10.9 and AFT works just fine.
Click to expand...
Click to collapse
O.K. I installed AFT, then uninstalled it. I'll try reinstalling it, and see what happens. My phone is rooted. Could that be the problem?
grunt0300 said:
O.K. I installed AFT, then uninstalled it. I'll try reinstalling it, and see what happens. My phone is rooted. Could that be the problem?
Click to expand...
Click to collapse
Mine is rooted as well.
Try toggling USB Debugging on / off depending on what its set at.
AFT is tricky, sometimes it won't work if USB Debugging is off for me, other times it won't work if its on, lol.
Exel said:
Mine is rooted as well.
Try toggling USB Debugging on / off depending on what its set at.
AFT is tricky, sometimes it won't work if USB Debugging is off for me, other times it won't work if its on, lol.
Click to expand...
Click to collapse
Tried everything that i could think of, but it still says "could not connect to device".
That's strange. I've used AFT on Mavericks with a Galaxy Nexus, GSIII, HTC One, and the Nexus 5. After you install it run it once without the phone and try it again. Get Appcleaner and uninstall AFT and start fresh.
grunt0300 said:
Tried everything that i could think of, but it still says "could not connect to device".
Click to expand...
Click to collapse
If you have Samsung Kies installed, AFT won't work.
ronakg said:
If you have Samsung Kies installed, AFT won't work.
Click to expand...
Click to collapse
Don't have Kies installed. I uninstalled it about six months ago. Would the drivers still be in place, even after the uninstall?
I resorted to just ADB pushing files to the Nexus 5 with my Macbook pro. It's easy enough to do and once you get used to it the process is really quick.
Follow the guide in this link to setup your computer properly for most efficient use of ADB and Fastboot commands:
http://forum.xda-developers.com/showthread.php?t=1917237
When it comes to moving or deleting files on the phone I just use Root Explorer.
Exel said:
Mine is rooted as well.
Try toggling USB Debugging on / off depending on what its set at.
AFT is tricky, sometimes it won't work if USB Debugging is off for me, other times it won't work if its on, lol.
Click to expand...
Click to collapse
You can also try AirDroid. Runs through the browser and is free. A great little cable free solution.
mdandashly said:
You can also try AirDroid. Runs through the browser and is free. A great little cable free solution.
Click to expand...
Click to collapse
^ what he said, Airdroid works great.
So I wanted to wake up my nexus 5 with the volume buttons. Looking online I found that you could add code to your build.prop.. which I did.. then rebooted...
Now my phone does 'nothing'... When I press the power button it vibrates 2 times and nothing happens...
Help!.. Have no idea what i can do to get things running again
P.S. I've got Slimkat ROM running
S.Phrenic said:
So I wanted to wake up my nexus 5 with the volume buttons. Looking online I found that you could add code to your build.prop.. which I did.. then rebooted...
Now my phone does 'nothing'... When I press the power button it vibrates 2 times and nothing happens...
Help!.. Have no idea what i can do to get things running again
P.S. I've got Slimkat ROM running
Click to expand...
Click to collapse
Can you get into bootloader? Recovery?
Lethargy said:
Can you get into bootloader? Recovery?
Click to expand...
Click to collapse
Currently, nope... I'm trying.. I see that sometimes the screen is on... sometimes I see the Google Logo... but Can't fully figure out when that happens
[EDIT]YES!!!!!!!!! Got in.!!!!!!... *pfieuw*.. now what do i do?
Reflash the factory with the nexus root toolkit
Croc on Nexus 5 with Mahdi + ElementalX
Croc97 said:
Reflash the factory with the nexus root toolkit
Croc on Nexus 5 with Mahdi + ElementalX
Click to expand...
Click to collapse
Please don't use toolkits.
Croc97 said:
Reflash the factory with the nexus root toolkit
Croc on Nexus 5 with Mahdi + ElementalX
Click to expand...
Click to collapse
Don't exaclty know what you mean with that..
I've downloaded Kwongger's Nexus 5 All-In-One Toolkit , I hope that's what you meant. And then it says it's missing the hammerhead.image.zip... which I assume is the stockROM?.. If so, shouldn't I Reflash to Slimkat?
Sorry for being such a Noob. I've had Samsung for years and just switched to Nexus (bought it last week). Still need to learn my way around things
S.Phrenic said:
Don't exaclty know what you mean with that..
I've downloaded Kwongger's Nexus 5 All-In-One Toolkit , I hope that's what you meant. And then it says it's missing the hammerhead.image.zip... which I assume is the stockROM?.. If so, shouldn't I Reflash to Slimkat?
Sorry for being such a Noob. I've had Samsung for years and just switched to Nexus (bought it last week). Still need to learn my way around things
Click to expand...
Click to collapse
Read my reply to your PM and the 2nd link in my signature, then refer to the first link if you need
Lethargy said:
Read my reply to your PM and the 2nd link in my signature, then refer to the first link if you need
Click to expand...
Click to collapse
Let me start with, Thank you so much for your time
However, It seems like I'm unable to install the right drivers on my PC for my phone and adb doesn't detect my device (which is strange as CF-auto-root did see the device and worked fine)
I walked through multiple tutorials about installing drivers. Actually have windows detecting my phone fine (I see it in device manager) and I've reinstalled google USB drivers multiple times now, rebooting my PC and deleting drivers and reinstalling them
I've justed factory reset my phone, but that just got me to a Google logo stuck (which I read about in your link in your signature)..
Because adb doesn't detect my device I'm unable to pull build.prop... which means I feel stuck again.
Would you have a direction for me to go towards to continue my journey through Nexus5-Land?
S.Phrenic said:
Let me start with, Thank you so much for your time
However, It seems like I'm unable to install the right drivers on my PC for my phone and adb doesn't detect my device (which is strange as CF-auto-root did see the device and worked fine)
I walked through multiple tutorials about installing drivers. Actually have windows detecting my phone fine (I see it in device manager) and I've reinstalled google USB drivers multiple times now, rebooting my PC and deleting drivers and reinstalling them
I've justed factory reset my phone, but that just got me to a Google logo stuck (which I read about in your link in your signature)..
Because adb doesn't detect my device I'm unable to pull build.prop... which means I feel stuck again.
Would you have a direction for me to go towards to continue my journey through Nexus5-Land?
Click to expand...
Click to collapse
If you're using Windows 8, 8.1 or 8.1U1 you'll need to disable driver signature enforcement.
Try flashing the factory images in fastboot?
Could somebody not just make a flashable zip with the correct build.prop?
Failing that, just reflash the ROM.
Lethargy said:
If you're using Windows 8, 8.1 or 8.1U1 you'll need to disable driver signature enforcement.
Try flashing the factory images in fastboot?
Click to expand...
Click to collapse
It seems like it worked! Completly back to StockROM but the phone works again. Thank you so much for your time.
And you're right, I should learn to read and understand what I'm doing before I do anything with my phone. Sorry for the inconvenience and thank you for the help you've given.
S.Phrenic said:
It seems like it worked! Completly back to StockROM but the phone works again. Thank you so much for your time.
And you're right, I should learn to read and understand what I'm doing before I do anything with my phone. Sorry for the inconvenience and thank you for the help you've given.
Click to expand...
Click to collapse
Glad you got it worked out
S.Phrenic said:
It seems like it worked! Completly back to StockROM but the phone works again. Thank you so much for your time.
And you're right, I should learn to read and understand what I'm doing before I do anything with my phone. Sorry for the inconvenience and thank you for the help you've given.
Click to expand...
Click to collapse
Glad you got it sorted but, unless you couldn't boot into recovery, you didn't need to go back to stock.
Flashing the correct build.prop or ROM you were using should have sorted it out, without losing any data (you would have lost any system mods if you flashed the ROM again, though).
I'm only mentioning this in case somebody else searches and finds this thread for the same problem.
I've changed the build.prop loads of times on many devices and only once it went into a bootloop. Flashing a build.prop zip sorted it.
Hello all,
I did a big mistake, I wanted to go back from DP 3 to Android 11 and once I was going to do the CMD steps, I downloaded the wrong Firmware for the Pixel 5
I didnt see that mistake until I started the steps and the phone turned off and did not turn on anymore.
I know I made a big mistake, but can I do to revert this? I try to restart the phone but nothing, not via power button for 10 or 20 or 30 sec.
Please help
vlc_marcos said:
Hello all,
I did a big mistake, I wanted to go back from DP 3 to Android 11 and once I was going to do the CMD steps, I downloaded the wrong Firmware for the Pixel 5
I didnt see that mistake until I started the steps and the phone turned off and did not turn on anymore.
I know I made a big mistake, but can I do to revert this? I try to restart the phone but nothing, not via power button for 10 or 20 or 30 sec.
Please help
Click to expand...
Click to collapse
No duplicated thread are permitted
Please help us to keep the forums neat
Thanks
vlc_marcos said:
I downloaded the wrong Firmware for the Pixel 5
Click to expand...
Click to collapse
So you used a firmware that was older or one that was for a different device?
Is the bootloader unlocked?
What exactly did you download?
Does the phone charge?
l7777 said:
So you used a firmware that was older or one that was for a different device?
Is the bootloader unlocked?
What exactly did you download?
Does the phone charge?
Click to expand...
Click to collapse
I used the firmware of pixel 4a 5g and I wanted to go from DP3 to android 11.
I cannot see the phone charging . I try long press in any of the buttons and different combinations and nothing. Zero signs of life
vlc_marcos said:
I used the firmware of pixel 4a 5g and I wanted to go from DP3 to android 11.
I cannot see the phone charging . I try long press in any of the buttons and different combinations and nothing. Zero signs of life
Click to expand...
Click to collapse
when its plugged into a computer does the computer see it at all?
thewraith420 said:
when its plugged into a computer does the computer see it at all?
Click to expand...
Click to collapse
not at all is there some kind of hard unbrick??
vlc_marcos said:
not at all is there some kind of hard unbrick??
Click to expand...
Click to collapse
Unfortunately i think your only option will be to send it in to google at this point.. wish you luck though maybe someone has an idea.
thewraith420 said:
Unfortunately i think your only option will be to send it in to google at this point.. wish you luck though maybe someone has an idea.
Click to expand...
Click to collapse
Mine bricked about a month ago and Google suggested uBreakiFix. They tried to do a force flash on it but it didn't work. They ended up replacing the motherboard which fixed it, but now my proximity sensor is always on. I don't know if they can fix that or if it will require another motherboard.
I have same problem, but i can go to bootloader. The problem my phone is locked bootloader and i don't have recovery mode. And when i try to flash it because of locked bootloader i can't do anything. Is there any solution for unbrick locked bootloader?
p_a_r_s_a7 said:
I have same problem, but i can go to bootloader. The problem my phone is locked bootloader and i don't have recovery mode. And when i try to flash it because of locked bootloader i can't do anything. Is there any solution for unbrick locked bootloader?
Click to expand...
Click to collapse
Did you use any special way to even turn on the phone or reach the bootloader?
vlc_marcos said:
Did you use any special way to even turn on the phone or reach the bootloader?
Click to expand...
Click to collapse
I did everything, unfortunately my bootloader is locked and that's problem. With locked bootloader i can't do anything. I had same problems with other phones before and i could unbrick. But for pixel devices i can't find some tool to unbrick.
p_a_r_s_a7 said:
I did everything, unfortunately my bootloader is locked and that's problem. With locked bootloader i can't do anything. I had same problems with other phones before and i could unbrick. But for pixel devices i can't find some tool to unbrick.
Click to expand...
Click to collapse
how did you end up with it like that with bootloader locked? what caused it?
I have the same issue like p_a_r_s_a7 with my Pixel 5.
Only fastboot mode: can't find valid operating system
After flashing the 'right' OTA image for Android 12 DP3 the device cannot be restored anymore.
The image was successfully flashed by 'adb sideload' as recommended.
Seems that a locked bootloader is not 100% save from 'flashed to death'
600 EURO paperwight.
I had this same issue on my 4a 5g and after many hours I managed to fix it. I don't recall exactly but I went through every option of flashing stock via fastboot and android flash tool it eventually worked this was 2 months ago
Cj719 said:
I had this same issue on my 4a 5g and after many hours I managed to fix it. I don't recall exactly but I went through every option of flashing stock via fastboot and android flash tool it eventually worked this was 2 months ago
Click to expand...
Click to collapse
But you could reach fastboot right?
Cj719 said:
I had this same issue on my 4a 5g and after many hours I managed to fix it. I don't recall exactly but I went through every option of flashing stock via fastboot and android flash tool it eventually worked this was 2 months ago
Click to expand...
Click to collapse
Android flash tool immediately detect the locked bootloader and stopped without flashing.
I've tried to check/uncheck every option but no luck. I've used Windows 10.
Did you used the common USB driver requested by Android flash tool ?
Anything else that could be special, eg Linux environment ( what distro, version .. )
Any detail could help..
speo said:
Android flash tool immediately detect the locked bootloader and stopped without flashing.
I've tried to check/uncheck every option but no luck. I've used Windows 10.
Did you used the common USB driver requested by Android flash tool ?
Anything else that could be special, eg Linux environment ( what distro, version .. )
Any detail could help..
Click to expand...
Click to collapse
Windows 10 laptop, adb minimal drivers, made sure device was detected, attempted through fastboot and android flash tool, that's the only things I remember my apologies.
speo said:
I have the same issue like p_a_r_s_a7 with my Pixel 5.
Only fastboot mode: can't find valid operating system
After flashing the 'right' OTA image for Android 12 DP3 the device cannot be restored anymore.
The image was successfully flashed by 'adb sideload' as recommended.
Seems that a locked bootloader is not 100% save from 'flashed to death'
600 EURO paperwight.
Click to expand...
Click to collapse
I send back to Google, i couldn't fix it
Cj719 said:
Windows 10 laptop, adb minimal drivers, made sure device was detected, attempted through fastboot and android flash tool, that's the only things I remember my apologies.
Click to expand...
Click to collapse
thank you anyway, it was a little light on the horizon at least ;-)
p_a_r_s_a7 said:
I send back to Google, i couldn't fix it
Click to expand...
Click to collapse
have you been charged ?
Mine is from another dealer, will see..