Database Users

[Q] Trouble with flashing / /data is destroyed

Hey Guys,
i have a big problem with my new S4 (i9505).
Ive rooted the Stockrom with Odin and then i flashed the Recovery, thats works well.
After this step ive tried to flash CM10.1.
The first boot works well, ive setup my phone, take a reboot and then i have a bootloop.
Ive go to the Recovery and i see that /data is destroyed.
Ive formating /data, flashed CM10.1 again, first boot works, second boot, /data is destroyed.
Then i flashed the prerooted XXUBF8-Firmware, flash the recovery, all works well. Then i flashed a alternative Kernel, my /data will be destroyed again. I have to format it, and to reflash the stock firmware.
My last try was to flash the minit-Framework. After this flash, i cant boot in my system, becaus my /data was destroyed.
I dont thought that my device is destroyed, because the Stock prerooted F8-Firmware (with custom recovery) works 2 weeks long without any problems (ive rebootet many times in the 2 weeks).
What i doing wrong?
And sorry for my bad english
Best regards

Just to follow you : what do you mean by "destroyed" ? Formatted partition ?
If so, try to do the following : flash stock ROM, then the recovery (I personally use Philz Touch based on CWM), do a factory wipe and then install the rom you want.

Hey,
thanks for answer.
When i have a bootloop and go to the recovery and want reflash a rom, the installer say: cannot mount /data, unknow partition. and then the setup breaks up.
After a format of the /data-Partition via Recovery, i can reflash the rom, and boot onetime.
Ive go "your way" and i have the some problem. After one Reboot my /data is destroyed.

Mmmm...in the Philz Touch recovery (based on ClockWorkMod but with a lot of improvements), there is an option called "wipe data for new rom install" or something similar... give it a try !

I will try it
Ive tried it with CWM / TWRP and have the same error.
But i will try it ) *flash*
Till later

androidnoobi said:
I will try it
Ive tried it with CWM / TWRP and have the same error.
But i will try it ) *flash*
Till later
Click to expand...
Click to collapse
Good luck ! As you can normally flash stock rom, you don't seem to have hardware issues so don't worry

omg Oo
I dont believ it -.-
All the trouble are only fail from CWM and TWRP??
Now with Philz it works perfectly.
Ive installed Bobcat, reboot, flashed minit, reboot, flash another Kernel, reboot .. and it works Oo
Great )
Thanks

Recovery can't mount /system S5 bricked

TWRP can't mount /system. Phone is a SM-G900T 16GB
- Running the latest version of TWRP I tried:
- Wiping, repairing, and reformatting from TWRP, also tried formatting data. I get a unable to mount '/system' error message every time.
- Using Odin and Heimdall to reformat using a downloaded .pit, neither works. I ran Heimdall in Windows and Linux (ran as sudo and admin). I re-downloaded the .pit multiple times and tried a couple different sources.
- Installing CWM using Heimdall, and ADB. In ADB and Heimdall I still have TWRP and in Odin it removes the recovery completely.
- Fix permissions gives the unable to mount '/system' error message.
- Installing ROM from Heimdall and TWRM
- Mounting /system with or without MTP
How it happened:
I was running Cyanogenmod 11 with encryption and updated to 12. CM12 was running great, flashed GApps, still running good. I signed in to my Google account and downloaded IPcamera. While running IPcamera I got an email, the screen started going crazy flashing between the alert and IPcamera screen, I couldn't do anything so I pulled the battery. When I rebooted it was stuck in a boot loop. I booted into recovery, it asked for my encryption password as usual. The password didn't work. I tried several times. I rebooted and tried again, still nothing. I rebooted again and this time hit cancel when asked for the password. I wiped everything and got the can't mount /system error. I tried everything above, nothing works.
I can't download my .pit so there is more wrong than just the data partition.
Any ideas? I would love this thing to no longer be a really expensive paperweight. I really can't afford to replace this thing right now
Thanks for your help.

