Related
Firstly, my nexus one is Locked + Rooted with Stock FRF91.
OK, So I rooted with 1-click, installed a custom recovery (first Clockwork then Amon RA 1.8.0.0).
Did a full backup
Tried out a couple of Roms
Reverted to Stock from backup. All good!
Now 1 week later, I really want to try MiUI Rom so I power on phone with VOL-, select Recovery - all I see is the yellow exclamation in a white triangle with a green Android below. Isn't that normal / stock recovery???
Could the FRG83 OTA that I have not installed (it is still bugging me to do so ) have restored the stock recovery?
Did I clear something / do something wrong when performing the Stock backup or restore?
TIA for any advice.
The OTA update did install, and in the process replaced install-recovery.sh and recovery-from-boot.p, which meant that the stock recovery was automatically reinstalled by the OS on reboot.
Hi rusty, thanks for the reply. I have not installed the update, it is still asking to be installed. I even checked the build number in about phone - frf91.
Are you saying that with out my explicit permission the ota has modified my phone and restored the stock recovery - that certainly would explain it.
I misread your post, sorry about that.
However, restoring your backup is probably the cause, due to the same reasons above.
To simplify, you can lose your recovery in this fashion:
Start with stock ROM
Root
Install custom recovery without removing the .sh and .p files mentioned
Boot up phone
Now, if you install custom recovery using several automated methods, OR manually remove the files previously mentioned in thread, no problem. But if those files remain the stock ROM will automatically run them and restore the recovery image. Happens to a lot of people.
So likely that's what happened; restoring and using your stock ROM had those scripts in the image.
khaytsus said:
To simplify, you can lose your recovery in this fashion:
Start with stock ROM
Root
Install custom recovery without removing the .sh and .p files mentioned
Boot up phone
Now, if you install custom recovery using several automated methods, OR manually remove the files previously mentioned in thread, no problem. But if those files remain the stock ROM will automatically run them and restore the recovery image. Happens to a lot of people.
So likely that's what happened; restoring and using your stock ROM had those scripts in the image.
Click to expand...
Click to collapse
Thankyou both for your help. It makes a bit more sense now.
So in order to get back to a custom recovery, will I need to reinstall it or will removing these .sh and .p files do the trick?
Ps, what is the exact location of these and how would I delete them (i assume they are system/ protected)
Thanks, Steve.
You'll have to remove/rename the files and flash it again.
They are: /system/recovery-from-boot.p and /system/etc/install-recovery.sh
You could rename them:
Code:
mv /system/recovery-from-boot.p /system/recovery-from-boot.p.bak
mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
or remove them altogether
Code:
rm /system/recovery-from-boot.p
rm /system/etc/install-recovery.sh
My advice would be to rename, just incase you feel like stock recovery again at some point.
Rusty! said:
You'll have to remove/rename the files and flash it again.
They are: /system/recovery-from-boot.p and /system/etc/install-recovery.sh
You could rename them:
Code:
mv /system/recovery-from-boot.p /system/recovery-from-boot.p.bak
mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
Click to expand...
Click to collapse
Perfect. Understood.
I'll try to remember to update this thread with how I get on once i'm done but even if I dont, I think the info contained is pretty clear.
Thanks Rusty & khaytsus.
Also I'm pretty sure that if you use ROM Manager to flash custom recovery, it automatically zaps the files that would otherwise revert you to stock recovery.
Sent from my Nexus One using XDA App
I did use rom manager and I have since done clockworkmod through rom manager but when I go into recovery I get the stock one. that's why I did the manual process installing ra after clockwork the first time round.
Anyone else has that where rom manager seems to install the custom recovery but then when you go there its stock?
this is how i did it anyways. i had to flash the boot.img and update via stock recovery to get the ota to flash. but then no root!
so heres how i got it back:
download the superboot/paulobrien method (http://forum.xda-developers.com/showthread.php?t=882333).
boot phone to fastboot.
Code:
fastboot boot boot.superboot.img
let phone boot, open terminal, su, just to check.
reboot phone.
rooted and ota'd now!
I've got root back, but not by that method. I think it might be a mistake to flash that boot.img, as the 2.3.1 update patched boot.img... so replacing it with one from 2.3 might not be the best idea. But I guess no one really know what the changes might be.
I guess time will tell
The method I used was:
1. Boot into fastboot.
2.
Code:
fastboot flash recovery recovery-clockwork-3.0.0.0-crespo.img
3. Reboot from fastboot directly into recovery (not doing so will cause android to replace CWR).
4. Mount USB, copy su-2.3.6.1-ef-signed.zip to the /sdcard via windows/linux
5. Mount /system
6. Install update from zip (browse to were you put su-2.3.6.1-ef-signed.zip).
7. Install it, and reboot.
8. open root explorer, and rename /etc/install-recovery.sh to install-recovery.sh.old
9. open ROM Manager, reflash CWR.
now you are all done, rooted, w/ CWR
I reflashed CWM, then from CWM, remounted /system, then used adb to chmod 6775 su. That restored root pretty easily.
What Recovery image are you using? Are you able to get into it consistently? I can't from fastboot except for if I immediately hit it up after flashing CWM with fb, or from ROM Manager (flash from RM, then select reboot to recovery).
Luxferro said:
I've got root back, but not by that method. I think it might be a mistake to flash that boot.img, as the 2.3.1 update patched boot.img... so replacing it with one from 2.3 might not be the best idea. But I guess no one really know what the changes might be.
I guess time will tell
Click to expand...
Click to collapse
its not flashing it. read the command. its only booting to that image to install su. then reboot will bring you back to stock 2.3.1 boot.img.
distortedloop said:
I reflashed CWM, then from CWM, remounted /system, then used adb to chmod 6775 su. That restored root pretty easily.
What Recovery image are you using? Are you able to get into it consistently? I can't from fastboot except for if I immediately hit it up after flashing CWM with fb, or from ROM Manager (flash from RM, then select reboot to recovery).
Click to expand...
Click to collapse
im using stock recovery.
I'm rooted on 2.3.1 but I lose clockwork recovery when I reboot an gota reflash it using rom manager. Anyone having this problem
k0mpresd said:
its not flashing it. read the command. its only booting to that image to install su. then reboot will bring you back to stock 2.3.1 boot.img.
Click to expand...
Click to collapse
Sure it is. But on Android bootup, a script is running somewhere to replace it with stock recovery. They did this on Droid_1 after the first or second update (that's my only other android phone... so my android experience is limited).
edit: I just found the script. It's /etc/install-recovery.sh .... just renamed my to install-recovery.sh.old. gonna reflash CWR and test it now.
edit2: yep, works great now. CWR, and retained my 2.3.1 boot.img
So is this something that the devs of clockworkmod need to fix in order to not lose clockwork recovery when u reboot the phone
chris6278 said:
So is this something that the devs of clockworkmod need to fix in order to not lose clockwork recovery when u reboot the phone
Click to expand...
Click to collapse
No, it's a safety mechanism so you can't lose recovery... It has nothing to do with clockworkmod. Someone can make a root script or app that disables it easily. Or people can just do it themselves manually.
edit: actually, all that needs to be done is add some code to the update script inside su-2.3.6.1-ef-signed.zip so when it installs the update, it renames install-recovery.sh
distortedloop said:
I reflashed CWM, then from CWM, remounted /system, then used adb to chmod 6775 su. That restored root pretty easily.
What Recovery image are you using? Are you able to get into it consistently? I can't from fastboot except for if I immediately hit it up after flashing CWM with fb, or from ROM Manager (flash from RM, then select reboot to recovery).
Click to expand...
Click to collapse
I want to attempt to restore my root by using your method. But I'm lost at the part when you use adb chomd 6775 su,
When I go into adb, do i just type chomd 6775 su? Do I have to download something else to use this? Please explain, thanks
If u dont mind can u please provide the instructions on how to do it manually. Id really appreciate it. Sorry im a noob lol
Where in root explorer do i need to rename
Where in root explorer do i rename it
plmiller0905 said:
I want to attempt to restore my root by using your method. But I'm lost at the part when you use adb chomd 6775 su,
When I go into adb, do i just type chomd 6775 su? Do I have to download something else to use this? Please explain, thanks
Click to expand...
Click to collapse
chmod needs to be done at a # prompt.
chris6278 said:
Where in root explorer do i rename it
Click to expand...
Click to collapse
I'm trying not to be rude... but if you can post in this thread, you can read it to. Before you asked your question a couple different step by step posts outlined all you need to know.... and this thread is only 2 pages...
Is it just me or does adb remount no longer work?
If I use the old koush rootboot.img it works, but no wifi, if I use the stock boot.img, I get no wifi but am able to remount.
I can read an ive done all the steps u posted but my ? Is where in root explorer do i find /etc/install-recovery.sh so i can rename it? Im learning this as i go so excuse me if i sound stupid sometimes
chris6278 said:
I can read an ive done all the steps u posted but my ? Is where in root explorer do i find /etc/install-recovery.sh so i can rename it? Im learning this as i go so excuse me if i sound stupid sometimes
Click to expand...
Click to collapse
do you have root explorer? if not, it's just a file explorer that has root access. by default when you open it you are at /
you need to scroll down to /etc
go in that folder and find the install-recovery.sh
look up top for the button to turn it from read-only to read-write, click it
go back to the file long press it, and then choose rename.
Luxferro said:
I'm trying not to be rude... but if you can post in this thread, you can read it to. Before you asked your question a couple different step by step posts outlined all you need to know.... and this thread is only 2 pages...
Click to expand...
Click to collapse
Thanks..I already rerooted but thanks anways
I got root explorer an followed ur directions an now everything works great. Thanx for ur help an sorry for being a pain lol
Yes, I'm a noob
so I got my Moto XOOM and rooted it with adb and flashed a new kernel and installed ROM Manager and got a new recovery in it and all that and it was smooth as butter. I'm not a fan of ROMs but the kernel does make a huge difference already. Now, I did that as soon as I took the XOOM outta the box so I had no data to lose when rooting...
I've had my N1 for about a year now, been using 1-click root exploits because I didn't feel like starting over and losing all data even though I can have backups I know... but just putting the settings back, losing high scores in games, etc... is annoying enough.
But I'm starting to think now's the time.
So:
1) Best backup solution to not lose anything? My last titanium backup is from about two month ago when I lost root after the Gingerbread OTA
2) does it still stay rooted now with gingerbread? basically adb --> fastboot oem unlock and that's it?
3) I've read the wiki and it's great but not "omg I'm such a noob" proof... so the steps:
- I backup my stuff
- Reboot in recovery
- from my PC, run the command in adb --> fastboot oem unlock
- yes
- my nexus one is now unlocked, rooted but is back to factory...
after that, get the 2.3.3 update zip file from XDA and flash that. flash a new kernel via kernel manager (which one you guys recommend for speed and stability without all the fuss?)
that's it, finito?
thanks if you respond!
A - there are exploits available for Gingerbread, so you don't need to unlock the bootloader (though don't let that stop you)...
http://forum.xda-developers.com/showpost.php?p=13090966&postcount=67
B - unlocking the bootloader doesn't give you root. You also have to install a custom recovery and flash the su zip to gain root...
C - flashing an update zip will probably cause you to lose root (unless it's a pre-rooted zip, in which case you would need a custom recovery to flash it)...
hmm so I skipped a step, after unlocking bootloader I need to do what exactly? (commands/links if possible!)
it seemed simpler on the xoom.... unless it's the same thing?
adb reboot bootloader
fastboot oem unlock (wait for reboot)
adb reboot bootloader
fastboot flash boot rootboot.img
fastboot reboot (wait for reboot)
adb remount
adb shell push su /system/bin
adb shell ln –s /system/bin/su /system/xbin/su
adb shell chmod 4755 /system/bin/su
adb push Superuser.apk /system/app
that's it? are the Nexus files different? (got a link?)
as for Gingerbreak, I kinda got sick of always waiting a long time for 1-click roots after each update. I will try to get it working (so far no go, gonna stick a blank sd in my phone and try that) just so I can do a full Titanium backup and maybe a recovery if possible
Gingerbreak worked - stuck a blank micro-sd, rooted, put my 16gb micro-sd back in - all is well
running full Titanium now...
When trying to use RUU's i get a error that it cant update my htc one.
i tried both europian RUU's and its a europian phone(dutch no simlock)
i also have a nandroid but i cant restore it....it says no files found.
Where do i place the nandroid backup(made by clockworkmod) and how do i restore it?
thanks.
borgqueenx said:
When trying to use RUU's i get a error that it cant update my htc one.
i tried both europian RUU's and its a europian phone(dutch no simlock)
i also have a nandroid but i cant restore it....it says no files found.
Where do i place the nandroid backup(made by clockworkmod) and how do i restore it?
thanks.
Click to expand...
Click to collapse
I read your post in my guide thread. What recovery do you have CWM or TWRP?
borgqueenx said:
When trying to use RUU's i get a error that it cant update my htc one.
i tried both europian RUU's and its a europian phone(dutch no simlock)
i also have a nandroid but i cant restore it....it says no files found.
Where do i place the nandroid backup(made by clockworkmod) and how do i restore it?
thanks.
Click to expand...
Click to collapse
I know my device(From the Netherlands Sim Unlock) is on WWE firmware. Is yours carrier branded?
My advice would be to try Reinstalling CWM through HTC One AIO toolkit and then place the backup back in the CWM folder.
Maybe that will work.
clockworkmod is the installed recovery.
it just doesnt want to start the restore function. i can however select install from sd card fine, proofing that it has no problems seeing the data....
mine is not carrier branded.
So when you attempt to do the restore from CWM it lists the date/name of your backup but fails? Or can you not even get CWM to start the restore because it doesn't see the backups?
crushalot said:
So when you attempt to do the restore from CWM it lists the date/name of your backup but fails? Or can you not even get CWM to start the restore because it doesn't see the backups?
Click to expand...
Click to collapse
no it does not list anything.
tried moving the backup folder but i have no idea where to place it. already tried putting it in root, triying to put it in /backup and in /clockwordmod or something.
the error i get is: couldnt open directory, no files found.
borgqueenx said:
no it does not list anything.
tried moving the backup folder but i have no idea where to place it. already tried putting it in root, triying to put it in /backup and in /clockwordmod or something.
the error i get is: couldnt open directory, no files found.
Click to expand...
Click to collapse
Sorry this part can be tricky because folder path is slightly different on 4.1.2 than 4.2.2. Also I haven't used CWM in a long time since I switched to TWRP.
Did you try putting the entire clockwordmod folder in:
/data/media
Then try the restore.
crushalot said:
Sorry this part can be tricky because folder path is slightly different on 4.1.2 than 4.2.2. Also I haven't used CWM in a long time since I switched to TWRP.
Did you try putting the entire clockwordmod folder in:
/data/media
Then try the restore.
Click to expand...
Click to collapse
had to make both folders, they didnt exist. there is a .data folder though.
edit: didnt work putting the backup folder in there.
borgqueenx said:
had to make both folders, they didnt exist. there is a .data folder though.
edit: didnt work putting the backup folder in there.
Click to expand...
Click to collapse
You didn't use the correct folders. I am not talking about folders on the root of your sdcard, I am talking about root of file system.
You should have a file explorer tool that will allow you to navigate to root and have R/W permissions so we can move files if needed. If not go to the play store and install https://play.google.com/store/apps/...wxLDEwOSwiY29tLmVzdHJvbmdzLmFuZHJvaWQucG9wIl0
Open the application and on the top left there is a small icon, click it and should open the fast access menu. Choose Root Explorer and then Mount R/W when prompted, click ok (keep defaults).
Now you should be at the device root and it will say Device in the top middle of ES.
Now browse to /data/ then /media
If you do not see a clockwork mod folder in media that is where we need to move the CMW backups in order to be able to restore them from recovery.
So move the clockwordmod folder from media/0/clockworkmod to the root of /media folder so it looks like
/data/media/clockworkmod(folders within here have your backups)
Then boot into recovery and try the restore.
crushalot said:
You didn't use the correct folders. I am not talking about folders on the root of your sdcard, I am talking about root of file system.
You should have a file explorer tool that will allow you to navigate to root and have R/W permissions so we can move files if needed. If not go to the play store and install https://play.google.com/store/apps/...wxLDEwOSwiY29tLmVzdHJvbmdzLmFuZHJvaWQucG9wIl0
Open the application and on the top left there is a small icon, click it and should open the fast access menu. Choose Root Explorer and then Mount R/W when prompted, click ok (keep defaults).
Now you should be at the device root and it will say Device in the top middle of ES.
Now browse to /data/ then /media
If you do not see a clockwork mod folder in media that is where we need to move the CMW backups in order to be able to restore them from recovery.
So move the clockwordmod folder from media/0/clockworkmod to the root of /media folder so it looks like
/data/media/clockworkmod(folders within here have your backups)
Then boot into recovery and try the restore.
Click to expand...
Click to collapse
tried to do exactly what you told me.
there is a data folder in root, but there is no media folder inside of that.
and if i try to create it it fails and says i should try giving the folder another name.
edit: never mind a restart of the app fixed it.
EDIT: didnt work.
my backup folder is inside /data/media/clockworkmod/
and clockwork recovery still gives desame error.
First confirm where CWM is actually putting your backups. Do this by booting into recovery and choose to do a backup. Then uncheck all partitions but the smallest and allow it to backup.
When you reboot navigate through the folders we have been talking about and see the exact path of where it put it. Then compare the contents of the backup folders to make sure it is not your original backup that is messed up.
As long as you place your backup(inside its folder) in the folder where CWM put the test backup, then you should be able to see it from recovery and restore it. If not your original backup may not be any good.
Going offline for about hour for lunch. Be back around 1:30pm EST.
grrrrrr...
made a backup for testing where clockword puts them.
they are in /data/media/clockwordmod/backup
my backup is placed in /data/media/clockwordmod.
when i try to move my backup folder to /data/media/clockwordmod/backup it says successfull, but nothing happens. i cant seem to move the folder.
EDIT: ok copying pasting worked instead of cutting pasting.
i now restored...but for some reason recovery is still clockwordmod, and it still shows tampered and unlocked on first screen before recovery.
Well you probably backed up with the custom recovery installed, right? You'll have to flash the stock recovery manually.
If you want it to be locked, you'll have to lock it. revone will do that for you, after you've flashed stock recovery.
BenPope said:
Well you probably backed up with the custom recovery installed, right? You'll have to flash the stock recovery manually.
If you want it to be locked, you'll have to lock it. revone will do that for you, after you've flashed stock recovery.
Click to expand...
Click to collapse
i made the backup using a started version of clockwordmod, not a flashed version of clockwordmod.
....but ok. where can i find the normalrecovery and how to flash it?
borgqueenx said:
i made the backup using a started version of clockwordmod, not a flashed version of clockwordmod.
....but ok. where can i find the normalrecovery and how to flash it?
Click to expand...
Click to collapse
Odd.
Have you tried looking for the stock recovery? A high proportion of the posts here are about returning to stock.
borgqueenx said:
grrrrrr...
EDIT: ok copying pasting worked instead of cutting pasting.
i now restored...but for some reason recovery is still clockwordmod, and it still shows tampered and unlocked on first screen before recovery.
Click to expand...
Click to collapse
That is all normal. All you have done is reset the ROM back to default. You will still need to restore the stock recovery and then relock the bootloader to get to 100% stock.
I am trying to find all the info needed for you to finish up and I will post it.
---------- Post added at 02:02 PM ---------- Previous post was at 01:44 PM ----------
borgqueenx said:
i made the backup using a started version of clockwordmod, not a flashed version of clockwordmod.
....but ok. where can i find the normalrecovery and how to flash it?
Click to expand...
Click to collapse
Back in post number 4 you state that CWM is your installed recovery.
So it seems correct that you have a custom recovery installed. However since you are S-Off, before I put together something for you to go back I need to know:
Did you upgrade your firmware?
Did you flash a new hboot (to get rid of the red warning lettering)?
Did you flash a new splash screen?
If you answered no to all three of those questions, you should be able to get back to stock by performing the following:
Download the ResetRecovery zip I made for you here:
https://dl.dropboxusercontent.com/u/36946918/ResetRecovery.zip
Unzip all the files into a folder. (examples will use C:\temp)
Install the HTCDriver.exe to make sure the device drivers are installed on your PC.
Make sure that USB device debugging is enabled on your device.
Open a command prompt and navigate to that folder - Start>Run>cmd Enter
Code:
cd c:\temp
Connect USB cable to phone and PC.
With the PC booted type:
Code:
adb reboot bootloader
When the bootloader screen appears:
Code:
fastboot erase cache
Then:
Code:
fastboot flash recovery recovery.img
Reboot phone and go into recovery to make sure that CWM has been replaced by HTC stock recovery. If HTC recovery appears then reboot phone.
Now relock the bootloader:
Use the revone file that you probably used to get S-Off. (If needed it can be downloaded here: http://forum.xda-developers.com/showthread.php?t=2314582)
Push revone to your device:
Put the downloaded revone (rename file to just revone) file in your adb/fastboot folder (c:\temp) and push it using this command:
Code:
adb push revone /data/local/tmp/
open a adb shell by typing:
Code:
adb shell
Now change to that directory:
Code:
cd /data/local/tmp
Now set permissions
Code:
chmod 755 revone
Since you have the tampered flag run this to remove it:
Code:
revone -t
Now do this so it will show locked:
Code:
revone -l
The newer revisions of revone don't do the actual locking any longer but it may output the command you need to run to fully re-lock:
Type exit to exit the adb shell session and issue the command to re-lock the device:
Code:
fastboot oem writesecureflag 3
Now verify that it worked by booting into the bootloader:
Code:
adb reboot bootloader
You should see it say Locked at the top and S-On, just like it was out of the box!
i have no idea if i upgraded firmware. i was from stock to android revolution wich is the newest android version.
but now i am back on stock.
software number 1.29.401.16
i didnt try to get rid of warning texr and i didnt flash a custom splash screen.
can i proceed with those instructions?
borgqueenx said:
i have no idea if i upgraded firmware. i was from stock to android revolution wich is the newest android version.
but now i am back on stock.
software number 1.29.401.16
i didnt try to get rid of warning texr and i didnt flash a custom splash screen.
can i proceed with those instructions?
Click to expand...
Click to collapse
Yes, you would know if you flashed firmware because it has many warnings and a few steps. Your version number is stock, the thing that worries me is that you are S-off and originally you thought you only unlocked bootloader.
Did you use revone or moonshine to achieve S-off?
Do you see the red warning lettering on the splash screen when booting?
AS long as the custom recovery is back to stock and you see the red warning letter on splash then you should be ok to proceed with locking now.
crushalot said:
Yes, you would know if you flashed firmware because it has many warnings and a few steps. Your version number is stock, the thing that worries me is that you are S-off and originally you thought you only unlocked bootloader.
Did you use revone or moonshine to achieve S-off?
Do you see the red warning lettering on the splash screen when booting?
AS long as the custom recovery is back to stock and you see the red warning letter on splash then you should be ok to proceed with locking now.
Click to expand...
Click to collapse
is s-off desame as unlocking bootloader?
i unlocked bootloader yes. no idea about s-off. never did anything where i saw s-on or s-off.
yes i see those red warning letters.
i have never used or heard of revone or moonshine before you mentioned it here.
need to know how to get stock recovery back then^^
Hello guys, i need a little help.
I was looking for some tutorial to unlock dev cameras on my xt1225. I found one tutorial and he said to edit Build.prop, i'm noob at this, so I downloaded a file manager and entered in /system/, copied build.prop for backup, and edited the original build.prop. I restarted my phone and now i'm stuck in the boot screen.
I don't know for what reason but ADB (properly configured) does not show any device connected to the PC so I can't use the commands adb pull and adb push.
I have tried copy the backup of build.prop and overwrite the modified one, but no sucess (I did it in TWRP file manager)
I'm using XT1225 5.0.2 Stock ROM.
Edit: So, i tried to change his permissions (or think that i tried, in twrp filme manager with chmod command,), now the phone runs the boot animation and turn black, before he did not do it, before he just stuck in the white screen with motorola logo. (Tried chmod 644, 755, 777)
Sorry for bad english.
Neblue said:
Hello guys, i need a little help.
I was looking for some tutorial to unlock dev cameras on my xt1225. I found one tutorial and he said to edit Build.prop, i'm noob at this, so I downloaded a file manager and entered in /system/, copied build.prop for backup, and edited the original build.prop. I restarted my phone and now i'm stuck in the boot screen.
I don't know for what reason but ADB (properly configured) does not show any device connected to the PC so I can't use the commands adb pull and adb push.
I have tried copy the backup of build.prop and overwrite the modified one, but no sucess (I did it in TWRP file manager)
I'm using XT1225 5.0.2 Stock ROM.
Edit: So, i tried to change his permissions (or think that i tried, in twrp filme manager with chmod command,), now the phone runs the boot animation and turn black, before he did not do it, before he just stuck in the white screen with motorola logo. (Tried chmod 644, 755, 777)
Sorry for bad english.
Click to expand...
Click to collapse
I don't know about the chmod command, but the TWRP "Fix Permissions" does not work with our current (old) version of TWRP. It just messes up the phone.
1) since you have TWRP, did you make a back-up? If so, restore that. Problem solved.
(If no back-up, why not? That's one of the reasons we use TWRP, so we can restore a good backup when we screw something up.)
2) If you have TWRP, that means your bootloader is unlocked. GOOD.
Boot back into recovery, reflash your ROM. Problem solved.
Reboot, make sure everything is OK, then make a TWRP back-up!
EDIT: OOPS. I see you are using stock 5.0.2, not custom ROM. OK, I hope you made a backup. See #1.
There may be other solutions but all the ones I find seem to involve pushing new files to your phone and you say you can't do that...
______
Also in our version of TWRP, if you wipe cache do NOT attempt it from the "install" prompt (There's an option there to wipe cache. Ignore it.) Only wipe Cache from the "Wipe" section/Advanced Wipe/checkmark Cache and Dalvik Cache. (Even though we use ART, habits die hard.)
OK, I restored a backup following your thread, but before, searching for a solution, I formated the cache/data partition from f2fs to ext4 (so dumb), there's a way to undo it? There's no f2fs wipe option in twrp, I think I'll need to wait to a new version of twrp? Or flashing with rsd lite will do it?
Everything is working fine.
Thanks for your answer.
Sent from my XT1225 using XDA Free mobile app
Neblue said:
OK, I restored a backup following your thread,
Everything is working fine.
Thanks for your answer.
Click to expand...
Click to collapse
Glad your phone is back up and running! Aren't you glad you made a back-up?
Not sure about the F2Fs stuff. I haven't messed with it.
Yes, I agree we need a newer version of TWRP. I would gladly donate money toward to the developer!