I've been trying to replace the images in my Doogee X5pro with custom rom.
My host PC environment is:
Ubuntu 14.04.5 Trusty, 64bit
fastboot (using the one installed along with Android Studio SDK)
I have unlocked the bootloader ('fastboot oem unlock' and have checked the variable 'unlock=yes' with 'fastboot getvar all')
At this point, I tried to replace the images in the custom rom zip file.
However, I found that while boot.img, recovery.img is flashed without any problems,
when I try to flash system.img, cache.img, and other images, it simply returns an error(FAILED. unknown command)
BTW, i have the scatter file and have been adding the 'base address' option to every fastboot flash command.
(ex: 'fastboot flash boot boot.img -b 0x2de000000' , where I simply retrieved the base address of each partition from the scatter file).
Also, I have specified the '-S' option which will sparse the image file when the image file to be flashed exceeds the size specified with the '-S' option
(ex: 'fastboot flash system system.img -b 0x2f000000 -S 100M).
Could someone point me in the right direction to solve this issue?
Hi and welcome to assist,
Please see this thread about rooting your device here:
Root Doogee X5 Pro
I'm sure you will find an answer there.
Additional info: [Guide] How To Setup And Use Fastboot
Good luck
Related
I went ahead and did the oem unlock but when I try and flash the recovery (or boot) image through fastboot using this:
C:\androidsdk\tools\fastboot flash recovery XXXXXXX.img
or
C:\androidsdk\tools\fastboot flash boot rootboot.img
I keep getting this error:
error: cannot load 'XXXXXXX.img'
I've trouble shooted all of the main things. ...my device is definitely attached. I have the recovery .img file in the same folder as fastboot (along with the 2 needed .dll files). I've also done stuff like re-install usb drivers, re-install sdk, I've oem unlocked 3 times.
I have a stock wifi xoom with 3.2
Here are the 2 main root guides I've been using
http://forum.xda-developers.com/showthread.php?t=1170760&highlight=how+to+root
http://forum.xda-developers.com/showthread.php?t=1242241&highlight=how+to+root
Thank you for your help
in cmd(assuming windows) type cd c:/•••••tools
your xoom should be in adb reboot bootloader
type fastboot flash recovery recovery.img
rename recovery file as recovery.img and place in tools/platformtools as the case may be.
sending this message from stock xoom.
awesome, thanks. What you told me was enough to show me what I was doing wrong.
In case someone else reads this later on I had to type
cd C:\androidsdk\tools ...hit enter
then it looked like this
C:\androidsdk\tools> ...and I then typed
fastboot flash recovery XXXX.img
earlier I also renamed the folder to androidSDK from android-sdk
Hi there,
I'm new to all things development. I have an HTC Sensation on Virgin mobile in Canada. I am trying desperately to root my phone and I have followed this guide (http://forum.xda-developers.com/showthread.php?t=1632553). I've done lots of searching on this forum and google and can't find anyone with my specific problem.
I have put the SupperSU.zip file into my SD root, unlocked my bootloader through the HTC dev website and flashed CWM using the One X program. However, when I try to boot into recovery it stalls on the white HTC loading screen. I have tried to boot into recovery using One X, a command control from my android folder on my computer and using the power button and down volume button but it always stalls. Since I cant boot into recovery I cant use CWM flash the SuperSU.zip, which I understand finishes the rooting process.
Also: I am pretty sure my drivers are up to date but when I tried to install the drivers from One X it always interrupts the installer saying the Device is in Use...andnI dont know if that means my phone (which its not) or my computer. I uninstalled my antivirus because I read that might be blocking it... but still no luck!
I would really appreciate any help or guidance you can offer! I am a complete newbie when it comes to this and I have done my best to search out answers and tutorials before coming here for help.
reflash the recovery.img using the fastboot command(rename it as recovery.img)
fastboot flash recovery recovery.img then do
fastboot reboot bootloader
after that try to enter to recovery
note:i assume you know how to use fastboot commands
if you still can't enter to recovery then try this
place the recovery.img in the folder where you have adb and fastboot files
boot the device to bootloader and connect it to pc via usb(in the hboot screen must say fastboot usb)
open in the folder a cmd window and do
fastboot reboot recovery.img
rzr86 said:
reflash the recovery.img using the fastboot command(rename it as recovery.img)
fastboot flash recovery recovery.img then do
fastboot reboot bootloader
after that try to enter to recovery
note:i assume you know how to use fastboot commands
if you still can't enter to recovery then try this
place the recovery.img in the folder where you have adb and fastboot files
boot the device to bootloader and connect it to pc via usb(in the hboot screen must say fastboot usb)
open in the folder a cmd window and do
fastboot reboot recovery.img
Click to expand...
Click to collapse
Thanks for your advice! I just want to double check what you mean before I try anything.. Do you mean that I should rename the fastboot file to 'recovery.img' and then use the fastboot commands (by holding shift and right click on my android folder to open command folder)? I am really quite new an d I think I know how to use fastboot commands but I'm not positive. I'm not sure where to find the recovery.img file!
I'm a complete beginner and I'm really trying to understand this Thanks for being patient and helping!
kellai15 said:
Thanks for your advice! I just want to double check what you mean before I try anything.. Do you mean that I should rename the fastboot file to 'recovery.img' and then use the fastboot commands (by holding shift and right click on my android folder to open command folder)? I am really quite new an d I think I know how to use fastboot commands but I'm not positive. I'm not sure where to find the recovery.img file!
I'm a complete beginner and I'm really trying to understand this Thanks for being patient and helping!
Click to expand...
Click to collapse
exactly as you said
about recovery.img use the one from the guide you used to root the device(CMW 5.8.0.9 )
or check 4ext recovery from this guide
http://forum.xda-developers.com/showthread.php?t=1631861 (step 2)
rzr86 said:
exactly as you said
about recovery.img use the one from the guide you used to root the device(CMW 5.8.0.9 )
or check 4ext recovery from this guide
http://forum.xda-developers.com/showthread.php?t=1631861 (step 2)
Click to expand...
Click to collapse
So when I renamed my CMW recovery file as recovery.img and put it in my android folder, booted my phone into fastboot usb mode and connected it to my pc. I opened a command window from the android folder with the recovery.img file in it and typed fastboot reboot recovery.img all I got was this:
C:\android>fastboot reboot recovery.img
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
What should I do now? Thank you again!!
--
I also tried to open a command window there and reflash the recovery.img by typing fastboot flash recovery recovery.img ...except it said "error: "cannot load recovery.img" except the file is definitely in that folder and named recovery.img
kellai15 said:
So when I renamed my CMW recovery file as recovery.img and put it in my android folder, booted my phone into fastboot usb mode and connected it to my pc. I opened a command window from the android folder with the recovery.img file in it and typed fastboot reboot recovery.img all I got was this:
C:\android>fastboot reboot recovery.img
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
What should I do now? Thank you again!!
Click to expand...
Click to collapse
try this
fastboot boot recovery.img
rzr86 said:
try this
fastboot boot recovery.img
Click to expand...
Click to collapse
I tried that but it keeps saying - Cannot Load "recovery.img" and I know that the file is in the folder I'm opening the command window from and named recovery.img .
kellai15 said:
I tried that but it keeps saying - Cannot Load "recovery.img" and I know that the file is in the folder I'm opening the command window from and named recovery.img .
Click to expand...
Click to collapse
ok then flash it again with fastboot command
don't use the tool
then from bootloader select recovery
rzr86 said:
ok then flash it again with fastboot command
don't use the tool
then from bootloader select recovery
Click to expand...
Click to collapse
Sorry - can you explain exactly how and what I should flash again? I'm just a little unclear.
kellai15 said:
Sorry - can you explain exactly how and what I should flash again? I'm just a little unclear.
Click to expand...
Click to collapse
as you are in the folder with cmd window opened do
fastboot flash recovery recovery.img
fastboot reboot bootloader
then from bootloader select recovery
i assume you still have the recovery.img in the folder
rzr86 said:
as you are in the folder with cmd window opened do
fastboot flash recovery recovery.img
fastboot reboot bootloader
then from bootloader select recovery
i assume you still have the recovery.img in the folder
Click to expand...
Click to collapse
That worked!! I realized I had renamed the recovery file 'recovery.img' instead of just 'recovery)" (the second .img was redundant) which is why it wouldnt find the file. Anyway, it's rooted now!
You are the best! Thanks so much for helping a newbie out
kellai15 said:
That worked!! I realized I had renamed the recovery file 'recovery.img' instead of just 'recovery)" (the second .img was redundant) which is why it wouldnt find the file. Anyway, it's rooted now!
You are the best! Thanks so much for helping a newbie out
Click to expand...
Click to collapse
congratulations mate
but i suggest you to have 4ext recovery instead of cwm because of the smartflash feature(for S-ON devices only)
as i understand you are on S-ON
rzr86 said:
congratulations mate
but i suggest you to have 4ext recovery instead of cwm because of the smartflash feature(for S-ON devices only)
as i understand you are on S-ON
Click to expand...
Click to collapse
I have now flashed 4ext and installed a customROM! Couldn't have done it without your help
Hello All,
The main question is How to repack boot.img rightly? (I mean do we need to sign it or specify the some device related properties).
Please see my requisites:
1) Product Market Name: finepower C2
2) Chipset: Spreadtrum SC7731C
3) Android OS Version: 6.0
4) Boot/Recovery partition was updated successfully via fastboot utility if original image was used.
I'm using the following command that flash images on device: fastboot flash boot boot.img OR fastboot flash recovery recovery.img && fastboot reboot
but I got the constant vibration after "fastboot reboot" command (see details below how it was repacked).
I'm trying to use the all famous tools to pack it back: imgtool (Mac OS), abootimg (Ubuntu), mkbootimg (legacy android tool).
Ramdisk was packed via mkbootfs tool or within using abootimg.
Could you please guide me how to solve this issue?
Hi Team,
I was able to unlock the bootloader on motg3 and do a twrp img. However when I ran the command
adb reboot recovery it doesn't boot into the recovery img and it just says no command on the phone screen. Please help.
Thanks,
Arun
'No Command' means you've still got the stock recovery. Flash TWRP again by:
Code:
fastboot flash recovery twrp.img
(Where twrp.img is the filename of the custom recovery).
Do *not* reboot the phone into system, instead scroll down to select 'recovery' and press power button to load TWRP.
TWRP should load now, swipe to confirm modification (important). Now go to reboot>recovery. Allow the phone to reboot back to TWRP. Now you can select reboot>system and TWRP shall stick permanently.
Broadcasted from Zeta Reticuli
Volume buttons aren't working on the mobile. So I tried adb reboot recovery. But still it didn't boot into recovery. Here is what I had tried.
https://pasteboard.co/HhTTVr1n.png
TWRP will be overwritten by stock recovery if the system is booted up before booting TWRP once.
If the volume buttons are broken, then I'd suggest you first copy twrp.img into phone memory, boot the recovery by :
Code:
fastboot boot recovery.img
Allow modifications, then go to Install>Select Image (img), browse twrp.img on phone>select 'recovery' and swipe to flash.
Now reboot>recovery and then reboot>system. Now it should stick.
I'd recommend being extra careful if your volume button, especially volume down button is broken. If you somehow end up with a non-booting phone, you'd have no way (that I know of) to get to the bootloader mode.
Broadcasted from Zeta Reticuli
I tried fastboot boot recovery.img but it says waiting for device and nothing happens.
https://pasteboard.co/HhVmOD9.png
Make sure your phone is in the bootloader mode and is being recognized by the pc. Run:
Code:
fastboot devices
and make sure it returns with 1 entry of the device along with the text 'fastboot'. Then the command should work.
Broadcasted from Zeta Reticuli
arunkumar413 said:
Hi Team,
I was able to unlock the bootloader on motg3 and do a twrp img. However when I ran the command
adb reboot recovery it doesn't boot into the recovery img and it just says no command on the phone screen. Please help.
Thanks,
Arun
Click to expand...
Click to collapse
Make sure you have installed proper Motorola drivers & Fastboot on you're PC / laptop,
You can get those files from this thread https://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
After installing proper drivers goto this thread https://forum.xda-developers.com/2015-moto-g/orig-development/twrp-twrp-moto-g-2015-t3170537 download & flash latest twrp by given instructions by OP..
I just checked the usb drivers page but there aren't any usb drivers for Linux.
https://mobilesupport.lenovo.com/us/en/solution/MS88481
I tried the command sudo fastboot boot recovery.img and it returned there is no such file or directory. Should recovery file be on phone or on the laptop. Also should all these commands be run from a specific folder either on phone or system?
[email protected] ~ $ sudo fastboot boot recovery.img
cannot load 'recovery.img': No such file or directory
[email protected] ~ $
arunkumar413 said:
I just checked the usb drivers page but there aren't any usb drivers for Linux.
https://mobilesupport.lenovo.com/us/en/solution/MS88481
I tried the command sudo fastboot boot recovery.img and it returned there is no such file or directory. Should recovery file be on phone or on the laptop. Also should all these commands be run from a specific folder either on phone or system?
[email protected] ~ $ sudo fastboot boot recovery.img
cannot load 'recovery.img': No such file or directory
[email protected] ~ $
Click to expand...
Click to collapse
Yes, the terminal should be open to the directory containing the recovery.img file. For simplicity, place twrp into your home folder. The default location for most terminals is home, so no worries about directory now.
Just to be sure, type in :
Code:
ls
(LS lowercase)
Your file should be in the list. You are ready to flash now.
Try the fastboot boot command again.
As you're using GNU/Linux (guessed it early from your screenshots), drivers should not be a problem, at least for this device; unless you are running a minimal or highly customised distro like Gentoo or Arch.
Note: And yes, you'll need another copy of TWRP inside phone storage to actually flash into the device, the PC one is just used to boot temporarily into TWRP.
Broadcasted from Zeta Reticuli
To add more clarity. There are two files here:
1) recovery.img
2)twrp.img
I was able to get the twrp.img file but where do I get the recovery.img file?
Hi All,
Thanks for all the help. I'm now able to root into the device.
arunkumar413 said:
To add more clarity. There are two files here:
1) recovery.img
2)twrp.img
I was able to get the twrp.img file but where do I get the recovery.img file?
Click to expand...
Click to collapse
I apologize for confusing you. They are the one and same. Just rename the downloaded TWRP img file to twrp.img and copy it over to both home folder in pc and into phone.
Use fastboot boot command on pc to temporarily boot up twrp in phone, allow modifications by swiping, go to Install>Install Image (img) option on the bottom>select the twrp.img inside the phone and flash it to 'recovery' partition.
Now reboot>recovery. This time the twrp should be permanently flashed and working properly. You are done.
Edit: Didn't see your last post, glad that you worked it out
Broadcasted from Zeta Reticuli
arunkumar413 said:
To add more clarity. There are two files here:
1) recovery.img
2)twrp.img
I was able to get the twrp.img file but where do I get the recovery.img file?
Click to expand...
Click to collapse
There can be only one either recovery.img file or twrp.img.....as you are trying to replace your stock recovery by TWRP... And you need .img file for this.... Just check the name there should be just one if you have TWRP.img then there is no need for recovery.img file
Hi All,
After I was able to flash twrp and root into the phone I switched off the phone and turned on after couple of days. But now the display isn't turning on. However adb is able to detect the device and also I was able to access the file system through usb. Could you please help me troubleshoot the display issue?
arunkumar413 said:
Hi All,
After I was able to flash twrp and root into the phone I switched off the phone and turned on after couple of days. But now the display isn't turning on. However adb is able to detect the device and also I was able to access the file system through usb. Could you please help me troubleshoot the display issue?
Click to expand...
Click to collapse
Try rebooting into the recovery mode by:
Code:
adb reboot recovery
And doing a Cache/ART cleanup.
If the phone boots up (it should vibrate) but the screen doesn't light up (not even a blank dark grey screen), then I'm afraid the display is at fault.
How to root moto g3
I try to root my motor but network has gone
Then how I root
Hello, i want to reactivate my old acer A701 by flashing a newer img or zip.I have the following problems.When I try to do the recovery with a zip file on an sdcard i get the prop error.When i try to flash it by an img i always get i haven set the ANDROID_PRODUCT_OUT even when I do an export ANDROID_PRODUCT_OUT=/home/leopold/platform-tools.
A printenv shows the ANDROID_Product_OUT and the img is in platform-tools.
What is going wrong, what can i do?
You either apply Flash zip from sd from within Android's Recovery menu or you use external ADB Sideload command to flash a properly signed ZIP-file what contains the ROM, or you use external Fastboot Flash command to flash an IMG-file what requires device's bootloader is unlocked.
Hello and thank you,
like i wrote above, i want to flash it.Now i found at another place i have to write:
sudo ANDROID_PRODUCT_OUT="./" fastboot flashall recovery Az.img
when i do that, the flash is starting but then i get the error android-info.txt is missing.
So i guess i have a wrong image.
Does anybody have an image for the A701 with a newer android version.Or can give me a link.
My 4.1.1 does not recognice newer apps.
leopold
Take note that
Code:
fastboot flashall <ROM.IMG>
is to be used to flash a complete ROM, whereas
Code:
fastboot flash recovery <RECOVERY.IMG>
is to be used to flash only a Recovery.
Ok, i understand but i m lost.
I have some imagees and some zip files what should work on my a701.
If I use fastboot with img, i get no android-txt found.
if I work with adb reboot recovery and the zip files I will allways get the partition error prop undefined.
Can I supress the search for the android -txt?
What else can I do?
one of the zip files is from here https://acer.shreps.fr/, it is the said stable kitkat.
If you have access to a Windows computer then make use of a Flash Tool what's suitable to the tablet.
Unfortunately i can not find a flashtool for the nividia tegra3.
I have some zip files what should work on the a701 but all have the error check partition size [-Prop_UNDEFINED-) then the installation will be aborted.
Is there a way to eliminate the partition check.
Or does somebody have a zip or an img with a working update or recovery for a recent Android working on the a701?