Database Develop

[Q] [AT&T][UCKB2]Heimdall One-Click -Total Stock- **now with or without root

So, I would have posted my question in another thread, but it wont let me and tells me to post it here.
I was having problems with Serendipity 7 (freezing up/slow/bad gps), so I decided to try Fasty II and tried the "[AT&T][UCKB2]Heimdall One-Click -Total Stock- **now with or without root" program to get back to a Stock Rooted Froyo build. That worked fine, but now no matter what I try I can't get my phone into download mode.
Is there a different way than the button methods that I've tried and used many times successfully before? I've never tried the ada or whatever. But, I can't seem to connect my phone to my pc anymore.
I have SuperUser, TiBu and Clockwork Mod Recovery on there (although it doesn't seem to work right), so I'm pretty sure it is the rooted version.
Any ideas appreciated, otherwise I guess I'll just use my 2.2, not as bad as I thought it would be.

Only way for me to get on Download Mode is to get it through ADB. That or a Jig
Try downloading the correct drivers and find SDK tools for Android.

If you were on Serendipity 7, your download button combo would be either V+/V- and insert USB for the i897 GB bootloaders, and hold Vol- and Power for the i9000 bootloaders.
As a couple of notes, I generally have better luck getting to download mode from a full power-off state. Also, the Heimdall one-click puts the 3e recovery back in place, so you'll probably need to ODIN/Heimdall a kernel with CWM in order to get around that.

1: from battery charging with cable inserted: press and hold vol+ and vol-, press power
2. from recovery, position the cursor on restart device, plug in usb, press and hold vol-, then hold vol+, then press power
3. remove battery press and hold vol+ and vol-, insert cable, insert battery
4. remove battery, press and hold vol+ and vol-, insert battery, insert cable
5. put phone into usb debugging mode, on the computer type "adb reboot download"
6. use clockwork mod recovery to reboot download mode
7. use custom ROM power option "download mode"
8. use a 301Kohm jig between USB pins 4-5
9. Apply UnBrickable mod to your device, then remove the battery, insert the batteyr, and click the "Download Mode" button on the computer
10. Use UART (619Kohm resistor between USB pins 4-5, D+=RX, D-=TX, 192500bps 8n1 comms), press and hold ENTER while booting, then type USB
11. Use UART, during battery charging, type "reboot download"
Did i forget one?

AdamOutler said:
1: from battery charging with cable inserted: press and hold vol+ and vol-, press power
2. from recovery, position the cursor on restart device, plug in usb, press and hold vol-, then hold vol+, then press power
3. remove battery press and hold vol+ and vol-, insert cable, insert battery
4. remove battery, press and hold vol+ and vol-, insert battery, insert cable
5. put phone into usb debugging mode, on the computer type "adb reboot download"
6. use clockwork mod recovery to reboot download mode
7. use custom ROM power option "download mode"
8. use a 301Kohm jig between USB pins 4-5
9. Apply UnBrickable mod to your device, then remove the battery and click the "Download Mode" button on the computer
10. Use UART (619Kohm resistor between USB pins 4-5, D+=RX, D-=TX, 192500bps 8n1 comms), press and hold ENTER while booting, then type USB
11. Use UART, during battery charging, type "reboot download"
Did i forget one?
Click to expand...
Click to collapse
12. HAMMER SMASHY SMASHY!!! Oh... wait. No, don't do that one.

I did forget one..
13. From a terminal, type "su", then "reboot download"

AdamOutler said:
I did forget one..
13. From a terminal, type "su", then "reboot download"
Click to expand...
Click to collapse
there is also an app in the market called quickboot....

Thank you guys for the suggestions. When i get time today i'll go through the list and try them out. Just realized amazon wont even let me install their apps bc my phone blocks it.

need help, installing ota zip to my nexus 6

Hello guys,
i was following this article, from yahoo, i cannot post it
and reached the point of
The fastboot menu will appear and you should see Start in the top right. Press Volume Up till it changes to Recovery. Press the Power button to select it.
You will see an Android with a red exclamation point icon, press and hold the Power key, then press the Volume up key to show the Recovery Menu.
You will get a new menu. Navigate to apply update from adb and select it by pressing the Power button.
but it says this in the cmd
device <null> NOT attached.
the phone is still connected, what do i do now?
please help

hendyanto said:
Hello guys,
i was following this article, from yahoo, i cannot post it
and reached the point of
The fastboot menu will appear and you should see Start in the top right. Press Volume Up till it changes to Recovery. Press the Power button to select it.
You will see an Android with a red exclamation point icon, press and hold the Power key, then press the Volume up key to show the Recovery Menu.
You will get a new menu. Navigate to apply update from adb and select it by pressing the Power button.
but it says this in the cmd
device <null> NOT attached.
the phone is still connected, what do i do now?
please help
Click to expand...
Click to collapse
Where does it say this and at what point? Your phone is 100% stock then, correct? You set up adb correctly?
We'll need more information than supplied. You should walk us through step by step

hendyanto said:
Hello guys,
i was following this article, from yahoo, i cannot post it
and reached the point of
The fastboot menu will appear and you should see Start in the top right. Press Volume Up till it changes to Recovery. Press the Power button to select it.
You will see an Android with a red exclamation point icon, press and hold the Power key, then press the Volume up key to show the Recovery Menu.
You will get a new menu. Navigate to apply update from adb and select it by pressing the Power button.
but it says this in the cmd
device <null> NOT attached.
the phone is still connected, what do i do now?
please help
Click to expand...
Click to collapse
I was having the exact same problem last night, following the same instructions. I still could not figure out how to sideload the OTA, so I ended up just flashing the update and starting from fresh. Wish I had the answer for you.
Here was my thread asking pretty much the same thing: http://forum.xda-developers.com/nexus-6/help/disconnects-computer-entering-bootloader-t3230705

danarama said:
Where does it say this and at what point? Your phone is 100% stock then, correct? You set up adb correctly?
We'll need more information than supplied. You should walk us through step by step
Click to expand...
Click to collapse
100% Stock, yes! 1 week old.
Yes i have set up ADB
I have followed the instruction until this part (i cannot post any link sorry, not authorized by xda)
The following ADB commands are for Windows machines. If you’re using a Mac, just add “./” before each command, for example: “./adb reboot bootloader”.
Assuming you device is already connected to your computer via USB and USB Debugging is enabled, you need to re-start it in fastboot mode. Follow one of the two methods below. Option A may be preferable because it’s another confirmation that your computer recognizes your Nexus device.
A) Type “adb reboot bootloader”
B) Turn your device off, then turn it back on while holding down the relevant key combinations for your device. For many devices it’s Volume Up + Volume Down + Power. You can see what your device’s key combinations are here.
The fastboot menu will appear and you should see Start in the top right. Press Volume Up till it changes to Recovery. Press the Power button to select it.
You will see an Android with a red exclamation point icon, press and hold the Power key, then press the Volume up key to show the Recovery Menu.
You will get a new menu. Navigate to apply update from adb and select it by pressing the Power button.
In the command window — make sure you are in the directory where ADB and Fastboot reside — type: “adb sideload [the full name of the file].zip” without the brackets around the file name.
The update will install and reach 100 percent.
Reboot and enjoy the latest version of Android Marshmallow.
Click to expand...
Click to collapse
(red arrow) and then the cmd says the null error, i am trying this now
I had the same problem. Turned MTP on and then it worked. You're told to turn it off but don't... Its in Settings-Storage-touch the ... Menu top right corner, USB settings and turn ON MTP mode. It worked well for me. I also used the Nexus Root Toolkit - makes things much easier!
Click to expand...
Click to collapse
My phone is able to rebooot (the options comes out sometimes after i did not do anything) and now optimising app (like it usually did after an OTA update)

