Database Info

help root

Hi everyone,
I tried the method given by @DallasCZ but I have an issue.
All the files are in the same folder but I have this message: "cannot load: 'boot.img': No such file or directory"
Please help me !
Thanks in advance.
Kisses

Bencaill said:
Hi everyone,
I tried the method given by @DallasCZ but I have an issue.
All the files are in the same folder but I have this message: "cannot load: 'boot.img': No such file or directory"
Please help me !
Thanks in advance.
Kisses
Click to expand...
Click to collapse
Hello, are you sure you have the boot.img also in the direcotry?

DallasCZ said:
Hello, are you sure you have the boot.img also in the direcotry?
Click to expand...
Click to collapse
yes, I am sure I have it

Bencaill said:
yes, I am sure I have it
Click to expand...
Click to collapse
i tried it again and it works well for me.
can you post a creen of the folder where you extracted the files?

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

you have to run the root.bat file, you cannot dir the boot.img

I know I have to run the bat file but you asked me a screen of the folder

I have this message:

strange... idunno for me its working well (windows 7 pro) and the boot.img is in the same directory... do you have some antivirus, anti spam apps running?

A other member of Frandroid forum has exactly the same issue. But he is running W8.1
That is really strange.

I am running win 8.1 as well

POThe only thing I can suggest is to change the line
fastboot -i 0x1bbb boot boot.img
to (in your specific case)
c:\users\user\desktop\idol3_6045_root\fastboot -i 0x1bbb boot c:\users\user\desktop\idol3_6045_root\boot.img
and see what occurs.
I'm thinking you may have fastboot somewhere else on your computer as well and that somehow, it's looking in the local directory of that fastboot. While that goes against everything logical (local directory should always be checked first), I'd give that a shot.
If that still doesn't work, open the cmd.exe with elevated permissions (right click "command prompt" in start menu, and run as administrator)

The problem seems to be resolved by using Windows 7 instead.
http://forum.frandroid.com/topic/223905-tuto-root-de-l-idol-3-55/?p=3417628

using win 7 is not a solution... there have to be a way how to do it, because there are thousands of users with win 8.1 who using fastboot and adb commands...

Is it a drivers issue? Does "adb devices" return anything? Or "fastboot devices" if you're in the bootloader? If you don't get a device listed after executing that command, the OS isn't fully recognizing the Icon 3.
I've all but abandoned using Windows for interaction with my Android devices. The driver issues are too big a pain in the butt. With Mac, and no need for installing drivers, the only issue is the occasional usb cable that doesn't work well. I don't mean that as a Mac is better than Windows thing. I use both and am not into these kinds of battles. But it is easier on Mac in this case.
OP, have you tried this with a different USB cable?

is your bootloader unlocked?

And I take it you've enabled Developer Options and USB Debugging?

After all my talk about the ease of communicating with Android devices from a Mac, I'm now unable to successfully issue fastboot commands when in the bootloader. I've tried using sudo, making sure to include arguments that address the device, etc. I can execute adb commands when the phone's system is booted, though. But fastboot commands either get me a "waiting for device" or nothing at all. I thought I was able to do this successfully yesterday, when I was just testing it out. Today, I was going to root by booting into TWRP and flashing SuperSU.

maigre said:
Is it a drivers issue? Does "adb devices" return anything? Or "fastboot devices" if you're in the bootloader? If you don't get a device listed after executing that command, the OS isn't fully recognizing the Icon 3.
I've all but abandoned using Windows for interaction with my Android devices. The driver issues are too big a pain in the butt. With Mac, and no need for installing drivers, the only issue is the occasional usb cable that doesn't work well. I don't mean that as a Mac is better than Windows thing. I use both and am not into these kinds of battles. But it is easier on Mac in this case.
OP, have you tried this with a different USB cable?
Click to expand...
Click to collapse
If it was a driver issue, my phone would not restart with the command, every drivers are OK

ractar28 said:
POThe only thing I can suggest is to change the line
fastboot -i 0x1bbb boot boot.img
to (in your specific case)
c:\users\user\desktop\idol3_6045_root\fastboot -i 0x1bbb boot c:\users\user\desktop\idol3_6045_root\boot.img
and see what occurs.
I'm thinking you may have fastboot somewhere else on your computer as well and that somehow, it's looking in the local directory of that fastboot. While that goes against everything logical (local directory should always be checked first), I'd give that a shot.
If that still doesn't work, open the cmd.exe with elevated permissions (right click "command prompt" in start menu, and run as administrator)
Click to expand...
Click to collapse
Your method worked !!!!!!!!!!!!!!! THX !!!!!

