Long story short, flashed an asop rom, data didn't work, tried to flash back, still cant get data to work.
I don't have an EFS backup...
Flashed dirty santa stock rom to try and get data working...no go.
would this work? http://www.theandroidsoul.com/fix-e...d-wifibluetooth-issues-restoring-twrp-backup/
Hey man, I just didn't wanna clog up the other thread. The OP gets a notification for every post, and it's also against the rules.
So...
1. Do a full wipe. Data, system, Dalvik, cache
2. Flash stock based rom. OBAR is what I used to grab EFS backup
3. If calls and data aren't working, go to updates in settings and try to do a profile update. This should restore your carrier.
4. Do a EFS backup in recovery.
5. Full wipe
6. Install new rom.
7. Do full rom setup.
8. Reboot into recovery and restore EFS
repeat step 8 until calls work in the new rom
holypuma said:
Hey man, I just didn't wanna clog up the other thread. The OP gets a notification for every post, and it's also against the rules.
So...
1. Do a full wipe. Data, system, Dalvik, cache
2. Flash stock based rom. OBAR is what I used to grab EFS backup
3. If calls and data aren't working, go to updates in settings and try to do a profile update. This should restore your carrier.
4. Do a EFS backup in recovery.
5. Full wipe
6. Install new rom.
7. Do full rom setup.
8. Reboot into recovery and restore EFS
repeat step 8 until calls work in the new rom
Click to expand...
Click to collapse
yea no problem, makes sense.
OBAR Rom and kernel or just the rom?
I used schwifty kernel, but I doubt that makes a difference.
holypuma said:
I used schwifty kernel, but I doubt that makes a difference.
Click to expand...
Click to collapse
i flashed the dirty santa stock rom, did the activation each time i restarted it. After about 8 restarts and trying to activate, i finally have data.
I did try running these commands, although i got "no space left" when running it. However, the next reboot, it finally activated.
adb shell 'dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1'
adb shell 'dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2'
adb reboot
Going to back up EFS, and go from there. Will update shortly.
BTW, thank you so much for your help!
Awesome! Getting the aosp rom running should be easy
solson20 said:
i flashed the dirty santa stock rom, did the activation each time i restarted it. After about 8 restarts and trying to activate, i finally have data.
I did try running these commands, although i got "no space left" when running it. However, the next reboot, it finally activated.
adb shell 'dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1'
adb shell 'dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2'
adb reboot
Going to back up EFS, and go from there. Will update shortly.
BTW, thank you so much for your help!
Click to expand...
Click to collapse
Glad you got it working.
Sent from my LG-LS997 using Tapatalk
rootlinux said:
Glad you got it working.
Sent from my LG-LS997 using Tapatalk
Click to expand...
Click to collapse
All is good now. Restored EFS on the Desolation ROM.
Thanks again!!!!!!!!!
solson20 said:
All is good now. Restored EFS on the Desolation ROM.
Thanks again!!!!!!!!!
Click to expand...
Click to collapse
Anytime
Sent from my LG-LS997 using Tapatalk
Related
Hello to all,
as one can easily deduce from the title I would need a guide with all the steps you can take to upgrade from the version of Paranoid Android 3.99 RC2 to the latest version 4.4 RC2.
I wanted to wait for it to come out of beta before flashing the new version but now I do not know if I need new bootloader and radio or make other steps introduced with the new versions of the PA.
Can someone guide me with the steps to follow to make this switch?
Thanks in advance for the answers.
PS: Sorry for my bad English.
make a nandroid backup in recovery, then dirty flash it over the previous version and also flash the gapps. if you have issues, wipe data and reflash everything.
Piota said:
Hello to all,
as one can easily deduce from the title I would need a guide with all the steps you can take to upgrade from the version of Paranoid Android 3.99 RC2 to the latest version 4.4 RC2.
I wanted to wait for it to come out of beta before flashing the new version but now I do not know if I need new bootloader and radio or make other steps introduced with the new versions of the PA.
Can someone guide me with the steps to follow to make this switch?
Thanks in advance for the answers.
PS: Sorry for my bad English.
Click to expand...
Click to collapse
Hiya Piota
basically:
1. Backup ur data
2. reboot into bootloader
3. Download and Flash the latest 2 files Radio , Bootloader
4. boot into recovery factory reset and format system
5. flash the rom and gapps.
new radio or bootloader is not needed if you dont want it.
nightmare911 said:
Hiya Piota
basically:
1. Backup ur data
2. reboot into bootloader
3. Download and Flash the latest 2 files Radio , Bootloader
4. boot into recovery factory reset and format system
5. flash the rom and gapps.
Click to expand...
Click to collapse
Can I flash radio and bootloader from the recovery?
If I factory reset and format system have I to reinstall all the apps?
PS: Thank you!
Piota said:
Can I flash radio and bootloader from the recovery?
If I factory reset and format system have I to reinstall all the apps?
PS: Thank you!
Click to expand...
Click to collapse
you can flash them in recovery, yes.
yes, wiping data/factory reset will get rid of all your apps and data.
simms22 said:
you can flash them in recovery, yes.
yes, wiping data/factory reset will get rid of all your apps and data.
Click to expand...
Click to collapse
I have done a bkp, then I've flashed radio and bootloader, than I've done wipe and format but now how can I flash something if I can't put the image in the phone (because there isn't an OS)?
Piota said:
I have done a bkp, then I've flashed radio and bootloader, than I've done wipe and format but now how can I flash something if I can't put the image in the phone (because there isn't an OS)?
Click to expand...
Click to collapse
why did you wipe the os? youll need to adb push a rom to your device now or flash the factory img and reroot. OR, restore your backup. thats why i wrote to dirty flash the rom first, you most likely would have been fine and had no data loss. second choice would be to wipe fdata and flash, where you would lose data. the last option is to wipe the os off your phone, only if you have serious issues.
edit. if you wiped all from your phone that means you cleared your backup as well.
simms22 said:
why did you wipe the os? youll need to adb push a rom to your device now or flash the factory img and reroot. OR, restore your backup. thats why i wrote to dirty flash the rom first, you most likely would have been fine and had no data loss. second choice would be to wipe fdata and flash, where you would lose data. the last option is to wipe the os off your phone, only if you have serious issues.
edit. if you wiped all from your phone that means you cleared your backup as well.
Click to expand...
Click to collapse
How can I restore the bkp if I can't put the bkp in the phone?
I have to push with ADB how can I do that?
search google "how to adb push a rom", or if youre using twrp you can search also search adb sideload. lots of links will come up.
Problem solved! Thank you all! I've just done an "adb push".
Piota said:
Problem solved! Thank you all! I've just done an "adb push".
Click to expand...
Click to collapse
sweet
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
Hello,
so i backup my phone before i do anything risky. so i was trying to restore my phone (from yesterday backup) using twrp. everything went perfect and when my device rebooted after restore. it stuck on Google Logo. i tried 3 times but no luck. any help? i select Boot, Data, System, System.img
EDIT: should i select vendor / vendor.img ?? while restoring it ?
UPDATE: when i tried 4th time. my phone rebooted after about 72% and stuck on google logo.
Tried clearing cache? Also, what things did you precisely backup?
DJBhardwaj said:
Tried clearing cache? Also, what things did you precisely backup?
Click to expand...
Click to collapse
almost everything including vendor ; no cache
setul34 said:
almost everything including vendor ; no cache
Click to expand...
Click to collapse
I had the same issue when I backed up system image.
DJBhardwaj said:
I had the same issue when I backed up system image.
Click to expand...
Click to collapse
okay so any solution?
Try it without the system image.
DJBhardwaj said:
Try it without the system image.
Click to expand...
Click to collapse
i did but that did not install root / apps / settings. basically i just got data and stock rom.
setul34 said:
i did but that did not install root / apps / settings. basically i just got data and stock rom.
Click to expand...
Click to collapse
No idea, I myself haven't tried further.
Lets see if someone else comes up with something
setul34 said:
Hello,
so i backup my phone before i do anything risky. so i was trying to restore my phone (from yesterday backup) using twrp. everything went perfect and when my device rebooted after restore. it stuck on Google Logo. i tried 3 times but no luck. any help? i select Boot, Data, System, System.img
EDIT: should i select vendor / vendor.img ?? while restoring it ?
UPDATE: when i tried 4th time. my phone rebooted after about 72% and stuck on google logo.
Click to expand...
Click to collapse
Let me guess you are on TWRP 3.0.0.0?
Yes
oneandroidnut said:
Let me guess you are on TWRP 3.0.0.0?
Click to expand...
Click to collapse
@oneandroidnut Yes.
setul34 said:
@oneandroidnut Yes.
Click to expand...
Click to collapse
You don't backup system image, only backup system, data, and boot.
setul34 said:
@oneandroidnut Yes.
Click to expand...
Click to collapse
pm me if you are still having issues we can go to hangouts or something and i can walk you through
oneandroidnut said:
pm me if you are still having issues we can go to hangouts or something and i can walk you through
Click to expand...
Click to collapse
It'd be much better if you did this here, that way the solution is available for others to find, that's pretty much the entire point of the Q&A section. I'm confident it's just a case of selecting the wrong partitions to backup anyway.
Heisenberg said:
It'd be much better if you did this here, that way the solution is available for others to find, that's pretty much the entire point of the Q&A section. I'm confident it's just a case of selecting the wrong partitions to backup anyway.
Click to expand...
Click to collapse
The solution i used when i incorrectly updated vendor image and then tried to restore old system image and vendor image was to use Nexus Tool kit by wugs fresh to flash back to stock while keeping internal card intact. Then flash the rom you were on with correct vendor image in TWRP 3.0.0.0 and then restore your twrp backup without the vendor image etc and boom should be back to normal. At least that is what worked for me. What should you backup and restore? I back up everything and restore everything but vendor stuff. any suggestions?
oneandroidnut said:
The solution i used when i incorrectly updated vendor image and then tried to restore old system image and vendor image was to use Nexus Tool kit by wugs fresh to flash back to stock while keeping internal card intact. Then flash the rom you were on with correct vendor image in TWRP 3.0.0.0 and then restore your twrp backup without the vendor image etc and boom should be back to normal. At least that is what worked for me. What should you backup and restore? I back up everything and restore everything but vendor stuff. any suggestions?
Click to expand...
Click to collapse
That seems over-complicated. You only need to backup/restore system, data, and boot. Vendor is optional if you have Layers that you want to keep. Don't backup/restore system image or vendor image. That's the reason he got into this mess, be backed up and restored system image. I posted the solution a couple of posts back.
okay so i tried to recover Data System Boot, still didn't work. so i remove everything including twrp and installed stock rom. and then i installed twrp 3.0 and somehow it worked and my device is back on
oneandroidnut said:
The solution i used when i incorrectly updated vendor image and then tried to restore old system image and vendor image was to use Nexus Tool kit by wugs fresh to flash back to stock while keeping internal card intact. Then flash the rom you were on with correct vendor image in TWRP 3.0.0.0 and then restore your twrp backup without the vendor image etc and boom should be back to normal. At least that is what worked for me. What should you backup and restore? I back up everything and restore everything but vendor stuff. any suggestions?
Click to expand...
Click to collapse
this worked for me thankyou
Heisenberg said:
That seems over-complicated. You only need to backup/restore system, data, and boot. Vendor is optional if you have Layers that you want to keep. Don't backup/restore system image or vendor image. That's the reason he got into this mess, be backed up and restored system image. I posted the solution a couple of posts back.
Click to expand...
Click to collapse
i won't make that mistake again to backup vendor or system image.
Thanks @oneandroidnut @Heisenberg
setul34 said:
okay so i tried to recover Data System Boot, still didn't work. so i remove everything including twrp and installed stock rom. and then i installed twrp 3.0 and somehow it worked and my device is back on
this worked for me thankyou
i won't make that mistake again to backup vendor or system image.
Thanks @oneandroidnut @Heisenberg
Click to expand...
Click to collapse
No problem man glad it worked!!
I had the same problem.
I tried to restore a backup (MMB29Q - system+data+boot, done after installing the last factory image without root) and I got blocked on the Google logo. I tried twice without managing.
In the end I solved the problem installing supersu v2.68 zip before restarting.
It's as though the restore needs the root to work properly.
What do you think?
Thanks.
Hello everyone! I bring news from the TWRP developers from the #TWRP IRC channel! TWRP 3.0.2-1 has a fatal bug! If you backup and restore EFS it will brick you! Do not backup and restore EFS on 3.0.2-1! Use 3.0.2-0 instead! This has already been fixed in the newer builds!
If you have been bricked you NEED to Erase the EFS partitions and that will fix it immediately.
For the Nexus 6P go to TWRP. Then on PC Open Command Prompt with access to ADB ( Android Debug Bridge) and execute the following commands:
ADB shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst1 bs=16384
and
ADB Shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst2 bs=16384
This should fix it for ANY Nexus 6P users. Users on other phones with the same problem await instructions!
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
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.