Database Develop

[Q] Boot loop - Still possible to backup internal sd?

Hi guys!
Here's my situation:
- P990, tonyp's PA 2.6 v.13, old bootloader, Kowalski kernel exp. version 12x
- Phone started boot looping (no obvious cause)
- Tried deleting cache. Didn't help.
- Tried flashing the same ROM from external SD. Didn't help.
- Tried restoring working backup (boot and system only, not complete restore) from CWM. Didn't help.
So then I guess I have to do a complete factory reset, but that means I'll lose everything on my internal SD card, right? I want to make a copy first so that I can keep my files. My nandroid backups are only 2.x GB, so I guess they don't include everything on the internal SD card.
I tried to connect the phone to my laptop, but nothing happened, so I deleted/reinstalled drivers from the LG website. That didn't work, but then I found this post which got me a little further. It said the installation was successful, but when I was in CWM, the disks (int. and ext. SD) wasn't being recognized. When I rebooted recovery (from CWM) or just rebooted the device, the computer recognized the discs and started installing four drivers, but as the phone either gets into CWM or just boot loops, it seems like Windows isn't able to finalize the installation of the drivers. This results in the SD cards not being functional in Windows. I can't even see disk labels or storage used/available.
Does someone have an idea of how I might be able to access the internal SD from Windows? Either by fixing the driver issue, or some other method?
I guess I have to fix this USB issue to be able to try to use adb pull to get all the stuff off the internal memory as well, right? Or is the connection between phone and computer not required to be "complete" to be able to do that? I do not remember for sure, but I believe I had turned on USB debugging before all this mess started. However, I have never used adb before.
I'm massively thankful for any help!

Sammy321 said:
Hi guys!
Here's my situation:
- P990, tonyp's PA 2.6 v.13, old bootloader, Kowalski kernel exp. version 12x
- Phone started boot looping (no obvious cause)
- Tried deleting cache. Didn't help.
- Tried flashing the same ROM from external SD. Didn't help.
- Tried restoring working backup (boot and system only, not complete restore) from CWM. Didn't help.
So then I guess I have to do a complete factory reset, but that means I'll lose everything on my internal SD card, right? I want to make a copy first so that I can keep my files. My nandroid backups are only 2.x GB, so I guess they don't include everything on the internal SD card.
I tried to connect the phone to my laptop, but nothing happened, so I deleted/reinstalled drivers from the LG website. That didn't work, but then I found this post which got me a little further. It said the installation was successful, but when I was in CWM, the disks (int. and ext. SD) wasn't being recognized. When I rebooted recovery (from CWM) or just rebooted the device, the computer recognized the discs and started installing four drivers, but as the phone either gets into CWM or just boot loops, it seems like Windows isn't able to finalize the installation of the drivers. This results in the SD cards not being functional in Windows. I can't even see disk labels or storage used/available.
Does someone have an idea of how I might be able to access the internal SD from Windows? Either by fixing the driver issue, or some other method?
I guess I have to fix this USB issue to be able to try to use adb pull to get all the stuff off the internal memory as well, right? Or is the connection between phone and computer not required to be "complete" to be able to do that? I do not remember for sure, but I believe I had turned on USB debugging before all this mess started. However, I have never used adb before.
I'm massively thankful for any help!
Click to expand...
Click to collapse
Can you tell me version of the recovery you use?
Did you tried wipe dalvik-cache? (Advance-->Wipe dalvik-cache)

bitdomo said:
Can you tell me version of the recovery you use?
Did you tried wipe dalvik-cache? (Advance-->Wipe dalvik-cache)
Click to expand...
Click to collapse
I'm using ClockworkMod Recovery v6.0.3.1.
Yes, I tried wiping dalvik cache as well, but that didn't fix it either.
Are there some other ways of getting out of the bootloop? I don't mind flashing stock rom or whatever else, as long as I can recover my internal SD.

Sammy321 said:
I'm using ClockworkMod Recovery v6.0.3.1.
Yes, I tried wiping dalvik cache as well, but that didn't fix it either.
Are there some other ways of getting out of the bootloop? I don't mind flashing stock rom or whatever else, as long as I can recover my internal SD.
Click to expand...
Click to collapse
Download AIO-toolkit from the developement forum. Install itt, and install nvflash drivers with it.
At the main screen select option 2, and then select option 2 again. Follow teh instructions on the screen, and select TWRP 2.5.0.0 to be installed, or cwm 5.0.2.8, both have working mass storage.
(6.0.3.1 has broken massstorage and adb interface. I think you installed cwm 6.0.3.1 through rom manager, if it that true you are on old bootloader.)