"Allow USB Debugging" to allow computer's RSA Keyprint not popping up (Windows 10)

"Allow USB Debugging" to allow computer's RSA Keyprint not popping up (Windows 10)
Hey all,
I recently got a new Windows 10 laptop and tried connecting my Pixel 3 to it today. The internal storage of the phone shows up no problem when plugging in. However, I cannot get ADB to work with the laptop. I have USB Debugging selected on the phone but when my phone connects to the laptop, there isn't any popup where it says "Allow USB Debugging?" and it also says the computer's RSA Keyprint.
On my old Windows 8.1 laptop, when it connected to my phone for the first time, a popup asking for permission to "Allow USB Debugging" would popup and I would allow it and things would work. I've opened a CommandPrompt window where my SDK platform tools are to check "adb devices" and it doesn't show up. Anybody able to help?

Have you gone into developer options and turned on USB debugging manually?

I would also try revoking authorizations on the phone. Try in ADB and Fastboot both (adb devices / fastboot devices) and see if it registers at all there. Make sure you have the latest SDK/platform tools, try a different cable, different port on the PC, etc. I've also had success with changing the USB mode to the various options (ptp, media, etc). Once you get the phone to show up as unauthorized in ADB you should see the prompt to approve it. I don't think Fastboot asks for auth but if fastboot works and ADB doesn't, it might indicate a problem with the drivers or platform tools version.
They can been picky sometimes.

Exokan said:
Have you gone into developer options and turned on USB debugging manually?
Click to expand...
Click to collapse
Yep, under developer options I have USB debugging turned on.
fury683 said:
I would also try revoking authorizations on the phone. Try in ADB and Fastboot both (adb devices / fastboot devices) and see if it registers at all there. Make sure you have the latest SDK/platform tools, try a different cable, different port on the PC, etc. I've also had success with changing the USB mode to the various options (ptp, media, etc). Once you get the phone to show up as unauthorized in ADB you should see the prompt to approve it. I don't think Fastboot asks for auth but if fastboot works and ADB doesn't, it might indicate a problem with the drivers or platform tools version.
They can been picky sometimes.
Click to expand...
Click to collapse
I've revoked authorizations and plugged the phone into my old Windows 8.1 laptop and right away on the pixel the popup asking to authorize USB debugging popped up. I will try later with the new laptop to see if it'll start working. I downloaded the newest SDK tools yesterday via downloading Android Studio and have the latest platform tools as well during the first time I tried. Will try with a different cable and port also to see if that's the issue, same with fastboot mode.
EDIT: OK, I've tried using 2 different cables now to try and connect the phone to the laptop, one more USB-A to USB-C and a direct USB-C to USB-C connection, both sense the phone but no authorization popup to allow USB debugging on the Pixel. I've also tried to switch different USB mode on the Pixel to different options like PTP, charging only etc. but nothing. No popup.

Toronadian said:
Yep, under developer options I have USB debugging turned on.
Click to expand...
Click to collapse
Sorry, I missed that in your original post. So when you plug the phone in the Pixel isn't showing the little P System Icon? And you're opening the command prompt (not Power Shell) in the same folder as the Tools from here: https://developer.android.com/studio/releases/platform-tools.html ? I honestly don't remember an authorization pop-up so this is weird...

Exokan said:
I honestly don't remember an authorization pop-up so this is weird...
Click to expand...
Click to collapse
It's this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Usually comes up the first time you use a given machine to connect via ADB but sometimes gets goofed and you have to remove and reauth it.

Exokan said:
Sorry, I missed that in your original post. So when you plug the phone in the Pixel isn't showing the little P System Icon? And you're opening the command prompt (not Power Shell) in the same folder as the Tools from here: https://developer.android.com/studio/releases/platform-tools.html ? I honestly don't remember an authorization pop-up so this is weird...
Click to expand...
Click to collapse
BINGO. Thank you. I've been using Powershell thinking it's the same for some reason. I use the same Shift+Right Click shortcut and kept clicking open powershell window thinking it's the same. Instead, opened up a proper command prompt window this time (the bar at the top of Windows Explorer, typed "cmd"), and when I typed "adb devices", the authorization popup came and now everything works.

Toronadian said:
BINGO. Thank you. I've been using Powershell thinking it's the same for some reason. I use the same Shift+Right Click shortcut and kept clicking open powershell window thinking it's the same. Instead, opened up a proper command prompt window this time (the bar at the top of Windows Explorer, typed "cmd"), and when I typed "adb devices", the authorization popup came and now everything works.
Click to expand...
Click to collapse
Awesome! And yeah, that's tripped me up before as well!

