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
so i have managed to come across a couple of Imerj Blugroov phones its a concept dual screen dual core android phone running 2.3.4
looking for any information on changing the Rom to something newer. i have heard they were using the nexus firmware for testing.
model number comes up as : New Era DV21 (US)
i have only been able to find a Chinese site that mentions this phone but no other information anywhere.
contact for link
if anyone knows anything about these please contact me
kkrakker said:
so i have managed to come across a couple of Imerj Blugroov phones its a concept dual screen dual core android phone running 2.3.4
looking for any information on changing the Rom to something newer. i have heard they were using the nexus firmware for testing.
model number comes up as : New Era DV21 (US)
i have only been able to find a Chinese site that mentions this phone but no other information anywhere.
contact for link
if anyone knows anything about these please contact me
Click to expand...
Click to collapse
The device is based on Blaze board.
You have a root adb shell already. Start from Blaze from TI builds.
Quite late this post but
-Use it from Linux. Windows is not supported.
-Check dmesg when you plug in the USB. Check for vendor and device
-ID's and add the rules in /etc/udev/rules.d/51-android.rules
-You would need android tools, SDK as they were in 2010 and also fastboot
version from 2010 or 2011 (Ubuntu).
-unplugg the USB from the PC
-Hold the mute button while power on
(power and volume up or down would go to recovery mode, indicated by some vibrations)
-Release power when the circle LED lights up (some vibrations might occur)
-Release the MUTE circle LED turns off, menu shows on and back LED is on
-Plug the USB cable to PC
-type in a terminal
$sudo fastboot devices
Presume you have a build for Blaze Board ( Gingerbread) as it was back in 2010
$sudo fastboot flash bootloader u-boot.bin
$sudo fastboot erase environment
Power off the device
Hold the mute button while power on
Plug the USB cable in
Check if PC sees the device
$sudo fastboot devices
$sudo fastboot flash boot boot.img
$sudo fastboot flash recovery recovery.img
$sudo fastboot flash system system.img
$sudo fastboot flash userdata userdata.img
$sudo fastboot flash cache cache.img
$sudo fastboot erase environment
$sudo fastboot reboot
The device partition table is:
ptable 0 128KB mbr.bin Master Boot Record (MBR) for the eMMC device
xloader 0x100 128KB MLO.emu X-Loader bootloader
bootloader 0x200 256KB u-boot.bin U-Boot bootloader
environment 0x400 128KB env.txt U-Boot bootloader environment
boot 0x500 14MB boot.img Kernel and ramdisk
recovery 0x7500 14MB recovery.img Kernel and recovery ramdisk
system 0xFB04 768MB system.img Android system image
userdata 0x1900E6 1GB userdata.img Android data partition
cache 0x391DA9 1GB cache.img Android cache partition
media 0x593A6C remaining none Android SDCard partition
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
- There are some models when the faulty update will hang on fastboot because the previous recovery has been changed. Here my device uses the global NA rom and has rooted the device, and when I updated it from v1.18 to v1.20, when booting up the recovery system failed, I was taken to the fastboot screen and stopped at the fastboot screen.
*TUTORIAL:
- S1: Install driver zte+usb android and adb fastboot tool (if you haven't).
- S2: Copy file recovery.img (of rom global you use) to folder adb
- S3: Open folder adb and open cmd cd to folder adb and type command:
fastboot devices //Check if the device is connected, if not then review the driver
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash recovery recovery.img
fastboot reboot
Done
Start by downloading the official stock rom. If you had a problem with the installation or just want to go back to the original usage
Flash SP Tools
- download the latest version of Android sdk platform-tools
- Put in the platform-tools folder your boot.img and vbmeta.img that you have copied from your previously downloaded official rom.
- Then download the generic system image you want to install, put it in the platform-tools folder and rename it GSI.img
- Put your smartphone in developer mode, in the settings press 7 times on the build number
- In the menu Options for developers that appeared, you must enable OEM unlocking, enable USB debugging
- Connect the smartphone to the computer, in Configuration usb choose Connection sharing via usb
accept the requested authorization on your smartphone,
- In the platform-tools folder enter the command
adb reboot bootloader
fastboot flashing unlock Press VOL+ to confirm
fastboot flashing unlock_critical Press VOL+ to confirm
fastboot --disable-verification flash boot boot.img
fastboot --disable-verify flash vbmeta vbmeta.img
fastboot -w
fastboot reboot fastboot The tel switch to FastbootD mode and wait for a moment before entering the following command
fastboot delete system
fastboot delete-logical-partition product_a
fastboot --disable-verity --disable-verification system flash Gsi.img Wait for a moment
fastboot -w
fastboot bootloader
fastboot delete user data
fastboot reboot
Lenovo then logo rom gsi and install
evolutionx rom
Releases ยท ponces/treble_build_evo
Script and patches for building PHH-Treble Evolution X - ponces/treble_build_evo
github.com
rom lenovo and flashtool 616f
https://mirrors.lolinet.com/firmware/lenovo/Tab_P11_Plus/TB-J616F/TB-J616F_S240155_230210_ROW_SVC.zip
https://mirrors.lolinet.com/firmware/lenovo/Tab_P11_Plus/flashtool/MTK_Flash_Tool_v5.2104_P522.zip
Last tested rom that works
https://private.projectelixiros.com/thirteen/gsi/ProjectElixir_3.6_gsi-13.0-20230223-1108-OFFICIAL.img.xz
Root lenovo 616f
Install the Magisk app to your phone and install
In the Options menu, enable both the Preserve Force Encryption and Recovery Mode options.
Choose Select and Patch a file.
Browse to the extracted boot.img file and select it.
Magisk will now load the boot.img file and start patching.
Then the patched patched boot image file will be saved as magisk_patched.img in Internal Storage Downloads.
The file will be named as magisk_patched.img.
Transfer the magisk_patched.img file to the platform-tools folder.In the platform-tools folder enter the command
adb reboot bootloader
fastboot flash boot magisk_patched.img
fastboot reboot
successfully rooted
Magisk 25.2
https://github.com/topjohnwu/Magisk/releases/download/v25.2/Magisk-v25.2.apk
Can you make a video to review that rom on p11
It has only one flaw,
The PC does not recognize the tablet, it can only be charged, files cannot be transferred and adb does not work either.