Database Develop

[RecoveryMenu] CWM based Recovery menu to enter stock or CWM recovery

CWM based Recovery menu for Huawei U9000 Ideos X6 phone
[which is also known as CherryMobile Magnum, Wellcomm A99, Spice CSL Mi 410]
{
"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"
}
[Features Working]
Boot into Clockworkmod recovery [stably ]
Boot into stock recovery [stably ]
ADB recovery support
[Requirements]
One of these mobiles: CherryMobile Magnum, Wellcomm A99, Spice CSL Mi 410etc. (with any ROM installed, rooted / un-rooted)
USB data cable / Working CWM recovery
[Installation Instructions][Using CWM recovery]
Copy recovery_menu_v2.0.0.1_signed.zip in sdcard
Boot into recovery (Steps are given below for how-to-boot-into-recovery)
Use "install zip from sdcard" option
Locate and choose recovery_menu_v2.0.0.1_signed.zip from sdcard for instllation
After installation reboot into recovery (advanced > Reboot recovery)
[Using USB cable]
Extract recovery.img from recovery_menu_v2.0.0.1_signed.zip
Power off your phone. Now press Volume UP + Power button to enter in Download mode (Please keep Volume UP button pressed for a second before pressing Power button)
Connect your phone to PC via USB and wait until USB-Storage device appears on your PC (In Linux, you might see loads of new devices being mounted. But we are concerned about the device with name as 'FIH')
Replace file recovery.img inside the folder image (In windows, X:\image\, where X is drive letter for new USB device)
Safely remove USB device to ensure complete file copy
Disconnect phone from PC
Remove battery of your phone to power off and then start it again.
[Instructions to boot into recovery][Using ADB]
If your phone is up and running then connect it to PC
Issue following command through terminal / Command prompt
Code:
adb reboot recovery
​[Without PC - Using your phones hardware keys]
Power off your phone
Now press Volume UP + Volume DOWN + Power (As said before, please press Volume keys for a second before pressing Power button)
The phone will take few seconds (5 - 10 secs) to boot into recovery mode (It will show splash screen before booting into recovery)
[Navigation]
(Same as CWM recovery)
Select = Power & Search
Move Up = Home & Vol-Up
Move Down = Menu & Vol-Down
Back = Back
[Releases]
recovery_menu_v1.0.0.1 (Options for Android System recovery <3e> and CWM based recovery 4.0.1.4) [Download Link1] [Download link2 for MIUI/CM]
recovery_menu_v1.0.0.2 (Fixed support for ext4 filesystem - problems related to MIUI and CM ROM releases) [Download link]
recovery_menu_v2.0.0.1 (Options for Android System recovery <3e> and CWM based recovery 5.0.2.3) [Download link]
[Problems]
Not that I know of.
[Disclaimer]
I am not to be held liable/responsible if you damage your phone by following/not following this thread.
[Acknowledgement]
DooMLoRD for patiently helping me out with all my doubts
koush for his CWM bootable recovery sources.
[For developers]
I will push my sources on github soon. ​

reserved for future use

thanks..
pls port newer cwm 5.xx to our phone its already available for some devices..and ask koush to add our existing cwm to cwm manager... for easy flashing

flashing possible??
i dont think it is possible to flash the recovery image to where it needs to be and also these are built very similar to samsung and how they built the stock recovery in the /system partition

Napstar said:
CWM based Recovery menu for Huawei U9000 Ideos X6 phone
[which is also known as CherryMobile Magnum, Wellcomm A99, Spice CSL Mi 410]
[Features Working]
Boot into Clockworkmod recovery [stably ]
Boot into stock recovery [stably ]
ADB recovery support
[Requirements]
One of these mobiles: CherryMobile Magnum, Wellcomm A99, Spice CSL Mi 410etc. (with any ROM installed, rooted / un-rooted)
USB data cable / Working CWM recovery
[Installation Instructions][Using CWM recovery]
Copy recovery_menu_v1.0.0.1_signed.zip in sdcard
Boot into recovery (Steps are given below for how-to-boot-into-recovery)
Use "install zip from sdcard" option
Locate and choose recovery_menu_v1.0.0.1_signed.zip from sdcard for instllation
After installation reboot into recovery (advanced > Reboot recovery)
[Using USB cable]
Extract recovery.img from recovery_menu_v1.0.0.1_signed.zip
Power off your phone. Now press Volume UP + Power button to enter in Download mode (Please keep Volume UP button pressed for a second before pressing Power button)
Connect your phone to PC via USB and wait until USB-Storage device appears on your PC (In Linux, you might see loads of new devices being mounted. But we are concerned about the device with name as 'FIH')
Replace file recovery.img inside the folder image (In windows, X:\image\, where X is drive letter for new USB device)
Safely remove USB device to ensure complete file copy
Disconnect phone from PC
Remove battery of your phone to power off and then start it again.
[Instructions to boot into recovery][Using ADB]
If your phone is up and running then connect it to PC
Issue following command through terminal / Command prompt
Code:
adb reboot recovery
​[Without PC - Using your phones hardware keys]
Power off your phone
Now press Volume UP + Volume DOWN + Power (As said before, please press Volume keys for a second before pressing Power button)
The phone will take few seconds (5 - 10 secs) to boot into recovery mode (It will show splash screen before booting into recovery)
[Navigation]
(Same as CWM recovery)
Select = Power & Search
Move Up = Home & Vol-Up
Move Down = Menu & Vol-Down
Back = Back
[Problems]
Not that I know of.
[Disclaimer]
I am not to be held liable/responsible if you damage your phone by following/not following this thread.
[Acknowledgement]
DooMLoRD for patiently helping me out with all my doubts
koush for his CWM bootable recovery sources.
[For developers]
I will push my sources on github soon. ​
Click to expand...
Click to collapse
do we need to copy META INF FOLDER TOO?

Napstar said:
reserved for future use
Click to expand...
Click to collapse
Now that's what i call a really useful tool thanx a ton

