I'm trying to unlock and s-off..I've got everything setup for firewater im just trying to issue commands through cmd now.
When I type in
adb push firewater /data/local/tmp
it tells me that there is no such file or directory. I've put firewater on my desktop like someone said to somewhere and in a bunch of adb file that i thought might help...Where am i suppose to put firewater to make it readable by adb?
It should be in the same folder that contains adb. Otherwise you would need to add the full path with slashes in front of "firewater"
Blockay said:
I'm trying to unlock and s-off..I've got everything setup for firewater im just trying to issue commands through cmd now.
When I type in
adb push firewater /data/local/tmp
it tells me that there is no such file or directory. I've put firewater on my desktop like someone said to somewhere and in a bunch of adb file that i thought might help...Where am i suppose to put firewater to make it readable by adb?
Click to expand...
Click to collapse
The file goes in your adb folder in platformtools. When you run the command it's looking for it there.
thunderbls said:
The file goes in your abd folder in platformtools. When you run the command it's looking for it there.
Click to expand...
Click to collapse
thanks you guys i see the light at the end of the tunnel now...
i got it to work now but firewater tells me this
" whelp, this sucks, firewater can not work on your device
no amount of reflashing, retrying, or ruuing will fix...
DO NOT COME TO IRC ASKING FOR UPDATES OR ETAS!!!!!!
if we are able to fix this issue, it will be announced
bye bye.....sorry it didn't work out."
:/ am i able to do anything or no?
Blockay said:
thanks you guys i see the light at the end of the tunnel now...but I have two different adb installations and i can't find the platformtools folder for the one that is working. i downloaded this one http://forum.xda-developers.com/showthread.php?t=2588979 . i see an 'adb' folder inside of /C: but it doesn't contain platformtools
Click to expand...
Click to collapse
Doesn't matter which, for Windows you just right click the adb file and open the command prompt from the folder. Just make sure you're sticking the firewater file in the same folder adb is located. It automatically sets the directory.
Blockay said:
thanks you guys i see the light at the end of the tunnel now...
i got it to work now but firewater tells me this
" whelp, this sucks, firewater can not work on your device
no amount of reflashing, retrying, or ruuing will fix...
DO NOT COME TO IRC ASKING FOR UPDATES OR ETAS!!!!!!
if we are able to fix this issue, it will be announced
bye bye.....sorry it didn't work out."
:/ am i able to do anything or no?
Click to expand...
Click to collapse
You can keep trying but firewater may just not work for your phone luckily there is the $25 option created by the same devs called sunshine. This is an application you download and run here is the web address...theroot.ninja/
Blockay said:
thanks you guys i see the light at the end of the tunnel now...
i got it to work now but firewater tells me this
" whelp, this sucks, firewater can not work on your device
no amount of reflashing, retrying, or ruuing will fix...
DO NOT COME TO IRC ASKING FOR UPDATES OR ETAS!!!!!!
if we are able to fix this issue, it will be announced
bye bye.....sorry it didn't work out."
:/ am i able to do anything or no?
Click to expand...
Click to collapse
Firewater definitely won't work, you need to use sunshine.
That's too bad..25$ is quite a bit considering I might not even keep my m8. Thanks for the help
Blockay said:
That's too bad..25$ is quite a bit considering I might not even keep my m8. Thanks for the help
Click to expand...
Click to collapse
Why might you not keep it, Looking into a different phone?
Yeah I like the xperias. But I may want a removeable battery..we'll see
Related
I have a question, when custom ROMs are available and we flash them to our Hero does that mean we will lose the Sprint apps that came with our phone? If so is there a way to back them up and restore them on the new ROM? I am most concerned about the GPS app.
Can you just
adb pull /system/app/Sprint_Navigator.apk C:\
and then install that apk?
nelson8403 said:
Can you just
adb pull /system/app/Sprint_Navigator.apk C:\
and then install that apk?
Click to expand...
Click to collapse
That would definitely work but there is no reason the apps should not be included. It's all up to the rom dev. But that would definitely work. That's how the Dream developers got the Sprint apps on the Dream.
chuckhriczko said:
That would definitely work but there is no reason the apps should not be included. It's all up to the rom dev. But that would definitely work.
Click to expand...
Click to collapse
This is what got Cyanogen in trouble and the C&D order. He was including Google licensed apps into his ROM.
Chances are custom ROM devs will not have the apps included for the same reasons.
Treefallingquietly said:
This is what got Cyanogen in trouble and the C&D order. He was including Google licensed apps into his ROM.
Chances are custom ROM devs will not have the apps included for the same reasons.
Click to expand...
Click to collapse
That is true, however Sprint has done no such thing yet. My theory is do until you get caught
nelson8403 said:
Can you just
adb pull /system/app/Sprint_Navigator.apk C:\
and then install that apk?
Click to expand...
Click to collapse
So, could i 'pull' the NFL app from my phone and email it to my friend with a G1 so he could use it too?
Negrito said:
So, could i 'pull' the NFL app from my phone and email it to my friend with a G1 so he could use it too?
Click to expand...
Click to collapse
Yep. The only one that did not work for me and my dream was the Sprint tv app.
chuckhriczko said:
Yep. The only one that did not work for me and my dream was the Sprint tv app.
Click to expand...
Click to collapse
Seriously? Dude i think you just made my best friends day!
Little help?
Ok, so i have a Mac and everything seems to be working ok but when i do this:
96-26-56-112:tools brynehobbs$ ./adb pull /system/app/Sprint_NFL.apk desktop
1185 KB/s (288423 bytes in 0.237s)
96-26-56-112:tools brynehobbs$
There is nothing new on my desktop. I'm not too sure what the 'local' path should be though...
Negrito said:
Ok, so i have a Mac and everything seems to be working ok but when i do this:
96-26-56-112:tools brynehobbs$ ./adb pull /system/app/Sprint_NFL.apk desktop
1185 KB/s (288423 bytes in 0.237s)
96-26-56-112:tools brynehobbs$
There is nothing new on my desktop. I'm not too sure what the 'local' path should be though...
Click to expand...
Click to collapse
Im not quite sure how the folder structure is for Mac OS but since it is unix this command will work:
Code:
./adb pull /system/app/Sprint_NFL.apk .
The dot basically says extract it right here. You can then look in the directory where adb is located and the file should be there.
Negrito said:
Seriously? Dude i think you just made my best friends day!
Click to expand...
Click to collapse
Yeah man. I was pretty psyched to have these apps (which personally, I like) on my Dream. The only complaint is the fantasy option in the NFL apk doesnt work on the Dream but then again, it currently does not work on my Hero so I dont know what gives there.
chuckhriczko said:
Im not quite sure how the folder structure is for Mac OS but since it is unix this command will work:
Code:
./adb pull /system/app/Sprint_NFL.apk .
The dot basically says extract it right here. You can then look in the directory where adb is located and the file should be there.
Click to expand...
Click to collapse
Awesome bro! That worked like a charm.
I just pulled this little move.
adb pull /system/apps c:\androidsdk\Stockapps
Backed up all of the apps... just incase...
Small correction
justpastfinish said:
I just pulled this little move.
adb pull /system/apps c:\androidsdk\Stockapps
Backed up all of the apps... just incase...
Click to expand...
Click to collapse
One small correction, it's "/system/app" (no plural s).
adb pull /system/app <wherever>
So i emailed my friend the Sprint_NFL.apk trough Gmail but when he tried to open it on his G1 he got: "there was a problem parsing the package"
Do i have to root his G1 and use adb to 'push' the file to the G1 for it to work properly?
justpastfinish said:
I just pulled this little move.
adb pull /system/apps c:\androidsdk\Stockapps
Backed up all of the apps... just incase...
Click to expand...
Click to collapse
Thats a good idea, i just did that as well.
5tr4t4 said:
One small correction, it's "/system/app" (no plural s).
adb pull /system/app <wherever>
Click to expand...
Click to collapse
Thank you... my bad...
I also am an Android/Linux noob. I dabble because I like to..
Negrito said:
So i emailed my friend the Sprint_NFL.apk trough Gmail but when he tried to open it on his G1 he got: "there was a problem parsing the package"
Do i have to root his G1 and use adb to 'push' the file to the G1 for it to work properly?
Thats a good idea, i just did that as well.
Click to expand...
Click to collapse
Well it should work. I just checked the dream forum and the mods were forced to remove the links so you cant get them from there anymore either. I dont think root is necessary but maybe it is. I would try adb or make sure he has install apps from unknown sources checked in settings->applications.
chuckhriczko said:
Well it should work. I just checked the dream forum and the mods were forced to remove the links so you cant get them from there anymore either. I dont think root is necessary but maybe it is. I would try adb or make sure he has install apps from unknown sources checked in settings->applications.
Click to expand...
Click to collapse
Yeah he has it checked, but he is across town so i cant quite adb it right this second. Next time i see him i'll see it i can get it going for him. Thanks for all your help!
Thanks for everyone's input I successfully backup up all my apps. Just in case. It was interesting to see the size of each app.
Just incase no one has stumbled upon it yet...
http://android.modaco.com/content/h...-modaco-custom-rom-core-featuring-wavesecure/
CDMA Rom - Modaco
I'm trying to perm root my mytouch 4g using Visionary
I have android 2.2.1 and have successfully temp rooted using Visionary
I download the root folder from HERE
I put them in the root of the SD card and open up Terminal Emulator and type in
su
cd /sdcard/root
sh root.sh
when I type the first line (su) I get the # and am told that Terminal Emulator has been granted superuser permissions.
when I type in the second line (cd /sdcard/root) I get this message
cd: can't cd to /sdcard/root
What could be causing this?
Thanks
Jonathan
The "cd" command is a "change directory" command, and there is no directory called "root" on your SD card, because either you haven't unzipped what you downloaded, or you unzipped it in the wrong place.
Unzipping what you downloaded creates a directory (or a "folder", if you're a Windows user) called "root" that has several files in it -- a kernel module and a script, if I remember correctly. The script loads the kernel module and makes a call to it in order to set S Off.
thank you much, I think I figured out the problem. I'll try again later and see what happens. I'll post back with the results later. Thanks again!
Jonathan
NOTE: Ok, I can now run through the
su
cd /sdcard/root
sh root.sh
commands but when it's done and I check for s-off I don't have it (I still have s-on)
I've tried this twice to no avail. any advise?
i am having the same problem. i've tried this method about 15 times, mostly with visionary r14, but also a couple times with r11. i have also tried the gfree method a couple times as well via the semi-automated method. no s=off!
i have a new MT4G direct from phone upgrade order. i've read of others who have rooted the MT4G before multiple times, but can't do it now with a new phone. i'm wondering if it's something HTC has changed with the newest releases.....
kenrippy said:
i am having the same problem. i've tried this method about 15 times, mostly with visionary r14, but also a couple times with r11. i have also tried the gfree method a couple times as well via the semi-automated method. no s=off!
i have a new MT4G direct from phone upgrade order. i've read of others who have rooted the MT4G before multiple times, but can't do it now with a new phone. i'm wondering if it's something HTC has changed with the newest releases.....
Click to expand...
Click to collapse
HTC was going to install a measure that would prevent "rage methods" from working on their phones. How ever, none of the tech blogs are reporting that this has been rolled out. So i doubt that is the case.
make sure the its set up as sdcard/root. If you've just extracted the folder and copied the extraction to the sdcard it's not set properly.
neidlinger said:
HTC was going to install a measure that would prevent "rage methods" from working on their phones. How ever, none of the tech blogs are reporting that this has been rolled out. So i doubt that is the case.
make sure the its set up as sdcard/root. If you've just extracted the folder and copied the extraction to the sdcard it's not set properly.
Click to expand...
Click to collapse
yes, i understand the root folder in the root of the sdcard, and not 2 root folders. (sdcard/root/root)
like i mentioned, i read posts from a couple people on here with the same problems with new mt4g's after having done it multiple times before with success.
kenrippy said:
yes, i understand the root folder in the root of the sdcard, and not 2 root folders. (sdcard/root/root)
like i mentioned, i read posts from a couple people on here with the same problems with new mt4g's after having done it multiple times before with success.
Click to expand...
Click to collapse
then set up the ADB (see my sig) and do it the long way.
neidlinger said:
then set up the ADB (see my sig) and do it the long way.
Click to expand...
Click to collapse
after doing that, would i start on #4 in this guide?
http://forum.xda-developers.com/showthread.php?t=858996
kenrippy said:
after doing that, would i start on #4 in this guide?
http://forum.xda-developers.com/showthread.php?t=858996
Click to expand...
Click to collapse
nope you would start @ number 1.
you need to download those files and check the MD5SUM of every download load. the files need to be PERFECT for it to work correctly.
and i cannot stress enough. take your time and read directions. Read through the list a few times and make sure you have a good understanding of what you are doing. Doing that wrong can make your phone an expensive paper weight.
instead of pushing stuff to the "SDK tools folder" you store it to the ADB folder TrueBlue had you create in his walkthrough. And make sure to change your target folder to "c:\adb".
and remember you are choosing to do this. so if you screw it up. it's on your shoulders not mine.
neidlinger said:
nope you would start @ number 1.
you need to download those files and check the MD5SUM of every download load. the files need to be PERFECT for it to work correctly.
and i cannot stress enough. take your time and read directions. Read through the list a few times and make sure you have a good understanding of what you are doing. Doing that wrong can make your phone an expensive paper weight.
instead of pushing stuff to the "SDK tools folder" you store it to the ADB folder TrueBlue had you create in his walkthrough. And make sure to change your target folder to "c:\adb".
and remember you are choosing to do this. so if you screw it up. it's on your shoulders not mine.
Click to expand...
Click to collapse
thanks for all the help/info. i'll hold off for a while to see what else unfolds in the coming weeks in regards to alternate root methods. i don't want to brick this thing, just to get it rooted.
kenrippy said:
thanks for all the help/info. i'll hold off for a while to see what else unfolds in the coming weeks in regards to alternate root methods. i don't want to brick this thing, just to get it rooted.
Click to expand...
Click to collapse
The way this phone is made it's going to be pretty difficult to write a "one click s=off" program.
If you are wanting the benefits of being rooted you can always use VISIONary.apk when you need the root features like AD-HOC tethering or Screen Shots.
neidlinger said:
The way this phone is made it's going to be pretty difficult to write a "one click s=off" program.
If you are wanting the benefits of being rooted you can always use VISIONary.apk when you need the root features like AD-HOC tethering or Screen Shots.
Click to expand...
Click to collapse
what i'd really like to do is remove some bloatware and demo games. (not just hide them) any way to do that aside from perm root?
kenrippy said:
what i'd really like to do is remove some bloatware and demo games. (not just hide them) any way to do that aside from perm root?
Click to expand...
Click to collapse
not really. As soon as you reboot they'll pop right back up.
ok thanks.
Two things.
1. I've decided to put off perm rooting until I can understand adb and use it properly. No need to rush, I've got time.
2. Is it true that given time, effort, and ingenuity there really isn't such a thing as a bricked phone? It can always be recovered, it's just a question of how far you have to go to do it?
I've read around a lot and though I've heard many people talk of bricking their phone, it seems like many say that if you can use things like adb commands you can pretty well fix any issue, it's just difficult.
Like I was saying in point 1, I'm newer to all this and I'm learning so thanks for answering!
Jonathan
lanternslight456 said:
2. Is it true that given time, effort, and ingenuity there really isn't such a thing as a bricked phone? It can always be recovered, it's just a question of how far you have to go to do it?
Click to expand...
Click to collapse
At minimum, I believe the phone requires a functioning bootloader in order to be able to connect via USB to fastboot.
Any update on this? I also just got a mytouch 4g yesterday and am trying to root it. Is it possible right now?
Root the mt4g
Friend, I used the adb method here on xda, after I got the forked childs msg, and restart terminal w/e, make sue to pull out battery. Restart, the LAST THING I DID WAS USE VISIONARY r14, to attempt permroot, took me a week before I figured out to try this, the guide said phone would be rooted after terminal commands went through. So, to recap if u entered everything correctly, (my avg protection was telling me my phone was rooted for a week after I pushed gfree using the adb method but had no s-off, tried visionary permroot, BINGO!) THANKS TO ALL THE HARD WORK/GUIDES ON XDA, using ICE GLACIER ROM, titanium backup, rom manager, root explorer, my internet security (ad free web) set cpu, cache cleaner ng, drocap, couldn't get barnacle to work, the tethering on board works fine. Quadrant standard for benchmarking.
My wifes mt4g arrived today, and I had it perm rooted, with s-off in about 20 minutes, following this guide from the wiki:
http://forum.xda-developers.com/showthread.php?t=858996
Sent from my Nexus One using XDA App
danger-rat said:
My wifes mt4g arrived today, and I had it perm rooted, with s-off in about 20 minutes, following this guide from the wiki:
http://forum.xda-developers.com/showthread.php?t=858996
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
dude this method is great especially if your a noob or cant use adb for whatever reason just use visionary for temp root and then using root explorer move the gfree file to data>local then open terminal emulator and follow the instructions that gives you s-off and allows you to use visionary to permaroot when you reboot and then rommanager it now supports 3.xx so you can flash gingerroms just be careful and have fun
[/FONT I thought of myself as a well seasoned vet when it came to rooting. I have had a G1 and a Mytouch 3g. Since I now have the Mytouch 4g I would like to root it completely. I have run Visionary and can have SU privileges, then cant boot into recovery. I then tried using my computer to root. Still nothing.. Any help? Thanks you!
Olliej said:
[/FONT I thought of myself as a well seasoned vet when it came to rooting. I have had a G1 and a Mytouch 3g. Since I now have the Mytouch 4g I would like to root it completely. I have run Visionary and can have SU privileges, then cant boot into recovery. I then tried using my computer to root. Still nothing.. Any help? Thanks you!
Click to expand...
Click to collapse
Visionary is only part of the process. You need a couple more files and a working knowledge of abd and using terminal on your Mytouch 4G:
files:
wpx.ko
hboot_dhd.nb0
Visionary
A Terminal app (I use SUFBS)
Commands:
push the above two files to /data/local using ADB
adb push wpx.ko /data/local
adb push hboot_dhd.nb0 /data/local
run visionary and get temp root
Terminal:
Open up the terminal app and type in “su” to gain root access
Once the “#” appears, type in “insmod /data/local/wpx.ko” and hit Enter. You should get a “function not implemented error,” which is what you want.
This next terminal command will turn your device into a nice paperweight if you mess it up. If you do mess it up, don’t blame me, this all on you!
dd if=/data/local/hboot_dhd.nb0 of=/dev/block/mmcblk0p18 and hit Enter.
Close the terminal app, now open up visionary again. Run temp root again. You might get the “device already rooted” notification, this does not matter, what you are doing is locking in root.
Go back and open up your terminal emulator once more time and request root by typing “su”
Once you get the #, type “sync” wait about three minutes and reboot.
You should have permanent root with the security off (S-off), to check : With the phone off, hold down volume down and power to open Hboot. The top line of the screen should have “S-off” at the end.
I wanna try this step soooo bad but i'm scared ****less I brick my fone. Considering I only got it for just 2 days now.
I did the terminal process with terminal emulator 4 times & whenever I bash the root.sh file, the wpx.ko gives me trouble. Did it this morning @ 4am so I cant quite remember the exact statement it came back with
Paso876 said:
I wanna try this step soooo bad but i'm scared ****less I brick my fone. Considering I only got it for just 2 days now.
I did the terminal process with terminal emulator 4 times & whenever I bash the root.sh file, the wpx.ko gives me trouble. Did it this morning @ 4am so I cant quite remember the exact statement it came back with
Click to expand...
Click to collapse
try this method ive havent done it as im waiting for my, mytouch 4g to come but u should the comments are saying it worked for them
http://briefmobile.com/how-to-permaroot-and-unlock-your-mytouch-4g/comment-page-1#comment-48683
My wifes mt4g arrive today, and I had it rooted and s-off in about 20 minutes, following this method from the wiki:
http://forum.xda-developers.com/showthread.php?t=858996
Sent from my Nexus One using XDA App
Something went wrong....
alfadog77 said:
try this method ive havent done it as im waiting for my, mytouch 4g to come but u should the comments are saying it worked for them
Click to expand...
Click to collapse
I tried that method, but whenever I right click & open the command window & type 'adb push gfree /data/local'......I get "adb is not recognized as an internal or external command, operable program or batch file"
The unlocker's method worked great for me, even as a total noob, and was real easy.
http://theunlockr.com/category/howto/android_how_tos/htc-mytouch-4g-how-tos/
Paso876 said:
I tried that method, but whenever I right click & open the command window & type 'adb push gfree /data/local'......I get "adb is not recognized as an internal or external command, operable program or batch file"
Click to expand...
Click to collapse
That means that the adb binary isn't in the folder you are working from. Either the binary is missing, our you are in the wrong folder with you command prompt.
Sent from my Nexus One using XDA App
danger-rat said:
That means that the adb binary isn't in the folder you are working from. Either the binary is missing, our you are in the wrong folder with you command prompt.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Ok so lemme just recap what I did to see where I went wrong. I downloaded the SDK, installed the platform-tools folder, then hold shift same time as I click on the tools folder, select open command winder here & started to type in the prompt. So Now which file is the adb binary?? Maybe I can try & see if I somehow moved or removed it
alfadog77 said:
try this method ive havent done it as im waiting for my, mytouch 4g to come but u should the comments are saying it worked for them
http://briefmobile.com/how-to-permaroot-and-unlock-your-mytouch-4g/comment-page-1#comment-48683
Click to expand...
Click to collapse
Thats the same gfree method stickied in the dev section.
Paso876 said:
I tried that method, but whenever I right click & open the command window & type 'adb push gfree /data/local'......I get "adb is not recognized as an internal or external command, operable program or batch file"
Click to expand...
Click to collapse
You need to set up the android sdk first. follow the directions in this thread
Droid_duder said:
The unlocker's method worked great for me, even as a total noob, and was real easy.
Thats the first method I tried and it didnt work. I got that wpx.ho isn't recognized or something like that & 1024 in, 1024 out yada yada. I've noticed ppl say that its regular to get that back but I've dont it like 5 times & whenever i boot into hboot, I'm still seeing 'S-ON'
Click to expand...
Click to collapse
I got the wpx error, which is why I searched a bit more, and then used the method I posted earlier...
To help with the cmd prompt, down load this file, and place it in the same folder that the adb binary is in (it's a file, named adb). Double click this file, and it silk open a prompt in that folder...
http://db.tt/aVW40cy
Sent from my Nexus One using XDA App
Paso876 said:
I wanna try this step soooo bad but i'm scared ****less I brick my fone. Considering I only got it for just 2 days now.
I did the terminal process with terminal emulator 4 times & whenever I bash the root.sh file, the wpx.ko gives me trouble. Did it this morning @ 4am so I cant quite remember the exact statement it came back with
Click to expand...
Click to collapse
I had no trouble with my previously posted root, however I have read that some people had to place the files in the root of the SDCard (and change the commands accordingly of course) to get it to work.
option94 said:
Thats the same gfree method stickied in the dev section.
You need to set up the android sdk first. follow the directions in this thread
Click to expand...
Click to collapse
Thanks. I didn't know about this step until I realized last nite I had no clue what 'SDK' was...lol
alfadog77 said:
try this method ive havent done it as im waiting for my, mytouch 4g to come but u should the comments are saying it worked for them
http://briefmobile.com/how-to-permaroot-and-unlock-your-mytouch-4g/comment-page-1#comment-48683
Click to expand...
Click to collapse
Thanks, this finally worked for me. I had to setup SDK, ADB & then in some miraculously way I got through all the commands without any errors....lol
Thanks to those who chipped in, I'll go by and individually thank you guys.
I wonder what I'll do next?? lol
I used the Ultimate s=off method and rooted and unlocked in 10 minutes. Work like a charm
Olliej said:
[/FONT I thought of myself as a well seasoned vet when it came to rooting. I have had a G1 and a Mytouch 3g. Since I now have the Mytouch 4g I would like to root it completely. I have run Visionary and can have SU privileges, then cant boot into recovery. I then tried using my computer to root. Still nothing.. Any help? Thanks you!
Click to expand...
Click to collapse
There are 4 or 5 complete guides in the development section. Just read through them all and pick the one you're most comfortable with. With the scripts provided it makes it pretty safe.
I've rooted 4 phones with no issues.
Alright so looks like I did something completely stupid and now my phone won't finish the boot process. I was looking at some remappings for the recent key to the menu option and from a post in the development section I found a thread in the International One X development forum that had re-odexed files so that the recent key stayed as the recent key and holding the home button became the menu key. Since they were re-odexed and I had root access I figured I would just manually replace them on my phone with Root Explorer...bad idea. The files were:
System/Framework/android.policy.odex
System/Usr/keylayout/qwerty.kl
After I moved them and reset permissions I rebooted my phone and now it goes through the first couple of boot animations but gets stuck on screen that displays beats audio at the bottom.
I really need to know what to do to fix this. When I plug my phone into my computer it recognizes it as a new \drive, but I don't have access to any of it (still says I need to mount). I also have the android SDk and adb installed if thats of any help. I would really like to not lose any data so hopefully thats possible.
Please help me with this if you have any knowledge of what to do.
Just one little quick update. Even though my computer won't let me access my One X as a drive, when I use command prompt and adb to check for adb devices my One X is listed.
Run the at&t ruu exe file, located in the Dev section.
tanman21 said:
Run the at&t ruu exe file, located in the Dev section.
Click to expand...
Click to collapse
Alright I'm downloading that now.
In the meantime, how do I get root access with adb/give it permission to overwrite read only files? I pulled the two files that caused this messed and pulled my backups, but when I push them back to the phone it tells me I can't because their read only. I'd rather do it this way since I will be changing only the files that caused the problem.
EDIT: Is the RUU really going to delete all the information on my device? If thats the case I would really appreciate figuring out how to get adb to push my backuped files to the /system directory instead
ErikWithNoC said:
Alright I'm downloading that now.
In the meantime, how do I get root access with adb/give it permission to overwrite read only files? I pulled the two files that caused this messed and pulled my backups, but when I push them back to the phone it tells me I can't because their read only. I'd rather do it this way since I will be changing only the files that caused the problem.
EDIT: Is the RUU really going to delete all the information on my device? If thats the case I would really appreciate figuring out how to get adb to push my backuped files to the /system directory instead
Click to expand...
Click to collapse
Yeah, the RUU returns your phone to factory (but doesn't touch your personal files)
EDIT: Also, just pulling this off the top of my head so take it with a grain of salt...
adb devices
adb shell
su
*grant the su request on your device*
adb push <from> <to>
stnguyen09 said:
Yeah, the RUU returns your phone to factory (but doesn't touch your personal files)
EDIT: Also, just pulling this off the top of my head so take it with a grain of salt...
adb devices
adb shell
su
*grant the su request on your device*
adb push <from> <to>
Click to expand...
Click to collapse
Thanks for your comment. I used the RUU and it kept my personal data so its not a big lose. Had to reinstall a few apps, but for most of them (games at least) my saved data was still there.
I tried a lot using adb and just couldn't get it to work. I don't the phone got far enough through the boot process for root access to be allowed. I was able to run the one click root tool while it was in its stuck boot phase, but it still wouldn't give me permission to modify the /system portion of the phone to be read/write.
All in all though this was a great learning experience. Prior to this happening I knew nothing about adb and now I know commands for pulling, pushing, remounting, shell commands, and other things. I also learned how to fix a softbrick (first one) and what RUU is.
Hi everyone.
I don't know why i have this "module". Only install the other one and nothing more.
I try to delete it then restart phone but it doesn't go away.
Not a problem, just aesthetic
That's weird....
If you are bothered and you don't mind re-installing/re-flashing all your modules again, you could try the adb command
Code:
adb wait-for-device shell magisk --remove-modules
and that should remove all your modules including that unknown weird one.
Also, if for whatever reason that doesn't work, I read somewhere that Magisk has its data folder outside of the internal storage folder and is more in the root data folder -- so if one wiped their phone, all the Magisk data (deny list i imagine, on top of modules) would still survive -- and you might consider finding and deleting that folder and reinstall/re-flash Magisk. CAUTION: I imagine this has a chance of bringing up some glitches or bugs (incompatibilities) when the app connects-to/works-in-conjuction-with the patched init_boot.
If you are still sure you wish to do that, I believe I found the folder which I put in spoilers below...
Spoiler: Magisk root folder
root: /data/adb
These are just a couple of ideas...hope it helps...
Thx for your help !
The adb command works.
Plathoon said:
Thx for your help !
The adb command works.
Click to expand...
Click to collapse
I also have the same problem.... ".core" and i cannot delete it...its like a bug or something like that?
Plathoon said:
Thx for your help !
The adb command works.
Click to expand...
Click to collapse
Hello, I have the same problem where I have to apply those lines, in the bootloader, recovery? I tried both and neither worked. Thank you in advance
is this the official version downloaded from an official source? check the magisk forum
febo17 said:
Hello, I have the same problem where I have to apply those lines, in the bootloader, recovery? I tried both and neither worked. Thank you in advance
Click to expand...
Click to collapse
sorry for the very late reply...been a busy couple of weeks and am only catching up on things now...I'm fairly positive you figured it out already, but in case you haven't and/or any other person reading this looking for the answer...
I've never used the line before, but as I understand it, after turning off your phone and before connecting your phone to the computer, open up the cmd and run the command when you've changed the directory to the platform-tools folder. I believe the "wait-for-device" part has it running but on standby to activate once you plug your phone to the computer and it powers on (and tries to load up)...
I imagine once it does, it'll run the command and is executed before it goes any further loading up the module that is causing the issue/bootloop...
Hopefully I am correct and this helps...
simplepinoi177 said:
sorry for the very late reply...been a busy couple of weeks and am only catching up on things now...I'm fairly positive you figured it out already, but in case you haven't and/or any other person reading this looking for the answer...
I've never used the line before, but as I understand it, after turning off your phone and before connecting your phone to the computer, open up the cmd and run the command when you've changed the directory to the platform-tools folder. I believe the "wait-for-device" part has it running but on standby to activate once you plug your phone to the computer and it powers on (and tries to load up)...
I imagine once it does, it'll run the command and is executed before it goes any further loading up the module that is causing the issue/bootloop...
Hopefully I am correct and this helps...
Click to expand...
Click to collapse
in fact I had already applied that line and it didn't work either in fastboot or in ell recovery. It worked for me, to my surprise, with the phone on. all modules were deleted
What version of Magisk are you using, and where did you download it from?