Odin back to factory stock and use Samsung's stock recovery to do a couple of wipes.

Commodore 64 said:
Odin back to factory stock and use Samsung's stock recovery to do a couple of wipes.
Click to expand...
Click to collapse
That worked!! I don't know why the stock recovery can fix it when TWRM couldn't. It worked though. Thanks a ton!!

Commodore 64 said:
Odin back to factory stock and use Samsung's stock recovery to do a couple of wipes.
Click to expand...
Click to collapse
This didn't work for me every time I wipe in TWRP it just never installs the packages, or upon restart it just doesn't mount system. Wipe repair on TWRP doesnt work either

egyptshun said:
This didn't work for me every time I wipe in TWRP it just never installs the packages, or upon restart it just doesn't mount system. Wipe repair on TWRP doesnt work either
Click to expand...
Click to collapse
I'm totally with you on wipes and package installs randomly failing on TWRP, but I have no idea why. Sometime in December, I made the switch to Philz CWM, and I haven't looked back since.
At any rate, it is always good practice to odin back to stock, use the stock recovery to do wipes (factory reset and wipe cache), and then odin Philz CWM or any recovery program of your choice.
If you're planning on loading Lollipop, then you might just download the latest from Sammobile, odin the stock and wipe, and then load your custom recovery.
Best of luck,

Commodore 64 said:
I'm totally with you on wipes and package installs randomly failing on TWRP, but I have no idea why. Sometime in December, I made the switch to Philz CWM, and I haven't looked back since.
At any rate, it is always good practice to odin back to stock, use the stock recovery to do wipes (factory reset and wipe cache), and then odin Philz CWM or any recovery program of your choice.
If you're planning on loading Lollipop, then you might just download the latest from Sammobile, odin the stock and wipe, and then load your custom recovery.
Best of luck,
Click to expand...
Click to collapse
I have a G900W8, there's no lollipop version for me. What phone FW can I flash and retain phone signals etc.

Captian Double post Double post here.
I'm going to snap my phone in half, it's been over 13 hours of trying to fix this. How does no one else have this problem?
EDIT: YAAAAAAAAAAAAAAAAAAAASSSSS I FINALLY GOT IT TO WORK > I HAVE NO CLUE HOW <

Cant install LineageOS 14.1 on G2 D802 (TWRP deletes root)

Heyy,
as i had some problems with my g2 i had to flash stock rom kitkat 4.4.2.
I rooted with ioroot, downloaded lineage and gapps files, flashed custom recovery with autorec but if i then go to twrp and install lineage os and gapps, i always get "your device does not appear to have root. do u want to install supersu?", althoug ive checked root with "root checker" before... i cant find the mistake
I WANT LINEAGE OS

Quicka said:
Heyy,
as i had some problems with my g2 i had to flash stock rom kitkat 4.4.2.
I rooted with ioroot, downloaded lineage and gapps files, flashed custom recovery with autorec but if i then go to twrp and install lineage os and gapps, i always get "your device does not appear to have root. do u want to install supersu?", althoug ive checked root with "root checker" before... i cant find the mistake
I WANT LINEAGE OS
Click to expand...
Click to collapse
Autorec is just the first step to twrp. Go to https://forum.xda-developers.com/lg-g2/development/twrp-twrp-2-8-0-0-kernel-f2fs-tools-t2898705 and get the bumped version 3.1.0-1.
Then put it in your phones memory, boot into twrp you got from autorec and flash the new version.

Jan Philipp said:
Autorec is just the first step to twrp. Go to https://forum.xda-developers.com/lg-g2/development/twrp-twrp-2-8-0-0-kernel-f2fs-tools-t2898705 and get the bumped version 3.1.0-1.
Then put it in your phones memory, boot into twrp you got from autorec and flash the new version.
Click to expand...
Click to collapse
i have done it... but after i wiped data,... etc. flashed lineage os and gapps and reboot system, phone screen gets black... and i can only go to download mode to flash again stock rom ive tried it about 5 times

