Related
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.
Hello,
I'm Using a Rooted Starmobile Up has an MediaTek MT6582M
well, it started when i was changing the bootanimation of my phone with an marvelboot.zip using ES File Explorer, i forgot to set the permissions so after i restart it, my phone stucked at boot animation.
i copied the marvelboot.zip at the /Device > system > media folder as far as i can remember.
i think it will be solved if i am able to delete the bootanimation.zip from that media folder using computer or something else.
i am wondering how can i delete that file from the system folder, or perhaps change permission? and is there a way to browse the system folder from android to computer?? i just wonder if theres such, but i will go with your answers.
i have no CWM installed and i dont know how, i dont know ADB, or SDK and all
when i tried installing CWM from recovery menu, it says installation aborted and thats my only way.
can someone help me?
another thing is i forgot to backup the firmware, and ofcourse warranty is voided as it is rooted, i cannot get it's firmware anywhere.
thanks again
I need your help, thank you.
OK so you can post your question here: http://forum.xda-developers.com/showthread.php?t=2257421&page=1
However, I urge you to keep searching for the stock firmware. This is a rare device that has practically no support.
If you had adb support which is highly unlikely you could use the command "adb push bootanimation.zip/system/media"
But I very much doubt you will be able to get adb to communicate.
I wish you all the best in searching, but I think you may have just learned a very costly lesson on always having a backup before tinkering.
Good luck
hello, hmm what if i buy a new unit of this model? lets say another starmobile up, and i backup its firmware, is it possible to do that?
and is it possible to copy the back up on this device?
whateverwhenever said:
hello, hmm what if i buy a new unit of this model? lets say another starmobile up, and i backup its firmware, is it possible to do that?
and is it possible to copy the back up on this device?
Click to expand...
Click to collapse
I honestly don't think it would work. You really need a custom recovery or a way to access your bootlooping phone's system.
You can check this thread out on adb http://forum.xda-developers.com/showthread.php?t=2588979
If you're successful in getting adb to work you may have a shot at fixing it. But the odds are against you.
This is why we are all encouraged to read and be careful.
Thats the problem...Android Device Manager is useless cuz there is already a pattern...I tried almost 100 times and there is no "forgot your password?" option...I need at least do a copy of my pictures.
Is there any solution to this? I feel like a real idiot...I was trying a different pattern and I forgot It...I cant believe it...
I think there's a file not sure if it is directly under /data/system or one of it's sub directories, but basically what I did was to boot to TWRP , use the built it file manager and delete that file. I could then access my phone. I will search maybe I kept the file name somewhere.
EDIT:
Just remove this file /data/system/gesture.key
and reboot.
wizardwiz said:
I think there's a file not sure if it is directly under /data/system or one of it's sub directories, but basically what I did was to boot to TWRP , use the built it file manager and delete that file. I could then access my phone. I will search maybe I kept the file name somewhere.
EDIT:
Just remove this file /data/system/gesture.key
and reboot.
Click to expand...
Click to collapse
How I do that? my phone is not rooted, the bootloader is locked and debugging mode is off :S
Jerber said:
How I do that? my phone is not rooted, the bootloader is locked and debugging mode is off :S
Click to expand...
Click to collapse
That could be a problem. I think that it might be done using adb but not sure if it can be done without root/bootloader secured
If cracking an Android device were as easy as deleting a file then I doubt that there's much value in any security on a device at all, no?
Surely this has to be a reinstall of the ROM...? Maybe with no-wipe to preserve the data?
Genuine question - I don't know for sure.
dahawthorne said:
If cracking an Android device were as easy as deleting a file then I doubt that there's much value in any security on a device at all, no?
Surely this has to be a reinstall of the ROM...? Maybe with no-wipe to preserve the data?
Genuine question - I don't know for sure.
Click to expand...
Click to collapse
Testing it would be really easy. just set a pattern and then delete that file.
Lets us know is it is that easy to hack it or not.
Since obviously you know better, share your findings with us.
dahawthorne said:
If cracking an Android device were as easy as deleting a file then I doubt that there's much value in any security on a device at all, no?
Surely this has to be a reinstall of the ROM...? Maybe with no-wipe to preserve the data?
Genuine question - I don't know for sure.
Click to expand...
Click to collapse
The phone has to have an unlocked bootloader and twrp installed, so you already compromised its security yourself. You could relock the bootloader, flash a stock recovery and encrypt the phone, that would solve the issue.
"Since obviously you know better, share your findings with us."
Look, guy, just because you're a senior member there's no need to be offensively sarcastic.
Maybe you didn't get as far as my last comment: "Genuine question - I don't know for sure."
dahawthorne said:
"Since obviously you know better, share your findings with us."
Look, guy, just because you're a senior member there's no need to be offensively sarcastic.
Maybe you didn't get as far as my last comment: "Genuine question - I don't know for sure."
Click to expand...
Click to collapse
Not being Sarcastic at all. Making a point. If you got offended, sorry about that.
I posted what I have , after testing it myself. Had the same issue on Lollipop.
Further more, I will share another piece of Info in here.
When You are able to access any Solaris/Linux server using a console , and boot it from DVD, you can simply edit the /etc/shadow file and reset even the root password. Does that mean Unix/Linux aren't secure OS's ?
When you have access to OS level files you can practically hack every OS.
Same goes here. When you have unlock bootloader and modified recovery you can access system files that otherwise would be inaccessible. if he can have access to that file and remove it, he will gain access to his system.
Well, I tried everything that I could because my phone is no rooted, and the bootloader is locked, plus, the debugging mode is off too... so I was close to give up, BUT finally I remembered that my phone was connected to Airdroid!; if Airdroid is connected to the phone It can bypass the lockscreen and you can access to the internal memory anyways with the Airdroid website!, so I did a full backup of all my pictures and then I did a factory reset!, the copy was a kinda slow but I didn't care of course!. What a relief!!!
So, I really recommend use Airdroid (and have the app connected of course), it saved my life!, I was really frustrated about this, I cant believe Google doesnt provide the old way the restore the pattern like in Kitkat and Jelly Bean.
wizardwiz said:
I think there's a file not sure if it is directly under /data/system or one of it's sub directories, but basically what I did was to boot to TWRP , use the built it file manager and delete that file. I could then access my phone. I will search maybe I kept the file name somewhere.
EDIT:
Just remove this file /data/system/gesture.key
and reboot.
Click to expand...
Click to collapse
It worked like a charm!
I have a fingerprint enabled phone. forgot my pattern, followed your suggestion and presented in my phone are data/system/gesture.password.key and gesture.pattern.key so I deleted the pattern.key (guided by forgotten pattern) I rebooted and my apps were optimized and voila the phone is unlocked.
However, I tried accessing the fingerprint menu on my phone but refused access. I then used root explorer, browse to aforementioned location, copied and renamed gesture.password.key to gesture.pattern.key as it was before deletion.
went back to the security setting of my phone, setup pin option (scared of forgetting the pattern again) and phone screen locked. I try using my fingerprint to unlock (which I am accustomed to) and voila! it says pin required for additional security. entered Pin and the fingerprint menu became functional again and all previously stored fingerprints remained unaltered....QED
hi guys,
first, i m all time thankful to these developer guys, you make mobile world so genius, yeah it was never genius,
second, something i learn and something i want to learn more is about android always, but here is my question below that is really important. i don't know if it really make sense or not but i would like to know your opinion.
question :- i see there is a way to push files into device without rooting it. is it secure? it is safe? i guess yes. than how can i push titanium backup(data only) of particular app into my device?
example : - i myself after learning lot about apk tool and all that, modded "whatsapp" successfully and which is out of this world according to me, lately i cam to know there is already one called whatsapp GB, but mine is mine. (right now i don't have rooted device so couldn't send screenshot), but what i am trying to figure out is, i can install my modded apk on my non-rooted device and can run it either, problem comes when it is about registering number, what i really thought that if i can push titanium backup of my modded whatsapp.apk (data only - taken perviously when i had rooted device) to this non rooted device via ADB, than i didn't need to root my device ever, and so for any other app that is modded by me or any developers can be executed on non rooted device.
pros - if this is possible than i guess People won't need to root device, will not loose warranties, will not loose device by bricking it, will get out of a procedure of root methods, no one will ask more about root method, soft brick, hard brick, boot loader issues and many more questions like that i guess.
there will left only one tutorial than if this is possible and it will be like this - how to use adb?(step by step : beginner to black hat).
if this is possible than what we need? proper method of how to use adb, most of people easily can learn how to use adb but most of tutorial misses some points like how to push file by changing r/w permission, and where to put new data backup or files in device like some tutorial i have seen gives only command line but people actually don't know where to put the file like /data/data and than what?
Developers and Rooted device owner will become God in fact in this case because they can lead the rest in right path.
is this possible? or am i ridiculously making no sense?
joy.julep said:
hi guys,
first, i m all time thankful to these developer guys, you make mobile world so genius, yeah it was never genius,
second, something i learn and something i want to learn more is about android always, but here is my question below that is really important. i don't know if it really make sense or not but i would like to know your opinion.
question :- i see there is a way to push files into device without rooting it. is it secure? it is safe? i guess yes. than how can i push titanium backup(data only) of particular app into my device?
example : - i myself after learning lot about apk tool and all that, modded "whatsapp" successfully and which is out of this world according to me, lately i cam to know there is already one called whatsapp GB, but mine is mine. (right now i don't have rooted device so couldn't send screenshot), but what i am trying to figure out is, i can install my modded apk on my non-rooted device and can run it either, problem comes when it is about registering number, what i really thought that if i can push titanium backup of my modded whatsapp.apk (data only - taken perviously when i had rooted device) to this non rooted device via ADB, than i didn't need to root my device ever, and so for any other app that is modded by me or any developers can be executed on non rooted device.
pros - if this is possible than i guess People won't need to root device, will not loose warranties, will not loose device by bricking it, will get out of a procedure of root methods, no one will ask more about root method, soft brick, hard brick, boot loader issues and many more questions like that i guess.
there will left only one tutorial than if this is possible and it will be like this - how to use adb?(step by step : beginner to black hat).
if this is possible than what we need? proper method of how to use adb, most of people easily can learn how to use adb but most of tutorial misses some points like how to push file by changing r/w permission, and where to put new data backup or files in device like some tutorial i have seen gives only command line but people actually don't know where to put the file like /data/data and than what?
Developers and Rooted device owner will become God in fact in this case because they can lead the rest in right path.
is this possible? or am i ridiculously making no sense?
Click to expand...
Click to collapse
Hello,
Please post your query here Ask any Query Newbie Friendly with all relevant details, the experts there maybe able to assist you.
-Vatsal
Found my old phone from high school. Turned it on and looks like I never factory reset it, and I would love to see all of the photos and messages I left behind, however I can not for the life of me remember the pin I used. Browsed around and tried to delete the gesture.key using ADB but permission is denied, and I wasn't able to find a custom recovery tool for this specific phone either. Anyone have any possible solutions? Thank you
Shiiiba said:
Found my old phone from high school. Turned it on and looks like I never factory reset it, and I would love to see all of the photos and messages I left behind, however I can not for the life of me remember the pin I used. Browsed around and tried to delete the gesture.key using ADB but permission is denied, and I wasn't able to find a custom recovery tool for this specific phone either. Anyone have any possible solutions? Thank you
Click to expand...
Click to collapse
If you cannot remember the PIN, you're most likely going to have to factory reset. There is no way around this that I know of, unfortunately.
you can just dump the whole userdata partition off flash memory in EDL mode, loop mount partition image from linux and modify it's content (like deleting locksettings.db)
Shiiiba said:
Hi there, thanks for responding to my forum post. I can give it a shot, however I was wondering if you would be willing to help me with attempting this. Im familiar with root and devices but I’ve not had any experiencing with dumps or tools like the one you provided on github. I have an extra ZTE Flash to test on but some extra insight would be nice. I also had two questions:
1: can I just take the locksettings.db and somehow retrieve my pin from it instead of modifying and dumping?
2: if I do end up having to dump, will the environment be the same (IE logged in apps, id like to see my message history in apps that are there)
Thanks so much, and sorry for disturbing.
Click to expand...
Click to collapse
you need a firehose programmer matching your SoC and OEM. the tool comes with collection (loaders) for quite few devices, just give it a try.
1. might be possible with password.key
2. yes by just deleting locksettings.db nothing is changed