nitindeck said:
thanks..
pls port newer cwm 5.xx to our phone its already available for some devices..and ask koush to add our existing cwm to cwm manager... for easy flashing
Click to expand...
Click to collapse
I will post it today if I am successful!

bandukia said:
do we need to copy META INF FOLDER TOO?
Click to expand...
Click to collapse
[Complete zip file for CWM based installation]
I guess here everyone must have working CWM recovery on their device. In that case just place the downloaded recovery_menu_v1.0.0.1_signed.zip file in your sdcard and install it using CWM recovery's "install zip from sdcard" option.
[Only recovery.img file for USB based instalation]
Otherwise just extract recovery.img from the zip file and replace it from /image folder that you will find in USB device that gets loaded when you conect your phone to PC in download mode.

snakebitezz said:
i dont think it is possible to flash the recovery image to where it needs to be
Click to expand...
Click to collapse
Do you mean flashing using CWM recovery. In that case, I have not flashed recovery.img like we do for boot.img
I have just extracted it to FIH partition. You can check my updater script in META-INF/google/android/updater-script file from zip
snakebitezz said:
and also these are built very similar to samsung and how they built the stock recovery in the /system partition
Click to expand...
Click to collapse
Sorry, I did not understand what you wanted to say. Can you please elaborate?

napstar you still havent replied my pm

huh this is a thing which deserve THANX more then eating my food ,,, guys before u download first thank the person who is behind it ... Jai ho Napstar Hats off to u

kshitij_bhatt said:
huh this is a thing which deserve THANX more then eating my food ,,, guys before u download first thank the person who is behind it ... Jai ho Napstar Hats off to u
Click to expand...
Click to collapse
Thanx for your complement!!

I have one bug to report. On latest MiUi your latest CWM will not mount /system.

Sergekarol said:
I have one bug to report. On latest MiUi your latest CWM will not mount /system.
Click to expand...
Click to collapse
Well, any ROM / FW should not bother CWM's activity. They function independent of each other.
Anyway, I will try new MIUI tomorrow as I cant download it now at my home with low bandwidth.
By the way can you send me the log files for recovery. (/cache/recovery/).
And also what exactly were you trying to do when this error occurred?

Napstar said:
Well, any ROM / FW should not bother CWM's activity. They function independent of each other.
Anyway, I will try new MIUI tomorrow as I cant download it now at my home with low bandwidth.
By the way can you send me the log files for recovery. (/cache/recovery/).
And also what exactly were you trying to do when this error occurred?
Click to expand...
Click to collapse
No problems Here is the zipped file. Its strange that mounting /data has no issues. I was installing an update zip that needed /system mounted. BTW It wouldn't make a backup either. I am restoring my old Andro-id RC2 and starting over tomorrow. I can help you then. After I restored the old backup it started working again. Maybe it was a phone issue.

Sergekarol said:
No problems Here is the zipped file. Its strange that mounting /data has no issues. I was installing an update zip that needed /system mounted. BTW It wouldn't make a backup either. I am restoring my old Andro-id RC2 and starting over tomorrow. I can help you then. After I restored the old backup it started working again. Maybe it was a phone issue.
Click to expand...
Click to collapse
Sorry to quote myself but I have a workaround to post. It seems to be a common MIUI issue and here is a workaround. Hook up your usb cable and using adb devices to start up server issue this command while in the CWM menu
Code:
adb shell mount /dev/block/mmcblk0p7 /system
The system then is mounted and you can backup you MiUi system. or install updates that need the /system mounted. perhaps you can figure out why it failed using this info.

There must be some issue with fstab...
Or u can always use ensure partition mount OR _system

Sergekarol said:
Sorry to quote myself but I have a workaround to post. It seems to be a common MIUI issue and here is a workaround. Hook up your usb cable and using adb devices to start up server issue this command while in the CWM menu
Code:
adb shell mount /dev/block/mmcblk0p7 /system
The system then is mounted and you can backup you MiUi system. or install updates that need the /system mounted. perhaps you can figure out why it failed using this info.
Click to expand...
Click to collapse
DooMLoRD said:
There must be some issue with fstab...
Or u can always use ensure partition mount OR _system
Click to expand...
Click to collapse
As rightly pointed out by DoomLoRD, there is a problem with fstab for MIUI OS.
Since Cyanogenmod and MIUI releases for our devices support ext4 filesystem and has there /system partition formatted with ext4 type, it prevents CWM to mount /system partition.
This is because our stock/official ROMs have /system partition of ext3 type and CWM is designed by keeping that in mind.
I have uploaded a modified CWM based recovery menu for MIUI and CM users in the first post. Please use it when you are on those ROMs. And make sure to install appropriate recovery_menu immediately after installing any type of ROM.
P.S. The update.zip that you were trying to install was not supported for our device. Please make sure compatibility of any softwares/apps before installing if you are not using Android market. I have attached a modified version of it (ESRight.v4-1.9.9.zip) with this post.

Napstar said:
As rightly pointed out by DoomLoRD, there is a problem with fstab for MIUI OS.
Since Cyanogenmod and MIUI releases for our devices support ext4 filesystem and has there /system partition formatted with ext4 type, it prevents CWM to mount /system partition.
This is because our stock/official ROMs have /system partition of ext3 type and CWM is designed by keeping that in mind.
I have uploaded a modified CWM based recovery menu for MIUI and CM users in the first post. Please use it when you are on those ROMs. And make sure to install appropriate recovery_menu immediately after installing any type of ROM.
P.S. The update.zip that you were trying to install was not supported for our device. Please make sure compatibility of any softwares/apps before installing if you are not using Android market. I have attached a modified version of it (ESRight.v4-1.9.9.zip) with this post.
Click to expand...
Click to collapse
Yea I knew it wasn't compatable but I knew a workaround but the workaround failed. Sorry Thanks for fixing

Sergekarol said:
Yea I knew it wasn't compatable but I knew a workaround but the workaround failed. Sorry Thanks for fixing
Click to expand...
Click to collapse
One more fix on its way.
Features included:
No need of switching between two different Recovery_menu. (Compatible for all ROMs)
Newer version of CWM Recovery v5.0.2.3 included
In testing stage...
Will upload in some time..