bitdomo said:
(6.0.3.1 has broken massstorage and adb interface.
Click to expand...
Click to collapse
Aha, that explains it!
I installed CWM 5.0.2.8 and I got a little further than before. When I mount USB storage in CWM, my external SD card shows up on my computer, but not my internal SD card. What can be the reason for this? Could the card be corrupted, or are there other ways of getting the internal SD to appear?
I tried mounting everything I could mount from the Mounts and storage menu in CWM, but the external SD was still the only thing that showed up on my laptop.
Thank you so much for helping with this!

Sammy321 said:
Aha, that explains it!
I installed CWM 5.0.2.8 and I got a little further than before. When I mount USB storage in CWM, my external SD card shows up on my computer, but not my internal SD card. What can be the reason for this? Could the card be corrupted, or are there other ways of getting the internal SD to appear?
I tried mounting everything I could mount from the Mounts and storage menu in CWM, but the external SD was still the only thing that showed up on my laptop.
Thank you so much for helping with this!
Click to expand...
Click to collapse
Can you try twrp 2.5.0.0?

bitdomo said:
Can you try twrp 2.5.0.0?
Click to expand...
Click to collapse
I've been trying, but I'm not even able to boot into recovery with TWRP installed.
Any other ideas? :fingers-crossed:

Sammy321 said:
I've been trying, but I'm not even able to boot into recovery with TWRP installed.
Any other ideas? :fingers-crossed:
Click to expand...
Click to collapse
Do a factory reset with a working cwm. You will lose all your installed apps and their data, but it will keep data on internal sdcard. After the factory reset you can boot up into andorid

bitdomo said:
Do a factory reset with a working cwm. You will lose all your installed apps and their data, but it will keep data on internal sdcard. After the factory reset you can boot up into andorid
Click to expand...
Click to collapse
YES! I thought factory reset would delete the internal SD, so I didn't even consider that, but it worked like a charm! Thank you so much for caring and helping! You just made my week! :highfive:

[Q] How to safely format Internal Storage ?

Okaii, there is nothing wrong with my phone and everything is working just fine , i always wipe system and data and and flash new roms ... i also have a backup of my rom , but now i want to make a FULL wipe , as in system, data, and internal storage.. but i know i can't connect my phone in twrp to add a rom file affter wiping storage.. so is there any way to do that , safely , without any errors and just flash the ROM again ?
Thanks.

ali-k95 said:
Okaii, there is nothing wrong with my phone and everything is working just fine , i always wipe system and data and and flash new roms ... i also have a backup of my rom , but now i want to make a FULL wipe , as in system, data, and internal storage.. but i know i can't connect my phone in twrp to add a rom file affter wiping storage.. so is there any way to do that , safely , without any errors and just flash the ROM again ?
Thanks.
Click to expand...
Click to collapse
You could try and use adb sideload, however for me sideloading ROM zips never works so what you would need to do is format the internal storage from a PC then transfer a ROM.zip over to it then proceed with the rest of the wipes except internal storage as you've already wiped that

Jonny said:
You could try and use adb sideload, however for me sideloading ROM zips never works so what you would need to do is format the internal storage from a PC then transfer a ROM.zip over to it then proceed with the rest of the wipes except internal storage as you've already wiped that
Click to expand...
Click to collapse
This works ?
Also i wanted to ask.. if i formated internal storage from the phone itself, after the boot , i transfer the rom.zip to it and do all wipes from recovery.. does it work too ?

ali-k95 said:
This works ?
Also i wanted to ask.. if i formated internal storage from the phone itself, after the boot , i transfer the rom.zip to it and do all wipes from recovery.. does it work too ?
Click to expand...
Click to collapse
Yep, both methods should work equally well

Jonny said:
Yep, both methods should work equally well
Click to expand...
Click to collapse
Thanks for the replies !
One more q. , how did you format your storage from PC ? i can't find that when right clicking my htc one..

ali-k95 said:
Thanks for the replies !
One more q. , how did you format your storage from PC ? i can't find that when right clicking my htc one..
Click to expand...
Click to collapse
Seems like its been disabled for MTP devices, that's new to me - looks like you'll have to go with the other way of doing it, flash the ROM with a full wipe of system and data beforehand then just wipe internal storage from recovery after the ROM has flashed.

Everything worked perfect , thanks alot !

Possibly Bricked? I'm an idiot.

I believe I may have bricked my Fire HD 7". I decided to flash a new ROM. Something I've done many many times. However, this time I decided to wipe the SD card because I wanted to get rid of all the app folders, my documents, music, etc. and start from a clean state. The problem is that it occurred to me half a second after the wipe that the ROM zip as well as the backup were on the internal SD.
So now I'm in TWRP trying to mount the device, but Windows (8.1) will not recognize the internal storage and mount it as a drive. I have the latest drivers installed but nothing...
It seems I have no way of getting a new ROM onto the internal SD card so that I can flash as normal. Help?

sicembaylor said:
I believe I may have bricked my Fire HD 7". I decided to flash a new ROM. Something I've done many many times. However, this time I decided to wipe the SD card because I wanted to get rid of all the app folders, my documents, music, etc. and start from a clean state. The problem is that it occurred to me half a second after the wipe that the ROM zip as well as the backup were on the internal SD.
So now I'm in TWRP trying to mount the device, but Windows (8.1) will not recognize the internal storage and mount it as a drive. I have the latest drivers installed but nothing...
It seems I have no way of getting a new ROM onto the internal SD card so that I can flash as normal. Help?
Click to expand...
Click to collapse
Use a Linux distro live CD to side load the ROM.
Sent from my device running CyanogenMod 11

SafinWasi said:
Use a Linux distro live CD to side load the ROM.
Sent from my device running CyanogenMod 11
Click to expand...
Click to collapse
Tried that under Ubuntu. I get an error message that the volume (Kindle) can't be mounted.

Figured out the solution. Neither Windows nor Linux would mount the device, so that I could transfer the ROM to internal storage the easy way. What worked was using ADB sideload. Now I'm relieved! For anyone else having this issue or a similar issue because they had a brain fart and wiped the internal storage AFTER wiping the ROM -- this is the solution to the problem. Use ADB sideload in TWRP.

So what are the steps
sicembaylor said:
Figured out the solution. Neither Windows nor Linux would mount the device, so that I could transfer the ROM to internal storage the easy way. What worked was using ADB sideload. Now I'm relieved! For anyone else having this issue or a similar issue because they had a brain fart and wiped the internal storage AFTER wiping the ROM -- this is the solution to the problem. Use ADB sideload in TWRP.
Click to expand...
Click to collapse
I'm in the exact same situation you were in (pre-brain fart) - I want to get a "fresh start" with my kindle. What are the steps I should take? I see in TWRP that I can wipe Dalvik, Data, Internal Storage, Cache and System.
I'm guessing I should wipe System, Cache, Dalvik, Flash the ROM, flash gapps, then wipe data/internal storage -- does this sound right?
Thanks

chiph72 said:
I'm in the exact same situation you were in (pre-brain fart) - I want to get a "fresh start" with my kindle. What are the steps I should take? I see in TWRP that I can wipe Dalvik, Data, Internal Storage, Cache and System.
I'm guessing I should wipe System, Cache, Dalvik, Flash the ROM, flash gapps, then wipe data/internal storage -- does this sound right?
Thanks
Click to expand...
Click to collapse
No need to wipe internal storage.

Re: No need to wipe internal storage
Rushead said:
No need to wipe internal storage.
Click to expand...
Click to collapse
Thanks - can you explain though? OP wanted to get rid of all of the music/documents/etc... Isn't the internal storage where these are? If not, what is stored here?

You can wipe internal if you want to, but be sure you can adb push your rom. I don't like to do this b/c it leaves you no backup plan. Besides, "fresh start" is mostly placebo imo.

[Q] encryption unsuccessful?

So, I figured I'd set up the scenario first in hopes to help make this understood:
1. Got the device
2. Booted/Updated to 5.0
3. Rooted using CF Autoroot
4. Remained on Stock 5.0 + Root (Stock bootloader/recovery)
- 1st "OFFICIAL" ROM came out so like the gentle flash'aholic I am, I rushed and downloaded [ROM][Unofficial][5.0.2][alpha/wip] Resurrection Remix v5.2.6[victara]
1. I installed TWRP via the Google Play App, (I think i was on 2.8.3.0)
2. Rebooted into TWRP, and did a FULL BACKUP (saved locally)
3. Formatted Davlik, System, Data, Internal Storage, Cache
4. Rebooted into TWRP, pushed the ROM files ([ROM][Unofficial][5.0.2][alpha/wip] Resurrection Remix v5.2.6[victara])
5. Flashed the ROM, GAPPS, SuperSU, Rebooted.
After about a minute of booting into the new ROM (new red loading animation) I started to get "encryption unsuccessful", and the only option was to factory reset phone, after which nothing happened, my guess was because of the custom recovery.
What was my error, and how do I prevent this from happening again?
My thinking is that wiping the Cache/System/Data/Internal/Davlik partitions somehow messed up some function someplace?
To fix it I took steps in this thread (http://forum.xda-developers.com/moto-x-2014/help/lollipop-update-failing-how-troubleshoot-t2961633) - thanks @randyklein
-Download "Official 4.4.4 Full Restore Images" from http://www.graffixnyc.com/motox.php# and extract. Move recovery.img, boot.img, and system.img into adb folder
-Boot into fastboot, plug in USB
-Using mfastboot v2, run the following commands:
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
How do I avoid this in the future if I decide to try a custom ROM/Recovery again?

Same problem...

Format data in twrp to fix encryption error

CWick4141 said:
Format data in twrp to fix encryption error
Click to expand...
Click to collapse
will i lose my twrp backup ?

marquesini said:
will i lose my twrp backup ?
Click to expand...
Click to collapse
Data partition just stores your apps (if not pre-loaded into system partition via ROM), and any data associated with them, so it leaves the Internal SD Card partition alone.
What concerns me is that I already wiped data, and I think I formatted the data partition as well, and still had the issue.
I'll have to try again soon.

I did a full wipe and then formated the data, then installed the ROM,gaaps,and supersu beta.
Got it working with root.

Shemploo said:
Data partition just stores your apps (if not pre-loaded into system partition via ROM), and any data associated with them, so it leaves the Internal SD Card partition alone.
What concerns me is that I already wiped data, and I think I formatted the data partition as well, and still had the issue.
I'll have to try again soon.
Click to expand...
Click to collapse
Formatting data in twrp is not the same as wiping data

CWick4141 said:
Formatting data in twrp is not the same as wiping data
Click to expand...
Click to collapse
True, that is why I said in above post that I think I formatted it as well, but being as I'm not certain I'll have to do it again to be sure.

Shemploo said:
True, that is why I said in above post that I think I formatted it as well, but being as I'm not certain I'll have to do it again to be sure.
Click to expand...
Click to collapse
You would know if you formatted data since it erases everything including internal storage

CWick4141 said:
You would know if you formatted data since it erases everything including internal storage
Click to expand...
Click to collapse
Alright, I booted TWRP, and clicked "Data" then "Repair/Change File System" it's currently showing f2fs, my format options are EXT2, EXT3, EXT4, FAT.
I think I want EXT4 right?
UPDATE: I tried EXT4 as every partition seems to use it, and from past experience, and It's working!.
Thank you for nudging me in the right direction.

edit: wrong thread

Xiaomi Mi A2 (jasmine) can I update stock ROM via TWRP

Good Morning, I want to upgrade brother device to new version of android (because he can`t install security updates for unknow reasons), but I affraid that he loose all apps and settings (he is a firefighter and have app from firefighter station which signals dangerous traffic etc.) So my question is can I update downloaded stock ROM via TWRP (adb sideload) without fears that he loose everything?

iHusky said:
Good Morning, I want to upgrade brother device to new version of android (because he can`t install security updates for unknow reasons), but I affraid that he loose all apps and settings (he is a firefighter and have app from firefighter station which signals dangerous traffic etc.) So my question is can I update downloaded stock ROM via TWRP (adb sideload) without fears that he loose everything?
Click to expand...
Click to collapse
The only thing that will take your fear, is a backup of all important partitions (boot, system, data, vendor, efs, persist), stored externally, plus a copy of the internal storage content, also stored externally.
With that you should be able to restore everything to the exact point it is at right now, so you'll really need to mess up hard to not come out of basically any situation with those partitions saved.
As for your inital question:
Why don't you just update via ota if you wanna stay on stock?

Phil_Smith said:
The only thing that will take your fear, is a backup of all important partitions (boot, system, data, vendor, efs, persist), stored externally, plus a copy of the internal storage content, also stored externally.
With that you should be able to restore everything to the exact point it is at right now, so you'll really need to mess up hard to not come out of basically any situation with those partitions saved.
As for your inital question:
Why don't you just update via ota if you wanna stay on stock?
Click to expand...
Click to collapse
Because, brother have error, while try install security updates, but he have from March this year
And this is not possible to make update, because after click backup (Data partition) I get error "cannot create data/media/0/TWRP

iHusky said:
Because, brother have error, while try install security updates, but he have from March this year
And this is not possible to make update, because after click backup (Data partition) I get error "cannot create data/media/0/TWRP
Click to expand...
Click to collapse
Okay, so maybe first copying internal storage content to your PC and backup important apps would be sufficient then.
For apps you can use Titanium Backup (good, but makes troubles on android 10 at the moment), Swift Backup (recommend by many others) and more.
These backup solutions save apps and app data on your phone, so copy that to an external place, or you might lose them if you need to format data (which I'll suggest).
After your "backups" are made, I would wipe every partition in each slot, which you can also achieve with a "fastboot -w", and then also format data - the one where you need to type "yes" (which will also erase all internal storage content, but most probably will also solve your troubles).
From here there are tools like miflash or fastboot images to reflash stock (inform yourself about them, before you start all that!).
Be sure to flash the latest one right away, so you won't be in the need of "dirty" updates immediately again.
Afterwards, you can copy back the internal storage content and the folder of the backup app, and restore the previously saved apps.

Phil_Smith said:
Okay, so maybe first copying internal storage content to your PC and backup important apps would be sufficient then.
For apps you can use Titanium Backup (good, but makes troubles on android 10 at the moment), Swift Backup (recommend by many others) and more.
These backup solutions save apps and app data on your phone, so copy that to an external place, or you might lose them if you need to format data (which I'll suggest).
After your "backups" are made, I would wipe every partition in each slot, which you can also achieve with a "fastboot -w", and then also format data - the one where you need to type "yes" (which will also erase all internal storage content, but most probably will also solve your troubles).
From here there are tools like miflash or fastboot images to reflash stock (inform yourself about them, before you start all that!).
Be sure to flash the latest one right away, so you won't be in the need of "dirty" updates immediately again.
Afterwards, you can copy back the internal storage content and the folder of the backup app, and restore the previously saved apps.
Click to expand...
Click to collapse
I tried MiFlash, but without wipe anything, and it don`t upgrade version of system
But if I must, flash 2 slots A/B using MiFlash or one slot (A) is for system?

You can just download the zip file with version u want from the site below and flash it via TWRP making cache and dalvik cache wipes and changing slots at the end.
https://mifirm.net/model/jasmine.ttt#zip-mif

pfss said:
You can just download the zip file with version u want from the site below and flash it via TWRP making cache and dalvik cache wipes and changing slots at the end.
https://mifirm.net/model/jasmine.ttt#zip-mif
Click to expand...
Click to collapse
So, I don't need
to flash second slot?

iHusky said:
So, I don't need
to flash second slot?
Click to expand...
Click to collapse
Just if u want. It's not necessary.
In october I updated mine this way but forgot to change the slot before rebooting to the system and realized that was in the old Android version. I just went to TWRP again and changed slot. After rebooting, the phone was in the updated Android One.

pfss said:
Just if u want. It's not necessary.
In october I updated mine this way but forgot to change the slot before rebooting to the system and realized that was in the old Android version. I just went to TWRP again and changed slot. After rebooting, the phone was in the updated Android One.
Click to expand...
Click to collapse
I tried using fastboot and MiFlash but after all it stuck on bootloader

iHusky said:
I tried using fastboot and MiFlash but after all it stuck on bootloader
Click to expand...
Click to collapse
I just updated mine to November patch downloaded from here: https://mifirm.net/downloadzip/4197
I entered fastboot mode, executed
Code:
fastboot boot my_twrp_image_file.img
In TWRP made de wipes, flashed the ROM, changed slot and rebooted phone. It looks like it's normal.