Hey guys,
I unlocked my bootloader and flashed a recovery succesfully. When I entered into recovery mode, I enter into TWRP, get to install SuperSU, but when I reboot my device, it is stuck on "warning etc..."
What could I have done wrong? How can I fix this? Any help would be very much appreciated.
I have a MXP XT1563
I installed this TWRP http://forum.xda-developers.com/devdb/project/?id=11587#downloads
And this SuperSU https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
I honestly can't remember what fastboot files I download, but I suppose it was ok since I got to enter my unlocking code and unlock it.
Thanks in advance.
Regards from Mexico
When I enter into TWRP and enter somewhere, for instance Install, I can see my folders: amazon, kindle, whatsapp, etc... I suppose that's good news.
I've tried doing a factory reset from Wipe, no sucess.
Please help! I will be uncommunicated until I solve this
you should have read the forums first. did you take a nandroid before flashing su? of yes then restore that,
you need su 2.62-3
download the su then flash it again. here is the su.forum.xda-developers.com/moto-x-play/general/root-how-to-root-6-0-easly-t3277202
bablu048 said:
you should have read the forums first. did you take a nandroid before flashing su? of yes then restore that,
you need su 2.62-3
download the su then flash it again. here is the su.forum.xda-developers.com/moto-x-play/general/root-how-to-root-6-0-easly-t3277202
Click to expand...
Click to collapse
hi bablu048, I did not "nandroid" before flashing su. I did it after I flashed it and when I try to restore it it says it's read only.
Do I download su 2.62-3, copy it into my storage and flash it again, no matter all I've done by now?
when it asks to keep read only refect it select allow modifications,
yes, download that su , copy it to storage and flash.
bablu048 said:
when it asks to keep read only refect it select allow modifications,
yes, download that su , copy it to storage and flash.
Click to expand...
Click to collapse
ok, this is what I did: I downloaded the su, put in internal storage, went into recovery mode, got into twrp, installed new su.
Now it gets past the warning, but gets stuck now in the water-ish motorola logo...
When I go into Restore, I can see two back ups, when I try to restore any of them, it says "cannot restore system - - mounted read only" and no option to modify it.
thanks a lot for your help! I'm trying to follow your every advice as best as I understand it
DO NOT restore the old backup it has the old su you will be back to where you started.
]boot into twrp clear cache/dalvic cache and leave the phone on the watery logo for a few minutes..it takes some time to boot
bablu048 said:
DO NOT restore the old backup it has the old su you will be back to where you started.
]boot into twrp clear cache/dalvic cache and leave the phone on the watery logo for a few minutes..it takes some time to boot
Click to expand...
Click to collapse
I see... actually I didnt get to restore any of them. I cleared both caches and now I'm waiting in the watery logo.
In case I don't make it, I'll have to let it for a while like this: on the watery logo, the MXP is quite hot now... no problem if I let it like that for half a day? I'm worried about that
In case it doesn't pass from there... is downloading twrp backups still an option? I just finished downloading RSD lite.
fsae3 said:
I see... actually I didnt get to restore any of them. I cleared both caches and now I'm waiting in the watery logo.
In case I don't make it, I'll have to let it for a while like this: on the watery logo, the MXP is quite hot now... no problem if I let it like that for half a day? I'm worried about that
In case it doesn't pass from there... is downloading twrp backups still an option? I just finished downloading RSD lite.
Click to expand...
Click to collapse
just let it on the watery logo for 15-20 minutes if it's still not going any further you can download the backups and wipe the system, cache, dalvic cache then restore the backup
RSD lite is used to flash the original factory firmware then you have to root again.
bablu048 said:
just let it on the watery logo for 15-20 minutes if it's still not going any further you can download the backups and wipe the system, cache, dalvic cache then restore the backup
RSD lite is used to flash the original factory firmware then you have to root again.
Click to expand...
Click to collapse
I went to sleep and it didn't pass from the watery logo.
I manually backed up my files, so I'm not worried about anything I might have on the phone; still, I think flashing a new firmware will factory reset my MXP correct?
Is the original factory firmware the same as a stock image? I found this list of resources: https://github.com/motoxplay/stock. Under XT1563 - México, I can see my carrier, Iusacell. Will this do it?
Please do let me know.
fsae3 said:
I went to sleep and it didn't pass from the watery logo.
I manually backed up my files, so I'm not worried about anything I might have on the phone; still, I think flashing a new firmware will factory reset my MXP correct?
Is the original factory firmware the same as a stock image? I found this list of resources: https://github.com/motoxplay/stock. Under XT1563 - México, I can see my carrier, Iusacell. Will this do it?
Please do let me know.
Click to expand...
Click to collapse
yes it will wipe,
that's the correct firmware. 6.0.1
always take a nandroid before flashing su 2.62-3
after flashing twrp again when you boot into twrp do "swipe to allow modifications to /system"..you didn't do this that's why you were not able to restore backups.
bablu048 said:
yes it will wipe,
that's the correct firmware. 6.0.1
Click to expand...
Click to collapse
hi bablu048,
I found in here a "unSu" guide. I ran it, it deleted Su, then ran Su you recommended and I still got suck in the watery logo.
Then I "unSu" it again, now didn't run any Su, reeboted device and it finally started.
I think su is the problem. Where can I check what su should I use?
great first take a nandroid.
finding the correct su is hit and trial method. generally su 2.62-3 worked. try other su's 2.65,2.66
bablu048 said:
great first take a nandroid.
finding the correct su is hit and trial method. generally su 2.62-3 worked. try other su's 2.65,2.66
Click to expand...
Click to collapse
Ok, I get it now. I backup my device with nandroid to make sure I have it there in case something goes wrong. If I have no info I want to save (my phone is blank, it's factory resetted from the bootloader unlocking) is it still necessary to nandroid? It's necessary in case a su fails right?
nandroid backup takes a backup of your OS with data and everything.
I think you didn't allow/system to be modified when you first booted into twrp. that's why su is failing, as su modifies the /system partition.
bablu048 said:
nandroid backup takes a backup of your OS with data and everything.
I think you didn't allow/system to be modified when you first booted into twrp. that's why su is failing, as su modifies the /system partition.try
Click to expand...
Click to collapse
by now, my MXP is factory resetted, I'm trying to read more before doing anything.
Since is factory resetted, it doesn't have developer mode (oem unlocking, usb debugging). I still see TWRP in recovery mode.
I suppose if I want to try another SU, I have to enable develper of course, oem-usb, obviously. Do I have to flash TWRP again? Or can I just try a SU? Of course, after having done a nandroid.
fsae3 said:
by now, my MXP is factory resetted, I'm trying to read more before doing anything.
Since is factory resetted, it doesn't have developer mode (oem unlocking, usb debugging). I still see TWRP in recovery mode.
I suppose if I want to try another SU, I have to enable develper of course, oem-usb, obviously. Do I have to flash TWRP again? Or can I just try a SU? Of course, after having done a nandroid.
Click to expand...
Click to collapse
you don't need to take nandroid backup always, once is sufficient unless you want to backup the latest data. no need to flash twrp again. just flash su.
take a nandroid backup once (everything system, boot, data) . after successfully flashing su you can keep another backup that contains su.
bablu048 said:
you don't need to take nandroid backup always, once is sufficient unless you want to backup the latest data. no need to flash twrp again. just flash su.
take a nandroid backup once (everything system, boot, data) . after successfully flashing su you can keep another backup that contains su.
Click to expand...
Click to collapse
ok, finally! My device is rooted. Thanks a lot!
I think I forgot to select external storage when taking a nandroid, so it went into internal storage, it filled a little more than 5 GB. I can't see this backup neither in TWRP, PC or an android file explorer. How can I get rid of those 5 GB? I take a nandroid on external storage and already copied it in my PC.
Is there a way via TWRP to get rid of it? Wiping something? I'm very cautios from now on.
it's stored at /data/media/twrp delete those backups. or boot into twrp >restore> it'll show all the backups delete those.
edit: Im stuck in the "watery logo" I need help unistalling SU can some1 point me to that guide?
I've already flashed SuperSU 2.62-3
edit 2: I flashed SU 2.65 and it did the trick! solved, i think
original post:
Hi guys hope you can help me
I have a XT1563, single sim. I unlocked bootloader, flashed recovery, went directly to TWRP to flash SuperSU v2.46, it finished, I restarted using TWRP option but hasnt restarted is stuck in the warning screen "Warning bootloader unlocked...your device's bootloader has been unlock...." I do not know what to do
I press power-off and any key combination and it doesnt do anything is just stuck at that warning screen. Unlike the OP I dont get the watery logo
Related
I've been reading something that interested me.
https://www.reddit.com/r/MotoX/comments/2kx2lv/how_do_you_encrypt_a_rooted_moto_x/
Specifically.
I had the same issue today. Booted into safe mode, then I was able to encrypt.
Press power button to get power off popup menu. Press and hold power off. You will get another popup offering to reboot in safe mode.
Safe mode worked. This uncomplicates my process of rooting, unrooting, encrypting, and having issues rerooting after encryption. This is also a crazy easy single step process for an issue that has given me months of headaches.
You shall be the first person ever that I have given gold to.
Thank you so much!
Click to expand...
Click to collapse
I enter my password in the encryption settings menu and hit the Encrypt button
Click to expand...
Click to collapse
How would encryption effect flashing a new rom?
What are your guys thoughts on encryptimg a unlocked and rooted phone?
I do not want to enable it yet till it is comfirmed its ok.
Thanks.
Um I haven't had a problem and I've encrypted the software many times as I have installed many rooms and I always encrypt after setting everything up post root so it should just work without issue. Maybe they just weren't being patient and it can take a bit of time
timde9 said:
Um I haven't had a problem and I've encrypted the software many times as I have installed many rooms and I always encrypt after setting everything up post root so it should just work without issue. Maybe they just weren't being patient and it can take a bit of time
Click to expand...
Click to collapse
What about unencrypting? To say to flash a new kernel or rom?
Well that's an interesting question. I am testing twrp builds from hashbang to try and get encryption fully supported for this device in twrp. Until that time you can actually still flash zips via adb sideload no problem
timde9 said:
Well that's an interesting question. I am testing twrp builds from hashbang to try and get encryption fully supported for this device in twrp. Until that time you can actually still flash zips via adb sideload no problem
Click to expand...
Click to collapse
Ohh. Cool. I'll have to learn adb.
@timde9
I've got twrp installed.
To get to recovrry mode, do I go into recovery mode in twrp and then the recovery button in twrp to install packages m zips from adb?
to install packages via adb is pretty simple really you just open twrp go to advanced menu and open "adb sideload" from there. Then connect your device to your computer install adb and sideload an app with this syntax
"adb sideload ***.zip"
That is radical. Ty for this.
Encryption went like a breeze.
took no more than 20 min. I feel safe now.
timde9 said:
Well that's an interesting question. I am testing twrp builds from hashbang to try and get encryption fully supported for this device in twrp. Until that time you can actually still flash zips via adb sideload no problem
Click to expand...
Click to collapse
Just found out after encrypting twrp fails to mount data to backup. I might restore without encryption. That way I have access to backups on my phone too.
So I am having a problem restoring a backup. Since I cannot decrypt, to get rid of data from being locked down, do I flash with a rom? I am stuck.
Ok I have to do a factory reset. But not sure if this exists and works through twrp. Or if I have to do a factory reset some otherway.
Ok I skipped trying to reinstall rom and did a little searching.
This guy but with a 6P had exact issue.
For me to wipe data I need to
Code:
fastboot format userdata
https://www.reddit.com/r/Nexus6P/comments/3qnzz0/twrp_unable_to_mount_data/
Hitti2 said:
Ok I skipped trying to reinstall rom and did a little searching.
This guy but with a 6P had exact issue.
For me to wipe data I need to
Code:
fastboot format userdata
https://www.reddit.com/r/Nexus6P/comments/3qnzz0/twrp_unable_to_mount_data/
Click to expand...
Click to collapse
Is this ok to do? I don't want mess anything up.
Hitti2 said:
Is this ok to do? I don't want mess anything up.
Click to expand...
Click to collapse
That will erase all your data including files, apps, etc. Anything installed to /system should be untouched.
asuhoops8628 said:
That will erase all your data including files, apps, etc. Anything installed to /system should be untouched.
Click to expand...
Click to collapse
Thanks for confirming this. Exactly what I need when time comes to decrypt "wipe" I will use this.
I wasn't sure if it would delete the partition or wipe, this is why I asked.
Ty.
Hitti2 said:
Thanks for confirming this. Exactly what I need when time comes to decrypt "wipe" I will use this.
I wasn't sure if it would delete the partition or wipe, this is why I asked.
Ty.
Click to expand...
Click to collapse
Upon reading this again, just to be safe, you might want to start with just a fastboot erase. I think format does the same thing, but I have never used it.
Since you would be specifying the partition with both commands, I do not think you are in risk of completely blowing up your user partition if you choose to use fastboot format, but once again, I have always just used fastboot erase.
Hitti2 said:
Ok I skipped trying to reinstall rom and did a little searching.
This guy but with a 6P had exact issue.
For me to wipe data I need to
Code:
fastboot format userdata
https://www.reddit.com/r/Nexus6P/comments/3qnzz0/twrp_unable_to_mount_data/
Click to expand...
Click to collapse
So I went to use this. I got an error.
Code:
Formatting is not supported for filesystem with type 'raw'
So now, that I am guessing, since twrp can now decrypt, I should just be able to go into twrp and do a full wipe and reinstall of the trupurexmm 2.5 And encryption should be gone?
Hitti2 said:
So I went to use this. I got an error.
Code:
Formatting is not supported for filesystem with type 'raw'
So now, that I am guessing, since twrp can now decrypt, I should just be able to go into twrp and do a full wipe and reinstall of the trupurexmm 2.5 And encryption should be gone?
Click to expand...
Click to collapse
Nope. Encryption is still enabled. I flashed trupurexmm 2.5 following
5. How To Install A ROM with TWRP Recovery
Prerequisites: unlocked bootloader, TWRP recovery.
Installing a ROM is a pretty straight forward and easy process. Before you install anything you should make a nandroid backup (instructions above).
Download a ROM and appropriate Gapps package and place on your device.
Boot into your custom recovery.
Perform a full wipe.
Select the wipe option from the TWRP home screen.
Select advanced wipe.
Check the system, data, cache, and dalvik cache options.
Swipe to wipe.
Install the ROM.
Select the install option from the TWRP home screen.
Navigate to where you have the ROM zip stored on your sd card and select it.
Swipe to install.
Most ROMs will run an installer script at this point but some ROMs have what is called an Aroma Installer which allow you to choose some install options before the script runs.
You will also need to install the appropriate gapps package directly after installing the ROM.
Once you've installed all necessary zips you'll have an option to wipe cache/dalvik and an option to reboot system. Wipe the cache/dalvik, hit the back button, and hit the reboot system button.
Click to expand...
Click to collapse
I'm having an issue encrypting. Encryption will not start on my rooted moto x. I factory reset and encrypted, but could not get root working. Flashed everything via adb sideload in twrp but root refueses to work. Any ideas
Sent from my XT1575 using Tapatalk
Ok, I messed up somewhere.
I had Nexus 6p running on MM, rooted along with xposed.
I had downloaded the beta OTA but not installed it.
I used flashfire to flash the old 6p image (the same one that was installed) and flashed system, boot, recovery, cache and vendor.
Then I updated using the downloaded OTA to N. When I did that , the phone showed me the corruption message and booted to recovery. My phone was being detected by adb in normal mode, but not by fastboot in the bootloader, somehow I was able to get it to detect and installed my older TWRP 2.8.7.2 recovery, which was able to decrypt data. After that, I sideloaded Android N via TWRP and even flashed TWRP 3.0.0.1, but it hangs whenever I try to boot to recovery, never been able to go past the TWRP bootlogo. Is there anyway I can get TWRP to work again without wiping data/userdata? I'm guessing it's all happening because of encrypted data.
kunal_07 said:
Ok, I messed up somewhere.
I had Nexus 6p running on MM, rooted along with xposed.
I had downloaded the beta OTA but not installed it.
I used flashfire to flash the old 6p image (the same one that was installed) and flashed system, boot, recovery, cache and vendor.
Then I updated using the downloaded OTA to N. When I did that , the phone showed me the corruption message and booted to recovery. My phone was being detected by adb in normal mode, but not by fastboot in the bootloader, somehow I was able to get it to detect and installed my older TWRP 2.8.7.2 recovery, which was able to decrypt data. After that, I sideloaded Android N via TWRP and even flashed TWRP 3.0.0.1, but it hangs whenever I try to boot to recovery, never been able to go past the TWRP bootlogo. Is there anyway I can get TWRP to work again without wiping data/userdata? I'm guessing it's all happening because of encrypted data.
Click to expand...
Click to collapse
Is there a reason you're messing around with Flashfire and sideloading instead of doing it the proper way via fastboot? I'd suggest taking that route now. I have instructions on flashing factory images in my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Heisenberg said:
Is there a reason you're messing around with Flashfire and sideloading instead of doing it the proper way via fastboot? I'd suggest taking that route now. I have instructions on flashing factory images in my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
I just had a phone next to me at that time, so I thought I'd be able to do it without a pc. Now I know it wasn't a good idea
So you suggest I fastboot flash everything like you've mentioned in the guide without formatting userdata and data? Also, should I flash twrp at that time as well? Do I need the modified boot mentioned in http://forum.xda-developers.com/nexus-6p/general/stock-modified-boot-img-regular-root-t3306684
kunal_07 said:
I just had a phone next to me at that time, so I thought I'd be able to do it without a pc. Now I know it wasn't a good idea
So you suggest I fastboot flash everything like you've mentioned in the guide without formatting userdata and data? Also, should I flash twrp at that time as well? Do I need the modified boot mentioned in http://forum.xda-developers.com/nexus-6p/general/stock-modified-boot-img-regular-root-t3306684
Click to expand...
Click to collapse
Yes, flash everything except userdata. Personally, I'd be wiping data with TWRP first though, just to make sure there's no lingering data causing problems moving forward. You can use Titanium to make a backup of your user apps first, and then restore them afterwards. No you don't need the modified boot.img.
In response to one of your initial statements though, I don't think TWRP is hanging due to not being able to decrypt. The 3.0.0-1 build has been patched so that it can decrypt.
Heisenberg said:
Yes, flash everything except userdata. Personally, I'd be wiping data with TWRP first though, just to make sure there's no lingering data causing problems moving forward. You can use Titanium to make a backup of your user apps first, and then restore them afterwards. No you don't need the modified boot.img.
In response to one of your initial statements though, I don't think TWRP is hanging due to not being able to decrypt. The 3.0.0-1 build has been patched so that it can decrypt.
Click to expand...
Click to collapse
any other way I can do that? I'm not rooted, and I cant flash supersu without booting to recovery, right?
kunal_07 said:
any other way I can do that? I'm not rooted, and I cant flash supersu without booting to recovery, right?
Click to expand...
Click to collapse
Instead of relying on the recovery partition on the phone, you can live-boot TWRP with fastboot. This will boot into TWRP using the TWRP image on your PC, via the fastboot connection. The command is as follows:
Code:
fastboot boot twrp-3.0.0-1-angler.img
Then you can flash SuperSU, make your backup with Titanium, and continue on.
Heisenberg said:
Instead of relying on the recovery partition on the phone, you can live-boot TWRP with fastboot. This will boot into TWRP using the TWRP image on your PC, via the fastboot connection. The command is as follows:
Code:
fastboot boot twrp-3.0.0-1-angler.img
Then you can flash SuperSU, make your backup with Titanium, and continue on.
Click to expand...
Click to collapse
sorry to bug you often, but i had no luck with live booting 3.0.0-1. I tried with 2.8.7.2 and it booted, asked to decrypt data. tried my pin/pattern as well as default_password but no luck.
the log says:
E:Unable to decrypt with default password, you may need to perform a format data.
E:unable to mount storage
E:unable to mount settings storage during GUI startup.
kunal_07 said:
sorry to bug you often, but i had no luck with live booting 3.0.0-1. I tried with 2.8.7.2 and it booted, asked to decrypt data. tried my pin/pattern as well as default_password but no luck.
Click to expand...
Click to collapse
That's odd, I can't think of why 3.0.0-1 wouldn't boot, but 2.8.7.2 definitely won't work as it obviously can't decrypt. You might not be able to backup.
Enabling 'require pattern at startup' allowed 3.0.0-1 to boot but this time it was stuck at decrypting.
kunal_07 said:
Enabling 'require pattern at startup' allowed 3.0.0-1 to boot but this time it was stuck at decrypting.
Click to expand...
Click to collapse
I think you're pretty much stuck, you could try disabling all security.
is it possible to sideload supersu somehow?
kunal_07 said:
is it possible to sideload supersu somehow?
Click to expand...
Click to collapse
Maybe, you could try adb sideload in TWRP, but SuperSU needs to access the data partition which TWRP can't decrypt.
I tried it and it got to
**Boot image patcher**
patching sepolicy.
Failure, aborting.
i seem to have the same issues too. unable to access recovery and lost root. phone cant be detected in fastboot.
supersu 2.69 to the rescue. chainfire auto root worked with encrypted data
1)So, now the best way forward is to backup via Titanium and format data?
2) will fastboot erase data erase userdata as well?
3) after the format, will data remain decrypted or do I need to do something else?
kunal_07 said:
supersu 2.69 to the rescue. chainfire auto root worked with encrypted data
1)So, now the best way forward is to backup via Titanium and format data?
2) will fastboot erase data erase userdata as well?
3) after the format, will data remain decrypted or do I need to do something else?
Click to expand...
Click to collapse
Great news
1. Yes.
2. I don't think such a command exists. You'd need to use the "fastboot format userdata" command instead if you want to decrypt anyway. Just remember to backup all your data first.
3. You'd need to flash a custom kernel today doesn't force encryption. Otherwise your data well will automatically encrypt on the first boot after formatting.
kunal_07 said:
supersu 2.69 to the rescue. chainfire auto root worked with encrypted data
1)So, now the best way forward is to backup via Titanium and format data?
2) will fastboot erase data erase userdata as well?
3) after the format, will data remain decrypted or do I need to do something else?
Click to expand...
Click to collapse
Is there a link for the CF Auto root?
I tried searching, but didn't find anything =(
kauemelhado said:
Is there a link for the CF Auto root?
I tried searching, but didn't find anything =(
Click to expand...
Click to collapse
http://forum.xda-developers.com/apps/supersu/wip-android-n-preview-t3335726
kunal_07 said:
http://forum.xda-developers.com/apps/supersu/wip-android-n-preview-t3335726
Click to expand...
Click to collapse
Tks,
I found it 2 seconds later I asked you. LOL
Anyhow, thank you bro.
Hi,
I have G935F, installed TWRP 3.0.0.0 and rooted, WITHOUT wiping. System boots correctly, but I cannot do factory reset or wipe with TWRP, because I got some messages like "Cannot mount Data" and "Failed crypto loader". I understand that it has to do with encryption. Can someone please enlight me, and give me tips about the issue?
Thank you
Polemos82 said:
Hi,
I have G935F, installed TWRP 3.0.0.0 and rooted, WITHOUT wiping. System boots correctly, but I cannot do factory reset or wipe with TWRP, because I got some messages like "Cannot mount Data" and "Failed crypto loader". I understand that it has to do with encryption. Can someone please enlight me, and give me tips about the issue?
Thank you
Click to expand...
Click to collapse
You have to download dm-verity and force encryption disabler from here , put it to SD card, reboot into TWRP, FORMAT DATA (not wipe) and flash that file (dm-verity and force encryption disabler). All your data will be erased.
No way to unencrypt without loosing you data for the moment(
"All your data will be erased" means that after boot I'll find a clean system installation (as factory reset)?
I hope not to be posing stupid questions, I'm completely new to this world
Thank you very much
Yes just as a factory reset
Sent from my SM-G935W8 using Tapatalk
Ok, thank you all!!! ???
s it very important to wipe data?
Can I first flash the twrp ,second back up the rom by TWRP recovery
and then after factory reset ,I restore thw rom by twrp??
IS IT possible?
AGU PENG said:
Can I first flash the twrp ,second back up the rom by TWRP recovery
and then after factory reset ,I restore thw rom by twrp??
IS IT possible?
Click to expand...
Click to collapse
No, you cannot perform a backup, because your data is encrypted by default and the only way to disable it is to format your data.
I have a unique problem. I have a HTC Desire 612 from Verizon and I decided to revive it to playe PoGo. But it was stuck in a boot loop and I couldn't get any custom ROM.
Finally a gentle soul here gave me the stock rom and I flashed it vide TWRP and played PoGo for weeks. Then yesterday the phone bro led and when it came up it was stuck in a boot loop.
So I decided to flash the stock ROM again. But before that I tried to factory reset. I could go to TWRP, select wipe data, enter yes and the wiping was successful, then clear dalvic and cache and system beforehand finally I flashed the stock ROM.
Surprise surprise is NOTHING happens. The phone boots without the apps telling me they are installing. Then I get back the exact same data in my phone including my selected wallpaper and apps. Before I can do anything the phone restarts.
Point is wiping and restoring the stock ROM does NOTHING to the phone yet the processes are successful. Can somebody help?
vooks said:
I have a unique problem. I have a HTC Desire 612 from Verizon and I decided to revive it to playe PoGo. But it was stuck in a boot loop and I couldn't get any custom ROM.
Finally a gentle soul here gave me the stock rom and I flashed it vide TWRP and played PoGo for weeks. Then yesterday the phone bro led and when it came up it was stuck in a boot loop.
So I decided to flash the stock ROM again. But before that I tried to factory reset. I could go to TWRP, select wipe data, enter yes and the wiping was successful, then clear dalvic and cache and system beforehand finally I flashed the stock ROM.
Surprise surprise is NOTHING happens. The phone boots without the apps telling me they are installing. Then I get back the exact same data in my phone including my selected wallpaper and apps. Before I can do anything the phone restarts.
Point is wiping and restoring the stock ROM does NOTHING to the phone yet the processes are successful. Can somebody help?
Click to expand...
Click to collapse
HTC?? Wrong thread.
B3311 said:
HTC?? Wrong thread.
Click to expand...
Click to collapse
It really is about TWRP failing to wipe
hello all
i have ZTE AXON 7 U model.
i did bootloader unloock and instaled TWRP 3041 and did this "Once you booted to TWRP , Tap Mount and Check "Mount, System as Read-only", this is very important".
now im on the A2017UV1.1.0B15_systemstock_by_DrakenFX.zip. all works great.
in twrp when i do backup and want to restore it i get this massage: " cannot restore system--mounted read only".
how can i backup and restore in the wright way?
ty all
le011 said:
hello all
i have ZTE AXON 7 U model.
i did bootloader unloock and instaled TWRP 3041 and did this "Once you booted to TWRP , Tap Mount and Check "Mount, System as Read-only", this is very important".
now im on the A2017UV1.1.0B15_systemstock_by_DrakenFX.zip. all works great.
in twrp when i do backup and want to restore it i get this massage: " cannot restore system--mounted read only".
how can i backup and restore in the wright way?
ty all
Click to expand...
Click to collapse
"Mount and Check "Mount, System as Read-only", this is very important".
What you have quoted is only to complete the installation Flash. Go ahead and uncheck 'Mount System Read-Only' for normal operation and you are ready to go!
amphi66 said:
"Mount and Check "Mount, System as Read-only", this is very important".
What you have quoted is only to complete the installation Flash. Go ahead and uncheck 'Mount System Read-Only' for normal operation and you are ready to go!
Click to expand...
Click to collapse
To for your replay.
When I unchecked the System read only and trying to restore the phone from the backup I made in Twrp the phone stucks after reboot on the screen that says the bootloader is unlocked and that's it.
le011 said:
To for your replay.
When I unchecked the System read only and trying to restore the phone from the backup I made in Twrp the phone stucks after reboot on the screen that says the bootloader is unlocked and that's it.
Click to expand...
Click to collapse
You should see that screen and the phone should continue to boot after 5 seconds.
To recap:
1. You stated all was fine in B15 after following the upgrade steps.
2. You made a TWRP backup (system, data & boot) of your new B15
3. When attempting to TWRP restore the B15 backup it could not as system was still mounted "read only"
4. You unchecked "read only" and then did the restore
5. Now system does not boot (hangs on bootloader unlocked warning screen)
If that is correct it sounds as if you have a bad or incomplete B15 backup or you are attempting to restore a B29 backup to a B15 bootstack.
amphi66 said:
You should see that screen and the phone should continue to boot after 5 seconds.
To recap:
1. You stated all was fine in B15 after following the upgrade steps.
2. You made a TWRP backup (system, data & boot) of your new B15
3. When attempting to TWRP restore the B15 backup it could not as system was still mounted "read only"
4. You unchecked "read only" and then did the restore
5. Now system does not boot (hangs on bootloader unlocked warning screen)
If that is correct it sounds as if you have a bad or incomplete B15 backup or you are attempting to restore a B29 backup to a B15 bootstack.
Click to expand...
Click to collapse
All correct.
After Im making backup, I'm wiping, and trying to restore the backup I just did.
No luck.
le011 said:
All correct.
After Im making backup, I'm wiping, and trying to restore the backup I just did.
No luck.
Click to expand...
Click to collapse
Confusing to me. How are you using phone after a bad restore?
What revision TWRP did you flash? Did you flash SU 2.79 after flashing ROM?
Perhaps someone w/ more knowledge can chime in, but sounds as if you are a candidate to begin again following the steps carefully
Goodluck
amphi66 said:
Confusing to me. How are you using phone after a bad restore?
What revision TWRP did you flash? Did you flash SU 2.79 after flashing ROM?
Perhaps someone w/ more knowledge can chime in, but sounds as if you are a candidate to begin again following the steps carefully
Goodluck
Click to expand...
Click to collapse
hi
i have TWRP version 3041.
after i'm trying to restore and wont succeeded , i flash the rom again. the rom im flashing is : A2017UV1.1.0B15_systemstock_by_DrakenFX.
then the phone boot up and work great.
im not flashing supersu because i dont want root.
le011 said:
hi
i have TWRP version 3041.
after i'm trying to restore and wont succeeded , i flash the rom again. the rom im flashing is : A2017UV1.1.0B15_systemstock_by_DrakenFX.
then the phone boot up and work great.
im not flashing supersu because i dont want root.
Click to expand...
Click to collapse
Interesting. How long are you waiting on the Bootloader unlocked warning screen?
Next time in TWRP look at the data partition and verify it is formatted as ext4 not f2fs. I might also download a different version of TWRP and reflash the IMG file from within TWRP. I reference @DrakenFX here as he may have the easy solution.
amphi66 said:
Interesting. How long are you waiting on the Bootloader unlocked warning screen?
Next time in TWRP look at the data partition and verify it is formatted as ext4 not f2fs. I might also download a different version of TWRP and reflash the IMG file from within TWRP. I reference @DrakenFX here as he may have the easy solution.
Click to expand...
Click to collapse
How i check in TWRP how the data partition formated?
I trayid the new version of TWRP 3100 and same thing.
after restoring the phone stuck on the Bootloader unlocked warning screen -last time i waited for 5 min before i
shut down whit power button.
le011 said:
hi
i have TWRP version 3041.
after i'm trying to restore and wont succeeded , i flash the rom again. the rom im flashing is : A2017UV1.1.0B15_systemstock_by_DrakenFX.
then the phone boot up and work great.
im not flashing supersu because i dont want root.
Click to expand...
Click to collapse
amphi66 said:
Interesting. How long are you waiting on the Bootloader unlocked warning screen?
Next time in TWRP look at the data partition and verify it is formatted as ext4 not f2fs. I might also download a different version of TWRP and reflash the IMG file from within TWRP. I reference @DrakenFX here as he may have the easy solution.
Click to expand...
Click to collapse
Easy fix, go back to TWRP,
* Wipe Data (if you are in different ROM a or version) - Dalvik- Cache
* Check MOUNT SYSTEM AS READ-ONLY
* Reflash B15 system
Happy reboot
If you Previously were using B15 , you may restore data only, other wise is a no go.
DrakenFX said:
Easy fix, go back to TWRP,
* Wipe Data - Dalvik- Cache
* Check MOUNT SYSTEM AS READ-ONLY
* Reflash B15 system
Happy rebokt
Click to expand...
Click to collapse
hi
i did that for 3 tomes ending whit the same result :
the rom working great after clean instal...restoring from TWRP....ending whit stuck phone.
le011 said:
How i check in TWRP how the data partition formated?
I trayid the new version of TWRP 3100 and same thing.
after restoring the phone stuck on the Bootloader unlocked warning screen -last time i waited for 5 min before i
shut down whit power button.
Click to expand...
Click to collapse
You may not have seen this on another thread with a similar issue:
"did find something else out. Under [TWRP] settings, if I enabled the "Use rm -rf instead of formatting", then I can restore successfully."
Goodluck
amphi66 said:
You may not have seen this on another thread with a similar issue:
"did find something else out. Under [TWRP] settings, if I enabled the "Use rm -rf instead of formatting", then I can restore successfully."
Goodluck
Click to expand...
Click to collapse
OK ty
i will try that and post if sucssed.
I used Flashfire to flash a radio.img without checking flash bootloader.
I can get into the bootloader and twrp.
When wiping the device and flashing another rom or restoring a backup my 6p does not get passed the custom rom splash screen.
I was thinking of trying to fastboot flash system/data/cache of the March update and see if it boots.
I know I messed up. don't even know if it was because I didn't check the bootloader option in Flashfire. Just my guess because everything was working fine beforehand.
Any help or ideas would be welcome.
dirtyreturn said:
I used Flashfire to flash a radio.img without checking flash bootloader.
I can get into the bootloader and twrp.
When wiping the device and flashing another rom or restoring a backup my 6p does not get passed the custom rom splash screen.
I was thinking of trying to fastboot flash system/data/cache of the March update and see if it boots.
I know I messed up. don't even know if it was because I didn't check the bootloader option in Flashfire. Just my guess because everything was working fine beforehand.
Any help or ideas would be welcome.
Click to expand...
Click to collapse
Hey... You said you wiped your device? What did you wipe in TWRP?
Try to install a ROM from TWRP. Once it's over go in wipe and do a factory reset. Reboot. It should likely fix your issue.
Good luck...
5.1 said:
Hey... You said you wiped your device? What did you wipe in TWRP?
Try to install a ROM from TWRP. Once it's over go in wipe and do a factory reset. Reboot. It should likely fix your issue.
Good luck...
Click to expand...
Click to collapse
Hey thanks for the reply.
Yeah, I wiped data, system, cache. Just the standard - I still have internal storage intact.
Its just strange, I've used Flashfire before but not for flashing a radio and it worked out fine.
I am on 3.79 and used Flashfire to flash 3.78. Went to the bootloader just to check and it still shows 3.79. Just my fault . I didn't check flash bootloader in the Flashfire settings. Atleast that's what I am guessing. Things were just fine before
Sent from my LG-E980 using Tapatalk
dirtyreturn said:
Hey thanks for the reply.
Yeah, I wiped data, system, cache. Just the standard - I still have internal storage intact.
Its just strange, I've used Flashfire before but not for flashing a radio and it worked out fine.
I am on 3.79 and used Flashfire to flash 3.78. Went to the bootloader just to check and it still shows 3.79. Just my fault . I didn't check flash bootloader in the Flashfire settings. Atleast that's what I am guessing. Things were just fine before
Click to expand...
Click to collapse
Well, if nothing work, maybe backup your internal storage and flash a factory image... Then in recovery do a factory reset afterward. Who knows. Going back to stock shouldn't hurt anyway.
Good luck...
@dirtyreturn
I've used FF to flash only radio files to the modem partition many times without issue. You untick all but modem, and you untick inject SU and preserve recovery. Not sure what went wrong for you. As mentioned , you should be able to manually flash stock and if you're careful, you'll still have your data. All your settings will be reset, but the userdata will be there. You can even use flash-all.bat, but open it in a text editor and remove the "-w" flag so it will not wipe your userdata. The Google page where you get the full factory image will have instructions.
v12xke said:
@dirtyreturn
I've used FF to flash only radio files to the modem partition many times without issue. You untick all but modem, and you untick inject SU and preserve recovery. Not sure what went wrong for you. As mentioned , you should be able to manually flash stock and if you're careful, you'll still have your data. All your settings will be reset, but the userdata will be there. You can even use flash-all.bat, but open it in a text editor and remove the "-w" flag so it will not wipe your userdata. The Google page where you get the full factory image will have instructions.
Click to expand...
Click to collapse
Thanks. It was obviously my fault somehow.
I do remember there being only one option to tick.
Using fastboot back to stock did the trick and made me realize maybe I should hold off on using Flashfire for a bit.
Sent from my Nexus+6P using Tapatalk
dirtyreturn said:
Thanks. It was obviously my fault somehow.
I do remember there being only one option to tick.
Using fastboot back to stock did the trick and made me realize maybe I should hold off on using Flashfire for a bit.
Click to expand...
Click to collapse
Nah, FF is awesome and a major time-saver. Just read up on the documentation here and become familiar with it.