Develop Bugs

[Q] Can I downgrade 10.3 with Windows?

Hello,
Still working on my kids KF2. I got root, yeah! However at some point it updated to 10.3. Can someone point me in the right direction for getting its bootloader downgraded from a Windows 7 x64 platform? I can use a RHEL box at work if I really need to, but rather not.
so I get CM on this thing
thanks!

http://forum.xda-developers.com/showthread.php?t=2100963

soupmagnet said:
http://forum.xda-developers.com/showthread.php?t=2100963
Click to expand...
Click to collapse
Does that mean I need a fastboot cable? I can make one no problem... but better if I don't have to
I ran: fastboot -i 0x1949 flash bootloader otter2-u-boot-prod-10.2.4.bin, device off, it said waiting for device, but then it just boot up to the lock screen.
Sorry im a little confused on this one.

Code:
adb shell su -c "reboot bootloader"

soupmagnet said:
Code:
adb shell su -c "reboot bootloader"
Click to expand...
Click to collapse
Thanks for the info.. but im gonna be a noob here...
What do I do with that? run it from command prompt? with the device booted, not booted? before the fastboot -i 0x1949 flash bootloader ?

s10010001 said:
Thanks for the info.. but im gonna be a noob here...
What do I do with that? run it from command prompt? with the device booted, not booted? before the fastboot -i 0x1949 flash bootloader ?
Click to expand...
Click to collapse
That is a command to be run from the command lint to put your device in fastboot mode without a factory cable. Once your device is in fastboot, then you can continue with the fastboot commands. If you are in fastboot and you still get "<waiting for device>", you need to make sure your drivers are configured properly.

soupmagnet said:
That is a command to be run from the command lint to put your device in fastboot mode without a factory cable. Once your device is in fastboot, then you can continue with the fastboot commands. If you are in fastboot and you still get "<waiting for device>", you need to make sure your drivers are configured properly.
Click to expand...
Click to collapse
Thanks a ton! Ill give it a try tonight when I get home.
In theroy:
Fastboot with that command
Install downgraded bootloader
install TWRP
Install rom
enjoy...

s10010001 said:
Thanks a ton! Ill give it a try tonight when I get home.
In theroy:
Fastboot with that command
Install downgraded bootloader
install TWRP
Install rom
enjoy...
Click to expand...
Click to collapse
Close
Make backups
Fastboot with that command
Install downgraded bootloader
Install 2nd bootloader
Install TWRP & kernel(boot.img)
Factory Reset in TWRP
Install rom
enjoy..
Enjoyment is relative, of course

Well bummer. I got into fast boot. I think I got a backup. But on a reboot, it just looks the Orange Kindle Fire logo...
Now I really need a fast boot cable hua? Assuming a fastboot cable will let me fast boot. Once there again what can I do?

s10010001 said:
Well bummer. I got into fast boot. I think I got a backup. But on a reboot, it just looks the Orange Kindle Fire logo...
Now I really need a fast boot cable hua? Assuming a fastboot cable will let me fast boot. Once there again what can I do?
Click to expand...
Click to collapse
Hold the power button to turn your device off, enter the following command and boot it up again...
Code:
fastboot -i 0x1949 getvar product
...dose your device boot into fastboot? If so, start over and try again. If not, you'll need a factory cable.

soupmagnet said:
Hold the power button to turn your device off, enter the following command and boot it up again...
Code:
fastboot -i 0x1949 getvar product
...dose your device boot into fastboot? If so, start over and try again. If not, you'll need a factory cable.
Click to expand...
Click to collapse
it was worth a shot, but no Ill be needing that cable
When I make one, will it just boot into fastboot upon boot if the cable is in? Just pins 1 and 4 right?

s10010001 said:
it was worth a shot, but no Ill be needing that cable
When I make one, will it just boot into fastboot upon boot if the cable is in? Just pins 1 and 4 right?
Click to expand...
Click to collapse
If your device is completely off, and you plug a working factory cable in, it will boot into fastboot.
Info on pin layout
You need a 5-pin usb cable BTW.

Cool, thanks for all the help.
One more question. Do you have one of the guides you specially recommend once I do get the cable made?

s10010001 said:
Cool, thanks for all the help.
One more question. Do you have one of the guides you specially recommend once I do get the cable made?
Click to expand...
Click to collapse
Were you able to successfully backup your boot, recovery, and system partitions before everything went wrong?

No I was looking at it, I think it errored out.
I can just fastboot with cable and start over with hash's guide?