[Unofficial][Recovery][Ideos X6] CWM Recovery v5.0.2.7 with Touch menu support

Full touch supported Clockworkmod Recovery v5 for Huawei U9000 Ideos X6 phone
which is also known as CherryMobile Magnum, Wellcomm A99, Spice CSL Mi 410
{
"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"
}
​
[Features Working]
Full Touch Panel support for menu navigation
Touch gesture support added for Go back and page up/down actions
ICS like menu buttons as an added option for menu navigation
All harware keys functionality retained.
Advanced Backup option for backing up in either TAR or IMG format. (Might be useful for Custom ROM developers using dsixda's kitchen)
Restore
Install From Zip
ADB recovery support
Mounting sd card as USB storage device from recovery
[Requirements]
One of these mobiles: CherryMobile Magnum, Wellcomm A99, Spice CSL Mi 410etc. (with any ROM installed, rooted / un-rooted)
USB data cable
[ Downloads]
Full Touch supported CWM based recovery v5.0.2.7
CWM based recovery v5.0.2.7
[Installation Instructions][Using CWM recovery]
Copy CWM recovery-fb0-v5_signed.zipin sdcard
Boot into recovery (Steps are given below for how-to-boot-into-recovery)
Use "install zip from sdcard" option
Locate and choose CWM recovery-fb0-v5_signed.zip from sdcard for instllation
After installation reboot into recovery (advanced > Reboot recovery)
[Using USB cable]
Extract recovery.img from CWM recovery-fb0-v5_signed.zip
Power off your phone. Now press Volume UP + Power button to enter in Download mode (Please keep Volume UP button pressed for a second before pressing Power button)
Connect your phone to PC via USB and wait until USB-Storage device appears on your PC (In Linux, you might see loads of new devices being mounted. But we are concerned about the device with name as 'FIH')
Replace file recovery.img inside the folder image (In windows, X:\image\, where X is drive letter for new USB device)
Safely remove USB device to ensure complete file copy
Disconnect phone from PC
Remove battery of your phone to power off and then start it again.
[Instructions to boot into recovery][Using ADB]
If your phone is up and running then connect it to PC
Issue following command through terminal / Command prompt
Code:
adb reboot recovery
​[Without PC - Using your phones hardware keys]
Power off your phone
Now press Volume UP + Volume DOWN + Power (As said before, please press Volume keys for a second before pressing Power button)
The phone will take few seconds (5 - 10 secs) to boot into recovery mode (It will show splash screen before booting into recovery)
[Navigation]
[Touch inputs]​
Use touch panel buttons at the bottom of screen for navigations.
Hover finger over menu buttons on screen and lift your finger on desired selection when it gets highlighted.
Use touch panel's back or device key's back button for return action.
Check out this video to know how about.
[Device keys]​
Select = Power & Search
Move Up = Home & Vol-Up
Move Down = Menu & Vol-Down
Back = Back
Please refer to his post and image for for more details.
http://forum.xda-developers.com/showpost.php?p=16248065&postcount=426
Originally Posted by tj_style
​
[Problems]
Currently gesture support is not included for menu navigation.
Same issue with using "USB Safely remove" option. Please refer to this thread for possible solutions. [Unofficial][Recovery][Ideos X6] CWM Recovery 4.0.1.4 [Update]
Beware, some of your earlier Backups might just show md5sum mismatch. [happened with me] So just keep earlier recovery update.zip in /sdcard, just in case.
The backup format for this recovery is .tar and not .img, this is done [not by me, by koush and CWM developers ] to reduce size of each backup. So, backup generated by using this version are not supported by earlier Recovery releases. But this release can use earlier releases' backup.
[Disclaimer]
I am not to be held liable/responsible if you damage your phone by following/not following this thread.
[Acknowledgement]
koush for his CWM bootable recovery sources.
Steam recovery sources by SteamMOD for touch input related modifications.
k1chy for testing this touch based CWM recovery on his ideosX6 device. (Since my device is bricked right now, I can not test it )
P.S.: I have purposefully kept same format as for my older post of CWM Recovery v3, so that it will be helpful for any new user to grasp everything at single place.

wats the change log

bandukia said:
wats the change log
Click to expand...
Click to collapse
Well I am not the right person to tell that, as I am not the developer of CWM recovery. Its Koush.
I have just ported it to our device.
Anyway to tell you few points that I found out:
Major change for our device is support for backup in tar format. (Size reduction of the backup files)
Support for firmware update check and its installation. (If you did ota update and phone restarted in recovery for the same, I guess) - NOT for our device
Support for zip installation from internal SDcard. (Avalable in few devices) - NOT for our device
Few comsetic changes during backup and recovery that you might have noticed.
And few changes in recovery log file.
You can find these out by yourself by looking at sources modifications at: https://github.com/CyanogenMod/android_bootable_recovery/commits/gingerbread/

Initial Test
Ok...set this up on my device:
1. Backup works fine (in tar format now)
2. Restore Works fine
3. Format/Wipes work fine
4. Didnt see much difference from functionality standpoint though...
Will definitely update if something fails or creates a problem
Thanks a lot for this....

cant mount the sdcard from recovery and get it available on windows
adb support ? what it means as i couldnt get the "adb devices" to show the device yet
may be am doing something wrong
i made a back up with this recovery and Tj sirs recovery failed to restore ?? is that normal ?
thanks

zailer said:
cant mount the sdcard from recovery and get it available on windows
adb support ? what it means as i couldnt get the "adb devices" to show the device yet
may be am doing something wrong
i made a back up with this recovery and Tj sirs recovery failed to restore ?? is that normal ?
thanks
Click to expand...
Click to collapse
This recovery's backup is in tar file format for non boot partitions, as its mentioned in few posts before. So the backup created by this re overy can not be used with earlier versions of recovery.
And for adb, is your device detected when it is booted into any ROM. I mean have installed drivers correctly.
For USB mounting, select mount USB storage in mounting menu. And remain in that menu untill you are done with USB usage.
Sent from my CSL-MI410 using XDA App

OK that was one info i might have missed .. about the .tar format! thanks for stressing it again
but about the other two advices .. i have my phone detected by all other roms ..yes ...thats how i could fix its looping at corrupted boot animation yesterday?(mentioned in another post ) so i guess its some other issue .. since its not worked with the combined recovery version too (stock and v5.0.x.x) ..any guess whats happening ??
about mounting and unmounting .. i stayed in the "mounted" state for 10 minutes and still it didnt show up on the pc. but with other clockwork i guess its again urs 0ne with orange colour i get this working so easily .
thanks for immediate response and thanks for these great releases i really like the details shown (each file name its backing up and restoring ) really cool

zailer said:
but about the other two advices .. i have my phone detected by all other roms ..yes ...thats how i could fix its looping at corrupted boot animation yesterday?(mentioned in another post ) so i guess its some other issue .. since its not worked with the combined recovery version too (stock and v5.0.x.x) ..any guess whats happening ??
about mounting and unmounting .. i stayed in the "mounted" state for 10 minutes and still it didnt show up on the pc. but with other clockwork i guess its again urs 0ne with orange colour i get this working so easily .
Click to expand...
Click to collapse
I really dont know the reason behind the problem. Try re-installing any of the latest recovery.
Sent from my CSL-MI410 using XDA App

Released new version of CWM recovery with touch support for menu navigations.
A brief intro:

Napstar said:
Released new version of CWM recovery with touch support for menu navigations.
A brief intro:
Click to expand...
Click to collapse
Its really good.
Thx for update....!!
Sent from my CSL-MI410 using xda premium

Napstar said:
Released new version of CWM recovery with touch support for menu navigations.
A brief intro:
Click to expand...
Click to collapse
hi
very nice and interesting uv been missing for a long time welcome back buddy
ur back with a bang buddy

Really good programming, much easier to use. My only suggestion is to make the bars wider. I have big fingers.

Sergekarol said:
Really good programming, much easier to use. My only suggestion is to make the bars wider. I have big fingers.
Click to expand...
Click to collapse
My changes are developer friendly. What i mean by that is, if you know how to extract and re-pack recovery.img file for our device then you can just replace button.png and button-sel.png to your choice. Graphical menu will adjust itself.
Anyway, i will release a separate version too, so as to make this process more friendly.
Sent from my CSL-MI410 using XDA App

this is really great.. this really solves the problem if one wants / needs to navigate thru CWM recovery in low light or no light conditions. bcoz in recovery mode the soft buttons do not glow. great man Napster!!!

Hi Napstar... Good work! Hows about your dual recovery using recovery menu, stock and this new one.

CacingKalung said:
Hi Napstar... Good work! Hows about your dual recovery using recovery menu, stock and this new one.
Click to expand...
Click to collapse
Recovery menu and Boot Menu are next in line.
But before that I am working on adding this touch support for Samsung Galaxy SL I9003 device that I have.

GreAt done napstar! But how about usb disk in recovery do? and if I install this cwm update there is the way to back to previous version of cwm to flash my old backups?

dtbang721 said:
GreAt done napstar! But how about usb disk in recovery do? and if I install this cwm update there is the way to back to previous version of cwm to flash my old backups?
Click to expand...
Click to collapse
Sorry, I did not follow what you meant by "usb disk in recovery".
Regarding restoring old backups, this recovery supports any backup from last releases. (backward compatibility).
Anyway, just for the sake of convenience I have retained older release in my first post attachments. So anyone can revert back to older release if they want.

dtbang721 said:
GreAt done napstar! But how about usb disk in recovery do? and if I install this cwm update there is the way to back to previous version of cwm to flash my old backups?
Click to expand...
Click to collapse
Just retain / copy (if you have a backup on your computer) clockworkmode folder in your SD card along with the old ROM backups. This cwm will simply take the backup and restore. Worked for me !

hihihi changed the pngs to one i liked bt gesture got disturbed sorry was jst try to mess it up lolz back to ur build
nd thank got it didnt get bricked this time ... i dont think they gonna replace it for this time (actually if it gets bricked it will be 3rd time )

DX ezSBF & Root 2.3.4/4.5.621

root created by phifc, original ezSBF by 1kds, and modified by bhigham
ezSBF and root cd
Droid_X_621-ezSBF-and-RootCD.iso (225MB) MD5: c4961b5b93aa1b2881023d3f3e3f4ea4
Dev-Host - Droid_X_621-SBF-and-RootCD.iso - The Ultimate Free File Hosting / File Sharing Service
Download Droid_X_621-SBF-and-RootCD.iso from Sendspace.com - send big files the easy way
https://docs.google.com/file/d/0B1hcBgk_03_aS0hldl94Zzd3WjQ/edit?usp=sharing
​How to verify the file was downloaded correct with
MD5/SHA-1 Hash Checksums
Root Only option
Droid2_D2G_DX_DX2-RootCD-2012.iso(54mb)md5 Hash:7BAEE9C34F6EF7AD0B4FA219AE387C68
Droid2_D2G_DX_DX2-RootCD-2012.iso
https://rapidshare.com/files/1493446314/Droid2_D2G_DX_DX2-RootCD-2012.iso
https://docs.google.com/file/d/0B1hcBgk_03_aU1Bpc0VuQUJfQnc/edit
what is ezSBF?
original [TOOL] ezSBF (not for 2.3.4)
1KDS said:
Don't let the word Linux scare you, this is just a cd you burn, nothing installs to your pc. Once you burn this CD you are ready to SBF flash anywhere you have a computer, no net connection needed to download any files.
This is an .iso file. It is a complete Linux operating system that you will download, burn to CD (or USB) then boot your pc from CD or USB, this allows your pc to reboot into a different operating system.
Click to expand...
Click to collapse
1KDS said:
Instructions (Mac):
Download .iso
Use Disk Utility (built in) to burn iso file to a CD (instructions)
Shut computer down
Hold c key, push power and hold c until you see the Linux OS start
Hit enter at the yellow "boot baby... boot" screen
You will see yellow dots for 3-5 minutes then the script will start
Instructions (Windows):
Download .iso
Burn iso image to a disk (Instructions, Windows 7 - Vista and XP)
Reboot PC
Hit F12 (sometimes F8 or esc) during boot to go to boot menu (possibly google search how to boot your specific pc from CDROM)
Select boot from CDROM (or USB if you used a flash drive)
Hit enter at the yellow "boot baby... boot" screen
You will see yellow dots for 3-5 minutes then the script will start
Live USB Instructions (Windows):
(Instructions from pendrivelinux.com)(thanks)
Download UNetBootin for Windows
Download your favorite Linux ISO
Double click the Unetbootin Executable to start the program
(1) Click the Diskimage radio box
(2) browse to select your ISO
(3) Set your target USB drive
(4) click OK to start the creation
{
"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"
}
(5) After the USB drive is done select reboot.
(6) During boot enter the boot menu and change USB to boot first, save and reboot.
(7) When booting from UNetbootin select SliTaz
Click to expand...
Click to collapse
if cd/usb flash drive is made correctly you will not have Droid_X_621-ezSBF-and-RootCD.iso or Droid2_D2G_DX_DX2-RootCD-2012.iso on cd
you will have a folder named 'Boot'
with two files and a folder in the boot folder
usb flash drive may have a few more files
Hit enter at the yellow "boot baby... boot" screen
You will see yellow dots for 1-3 minutes then the script will start
root only
ezSBF and root
basically read onscreen directions
don't use numbers on right side of your keyboard, just use the ones above qwerty
select flash sbf only if phone is not working correct or you do not have 621 on phone yet
follow onscreen directions
root
select root DX
follow onscreen directions
turn phone on, connect to pc with usb cable
check usb debugging (settings/apps/development)
select charge only usb mode in top status bar
press continue
adb will push
Code:
data/local.prop /data/preinstall_md5/magic.md5
program will prompt you to
manually reboot phone to bootloader (Hold volume up+down buttons and power button, or hold Vol.Down and Camera and wait for the screen to flash)
program will will be flash repacked sbf (less than 50mb)
Program will reboot phone twice, very important (reboot just replaces the local.prop, but the old local.prop is still in memory, till second reboot)
adb pushes su,superuser, and busybox
program will reboot to recovery,
manually wipe cache (should auto reboot to recovery, at android andy press both volume buttons, if it doesn't press home button and hold it in then press your power button, hold it in also till you see a triangle on the screen w/ android andy then press both volume buttons)
then select reboot
rooted
error info
when running the program you may see these errors
rm failed for /data/preinstall_md5/magic.md5 no such file or directory
no root.img.gz no such file or directory
rm failed for /data/preinstall_md5/magic.md5 read only file system
that is fine, it will still work
after flashing files in bootloader, phone reboots to bootloader, instead of normal android operating system..... now what?try disconnecting usb, pull battery,wait a few secs, replace battery, reboot, wait for reboot to complete, reconnect usb
don't want to reboot pc try
Using Oracle VM VirtualBox, and Magic MD5 root iso
If you planning on making nandroid backups or flashing roms
read [HOW TO] Install/Use Droid 2 Bootstrap
bhigham/beh modified the root method
based on New D2 root method for stock 2.3.4 (621/622) found (Droid2, R2D2)
How this works
Originally Posted by phifc
There's an exploit in loadpreinstall.sh. It compares md5 sum files of preinstalled apps and if they're different, copies the md5 to the local cache. The preinstall just has an empty file in app/ so it will parse the md5 for it. Instead of an md5 sum, it contains a local.prop that allows adb root shell. So the system thinks it's copying the md5sum to the cache when it bounces off the symlink and overwrites the /data/local.prop, giving adb root on next reboot
Click to expand...
Click to collapse
originally posted by bhigham/beh
Since all these devices (Droid 2/R2D2/D2G/DX2 and DX seem to be vulnerable to the same exploit found by phifc at
http://rootzwiki.com...nd-droid2-r2d2/
I have assembled rooting methods for all of them in EzSbf style CD. I have tested it on my D2G, and the same method has been tested by multiple users on the D2/R2D2, and has worked fine.
Credit for this method go to phifc, djrbliss, and the others who developed the method.
I have simply taken the method, and assembled the tools.
Credit for the idea behind the CD method should go to 1KDS, as I have mostly patterned this CD after his method.
Credit should also go to Skrilax_CZ, as without his Motorola Android Firmware (De)packer, we wouldn't be able to have a 55 meg CD that covers multiple devices.
Special thanks also to themib for testing and troubleshooting on the DroidX2. In fact, since I don't have a DX2, he actually did a majority of the work in finding a method that would work (the method for the D2 and D2G doesn't quite work), and then we worked together to get it assembled and working.
This CD is for the D2,R2D2, D2G, and DX on Android version 2.3.4, and the DX2 on 2.3.5.
One note if you have troubles with it not working. It might be necessary to disconnect the phone after it flashes the preinstall and reboots. It seems that some phones may not complete the reboot process before being rebooted by ADB, so you may need to disconnect the phone when it starts booting, and let it boot fully before hooking it back up. when hooked back up, it will be rebooted, and should go on with the process like normal.
Of course, like all other things here, I have done my best on this, but there are no guarantees, and anything you do on your phone is at your own risk.
Click to expand...
Click to collapse
My Lists
Magic MD5 Root 2.3.4 for D2, R2D2, D2G, DX and 2.3.5 for DX2 - Google Docs
sd_shadow's [Collection] of Links: FAQs, Guides, Rooting, SBFs, ROMs... - Google Docs

[Video] How to Root Droid X on Android V2.3.4-Tomsgt123

Droid_X_621-SBF-and-RootCD-2nd_edition.iso 225.00 MB
other version had incorrect instructions, for boot to recovery, after flashing sbf

[ROOT] Framaroot, a one-click application to root
I have verified it works with these Motorola devices running android 2.3.4
Droid 2 (a955), Droid 2 Global (a956), R2D2 (a957), & Droid X (MB810)
Just download, allow unknown sources, install, open, select top root method (Gimli), reboot phone, done
no pc needed

I can also confirm, Framaroot works with with essentially one touch, at least for .621.
Sent from my Inspire 4G w/CM10.1

Bump
Sent from my Amazon Kindle Fire using Tapatalk

sd_shadow said:
Bump
Sent from my Amazon Kindle Fire using Tapatalk
Click to expand...
Click to collapse
Thank you for this by the way. I pulled my DX out of retirement to try CM11 and not everything went as planned. I remembered I had an old sbf disk tried that it turned out to be 605 which of course resulted in a bootlader error. I was able to use 621 restore and root to recover from disaster. :highfive:

[GUIDE] Root/Flash for Xiaomi Redmi 2

AnandMore's How-To Guide For Beginners
Xiaomi Redmi 2
{
"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"
}
Intro:
This thread will serve as a location for basic how-to guides for the Xiaomi Redmi 2. I'm going to start off with a couple of the more obvious ones and go from there. If anyone has any suggestions for additions please feel free to let me know.
By attempting any of the processes listed this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches on fire, or turns into a hipster and claims to have been modified before it was cool.
Index:
Post #1 - Rooting your Redmi 2
Post #2 - Flashing Custom Recovery
Post #3 - Flashing Custom ROMs
Post #4 - Flashing Custom Kernels
Resources:
Everything you need for Xiaomi Redmi 2 is available in the below given thread -
[INDEX] Xiaomi Redmi 2

Rooting your Redmi 2:
This guide will root your device through Stock MI Recovery(Works with TWRP also), but this is not Native Root. A new app named SuperSU will be installed, which will give root Permission.
Note:
Rooting does not Void Warranty.
Caution:
This is a safe process, but I am not responsible for anything bad that happens to your phone.
In most cases this approach of rooting should not block OTA updates.
Steps to follow for rooting:
Download the Root.zip and Copy the file to the folder 'Internal storage' (root of internal storage).
(File at the end of thread)
Open the Updater app, Press the 3 dots at Right Top Corner, A menu will open. Tap on “Choose Update Package“ and select the Root.zip File.
Wait until device will reboot.
After reboot a new app SuperSu will be installed.
Open the app and Choose "Continue".
Choose "Normal", Don't Choose TWRP/CWM, device will go into Boot Loop.
Note - Don't Choose TWRP/CWM, it will brick your device.
After sucessful updation , press ok.
Your Phone has now Root Permission.
Open any app using Root permission and SuperSU will ask for Permission.
Enjoy your rooted Redmi 2.
Un Root The Device:
For Un Root , open the SuperSU app,tap on Settings, Choose Full Unroot.
Your Device is Un Rooted Sucessfully. The SuperSU app will be removed.

Flashing Custom Recovery:
From Mobile:
Install Flashify app from Playstore
Once installed, access the application through app drawer.
Allow root access now and get navigate to Flashify’s home screen.
First take a backup of your recovery in case something goes wrong. (RECOMMENDED)
Now tap on recovery image and by "Choose the file" menu locate the .img file you want to flash.
After successful flashing it will ask you to reboot your device.
Done! You have custom recovery on your phone.
From PC:
Enable USB debugging, go to settings>about phone and then tap on Android/MIUI version 5 times. Developer Options will be enabled. Now go back to settings>Developer options and enable USB debugging.
ADB and Fastboot Drivers installed on your PC. I can provide you the drivers but it would be a better option to install MiFlash to get all the necessary drivers and Miflash software with you for future use.
Install Miflash on your PC. Lets suppose we installed it in C:\Xiaomi folder.
You can see two folders, proceed to "adb' folder
Then proceed to "Google" folder.
Proceed to "Android" Folder.
We are at our destination.
Now Hold down "Shift" button on your computer keyboard and right click with mouse on an empty part of the window. You will see that in the menu that appears, you have an option - "open command window here". Click on that
To verify if ADB is working and installed correctly, type "adb version" in the command window that opened without the code. You should get the adb version which means its working fine.
Turn off your Phone. When its completely switched off, press and hold "Volume Down" and "Power" button together and then the phone will turn on in Fastboot mode.
Use the USB cable to connect Phone to PC.
Copy the Recovery.img in the Android folder where we are running the Command prompt. (C:\Xiaomi\adb\Google\Android in my case as i installed Mi flash in C:\Xiaomi folder)
Now go back to command promt and enter the following commands -
Code:
fastboot devices
Once you enter that command, you will get a non-empty name for the device meaning the device is connected. Proceed to enter the next command to flash recovery image -
Code:
fastboot flash recovery recovery.img
Once you enter this command, the recovery image will be flashed on your device. Once it is completed, enter the final command to reboot your phone -
Code:
fastboot reboot
Your phone will reboot.
You have have now completed flashing custom recovery replacing Stock Mi recovery on your Xiaomi Redmi 2.

Flashing custom ROMs:
Steps to Follow:
Download and transfer the custom ROM you wish to flash to your device’s storage.
Boot your device into TWRP recovery.
Select “Wipe” from TWRP main menu and do a “Swipe to Factory Reset” on the bottom of screen.
Note: This will factory reset your device. If your custom ROM doesn’t require a factory reset, then simply skip this step.
Go back to TWRP main menu, tap on “Install” and select the custom ROMs .zip file that you transferred to your device in Step 1.
After selecting the .zip file, do “Swipe to Confirm Flash” on the bottom of screen to begin the custom ROM installation process. This may take some time.
Once your ROM is successfully flashed, you’ll see “Wipe cache/dalvik” option, select it and then do “Swipe to wipe” on bottom of screen.
Once cache & dalvik wipe completes, hit the “Back” button on-screen and then select “Reboot System” button.
That’s all. Your device will now reboot with the custom ROM you just flashed. Since this will be the first reboot after flashing a new ROM, it might take some time to rebuild cache and finish boot, have patience.

Flashing Custom Kernels:
Steps to Follow:
Download and transfer the custom Kernel you wish to flash to your device’s storage.
Boot your device into TWRP recovery.
In the TWRP main menu, tap on “Install” and select the custom Kernel .zip file that you transferred to your device in Step 1.
After selecting the .zip file, do “Swipe to Confirm Flash” on the bottom of screen to begin the custom Kernel installation process. This may take some time.
Once flashing completes, hit the “Back” button on-screen and then select “Reboot System” button.
That’s all. Your device will now reboot with the custom Kernel you just flashed. Since this will be the first reboot after flashing a new Kernel, it might take some time to rebuild cache and finish boot, have patience.

For list of all available Roms visit this thread :
http://forum.xda-developers.com/redmi-2/how-to/available-custom-marshmallow-roms-redmi-t3278535
Click to expand...
Click to collapse
Better if you make lollipop ROMs thread too

Superb work bro thanks ...u

Isn't MIUI rooted out of the box already? [emoji52]

Stachura5 said:
Isn't MIUI rooted out of the box already? [emoji52]
Click to expand...
Click to collapse
Developer ROMs are. Global ROMs aren't.
Device comes with global ROM :3

noobpremium said:
Better if you make lollipop ROMs thread too
Click to expand...
Click to collapse
I made both lollipop and marshmallow roms in one thread. So you think i should make seperate one for lollipop.

Stachura5 said:
Isn't MIUI rooted out of the box already? [emoji52]
Click to expand...
Click to collapse
All roms(Beta,developer,stable) for Redmi 2 are not Pre rooted.

Added videos tutorials for better understanding.

Great info, thanks a lot!
I have a very basic, very likely extremely stupid question: I flashed an early CM12.1 build (using CWM afaik) and for unknown reasons, I cannot boot into recovery and don't have root. How can I re-gain root access from here?

my phone also rebooting. please help me. how to go to recovery?

srmohanrajan said:
my phone also rebooting. please help me. how to go to recovery?
Click to expand...
Click to collapse
1) Switch off the phone.
2) Press the Volume Down, Volume Up and the Power Button at the same time, about 2-3 seconds until the mi logo shows up.
3) Recovery mode menu will appear.