HOW TO UNLOCK BOOTLOADER ON LENOVO TAB TB-7504X

I am using 'fastboot oem unlock' but
Erorr shows me
'fastboot (remote : unknown command)
How to solve this problem
???
Please help me

Download the latest version of fastboot & ADB.
You can see what version adb and fastboot you have installed, just open a command window and type: sudo adb --version (then hit enter) sudo fastboot --version (hit enter key) that will show your installed version of those tools. I believe right now the latest is 31.02 but I could be wrong. It is updated often and using an older release of adb and fastboot can and will cause issues..
Go here to download adb and fastboot. https://developer.android.com/studio/releases/platform-tools
Just download the android sdk for whatever OS you use on your computer, unzip...
What is the device you are trying to unlock? Have you enabled developer options on the phone and changed usb settings to file transfer instead of the default which is charging? Also have if that was done did you keep a close eye on your device because there will be a small box that pops up that must be immediately checkmarked so that your computer can communicate with your device. Have you selected "allow oem unlock"Also in the developer options? it might be good idea to set your lock screen to "none" instead of having a lock set for it. Any time anything is installed on a computer it almost always needs to be rebooted. If you have not done any of that I would suggest doing it all.
Also depending on what device you are attempting to unlock the bootloader on, the wording could be slightly different. My Pixel 4XL uses: fastboot flashing unlock , to unlock bootloader. So keep that in mind as well. If you use Windows OS on your computer some day when you have a minute check out Linux. You can make a "live USB" burn a copy of a Linux distro to a USB drive and boot from it and or install it along with your Windows OS, aka dual boot... The very first time I used Linux, it was Ubuntu and quite a few years ago and I would never return to Windows!! Can't stand it! Linux is made for doing what we do to our phones.
If you need more any help with this some other time and still cannot get it installed message me on here or should I say "start a conversation" with me here on xda. Same thing with the new layout.. My user name is the same here on XDA as it is on telegram. Feel free to shoot me a message any time. It may take a some time to respond depending on what day it is and what time and all that but I will respond.
Here is one of the best guides in my opinion on how to get and setup adb and fastboot tools on MAC, Linux and Windows OS. https://forum.xda-developers.com/t/guide-unlock-flash-root-for-the-pixel-2-xl-taimen.3702418/
(Edited)

flash713 said:
it is not working, same error after update.............
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

MBF_9802 said:
View attachment 5323891
Click to expand...
Click to collapse
Try typing: sudo fastboot --version & sudo adb --version and make 100/% that they are most current and up to date. I'll go grab a link really fast...
Okay idk how you installed adb & fastboot but this guide in my opinion is the best!!! https://forum.xda-developers.com/t/guide-unlock-flash-root-for-the-pixel-2-xl-taimen.3702418/
Try using different ports, reboot your computer..
Did you already have the pop up on your device once connected to computer or no? If not your it won't work at all.
Enable developer options
USB debugging
Now plug in to a different USB port.
Now scroll down on phone to default USB configuration and change it from the default which is "charging" to "file transfer" but keep your eyes on your device screen because the pops up will only show itself for a few seconds. When it does checkmark the box. You should be good then. Windows has driver issues alot of the time!! I switched to Linux years ago and I have no driver issues. Or anything else far as that goes.

flash713 said:
Try typing: sudo fastboot --version & sudo adb --version and make 100/% that they are most current and up to date. I'll go grab a link really fast. Brb
Click to expand...
Click to collapse

MBF_9802 said:
View attachment 5323897
Click to expand...
Click to collapse
Looks like that's not latest. Go here and download latest and install on your computer. See if that helps. Directions in the op of link I pasted in my last post for all OS, Mac, Windows, and Linux.
Type sudo adb devices
What does that do when you are plugged in to pc with phone?

flash713 said:
Looks like that's not latest. Go here and download latest and install on your computer. See if that helps. Directions in the op of link I pasted in my last post for all OS, Mac, Windows, and Linux.
Type sudo adb devices
What does that do when you are plugged in to pc with phone?
Click to expand...
Click to collapse
All try but reason only command not found
Please help......

flash713 said:
Looks like that's not latest. Go here and download latest and install on your computer. See if that helps. Directions in the op of link I pasted in my last post for all OS, Mac, Windows, and Linux.
Type sudo adb devices
What does that do when you are plugged in to pc with phone?
Click to expand...
Click to collapse
Same error in updated version
How to solve

