Hi I have installed substratum theme but after restart my phone is blinking and showing system ui keeps stopped and im unable to give access adb command when i type adb devices its not giving authorize and i dont have twrp i have rooted my phone with magisk boot kindly help
sjadhav252 said:
Hi I have installed substratum theme but after restart my phone is blinking and showing system ui keeps stopped and im unable to give access adb command when i type adb devices its not giving authorize and i dont have twrp i have rooted my phone with magisk boot kindly help
Click to expand...
Click to collapse
Flash the stock boot.img from your PC. Boot into the system, enable adb debugging, then reboot to the bootloader.
Flash the Magisk modified boot.img and boot it. While SystemUI crashes enter the following command on your PC
Code:
adb wait-for-device shell magisk --remove-modules
Your device will remove all Magisk modules and it will reboot. Done
thanks for your guide bt i have done system reset settings from recovery mode
hello dear do you any data recovery software for oneplus 7t pro
Related
So I'm in the process of trying to Root my ZTE Smarttab 10 on firmware v03b.
Ive been following instructions on the following pages:
http://forum.xda-developers.com/showthread.php?t=1629630
http://forum.xda-developers.com/showthread.php?t=1473555
The instructions are spread out across those threads and my problem starts kind of early in the process.
My goal is to use ADB to boot in to the Bootloader and then use a recovery rom to use TWRP to install a rom.
What i have done:
I have installed the ZTE Drivers
I have installed the SDK tools and updated it.
Now when the tablet is running normally I can see it in ADB and is able to run the command.
ADB Reboot Bootloader
This reboots the devices to a black screen (I assume this is the bootloader) and windows recognizes that a device is there.
The problem is that when I try to see this from ADB i cannot see the device when running ADB Devices.
This makes the next step impossible as I need to use ADB to boot a recovery rom.
So I would have posted in the development treads listed above but as I dont have 10 posts (this being my first post) I cannot post in the threads above.
I'm confident that this is a driver problem and I have uninstalled and re-installed all the drivers related to this including SDK.
But no luck yet.
Where other people say they have succeeded is when in the device manager they have ADB interface and ZTE Handset ADB interface listed.
This is the state where I'm at but I still cannot see the device in ADB.
Anyone have any insight on this kind of problem and can offer any help for a solution or direction to get to the solution.
Thank you for your help and attention!
//Nagarutu
Vodafone (ZTE) SmartTab10 3.2 HoneyComb
You can't use adb in bootloader mode, you want fastboot. So when you do 'adb reboot bootloader'. It reboots to the black screen (that is the bootloader). Try typing 'fastboot devices' and see if you're device comes up. It should if you have all drivers installed correctly and fastboot on your system. Then you'll be able to do 'fastboot flash recovery recovery.img' to install the custom recovery, then a 'fastboot reboot' and lastly an 'adb reboot recovery' will get you into your custom recovery to flash a new rom. Don't forget to make a backup.
matt4321 said:
You can't use adb in bootloader mode, you want fastboot. So when you do 'adb reboot bootloader'. It reboots to the black screen (that is the bootloader). Try typing 'fastboot devices' and see if you're device comes up. It should if you have all drivers installed correctly and fastboot on your system. Then you'll be able to do 'fastboot flash recovery recovery.img' to install the custom recovery, then a 'fastboot reboot' and lastly an 'adb reboot recovery' will get you into your custom recovery to flash a new rom. Don't forget to make a backup.
Click to expand...
Click to collapse
Thank you for the help ! it cleared things up for me.
Now the trouble's continue.
With the firmware im on (v03b) you cannot use the fastboot flash method but only fastboot.
And they way it is supposed to be done is that you run
fastboot boot recovery.img (recovery being a twrp recovery for my device)
When its booted to TWRP i should be able to see it in ADB to be able to run the following commands to it:
--> adb remount
--> adb shell
--> ln -s /system/xbin/su /system/bin/su
However I cannot get it to show in ADB (or fastboot) when its booted in to TWRP.
Any ideas?
I managed to solve the last bit to.
Now it was actually a driver problem, so i just updated the driver in device manager and located the ADB driver from ZTE and it worked to boot in to TWRP and then to flash the device.
Now I have CM10 installed and is smiling!
Took me 4 days but damn it its done!
Thanks for the help!
Glad you've figured it out
1a
2a
3a
4a
5a
This is a copy of the comment I made in the [Help] topic, figured I would make a separate post since that thread is a mess. Anyway, credit for the method is to krytikul and evelpotatoman. I am not responsible for any damage/unwanted results/house fires. Use at your own risk yada yada.
Without furher ado, here is my tutorial for those who want working SuperSU on their MDZ-16-AB Mi Box 3. Warning: since the bootloader isn't unlockable yet, you will have to connect a laptop to run some commands EVERY TIME YOU BOOT UP THE MI BOX. If you do not connect to run the specified commands YOUR DEVICE WILL BOOTLOOP, it won't even be able to boot in unrooted state. Luckily, this doesn't apply to waking up from standby mode, so as long as you keep your Mi Box plugged in and don't power it off, you'll be fine.
You will need:
A USB male to male cable (I made one myself soldering two cable plugs together)
Mi Box Marshmallow userdebug firmware ROM (this guide will not work if you are already on Nougat test build)
SuperSU installation files
The ability to use adb on your computer
The steps:
Put the downloaded userdebug firmware ROM on a FAT32 formatted drive.
Enable developer options on the Mi Box. This can be done in your settings, find "About" and then click on "build" 7 times to enable the developer options. It will confirm you've done this with an on-screen toast notification.
Connect the Mi Box to your computer and check if a device comes up when typing "adb devices" in command prompt. If not, wait for the Mi Box to display a dialogue confirming you want to allow adb on this computer.
Type "adb reboot recovery" to put the Mi Box in recovery mode. Once in recovery, unhook the cable and plug in your usb, click "Apply update from EXT" then "Update from udisk" and select MiBOX3_USA_once_r454.zip, then just let the update do it's thing.
Reboot the device. Once we're back, see if the box is still under adb devices.
Now run these commands:
Code:
adb root
adb remount
adb disable-verity
adb reboot
The device will reboot. Once it's rebooted, run these commands to disable OTA updates (otherwise it will immediately update to an unrootable firmware
Code:
adb root
adb remount
adb shell pm disable com.google.android.gms/.update.SystemUpdateService
adb shell pm disable com.google.android.gms/.update.SystemUpdateService$ActiveReceiver
adb shell pm disable com.google.android.gms/.update.SystemUpdateService$Receiver
adb shell pm disable com.google.android.gms/.update.SystemUpdateService$SecretCodeReceiver
adb shell pm disable com.google.android.gsf/.update.SystemUpdateActivity
adb shell pm disable com.google.android.gsf/.update.SystemUpdatePanoActivity
adb shell pm disable com.google.android.gsf/.update.SystemUpdateService
adb shell pm disable com.google.android.gsf/.update.SystemUpdateService$Receiver
adb shell pm disable com.google.android.gsf/.update.SystemUpdateService$SecretCodeReceiver
adb reboot
Wait for the device to reboot. Now we've disabled OTA updates we can install SuperSU. Unzip the SuperSU installer and run the installer BAT script. When the script is done, it will seem as if the device is bootlooping. From now on, this will happen EVERY TIME THE DEVICE BOOTS. If you do not connect to run the specified commands YOUR DEVICE WILL BOOTLOOP, it won't even be able to boot in unrooted state. Below are the steps you should perform to get your device to boot in SuperSU-rooted state.
While the bootanimation is running, keep executing "adb devices" until your device is in the list.
Once the Mi Box is in the adb devices list, type "adb root" and press enter. your device will be disconnected from adb again.
Keep executing "adb devices" again until the Mi Box reappears. When it's there, type "adb shell setenforce 0"
All these steps are performed while the bootanimation is playing. The device will boot shortly after the last command is executed. Be patient as it can take a while for the device to re-enter the adb devices list.
thanks. all works fine
maybe i'd try this.
but is there a way also to undo the rooting without reflashing the firmware? or is there also a script to undo or remove the root?
Hey guys;
hope you are all doing great, I need your help.
I have Oreo on my device and I really need to have permission to change my stupid launcher. I hate the original one.
does anybody know how to give this permission to my device when I have Oreo?
you know? before Oreo there were a lot of problem with device and wifi.
But all gone with Oreo, and now I don't have any admin Permission.
please help.
thanks a lot.
arashdan89 said:
Hey guys;
hope you are all doing great, I need your help.
I have Oreo on my device and I really need to have permission to change my stupid launcher. I hate the original one.
does anybody know how to give this permission to my device when I have Oreo?
you know? before Oreo there were a lot of problem with device and wifi.
But all gone with Oreo, and now I don't have any admin Permission.
please help.
thanks a lot.
Click to expand...
Click to collapse
N o Can Do!!
Final answer.......
The link to google drive is dead can someone plz repost
LgPWN'd said:
The link to google drive is dead can someone plz repost
Click to expand...
Click to collapse
Won't do you much good if your mdz-16-ab is not on a MM build
Uart
bigtalker said:
Won't do you much good if your mdz-16-ab is not on a MM build
Click to expand...
Click to collapse
I have decided to go a different route...
Ordered a uart rig
LgPWN'd said:
I have decided to go a different route...
Ordered a uart rig
Click to expand...
Click to collapse
Good luck wid dat!
I'm happy to tell you magisk and twrp on mdz-16-ab is possible. And I managed to do this. It need a small hack on u-boot. I need someone who have this device to do more tests for this method.
Hi all, I wonder if anybody can help with this.
my volume buttons are not working (hardware issue) and I was trying to install TWRP and a custom rom but, after installing TWRP the phone now always boots in recovery mode (at least this is what adb tells me) but TWRP does not really start, I keep seeing only "honor, powered by android" black screen.
adb is working but not fastboot. I tried to reboot to bootloader but it always go to recovery instead. I have no su, and I am stuck just with adb in recovery.
any idea?
If you have full adb access maybe you can restore your backup directly from it
Thanks Rayan
how? what do you mean by "full adb access"?
I tried to run adb sideload but it does not work (it says "closed" shortly after without doing anything)
I don't really understand what the issue is, do you have access to TWRP menu or not at all? And when you say that you can use adb, is the device recognized when you type adb devices ? And what happens when you try to boot in bootloader and use fastboot? Can you try to the command "adb reboot bootloader"?
Rayan19997 said:
I don't really understand what the issue is, do you have access to TWRP menu or not at all? And when you say that you can use adb, is the device recognized when you type adb devices ? And what happens when you try to boot in bootloader and use fastboot? Can you try to the command "adb reboot bootloader"?
Click to expand...
Click to collapse
Thanks Rayan, I finally solved replacing the volume buttons (found cheap ones). However adb was working but no matter which command I was sending (adb reboot bootloader) the phone was always rebooting in recovery mode but TWRP was not starting properly (could not see anything)
with volume buttons I managed to enter into bootloader, reflash TWRP and do everything I needed
Thanks
please some can you help with the porting of twrp for this phone
even some help with official firmware v217 then we can root with magiusk and recovery image
this phone has the mtk processor MT6765
Infinix hot 8 pliss, i can instal twrp
Yes, help sir ? :good:
Infinix Hot 8 Need Support
Please really need support for root and twrp for this device,, this device is really nice,,
guys again some try and get the firmware v217 so we can extract the boot.img for magisk
i hope a update is coming soon plan to get thta to find this boot.img
online the v174 firmware is not the same
OTA Update for Infinix
X650C-H626DE-P-191005V224.zip
240Mb
capture via usbdebugg
http://www.mediafire.com/file/24dmq3hk7wbu6b3/X650C-H626DE-P-191005V224.zip/file
Mtk(mediatek) processor devices are not supported by custom ROM developers. Don't expect custom rom support for hot infinix 8. Sorry.
Did anyone try Readback in SP Flash tool? So far, I have not been successful in doing so.
got it
To unlock Bootloaded withour error in Fastboot use command
fastboot flashing unlock
and then on the phone select volume up key to acknowledge
phone is booted into fresh android
and now rooted with magisk
thnx guys all done for now
off topic if you have a pihole on rasberry pie you can see that this phone is THE WORST i do mean UTTER DISREGUARD for user privacy and send EVERYTHING and i mean EVERTHING home to china
included is user app usage
user data
crash analytics
with root i will NOW TAKE CARE to THIS
any one needs boot.img modified for firmware 216 for magisk root will upload it
darylzero said:
phone is booted into fresh android
and now rooted with magisk
thnx guys all done for now
off topic if you have a pihole on rasberry pie you can see that this phone is THE WORST i do mean UTTER DISREGUARD for user privacy and send EVERYTHING and i mean EVERTHING home to china
included is user app usage
user data
crash analytics
with root i will NOW TAKE CARE to THIS
any one needs boot.img modified for firmware 216 for magisk root will upload it
Click to expand...
Click to collapse
Screenshots
and UPLOAD THE orignal+patched BOOT.img
With complete VERSION INFO
Sent from my Infinix-X650C using XDA Labs
Boot.img Magisk patched
https://www.mediafire.com/file/0nzyd8t9yu8vqpd/magisk_patched.img/file
Original Boot.img
http://www.mediafire.com/file/32gtumg9q6r46bi/boot.img/file
downloaded the uploaded firmware from google drive v236 i think
used techno tool to flash this to phone to VERIFY the firmwareis good and proper
once the firmware was verified and phone booted i uploaded the boot.img from that firmware v236 to magisk on phone and patched it
got this patched boot.img back to computer
now for the flashing part
install ADB drivers
on phone activate usb debug and oem unlock in developer mode in settings
check ADB is working and sees phone n computer via usb with command
"adb shell"
shouls show a valid response indicating phone is ADB ready
next get it into Fastboot mode with command
"adb reboot bootloader"
wait till phone reboots into fastboot mode check fastboot mode is active with this command
"fastboot devices"
now to unlock bootloader in fastboot else it will give error
use command
"fastboot flashing unlock "
this will also give a acknowledge on the phone that BOOTLOADER will now b unlocked and press volume up to agree
once bootloader is unlocked in fast boot next it to flash the magisk boot.img patched
i have uploaded this to medifire please download
place this file named
magisk_patched.img on desktop
use command boot
"fastboot flash boot (( need to drag and drop the file magisk_patched.img from desktop here ))"
wait till magic is done
after use to
"fastboot reboot "
after phone reboot it will b factory reset and rooted check root with magisk manager installed
root checked verified
https://www.mediafire.com/view/a2ivwbm530gdb9v/Screenshot_20191210-122733.png/file
Thank you very much.
My phone now has root access
Are you installed TWRP Recovery in your device.???
darylzero said:
Boot.img Magisk patched
https://www.mediafire.com/file/0nzyd8t9yu8vqpd/magisk_patched.img/file
Original Boot.img
http://www.mediafire.com/file/32gtumg9q6r46bi/boot.img/file
downloaded the uploaded firmware from google drive v236 i think
used techno tool to flash this to phone to VERIFY the firmwareis good and proper
once the firmware was verified and phone booted i uploaded the boot.img from that firmware v236 to magisk on phone and patched it
got this patched boot.img back to computer
now for the flashing part
install ADB drivers
on phone activate usb debug and oem unlock in developer mode in settings
check ADB is working and sees phone n computer via usb with command
"adb shell"
shouls show a valid response indicating phone is ADB ready
next get it into Fastboot mode with command
"adb reboot bootloader"
wait till phone reboots into fastboot mode check fastboot mode is active with this command
"fastboot devices"
now to unlock bootloader in fastboot else it will give error
use command
"fastboot flashing unlock "
this will also give a acknowledge on the phone that BOOTLOADER will now b unlocked and press volume up to agree
once bootloader is unlocked in fast boot next it to flash the magisk boot.img patched
i have uploaded this to medifire please download
place this file named
magisk_patched.img on desktop
use command boot
"fastboot flash boot (( need to drag and drop the file magisk_patched.img from desktop here ))"
wait till magic is done
after use to
"fastboot reboot "
after phone reboot it will b factory reset and rooted check root with magisk manager installed
root checked verified
https://www.mediafire.com/view/a2ivwbm530gdb9v/Screenshot_20191210-122733.png/file
Click to expand...
Click to collapse
Are you installed TWRP Recovery in your device.i want TWRP recovery.can I install TWRP recovery after root my device.tel me.
https://forum.xda-developers.com/android/help/infinix-hot-8-t3986799/post80598837
Check this Thread for complete guide on
* UNLOCKING-BOOTLOADER
* ROOTING
* TWRP
* OPTIMIZATION
* UN-BRICKING
* CUSTOM-ROM
Sent from my Infinix-X650C using XDA Labs
How can I root my infinix hot 8 v x650D
Misbahu said:
How can I root my infinix hot 8 v x650D
Click to expand...
Click to collapse
Same method as I stated above.. just use compatible TWRP
Sent from my Infinix-X650C using XDA Labs
darylzero said:
Boot.img Magisk patched
https://www.mediafire.com/file/0nzyd8t9yu8vqpd/magisk_patched.img/file
Original Boot.img
http://www.mediafire.com/file/32gtumg9q6r46bi/boot.img/file
downloaded the uploaded firmware from google drive v236 i think
used techno tool to flash this to phone to VERIFY the firmwareis good and proper
once the firmware was verified and phone booted i uploaded the boot.img from that firmware v236 to magisk on phone and patched it
got this patched boot.img back to computer
now for the flashing part
install ADB drivers
on phone activate usb debug and oem unlock in developer mode in settings
check ADB is working and sees phone n computer via usb with command
"adb shell"
shouls show a valid response indicating phone is ADB ready
next get it into Fastboot mode with command
"adb reboot bootloader"
wait till phone reboots into fastboot mode check fastboot mode is active with this command
"fastboot devices"
now to unlock bootloader in fastboot else it will give error
use command
"fastboot flashing unlock "
this will also give a acknowledge on the phone that BOOTLOADER will now b unlocked and press volume up to agree
once bootloader is unlocked in fast boot next it to flash the magisk boot.img patched
i have uploaded this to medifire please download
place this file named
magisk_patched.img on desktop
use command boot
"fastboot flash boot (( need to drag and drop the file magisk_patched.img from desktop here ))"
wait till magic is done
after use to
"fastboot reboot "
after phone reboot it will b factory reset and rooted check root with magisk manager installed
root checked verified
https://www.mediafire.com/view/a2ivwbm530gdb9v/Screenshot_20191210-122733.png/file
Click to expand...
Click to collapse
I have an Infinix Hot 8 X650B.
I am trying to root the device. I have installed all ADB required files and the drivers.
The computer detects the drivers and the device is showing in ADB Device list.
But it's not being listed in fastboot devices check, and no fastboot command is working.
Please what can I do?
Papichoolo said:
I have an Infinix Hot 8 X650B.
I am trying to root the device. I have installed all ADB required files and the drivers.
The computer detects the drivers and the device is showing in ADB Device list.
But it's not being listed in fastboot devices check, and no fastboot command is working.
Please what can I do?
Click to expand...
Click to collapse
Try Installing driver's on an different computer and check if it loads to fastboot.
Sent from my Infinix-X650C using XDA Labs
AshhRED said:
Try Installing driver's on an different computer and check if it loads to fastboot.
Sent from my Infinix-X650C using XDA Labs
Click to expand...
Click to collapse
I tried on a different PC with Windows 7, same issue. ADB Loads and detects, but fastboot doesn't.
It shows under ADB Devices but when I type, adb reboot bootloader.
The phone goes into fastboot mode, but isn't detected when using command, fastboot devices.
Drivers and eveything is setup correct on it too.
Hi,
I am new in this topic and not a great geek ans please excuse mi for my aprroximative english ! but i am trying to convert an old cube tablet to a domotic tablet. So i have to flash the old rom to a newer like lineageos for example.
So the tablet is an U30GT C4H with android 4.2.2 and the original rom.
I connect the device to my Mac Os and with adb tools (from plateform tools find here) and terminal i wrote adb devices (tablet on) i see the device. OK
When i command fastboot devices, nothing, no line
When i command adb reboot-bootloader, the tablet take off and the screen keep black. With the terminal fastboot devices, no response, with adb devices command > List of devices attached but no more, no device.
With this tablet it is possible to start in recovery mode with power + audio down but with this option i have the android logo and no command. If i take power on no change.
If with adb command and tablet on, i write adb reboot recovery, the tablet restart and the screen see logo android and no command.
I know this kind of topic do not interese a lot of people but i would like use this cube for my house to command domotic (music, heaters etc..). More, i think it's a shame not to recycle this type of device for the planet !!!
Thanx
Fastboot only works if in your tablet's Android's Settings -> Developer options the option OEM unlock got enabled and tablet got restarted afterwards.
i don't see any option OEM in the menu developer
I found that the solution is use slideload protocol. I reseted the tablet and now i get recovery mode. Then i can connect the tablet to my Mac and use terminal with slideload lines. OK
But each time the process failed with rom i found on the net...
Is there an universal rom !!!
Any idea ?
You don't have to boot the device into Recovery mode:
Code:
adb devices
adb reboot sideload
adb sideload <PROPERLY-SiIGNED-FILE.ZIP>
adb reboot
BTW: adb sideload is meant to re-flash Stock ROMs only.
jwoegerbauer said:
You don't have to boot the device into Recovery mode:
Code:
adb devices
adb reboot sideload
adb sideload <PROPERLY-SiIGNED-FILE.ZIP>
adb reboot
BTW: adb sideload is meant to re-flash Stock ROMs only.
Click to expand...
Click to collapse
maybe the issue is the rom i doawnloaded ?
it is kasty-cube_u30gt_h-411-111-rooted4_4gb.zip
or
kasty-cube_u30gtc4-441-20131212-rooted4.zip
both failed.
Perhaps i have to unlock the bootloader as you said but i don't know
I'm pretty sure the 2 mentioned ROMs are a Custom ROM. Hence you can't use adb sideload method to flash them. To install a Custom ROM it's required that a Custom Recovery already got installed on device's Android.
I don't find any way to instal a recovery. I had arctools.zip but the app failed to acess to the SD disk or internal storage...