Related
Yes, I did search and the funny part here, not ha ha funny, is that I have adb and fastboot working perfectly except for this one thing and it is driving me crazy. Have spent a few days on before asking for help. What might I be missing here for there has to be a solution and I have tried I thought them all? Any help greatly appreciated.
What kind of error do you get? Do you give the correct path to the recovery image?
I would love to try and help, but you did not provide the error message.
ehnvis said:
What kind of error do you get? Do you give the correct path to the recovery image?
Click to expand...
Click to collapse
at tigerteal as well
The exact error message is stated at the thread title. Not sure what you mean by path, but here is exactly what I type and the error it duplicates on not only one Vista machine but 2.
fastboot boot RAv1.1.2H.img then enter. result: cannot load recovery image
P.S. Yes, I am pretty certain by path if you mean under advanced settings system variables yes I did create one.
Are you opening your command prompt in the tools dir? Just thought i'd check the easy stuff first.
Clinton
ClintonH said:
Are you opening your command prompt in the tools dir? Just thought i'd check the easy stuff first.
Clinton
Click to expand...
Click to collapse
thanks clinton and i did try to cd this yet got another error message not sure why. not even sure how to do to be honest. the very odd part here and i have followed all of the guides is that if i do fastboot devices and other fastboot commands they all work perfectly, i.e. my phone's serial number shows etc, so i am at a complete loss as to what is causing this for fastboot works and does not work at the same time which makes no sense to my brain. please help if time. kevin
kevinrirvine said:
at tigerteal as well
The exact error message is stated at the thread title. Not sure what you mean by path, but here is exactly what I type and the error it duplicates on not only one Vista machine but 2.
fastboot boot RAv1.1.2H.img then enter. result: cannot load recovery image
P.S. Yes, I am pretty certain by path if you mean under advanced settings system variables yes I did create one.
Click to expand...
Click to collapse
Either you've changed the name of the recovery image or you're not typing it right.
It should be:
fastboot boot recovery-RAv1.1.2H.img
ClintonH said:
Are you opening your command prompt in the tools dir? Just thought i'd check the easy stuff first.
Clinton
Click to expand...
Click to collapse
that fixed the problem for me.
i don't understand it. i added a path and was able to see the device. i could even reboot the phone into fastboot mode from the cmd prompt, but until i cd'd to the tools directory it wouldn't load the recovery image via fastboot.
I see there are a lot of users here in these forums that either are scared of ADB or have no idea how to use it or what to do with it.
The beauty of ADB is it's cross platform, it works on Windows, Mac, and Linux.
The adb commands everyone should know how to use are very basic and used for file manipulation and device control.
To use ADB Google will tell you you need to download and install the most current Android SDK. If you want to write apps for Android, this is true, but for most people there's no need to do this.
You can get everything you need from one of the one clicks.
You need adb and fastboot for your platform.
Download them and put them in a directory of your choice, on my Mac they live in /Android.
I've dug them up and attached adb and fastboot for all platforms. Just unzip them and put the ones for your Operating System somewhere easy to get to.
if you're on Windows you'll need drivers. The best way to get the driver is to download HTC Sync from here http://dl4.htc.com/managed-assets/support/software/htc-sync/htc_sync_setup_3.2.20.exe and install it. After it is installed make sure it isn't running.
I'm now going to go through a few simple adb command and what they're for.
To use ADB or Fastboot your phone has to be in USB Debugging mode Set this in Settings/Developer Options on the phone.
Open a Command prompt
Navigate to the location you put the adb and fastboot commands
1) adb reboot
this command does exactly what it says. If you type it without any modifiers your phone will reboot. You can also reboot recovery or reboot bootloader.
2) adb push
Adb push is the command for putting a file on your device.
The format to use the command is adb push /filelocation/filename /destination the destination is usually /sdcard
3) adb pull
this command is how you get a file off of your phone
adb pull /file location the file will be downloaded to the location of your adb executable
4) Sometimes to help you troubleshoot a problem you may be asked to provide a logcat to someone. What this means is a log of the what is happening on the device. Getting one is easy
adb logcat > logcat.txt
this will create a logcat file and save it to the directory on your computer that you're running the adb commands from. To stop the logcat just use ctrl-c
Now on to fastboot
fastboot is a special mode on Android phones that allow system level partitions to be written or commands executed.
fastboot only works if your phone is in bootloader mode.
Once in bootloader mode
open a command prompt and navigate to where you installed the fastboot executable
You need fastboot to unlock your bootloader
fastboot flash unlocktoken Unlock_code.bin
and to relock it:
fastboot oem lock
you can also use fastboot to flash recoveries
fastboot flash recovery recovery.img use the filename of the recovery you downloaded.
If you've installed the 2.20 firmware from AT&T and you have root, you'll need to flash the kernel for any new rom separately using fast boot.
unzip the rom you've downloaded and locate the boot.img file and put it in the same directory as your fastboot and dab commands
reboot to bootloader then flash the kernel using the command fastboot flash boot boot.img. after hat you can boot into recovery right from the bootloader and install your rom.
These commands are just a few very basic ones.
There's no reason to be afraid of the command line or these tools.
I hope this quick and dirty tutorial helps someone.
If there's something else that can be explained here, feel free to add it to the thread and I'll add it to the OP.
you're right. nobody should be afraid of adb/fastboot commands or understanding WHY they are useful.
i would as far to say that if you dont understand basic adb/fastboot commands, then you have no business modding your phone....
You gotta add that they need to open a command line from the directory that has adb in it and type the commands from there.
_MetalHead_ said:
You gotta add that they need to open a command line from the directory that has adb in it and type the commands from there.
Click to expand...
Click to collapse
Oh yeah, duh
gunnyman said:
Oh yeah, duh
Click to expand...
Click to collapse
You're slackin'
I would go so far to say that this lack of comfort with adb/fastboot is the single largest contributor to the issues people have had in rooting and unlocking their HOXs over the last two months. Thanks for taking the time to put this together. Should help quite a few people unsure of adb/fastboot in general.
Another adb usage that may be helpful to add to this list is adb pull of user apps before updating ROM and then pushing them back. I have often seen people unsure of the best way to restore apps after a ROM upgrade. For me TiB works great, but you need to know what to restore via TiB and what to configure again manually. I think Scott posted the general steps in one of his CleanROM threads, but adding it to this list would be good too.
Just realized it's exactly two months since I received my pre-ordered HOX . No bricks, a superb HOX that I haven't had to warranty replace for any reason so far, and then comes along Scott with his fantastic CleanROM series. What a fun-filled ride it has been so far
Add adb logcat as well please, not enough people know how to use it
nice bro! this will come in handy for those that need it. i was there once! we all were. but good job man!
rohan32 said:
Add adb logcat as well please, not enough people know how to use it
Click to expand...
Click to collapse
Good call. Tomorrow I'll update it.
Done. Keep the suggestions coming. I know enough to get someone started, but I'm no developer.
I like this. Information that won't get old and everyone needs at one point or another. Nice call gunny.
Stickify!
this is great! excellent idea gunny
Oh yeah, stickied! :highfive: Too bad noobs still won't read it lol. They never read anything :silly:
_MetalHead_ said:
Oh yeah, stickied! :highfive: Too bad noobs still won't read it lol. They never read anything :silly:
Click to expand...
Click to collapse
Yeah but now we can be snarky and say "didn't you read the effing sticky???"
What about common connection issues?
Im facing one now
Funny you should say that. Your post made me realize it was missing.
So I'm getting a replacement One X from AT&T on July 19th and need to send my current phone back. I unlocked the bootloader and flashed ROM's on my current phone, so I should just follow this guide to return my phone back to stock before shipping it out to AT&T, correct?
Sent from my HTC One X using Tapatalk 2
acles003 said:
So I'm getting a replacement One X from AT&T on July 19th and need to send my current phone back. I unlocked the bootloader and flashed ROM's on my current phone, so I should just follow this guide to return my phone back to stock before shipping it out to AT&T, correct?
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
lock bootloader install RUU
done
Simple and awesome thread. Should help a lot of people.
This really helped me out before I became a member, thanks
Phone: Alcatel One touch POP 5036x
PC OS: Windows 8.1
Hello, I am Nick from Holland and I am 13 years old. My first post is a request for help, for which I apologize.
I recently bought my second mobile phone, which is my first smartphone/android device.
Quickly after I purchased it, I decided to root the apparatus and got into sudo-ing and that kind of stuff.
Now my phone is in a boot loop and I am unable to recover from it.
I have been searching and reading this forum for days now, and I just cannot figure out what to do.
I' m having trouble finding the right files ( Stock image, CWM and such ) for my particular model.
What happened before this mess:
I installed an anti-theft program called ' Prey'
To see how this worked, I flagged my device as missing. Nothing happened though, so I reverted its status to OK.
Later on I decided to delete some bloatware, and eventually I accidentally erased a file called ' Android System' or something like that.
I am not 100% sure about this particular name though, but I do know it sounded important.
My phone froze during the deletion process and I decided to take the battery out and do a reset.
Phone OFF
Power + Volume up
wipe cache partition
wipe data/factory reset
After which I ended up[ in this boot loop.
The phone boots past the android logo, and restarts during the blue Alcatel POP-C5 animation.
To make things worse, I looked in the ' Prey Control panel, and noticed my phone was still flagged as missing.
I remember I read something, somewhere about a security measure that involves being unable to simply remove Prey
by resetting the phone to its factory defaults.
My current status:
I installed the necessary USB drivers on my Windows 8.1 machine, and I am able to connect to my phone using ADB.
I am able to reboot into fastboot. (
Code:
ADB reboot-bootloader
)
I am able to transfer files and such using ADB
I have collected and properly configured the paths within windows to use the command line and downloaded (I think) all the necessary software. like Flash Tool, MTK Droid, the Android SDK, etc.
Code:
fastboot devices
resolves mt6572v1_phone fastboot
Some discrepancies:
Code:
adb devices
resolves the following data:
List of devices attached
0123456789ABCDEF sideload
Notice 1-to-9 and A-to-F. This seems weird to me.
Code:
get-state
and
Code:
get-devseria
l both resolve 'unknown'
Is there anyone willing/able to help me resolve my issues?
In return I can eventually make a new tutorial or Alcatel OT-5036x recovery thread.
I will try pulling the debug info and produce a logfile later on and upload them to my Google Drive.
Regards,
p011i3 said:
Phone: Alcatel One touch POP 5036x
PC OS: Windows 8.1
Hello, I am Nick from Holland and I am 13 years old. My first post is a request for help, for which I apologize.
I recently bought my second mobile phone, which is my first smartphone/android device.
Quickly after I purchased it, I decided to root the apparatus and got into sudo-ing and that kind of stuff.
Now my phone is in a boot loop and I am unable to recover from it.
I have been searching and reading this forum for days now, and I just cannot figure out what to do.
I' m having trouble finding the right files ( Stock image, CWM and such ) for my particular model.
What happened before this mess:
I installed an anti-theft program called ' Prey'
To see how this worked, I flagged my device as missing. Nothing happened though, so I reverted its status to OK.
Later on I decided to delete some bloatware, and eventually I accidentally erased a file called ' Android System' or something like that.
I am not 100% sure about this particular name though, but I do know it sounded important.
My phone froze during the deletion process and I decided to take the battery out and do a reset.
Phone OFF
Power + Volume up
wipe cache partition
wipe data/factory reset
After which I ended up[ in this boot loop.
The phone boots past the android logo, and restarts during the blue Alcatel POP-C5 animation.
To make things worse, I looked in the ' Prey Control panel, and noticed my phone was still flagged as missing.
I remember I read something, somewhere about a security measure that involves being unable to simply remove Prey
by resetting the phone to its factory defaults.
My current status:
I installed the necessary USB drivers on my Windows 8.1 machine, and I am able to connect to my phone using ADB.
I am able to reboot into fastboot. (
Code:
ADB reboot-bootloader
)
I am able to transfer files and such using ADB
I have collected and properly configured the paths within windows to use the command line and downloaded (I think) all the necessary software. like Flash Tool, MTK Droid, the Android SDK, etc.
Code:
fastboot devices
resolves mt6572v1_phone fastboot
Some discrepancies:
Code:
adb devices
resolves the following data:
List of devices attached
0123456789ABCDEF sideload
Notice 1-to-9 and A-to-F. This seems weird to me.
Code:
get-state
and
Code:
get-devseria
l both resolve 'unknown'
Is there anyone willing/able to help me resolve my issues?
In return I can eventually make a new tutorial or Alcatel OT-5036x recovery thread.
I will try pulling the debug info and produce a logfile later on and upload them to my Google Drive.
Regards,
Click to expand...
Click to collapse
You mention cwm.
Don't you have a backup?
Try google translating this thread: http://www.phonandroid.com/forum/carliv-recovery-cwm-6-0-4-4-pop-c5-et-x-pop-t81752.html
Lgrootnoob;50489116]You mention cwm.
Don't you have a backup?
Try google translating this thread: *link removed due restrictions*
Click to expand...
Click to collapse
I thank you for your kind answer.
No, I do not have a backup prior to my problem.
I have one now though, before things get worse.
I actually made some progress - I managed to correctly install and boot CWM.
I already stumbled upon and downloaded the files mentioned in your link.
The teXt translates as:
-put mobileuncle tools and recovery on your SD
mobileuncle-install and granted him the rights superSU
-click recovery update
-then recovery.img
clicked OK
-then it will ask to restart a recovery click OK
I downloaded the file called ' recovery.img' but I am unsure how to transfer it to my device and implement it.
Also, how do I install and run mobileuncle without being able to boot?
Regards,
EDIT:
Code:
C:\Users\Maya\Desktop>fastboot flash recovery recovery.img
sending 'recovery' (5522 KB)...
OKAY [ 0.217s]
writing 'recovery'...
FAILED (remote:
partition 'recovery' not support flash)
finished. total time: 0.242s
Install stock firmware anf stock rom and ur phone via Odin.... and ur phone will start as it was when u purchased it...
DeathNotice said:
Install stock firmware anf stock rom and ur phone via Odin.... and ur phone will start as it was when u purchased it...
Click to expand...
Click to collapse
Were do I find these for my Alcatel 5036x?
I searched for like four days without any definitive result.
p011i3 said:
Were do I find these for my Alcatel 5036x?
I searched for like four days without any definitive result.
Click to expand...
Click to collapse
Either try:
Code:
fastboot oem unlock
Or talk to the manufacturer.
They should actually provide source code since it is an android/linux OS.
Once you try these things we will move forward.
Lgrootnoob said:
They should actually provide source code since it is an android/linux OS.
Once you try these things we will move forward.
Click to expand...
Click to collapse
This is wrong. They are not required to provide the source code for the OS. Only the kernel is licensed under the gpl. The rest is closed sourced.
You will need to track down the default software for the device. Which maybe hard if not impossible as clone devices/MTK devices are based out of China and few if any have any after market support.
p011i3 said:
Were do I find these for my Alcatel 5036x?
I searched for like four days without any definitive result.
Click to expand...
Click to collapse
Search it on www.SamMobile.com......U may get ur stock rom and firmware on it
Lgrootnoob said:
Either try:
Code:
fastboot oem unlock
Or talk to the manufacturer.
They should actually provide source code since it is an android/linux OS.
Once you try these things we will move forward.
Click to expand...
Click to collapse
Code:
Windows PowerShell
Copyright (C) 2013 Microsoft Corporation. All rights reserved.
PS C:\Windows\system32> adb start-server
PS C:\Windows\system32> adb reboot-bootloader
PS C:\Windows\system32> fastboot oem unlock
...
And it just hangs there. (Tried 3 times and waited ~10minutes each.)
The cause of this is that I made things worse - yesterday I formatted the /system partition using CWM.
I did make a backup using Android Toolkiot first though, but again I am unsure how to recover it.
Also, I downloaded the files mentioned in the French I briefly discussed above.
I consists of almost all files listed in Flash Tool, except MOBILE_INFO, CACHE and USERDATA
The Alcatel Source code is hosted at Sourceforge under project name ' Alcatel'
zelendel said:
This is wrong. They are not required to provide the source code for the OS. Only the kernel is licensed under the gpl. The rest is closed sourced.
You will need to track down the default software for the device. Which maybe hard if not impossible as clone devices/MTK devices are based out of China and few if any have any after market support.
Click to expand...
Click to collapse
You are probably right. However, Alcatel actually does provide source code. See the ' Open Source' link at the bottom of the Alcatel website.
It is hosted at Sourceforge. Project name:: ' Alcatel'
I downloaded the the tar.gz archive earlier this week and extracted it, but I have no idea how to use this.
I am somewhat familiar with Linux though. I could set something up if I need to.
DeathNotice said:
Search it on SamMobile.com......U may get ur stock rom and firmware on it
Click to expand...
Click to collapse
I searched for ' 5036x' : " No entries found."
p011i3 said:
Code:
Windows PowerShell
Copyright (C) 2013 Microsoft Corporation. All rights reserved.
PS C:\Windows\system32> adb start-server
PS C:\Windows\system32> adb reboot-bootloader
PS C:\Windows\system32> fastboot oem unlock
...
And it just hangs there. (Tried 3 times and waited ~10minutes each.)
The cause of this is that I made things worse - yesterday I formatted the /system partition using CWM.
I did make a backup using Android Toolkiot first though, but again I am unsure how to recover it.
Also, I downloaded the files mentioned in the French I briefly discussed above.
I consists of almost all files listed in Flash Tool, except MOBILE_INFO, CACHE and USERDATA
The Alcatel Source code is hosted at Sourceforge under project name ' Alcatel'
You are probably right. However, Alcatel actually does provide source code. See the ' Open Source' link at the bottom of the Alcatel website.
It is hosted at Sourceforge. Project name:: ' Alcatel'
I downloaded the the tar.gz archive earlier this week and extracted it, but I have no idea how to use this.
I am somewhat familiar with Linux though. I could set something up if I need to.
I searched for ' 5036x' : " No entries found."
Click to expand...
Click to collapse
I did look at it and it is the part of the source code for the kernel and that's it
Bat cave One
zelendel said:
This is wrong. They are not required to provide the source code for the OS. Only the kernel is licensed under the gpl. The rest is closed sourced.
You will need to track down the default software for the device. Which maybe hard if not impossible as clone devices/MTK devices are based out of China and few if any have any after market support.
Click to expand...
Click to collapse
The kernel should be good enough though. (With modules)
---------- Post added at 10:41 AM ---------- Previous post was at 10:36 AM ----------
@p011i3 Hey, what version of android do you have.
YOu might be able to make a flashable zip if you have a working system img.
Or we could make a false cwm backup and just restore system only from that.
I managed to fully recover my Alcatel One Touch POP C5 5036X without having a backup for my own. I did this by formatting the entire device using Flash Tool and downloading the files from the French Website discussed earlier in this thread.
I'll post a 5036X recovery topic including all files later this weekend.
Again, I thank everyone for their kind help.
Not needed..............
@jmz will this work on OS 4.5.2
krazyace35 said:
@jmz will this work on OS 4.5.2
Click to expand...
Click to collapse
I don't see why it wouldn't as I am on 4.5.3 and it worked.
jmz said:
I don't see why it wouldn't as I am on 4.5.3 and it worked.
Click to expand...
Click to collapse
Cool thanks I'll give it a try and thanks for this unlock tutorial
jmz said:
You will need a linux box or python installed on windows. Find instructions on the web for that.
Step 1: Download attachment
Step 2: Run command and make note of code return
Code:
adb shell cat /sys/block/mmcblk0/device/manfid
Step 3: Run command and make note of code return
Code:
adb shell cat /sys/block/mmcblk0/device/serial
Now you should have 2 sets of numbers. first should be in the format of 0x0000XX where XX is numbers. And the other is 0xSSSSSSSS.
So now use the downloaded file and execute (obivously replacing the entries with what was returned above.
Code:
./cublock.py XX SSSSSSSS
This will tell you you have unlock.signed now. So move that to your fastboot/adb directory and then reboot to bootloader and issue this command
Code:
adb reboot-bootloader
fastboot -i 0x1949 flash unlock unlock.signed
Once done, get back to android and do the following:
Code:
adb shell
su
idme print
You should now see unlock_code: AAAAAAAA and on and on.
Now go flash my TWRP build in OG dev
Original credit goes to @dpeddi & @vortox for the exploit. I did nothing to this code and it is all their work. So give them thanks
Click to expand...
Click to collapse
Sorry for the noob-ish question. How do you get adb to recognize the fire? When I type "adb devices" there are no devices present.
ryanyz10 said:
Sorry for the noob-ish question. How do you get adb to recognize the fire? When I type "adb devices" there are no devices present.
Click to expand...
Click to collapse
do steps 1 through 6 in this thread
http://forum.xda-developers.com/fire-hd/general/root-supersu-stable-appstore-custom-t3113311
Question
Sorry for another question. When I type ./cublock.py, I get ". is not recognized as an internal or external command".
Sorry again for being annoying lol
ryanyz10 said:
Sorry for another question. When I type ./cublock.py, I get ". is not recognized as an internal or external command".
Sorry again for being annoying lol
Click to expand...
Click to collapse
if on windows you need to get python installed
jmz said:
if on windows you need to get python installed
Click to expand...
Click to collapse
I've got python 3.4.2 installed. Which version would you recommend?
After some researching, people have said that python doesn't work very well on Windows 10, which is what I'm on right now.
jmz said:
You will need a linux box or python installed on windows. Find instructions on the web for that.
Step 1: Download attachment
Step 2: Run command and make note of code return
Code:
adb shell cat /sys/block/mmcblk0/device/manfid
Step 3: Run command and make note of code return
Code:
adb shell cat /sys/block/mmcblk0/device/serial
Now you should have 2 sets of numbers. first should be in the format of 0x0000XX where XX is numbers. And the other is 0xSSSSSSSS.
So now use the downloaded file and execute (obivously replacing the entries with what was returned above.
Code:
./cublock.py XX SSSSSSSS
This will tell you you have unlock.signed now. So move that to your fastboot/adb directory and then reboot to bootloader and issue this command
Code:
adb reboot-bootloader
fastboot -i 0x1949 flash unlock unlock.signed
Once done, get back to android and do the following:
Code:
adb shell
su
idme print
You should now see unlock_code: AAAAAAAA and on and on.
Now go flash my TWRP build in OG dev
Original credit goes to @dpeddi & @vortox for the exploit. I did nothing to this code and it is all their work. So give them thanks
Click to expand...
Click to collapse
Hi jmz,
I have a question here- all that was in your ZIP file was the cublock.py file.
Are we supposed to use this with the rest of draxie's tools in the HDX thread? If so, I was able to get an 'unlock.img' file, but nothing called 'unlock.signed'
maybe you didn't upload all the attachments we needed?
either way, thanks soooo much for your work !
edouble312 said:
Hi jmz,
I have a question here- all that was in your ZIP file was the cublock.py file.
Are we supposed to use this with the rest of draxie's tools in the HDX thread? If so, I was able to get an 'unlock.img' file, but nothing called 'unlock.signed'
maybe you didn't upload all the attachments we needed?
either way, thanks soooo much for your work !
Click to expand...
Click to collapse
sorry, with that tool you only get the unlock.img . I need to correct the post
In my linux box 'cuber' module, required by cublock.py, is not installed; is this the correct source? https://github.com/benesch/cuber
One more question: I forgot to block OTA update so my HD6 updated to 4.5.4, loosing root permissions. What I should do? Need to wait KingRoot supports the new software version or can I proceed to unlock bootloader and install twrp? Or could install, if available, a 4.5.3 recovery through dd? Very thanks.
I sense many roms being ported very soon...
Sure hope so!
I used the tools (cuber) in this post:
http://forum.xda-developers.com/kin...tools-create-unlock-img-fix-boot-img-t3050689
So i generated unlock.img, but i am still unable to enter fastboot mode,
i tried changing boot to 4002, i rooted and tried to execute fastboot file, nothing works tbh, how do you suppose i fix this?
thanks in advance
robert896 said:
So i generated unlock.img, but i am still unable to enter fastboot mode,
Click to expand...
Click to collapse
Need more info: Your computer OS, tablet device model (Settings>Device Options), Fire OS version (Device Options>System Updates). Tell exactly what happens when you run: adb reboot-bootloader.
DoLooper said:
Need more info: Your computer OS, tablet device model (Settings>Device Options), Fire OS version (Device Options>System Updates). Tell exactly what happens when you run: adb reboot-bootloader.
Click to expand...
Click to collapse
ok im on ubuntu 15.04 got full adb and fastboot (they work on other devices) --- fire os 4.4.3---device model, kfhd 3rd gen
i also have windows 7 x64 dual booted with full adb and fastboot set up also
when i do adb reboot-bootloader, it restarts but doesnt enter fastboot ,, it boots into normal mode
robert896 said:
device model, kfhd 3rd gen
Click to expand...
Click to collapse
These unlock instructions are for Fire HDs (4th gen). You need a fastboot cable for KFSOWI. Try G+ KFSOWI modding.
I am new to the tablet scene. This is my very first tablet. I would like to root the device and install custom recovery and hopefully custom Rom. Is this the first thing I do or should I start somewhere else?
Hi
I have a Facetel q3pro android 10 tablet. I recently replaced the screen which inverted the x axis on the screen. I can't find any way to change the axis back so I want to root and try and fix myself. The problem is once I get into fastboot to unlock the bootloader the commands fail. Both oem unlock and flashing unlock. Am I missing something or is there another command or is the bootloader just not unlockable? If so is there a way to get around this bootloader issue?
To root a device's Android it's NOT required that device's bootloader gets unlocked before.
xXx yYy said:
To root a device's Android it's NOT required that device's bootloader gets unlocked before.
Click to expand...
Click to collapse
O really, is there a guide to do that? Or would i need a stock rom cuz im not able to find on of those?
Thanks for the reply
All what's needed is to extend the scope of existing Android OS functions by su - read: switch user - command, what by default is left off for security reasons.
This can get achieved by means of ADB.
xXx yYy said:
All what's needed is to extend the scope of existing Android OS functions by su - read: switch user - command, what by default is left off for security reasons.
This can get achieved by means of ADB.
Click to expand...
Click to collapse
So I've been trying to research what you're saying but not having much luck I've found a few commands such as going to shell then typing su, but says inaccessible or not found. I can pull user lists, and see commands for users but nothing about switching to su. I think I found the issue to solve my axis issue but it requires access to config.txt which is denied without root I believe. Sorry I'm not the most advanced these shell/adb commands
People who carefully read posts are certainly in advantage.