MBF_9802 said:
Same error in updated version
How to solve
Click to expand...
Click to collapse
Did you ever onstll universal usb drivers for adb? If not install them and afterwards reboot your computer and then try.

flash713 said:
Looks like that's not latest. Go here and download latest and install on your computer. See if that helps. Directions in the op of link I pasted in my last post for all OS, Mac, Windows, and Linux.
Type sudo adb devices
What does that do when you are plugged in to pc with phone?
Click to expand...
Click to collapse
Same error in updated version
flash713 said:
Did you ever onstll universal usb drivers for adb? If not install them and afterwards reboot your computer and then try.
Click to expand...
Click to collapse
yes but same problem in universal usb drivers

Problems with getting some console commands working

I'm pretty new to stuff like rooting phones and such so I figured out that I'd be trying to see if I could manage to get my bootloader unlocked so I can once and for all install TWRP, which my dumbass has been trying to install without an unlocked bootloader.
I've got the basics going, like how should I do the unlocking (my phone's model is 5054S, yes it's an alcatel phone) and found a website which tells what commands you should do to unlock it
Well...
It just gets stuck there without further response. Amazing.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Could you guys help me on this one?

Command
Code:
fastboot reboot fastboot
is only to be used if Fastboot server is located in Android's user-space what only is case when Android OS has Dynamic Partition Layout.

jwoegerbauer said:
Command
Code:
fastboot reboot fastboot
is only to be used if Fastboot server is located in Android's user-space what only is case when Android OS has Dynamic Partition Layout.
Click to expand...
Click to collapse
Oh no, this happens with every piece of code that needs some input from a phone (with this i mean the part where the command line just gets stuck)
And this is essentially the same with every code I have to utilize in the guide for unlocking

jwoegerbauer said:
Command
Code:
fastboot reboot fastboot
is only to be used if Fastboot server is located in Android's user-space what only is case when Android OS has Dynamic Partition Layout.
Click to expand...
Click to collapse
Extra thing:
There's also this
Code:
fastboot -i 0x1bbb devices
Which when actually used, it kinda does work?? Just doesn't recognize the -i as a parameter in the programs. And yes, this happens with both CMD and PowerShell

Okay,
Code:
adb reboot-bootloader
DOES work. But it only restarts the phone.
And there's also this

Polaroid. said:
Okay,
Code:
adb reboot-bootloader
DOES work. But it only restarts the phone.
And there's also this View attachment 5348201
Click to expand...
Click to collapse
You are contradicting yourself: The applied ADB command of course DID NOT WORK, you got an error.
Reason: ADB got inproperly configured on phone.
Try this to get rid off of the error:
1. Disconnect phone from computer.
2. Revoke "USB debugging authorizations" in Android's Developer options on the phone.
3. Reconnect the phone to the computer and allow USB debugging on phone again.
4. Confirm the RSA-key in Authorization popup.

jwoegerbauer said:
You are contradicting yourself: The applied ADB command of course DID NOT WORK, you got an error.
Reason: ADB got inproperly configured on phone.
Try this to get rid off of the error:
1. Disconnect phone from computer.
2. Revoke "USB debugging authorizations" in Android's Developer options on the phone.
3. Reconnect the phone to the computer and allow USB debugging on phone again.
4. Confirm the RSA-key in Authorization popup.
Click to expand...
Click to collapse
Ah, thanks for correcting me. Didn't know about that. Gonna try if it works now

jwoegerbauer said:
You are contradicting yourself: The applied ADB command of course DID NOT WORK, you got an error.
Reason: ADB got inproperly configured on phone.
Try this to get rid off of the error:
1. Disconnect phone from computer.
2. Revoke "USB debugging authorizations" in Android's Developer options on the phone.
3. Reconnect the phone to the computer and allow USB debugging on phone again.
4. Confirm the RSA-key in Authorization popup.
Click to expand...
Click to collapse
Okay, I tried doing this and it does not resolve the problem, still restarts the phone
Yes. It is the same command and all but it still just doesn't work properly.

Q1: What is returned by command
Code:
adb devices
Q2: What is returned by command
Code:
fastboot devices

Hint: Add Alcatel 5054S to this thread's title thus mainly owners of such phone get addressed.

Mi projector MJJGYY02FM crashed