Problem fixed
problem fixed: flashed lollipop firmware, then rooted with LGoneClickRoot and installed TWRP with autorec

Quicka said:
problem fixed: flashed lollipop firmware, then rooted with LGoneClickRoot and installed TWRP with autorec
Click to expand...
Click to collapse
How did you flashed your phone? Your display have been black and you haven't seen anything. How did you entered into download mode?

djsasha78 said:
How did you flashed your phone? Your display have been black and you haven't seen anything. How did you entered into download mode?
Click to expand...
Click to collapse
just held the volume up button and then connected with pc. then using lg flash tool to flash lollipop stock rom

1. Root + TWRP : https://www.dropbox.com/s/2shvozzbu29xjfu/LGG2-D802-OneClickRootRecoveryV1.1.zip?dl=0
2. Update TWRP to 3.1 by flashing zip file and then rebooting recovery: http://www.gregtwallace.com/lgg2-projects/twrp/?version=3.1.0-1
3. LineageOS by flashing rom zip file and gapps: https://download.lineageos.org/d802 + http://opengapps.org/ (ARM + Android 7.1)
easiest method to flash lineageOS on LG G2 https://www.youtube.com/watch?v=BoPjGM0nrak (Video tutorial)

Hi,
It seems I have the same issue :
I tried to install LineAge, using TWRP 3.2.1 (from CM12.1), but nothing is working (I tried 20180425 and 20180404 nightly versions). After reboot I can see the backlight on the lcd screen but nothing else. Then I tested the installation of a CM12 version, all is right, normal boot. No error message written in the console. i tried also a CM13 install, same as Lineage.
Do you think I have to flask back to LG "OS" ?

JackSparreau said:
Hi,
It seems I have the same issue :
I tried to install LineAge, using TWRP 3.2.1 (from CM12.1), but nothing is working (I tried 20180425 and 20180404 nightly versions). After reboot I can see the backlight on the lcd screen but nothing else. Then I tested the installation of a CM12 version, all is right, normal boot. No error message written in the console. i tried also a CM13 install, same as Lineage.
Do you think I have to flask back to LG "OS" ?
Click to expand...
Click to collapse
Are you clean flashing? Make sure to factory reset, wipe system, data and cache before flash. Never wipe internal storage. Swipe factory reset again after flash. Try flashing gapps later after confirming that Rom boots fine.

cropsroth said:
Are you clean flashing? Make sure to factory reset, wipe system, data and cache before flash. Never wipe internal storage. Swipe factory reset again after flash. Try flashing gapps later after confirming that Rom boots fine.
Click to expand...
Click to collapse
Hi,
yes I wiped Dalvik, system, data & cache through TWRP, before flash. But I don't wipe after, I rebooted without GApps...
Maybe, because I read that somewhere, I need to flash a bootstack. I don't know when I have to di it, if I have to do.
Thanks

JackSparreau said:
Hi,
yes I wiped Dalvik, system, data & cache through TWRP, before flash. But I don't wipe after, I rebooted without GApps...
Maybe, because I read that somewhere, I need to flash a bootstack. I don't know when I have to di it, if I have to do.
Thanks
Click to expand...
Click to collapse
Yes, you don't wipe after flash, but you swipe the factory reset, it does not wipe but resets the flashed Rom. Give it a clean shot again. Check MD5 of the all files you downloaded with original MD5 to confirm the file didn't get corrupt.
Boot stack flash not needed. Please read the first post thoroughly in lineage thread
"""
Requirements:
Custom recovery (TWRP or any other)
KitKat (KK) bootloader (included in the lg-devs LP bootstack)
KitKat (KK) bootstack minimum; Please read the entire FAQ for important bootstack information. Installation of bootstacks is NOT recommended.
Clean flash if coming from another ROM or CM 13 (no dirty flash, wipe system too check you bootstack(needen bump support)
"""

