Related
Hi,
I have couple of questions about micromax canvas A1.
1) What is the most effective and efficient way to root this phone.
2) Is there fully functioning(without any bug) CM11 developed for this phone. If yes, could anyone please share the link.
3) I have heard that these stuffs voids the warranty of the phone. How can I get back to warranty.
I am new to these thing and got confused after looking so may links. Can anyone please share the links which will help me for my 3 questions.
icooldude007 said:
Hi,
I have couple of questions about micromax canvas A1.
1) What is the most effective and efficient way to root this phone.
2) Is there fully functioning(without any bug) CM11 developed for this phone. If yes, could anyone please share the link.
3) I have heard that these stuffs voids the warranty of the phone. How can I get back to warranty.
I am new to these thing and got confused after looking so may links. Can anyone please share the links which will help me for my 3 questions.
Click to expand...
Click to collapse
Here are the answers:
1. Best way: http://forum.xda-developers.com/crossdevice-dev/android-one-general/tut-how-to-root-android-one-devices-t2928240
2. Yes, CM11 link: http://forum.xda-developers.com/crossdevice-dev/android-one-crossdevice-development-original-android-development/sproutdevelopment-cyanogenmod-11-alpha-t2897516
3. Rooting with step 1 doesn't void warranty. Step 2 (flashing) voids warranty.
To get back warranty when needed to go to service centre, unlock bootloader and completely format everything, download stock ROM and follow procedure from here: [Official][Stock][4.4.4] Mircromax Canvas A1
In SP Tools, remember to choose the option "Firmware Upgrade" instead of "Download All" to get back warranty.
Hope I helped you
Question about root, Unroot and custom rom installation
GokulNC said:
Here are the answers:
1. Best way: http://forum.xda-developers.com/crossdevice-dev/android-one-general/tut-how-to-root-android-one-devices-t2928240
2. Yes, CM11 link: http://forum.xda-developers.com/crossdevice-dev/android-one-crossdevice-development-original-android-development/sproutdevelopment-cyanogenmod-11-alpha-t2897516
3. Rooting with step 1 doesn't void warranty. Step 2 (flashing) voids warranty.
To get back warranty when needed to go to service centre, unlock bootloader and completely format everything, download stock ROM and follow procedure from here: [Official][Stock][4.4.4] Mircromax Canvas A1
In SP Tools, remember to choose the option "Firmware Upgrade" instead of "Download All" to get back warranty.
Hope I helped you
Click to expand...
Click to collapse
Thank you for your reply.
But these links are taking me to lots of other links and I am confused now. Isn't there a simpler way to achieve these.
Sorry, I am new to these things although once I have installed CM11 to my Xperia GO but it was much simpler.
icooldude007 said:
Thank you for your reply.
But these links are taking me to lots of other links and I am confused now. Isn't there a simpler way to achieve these.
Sorry, I am new to these things although once I have installed CM11 to my Xperia GO but it was much simpler.
Click to expand...
Click to collapse
Atleast try the rooting as in step 1. Those links are just download links.
OK. I'll tell you in short. Download and install these softwares: Minimal ADB and fastboot & AQ 4501Driver
Download this: twrp.img and place it in folder: C:\Program Files\Minimal ADB and Fastboot\
Download this: SuperSu, remove memory card from phone, connect it to PC via card reader and cut & paste this (.zip) file just inside Memory Card and put it back into phone.
Enable USB debugging in phone (Google if u dont know)
Connect phone to PC via USB cable and click on the "Minimal ADB and Fastboot" shortcut in desktop.
Type the following one by one:
Code:
adb devices
adb reboot bootloader
fastboot boot twrp.img
In your phone, wait for few seconds. Click on "Install ZIP". Browse to external_sd and select the file UPDATE-SuperSU-v2.40.zip (which you pasted)
If it asks for confirmation, just do it. That's all! Now reboot phone from there! Your phone is rooted.
Thanks...
GokulNC said:
Atleast try the rooting as in step 1. Those links are just download links.
OK. I'll tell you in short. Download and install these softwares: Minimal ADB and fastboot & AQ 4501Driver
Download this: recovery.img and place it in folder: C:\Program Files\Minimal ADB and Fastboot\
Download this: SuperSu, remove memory card from phone, connect it to PC via card reader and cut & paste this (.zip) file just inside Memory Card and put it back into phone.
Enable USB debugging in phone (Google if u dont know)
Connect phone to PC via USB cable and click on the "Minimal ADB and Fastboot" shortcut in desktop.
Type the following one by one:
Code:
adb devices
adb reboot bootloader
fastboot boot recovery.img
In your phone, wait for few seconds. Click on "Install ZIP". Browse to external_sd and select the file UPDATE-SuperSU-v2.40.zip (which you pasted)
If it asks for confirmation, just do it. That's all! Now reboot phone from there! Your phone is rooted. And I'm tired.
Click to expand...
Click to collapse
Thanks for your patience and reply...
GokulNC said:
Here are the answers:
1. Best way: http://forum.xda-developers.com/cro.../tut-how-to-root-android-one-devices-t2928240
2. Yes, CM11 link: http://forum.xda-developers.com/cro...routdevelopment-cyanogenmod-11-alpha-t2897516
3. Rooting with step 1 doesn't void warranty. Step 2 (flashing) voids warranty.
To get back warranty when needed to go to service centre, unlock bootloader and completely format everything, download stock ROM and follow procedure from here: [Official][Stock][4.4.4] Mircromax Canvas A1
In SP Tools, remember to choose the option "Firmware Upgrade" instead of "Download All" to get back warranty.
Hope I helped you
Click to expand...
Click to collapse
Can I install a cwm backup file without unlocking the boot loader ? As an Indonesian android one, android 5.1 cwm backup file is available to download, I'm thinking of installing it myself.
send from my canvas A1
issei007 said:
Can I install a cwm backup file without unlocking the boot loader ? As an Indonesian android one, android 5.1 cwm backup file is available to download, I'm thinking of installing it myself.
Click to expand...
Click to collapse
Yes you can. First boot up the CWM recovery from fastboot mode using the command
Code:
fastboot boot recovery_name.img
(I'd recommend Philz Recovery)
First, take a backup of your present ROM from Backup and Restore menu-> Backup to external_SD (so that if things go wrong, you can come back to present ROM)
From now on, you can adopt this procedure: http://youtube.com/watch?v=H4JJu0igXmU
(What the video says is
1. Wipe the system and boot partition
2. Place the extracted Lollipop Nandroid in clockworkmod/backup of memory card from computer using card reader and put it back in phone.
3. Restore this Lollipop Nandroid from recovery.)
Anyway, within a few days, we'll be getting the 5.1 update in India. Why so hurry to see Lollipop??
GokulNC said:
Yes you can. First boot up the CWM recovery from fastboot mode using the command
Code:
fastboot boot recovery_name.img
(I'd recommend Philz Recovery)
First, take a backup of your present ROM from Backup and Restore menu-> Backup to external_SD (so that if things go wrong, you can come back to present ROM)
From now on, you can adopt this procedure: http://youtube.com/watch?v=H4JJu0igXmU
(What the video says is
1. Wipe the system and boot partition
2. Place the extracted Lollipop Nandroid in clockworkmod/backup of memory card from computer using card reader and put it back in phone.
3. Restore this Lollipop from recovery.)
Anyway, within a few days, we'll be getting the 5.1 update in India. Why so hurry to see Lollipop??
Click to expand...
Click to collapse
Lol, no hurry just disgusted by the support of Google and of course can't wait, I bought this phone on a sole purpose of getting fast updates, and did a mistake by choosing this over moto G2. BTW thanks for the reply. I'm trying root for the first time, by your instructions.
send from my canvas A1
GokulNC said:
Atleast try the rooting as in step 1. Those links are just download links.
OK. I'll tell you in short. Download and install these softwares: Minimal ADB and fastboot & AQ 4501Driver
Download this: twrp.img and place it in folder: C:\Program Files\Minimal ADB and Fastboot\
Download this: SuperSu, remove memory card from phone, connect it to PC via card reader and cut & paste this (.zip) file just inside Memory Card and put it back into phone.
Enable USB debugging in phone (Google if u dont know)
Connect phone to PC via USB cable and click on the "Minimal ADB and Fastboot" shortcut in desktop.
Type the following one by one:
Code:
adb devices
adb reboot bootloader
fastboot boot twrp.img
In your phone, wait for few seconds. Click on "Install ZIP". Browse to external_sd and select the file UPDATE-SuperSU-v2.40.zip (which you pasted)
If it asks for confirmation, just do it. That's all! Now reboot phone from there! Your phone is rooted. And I'm tired.
Click to expand...
Click to collapse
In the adb command box whenever I'm typing " adb reboot bootloader"the reply is "device not found". What to do
send from my canvas A1
issei007 said:
In the adb command box whenever I'm typing " adb reboot bootloader"the reply is "device not found". What to do?
Click to expand...
Click to collapse
Did u enable USB debugging in phone and install phone drivers in computer??
If u r sure about this, try this:
Code:
adb devices
If u see a serial number listed in " Devices connected", then it means ur phone is properly configured for ADB.
GokulNC said:
Did u enable USB debugging in phone and install phone drivers in computer??
If u r sure about this, try this:
Code:
adb devices
If u see a serial number listed in " Devices connected", then it means ur phone is properly configured for ADB.
Click to expand...
Click to collapse
Yeah debugging was on and my phone was in fastboot mode. I put the command "adb devices" the reply was "device connected successfully>list of devices connected" and then nothing. When putting the command "adb boot recovery.img" the reply was "waiting for devices" and no nothing happened. Tried this 4 times, did exactly as the video from the XDA root for micromax canvas a1 forum says.
send from my canvas A1
I my problem was with the drivers. I didn't installed the USB driver. Trying again after installing the driver.
send from my canvas A1
Hey Everyone,
I have a Find 7 (X9076). A while back I updated to the "stable version " of ColorOSi and ever since my usb doesn't charge the phone and vol down key doesn't work. Additionally it is being misread by the computer device manager as a "Samsung Android Device" when it is in boot loader mode.
I suspected it was a software/kernel issue because when I checked the registry I found the original oppo drivers, so I attempted to flash a new kernel to the device and ended up soft bricking it (no image). Now even though it is soft bricked I am still able to get into boot loader mode (no image). Please Help?
I have used Find 7 recovery installer and FASTBOOT (CMD) as well as trying to use ADB and a Find 7 unbricking tool in Windows 7 test mode the last two didn't work/didn't recognize my phone at all. I refuse to abandon my device so what do I do?
Given you have adb access, you could extract the contents of the current (2.x?) color os image, and fastboot flash the partitions manually.
I recently did this and 'recovered' my device.
adb didnt recognize my device -but how do I do that just in case I'm able to get it working?
Midnight247 said:
adb didnt recognize my device -but how do I do that just in case I'm able to get it working?
Click to expand...
Click to collapse
I flashed a kernel once and the phone just died. I fixed it by following the unbrick thread in oppo forum.
ADB, FastBoot and the USB
I don't know if I was clear in my explanation as to how and when my device (FIND7 X9076) is recognized ONLY by the following: my Computer (Windows 7), the Device Manager, Fast-Boot and on the FIND7 Recovery Installer. I have been able to enter fast-boot mode on any version of the ColorOS I flashed, 1.2 - 2.5.1, (stable version) and work within the confines of that mode. However when the USB is connected in anything other mode (recovery-main OS) it ceases functionality (sending information to comp for recognition, charging, etc.). Also the charger doesn't work and nor does the notification light. Now I may be wrong, but for these reasons I believe the problem is likely software related. I am open to any opinions and advice.
-Thank You Everyone
tropical cactus said:
I flashed a kernel once and the phone just died. I fixed it by following the unbrick thread in oppo forum.
Click to expand...
Click to collapse
If this http://community.oppo.com/en/forum.php?mod=viewthread&tid=23067&extra= is the guide you are referring to I have downloaded the tool but I cannot seem to get it to recognize my device. I went into test mode downloaded and installed all of the drivers but my FIND7 still doesn't show. Have you had this problem?? What should I do??
Midnight247 said:
If this http://community.oppo.com/en/forum.php?mod=viewthread&tid=23067&extra= is the guide you are referring to I have downloaded the tool but I cannot seem to get it to recognize my device. I went into test mode downloaded and installed all of the drivers but my FIND7 still doesn't show. Have you had this problem?? What should I do??
Click to expand...
Click to collapse
Try the guide by cpthero on pg 28. It worked for me but didn't for the last person who tried it. You have to keep trying. For me, installing drivers was the hard part. After that, it just sailed through. Good luck.
tropical cactus said:
Try the guide by cpthero on pg 28. It worked for me but didn't for the last person who tried it. You have to keep trying. For me, installing drivers was the hard part. After that, it just sailed through. Good luck.
Click to expand...
Click to collapse
Okay, I will. To be honest that is one of the struggles I have been having (drivers installing). I am about to try erasing the false drivers that keep popping up ("Samsung Android Device") from my windows registry. Did you go this far? What did you do to resolve the problem? Thank you for your feedback, I will keep everyone posted.
Midnight247 said:
Okay, I will. To be honest that is one of the struggles I have been having (drivers installing). I am about to try erasing the false drivers that keep popping up ("Samsung Android Device") from my windows registry. Did you go this far? What did you do to resolve the problem? Thank you for your feedback, I will keep everyone posted.
Click to expand...
Click to collapse
Step 7-9 is crucial. If not done, the rest of the process cannot be carried out. Remove battery as well.
tropical cactus said:
Step 7-9 is crucial. If not done, the rest of the process cannot be carried out. Remove battery as well.
Click to expand...
Click to collapse
hmm okay, i see I will keep you posted
**IMPORTANT UPDATE**
***MAKE OPPO FIND 7 OPERABLE****
following commands in fastboot mode:
fastboot flash boot boot.img
fastboot flash userdata userdata.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
By using the afformentioned commands in fastboot (of course) I was able to restore my phone to almost full functionality. It operates noramally and I fixed the notication light, But I say almost because I cannot charge my phone or have it recognized by my computer through any charger or usb connection when it is on normally or in recovery mode so if any one is familiar with this problem please respond or simply voice ideas.
If you got enough functionality to use it, is it on ColorOS? If so, can it be updated? If you have stock recovery you could flash it with AOSP or Spectrum, get full function back then work toward whichever ROM you really want.
RobboW said:
If you got enough functionality to use it, is it on ColorOS? If so, can it be updated? If you have stock recovery you could flash it with AOSP or Spectrum, get full function back then work toward whichever ROM you really want.
Click to expand...
Click to collapse
I do, have full functionality : ) everything but the USB is performing properly, but to be honest I dont know what AOSP is.....also this will repair functionality to the USB?
Hi guys!
After years playing around with android roms and devices it looks that i probably brick a device for first time.
I'll try to be brief, but if you need more info it will be a pleasure give it to you.
Now my MI6 have recovery cofface 3.1.1.-0 installed but no os. I can reboot on bootload with keys. The problem is that im unable to push a zip into the device. Commands "adb devices" and "fastboot devices" return no devices founded.
a) OTG: Recovery doesnt allow me to mount USB-OTG. I enter in Mount and when i click over USB-OTG it highlighted but the checkbox still empty.
b)Plug into pc: The phone appears and disappears each second. Tried multiples wires.
Udev not found warning shows up when I click in the device before it disappears.
c) ADB sideload: not working, cause i cant reach MI6 from PC.
I add some stuff i see in logs and could be interesting:
When i use sideload:
Code:
I: cannot find file /sys/class/android_usb/android0/idProduct
I: cannot find file /sys/class/android_usb/android0/idVendor
When is in appear/disappear loop:
Code:
I:[MTP]Mtpserver::run fd: 20
E:[MTP] request read returned -1, errno: 5 , exiting MtpServer::run loop
I tried to recover it from Windows and Linux even from FWUL liveiso but all same results.
Any idea is appreciated, thanks a lot!
PD: Excuse my English Besides not having a good level, I'm tired of being all day trying things
Shugui said:
Hi guys!
After years playing around with android roms and devices it looks that i probably brick a device for first time.
I'll try to be brief, but if you need more info it will be a pleasure give it to you.
Now my MI6 have recovery cofface 3.1.1.-0 installed but no os. I can reboot on bootload with keys. The problem is that im unable to push a zip into the device. Commands "adb devices" and "fastboot devices" return no devices founded.
a) OTG: Recovery doesnt allow me to mount USB-OTG. I enter in Mount and when i click over USB-OTG it highlighted but the checkbox still empty.
b)Plug into pc: The phone appears and disappears each second. Tried multiples wires.
Udev not found warning shows up when I click in the device before it disappears.
c) ADB sideload: not working, cause i cant reach MI6 from PC.
I add some stuff i see in logs and could be interesting:
When i use sideload:
When is in appear/disappear loop:
I tried to recover it from Windows and Linux even from FWUL liveiso but all same results.
Any idea is appreciated, thanks a lot!
PD: Excuse my English Besides not having a good level, I'm tired of being all day trying things
Click to expand...
Click to collapse
That recovery is ancient. Just use fastboot to flash a stock rom with miflash. Then flash latest twrp.
NickTheSickDick said:
That recovery is ancient. Just use fastboot to flash a stock rom with miflash. Then flash latest twrp.
Click to expand...
Click to collapse
Commands "adb devices" and "fastboot devices" return no devices founded.
Click to expand...
Click to collapse
This is the first roadblock for him.
if fastboot devices can't detect his device, then any fastboot command to flash a partition is also invalid.
Have you tried different machine to do adb devices/ fastboot devices?
ArcOnFire said:
This is the first roadblock for him.
if fastboot devices can't detect his device, then any fastboot command to flash a partition is also invalid.
Click to expand...
Click to collapse
You right
ArcOnFire said:
Have you tried different machine to do adb devices/ fastboot devices?
Click to expand...
Click to collapse
Yes, linux and windows. And drivers are OK cause it worked before.
I think when i wiped system the device got corrupted someway. Now if i plug it into debian machine the computer detect the phone one sec., then dissapear other second, appear again... and so on.
My idea was to flash new recovery from otg but recovery didnt mount the device. Im researching for some way to mount it manually but at the moment not success.
Shugui said:
You right
Yes, linux and windows. And drivers are OK cause it worked before.
I think when i wiped system the device got corrupted someway. Now if i plug it into debian machine the computer detect the phone one sec., then dissapear other second, appear again... and so on.
My idea was to flash new recovery from otg but recovery didnt mount the device. Im researching for some way to mount it manually but at the moment not success.
Click to expand...
Click to collapse
I'm assuming it's a driver error. Few years ago i had a mtk smartphone and somehow i managed to hard brick it, PC recognize it just for 2 or 3 seconds and that was because fastboot drivers didn't installed so i had to install it manually from device manager, for mtk drivers name was preload 89xx (driver must be for specific motherboard model number), i opened device manager, boot phone in fastboot mode, connect it to pc and on the short time wen the PC recognize the phone i hited right click and choose update driver manually, i believe it could be possible to do the same thing with mi 6, i don't know if there are separate drivers for fastboot mode to be able to install them.
mArIuS% said:
I'm assuming it's a driver error. Few years ago i had a mtk smartphone and somehow i managed to hard brick it, PC recognize it just for 2 or 3 seconds and that was because fastboot drivers didn't installed so i had to install it manually from device manager, for mtk drivers name was preload 89xx (driver must be for specific motherboard model number), i opened device manager, boot phone in fastboot mode, connect it to pc and on the short time wen the PC recognize the phone i hited right click and choose update driver manually, i believe it could be possible to do the same thing with mi 6, i don't know if there are separate drivers for fastboot mode to be able to install them.
Click to expand...
Click to collapse
I'll try this when i have a bit more time. Right now i dont have all the time i desire. Too much work and university stuff
Thank you all.
I'll be back
Shugui said:
I'll try this when i have a bit more time. Right now i dont have all the time i desire. Too much work and university stuff
Thank you all.
I'll be back
Click to expand...
Click to collapse
Guys i need ur help please, i cant boot into twrp from fastboot
My step is
My step is go to fastboot > instal mi driver in device manager then adb interface coming > open adb folder > put twrp into adb folder > change name twrp file into recovery then use this command > fastboot flash recovery recovery.img then succes and fastboot boot recovery.img but just stuck on mi logo for 30minutes i guess
Fahrilubis said:
Guys i need ur help please, i cant boot into twrp from fastboot
My step is
My step is go to fastboot > instal mi driver in device manager then adb interface coming > open adb folder > put twrp into adb folder > change name twrp file into recovery then use this command > fastboot flash recovery recovery.img then succes and fastboot boot recovery.img but just stuck on mi logo for 30minutes i guess
Click to expand...
Click to collapse
fastboot devices
fastboot flash recovery twrp.img
fastboot flash boot twrp.img
fastboot reboot
i think u forgot the third command. Anyway check the info, im not 100% sure
Shugui said:
fastboot devices
fastboot flash recovery twrp.img
fastboot flash boot twrp.img
fastboot reboot
i think u forgot the third command. Anyway check the info, im not 100% sure
Click to expand...
Click to collapse
Thx brother solv
Guide updated!!!!!
If you wanna get back to stock ROM and relock bootloader + get OTAs working again, this is the right place!
DISCLAIMER: Relocking bootloader erases all your data/internal storage and (off course) remove TWRP/modules/root, so do a backup of all your data first. Also, I'm not responsible for any bricked devices (phones, SD Cards, etc). I tested it in my XT1955-1 and it worked fine, but we all know that errors might occur.
Finally, let's go to the steps.
Step 1 - Downloading necessary files
Download Android Platform Tools here and then extract it.
Install Motorola Drivers on your PC (download here).
Download the lastest firmware according to your variant/software channel here and extract it in the same folder you had extracted Android Platform Tools.
Download the "Lock Script" here, according to your android version and PC's OS.
For example: if your PC uses Windows as OS, and your phone is in android 10, download the "Lock-10q_windows.bat" file.
Or if you have a Linux distro on your PC and android 9 on your phone, download "Lock-9pie_linux.sh" file.
Place the file inside the platform-tools folder, where the ROM was extracted too.
Step 2 - Preparing your phone
Remove all your google account in device's settings and then go to Developer Options. Enable Android debugging and OEM unlocking (if you can't enable OEM unlocking, you may need to root your device first to get it avaible again (see Rooting thread)).
Power off your phone and put it fastboot mode. Connect it on PC using USB cable.
Step 3 - Installing Stock ROM and re-locking bootloader
Just double click on the Lock.bat/.sh file and it will reflash stock ROM and lock bootloader. Now all you have to do is wait till it finishes. This should take a few minutes to be done.
The phone will boot automatically after the last command is executed.
It seems to be a little hard, but it's easy. If you have any questions, let me know, I'll try to answer ASAP.
Very nice, it's really working! Thanks!
Works on xt1955-4 thanks very much, will the warranty still apply?
piotr1859 said:
Works on xt1955-4 thanks very much, will the warranty still apply?
Click to expand...
Click to collapse
run
Code:
fastboot getvar all
Will tell you if warranty is voided.
Sent from my ali using XDA Labs
piotr1859 said:
Works on xt1955-4 thanks very much, will the warranty still apply?
Click to expand...
Click to collapse
Yes, should work fine. Afaik, once you unlock your bootloader, your warranty is avoid, theoretically. But I guess you can send it to service center (if it's needed) with no problems. They don't always check if you have unlocked your bootloader or not.
Warning: Due to some changes in bootloader and people getting hard bricks in February security patch, i don't recommend to relock bootloader in that version, do it in December security patch instead!
Hello guys. I have Motorola Moto G7 Power (XT1955-4). I've tried to put in twrp and a rom, but when I rebooted my device it don't power on anymore. So I've searched many guides to repair. I've used "blankflash" and after many times I was finally power on my device and go in Fastboot Mode. But now there's another problem. When I connect with usb and open CMD and type "adb devices" appear:
LIST OF DEVICES ATTACHED
or
WAITING FOR DEVICES
I tried many things to fix it but nothing work. Now I've uninstalled everything on my pc, drivers too.
Maybe I've installed bad "blankflash"???
How can I fix my troubles?
DarkAngelNoctis said:
Hello guys. I have Motorola Moto G7 Power (XT1955-4). I've tried to put in twrp and a rom, but when I rebooted my device it don't power on anymore. So I've searched many guides to repair. I've used "blankflash" and after many times I was finally power on my device and go in Fastboot Mode. But now there's another problem. When I connect with usb and open CMD and type "adb devices" appear:
LIST OF DEVICES ATTACHED
or
WAITING FOR DEVICES
I tried many things to fix it but nothing work. Now I've uninstalled everything on my pc, drivers too.
Maybe I've installed bad "blankflash"???
How can I fix my troubles?
Click to expand...
Click to collapse
If the device is in fastboot mode only fastboot commands will work
Code:
fastboot getvar all
edit:grammer
Sent from my ali using XDA Labs
sd_shadow said:
If the device is in fastboot mode only fastboot commands work like
Click to expand...
Click to collapse
Ok. Thanks!
LuisLFSS said:
Warning: Due to some changes in bootloader and people getting hard bricks in February security patch, i don't recommend to relock bootloader in that version, do it in December security patch instead!
Click to expand...
Click to collapse
hey would it be safe to use this method on security patch version April1,2020? if not please point me in the right direction.
thanks
darko454 said:
hey would it be safe to use this method on security patch version April1,2020? if not please point me in the right direction.
thanks
Click to expand...
Click to collapse
Yes, it's safe. Now we have blankflash so it's safe
LuisLFSS said:
Yes, it's safe. Now we have blankflash so it's safe
Click to expand...
Click to collapse
ok thanks!
LuisLFSS said:
Yes, it's safe. Now we have blankflash so it's safe
Click to expand...
Click to collapse
Hi, can you send a link to blankflash for XT1955-1?
THANK YOU.
hawkdown77 said:
Hi, can you send a link to blankflash for XT1955-1?
THANK YOU.
Click to expand...
Click to collapse
Yes, join in my group: t.me/motog7brasil
LuisF201707 said:
If you wanna get back to stock ROM and relock bootloader + get OTAs working again, this is the right place!
DISCLAIMER: Relocking bootloader erases all your data/internal storage and (off course) remove TWRP/modules/root, so do a backup of all your data first. Also, I'm not responsible for any bricked devices (phones, SD Cards, etc). I tested it in my XT1955-1 and it worked fine, but we all know that errors might occur.
Finally, let's go to the steps.
Step 1 - Downloading necessary files
Download Android Platform Tools here and then extract it.
Install Motorola Drivers on your PC (download here).
Download the lastest firmware according to your variant/software channel here and extract it in the same folder you had extracted Android Platform Tools.
Step 2 - Preparing your phone
Remove all your google account in device's settings and then go to Developer Options. Enable Android debugging and OEM unlocking (if you can't enable OEM unlocking, you may need to root your device first to get it avaible again (see Rooting thread)).
Power off your phone and put it fastboot mode. Connect it on PC using USB cable.
Step 3 - Installing Stock ROM
If you're already in stock ROM with no modules and stuff installed on it, just skip this and jump to the next step. If you're not, then stay here.
Open CMD (command prompt) in the same folder you had extracted firmware and android platform tools.
Shift+right click and then "Open command window here" or just type CMD in the folder path bar at the top in windows explorer. Run this commands all at once in CMD:
Once it is done, DON'T power on your phone, just leave it as it is and let's go to the last step.
Step 4 - Relocking Bootoader
In cmd, run this commands all at once
Done! The phone will boot automatically after the last command is executed.
It seems to be a little hard, but it's easy. If you have any questions, let me know, I'll try to answer ASAP.
Click to expand...
Click to collapse
There is an bat file out to relsash stock rom with out trying all that stuff in manually
Help
I followed all the steps and managed to block the bootloader but when I turn on the phone I get "start up failed" can someone help me.
I did it in the April 1 patch
JPalomo1997 said:
I followed all the steps and managed to block the bootloader but when I turn on the phone I get "start up failed" can someone help me.
I did it in the April 1 patch
Click to expand...
Click to collapse
Which android version? There's april security patch for android 9 and 10...
roadkill42 said:
There is an bat file out to relsash stock rom with out trying all that stuff in manually
Click to expand...
Click to collapse
I know... I'll update the thread soon
chrisbchrisb85 said:
For step 4 relocking the bootloader what does "run these commands all at once" mean??? As soon as I lock the bootloader I can no longer flash anything else, therefore still stuck with a boot screen warning
Click to expand...
Click to collapse
"run these commands all at once" = copy all the commands and execute them in cmd...
And which android version did you install? because the commands to flash android 10 are different than android 9 ones
Guide updated!!!!!
I removed those annoying commands and put a link to download Scripts that already do everything automatically. Now the guide is simpler and easier
Hello everyone.
Yesterday I bricked my Xiaomi Redmi Note 8 Pro, and today I managed to unbrick it without requiring anything special (no need for a Authorized Service Account).
I use Linux, so the scripts inside the Stock ROM end with the .sh file extension. If you're using Windows, use the .bat files.
Phone:
Xiaomi Redmi Note 8 Pro 128GB - Begonia (with NFC).
Bricked state:
Constant boot loop;
No access to bootloader;
No access to system;
Access to fastboot.
Phone requirement:
You must be able to load fastboot mode.
PC requirements:
1. You'll need adb tools (SDK Platform-Tools) to communicate with your phone. Official link is below;
2. Download and unpack the Stock ROM linked below.
Instructions:
1. You need to make sure your phone has some power in it;
2. Unpack the Stock Rom and enter its folder (begonia_global_images_V10.4.2.0.PGGMIXM_20191024.0000.00_9.0_global);
3. Put your phone into fastboot mode (Key Combo: Hold the Power button + Volume Down button until the fastboot logo appears);
4. Connect your phone to your PC;
5. Run the flash_all.* scripts according to your operating system:
5.1. Linux: "./flash_all.sh";
5.2. Windows (untested; I'm not using Windows): Run "flash_all.bat" (How to Run a BAT File on Windows);
6. Wait something between 5min to 10min. It's quite fast, and the flashing process is verbose enough.
7. Profit.
F.A.Q.:
1. How did you find this?
Well, none of the unbrick methods in the forum were working, except for the Authorised Service Account one which I didn' t test. I desperately wanted to unbrick my phone by myself, and I thought that it couldn't get worse (it could with a completely blank screen, but I got away with it).
2. Where did you get the Stock ROM from?
I can't remember. It likely was from a xda forum post but I'm unsure. If I can find the original post containing the Stock ROM I used I'll write it here.
3. Which Miui and Android version did you have prior to the brick?
MIUI Global 11.x + Android 9.
4. Which Miui and Android version does the Stock ROM you installed have?
MIUI Global 10.4.2 + Android 9.
5. Can I install any Stock ROM?
As long as it's compatible with your phone version, yes. I recommend not installing a Android 10 Stock ROM because of this: https://forum.xda-developers.com/showpost.php?p=82743011&postcount=3
6. What if can't enter fastboot mode (phone screen in dead blank)?
You won't be able to unbrick your phone using this method. It is worth trying to enter fastboot mode even though your phone has a dead screen, because fastboot might be working anyway (you'll have to test this yourself, as in trying to load fastboot with a blank screen). Read the next question.
7. How can I test if fastboot mode is working?
"adb devices" returns nothing;
"fastboot devices" returns your device (proof it works). Since "fastboot devices" finds your device, you can run the appropriate scripts.
8. What about your Mi Unlock Status before and after the brick?
Before: Unlocked.
After: Unlocked (I thought it would lock the bootloader again, but it didn't).
9. My phone is bricked and I don't know how much battery my phone has left. What should I do?
You should let it turn off due to 0% battery and charge it fully. I do not recommend you flash like I did, without knowing how much battery I had (yes, I took my chances there). As far as I know, any phone in fastboot mode does not charge its battery.
10. Why is fastboot working in your case?
I don't know. I suspect flashing the preloader and the lk from this OP Redmi Note 8 Pro - The Megathread helped, but it's just a hunch.
11. Will you attempt to flash a Custom ROM again?
After taking a break, yes.
12. Is this phone now unbrickable?
As long as fastboot mode works, perhaps. More feedback is required.
Files:
SDK Platform-Tools (adb/fastboot): https://developer.android.com/studio/releases/platform-tools
Stock ROM used: http://bigota.d.miui.com/V10.4.2.0.PGGMIXM/begonia_global_images_V10.4.2.0.PGGMIXM_20191024.0000.00_9.0_global_270117fdb2.tgz
Feedback:
Due to my job I'm currently very short on time during the week to follow this thread, so it would be immensely helpful to have your feedback on this procedure.
Feedback from people who's phones are bricked with blank screens would be very appreciated, specifically if they can enter fastboot mode without any visual cues from their phones. If any bricked state allows fastboot mode, it seems this phone is easily unbrickable.
Thanks:
strongst for his understanding and in reopening this thread.
Compass.
Thread open again
strongst
Forum Moderator
Hi there,
Is there anyway to fix the hardbrick without the authorized account?? If not how can i find someone to do this for me?
andrewff2 said:
Hi there,
Is there anyway to fix the hardbrick without the authorized account?? If not how can i find someone to do this for me?
Click to expand...
Click to collapse
Yes, if you can access fastboot mode in your phone like I mentioned above. If hardbrick means loss of access to fastboot mode/recovery/system/basically everything, you'll need to find some other unbrick method.
If fastboot mode is working for you, you can unbrick your device by yourself with nothing else than the fastboot command and the Stock ROM. No need for any extra tools/programs.
inb4: The fastboot command is in the SDK Platform-Tools package I linked in the OP.
Compass.
Compass Linux said:
Yes, if you can access fastboot mode in your phone like I mentioned above. If hardbrick means loss of access to fastboot mode/recovery/system/basically everything, you'll need to find some other unbrick method.
If fastboot mode is working for you, you can unbrick your device by yourself with nothing else than the fastboot command and the Stock ROM. No need for any extra tools/programs.
inb4: The fastboot command is in the SDK Platform-Tools package I linked in the OP.
Compass.
Click to expand...
Click to collapse
Yeah i tried this method but fastboot cannot even detect device
andrewff2 said:
Yeah i tried this method but fastboot cannot even detect device
Click to expand...
Click to collapse
That's a shame.
It's worth trying different USB ports, cables etc.
I usually enter fastboot mode first and only then I connect the phone to my PC.
Then "./fastboot devices" and my phone is listed.
Compass.
Compass Linux said:
Yes, if you can access fastboot mode in your phone like I mentioned above. If hardbrick means loss of access to fastboot mode/recovery/system/basically everything, you'll need to find some other unbrick method.
If fastboot mode is working for you, you can unbrick your device by yourself with nothing else than the fastboot command and the Stock ROM. No need for any extra tools/programs.
inb4: The fastboot command is in the SDK Platform-Tools package I linked in the OP.
Compass.
Click to expand...
Click to collapse
Yeah i tried this method but fastboot cannot even detect device in windows appear com5 in Windows but fastboot do nothing just white led that blinks
andrewff2 said:
Yeah i tried this method but fastboot cannot even detect device in windows appear com5 in Windows but fastboot do nothing just white led that blinks
Click to expand...
Click to collapse
I can't give support in this area, but do you have the proper Windows drivers installed?
If you do and it still doesn't work, try a different computer. If you can use a Linux machine somehow it's worth trying. With Linux I didn't need to install anything besides the SDK Platform-Tools package to communicate with my phone.
I think you can unbrick your phone, because fastboot mode is loading (if it's loading it should reply to fastboot commands).
Compass.
Compass Linux said:
I can't give support in this area, but do you have the proper Windows drivers installed?
If you do and it still doesn't work, try a different computer. If you can use a Linux machine somehow it's worth trying. With Linux I didn't need to install anything besides the SDK Platform-Tools package to communicate with my phone.
I think you can unbrick your phone, because fastboot mode is loading (if it's loading it should reply to fastboot commands).
Compass.
Click to expand...
Click to collapse
Thanks for the help man but no the only thing is the white led that sometimes blink nothing more no vibration no sound no screen nothing.....
I'm trying to find someone who can help me with this but no one responds... sad
andrewff2 said:
Thanks for the help man but no the only thing is the white led that sometimes blink nothing more no vibration no sound no screen nothing.....
I'm trying to find someone who can help me with this but no one responds... sad
Click to expand...
Click to collapse
It seems the only solution for you is this (for now): [GUIDE] [begonia] UNBRICK - stuck on DA mode / Authorised Service Account required
Which you've probably read already.
I think you either do that or wait to see if another unbrick method appears.
Compass.
I have the same problem as yours and tried your solution but after i run flash_all.bat it just opens and closes in a split-second and i have no idea whether it works or not. Should I wait a couple of minutes or just try again?
advan93 said:
I have the same problem as yours and tried your solution but after i run flash_all.bat it just opens and closes in a split-second and i have no idea whether it works or not. Should I wait a couple of minutes or just try again?
Click to expand...
Click to collapse
That's not normal.
What you should see are various files being flashed along with their progress meter.
I'm assuming you're double clicking the .bat file. Instead of doing that, open a CMD Prompt and use that instead.
Compass.