s10010001 said:
No I was looking at it, I think it errored out.
I can just fastboot with cable and start over with hash's guide?
Click to expand...
Click to collapse
Possibly, but depending on where things went wrong, you may have to restore first. Do you know what the error was?

Something like this max-download-size: 486,539,264

s10010001 said:
Something like this max-download-size: 486,539,264
Click to expand...
Click to collapse
You are supposed to save your partition images with the 'dd' command using the shell:
Hashcode said:
STEP 1. Backup your stock partitions to your own HD for later if you need disaster recovery:
Code:
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/boot of=/sdcard/stock-boot.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/recovery of=/sdcard/stock-recovery.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/system of=/sdcard/stock-system.img" # This will take a few minutes
adb pull /sdcard/stock-boot.img
adb pull /sdcard/stock-recovery.img
adb pull /sdcard/stock-system.img # This will take a few minutes
Take those files and put them somewhere safe.
Click to expand...
Click to collapse
You won't see a "max-download-size" message unless you are using fastboot to flash those images.

ohh ok.. so I dont have a backup
But the fastboot cable is working! Im in fastboot

keeps telling me no device found
do I want the "Android ADB Interface" or "Andriod Composite ADB Interface"?
Also once booted in to fastboot with the cable, do I just leave the cable or put the stock cable back in? Shouldnt matter... but just want to make sure.

fastboot never start after update to android 6

Hy
I had an unlocked bootloader phone. Yesterday I flashed the new Android 6, Europe version from the Huawei blog forum, no beta, on my Huawei GX8. I used the method, dload on SD card, Phone off an the press Volume down+volume up+Power button.The flashing was normaly.
Now the phone starts normaly but I can´t start fastboot. When the phone is off and i press Vol down + Power the phone start the android system and the Huawei logo is coming not the fastboot Modus. I can see my phone and the order under Windows but i can not control my phone with the fastboot command. (example: fastboot device. the answere ist searching devices, but it comes no resolution) I loaded the last version of Fastboot, but the problem is the same.
Please can you help me. What can i do? Many thanks for your help!

Should be connect the charger cable to the phone.
charger or computer
excuse me for bad english

No i use a data cable, debugging is on. I can copy data from my phone to PC or from PC to phone, but fastboot does not found my device.

bertl237 said:
No i use a data cable, debugging is on. I can copy data from my phone to PC or from PC to phone, but fastboot does not found my device.
Click to expand...
Click to collapse
And when you use adb to reboot to bootloader, what happen? Do you have "Minimal adb and fastboot tool" installed?

krispin said:
And when you use adb to reboot to bootloader, what happen? Do you have "Minimal adb and fastboot tool" installed?
Click to expand...
Click to collapse
Sorry for my question, what´s the differents about adb and fastboot tool? I have install the last version of minimal adb and the fastboot tool, also the Windows driver for the phone. Debugging is on. I try to connect my phone about the fastboot terminal. When i try to set the phone into the bootloader mod with the fastboot terminal and the equivalent command, fastboot say´s "searching phone". My phone does not react.

bertl237 said:
Sorry for my question, what´s the differents about adb and fastboot tool? I have install the last version of minimal adb and the fastboot tool, also the Windows driver for the phone. Debugging is on. I try to connect my phone about the fastboot terminal. When i try to set the phone into the bootloader mod with the fastboot terminal and the equivalent command, fastboot say´s "searching phone". My phone does not react.
Click to expand...
Click to collapse
So, you connect your phone, open minimal adb and fastboot too, run "adb devices", you see device id? If yes, run "adb reboot bootloader" . Phone shoult reboot to fastboot mode. Then run "fastboot devices" to see if it is connected properely.

i did it, like you described, but i see not my device id. Only the note "seach device"
Is it possible that TWRP is defect on my device? Is TWRP necessary for fastboot or only for root?

bertl237 said:
i did it, like you described, but i see not my device id. Only the note "seach device"
Is it possible that TWRP is defect on my device? Is TWRP necessary for fastboot or only for root?
Click to expand...
Click to collapse
No, you should be able to use adb and fastboot with stock recovery.
After first adb command you shoult approve authorization on your phone.

Here is screenshot from minimal adb...
Phone must be in MTP mode.

And here is phone in fastboot

Many thanks for your help, now I m in my bootloader.
2 problems i had.
1. My daemon was not started correctly, i have not seen my device.
2. I used the wrong command. I started with fastboot, not with the command adb device. I tap „fastboot reboot-bootloader“,but the correct command is “adb reboot-bootlader“
Now i have seen my phone is unlocked, i hope i can root my android 6.