crophs said:
... but you swipe the factory reset, it does not wipe but resets the flashed Rom. Give it a clean shot again. ...
Click to expand...
Click to collapse
Hi,
what do you mean by "you swipe the factory reset", I'm not sure what it is, either "give it a clean shot again".
Sorry I'm not very aware of all those processes ^_^, and I'm french so not very aware of some vocabulary words
Thank you

Max pro m1 bootloop? Please help

Hello, so im stuck now on startup. I actually rooted my phone a week ago and everything's fine until I've downloaded some cracked apks online and restarted my phone. Please help what would i do now
imgur.com/a/07UWA4l

Did you installed Twrp...if yes then you might want clear cache and restart the phone or you could just reflash the rom or any other custom rom....and if you havn't then i am afraid you will have to lose your data..

Paramvir Singh said:
Did you installed Twrp...if yes then you might want clear cache and restart the phone or you could just reflash the rom or any other custom rom....and if you havn't then i am afraid you will have to lose your data..
Click to expand...
Click to collapse
yes yes i've installed twrp, i've actually tried formatting my data, clearing dalvik cache (thru twrp) then restarted it but still stuck at loading zenfone logo. i dont care bout my data on phone, just wanna get my phone back to normal.
can u please elaborate bout reflashing rom? i've never done flashing any rom before , stock or custom,

Never done this on my M1 but on my note edge,
When i got a bootloop, i simply reinstall stock rom, or just clean install custom rom

abcnormal said:
yes yes i've installed twrp, i've actually tried formatting my data, clearing dalvik cache (thru twrp) then restarted it but still stuck at loading zenfone logo. i dont care bout my data on phone, just wanna get my phone back to normal.
can u please elaborate bout reflashing rom? i've never done flashing any rom before , stock or custom,
Click to expand...
Click to collapse
Ok so it's good opportunity to try something new...first you need to download custom rom and gapps package to sd card (always a better option)or internal storage...do the downloads on pc or somewhere else...
1. Wipe cache, dalvik cache, system, vendor, data, internal storage(this one is optional)
2. Mount extsd card
3. Install Rom package...(i personally use xenonhd based on pie) from here https://mirrors.c0urier.net/android...tal/X00T/XenonHD-181007-Experimental-X00T.zip
You can try any other of your choice
4. Install Gapps package from here..http://download2264.mediafire.com/r0vq21tabscg/m1u4llu62bdwyos/BiTGApps-arm64-9.x.x-0.1-unsigned.zip
5. This step is optional if you want root access then flash magisk package from here..https://github.com/topjohnwu/Magisk/releases/download/v17.1/Magisk-v17.1.zip and uninstall package from https://github.com/topjohnwu/Magisk/releases/download/v17.2/Magisk-uninstaller-20180921.zip ......after tge rom boot up install magisk manager from https://github.com/topjohnwu/Magisk/releases/download/manager-v6.0.0/MagiskManager-v6.0.0.apk
6. Reboot to system..first boot up will take 4-5 minutes...ENJOY

so i tried flashing the stock rom but i got an error
Code:
[B] This package is for "ASUS_X00TD" devices; this is a "X00TD"[/B]
i got the rom at asus.com/ph/Phone/ZenFone-Max-Pro-ZB602KL/HelpDesk_BIOS/
i guess i'll try flashing with a custom rom instead?
also a follow up question: is it safe to reboot to recovery with twrp even my phone has no OS installed (already wiped it for flashing a new rom)

abcnormal said:
so i tried flashing the stock rom but i got an error
Code:
[B] This package is for "ASUS_X00TD" devices; this is a "X00TD"[/B]
i got the rom at asus.com/ph/Phone/ZenFone-Max-Pro-ZB602KL/HelpDesk_BIOS/
i guess i'll try flashing with a custom rom instead?
also a follow up question: is it safe to reboot to recovery with twrp even my phone has no OS installed (already wiped it for flashing a new rom)
Click to expand...
Click to collapse
Stock rom available at asus website is not flashable through twrp...u need twrp flashable zip...download this file...
https://forum.xda-developers.com/showpost.php?p=77671149&postcount=83
And also decrypt file from here.... https://forum.xda-developers.com/asus-zenfone-max-pro-m1/how-to/mod-decrypt-data-t3787311
After flashing the rom...flash decrypt zip
And remember to wipe internal storage after flashing these two zips!

