I tried to post a reply to [HOW-TO]Fix your phone in the developer's section, but since I'm a new user, the system wouldn't let me. However, this post links to a page (imnuts.org/odin-packages/) that has taken down it's most valuable resources, the files needed for a factory reset. So although this might be the correct way to proceed, the missing resources makes it less valuable at this point in time.
victimoflg said:
I tried to post a reply to [HOW-TO]Fix your phone in the developer's section, but since I'm a new user, the system wouldn't let me. However, this post links to a page (imnuts.org/odin-packages/) that has taken down it's most valuable resources, the files needed for a factory reset. So although this might be the correct way to proceed, the missing resources makes it less valuable at this point in time.
Click to expand...
Click to collapse
try to PM some user who post in that section regularly.
he might help you
Sent from my SM-N900 using Tapatalk
Related
I'm curious if someone could put together a one-click root for Mac users. I've been in the rooting game for a while now (had a Droid 2 before) so I know what I'm doing. I just want a one-click in order to save time and convenience.
I'm sure there are other Mac users out there also interested in this. If something for Mac has already been posted then I apologize, please direct me to the appropriate thread.
I could possibly give it a shot. I have to stop this kernel panic on my pc before I boot mac, but it shouldn't be that hard. I'm already rooted, so I'll need some testers, but I'll try a similar method as the one for windows and try to make it mac/linux compatible.
That'd be great! Unfortunately I have a feeling this thread might be deleted since apparently only Developers are allowed to create threads in this section (even if others' posts are on topic).
Keep in touch with me via PM, I'd love to know of your progress.
Please lock this thread mods. I'll start a thread when I finish an alpha for mac/linux. Thank you, and please no one else post so this can die off and not get unneeded attention/wasted space on the forum. Please save for the thread that will contain the root pack.
kdb424 said:
Please lock this thread mods. I'll start a thread when I finish an alpha for mac/linux. Thank you, and please no one else post so this can die off and not get unneeded attention/wasted space on the forum. Please save for the thread that will contain the root pack.
Click to expand...
Click to collapse
Please contact me, want to make sure brick precautions are made.
I'm beginning to think the manual method maybe more reliable from reading post on the easy root
Guys - here is where my blond shows.
I have a galaxy tab 7.7 sch-i915 running android 4.0.1 I would like to "root" this device as I did my ipad so and unleash the power of my tab
My issue is there is soooo many to pick from and I do not want to mess this up.. When I did my ipad, It was plain and simple with greenpoison. I'm new with android and I'm not sure on how to go about rooting my device?
I read the fourms guys - everyone is talking about ice cream, ginger bread, honeycombs... Im sorry If I read anymore of these topics I will have to hit the gym!!
Please - Someone anyone ... A simple way that I can Jailbreak my samsung to unleash its magic...
Muahhhhhhh
Ana :silly::silly::silly::silly::silly::silly::silly::silly:
we dont support piracy... and you think that rooting is like jailbreaking then... go use that idevice instead... you dont even need root to install apps... android is not crapple...
edit:type this on uncle google... how to install apps on android...
edan1979 said:
we dont support piracy... and you think that rooting is like jailbreaking then... go use that idevice instead... you dont even need root to install apps... android is not crapple...
edit:type this on uncle google... how to install apps on android...
Click to expand...
Click to collapse
Sweetie what is your problem? If I wanted to use that Idevice I would not be here asking how to root my samsung.. hun you need to step away from the keyboard - stop downing monster energy drinks and basically you need to get laid hun.. I never asked you to support piracy.. your a weird one baby...
anyway.. can someone please help me root my device? many thanks!
hehehe... just because mostly the old idevice user will relate jailbreaking & rooting for piracy... sorry if i offended you... ^_^
anyway... you just need to read in the forum... but since you've been nice... and i'm feeling nice... so i'm showing you the proper way.
the files you need
CWM recovery - http://d-h.st/hSK
Rooting files - http://download.chainfire.eu/331/SuperSU/UPDATE-SuperSU-v1.32.zip
how to root. first you need custom recovery (CWM)
1. go into download mode.
2. flash cwm with pc odin. can refer to this thread on how to... it got pictures as well if you still confuse http://forum.xda-developers.com/showthread.php?t=1469635
3. just subs the firmware part on step 5 with the cwm files.
Rooting guide
1. Transfer the attached file UPDATE-SuperSU-v1.32.zip to the INTERNAL or EXTERNAL CARD on Galaxy Tab 7.7
2. Turn off the Galaxy Tab 7.7
3. Enter Recovery
- Hold Volume UP button + Power Button
- When TAB turns ON, RELEASE POWER BUTTON (Keep Holding Volume UP Button)
- Will Enter Recovery
4. Select install update from EXTERNAL Storage
5. Look for the file UPDATE-SuperSU-v1.32.zip and select it with power button
6. When Finish, REBOOT. You're done!
edan1979 said:
hehehe... just because mostly the old idevice user will relate jailbreaking & rooting for piracy... sorry if i offended you... ^_^
anyway... you just need to read in the forum... but since you've been nice... and i'm feeling nice... so i'm showing you the proper way.
the files you need
CWM recovery - http://d-h.st/hSK
Rooting files - http://download.chainfire.eu/331/SuperSU/UPDATE-SuperSU-v1.32.zip
how to root. first you need custom recovery (CWM)
1. go into download mode.
2. flash cwm with pc odin. can refer to this thread on how to... it got pictures as well if you still confuse http://forum.xda-developers.com/showthread.php?t=1469635
3. just subs the firmware part on step 5 with the cwm files.
Rooting guide
1. Transfer the attached file UPDATE-SuperSU-v1.32.zip to the INTERNAL or EXTERNAL CARD on Galaxy Tab 7.7
2. Turn off the Galaxy Tab 7.7
3. Enter Recovery
- Hold Volume UP button + Power Button
- When TAB turns ON, RELEASE POWER BUTTON (Keep Holding Volume UP Button)
- Will Enter Recovery
4. Select install update from EXTERNAL Storage
5. Look for the file UPDATE-SuperSU-v1.32.zip and select it with power button
6. When Finish, REBOOT. You're done!
Click to expand...
Click to collapse
Thank you for your help.. I'm sorry that I do not know the difference between my ipad and android I'm just trying to learn.. Can you give me an idea on what this will do for my tab? Thanks! what are you doing home on a nice sat night?
One of (if not the first) rule in XDA is search before posting
Have a read of the (discontinued) guide in the General section by evil penguin. It is a "sticky". There are many similar throughout XDA where you will find a lot of the answers to your questions. They have been answered many times over and over, so there will be a plethora of information to digest
Sent from my GT-I9500 using xda premium
RhodeAna said:
Sweetie what is your problem? If I wanted to use that Idevice I would not be here asking how to root my samsung.. hun you need to step away from the keyboard - stop downing monster energy drinks and basically you need to get laid hun.. I never asked you to support piracy.. your a weird one baby...
anyway.. can someone please help me root my device? many thanks!
Click to expand...
Click to collapse
Seriously, what is with Captain Control!
---------- Post added at 02:43 PM ---------- Previous post was at 02:32 PM ----------
UpInTheAir said:
One of (if not the first) rule in XDA is search before posting
Have a read of the (discontinued) guide in the General section by evil penguin. It is a "sticky". There are many similar throughout XDA where you will find a lot of the answers to your questions. They have been answered many times over and over, so there will be a plethora of information to digest
Sent from my GT-I9500 using xda premium
Click to expand...
Click to collapse
The "rules" might very well say that but the intent of this site is to HELP users, correct? Most of us are trying to find a fix, solve a problem and landed on one of these pages from a spidered Google result. When trying to solve these problems we are hitting multiple sites and I guarantee you, you have not gone to each one and READ THE RULES! If you don't want to break Android policy and help her root, then why say anything at all?
sharonpta said:
Seriously, what is with Captain Control!
---------- Post added at 02:43 PM ---------- Previous post was at 02:32 PM ----------
The "rules" might very well say that but the intent of this site is to HELP users, correct? Most of us are trying to find a fix, solve a problem and landed on one of these pages from a spidered Google result. When trying to solve these problems we are hitting multiple sites and I guarantee you, you have not gone to each one and READ THE RULES! If you don't want to break Android policy and help her root, then why say anything at all?
Click to expand...
Click to collapse
Are you just trolling, yep, think so. Or have I misread your post? Most users and the recipient of my reply could obviously take the first sentence light hearted, with the "", the way it's meant to be....
I gave a suggestion and place to start to read the stickies. Stickies have lots of useful info. This, she can do herself without any help
Yes, PART of XDA ethos is about helping, but it's not about spoon feeding, is it?
BTW, I have read the rules nobody's perfect and will admit that even i have deviated from time to time edit: I'm also guilty spoon feeding too
Sent from my GT-I9500 using xda premium
UpInTheAir said:
Are you just trolling, yep, think so. Or have I misread your post? Most users and the recipient of my reply could obviously take the first sentence light hearted, with the "", the way it's meant to be....
I gave a suggestion and place to start to read the stickies. Stickies have lots of useful info. This, she can do herself without any help
Yes, PART of XDA ethos is about helping, but it's not about spoon feeding, is it?
BTW, I have read the rules nobody's perfect and will admit that even i have deviated from time to time edit: I'm also guilty spoon feeding too
Sent from my GT-I9500 using xda premium
Click to expand...
Click to collapse
It seems pretty clear to me that English is not the first language of a significant majority of people here.
It's also very clear that regardless of the first language of the members, understanding of the terms, concepts, applications and procedures vary widely among members. Subtexts are also lost or misunderstood.
Something to keep in mind when offering snarky opinions, offering help, etc
whitehawk66 said:
It seems pretty clear to me that English is not the first language of a significant majority of people here.
It's also very clear that regardless of the first language of the members, understanding of the terms, concepts, applications and procedures vary widely among members. Subtexts are also lost or misunderstood.
Something to keep in mind when offering snarky opinions, offering help, etc
Click to expand...
Click to collapse
Sorry, getting OT here.
Agreed. Things can be taken out of context easily. Happens all the time..... Sometimes we need to take things a little more light-hearted. myself included among those
Sent from my GT-I9500 using xda premium
Q&A for [ROM][GT-S6310N]GlassROM Young N Installer
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][GT-S6310N]GlassROM Young N Installer. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
I have used the installer from here: adbdriver.com/downloads to install the driver. It solved the driver problem which was the same.
However, the windows script is useless, it freezes the phone, do not waste your time.
martonl74 said:
I have used the installer from here: adbdriver.com/downloads to install the driver. It solved the driver problem which was the same.
However, the windows script is useless, it freezes the phone, do not waste your time.
Click to expand...
Click to collapse
Dude... you should be reporting that it does not work properly, instead of saying "don't waste your time". How am I supposed to fix the script if I don't get constructive feedback?
I didn't have time to try the Windows version, but I worked to make it work. So don't do that.
Sent from my GT-I9100 using XDA Free mobile app
> Dude... you should be reporting that it does not work properly, instead of saying "don't waste your time". How am I supposed
> to fix the script if I don't get constructive feedback?
> I didn't have time to try the Windows version, but I worked to make it work. So don't do that.
Gnmmarechal if you did not test the windows version, then why did you upload it? I am right that wasting time when trying a not tested script. So please do not delete my post again.
When the script runs, it makes several errors, for example this line is invalid:
adb shell rm /system/app/.apk
If you would like, I can upload the screenshot, but after then I have to re-flash the phone, so please ask me if you would really like to solve it. I have tried under Windows XP and Win7 with admin.
martonl74 said:
> Dude... you should be reporting that it does not work properly, instead of saying "don't waste your time". How am I supposed
> to fix the script if I don't get constructive feedback?
> I didn't have time to try the Windows version, but I worked to make it work. So don't do that.
Gnmmarechal if you did not test the windows version, then why did you upload it? I am right that wasting time when trying a not tested script. So please do not delete my post again.
When the script runs, it makes several errors, for example this line is invalid:
adb shell rm /system/app/.apk
If you would like, I can upload the screenshot, but after then I have to re-flash the phone, so please ask me if you would really like to solve it. I have tried under Windows XP and Win7 with admin.
Click to expand...
Click to collapse
That line was a typo, and I believe was fixed on the Linux version. Anyways, I uploaded it because I did not find any errors with it, people would likely want to use it on Windoes, and I didnt test it because I could not. You can, and it is your own fault if you brick anything. It does not hard brick anyways. Also, I did not delete any posts.
---------- Post added at 05:36 AM ---------- Previous post was at 05:05 AM ----------
Anyways, a new revision has been packed and uploaded, could you check it out?
Hello everyone.
First of all thanks gnmmarechal for your work on this unlucky device.
Before flashing current release (0.1.1) I'd like to ask the known issues, if any.
Is this ROM suitable enough for everyday use? I still can't find user's feedback about that.
Second question: what about flashing MammouthKernel v5 too?
It is reported to have some problem with N devices. Can someone confirm?
Thank you for your answers.
Up!
I flashed Emotion V10L... thanx anyway.
Like for example: A sticky thread informing you of what variants have unlocked bootloader or not, or what devices can be rooted what not, whether it's safe to update to the latest software, etc etc you get the gist of it. This has always been my gripe with XDA since back then. I would always have to dig to find these information
noddledizzy said:
Like for example: A sticky thread informing you of what variants have unlocked bootloader or not, or what devices can be rooted what not, whether it's safe to update to the latest software, etc etc you get the gist of it. This has always been my gripe with XDA since back then. I would always have to dig to find these information
Click to expand...
Click to collapse
And whom would create and maintain this sticky?
Sent from my mata using XDA Labs
---------- Post added at 09:30 PM ---------- Previous post was at 09:20 PM ----------
A few years ago a few of us started
The Index Project
https://forum.xda-developers.com/general/about-xda/public-index-program-project-t3147245
But it never really went anywhere.
While several Index were created
Participation from anyone other than the OPs
Was almost nonexistent.
Very few people have the time or knowledge
To maintain such threads.
Sent from my mata using XDA Labs
sd_shadow said:
And whom would create and maintain this sticky?
Sent from my mata using XDA Labs
---------- Post added at 09:30 PM ---------- Previous post was at 09:20 PM ----------
A few years ago a few of us started
The Index Project
https://forum.xda-developers.com/general/about-xda/public-index-program-project-t3147245
But it never really went anywhere.
While several Index were created
Participation from anyone other than the OPs
Was almost nonexistent.
Very few people have the time or knowledge
To maintain such threads.
Sent from my mata using XDA Labs
Click to expand...
Click to collapse
It does not really need to get maintained as much.Like for example: once X device is known to not allow bootloader unlocking, or X update won't let you downgrade thus you will lose the ability to root, etc etc. then it is established as it is. It takes a few minutes to just compile vital information on such devices. And the community for each individual device's forum should be responsible for each meta do's and don't sticky thread. Not a limited group of people who have to go to every single Android devices and compile each roms and guides like the project you linked me to. This isn't exactly what I'm proposing. Ggain, it's just a simple do's and don't/warning stick thread on each device's forums.
I mean I will be willing to make and maintain such thread in my devices' forums if this were a global rule on XDA. Because I don't want other people to make mistakes like I did just because I didn't find the information that is buried in a 100 page post.
Let me make an example. For my LGV30:
Thread title: Read me first/LGV30 Meta and Do's and Don't *sticky
+Updating to Stock PIE will require you to set your Selinux to Permissive in order to use AOSP/LOS roms
+sH932(T-mobile) is the only device with unlocked bootloader and require a more complicated root method
+US998(factory unlocked) is the preferred device because it can easily be converted to H930 which makes it compatible to all roms and overall have more support.
+Only H932 variant does not support Android 10
(etc etc...)
that wasn't so hard, if threads like this get enforced in all individual devices' forum, then it will reduce the amount of time people have to look, scavenging threads and also reduce questions all together. And also preventing people from making mistakes.
noddledizzy said:
It does not really need to get maintained as much.Like for example: once X device is known to not allow bootloader unlocking, or X update won't let you downgrade thus you will lose the ability to root, etc etc. then it is established as it is. It takes a few minutes to just compile vital information on such devices. And the community for each individual device's forum should be responsible for each meta do's and don't sticky thread. Not a limited group of people who have to go to every single Android devices and compile each roms and guides like the project you linked me to. This isn't exactly what I'm proposing. Ggain, it's just a simple do's and don't/warning stick thread on each device's forums.
I mean I will be willing to make and maintain such thread in my devices' forums if this were a global rule on XDA. Because I don't want other people to make mistakes like I did just because I didn't find the information that is buried in a 100 page post.
Let me make an example. For my LGV30:
Thread title: Read me first/LGV30 Meta and Do's and Don't *sticky
+Updating to Stock PIE will require you to set your Selinux to Permissive in order to use AOSP/LOS roms
+sH932(T-mobile) is the only device with unlocked bootloader and require a more complicated root method
+US998(factory unlocked) is the preferred device because it can easily be converted to H930 which makes it compatible to all roms and overall have more support.
+Only H932 variant does not support Android 10
(etc etc...)
that wasn't so hard, if threads like this get enforced in all individual devices' forum, then it will reduce the amount of time people have to look, scavenging threads and also reduce questions all together. And also preventing people from making mistakes.
Click to expand...
Click to collapse
Yep, so create the thread.
Sent from my mata using XDA Labs
---------- Post added at 03:24 AM ---------- Previous post was at 02:52 AM ----------
noddledizzy said:
... if threads like this get enforced in all individual devices' forum, then it will reduce the amount of time people have to look, scavenging threads and also reduce questions all together. And also preventing people from making mistakes.
Click to expand...
Click to collapse
How do you propose that these threads be enforced?
This site is maintained by volunteers.
If you want a thread with a list a of devices that can be bootloader unlocked
Create it.
The threads you are referring to were not created by Moderators
But mostly by regular members.
Sent from my mata using XDA Labs
sd_shadow said:
Yep, so create the thread.
Sent from my mata using XDA Labs
---------- Post added at 03:24 AM ---------- Previous post was at 02:52 AM ----------
How do you propose that these threads be enforced?
This site is maintained by volunteers.
If you want a thread with a list a of devices that can be bootloader unlocked
Create it.
The threads you are referring to were not created by Moderators
But mostly by regular members.
Sent from my mata using XDA Labs
Click to expand...
Click to collapse
Yes I could, but that would only be for my LGV30. What about for other devices? Besides, if I were to post this, such an unpopular idea would get buried below posts and unlikely for it to get stickied. People post guides all the time and custom roms, also take their time to help people individually who asks the same questions. So I think it's not hard to create such thread. I just want to spread awareness to help each other out.
If moderators were to spread this idea and tell users to make a meta thread about a device's do's and don't then people would be encouraged to do it. It's simply the lack of this idea is what stopping it. It's not like it's all going to be for naught. You will get 'thanks' for it, racking up your stack of 'thanks' lol.
In the end, I apologize if this idea is absurd and unnecessary . I just think that it will help everyone from the long run. Including myself. Thank you for listening to my suggestion.
I've got a bit of a problem. After installing a rom and deciding to go back to stock, I've run into the issue that I cannot for the life of god get my fingerprint registered. My phone says it fails to register, and I've factory reset it every way possible. I'm pretty positive that it's something to do with the persist img, but when I used the solution the one guy posted for it, it of course didn't work. Why doesn't the msm tool fix it? Doesn't it reset everything? What should I do?
Qualex11 said:
I've got a bit of a problem. After installing a rom and deciding to go back to stock, I've run into the issue that I cannot for the life of god get my fingerprint registered. My phone says it fails to register, and I've factory reset it every way possible. I'm pretty positive that it's something to do with the persist img, but when I used the solution the one guy posted for it, it of course didn't work. Why doesn't the msm tool fix it? Doesn't it reset everything? What should I do?
Click to expand...
Click to collapse
Welcome to XDA!.
The more info you provide the better and faster you will get help.
Try reading the forum rules and post in the specific device section.
Enjoy!
orb3000 said:
Welcome to XDA!.
The more info you provide the better and faster you will get help.
Try reading the forum rules and post in the specific device section.
Enjoy!
Click to expand...
Click to collapse
Hey could you delete this thread? I managed to fix my problem.
Qualex11 said:
Hey could you delete this thread? I managed to fix my problem.
Click to expand...
Click to collapse
Hello @Qualex11 and I'd like to also welcome you to XDA. I hope you like your visits and stays on this website and that you always receive valuable support in case of any problems.
First, please be aware that we don't delete threads after XDA has been indexed by search engines as this would provide HTTP 404 errors and in turn a poor user experience. We rather close a thread on request of a thread owner like you!
However, in this case I like the thread to remain open unless you definitely want to have it closed but with a serious request to you. XDA is about sharing - not only development but also knowledge and experiences. How about if you share here what you did that solved your issue? I'm convinced there're other XDA members around who have either already experienced the same problem and are eagerly waited for a solution or there're might be others who will be very happy in future if they directly find a fix for their issue.
I honestly invite you to present your solution here - and we're all be very grateful! If you don't want just feel free to shoot me a PM or to report via the report function, and your thread will be closed.
Stay safe and stay healthy!
Regards
Oswald Boelcke
Forum Moderator
I actually fixed the problem with a tutorial about it on youtube. I had just messed up a step previously, but I repeated it and it worked. Just do a quick search "oneplus 8 persist fix" on youtube, and it should be the first one