hendyanto said:
100% Stock, yes! 1 week old.
Yes i have set up ADB
I have followed the instruction until this part (i cannot post any link sorry, not authorized by xda)
(red arrow) and then the cmd says the null error, i am trying this now
My phone is able to rebooot (the options comes out sometimes after i did not do anything) and now optimising app (like it usually did after an OTA update)
Click to expand...
Click to collapse
There are lots of additional steps in that guide and not always the simplest way of doing it.
First thing to do is boot into recovery.
- Turn off the phone.
- Hold volume down + power
- At the bootloader screen, use volume keys to navigate to recovery and press power to select#
- At the Red warning triangle, hold power then press volume up.
At this stage, type "adb devices" in your command prompt and see if it returns your serial number or not. If it does, you can follow the steps to use adb to flash the update.
Please note, the guide talks about USB debugging. This only works in android. Nothing you need to do needs to be done via android so this is nonsense. Also the MTP option only works in android, so setting this in settings as a fix is also nonsense.

danarama said:
There are lots of additional steps in that guide and not always the simplest way of doing it.
First thing to do is boot into recovery.
- Turn off the phone.
- Hold volume down + power
- At the bootloader screen, use volume keys to navigate to recovery and press power to select#
- At the Red warning triangle, hold power then press volume up.
At this stage, type "adb devices" in your command prompt and see if it returns your serial number or not. If it does, you can follow the steps to use adb to flash the update.
Please note, the guide talks about USB debugging. This only works in android. Nothing you need to do needs to be done via android so this is nonsense. Also the MTP option only works in android, so setting this in settings as a fix is also nonsense.
Click to expand...
Click to collapse
I cannot get my windows to detect the phone during recovery mode, it always disconnected at that point.
I'll try again when i have the time, thank you all.

