Related
Hello, all. I am new and am here for one reason today.
Recently, my dad got a new phone and said that I could mess around with his old Droid 2. I decided to root and try and install CM9 on it to get Android 4. That failed, and I was stuck with a bricked phone.
Basically, I was able to successfully root it, but when it came to install CM and its package of Google apps, the phone would not boot past the "M" logo. Here is the site I used mainly to guide me... (website prevents me from posting this link but I will soon update)
Maybe this site is what led me wrong. The downloads of CM9, the Recovery Bootstrap thingy, and the Google apps came from separate sites each... I think maybe they may've been incompatible with each other.
I did what was logical. I removed the battery, tried to power it on again, maybe even somehow boot into ClockworkMod recovery and not have to start over. Sadly this did not work.
Then, I decided to do a bit of research... I then tried to wipe the phone and reboot. Fail.
I finally came across this video which I resorted to... (website prevents me from posting this link but I will soon update)
I would have to unbrick it... a long tedious process, then start from square one... with not guarantee that it'll even work again.
Through this video, I ran into my final problem... it seems my phone won't even load the Bootloader! Every single time I try, it says "Battery Low...Cannot program". It seems there may be a problem with the battery, SINCE I'VE BEEN CHARGING IT FOR 12 HOURS! My theory about this is that it is trying to load CM from my previous attempt, but drains so much battery trying to do so that the battery itself has very little charge. Another note: whenever I plug it in, the phone goes to the "M" logo and freezes. There's no way to completely turn off the thing, except to unplug it and take out the battery. So, I can't even get the bootloader to work in order to unbrick it! That's about as worse it can get.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------
My question to you guys is... what would you do in my place? I am still intent on getting CM on this device, but I can't even fix my current state!
1) how to fix my current problem?
2) experienced rooters and rom-flashers: how to get CM9 (Android 4) on this device without bricking it again?
--- Note that I am a noob and this is my first time doing such a thing. I need ALL details!
Thank you guys sooo much for your time!
does label under battery say a955 or a956?
sd_shadow said:
does label under battery say a955 or a956?
Click to expand...
Click to collapse
A955, sir. Is there any other info I can help provide to further assist you? I'd really like this fixed...
Thanks!
HuiDoge said:
A955, sir. Is there any other info I can help provide to further assist you? I'd really like this fixed...
Thanks!
Click to expand...
Click to collapse
you can try a factory reset in Stock recovery
but most likely need to flash stock firmware 2 options RSD Lite or ezSBF
links in my list
sd_shadow's [Collection] of Links for:
Droid 2 (a955)
Sent from my XT907 using Tapatalk
sd_shadow said:
you can try a factory reset in Stock recovery
but most likely need to flash stock firmware 2 options RSD Lite or ezSBF
links in my list
sd_shadow's [Collection] of Links for:
Droid 2 (a955)[/URL]
Sent from my XT907 using Tapatalk
Click to expand...
Click to collapse
Like I said, I know I can use RSD for a reset, but the thing is the bootloader won't work. The battery is bad, I think, so it ends up saying, "Battery low, Cannot program". Even if I plug it into the computer nothing happens.
HuiDoge said:
Like I said, I know I can use RSD for a reset, but the thing is the bootloader won't work. The battery is bad, I think, so it ends up saying, "Battery low, Cannot program". Even if I plug it into the computer nothing happens.
Click to expand...
Click to collapse
see low battery options in my list
Sent from my XT907 using Tapatalk
sd_shadow said:
see low battery options in my list
Sent from my XT907 using Tapatalk
Click to expand...
Click to collapse
Ok. I will see what I can do. I briefly went over that option in your list.. it seems risky. I am not a person that wants to mess with wires and risk explosions. If I buy another battery, will that do the trick? That'd be safer. I'd rather pay that risk that other stuff. Could you provide me a link to a good battery? I know it sounds dumb but I don't want to get the wrong model.
Thanks for all of your help. I think I'll use your guide to root and get CM9 on that phone.
When I do get the battery and am ready to root and flash, do you think you could chat here step by step with me? I don't want to mess this up again, and you seem like the experienced type of person. Online guides don't really have the best step by step guidance, and even videos sometimes don't do the trick. Though, if you are busy but happen to have a link to a good video, could you send it to me? Thanks!
HuiDoge said:
Ok. I will see what I can do. I briefly went over that option in your list.. it seems risky. I am not a person that wants to mess with wires and risk explosions. If I buy another battery, will that do the trick? That'd be safer. I'd rather pay that risk that other stuff. Could you provide me a link to a good battery? I know it sounds dumb but I don't want to get the wrong model.
Click to expand...
Click to collapse
Sorry if that was not clear, I haven't updated that for a while.
Low battery options There are 3 options the first is a warning and not recommended MacGyver Method, 2. is Factory Programming / Fastboot Cable, 3rd is a spare battery charger (with link), and 4th would be borrow a charged battery. A new battery may not be charged enough to flash.
---------- Post added at 03:06 PM ---------- Previous post was at 02:53 PM ----------
[VIDEOS] How to root, Nandroid, Flash, & Restore
sd_shadow said:
Sorry if that was not clear, I haven't updated that for a while.
Low battery options There are 3 options the first is a warning and not recommended MacGyver Method, 2. is Factory Programming / Fastboot Cable, 3rd is a spare battery charger (with link), and 4th would be borrow a charged battery. A new battery may not be charged enough to flash.
---------- Post added at 03:06 PM ---------- Previous post was at 02:53 PM ----------
[VIDEOS] How to root, Nandroid, Flash, & Restore
Click to expand...
Click to collapse
I see, I see. So from what I see here, I should buy the Black Hat thing and the charger and try those options to reset my phone.
I have see a YouTube vid where a guy from RootJunky shows you how to do this, so I will be using that as a guide, unless you recommend another way.
Once I have reset my phone, could you help me root and get ICS on my Droid? I still am intent on getting Android 4 on this phone, now more out of trying to solve the mess I've gotten myself into that actually enjoying the final result. Not that I don't want ICS, but I want to learn how to do this the right way. If there is a good YouTube video about how to get CM9 on the Droid 2 or something similar, could you direct me there? Or, do you just recommend the guide you have?
Thanks again.
Once I have reset my phone, could you help me root and get ICS on my Droid? I still am intent on getting Android 4 on this phone, now more out of trying to solve the mess I've gotten myself into that actually enjoying the final result. Not that I don't want ICS, but I want to learn how to do this the right way.
Thanks again.
Click to expand...
Click to collapse
Android 4.0 = Ice Cream Sandwich (ICS) = CM9
---------- Post added at 06:06 PM ---------- Previous post was at 05:39 PM ----------
HuiDoge said:
I see, I see. So from what I see here, I should buy the Black Hat thing and the charger and try those options to reset my phone.
Click to expand...
Click to collapse
Either or, shouldn't need both.
If there is a good YouTube video about how to get CM9 on the Droid 2 or something similar, could you direct me there? Or, do you just recommend the guide you have?
I have see a YouTube vid where a guy from RootJunky shows you how to do this, so I will be using that as a guide, unless you recommend another way.
Click to expand...
Click to collapse
[VIDEOS] How to root, Nandroid, Flash, & Restore is from same Guy.
---------- Post added at 06:13 PM ---------- Previous post was at 06:06 PM ----------
basic Rom install steps
root with framaroot
install a bootstrap app
use bootstrap app install CWM recovery
install Rom in cwm
see installing and using 2/x/3 bootstrap
in my list
sd_shadow's [Collection] of Links for:
Droid 2 (a955)
sd_shadow said:
Android 4.0 = Ice Cream Sandwich (ICS) = CM9
---------- Post added at 06:06 PM ---------- Previous post was at 05:39 PM ----------
Either or, shouldn't need both.
[VIDEOS] How to root, Nandroid, Flash, & Restore is from same Guy.
---------- Post added at 06:13 PM ---------- Previous post was at 06:06 PM ----------
basic Rom install steps
root with framaroot
install a bootstrap app
use bootstrap app install CWM recovery
install Rom in cwm
see installing and using 2/x/3 bootstrap
in my list
sd_shadow's [Collection] of Links for:
Droid 2 (a955)
Click to expand...
Click to collapse
Ok. I have successfully rooted my device and have done a nandroid backup.
I am obviously moving on to actually getting a rom on my phone. Before I start, I have a few questions.
- Is there anything I need to do right now? My current state includes a root and a nandroid backup. What other tweaks do I need to make as of right now>?
- I cannot find a good link to CM9 for Droid 2. Either the site is a virus website or my computer thinks it is. Can you give me a direct link here? In addition, could you provide me with a link to a Gapps link as well? I saw a few links in the guide and heard from RootJunky that Gapps should be installed with any ICS build, but I can never find a page where both are listed and are confirmed to be compatible. Last time, I had gotten both from different sites, and I think they were not compatible.
So, here is what I have in mind. Correct me or add to me if I miss something.
1) download the CM9 build from some site onto PC
2) download the Gapps from some site onto PC
3) attach phone to PC and copy both to a folder on the storage
4) boot into ClockworkMod Recovery and wipe all data
5) in Clockwork also wipe the cache
6) in Clockwork there is some option to "install from SD card". Select that
7) find the CM9 and select that
8) after selecting CM9, also select the Gapps
9) let it run installation process and reboot.
NOTE: the above is almost exactly what I did last time, except I didn't wipe cache and I didn't do a nandroid backup
From the above, do you think I will be successful?
HuiDoge said:
Ok. I have successfully rooted my device and have done a nandroid backup.
I am obviously moving on to actually getting a rom on my phone. Before I start, I have a few questions.
- Is there anything I need to do right now? My current state includes a root and a nandroid backup. What other tweaks do I need to make as of right now>?
- I cannot find a good link to CM9 for Droid 2. Either the site is a virus website or my computer thinks it is. Can you give me a direct link here? In addition, could you provide me with a link to a Gapps link as well? I saw a few links in the guide and heard from RootJunky that Gapps should be installed with any ICS build, but I can never find a page where both are listed and are confirmed to be compatible. Last time, I had gotten both from different sites, and I think they were not compatible.
So, here is what I have in mind. Correct me or add to me if I miss something.
1) download the CM9 build from some site onto PC
2) download the Gapps from some site onto PC
3) attach phone to PC and copy both to a folder on the storage
4) boot into ClockworkMod Recovery and wipe all data
5) in Clockwork also wipe the cache
6) in Clockwork there is some option to "install from SD card". Select that
7) find the CM9 and select that
8) after selecting CM9, also select the Gapps
9) let it run installation process and reboot.
NOTE: the above is almost exactly what I did last time, except I didn't wipe cache and I didn't do a nandroid backup
From the above, do you think I will be successful?
Click to expand...
Click to collapse
I will reupload CM9-D2-01032013.zip to a different site, the advertisements on DevHost are the problem.
If you still have your copy of CM9-D2-01032013.zip verify MD5 Sum: e0aa070f9032f6ff458c997275e66ffb
Links to GApps in my sd_shadow's List of GApps gapps-ics-20120429-signed.zip should be good just verify md5
---------- Post added at 10:29 AM ---------- Previous post was at 10:02 AM ----------
https://www.androidfilehost.com/?fid=95887005526789875
sd_shadow said:
I will reupload CM9-D2-01032013.zip to a different site, the advertisements on DevHost are the problem.
If you still have your copy of CM9-D2-01032013.zip verify MD5 Sum: e0aa070f9032f6ff458c997275e66ffb
Links to GApps in my sd_shadow's List of GApps gapps-ics-20120429-signed.zip should be good just verify md5
---------- Post added at 10:29 AM ---------- Previous post was at 10:02 AM ----------
https://www.androidfilehost.com/?fid=95887005526789875
Click to expand...
Click to collapse
Ok. Downloaded both. My thought process before was good, right?
HuiDoge said:
Ok. Downloaded both. My thought process before was good, right?
Click to expand...
Click to collapse
Just follow Install a rom in ClockworkMod Recovery (CWM)
sd_shadow said:
Just follow Install a rom in ClockworkMod Recovery (CWM)
Click to expand...
Click to collapse
I DID IT! It works now!
Thank you so much! Is there some "like" button I can click to thank you? I was really happy when someone came to my rescue because I thought no one would have any info on an old phone like this one!
Thanks a ton! I hope this thread might help others as well, but if it needs to be deleted that will be okay, too.
All credit goes to captaingowa and his post (http://forum.xda-developers.com/grand-prime/general/att-samsung-galaxy-prime-sm-g530a-links-t3283066) for the AT&T version.
I'm just providing stock kernel for 5.1.1 SM-G530AZ
1. Root SM-G530AZ 5.1.1 with kingroot 4.6.2 or higer (kingroot.net)
2. DON'T Reboot
3. Download and install Flashify on play store or APK
4. Flash stock kernel with flashify (http://www.mediafire.com/download/2fk19cadccq0xd7/boot.img)
5. Reboot.
6. Replace kinguser with supersu (optional) (http://www.mediafire.com/download/x1efi7ev6nf3mvd/Replace_Kinguser_with_SuperSU-v2.0.zip)
7. Enjoy
wally86 said:
All credit goes to captaingowa and his post (http://forum.xda-developers.com/grand-prime/general/att-samsung-galaxy-prime-sm-g530a-links-t3283066) for the AT&T version.
I'm just providing stock kernel for 5.1.1 SM-G530AZ
1. Root SM-G530AZ 5.1.1 with kingroot 4.6.2 or higer (kingroot.net)
2. DON'T Reboot
3. Download and install Flashify on play store or APK
4. Flash stock kernel with flashify (http://www.mediafire.com/download/2fk19cadccq0xd7/boot.img)
5. Reboot.
6. Replace kinguser with supersu (optional) (http://www.mediafire.com/download/x1efi7ev6nf3mvd/Replace_Kinguser_with_SuperSU-v2.0.zip)
7. Enjoy
Click to expand...
Click to collapse
Awesome, thank you so much. Going to try it right now, but I'm betting it will work. Thank you again for putting this all together.
Nice, think I flashed the wrong boot.img from that thread, there are two different img's, one as tar and the other as img. We actually need the img in the tar, which you have posted above. Thanks for posting this up.
guys thank you very much! i will try this and report results to the forum!
HELP!!
kenboyles72 said:
Nice, think I flashed the wrong boot.img from that thread, there are two different img's, one as tar and the other as img. We actually need the img in the tar, which you have posted above. Thanks for posting this up.
Click to expand...
Click to collapse
I tried the same procedure and my wifi will still not work!!!
thecomputerdude87 said:
I tried the same procedure and my wifi will still not work!!!
Click to expand...
Click to collapse
There are a couple things you can do here.
1. Try re-downloading the boot.img and reflashing with flashify
2. Try flashing the boot.img with Odin3
3. Restoring your phone with Kies http://forum.xda-developers.com/showpost.php?p=61977268&postcount=14
I rooted my phone and had to restore with kies three times before i got my wifi working. This is only if I switched to SuperSU, if you stay with kingroot, you wont have the wifi issue.
Help help help!
I did this and now my wifi won't turn on!! AT ALL
so the root metod its safe??? now there is another metod done from between Android using terminal emulator to switch from kingroot to chains fire super su! you have to be fully rooted to be able to work on terminal emulator.
but the root metod for sm g530az its safe?
flashing the stock kernel, do you click boot image or recovery image?
---------- Post added at 06:57 AM ---------- Previous post was at 06:18 AM ----------
OK, I got the wifi to turn back on by using the link above again.
I still cant get the wifi tether app to work, tho.
any suggestions?
well..happy to report that root on criket grand prime sm-g530az its a big...SUCCESS!!!
Im rooted on lollipop 5.1.1.
i do have cwm recovery but i need to flash it and see how it goes.for those with the Wi-Fi problem flash that boot image again.i have two one didn't work so i flash that second and Wi-Fi was working again.
Samsung bootlogo reports as "custom" so guaranty its gone
but I don't care abt that,im rooted thnx guys for sharing all that informacion!
I got the root to work with kingroot, but didn't do the 'optional' SU part, but now I want to.
Can anyone tell me what the step is with that zip file? do I download it directly to the phone? use Flashify? if I'm using flashify, do I flash it as a "boot image", a "recovery image" or a "zip file" ?
LOL talk to me like I'm five, please! I'm a noob at this. I'm smart at some things but this is a little overwhelming. LOL I'm a critical care nurse. I can fix a PERSON, but phones are a little more complicated :laugh:
---------- Post added at 03:39 AM ---------- Previous post was at 03:10 AM ----------
Oh OOH OOOHH!!!
Did that final step and the wifi tethering app WORKS!!!
WHOO HOOOOO!!!!
Thanks, wally, you are AWESOME!!
Root wifi teather
What wifi teather apk do yuo use?
hello try to this post :
http://forum.xda-developers.com/gra...t/cm-13-android-6-0-1-grand-prime-sm-t3291892
this post help you to install custom rom on grand prime sm-g530h and other . . .
adj5064 said:
well..happy to report that root on criket grand prime sm-g530az its a big...SUCCESS!!!
Im rooted on lollipop 5.1.1.
i do have cwm recovery but i need to flash it and see how it goes.for those with the Wi-Fi problem flash that boot image again.i have two one didn't work so i flash that second and Wi-Fi was working again.
Samsung bootlogo reports as "custom" so guaranty its gone
but I don't care abt that,im rooted thnx guys for sharing all that informacion!
Click to expand...
Click to collapse
Wait you have cwm compiled for our sm-g530az? That would be useful
Okay thanks a ton for the info, finally got my wifi back after flashing the correct boot.img, not sure where it was on the original forum never saw it but luckily others that had same issue posted it.
---------- Post added at 09:28 PM ---------- Previous post was at 09:26 PM ----------
Going to try to blow the dust off my builduntu box and see if I cant get us a recovery going for the cricket version, I usually like twrp but now that cwm has touch as well could go that route....is their a custom recovery built for the other variants at all yet....if so then forking those repos would be a good starting point, should only take minor edits to get it working proper for us.
toxinburn said:
Okay thanks a ton for the info, finally got my wifi back after flashing the correct boot.img, not sure where it was on the original forum never saw it but luckily others that had same issue posted it.
---------- Post added at 09:28 PM ---------- Previous post was at 09:26 PM ----------
Going to try to blow the dust off my builduntu box and see if I cant get us a recovery going for the cricket version, I usually like twrp but now that cwm has touch as well could go that route....is their a custom recovery built for the other variants at all yet....if so then forking those repos would be a good starting point, should only take minor edits to get it working proper for us.
Click to expand...
Click to collapse
I already built twrp for this phone, but as you found out, the damn security checks prevent the use of it. This is my device tree, can't remember if I pushed my last commits and I dont have what I had, due to a hdd failure.
https://github.com/LoneStar-/android_device_samsung_grandprimeltetu
kenboyles72 said:
I already built twrp for this phone, but as you found out, the damn security checks prevent the use of it. This is my device tree, can't remember if I pushed my last commits and I dont have what I had, due to a hdd failure.
https://github.com/LoneStar-/android_device_samsung_grandprimeltetu
Click to expand...
Click to collapse
So can you get a custom recovery working for this device? I have tried many ways but they all ended with my flashing stock img. twrp or cwm would be fine by me. Or another alternative is to find out how to disable the security check. Anyway please find a way to get custom recovery for 5.1.1 SM-G530AZ. Thanks
Illyakulinych said:
So can you get a custom recovery working for this device? I have tried many ways but they all ended with my flashing stock img. twrp or cwm would be fine by me. Or another alternative is to find out how to disable the security check. Anyway please find a way to get custom recovery for 5.1.1 SM-G530AZ. Thanks
Click to expand...
Click to collapse
Okay I think we should put our heads together to try and kick this lockdown to the curb, things I have tried so far...I found that on some other variants they have the option within their settings/developer settings menu to enable oem unlock which is what we are needing to be able to flash custom recovery, I have replaced my settings.jar and settings.odex with theirs with no luck the option is still not showing up for me, but I think it may be the right direction into getting that to show up, the question i am now posing is this. Are the checks in place simply reading carrier info to allow/disallow this option? If so would we possibly be able to change the build.prop or other settings with our newly found root access to trick the device into giving this option? If that is the case then we need to get as much info from the stock devices that have that option as possible and maybe try swapping certain files out with theirs to get the option back and/or editing certain files on our own device to get it to show up. It only takes one g530AZ with unlocked bootloader to share the boot.img i would think. I had thought about flashing another boot.img or aboot.img from another variant but I am pretty concerned about brickage although I think it could be recoverable as long as one can get back into download mode. Has anyone zeroed out the download partition to see if a fastboot is hidden behind it?
toxinburn said:
Okay I think we should put our heads together to try and kick this lockdown to the curb, things I have tried so far...I found that on some other variants they have the option within their settings/developer settings menu to enable oem unlock which is what we are needing to be able to flash custom recovery, I have replaced my settings.jar and settings.odex with theirs with no luck the option is still not showing up for me, but I think it may be the right direction into getting that to show up, the question i am now posing is this. Are the checks in place simply reading carrier info to allow/disallow this option? If so would we possibly be able to change the build.prop or other settings with our newly found root access to trick the device into giving this option? If that is the case then we need to get as much info from the stock devices that have that option as possible and maybe try swapping certain files out with theirs to get the option back and/or editing certain files on our own device to get it to show up. It only takes one g530AZ with unlocked bootloader to share the boot.img i would think. I had thought about flashing another boot.img or aboot.img from another variant but I am pretty concerned about brickage although I think it could be recoverable as long as one can get back into download mode. Has anyone zeroed out the download partition to see if a fastboot is hidden behind it?
Click to expand...
Click to collapse
Any progress?
Illyakulinych said:
Any progress?
Click to expand...
Click to collapse
Only thing I have done Is zeroed out the sec partition which caused non problem however it did no good either....also playing around with the databases and able to change some options just not the one in wanting yet...I work a ton son my freetime is limited but if anyone that has a different variant that could share their system apps primarily their settings all and databases and xml associated with it is really like to look through them.
Sent from my SAMSUNG-SM-G530AZ using Tapatalk
If anybody can put up a step-by-step guide, or a video that shows how to properly install it all, I'm sure myself, and much of the community would appreciate it.
Recently, my laptop that I had ADB, and every tool imaginable for Androids, and specifically the Galaxy Series, took a huge dump on me and I lost it all. I installed it so long ago, that embarrassingly I've forgotten how I did it all. If someone could post how they rooted their GS7 (non-edge variant), I would be very appreciative. And I'm sure much of the community would be too. I'm embarrassed to even have to ask as someone who used to formerly develop mods on phones. But it is what it is. It's been so long since I've set it all up, and I've had to do so much since that time that I've simply forgotten how I did it/how to do it. Any help would be GREATLY appreciated. Thank you ahead of time...
I've tried following the instructions in the sticky above. I ran the 930X ROOT.TAR in the special version of ODIN. And every ran OK. It said "Success" and then rebooted. All seemed well, then it froze on the AT&T Boot Logo. What can I do from here? I know from history that this is one of the points that people panic and claimed "brick" (though I've never seen a real brick from rooting). Any help would be greatly appreciated
There's a great guide in the Verizon forum. Root was universal based on FW. Just make sure you flash the correct 930 or 935 with the modded odin. I recommend you follow the steps to "unroot" for the sake of doing an extremely in depth factory reset. Also make sure you get chain fires latest supersu built for the s7qc.
Sent from my SAMSUNG-SM-G930A using Tapatalk
twizt3d said:
There's a great guide in the Verizon forum. Root was universal based on FW. Just make sure you flash the correct 930 or 935 with the modded odin. I recommend you follow the steps to "unroot" for the sake of doing an extremely in depth factory reset. Also make sure you get chain fires latest supersu built for the s7qc.
Sent from my SAMSUNG-SM-G930A using Tapatalk
Click to expand...
Click to collapse
thank you for that. I'll check it out. Hopefully it'll get me past this bootscreen issue
yup. Great instructions. All set rooted now. Now time to play with xposed and V4A and the like. Yay
OK. Followed the instructions on the Verizon page and used the PrinceComsy version. Stuck at the AT&T logo. How did you go past this step? Should I have used the standard version? thanks
thanirs said:
OK. Followed the instructions on the Verizon page and used the PrinceComsy version. Stuck at the AT&T logo. How did you go past this step? Should I have used the standard version? thanks
Click to expand...
Click to collapse
(keep in mind this is only my personal experience...)
but the PrinceComsy version of ODIN was the only one to work for me. How far exactly have you gotten in the process before you got stuck at the logo? You do have ADB installed correctly installed on your PC and turned on on your phone right? and cd-ed the specific "super" folder for the SU adb install, right? FYI: It's not a simple root process, like 1-click roots on previous devices. This is more similar to the in-depth root methods like on the N1 and D1 before super nice devs went out of their way to make it simple. So if you're not familiar with ADB shell and the likes, it'll be difficult for you. But, no matter how high and mighty or condescending people act, we've all had to start somewhere. I'll help you get through the process as much as I can
Thanks for your reply. BTW I am fairly experienced in this stuff. This is what I did to get it to work. ADB and drivers all work fine.
Flashed the boot image using the PrinceComsy version. Got stuck at AT&T logo
Attempted to flash with the other version of Odin. When I open Odin, a window would pop-up with some ini issue and Odin would close immediately.
So I moved the ini file from PrinceComsy version to the other version. At this point, Odin would open and detect the phone at the correct COM port
Tried flashing it with this Odin but I got a SHA256 error
SO..
I went back to stock (which deletes all data, no big deal - everything was backed up)
Boot was successful
Re-flashed with the boot image and viola!
52brandon said:
(keep in mind this is only my personal experience...)
but the PrinceComsy version of ODIN was the only one to work for me. How far exactly have you gotten in the process before you got stuck at the logo? You do have ADB installed correctly installed on your PC and turned on on your phone right? and cd-ed the specific "super" folder for the SU adb install, right? FYI: It's not a simple root process, like 1-click roots on previous devices. This is more similar to the in-depth root methods like on the N1 and D1 before super nice devs went out of their way to make it simple. So if you're not familiar with ADB shell and the likes, it'll be difficult for you. But, no matter how high and mighty or condescending people act, we've all had to start somewhere. I'll help you get through the process as much as I can
Click to expand...
Click to collapse
---------- Post added at 08:47 PM ---------- Previous post was at 08:21 PM ----------
OK. Proceeding with the recommended steps in the install guide, I ran into this one nagging pop-up:
Security notice: Unauthorized actions have been detected. Restart your phone to undo any unauthorized changes.
Its a rather annoying notice that keeps popping up. What is the fix for this? Quick 'google' suggested some people uninstalling Knox altogether and it seemed fairly drastic. Suggestions?
thanirs said:
Thanks for your reply. BTW I am fairly experienced in this stuff. This is what I did to get it to work. ADB and drivers all work fine.
Flashed the boot image using the PrinceComsy version. Got stuck at AT&T logo
Attempted to flash with the other version of Odin. When I open Odin, a window would pop-up with some ini issue and Odin would close immediately.
So I moved the ini file from PrinceComsy version to the other version. At this point, Odin would open and detect the phone at the correct COM port
Tried flashing it with this Odin but I got a SHA256 error
SO..
I went back to stock (which deletes all data, no big deal - everything was backed up)
Boot was successful
Re-flashed with the boot image and viola!
Click to expand...
Click to collapse
---------- Post added at 09:08 PM ---------- Previous post was at 08:47 PM ----------
OK never mind please and sorry. Found the answer in the Fix/debloat script.
thanirs said:
Thanks for your reply. BTW I am fairly experienced in this stuff. This is what I did to get it to work. ADB and drivers all work fine.
Flashed the boot image using the PrinceComsy version. Got stuck at AT&T logo
Attempted to flash with the other version of Odin. When I open Odin, a window would pop-up with some ini issue and Odin would close immediately.
So I moved the ini file from PrinceComsy version to the other version. At this point, Odin would open and detect the phone at the correct COM port
Tried flashing it with this Odin but I got a SHA256 error
SO..
I went back to stock (which deletes all data, no big deal - everything was backed up)
Boot was successful
Re-flashed with the boot image and viola!
---------- Post added at 08:47 PM ---------- Previous post was at 08:21 PM ----------
OK. Proceeding with the recommended steps in the install guide, I ran into this one nagging pop-up:
Security notice: Unauthorized actions have been detected. Restart your phone to undo any unauthorized changes.
Its a rather annoying notice that keeps popping up. What is the fix for this? Quick 'google' suggested some people uninstalling Knox altogether and it seemed fairly drastic. Suggestions?
---------- Post added at 09:08 PM ---------- Previous post was at 08:47 PM ----------
OK never mind please and sorry. Found the answer in the Fix/debloat script.
Click to expand...
Click to collapse
so you got it all figured out and running great now right? No other issues right?
Just to add to this, I have verified that this still works using PG1.
http://forum.xda-developers.com/showpost.php?p=67970468&postcount=33
twizt3d said:
Just to add to this, I have verified that this still works using PG1.
http://forum.xda-developers.com/showpost.php?p=67970468&postcount=33
Click to expand...
Click to collapse
Can you please try restoring to af2?
Thanks for the ping. I think so. One thing I ran into which I don't know if its related to rooting. When I am in a phone conversation, audio on the other end goes in and out after a few minutes into the call. This happens with bluetooth or not. Still figuring out this issue.
52brandon said:
so you got it all figured out and running great now right? No other issues right?
Click to expand...
Click to collapse
Seeing battery drain. So went back to stock /unroot for now.
I was not trying to root my phone but reflash to an earlier version. I tried the Prince version of Odin and it did not work. The version that ended up working is in this thread
http://forum.xda-developers.com/att-galaxy-s7/how-to/firmware-g930a-edge-variant-afp-stock-t3415344
http://click.xda-developers.com/api...ww.mediafire.com/download/2t...din_3.12.3.rar
Hello,
I can't find nothing for sm-j320zn version, I tried to install TWRP and I did it, but when I try to install the Supersu the mobile goes to a bootloop...
Help! Thank you so much!!
Nobody?
mathius89 said:
Nobody?
Click to expand...
Click to collapse
Also trying to find a root for mine. The only thing I haven't tried is cf auto root
mathius89 said:
Nobody?
Click to expand...
Click to collapse
I have an j320w8 samsung please help
Build
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
telephony.lteOnCdmaDevice=0
persist.eons.enabled=true
rild.libpath=/system/lib/libsec-ril.so
persist.security.ams.enforcing=3
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
ro.adb.secure=1
persist.sys.usb.config=mtp
ro.zygote=zygote32
dalvik.vm.image-dex2oat-Xms=64m
dalvik.vm.image-dex2oat-Xmx=64m
dalvik.vm.dex2oat-Xms=64m
dalvik.vm.dex2oat-Xmx=512m
ro.dalvik.vm.native.bridge=0
debug.atrace.tags.enableflags=0
#
# BOOTIMAGE_BUILD_PROPERTIES
#
ro.bootimage.build.date=Mon Jan 2 15:19:13 KST 2017
ro.bootimage.build.date.utc=1483337953
ro.bootimage.build.fingerprint=samsung/j3xltebmc/j3xltebmc:6.0.1/MMB29K/J320W8VLU2AQA1:user/test-keys
Sent from my Samsung SM-J320W8 using XDA Labs
j320zn
please help how to rootj320zn me try all root tools :
mathius89 said:
Hello,
I can't find nothing for sm-j320zn version, I tried to install TWRP and I did it, but when I try to install the Supersu the mobile goes to a bootloop...
Help! Thank you so much!!
Click to expand...
Click to collapse
You need V2.79 sr3
Samsung Galaxy j320zn
ashyx said:
You need V2.79 sr3
Click to expand...
Click to collapse
Can you explain what your answer means is there a way to root the phone thats successful?
jdkeys said:
Can you explain what your answer means is there a way to root the phone thats successful?
Click to expand...
Click to collapse
Ashyx means you need SuperSU version 2.79 sr3.
---------- Post added at 10:50 AM ---------- Previous post was at 10:49 AM ----------
Wulfie217 said:
Ashyx means you need SuperSU version 2.79 sr3.
Click to expand...
Click to collapse
If I remember rightly that can be found here on XDA somewhere.
Working root?
What did any users here use to root the J3 SM-J320ZN? I can't get it to root and I'm spitting chips.
mathius89 said:
Hello,
I can't find nothing for sm-j320zn version, I tried to install TWRP and I did it, but when I try to install the Supersu the mobile goes to a bootloop...
Help! Thank you so much!!
Click to expand...
Click to collapse
mathius, which TWRP did you successfully install for SM-J320ZN? I'm so confused. I've looked at sites with tables for different models, and this model isn't available. I've sort of looked here, and done a Google search and it points me to 3.02 for SM-J320H. Is this the one you used?
I've got the SuperSU v.2.79 sr3 that was recommended ready. Now I don't know what TWRP to try lol.
I'm so upset. This is my first new phone in 6 years (I've been stuck on Gingerbread with a bizarre/rare Australian model phone that could not get custom ROMS). I'm disabled, it took me so long to get this phone and I find out I can't root it? Useless to me unless I can get root.
Also anyone, would the fact the phone is locked make things more difficult? Obviously people are having trouble rooting this model regardless, but will this interfere further, esp. with things like TWRP?
Winston Churchill said:
mathius, which TWRP did you successfully install for SM-J320ZN? I'm so confused. I've looked at sites with tables for different models, and this model isn't available. I've sort of looked here, and done a Google search and it points me to 3.02 for SM-J320H. Is this the one you used?
I've got the SuperSU v.2.79 sr3 that was recommended ready. Now I don't know what TWRP to try lol.
I'm so upset. This is my first new phone in 6 years (I've been stuck on Gingerbread with a bizarre/rare Australian model phone that could not get custom ROMS). I'm disabled, it took me so long to get this phone and I find out I can't root it? Useless to me unless I can get root.
Also anyone, would the fact the phone is locked make things more difficult? Obviously people are having trouble rooting this model regardless, but will this interfere further, esp. with things like TWRP?
Click to expand...
Click to collapse
J320fn has the same specs so there's a good chance it will work for j320zn
ashyx said:
J320fn has the same specs so there's a good chance it will work for j320zn
Click to expand...
Click to collapse
Thanks for the response.
I've tried flashing TWRP for the J320FN model from a tutorial I found here on xda. I've tried a couple of times. Odin says it's flashed OK but it hasn't worked in reality.
Sigh. A bit devastated.
Winston Churchill said:
Thanks for the response.
I've tried flashing TWRP for the J320FN model from a tutorial I found here on xda. I've tried a couple of times. Odin says it's flashed OK but it hasn't worked in reality.
Sigh. A bit devastated.
Click to expand...
Click to collapse
Very minimal on details.
'Hasn't worked' neither helps you or anyone else.
Explain the details of 'hasn't worked' if you require assistance.
ashyx said:
Very minimal on details.
'Hasn't worked' neither helps you or anyone else.
Explain the details of 'hasn't worked' if you require assistance.
Click to expand...
Click to collapse
Sorry. What I meant was nothing appears to be different at all. When I try to flash in Odin, it hits "Reset" section quickly, my phone reboots itself. I wait awhile and eventually Odin gives me the (1) success / (0) fail type message and I get the green "Pass" to indicate that it was successfully flashed. But, there is no difference to my system at all, and when I boot to recovery, it's still stock recovery if that makes sense.
Something to note: my phone is currently locked to my provider (so I can only use a Telstra SIM). Would this impact being able to flash TWRP? Otherwise, it's just not the right one to use.....ZN isn't compatible with FN maybe.
It's been many years since I've flashed or rooted (ordinarily I root tablets with KingoRoot). I remember back in the bad old days that my old phone had the processor or drivers or chip or something that meant I could not run custom ROMS because it was Qualcomm and all the other phones were the other type that released the drivers publicly. Started with B I think (this other chipset or whatever. Sorry I'm not a full on geek to know heh). Anyway, I was wondering if I'm in the same boat again with my Australian phone because it's Qualcomm (or Quadcomm..... something like that)....... hence all the hacks and mods that you guys make won't work.
Does/can installing SuperSU through stock recovery grant root? I tried doing that anyway - executing v2.79 sr3 that you recommended as well as v2.74, which was the package I found in the tutorial for installing TWRP and rooting for J320FN. I got failed messages.
Winston Churchill said:
Sorry. What I meant was nothing appears to be different at all. When I try to flash in Odin, it hits "Reset" section quickly, my phone reboots itself. I wait awhile and eventually Odin gives me the (1) success / (0) fail type message and I get the green "Pass" to indicate that it was successfully flashed. But, there is no difference to my system at all, and when I boot to recovery, it's still stock recovery if that makes sense.
Something to note: my phone is currently locked to my provider (so I can only use a Telstra SIM). Would this impact being able to flash TWRP? Otherwise, it's just not the right one to use.....ZN isn't compatible with FN maybe.
It's been many years since I've flashed or rooted (ordinarily I root tablets with KingoRoot). I remember back in the bad old days that my old phone had the processor or drivers or chip or something that meant I could not run custom ROMS because it was Qualcomm and all the other phones were the other type that released the drivers publicly. Started with B I think (this other chipset or whatever. Sorry I'm not a full on geek to know heh). Anyway, I was wondering if I'm in the same boat again with my Australian phone because it's Qualcomm (or Quadcomm..... something like that)....... hence all the hacks and mods that you guys make won't work.
Does/can installing SuperSU through stock recovery grant root? I tried doing that anyway - executing v2.79 sr3 that you recommended as well as v2.74, which was the package I found in the tutorial for installing TWRP and rooting for J320FN. I got failed messages.
Click to expand...
Click to collapse
If I'm reading that correctly it seems like in Odin you have auto reboot turned on. You need to change that under options, the only thing on in Odin should be F.reset time. Then use (iirc) both volume buttons, gone button and power to restart the phone when it's finished.
For some reason having auto reboot off is important.
Winston Churchill said:
Sorry. What I meant was nothing appears to be different at all. When I try to flash in Odin, it hits "Reset" section quickly, my phone reboots itself. I wait awhile and eventually Odin gives me the (1) success / (0) fail type message and I get the green "Pass" to indicate that it was successfully flashed. But, there is no difference to my system at all, and when I boot to recovery, it's still stock recovery if that makes sense.
Something to note: my phone is currently locked to my provider (so I can only use a Telstra SIM). Would this impact being able to flash TWRP? Otherwise, it's just not the right one to use.....ZN isn't compatible with FN maybe.
It's been many years since I've flashed or rooted (ordinarily I root tablets with KingoRoot). I remember back in the bad old days that my old phone had the processor or drivers or chip or something that meant I could not run custom ROMS because it was Qualcomm and all the other phones were the other type that released the drivers publicly. Started with B I think (this other chipset or whatever. Sorry I'm not a full on geek to know heh). Anyway, I was wondering if I'm in the same boat again with my Australian phone because it's Qualcomm (or Quadcomm..... something like that)....... hence all the hacks and mods that you guys make won't work.
Does/can installing SuperSU through stock recovery grant root? I tried doing that anyway - executing v2.79 sr3 that you recommended as well as v2.74, which was the package I found in the tutorial for installing TWRP and rooting for J320FN. I got failed messages.
Click to expand...
Click to collapse
As said above you need to disable auto reboot. It's important to manually boot into recovery immediately after flashing twrp or it will be replaced by stock recovery at first boot.
ashyx said:
As said above you need to disable auto reboot. It's important to manually boot into recovery immediately after flashing twrp or it will be replaced by stock recovery at first boot.
Click to expand...
Click to collapse
Thanks guys.
The problem I'm having is - is there a proper way to boot into recovery from download mode once the flash has finished? I've tried button combos and looked about a bit.
The only thing I've got to work is to exit odin, then take the battery out and boot into recovery using vol up, home and power once I put the battery back in.
When I do that, the Samsung splash screen comes up and in the top left corner it's still saying it's in Odin mode (then it gives my model number and some other details - I can redo if you want to know all the listed details). It appears to just stay stuck at this spalsh screen. I waited about 5 minutes (trying two different times) and it just stays on that splash screen and wont boot to phone or recovery.
Sorry, I'm really hopeless Thanks for your patience.
P.S. So once I take battery out again and restart the phone works fine again because it's obviously reverted to stock recovery again like you said it would if I didn't manually boot to recovery. So it's OK, I've not bricked my phone or anything. I'm just wondering if there's a method I need to do to get it to work other than battery out.
---------- Post added at 05:30 PM ---------- Previous post was at 04:40 PM ----------
I just want to say that I got root for the SM-J320ZN using CF-Auto-Root.
Follow this link to download the package CF-Auto-Root-j3lteusc-j3lteusc-smj320r4.zip:
https://download.chainfire.eu/986/C...3lteusc-j3lteusc-smj320r4.zip?retrieve_file=1
The package came bundled with a version of Odin and some other files, so I extracted them all to a directory, ran Odin, and flashed the .md5 through the AP button. It takes a little while and as it says while it is loading, your phone might reboot several times in the process before it finishes so DON'T interfere with it.
YAY.
Any help on the TWRP issue I'm still having would be greatly appreciated still
420blazedman said:
Also trying to find a root for mine. The only thing I haven't tried is cf auto root
Click to expand...
Click to collapse
root j320zn cf auto root done with odin
---------- Post added at 10:35 AM ---------- Previous post was at 10:19 AM ----------
j320zn root done with cfauto root using odin:
I've finally gotten a TWRP version to work for the J320ZN with no issues. I've had a week of tinkering so I thought I'd go back to my phone and try on that again too after previously giving up.
To repeat what I've already written, the suggested TWRP version for J320FN DOES NOT seem to work. When manually booting to recovery after flashing, you get stuck on the default Samsung boot screen, but with Download Mode text still stuck in the corner (to finally answer your question ashyx)
I got TWRP J3lte to work. To download: https://dl.twrp.me/j3lte/
I've had a BILLION problems doing this... because like the OP, I couldn't get root by using SuperSU.zip through TWRP.... it would cause a bootloop. I tried the suggested version of SuperSU posted by ashyx earlier in the thread... plus the latest with no luck.
My "solution" (LOL) was to flash CF-Auto-Root... without realizing it wiped to stock recovery! So here's me all happy thinking I've got TWRP and root...and gotten rid of the bootloop until I set up my phone and went to recovery to make my first full backup... and saw that not only was I getting stock (DUH lolol), but a dm-verity error.
This is something I know nothing about, other than there is a patch for it. So this time, I decided to try the dm-verity patch and REAL SUCCESS! Root, TWRP recovery (that's still there after multiple checks).
So... if you've tried TWRP j3lte and the latest SuperSU.zip and instead of working, you got bootloop you could try the dm-verity patch in your procedure (also to get rid of the bootloops I just flashed CF-Auto-Root again... but then you'll have to start again with TWRP etc).
My successful procedure was:
1) Install TWRP j3lte as linked above (lastest version twrp-3.2.1-0-j3lte.img)
2) Install SuperSU v.2.82 SR5 through TWRP....https://download.chainfire.eu/1220/SuperSU/SR5-SuperSU-v2.82-SR5-20171001224502.zip
3) THEN BEFORE REBOOT, install Dm-verity and Forced Encryption Disabler patch (no-verity-opt-encrypt-6.0.zip) from https://androidfilebox.com/miscellaneous/dm-verity-and-forced-encryption-disabler/ using the same "Install" button/method in TWRP.
Then you can reboot and THIS TIME it worked... I've rebooted many times, recovery still there, got root.... Link2SD working fine and I've made several backups to test.
A comedy of errors.....but I FINALLY fixed it just through tinkering. Hope this helps.
Though this thread is probably dead, I did have someone PM me a few weeks ago seeing if I'd found a solution (which is why I've been tinkering). So.....
In future I'd appreciate anyone who follows this updating me about what they had to do - did you get it to work with just TWRP j3lte and the newest SuperSU.zip? Or did you need the patch for Dm-verity/encrypt? It will help me learn what's really going on and why I have to do the things I do. I'm still a novice to things beyond simple rooting.
FOR XPOSED: please note if you're on stock ROM for this device, the Official Xposed Framework WILL NOT WORK. You will land in bootloop. Touchwiz is not supported. You need to install an Unofficial version by wanam. Our chipset is arm so make sure you download the correct version for 5.1.1 arm chipset (not arm64 or x86):
https://www.tricksfolks.com/install-xposed-framework-samsung-lollipop-marshmallow/
Make sure you download the uninstaller.zip for 5.1.1 and have it on your external SD card as well just in case you get into bootloop... then you can go to recovery and just uninstall the framework. This appears to be a custom uninstaller, so use that and NOT the official uninstaller zip for Xposed. It's right at the end of the tutorial (DL link). I had no issues however. Wanam's framework installed fine.
ALSO, the latest (at time of writing) Xposed Installer (apk) v.3.2 doesn't like the unofficial framework - it won't detect it properly plus there are some other annoyances, so I rolled back to v.3.1.5. Older versions shouldn't be too hard to find, but there is a link to an older apk version in the tutorial I just linked with the wanam files.
Finally, If anyone has recommendations for Custom ROMS that work on this model in future, also please let me know here. I'm a bit wary of trying after the trouble I've had with Xposed.
Hey folks. I am seriously stumped and I can't figure this out.
I want to install Android 10 on my 6P. I figured I would have to root it first. I installed TWRP 3.3.1.0-FBE-10-angler.
I successfully did OEM Unlocking.
I Pushed Beta-SuperSU-v2.67-20160121175247 and it seemed to install fine.
I reboot and its not there. It should be in the apps, but its not. What am I missing? Should I do Magisk? This is new for me and once I get it, I won't have to ask again.
I also have the PixelExperience_angler-10.0-20200101-0925-OFFICIAL. I have not installed this yet, but this is the image I want, I believe.
Any advice is appreciated.
Thank you
xa3phod said:
Hey folks. I am seriously stumped and I can't figure this out.
I want to install Android 10 on my 6P. I figured I would have to root it first. I installed TWRP 3.3.1.0-FBE-10-angler.
I successfully did OEM Unlocking.
I Pushed Beta-SuperSU-v2.67-20160121175247 and it seemed to install fine.
I reboot and its not there. It should be in the apps, but its not. What am I missing? Should I do Magisk? This is new for me and once I get it, I won't have to ask again.
I also have the PixelExperience_angler-10.0-20200101-0925-OFFICIAL. I have not installed this yet, but this is the image I want, I believe.
Any advice is appreciated.
Thank you
Click to expand...
Click to collapse
Hey, Did you follow the instructions mentioned in Pixel Experience thread one by one as they are?
Ata Ur Rehman said:
Hey, Did you follow the instructions mentioned in Pixel Experience thread one by one as they are?
Click to expand...
Click to collapse
I was still stuck on the earlier problems. Before I went in and completely destroyed this phone, I wanted to make sure I was not missing something fundemental.
Also, for some reason the phone always pops out of data transfer mode. Do you think its my USB C cable that's losing the connection?
xa3phod said:
I was still stuck on the earlier problems. Before I went in and completely destroyed this phone, I wanted to make sure I was not missing something fundemental.
Also, for some reason the phone always pops out of data transfer mode. Do you think its my USB C cable that's losing the connection?
Click to expand...
Click to collapse
Probably It is losing connection to PC try another cable and reinstall and drivers on your PC.
---------- Post added at 03:53 PM ---------- Previous post was at 03:51 PM ----------
You can follow this video for detailed installation ( keep in mind if you aren't a BLOD user so you just skip flashing 4 core files )
Another issue: I installed TRWP and I was able to get into TRWP just fine. But, if I reboot and go into recovery I get the robot on his back with the triangle over it. I have reinstalled TWRP 3 times, but this keeps happening. Before I install a new ROM, I think I should know why this is happening and how to fix it.
Thanks again!
xa3phod said:
Another issue: I installed TRWP and I was able to get into TRWP just fine. But, if I reboot and go into recovery I get the robot on his back with the triangle over it. I have reinstalled TWRP 3 times, but this keeps happening. Before I install a new ROM, I think I should know why this is happening and how to fix it.
Thanks again!
Click to expand...
Click to collapse
Did you Turn OEM unlocking on?
Did you have flashing and downlaod mode unlocked?