Related
Does anyone know how to root the Acer Iconia B1 tablet. Is it too early for a root?
I already tried the bin4ry method but it doesn't work.
Thanks in advance
Edit: Iconia B1 root method on page 16 by bullbrand http://forum.xda-developers.com/showthread.php?t=2113944&page=16
mripfreely said:
Does anyone know how to root the Acer Iconia B1 tablet. Is it too early for a root?
I already tried the bin4ry method but it doesn't work.
Thanks in advance
Click to expand...
Click to collapse
Yup same here, tried it didn't work.
Guess we will just have to wait till the device becomes more popular.
Incase anyone is wondering, its a pretty good device for the price. Seems to be running unmodified Jelly Bean and performance is quite snappy.
any update on this?
It would be great if there were someone that would develop a rom for this. I just ordered one
I would appreciate it, if there would soon be a way for root or to install a custom rom!
The bin4ry method doesn't even detect the device without some initial work.
When the device is plugged in, Windows detects the MTP drivers but not the MT65XX drivers which I believe is needed for Android ADB.
You can download the MT65XX drivers from the link below
http://www.mediafire.com/?bqab7ewrdkbaaqi
After installing these drivers the Bin4ry root will detect the device but it will get stuck in one of the steps.
Maybe a newer version of Bin4ry will work or someone can figure out how to get it to work.
No longer need this driver, just read "New Acer Drivers" post below
Instructions for installing MT65XX drivers
1. Download USB drivers for MT65xx
2. Set device on USB debugging mode.
3. Connect to PC using USB 2.0
4. After PC fails to find driver go to device manager ->Find MT65XX device ->Right click ->Update driver ->Browse for driver ->Now there are two ways to install:
1. ''Search for a driver in this location'' ->Browse to the driver location and press next. If this fails try the next method.
2. ''Let me pick from a list....'' ->Select ''let me pick from a list...'' ->Click on "have disk" ->Browse to driver folder and choose 'android_winusb.inf' -> From the list pick 'Android composite ADB interface' and click install.
5. After successful driver installation you should see 'Android composite ADB interface' in device manager.
New Acer Drivers
Acer recently released the ADB drivers for this tablet. So there no need to use the MT65xx drivers anymore.
In one of my tries the bin4ry method actually proceeded to completion but with multiple permission denied errors.
So still no root.
You can download the acer drivers from their website.
q
Hey i bought one of these badasses. Any updates on rooting or romming? Is there a recovery console on this device?
mripfreely said:
Acer recently released the ADB drivers for this tablet. So there no need to use the MT65xx drivers anymore.
In one of my tries the bin4ry method actually proceeded to completion but with multiple permission denied errors.
So still no root.
You can download the acer drivers from their website.
Click to expand...
Click to collapse
because write permissions on /data/
iconia tab B1
Je cherche tout comme vous un moyen de rooter cette petite tablette et je le fais savoir comme ça si quelqu'un a une solution ça motivera peut-être à faire une rom ou au moins une façon de la rooter.:fingers-crossed:
Merci à tous!!
quickstyler said:
because write permissions on /data/
Click to expand...
Click to collapse
Any idea how to rectify it?
R: [Q] Acer Iconia B1 A71 Root
can someone post the apk of the launcher B1? I would like to try it on my A100
Inviato dal mio A100 con Tapatalk 2
mripfreely said:
Any idea how to rectify it?
Click to expand...
Click to collapse
not really.. i also saw the full source code from acer on their website - isn't this a starterkit for a new rom
pakisan said:
can someone post the apk of the launcher B1? I would like to try it on my A100
Inviato dal mio A100 con Tapatalk 2
Click to expand...
Click to collapse
Here's the launcher I got off my device. Not sure if these are the files you want. Lemme know if you have any specific instructions
quickstyler said:
not really.. i also saw the full source code from acer on their website - isn't this a starterkit for a new rom
Click to expand...
Click to collapse
Yep, now we just need to wait for someone to make a ROM and recovery
sorry for posting here but since there is no b1-a71 forum... How it's performance in 3d games? order and chaos / modern combat 3/4??? hows battery life?
mripfreely said:
Acer recently released the ADB drivers for this tablet. So there no need to use the MT65xx drivers anymore.
In one of my tries the bin4ry method actually proceeded to completion but with multiple permission denied errors.
So still no root.
You can download the acer drivers from their website.
Click to expand...
Click to collapse
How many tries did it take for it to proceed to completion? If it passes to the reboot stage, you should at least have a root shell in "adb shell" after the reboot unless the vulnerability has been patched.
Bad news
Code:
Package com.android.settings is system level with no agent
The bin4ry exploit has been patched. Fastboot and SP Flash tool doesn't seem to work without some kind of authentication. So unless the flashing utilities are leaked from Acer or a new exploit has been identified, we won't be able to root this for the time being.
root and after ? otg ?
hello all, even if root access is not for now (but I hoped it will come) do you know if the tablet has the harware (chipset?) for suporter USB-HOST function?
ps: sorry for my bad English
I've just ordered one of this. It should be mine by the start of the next week and the I can try testing some root methods....... Keep in touch
Hello,
I've got an Allview A4All bricked by rooting (following the tutorial on the site allviewa4all(dot)weebly(dot)com), got stuck at step 13, after that the phone won't boot up at all, nor the flash mode (connecting the phone without battery) does not work. Tried every button combination possible to try to start the phone, but it won't respond, neither communicate via USB. Does someone have an idea?
Thanks in advance!
eddie303 said:
Hello,
I've got an Allview A4All bricked by rooting (following the tutorial on the site allviewa4all(dot)weebly(dot)com), got stuck at step 13, after that the phone won't boot up at all, nor the flash mode (connecting the phone without battery) does not work. Tried every button combination possible to try to start the phone, but it won't respond, neither communicate via USB. Does someone have an idea?
Thanks in advance!
Click to expand...
Click to collapse
si eu am patit acelasi lucru. cum ai rezolvat problema?
Translation: The same thing happened to me. How did you fix the problem?
Metoda de recuperare telefon mort! cu firmware Airis TM350
Instalati driverele USB VCOM Driver si PL2303_Prolific_DriverInstaller_v1417
Opriti telefonul,scoateti bateria
Deschideti flash tools
selectati ,,MT6575_Android_scatter,,
Click pe SCI Download si apasati download
Hi guys.
I own this "Notebook"
Hardware is a Quad Rk3188 an OS is Android 4.2.2
my problem is that the generic root method for RK3188 does nothing else but prints one error msg after an other.
I have the sources for the tab, but i don't exactly know where to start looking for exploits or backdors.
Any Help would be appreciated.
Can't help rooting your device, haven't rooted any of my Android devices before and will probably not root my A10 ether.
But me too got this "Android Notebook" and glad to see some one else having it.
Of all apps at App Store was there only one app that wasn't compatibel whit the Lenovo A10. A broadband speed measuring app. That I can live without.
Using mine A10 for wordprocessing, mostly.
Yeah I've tried several exploits and rooting methods by now and none of them was working.. i couldn't even get Fastboot working, so i can't try booting into CWM -.- ... but the device is working really good so I'm not that unhappy
Blåburk said:
Can't help rooting your device, haven't rooted any of my Android devices before and will probably not root my A10 ether.
But me too got this "Android Notebook" and glad to see some one else having it.
Of all apps at App Store was there only one app that wasn't compatibel whit the Lenovo A10. A broadband speed measuring app. That I can live without.
Using mine A10 for wordprocessing, mostly.
Click to expand...
Click to collapse
I succeeded with the kingo android root app.
Confirmed
Thanks pal .. exactly this thing did it for me .. now i can use rooted A10 .. ... and so it begins
loskarlitos said:
I succeeded with the kingo android root app.
Click to expand...
Click to collapse
Bonjour, j'ai essayé de rooter mon appareil avec Kingo mais je rencontre quelques problèmes. Kingo indique "no device connected" alors que mon appareil est bien connecté à mon ordinateur. Windows n'arrive pas à installer le driver de mon appareil. Voici ce que j'ai dans mon gestionnaire de périphérique. J'ai essayé de mettre à jour le pilote, sans succès.
Hello, I tried to root my Ideapas A10 with Kingo but I am having some problems. Kingo says "no device connected" while my device is connected to my computer. Windows can not install the driver for my device. Here is what I have in my device manager:
www*noelshack*com/2014-03-1389700608-a10problem.png (I just signed up, so I do not have the right to post links, but here's a screenshot. replace "*" with ".")
I tried to update the driver without success. Thank you for your help and sorry for my bad English.
Titouskylive said:
Bonjour, j'ai essayé de rooter mon appareil avec Kingo mais je rencontre quelques problèmes. Kingo indique "no device connected" alors que mon appareil est bien connecté à mon ordinateur. Windows n'arrive pas à installer le driver de mon appareil. Voici ce que j'ai dans mon gestionnaire de périphérique. J'ai essayé de mettre à jour le pilote, sans succès.
Hello, I tried to root my Ideapas A10 with Kingo but I am having some problems. Kingo says "no device connected" while my device is connected to my computer. Windows can not install the driver for my device. Here is what I have in my device manager:
www*noelshack*com/2014-03-1389700608-a10problem.png (I just signed up, so I do not have the right to post links, but here's a screenshot. replace "*" with ".")
I tried to update the driver without success. Thank you for your help and sorry for my bad English.
Click to expand...
Click to collapse
i had the same issue .. switching ADB-Debug mode off and on again helped me out.. (you sure have Debug Mode enabled?)
hell_fire79 said:
i had the same issue .. switching ADB-Debug mode off and on again helped me out.. (you sure have Debug Mode enabled?)
Click to expand...
Click to collapse
Yes my debug mode is enabled . I tried to switch it off and on but it doesn't work. Thank you for your help.
Great to see it's been successfully rooted.
Can you get the LinuxOnAndroid app to work? Some apps such as Gimp and LibreOffice don't really have equivalents for power users in Android.
If we can get it to work, it's the best of both worlds
JLIT99 said:
Great to see it's been successfully rooted.
Can you get the LinuxOnAndroid app to work? Some apps such as Gimp and LibreOffice don't really have equivalents for power users in Android.
If we can get it to work, it's the best of both worlds
Click to expand...
Click to collapse
Haven't tried yet .. also i don't know if the default kernel supports loops devices which are needed for linux on android ... i will test the next few days and post my experiences.
Lenovo Ideapad A10 Kingo Root
Hi, how did you manage to root A10 with Kingo?
I have a problem that Kingo cannot connect to my "notebook"
After I connect via USB it shows connecting... and after several tries it stops with "No device connected" in the application status bar.
I have USB debugging mode turned on. I've also tried to disable and enable it few times. Still no connection.
I use Windows 8.1 64bit but also tried to connect from WIndows 7 64bit - no connection
I have Android 4.2.2 installed on my Lenovo Ideapad A10 with latest updates (build JDQ39.A10_S020_131203).
Any advices?
-----------------
Mix
Do you have your drivers installed properly? .. esp. can you connect using ADB? (try this one First) .. next try disabling USB Storage - Mode.
mix2ra said:
Hi, how did you manage to root A10 with Kingo?
I have a problem that Kingo cannot connect to my "notebook"
After I connect via USB it shows connecting... and after several tries it stops with "No device connected" in the application status bar.
I have USB debugging mode turned on. I've also tried to disable and enable it few times. Still no connection.
I use Windows 8.1 64bit but also tried to connect from WIndows 7 64bit - no connection
I have Android 4.2.2 installed on my Lenovo Ideapad A10 with latest updates (build JDQ39.A10_S020_131203).
Any advices?
-----------------
Mix
Click to expand...
Click to collapse
No drivers
I bought an ideapad a10 but the drivers are not included in the box. When i try to connect via pc (win8.1) and enable adb i noticed that the drivers are not installed in my pc thats why i cant connect to kingoapp. Can someone give me a link of this driver. Thanks.
Try the Lenovo homepage and download the sources for the tablet, there is a flashtool included and besides that are the drivers .. maybe you have to install these manually ..
jobmasterlester said:
I bought an ideapad a10 but the drivers are not included in the box. When i try to connect via pc (win8.1) and enable adb i noticed that the drivers are not installed in my pc thats why i cant connect to kingoapp. Can someone give me a link of this driver. Thanks.
Click to expand...
Click to collapse
hell_fire79 said:
Try the Lenovo homepage and download the sources for the tablet, there is a flashtool included and besides that are the drivers .. maybe you have to install these manually ..
Click to expand...
Click to collapse
There is no download sources for ideapad a10. I checked every single link in the site and then i ended up nothing.. I also search in google but it only takes me to manuals and user guides.
of there is
http://download.lenovo.com/consumer/open_source_code/a10_open_source.tar.gz
jobmasterlester said:
There is no download sources for ideapad a10. I checked every single link in the site and then i ended up nothing.. I also search in google but it only takes me to manuals and user guides.
Click to expand...
Click to collapse
hell_fire79 said:
of there is
http://download.lenovo.com/consumer/open_source_code/a10_open_source.tar.gz
Click to expand...
Click to collapse
Thanks. Downloading.
jobmasterlester said:
Thanks. Downloading.
Click to expand...
Click to collapse
Hy guys! I can' find where is a flashtool.... thanks
when you've downloaded the source files tar.gz, extract this archive. (use 7zip or winrar to extract)
you'll find the drivers in A10_Open_Source_20130827\kernel\rktools\RK3188DevelopTool\rockusb.zip
these should work, since they are shipped with the sources
defffos said:
Hy guys! I can' find where is a flashtool.... thanks
Click to expand...
Click to collapse
hell_fire79 said:
when you've downloaded the source files tar.gz, extract this archive. (use 7zip or winrar to extract)
you'll find the drivers in A10_Open_Source_20130827\kernel\rktools\RK3188DevelopTool\rockusb.zip
these should work, since they are shipped with the sources
Click to expand...
Click to collapse
ok I found them! but how do I make them install? I have windows vista and if I update driver and I select the folder where the driver always tells me impossible ... thanks
Hi guys,
I have created this thread in order to have a clean and updated one with links for dload firmware, info, changelog and other guides which will be added later.
Latest firmware link added on 29.09.2020 is LIO-L29 v10.1.0.259 hw-eu (C432E6R8P1) dload firmware. I will keep updating this OP with further dload firmware, so that we have them all in one place and easy for you guys to acces them.
!!! USING dload FW in order to update your device WILL DO A FULL WIPE & WILL ERASE YOUR INTERNAL MEMORY, so DON'T FORGET TO BACKUP BEFORE (with HiSuite version 10.0.1.100 or COPY your stuffs to a PC) !!!
Huawei MATE 30 PRO LIO-L29 C432 HW-EU (C432E6R8P1) v10.1.0.259
androidhost.ru (faster download using phone) LIO-L29 10.1.0.259(C432E6R8P1) FIRMWARE EMUI10.1.0 05016HWD online
Huawei MATE 30 PRO LIO-L29 C432 HW-EU (C432E6R8P1) v10.0.0.193
androidhost.ru (faster download using phone) LIO-L29 10.0.0.193(C432E6R8P1) Firmware EMUI10.0.0 05016LAM online
HOW TO flash dload FW guide:
UPGRADE USING OTG ADAPTER or OTG CABLE + USB MEMORY STICK
1. Extract dload folder from downloaded archive above (dload folder with all 3 zips inside) and copy to your memory stick / drive (formatted as exFat or NTFS) that will be used to upgrade
2. BACKUP your stuffs if you haven't done yet
3. Factory Reset your phone (optional) and POWER it OFF
4. Insert your OTG + memory stick / drive with the correct firmware on it (dload folder with all 3 zips inside)
5. Press Power button and as it vibrates and shows Huawei + Android logo, hit 3 times Power button and device will reboot again in eRecovery mode. When in menu, select Update mode, then select Memory card/OTG update mode and it should start the update.
UPGRADE USING Huawei NM Card
1. Extract dload folder from downloaded archive above (dload folder with all 3 zips inside) and copy to your Huawei NM Card
2. BACKUP your stuffs if you haven't done yet
3. Factory Reset your phone (optional) and POWER it OFF
4. Press Power button and as it vibrates and shows Huawei + Android logo, hit 3 times Power button and device will reboot again in eRecovery mode. When in menu, select Update mode, then select Memory card/OTG update mode and it should start the update.
OR
If you want to do it from sistem after you've made your backup and had an factory reset (optional), insert OTG + memory stick / drive OR copy dload folder with all 3 zips inside to your Huawei NM Card and dial this on dialer *#*#2846579#*#* and select 4.Software Update then 1.Memory card Upgrade . If your inserted card / memory stick or USB drive or Huawei NM Card it's recognised and contains the right files, phone will restart and start flashing the firmware. At the end when it's restarting after succesfully flashed firmware, you can remove the OTG (if you used one).
How to check for update using eRecovery:
In order to acces eRecovery (using this method in order to update WON'T wipe your phone data, it's acting like an normal OTA), follow these steps:
1. Power OFF your device
2. Press Power button and as it vibrates and shows Huawei + Android logo, hit 3 times Power button and device will reboot again in eRecovery mode
3. When in menu, select Update mode, then select eRecovery mode then Update and recover system then Download update and recover. Connect it to Wi-Fi and it should start the update. If it's still the version you're atm, you can hit Cancel and then Restart. If it's a newer version than the one installed, let it download and update. At the end, it will restart to system.
Clean and succesfully flashing, m8s :highfive:
CHANGELOG for LIO devices dload/OTA firmware v10.1.0.259 :
1.App
Adds the Petal Search app to the home screen for easier app searches.
2. System
Optimizes the deterministic latency engine to provide you with a smoother system user experience.
3. Security
Integrates Android security patches released in August 2020 for improved system security.
______________________________________________________________________________________________________________________
IF you want to remove ads and you have no root or don't wan't to block your VPN or use Blokada, you can use my trick, it works on both WI-FI and mobile networks, as good as Adaway is doing :
Just set: Settings > Wi-Fi & Internet > Private DNS > dns.adguard.com OR dot-de.blahdns.com then press Save & enjoy ad free browsing without any additional app. These are secure DNS servers that have integrated ad blocking. Adguard is a Russian company, blahdns is a small hobby project with a good history.
Extra step for Chrome users:
- Open Chrome, type in chrome://flags, search for async DNS resolver (#enable-async-dns) and choose disabled in the drop down menu, otherwise Chrome could use a built in dns resolver which does not block ads.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
In order to remove Huawei bloatware (and get a better battery lifetime) without root access and using ADB & USB Debugging, please check my thread from the link bellow:
Remove Huawei Bloatware Without Root Access - using ADB & USB Debugging
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
As a comprehensive battery optimization mini guide to achieve the best possible SOT's on Huawei phones go to Settings/Battery/App launch and disable the app or give permission to the app you need to run in background (ex. NOT working in background Netflix is set to Managed manually with NO Auto-launch, NO Secondary launch and NO Run in background; WORKING AUTO - OUTLOOK - Manage automatically). Next you can customize notifications separately for any customisable app in own settings.
Hello my friend, just tested this firmware on a friends Mate 30 Pro (LIO-L29 C432E6R7P1) and firmware flashed succesfull. So this is working for his device and followed your post from P30 Pro thread and installed him all the Google apps. All working great for him :good:
adambrown said:
Hello my friend, just tested this firmware on a friends Mate 30 Pro (LIO-L29 C432E6R7P1) and firmware flashed succesfull. So this is working for his device and followed your post from P30 Pro thread and installed him all the Google apps. All working great for him :good:
Click to expand...
Click to collapse
Thanks for letting me know, m8. Really appreciate it :highfive:
Sent from my LIO-L29 using Tapatalk
Can I get OTA after change these ROM ?
winkhant said:
Can I get OTA after change these ROM ?
Click to expand...
Click to collapse
YES, you will get OTA updates the same as now, when your device SN/IMEI is whitelisted for update on Huawei servers.
This firmware is the oficial stock one, with no modifications and is used by Huawei Service Centers after they've change the motherboard of a device or in order to revive a softbricked device or for their internal tests ?
Sent from my LIO-L29 using Tapatalk
Huawei mate 30 pro 5g
Hello guys . I gonna do this switch from a Chinese Ron I can't wait more. But I want to ask , I have a mate 30 pro 5g version , it's ready for me or it's only for 4g version on mate 30 pro? I'm sorry if I write on wrong section. Thank you
Ends87 said:
Hello guys . I gonna do this switch from a Chinese Ron I can't wait more. But I want to ask , I have a mate 30 pro 5g version , it's ready for me or it's only for 4g version on mate 30 pro? I'm sorry if I write on wrong section. Thank you
Click to expand...
Click to collapse
Hi m8,
This firmware is ONLY for INTERNATIONAL 4G version of Mate 30 Pro. Using it on a 5G Chinese version it will softbrick your device.
Wait for your OTA/eRecovey update and don't flash this version.
Sent from my LIO-L29 using Tapatalk
Huawei mate 30 pro 5g
Thank you friend. Do you know maybe where is possible to have this ota / erecovery update on my phone? Sooner or later . ? Thank you again.
Ends87 said:
Thank you friend. Do you know maybe where is possible to have this ota / erecovery update on my phone? Sooner or later . ? Thank you again.
Click to expand...
Click to collapse
Nope, only a dload firmware for your cust can get you updated before your device get whitelisted for update on Huawei servers to gwt OTA or eRecovery
Sent from my LIO-L29 using Tapatalk
Any update ?
Ogy77 said:
Any update
Click to expand...
Click to collapse
Nope ?, but it seems that they are testing some features for Mate 30 Pro on the Chinese market and have released a beta firmware to those enrolled for testing - https://www. huaweicentral dot com/new-features-first-emui-10-beta-rolling-out-for-huawei-mate-30-series/ . So it may take a whille untill they release a new build.
As soon as i get it, i will update OP with it ?
Sent from my LIO-L29 using Tapatalk
SilviuO said:
Nope ?, but it seems that they are testing some features for Mate 30 Pro on the Chinese market and have released a beta firmware to those enrolled for testing - https://www. huaweicentral dot com/new-features-first-emui-10-beta-rolling-out-for-huawei-mate-30-series/ . So it may take a whille untill they release a new build.
As soon as i get it, i will update OP with it ?
Sent from my LIO-L29 using Tapatalk
Click to expand...
Click to collapse
Ok I hope soon. I change p30 pro for mate 30 pro,maybe you remember me from p30 pro foruma ?
Ogy77 said:
Ok I hope soon. I change p30 pro for mate 30 pro,maybe you remember me from p30 pro foruma
Click to expand...
Click to collapse
Yes m8, i remember you and i'm still active on the other forum, 'cause i have both devices (untill i will switch to P40 Premium as my personal device).
Keep an eye here for new update or in the Software Updates thread .
Sent from my LIO-L29 using Tapatalk
Update
SilviuO said:
Yes m8, i remember you and i'm still active on the other forum, 'cause i have both devices (untill i will switch to P40 Premium as my personal device).
Keep an eye here for new update or in the Software Updates thread .
Sent from my LIO-L29 using Tapatalk
Click to expand...
Click to collapse
U going to buy the best camera smartphone in the world actually... Lucky you . I hope the updates with international firmware coming fast .
Ends87 said:
U going to buy the best camera smartphone in the world actually... Lucky you . I hope the updates with international firmware coming fast .
Click to expand...
Click to collapse
We'll see at that time, but my guess is that they will release 2-3 firmwares faster after people will start buying (as they did every time when launching a flagship) to improve camera software or other stuffs, then they will focus on launching Mate 40 Pro and P40 Pro will get the same treatment as P30 Pro received from October last year (getting some security patches, the update to EMUI 10) untill now...
Sent from my LIO-L29 using Tapatalk
Mate 30 pro fallos de pantalla
Problemas con mi mate 30 pro, 5 días de uso, apariencia de pantalla quemada
oremor305 said:
Problemas con mi mate 30 pro, 5 días de uso, apariencia de pantalla quemada
Click to expand...
Click to collapse
That's bad, you better get it to a Huawei service center, it's more than sure covered by warranty ?. They will have to replace your unit or change the screen.
Sent from my LIO-L29 using Tapatalk
SilviuO said:
That's bad, you better get it to a Huawei service center, it's more than sure covered by warranty . They will have to replace your unit or change the screen.
Sent from my LIO-L29 using Tapatalk
Click to expand...
Click to collapse
Amigo ya es la segunda unidad que me dan, el primo tenía una especie de fugaz de luz como gluegate, me dieron uno nuevo, y este presenta esa especie de quemado, dura unos instantes pero al estar estático unos instantes en el cajón de aplicaciones o con el teclado, vuelve y aparecen
my MDZ 22 AB was running great on 8.1 and when it upgraded to 9.0 i didnt like the new version so i wanted to downgrade. i sourced several firmware files for 8.1. they were diff files sizes. looks like the first one was for like model or was corrupted and the box was bricked...only the red diode in rear and no access to recovery. after searching around i successfully unbricked it using the "other" file for 8.1 and all now seemed normal, i have access to recovery menu and it will boot up to the initial wizard mode where you are pressing the "OK" button then later have to press both the "home and app's keys" to pair the remote.
the problem is that the above operations fail: the "OK" button and the "home and app's keys" are not being received by the box. the "power" button also doesnt work. the batteries are fresh i charged them. during the time im pressing the OK key over and over a message pops up saying, "cannot connect to internet". FURTHER info: i can successfully boot into recovery mode using the remote by using both the back arrow and the OK key and applying power to unit. once inside recovery all remote keys work perfectly.
why would the OK key work okay in recovery but not during bootup?
do i have to "reset" my remote? is there a way?
Hi,
Unfortuantely I won't be able to help you on your request but I would be curious on having more details on the way you used to unbrick your box?
I am stuck on the topic for a week now and haven't been able to do anything...
Many thanks in advance,
Regards,
i used this link to fix mine but im still having remote issues they arent
https://forum.xda-developers.com/an...c/help-to-unbrick-mi-box-s-mdz-22-ab-t4020279
make sure you DL the link for your unit....MDZ 22 AB? 2 links are provided one is for the Mi Box 3 not the S (MDZ 22 AB)
this link show step by step instructions from the russian in the first post but here in english. however, in this pic where he shows which pins to short together to initiate the restore of the rom, his pics show the Mi Box 3 NOT the Mi Box S. link here however only thing wrong is the pin shorting pic. i can send you pic of the correct oins for the MDZ 22 AB for Mi Box S (only). not sure how to post on this forum?
nedro018 said:
i used this link to fix mine but im still having remote issues they arent
https://forum.xda-developers.com/an...c/help-to-unbrick-mi-box-s-mdz-22-ab-t4020279
make sure you DL the link for your unit....MDZ 22 AB? 2 links are provided one is for the Mi Box 3 not the S (MDZ 22 AB)
this link show step by step instructions from the russian in the first post but here in english. however, in this pic where he shows which pins to short together to initiate the restore of the rom, his pics show the Mi Box 3 NOT the Mi Box S. link here however only thing wrong is the pin shorting pic. i can send you pic of the correct oins for the MDZ 22 AB for Mi Box S (only). not sure how to post on this forum?
Click to expand...
Click to collapse
looking for advice from bigtalker or others here about this remote issue. when i boot up from freshly installed 8.1 or 9.0 installs, the operating system comes to the "wizard" after a fresh startup and you are asked to press the OK button and or later the 2 "pairing" buttons. my remote is simply not responding to the main Mi Box S unit. i cant get past this wizard.
i have changed my batteries many times no help. i have removed them for 10 moin plus no help.
question(s) (since i may not have a functioning remote i dont know):
1) is there supposed to be a light emitting from the front of the remote?
2) is there a way to "reset" the remote?
3) i cannot locate on Net purchase of a OEM remote for the Mi Box S MDZ 22 AB so is there a "universal" option?
thanks to all for any help. read this entire thread above before answering and special note: the "OK" button does NOT work during initial boot ups from the operating system however it DOES work when im navigating around inside of the Mi Box S recovery menu. how is that possible?
currently, my remote is not emitting any lights at all whatsoever when pressing any buttons. i think it is supposed to do so. so the remote is not working in operating system (OS) interaction but it DOES work inside recovery.
this remote is supposed to be both IR and BT compatible....maybe the BT part is broke (the part that interacts in the OS) but the IR signal (which works during recovery?) is why the remote works ok there?
My issue is same as you, at the time of dowgrading my mi box s is bricked, only red light glows and box doen't boot up.
sushnimo said:
My issue is same as you, at the time of dowgrading my mi box s is bricked, only red light glows and box doen't boot up.
Click to expand...
Click to collapse
check the links above you can unbrick yours i did.
but you are off topic here my post and problem is about the "remote control unit" not pairing upon the first bootup stage of the mi box OS... at this satge you cannot use a cell phone app to engage with the OS you need a remote. i cannot setup my mi box fresh installs because i cant get past the initial wizard of interacting with the remote.
my remote is not emitting any lights from the front when pressing buttons. does yours? is no lights normal? are these lights from IR (infrared) signals or BTooth signals?
repeat this topic is about my REMOTE issues i am not bricked any more thanks
need help in unbricking my mi-box
how to check is my remote emitting any lights from the front when pressing buttons.?
sushnimo said:
how to check is my remote emitting any lights from the front when pressing buttons.?
Click to expand...
Click to collapse
there's a small diode on the front face of remote. it supposed to blink "green" i believe when you are pressing buttons. i was told this by a friend who has same MI box unit and i had him test his remote....he said it was blinking green signal lights.
i have unbricked my mi Box S MDZ 22 AB. it boots up OK now. i can successfully go to Pie version or back to Oreo at will. my problem is that i cant get past the intial startup wizard because at bootup the remote wont talk to the Mi Box. im stuck at the wizard. in either Pie 8 or Oreo 8. i dont how the remote suddenly "died" or how to do a hard "reset" of it. ive left the batteries out for days. the batteries are fresh.
so ive order both a new Mi Box S with Oreo on it from china and also a new Mi Box S remote from china as well. they have not arrived in over 4 or 5 weeks prob due the the chinese new year delay. for now im stuck.
any other experts here know how to tear open the remote and "revive" it???
nedro018 said:
check the links above you can unbrick yours i did.
but you are off topic here my post and problem is about the "remote control unit" not pairing upon the first bootup stage of the mi box OS... at this satge you cannot use a cell phone app to engage with the OS you need a remote. i cannot setup my mi box fresh installs because i cant get past the initial wizard of interacting with the remote.
my remote is not emitting any lights from the front when pressing buttons. does yours? is no lights normal? are these lights from IR (infrared) signals or BTooth signals?
repeat this topic is about my REMOTE issues i am not bricked any more thanks
Click to expand...
Click to collapse
nedro018 said:
there's a small diode on the front face of remote. it supposed to blink "green" i believe when you are pressing buttons. i was told this by a friend who has same MI box unit and i had him test his remote....he said it was blinking green signal lights.
i have unbricked my mi Box S MDZ 22 AB. it boots up OK now. i can successfully go to Pie version or back to Oreo at will. my problem is that i cant get past the intial startup wizard because at bootup the remote wont talk to the Mi Box. im stuck at the wizard. in either Pie 8 or Oreo 8. i dont how the remote suddenly "died" or how to do a hard "reset" of it. ive left the batteries out for days. the batteries are fresh.
so ive order both a new Mi Box S with Oreo on it from china and also a new Mi Box S remote from china as well. they have not arrived in over 4 or 5 weeks prob due the the chinese new year delay. for now im stuck.
any other experts here know how to tear open the remote and "revive" it???
Click to expand...
Click to collapse
When I press remote key, green diode not blinking while pressing buttons. and i never seen any blinking diode when my mi box was working. So how ti unbrick it, can you share procedure with me on my mail. In my MI Box only red light is on in 3.5 mm jack, and and in TV it shows no HDMI Connected. please help..
My Mail ID Is- [email protected]
nedro018 said:
i used this link to fix mine but im still having remote issues they arent
https://forum.xda-developers.com/an...c/help-to-unbrick-mi-box-s-mdz-22-ab-t4020279
make sure you DL the link for your unit....MDZ 22 AB? 2 links are provided one is for the Mi Box 3 not the S (MDZ 22 AB)
this link show step by step instructions from the russian in the first post but here in english. however, in this pic where he shows which pins to short together to initiate the restore of the rom, his pics show the Mi Box 3 NOT the Mi Box S. link here however only thing wrong is the pin shorting pic. i can send you pic of the correct oins for the MDZ 22 AB for Mi Box S (only). not sure how to post on this forum?
Click to expand...
Click to collapse
Hi my friend,
Can you email me the pic of the correct pins to short for the MDZ 22 AB for Mi Box S?
my email : [email protected]
Many thanks!
nedro018 said:
my MDZ 22 AB was running great on 8.1 and when it upgraded to 9.0 i didnt like the new version so i wanted to downgrade. i sourced several firmware files for 8.1. they were diff files sizes. looks like the first one was for like model or was corrupted and the box was bricked...only the red diode in rear and no access to recovery. after searching around i successfully unbricked it using the "other" file for 8.1 and all now seemed normal, i have access to recovery menu and it will boot up to the initial wizard mode where you are pressing the "OK" button then later have to press both the "home and app's keys" to pair the remote.
the problem is that the above operations fail: the "OK" button and the "home and app's keys" are not being received by the box. the "power" button also doesnt work. the batteries are fresh i charged them. during the time im pressing the OK key over and over a message pops up saying, "cannot connect to internet". FURTHER info: i can successfully boot into recovery mode using the remote by using both the back arrow and the OK key and applying power to unit. once inside recovery all remote keys work perfectly.
why would the OK key work okay in recovery but not during bootup?
do i have to "reset" my remote? is there a way?
Click to expand...
Click to collapse
I FOUND THE PROBLEM
You flashed an old/unstable image (r363) with the bridge
I FOUND A SOLUTION, YES THATS RIGHT
Flash the newer stable image (r699) with an update.zip file via an usb-stick in the recovery mode
Here is the Mi Box S Android 8.1 Oreo update direct link
Source of the stable image
Reboot after the flash
No wait and use the OK-Button multiple times until a noise comes to be able to use the remote keys
DONE
Hasenkampf said:
I FOUND THE PROBLEM
You flashed an old/unstable image (r363) with the bridge
I FOUND A SOLUTION, YES THATS RIGHT
Flash the newer stable image (r699) with an update.zip file via an usb-stick in the recovery mode
Here is the Mi Box S Android 8.1 Oreo update direct link
Source of the stable image
Reboot after the flash
No wait and use the OK-Button multiple times until a noise comes to be able to use the remote keys
Can you please give me full instructions for flashing firmware from pendrive
Click to expand...
Click to collapse
Hasenkampf said:
I FOUND THE PROBLEM
You flashed an old/unstable image (r363) with the bridge
I FOUND A SOLUTION, YES THATS RIGHT
Flash the newer stable image (r699) with an update.zip file via an usb-stick in the recovery mode
Here is the Mi Box S Android 8.1 Oreo update direct link
Source of the stable image
Reboot after the flash
No wait and use the OK-Button multiple times until a noise comes to be able to use the remote keys
Can you please give me full instructions for flashing firmware from oendrive
Click to expand...
Click to collapse
Hasenkampf said:
I FOUND THE PROBLEM
You flashed an old/unstable image (r363) with the bridge
I FOUND A SOLUTION, YES THATS RIGHT
Flash the newer stable image (r699) with an update.zip file via an usb-stick in the recovery mode
Here is the Mi Box S Android 8.1 Oreo update direct link
Source of the stable image
Reboot after the flash
No wait and use the OK-Button multiple times until a noise comes to be able to use the remote keys
DONE
Click to expand...
Click to collapse
Thank you! I was frustrated when my remote didnt work after unbricking my mi box s. Used your update method and voila - everything works perfect now, but I used this update Link instead, since your direct update link didn't fix my problem. You're the real MVP
Hasenkampf said:
I FOUND THE PROBLEM
You flashed an old/unstable image (r363) with the bridge
I FOUND A SOLUTION, YES THATS RIGHT
Flash the newer stable image (r699) with an update.zip file via an usb-stick in the recovery mode
Here is the Mi Box S Android 8.1 Oreo update direct link
Source of the stable image
Reboot after the flash
No wait and use the OK-Button multiple times until a noise comes to be able to use the remote keys
DONE
Click to expand...
Click to collapse
Hello,
I have the exact same issue. But since remote is not responsive after flash with bridge I cannot enter recovery mode using the OK+BACK button combination on the remote. Is there a stable image to be flashed over usb or an alternative way to enter recovery mode?
I finally managed to restore my Mi Box S from r363 which I have flashed with USB Burning Tool and had lost remote control connectivity and wifi connectivity (bad MAC address 02:00:00:00:00:00) back to fully working r3933 (last version) so I would like to share it with you.
In my case tha OK+BACK button combination did not work to enter the recovery menu. So this is what I did.
You will need Amlogic CustomizationTool v2.0.10 for this. You will also need r2216 and r3933 recovery images.
First download and unzip r2216. We will need boot.img file found in this file.
Install Amlogic CustomizationTool. Run it and press Load button. Check all the first 4 Level Low options, click ok and a window will open to select burn image. Select the r363 buggy image and click Open. The firmware will unpack and there will be an "Unpack Success" dialog box where you click ok. Go to "Advance" tab and press the "Kernel" button on the right. A dialog will appear with the currect boot.partition. Select it and press Replace. Browse to the boot.img file from r2216 recovery. Verify your selection in next dialog box and cloce the dialog with the partitions. Press the Pack button and save the new generated image.
Format a USB stick with FAT32 and place r3933 recovery image renamed to update.zip in the stick.
Flash the image generated above with USB Burning Tool that works for you using the same method that you flashed r393. I used Amlogic USB Burning Tool v2.2.4.
Boot the box after the flash with a USB hub connected with a usb keyboard only. I guess this kernel does not match with the r363 system so the recovery menu for 8.1.0/r363 pops up. Now plug the USB stick in the hub. My box didn't boot with USB stick connected that is why I advice to plug the stick after the recovery menu appears.
Select "Wipe data/factory reset" with the keyboard and verify. Then select "Apply update from EXT", then "Update from udisk" then select the update.zip from the stick. It will verify the package (this might take 10 minutes) and it will update the recovery.img and reboot.
The recovery menu will appear again but now it is the newer version from r3933. Redo the above (wipe data, update from the same update.zip). This time the whole update is flashed and there is also a graphic with the progress. Let it finish.
After the update reboot the box and you should be back!
P.S.: I did not erase the bootloader via the option in the USB burning tool so my DRM license for Netflix survived. Please make sure not to check this option. If you started with the option checked abort immediately and you will save the bootloader since it is the very last part flashed. Restart the procedure from scratch with the option unchecked.
babylonx said:
I finally managed to restore my Mi Box S from r393 which I have flashed with USB Burning Tool and had lost remote control connectivity and wifi connectivity (bad MAC address 02:00:00:00:00:00) back to fully working r3933 (last version) so I would like to share it with you.
In my case tha OK+BACK button combination did not work to enter the recovery menu. So this is what I did.
You will need Amlogic CustomizationTool v2.0.10 for this. You will also need r2216 and r3933 recovery images.
First download and unzip r2216. We will need boot.img file found in this file.
Install Amlogic CustomizationTool. Run it and press Load button. Check all the first 4 Level Low options, click ok and a window will open to select burn image. Select the r393 buggy image and click Open. The firmware will unpack and there will be an "Unpack Success" dialog box where you click ok. Go to "Advance" tab and press the "Kernel" button on the right. A dialog will appear with the currect boot.partition. Select it and press Replace. Browse to the boot.img file from r2216 recovery. Verify your selection in next dialog box and cloce the dialog with the partitions. Press the Pack button and save the new generated image.
Format a USB stick with FAT32 and place r3933 recovery image renamed to update.zip in the stick.
Flash the image generated above with USB Burning Tool that works for you using the same method that you flashed r393. I used Amlogic USB Burning Tool v2.2.4.
Boot the box after the flash with a USB hub connected with a usb keyboard only. I guess this kernel does not match with the r393 system so the recovery menu for 8.1.0/r363 pops up. Now plug the USB stick in the hub. My box didn't boot with USB stick connected that is why I advice to plug the stick after the recovery menu appears.
Select "Wipe data/factory reset" with the keyboard and verify. Then select "Apply update from EXT", then "Update from udisk" then select the update.zip from the stick. It will verify the package (this might take 10 minutes) and it will update the recovery.img and reboot.
The recovery menu will appear again but now it is the newer version from r3933. Redo the above (wipe data, update from the same update.zip). This time the whole update is flashed and there is also a graphic with the progress. Let it finish.
After the update reboot the box and you should be back!
P.S.: I did not erase the bootloader via the option in the USB burning tool so my DRM license for Netflix survived. Please make sure not to check this option. If you started with the option checked abort immediately and you will save the bootloader since it is the very last part flashed. Restart the procedure from scratch with the option unchecked.
Click to expand...
Click to collapse
hi i'm follow your steps but i have no luck. i'm a little confused with 2 things. when you say r393 did you mean r363 right? and in the part when you replace boot.partition and ask if you want continue you select yes and close the dialog and then pack the new image?
my mac address still it's 02:00:00:00:00:00 and bluetooth completely dead
Sorry, I was kind of exhausted yesterday and I didn't remeber the exact version number, yes I mean r363 obviously. It is the only burn image I found anyway.
And yes you cloce the dialog after you confirm replace of kernel boot.img and then Pack. You are asked for a name to save to.
Do you know what version you were before bricking with r363? I was at r3933 (last one from October 2021). If you were at different version maybe you should try to restore to that version instead of r3933. Here you can find other versions:
Official Stock Firmware Thread - Mi Box (MDZ-16-AB and MDZ-22-AB)
Disclaimer Flash these at your own risk, I am not responsible for any problems that may occur. It is NOT possible to easily downgrade firmware using recovery once upgraded. Downgrading requires a special cable and opening of the box. I am not...
forum.xda-developers.com
babylonx said:
I finally managed to restore my Mi Box S from r363 which I have flashed with USB Burning Tool and had lost remote control connectivity and wifi connectivity (bad MAC address 02:00:00:00:00:00) back to fully working r3933 (last version) so I would like to share it with you.
In my case tha OK+BACK button combination did not work to enter the recovery menu. So this is what I did.
You will need Amlogic CustomizationTool v2.0.10 for this. You will also need r2216 and r3933 recovery images.
First download and unzip r2216. We will need boot.img file found in this file.
Install Amlogic CustomizationTool. Run it and press Load button. Check all the first 4 Level Low options, click ok and a window will open to select burn image. Select the r363 buggy image and click Open. The firmware will unpack and there will be an "Unpack Success" dialog box where you click ok. Go to "Advance" tab and press the "Kernel" button on the right. A dialog will appear with the currect boot.partition. Select it and press Replace. Browse to the boot.img file from r2216 recovery. Verify your selection in next dialog box and cloce the dialog with the partitions. Press the Pack button and save the new generated image.
Format a USB stick with FAT32 and place r3933 recovery image renamed to update.zip in the stick.
Flash-elje meg a fent generált képet az Ön számára megfelelő USB-író eszközzel, ugyanazzal a módszerrel, mint az r393 flashelésekor. Amlogic USB Burning Tool v2.2.4-et használtam.
A vaku után indítsa el a dobozt egy USB-elosztóval, amely csak USB-billentyűzethez van csatlakoztatva. Azt hiszem, ez a kernel nem egyezik az r363 rendszerrel, így a 8.1.0/r363 helyreállítási menüje megjelenik. Most csatlakoztassa az USB-meghajtót a hubhoz. A dobozom nem indult el, ha USB-stick van csatlakoztatva, ezért azt tanácsolom, hogy a helyreállítási menü megjelenése után csatlakoztassa a pendrive-ot.
Válassza az „Adatok törlése/gyári beállítások visszaállítása” lehetőséget a billentyűzeten, és ellenőrizze. Ezután válassza az "Apply update from EXT", majd az "Update from udisk" lehetőséget, majd válassza ki az update.zip fájlt a stickről. Ellenőrzi a csomagot (ez 10 percig is eltarthat), frissíti a recovery.img fájlt, és újraindítja a rendszert.
A helyreállítási menü ismét megjelenik, de most az r3933 újabb verziója. Ismételje meg a fentieket (adatok törlése, frissítés ugyanarról az update.zip-ről). Ezúttal a teljes frissítés fel van villantva, és van egy grafika is a folyamatról. Hadd fejezze be.
A frissítés után indítsa újra a dobozt, és vissza kell jönnie!
Ui: Nem töröltem a rendszerbetöltőt az USB-író eszköz opciójával, így a Netflix DRM-licencem megmaradt. Kérjük, ne jelölje be ezt a lehetőséget. Ha a bejelölt opcióval kezdted, azonnal szakítsd meg, és elmented a rendszerbetöltőt, mivel ez a legutolsó felvillantott rész. Indítsa újra az eljárást a nulláról úgy, hogy az opció nincs bejelölve.
Click to expand...
Click to collapse
Szia !
)Köszönöm szépen a leírást ! ) Nekem sem volt távirányító , mac cím és wifi ! de a leírásod alapján minden rendbe jött ! ))
)Köszönöm szépen !!!!!
babylonx said:
Végre sikerült visszaállítani a Mi Box S-emet az r363-ról, USB Burning Tool-al flasheltem, és elvesztettem a távirányítót és a wifi kapcsolat (rossz MAC-cím 02:00:00:00:00:00) teljesen működőképes r3933 -ra (utolsó verzió), ezért szeretném megosztani veletek.
Az én esetemben az OK+VISSZA gomb kombinációja nem működött a helyreállítási menübe való belépéshez. hát ezt tettem.
Ha szükséges lesz az Amlogic CustomizationTool v2.0.10 -re. Szüksége lesz az r2216 és r3933 helyreállítási lemezképekre is.
Először töltse le és csomagolja ki az r2216-ot. Szükségünk lesz ebben a fájlban található boot.img fájlra.
Telepítse az Amlogic CustomizationTool eszközt. Futtassa és nyomja meg a Betöltés gombot. Jelölje be az összes első 4 Level Low opciót, kattintson az OK gombra, és válassza ki az ablakot, ahol kiválaszthatja a képírást. Ki az r363 bugos képet, és kattintson a Megnyitás gombra. A firmware kicsomagol, és megjelenik egy "Sikeres kicsomagolás" párbeszédpanel, ahol kattintson az OK gombra. Lépjen az "Advance" fülre, és nyomja meg a "Kernel" gombot a jobb oldalon. Megjelenik egy párbeszédpanel a megfelelő boot.partícióval. Ki, és nyomja meg a Csere gombot. Keresse meg a boot.img fájlt az r2216 helyreállításból. én a választást a következő párbeszédpanelen, és zárja be a párbeszédpanelt a partíciókkal. Nyomja meg a Pack gombot, és mentse el az új generált képet.
Formázz meg egy USB-meghajtót FAT32-vel, és helyezd el az update.zip-re átnevezett r3933 helyreállítási képfájlt a pendrive-on.
Flash-elje meg a fent generált képet az Ön számára megfelelő USB-író eszközzel, ugyanazzal a módszerrel, mint az r393 flashelésekor. Amlogic USB Burning Tool v2.2.4-et használtam.
A vaku után indítsa el a dobozt egy USB-elosztóval, amely csak USB-billentyűzethez van csatlakoztatva. Azt hiszem, ez a kernel nem egyezik meg az r363 rendszerrel, így megjelenik a 8.1.0/r363 helyreállítási menüje. Most csatlakoztassa az USB-meghajtót a hubhoz. A nem indul el, ha USB-stick van dobozba, ezért azt tanácsolom, hogy a helyreállítási menü megjelenése után csatlakoztassa a pendrive-ot.
Az „Adatok törlése/gyári beállítások visszaállítása” lehetőség a billentyűzeten, és egyszerűen. választás az "Apply update from EXT", az "Update from udisk" lehetőségek, majd választás ki az update.zip fájlt a stickről. Ellenőrzi a csomagot (ez 10 percig is eltarthat), frissíti a recovery.img fájlt, és újraindítja a rendszert.
A helyreállítási menü ismét megjelenik, de most az r3933 újabb verziója. Ismételje meg a fentieket (adatok törlése, frissítés ugyanarról az update.zip-ről). Ezúttal a teljes frissítés fel van villantva, és van egy grafika is a folyamatról. Hadd fejezze be.
A frissítés után indítsa újra a dobozt, és vissza kell jönnie!
Ui: Nem töröltem a rendszerbetöltőt az USB-író eszköz opciójával, így a Netflix DRM-licencem megmaradt. Kérem, ne jelölje be ezt a lehetőséget. Ha a bejelölt opcióval kezdte, azonnal szakítsd meg, és elmented a rendszerbetöltőt, mivel ez a legutolsó felvillantott rész. Indítsa újra az eljárást a nulláról úgy, hogy az opció nincs bejelölve.
Click to expand...
Click to collapse
Szia !
)Köszönöm szépen a le írást ! így sikerült visszaállítani a xiaomi mi box s-t )
)Szuper munka ! )