Related
Hi guys,,, just bought myself a X10i to play with,,, figured I,ve flash the thing with a rom from the developers forum,
This is where I came unstuck,,,, cant for the life of me get it into flash mode.
Instructions were as follows
1 With fone OFF. Hold down back button and insert usb cable, green light comes on and hit enter. What bloody enter, on the fone or on your keyboard. I,ve tried both, fone just keeps on booting into the main screen, nothing even resembles a flash mode screen. Tried this untill my thumb nearly bled.
Someone help please.
Read the tuts in the dev forum. P.S. no custom roms yet but there is root.
TrevvyD said:
Hi guys,,, just bought myself a X10i to play with,,, figured I,ve flash the thing with a rom from the developers forum,
This is where I came unstuck,,,, cant for the life of me get it into flash mode.
Instructions were as follows
1 With fone OFF. Hold down back button and insert usb cable, green light comes on and hit enter. What bloody enter, on the fone or on your keyboard. I,ve tried both, fone just keeps on booting into the main screen, nothing even resembles a flash mode screen. Tried this untill my thumb nearly bled.
Someone help please.
Click to expand...
Click to collapse
Try hold down "back button" without battery then insert USB cable and then insert battery.
When it says to hit enter, that is to continue from the screen (on the PC) that says "press any key to continue" when you are doing the steps for rooting. If you don't have that window ready the phone will only stay in flash mode for about 5 seconds and then it will continue to boot. So, just make sure you are ready with the PC before entering flash mode.
Dr_Wolodya said:
Try hold down "back button" without battery then insert USB cable and then insert battery.
Click to expand...
Click to collapse
thanks!!
this really helps!
My phone is also x10i.I have trouble to enter in flash mode.It shows up the green LED but flash tool says it occurs error and plug your phone in flash mode.
What should I do?Help me , plz.
johnmin said:
My phone is also x10i.I have trouble to enter in flash mode.It shows up the green LED but flash tool says it occurs error and plug your phone in flash mode.
What should I do?Help me , plz.
Click to expand...
Click to collapse
check drivers (install SE PC suite and let it atleast detect the phone once in FLASH mode)...
also it might help to disable any antivirus (worked for me)
cannot enter the flash mode
Hi,
I know this post is pretty old, but still I'm struglig the second day now to get into flash mode and still no luck despite trying every method there is on the web.
I've got Xperia X10i mini pro, reinstalled standard ROM with PC companion just to make sure it's nothing with the software or any modifications I made to it.
I'm guiding myself with instruction given here:
wiki.cyanogenmod.com/wiki/Sony_Ericsson_Xperia_Mini_Pro:_Full_Update_Guide
in order to get my bootloader unlocked
what I've done so far:
-installed Android SDK incl. SDK Tools, SDK Platform-tools, Google USB driver package. Not installed any API from SDK.
-put android_winusb.inf (18 KB size) in C:\android-sdk-windows\extras\google\usb_driver
-in general- everyting given here: wiki.cyanogenmod.com/wiki/Howto:_Install_the_Android_SDK#Windows
command
Code:
adb devices
rerurns
Code:
List of devices attached
43423531315537465737 device
in my opinion meaning it works as it should.
So I turn the phone off, unplug the cable both from computer and the phone, take the abttery out, plug both end of USB cable where these should be, hold the Back button (tried with Volume up too) and put the battery in.
The result is it only goes into flash mode for several seconds (confirmed by SuperOneClisk log) and then goes into charging mode. nothing gets displayed on the screen. Only when PC Companion is on it detects it, than looses it and pops up with a window on how to properly connect the device... :/
So can someone please tell me what I do wrong?
Why it doesn't stay in flash mode?
PS. when I enter *#*#7378423#*#* to access the service menu, after pressing the last * the numbers just disappear and nothing happens...
Pls help
Edit:
I somehow got around that with s1tool and Flashtool. But eventually I could not go along the way given at cyanogenmod.com and unlocked with the help of this: http://forum.xda-developers.com/showthread.php?t=1254225
So apparently, I went home and usually put my phone into my desk.
While I took it from my pocket, I noticed the hardware buttons were lit but no display, I removed the battery to restart, during the week, frozen screen were occurring a dozen times when playing Clash, that though I didn't mind I just said to myself I will reflash the rom in the weekend.
But up to now,
It won't turn on, recovery mode or anything also doesn't work
It wont charge
Tried a new battery but still no luck
I think PC reads it but SPFT wont
Any suggestion on how I can revive my phone?
Attached is the error I get from SPFT
I don't own the A120 anymore. That is almost similar to this, as you might know.
Anyway, as nobody has answered your question, I will try to help as much as I can.
Does it give you a haptic feedback(vibration) when you try to power on the device?
Are you saying that it won't turn on completely?
If it is being detected on the computer and not on SPFT, you might want to check with the drivers you have. Do you have the MTK VCOM drivers installed? (I'm not really sure about the name, but it was something like that).
And try flashing the Stock ROM with SPFT with your battery removed from the phone.
Download the drivers.
Connect your phone without the battery and keep your device manager open, if it shows a device with a yellow exclamation mark beside it, right click and click on properties. You will have to do this quickly.
Once that is done, go to driver tab on the properties window. Select Update Driver. Browse my computer and enter the location of your downloaded and unzipped drivers.
(You might get a digital signature error or something similar. I'll tell you how to bypass that in the end. If you get that, go to the end, follow those steps and then come back and do all the steps after the downloading part.)
If the drivers are successfully installed, then unplug your device, run the SPFT and load the Scatter file of the Stock ROM.
Now select Download only and start the download, it will wait for you to connect the phone.
Plug in your phone without the battery. This should initialize the download process.
Now wait for the flash to be completed and if it is successful, take out your phone and boot it. If it boots up, congratulations.
If it does not, flash the same ROM the same way another time and check, if it is still not working, try with Firmware upgrade mode, twice. It should work in those tries.
Digital Signature Error bypassing.
I know only one method which works on Windows 8 and above(Tested).
Hold the Shift key while pressing Reboot.(Yes, you have to reboot your PC)
Once there is a blue screen with options, you should see "Troubleshoot". Select that.
Then Advanced Options and then Start Up settings. Then press Restart.
This will show you a menu with a lot of options. Select the option number which says "Disable Driver Signature Enforcement".
This will log you into the PC normally, but now, you can go back and do all the steps again and you won't get an error.
Cheers!
If this still doesn't help you, let me know on what happens so I can try to get you back your phone. Hope this helps.
WalterWh1te said:
I don't own the A120 anymore. That is almost similar to this, as you might know.
Anyway, as nobody has answered your question, I will try to help as much as I can.
Does it give you a haptic feedback(vibration) when you try to power on the device?
Are you saying that it won't turn on completely?
If it is being detected on the computer and not on SPFT, you might want to check with the drivers you have. Do you have the MTK VCOM drivers installed? (I'm not really sure about the name, but it was something like that).
And try flashing the Stock ROM with SPFT with your battery removed from the phone.
Download the drivers.
Connect your phone without the battery and keep your device manager open, if it shows a device with a yellow exclamation mark beside it, right click and click on properties. You will have to do this quickly.
Once that is done, go to driver tab on the properties window. Select Update Driver. Browse my computer and enter the location of your downloaded and unzipped drivers.
(You might get a digital signature error or something similar. I'll tell you how to bypass that in the end. If you get that, go to the end, follow those steps and then come back and do all the steps after the downloading part.)
If the drivers are successfully installed, then unplug your device, run the SPFT and load the Scatter file of the Stock ROM.
Now select Download only and start the download, it will wait for you to connect the phone.
Plug in your phone without the battery. This should initialize the download process.
Now wait for the flash to be completed and if it is successful, take out your phone and boot it. If it boots up, congratulations.
If it does not, flash the same ROM the same way another time and check, if it is still not working, try with Firmware upgrade mode, twice. It should work in those tries.
Digital Signature Error bypassing.
I know only one method which works on Windows 8 and above(Tested).
Hold the Shift key while pressing Reboot.(Yes, you have to reboot your PC)
Once there is a blue screen with options, you should see "Troubleshoot". Select that.
Then Advanced Options and then Start Up settings. Then press Restart.
This will show you a menu with a lot of options. Select the option number which says "Disable Driver Signature Enforcement".
This will log you into the PC normally, but now, you can go back and do all the steps again and you won't get an error.
Cheers!
If this still doesn't help you, let me know on what happens so I can try to get you back your phone. Hope this helps.
Click to expand...
Click to collapse
Thanks bro, but I already gave up and bought a new one because I badly need an android device for my mini accounts in CoC. Haha but I am till trying to revive my Rio during my free time, this has been my phone for 1 1/2 year..
Yes I am aware that Rio is rebranded A120, I also asked from CM12.1 and AOSP LP Wiko Rainbow threads and some suggested help. Tried all that but still same errors.
No, there's no response of any kind including vibration when turning on. Hmn, as per the drivers, I've been using Tinno Driver since the jelly bean era of this phone, no problems or whatsoever from jb to kk to lp using that driver, so I thought there would be no problems. Still no luck in getting success. Using different versions of SPFT, using sp flashable Rio jb, kk, MMX A120 jb, kk, Wiko kk,lp stock roms, still no luck. Tried every port and cord. And I am using the Win7 64bit, I also resorted to MTK drivers, both the preloader and Da. Still.. No luck. Haha. I also tried, download only, format all+download, and firmware upgrade option with every possible combination from above but no success..
Thanks for your answer btw!
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?
In trying to root it, I downgraded to H990DS10b_00_open_ame_ds_op_1103 via Uppercut. From there I followed carefully the "dirty Santa comes for the H990" thread. I got through to the "untrusted app" message, but I did not get the bat.2 on the cmd window. So I had to restart the phone, and the screen was weird and unreadable. By coincidence Uppercut was not working, giving "error reading from file" on my Windows machine. So from here I did the mistake and got too impatient. At that time I could still see the phone via ADB. Then I thought it might be helpful to do a hard reset - which obviously was a big mistake. Now it powers up showing the LG logo, gives the sound and turns into a weird screen. I can make sound from it by pressing the screen, but after some time it reboots into is a black screen saying kernel crash. It says that I can restart by pressing vol down. When I do that, the same happens again. It also says that I can do ram drop using QPST configuration, whatever that means?
Do I have to say goodbye to it, of do I have any hope?
Doesn't sound like a hard brick to me. I would completely restart the rooting process.
What I would do however, is make sure that all the programs (LG UP etc) and DirtySanta files are correct and working.
Things to try:
• Make sure the drivers are installed correctly. You can google for LG USB drivers. Install and restart.
• Make sure LG UP is run as administrator (as a precaution to access devices)
• Hold Vol Up while the device is off and the plug in the usb cable (while the other end is plugged into the machine) - this should get you into Download mode
• Make sure that you are running the "Run Me First" files in Dirty Santa. This is a common mistake that I have made before even when re-rooting for the tenth time.
• Run all the Dirty Santa CMD files as administrator (it can't hurt).
As far as the screen, does it look like white noise? if so, it is a known kernel incompatibility (the stock kernel) with root. Best thing to do, is that when you get to the step that requires you to install TWRP and then reboot using the reboot command in fastboot, is that you actually pull the batter out after installing TWRP and then reboot into recovery using the hardware keys (Vol Down and Power Button, then let go of Power Button and repress it whilest holding Vol Down but ONLY when the LG logo first appears.).
This is just some general troubleshooting, and not in any particular order. Hopefully it is of some help.
Thank you very much. I appreciate Some observations before I move on. Yes, the screen looks like white noise. In download mode - it only shows download mode shortly in an box, and then goes to white noise again. I mave manages to get in touch with it from Windows in fastboot mode, here it gives me a serial number from LGUS996, definitely not my h990DS? Is that normal?
Another thing, right now Uppercut is teasing me. I think I started it from the zip file, so now it is looking for the program in a temp file that I cannot find. I need to find out how to remove that link in windows to move on with LGUP.
henrylar said:
Thank you very much. I appreciate Some observations before I move on. Yes, the screen looks like white noise. In download mode - it only shows download mode shortly in an box, and then goes to white noise again. I mave manages to get in touch with it from Windows in fastboot mode, here it gives me a serial number from LGUS996, definitely not my h990DS? Is that normal?
Another thing, right now Uppercut is teasing me. I think I started it from the zip file, so now it is looking for the program in a temp file that I cannot find. I need to find out how to remove that link in windows to move on with LGUP.
Click to expand...
Click to collapse
Even though there is white noise in download mode, download mode will still function.
I'm not sure about the serial number thing though. Is it a refurb?
Rather copy Uppercut to its own file outside of the .zip and also disable your antivirus just incase while you are running it. Run it as administrator.
Honestly, I would go into Download mode and user Uppercut to flash a completely stock KDZ. Then try the process over again from the start.
I've had this exact issue and it is totally recoverable.
Thank you so much for the help. Because of that I am now back to a working phone. Have installed the old KDZ file, and now it correctly says that I have a H990DS phone again. You were right about antivirus - even if I thought I had disabled it, I had not, and that made the strange message in uppercut. I will try rooting once more - this time I know how more about what to do if it goes wrong.
I have now re-installed the santa files again, and everything goes fine according to the description until the message about installing step 2, that message never comes to the first cmd window, unfortunately. And I have not (yet) dared to start the step 2 bat from a new cmd window. As I read the description, it should give me a message in the first started cmd window, right?
henrylar said:
I have now re-installed the santa files again, and everything goes fine according to the description until the message about installing step 2, that message never comes to the first cmd window, unfortunately. And I have not (yet) dared to start the step 2 bat from a new cmd window. As I read the description, it should give me a message in the first started cmd window, right?
Click to expand...
Click to collapse
Did you do the terminal thing on the phone?Also have you installed and drivers the right way?you definitely skip something
I think you are right, I can just not understand what. I did the terminal thing, yes and no failure messages of any kind, just no messages at the first cmd screen. . The drivers works fine for everything else, so I cannot imagine any problem there.
I have now tried several times to do the procedure. It all goes very well until the point where there should come a message in the runmefirst command window. No message comes, and for this reason I have not dared to go on. It gives all the right messages on the terminal window on the phone until the point where I have to run step2.bat. I have become pretty good at recovering via LGUP, but do any of you have a hint for me? I have disables antivirus, and I run the windows as administrator?
edit: I succeeded, by simply moving on without any messages from the runmefirst. Worked fine. So now I am rooted Thank you very much JL and Mike for the help.
I have a Samsung Galaxy Tab A (2020, SN-T307U) that I got from work. It's an old Doordash tablet that Doordash didn't want back, so I'm trying to reset it and it's driving me crazy. I have followed so many tutorials trying to get this thing to work, I keep getting caught on something.
- Simply factory resetting does not work, gives an error that MDM does not allow it.
- I cannot put in the wrong password 15 times to factory reset, even though I get a warning it just lets me continue trying after 15 fails.
- I cannot enter the bootloader, rebooting to bootloader just reboots to the OS.
- I cannot enter safemode, same as above.
- I cannot enable developer options, so no OEM unlock or USB debugging. Tapping build number gives me an error that the MDM does not allow this option.
The device is recognized by Odin, can I just brick this thing and repartition from scratch? Can someone who knows what they're talking about walk me through that? I'm not really sure what I'm doing here, learning as I go over these last 2 days.
Hello,
I have the same exact same issue, have you been able to unlock it?
Thank you!
I can fix it remotely the last hope
Same Issue here,
Any one had any luck with MDM T307U. Please assist.
rittnerb said:
I have a Samsung Galaxy Tab A (2020, SN-T307U) that I got from work. It's an old Doordash tablet that Doordash didn't want back, so I'm trying to reset it and it's driving me crazy. I have followed so many tutorials trying to get this thing to work, I keep getting caught on something.
- Simply factory resetting does not work, gives an error that MDM does not allow it.
- I cannot put in the wrong password 15 times to factory reset, even though I get a warning it just lets me continue trying after 15 fails.
- I cannot enter the bootloader, rebooting to bootloader just reboots to the OS.
- I cannot enter safemode, same as above.
- I cannot enable developer options, so no OEM unlock or USB debugging. Tapping build number gives me an error that the MDM does not allow this option.
The device is recognized by Odin, can I just brick this thing and repartition from scratch? Can someone who knows what they're talking about walk me through that? I'm not really sure what I'm doing here, learning as I go over these last 2 days.
Click to expand...
Click to collapse
If you look at all of the previous post, it should tell you that no one has found a way to disable an MDM lock. Which is as it should be. Otherwise the lock would be useless.
lewmur said:
If you look at all of the previous post, it should tell you that no one has found a way to disable an MDM lock. Which is as it should be. Otherwise the lock would be useless.
Click to expand...
Click to collapse
That's not true as of today's date. (In the event this post is viewed after this exploit can be successful).
I am not taking credit and perhaps the op has discovered it. Anyway...
I am in Canada and noticed the carriers here stop at BL 8 while the USA has BL 9.
The unit i had was on BL 9 (csc TMB).
This probably works for Canadians on BL 8. I don't recommend flashing to BL 9 as that may affect your service or experience.
ANYWAY! This guide won't explain any prerequisites. They are adb, installing unsigned drivers, and you aren't able to use the device and are the owner
1) if not already, power off device with vol down+power and ensure battery is at least 50%.
2) enter recovery and factory reset. If you're having difficulty entering recovery, plug into your pc and as soon as you hear the audible disconnect, switch to vol up+power. Or jam on all three buttons for dl mode.
If in dl mode you can check firmware version and just flash it with bl, ap, cp and csc (NOT home csc). Use exact current version. Don't worry about userdata if it is USA
3) at welcome, connect wifi and imnediately go back to first screen. Don't use data sim
4) dl samfw app and on misc tab, check driver status and your pc will reboot.
*you must not have secure boot enabled
5) plug phone into pc. In the app, mtp and select youtube. If done right, click the pop up on your phone and navigate to chrome. Should be automatic.
6) search for vnrom frp. Once there download package disabler pro and notification app. They are side by side. Install notification app and set it up so you can swipe quick settings from top of screen.
5) unplug your phone from pc and plug it back in. Should be able to get back to the package app various ways to install it. Before install, turn wifi off. Now run package disabler and when it prompts for device admin, turn wifi on. It'll glitch a bit but should start.
6) locate samsung setup wizard. Don't confuse with the other. It'll have a green icon. Disable it and clear the storage. At bottom left, tap the back arrow and you should be back at final setup.
7) when asked to add samsung account, turn off wifi. Complete setup and don't add any accounts.
8) you should arrive at home screen. Your phone is re-plugged right? Good. Now turn on usb debugging and use the remove knox from the app. Done.
*i think i turned wifi on just before enabling debugging. I forget.
*if you are sloppy... you'll need to start over. You'll see, or already know
*you can do ota (if there still is any) but factory resetting or odin flashing will put you back to managed.
mindlery said:
That's not true as of today's date. (In the event this post is viewed after this exploit can be successful).
I am not taking credit and perhaps the op has discovered it. Anyway...
I am in Canada and noticed the carriers here stop at BL 8 while the USA has BL 9.
The unit i had was on BL 9 (csc TMB).
This probably works for Canadians on BL 8. I don't recommend flashing to BL 9 as that may affect your service or experience.
ANYWAY! This guide won't explain any prerequisites. They are adb, installing unsigned drivers, and you aren't able to use the device and are the owner
1) if not already, power off device with vol down+power and ensure battery is at least 50%.
2) enter recovery and factory reset. If you're having difficulty entering recovery, plug into your pc and as soon as you hear the audible disconnect, switch to vol up+power. Or jam on all three buttons for dl mode.
If in dl mode you can check firmware version and just flash it with bl, ap, cp and csc (NOT home csc). Use exact current version. Don't worry about userdata if it is USA
3) at welcome, connect wifi and imnediately go back to first screen. Don't use data sim
4) dl samfw app and on misc tab, check driver status and your pc will reboot.
*you must not have secure boot enabled
5) plug phone into pc. In the app, mtp and select youtube. If done right, click the pop up on your phone and navigate to chrome. Should be automatic.
6) search for vnrom frp. Once there download package disabler pro and notification app. They are side by side. Install notification app and set it up so you can swipe quick settings from top of screen.
5) unplug your phone from pc and plug it back in. Should be able to get back to the package app various ways to install it. Before install, turn wifi off. Now run package disabler and when it prompts for device admin, turn wifi on. It'll glitch a bit but should start.
6) locate samsung setup wizard. Don't confuse with the other. It'll have a green icon. Disable it and clear the storage. At bottom left, tap the back arrow and you should be back at final setup.
7) when asked to add samsung account, turn off wifi. Complete setup and don't add any accounts.
8) you should arrive at home screen. Your phone is re-plugged right? Good. Now turn on usb debugging and use the remove knox from the app. Done.
*i think i turned wifi on just before enabling debugging. I forget.
*if you are sloppy... you'll need to start over. You'll see, or already know
*you can do ota (if there still is any) but factory resetting or odin flashing will put you back to managed.
Click to expand...
Click to collapse
This method works up to step 7 for me. I can't seem to enable usb debugging before knox kicks in. With or without wifi. I'm experimenting to see if I can get past that step.
How to Remove MDM Control from Android?For anyone suffering from this issue, the following are the steps to bypass Samsung Knox factory reset protection:
First of all, create a password for the device.
Make sure that your device is charged to an 80% or greater charge.
Next, you’ll need to go to Settings and Security Encrypt Device tabs respectively.
Set a PIN/password for your device.
After you have secured your device and it’s gone through. Reboot the device, and when it boots, it will ask you to enter a password in order to access your device to view encrypted data. If you type the wrong password 15-20 times (it depends on your device), it’ll wipe your device of any information and will restart and then appear like you’re registering as a brand new device after a factory reset.
Thats the 2th!!! Try it
Video - Samsung SM-T307U Galaxy Tab A 8.4 2020 Knox Remove || Tab a 8.0 MDM Remove
the Tool from the Video Tutorial is here >> SamFwToolSetup_4.3