Good morning,
I'm new here, and i hope you can help me with my problem.
I have a mi MJJGYY02FM projector and i did a update with USB stick with files from Xiaomi.
Now after the update the projector start with MI logo and than shuts down, after that he start up with no screen and do nothing.
Can someone help me how to fix this. i can't get the projector in a boot menu with the remote, maybe he dont recognize the remote.
Kind Regards,
Bas

Reflash projector's Stock ROM.

jwoegerbauer said:
Reflash projector's Stock ROM.
Click to expand...
Click to collapse
I have the stock ROM on USB now, but hè will not install it. When i press the home and enter button and plug the power cable. Hè start up with the MI logo and shuts down, then start up with no screen.
Are there other ways to install the stock ROM?

AFAIK the Stock ROM typically gets installed by means of ADB Sideload method:
Code:
adb devices
adb reboot sideload
adb sideload <FULL-PATH-TO-STOCK-ROM-ZIP-FILE-ON-PC-HERE>

jwoegerbauer said:
AFAIK the Stock ROM typically gets installed by means of ADB Sideload method:
Code:
adb devices
adb reboot sideload
adb sideload <FULL-PATH-TO-STOCK-ROM-ZIP-FILE-ON-PC-HERE>
Click to expand...
Click to collapse
Thanks
Im gonna search out and try that option.
I let it know when it works. maybe i have some questions.

jwoegerbauer said:
AFAIK the Stock ROM typically gets installed by means of ADB Sideload method:
Code:
adb devices
adb reboot sideload
adb sideload <FULL-PATH-TO-STOCK-ROM-ZIP-FILE-ON-PC-HERE>
Click to expand...
Click to collapse
Im trying something, but do you have a discription how to make that USB with the Stock Rom?
I got your files on my pc. I have a 16GB USB format FAT32.
What is the way to make that sideload with the ROM version?
Im sorry for the questions, but i have never done this before.

I have done thist thing
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

The USB-stick, once plugged into Windows computer, in Windows OS is recognized as a drive: note down this drive letter returned. Then sequentially run the ADB commands listed above.

jwoegerbauer said:
The USB-stick, once plugged into Windows computer, in Windows OS is recognized as a drive: note down this drive letter returned. Then sequentially run the ADB commands listed above.
Click to expand...
Click to collapse
Must i do the commander when the stock ROM is on the USB?
By what command must i write the letter from the USB?

Vross46 said:
Must i do the commander when the stock ROM is on the USB?
By what command must i write the letter from the USB?
Click to expand...
Click to collapse
My drive letter is :e

Didn't think it can be so difficult.
Assumed the Stock ROM's file is located in root of E: drive then the ADB command in your case becomes
Code:
adb sideload E:\<NAME-OF-STOCK-ROM-ZIP-FILE>
where you have to substitute
<NAME-OF-STOCK-ROM-ZIP-FILE>
by ROM's true file name

jwoegerbauer said:
Didn't think it can be so difficult.
Assumed the Stock ROM's file is located in root of E: drive then the ADB command in your case becomes
Code:
adb sideload E:\<NAME-OF-STOCK-ROM-ZIP-FILE>
where you have to substitute
<NAME-OF-STOCK-ROM-ZIP-FILE>
by ROM's true file name
Click to expand...
Click to collapse
ah ok. lets try.
It seems not so difficult but, for the first time is everything more difficult

What do i wrong. sorry! I do really my best
1, i have a format 16gb usb FAT32
2. i have install ADB installer.
3. i have download the stock rom (see picture)
4. my drive name is e:
5. When i zip my stock rom file, i got an another zip file, and an file of 1kb
in the next picture is what i do in CMD
anglee_full_9.0.0.1911 is my zipped stock rom downloadfile
the other 2 are the unzipped files from the first file

1st screenshot provided above shows
1. Device isn't connected via USB-cable with PC or, if, not powered on
2. The ROM's archive name you entered is without fileextension -> required :ZIP
If ROM's archive is packed as .RAR file then you have it to repack to .ZIP file

I think it will not gonna help.
When i connect my projector to the pc, the pc dont recognize him.
What i try, nothing works.

but thanks for your help anyway

Have you ever enabled "USB Debug" in Android's Settings -> Developer otions?

I dont know if its enabled. But now in can not come in the menu.
MI logo shine for 1 second. And it turns off.
So i have no possibillity to check

Vross46 said:
I dont know if its enabled. But now in can not come in the menu.
MI logo shine for 1 second. And it turns off.
So i have no possibillity to check
Click to expand...
Click to collapse
Hello Vross46, have you been able to solve your problem? I’m stuck with the logo as well