Hi,
I installed Galaxian Soup 1.5.1 beta a week ago and all has been running fine. This morning the tab was blank like it had run out battery so I put it on charge and found it wasn't dead. Tried to reboot and it's just stuck at the "Samsung Galaxy Tab 8.9" screen. I was using it fine last night and haven't changed anything!
I've tried ODIN to restore Stock Recovery which said it passed and worked, but still the same problem. It has removed CWM though. When I try to do anything in Stock Recovery it complains about not being able to mount the /data directory.
Is there anything else I can try, do I need to use ODIN to flash a ROM again? If so, can you tell me which file to use as there are hundreds in the Galaxian Soup zip.
Thanks!
Flash stock rom with Odin. Unfortunately you also need to wipe data in stock recovery for this to work, so you will loose everything.
Thanks for the reply. Unfortunately this hasn't worked, it passes in Odin but then on the tablet it says E:failed to mount /data, and "your storage not prepared yet, please use UI for format and reboot actions.
Trying to factory reset fails.
Any other ideas?
OK, a bit more detail. I use ODIN to flash the stock rom found here - http://forum.xda-developers.com/showthread.php?t=1483168
It passes and goes into recovery but complains in red letters about not being able to mount /data, can't access /system/csc/XEU/system in yellow and can't mount /cache or a few other subdirectories.
I select wipe data which appears to work although it complains about make_extf4fs failing on /dev/block/mmcblk0p8. It then complains about not being able to mount /cache and other subdirectories again.
I then select reboot, it complains again about not being able to mount /data and /cache and switches off, not reboot. If I turn it on again I'm straight back to recovery.
Got to be something I'm missing here!
Any input appreciated.
It seems your partition tables are messed up, but i have no idea how this could happen if you didn't flash anything that could cause this, maybe a hardware problem?
There is a way to repartition the tables, you need a PIT file for this. I have not done this myself, so unfortunately i don't know much about it. Try to search for a PIT file, but make sure it's for your tab model, otherwise you can mess it up completely.
Many thanks - that fixed it! For future reference and for anyone searching this thread I found the pit file here - http://forum.xda-developers.com/showthread.php?t=1406137&page=9 and flashed it with ODIN together with the standard firmware I mentioned in the earlier post.
It's not all good news though. The tablet now keeps freezing. Even in recovery while I was trying a factory reset for the freezing. This leads me to believe it may be a hardware problem that caused the original brick and ongoing freezing issues. What do you think? Does it save a dump anywhere when it crashes?
Glad to see it worked. Maybe try to flash the stock rom again, now without the pit file. Also try factory reset in stock recovery. If you are still having problems, then im afraid its a hardware problem.
Yeah, I came to the same conclusion. It was hanging even whilst in stock recovery which means it had to be a hardware problem. Took it back to the shop and got a refund, new one is on it's way.
Bit nervous about ROMing the new one! The only thing I can think of is maybe overclocking damaged the cpu, although I only set it to 1.4Ghz. Or I was attaching a card reader and it was complaining about a service crashing when I removed it. Maybe it would have happened whether I messed with it or not!
Mbuxton said:
Yeah, I came to the same conclusion. It was hanging even whilst in stock recovery which means it had to be a hardware problem. Took it back to the shop and got a refund, new one is on it's way.
Bit nervous about ROMing the new one! The only thing I can think of is maybe overclocking damaged the cpu, although I only set it to 1.4Ghz. Or I was attaching a card reader and it was complaining about a service crashing when I removed it. Maybe it would have happened whether I messed with it or not!
Click to expand...
Click to collapse
I have been flashing different roms, kernels and recoveries on my tab for more then 200 times probably. And i have been using Galaxian-Soup AOSP ICS rom with molteys kernel for almost two months. Never had any problems (that i didnt create myself). Never used overclock, but havent heard of anyone who has had problems with it either.
I've encrypted my phone but I forgot to decrypt before flashing ROM. I flashed custom LSC in this forum and after boot it ask my encryption password. I type the correct password but it said it's failed.
I try to use PCodin with downloading mode to back to stock GB. When the phone boot it won't ask anything, I can use it normally, but when I flash JB again the encryption page is still keep asking for the password. When I boot into CWM (I use PhilZ kernel) it said failed to move "exfat /dev/block/mmcblk1p1 sdcard", I cannot even wipe my internal memoery.
I've tried to find an answer in this forum but I only found an answer for GNex. It about booting into fastboot mode but GNote cannot do this.
please help!!!
--------------------------------------------------------------------------------------------------------------------------------------------------
Edit Fixed!!
I've flashed my SGN to stock GB with ODIN (with PIT file and check Re-Partition). When I updated it to JB again it still asked for the password, but this times it has password failed count. When it reached 10 it's reset and my problem was fixed, the next boot didn't ask a password anymore.
(Note !! - the messsage in CWM "exfat /dev/block/mmcblk1p1 sdcard" it because I forgot I've removed my SDCard. CWM will said that when it's not found SDCard)
Bump. In the same boat. Praying we're not up shoot creak. I have the same phone I used to encrypt (till Friday when this phone gets exchanged for new one. Radio is dead and tech at sprint flashed it).
Card encrypted, irreplaceable files trapped inside
Card is still in the Same device that originally encrypted the card
Know the password
Flashed device before decryption possible
Scouring the web for way to retrieve files
It should also be interesting to note that zi can see "all" files on the card. I just can't open them. I see the movies, pictures, documents. They are all there. Their just scrambled up so I can't open them. Please help
EncryptedMemories said:
Bump. In the same boat. Praying we're not up shoot creak. I have the same phone I used to encrypt (till Friday when this phone gets exchanged for new one. Radio is dead and tech at sprint flashed it).
Card encrypted, irreplaceable files trapped inside
Card is still in the Same device that originally encrypted the card
Know the password
Flashed device before decryption possible
Scouring the web for way to retrieve files
It should also be interesting to note that zi can see "all" files on the card. I just can't open them. I see the movies, pictures, documents. They are all there. Their just scrambled up so I can't open them. Please help
Click to expand...
Click to collapse
My problem is I've encrypted my device and did factory reset wihout decrypted it.
But I think your problem is you've encrypted SDCard because you still can use your phone normally.
I think the solution is you need to restore the backup of the ROM you've used encryption (the backup, not the ROM).
Because only the ROM (backup file) that encrypted it can do a decryption.
There have been several similar cases.
The encryption file resides in the /EFS metadata.
If you search the N7000 threads there is a user that solved the problem
by changing the efs metadata. ask him for details.
Af
takato11000045 said:
My problem is I've encrypted my device and did factory reset wihout decrypted it.
But I think your problem is you've encrypted SDCard because you still can use your phone normally.
I think the solution is you need to restore the backup of the ROM you've used encryption (the backup, not the ROM).
Because only the ROM (backup file) that encrypted it can do a decryption.
Click to expand...
Click to collapse
What backup.
I don't even have a note. I have a GSII. I found this thread which was close to what I was going through.
Hi i am using samaung Galaxy Note GT-N7000, with stock rom. I encrypted my phone. It was working fine.
Now i have started decrypting it. I know the password and applied it. My phone also took it successfully and started the decryption process.
Its been nearly 2 hours since its decrypting. I didnt tocuh it. Just getting curious now, how much more time would it take to decrypt?
Battery was full and phone is plugged in wall charger for the past 2 + hours, so battery isn't any issue. I am just seeing samsung logo. Can anyone help me what should i do? How much time i should wait? Any feedback would be appreciated. Please help.
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.
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
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