Fr3ak23 said:
Great info, thanks a lot!
I have a very basic, very likely extremely stupid question: I flashed an early CM12.1 build (using CWM afaik) and for unknown reasons, I cannot boot into recovery and don't have root. How can I re-gain root access from here?
Click to expand...
Click to collapse
Follow the same steps to boot into recovery and flash SuperSU v2.4.6 zip via recovery
(And remember you are responsible if anything happens to the device)

omg, I am so stupid. I tried vol up + power, vol down + power and all possible combinations including the home button, but never vol up + vol down + power button. Thank you!

Fr3ak23 said:
omg, I am so stupid. I tried vol up + power, vol down + power and all possible combinations including the home button, but never vol up + vol down + power button. Thank you!
Click to expand...
Click to collapse
No problem bro !
✌

Great !

New CM 12.1 is awesome, finally the camera works
I am curious on why I keep on losing root access. I never had that issue with any other phones and custom ROMs.

How to root your Phab 2 (PB2-650Y)

This is NOT a guide for n00bs. You will need a functional copy of ADB and FASTBOOT (as well as any required Lenovo ADB drivers if you are windows tragic) running on your PC with Debugging enabled prior to proceeding.
This is NOT my original work. All the real credit goes to some guys in Russia as best as I can tell. I merely google translated their work and cooked up my own method for rooting (which is a bit easier than what they recommend). You can find their source materials here: Russian Lenovo Website - Phab 2 Unlocking the bootloader thread.
Grab the latest version of SuperSU from Chainfire (https://download.chainfire.eu/696/supersu/)
Download the version of TWRP I found on the Lenovo Russia website here (it is attached to this post)
Copy SuperSU to your Phab 2's SD Card (it can go on either the internal or an external drive) (ADB push SuperSUxxx.img /sdcard/)
You need to unlock your bootloader if you have not already done so:
Code:
adb reboot bootloader
fastboot oem unlock
Allow your Phab 2 to fully reboot and verify debugging is still enabled and the OEM unlocking option is enabled in Developer options.
Now that we've got a good clean operational unlocked bootloader let's apply our new recovery:
Code:
adb reboot bootloader
fastboot flash recovery TWRP-PB2-650_3.0.2.img
Hold down the power button on your Phab 2 until it powers off.
Press the center of the volume rocker (both vol+ and vol- need to be depressed) and at the same time hold down the power button until your Phab 2 posts. You'll know you did the procedure right because an ASCII arrow symbol will be scrolling through the device's 3 boot options (Recovery / Fastboot / Normal).
Release the power button and roll your finger holding the volume rocker to the volume up side of the rocker. Release the volume button.
Press Vol+ until Recovery is selected (it is the first option)
Press Vol- and wait 20 or so seconds for TWRP to load.
You now have to decide if you want to make TWRP your permanent recovery. If so, mount SYSTEM as RW and using TWRP's Advanced File Explorer navigate to /system and either delete or rename recovery-from-boot.p (I renamed mine to recovery-from-boot.p.save).
Go back to TWRP's main menu and select INSTALL. Navigate to the SuperSU image you copied to storage at the very beginning of this guide and flash it.
When you're done, reboot.
Don't panic when your Phab 2 bootloops once. It'll boot fine on its second pass. In another 20-30 seconds you will be greeted by a fully rooted Phab 2.
Enjoy! Screenshots are attached to the second post.

First boot into recovery (757):
{
"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"
}
Mount System RW (102):
File Manager 1 (010):
File Manager 2 (019):
Install SuperSU (243):
Celebrate

third post reserved for whatever

fourth post reserved for whatever

fifth post reserved for whatever

is this working for phab2 pb2-650m?

I assume so. The original work was based on a 650M but I can only validate my additions on the 650Y since I don't have a 650M

Synman said:
This is NOT a guide for n00bs. You will need a functional copy of ADB and FASTBOOT (as well as any required Lenovo ADB drivers if you are windows tragic) running on your PC with Debugging enabled prior to proceeding.
This is NOT my original work. All the real credit goes to some guys in Russia as best as I can tell. I merely google translated their work and cooked up my own method for rooting (which is a bit easier than what they recommend). You can find their source materials here: Russian Lenovo Website - Phab 2 Unlocking the bootloader thread.
Grab the latest version of SuperSU from Chainfire (https://download.chainfire.eu/696/supersu/)
Download the version of TWRP I found on the Lenovo Russia website here (it is attached to this post)
Copy SuperSU to your Phab 2's SD Card (it can go on either the internal or an external drive) (ADB push SuperSUxxx.img /sdcard/)
You need to unlock your bootloader if you have not already done so:
Allow your Phab 2 to fully reboot and verify debugging is still enabled and the OEM unlocking option is enabled in Developer options.
Now that we've got a good clean operational unlocked bootloader let's apply our new recovery:
Hold down the power button on your Phab 2 until it powers off.
Press the center of the volume rocker (both vol+ and vol- need to be depressed) and at the same time hold down the power button until your Phab 2 posts. You'll know you did the procedure right because an ASCII arrow symbol will be scrolling through the device's 3 boot options (Recovery / Fastboot / Normal).
Release the power button and roll your finger holding the volume rocker to the volume up side of the rocker. Release the volume button.
Press Vol+ until Recovery is selected (it is the first option)
Press Vol- and wait 20 or so seconds for TWRP to load.
You now have to decide if you want to make TWRP your permanent recovery. If so, mount SYSTEM as RW and using TWRP's Advanced File Explorer navigate to /system and either delete or rename recovery-from-boot.p (I renamed mine to recovery-from-boot.p.save).
Go back to TWRP's main menu and select INSTALL. Navigate to the SuperSU image you copied to storage at the very beginning of this guide and flash it.
When you're done, reboot.
Don't panic when your Phab 2 bootloops once. It'll boot fine on its second pass. In another 20-30 seconds you will be greeted by a fully rooted Phab 2.
Enjoy! Screenshots are attached to the second post.
Click to expand...
Click to collapse
You should make a video of the procedure. So you are saying after flashing the recovery, have to press power and volume up+down together until phab2 posts. What is posts? Do you mean reboots? And what do you mean by roll the finger?

Synman said:
This is NOT a guide for n00bs. You will need a functional copy of ADB and FASTBOOT (as well as any required Lenovo ADB drivers if you are windows tragic) running on your PC with Debugging enabled prior to proceeding.
This is NOT my original work. All the real credit goes to some guys in Russia as best as I can tell. I merely google translated their work and cooked up my own method for rooting (which is a bit easier than what they recommend). You can find their source materials here: Russian Lenovo Website - Phab 2 Unlocking the bootloader thread.
Grab the latest version of SuperSU from Chainfire (https://download.chainfire.eu/696/supersu/)
Download the version of TWRP I found on the Lenovo Russia website here (it is attached to this post)
Copy SuperSU to your Phab 2's SD Card (it can go on either the internal or an external drive) (ADB push SuperSUxxx.img /sdcard/)
You need to unlock your bootloader if you have not already done so:
Code:
adb reboot bootloader
fastboot oem unlock
Allow your Phab 2 to fully reboot and verify debugging is still enabled and the OEM unlocking option is enabled in Developer options.
Now that we've got a good clean operational unlocked bootloader let's apply our new recovery:
Code:
adb reboot bootloader
fastboot flash recovery TWRP-PB2-650_3.0.2.img
Hold down the power button on your Phab 2 until it powers off.
Press the center of the volume rocker (both vol+ and vol- need to be depressed) and at the same time hold down the power button until your Phab 2 posts. You'll know you did the procedure right because an ASCII arrow symbol will be scrolling through the device's 3 boot options (Recovery / Fastboot / Normal).
Release the power button and roll your finger holding the volume rocker to the volume up side of the rocker. Release the volume button.
Press Vol+ until Recovery is selected (it is the first option)
Press Vol- and wait 20 or so seconds for TWRP to load.
You now have to decide if you want to make TWRP your permanent recovery. If so, mount SYSTEM as RW and using TWRP's Advanced File Explorer navigate to /system and either delete or rename recovery-from-boot.p (I renamed mine to recovery-from-boot.p.save).
Go back to TWRP's main menu and select INSTALL. Navigate to the SuperSU image you copied to storage at the very beginning of this guide and flash it.
When you're done, reboot.
Don't panic when your Phab 2 bootloops once. It'll boot fine on its second pass. In another 20-30 seconds you will be greeted by a fully rooted Phab 2.
Enjoy! Screenshots are attached to the second post.
Click to expand...
Click to collapse
Hey thank you for the method. My device is PB2-650m Philippine version. Twrp recovery installed without issue , but after flashing supersu, would not boot. Stuck on second boot. I flashed UPDATE-unSU.zip to unroot and factory reset device. Flashed SuperSu-v2.79 and rooted without issue.

Too bad you didn't make a video...

Synman said:
Too bad you didn't make a video...
Click to expand...
Click to collapse
I did not have time. My phone got stuck on 2nd boot and was trying to figure out way to fix it. I fixed it by deleting supersu and factory resetting. I found different SuperSU version and worked. Thanks to you for providing me and the other phab2 owners with custom recovery.

Anyone get voLTE to work on this phone (PB2-650Y)?

query
http://support.lenovo.com/in/en/products/Tablets/PHAB-Series/PHAB2/downloads/DS118503

Did anybody flash PB2-650M OTA update. If you did, is there a way to flash it on rooted device?

thanx
thanx 4 news, got updated just niw 1.4 gb approx. Lets see.

stock rom for pb2-650m
I bought this phone last month. I gonna root my device and install twrp recovery. before that i wanna know whether stock rom available for this? if yes, please share me the link.

l.a.s.
Was searching for it, Lenovo smart assistant etc.. but couldn't find one.

I tried "adb" command in Linux. But not working. Saying "????? No permission". If anyone having USB driver means please share it with me.

lenovo companion appi installed above app,
I nstalled above app, and in search found mobile assistant appfor lenovo, guess it automatically installed usb driver s

Adb command working. And also I unlocked my bootloader. Gonna flash twrp. Any custom ROM for this device?