I've installed lineage OS and didn't like it, then I downloaded the pixel experience ROM to try it out.
So i went into TWRP, wiped everything, internal storage, cache, dalvik, system, etc. and then flashed the pixel experience ROM, and now it is stuck in the fastboot mode..
It will not boot into the normal OS! And now i've wiped everything again, and then powered off the phone
What should I do? I'm feel panicked now..please help
guyzz6370 said:
I've installed lineage OS and didn't like it, then I downloaded the pixel experience ROM to try it out.
So i went into TWRP, wiped everything, internal storage, cache, dalvik, system, etc. and then flashed the pixel experience ROM, and now it is stuck in the fastboot mode..
It will not boot into the normal OS! And now i've wiped everything again, and then powered off the phone
What should I do? I'm feel panicked now..please help
Click to expand...
Click to collapse
Download AIT Here : https://forum.xda-developers.com/mi-8/development/tool-tool-one-driverstwrpfactory-t3895807
Use it to reinstall TWRP and unencrypted userdata ( only if needed) Then reinstall whatever Rom, Gapps ( if needed) and Root.
You likely missed a step or flashed something such as gapps on the Pixel Rom, and that caused this issue. FYI, as long as you have fastboot there is never a need to worry. Once this is sorted out I would highly recommend that you make a TWRP backup and save it to your PC, to resolve any deeper issues such as sensor problems.
tsongming said:
Download AIT Here : https://forum.xda-developers.com/mi-8/development/tool-tool-one-driverstwrpfactory-t3895807
Use it to reinstall TWRP and unencrypted userdata ( only if needed) Then reinstall whatever Rom, Gapps ( if needed) and Root.
You likely missed a step or flashed something such as gapps on the Pixel Rom, and that caused this issue. FYI, as long as you have fastboot there is never a need to worry. Once this is sorted out I would highly recommend that you make a TWRP backup and save it to your PC, to resolve any deeper issues such as sensor problems.
Click to expand...
Click to collapse
Ok, it happens like this. First I had MIUI, then I installed LOS (which is working) but I didn't like it, so I went and downloaded the PE ROM, and then I just went into TWRP, deleted everything, wipe everything, etc and then I transferred the PE zip file to my phone's internal storage via usb and then I flash it using TWRP. I then went to reboot system, and now it is stuck in the fastboot.
flashed something such as gapps on the Pixel Rom, and that caused this issue
Click to expand...
Click to collapse
I really didn't flash gapps on the PE ROM, because I read that PE had gapps pre-installed, this is something I'm sure I didn't do.
FYI, as long as you have fastboot there is never a need to worry
Click to expand...
Click to collapse
Really thanks for telling me this, I feel relieved already! :laugh:
deeper issues such as sensor problems.
Click to expand...
Click to collapse
really? sensor problems? omg
Use it to reinstall TWRP and unencrypted userdata ( only if needed) Then reinstall whatever Rom, Gapps ( if needed) and Root.
Click to expand...
Click to collapse
okok, how do I use it? which options to click on?
FIXED! Ok, I fixed by downloading the MIUI fastboot ROM located here >> http://en.miui.com/a-234.html
When you download the ROM, you need to extract it, because it comes downloaded as a .tgz, when you extract it becomes a .tar, then you need to extract AGAIN to have the final normal folder, inside this folder you will find all the needed .bat files.
Then you need the Mi flash tool >> api.en.miui.com/url/MiFlashTool
After you download the Mi flash tool, you need to connect your phone via usb and go into fastboot (volume up + power button), then inside the Mi flash tool you need to click on refresh to detect your device.
Once you see your device, you need to go to your final extracted folder and then copy the path of the folder (the location of the folder), by right-clicking the path and click on copy.
You now paste the path onto the mi flash tool, and then click on flash!
When it finishes flashing, it will reboot, but this time into the system! :laugh::laugh::laugh::laugh::laugh:
omg, I'm so happy this is fixed, i thought my mi 8 was gone forever!
Hopefully someone will find this useful in the future!
guyzz6370 said:
FIXED! Ok, I fixed by downloading the MIUI fastboot ROM located here >> http://en.miui.com/a-234.html
When you download the ROM, you need to extract it, because it comes downloaded as a .tgz, when you extract it becomes a .tar, then you need to extract AGAIN to have the final normal folder, inside this folder you will find all the needed .bat files.
Then you need the Mi flash tool >> api.en.miui.com/url/MiFlashTool
After you download the Mi flash tool, you need to connect your phone via usb and go into fastboot (volume up + power button), then inside the Mi flash tool you need to click on refresh to detect your device.
Once you see your device, you need to go to your final extracted folder and then copy the path of the folder (the location of the folder), by right-clicking the path and click on copy.
You now paste the path onto the mi flash tool, and then click on flash!
When it finishes flashing, it will reboot, but this time into the system! :laugh::laugh::laugh::laugh::laugh:
omg, I'm so happy this is fixed, i thought my mi 8 was gone forever!
Hopefully someone will find this useful in the future!
Click to expand...
Click to collapse
Glad you fixed it but you didn't really need to use the flashbat method for this issue. although yes it works.
I have written these exact instructions in the questions and answers section numerous times. You should still download and install AIT, in case you ever need it in the future. Plus, it has other great features such as keeping fastboot tools up to date, systemwide ADB use, as well as the many, many other features.
To help you understand what happened
Somehow, your data became encrypted, badly enough that you could not access your data, system or recovery. This issue has happened to alot of people including myself...many times.
So when I was talking about using AIT to remove encryption, what that basically means is the AIT tool formats the userdata/user storage. After that is resolved, you can, reinstall TWRP, and be back to being able to use custom roms again.
Now that you are restored,
Boot to TWRP and make a complete backup up of your installation, checking everybox.
Next connect to your PC and copy the backup from storage/Twrp/Backups, over to your PC.
Never delete this backup. If you have an issue in the future, such as Wifi, BT, or cellular not connecting, or if you have a Wifi mac address of 02:00:00:00:00 you can use the Recovery to restore your partitions, notably the persist partition.
Restoring your backup will fully resolve those kinds of issues, even when flashbat will not.
Enjoy
This issue has happened to alot of people including myself...many times.
Click to expand...
Click to collapse
I'm interested to read about this too, can you link me to some threads of other people having the same issue?
Now that you are restored,
Boot to TWRP and make a complete backup up of your installation, checking everybox.
Next connect to your PC and copy the backup from storage/Twrp/Backups, over to your PC.
Never delete this backup. If you have an issue in the future, such as Wifi, BT, or cellular not connecting, or if you have a Wifi mac address of 02:00:00:00:00 you can use the Recovery to restore your partitions, notably the persist partition.
Click to expand...
Click to collapse
Yeah, time to make a backup! A working one!
guyzz6370 said:
I'm interested to read about this too, can you link me to some threads of other people having the same issue?
Yeah, time to make a backup! A working one!
Click to expand...
Click to collapse
Sure this post has an issue that I also ended up having myself :
https://forum.xda-developers.com/mi-8/help/xiaomi-mi-8-wifi-issue-help-t3941288
Read through the post, everything that I recommended usually works ...most of the time. However, I recently had the exact issue where nothing worked including using Fastboot FlashAll.bat , and I tried several versions of stock and kept having persist issues, which caused my Wifi and mobile to not work. Note, the solution here is using your backup ( Using someone else's, apparently does not always work)
What finally resolved my issue was restoring my own recovery backups which fortunately I had previously made one with the Xiaomi EU version of the backup and it finally solved the issue.
For the record, booting the phone into EDL mode and using the QPST program to restore the factory rom should also work. Plus, QPST has a built in tool that is specific to repairing the Radio, IMEI, Mac Address Etc. Needless to say, restoring your TWRP backup is much much easier and much less stressful than doing trial and error with QPST.
See the screenshots ( attached) One backup made with official TWRP makes a highly compressed version of the backup. I would also suggest making a backup of with the linked version of TWRP from the Xiaomi.EU website, this version decompresses some of the driver images allow you to restore individual files such as individual persist images
TWRP-3.3.1-0607-XIAOMI8-CN-wzsx150 .zip ( Two Languages, Chinese and English)
https://mega.nz/#!QstBnAaD!V6riZpEjctWhzWhoFcDDEv0wRlFESfcEsxAHpdaerxE
tsongming said:
Sure this post has an issue that I also ended up having myself :
https://forum.xda-developers.com/mi-8/help/xiaomi-mi-8-wifi-issue-help-t3941288
Read through the post, everything that I recommended usually works ...most of the time. However, I recently had the exact issue where nothing worked including using Fastboot FlashAll.bat , and I tried several versions of stock and kept having persist issues, which caused my Wifi and mobile to not work. Note, the solution here is using your backup ( Using someone else's, apparently does not always work)
What finally resolved my issue was restoring my own recovery backups which fortunately I had previously made one with the Xiaomi EU version of the backup and it finally solved the issue.
For the record, booting the phone into EDL mode and using the QPST program to restore the factory rom should also work. Plus, QPST has a built in tool that is specific to repairing the Radio, IMEI, Mac Address Etc. Needless to say, restoring your TWRP backup is much much easier and much less stressful than doing trial and error with QPST.
See the screenshots ( attached) One backup made with official TWRP makes a highly compressed version of the backup. I would also suggest making a backup of with the linked version of TWRP from the Xiaomi.EU website, this version decompresses some of the driver images allow you to restore individual files such as individual persist images
TWRP-3.3.1-0607-XIAOMI8-CN-wzsx150 .zip ( Two Languages, Chinese and English)
https://mega.nz/#!QstBnAaD!V6riZpEjctWhzWhoFcDDEv0wRlFESfcEsxAHpdaerxE
Click to expand...
Click to collapse
Well well, it seems that there are some scary stuff that can happen to your device that thank God I personally don't have to deal with :laugh:
I was already scared sh**less when I started this post, and luckily for me my device is fine now running the PE ROM (so smooth and beautiful) and never encountered any radio/sensor issues..
So from what I can gather...always make a TWRP back up of your device so if anything stupid happens in the future (I think it's unlikely, but just to be safe...) you can easily restore and your device is safe again..so yeah thank God I don't have to deal with more complex issues :fingers-crossed:
And thanks for answering, it very comforting to know that there are people like you who answer on these forums whenever urgent help is needed...so thanks for that!:good::good:
guyzz6370 said:
Well well, it seems that there are some scary stuff that can happen to your device that thank God I personally don't have to deal with :laugh:
I was already scared sh**less when I started this post, and luckily for me my device is fine now running the PE ROM (so smooth and beautiful) and never encountered any radio/sensor issues..
So from what I can gather...always make a TWRP back up of your device so if anything stupid happens in the future (I think it's unlikely, but just to be safe...) you can easily restore and your device is safe again..so yeah thank God I don't have to deal with more complex issues :fingers-crossed:
And thanks for answering, it very comforting to know that there are people like you who answer on these forums whenever urgent help is needed...so thanks for that!:good::good:
Click to expand...
Click to collapse
Yes, exactly and although its somewhat rare it happened to me for no real reason, suddenly the phone froze and would not boot again. To be fair I was trying out an untested version of TWRP. However I was not experiencing any issues for weeks, until I installed Swift themer, similar to Substratum. Though I am not sure that it was related to the issue.
Bottom line, make the TWRP backup ASAP, it will literally take you no more than 15 minutes to make it and back it up to your PC. This way you never ever have to worry about unpredictable issues., pass it on to any friends or relatives to do the same.
Enjoy your awesome phone, Cheers.
tsongming said:
Yes, exactly and although its somewhat rare it happened to me for no real reason, suddenly the phone froze and would not boot again. To be fair I was trying out an untested version of TWRP. However I was not experiencing any issues for weeks, until I installed Swift themer, similar to Substratum. Though I am not sure that it was related to the issue.
Bottom line, make the TWRP backup ASAP, it will literally take you no more than 15 minutes to make it and back it up to your PC. This way you never ever have to worry about unpredictable issues., pass it on to any friends or relatives to do the same.
Enjoy your awesome phone, Cheers.
Click to expand...
Click to collapse
So I tried restoring from the backup and...wasn't what I expected..I expected it to be 100% exact. I thought it will be as if I restarted my phone and when I turn on the phone again, it will be like nothing ever happened..
but the restore feature isn't perfect
Firstly, when I checked all the partitions to restore, it gave me the 255 error..so what ended up working for me was to uncheck the recovery,cache, and data partitions..this restored the device and the device booted (it wasn't booting before this, it will show the mi logo and shut off).
After booting up, I still needed to set up my phone..
But other than that...it does seem to save some of phone's settings
certain settings, wallpapers, status bar icons, home screen icons..these things seem to have been saved..but everything else is still starting from fresh..
What gives? I thought it was supposed to behave as if I restarted my phone and nothing happened...
guyzz6370 said:
So I tried restoring from the backup and...wasn't what I expected..I expected it to be 100% exact. I thought it will be as if I restarted my phone and when I turn on the phone again, it will be like nothing ever happened..
but the restore feature isn't perfect
Firstly, when I checked all the partitions to restore, it gave me the 255 error..so what ended up working for me was to uncheck the recovery,cache, and data partitions..this restored the device and the device booted (it wasn't booting before this, it will show the mi logo and shut off).
After booting up, I still needed to set up my phone..
But other than that...it does seem to save some of phone's settings
certain settings, wallpapers, status bar icons, home screen icons..these things seem to have been saved..but everything else is still starting from fresh..
What gives? I thought it was supposed to behave as if I restarted my phone and nothing happened...
Click to expand...
Click to collapse
What? It seems that you missed the point of what I was suggesting.
Why would you assume that the restore would restore everything and it would be like nothing happened, where did I say that? Restoring the back would definitely be like nothing happened to your missing partitions.
I never said anything about fully restoring your phone although that is indeed completely possible if done right, and you restore the system base and files in storage that were present when you made the backup.
The only thing that I was talking about is when/ if you eventually experience a unsolvable persist issue. If you flash a lot of different roms, frequently it is a problem that you may eventually experience for yourself. Google Xiaomi persist issue. A lot of people had that issue about a month ago.
So again, the point is to have a quick fix on hand, that you can restore, drivers and crucial partitions without having to use EDL mode.
The full backup does not include your files, or settings and that message appears within TWRP when you make the back up.
Some devices including Xiaomi have "special partitions" like WiMAX, pds, efs, etc. These partitions almost never need to be included in a normal backup. However, it's usually a good idea to make a single backup of these partitions and hang on to them just in case.
tsongming said:
What? It seems that you missed the point of what I was suggesting.
Why would you assume that the restore would restore everything and it would be like nothing happened, where did I say that? Restoring the back would definitely be like nothing happened to your missing partitions.
I never said anything about fully restoring your phone although that is indeed completely possible if done right, and you restore the system base and files in storage that were present when you made the backup.
The only thing that I was talking about is when/ if you eventually experience a unsolvable persist issue. If you flash a lot of different roms, frequently it is a problem that you may eventually experience for yourself. Google Xiaomi persist issue. A lot of people had that issue about a month ago.
So again, the point is to have a quick fix on hand, that you can restore, drivers and crucial partitions without having to use EDL mode.
The full backup does not include your files, or settings and that message appears within TWRP when you make the back up.
Some devices including Xiaomi have "special partitions" like WiMAX, pds, efs, etc. These partitions almost never need to be included in a normal backup. However, it's usually a good idea to make a single backup of these partitions and hang on to them just in case.
Click to expand...
Click to collapse
oh.. because i thought it would be perfect like nothing happened ? that's the whole point of backing up right?
I expected to be like a normal hard disk on your computer..on a hard disk i can just make a clone of the disk and clone it to a new hard disk, and the computer starts like nothing happened...
so i assumed it was the same for a phone too, but apparently not ?
guyzz6370 said:
oh.. because i thought it would be perfect like nothing happened ? that's the whole point of backing up right?
I expected to be like a normal hard disk on your computer..on a hard disk i can just make a clone of the disk and clone it to a new hard disk, and the computer starts like nothing happened...
so i assumed it was the same for a phone too, but apparently not ?
Click to expand...
Click to collapse
Miui local backup works something like that. Titanium backup used to be awesome for that kind of restore, but on pie roms it's kind of buggy
If using an Aosp rom, there is a program called migrate that can restore apps but the user data part hasn't always worked for me.
TWRP full restore, along with manually restoring storage media from the desktop will be close to using a restore point from a PC or restoring a time machine backup on a mac but still not the same.
Now you have the backup so your phone is safe from weird future issues. If that ever happen message me and I will help you .
Sent from my Xiaomi MI 8 using XDA Labs
Related
hello, i recently bought used droid 4, found it to be with some leftover data (sms, and such) so first thing i did was a factory reset only to
find it after a while in extact same state. weird thing is that when i factory reset it after removing some apps or changing anything at all it acts
as if i restored some backup instead of wiping device. it spams me with errors every few seconds too which is quite troublesome to say the least.
i searched the internet for an answer (still looking) to this problem but so far got nothing. i mean there are lots of ppl with similiar issue
but no real answer anywhere i looked. i thought maybe flashing some stock rom (dont wanna try anything custom yet since i got lapdock
too and havent checked if webtop works with custom roms yet). is it the right direction in my case or is there some simplier answer to my problem?
thanks in advance
update: cant root it, cant install official update through rsdlite, cant update through other unofficial ways,
it acts as if everything went fine and each time im back to square 1. it aint my first or second journey with rooting,
changing rom but im not really sure what else can i do. also rsdlite cant detect any information about device (imei,
os version, flex drm boot etc are all filled with N/A
install from sdcard also failed - signature verification failed. keeps gettin better. downloading another rom from
official moto website... not expecting anything though
wyklocnik said:
hello, i recently bought used droid 4, found it to be with some leftover data (sms, and such) so first thing i did was a factory reset only to
find it after a while in extact same state. weird thing is that when i factory reset it after removing some apps or changing anything at all it acts
as if i restored some backup instead of wiping device. it spams me with errors every few seconds too which is quite troublesome to say the least.
i searched the internet for an answer (still looking) to this problem but so far got nothing. i mean there are lots of ppl with similiar issue
but no real answer anywhere i looked. i thought maybe flashing some stock rom (dont wanna try anything custom yet since i got lapdock
too and havent checked if webtop works with custom roms yet). is it the right direction in my case or is there some simplier answer to my problem?
thanks in advance
Click to expand...
Click to collapse
uncheck restore data Hard Reset - DROID 4 by MOTOROLA - Verizon Wireless Support
update: cant root it, cant install official update through rsdlite,
Click to expand...
Click to collapse
updates.zips are not installed with rsdlite, XML/firmware is install with rsd lite, but adroid version can not be downgraded
cant update through other unofficial ways,
it acts as if everything went fine and each time im back to square 1. it aint my first or second journey with rooting,
changing rom but im not really sure what else can i do. also rsdlite cant detect any information about device (imei,
os version, flex drm boot etc are all filled with N/A
install from sdcard also failed - signature verification failed. keeps gettin better. downloading another rom from
official moto website... not expecting anything though
Click to expand...
Click to collapse
what official site? use files from my page How to Use RSD Lite to flash a .XML Stock Rom (firmware)
thanks for taking interest
tried factory reset with options You mentioned unchecked, same thing as before.
i did use xml with rsdlite and zip through built in recovery.
tried to find this page i downloaded files but theres too much in yesterdays history, trying those from Your link now.
also tried to update rom ota, but of course theres an error. oh my droid runs 4.0.4, i havent mentioned it before.
also, found in the net schematics for factory cable, was thinking if its worth a shot this way:
http://www.droidforums.net/forum/droid-labs/146492-how-why-make-your-own-motorola-factory-cable-4.html
Factory cable only allows you to power device with low battery/no battery
Sent from my Amazon OtterX using Tapatalk
---------- Post added at 10:33 AM ---------- Previous post was at 10:31 AM ----------
Update zips only update specific system versions, you have to use correct one, and must be complete stock.
Sent from my Amazon OtterX using Tapatalk
from what i read in this post about factory cable it says it boots phone different way than normal thats why i thought maybe
itll be able to successfully update with it. also after every reset of this droid its not a simple matter of apps coming back thru wifi.
wifi is disabled and theyre there right from the start. i can remove some widgets or apps from home screen, i can delete texts,
and after reset theyre all back where they were. its as if every change i made havent been saved. i dont even have to reset phone,
i just need to reboot it to have it all back
phone needs to be in AP Fastboot mode when flashing with rsd lite.
verify md5 checksum for xml file before flashing.
yes, it was in ap fatboot mode, didnt verify the md5 tho.
more importantly, file i downloaded from site You linked passed verification! guess what i found wasnt official updates after all...
i hope this works
wyklocnik said:
from what i read in this post about factory cable it says it boots phone different way than normal thats why i thought maybe
Click to expand...
Click to collapse
Factory/Fastboot cable only uses the alt power (4) pin to power device, there are several pre-made ones
itll be able to successfully update with it. also after every reset of this droid its not a simple matter of apps coming back thru wifi.
wifi is disabled and theyre there right from the start. i can remove some widgets or apps from home screen, i can delete texts,
and after reset theyre all back where they were. its as if every change i made havent been saved. i dont even have to reset phone,
i just need to reboot it to have it all back
Click to expand...
Click to collapse
try reformatting internal sd card, before wiping
---------- Post added at 10:58 AM ---------- Previous post was at 10:53 AM ----------
wyklocnik said:
yes, it was in ap fatboot mode, didnt verify the md5 tho.
more importantly, file i downloaded from site You linked passed verification! guess what i found wasnt official updates after all...
i hope this works
Click to expand...
Click to collapse
there are no official moto download sites, all moto firmware is pulled by people with special access, and reuploaded
try reformatting internal sd card, before wiping
Click to expand...
Click to collapse
is it any different than checking "erase internal storage" when reseting phone?
anyways did it but atm have to recharge battery before trying to wipe it again.
also rom was succesfully updated thru recovery with no errors and after reboot im... back to square 1...
wyklocnik said:
is it any different than checking "erase internal storage" when reseting phone?
Click to expand...
Click to collapse
formatting is different than wiping data, in menu>settings>storage>unmount>format
anyways did it but atm have to recharge battery before trying to wipe it again.
also rom was succesfully updated thru recovery with no errors and after reboot im... back to square 1...
Click to expand...
Click to collapse
did system version change?
same story after formating internal memory.
no changes whatsoever. same homescreen, same widgets/apps present. same system version.
and of course new error every 5 seconds. guess the phone is messed up good.
talk about luck. its second droid 4 i bought. first i bought over a month ago on auction site, it was new. i paid, guy never sent it.
now this one. its like a curse
formatting internal won't wipe, user data, but will wipe backup data.
tried xml with rsdlite now.
after first reboot its supposed to go into the recovery mode right?
it went back in to ap fastboot... and after rsd transfered all the files then it went to bootloader... and now program says reboot is in process while phone sits in recovery mode...
wyklocnik said:
tried xml with rsdlite now.
after first reboot its supposed to go into the recovery mode right?
Click to expand...
Click to collapse
it happens sometimes
it went back in to ap fastboot... and after rsd transfered all the files then it went to bootloader... and now program says reboot is in process while phone sits in recovery mode...
Click to expand...
Click to collapse
select wipe data, then select reboot
done, nothing changed.
also, when rsd works it acts as if it doesnt wait for the phone with operations.
it writes reboot, phone starts to reboot, and long time before it boots back either in ap fastboot mode or into recovery
rsd says its already transfering files, it says reboot again (before phone even gets into fastboot or recovery after 1st reboot) and so on.
wyklocnik said:
done, nothing changed.
also, when rsd works it acts as if it doesnt wait for the phone with operations.
it writes reboot, phone starts to reboot, and long time before it boots back either in ap fastboot mode or into recovery
rsd says its already transfering files, it says reboot again (before phone even gets into fastboot or recovery after 1st reboot) and so on.
Click to expand...
Click to collapse
which fastboot version? 0A.74 , 0A.77?
which xml file?
0A.74
cdma_maserati_9.8.2O-72_VZW-18-2_1ff.xml
looks like you have a failure to write data, don't think there is a fix.
could try my Unbrick Moto device with moto-fastboot.exe
but unlikely that it will work
Hi a friend of mine has a Nexus 6 but for some reason it wont get past the google screen, it would just turn off again, and if it is plugged it will just go to the Battery Icon and then off again.
He has tried everything, even flashall.bat to add new stock rom, tried pushing TWRP recovery etc, etc.
Is there a way he can extract EFS folder to see if by any chance that or something else is corrupt?
Thanks! I know XDA Peeps have helped me a lot before and I tried almost everything with him with no avail
He wants to extract the EFS, just in case trying to flash more things or something might break it, he just wants to have a backup just in case.
ZeroHart said:
Hi a friend of mine has a Nexus 6 but for some reason it wont get past the google screen, it would just turn off again, and if it is plugged it will just go to the Battery Icon and then off again.
He has tried everything, even flashall.bat to add new stock rom, tried pushing TWRP recovery etc, etc.
Is there a way he can extract EFS folder to see if by any chance that or something else is corrupt?
Thanks! I know XDA Peeps have helped me a lot before and I tried almost everything with him with no avail
He wants to extract the EFS, just in case trying to flash more things or something might break it, he just wants to have a backup just in case.
Click to expand...
Click to collapse
If he can go into bootloader mode he can flash the stock rom manualy, look here http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008, method 2.
ZeroHart said:
Hi a friend of mine has a Nexus 6 but for some reason it wont get past the google screen, it would just turn off again, and if it is plugged it will just go to the Battery Icon and then off again.
He has tried everything, even flashall.bat to add new stock rom, tried pushing TWRP recovery etc, etc.
Is there a way he can extract EFS folder to see if by any chance that or something else is corrupt?
Thanks! I know XDA Peeps have helped me a lot before and I tried almost everything with him with no avail
He wants to extract the EFS, just in case trying to flash more things or something might break it, he just wants to have a backup just in case.
Click to expand...
Click to collapse
Since you want to backup the efs here is my best advice:
Normally you can backup the efs via custom recovery(thats out) or through adb. I don't know the details of adb, nor how one might backup efs in fastboot. I looked through the files in roots I believe the efs partitions are in /dev/block/platform/msm_sdcc.1/by-name/ and the files are probably mdm1m9kefs1 mdm1m9kefs2 mdm1m9kefs3 and mdm1m9kefsc Now this is my best guess and I'm not sure if you can just copy them in adb to save on your comp or wherever, and well you would need to look up some adb commands... But that's all I can say.
What you can do in fastboot is really limited. adb via custom recovery would be the only way really.
I haven't seen any instances of this phone with a corrupted efs yet
Too bad, he tried flashing stock but did not work, not by doing flash all nor by doing one by one, also tried flashing recovery, but when he selects fastboot boot recovery the phone will just turn off again.
He says he is tied and will send it back to t mobile, hopefully they fix it or send him a new one
ZeroHart said:
Too bad, he tried flashing stock but did not work, not by doing flash all nor by doing one by one, also tried flashing recovery, but when he selects fastboot boot recovery the phone will just turn off again.
He says he is tied and will send it back to t mobile, hopefully they fix it or send him a new one
Click to expand...
Click to collapse
Did they flash o.k.?. But won't boot to os. Because I have similar issues. I had it working o.k. was on bliss rom. Then when I woke up phone was on Google logo and won't go any further. I tried flashing the images. They flash only manually. But won't let me go to recovery or the os. Any advice what could went wrong with device.
Nochis said:
Did they flash o.k.?. But won't boot to os. Because I have similar issues. I had it working o.k. was on bliss rom. Then when I woke up phone was on Google logo and won't go any further. I tried flashing the images. They flash only manually. But won't let me go to recovery or the os. Any advice what could went wrong with device.
Click to expand...
Click to collapse
That is exactly what happened to him, everything flashes but it wont get to recovery or OS, if it is plugged it will just show the google screen then battery and that is it
ZeroHart said:
That is exactly what happened to him, everything flashes but it wont get to recovery or OS, if it is plugged it will just show the google screen then battery and that is it
Click to expand...
Click to collapse
What rom he was before this happen?.
Stock Rooted
ZeroHart said:
Stock Rooted
Click to expand...
Click to collapse
So it may be a hardware issue. My guess is something went wrong with the device.
Yesterday I was using my phone and it suddenly started rebooting itself. Since my bootloader was locked, my phone was stock rom, no root, no custom recovery and usb debugging off my hopes of doing something through ADB or Fastboot vanished. I think it is fixable but I would like to recover all my data first. I heard that you can try to get your phone into EDL mode in order to recover your data, so I tried to via test point method and my phone is now recognized as Qualcomm 9008. However, afaik this mode wont let me recover any data, and I need to get it to be 9006 instead of 9008. Any help?
Proceed at your risk.
The test point method http://en.miui.com/thread-693884-1-1.html it is using Mi flash tools to flash the ROM so you can opt out for save user data in order to keep internal storage.
in that thread it is mentioned to clean flash but there is one step given to save user data so i don't know what things will be saved and what not. most possibly itll wipe app and its data so messages,call logs,contact will get wiped if there are in internal storage if they haven't backed up to the cloud.
do read carefully and then proceed.
metelhammer said:
Proceed at your risk.
The test point method it is using Mi flash tools to flash the ROM so you can opt out for save user data in order to keep internal storage.
in that thread it is mentioned to clean flash but there is one step given to save user data so i don't know what things will be saved and what not. most possibly itll wipe app and its data so messages,call logs,contact will get wiped if there are in internal storage if they haven't backed up to the cloud.
do read carefully and then proceed.
Click to expand...
Click to collapse
I guess I´ll try that then, I already saw this ''Wipe everything but userdata'' option but was not sure, as it seems a bit strange. I'll give it a shot, thanks!
Lolo147 said:
I guess I´ll try that then, I already saw this ''Wipe everything but userdata'' option but was not sure, as it seems a bit strange. I'll give it a shot, thanks!
Click to expand...
Click to collapse
Your welcome, hope to see that work.
metelhammer said:
Your welcome, hope to see that work.
Click to expand...
Click to collapse
So I tried this and, after dealing with many versions of Mi Flash (newer ones crashed, older ones had many errors) I was finally able to flash a fastboot rom but unfortunately I'm still stuck in the bootloop. I guess wiping data is an unavoidable fate. Thanks again 4 everything
1.Install twrp.(if you dont have)
2.Turn off phone and click power volup+voldown and when phone turns on release power btn. Recovery will appear wipe data,cache,dalvik,system,vendor then install any rom (i recommend pixelexperience or miui stable). Then wait if there an bootloop i cant help bye.
I thought I had finally reached nirvana with this device thanks to the help of so many here. I had TWRP, root, defeated encryption, and a nicely running Android. I was even able to make TWRP backups of /data and /boot (to be precise, at one point - not sure when it was but I think after initial Android setup - I was able to make a much more complete TWRP backup with many partitions never shown again but that disappeared at some point).
So I went on with my transition from my old Note3 phone to this device. I spent all day yesterday moving TiBackups of user apps, copying across data, making more limited TWRP backups (of data and boot the only options - except if I mounted system_root, which allowed me to include /system but that did not actually work either), polishing settings, and thinking I had it made! Throughout all of this I had no problems or signs of problems other than some apps not working on the new device and having to be replaced with alternatives which I completely expected.
At cocktail hour I decided to do a reboot to see the "finished product" of all this effort. When I did, the device tried to boot into Android: I saw the thinq logo but no boot animation, just the thinq logo for a very long time - followed by a screen blank and bootloop. I was able to enter TWRP and things looked "normal" from there. I kept trying to boot into system with no progress. I tried wiping /data, I tried restoring the backups I had made. Nothing changed - still bootlooping.
From within TWRP I can use adb shell to look around. I can see familiar stuff from my installed apps in /data/data and /data/app - including from one of the very last apps I installed (from Play not via TiBackup). I know this was not in any TWRP backup I had taken or restored. So this makes me think that my attempts to restore /data from backups or even wiping /data from TWRP have had no effect despite no errors showing. I wanted to see what was in /system so I mounted system and now in adb shell I can see familiar stuff in there too - including busybox installed into xbin. I can also mount vendor and in /vendor/etc I can see the fstab.judypn with encryptable for /data.
One thing I do NOT see is the result of one of the last things I did/tested. I installed Termux, installed the dropbear package, and copied the resulting dbclient binary to /data/local. After doing this I actually invoked /data/local/dbclient with success. Now, I do not see anything in /data/data/com.termux/files/usr related to dropbear nor do I see the dbclient in /data/local.
When I tried to power off from TWRP, the device never fully turned off. The animation showing the power level remained showing all the time but it was just a circle with lightening bolt but no actual power level showing. Removing power cable made no difference. Finally, I left the device in TWRP and powered on. At least I could blank the screen and prevent the battery from running dry.
All of this is with slot A current as reported by TWRP. I cannot seem to enter fastboot mode (I was previously able to do this from a power off condition by holding volume up and inserting USB). Of course, I am not able to achieve a real powered-off condition. Thankfully, I am still able to enter engineering mode and see the device in QFIL. But I have not tried anything here as of now. I can switch to slot b and get into download mode by holding power up and inserting USB. All attempts to use other TWRP boot options (save recovery and "power off") just put me into bootloop again.
I am stumped as to what is happening, how to "fix" this, or what to do.
Thanks for any suggestions.
Same thing happened to me. Yesterday.
I was going through my system programs, and nuked several of the extra Google Play items (Movies, Music, etc.). Same thing. Boot to V40 ThinkQ screen. Sat there for a while. Then reboot.
Nothing I did brought the old girl back to life. So I started over with kdz and redid everything again. Pain in the ass, but it's working again. Interestingly enough, loading the full kdz didn't relock the bootloader. I used both Refurbish and Partition DL on two separate attempts. Bootloader stayed unlocked throughout, and is still unlocked.
Had a devil of a time getting system to mount. Tried over and over again to get Magisk installed.
What finally worked was rebooting into recovery after pushing the .magisk file, and only then installing Magisk.
[NG]Owner
NGOwner said:
Same thing happened to me. Yesterday.
I was going through my system programs, and nuked several of the extra Google Play items (Movies, Music, etc.). Same thing. Boot to V40 ThinkQ screen. Sat there for a while. Then reboot.
Nothing I did brought the old girl back to life. So I started over with kdz and redid everything again. Pain in the ass, but it's working again. Interestingly enough, loading the full kdz didn't relock the bootloader. I used both Refurbish and Partition DL on two separate attempts. Bootloader stayed unlocked throughout, and is still unlocked.
Had a devil of a time getting system to mount. Tried over and over again to get Magisk installed.
What finally worked was rebooting into recovery after pushing the .magisk file, and only then installing Magisk.
[NG]Owner
Click to expand...
Click to collapse
Well, they say misery loves company and I do feel a bit better just knowing I am not alone here.
Since I could enter download mode, I too decided to try re-flashing the .kdz using LGUP's partition dl and specifically NOT checking boot_a, laf_a or boot_b as described here <https://forum.xda-developers.com/showpost.php?p=82206107&postcount=115>. I was not fast enough to get into TWRP on the automatic reboot and saw that I was brought to a bootable system and an Android start page with the boot loader still locked and TWRP still there.
So did the partition dl again and managed to catch TWRP. I mounted vendor but when I tried to push the fstab I got something I have not seen before "remote could not create file: Read-only file system" and 0 files pushed. To be sure, I used adb shell and cat'ed /vendor/etc/fstab.judypn and it contains force encrypt. So I know things are not quite right.
Trying again from the partition dl. And this time I managed the push. I think I missed re-doing the ramdisk and rebooting into recovery. I made sure to do that this time and now I can proceed. I seem to have managed to get back to a bootable Android with TWRP, Magisk, and defeated encryption once again.
So I wonder if I should try to restore anything from a backup or just redo all of yesterday's efforts (like the movie Groundhog Day)?
Can I ask which device and firmware you are using? Thanks
I would not use any backups aside from the backups in your google account. Redo all of yesterday's efforts (except the one thing that caused the reboot loop ... whatever that was!).
You said your bootloader was relocked after LGUP? Or did you mistype there?
Odd. Mine wasn't, not once. Despite multiple LGUP loads.
I've got a crossflashed Sprint LM-V405UA to US specs 20E.
And yes, misery does love company!
[NG]Owner
NGOwner said:
I would not use any backups aside from the backups in your google account. Redo all of yesterday's efforts (except the one thing that caused the reboot loop ... whatever that was!).
You said your bootloader was relocked after LGUP? Or did you mistype there?
Odd. Mine wasn't, not once. Despite multiple LGUP loads.
I've got a crossflashed Sprint LM-V405UA to US specs 20E.
And yes, misery does love company!
[NG]Owner
Click to expand...
Click to collapse
No, you are correct - I mistyped. My bootloader has remained unlocked (this time I got it right)
Nor sure it matters any, but mine if a 405QA with 20E.
I have read some recently (while searching for this bootloop problem) that LG seems to have long had a problem with bootloops on their devices. Not sure I saw anything specifically about the V40 though. Seems that in the past they were "fixed" with software updates. I do not expect any updates beyond 20E and wonder if 20a (which I think I had earlier) would be any different/better.
I have had great luck with Nandroid and TWRP backups in the past. They have really saved me (most often from myself but also from apps/mods gone wild). Indeed, I used TWRP restore yesterday with the previous night's auto-made backup on my Note 3. It seems that in doing something - maybe the TiBackup of all user apps/data - the phone got messed up and even reboots would not fix it. The TWRP restore certainly did!
I am new to the whole Magisk "systemless" root as I have always used SuperSu before. As I understand it (which is limited for sure) the idea here is to NOT modify system in any way. But I also note that this does not seem to preclude me from modifying things in system using my file manager, for example. And I did some of this sort of thing. If you are nuking pre-installed apps, that would be changing system as well, no? I wonder if that is the activity that caused this?
I am a bit hesitant to re-live yesterday. At least not until I have some idea of what I did that caused this. Not sure what I will do.
Thanks for all the help.
PS - given that I had TWRP backup (of at least /data) and how often I rely upon these in everyday life, I decided to at least try restoring and see what happened. Hard to imagine ending up worse that I was earlier this morning. I did the restore and rebooted to system. I was shocked, quite frankly, to see the system come right up and have many of my previously installed apps visible and working. I did find that I had to re-enable the modules in EdXposed (even though they showed as enabled already) since they were not working) and that brought them back to life.
So I guess I can move forward from here being careful, taking TWRP backups even more often, and rebooting more often to see what, if anything, kills this again.
NGOwner said:
Same thing happened to me. Yesterday.
I was going through my system programs, and nuked several of the extra Google Play items (Movies, Music, etc.). Same thing. Boot to V40 ThinkQ screen. Sat there for a while. Then reboot.
Nothing I did brought the old girl back to life. So I started over with kdz and redid everything again. Pain in the ass, but it's working again. Interestingly enough, loading the full kdz didn't relock the bootloader. I used both Refurbish and Partition DL on two separate attempts. Bootloader stayed unlocked throughout, and is still unlocked.
Had a devil of a time getting system to mount. Tried over and over again to get Magisk installed.
What finally worked was rebooting into recovery after pushing the .magisk file, and only then installing Magisk.
[NG]Owner
Click to expand...
Click to collapse
Well, this happened to me once again. I saw no reason why it should not do so. So I have been re-introducing apps from my TiBackup slowly and in under a strict protocol in an effort to (a) limit the damage done to my work and (b) try to isolate the culprit(s). I decided, since I found that I could restore TWRP backups of /data after re-doing the most of the TWRP install and defeat encryption process, that I would install apps slowly and execute them and in small groups. After each group I would do a reboot to see if that worked. If that worked, I would go into TWRP, run a backup, and name the backup of /data with something to id the app group that was added and seemed fine.
I started working backwards by the first letter of the app name. I first did U-Z and found that worked fine. Took a backup and went on to S-T. After this group it was bootloop time! So I put humpty-dumpty back together, restored the /data backup from U-Z, and this time installed only those apps starting with T. After this a no-problem reboot and a backup of /data and I will continue to plod on with those apps starting with S (and so on).
Horribly tedious. I can see no other way to proceed unless someone has a better idea.
PS - So I re-installed apps starting with S and basically had no problems. Hmmm. But I do recall that when testing execution of some of these apps the first time around, I decided to install busybox (Stericson), AdAway, and Afwall+ out of sequence. Before I did this I decided to check a bit more. I found that there is a Magisk busybox module and even though I have always used Stericson without troubles, I thought it best to use the Magisk module for this. I also found that Magisk has a setting for systemless hosts which could be affected by AdAway. So I enabled that before doing anything with AdAway. I also checked to see if AfWall+ might have any issues and found none. So I guess it is possible that using Stericson busybox or failing to use systemless hosts could have been an issue. I may never know for sure but at least so far I am fine after installing apps that I previously installed and had a bootloop. So FYI.
Alright, I'm a total idiot. I went and did this again, following the mantra: If it aint broke, you're not trying hard enough.
Setting all that aside, I went and tried to do some more debloating of my v40 (used this guide, that I was linked to from here), and wound up in "this fresh hell" again. Dammit! Crap.
So apparently there is a system application that is crucial to the boot of the phone that I uninstalled.
There is a fix to this, but it comes at a cost. Get into TWRP. Navigate to advanced, select Fix Recovery Reboot. Your phone will boot normally now. But you will lose root. And (so far) any attempt to reinstall Magisk to re-obtain root will result in the same bootloop again.
So here's where I need some help:
1) So if I wanted to reinstall my system partition to get back to stock from a KDZ, but still keep my installed apps, etc., how do I do that?
2) How do I get my Slot B to work correctly? It has only bootlooped there. Since I got my phone. Once I get my phone back to operational state with root, how do I make sure that Slot B works (so I have a backup I can fall back on if (when) I bork something else?
[NG]Owner
like the title says I uninstalled the mentioned apps using adb and all of a sudden my camera stopped working so I decided for a simple restart and the device stuck in the loop ever since.
it restarts several times and open realme UI recovery and when I choose language it says " KINDLY REMINDER : system error, after select language, please select Online update(keep data) to recovery system, thanks! " .
So I did what the message said and I connect the wifi but instead of updating it says no updates found.
I also tried to wipe data but I got asked whether to retain contacts/media or format data.
I obviously tried the first one because I need the data but as expected it didn't work.
I am skeptical to clean format because I feel that I can still fix it with retaining the data.
I tried all the key combinations but only the realme UI recovery comes up . Please help me!
thank you
I don't think you'll be able to fix this without a full reflashing of the ROM using SP Tools and a format of the data partition from Recovery. You probably don't have access to full ADB now, if at all, and Fastboot won't help you recover anything. However, you should be able to rescue important files before you do this, as long as you have unlocked your bootloader.
Follow the steps here to install TWRP custom recovery. Once done, you can boot into it from fastboot by running `fastboot reboot recovery`. Once you're in TWRP, you can mount partitions so you can access them over USB from your PC.
Once you've got your important files transferred to your PC, take a full backup to be safe, then flash the stock ROM. This thread can help you do both of those things. Note that flashing the stock ROM using SP Tools will also restore the stock recovery. Once the process is done, boot right into fastboot and use it to reboot back into the stock recovery before letting it actually boot the ROM. Format your data partition (yes the whole thing). Now you can restart, and it should go through first time setup just fine.
I was going to uninstall these apps, but was too lazy. Guess lazyness is not too bad after all.
@Ricodey have you got the solution for this thing beacause i am also experiencing same issue
e_v_i_l_x_ said:
@Ricodey have you got the solution for this thing beacause i am also experiencing same issue
Click to expand...
Click to collapse
Unfortunately I had to go for the latter option of complete reset with the loss of data to get my device boot up . It seems the option to recover the device with data seems too complicated and not to mention the fact that this process is not without it's own risks. If you want an easy out from this issue I suggest that you complete format the device and have your important data backed up from now.
And Obviously I had data not backed up which I wanted on my device during this issue but it wasn't too important and I could let go of it cuz rest of my data was backed up.. but being the nerd I am, I tried to recover that data too.. but as I said it wasn't worth the time and risk for me so I chose the latter option.
Hope this helps! Do reply if you need further assistance !
Ricodey said:
Unfortunately I had to go for the latter option of complete reset with the loss of data to get my device boot up . It seems the option to recover the device with data seems too complicated and not to mention the fact that this process is not without it's own risks. If you want an easy out from this issue I suggest that you complete format the device and have your important data backed up from now.
And Obviously I had data not backed up which I wanted on my device during this issue but it wasn't too important and I could let go of it cuz rest of my data was backed up.. but being the nerd I am, I tried to recover that data too.. but as I said it wasn't worth the time and risk for me so I chose the latter option.
Hope this helps! Do reply if you need further assistance
Click to expand...
Click to collapse
for me the issue was like i just downgraded my device to the a.15 firmware after setting up i uninstalled the bloatware apps and some google apps which were not needed obviously and restarted my device and it got a bootloop, the issue of bootloop wasn't new to me i previoulsy had the same issue when i have downgraded to a.19 firmware. there is a simple fix, if you want to get rid of the bloatware apps now also you can use the disable command like.
(pm uninstall-user --user 0 ----package name---) this will not give any bootloop and can enjoy a part of RAM....
THIS WILL HELP
get in touch if need anything else