Hello,
So the good news is - apparently we can unlock Kirin 970 now. I did the hardware testpoint mode with the HCU Client and it worked just fine! I was replacing the battery anyway so I already had access to the motherboard. The question now is - what happened to LineageOS ROMs? Looks like they just deleted all of them.
Is there anybody out there with one of them on their HDD willing to share? Google cached website is showing two of them:
lineage-16.0-20210211-nightly-charlotte-signed.zip 2/11/21
lineage-16.0-20210204-nightly-charlotte-signed.zip 2/4/21
I'm gonna try to build a custom LineageOS 18.1 (Android 11) soon as well.
Thanks.
RafBB said:
Hello,
So the good news is - apparently we can unlock Kirin 970 now. I did the hardware testpoint mode with the HCU Client and it worked just fine! I was replacing the battery anyway so I already had access to the motherboard. The question now is - what happened to LineageOS ROMs? Looks like they just deleted all of them.
Is there anybody out there with one of them on their HDD willing to share? Google cached website is showing two of them:
lineage-16.0-20210211-nightly-charlotte-signed.zip 2/11/21
lineage-16.0-20210204-nightly-charlotte-signed.zip 2/4/21
I'm gonna try to build a custom LineageOS 18.1 (Android 11) soon as well.
Thanks.
Click to expand...
Click to collapse
Here you are
lineage-16.0-20210211-nightly-charlotte-signed.zip
drive.google.com
RafBB said:
Hello,
So the good news is - apparently we can unlock Kirin 970 now. I did the hardware testpoint mode with the HCU Client and it worked just fine! I was replacing the battery anyway so I already had access to the motherboard. The question now is - what happened to LineageOS ROMs? Looks like they just deleted all of them.
Is there anybody out there with one of them on their HDD willing to share? Google cached website is showing two of them:
lineage-16.0-20210211-nightly-charlotte-signed.zip 2/11/21
lineage-16.0-20210204-nightly-charlotte-signed.zip 2/4/21
I'm gonna try to build a custom LineageOS 18.1 (Android 11) soon as well.
Thanks.
Click to expand...
Click to collapse
Are you use EMUI 9.1 to unlock Bootloader ?
RafBB said:
Hello,
So the good news is - apparently we can unlock Kirin 970 now. I did the hardware testpoint mode with the HCU Client and it worked just fine! I was replacing the battery anyway so I already had access to the motherboard. The question now is - what happened to LineageOS ROMs? Looks like they just deleted all of them.
Is there anybody out there with one of them on their HDD willing to share? Google cached website is showing two of them:
lineage-16.0-20210211-nightly-charlotte-signed.zip 2/11/21
lineage-16.0-20210204-nightly-charlotte-signed.zip 2/4/21
I'm gonna try to build a custom LineageOS 18.1 (Android 11) soon as well.
Thanks.
Click to expand...
Click to collapse
Here is my p20 pro , can I unlock the Bootloader ?
ArthurTsai said:
Here you are
lineage-16.0-20210211-nightly-charlotte-signed.zip
drive.google.com
Click to expand...
Click to collapse
Awesome! Thanks a lot. I've found an UNOFFICIAL rom yesterday and flashed it, but looks like I'll be doing it all over again today with this one.
ArthurTsai said:
Are you use EMUI 9.1 to unlock Bootloader ?
Click to expand...
Click to collapse
Ok so here was the process:
1) Backed up all my data from the device (CLT-L29)
2) Factory reset the device
3) I used Huawei Hisuite software to rollback as far (BACK) as I could. It actually let me downgrade to EMUI 8.
4) Installed HCU and DC Phoenix (timed 72 hour license for both was like 20 euro)
5) Installed NECESSARY drivers on my Windows 10 machine (HUAWEI USB COM 1.0) for the testpoint
6) I opened the phone (I wanted to replace the battery anyway). Unscrew a couple of screws and take a shield to get to the pad.
7) With the phone completely off, short the testpad to ground (I used tweezers) and plug in the USB cable while still shorting out that pad. (USB cable that is connected to your Windows machine that is). Your phone screen will stay completely OFF, but you should hear an USB "ding" sound in you windows machine. Go to the device manager and check for HUAWEI USB COM 1.0 (Your Port). If you don't see it it won't work.
8) Fire up HCU Client, check account, select "Fastboot/XLoader (Hisilicon only)" on phone connection mode.
9) Go to the "Fastboot/Xloader" tab and select CPU (for me Kirin970_T2_A8.1_V5) worked fine.
10) Click Read phone info button, you'll see a progress bar on the bottom, it should take like 2 minutes
11) If everything went fine you'll see a log on the right with your unlock code in it
12) You can unlock it from that software, select "Bootloader lock: unlock", and "Write bootloader code" I also selected "Erase Huawei ID" and click "Repair" button. It will be quick. And that's it!
Now, flashing a custom ROM was a pain. Apparently most of them REQUIRE EMUI 9.0.0.159 (159 is the KEY!). You must get the original firmware and flash it with DC Phoenix. After that the process went something like this...
1) Put the phone in fastboot/rescue mode (hold the volume down button wile inserting USB cable with the phone off)
2) Flash TWRP for charlotte with fastboot from your PC
3) Restart phone into RECOVERY (TWRP) mode
4) Sideload your rom.ZIP file (Lineage for example)
5) Sideload google apps
6) Sideload factory camera app (honestly its the best for that phone)
7) Restart the bootloader (you will be in the fastboot mode again)
8) Upload the ORIGINAL recovery image (it wont boot if you dont do it) you can revert to TWRP after the first boot
9) Go into Huawei recovery mode (power+volume up)
10) Wipe/factory reset
11) Restart and you are done! (now you can flash TWRP again if you want)
It took me an entire day of work to figure it out. All the info (steps) is available online including the location of the test pad and disassembly of the phone. Here's an awesome guide to flashing Lineage (https://depl0y.com/posts/P20-Pro-LineageOS-Guide/). One thing I've noticed if you try to use HiSuite AFTER you unlocked your bootloader it WILL lock it again. I had to do it twice while I was trying to get EMUI 9.0.0.159. The best way was to use DC Phoenix and ROM from androidhost.ru.
Anyway after all that I now have an unlocked P20 Pro with stock android. It's bloatware free and runs great. So far no major issues with the ROM.
RafBB said:
Ok so here was the process:
1) Backed up all my data from the device (CLT-L29)
2) Factory reset the device
3) I used Huawei Hisuite software to rollback as far (BACK) as I could. It actually let me downgrade to EMUI 8.
4) Installed HCU and DC Phoenix (timed 72 hour license for both was like 20 euro)
5) Installed NECESSARY drivers on my Windows 10 machine (HUAWEI USB COM 1.0) for the testpoint
6) I opened the phone (I wanted to replace the battery anyway). Unscrew a couple of screws and take a shield to get to the pad.
7) With the phone completely off, short the testpad to ground (I used tweezers) and plug in the USB cable while still shorting out that pad. (USB cable that is connected to your Windows machine that is). Your phone screen will stay completely OFF, but you should hear an USB "ding" sound in you windows machine. Go to the device manager and check for HUAWEI USB COM 1.0 (Your Port). If you don't see it it won't work.
8) Fire up HCU Client, check account, select "Fastboot/XLoader (Hisilicon only)" on phone connection mode.
9) Go to the "Fastboot/Xloader" tab and select CPU (for me Kirin970_T2_A8.1_V5) worked fine.
10) Click Read phone info button, you'll see a progress bar on the bottom, it should take like 2 minutes
11) If everything went fine you'll see a log on the right with your unlock code in it
12) You can unlock it from that software, select "Bootloader lock: unlock", and "Write bootloader code" I also selected "Erase Huawei ID" and click "Repair" button. It will be quick. And that's it!
Now, flashing a custom ROM was a pain. Apparently most of them REQUIRE EMUI 9.0.0.159 (159 is the KEY!). You must get the original firmware and flash it with DC Phoenix. After that the process went something like this...
1) Put the phone in fastboot/rescue mode (hold the volume down button wile inserting USB cable with the phone off)
2) Flash TWRP for charlotte with fastboot from your PC
3) Restart phone into RECOVERY (TWRP) mode
4) Sideload your rom.ZIP file (Lineage for example)
5) Sideload google apps
6) Sideload factory camera app (honestly its the best for that phone)
7) Restart the bootloader (you will be in the fastboot mode again)
8) Upload the ORIGINAL recovery image (it wont boot if you dont do it) you can revert to TWRP after the first boot
9) Go into Huawei recovery mode (power+volume up)
10) Wipe/factory reset
11) Restart and you are done! (now you can flash TWRP again if you want)
It took me an entire day of work to figure it out. All the info (steps) is available online including the location of the test pad and disassembly of the phone. Here's an awesome guide to flashing Lineage (https://depl0y.com/posts/P20-Pro-LineageOS-Guide/). One thing I've noticed if you try to use HiSuite AFTER you unlocked your bootloader it WILL lock it again. I had to do it twice while I was trying to get EMUI 9.0.0.159. The best way was to use DC Phoenix and ROM from androidhost.ru.
Anyway after all that I now have an unlocked P20 Pro with stock android. It's bloatware free and runs great. So far no major issues with the ROM.
Click to expand...
Click to collapse
Things are not that simple. The HiSuite on Mac have been updated.
I can't find the button that can roll back or check for update after this.
Maybe I should try HiSuite on Windows.
I suddenly remembered that I cannot use HiSuite Windows version to roll back to EMUI 8 , but I can roll back to EMUI 9. Maybe I can roll back to EMUI 8 from EMUI 9. Needing roll back twice ?
ArthurTsai said:
I suddenly remembered that I cannot use HiSuite Windows version to roll back to EMUI 8 , but I can roll back to EMUI 9. Maybe I can roll back to EMUI 8 from EMUI 9. Needing roll back twice ?
Click to expand...
Click to collapse
You *should be able to unlock it with EMUI 9. I rolled it back to 8, just to find out later on I need 9.0.0.159 anyway. So I used HiSuite to update it to 9 - but it wasn't the version I wanted and also doing this in HiSuite removed my bootloader code, so I ended up using HCU Client on EMUI 9 and it worked just fine. After that I used DC Phoenix to flash the 9.0.0.159 (bootloader stayed unlocked). It was a pain, but yeah you SHOULD be able to unlock it with EMUI9.
ArthurTsai said:
I suddenly remembered that I cannot use HiSuite Windows version to roll back to EMUI 8 , but I can roll back to EMUI 9. Maybe I can roll back to EMUI 8 from EMUI 9. Needing roll back twice ?
Click to expand...
Click to collapse
Here's a log from unlocking 9.0.0.168...
Just to let you know that official ROM (lineage-16.0-20210211-nightly-charlotte-signed.zip) is not working on my P20 Pro. It crashes on the first boot. I'm back with (lineage-16.0-20190217_125340-UNOFFICIAL-charlotte.zip) I believe it was made made by LuK1337. Works great. I use it with open gapps pico version.
guys, this is p20 non-pro forum.
why are you discussing this here?
Related
Let it now be hacked by the USA! France, those silly, um, baguette-eaters, via Bloggee, has several videos and some forums (in French) showing (but I don't think explaining) a hacked Archos 70B ereader/tablet. Can we get there??
I'd like to see a guide for hacking this 130 euro Android tablet!
About: I AM A N00B. I AM UNWORTHY! You are all wiser and cooler and better at all of this than me. I cannot write code, except some CSS and HTML, blah blah beginner stuff. I was the guy that jailbroke friends' iPhones when we studied in Italy. I like learning how to do things, but can't get extremely in depth, though I respect the process and the art behind it. Currently, my iPhone died so for a phone I have a quad-band Huawei J2SE POS I couldn't modify much, and a netbook with dual-boot Win7/Linux. Now in Germany, I bought a lovely Archos 70B ereader, and while it does the job of ereader, it's ugly and clunky and I want to hack it into running a cleaner, prettier Android ROM (with marketplace) since this seems to be a new device with a lot of potential.
Questions that haven't been answered by looking through these forums, and that I have encountered trying to customize my tablet:
Trying to get marketplace, I finally found an .apk to download, but trying to install, it said (paraphrase) "Only works with Froyo." SOO, Android's various versions (Eclair, Froyo, Gingerbread, Honeycomb, etc) while all the same OS in a way, prevent apps compatible with one version from being installed onto another version. It's like trying to install Win95 stuff on XP, or Win7 stuff on XP. Correct?
Issue: Finding Eclair-compatible .apk files. Where are they? Or, can Eclair apps be installed on other builds of Android, & vice versa?
Trying to upgrade the hardware to Froyo, well, I can't find anything. If a machine has the minimum hardware specs, why is installing any version an issue? Why can't I just search certain websites for an installer package and then use it, like a Windows or Linux .ISO, etc?
Issue: Upgrading from one Android OS/version to another (Eclair to Froyo, Froyo to Gingerbread, Eclair to Gingerbread)
Trying to upgrade firmware on device, I've found that Archos' website has no downloads for 70B ereader...HMMM. Issue, much? My firmware on the device is 1.0.1. There is no "Update Firmware" option or anything, and the firmware display is grayed out, so you can't touch it for further details or anything.
Issue: How do I update/backup/recover firmware for this device (or any, I guess)
While I have found guides to using Nandroid to backup a system in case of issues, they all seem to require that you have Marketplace so you can get Nandroid...and since this Archos version of Android doesn't have Marketplace...I've tried AppBrain Appmarket but the webpage isn't helpful: it says dl nandroid from marketplace or navigate there on my device's browser, but my device's browser won't download the APK when I visit the site. How does one get nandroid and a solid backup without marketplace? (.apk anywhere??)
Permanent rooting on this device; currently I use Z4Root and do temporary rooting, since 1) that's what guides said worked and 2) I don't know if permanently rooting my device will somehow destroy my data or be unrecoverable without further restore options.
Issue: Permanent root vs. temporary root (and why use one or the other)
Installing a custom ROM. In short, because I just am not clear, can someone clarify for me? Is this like basically wiping the HDD to all 0's, down to the first sector, and installing an entire new OS (called a "ROM") onto the HDD? I know a flash HDD is different than a circular spinning drive with Windows and an MBR, etc, but I'm curious if a custom ROM erases EVERYTHING, including a flash drive equivalent to all recovery/installer partitions. Or is there a tiny partition left and, if the factory reset button is pushed, that reinstalls/recovers everything? If that is not the case, then don't I need stock Archos ROM to reinstall/recover, if I wanted to go back to that?
Issue: Does a custom ROM completely wipe a HDD all to 0's, and if so, how does recovery work if using a device-specific build for Android (like Archos')
Maybe nobody cares about this tablet, and sure it's slow, but having a sub-$200 Android tablet would rock, and figuring out how to root and ROM and customize a device would be great.
Also, I want to say that most important is knowing if/how/why I can return to my stock Archos version of Android if dissatisfied; second most importantly is how to improve this (and any) device with a crappy tweaked Android OS into a pretty and fast (with marketplace) Android OS.
THANKS
Current for Archos 70B
Model Number A7EB
Firmware Version 1.0.1
Kernel Version 2.6.25 [email protected] #14
Build Number v.0.18.ECLAIR.eng.root.20110324.142810
Have successfully rooted (temporarily, until reboot) via Z4root.
Currently trying to use ArcTools...I had the site linked, and lots of other nifty links throughout, but xda handicaps us n00bs until 8 posts. So no links. Sorry.
Currently...
stuck at the same place as these people, pretty much.
http
forum.archosfans.com
viewtopic.php?f=82&t=51066
sorry for breaking it up. insert slashes to go to the link, or just visit the forum and search for Archos 70b.
currently looking into loading the (much nicer-looking) Voltaire firmware onto the 70b, if the parts are the same...hope i don't get a spanish installer program
BQReaders voltaire is exactly same hardware than archos 70b ereader,
BQReaders voltaire use a "standard" google android interface: android market, no application install restriction, google account sync etc.
Rom install procedure:
Download 3 zips from bqreaders.com website:
Usb device driver, MSWindows upgrade software, bqreader voltaire firmware.
1. Uncompress the 3 zips on your windows desktop
2. Turn off the 70b
3. Connect 70b to your PC using the usb link
4. press and lock right arrow button on 70b
5. press and lock power button
6. windows detects a neu device.
7. remove locks on keys and install the new device using uncompressed drivers.
9. Run the upgrade softwarelancer: RKAndroidBatchUpgrade.exe (if driver is correctly installed, youshould see the square "1" in device upgrade area in green color.
10. Check "image", and select the firmware (.img) décompressé.
11. click on Upgrade.
12. The square blink in "orange" color.
13. The device restarts.
14. unconnect usb link
15. the upgrade procedure continue on 70b screen.
16. the device restarts showing "bq" logo
17. screen calibration.
Warning: all internal flash data is lost!
stopdatrue said:
BQReaders voltaire is exactly same hardware than archos 70b ereader,
BQReaders voltaire use a "standard" google android interface: android market, no application install restriction, google account sync etc.
Rom install procedure:
Download 3 zips from bqreaders.com website:
Usb device driver, MSWindows upgrade software, bqreader voltaire firmware.
1. Uncompress the 3 zips on your windows desktop
2. Turn off the 70b
3. Connect 70b to your PC using the usb link
4. press and lock right arrow button on 70b
5. press and lock power button
6. windows detects a neu device.
7. remove locks on keys and install the new device using uncompressed drivers.
9. Run the upgrade softwarelancer: RKAndroidBatchUpgrade.exe (if driver is correctly installed, youshould see the square "1" in device upgrade area in green color.
10. Check "image", and select the firmware (.img) décompressé.
11. click on Upgrade.
12. The square blink in "orange" color.
13. The device restarts.
14. unconnect usb link
15. the upgrade procedure continue on 70b screen.
16. the device restarts showing "bq" logo
17. screen calibration.
Warning: all internal flash data is lost!
Click to expand...
Click to collapse
IMPORTANT QUESTION !!
Can i downgrade when i do this ^^ ?
i have found this:
xxx:xxx.archoslounge.net/forum/showthread.php?t=17642&p=275535&viewfull=1#post275535
^^
firmware_Archos70bereader.zip
xxxx:xxx.multiupload.com/U8MOUTWI5T
Does not work
It crashes at 99%. Luckily I had a recovery image.
I followed all the steps but can't get the image to install properly
We really need a rooted version of the BQ Voltaire software. Mine has now crashed twice since using it. If I could backup it wouldnt be nearly so bad.
The temporary root doesnt seem to work for me.
I have recently brought the Archos 70B ereader. I would like to know how to perform a factory restore. I have already tried to the reset button on the back, but that's just resulting in turning of the device. I also noticed the startup wizard on the setting menu, which after adjusting the startup setting is adding the factory apps back to the device. However, it does not seem to erase the whole internal memory like a real factory restore would do.
Does anyone knows how to perform a real hardreset on the reader?
Thanx.
I have upgraded my 70b succesfully with the BQ firmware.
It runs nicely tho it seems the battery is having a hard time.
So far i haven't managed to get it to last for more then a day.
Currently testing with juice defender to see if it helps.
I noticed some questions about reinstalling the default archos image (factory reset). The procedure to do this is the same as the installation of the BQ firmware. You just need to select the correct image.
So make sure you have both the archos and the bq image before attempting the upgrade. When you brick it, use the installation procedure to get it back to life.
However, when done properly, the BQ firmware should work.
Note: The drivers are not compatible with a 64bit OS. I flashed mine with an old XP-32 running laptop where WIN7-64 would fail.
I have a bq Voltaire running latest firmware (1.0.8) an i was able to temp root with Universal Androot.
will try to perm root and report back
...but is there any rom with software buttons (back, home, menu)?
because the bq does not have them...
cheers
EDIT: was unable to perm root with either Universal Androot or z4root...
I also have the software installed BQ. Works perfectly. I can not say that the batterylif is a problem. BQ software works much better tehn de the Archos Software.
The Archos 70 b eReaders and BQ Voltaire tablet run with the firmware Voltaire_20110699_v2.0.9.-2 _update.img very stable. For some days has been there one for this equipment android 2.2 version. There were some crahs on my device with that and moving the Apps on a SD card also doesn't work.
A rooted version with containedly in the Link2SD (you can move the Apps on SD card) the above-mentioned version in the link. E.g. an optimal mode of operation is possible with a 32 GB SD card class 10.
The Mini tool partition software can with standalone the SD card be formatted into 2 partitions. 1st partition FAT32 (e.g. 28 GB) 2nd partition ext3 (rest) both primary.
The approx. 2 GB suffice for many Apps.
For link see Archosfans forum. (i can't write link here)
Works like a charm with the Voltaire rom!
So THANX guys
how to remove key locks ?
stopdatrue said:
BQReaders voltaire is exactly same hardware than archos 70b ereader,
BQReaders voltaire use a "standard" google android interface: android market, no application install restriction, google account sync etc.
Rom install procedure:
Download 3 zips from bqreaders.com website:
Usb device driver, MSWindows upgrade software, bqreader voltaire firmware.
1. Uncompress the 3 zips on your windows desktop
2. Turn off the 70b
3. Connect 70b to your PC using the usb link
4. press and lock right arrow button on 70b
5. press and lock power button
6. windows detects a neu device.
7. remove locks on keys and install the new device using uncompressed drivers.
9. Run the upgrade softwarelancer: RKAndroidBatchUpgrade.exe (if driver is correctly installed, youshould see the square "1" in device upgrade area in green color.
10. Check "image", and select the firmware (.img) décompressé.
11. click on Upgrade.
12. The square blink in "orange" color.
13. The device restarts.
14. unconnect usb link
15. the upgrade procedure continue on 70b screen.
16. the device restarts showing "bq" logo
17. screen calibration.
Warning: all internal flash data is lost!
Click to expand...
Click to collapse
Hallo all and thank you for this great manual.
I allready prepared all: downloads, installing usb and uncompressing and so on, tryed many times, but my problem is your point 7): remove key-locks. , whichj I didn´read clearly before and thats why I want to install any new system on my/our Archos BQVoltaire: My daughter played with the login until it was locked and I do not have any Google-Password to unlock this. Nor dont know, how to hard reset or anything else. I am just a user, nothing else. Tried everything, but didn´t get it.
Do anybody hav an idea, how I can solve this, I would be really happy. Thx a lot in advance.
Giant THANKS, is easy as instruction say, and works a charm...now i have a tablet instead of a****!
stopdatrue said:
BQReaders voltaire is exactly same hardware than archos 70b ereader,
BQReaders voltaire use a "standard" google android interface: android market, no application install restriction, google account sync etc.
Rom install procedure:
Download 3 zips from bqreaders.com website:
Usb device driver, MSWindows upgrade software, bqreader voltaire firmware.
1. Uncompress the 3 zips on your windows desktop
2. Turn off the 70b
3. Connect 70b to your PC using the usb link
4. press and lock right arrow button on 70b
5. press and lock power button
6. windows detects a neu device.
7. remove locks on keys and install the new device using uncompressed drivers.
9. Run the upgrade softwarelancer: RKAndroidBatchUpgrade.exe (if driver is correctly installed, youshould see the square "1" in device upgrade area in green color.
10. Check "image", and select the firmware (.img) décompressé.
11. click on Upgrade.
12. The square blink in "orange" color.
13. The device restarts.
14. unconnect usb link
15. the upgrade procedure continue on 70b screen.
16. the device restarts showing "bq" logo
17. screen calibration.
Warning: all internal flash data is lost!
Click to expand...
Click to collapse
Point 7) of the instruction ????
Maybe for you woks like a charm. :good: Congratulations, fine for you.
But my problem has not been solved, since july last year!! I understand the entire instruction, already downloaded all indicated files, but as I already mentioned, my problem is point 7 of the instructions: "7. remove locks on keys and install the new device using uncompressed drivers"
.
The thread here is called something like "how to hakk keylocked installation...". Isn´t it?
But in Point 7) says: ".. remove locks on keys..." !!! What a fool is this, it is ridiculous. If I could remove this f... keylock manually, so why should I make a hard-reset.??? This is the REASON for what I´m going to do this !!!
My Archos ereader is not stolen nor part of any fraud. It just were handled foolish form my daughter, which is 10 y old.
Ok, if anybody have another idea, how to remove this keylock, you are welcome, thx
cvesch said:
I have upgraded my 70b succesfully with the BQ firmware.
It runs nicely tho it seems the battery is having a hard time.
So far i haven't managed to get it to last for more then a day.
Currently testing with juice defender to see if it helps.
I noticed some questions about reinstalling the default archos image (factory reset). The procedure to do this is the same as the installation of the BQ firmware. You just need to select the correct image.
So make sure you have both the archos and the bq image before attempting the upgrade. When you brick it, use the installation procedure to get it back to life.
However, when done properly, the BQ firmware should work.
Note: The drivers are not compatible with a 64bit OS. I flashed mine with an old XP-32 running laptop where WIN7-64 would fail.
Click to expand...
Click to collapse
For me it was the same. The drivers are working only on 32-bit win WinToUSB - cool tool, if you don't want to reinstall your win.
---------- Post added at 09:21 AM ---------- Previous post was at 09:07 AM ----------
hi,
After spending many time trying to root my storex tab 901 I bought in france (Already installed on 4.1.1 with google play), Iwas finnaly able to root it using adb and command line.
to do so:
- Download attached file
- Download from google SDK usb_adb_driver
- Go to your device parameters-> USB -> enable debbuging mode
- create a c:\root folder on your windows XP computer then Extract the zip file attached into it.
- Plugin your device to the computer, when prompted for driver, use google sdk USB_ADB_Driver
- When done, open a windows terminal command line
- type: c:
- type: cd \
- type: cd root
- type: cd rootkit
- type: go.cmd
If everything goes well, your tablet should reboot. you can try installing the free app from google store called "Root checker" to confirm your device is properly rooted.
Also, if you lost the original rom and live suite, here is the link to download the latest build from storex web site:
(I will post the link later when I find it)
JB 4.2.2
CAUTION: USE THIS ROM AS YOUR OWN RISK.......Be sure you have the official rom in case it is not working for you. It appears that even though you have the same tablet Reference, depending on when you buy it, hardware might be a bit different and most likely you will take the risk of having a unusable Touch screen or wifi...
I found out you can fully use your Ezee Tab 901 4.2.2
you can install rom from Manta MID 13.
You will be able to install the rom using Livesuite.
Gain:
- Android 4.2.2
- Root Access out of the box
- Play store installed.
Everything will be working
For the link type in google:
MID13 Android 4.2.2 Jelly Bean - Manta Multimedia Info
select google link called: manta.info.pl
select the link catshare or 4shared.
Start live suite 1.7, select the download img file, do a format when prompted. You done.
When the tablet restart, go to the parameter icon, and change language to French or english
Procedure on the Ezee tab 901 with livesuit:
- completly turn off the tablet, unplug cable
- start livesuite and select the downloaded image file
- keep the VOL- button pressed and plug the usb cable
- without releasing the VOL- button press the Power button 6 times.
- You should hear windows sound saying a USB device has been plugged
- if windows request it, install the driver from Livesuitefolder\usbdriver
- Livesuite should automatically start the flashing process.
- when prompted, "Format device" press YEs.
- When it s 100% you tablet should reboot.
Done.
Note: I did not invent anything, thanks to the good work of MANTA team members. I just found out this rom works on my tablet out of the box.
Hi,
Thanks for sharing these tips. I'm gonna try to update to 4.2.2, hoping this is going to fix some problems with this tablet.
I've been looking a lot for information about how to update ezee tab 901, so you did definitely a great work !
edit : iflash went well, but touch screen is not responding anymore. Any idea of how to solve it ?
Thanks.
samus64 said:
Hi,
Thanks for sharing these tips. I'm gonna try to update to 4.2.2, hoping this is going to fix some problems with this tablet.
I've been looking a lot for information about how to update ezee tab 901, so you did definitely a great work !
edit : iflash went well, but touch screen is not responding anymore. Any idea of how to solve it ?
Thanks.
Click to expand...
Click to collapse
Hi,
did you try going into recovery mode and factory reset? (shutdown tabel completely and keep press on volume+key then press power button)
in the menu, using vol+/- scroll down to wipe factory reset and validate by pressing the power key.
Let me know how it goes.
btw, are you sure your tablet is a Ezee tab 901 and not 971?
Cheers
Hi,
Yes I've got 901 and not 971 (written on the back of the device). I tried factory reset , but still the same problem. However, I flashed again with the original rom, and then touch screen went functional again but the wifi switch is kinda "broken" : it's impossible to turn on wifi from the Settings menu.
I returned the tablet where I bought it, seems there's a sort of material problem with it :/
samus64 said:
Hi,
Yes I've got 901 and not 971 (written on the back of the device). I tried factory reset , but still the same problem. However, I flashed again with the original rom, and then touch screen went functional again but the wifi switch is kinda "broken" : it's impossible to turn on wifi from the Settings menu.
I returned the tablet where I bought it, seems there's a sort of material problem with it :/
Click to expand...
Click to collapse
Im sorry to hear that, i dont think something is broken, i had the same issue with a memup tablet, even though it was a same reference, some model had different hardware, sonlike you after testing multiple rom i had only touch s creen and no wifi ( wifi switch went back to off when i tried to turn it on) or on other rom, i had working wifi but no touch screen.
I hope they will replace your device...
Cheers
pierrottls31 said:
Im sorry to hear that, i dont think something is broken, i had the same issue with a memup tablet, even though it was a same reference, some model had different hardware, sonlike you after testing multiple rom i had only touch s creen and no wifi ( wifi switch went back to off when i tried to turn it on) or on other rom, i had working wifi but no touch screen.
I hope they will replace your device...
Cheers
Click to expand...
Click to collapse
Yep the wifi switch is exactly what i've got on this storex. Thanks for your help anyway. Ho and by the way, I properly rooted it with you first tuto
Cheers.
Fast custom ROM 4.2.2 by TOxico for Ezee tab 901
Guys,
I manage to find a very fast and usable rom for our tablet: (THanks to Toxico.) this rom will change your life.
All information and download are in the thread here:
http://forum.xda-developers.com/show...php?p=42274265
It should basically work on any A13 device with livesuit (tested on my Ezee tab 901 and on my 704CET mem up)
This rom comes with no TS driver, but there is all explanation and download to install the needed driver.
note: you might loose the camera though. I encourage you to read the full thread before going further and flash your tablet.
If you want to know the driver used on your tablet, run a adb shell and type lsmod (You will have a list of loaded/used driver.)
Dont be scared, everything is written in the toxico's thread
My only advice, if you dont know how to use adb, do not try it, this is not that easy.
I hope this will help.
Best regards.
As usual do it at your own risk and even more: make sure you have the original rom... just in case
Tutorial for 971.
Hi there,
Does anyone know a tutorial like this one but for the 971??
My brother-in-law wasn't using is so I'm thinking in tweaking it to see how it gets.
MaedaKeiji said:
Hi there,
Does anyone know a tutorial like this one but for the 971??
My brother-in-law wasn't using is so I'm thinking in tweaking it to see how it gets.
Click to expand...
Click to collapse
Hi, sorry i cant help you, it looks like the 971 is using a10 cpu, sôit can be different.
If you know what you are doing, u can try to backup your original firmware and test the solution i have provided from toxico in py post above. But there is no warranty it s going to work.
Any case, donnot forget google is your friend
Good luck
Unfornetly it seems google doens't like this tablet...
I'll see what I can do with some backups and all.
Thanks anyway!
Hello everybody !
Ok, I am use to not ask any help, and to find out by myself. But I have to admit I don't have any idea remaining to solve this problem.
Let me explain you the situation :
I explain everything with details to not waste your time when you will help me !
When I first bought my Zenfone, everything worked properly. Then, I decided to flash a Custom ROM (to remove the bloatware, and to get the others optimizations). So what I did :
- I unlocked the bootloader,
- I flashed TWRP,
- I installed my custom ROM (SuperZen R15, super clean install) => at this moment, everything is working perfectly,
- I installed a custom Kernel (ProjectT, v56) by fastboot => here we are, the problem just appeared.
At this moment, the WiFi issues appear. When I boot the phone, I can turn on the WiFi (in most cases), then, WiFi just turn off. It is impossible to activate it again. In the best case, I can switch on/off the WiFi, but as soon as I download something, the WiFi just turn off immediately. Often, I just don't detect any network. In the worse case, it is impossible to activate again the WiFi, the ON/OFF button is grey.
So here is what I tried to get it back :
1) put the standard kernel with my TWRP backup => no success
2) flash another ROM (CM12, Paranoid Android, Barebone,...etc) => no success
3) flash my whole TWRP backup (system + kernel) => no success
4) flash the official Asus ROM (recovery.img, system.img, boot.img, droidboot.img) => no success
At the moment, I started thinking that maybe the WiFi just "forgot" my WPA key. So I modified the build.prop :
5) modification of the build.prop by adding the line ro.securestorage.support=false (instead of "true") => no success
6) flash the last Asus update 2.20.40... => no success.
...
I haven't any idea remaining !So I need your help ! This problem seems very standard, but I just couldn't find any solution yet !
P.S : I almost forgot. I talked about the wiFi signal, but it is exactly the same for the bluetooth signal : working on first boot, then when I use it, it just stop working and disconnect itself, and then, impossible to activate it again (grey button)
=> My last idea was to flash the radio directly by TWRP, but I didn't find any radio files for the zenfone 2...
Many thanks for your help, and thank you for reading everything !!
Max
Up !
BackDraft647 said:
Up !
Click to expand...
Click to collapse
Try setting your phone as a wifi hotspot. If other devices are able to detect your device, it is a software issue. Or else, you might have to book an appointment with the Asus service center
[email protected] said:
Try setting your phone as a wifi hotspot. If other devices are able to detect your device, it is a software issue. Or else, you might have to book an appointment with the Asus service center
Click to expand...
Click to collapse
You're such a genius ! I will try this evening ! Thanks a lot !
Didn't do anything. It's not working. I was thinking my wifi was just broken, but something creepy happened this morning. The Wi-Fi worked again (I downloaded one thing to be sure !) and then... My phone froze, and reboot... Is the devil inside my phone ??
SOLVED ! If someone has the same problem, just flash the stock ROM via ADB Sideload !
Step by step :
1) You go here, and download your version of the stock ROM : http://www.asus.com/fr/Phones/ZenFone_2_ZE551ML/HelpDesk_Download/
2) (If fastboot/adb drivers are installed) Go into your recovery (Advanced in TWRP)
3) Connect the phone to the PC, type WINDOWS + R , enter 'cmd'
4) Go into your firmware directory you just downloaded, and type : adb sideload 'thenameofthefirmwarefile'.zip
5) Wait (a loooong time), and here we go, reboot, and your phone work again.
BackDraft647 said:
SOLVED ! If someone has the same problem, just flash the stock ROM via ADB Sideload !
Step by step :
1) You go here, and download your version of the stock ROM :
2) (If fastboot/adb drivers are installed) Go into your recovery (Advanced in TWRP)
3) Connect the phone to the PC, type WINDOWS + R , enter 'cmd'
4) Go into your firmware directory you just downloaded, and type : adb sideload 'thenameofthefirmwarefile'.zip
5) Wait (a loooong time), and here we go, reboot, and your phone work again.
Click to expand...
Click to collapse
can you tell me what firmware you used exactly? because i tried to flash the first one, from the asus page.
But it says that i have a newest build and it doesn`t lets me past trough the installing part.
I am also having troubles with my wifi and i would like to fix it
Hello ! I don't remember exactly, I went on a website and selected the right version for my country ! But my problem wasn't solve at all actually... I brought my phone to the store, and they told me my motherboard was just burnt. They changed everything, and now it works like a charm ! Be careful with the custom kernel, I'm pretty sure that's how my phone broke (I'm very careful with batteries,...etc)
Well thanks anyway. I will try to take the phone to te oficial ASUS services from my country but i don´t think they give a new one. I live in Uruguay and this cellphone is not at sale over here
Does sideloading the firmware wipe your apps? Or is every thing still there when its done?
Sent from my ASUS_Z00AD using Tapatalk
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been modified before it was cool.
Hi everyone, similar to the previous threads for
OP3, OP3T, OP5, OP5T, OP6, OP6T, OP7, OP7PRO, regular OP7T, T-Mobile OP7T, regular OP7TPRO and T-Mobile OP7TPro 5G here are the EDL packages (also known as MSM tools or unbrick tools) that can revive a bricked OnePlus 8 Pro.
You should also be able to rollback your phone to a previous release of OOS with them if for some reason you want to go back to an older firmware
You can download the following versions:
IN11BA tools (european firmware):
ANDROID 10:
OOS 10.5.4
OOS 10.5.6
OOS 10.5.8
OOS 10.5.10
OOS 10.5.11
ANDROID 11:
OOS 11.0
OOS 11.0.1.1
OOS 11.0.2.2
OOS 11.0.3.3
OOS 11.0.4.4
Mirror for first and last MSMs per Android version: https://onepluscommunityserver.com/
IN11AA tools (international firmware):
ANDROID 10:
OOS 10.5.4
OOS 10.5.5
OOS 10.5.10
OOS 10.5.11
OOS 10.5.12
ANDROID 11:
OOS 11.0
OOS 11.0.1.1
OOS 11.0.2.2
OOS 11.0.4.4
Mirror for first and last MSMs per Android version: https://onepluscommunityserver.com/
IN11DA tools (indian firmware):
ANDROID 10:
OOS 10.5.4
OOS 10.5.5
OOS 10.5.8
OOS 10.5.9
OOS 10.5.10
OOS 10.5.11
OOS 10.5.12
OOS 10.5.13
ANDROID 11:
OOS 11.0
OOS 11.0.1.1
OOS 11.0.2.2
OOS 11.0.3.3
OOS 11.0.4.4
Mirror for first and last MSMs per Android version: https://onepluscommunityserver.com/
Warning:
It is advised to take backup of /persist partition before crossflashing (eg going from International to Indian build) as fingerprint reader may give an error related to enrollment issue. You can do so by using dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img (you must have root access, which is not something I'm going to explain here) and moving it to your computer/cloud.
Instructions:
Launch MsmDownloadTool V4.0.exe.
On Android 11 MSMs and up Windows 7 users may need to launch MsmDownloadTool V4.0_Win7.exe instead, but it hasn't been tested
On the login prompt select "Other" in the dropdown menu and click on Next.
Wait a few seconds until main window shows up.
Click on Target button and select O2 while using international tool or India while using indian tool or EU when using european tool.
Power your device off.
Maintain volume up and volume down keys to get into Qualcomm EDL mode.
Plug your device to your computer using stock OnePlus cable. (You may let volume keys go once done.)
Click on Enum to be sure your device is detected and press Start.
Wait ~300 seconds.
Enjoy your brand new device.
FAQ:
Does this work on Mac or on Linux?
Unfortunately no, tool is Windows only. You should need at least Windows 7.
Why is my antivirus freaking out when unzipping the archive or running the tool?
In an effort to protect reverse engineering from being done (and by extension prevent conversion process like it was done on 6T and 7Pro), OnePlus now use VM Protect V3 in their MSM tools. As this tries to detect debug environment, this is seen as malicious behaviour by some antivirus.
My device isn't detected when I click on "Enum" button
Go to device manager and make sure your phone shows up as QDLOADER 9008.
If it shows up as QHUSB_BULK, it means Qualcomm driver wasn't installed automatically by Windows Update. Download the latest one from Microsoft website at http://download.windowsupdate.com/c..._fba473728483260906ba044af3c063e309e6259d.cab (source https://www.catalog.update.microsoft.com/Search.aspx?q=qualcomm hs usb 9008 ) and install it manually by right clicking on QHUSB_BULK and selecting "Update driver software" and "Browse my computer for driver software" to where you downloaded CAB file.
MSM tool is stuck on "Param pre-processing"
Ensure you're using the Qualcomm drivers linked above.
MSM tool is stuck on "Sahara communication failed"
Unplug your phone, get in fastboot mode, turn off phone, wait 15 secondes and get back in Qualcomm EDL mode. You can also try using a USB 2.0 port instead of a 3.0 one.
What is SMT Download mode?
Just don't try to unlock that mode, it will wipe your IMEI and your Widevine certificate if you use it.
How can I fix "SMT config not found" error?
Please refer to https://forum.xda-developers.com/showpost.php?p=83448961&postcount=61, all credits to @Shadow12347 for finding it out.
Credits:
@LL Starks for getting 10.5.4 IN11AA and 10.5.4 IN11DA links from OnePlus
@pysklona for testing 10.5.4 international and indian versions
@Titokhan for being a friend and providing inspiration in writing
@headsh0t95 for being a friend and suggesting me to request an access to upload files on AndroidFileHost now one year ago for my previous threads
@AndroidFileHost for the hosting
@Zer0De8th for OOS 11.0/11.0.1.1/11.0.2.2/11.0.3.3/11.0.4.4 MSMs.
OnePlus for the device and OS
Related: [OnePlus 8 Pro][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
That was quick! Great thank you.
i see oneplus 8 is IN21 ? 8Pro : IN11
empty.cad said:
i see oneplus 8 is IN21 ? 8Pro : IN11
Click to expand...
Click to collapse
Fixed typo in thread thanks, ironically enough I didn't have it in the title, guess that's what I get for making threads at the hour where people normally sleep in my timezone...
I've installed the global version of Oxygen OS on OP8 Pro but I definitely bricked it because it's stuck on the boot screen. Tried using your software to unbrick but the phone is not showing up at all, even after using the power button + volume up. Also unable to switch the phone off with the power button. Any advice?
jaques1979 said:
I've installed the global version of Oxygen OS on OP8 Pro but I definitely bricked it because it's stuck on the boot screen. Tried using your software to unbrick but the phone is not showing up at all, even after using the power button + volume up. Also unable to switch the phone off with the power button. Any advice?
Click to expand...
Click to collapse
As said in the OP, the key combination to get in EDL mode is volume up and down, not power and volume up.
How come your device doesn't turn off? It normally should after maintaining power button for 30 seconds.
太好了谢谢。
Thanks! Nice work, tool for op 8 vanilla coming soon?
Some_Random_Username said:
Fixed typo in thread thanks, ironically enough I didn't have it in the title, guess that's what I get for making threads at the hour where people normally sleep in my timezone...
Click to expand...
Click to collapse
Tested Done , thank bro
Wow, that was quick!
Thanks for the posting the msm tool and for your due diligence.:good:
Added EU 10.5.4 IN11BA to go back to EU build directly.
Hi,
I bought a Chinese Version, tried to install international rom, didn't know oneplus started locking their phones, and I believe I bricked it.
Any version to unbrick the Chinese version?
Thank you
kniaz759 said:
Hi,
I bought a Chinese Version, tried to install international rom, didn't know oneplus started locking their phones, and I believe I bricked it.
Any version to unbrick the Chinese version?
Thank you
Click to expand...
Click to collapse
You should be able to use any of the tools present in the OP but I would advise that you backup your /persist partition before (in main window of tool, press F8, tick "persist", input "oneplus" as password, press "ok" and click on the readback button).
Partition will be at the root of your system drive.
Some_Random_Username said:
You should be able to use any of the tools present in the OP but I would advise that you backup your /persist partition before (in main window of tool, press F8, tick "persist", input "oneplus" as password, press "ok" and click on the readback button).
Partition will be at the root of your system drive.
Click to expand...
Click to collapse
When I click to launch MsmDownloadTool V4.0.exe, nothing happens, just a small window comes up stating "program has been started but nothing happens...
EDIT: I got it working, driver needed restart.
I cannot enter EDL mode. I can reboot between system, recovery and bootloader but cannot enter EDL mode. I help vol+ and - for a while several times, nothing.
Another EDIT: I got into EDL via adb, it's doing it's thing now.
Some_Random_Username said:
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been modified before it was cool.
Hi everyone, similar to the previous threads for
OP3, IN11BA tools (european firmware):[/B]
ANDROID 10:
[URL="https://androidfilehost.com/?fid=4349826312261777331"]OOS 10.5.4
IN11AA tools (international firmware):
ANDROID 10:
OOS 10.5.4
IN11DA tools (indian firmware):
ANDROID 10:
OOS 10.5.4
Click to expand...
Click to collapse
I have not been able to determine the different 8 Pro devices, and since you seem to be on top of everything, I would like to ask a question.
OnePlus is calling the 8 Pro they are selling here a "US" version, and i don't see anything like that here or elsewhere. The overseas versions are "Global" which I would guess is the same as your "international" above. Since I am looking at a possible Global version, I am not sure if it will have the same frequencies as the OnePlus one.
If you can help - thanks. After I get an 8, I will be using your tool and firmware to take My 7 McLaren 5G back to stock.
Can I unlock a T-Mobile device to install an International version??
gpompeus said:
Can I unlock a T-Mobile device to install an International version??
Click to expand...
Click to collapse
From previous posts elsewhere (if you look), no international working on that. If it could be, I would not be looking at a non-carrier replacement.
t-mizzle said:
When I click to launch MsmDownloadTool V4.0.exe, nothing happens, just a small window comes up stating "program has been started but nothing happens...
EDIT: I got it working, driver needed restart.
I cannot enter EDL mode. I can reboot between system, recovery and bootloader but cannot enter EDL mode. I help vol+ and - for a while several times, nothing.
Another EDIT: I got into EDL via adb, it's doing it's thing now.
Click to expand...
Click to collapse
Can you explain how?
I am also stuck between fastboot and recovery, can't seem to enter EDL
any guide how to do it?
Pressing Vol up + Vol down + power gets me to fastboot mode not EDL
Thanks.
kniaz759 said:
Can you explain how?
I am also stuck between fastboot and recovery, can't seem to enter EDL
any guide how to do it?
Pressing Vol up + Vol down + power gets me to fastboot mode not EDL
Thanks.
Click to expand...
Click to collapse
Are you trying to use the unbrick tool? Also I think EDL is just vol+ and vol-, no power button for that. It did not work for me with buttons, I got into EDL via adb, adb fastboot EDL, I believe.
I would like to thank everyone for trying to help me out. It was a mentally exhausting day, I must have wiped my phone at least 15 times. I'm giving it a break for now, will get back into it over the weekend.
Earlier this year i bricked a RN8P brought in by a customer to convert to global rom. After applying and waiting to unlock bootloader for 168 hours, it was successful then installing the global rom the device disconnected went into a total black screen no recovery, no fastboot just a white led when connected. after so many researches this forum and google there was nothing to write home about. i was frustrated and sad the only solution was to get someone with and authorization account which was $30 and couldn't afford. Customer was on my neck and was already talking of paying for the device then lo and behold today i was reading through some post on unbrick and i bumped into a solution i thought wasnt worth it as i have tried it buh never paid attention too. its a post by @white_3n on https://forum.xda-developers.com/redmi-note-8-pro/how-to/guide-unbrick-stuck-da-mode-authorised-t4000433/page5. here is it in details:
1- open phone (this aint necessary)
2- disconnect the battery (this aint necessary)
3- wait 10 seconds (this aint necessary)
4- connect the battery (this aint necessary)
5- Press and hold power and volume-
6- Plug to PC
7- Wait for the second vibration (longer).
8- Download MiFlash2018-5-28-0 https://mva2.androidfilehost.com/dl/l-WKOxk-I6mBdYiEVPDMUQ/1598950844/8889791610682902064/MiFlash20181115.zip?
9- Download https://mifirm.net/download/3520
10- Extracted the firmware as it comes in a .TGZ format
11- then open MiFlash2018-5-28-0
12- Click on refresh to be sure its on fastboot mode
13- then select and locate file you have extracted in 10
14- then select clean at the bottom right side of the MiFlash2018-5-28-0
15- Flash
Viola RN8P is back to life
The phone must have the bootloader unlocked?
Goatzilla47 said:
The phone must have the bootloader unlocked?
Click to expand...
Click to collapse
yes bootloader already unlocked before brick
Hello Mdutsu,
Are you saying that removing the battery and putting it back gave you access back to fastboot (power + volume-) ?
I'm in your situation, without access to fastboot and only EDL falshing seems to be an option, but I have to pay someone with an authorized account...
I'd like to confirm that as you void warranty by removing the back cover.
hi this just happen to me i try you're method but screen stay black and when i connect to computer i just hear the connect/disconnect sound and mi tools don't find the phone what can i do ?
I had the same exact issue a few days ago. follow the instructions on this video and it should get you back up and running. Worked like a charm for me. ask me if have any questions.
There is a youtube video that will show you how to fix it but i cant paste the URL because it adds the entire video. search this in youtube
How To Unbrick Redmi Note 8 Pro || Flash Stock Rom using SP Flash Tool 100% Working without Mi Auth
MidNight0780 said:
I had the same exact issue a few days ago. follow the instructions on this video and it should get you back up and running. Worked like a charm for me. ask me if have any questions.
There is a youtube video that will show you how to fix it but i cant paste the URL because it adds the entire video. search this in youtube
How To Unbrick Redmi Note 8 Pro || Flash Stock Rom using SP Flash Tool 100% Working without Mi Auth
Click to expand...
Click to collapse
This video saved me too!
Bro I created a new account here just to thank you, my RN8PRO gave up and you saved me. THANK YOU SO MUCH
Mdutsu said:
Earlier this year i bricked a RN8P brought in by a customer to convert to global rom. After applying and waiting to unlock bootloader for 168 hours, it was successful then installing the global rom the device disconnected went into a total black screen no recovery, no fastboot just a white led when connected. after so many researches this forum and google there was nothing to write home about. i was frustrated and sad the only solution was to get someone with and authorization account which was $30 and couldn't afford. Customer was on my neck and was already talking of paying for the device then lo and behold today i was reading through some post on unbrick and i bumped into a solution i thought wasnt worth it as i have tried it buh never paid attention too. its a post by @white_3n on https://forum.xda-developers.com/re...brick-stuck-da-mode-authorised-t4000433/page5. here is it in details:
1- open phone (this aint necessary)
2- disconnect the battery (this aint necessary)
3- wait 10 seconds (this aint necessary)
4- connect the battery (this aint necessary)
5- Press and hold power and volume-
6- Plug to PC
7- Wait for the second vibration (longer).
8- Download MiFlash2018-5-28-0 https://mva2.androidfilehost.com/dl...0844/8889791610682902064/MiFlash20181115.zip?
9- Download https://mifirm.net/download/3520
10- Extracted the firmware as it comes in a .TGZ format
11- then open MiFlash2018-5-28-0
12- Click on refresh to be sure its on fastboot mode
13- then select and locate file you have extracted in 10
14- then select clean at the bottom right side of the MiFlash2018-5-28-0
15- Flash
Viola RN8P is back to life
Click to expand...
Click to collapse