Hello sir i got stuck in bootloop in asus max pro m1
Actually its not showing anything screen is blinking as i try to turn it on. I was on custom rom and suppose to install stock rom and i followed every step but my phone doesn’t start its just reboot and nothing displays anything. Please can anyone tell me the solution of this issue.

did u solved issue
how did u soolves issue ??

.

.

HMSS013 said:
Had my new OP5 rooted and almost everything was right in the world, but i flew too close to the sun by uninstalling a few apps I thought were expendable and eventually Google Play Services started crashing. When all troubleshooting failed I ended up flashing a fresh copy of OxygenOS (5.1.7) to my device, but every attempt to re-root the device has failed.
The first obstacle I ran into was that there was no access to Internal Storage in TWRP, I was able to fix that by Wipe > Format Data and then using Advanced Wipe to clean Dalvik/Cache/System/Data for good measure.
My next issue was that TWRP returned Error 7 when attempting to flash the stock OOS rom... after some digging I was able to clean the 'asserts' line from the updater-script file and now the rom will flash.
The headache has been getting the device re-rooted, and I feel like I've tried everything. I have to flash the SuperSU or Magisk zip (both fail to root the device) before reboot because the dm-verity encrypts on first boot and after that I can't access any storage to flash from internal memory. The three different dm-verity patches I've found don't prevent it. I also tried 'fastboot oem disable_dm_verity' to try and stop it but after talking with the device fastboot returns 'unknown command'.
My final effort to get around it was to flash a kernel that didn't force dm-verity (blu_spark kernel) but that returns Error 1: 'Unsupported Android Version' when I attempt to flash it.
I've tried dozens of variations on this, including a Lineage OS rom instead and also trying to sideload certain zips, but still no dice. Any and all help would be appreciated.
Click to expand...
Click to collapse
Which rom do you want to install?

HMSS013 said:
The first obstacle I ran into was that there was no access to Internal Storage in TWRP, I was able to fix that by Wipe > Format Data and then using Advanced Wipe to clean Dalvik/Cache/System/Data for good measure.
Click to expand...
Click to collapse
Hi, this one is because of your TWRP. Please flash Codework's TWRP and try that with it. It should solve your issue for sure. (same thing happened to me while I tried installing custom roms and every time I needed to wipe everything to see my internal storage again)
This guide can help you out with Error 7 on TWRP https://forum.xda-developers.com/showthread.php?t=2522762
I do believe your this issue you're having caused by TWRP. Also after rooting the phone, install magisk app. (you don't need to install supersu, it comes with magisk). After rebooting into system reboot your phone again once more it should show up on magisk app that you've successfully rooted your phone. Remember after flashing magisk you need to reboot twice in order for phone to realize it. Please try the steps I told you and let me know.
Also you don't need to flash dm-verity patch at all.
Try clean flash instructions with Codework's TWRP and root it with latest Magisk.

.

.

HMSS013 said:
I actually really like the Oreo version of OxygenOS, so when I had to resort to re-flashing to fix this mess I dug up one of the stock (5.1.7) roms, it served me well (assuming I can get it rooted, lol).
I'd be willing to move to Lineage if I absolutely have to, but if not, I'd really like to keep Oreo if at all possible.
Click to expand...
Click to collapse
For 5.1.7 try this twrp https://drive.google.com/file/d/1UlTftbe6wooAs4Fp0cjwXlOKmfQHgdfL/view?usp=drivesdk along with magisk 17.1.
Clean flash is recommended. If it didn't help, please list your steps again(detailed).
Don't use supersu and skip the other suggestions for now please.

.