bertl237 said:
Many thanks for your help, now I m in my bootloader.
2 problems i had.
1. My daemon was not started correctly, i have not seen my device.
2. I used the wrong command. I started with fastboot, not with the command adb device. I tap „fastboot reboot-bootloader“,but the correct command is “adb reboot-bootlader“
Now i have seen my phone is unlocked, i hope i can root my android 6.
Click to expand...
Click to collapse
Just reboot to fastboot and flash surdu-petru version of TWRP recovery 3.0.2 with command "fastboot flash recovery xxxxx.img". And than reboot to recovery and flash supersu zip.

OP3 will show up in fastboot but not adb in fastboot mode

So I was trying to root my OP3... I don't know how but I Nuked the OS without oem unlocking enabled... I found this: https://forum.xda-developers.com/nexus-9/help/to-toggle-allow-oem-unlock-via-fastboot-t3091119 thread and thought I can apply this to my own situation. in fastboot mode (which I saw online the OP3 should respond to adb & fastboot in this mode) I try
Code:
adb devices
and nothing and
Code:
fastboot devices
[serial number] fastboot
I have tried every driver known to man.
Thanks in advanced for any support.

adb doesn't work in bootloader, only fastboot. What's the state of your phone now. Can you boot to os?
Sent from my ONEPLUS A3003 using Tapatalk

Having trouble going into fastboot

I got a new Robin, wanted to unlock and root. It has the latest update. When I try to go into fastboot, it reboots into a menu which has fastboot as an option, but when I select it it goes back into that menu, help. Thanks in advanced
https://imgur.com/a/d2JWB
Sent from my FRD-L14 using Tapatalk

That is fastboot mode, even says so on the top.

demeez said:
That is fastboot mode, even says so on the top.
Click to expand...
Click to collapse
I forgot to mention that I tried the commands to unlock the bootloader but adb didn't detect the phone. That's why I thought that wasn't fastboot mode. Adb finds the device if booted in the OS, but not in fastboot mode.
Sent from my FRD-L14 using Tapatalk

Is USB debugging on? Also oem unlock has to be set to on. Both are in developer options.

LavLab said:
Is USB debugging on? Also oem unlock has to be set to on. Both are in developer options.
Click to expand...
Click to collapse
they were, I'm using minimal adb and fastboot, also doing everything in virtualbox, I couldn't get adb in Linux mint to detect the phone.
Sent from my FRD-L14 using Tapatalk

maurogg84 said:
I forgot to mention that I tried the commands to unlock the bootloader but adb didn't detect the phone. That's why I thought that wasn't fastboot mode. Adb finds the device if booted in the OS, but not in fastboot mode.
Sent from my FRD-L14 using Tapatalk
Click to expand...
Click to collapse
What command did you use?

L3R0N said:
What command did you use?
Click to expand...
Click to collapse
I use this command
fastboot -i 0x2c3f oem unlock-go
But it kept saying waiting for device.
Sent from my FRD-L14 using Tapatalk

So I finally was able to unlock with Linux by adding the device 2c3f to udev. Maybe after adding the device to udev it could also work in virtualbox.
Sent from my FRD-L14 using Tapatalk

I use this walkthrough for linux users, leaving it here for reference
https://android.stackexchange.com/questions/144966/how-do-i-get-my-device-detected-by-adb-on-linux

New Razer Phone (1) stuck on download mode.

I bought a refurbished Razer phone one from the official razer eBay page, and it's stuck on download mode. I haven't tried flashing anything, I haven't even ever been to the home screen. What can I do to fix this?

Get the Google USB Driver and make sure your Razer phone is installed with these drivers
https://developer.android.com/studio/run/win-usb
Get Android SDK Platform Tools for latest ADB and fastboot tool
https://developer.android.com/studio/releases/platform-tools
Open command prompt to that folder and run these commands
fastboot flashing unlock
fastboot flashing unlock_critical
fastboot set_active a
from what i've gathered from other threads with similar problems, that's the jist of it...

It says "Waiting for any device" the problem is that it's not recognized by the computer.

Thank you ! Same problem. This is halp! after first run, works. Question, can I block it now? and how please... fastboot flashashing lock ?