hendyanto said:
I cannot get my windows to detect the phone during recovery mode, it always disconnected at that point.
I'll try again when i have the time, thank you all.
Click to expand...
Click to collapse
Could be a driver issue. You'll need to check device manager. Perhaps uninstall the existing drivers and let it auto detect.
Failing that, install the Naked driver from my adb and fastboot thread (Nexus 6 general > Sticky roll-up thread > Adb and fastboot. What is it?)

I had the same issue with you until i did the following: I used wugfresh's nexus utility. Then I downloaded the respective file from XDA and saved it in the same folder as the Wugfresh's tool. Restarted in Recovery mode and chose 'update from adb'. Connected the phone with the usb having USB debugging on from before going to recovery. Started the CMD window from Wugfresh's tool (Advanced Utilities -> Launch) and check that the phone is connected (I think "adb devices") . Then "adb sideload xxxx.zip" and waited for the process to finish.
Instruction here: androidpolice 2012/11/13/android-4-2-build-jop40c-rolling-out-to-the-nexus-7-now-manual-download-link-available/
You do not have to install the full Android utility. Just use wugfresh;s cmd screen. Good luck!

danarama said:
Could be a driver issue. You'll need to check device manager. Perhaps uninstall the existing drivers and let it auto detect.
Failing that, install the Naked driver from my adb and fastboot thread (Nexus 6 general > Sticky roll-up thread > Adb and fastboot. What is it?)
Click to expand...
Click to collapse
qwerty1gr said:
I had the same issue with you until i did the following: I used wugfresh's nexus utility. Then I downloaded the respective file from XDA and saved it in the same folder as the Wugfresh's tool. Restarted in Recovery mode and chose 'update from adb'. Connected the phone with the usb having USB debugging on from before going to recovery. Started the CMD window from Wugfresh's tool (Advanced Utilities -> Launch) and check that the phone is connected (I think "adb devices") . Then "adb sideload xxxx.zip" and waited for the process to finish.
Instruction here: androidpolice 2012/11/13/android-4-2-build-jop40c-rolling-out-to-the-nexus-7-now-manual-download-link-available/
You do not have to install the full Android utility. Just use wugfresh;s cmd screen. Good luck!
Click to expand...
Click to collapse
Thank you guys! But after this "happy"night, i woke up to the OTA for marshmallow arrived on my phone, so see you guys on the rooting section instead, Thank you thank you for the help

LGmusic app return for UltraPOP v1.51

1) Download this and unzip.
2) Enable USB debuging and conect your device to PC.
3) Run backLGmusic.bat and press any key for start
4) On device grant Root permissions and confirm debugging.
5) At the end of the script prompts you to restart the device,
press any key

Awesome, thanks for this..

