Related
I am trying to use 'adb' from the android dev kit but I cannot see the devices, i.e. 'adb devices' doesn't report any devices. It appeared to be working earlier this evening but not any more. I was going to push a rom file to my rooted phone but obviously since I no longer see the device I am stuck. I rooted yesterday and installed the maximus rom but my phone went into a loop of restarting. Unfortunately I didn't backup before I rooted and installed Maximus rom.
Can anybody offer any help? I am using Mac OSX.
Desperate since phone is now effectively redundant
adiemask said:
I am trying to use 'adb' from the android dev kit but I cannot see the devices, i.e. 'adb devices' doesn't report any devices. It appeared to be working earlier this evening but not any more. I was going to push a rom file to my rooted phone but obviously since I no longer see the device I am stuck. I rooted yesterday and installed the maximus rom but my phone went into a loop of restarting. Unfortunately I didn't backup before I rooted and installed Maximus rom.
Can anybody offer any help? I am using Mac OSX.
Desperate since phone is now effectively redundant
Click to expand...
Click to collapse
try this: http://forum.xda-developers.com/showthread.php?t=1706918
if it didnt help u just reply and we´re gonna look whats next to unbrick ur phone
Hi
Thanks for your reply, I have hit the 'Thanks' button
I read the posting you referenced but it doesn't really offer a solution to my problem.
As described earlier I rooted my phone and flashed a Rom (Maximus) succesfully but on turning the phone on after installing the new Rom I got into a cycle of the phone rebooting without actually getting past the lock screen. My thoughts at that stage were to re flash using stock rom but on running fastboot and plugging into my Mac OSX machine via USB, the phone doesn't show up in 'devices' on the Mac. I have also tried 'adb devices' form within Android Dev Tools and although 'adb' runs fine no device is reported. Of course without devices being avaialble to 'adb' then I cannot reflash!
I have also tried from within a bootcamp installation of 'Windows XP' installed on the mac with the same results, this with 'HTC Sync' installed and therefore providing the USB Drivers required within Windows.
I have tried logging into fastboot using 'power' and 'Down Volume' at various stages of the boot process on the phone but have never seen the phone within devices.
Clearly prior to installation of the Rom (Maximus) I could see devices at both the Finder window on the Mac and from adb devices.
Any help or insight you could provide would be very gratefully received
Ok ok ok dont worry
I had to read a bit and found quit much german threads where they flash back the stock rom
as is suggested u cant flash it with odin...
the only solution i woul suggest is that u have to find a computer running windows
there its very easy to restore the stock with the methods u described earlier in the thread...
hope u get done let me know what happend
=)
The question remains; how can I flash anything be it a hacked rom or an official rom when I cant see the 'device' in both windows and mac osx?
I think what I am looking for is a reason why the phone isn't seen when plugging in via USB. Once it is seen as a 'device' I will be able to flash anything via 'adb'.
Thank you for your continued interest and assistance
ok so u know how the get it back but ur phone is not really recognized by ur computer
but i found a method using the bootloader
the problem is that the instructions are in german
but i think if u google a bit u may find it
Don't know if I misunderstood what you said..but to get into recovery, you hold volume down and the power button when the phone is turned off. Not during the boot process.
Yes you can do it with bootloader (power+volume down)
Sent from my HTC Salsa C510e using xda premium
moksha098 said:
Yes you can do it with bootloader (power+volume down)
Sent from my HTC Salsa C510e using xda premium
Click to expand...
Click to collapse
Yes, I know that. He said he attempted to do that DURING the boot process. I was stating that he had to do it while the phone was powered down.
Guys, I can get into recovery no problem. The issue is that my phone doesn't show up in devices on the mac finder window and hence when I run 'ADB Devices' from the mac when the phone is plugged into the mac with USB no device is found and so no serial number is reported in my terminal window on the mac. If I can get to see the device with 'ADB' I can push the rom and recover the phone. At the moment the phone is bricked.
Thanks guys for your continued assistance.
adiemask said:
Guys, I can get into recovery no problem. The issue is that my phone doesn't show up in devices on the mac finder window and hence when I run 'ADB Devices' from the mac when the phone is plugged into the mac with USB no device is found and so no serial number is reported in my terminal window on the mac. If I can get to see the device with 'ADB' I can push the rom and recover the phone. At the moment the phone is bricked.
Thanks guys for your continued assistance.
Click to expand...
Click to collapse
But if this doenst work why dont u try the method with the recovery mode or the bootloader i suggested
Dear friends!
I finally decided to say goodbye to my drm keys and root my tablet. But the problem is adb comand line was waiting my device for ever. Thus, I started to investigate my problem. Finally. I've understood thet the very wanted driver is not installed when I took a look at "S1Boot fastboot" device. As I've understood the android_winusb provided by sony is not enough to install driver successfully. You should put android_winusb into this thing http://developer.android.com/intl/ru/sdk/win-usb.html as I did. But my windows 10 x64 tells me that it found a driver but encountered a problem. So what should I do? Please, help me out.
PS I don't wonna install giant-full android studio, because it's too huge and takes a lot of time to be installed
alex009988 said:
Dear friends!
I finally decided to say goodbye to my drm keys and root my tablet. But the problem is adb comand line was waiting my device for ever. Thus, I started to investigate my problem. Finally. I've understood thet the very wanted driver is not installed when I took a look at "S1Boot fastboot" device. As I've understood the android_winusb provided by sony is not enough to install driver successfully. You should put android_winusb into this thing http://developer.android.com/intl/ru/sdk/win-usb.html as I did. But my windows 10 x64 tells me that it found a driver but encountered a problem. So what should I do? Please, help me out.
PS I don't wonna install giant-full android studio, because it's too huge and takes a lot of time to be installed
Click to expand...
Click to collapse
Congrats on taking the step! You're almost there Maybe the steps in this post of me help you out?
alex009988 said:
Dear friends!
I finally decided to say goodbye to my drm keys and root my tablet. But the problem is adb comand line was waiting my device for ever. Thus, I started to investigate my problem. Finally. I've understood thet the very wanted driver is not installed when I took a look at "S1Boot fastboot" device. As I've understood the android_winusb provided by sony is not enough to install driver successfully. You should put android_winusb into this thing http://developer.android.com/intl/ru/sdk/win-usb.html as I did. But my windows 10 x64 tells me that it found a driver but encountered a problem. So what should I do? Please, help me out.
PS I don't wonna install giant-full android studio, because it's too huge and takes a lot of time to be installed
Click to expand...
Click to collapse
It happens because the driver are unsigned. You can install it by disablIng the drivers signature enforcement control momentarily.
In win 10 hit the maj key and click on restart a menu appear click on Troubleshooting -> advanced options -> parameters->restart. Install the driver and reboot.
Thanks for your help guys. I've finally rooted my tablet and I used windows xp on a virtual machine. I'm also sure that flashtool can be used virtually. It's much better than fighting with windows 10. After all, I did a mistake I flash twrp adb as a kernel and my tablet was finding no way of loading except for tarp, and the screen was untouchable. Nevertheless, I had to connect my pc and twrp and use a command which do fastboot reboot, flash adroplus kernel anew and flash twrp properly. Xmodgames and lockpatcher work well. Xposed haven't tested yet by me.
By the way, what is the difference between "twrp adb" only and "tarp not fixed"? What's better?
PS After all, I'm happy with the root, I bought an android device not in order to be without root. Sony album application works as well as it was
alex009988 said:
Thanks for your help guys. I've finally rooted my tablet and I used windows xp on a virtual machine. I'm also sure that flashtool can be used virtually. It's much better than fighting with windows 10. After all, I did a mistake I flash twrp adb as a kernel and my tablet was finding no way of loading except for tarp, and the screen was untouchable. Nevertheless, I had to connect my pc and twrp and use a command which do fastboot reboot, flash adroplus kernel anew and flash twrp properly. Xmodgames and lockpatcher work well. Xposed haven't tested yet by me.
By the way, what is the difference between "twrp adb" only and "tarp not fixed"? What's better?
PS After all, I'm happy with the root, I bought an android device not in order to be without root. Sony album application works as well as it was
Click to expand...
Click to collapse
Ok good:good:
With twrp not fixed you can navigate under twrp with the touch screen fonction
alex009988 said:
Xposed haven't tested yet by me.
Click to expand...
Click to collapse
Please do It's easy to uninstall if it causes problems, but when it works, it opens up so many possibilities.
PS After all, I'm happy with the root, I bought an android device not in order to be without root. Sony album application works as well as it was
Click to expand...
Click to collapse
Good! I completely agree. Having root access on Android is fantastic.
I hope this is useful information. It took me a bit to figure it out due to a lot of conflicting information, since the procedure has changed, perhaps several times, since the first version of Android. Also, I'll probably forget myself.
Please note that I've performed these steps on Linux (Specifically Arch Linux). Others have pointed out that if you have issues executing step 7 from Windows, you may need to follow this post.
1. Install Android Studio, or otherwise obtain the latest versions of the adb and fastboot programs. I think Windows users also need to install a USB driver, but I run Linux, so I am not sure about that procedure.
2. Gain access to the developer options on the tablet. Go to the settings, and find the "about tablet" section. Scroll down to the "Software version" section and tap on that several times until it says that you are now a developer. Feel special.
3. Go to the new "Developer options" setting. Select "OEM unlocking." Also, I selected "USB debugging" as a straightforward way to reboot into the boot loader.
4. Connect to the computer on which you've installed adb and fastboot.
5. Type 'adb devices' to see your device listed. The tablet will ask you if you're sure you want to allow the computer access to it. Answer in the affirmative, and save that option.
6. Type 'adb reboot-bootloader' to do just that.
7. After you see the innards of your 'droid, type 'fastboot flashing unlock' . On Linux, you may need root permissions to do this. The tablet will ask you to confirm (select with up/down volume, and accept with the power button), and will then erase all of your data! I didn't worry about this as I'm all on Google services, and so they can be restored easily enough.
Huhu
and where is that for? What can I do after the bootloader is unlocked? Is there any alternative bootloader that I can use then?
Huhu
and where is that for? What can I do after the bootloader is unlocked? Is there any alternative bootloader that I can use then?
Click to expand...
Click to collapse
you are then able to flash another (custom) recovery, which would let you install unsigned zip-files, e.g. in order to get root.
Unfortunately, there is no recovery port by now.
I don't know if one could use the source code on Lenovo's website to port one, if not we would probably need an image dump directly from the device (if I'm not mistaken you need root to dump the recovery image).
I really would like to have root, but it still seems far away unless there's an experienced developer somewhere who owns the device.
I've already thought of starting a bounty thread...maybe enough people are willing to contribute so that developers might feel attracted.
Hello,
Do you think it would be possible to install Windows 10 on our android yoga book?
Thanks,
I faced with one question , when I typed the 'fastboot flashing unlock ', there was nothing occurred except the innards of driod :crying,and I also selected the oem unlocking
(All right, I solved it )
AndyVerne said:
I faced with one question , when I typed the 'fastboot flashing unlock ', there was nothing occurred except the innards of driod :crying,and I also selected the oem unlocking
(All right, I solved it )
Click to expand...
Click to collapse
can you tell me how to deal with it? I met the same problem.
Vsplorer said:
can you tell me how to deal with it? I met the same problem.
Click to expand...
Click to collapse
I used one exe for adb and fastboot which is written by others, and every thing went perfectly.
AndyVerne said:
I used one exe for adb and fastboot which is written by others, and every thing went perfectly.
Click to expand...
Click to collapse
can you tell me where to download the exe？ thanks a lot！
Vsplorer said:
can you tell me where to download the exe？ thanks a lot！
Click to expand...
Click to collapse
Here is the link of the exe, hope it will be helpful
https://forum.xda-developers.com/showthread.php?t=2588979
AndyVerne said:
Here is the link of the exe, hope it will be helpful
https://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
thanks！
Missing Something?
I tried to follow the instructions above, but I might be missing something. After typing in 'adb reboot-bootloader' the Yoga Book reboots into a screen that says 'FASTBOOT MODE.' But when I type 'fastboot flashing unlock' it just says '< waiting for device >' and nothing ends up happening. What am I doing wrong?
jasonccheng said:
I tried to follow the instructions above, but I might be missing something. After typing in 'adb reboot-bootloader' the Yoga Book reboots into a screen that says 'FASTBOOT MODE.' But when I type 'fastboot flashing unlock' it just says '< waiting for device >' and nothing ends up happening. What am I doing wrong?
Click to expand...
Click to collapse
See this post:
https://forum.xda-developers.com/yoga-book/help/missing-usb-driver-cherry-trail-tablet-t3537008
Same here with Linux... The adb devices command shows the device but the flash command ends in 'waiting for device' and thats it. Damn
I relocked the bootloader, sinct then I got following message at the boot screen: bootloader error 01, please contact support.
After that the device is booting android properly. Anybody else experienced this and know how to get rid of the message?
Thx.
carepack said:
I relocked the bootloader, sinct then I got following message at the boot screen: bootloader error 01, please contact support.
After that the device is booting android properly. Anybody else experienced this and know how to get rid of the message?
Thx.
Click to expand...
Click to collapse
It's the price you pay for unlocking the bootloader. Affects many lower end devices, presumably using Intel chips. There is a solution for several devices - check around XDA - but I have not been able to get it to work with the YB.
For what it's worth, I would suggest those tempted to unlock the device and root it to check that you will be able to do what you want to do. Even rooted, I have found it impossible to get rid of the junk apps, so the whole exercise for me has been a waste of time. I'm waiting now to see if Lenovo will release the stock firmware. Until then, the YB is back in its box and I am a bit older and a bit wiser. Lenovo is junk.
carepack said:
I relocked the bootloader, sinct then I got following message at the boot screen: bootloader error 01, please contact support.
After that the device is booting android properly. Anybody else experienced this and know how to get rid of the message?
Thx.
Click to expand...
Click to collapse
i believe, this is due to android's security feature 'verified boot'. it warns that the system was somehow altered and can't be trusted - in other words that it is not an oem stock rom any more.
you might be able to get rid of it by flashing a complete stock rom, but i'm not sure.
zamzenos said:
It's the price you pay for unlocking the bootloader. Affects many lower end devices, presumably using Intel chips. There is a solution for several devices - check around XDA - but I have not been able to get it to work with the YB.
For what it's worth, I would suggest those tempted to unlock the device and root it to check that you will be able to do what you want to do. Even rooted, I have found it impossible to get rid of the junk apps, so the whole exercise for me has been a waste of time. I'm waiting now to see if Lenovo will release the stock firmware. Until then, the YB is back in its box and I am a bit older and a bit wiser. Lenovo is junk.
Click to expand...
Click to collapse
firstly, it has nothing to do with intel or lenovo or low end devices, because secure boot or verified boot is part of android - it is nothing more than a security feature to show whether system integrity (as provided by the vendor) is still valid.
secondly, why is Lenovo junk just because you are not able to get things done? i don't get it. i've already told you that it is possible to get rid of system apps, just use the right tools... e.g. 'Sytstem App Entferner' which definitely works. also i helped you to get your twrp backup working and i was also able to use the newest magisk root (v10.2) immediately, which you said was not possible. so i guess you shouldn't blame others for your shortcomings. the yb might surely have it flaws, bur no more or less than devices of other manufacturers.
danjac said:
i believe, this is due to android's security feature 'verified boot'. it warns that the system was somehow altered and can't be trusted - in other words that it is not an oem stock rom any more.
you might be able to get rid of it by flashing a complete stock rom, but i'm not sure.
firstly, it has nothing to do with intel or lenovo or low end devices, because secure boot or verified boot is part of android - it is nothing more than a security feature to show whether system integrity (as provided by the vendor) is still valid.
secondly, why is Lenovo junk just because you are not able to get things done? i don't get it. i've already told you that it is possible to get rid of system apps, just use the right tools... e.g. 'Sytstem App Entferner' which definitely works. also i helped you to get your twrp backup working and i was also able to use the newest magisk root (v10.2) immediately, which you said was not possible. so i guess you shouldn't blame others for your shortcomings. the yb might surely have it flaws, bur no more or less than devices of other manufacturers.
Click to expand...
Click to collapse
Let me start at the top:
1. My comments on Lenovo are no reflection on the useful tools you have provided us here, for which I have thanked you more than once. So no need to be defensive on that score.
2. If the unlock warning had its source in Android itself, we could expect the warning to bear its logo. I assume it bears the Intel logo because Intel is the author of it. In itself, this is of no importance. What is profoundly irritating is the fact that the security warning is followed by a completely unjustfied 5 second suspension. This is a penalty. Perhaps many do not mind this interference with their use of their devices, but I do. I'm not used to that kind of treatment and I don't take kindly to it.
3. My opinion of Lenovo has always been low, especially since their attempts some years ago to spike their devices with spyware. I regard Lenovo as an exploitative bottom feeder, supplying workaday gear and screwing their customers every way they can for an extra buck or two. I offered the YB to several of my friends. All turned their noses up at the mention of the manufacturer. Don't blame them.
4. If you do want to be of further assistance here, perhaps you can use your obvious technical skills and knowhow to work out how we can replace the Intel penalty with something more benign. I have tried, but can't find where the Intel warning is hidden.
I have downloaded and extracted the apk of the system app remover you mentioned. But until I can get rid of the Intel warning I won't bother to re-root the YB and test if it will clear the junk.
#carepack: at the moment, you must buy the stock firmware (and won't it be expensive!). All part of lenny's screw.
thx to all for youre response. my hope is that with next update the problem will solve by itself. We'll see. I were doin this ooi and was aware of things like that. So no drama for me.
@zamzenos
Buying the stock firmware? Could you provide more info about this?
carepack said:
thx to all for youre response. my hope is that with next update the problem will solve by itself. We'll see. I were doin this ooi and was aware of things like that. So no drama for me.
@zamzenos
Buying the stock firmware? Could you provide more info about this?
Click to expand...
Click to collapse
Yes, that could well do it. But will there be an update? There's a new 12" YB on offer. Could be our 10" version is history already. But we could then hope that they will release the stock.
Re buying the stock: https://forums.lenovo.com/t5/Android-Yoga-Series-Tablets/Lenovo-Yoga-Book-Firmware/td-p/3511903
zamzenos said:
Yes, that could well do it. But will there be an update? There's a new 12" YB on offer. Could be our 10" version is history already. But we could then hope that they will release the stock.
Re buying the stock: https://forums.lenovo.com/t5/Android-Yoga-Series-Tablets/Lenovo-Yoga-Book-Firmware/td-p/3511903
Click to expand...
Click to collapse
According to this:
http://www.androidpolice.com/2016/1...views-cite-software-issues-incredible-design/
We'll receive the nougat Update.
Greetings
Hi, i'm starting this thread by excusing myself for this approximativly english, i'm not really an english man :angel:
I don't really like calling help on forum, but at 00:30, with studies tomorrow, i'm really bored.
So, today at 17:30, i have reboot my OPX, simply reboot, and i'm now on a bootloop... I read a looooooot of thing on internet and i deduce that : My bootloader has relocked himself.
Before this reboot, i was on OxygenOS 3.* with TWRPblu****** and an unlocked bootloader. I can't access to recovery, only to a bootloop or fastboot mode.
I've tried :
- Use fastboot commands to flash recoveries, but nothing happen because i can't unlock the bootloader
- Use the MSMdowloadtool like all guide said, but the problem is there i think. My device aren't recognize as a "Qualcomm ***********" is recognize as "Android" or "One plus bootloader device" (i haven't exact name here). I thinked Windows 10 have the faculty to identify android devices, so i've installed on dual boot windows 7, no more results. (Signed Drivers are disabled)
I have no idea, i need u :crying:
If anyone have ever see the same issue, give me ur solution please
I certainly will contact the OnePlusSupport too but i know it's not really a good idea.
I will go to sleep now, i need to go to school tomor... today.
Have a good night !
Nekkoelb said:
Hi, i'm starting this thread by excusing myself for this approximativly english, i'm not really an english man :angel:
I don't really like calling help on forum, but at 00:30, with studies tomorrow, i'm really bored.
So, today at 17:30, i have reboot my OPX, simply reboot, and i'm now on a bootloop... I read a looooooot of thing on internet and i deduce that : My bootloader has relocked himself.
Before this reboot, i was on OxygenOS 3.* with TWRPblu****** and an unlocked bootloader. I can't access to recovery, only to a bootloop or fastboot mode.
I've tried :
- Use fastboot commands to flash recoveries, but nothing happen because i can't unlock the bootloader
- Use the MSMdowloadtool like all guide said, but the problem is there i think. My device aren't recognize as a "Qualcomm ***********" is recognize as "Android" or "One plus bootloader device" (i haven't exact name here). I thinked Windows 10 have the faculty to identify android devices, so i've installed on dual boot windows 7, no more results. (Signed Drivers are disabled)
I have no idea, i need u :crying:
If anyone have ever see the same issue, give me ur solution please
I certainly will contact the OnePlusSupport too but i know it's not really a good idea.
I will go to sleep now, i need to go to school tomor... today.
Have a good night !
Click to expand...
Click to collapse
Fastboot commands : is the phone recognised?
"fastboot oem device-info" output?
Did you tried the Mega unbricked guide?
Which step precisely is a problem?
Kéno40 said:
Fastboot commands : is the phone recognised?
"fastboot oem device-info" output?
Did you tried the Mega unbricked guide?
Which step precisely is a problem?
Click to expand...
Click to collapse
Yes he used..read full op.
Nekkoelb said:
Hi, i'm starting this thread by excusing myself for this approximativly english, i'm not really an english man :angel:
I don't really like calling help on forum, but at 00:30, with studies tomorrow, i'm really bored.
So, today at 17:30, i have reboot my OPX, simply reboot, and i'm now on a bootloop... I read a looooooot of thing on internet and i deduce that : My bootloader has relocked himself.
Before this reboot, i was on OxygenOS 3.* with TWRPblu****** and an unlocked bootloader. I can't access to recovery, only to a bootloop or fastboot mode.
I've tried :
- Use fastboot commands to flash recoveries, but nothing happen because i can't unlock the bootloader
- Use the MSMdowloadtool like all guide said, but the problem is there i think. My device aren't recognize as a "Qualcomm ***********" is recognize as "Android" or "One plus bootloader device" (i haven't exact name here). I thinked Windows 10 have the faculty to identify android devices, so i've installed on dual boot windows 7, no more results. (Signed Drivers are disabled)
I have no idea, i need u :crying:
If anyone have ever see the same issue, give me ur solution please
I certainly will contact the OnePlusSupport too but i know it's not really a good idea.
I will go to sleep now, i need to go to school tomor... today.
Have a good night !
Click to expand...
Click to collapse
Power off your phone, connect to PC with power off holding volume up button. It should detect phone as Qualcomm.
Nekkoelb said:
Hi, i'm starting this thread by excusing myself for this approximativly english, i'm not really an english man :angel:
I don't really like calling help on forum, but at 00:30, with studies tomorrow, i'm really bored.
So, today at 17:30, i have reboot my OPX, simply reboot, and i'm now on a bootloop... I read a looooooot of thing on internet and i deduce that : My bootloader has relocked himself.
Before this reboot, i was on OxygenOS 3.* with TWRPblu****** and an unlocked bootloader. I can't access to recovery, only to a bootloop or fastboot mode.
I've tried :
- Use fastboot commands to flash recoveries, but nothing happen because i can't unlock the bootloader
- Use the MSMdowloadtool like all guide said, but the problem is there i think. My device aren't recognize as a "Qualcomm ***********" is recognize as "Android" or "One plus bootloader device" (i haven't exact name here). I thinked Windows 10 have the faculty to identify android devices, so i've installed on dual boot windows 7, no more results. (Signed Drivers are disabled)
I have no idea, i need u :crying:
If anyone have ever see the same issue, give me ur solution please
I certainly will contact the OnePlusSupport too but i know it's not really a good idea.
I will go to sleep now, i need to go to school tomor... today.
Have a good night !
Click to expand...
Click to collapse
You have noting to do but to flash stock oos 2.1.4 using Qualcomm flasher and driver.I faced the same issue.but I managed to flash using Qualcomm in windows 10.and got my onyx back.
My suggesting is remove the adv or oneplus drivers.just install the Qualcomm driver and connect the device.follow the device manager if the deivce detected or not.it will detect and flash using Qualcomm flasher.
Hi guys, after 3 days of testing and testing to unlock my Mi Pad 4 i really have to ask what else i could do.
First what i did till now:
1. got my Mi Pad 4
2. Started it and got an update (i am now on version MIUI 10.1 Stable 10.1.1.0 (ODJCNFI)
3. tested it and because of problems with the GAPPS i wanted to unlock the device.
My account (i have a mi max 2 locked, Pocophone locked and Mi Pad 4) is verified already ( month ago - but i never unlocked a device).
I did not get a message which says you have to wait for xxx hours.
I tested on Win 10 home, Win 10 pro, Win 7 home, Win 7 ultimate.
I tested 13 different cables and overall i tried to unlock the device i think 743563475 times.
I followed every single tutorial i found. i enabled fastboot, USB debugging, OEM unlocking and added my account and device successfull.
My problems are: Most of the time when i am in fastboot and i plug the cable in the mi pads display turns black and it says 'press any key to turn off'
After trying to connect the fastboot Mi Pad 4 to my PC (no matter Win 10 or Win 7 ) after testing 10x or so it works.
Then in the Xiaomi unlocking tool my account gets verified if I have the rights. then it says unlocking ....
Sometimes it stucks at 50% and it says couldnt unlock, sometimes it stucks at 99% and it says couldnt verify the device.
I reseted the device. i tried everything.
i tested all sorts of drivers, i did really everything. When i try to use the command line and type in 'fastboot devices' only '?????? ' appears.
Month and years ago i unlocked 20 or more android devices (mostly LG or Sony) and i worked all the time. But now the Mi Pad 4 is my endboss i dont now what to do.
(i changed my PC so there are no old drivers from LG or sony on my PC)
In short:
i tested Win 7 and 10
i tested many cables
i reseted the device
i tested with and without windows in testmode
i tested with Mi unlock 3.3.827.31
I hope somebody can help me. thanks for every hint and help
And of course i tested the USB 2.0 USB 3.0 and USB 3.1 Ports on all PCs.
https://i.mi.com/find/device/activationlock#
Try find your device if it's bound to another phone number
also there could be problem with your usb port. i have similar problem where if i connect my phone or tab to a certain usb port, it fails to detect properly in fastboot mode. port working just fine in normal mode for data transfer or charging. so try with another computer if possible. and in fastboot mode first check if ur device is available by using "fastboot devices" command. that will confirm if adb can access ur device accurately.
Does you use ryzen series? I aslo has this problem when I use my PC(2600X). When I use my Intel notebook, everything is okey. If you use ryzen series, try to turn to use intel CPU.
Neptunew said:
Does you use ryzen series? I aslo has this problem when I use my PC(2600X). When I use my Intel notebook, everything is okey. If you use ryzen series, try to turn to use intel CPU.
Click to expand...
Click to collapse
Oh man, you are GREAT !
Yes i am using Ryzen 2700x and yes, i built an old frankenstein Win7 PC with my old Intel components. Now its working. I am very angry, because now it says i have to wait 300+ hours before unlocking (even if i already did the unlock process weeks ago) but i am happy, that i now have ONE single "error" message. and now unlocking will be possible i think.
Now i am looking for a good tutorial of how to install WRP properly on my Mi Pad 4, but man, thanks a lot. do you know WHY ryzen is doing such things?
bUll1t_335i said:
Oh man, you are GREAT !
Yes i am using Ryzen 2700x and yes, i built an old frankenstein Win7 PC with my old Intel components. Now its working. I am very angry, because now it says i have to wait 300+ hours before unlocking (even if i already did the unlock process weeks ago) but i am happy, that i now have ONE single "error" message. and now unlocking will be possible i think.
Now i am looking for a good tutorial of how to install WRP properly on my Mi Pad 4, but man, thanks a lot. do you know WHY ryzen is doing such things?
Click to expand...
Click to collapse
That's strange. I unlocked successfully on my Ryzen 7 1700 (Windows 10). Although - I did do the intial request on an Intel laptop a few months back.
ksoze said:
That's strange. I unlocked successfully on my Ryzen 7 1700 (Windows 10). Although - I did do the intial request on an Intel laptop a few months back.
Click to expand...
Click to collapse
Mybe rezen 2000 series or 400 series chip has this problem? I don't know about that. I just know my ryzen 2600X can't flash rec in MI PAD4.
it is possible the boot loader to be unlocked from factory ? mine did. it might be used ?
chivu246 said:
it is possible the boot loader to be unlocked from factory ? mine did. it might be used ?
Click to expand...
Click to collapse
1. what has your question todo with this thread?
2. many shops put own "ROMs" (mostly fake global ROMs) on the tablet, before selling it to international buyers. And for putting custom ROMs on the tablet, the bootloader must be unlocked. You can try original MIUI ROM or Xiaomi.eu with your unlocked bootloader. Would not recommand to use a ROM where the bootloader is opened.. You never know, what they re-seller has installed.
Hello friends,
Now I have a question, which makes me crazy:
Mi Pad 4 3/32GB Wifi
I have installed Miui 10.3 9.2.4 (weekly update) on my device and then got 2 OTA updates so I am now on MIUI 10.3 9.3.7.
Since then, this has happened to me twice, that is, when I restart the device, the device remains on the lock screen and I can not log in.
Everything is possible (use of camera etc. on lock screen) but the screen does not respond to my command to specify pattern or password, that is it does not come at all points for pattern or numbers to show password.
Many times restart did not help either, so I had to delete everything via TWRP (wipe) and then restart Android and I have to trouble fully reinstall everything (apps, etc.)
It's weird and I do not know what to do anymore.
Therefore, please for your advice.
Regards
djgholum said:
Hello friends,
Now I have a question, which makes me crazy:
Mi Pad 4 3/32GB Wifi
I have installed Miui 10.3 9.2.4 (weekly update) on my device and then got 2 OTA updates so I am now on MIUI 10.3 9.3.7.
Since then, this has happened to me twice, that is, when I restart the device, the device remains on the lock screen and I can not log in.
Everything is possible (use of camera etc. on lock screen) but the screen does not respond to my command to specify pattern or password, that is it does not come at all points for pattern or numbers to show password.
Many times restart did not help either, so I had to delete everything via TWRP (wipe) and then restart Android and I have to trouble fully reinstall everything (apps, etc.)
It's weird and I do not know what to do anymore.
Therefore, please for your advice.
Regards
Click to expand...
Click to collapse
My first suggestion would be to use a Stable ROM, not a developer.
darkhelmetnl said:
My first suggestion would be to use a Stable ROM, not a developer.
Click to expand...
Click to collapse
Thanks for your feedback. I was in stable and it was not okay, do the setting was not remain on tablet. So after any restart I had to made some setting again. After being in weekly beta, it is fine.
May be other suggestion?
Sent from my MI PAD 4 using Tapatalk
I am not able to bond my mi pad 4 wifi
I want to unlock my mi pad 4 wifi only BUT when I try to bond my device under developer settings>MI unlock status page it is asking me to insert a SIM Card on this wifi ONLY device. What can I do to bond my device? It is really frustrating. Please offer some advice. Thank you in advance.
genau1954 said:
I want to unlock my mi pad 4 wifi only BUT when I try to bond my device under developer settings>MI unlock status page it is asking me to insert a SIM Card on this wifi ONLY device. What can I do to bond my device? It is really frustrating. Please offer some advice. Thank you in advance.
Click to expand...
Click to collapse
Try with mi flash tool
Sent from my MI PAD 4 using Tapatalk
djgholum said:
Try with mi flash tool
Sent from my MI PAD 4 using Tapatalk
Click to expand...
Click to collapse
I have a Chinese version so how can do anything on the mi flash tool. Can you please describe what I could do. Thanks
genau1954 said:
I have a Chinese version so how can do anything on the mi flash tool. Can you please describe what I could do. Thanks
Click to expand...
Click to collapse
Mi Pad 4 is just one China version available. So you have to download mi flash tool for this device, used drivers also for your pc. Then you can connect your device to PC and start to unlock.
Remember you should have Xiaomi account with username and password.
After connecting to PC and starting flash tool you have to sign in and start. Normally will Xiaomi say you you have to wait for 2-3 weeks. After this time you can back and try again to unlock.
Remember during/ after unlock all of your data will be clean and you have to set the device again.
The rest is installing TWRP and European Rom (EU Room).
If you are from Germany [emoji6] then you are lucky cuz du kannst jede Menge Anleitung in Netz finden bzw bei chinahandy.net
Good luck, viel Glück
see the forums informations and I assume no liability and you do it at your own risk/ ich übernehme keine Haftung und du machst es auf eigene Gefahr.
Sent from my MI PAD 4 using Tapatalk
djgholum said:
Mi Pad 4 is just one China version available. So you have to download mi flash tool for this device, used drivers also for your pc. Then you can connect your device to PC and start to unlock.
Remember you should have Xiaomi account with username and password.
After connecting to PC and starting flash tool you have to sign in and start. Normally will Xiaomi say you you have to wait for 2-3 weeks. After this time you can back and try again to unlock.
Remember during/ after unlock all of your data will be clean and you have to set the device again.
The rest is installing TWRP and European Rom (EU Room).
If you are from Germany [emoji6] then you are lucky cuz du kannst jede Menge Anleitung in Netz finden bzw bei chinahandy.net
Good luck, viel Glück
see the forums informations and I assume no liability and you do it at your own risk/ ich übernehme keine Haftung und du machst es auf eigene Gefahr.
Sent from my MI PAD 4 using Tapatalk
Click to expand...
Click to collapse
I tried to follow the process as described above but I get stuck when I try to bond my device in the developer>Mi unlock status page. the system is asking me to put a sim card although this is a wifi only version of MI PAD 4. The China stable ROM is 10.2.1.0 ODJCNXM. I think that as long as the system asks me to put a sim card I am some how lost. any ideas what I could do next?
genau1954 said:
I tried to follow the process as described above but I get stuck when I try to bond my device in the developer>Mi unlock status page. the system is asking me to put a sim card although this is a wifi only version of MI PAD 4. The China stable ROM is 10.2.1.0 ODJCNXM. I think that as long as the system asks me to put a sim card I am some how lost. any ideas what I could do next?
Click to expand...
Click to collapse
Ummmm, I think something was wrong. You need 7 time knock on kernel no to be a developer the activate debugging mode to be able to connect to PC, the rest will be made in PC...
Sent from my MI PAD 4 using Tapatalk
djgholum said:
Ummmm, I think something was wrong. You need 7 time knock on kernel no to be a developer the activate debugging mode to be able to connect to PC, the rest will be made in PC...
Sent from my MI PAD 4 using Tapatalk
Click to expand...
Click to collapse
I did that already, as aresult I can see the developer page from there I can go to the MI status can bond the device by pushing the button "Add device".
That is where my problem starts. The system is asking me to add a sim card.