Related
About a day ago I didn't know anything about rooting and what it was but now I know to a degree from many hours of reading.
These are the steps I did.
You have to make sure that you choose the correct one click root method for the DI07 patch. Obviously you need to put the epic in debugging mode and click on the appropriate run.bat command and let the batch run. That part wasn't to hard for me, pretty much self explanatory.
Also to check for "root", to make sure your epic is rooted, download titanium backup from the android market and if it launches your epic is rooted and plus it will say root status "ok"..
The part I had issues with was with the one click clockwork recovery. Especially when people started talking about typing in commands in the dos prompt. I'm ok with doing that but it wasn't explained in full detail regarding what to do.
So first thing that I had to figure out was what they meant by c:/android-sdk-windows/tools and where was this located. I didn't have this file on my cpu on the c: drive and i was lost at this point being that I didn't know where to get it. I later found out and if im wrong please tell me you had to create your own folder on your c: drive so you can point to it from the c: prompt in dos. So I went ahead and did that.
In the tools folder from android-sdk-windows folder you would go ahead and place the contents of the clockwork recovery files in the tools folder. So wahla I now have a folder I can point to in the dos prompt. At this point I still didn't know if this is going to work or not but I felt like I was close.
Next step was to follow "open up command prompt and redirect it to your C:/android-sdk-windows/tools folder and then run the following code."
adb devices
adb shell
su
remount rw
exit
exit
first you need to type cd C:/android-sdk-windows/tools and press enter to point to that folder. And run subsequent commands from there.
If when you type in adb devices and a device does not pull up that means that the usb drivers are not installed properly for the epic phone and you need to look into that first.
After you run those commands now you can go ahead and run the run.bat file for the clock works recovery. But also make sure your still in debugging mode.
This might take a few tries but it will eventually work and if it does not work after trying to flash the recovery and the epic reboots pull the battery (reinstall battery) and then try to go into recovery by pressing the vol down--camera--and power button at the same time and you should see a green recovery screen.
I wish someone had typed something like this sooner so I wouldn't of had issues.
I hope this helps at-least one person.
Good idea except it's already been done :-\
http://forum.xda-developers.com/showthread.php?t=786305
Whosdaman said:
Good idea except it's already been done :-\
http://forum.xda-developers.com/showthread.php?t=786305
Click to expand...
Click to collapse
I know I was trying to follow that but there was parts missing that I didn't understand for ex. the part where I had to create the actual folder it never stated to create a folder but it wanted you to point to it in the dos prompt. And yes that tutorial did help out tremendously but i was still a little lost. My explanation fills in the missing gaps or parts. But thank you for pointing that out.
Maybe with noobnl latest version of the clockwork installer (version 32 with mount rw included in the script) you no longer need to go into adb?
jimmyz said:
Maybe with noobnl latest version of the clockwork installer (version 32 with mount rw included in the script) you no longer need to go into adb?
Click to expand...
Click to collapse
That is correct. Version 32 is truly one-click.
mattallica76 said:
That is correct. Version 32 is truly one-click.
Click to expand...
Click to collapse
Thats true
I'm not quite as noobish as the OP but I'm a complete noob to Android and -nix os's in general (besides a tiny bit of unix experience and a non-fear of command-line interfaces). Still, I have enough fear of the process to wait until Epic ROMs are a little further along and more refined to the degree that that's possible. If I weren't quite so noobish I'd dive right in.
Hey guys
I screwed up my vold.fstab trying to get "_ExternalSD" back.
Unfortunately! I did not run a nandroid before I made the change.
Now, I can dirty flash my rom on top, or go back to a nandroid from a few days ago, but I'd really just like to recover and go on my merry way. And maybe learn something in the process.
Only thing is, I can't figure out how to access the phone other than the External SD card through CWM.
Can I mount the internal /system and access through USB? Is there some facility to copy a file from one point to another? Any other methods? I guess the phone has to be up to run ADB, right?
I don't know how to generate a flashable zip but I could extract the original version of the file from the original rom. I assume that its non trivial to create a flashable zip, but maybe someone can comment? It looks like there is signing and certificates involved..
thanks for any ideas
bluenote73 said:
Hey guys
I screwed up my vold.fstab trying to get "_ExternalSD" back.
Unfortunately! I did not run a nandroid before I made the change.
Now, I can dirty flash my rom on top, or go back to a nandroid from a few days ago, but I'd really just like to recover and go on my merry way. And maybe learn something in the process.
Only thing is, I can't figure out how to access the phone other than the External SD card through CWM.
Can I mount the internal /system and access through USB? Is there some facility to copy a file from one point to another? Any other methods? I guess the phone has to be up to run ADB, right?
I don't know how to generate a flashable zip but I could extract the original version of the file from the original rom. I assume that its non trivial to create a flashable zip, but maybe someone can comment? It looks like there is signing and certificates involved..
thanks for any ideas
Click to expand...
Click to collapse
this is why i hate it when people make those guides.
messing with the vold.fstab is dangerous (even though its only a few lines) if your trying to recover your data, give up. its not going to happen. (sorry)
when you edit the vold.fstab it messed up the partitions on your internal SD card and most likely did the equivalent of wiped your /system partition. (or another important one.) your actually lucky it did not completely brick your phone.
your post was a little vague, but if you can, just restore an older nandroid, or wipe everything and install another ROM. (you can try dirty flashing but i dont think itll work)
if you cannot access CWM, then follow the steps in This guide. it should get you back up on your feet. after you follow that guide flash a gingerbread ROM (any gingerbread rom will do fine) then you can reboot and flash any ROM you want. (it needs this to fix a quirk in that script)
Hope you get it fixed
EDIT: re read your post, if your feeling adventurous and want to give it a shot, boot into CWM and connect it via usb. you can now get into an ADB shell on your phone by typing 'adb shell' if you have adb all setup and working. (im working from memory here so dont quote me on any of this)
now, you should be able to access your /system folder from that shell. be very careful though, i dont have much experience right here, and if i remember correctly you might not be in the full root directory yet)
if you can get into it try replacing your vold.fstab with a stock one,
if you dont have a stock one lying around, make a nandroid of the current state of the rom, then flash another rom, pull the vold.fstab, then re-restore back to the broken one and restore it (id upload mine but my phone is OOC right now )
after that just reboot and hope it resolves itself, if not then just follow my advice above
and keep that guide i linked to handy, messing around in CWM has the ability to brick your phone, if it does, then just follow that guide.
Klathmon said:
this is why i hate it when people make those guides.
messing with the vold.fstab is dangerous (even though its only a few lines) if your trying to recover your data, give up. its not going to happen. (sorry)
when you edit the vold.fstab it messed up the partitions on your internal SD card and most likely did the equivalent of wiped your /system partition. (or another important one.) your actually lucky it did not completely brick your phone.
your post was a little vague, but if you can, just restore an older nandroid, or wipe everything and install another ROM.
if you cannot access CWM, then follow the steps in This guide. it should get you back up on your feet. after you follow that guide flash a gingerbread ROM (any gingerbread rom will do fine) then you can reboot and flash any ROM you want. (it needs this to fix a quirk in that script)
Hope you get it fixed
Click to expand...
Click to collapse
How bout adb and pushing the file back in? Or cant you access the phone via adb?
Sent from my LG-P970 using XDA
N00BY0815 said:
How bout adb and pushing the file back in? Or cant you access the phone via adb?
Sent from my LG-P970 using XDA
Click to expand...
Click to collapse
re read your post and updated my last post right after you posted
after dealing with noobies all day, i forget sometimes people want to try big things
Thanks guys. The info I was missing was there's no special trick to attaching adb while in CWM! Just plug in!
My phone is back up and running and partitions are fine as far as I can see after just booting up.
Hi there! I messed up with the vold.fstab filfe on my tablet – I replaced it with a downloaded file with the intention to transfer apps to my external SD card.
Now my tablet is only showing the startup logo and won’t continue loading. I can access recovery mode. Now I want to restore the original vold.fstab file.
My questions:
1. Using the Android SDK, the file explorer does not show any files, though my tablet is recognized.
2. Using adb push, it yields an error: permission denied, how to successfully push the original vold.fstab and replace the existing vold.fstab?
3. If I dump an image of my tablet and edit the dumped image, would this be easier compared to the steps above?
Thanks!
http://forum.xda-developers.com/showthread.php?t=1646108
Try this.
If this doesn't help you should ask in the section for your tablet to get more specific advice.
TwitchyEye said:
http://forum.xda-developers.com/showthread.php?t=1646108
Try this.
If this doesn't help you should ask in the section for your tablet to get more specific advice.
Click to expand...
Click to collapse
Thanks, I will try it later when I got home. My tablet is not found here. I have a Skyworth S71(3G) with RK3066 chipset.
BryanF said:
Thanks, I will try it later when I got home. My tablet is not found here. I have a Skyworth S71(3G) with RK3066 chipset.
Click to expand...
Click to collapse
You need to do an adb remount before you can push. Was it rooted before?
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
Mansa_noob, yes, my tablet is rooted. I followed some instructions about adb but had an error saying access denied, and also no files are displayed at file explorer. See my posts above. I also mounted it successfully. I will post some sreenshots later.
Please if you have some instructions, I am willing to try.
---------- Post added at 07:06 AM ---------- Previous post was at 07:02 AM ----------
TwitchyEye said:
http://forum.xda-developers.com/showthread.php?t=1646108
Try this.
If this doesn't help you should ask in the section for your tablet to get more specific advice.
Click to expand...
Click to collapse
Hi twitchyEye, it did not work. It attemps to install (using the install update from ext sd card) but then says installation aborted.
Any more suggestions? Thanks
What recovery are you using? I suck with adb so I got nothing on that front.
It was the stock recovery from my Tablet. I don't have it on hand right now, I will post later. The chipset is RK3066. My problem is my tablet has no official support on the internet (maybe becaue it's still new). Model is Skyworth S71(3G).
I see. Yeah this is over my head man. I thought for sure you were running a custom recovery and it was an easy answer. I'm actually struggling right now with adb myself with a similar issue something about permissions whenever I try to do anything to my phone. So I guess right now would be a perfect time for somebody to chime in with a smarter answer!
TwitchyEye said:
I see. Yeah this is over my head man. I thought for sure you were running a custom recovery and it was an easy answer. I'm actually struggling right now with adb myself with a similar issue something about permissions whenever I try to do anything to my phone. So I guess right now would be a perfect time for somebody to chime in with a smarter answer!
Click to expand...
Click to collapse
Are you doing adb remount and still getting permission denied?
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
mansa_noob said:
Are you doing adb remount and still getting permission denied?
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
Click to expand...
Click to collapse
Yes, I did adb remount and still access denied
BryanF said:
Yes, I did adb remount and still access denied
Click to expand...
Click to collapse
This is strange. A properly rooted phone would adb remount to r/w system. Something is fishy. Is it rooted+
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
mansa_noob said:
This is strange. A properly rooted phone would adb remount to r/w system. Something is fishy. Is it rooted+
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
Click to expand...
Click to collapse
I am sure it is rooted, because I downloaded an application from Google play to check it it is rooted or not. It is really rooted. I alvo confirmed this as I can now fully backup and restore my apps using Titanium backup before the tablet is messed up.
BryanF said:
I am sure it is rooted, because I downloaded an application from Google play to check it it is rooted or not. It is really rooted. I alvo confirmed this as I can now fully backup and restore my apps using Titanium backup before the tablet is messed up.
Click to expand...
Click to collapse
OK. Odd or not, it is what it is. Is it possible for you to load a custom recovery?
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
mansa_noob said:
OK. Odd or not, it is what it is. Is it possible for you to load a custom recovery?
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
Click to expand...
Click to collapse
I want to try, but the stock recovery is my last hold as I have no stock ROM. If I overwrite the stock ROM, I cannot reinstall it as I don't have a copy of it.
So why not flash cwm with nvflash and then make a backup of your current stock rom? I did exactly that.
Sent from my LG-P999 using xda premium
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.
I download the OTA and the phone resets. When I get the Android updating screen, it dies on 20%... then reboots and tells me the update failed. anyone know why it's failing to update? I did freeze some apps from titanium backup.
ImYoungxD said:
I download the OTA and the phone resets. When I get the Android updating screen, it dies on 20%... then reboots and tells me the update failed. anyone know why it's failing to update? I did freeze some apps from titanium backup.
Click to expand...
Click to collapse
That is probably why. I'd recommend doing a factory reset in recovery.
ImYoungxD said:
I download the OTA and the phone resets. When I get the Android updating screen, it dies on 20%... then reboots and tells me the update failed. anyone know why it's failing to update? I did freeze some apps from titanium backup.
Click to expand...
Click to collapse
If you're running titanium then that means you're rooted, right? If you're rooted you should NOT (ie. Never) take a factory ota update. It has the potential to brick your phone.
What ota was it?
Sent from a SYNERGIZED GalaxySIII
Thats your device telling you to stay way the hell away from OTA's and revert to the dev section for your flashing needs!
I usually update my rooted transformer infinity OTAs with no problems.
Never knew rooted S3 can't update OTAs. meh.
I don't feel like flashing the phone because backing up the IMEI looks like such a pain ... Looks like I will have to look over it again.
ImYoungxD said:
I usually update my rooted transformer infinity OTAs with no problems.
Never knew rooted S3 can't update OTAs. meh.
I don't feel like unlocking the phone because backing up the IMEI looks like such a pain ... Looks like I will have to look over it again.
Click to expand...
Click to collapse
all you do is open terminal emulator, grant super user access, and type "NV Backup". I almost busted out in sweat the task was so strenuous.
droidstyle said:
all you do is open terminal emulator, grant super user access, and type "NV Backup". I almost busted out in sweat the task was so strenuous.
Click to expand...
Click to collapse
I have to start from scratch. I don't have ABD or whatever that thing was called. I'm going to try it out again some other day.
ImYoungxD said:
I have to start from scratch. I don't have ABD or whatever that thing was called. I'm going to try it out again some other day.
Click to expand...
Click to collapse
terminal is a app you download from the playstore... all you need is root access to use it.
droidstyle said:
terminal is a app you download from the playstore... all you need is root access to use it.
Click to expand...
Click to collapse
It's that simple...? never knew i can download it from the play store...
What is this whole site for? http://www.addictivetips.com/mobile/what-is-adb-and-how-to-install-it-android/
read this thread
http://forum.xda-developers.com/showthread.php?t=1852255
I got that link in step 1.
"1. If your phone does not have Terminal Emulator installed, you will need to use ADB. Download and install the Android SDK platform-tools for your platform. This is a bit non-trivial as it requires the installation of the Android SDK, however, you can find a guide for installing adb here. After installing, open a command prompt and navigate to the "platform-tools" folder within the SDK, where adb is stored. If you need additional help on this, simply ask in this thread."
That site with the guide to install adb has terrible instructions so I gave up.
ImYoungxD said:
I got that link in step 1.
"1. If your phone does not have Terminal Emulator installed, you will need to use ADB. Download and install the Android SDK platform-tools for your platform. This is a bit non-trivial as it requires the installation of the Android SDK, however, you can find a guide for installing adb here. After installing, open a command prompt and navigate to the "platform-tools" folder within the SDK, where adb is stored. If you need additional help on this, simply ask in this thread."
That site with the guide to install adb has terrible instructions so I gave up.
Click to expand...
Click to collapse
Dude you are making this way too difficult lol...install terminal emulator from the playstore and run the nv backup command...then never worry about losing imei again.
For Terminal Emulator: The actual "beef" of the command is the "reboot nvbackup" line. Therefore, if you have Terminal Emulator installed, you can just run the command straight off your phone. Enter these two commands from the app:
Code:
su
reboot nvbackup
I had the same problem. Ended up using odin to push the latest stock software which included the update. Now to see if I still get the no sim error. Realizing after all this time I really didn't need to root.
ImYoungxD said:
I did freeze some apps from titanium backup.
Click to expand...
Click to collapse
This is without a doubt the reason the update failed (unless there are multiple reasons). If you unfreeze the apps, it should install as expected.
apacseven said:
This is without a doubt the reason the update failed (unless there are multiple reasons). If you unfreeze the apps, it should install as expected.
Click to expand...
Click to collapse
I had zero apps frozen and was unable to install the update. Pushing it via Odin was the only thing that worked for me.
mdt73 said:
I had zero apps frozen and was unable to install the update. Pushing it via Odin was the only thing that worked for me.
Click to expand...
Click to collapse
Yes it isnt the only thing that can cause an update to fail. But since he already stated that he had frozen some apps, then it is known that the check will fail and the update wont proceed.
If you don't know why it failed. download to OTA. And when it prompts you to install, say you'll do it later. Now extract the update file from your /cache/ directory. (That's where it was on Motorola's, I think its /cache/fota/ on our S3 ). Copy/move that file to the root of your SD card. Reboot into stock recovery and flash it. Watch the update when it fails it will call out specifically what went wrong. When you let the system automatically do it you don't get that luxury. If you initiate the update on your own through stock recovery though, you are granted that key piece of Intel as to what it didn't like.
Freezing anything in titanium will fail an OTA automatically. It checks system files to make sure certain ones are there, especially bloatware. Also having custom recovery will fail you.
As was said if your rooted you should never both with OTA anymore. If you're coming from a motorola like I did it is hard to grasp that at first. We needed official OTA to update the kernel. So you almost had to do it. Now though. We have an unlocked bootloader here. You can flash any kernel you feel. So OTA are meaningless for us on the S3. The devs steal all the good code and bits and put it in their ROMs and leave out the garbage. No reason to need official OTA anymore then unless you truly want to
Sent from a GlaDos Baked Potato
droidstyle said:
Dude you are making this way too difficult lol...install terminal emulator from the playstore and run the nv backup command...then never worry about losing imei again.
For Terminal Emulator: The actual "beef" of the command is the "reboot nvbackup" line. Therefore, if you have Terminal Emulator installed, you can just run the command straight off your phone. Enter these two commands from the app:
Code:
su
reboot nvbackup
Click to expand...
Click to collapse
Seriously..... That was easy lol. What's the point of step 1
Since I never read the next lines that says " If your phone is rooted and has Terminal Emulator installed, you don't need to do any of this. Simply open up the Terminal Emulator and go to step 2.", I never completed backing up the IMEI probably because I didn't know the Terminal Emulator was an playstore app.... Now I got a backup, I'm unlocked, running a custom rom. Thanks a lot man. You helped a lot.
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thanks
FNM
ImYoungxD said:
Seriously..... That was easy lol. What's the point of step 1
Since I never read the next lines that says " If your phone is rooted and has Terminal Emulator installed, you don't need to do any of this. Simply open up the Terminal Emulator and go to step 2.", I never completed backing up the IMEI probably because I didn't know the Terminal Emulator was an playstore app.... Now I got a backup, I'm unlocked, running a custom rom. Thanks a lot man. You helped a lot.
Click to expand...
Click to collapse
No prblem sir, glad to help!
Hi!
Is there a root available or in the works for the dual-screen NEC Medias W N-05E?
The question has been asked (no answer so far) at the end of a thread under the N-05D but that's a quite different model.
I'd like to create a separate thread for this model to give it more visibility. Hope that's ok!
Thanks in advance!
bohemianRhapsody said:
Hi!
Is there a root available or in the works for the dual-screen NEC Medias W N-05E?
The question has been asked (no answer so far) at the end of a thread under the N-05D but that's a quite different model.
I'd like to create a separate thread for this model to give it more visibility. Hope that's ok!
Thanks in advance!
Click to expand...
Click to collapse
OK! I've made some progress on this: the japanese blogger "dupondroid" appears to say that run_root_shell (hosted at github)
successfully gives temp root. At least, that's my necessarily blurry understanding via google translate. Would any japanese readers here be able to post a better translation?
And a thread at r-2ch dot com links to the github commit in run_root_shell which made that possible: it's commit ID 811be8639aed64c158798a72a1d520a4d21e8b8b "Support N-05E"
Code:
+ { "N-05E", "A1000311", 0xc0094430, 0xc0093ebc }
So it definitely seems temp root is possible.
Sorry for the lack of links but I'm a new user so can't add them for now.
root is easy
bohemianRhapsody said:
OK! I've made some progress on this: the japanese blogger "dupondroid" appears to say that run_root_shell (hosted at github)
successfully gives temp root. At least, that's my necessarily blurry understanding via google translate. Would any japanese readers here be able to post a better translation?
And a thread at r-2ch dot com links to the github commit in run_root_shell which made that possible: it's commit ID 811be8639aed64c158798a72a1d520a4d21e8b8b "Support N-05E"
Code:
+ { "N-05E", "A1000311", 0xc0094430, 0xc0093ebc }
So it definitely seems temp root is possible.
Sorry for the lack of links but I'm a new user so can't add them for now.
Click to expand...
Click to collapse
root is easy via a tool called impactor.
however it's only temporary, I couldn't get /system mounted for rw. so I made a new recovery image to push.
that didn't work either, although I cannot write to recovery there is no error. recoverybkp was successful.
Also I found that the code to enter in recovery mode is based on your imei.
If I remember correctly digit 2,12,13,14 of your imei.
So possible attack vectors are:
1) kernel module to unlock partitions
2) figure out how update.dat files are constructed.
3) write to recovery partition
it0 said:
root is easy via a tool called impactor.
however it's only temporary, I couldn't get /system mounted for rw. so I made a new recovery image to push.
that didn't work either, although I cannot write to recovery there is no error. recoverybkp was successful.
Also I found that the code to enter in recovery mode is based on your imei.
If I remember correctly digit 2,12,13,14 of your imei.
So possible attack vectors are:
1) kernel module to unlock partitions
2) figure out how update.dat files are constructed.
3) write to recovery partition
Click to expand...
Click to collapse
I can't seem to get anything to work i'v tried Impactor did not work just gave me errors also tried run_root_shell but had to have some device.db file with I didn't really figured out, could some one please help?
Lukas_a_1996 said:
I can't seem to get anything to work i'v tried Impactor did not work just gave me errors also tried run_root_shell but had to have some device.db file with I didn't really figured out, could some one please help?
Click to expand...
Click to collapse
I used impactor 0.9.14, you just hook up the phone using microusb and put the phone in usb debugging mode under development options. then selecct "# start telnetd as root on port 22" from the pulldown and click start.
Then using a tool like putty ,telnet to your phone on port 22 (make sure it's connected to you wifi network when you do).
What android version are you running ? 4.1.2 is vulnarable for this attack.
it0 said:
I used impactor 0.9.14, you just hook up the phone using microusb and put the phone in usb debugging mode under development options. then selecct "# start telnetd as root on port 22" from the pulldown and click start.
Then using a tool like putty ,telnet to your phone on port 22 (make sure it's connected to you wifi network when you do).
What android version are you running ? 4.1.2 is vulnarable for this attack.
Click to expand...
Click to collapse
Thanks for the reply . I tried to run the command in impactor but whatever i do i get "Signature bugs unavailable" could it be that i have the wrong ADB drivers installed or is my Impactor setup wrong?
Edit: yeah im running 4.1.2 Build A1001231
You could try if you can just get an adb connection working.
with commands like
adb devices
adb shell
If that works then the rest should work as well.
it0 said:
You could try if you can just get an adb connection working.
with commands like
adb devices
adb shell
If that works then the rest should work as well.
Click to expand...
Click to collapse
All the adb commands basically work but nothing works with impactor i just get error
it0 said:
You could try if you can just get an adb connection working.
with commands like
adb devices
adb shell
If that works then the rest should work as well.
Click to expand...
Click to collapse
Bump!
How to Root Medias N05e
Dear All Pro
Does anyone show me how to root N05e? because there is very few information about that. I want to Swapfile to increase Ram size but it required N05e must be rooted.
So if anyone have any information about N05e, please share. Thanks
nguyenbuulam said:
Dear All Pro
Does anyone show me how to root N05e? because there is very few information about that. I want to Swapfile to increase Ram size but it required N05e must be rooted.
So if anyone have any information about N05e, please share. Thanks
Click to expand...
Click to collapse
There is a way for temp root N05E, basically u can use pm disable command or other su stuff. But u cannot mount system rw right now.
Some news about rooting
If someone in doubt, temp root is 100% working with run_root_shell https://github.com/android-rooting-tools/android_run_root_shell
With this I was able to copy full system, boot and recovery image. But I can't push new boot or recovery.
More than that, almost all fuctions in standard recovery mode (available through "reboot recovery" in root shell) are protected with some code. And it's not 2,11,12,13 numbers of IMEI.
Anyone know where to get this code? Or how to write new boot, recovery image? If we do so, we can get permanent root access =)
Maybe someone have Japanese friends? Search all English web, but maybe in Japan web there are some info.
P.S. with Impactor you only can start talnetd from root, becouse Impactor can't remount /system in rw mode and ro.kernel.qemu=1 option is not working
How to enter recovery mode?
Despite starting this thread, in the end I never did bother to attempt rooting.
Anyway, unfortunately now the phone refuses to boot. Not triggered by anything obvious, haven't installed any new software recently, etc. Just hung one day and then when I removed and re-inserted the battery, it won't get any further than the "docomo" splash screen. I.e. the OS doesn't appear to be getting bootstrapped at all. The "docomo" splash screen appears and disappears then the phone sits there with both screens powered up but blank.
As it happens, I had ADB Debug enabled in the developer options at the time, so I've tried to see if I can adb shell into the device, but no luck. Not surprised as it's clearly not getting far enough into the boot for that to work.
Any other suggestions? From the way it happened I do suspect it might just be hardware failure....
Not even sure how I enter recovery mode -- what are the key combinations for this?
bohemianRhapsody said:
Despite starting this thread, in the end I never did bother to attempt rooting.
Any other suggestions? From the way it happened I do suspect it might just be hardware failure....
Not even sure how I enter recovery mode -- what are the key combinations for this?
Click to expand...
Click to collapse
In recovery mode, clear cache, etc..
To get there hold volume down and power at the same time,then you'll see the broken android then wait/ press vol down a couple of times to see the menu.
GRbit said:
Some news about rooting
If someone in doubt, temp root is 100% working with run_root_shell https://github.com/android-rooting-tools/android_run_root_shell
With this I was able to copy full system, boot and recovery image. But I can't push new boot or recovery.
More than that, almost all fuctions in standard recovery mode (available through "reboot recovery" in root shell) are protected with some code. And it's not 2,11,12,13 numbers of IMEI.
Anyone know where to get this code? Or how to write new boot, recovery image? If we do so, we can get permanent root access =)
Maybe someone have Japanese friends? Search all English web, but maybe in Japan web there are some info.
P.S. with Impactor you only can start talnetd from root, becouse Impactor can't remount /system in rw mode and ro.kernel.qemu=1 option is not working
Click to expand...
Click to collapse
did you ever figure out the recovery keys?
hamishhhhs said:
did you ever figure out the recovery keys?
Click to expand...
Click to collapse
No I didn't(
I'm actually sold this phone and lost interest in the topic.
GRbit said:
No I didn't(
I'm actually sold this phone and lost interest in the topic.
Click to expand...
Click to collapse
do you by chance still have the files you dumped?
Ive teamed with a friend in twitter to try and make a rom for this but I haven't gotten very far
hamishhhhs said:
do you by chance still have the files you dumped?
Ive teamed with a friend in twitter to try and make a rom for this but I haven't gotten very far
Click to expand...
Click to collapse
Sorry, but this was too long time ago. Nothing left
GRbit said:
Sorry, but this was too long time ago. Nothing left
Click to expand...
Click to collapse
how would j be able to get the files from my phone?
hamishhhhs said:
how would j be able to get the files from my phone?
Click to expand...
Click to collapse
I dunno man.
I've already described (in the first post you have quoted) what I achieved with this github repo https://github.com/android-rooting-tools/android_run_root_shell . That's all I've got.