Now I can block back? fastboot flashashing lock ?
ShadowVlican said:
Get the Google USB Driver and make sure your Razer phone is installed with these drivers
Open command prompt to that folder and run these commands
fastboot flashing unlock
fastboot flashing unlock_critical
fastboot set_active a
from what i've gathered from other threads with similar problems, that's the jist of it...
Click to expand...
Click to collapse
Hello. Same problem. ( I bought a refurbished Razer phone one from the official razer eBay page, and it's stuck on download mode. I haven't tried flashing anything). It helped me. Now I can block back? fastboot flashashing lock ? Please, sorry my english...

EDIT: The links did not copy paste appropriately. I fixed them now.
These are all posts from various places in this thread:
https://forums.redflagdeals.com/raz...b-1yr-warranty-8gb-64gb-octacore-9-0-2336958/
"Find the driver here:
https://dl-ssl.google.com/android/repository/latest_usb_driver_windows.zip
unzip the files/folder to a location you will remember
Follow the instructions below, point the windows driver update to the .inf file in that folder then driver will install. Make sure you have the latest Android platform tools, the link is also in the PDF below.
https://s3.amazonaws.com/cheryl-fac...stall_Android_Fastboot_Drivers_on_Windows.pdf
open a command prompt from within the Android sdk folder while the phone is still in download mode (phone stays and reboots to download mode through each process below making the process fairly easy)
type: fastboot devices
your phone should show up once drivers are installed correctly
type: fastboot flashing unlock
use the phone vol + - and power to select yes
phone should stay in download mode
type: fastboot flashing unlock_critical
use vol + - and power to select yes
phone should stay in download mode
Download the firmware image below or if you want to try the following command type: fastboot set_active a && fastboot reboot
to see if the phone boots, not sure if all the phones have Android installed. One poster below seems to and also seems to have his bootloader unlocked. This won't be the case for everyone. If phone does not boot continue downloading the firmware to install it
https://s3.amazonaws.com/cheryl-factory-images/cheryl-o-global-6033.zip
unzip all the files and put them in the android sdk folder, from the same command prompt if you're on Windows
type: flash_all.bat
For Mac type: flash_all.sh
Will take a few minutes but firmware will install. These instructions are for RFD members that do not either 1) want the hassle of RMA or 2) take a chance at voiding the warranty (any phone flashing via adb is frowned upon by Razer)"
------------------------------------------------------------
"Yes. Reverse the locking procedure. Put phone back into Download mode (from power off, press and hold Vol up and then plug phone into computer) then issue fastboot commands to lock boatloader starting with critical."
------------------------------------------------------------
"if you have a ryzen pc and getting some error while unlocking... dont plug the phone in at the beginning... type the command when it says [waiting for device] then plug it in ... also dont forget to unlock critical right after"

Now I can block back? fastboot flashashing lock ?
ShadowVlican said:
Get the Google USB Driver and make sure your Razer phone is installed with these drivers
Open command prompt to that folder and run these commands
fastboot flashing unlock
fastboot flashing unlock_critical
fastboot set_active a
from what i've gathered from other threads with similar problems, that's the jist of it...
Click to expand...
Click to collapse
it helped, now it is loaded; but after each reboot it writes, the phone is unlocked and that it is unsafe. can it be blocked back, is it safe that everything continues to work? please write what commands to enter?

365Thanks said:
it helped, now it is loaded; but after each reboot it writes, the phone is unlocked and that it is unsafe. can it be blocked back, is it safe that everything continues to work? please write what commands to enter?
Click to expand...
Click to collapse
Repeat the unlock commands using lock instead of unlock but in reverse order so:
fastboot flashing lock_critical
fastboot flashing lock
again you must place the phone in download mode (powered off...hold volume down key down...plug in) between each command and follow the onscreen instructions.

Open command prompt to that folder and run these commands
fastboot flashing unlock
fastboot flashing unlock_critical
fastboot set_active a
from what i've gathered from other threads with similar problems, that's the jist of it...[/QUOTE]
flopticalcube said:
Repeat the unlock commands using lock instead of unlock but in reverse order so:
fastboot flashing lock_critical
fastboot flashing lock
again you must place the phone in download mode (powered off...hold volume down key down...plug in) between each command and follow the onscreen instructions.
Click to expand...
Click to collapse
after each command you need to disconnect from the computer? fastboot flashing unlock
fastboot flashing unlock_critical
fastboot set_active a
I used to enter these commands , the instructions were only after 1
I did not turn off the phone and the question on the screen was only after the first command. I probably entered only 1 command <if it was necessary to disconnect phone? ... thank you for help.

Sudo.
If ur using linux - run it with sudo. always run fastboot with sudo

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot set_active a
error: Device does not support slots