mayrer said:
1) Download this and unzip.
2) Enable USB debuging and conect your device to PC.
3) Run backLGmusic.bat and press any key for start
4) On device grant Root permissions and confirm debugging.
5) At the end of the script prompts you to restart the device,
press any key
Click to expand...
Click to collapse
check my attachment ideas?

umcc05 said:
check my attachment ideas?
Click to expand...
Click to collapse
I checked , it works.
Make manually, folders LgMusic and LgMusicWidget copy to system\priv-app.

[Guide] [One UI 3] How to boot into recovery in One ui 3 & above without a pc and root access

Reboot Your Device Into Recovery Mode
There are multiple ways to reboot an Android device into recovery mode. But after the latest OneUI 3.0 update, Samsung does not allow booting into recovery without connecting your phone to a PC with a USB-C cable. Here's a solution to easily reboot to recovery.
The steps mentioned can be applied to boot into both the stock recovery as well as a custom recovery if you have one installed.
Reboot to recovery without root access and without connecting your phone to Laptop/Pc.​
Download & Install LADB - Local ADB shell from playstore or download it directly from here.
Open Settings > About Phone and tap on the “Build number” field 7 times. This will enable “Developer Options.”
Go to Settings > System > Developer Options and enable “USB debugging” and “Wireless debugging.”
Open the LADB app. It will show a “Pairing information” dialog.
Open the recent apps screen. Press and hold on the app’s icon and tap “Split Screen” to open LADB in split-screen multitasking view.
On the bottom half, open Settings. Go to System > Developer Options > Wireless debugging. Tap on “Pair device with pairing code.” You’ll see a “Pair with device” dialog pop-up.
Copy the 6 digit “Wi-Fi pairing code” and paste it into the “pairing code” box in LADB. Copy the 5 digit port number from the IP address (the 5 numbers after the colon) and paste it into the “Port” box in LADB.
Hit “OKAY” in LADB and you should hopefully see text that says "Hello World”
Enter "reboot recovery"
And done now your phone will automatically reboot to recovery.
Note :
You can even try out different adb commands like deblooting system apps, allow permissions to apps like macdriod, system ui turner, etc and many more other adb commons without root and without a PC. (tested on Galaxy M30s)
Thanks to the developer of LADB
For downloads and other instructions : Click here

Reserved..

thanks .. good tut and very useful

Power off, then hold volume up and bixby button till recovery comes up. Works without a pc or cable.
realbbb
Moldly Going

realbbb said:
Power off, then hold volume up and bixby button till recovery comes up. Works without a pc or cable.
realbbb
Moldly Going
Click to expand...
Click to collapse
It's for users without root and pc

razs.originals said:
It's for users without root and pc
Click to expand...
Click to collapse
Power off, then hold volume up and bixby button till recovery comes up works for root, no-root, pc, or no-pc. It does not matter what version of OneUI.
realbbb
Purely Board

realbbb said:
Power off, then hold volume up and bixby button till recovery comes up works for root, no-root, pc, or no-pc. It does not matter what version of OneUI.
realbbb
Purely Board
Click to expand...
Click to collapse
Okay it might be working that way for you but many users reported that without connecting USB they aren't able to boot into recovery
recovery mode in android 11 one ui 3.1
Guys anybody know that how to go recovery mode in android 11 ( one ui 3.1 )
r2.community.samsung.com

Will this let me unlock bootloader?

Question Hi Not working fastboot mode on Oppo reno 5 (CPH2159)

What's on the buttons, all buttons are in working order
oem-unlock & usb debugging included
no password on the phone
holding the power button and sound -, I get into recovery, I don't need to go there
holding down the power button and sound +, some **** the system is loaded
================================================== ==============
On the command line:
adb devices - it shows up as (9cd64a6d device)
adb reboot bootloader - a picture appears (fastboot mode. To exit, pull out the battery or hold it off for 6-10 seconds) for a quarter of a second and reboot into the system.
What have I not done yet to enter fastboot mode?
If you need to install Deep Testing / in-depth test / deep scanning, then it cannot be installed, the application is not installed

Are you solved your problem

Are you solved your problem? Please answer me.