Related
i used nexus root tool kit to update nexus 4 from 4.4 to 5.0... all done in pc but mobile is stuck in boot loop. can anyone tell me how can i restore my phone to normal working...
Please help me i am noob here
is there any one who can help me here
i thought i will get ans with in 1hr... still waiting if someone can help
letsnexus said:
i thought i will get ans with in 1hr... still waiting if someone can help
Click to expand...
Click to collapse
This is why we don't recommended using tool kits. You should try flashing the factory image using fastboot.
Sent from my Nexus 9 using XDA Free mobile app
Same here, i tried re-flashing many times. Darn that nexus root toolkit
any suggetion or link which can help me to use fastboot use and install stock rom
thank alot for help
I am currently in the same position ! Used a toolkit too, always have.
This is why you never use a Toolkit, it's always been mentioned around in XDA that this has always been a developer website of learning and knowledge. You must always know what goes on behind than just blindly flashing things. It's a rule of thumb that you're more likely to brick your phone with a Toolkit than by yourself. Easiest step as follows.
1. Download factory image
2. Download ADB files
3. Make a folder and extract the adb files and factory image inside the same folder.
4. Plug the phone in bootloader mode or simply type adb reboot bootloader (Developer options must be enabled and USB Debugging) by exiting the folder, holding shift, right clicking the folder and pressing open command window and typing the command.
5. Every factory image comes with a flashall.bat, double click it and voila. Updates like it should. (User data will be wiped)
If you don't want your userdata to be wiped, simply open flashall.bat with notepad++, erase the '-w' in "fastboot -w update image" and save the file and launch it again.
Sent from my HTC One_M8 using Tapatalk
I will try that way later when I get in, I would have assumed that the toolkit did exactly those steps though, just an easy to use frontend
hazwheel said:
I will try that way later when I get in, I would have assumed that the toolkit did exactly those steps though, just an easy to use frontend
Click to expand...
Click to collapse
Go to stock recovery and do factory data reset and reboot phone. First time boot takes very long time (around 10 to 15 minutes). After successfully boot into android L check for the storage space. If it says only 5 GB available instead of 12 GB (My nexus is 16GB) then Go to Settings > Backup & Reset and select Factory data reset.
I had experienced these issues when upgrading to Lollypop and solved them on my own.
Note: If you were not able to boot into stock recovery, try twrp recovery. you have to install it using fastboot
fastboot flash recovery <filename.img>
letsnexus said:
any suggetion or link which can help me to use fastboot use and install stock rom
thank alot for help
Click to expand...
Click to collapse
although the link is for kitkat but the same method applies to flashing lollipop
http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
moorthidaniel said:
Go to stock recovery and do factory data reset and reboot phone. First time boot takes very long time (around 10 to 15 minutes). After successfully boot into android L check for the storage space. If it says only 5 GB available instead of 12 GB (My nexus is 16GB) then Go to Settings > Backup & Reset and select Factory data reset.
I had experienced these issues when upgrading to Lollypop and solved them on my own.
Note: If you were not able to boot into stock recovery, try twrp recovery. you have to install it using fastboot
fastboot flash recovery <filename.img>
Click to expand...
Click to collapse
OK, I was able to get into recovery with this method, and wipe but I get can't mount cache errors during the wipe , waiting for the phone to reboot now, hopefully it will and get out of the bootloop. stupid thing is I'm not a noob, but stumped by this. Good excuse to upgrade to the N5 I guess
---------- Post added at 03:14 PM ---------- Previous post was at 02:55 PM ----------
Wow, this method worked! Brilliant! Thanks, and dammit, it worked, 10 minutes after she agreed to me getting am upgrade !
For all of you whom are stuck in bootloop a fastboot oem lock comand when in fastboot will solve the problem.
So go into bootloader and run "fastboot oem lock" for some reason on some devices Android 5.0 won't boot with unlocked bootloader.
hazwheel said:
OK, I was able to get into recovery with this method, and wipe but I get can't mount cache errors during the wipe , waiting for the phone to reboot now, hopefully it will and get out of the bootloop. stupid thing is I'm not a noob, but stumped by this. Good excuse to upgrade to the N5 I guess
---------- Post added at 03:14 PM ---------- Previous post was at 02:55 PM ----------
Wow, this method worked! Brilliant! Thanks, and dammit, it worked, 10 minutes after she agreed to me getting am upgrade !
Click to expand...
Click to collapse
OK great. Cheers, I helped someone today in this forum.
bett3rthan said:
For all of you whom are stuck in bootloop a fastboot oem lock comand when in fastboot will solve the problem.
So go into bootloader and run "fastboot oem lock" for some reason on some devices Android 5.0 won't boot with unlocked bootloader.
Click to expand...
Click to collapse
That did NOT work for me, the getting into recovery and wiping the device DID work though.
---------- Post added at 04:05 PM ---------- Previous post was at 04:03 PM ----------
moorthidaniel said:
OK great. Cheers, I helped someone today in this forum.
Click to expand...
Click to collapse
Yes, Thanks, unfortunately, she has withdrawn the offer of an early upgrade :silly:
thax
Misledz said:
This is why you never use a Toolkit, it's always been mentioned around in XDA that this has always been a developer website of learning and knowledge. You must always know what goes on behind than just blindly flashing things. It's a rule of thumb that you're more likely to brick your phone with a Toolkit than by yourself. Easiest step as follow
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Thank you alot, you help in really good manner
and teached us not to use toolkit
will learn more abt rooting and flashing thank you once again
I am hitting this problem now, I got a OTA. After restarting its keep on looping waiting for more than 20mins still it's looping.
Tried going to boot-menu and did factory reset and it booted good after ~10 mins.
sububack said:
I am hitting this problem now, I got a OTA. After restarting its keep on looping waiting for more than 20mins still it's looping.
Click to expand...
Click to collapse
Power off, hold Vol Down + Power, when you get to the Android laying down, press volume up + pwr, then wipe the /cache from the menu (you do not need to do a full factory wipe, just wiping cache will do), and then reboot and wait. It will boot this time properly. @WugFresh is aware of the issue and said will put a fix in 1.9.9 for the N4
Thanks , I have tried clearing the cache and started waiting for an hour. Since it was still looping tried after factory reset/wiping user data. And then after 10min it came good.
I post this on Google Product Forum 2 days ago. Hope it helps
https://productforums.google.com/fo...ce=footer#!msg/nexus/Lv8fHtyJOPQ/wDzRUm4b2UsJ
(updated 29/11/2014)[not perfect but it is a SOLUTION]
The idea of this is to downgrade your nexus 4 without wiping your data, which means stuff you will need includes:
1. adb and fastboot on your computer (I am using mac but you can find it on windows as well. There are tones of website and forums telling you the latest method of getting it onto your computer)
2. factory image of nexus 4(I use 4.4.4, since that's what it was. I don't have the time and energy to try to do the same thing with lollipop. you can try can leave a comment).
update: do NOT try to flash 5.0 rom using this method. You will be stuck at boot loop again
3. usb cable
4. nexus 4 with unlocked bootloader(the process of unlocking bootloader will wipe your device)
5. computer
steps
1. unzip the factory image (something.tgz)
2. for me, after unzipping the .tgz, I still find another .zip inside. unzip that too.
3. hold vol+, vol-, and power button simultaneously to enter fastboot mode
4. open terminal(mac)(it would probably be cmd for windows)
5. connect your nexus 4(in fastboot)
6. to make sure it connect successfully, type "fastboot devices". if something like "005040c0d54bb291 fastboot" appears, you are good. Otherwise, try reconnect your device/boot to fastboot again/use another usb cable
7.now we need to tell the terminal to navigate to the location of the unzipped factory image. to do that, i suggest you put the unzipped folder to somewhere easy to find, like desktop. these are some commands to help you navigate:
"ls" allows you to look at whats inside the current directory of the terminal. For example, this is the output after typing "ls" for me:
some folder Photos
nexus4image.tgz how many folders do you have
5.zip occam-ktu84p
more folder occam-ktu84p.zip
after knowing where you are, use "cd" (below) to go to your folder
"cd" means change directory. For example. "cd Photos" will brings me to the "Photos" folder. And then if I type ls, I will see a whole bunch of photos in my photos. If you go to the wrong folder, type "cd ..", and it will bring you back to the previous folder.
8. flash bootloader.
enter the following command, BUT REMEMBER TO CHANGE THE NAME TO FIT YOURS(DIFFERENT VERSIONS HAVE SLIGHTLY DIFFERENT FILE NAME AT THE END(type ls first to help you type the correct name)
fastboot flash bootloader bootloader-mako-makoz30d.img
9. reboot bootloader. just copy and paste
fastboot reboot-bootloader
10. flash radio
enter the following command, BUT REMEMBER TO CHANGE THE NAME TO FIT YOURS(DIFFERENT VERSIONS HAVE SLIGHTLY DIFFERENT FILE NAME AT THE END(type ls first to help you type the correct name)
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.03.img
11. reboot bootloader. just copy and paste
fastboot reboot-bootloader
12. flash system
system.img is located inside the zip, use ls to help you navigate. This steps takes the longest time, total time on this step is 87 seconds while the others are less then 1 second
fastboot flash system system.img
13. flash boot
boot.img is located inside the zip, use ls to help you navigate.
fastboot flash boot boot.img
14. flash recovery
fastboot.img is located inside the zip, use ls to help you navigate.
fastboot flash recovery recovery.img
15. format cache(not the memory, so everything should be fine)
fastboot format cache
16. reboot and wait
this will reboot your device. You probably have to wait for a while to initialise all the apps. after than you are good to go!
fastboot reboot
credit: my friend for giving me this idea + http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312 + HelpMyNexus
Hello everyone, in today's guide I will tell you all how to fix bootloop problem in Redmi note 4
NOTE: THIS FIX IS FOR THOSE WHOSE PROBLEM DIDN'T GET FIXED EVEN AFTER FLASHING WITH MIFLASH
QFIL is a tool which is used to flash stock firmwares in Qualcomm smartphones.
Prerequisites:
1)Bricked Redmi note 4 (lol I guess you have that already if you are reading this)
2) Working USB cable (You really dont want yourself smashing your head and then finding out faulty cable)
3) QPST Version 2.7.438.3 (Google it)
4) Unlocked bootloader
5) Platform Tools (For passing OEM EDL command)
6) Stock fastboot MIUI ROM (IMPORTANT: Use V8.1.10.0.MCFMIDI from here: http://bigota.d.miui.com/V8.1.10.0....DI_20161228.0000.00_6.0_global_7557bfe334.tgz)
7)QDLoader HS-USB Driver for Redmi Note 4X
Note: I'm not responsible if you mess up your device the mentioned process helped me and others in fixing our devices. You yourself are responsible!
Steps:
1) Open QFIL tool from C:\Program Files\Qualcomm\QPST\bin or wherever you installed it. Run as administrator!
Note: Don't use older version QPST, because you will get an error message when writing userdata section.
2) In QFIL choose Flat Build option.
3) Make sure you you have extracted the above ROM file onto desktop
4) In QFIL tool browse and locate .mbn file
(Named like: prog_emmc_firehose_8953_ddr.mbn)
5) Click on Load XML and select rawprogram0.xml and patch0.xml inside your Fastboot ROM folder.
6) Now turn off your phone and enter Fastboot mode by pressing ans holding power button+vol down button. After that open platform tools folder downloaded above and right click opening cmd in that folder and write following command:
fastboot oem edl
And hit enter (The above command does require your bootloader to be unlocked so kindly keep that in mind before passing the command)
7) Your phone will exit Fastboot mode and red led will start blinking and your phone will be detected as COM port in QFIL tool.
8) At last hit download button, if you did everything right process should begin and end saying download complete.
9) You can now remove your phone and keep holding power button till it boots up. First boot will take some time.
Optional step 10) If you loose your IMEI in flashing process then you can flash your IMEI using Qualcomm IMEI tool (If you face problem in this then comment and i will come up with another guide regarding IMEI flashing)
Hope it helps, if yes be sure you hit that thumbs up button it gives me good feeling lol ?
Reply if you face any problem
Peace!
addymishra said:
Hello everyone, in today's guide I will tell you all how to fix bootloop problem in Redmi note 4
NOTE: THIS FIX IS FOR THOSE WHOSE PROBLEM DIDN'T GET FIXED EVEN AFTER FLASHING WITH MIFLASH
QFIL is a tool which is used to flash stock firmwares in Qualcomm smartphones.
Prerequisites:
1)Bricked Redmi note 4 (lol I guess you have that already if you are reading this)
2) Working USB cable (You really dont want yourself smashing your head and then finding out faulty cable)
3) QPST Version 2.7.438.3 (Google it)
4) Unlocked bootloader
5) Platform Tools (For passing OEM EDL command)
6) Stock fastboot MIUI ROM (IMPORTANT: Use V8.1.10.0.MCFMIDI from here: http://bigota.d.miui.com/V8.1.10.0....DI_20161228.0000.00_6.0_global_7557bfe334.tgz)
7)QDLoader HS-USB Driver for Redmi Note 4X
Note: I'm not responsible if you mess up your device the mentioned process helped me and others in fixing our devices. You yourself are responsible!
Steps:
1) Open QFIL tool from C:\Program Files\Qualcomm\QPST\bin or wherever you installed it. Run as administrator!
Note: Don't use older version QPST, because you will get an error message when writing userdata section.
2) In QFIL choose Flat Build option.
3) Make sure you you have extracted the above ROM file onto desktop
4) In QFIL tool browse and locate .mbn file
(Named like: prog_emmc_firehose_8953_ddr.mbn)
5) Click on Load XML and select rawprogram0.xml and patch0.xml inside your Fastboot ROM folder.
6) Now turn off your phone and enter Fastboot mode by pressing ans holding power button+vol down button. After that open platform tools folder downloaded above and right click opening cmd in that folder and write following command:
fastboot oem edl
And hit enter
7) Your phone will exit Fastboot mode and red led will start blinking and your phone will be detected as COM port in QFIL tool.
8) At last hit download button, if you did everything right process should begin and end saying download complete.
9) You can now remove your phone and keep holding power button till it boots up. First boot will take some time.
Optional step 10) If you loose your IMEI in flashing process then you can flash your IMEI using Qualcomm IMEI tool (If you face problem in this then comment and i will come up with another guide regarding IMEI flashing)
Hope it helps, if yes be sure you hit that thumbs up button it gives me good feeling lol
Reply if you face any problem
Peace!
Click to expand...
Click to collapse
Hi,
after your manual, download success, the device restarts, but it then gets stuck with the MI logo?
What can I do?
sieg
sieg01 said:
Hi,
after your manual, download success, the device restarts, but it then gets stuck with the MI logo?
What can I do?
sieg
Click to expand...
Click to collapse
Hello there,
First of all make sure that you are flashing the fastboot rom which I mentioned in the thread.
Now coming to your problem, open QFIL tool and open configuration panel. You will see many options, check for 'Erase before Download' option and make sure its unchecked then try flashing again. If the problem persist then send me screenshot of QFIL tool along with configuration.
All the best!
addymishra said:
Hello there,
First of all make sure that you are flashing the fastboot rom which I mentioned in the thread.
Now coming to your problem, open QFIL tool and open configuration panel. You will see many options, check for 'Erase before Download' option and make sure its unchecked then try flashing again. If the problem persist then send me screenshot of QFIL tool along with configuration.
All the best!
Click to expand...
Click to collapse
Hi again,
I have flashed again and in the " download configuration " I set " Erase before Download", please see the Attachment, unfortunately the same device restarts, but it then gets stuck with the MI logo?
sieg01 said:
Hi again,
I have flashed again and in the " download configuration " I set " Erase before Download", please see the Attachment, unfortunately the same device restarts, but it then gets stuck with the MI logo?
Click to expand...
Click to collapse
Dear, you DON'T NEED TO SELECT "ERASE BEFORE DOWNLOAD" !!! Now listen carefully what to do-:
1) Download mi flash tool and mi unlock tool
2) Your bootloader must be locked now so unlock it with mi unlock (Don't worry just use your mi account it will unlock successfully)
3) Once unlocked flash the fastboot rom in fastboot mode using mi flash tool. IMPORTANT: MAKE SURE YOU SELECT "CLEAN ALL" OPTION
4) Now when flashed your device will restart. Dont let it boot up. Press and hold power+volume down button till you enter into fastboot
5) From fastboot enter EDL mode using "fastboot oem edl" command. Red light will blink
6) Open QFIL and make sure "Erase before download" IS *NOT* SELECTED
7)Click download and you should be good to go
All the best
addymishra said:
Dear, you DON'T NEED TO SELECT "ERASE BEFORE DOWNLOAD" !!! Now listen carefully what to do-:
1) Download mi flash tool and mi unlock tool
2) Your bootloader must be locked now so unlock it with mi unlock (Don't worry just use your mi account it will unlock successfully)
3) Once unlocked flash the fastboot rom in fastboot mode using mi flash tool. IMPORTANT: MAKE SURE YOU SELECT "CLEAN ALL" OPTION
4) Now when flashed your device will restart. Dont let it boot up. Press and hold power+volume down button till you enter into fastboot
5) From fastboot enter EDL mode using "fastboot oem edl" command. Red light will blink
6) Open QFIL and make sure "Erase before download" IS *NOT* SELECTED
7)Click download and you should be good to go
All the best
Click to expand...
Click to collapse
1. My redmi is unlocked ( from Xiaomi )
2. MI flash tool don`t work, because I get error: can not found file flash_all.bat, so I dont`t use this tool
sieg01 said:
1. My redmi is unlocked ( from Xiaomi )
2. MI flash tool don`t work, because I get error: can not found file flash_all.bat, so I dont`t use this tool
Click to expand...
Click to collapse
In order to use mi flash correctly kindly place the fastboot rom in C: drive root directory then try flashing, it will work. Its a bug of mi flash
Hi I followed your all 9 steps in the first post. However, me too is stuck in 'mi' logo nothing happens waiting after 10 minutes
Then I followed the following steps, flashed by mi tool followed by QFIL. But my QFIL didn't have "ERASE BEFORE DOWNLOAD" option. I downloaded the exact QPST version 2.7.438.3 from gsmhosting forum.
Still the phone boots and stuck with 'mi' logo forever. I have tried flashing other ROMs like RR, lineageOS from TWRP but each of the ROM is stuck while booting . Only miuiPro "miuipro_v7.0_mido_v9.2.1.0_NCFCNEK.zip" manages to boot but keeps rebooting after every 2-3 seconds. My phone has been useless for 3 long days.
addymishra said:
Dear, you DON'T NEED TO SELECT "ERASE BEFORE DOWNLOAD" !!! Now listen carefully what to do-:
1) Download mi flash tool and mi unlock tool
2) Your bootloader must be locked now so unlock it with mi unlock (Don't worry just use your mi account it will unlock successfully)
3) Once unlocked flash the fastboot rom in fastboot mode using mi flash tool. IMPORTANT: MAKE SURE YOU SELECT "CLEAN ALL" OPTION
4) Now when flashed your device will restart. Dont let it boot up. Press and hold power+volume down button till you enter into fastboot
5) From fastboot enter EDL mode using "fastboot oem edl" command. Red light will blink
6) Open QFIL and make sure "Erase before download" IS *NOT* SELECTED
7)Click download and you should be good to go
All the best
Click to expand...
Click to collapse
biits1993 said:
Hi I followed your all 9 steps in the first post. However, me too is stuck in 'mi' logo nothing happens waiting after 10 minutes
Then I followed the following steps, flashed by mi tool followed by QFIL. But my QFIL didn't have "ERASE BEFORE DOWNLOAD" option. I downloaded the exact QPST version 2.7.438.3 from gsmhosting forum.
Still the phone boots and stuck with 'mi' logo forever. I have tried flashing other ROMs like RR, lineageOS from TWRP but each of the ROM is stuck while booting . Only miuiPro "miuipro_v7.0_mido_v9.2.1.0_NCFCNEK.zip" manages to boot but keeps rebooting after every 2-3 seconds. My phone has been useless for 3 long days.
Click to expand...
Click to collapse
Try downloading the lastest version from here:
https://androidmtk.com/download-qpst-flash-tool
Erase before download must be unchecked
And remember first boot does take some time so be patient a little. Hope it works!
addymishra said:
Try downloading the lastest version from here:
https://androidmtk.com/download-qpst-flash-tool
Erase before download must be unchecked
And remember first boot does take some time so be patient a little. Hope it works!
Click to expand...
Click to collapse
Hi, Thank you very much, I managed to boot the ROM using QFil , however in setup wizard I can't get past the getting device security info in mi account setup. Besides, dialogues for lots "app stopped working" keeps coming. and also there are frequent reboots
addymishra said:
In order to use mi flash correctly kindly place the fastboot rom in C: drive root directory then try flashing, it will work. Its a bug of mi flash
Click to expand...
Click to collapse
Hi,
II managed to flash successfully with MIflash tool, but after switching it on
do I have permanent boot loop with MI logo? Andere Fastboot ROM`s will MIflash nicht machen. Please look my Screenshot.
Greating
biits1993 said:
Hi, Thank you very much, I managed to boot the ROM using QFil , however in setup wizard I can't get past the getting device security info in mi account setup. Besides, dialogues for lots "app stopped working" keeps coming. and also there are frequent reboots
Click to expand...
Click to collapse
Strange :/ you can try miflash tool for that case. Download the lastest mi flash tool, enter into EDL mode using "fastboot oem edl" command then in mi flash drop down menu in left corner select "flash_factory.bat" and click flash. It will take around 400 seconds. Make sure you are in edl mode with red blinking light otherwise it will wipe your IMEI. Hope it works!
sieg01 said:
Hi,
II managed to flash successfully with MIflash tool, but after switching it on
do I have permanent boot loop with MI logo? Andere Fastboot ROM`s will MIflash nicht machen. Please look my Screenshot.
Greating
Click to expand...
Click to collapse
Are you able to enter into setup wizard? If not then try the procedure I posted above using factory flash. After flashing with mi flash once again try flashing with QFIL. It's sometimes hit or miss :/
addymishra said:
Are you able to enter into setup wizard? If not then try the procedure I posted above using factory flash. After flashing with mi flash once again try flashing with QFIL. It's sometimes hit or miss :/
Click to expand...
Click to collapse
Hi,
I don`t able to enter into setup wizard, because boot-loop, so I done following:
1. mi flash factory flash-successfully
2. mi flash flash once again-successfully
3. flashing with QFIL- successfully
After switch-on again boot loop every 22 seconds with mi-logo
Do you have any more tips for me?
Greating
sieg
sieg01 said:
Hi,
I don`t able to enter into setup wizard, because boot-loop, so I done following:
1. mi flash factory flash-successfully
2. mi flash flash once again-successfully
3. flashing with QFIL- successfully
After switch-on again boot loop every 22 seconds with mi-logo
Do you have any more tips for me?
Greating
sieg
Click to expand...
Click to collapse
Man, I think its some sort of hardware issue then. Or maybe your messed up your blobs or your partitions real bad and corrupted them. QFIL helped in my case. Got no more tips, maybe its time to visit service center brother One last shot you can give is to try flashing with QFIL first then with Mi Flash. That's last hope! All the best!
flash failed in QFIL please help
sohanaw said:
flash failed in QFIL please help
Click to expand...
Click to collapse
Which version of QFIL and which ROM are you flashing with? I managed to flash the said version in OP through QFIL without any error. However, other official versions like 9.xx fail to be flashed by QFIL
A solution that worked after all these troubles
Hi everyone,
This post is for those who are still struggling with 'cool' bootloop in Redmi note 4x irrespective of stock, custom ROMS, you are flashing.
Before all these steps I flashed "mido_global_images_V8.1.10.0.MCFMIDI_20161228.0000.00_6.0_global_7557bfe334.tgz" using QFIL first, then miFlash tool. I was greeted by "can't decrypt phone".
Refer to the OP
Then I flashed lazy_flasher and managed to boot into the stock ROM but couldn't get past the Mi account setup. Even my Keyboard app keeps stopping, so annoying.
The the below Steps I followed redeemed me of this agony powered by xiaomi:
1. Downloaded this firmware==>"global-mido-firmware-7.12.14.zip"
Mokee ROM==>"MK71.2-mido-201803080920-NIGHTLY"
open gapps arm-64, 7.1, pico
open gapps arm-64, 7.1, nano [BOTH] from gapps
2. flashed TWRP=3.1.1-0[official version] from the xda
Code:
fastboot flash recovery [name_of_recovery_image_of_twrp]
3. Entered into Recovery==>WIPE=>Advanced WIPE=> select all partitions==>WIPE[can leave Internal storage unchecked]
4. Then Format Data==>yes
5. Copied firmware, Mokee ROM, pico and nano gapps [4 items] to internal storage
6. Flashed downloaded firmware, then MOKEE ROM, then gapps-nano
7. Reboot to recovery
8. After entering Recovery, Reboot to system
Hopefully we will see mi logo, then Mokee robot animating soon enough. It will take you to setup wizard within 5-10 minutes, If you see any Google apps [Gboard in my case] stopping,
it may mean that google Play services were not installed properly[Don't know why]. In my case I couldn't set up Google account/framework first time. If it happens, go to settings,
enable developer options tapping BUILD version==>then enable USB debugging.
Then reboot to Recovery
Flash gapps-pico.
Do factory reset from Recovery, simple wipe.
Then reboot to System.[DON'T install TWRP as system app etc]
For me, this time I was able to setup google account from the setup wizard. Google service framework has been working without any issues. [ Again Don't know why]
This time I have been able to install my desired apps from playstore
Few more words:
Firstly, I tried flashing only pico, but I couldn't set up the google account, no matter how many times I reboot to recovery, wipe Dalvik-cache etc, then flash pico.
I described exactly what I did that worked out for me. There could be many possible orders, combinations, but I don't have time for that.
I tried to flash Alexy's "RR-N-v5.8.5-20180121mido_alexy.zip" ROM in combination with this firmware but it just will hang TWRP while flashing. only this MOKEE ROM worked with this firmware for me.
I wasted full 3 days for fixing this device. And no intention to tinker with it anymore, my communication has been in a mess!.
While in stock MIUI 'google *apps keeps stopping" just annoyed me as hell, so decided to switch, and after 3 days of disgusting 'Waiting period for bootloader UNLOCK' I couldn't even install a working stock
MIUI ROM now, maybe cheap hardware issue offered by Xiaomi. They have just made everything complex. This is my first and last device from them. My previous Moto G3 was amazing and would be with me had it not been stolen
Will be happy to help regarding this issue, and thank you the OP of this thread, who helped me realize that this device is still able to boot.
Wishing everyone in this note 4x trouble good luck!!
biits1993 said:
Hi everyone,
This post is for those who are still struggling with 'cool' bootloop in Redmi note 4x irrespective of stock, custom ROMS, you are flashing.
Before all these steps I flashed "mido_global_images_V8.1.10.0.MCFMIDI_20161228.0000.00_6.0_global_7557bfe334.tgz" using QFIL first, then miFlash tool. I was greeted by "can't decrypt phone".
Refer to the OP
Then I flashed lazy_flasher and managed to boot into the stock ROM but couldn't get past the Mi account setup. Even my Keyboard app keeps stopping, so annoying.
The the below Steps I followed redeemed me of this agony powered by xiaomi:
1. Downloaded this firmware==>"global-mido-firmware-7.12.14.zip"
Mokee ROM==>"MK71.2-mido-201803080920-NIGHTLY"
open gapps arm-64, 7.1, pico
open gapps arm-64, 7.1, nano [BOTH] from gapps
2. flashed TWRP=3.1.1-0[official version] from the xda
Code:
fastboot flash recovery [name_of_recovery_image_of_twrp]
3. Entered into Recovery==>WIPE=>Advanced WIPE=> select all partitions==>WIPE[can leave Internal storage unchecked]
4. Then Format Data==>yes
5. Copied firmware, Mokee ROM, pico and nano gapps [4 items] to internal storage
6. Flashed downloaded firmware, then MOKEE ROM, then gapps-nano
7. Reboot to recovery
8. After entering Recovery, Reboot to system
Hopefully we will see mi logo, then Mokee robot animating soon enough. It will take you to setup wizard within 5-10 minutes, If you see any Google apps [Gboard in my case] stopping,
it may mean that google Play services were not installed properly[Don't know why]. In my case I couldn't set up Google account/framework first time. If it happens, go to settings,
enable developer options tapping BUILD version==>then enable USB debugging.
Then reboot to Recovery
Flash gapps-pico.
Do factory reset from Recovery, simple wipe.
Then reboot to System.[DON'T install TWRP as system app etc]
For me, this time I was able to setup google account from the setup wizard. Google service framework has been working without any issues. [ Again Don't know why]
This time I have been able to install my desired apps from playstore
Few more words:
Firstly, I tried flashing only pico, but I couldn't set up the google account, no matter how many times I reboot to recovery, wipe Dalvik-cache etc, then flash pico.
I described exactly what I did that worked out for me. There could be many possible orders, combinations, but I don't have time for that.
I tried to flash Alexy's "RR-N-v5.8.5-20180121mido_alexy.zip" ROM in combination with this firmware but it just will hang TWRP while flashing. only this MOKEE ROM worked with this firmware for me.
I wasted full 3 days for fixing this device. And no intention to tinker with it anymore, my communication has been in a mess!.
While in stock MIUI 'google *apps keeps stopping" just annoyed me as hell, so decided to switch, and after 3 days of disgusting 'Waiting period for bootloader UNLOCK' I couldn't even install a working stock
MIUI ROM now, maybe cheap hardware issue offered by Xiaomi. They have just made everything complex. This is my first and last device from them. My previous Moto G3 was amazing and would be with me had it not been stolen
Will be happy to help regarding this issue, and thank you the OP of this thread, who helped me realize that this device is still able to boot.
Wishing everyone in this note 4x trouble good luck!!
Click to expand...
Click to collapse
will try this tonight, thanks bhai
sohanaw said:
will try this tonight, thanks bhai
Click to expand...
Click to collapse
Let me know bro what happens, hope it works for you
I wanted to use RR rom though, but in the end no ROM worked for me except this one. So I'm just happy with it.
I'm 63 years old & could do with some help - trying to flash my Moto G4 but no luck
Hello folks.
I apologise in advance. I thought something was a good idea, and I said to myself I would give it a try and I won't give up, but I have been at this for about 5 hours now and no progress.
I have a Moto G4 which my wife gave about a year ago. I don't like stock Android and want to install Lineage OS onto it. I understand that first I need to:
1. Unlock my bootloader (done)
2. Install ADB Driver Installer onto my Dell (done)
3. Install Minimal ADB and Fastboot onto my Dell (done)
4. Plug my G4 into my Dell using the correct cable. It seems to work as the ADP Driver Installer / APK Installer recognises it as per the image below
https://drive.google.com/open?id=1QZAu9ZrCsKBhUcCofo2bde5aB89v76TB
5. Open up the command promt in the Minimal ADB and Fastboot folder, type adb devices - the device is recognised
6. Here is where the problems start!
(a) At this stage, as soon as I type adb reboot bootloader, the G4 reboots but as it does, it disappears from the ADB Diver Installer / APK Installer!
(b) Soon after when I type fastboot flash recovery twrp.img then nothing is found, no files or directory or anything.
I don't understand what I am doing wrong and am very stuck sadly.
https://drive.google.com/file/d/1zR361DukYrsc923zD2q6Aml3Xr0DVqlj/view?usp=sharing
Would really appreciate some help from you young clever guys!
Thank you.
George.
George425 said:
Hello folks.
I apologise in advance. I thought something was a good idea, and I said to myself I would give it a try and I won't give up, but I have been at this for about 5 hours now and no progress.
I have a Moto G4 which my wife gave about a year ago. I don't like stock Android and want to install Lineage OS onto it. I understand that first I need to:
1. Unlock my bootloader (done)
2. Install ADB Driver Installer onto my Dell (done)
3. Install Minimal ADB and Fastboot onto my Dell (done)
4. Plug my G4 into my Dell using the correct cable. It seems to work as the ADP Driver Installer / APK Installer recognises it as per the image below
https://drive.google.com/open?id=1QZAu9ZrCsKBhUcCofo2bde5aB89v76TB
5. Open up the command promt in the Minimal ADB and Fastboot folder, type adb devices - the device is recognised
6. Here is where the problems start!
(a) At this stage, as soon as I type adb reboot bootloader, the G4 reboots but as it does, it disappears from the ADB Diver Installer / APK Installer!
(b) Soon after when I type fastboot flash recovery twrp.img then nothing is found, no files or directory or anything.
I don't understand what I am doing wrong and am very stuck sadly.
https://drive.google.com/file/d/1zR361DukYrsc923zD2q6Aml3Xr0DVqlj/view?usp=sharing
Would really appreciate some help from you young clever guys!
Thank you.
George.
Click to expand...
Click to collapse
It says no twrp.img in that folder.
Because You renamed it's name to twrp.img.img ?
Try flash with "fastboot flash recovery twrp.img.img"
common file extensions are not shown in name, or while rename, but you added ".img" at last, so it is doubled..
Hello sir,
Copy the twrp file to the folder where ADB is installed. The folder is located in C drive.
Next you can Shift+right click, open powershell/cmd, whichever is there.
Now type in command
" fastboot flash recovery tw" and click tab button. After tab button, click enter.
This should be done when phone is in bootloader mode and connected to laptop/PC.
after the command execution is over, you can reboot to recovery.
First flash Ex kernel and then flash magisk, in THIS ORDER ONLY, OR YOUR PHONE WILL BRICK!
And voila, you have root! Flash anything!
____Mdd said:
It says no twrp.img in that folder.
Because You renamed it's name to twrp.img.img ?
Try flash with "fastboot flash recovery twrp.img.img"
common file extensions are not shown in name, or while rename, but you added ".img" at last, so it is doubled.
Click to expand...
Click to collapse
Thank you for your suggestion. I did exactly as you said, in fact I tried different variations - I changed twrp.img to just twrp, then tried the command fastboot flash recovery twrp.img, nothing and then I changed it back to how it was, twrp.img and tried the command again, this time ending with twrp.img.img and nothing. Result is as shown below (bootloader not found / not signed or corrupted).
https://drive.google.com/open?id=1qMgUDp767Q32c0MmH2Ey17cpEGI75cJS
What shall I try now?
George425 said:
Thank you for your suggestion. I did exactly as you said, in fact I tried different variations - I changed twrp.img to just twrp, then tried the command fastboot flash recovery twrp.img, nothing and then I changed it back to how it was, twrp.img and tried the command again, this time ending with twrp.img.img and nothing. Result is as shown below (bootloader not found / not signed or corrupted).
https://drive.google.com/open?id=1qMgUDp767Q32c0MmH2Ey17cpEGI75cJS
What shall I try now?
Click to expand...
Click to collapse
You flashed it. Reboot into recovery now.
George425 said:
Thank you for your suggestion. I did exactly as you said, in fact I tried different variations - I changed twrp.img to just twrp, then tried the command fastboot flash recovery twrp.img, nothing and then I changed it back to how it was, twrp.img and tried the command again, this time ending with twrp.img.img and nothing. Result is as shown below (bootloader not found / not signed or corrupted).
https://drive.google.com/open?id=1qMgUDp767Q32c0MmH2Ey17cpEGI75cJS
What shall I try now?
Click to expand...
Click to collapse
You've done it! Reboot to recovery!
Lyuu said:
You flashed it. Reboot into recovery now.
Click to expand...
Click to collapse
DhirajKale789 said:
You've done it! Reboot to recovery!
Click to expand...
Click to collapse
Yes you are both absolutely correct thank you for your help! I didn't think it was working!
At some moment when playing with Magisk modules, I've got Android crash, after which sensors (Accelerometer, Gravity, etc.) and Camera stopped working.
Obviously, somehow persist partition data got corrupted and must be reflashed. I believe, that flashing persist via fastboot is not supported, so I reflashed it via ADB, and got everything working.
What we'll need to flash persist partition:
1. Mi A2 with unlocked bootloader and critical partitions, on stock Pie 10.0.2.0 to 10.0.7.0, connected to an USB 2.0 port in PC MB; USB debugging and MTP file transfer enabled;
2. Working copy of ADB / Fastboot installation
3. image of persist partition, can be found in each stock fastboot image
https://forum.xda-developers.com/mi-a2/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824849
as "jasmine_global_images_V10.0.2.0.PDIMIFJ_9.0\images\persist.img"; must be copied to ADB / Fastboot installation directory.
4. twrp-3.3.1-5-jasmine_sprout-unofficial.img, copied to ADB / Fastboot installation directory
https://forum.xda-developers.com/mi-a2/development/recovery-mi-a2-jasminesprout-t3941096
Note: even if TWRP boots with black screen, this method should work as we'll not control process on Mi A2, instead we'll use ADB commandsthis TWRP is reported to work with all variants of MiA2 screen panels.
5. Attached command file "flash_persist.cmd", unZIPped to ADB / Fastboot installation directory.
Instruction:
Run "flash_persist.cmd" from CMD shell or Explorer (probably admin rights needed?).
Command file execution will be paused several times, waiting for ADB and fastboot commands execution.
Please read CMD window output, check that phone is being switched to needed mode and/or ADB/Fastboot commands succeed.
In case something goes wrong, press Ctrl^C and terminate batch job.
After 1st reboot from TWRP, reboot once more by standard means.
Update:
- attached f"lash_persist_V2.zip" using "twrp-3.3.1-5-jasmine_sprout-unofficial"
my mi a2 is in ARB4, I can only use MIUI, could you tell me how do I get the persist file, could also explain where TWRP comes in since the command is made by ADB?
Aerobatic said:
At some moment when playing with Magisk modules, I've got Android crash, after which sensors (Accelerometer, Gravity, etc.) and Camera stopped working.
Obviously, somehow persist partition data got corrupted and must be reflashed. I believe, that flashing persist via fastboot is not supported, so I reflashed it via ADB, and got everything working.
What we'll need to flash persist partition:
1. Mi A2 with unlocked bootloader and critical partitions, on stock Pie 10.0.2.0 to 10.0.7.0, connected to an USB 2.0 port in PC MB; USB debugging and MTP file transfer enabled;
2. Working copy of ADB / Fastboot installation
3. image of persist partition, can be found in stock fastboot image
http://en.miui.com/download-353.html
as "jasmine_global_images_V10.0.2.0.PDIMIFJ_9.0\images\persist.img"; must be copied to ADB / Fastboot installation directory.
4. twrp-3.2.3-0-jasmine_sprout.img, copied to ADB / Fastboot installation directory
https://dl.twrp.me/jasmine_sprout/
Note: even if TWRP boots with black screen, this method should work as we'll not control process on Mi A2, instead we'll use ADB commands.
5. Attached command file "flash_persist.cmd", unZIPped to ADB / Fastboot installation directory.
Instruction:
Run "flash_persist.cmd" from CMD shell or Explorer (probably admin rights needed?).
Command file execution will be paused several times, waiting for ADB and fastboot commands execution.
In case something goes wrong, press Ctrl^C and terminate batch job.
After 1st reboot from TWRP, reboot once more by standard means.
Click to expand...
Click to collapse
I don't understand either why is twrp involved. I'm at stock 10.0.12 ROM, with unlocked bootloader and usb depuration turned on. Should I get the persist.img from the Fastboot image of 10.0.12? I only see the link to an unofficial one which I don't know in which way is different to the official one...
marcushg said:
I don't understand either why is twrp involved..
Click to expand...
Click to collapse
ADB.exe is sending requests to phone. Usual ROM cannot evaluate these requests, while TWRP is specially developed to perform actions specified by ADB requests.
Thanks for the reply. Now what I'm not sure is if flashing persist.img will delete my original IMEI and Bluetooth and WiFi Mac address. I don't want to lose them.
[/COLOR]
marcushg said:
Thanks for the reply. Now what I'm not sure is if flashing persist.img will delete my original IMEI and Bluetooth and WiFi Mac address. I don't want to lose them.
Click to expand...
Click to collapse
This happens to me, camera and sensors are not working. the solution for this is to flash persist.img from original and official rom. you can get that on miui official website. there you can get the persist.img and flash it on TWRP in Mi6X version not the jasmin_sprout. I have try and tested and sensors and camera on my Mi A2 is working now. Blaming myself by deleting the persist! and persist_back up at the twrp. Not to worry by lost imei and etc. mine is all working fine.
how can i do this on android 10? I say that because twrp is not available for android 10. I have problem with frond camera. it return at secondary back camera. please help me
tnt-4- said:
how can i do this on android 10? I say that because twrp is not available for android 10. I have problem with frond camera. it return at secondary back camera. please help me
Click to expand...
Click to collapse
TWRP_4pda_verison works for me in 9 and 10 stock crypted. See link in item 4 of OP instruction.
Aerobatic said:
TWRP_4pda_verison works for me in 9 and 10 stock crypted. See link in item 4 of OP instruction.
Click to expand...
Click to collapse
sorry i am noob. please give me the link
tnt-4- said:
sorry i am noob. please give me the link
Click to expand...
Click to collapse
'OP' in these forums is mostly used in 2 meanings:
- 'OP' refers to the person who Originally Posted this thread;
- 'OP' refers to the Opening Post in this thread.
So, " See link in item 4 of OP instruction" means:
- scroll page up to the beginning (or go to the beginning of 1st page of a thread, here we still have 1 page);
- then read it carefully;
- find item 4:
4. twrp-3.3.1-5-jasmine_sprout-unofficial.img, copied to ADB / Fastboot installation directory
https://forum.xda-developers.com/mi-...prout-t3941096
Click to expand...
Click to collapse
Do I need to go through alphabet or google search course also? no offence, cheer up!
Aerobatic said:
'OP' in these forums is mostly used in 2 meanings:
- 'OP' refers to the person who Originally Posted this thread;
- 'OP' refers to the Opening Post in this thread.
So, " See link in item 4 of OP instruction" means:
- scroll page up to the beginning (or go to the beginning of 1st page of a thread, here we still have 1 page);
- then read it carefully;
- find item 4:
Do I need to go through alphabet or google search course also? no offence, cheer up!
Click to expand...
Click to collapse
thanks for all. i will try to do it beacause the front camera is very usefull.
Persist.img flash via flashed_persist.cmd or flash with twrp??
tnt-4- said:
Persist.img flash via flashed_persist.cmd or flash with twrp??
Click to expand...
Click to collapse
Read OP carefully and try to Google about ADB, TWRP, etc. to understand the process. Why should we do your homework instead of you?
In brief, again and again:
1. TWRP is needed to be booted into phone, as it is the only valid means to perform ADB requests from PC.
2. TWRP has no options to reflash /persist partition from its UI
3. /persist partition image is flashed into phone from PC using ADB commands, so:
3.1. PC is to be prepared (drivers installed, latest platform-tools with ADB unpacked and tested to work, persist.img unpacked and copied into platform-tools directory)
3.2. phone is to be prepared (successfully connected via USB and then booted into TWRP with command from "flash_persist.cmd").
4. "flash_persist.cmd" is just Windows::CMD command file, helping to make ADB / fastboot / ADB requests from PC to phone/TWRP in correct order, and with intermediate checks of successful connection / mode switching: rebooting into bootloader (ADB command), booting into TWRP (fastboot command), and then reflashing /persist (ADB command)
You can read it, e.g. in Notepad, and try to understand what it should make, Googling for Windows::CMD commands and ADB commands descriptions.
Aerobatic said:
Read OP carefully and try to Google about ADB, TWRP, etc. to understand the process. Why should we do your homework instead of you?
In brief, again and again:
1. TWRP is needed to be booted into phone, as it is the only valid means to perform ADB requests from PC.
2. TWRP has no options to reflash /persist partition from its UI
3. /persist partition image is flashed into phone from PC using ADB commands, so:
3.1. PC is to be prepared (drivers installed, latest platform-tools with ADB unpacked and tested to work, persist.img unpacked and copied into platform-tools directory)
3.2. phone is to be prepared (successfully connected via USB and then booted into TWRP with command from "flash_persist.cmd").
4. "flash_persist.cmd" is just Windows::CMD command file, helping to make ADB / fastboot / ADB requests from PC to phone/TWRP in correct order, and with intermediate checks of successful connection / mode switching: rebooting into bootloader (ADB command), booting into TWRP (fastboot command), and then reflashing /persist (ADB command)
You can read it, e.g. in Notepad, and try to understand what it should make, Googling for Windows::CMD commands and ADB commands descriptions.
Click to expand...
Click to collapse
I understand that. I have unlock bootloader and criticals. Then i need run twrp.img on cmd to boot twrp. Then?? Sorry for my questions i am afraid for my phone. I dont want to destroy it with any fault step
tnt-4- said:
I understand that. I have unlock bootloader and criticals. Then i need run twrp.img on cmd to boot twrp. Then?? Sorry for my questions i am afraid for my phone. I dont want to destroy it with any fault step
Click to expand...
Click to collapse
Then read everything I wrote and understand what you are going to do.
Again: read text in "flash_persist.cmd" and make sure you understand each line in it.
At this I stop helping you, I'm to make my work, I'm really busy.
Aerobatic said:
Then read everything I wrote and understand what you are going to do.
Again: read text in "flash_persist.cmd" and make sure you understand each line in it.
At this I stop helping you, I'm to make my work, I'm really busy.
Click to expand...
Click to collapse
i've done it but my front camera still not working. when return it returned at secondary. :crying:
Then i disassembly my phone and disconnect my camera. I open my phone again and did the same thing. Finally i reconnect the camera and it works!! Thanks fo all Aerobatic
Would this work on a V11.0.6.0.QDIMIXM?
Also, where can I find the persist files for it?
valp88 said:
Would this work on a V11.0.6.0.QDIMIXM? Also, where can I find the persist files for it?
Click to expand...
Click to collapse
Yes, it should, if this is really /persist corruption issue, and not HW problem. Diagnostics can be made running tests in engineering mode or with 3rd-party apps like AIDA64: if most or at least several sensors are misbehaving or disfunctional, this is the direct prompt to reflash /persist.
As for your question, It is always recommended to read the OP:
Aerobatic said:
3. image of persist partition, can be found in each stock fastboot image
https://forum.xda-developers.com/mi-a2/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824849
as "jasmine_global_images_V10.0.2.0.PDIMIFJ_9.0\images\persist.img"; must be copied to ADB / Fastboot installation directory.
Click to expand...
Click to collapse
Latest variant of persist.img for A10 can be found in unofficial repack of 11.0.8.0 OTA, link was published in https://forum.xda-developers.com/showpost.php?p=82370929&postcount=42.
Funny fact, but someone wrote in these forums that he solved his problem with corrupted /persist (being on Pie?) using image from the 1st official fastboot image for Oreo (V9.6.9.0.ODIMIFE, link in the thread pointed to in OP and above.)
Will it work with WIfi problems in MIUI for Mi A2
I'm using Custom Rom named as Derpfest and i had also flashed MIUI 11 but my wifi doesn't works in MIUI while it works perfectly for Derpfest.
steps please?
tnt-4- said:
i've done it but my front camera still not working. when return it returned at secondary. :crying:
Then i disassembly my phone and disconnect my camera. I open my phone again and did the same thing. Finally i reconnect the camera and it works!! Thanks fo all Aerobatic
Click to expand...
Click to collapse
Can you describes the steps... yo disassembly and disconnect the camera module, and then? you power it on?
im a XDA pleb im sorry but before i junk my ph-1 which i love to death i want to flash it to something spicy, i got the bootloader unlocked started to get twrp going then thats where it all went bad. 1. im feb 2020 update latest 2. fastboot is kinda working, i see my phone flash the img to slot a not slot b which im on and well says either file size too large or another error i can pull it all up. one error i got through my attempts i seen my bootloader was out of date update for a/b ? but some direction would BE MUCH appreciated !?!? also maybe a suggestion on a rom thats works best thats de-googled?
im even willing to pay a little bit to help me over discord or something, really would like to de-google my ph-1 hit things past my knowledge
TDIfrogman said:
im even willing to pay a little bit to help me over discord or something, really would like to de-google my ph-1 hit things past my knowledge
Click to expand...
Click to collapse
If you like the rom without Google, then there're only two right now far I know: LineageOS and crDroid
To install LineageOS, you don't need TWRP, because LineageOS has its own recovery image, you must follow exactly their instruction for installation.
Here's the link for LineageOS: https://download.lineageos.org/mata
To install crDroid, you need TWRP, at first, you must go back to Jan stock since Feb stock rom has issue with using TWRP.
Also, you need special TWRP image patched that gives you touch otherwise you need USB dongle with mouse to use TWRP. I can give you that TWRP if you need.
Here's the link for crDroid: https://forum.xda-developers.com/t/...microg-volte-wireguard-crdroid-v6-13.4129739/
Good luck!
TDIfrogman said:
im a XDA pleb im sorry but before i junk my ph-1 which i love to death i want to flash it to something spicy, i got the bootloader unlocked started to get twrp going then thats where it all went bad. 1. im feb 2020 update latest 2. fastboot is kinda working, i see my phone flash the img to slot a not slot b which im on and well says either file size too large or another error i can pull it all up. one error i got through my attempts i seen my bootloader was out of date update for a/b ? but some direction would BE MUCH appreciated !?!? also maybe a suggestion on a rom thats works best thats de-googled?
Click to expand...
Click to collapse
You can download that special TWRP image from Telegram channel
Essential Nostalgia Chat
and memes.
t.me
chanh2018 said:
If you like the rom without Google, then there're only two right now far I know: LineageOS and crDroid
To install LineageOS, you don't need TWRP, because LineageOS has its own recovery image, you must follow exactly their instruction for installation.
Here's the link for LineageOS: https://download.lineageos.org/mata
To install crDroid, you need TWRP, at first, you must go back to Jan stock since Feb stock rom has issue with using TWRP.
Also, you need special TWRP image patched that gives you touch otherwise you need USB dongle with mouse to use TWRP. I can give you that TWRP if you need.
Here's the link for crDroid: https://forum.xda-developers.com/t/...microg-volte-wireguard-crdroid-v6-13.4129739/
Good luck!
Click to expand...
Click to collapse
this is what i get after trying to flash recovery
target didn't report max-download-size
sending 'boot' (25741 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.004s
TDIfrogman said:
this is what i get after trying to flash recovery
target didn't report max-download-size
sending 'boot' (25741 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.004s
Click to expand...
Click to collapse
What rom did you try to flash?
chanh2018 said:
What rom did you try to flash?
Click to expand...
Click to collapse
the one on there site you linked , also tried sideloading the .zip and got Signature verification failed , no where to click continue just failed with error 21
TDIfrogman said:
the one on there site you linked , also tried sideloading the .zip and got Signature verification failed , no where to click continue just failed with error 21
Click to expand...
Click to collapse
Ok, here's the steps that I do to install custom rom (not LineageOS):
1. Make sure Essential driver is installed in computer
2. Make sure to use the latest adb package from Essential (or from Android)
3. Make sure your phone is unlocked boot loader
4. Make sure your phone is in Jan stock rom
5. Make sure to turn off finger print log in and password
6. Copy TWRP installer .zip and Rom to phone
7. Boot phone to boot loader and flash boottwrp.img
8. In TWRP, in Wipe, in Advanced Wipe, select Dalvik/ ART Cache, System, Data (DO NOT select Internal Storage), and Swipe to Wipe
9. Now still in TWRP, in Install, install ROM (first), after ROM installation is done, do not reboot, install TWRP installer .zip
10. Reboot phone.
11. DONE
that's the thing i have Feb 2020 on it, how do i go back now ?
TDIfrogman said:
that's the thing i have Feb 2020 on it, how do i go back now ?
Click to expand...
Click to collapse
Download original Jan stock rom
- Unzip it to your computer
- Put phone in boot loader
- From command prompt, goto unzip folder and run flashall.bat
- Sit back and let the batch file running installation process
- When it's done, just reboot, and you'll be back to Jan stock
chanh2018 said:
Download original Jan stock rom
- Unzip it to your computer
- Put phone in boot loader
- From command prompt, goto unzip folder and run flashall.bat
- Sit back and let the batch file running installation process
- When it's done, just reboot, and you'll be back to Jan stock
Click to expand...
Click to collapse
ok so it hangs on first command might be my cable ? im gonna run and go grab a better one and try that switching ports too
TDIfrogman said:
ok so it hangs on first command might be my cable ? im gonna run and go grab a better one and try that switching ports too
Click to expand...
Click to collapse
Make sure your path of adb is working, or quick solution is to copy these 4 files into your unzip folder and run flashall.bat
You can find these 4 files in your adb folder: adb.exe, AdbWinApi.dll, AdbWinUsbApi.dll, fastboot.exe
chanh2018 said:
Make sure your path of adb is working, or quick solution is to copy these 4 files into your unzip folder and run flashall.bat
You can find these 4 files in your adb folder: adb.exe, AdbWinApi.dll, AdbWinUsbApi.dll, fastboot.exe
Click to expand...
Click to collapse
i couldnt find a single cable in town, its not the best cable either no damage just kinda cheap i left my anker at my friends house
im pretty sure my path is ok using the essential drivers and adb/fastboot "platform-tools_r30.0.5-windows" i tried moving those files over same thing hangs at
fastboot flash nvdef_a nvdef
Sending 'nvdef_a' (310 KB)
but i can see it with fastboot devices
TDIfrogman said:
i couldnt find a single cable in town, its not the best cable either no damage just kinda cheap i left my anker at my friends house
im pretty sure my path is ok using the essential drivers and adb/fastboot "platform-tools_r30.0.5-windows" i tried moving those files over same thing hangs at
fastboot flash nvdef_a nvdef
Sending 'nvdef_a' (310 KB)
but i can see it with fastboot devices
Click to expand...
Click to collapse
Did you enable USB debugging in Developer options?
chanh2018 said:
Did you enable USB debugging in Developer options?
Click to expand...
Click to collapse
yes dev options on , usb debug on
- Un plug USB cable from phone
- Goto Setting - About phone - Build number, tap on Build number (don't remember how many, maybe 5 or 7 times) until Developer Options is enable
- Goto System - Developer Options and turn on Android debugging (or USB debugging...I forgot)
- Connect USB cable back to phone, you will see a message popup asking to allow, enable it.
- Now from command prompt, in that unzip folder (assume you already have those 4 files copied), type: adb reboot bootloader
- Let see if your phone can goto bootloader
- If it does, continue to issue command flashall
TDIfrogman said:
yes dev options on , usb debug on
Click to expand...
Click to collapse
Ok, I'm not sure it's the cable or the adb path.
If you're positive about adb path, then your cable is bad.
You can try another version of adb (version 1.4.3)
[OFFICIAL][TOOL][WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3
15 seconds ADB Installer v1.4.3 ADB, Fastboot and Drivers What is this? This is All-in-One installer for 3 most needed PC tools for Android. No need to download big SDK for 3 small things. I originaly made it for my Kurdish friend AnGrY DuDe in...
forum.xda-developers.com
chanh2018 said:
Ok, I'm not sure it's the cable or the adb path.
If you're positive about adb path, then your cable is bad.
You can try another version of adb (version 1.4.3)
[OFFICIAL][TOOL][WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3
15 seconds ADB Installer v1.4.3 ADB, Fastboot and Drivers What is this? This is All-in-One installer for 3 most needed PC tools for Android. No need to download big SDK for 3 small things. I originaly made it for my Kurdish friend AnGrY DuDe in...
forum.xda-developers.com
Click to expand...
Click to collapse
i just uninstalled the essential driver/adb , using the universal everything now and i get this
fastboot flash nvdef_a nvdef
fastboot: error: cannot load 'nvdef': No such file or directory and more , but my phone reboots seems to be adb/driver issue
tried the auto install now it doesnt see my phone at all, found this user same issue but i cant follow what he did to fix it
https://www.reddit.com/r/essential/comments/8vi0nt
TDIfrogman said:
i just uninstalled the essential driver/adb , using the universal everything now and i get this
fastboot flash nvdef_a nvdef
fastboot: error: cannot load 'nvdef': No such file or directory and more , but my phone reboots seems to be adb/driver issue
Click to expand...
Click to collapse
Did you copy those 4 files to unzip rom folder?
If you did, then you can run fastboot or adb within that folder.