Related
SOLVED
See my most recent post in this thread
______________________________________________________________________________________
Firstly, I've spent the last three days scouring XDA and some other forums searching for solutions and trying various options.
The screen on my N4 has cracked and I've lost the use of the bottom half of the touchscreen. This means that I can't unlock my phone.
The phone is insured and will be repaired, but there are photos of my son's first birthday on the internal memory that I don't want to lose. I'm concerned that the phone will be factory reset during a repair or I'll receive a replacement. I'm trying to access the internal memory remotely to backup these files before I send the phone off. The problem is that I hadn't enabled USB debugging before the accident. The phone is completely stock including the bootloader.
So I can access via fastboot but not via adb.
Q1: Can I pull file from the internal memory via fastboot
Q2: Can I enable usb debugging via fastboot
Q3: The phone is set to display as an MTP device in windows but as I can't unlock the screen, none of the files are showing. Is there anyway around this?
Q4: Purely via fastboot, can I unlock the bootloader, install CWM so to use ADB within it and then return to a stock bootloader?
I think they're my options. Any answers to the above or alternatives would be appreciated.
All of the other threads regarding this, the users seem to either already have CWM installed or they're looking to perform a factory reset. I did consider resetting the device via the bootloader in order to bypass the screenlock but I understand that on the N4 this wipes the internal memory as well.
Unlocking the device isn't needed to pull the files from it, just plug it in and get what you need from the internal memory
EddyOS said:
Unlocking the device isn't needed to pull the files from it, just plug it in and get what you need from the internal memory
Click to expand...
Click to collapse
On mine if I plug it in it appears as an MTP device but with no files. I then have to unlock the screen and select USB something-or-other from the notificationss bar, then the files appear in windows.
Strange, mine never needs to be unlocked...I'm using Windows 8 Pro btw but it also works fine in work on Vista Business
Only other thing I can think of is the fact I'm unlocked and running a custom ROM, I've never used my N4 stock. It was on CM within 30 mins of receiving the unit!
So over the last week I've managed to solve my problem. I've seen several other people asking for help with no luck so I'm posting this here in the hope that the search function will bring it up.
Firstly, my phone was completely stock running 4.2.2, unrooted, with the locked stock bootloader. USB Debugging WAS NOT enabled. I had pattern lock enabled when I dropped the phone. The screen cracked and the bottom half of the touchscreen was unresponsive.
The phone was insured, but I wanted to backup photos from the device before sending it off for repair/replacement.
HOW I FIXED IT.
Please note, you need at least some part of the screen to be working, specifically, some part of the screen where the pattern lock is.
You only need two pieces of software. The Android SDK and the Nexus 4 Toolkit http://forum.xda-developers.com/showthread.php?t=1995688
If you are running 4.2.2 you will need to update the toolkit. I also had the standard issues of installing the USB drivers for the N4. You need to get to a point where is shows up as an ADB device in Windows Device Manager.
As I didn't have USB debuggin enabled I couldn't connect tothe phone via ADB, but if you put it into recovery mode you can use Fastboot. Hold down the power key to turn the device off and turn it on while holding down Vol Down to load up recovery mode.
If you then start the N4 Toolkit, you should see the device listed as a fast boot device.
From within the toolkit unlock your bootloader.
Flash a temporary bootlader, (option 10) as the touchscreeen was broken it has to be CWM.
Once in CWM you can start to use ADB. Open up a DOS command prompt in Windows, go to your SDK/platform tools folder/ to access ADB.exe and you can use the pull command to copy folders to your PC. At this point, instead you can use applications like ADBexplorer or DroidExplorer to do the same thing through a nicer GUI.
If you'd like to still be able to use your phone, although without the touchscreen, you can load an unstable image to get into android and then use ADB to start changing system settings.
Firstly, before exiting CWM, clear the cache. Without doing this the phone jsut hung on the Nexus symbol while loading the image.
in the toolkit go to root/unroot options and select load unstable image(option 4 and then 6). This will fire you up into Android and it should be set up as you left it.
I wanted to enable bluetooth so to use a keyboard (I didn't have a mouse but this is a better option) from the DOS window type the following command
am start -a android.bluetooth.adapter.action.REQUEST_ENABLE
You should eventually get a pop-up on your screen saying that a request has been made to enable bluetooth. Hopefully your screen is working enough to select enable.
Then I use the workaround to disable the sceenlock, found here -> (http://www.addictivetips.com/androi...e-pattern-unlock-on-android-via-adb-commands/) I found method 2 worked for me. I imagine this will be stopped in a future update.
Method 1
adb shell
cd /data/data/com.android.providers.settings/databases
sqlite3 settings.db
update system set value=0 where name='lock_pattern_autolock';
update system set value=0 where name='lockscreen.lockedoutpermanently';
.quit
Method 2
adb shell rm /data/system/gesture.key
If either of these methods are successful you will be able to unlock the phone with an pattern, hence why you need to be able to touch some part of it.
From then, my bluetooth keyboard was already mated to my phone to I was able the navigate the menus to turn on USB Debugging, turn-off the screen lock and a few other bits and pieces I needed to do.
I then restarted (I was still working within the unstable image) and on reboot, all my changes had al been applied. No screen lock, bluetooth enabled and USB Debugging enabled.
Hopefully this will be of help to those in a similar position. Thanks has to go to the toolkit though which provides all the necessary access to carry this out.
I should probably add, you can use the toolkit to relock the bootlader if you're concerned about that and if you can't click the screen to enable bluetooth or mate a keyboard or mouse, once you have USB Debugging enabled you can use software like Screencast to control you phone's screen from a PC.
So typically, just as I fill my claim to repair my nexus my wife drops her, smashing the screen even more than I did so she has absolutely no use of her screen. I went through the process again and though I'd post it in a more simple fashion.
1. Reset Nexus into recovery mode (power & volume down)
2. Connect to PC via USB. Install the USB driver from the SDK so that it appears as an ADB device
3. Fire up the updated toolkit. You should see the nexus as a fast boot device
4. Unlock bootloader
5. Using option 10 on the toolkit load up CWM on the phone. This gives you ADB access so can you pull files off the device via ADB although I could access the SD card through programs like Droid explorer.
6. If you want to carry on further and get into Android properly, you'll need to wipe the cache from within CWM
7. Reboot and hold down the volume key to get back into recovery
8. In the toolkit select root options (option 4) and load temporary image (6) If it hangs on the google or nexus logo you've not wiped the cache.
9. With this second phone I couldn't access it through droid explorer as it was popping up as an MTP device but I could pull the files via command prompt or through the toolkit
10. If you have any use of the touchscreen at all you can run the following command which will then mean that any touch will unlock the device
adb shell rm /data/system/gesture.key11. You can activate bluetooth via adb if you have a mouse or keyboard available but you will need to be able to press okay on the screen
12. Any changes you make in the unstable android image such as lockscreen, bluetooth, enabling debugging, etc will remain in place when you restart the device.
13. You can relock the bootloader if you wish via the toolkit. You just need to be in recovery mode first.
Hope this simplifies the process
Does unlocking bootloader via toolkit not wipe everything? How are you unlocking bootloader and still able to pull data off?
EDIT: it appears fastboot oem unlock on the Nexus 4 *does not* wipe data!
Carpetboy said:
So typically, just as I fill my claim to repair my nexus my wife drops her, smashing the screen even more than I did so she has absolutely no use of her screen. I went through the process again and though I'd post it in a more simple fashion.
1. Reset Nexus into recovery mode (power & volume down)
2. Connect to PC via USB. Install the USB driver from the SDK so that it appears as an ADB device
3. Fire up the updated toolkit. You should see the nexus as a fast boot device
4. Unlock bootloader
5. Using option 10 on the toolkit load up CWM on the phone. This gives you ADB access so can you pull files off the device via ADB although I could access the SD card through programs like Droid explorer.
6. If you want to carry on further and get into Android properly, you'll need to wipe the cache from within CWM
7. Reboot and hold down the volume key to get back into recovery
8. In the toolkit select root options (option 4) and load temporary image (6) If it hangs on the google or nexus logo you've not wiped the cache.
9. With this second phone I couldn't access it through droid explorer as it was popping up as an MTP device but I could pull the files via command prompt or through the toolkit
10. If you have any use of the touchscreen at all you can run the following command which will then mean that any touch will unlock the device
adb shell rm /data/system/gesture.key11. You can activate bluetooth via adb if you have a mouse or keyboard available but you will need to be able to press okay on the screen
12. Any changes you make in the unstable android image such as lockscreen, bluetooth, enabling debugging, etc will remain in place when you restart the device.
13. You can relock the bootloader if you wish via the toolkit. You just need to be in recovery mode first.
Hope this simplifies the process
Click to expand...
Click to collapse
Please HELP, i can get to step 5...but then, when I try to use ADB via cmd (ie. adb shell), it says "error: device offline". what can it be? I don't know if this is a driver related issue (i've tried the toolkit drivers and the SDK drivers)...i'm desperated, I can't access the phone!!
Thanks in advance
not working for me
i'm in same boat with cracked screen. i can get CWM installed but i cant enabled usb debugging without touching the screen so i cant get adb working. how did you turn on usb debugging without the screen
Thanks for the guide.
Im curious on why youd want to boot an unstable(temporary) image after pulling the files using ADB in CWM recovery. Why not just wipe cache and reboot normally into Android ?
usb debugging without screen?
compsmart said:
i'm in same boat with cracked screen. i can get CWM installed but i cant enabled usb debugging without touching the screen so i cant get adb working. how did you turn on usb debugging without the screen
Click to expand...
Click to collapse
Can someone please walk me through how to do this? My screen is completely broken, but I can still turn on/off, I have reason to believe debugging is off because when I connect the phone (a Samsung galaxy sII skyrocket) to my Toshiba laptop via a micro USB, it makes a sound to signal that it's connected. Drives E and F then open up (but are empty) and then disappear. I have no idea what's going on but I absolutely cannot lose all of the data on this phone. Pictures and videos from my old blackberry Torch are on here too, making up about 4 years of my daughter's life that I would lose if I cannot retrieve. Also, I am not super -tech savvy, so if someone could help me I would be forever grateful.
Please!!
:crying:
almost the same issue
I have an Asus memo pad 10 (smart) some of the core apps have been corrupted, (keyboard, UI, launcher etc all the essential stuff) I've been trying to reinstall my UI and launcher from my computer when i found out that USB debugging was disabled. the tablet is basically unusable, i have no way of enabling from the tablet itself. is there a piece of script or something i could run from my PC to enable it?
any help would be greatly appreciated :crying:
bob mc bob said:
I have an Asus memo pad 10 (smart) some of the core apps have been corrupted, (keyboard, UI, launcher etc all the essential stuff) I've been trying to reinstall my UI and launcher from my computer when i found out that USB debugging was disabled. the tablet is basically unusable, i have no way of enabling from the tablet itself. is there a piece of script or something i could run from my PC to enable it?
any help would be greatly appreciated :crying:
Click to expand...
Click to collapse
My screen became unresponsive a while back. I ended up getting and OTG cable and plugging in a mouse. This allowed me to do everything as if the touchscreen was working. There's also an app called MyMobiler that let me plug in my device over USB and control my screen from my PC. Those two helped me enable USB Debugging, flash a custom ROM, root the phone, backup everything I needed, then restore the phone to stock. I hope this helps.
*Sorry for bumping such an old post*
Thanks for the really useful guide!
Could you or someone just confirm to me that unlocking the bootloader does not factory reset? The reason I'm doing this process is to access my personal data so it's important that I can keep it all.
I ask because at the unlock bootloader stage it implicitly warns me that there'll be a factory reset.
Thanks again!
HikerMan said:
*Sorry for bumping such an old post*
Thanks for the really useful guide!
Could you or someone just confirm to me that unlocking the bootloader does not factory reset? The reason I'm doing this process is to access my personal data so it's important that I can keep it all.
I ask because at the unlock bootloader stage it implicitly warns me that there'll be a factory reset.
Thanks again!
Click to expand...
Click to collapse
Unlocking to bootloader will wipe your device
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Unlocking to bootloader will wipe your device
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
In that case, I am confused as to how OP managed to unlock his bootloader. He actually states that the purpose of this was to retrieve data, like me.
Also, in a previous comment in this thread by jw95275, they claim that "it appears fastboot oem unlock on the Nexus 4 *does not* wipe data".
I am concerned about the conflicting answers so far, so will hold off for an explanation before I do anything. Thanks for the response!
HikerMan said:
In that case, I am confused as to how OP managed to unlock his bootloader. He actually states that the purpose of this was to retrieve data, like me.
Also, in a previous comment in this thread by jw95275, they claim that "it appears fastboot oem unlock on the Nexus 4 *does not* wipe data".
I am concerned about the conflicting answers so far, so will hold off for an explanation before I do anything. Thanks for the response!
Click to expand...
Click to collapse
You should just be able to "fastboot boot recovery.img" and boot CWM and then use ADB. W/O unlocking the BL
npjohnson said:
You should just be able to "fastboot boot recovery.img" and boot CWM and then use ADB. W/O unlocking the BL
Click to expand...
Click to collapse
This did not work for me. I have a Nexus 4 with a broken digitizer, locked bootloader, and usb debugging disabled. I need to grab some data off.
I've tried `fastboot flash recovery {{recovery .img}}` and `fastboot boot {{recovery .img}}` without unlocking the bootloader first, and via both methods, I get back "FAILED (remote: not supported in locked device)"
So I'm not sure how people are able to get into custom recovery without first unlocking BL/losing all their data. Can someone explain?
jinglejuice said:
This did not work for me. I have a Nexus 4 with a broken digitizer, locked bootloader, and usb debugging disabled. I need to grab some data off.
I've tried `fastboot flash recovery {{recovery .img}}` and `fastboot boot {{recovery .img}}` without unlocking the bootloader first, and via both methods, I get back "FAILED (remote: not supported in locked device)"
So I'm not sure how people are able to get into custom recovery without first unlocking BL/losing all their data. Can someone explain?
Click to expand...
Click to collapse
On some (few) Motorola devices (not nexus 4), you can fastboot boot without unlocking the BL.
Hi, I have a S4 i9505 with a problem, screen broken and no display at all + usb debugging is disabled.
Phone: Not rooted, original software, usb debugging disabled, no display at all
What I want to achieve: restore all my photos / videos on the phone memory, no sd card
What I have attempted:
installed ADB & fastboot based on instructions from http://forum.xda-developers.com/showthread.php?t=2786395
What I need help with:
- When i try to get into recovery mode, i wasn't sure if i am indeed in there since i can't see anything, but in total there's a vibration when i turn on the phone, and another vibration when i release the power up+power+home after pressing them down for about 5 seconds.
- When in command prompt I type adb devices and there was none, and when i type adb shell it says error: device not found
I have ensured all drivers for my phone are installed (even with PdaNetA4180 & UniversalAdbDriverSetup6 from cynanogen) but the error remains. refer to attached image.
I have done extensive search on the forum but still couldn't find any ways to get usb debugging enabled on my crippled phone.
Any step by step guide would really be helpful! Thanks
Ps. Main problem = device not found in adb , usb debugging disabled, screen no display/cracked
What do you want? To recover files? To my knowledge that is not possible.
You would first need to flash a custom recovery for adb to work in recovery.
Then you would need to allow the connection on your device (which you can't do).
Yes I need to recover photos only. Nothing else.
Please kindly guide the steps on how to flash a custom recovery (w/o control of the phone's display or touch)
Thanks.
Your device is shown connected in windows
Why not use the mtp protocol and copy whatever you want
Hi, in the beginning, my phone is locked with a pattern pin.
I read the tutorials and managed to get away with the pattern pin by resetting my phone to factory settings via recovery mode i guess by watching youtube guide.
I didn't knew the photos and all will get deleted off from it, so there's nothing to transfer over when i got MTP working and able to access files inside the phone.
What do you recommend? Would fixing the screen and then using dr fone recovery works? or is there any other way to solve this without getting the phone display fixed? Thanks.
If the photos are deleted by the factory reset then i am sorry to day but you cannot recover them even if you get the screen fixed
bomby481 said:
Hi, in the beginning, my phone is locked with a pattern pin.
I read the tutorials and managed to get away with the pattern pin by resetting my phone to factory settings via recovery mode i guess by watching youtube guide.
I didn't knew the photos and all will get deleted off from it, so there's nothing to transfer over when i got MTP working and able to access files inside the phone.
What do you recommend? Would fixing the screen and then using dr fone recovery works? or is there any other way to solve this without getting the phone display fixed? Thanks.
Click to expand...
Click to collapse
Your photos are gone and there is no way to get them back.
hey guys today i was rooting my nexus player.
everything was smooth until SuperSU didn not show up.
after restarting my NP i got stock in boot loop.
I tried to use adb to access my device but ran into an issue
when i use: adb devices - it shows me empty list of devices.
i think its because i can not detect it because its not actually boot in the rom it self.
does anyone know how to fix this?
things i tied:
updating drivers
using adb devices
unplugging power cord and pluging back in
using different usb cables
-- I downloaded SkipSoft tool not really sure how to use it yet or what i exactly need from it.
did anyone use it?
any help would be very appreciated
thank you.
UPDATE:
i managed to get into a stock recovery mode
fastboot is offline.
I think its because the USB debugging is not enabled. is there a way to avoid this?
Did you solve your issue? I also have bootloop and can't access fastboot.
if you saved your old stick rom you should be able to reset it. i think you have to hold power button. this willl allow you to get into settings and pick what file to boot from. sorry it was a while ago when i did this. but if you haven't saved your stick boot than you might be out of options.
eried1 said:
Did you solve your issue? I also have bootloop and can't access fastboot.
Click to expand...
Click to collapse
TotalONE said:
if you saved your old stick rom you should be able to reset it. i think you have to hold power button. this willl allow you to get into settings and pick what file to boot from. sorry it was a while ago when i did this. but if you haven't saved your stick boot than you might be out of options.
Click to expand...
Click to collapse
Tried it and it didn't work. Resetting will just wipe user settings. I believe this to be system related.
I have a Verizon Note 3 running Android 5.0, non-rooted (never had luck getting it rooted). As far as I know, the bootloader is locked. Here is all the information that I thought might be pertinent:
Model #: SM-N900V
Baseband version: N900VVRUEOF1
Android version: 5.0
Kernel version: 3.4.0
Build number: LRX21V.N900VVRUEOF1
Although I work in IT and am fairly comfortable with this sort of stuff, I have almost no experience when it comes to working with Android development / phones, etc.
The phone does not have a valid SIM card, nor do I have service for it. I use it just as a WiFi device and I don't care if it ever works for phone/SMS/MMS again. That being said, I would really like to be able to (a) root the phone and (b) load the Resurrection firmware that I've read about that would allow me to run Marshmallow.
Is there someone who is willing to take me "under their wing," so to speak, and take me through what I need to do, step by step, to make this happen. I've read several posts, but they all assume a prior level of knowledge that I just don't possess. I'm confident that I could do this if I have a clear list of instructions and and understanding of what steps I need to follow to do this. Thanks in advance to anyone who could give me a hand.
Same problem here. Would appreciate help
Alright,
*First thing you need to do is enable USB debugging:
How?
On your phone Navigate to Settings > About Phone > scroll to the bottom > tap Build number seven (7) times. You'll get a short pop-up in the lower area of your display saying that you're now a developer. Then Go back (to the settings menu) and now access the Developer options menu, check ‘USB debugging’ and click OK on the prompt.
------------------------------------
(DONT plug your phone to your PC yet)
Download USB Drivers and Install.
------------------------------------
*2nd thing to do is Rooting your phone:
Download THIS tool on PC > Run. then plug your phone to PC > Choose Version OF1 > Click Read phone info (Your phone will ask if the program can access your phone press YES on your phone)> Root. wait until its done. now you are Rooted.
------------------------------------
Here is the fun part (Unlocking your bootloader) All through the phone no PC required for this.
You need to use an SDCard for this and
Keep in mind this method ((WILL WIPE YOUR EXTERNAL SD CARD)) So backup your MicroSD or use another one.
* Install Busybox on your phone (you can get it from the Playstore)
* Download Samsung Unlocker N3
1. Install SamsungUnlockerN3.apk
2. Grant SU access
3. Click On Install SamBootloader Unlocker
4. Grant SU access
5. Type Yes Hit enter wait for device to power off. Then pull the battery out > Battery back in then power on the phone.
6. Should be unlocked
Keep in mind this method ((WILL WIPE YOUR EXTERNAL SD CARD))
Thats all. your N3 is rooted and bootloader unlocked
Sczar said:
Alright,
*First thing you need to do is enable USB debugging:
How?
On your phone Navigate to Settings > About Phone > scroll to the bottom > tap Build number seven (7) times. You'll get a short pop-up in the lower area of your display saying that you're now a developer. Then Go back (to the settings menu) and now access the Developer options menu, check ‘USB debugging’ and click OK on the prompt.
------------------------------------
(DONT plug your phone to your PC yet)
Download USB Drivers and Install.
------------------------------------
*2nd thing to do is Rooting your phone:
Download THIS tool on PC > Run. then plug your phone to PC > Choose Version OF1 > Click Read phone info (Your phone will ask if the program can access your phone press YES on your phone)> Root. wait until its done. now you are Rooted.
------------------------------------
Here is the fun part (Unlocking your bootloader) All through the phone no PC required for this.
You need to use an SDCard for this and
Keep in mind this method ((WILL WIPE YOUR EXTERNAL SD CARD)) So backup your MicroSD or use another one.
* Install Busybox on your phone (you can get it from the Playstore)
* Download Samsung Unlocker N3
1. Install SamsungUnlockerN3.apk
2. Grant SU access
3. Click On Install SamBootloader Unlocker
4. Grant SU access
5. Type Yes Hit enter wait for device to power off. Then pull the battery out > Battery back in then power on the phone.
6. Should be unlocked
Keep in mind this method ((WILL WIPE YOUR EXTERNAL SD CARD))
Thats all. your N3 is rooted and bootloader unlocked
Click to expand...
Click to collapse
I tried this root method and all it does is put me in a boot loop.Goes to somethingiin recovery and just stays there until I manually reboot phone then get boot loop.Tried both 1 click versions.
Sent from my LG-D851 using XDA-Developers Legacy app
AtrixHDMan said:
I tried this root method and all it does is put me in a boot loop.Goes to somethingiin recovery and just stays there until I manually reboot phone then get boot loop.Tried both 1 click versions.
Click to expand...
Click to collapse
Try to do a factory reset in recovery mode. It will wipe all your apps and data and restore it to factory settings. The instructions you got from @Sczar are very good , so try again step by step if factor reset doesn't work to get you out of the boot loop.
S2_brickmaker said:
Try to do a factory reset in recovery mode. It will wipe all your apps and data and restore it to factory settings. The instructions you got from @Sczar are very good , so try again step by step if factor reset doesn't work to get you out of the boot loop.
Click to expand...
Click to collapse
I got it figured out.Had to use a different twrp and flash Samsung lollipop 01.
Sent from my LG-D851 using XDA-Developers Legacy app
Very new to this. Have a technical background but confused on the above steps. Completed all listed Note3 connected,odin started on phone, then progress stopped at 28 sec. Waited over an hour then crossed fingers and unplugged phone removed battery and restarted. Luckily it came back up. Any ideas on went wrong with root process? Help!!
Thanks in advance.
Sczar said:
Alright,
*First thing you need to do is enable USB debugging:
How?
On your phone Navigate to Settings > About Phone > scroll to the bottom > tap Build number seven (7) times. You'll get a short pop-up in the lower area of your display saying that you're now a developer. Then Go back (to the settings menu) and now access the Developer options menu, check ‘USB debugging’ and click OK on the prompt.
------------------------------------
(DONT plug your phone to your PC yet)
Download and Install.
------------------------------------
*2nd thing to do is Rooting your phone:
Download tool on PC > Run. then plug your phone to PC > Choose Version OF1 > Click Read phone info (Your phone will ask if the program can access your phone press YES on your phone)> Root. wait until its done. now you are Rooted.
------------------------------------
Here is the fun part (Unlocking your bootloader) All through the phone no PC required for this.
You need to use an SDCard for this and
Keep in mind this method ((WILL WIPE YOUR EXTERNAL SD CARD)) So backup your MicroSD or use another one.
* Install Busybox on your phone (you can get it from the Playstore)
* Download
1. Install SamsungUnlockerN3.apk
2. Grant SU access
3. Click On Install SamBootloader Unlocker
4. Grant SU access
5. Type Yes Hit enter wait for device to power off. Then pull the battery out > Battery back in then power on the phone.
6. Should be unlocked
Keep in mind this method ((WILL WIPE YOUR EXTERNAL SD CARD))
Thats all. your N3 is rooted and bootloader unlocked
Click to expand...
Click to collapse
OK, made it to rooted. It came back up the first time while connected to the computer. I shut down to swap sd cards to put in an older one that isnt used and when I start back up all I get is Process System isnt responding in a white box. If I do nothing, the white square asking to quit or wait will disappear, I get the top bar with 4G, bars, battery level, and time, but black screen. If I swipe the screen with my finger, the desktop (for lack of better word) flashes on, then goes all black. In about 3-5 minutes it will restart again. Before it restarts on its own, I can hold the power button and it will give me the power off, restart, etc menu and allow restart.
EDIT: Nevermind... If it warns Process System is not responding, wait for the notification bar to appear, use the power button to get the restart menu and choose restart. Then it starts normally and is Rooted! THANK YOU! I will work on the rest tomorrow!
Oldguy64 said:
Very new to this. Have a technical background but confused on the above steps. Completed all listed Note3 connected,odin started on phone, then progress stopped at 28 sec. Waited over an hour then crossed fingers and unplugged phone removed battery and restarted. Luckily it came back up. Any ideas on went wrong with root process? Help!!
Thanks in advance.
Click to expand...
Click to collapse
Why are you using Odin?
Sczar said:
Why are you using Odin?
Click to expand...
Click to collapse
It just started, I assume, as a result of running the root program. I downloaded program from the suggested link. I ran it which installed files on my pc and made a desktop shortcut. I double-clicked the shortcut, the program started, I connected the phone via usb, and selected the scan button in the program. It found the phone and I selected install root. I then had a progress bar start in the program and a window opened on the task showing odin 3.10. The phone indicated that odin had started and said it was downloading, however, progress stopped at 28 seconds. Did I do something wrong? I would really like to get this thing rooted so I have control over it.
Thanks immensely for your help.
Oldguy64 said:
It just started, I assume, as a result of running the root program. I downloaded program from the suggested link. I ran it which installed files on my pc and made a desktop shortcut. I double-clicked the shortcut, the program started, I connected the phone via usb, and selected the scan button in the program. It found the phone and I selected install root. I then had a progress bar start in the program and a window opened on the task showing odin 3.10. The phone indicated that odin had started and said it was downloading, however, progress stopped at 28 seconds. Did I do something wrong? I would really like to get this thing rooted so I have control over it.
Thanks immensely for your help.
Click to expand...
Click to collapse
Are you on OF1 baseband and Build?
Sczar said:
Are you on OF1 baseband and Build?
Click to expand...
Click to collapse
Yes on both accounts. Because I had no intent to flash a new ROM and only wanted to root I did not have an SD card in the phone. Could this be affecting the process?
Oldguy64 said:
Yes on both accounts. Because I had no intent to flash a new ROM and only wanted to root I did not have an SD card in the phone. Could this be affecting the process?
Click to expand...
Click to collapse
If you just want to root your phone you only need to run the root program on your pc. You DO NOT use odin. If I'm reading your post correctly you are saying the odin program is starting automatically? That should not happen. SD card should not matter if you just root.
Yes it is starting automatically. Any ideas why. Going to search registry on computer to see if it might be on there. Does Samsung Kies use Odin in any manner. I do have Kies on the computer. Grasping at straws I know. Thanks for the help you folks are great.
Oldguy64 said:
Yes it is starting automatically. Any ideas why. Going to search registry on computer to see if it might be on there. Does Samsung Kies use Odin in any manner. I do have Kies on the computer. Grasping at straws I know. Thanks for the help you folks are great.
Click to expand...
Click to collapse
I have no idea why odin would start on its own. If you would like to, uninstall Odin so you can root your phone without any interference from Odin. Samsung Kies DOES NOT use Odin. Samsung Kies is its own separate program from Odin.
If all you want to do is root the phone follow Sczar post and run the root program again it should only take about 1 minute tops to root phone.
Tried one more time. Stopped in exactly the same place as multiple times before. As far as Odin goes; after downloading the root file and running it, it extracted a number of files and created a directory in my program files directory on my pc. One of the files extracted was Odin.exe. Also the program does not automatically detect my phone or ask me to select OF1. I have to select a scan button and it then populates the fields showing the build. I select install root and all goes good,like I have mentioned until 26 or 27 seconds of progress has occurred the the program stops. My phone shows Odin has started and says it is downloading not to turn off, but nothing ever writes to the phone. I have to get into the task manager on the pc to stop the processes dealing with the root program as it becomes totally unresponsive. I have to kill adb also. I am totally baffled and about ready to give up. Wish I had stayed with Motorola at least that phone I was able to root. I have been holding off the new software update for days but may just let it fly unless someone has any other ideas about why this thing stops. Thanks to those who have tried so far.
Oldguy64 said:
Tried one more time. Stopped in exactly the same place as multiple times before. As far as Odin goes; after downloading the root file and running it, it extracted a number of files and created a directory in my program files directory on my pc. One of the files extracted was Odin.exe. Also the program does not automatically detect my phone or ask me to select OF1. I have to select a scan button and it then populates the fields showing the build. I select install root and all goes good,like I have mentioned until 26 or 27 seconds of progress has occurred the the program stops. My phone shows Odin has started and says it is downloading not to turn off, but nothing ever writes to the phone. I have to get into the task manager on the pc to stop the processes dealing with the root program as it becomes totally unresponsive. I have to kill adb also. I am totally baffled and about ready to give up. Wish I had stayed with Motorola at least that phone I was able to root. I have been holding off the new software update for days but may just let it fly unless someone has any other ideas about why this thing stops. Thanks to those who have tried so far.
Click to expand...
Click to collapse
I'm starting to figure out what you are saying is going on (I think).
1. Forget about Odin you do not use it, at all for root.
2. If I'm right your "phone" is going into DOWNLOAD MODE automatically that is what it should do.That is not Odin running. That's how your phone programs itself.
Quick checks
1.Make sure you have latest drivers from Samsung installed.
2. check USB debugging is on.
3. Install Arabic Tool For rooting on PC.
http://www.mediafire.com/?pvm1reerboz2c25
4. Open Arabic tool,
5. plug phone into PC make sure you connect as MTP not installer mode.
6. Click on Version, select OF1 (make sure your firmware is running on OF1)
7. Click Read Phone Info. (Your phone info should fill in the blanks)
8. HIT ROOT.
Your phone should go into "Download Mode" not Odin (a little green dude should be on the screen) automatically. Let the program do its thing. Then it will reboot your phone automatically, and if everything goes correctly it should say your rooted!.
9. It should take about 1 or 2 minutes to complete.
10. If it doesn't work try it again. It took me 2 tries for it to work right.
Everytime I've tried rooting my SM N900V with this Yemen tool I get hard bricked. To fix that issue I just put phone in odin mode and flash the OF1 firmware and everything is back to normal but still no root. Any suggestions?
mdj8606 said:
Everytime I've tried rooting my SM N900V with this Yemen tool I get hard bricked. To fix that issue I just put phone in odin mode and flash the OF1 firmware and everything is back to normal but still no root. Any suggestions?
Click to expand...
Click to collapse
Try the Arabic tool I posted above ^^^. I rooted my phone 3 times with no problems. I've not used the Yemen root method.
I made it to root, but the bootloader is not replacing so I am evidently missing an obvious step.
Samsung Note 3 SM-N900V 0F1 firmware
1. Install SamsungUnlockerN3.apk
2. Grant SU access (How do I do this? It is not asking anything)
3. Click On Install SamBootloader Unlocker
4. Grant SU access (Again, how do I do this? It is not asking anything)
5. Type Yes Hit enter wait for device to power off. Then pull the battery out > Battery back in then power on the phone.
6. Should be unlocked
It says it works, it shuts down and I remove the battery, and I reboot. However, as soon as I install TWRP and allow it to reboot I get the unauthorized software message from Verizon, use Kies to save, use Odin to reflash 0F1, root again, and now what? Why is the actual bootloader not being installed? How do I enable superuser?
I'll be making a video for this with the 7 inch tablet on Nov. 29th or 30th (depending on the time I have)
General Disclaimer: I'm not responsible if you brick your tablet. This is how I did it personally as other methods here didn't work for me. I have yet to test this method on a 7 inch, also do not have access to the Surf variants. This has only been tested on the 10.1 inch with the keyboard. Will update when I test with the 7 inch.
What's Needed:
MTK Fastboot Drivers: https://online.mediatek.com/Public Documents/MTK_Android_USB_Driver.zip
Magisk Manager Canary: https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
Stock Boot Image: https://forum.xda-developers.com/wa...eral/stock-stock-backups-images-otas-t3998227
ADB and Fastboot: https://www.xda-developers.com/what-is-adb/
Prerequisites:
Personally, I had issues getting my PC to recognize the tablets in Fastboot mode. The drivers wouldn't install. This might be optional for some of you, but I thought I'd include it just in case.
Installing MTK Fastboot Drivers from the link above
If you plugin your device in fastboot mode and your PC doesn't recognize it, follow these steps. If it did, skip this part.
1.) Download the drivers above and unzip the Zip file somewhere on your PC (desktop or My Documents is easiest)
2.) Boot your Tablet into Fastboot Mode by holding Vol + and Power, then select Fastboot from the Menu
*NOTE* There is a bug with these tablet's that the volume buttons are mislabeled. Really dumb, but I guess that's why they were 55 bucks for the 10 inch on black friday
3.) Plug the device into your PC and open Device Manager by pressing WinKey+R and typing devmgmt.msc, hit Enter
4.) If there's an Other Device listed called Android, follow these steps. If it isn't there, follow the next set of steps
5.) Open a Command Prompt window as Admin and type the following command
Code:
bcdedit.exe /set nointegritychecks on
6.) Hit enter, then restart your PC
7.) Once the PC is restarted, make sure your tablet is connected in Fastboot mode and open Device Manager again
8.) Right click Android under Other Devices and select Update Drivers
9.) Click the Browse my Computer for driver software button and select the MTK Folder you extracted from the download link above
10.) From there, you can open command prompt, type fastboot devices and see if your tablet shows up and move on to root!
Unlocking your Bootloader
From here, you can unlock your bootloader very easily to Root your device
This will wipe all data off the tablet!
0.) Enable OEM Unlock and USB Debugging on the tablet by going to Settings->About and tap Build Number 7 times. From here, enter the new Developer Options that unlock and turn on OEM Unlock and USB Debugging.
1.) Boot your tablet into Fastboot mode and connect it to your PC
2.) Open a Command Prompt window and type the following command, then hit enter
Code:
fastboot flashing unlock
3.) Follow the instructions on screen to unlock your bootloader
4.) Now Boot your device and we'll move on to making a rooted Boot Image
Creating a Rooted Boot Image with Magisk Manager
0.) Make sure you already have Wifi setup and connected before the first time you open Magisk Manager on your device! Make sure it auto connects as well
1.) Download Magisk Manager Canary from the link above
2.) Install it to your device
3.) Download boot Image from the Stock Boot Image part of the Prerequisites above and put the boot.img on your devices internal memory
4.) Open Magisk Manager and select Install Magisk
5.) Select Patch File and select the boot.img from your internal storage
6.) Once its done patching the image, take magisk_patched.img from the downloads folder of your device and move it onto your PC
7.) Boot your tablet into Fastboot mode and plug it into your PC
8.) Open Command Prompt and type the following command and hit enter (make sure you know your magisk_patched.img file location)
Code:
fastboot flash boot magisk_patched.img
9.) Reboot the device and you'll be Rooted!
Optional Steps like Modules and Debloating
My basic debloat script: https://forum.xda-developers.com/wa...s-general/root-walmart-bloat-remover-t4011639
Will be testing GSI roms on the spare 7 inch and will list those here
Recommended Magisk Modules:
Viper4Android Legacy
FDE.AI
MagiskHide Props Config
Systemless Hosts
Youtube Vanced Black
Magisk Setting to Enable:
Magisk Hide
Rename Magisk Manager App (keeps app from detecting magisk root)
Credits:
Myself for this root method @byproxy for reminding me to add the steps for OEM Unlock and enabling wifi before opening Magisk Manager for the first time
I'll start this off saying i'm an amateur at this, but I cannot for the life of me get an option to show up in magisk to patch the boot image even though it's on my 7" tablet. Any thoughts?
The bootloader was unlocked and it was successful so that's not the issue.
Are you online? I had the same problem.
Xavster2 said:
I'll start this off saying i'm an amateur at this, but I cannot for the life of me get an option to show up in magisk to patch the boot image even though it's on my 7" tablet. Any thoughts?
The bootloader was unlocked and it was successful so that's not the issue.
Click to expand...
Click to collapse
Xavster2 said:
I'll start this off saying i'm an amateur at this, but I cannot for the life of me get an option to show up in magisk to patch the boot image even though it's on my 7" tablet. Any thoughts?
The bootloader was unlocked and it was successful so that's not the issue.
Click to expand...
Click to collapse
Sorry, been a busy few days, but make sure you're connected to Wifi, close Magisk Manager, then reopen it and you'll be good to go!
Onn 8" walmart tablet
I purchased the 8" Onn walmart tablet second hand from a store called dirt cheap. Box didnt look to be opened but it had been. The tablet had been setup with someones gmail account that i do not know. The tablet was for a 4yo girl to use to learn preschool. Is there just any simple way to remove this google FRP lock ? I dont care if i lose the info on it as its not mine. I just want her to be able to use the tablet. Any help would be much appreciated please
CoachDad said:
I purchased the 8" Onn walmart tablet second hand from a store called dirt cheap. Box didnt look to be opened but it had been. The tablet had been setup with someones gmail account that i do not know. The tablet was for a 4yo girl to use to learn preschool. Is there just any simple way to remove this google FRP lock ? I dont care if i lose the info on it as its not mine. I just want her to be able to use the tablet. Any help would be much appreciated please
Click to expand...
Click to collapse
Forced factory reset should do it. There is small pin hole near the power button. I believe pressing this hidden button(with a Sim card ejector, or paper clip).
If pressing does not do anything. Maybe press the button then hold power button too
mrmazak said:
Forced factory reset should do it. There is small pin hole near the power button. I believe pressing this hidden button(with a Sim card ejector, or paper clip).
If pressing does not do anything. Maybe press the button then hold power button too
Click to expand...
Click to collapse
Thank you for responding so fast. I've boot into recovery mode /wiped everything...its back to factory. The pinhole reset button does nothing other than reboot it . Ive tried all combos to with the reset button but nothing. Also i've read that its possible to use odin? if i can get it into download mode.
Ive downloaded the stock rom posted on an sdcard wondering if i can possibly update in recovery mode? Im sorta a newb at this stuff. I've been reading for 4 days on this matter. I've practiced a root on an old tablet with success. I guess at this point unless i can sell it as is giving the customer that it has this frp lock on it. If the know how to fix it so be it. Im not sure there is a working solution for frp bypass on these tablets.
CoachDad said:
Thank you for responding so fast. I've boot into recovery mode /wiped everything...its back to factory. The pinhole reset button does nothing other than reboot it . Ive tried all combos to with the reset button but nothing. Also i've read that its possible to use odin? if i can get it into download mode.
Ive downloaded the stock rom posted on an sdcard wondering if i can possibly update in recovery mode? Im sorta a newb at this stuff. I've been reading for 4 days on this matter. I've practiced a root on an old tablet with success. I guess at this point unless i can sell it as is giving the customer that it has this frp lock on it. If the know how to fix it so be it. Im not sure there is a working solution for frp bypass on these tablets.
Click to expand...
Click to collapse
This is an mtk device not Samsung. So there is no Odin or download mode. There is spflash tool, and preloader.
And if you flash firmware (with default frp partition) then frp lock is cleared.
But you will have to find that file. It maybe in the stock firmwares that are shared, I do not know.
EDIT:
i was having issues but figure it out. maybe it should be so common knowledge that it shouldn't need to be included as a step, but since i don't do this THAT often i didn't think about it and it took me a bit to figure out why i was having issues.
once you get your computer to recognize your device (mine did without needing to mess with any drivers) you need to first make sure to got into the tablet settings -> about and then tap on the build number 7 times to access developer options. then you need to go into developer options and turn on OEM Unlocking & USB Debugging.
THEN follow the guide to unlock bootloader.
then (since the tablet is factory reset once you unlock) do the above AGAIN to turn USB Debugging back on after you reboot.
also note that you need to have an internet connection on the tablet to utilize magisk. once you got all that square, then continue on with steps for full root.
hope that helps!
byproxy said:
EDIT:
i was having issues but figure it out. maybe it should be so common knowledge that it shouldn't need to be included as a step, but since i don't do this THAT often i didn't think about it and it took me a bit to figure out why i was having issues.
once you get your computer to recognize your device (mine did without needing to mess with any drivers) you need to first make sure to got into the tablet settings -> about and then tap on the build number 7 times to access developer options. then you need to go into developer options and turn on OEM Unlocking & USB Debugging.
THEN follow the guide to unlock bootloader.
then (since the tablet is factory reset once you unlock) do the above AGAIN to turn USB Debugging back on after you reboot.
also note that you need to have an internet connection on the tablet to utilize magisk. once you got all that square, then continue on with steps for full root.
hope that helps!
Click to expand...
Click to collapse
I did not realize I didn't include that step. Total noob mistake when typing a tutorial up for android. I do this almost daily at work, so I forget to include it
CoachDad said:
Thank you for responding so fast. I've boot into recovery mode /wiped everything...its back to factory. The pinhole reset button does nothing other than reboot it . Ive tried all combos to with the reset button but nothing. Also i've read that its possible to use odin? if i can get it into download mode.
Ive downloaded the stock rom posted on an sdcard wondering if i can possibly update in recovery mode? Im sorta a newb at this stuff. I've been reading for 4 days on this matter. I've practiced a root on an old tablet with success. I guess at this point unless i can sell it as is giving the customer that it has this frp lock on it. If the know how to fix it so be it. Im not sure there is a working solution for frp bypass on these tablets.
Click to expand...
Click to collapse
I was able to remove FRP lock on one of mine by flashing the stock rom with SP Flash Tool. I used the full wipe and download selection with every partition selected including boot.
no worries! i didn't think about it either until i was having issues. thanks for the tutorial... it was super helpful!! btw it definitely works on the 8" tablet.
Hello! I'm new to all of this, but what I'm trying to accomplish is removing the Google account from this tablet and putting a new image on the ONA19TB002, ONA19TB003, ONA19TB007, Surf 7 and 10 tablets. I followed all of the steps as far as installing the drivers. I had to go through hoops to get the MediaTek Drivers installed, but I have a "warning" cone by it. I haven't been able to find any resolution to this. Any help would be appreciated. I' have a Windows 10 64-bit system that I'm using and the tablet I'm specifically working on at the moment is the ONN ONA19TB003 tablet. The tablet is not being recognized by my laptop when I run the 'fastboot devices' command in PowerShell. Is there something that I'm missing? Any help would be appreciated.
'Quis said:
Hello! I'm new to all of this, but what I'm trying to accomplish is removing the Google account from this tablet and putting a new image on the ONA19TB002, ONA19TB003, ONA19TB007, Surf 7 and 10 tablets. I followed all of the steps as far as installing the drivers. I had to go through hoops to get the MediaTek Drivers installed, but I have a "warning" cone by it. I haven't been able to find any resolution to this. Any help would be appreciated. I' have a Windows 10 64-bit system that I'm using and the tablet I'm specifically working on at the moment is the ONN ONA19TB003 tablet. The tablet is not being recognized by my laptop when I run the 'fastboot devices' command in PowerShell. Is there something that I'm missing? Any help would be appreciated.
Click to expand...
Click to collapse
Personally, I avoid PowerShell at all costs. This kinda stuff has always just seemed to work better with CMD.exe instead of Powershell.
These tablets are kind of a nightmare for this. If you've done the mediatek drivers and still have the warning cone icon, I'm not sure what's next as I haven't hit that wall myself. All I can maybe recommend is right click delete drivers in Device Manager, then start over with the driver install
Removing the Google Account would be needing a FRP Bypass. Someone above stated "I was able to remove FRP lock on one of mine by flashing the stock rom with SP Flash Tool. I used the full wipe and download selection with every partition selected including boot. " so if you can get it recognized, try that
KaptinBoxxi said:
Personally, I avoid PowerShell at all costs. This kinda stuff has always just seemed to work better with CMD.exe instead of Powershell.
These tablets are kind of a nightmare for this. If you've done the mediatek drivers and still have the warning cone icon, I'm not sure what's next as I haven't hit that wall myself. All I can maybe recommend is right click delete drivers in Device Manager, then start over with the driver install
Removing the Google Account would be needing a FRP Bypass. Someone above stated "I was able to remove FRP lock on one of mine by flashing the stock rom with SP Flash Tool. I used the full wipe and download selection with every partition selected including boot. " so if you can get it recognized, try that
Click to expand...
Click to collapse
Ok, thank you! This is a shot in the dark, but in order for ADB to work, USB debugging has to be enabled. I can't do that as the tablet is locked by FRP and I have looked countless times on Google and MSN to see if it's possible. Do you have any tips for that?
I don't know what I'm doing wrong, but for some reason I can't seem to get. The tablet to stay in fastboot mode. It just says waiting for device.
will this root onn 8 inch tablet running android 9
soateufel said:
I don't know what I'm doing wrong, but for some reason I can't seem to get. The tablet to stay in fastboot mode. It just says waiting for device.
Click to expand...
Click to collapse
Sorry for late reply. Been away from home with work. When fastboot mode indicates "waiting for device," it generally means that your device is not properly communicating with your PC or laptop. This is nearly always due to missing or incorrect drivers 9n your computer. There are several comprehensive guides here on XDA for installing necessary ADB & Fastboot drivers.
installed magisk manager on onn 8 and also have img zip but win i go to patch it magisk manager crashes
when you mean patch boot img do mean to unzip file on onn 8