Related
Not applicable
Delete this thread
Hello, thanks for the post.
I got a brand new Nexus S, I got a update direct from Google so I just flash it to GRJ22 :-(. I follow your guide (I have to do the step 1/2 in the other post you refer). Now I got clockwork done. But everytime I restart my phone, I always boot into clockwork. I try to 'mount sdcard' and reboot, but still boot into clockwork. How can I boot into the stock ROM?
many thanks!!
Too complicated.
Just:
1. turn on phone by holding volume up + power to go to bootloader
2. fastboot oem unlock (confirm it on the phone)
3. fastboot flash recovery recoveryfilename.img
4. Select recovery on the phone.
5. You're in ClockworkMod. Go flash a new ROM.
Let me answer myself.
I don't think the latest rom 2.3.4 is compatible with the clockwork you supplied. So I have to flash my phone back to GRH78. I downloaded the stock ROM from the internet. and then push all the images file into /sdcard/clockworkmod/backup/2010.xxx.
Next, I restore the image in clockwork menu.
after restore, reboot the phone, now I am back in business.
When the phone is boot, i lost the root again, so i went to modaco.com and get Paul's package. run it, restart, I got the root.
Finally, go to market place and get ROM Manager, install the clockwordmod. and I have a 'proper' phone.
although I don't have the least rom, at least i got a working phone that is rooted.
bante said:
Hello, thanks for the post.
I got a brand new Nexus S, I got a update direct from Google so I just flash it to GRJ22 :-(. I follow your guide (I have to do the step 1/2 in the other post you refer). Now I got clockwork done. But everytime I restart my phone, I always boot into clockwork. I try to 'mount sdcard' and reboot, but still boot into clockwork. How can I boot into the stock ROM?
many thanks!!
Click to expand...
Click to collapse
I have the same problem. How did you handle it?
Wow, why risk messing up your phone with flashing a boot.img when you can just rename /etc/install-recovery.sh to something like /etc/install-recovery.bak?
Here's one way to rename (courtesy of Matridom). Another is to use Root Explorer.
Matridom said:
The new update applies the install-recovery.sh script into our phones (not there previously.
Boot into the bootloader
flash CWM
select recovery from the bootloader (DO NOT reboot the phone)
apply the su binary
boot into the OS and test root
make sure busybox is properly installed
run ADB shell
then:
Code:
su
mount -o remount,rw /dev/block/mtdblock3 /system
mv /system/etc/install-recovery.sh /system/etc/install-recovery.bak
Boot back into the bootloader and re-flash CWM, should stay permanent now.l had applied the SU binary at the same time as the OTA update, then renamed the installer script and flashed back CWM.
Click to expand...
Click to collapse
andnaz said:
I have the same problem. How did you handle it?
Click to expand...
Click to collapse
same here someone please help ?
This is a totally unorthodox way to make the custom recovery permanent. If your phone is messed up, good luck fixing it.
There is a much easier and safer way like I mentioned.
PS: flashing recovery for 2.3.4 is the exact same as for 2.3.3!
fastboot flash recovery <recovery .img>
Sent from my Nexus S using XDA App
bante said:
Hello, thanks for the post.
I got a brand new Nexus S, I got a update direct from Google so I just flash it to GRJ22 :-(. I follow your guide (I have to do the step 1/2 in the other post you refer). Now I got clockwork done. But everytime I restart my phone, I always boot into clockwork. I try to 'mount sdcard' and reboot, but still boot into clockwork. How can I boot into the stock ROM?
many thanks!!
Click to expand...
Click to collapse
Hi Bante, I am sorry for the inconvenience. I have revert back the CWM Recovery to 3.0.2.4. You can download it at the link above, and try it again
I hope that the problem you mention wont persist anymore
zero383 said:
This is a totally unorthodox way to make the custom recovery permanent. If your phone is messed up, good luck fixing it.
There is a much easier and safer way like I mentioned.
PS: flashing recovery for 2.3.4 is the exact same as for 2.3.3!
fastboot flash recovery <recovery .img>
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
I am sorry but not all people can successfully use Command Prompt to do so.
I cant use command prompt, as it says "Image cant be loaded".
So I had to use this method.
I search around the forum and seen this as a quite common problem,
so I decided to share it
Hope you understand.
Anyway, thanks for your method too Cheers
andnaz said:
I have the same problem. How did you handle it?
Click to expand...
Click to collapse
The CWM Recovery I supplied is version 3.0.2.5,
which is not compatible.
So I replaced with version 3.0.2.4.
You just download it at the link above and follow all the step again.
You should able to solve this problem
Do notify me if any problem persist
16vMK1 said:
same here someone please help ?
Click to expand...
Click to collapse
The CWM Recovery I supplied is version 3.0.2.5,
which is not compatible.
So I replaced with version 3.0.2.4.
You just download it at the link above and follow all the step again.
You should able to solve this problem
Do notify me if any problem persist
Wow people like to make things complicated. Why install an entire rom to get ride of a script?
if you can flash cwm, you should have some basic understanding of fastboot, adb and the search options in the forums. the answers are all there already.
Sent from my Nexus S
No disrespect, I agree flashing recoverys should only be done after you understand how to use the tools to do it. there is no reason someone who is going to mod systems on their nexus shouldn't be able to use fastboot and adb properly. all the right drivers are in the sdk.
Sent from my Nexus S 4G using Tapatalk
nxt said:
Too complicated.
Just:
1. turn on phone by holding volume up + power to go to bootloader
2. fastboot oem unlock (confirm it on the phone)
3. fastboot flash recovery recoveryfilename.img
4. Select recovery on the phone.
5. You're in ClockworkMod. Go flash a new ROM.
Click to expand...
Click to collapse
This is what I did.
I rooted my NS, which had 2.3.3
Used phone with stock 2.3.3 until I figured out which ROM I want to flash.
Before I flashed any ROM, did a Nandroid Backup through CWM.
Used the ROM for a few days, but when I saw that official update is ready for download for i9020A, did do a restore from the Nandroid backup I created.
Updated from 2.3.3 to 2.3.4, phone works fantastic, video chat also works great.
After update when I tried using any of the apps required SU permission, they didn't work. I tried installing a couple of .apk files, couldn't either install it or after installation it didn't work.
Thought let me try wiping my phone clean and start all over again, may be I will use a custom ROM again, downloaded ROM, went to ROM Manager to reboot into recovery, nothing happens.
Tried booting into Recovery option manually by pressing Volume Up and Power button, nothing happens but the Bot with an Arrow appears on screen.
So, I thought I will follow this procedure to reflash CWM to my phone and get it going. I was able to use the command FastBoot once, and suceeded pushing .img file to my phone but now whenever I try using the commands from my computer, this error message appears : "This application has failed to start becasue AdbWinApi.dll was not found. Re-installing the application may fix this problem."
Why this error message if I have the sdk on my computer already through which I was once able to push .img file without any troubles?
Can anyone tell me what would be a possible solution?
Also, how can I fix this problem and get ClockWorkMod Recovery installed on my NS again?
How can I get stock recovery image on my phone if I want start all over again from scratch?
Thx a million.
Edit ::: I found the answer as to how to how to install CWM again. Thx anyways.
Other question still remains a puzzle... why am I not able to install certain programs or if did manage to install, can't run them?
I ran your method and I think I'm stuck at some step...
My phone now default boots into CWM 3.0.2.4
Recovery boots to a newer recovery I flashed.
How do I get my phone to default boot into the OS again?
Edit: nevermind, just downloaded the full 2.3.4 rom, extracted and flashed the original boot.img.
dreamsforgotten said:
All the right drivers are in the sdk.
Click to expand...
Click to collapse
After installing the sdk and a platform, I have adb, but where is fastboot?
I was getting the same error as "Image cant be loaded". after hours of struggling I found that It's only because I was not in the same directory as the img file. silly eh?
hi,did you repaiar your phone,i have try everything but it just keep going in clockwork mode,if i than pres reboot now in clockworkmode it stays on google padlock
i realy need phone if you can help or someone else,than ....
just tried this method of window7 (thanks for the work) with cwm 3.0.2.4, but got the same result like the others in this thread: cant boot the android 2.3.4, the system is always booting into the cwm, no way out.
I don't think this tool works as it should.
:-(
EDIT:
I didn't realize that window7's tool would install the cwm into the boot-partition instead of the recovery-partition.
To get my boot partition back I downloaded the 2.3.4 firmware image from http://forum.xda-developers.com/showthread.php?t=1056062 and extracted the boot.img from the zip.
with "fastboot flash boot boot.img" I restored my orginal boot partition an can boot into android again.
(fastboot is part of the android sdk)
Do I have to install cwmtouch also if all I want to add is kinfauns fff1.3 bootloader, to change the logo and keep TWRP?. I tried installing just kinfauns fff1.3 bootloader, but can not gain SU.
palmheel said:
Do I have to install cwmtouch also if all I want to add is kinfauns fff1.3 bootloader, to change the logo and keep TWRP?. I tried installing just kinfauns fff1.3 bootloader, but can not gain SU.
Click to expand...
Click to collapse
would try latest kfu 0.9.4 - point install latest firefirefire
hope this is 1.3 ...
palmheel said:
Do I have to install cwmtouch also if all I want to add is kinfauns fff1.3 bootloader, to change the logo and keep TWRP?. I tried installing just kinfauns fff1.3 bootloader, but can not gain SU.
Click to expand...
Click to collapse
You can mix and match whatever bootloader/recovery combination you want. They are on separate partitions, so flashing one does not affect the other.
The only caveat is that you must have TWRP installed before changing the bootloader because the distribution image for TWRP is a boot image that actually boots up and flashes both the recovery and bootloader partitions on its own. That boot image contains version 1.0 of FFF, so you must then overwrite it with whatever bootloader you want.
As a side note, the install process for TWRP is unintuitive and may be confusing for new users to have to use the "fastboot boot" instead of the "fastboot flash recovery" command. I've gone back and forth with CWMR and TWRP several times and it's annoying to have to flash the bootloader over and over again in the process. To get around that, I've extracted just the recovery image from the TWRP distribution and have been using that image instead. I've thought about posting it somewhere, but I didn't want to piss off the developers. Maybe if there's some demand for it, I'll just upload it somewhere to see if anybody comes screaming at me... or maybe just write a how-to for those interested in extracting it for themselves.
I've packaged it in my new method, I just need time to sit down n rewrite the install directions and update my post. I've also compiled a blue cwm of sbloods version 1.1 which will also be in the updated method.
but yup, what kinfaun said lol
Sent from my HTC Glacier using xda premium
Ok. Now, for the the dumb question of the day. I do have TWRP installed, I tried using the instructions on the [gscript][march11]install cwm recovery+bootloader of your choice (no fastboot) thread, but keep getting error with SU.
palmheel said:
Ok. Now, for the the dumb question of the day. I do have TWRP installed, I tried using the instructions on the [gscript][march11]install cwm recovery+bootloader of your choice (no fastboot) thread, but keep getting error with SU.
Click to expand...
Click to collapse
You might want to wait a day or two for everyone to finish banging away at the 6.3 update. I got one of the $139 refurbs and it came today. Trying to root it, I'm running into SU/permission issues too. Something changed but everyone just don't know what yet. From what I can tell, this is fairly standard every time Amazon releases an update.
Got it installed. Thanks to all, for all the info. Learning, all this is new to me.
I was running stock 4.1.1 rooted with NO cwm and I accepted the OTA undate two days ago. Now, I have SU still installed but nothing can obtain root permissions. I used Wugz toolkit to reflash su binaries through TWRP a few times and still no dice. Any thoughts?
Trickee360 said:
I was running stock 4.1.1 rooted with NO cwm and I accepted the OTA undate two days ago. Now, I have SU still installed but nothing can obtain root permissions. I used Wugz toolkit to reflash su binaries through TWRP a few times and still no dice. Any thoughts?
Click to expand...
Click to collapse
Here you go. Just follow the directions. It works fine for 4.1.2.
http://www.talkandroid.com/guides/misc/how-to-unlock-and-root-the-nexus-7/
veeman said:
Here you go. Just follow the directions. It works fine for 4.1.2.
http://www.talkandroid.com/guides/misc/how-to-unlock-and-root-the-nexus-7/
Click to expand...
Click to collapse
Welp, I've never actually used adb to push anything manually myself, but now is as good as time as any to try it. The link to CWM on that page is dead. Where else can I get it?
Trickee360 said:
Welp, I've never actually used adb to push anything manually myself, but now is as good as time as any to try it. The link to CWM on that page is dead. Where else can I get it?
Click to expand...
Click to collapse
http://www.clockworkmod.com/rommanager
You can download the Touch Recovery on the right side for Google Nexus 7 version. But make sure when you put in
Code:
fastboot flash recovery recovery-clockwork-touch-6.0.1.0-grouper.img
for step 5. instead of what they put.
veeman said:
http://www.clockworkmod.com/rommanager
You can download the Touch Recovery on the right side for Google Nexus 7 version. But make sure when you put in
Code:
fastboot flash recovery recovery-clockwork-touch-6.0.1.0-grouper.img
for step 5. instead of what they put.
Click to expand...
Click to collapse
got it. thanks much
Will only boot to stock recovery
veeman said:
You can download the Touch Recovery on the right side for Google Nexus 7 version. But make sure when you put in
Code:
fastboot flash recovery recovery-clockwork-touch-6.0.1.0-grouper.img
for step 5. instead of what they put.
Click to expand...
Click to collapse
Every time I reboot into recovery from the bootloader after flashing any recovery (except stock), it fails to boot into recovery. What happens is it shows the Google/Unlocked screen for a couple seconds, goes black (this is where it should enter recovery), but then shows the Google screen again and boots normally. I have tried this with two CWM recoveries and a TWRP recovery, both plugged into a computer and not. when flashing recovery it says OKAY. It seems as if something has gotten corrupted.
Before updating to 4.1.2 everything was working. To get the 4.1.2 update to install, I had to revert back to stock recovery and also revert back to the stock wallet app. Now 'su' is still a command, but it does not do what it is supposed to and no apps have root.
:'(
jphilli85 said:
Every time I reboot into recovery from the bootloader after flashing any recovery (except stock), it fails to boot into recovery. What happens is it shows the Google/Unlocked screen for a couple seconds, goes black (this is where it should enter recovery), but then shows the Google screen again and boots normally. I have tried this with two CWM recoveries and a TWRP recovery, both plugged into a computer and not. when flashing recovery it says OKAY. It seems as if something has gotten corrupted.
Before updating to 4.1.2 everything was working. To get the 4.1.2 update to install, I had to revert back to stock recovery and also revert back to the stock wallet app. Now 'su' is still a command, but it does not do what it is supposed to and no apps have root.
:'(
Click to expand...
Click to collapse
You can just root again and you will have root access.
I lost root too, so I just opened wugtoolkit and hit root. no unlock needed so no loss of programs either.
jphilli85 said:
Every time I reboot into recovery from the bootloader after flashing any recovery (except stock), it fails to boot into recovery. What happens is it shows the Google/Unlocked screen for a couple seconds, goes black (this is where it should enter recovery), but then shows the Google screen again and boots normally. I have tried this with two CWM recoveries and a TWRP recovery, both plugged into a computer and not. when flashing recovery it says OKAY. It seems as if something has gotten corrupted.
Before updating to 4.1.2 everything was working. To get the 4.1.2 update to install, I had to revert back to stock recovery and also revert back to the stock wallet app. Now 'su' is still a command, but it does not do what it is supposed to and no apps have root.
:'(
Click to expand...
Click to collapse
Any news about this. I stay in the same problem.
Here's my experience:
Stock ROM, rooted, custom kernel.
Got the notification for the 4.1.2 OTA update, so I did a nandroid backup in TWRP. Then I flashed back to the stock recovery and boot.img.
I was thinking that I might lose root, based on other's problems. Looked into installing Root Keeper by Voodoo. In the description it said the same feature is built into SuperSU. Problem was it's built into the paid version, which I didn't have (discovered this after it was too late). Installed 4.1.2 OTA. I lost root. My bootloader was updated to 3.41. I also was not able to flash a recovery. Fastboot flash would not work, Wugs toolkit didn't work. Tried several methods. After reading several threads that have been pretty active for the last few days, here's what finally worked for me. Found it in another thread, which I can't find at the moment.
adb reboot bootloader
fastboot flash bootloader bootloader-grouper-3.34.img from the JRO03D factory image
fastboot flash recovery TWRP img
fastboot reboot-bootloader
TWRP recovery started up :laugh:.
flashed SuperSU to re-root, it was sucessful.
updated busybox binaries.
installed OTA rootkeeper, so hopefully this won't happen again.
I'm not really sure I want to try flashing the 3.41 bootloader.
What a pain in the A.
Now it's time to flash faux kernel.
jayyo said:
Here's my experience:
Stock ROM, rooted, custom kernel.
Got the notification for the 4.1.2 OTA update, so I did a nandroid backup in TWRP. Then I flashed back to the stock recovery and boot.img.
I was thinking that I might lose root, based on other's problems. Looked into installing Root Keeper by Voodoo. In the description it said the same feature is built into SuperSU. Problem was it's built into the paid version, which I didn't have (discovered this after it was too late). Installed 4.1.2 OTA. I lost root. My bootloader was updated to 3.41. I also was not able to flash a recovery. Fastboot flash would not work, Wugs toolkit didn't work. Tried several methods. After reading several threads that have been pretty active for the last few days, here's what finally worked for me. Found it in another thread, which I can't find at the moment.
adb reboot bootloader
fastboot flash bootloader bootloader-grouper-3.34.img from the JRO03D factory image
fastboot flash recovery TWRP img
fastboot reboot-bootloader
TWRP recovery started up :laugh:.
flashed SuperSU to re-root, it was sucessful.
updated busybox binaries.
installed OTA rootkeeper, so hopefully this won't happen again.
I'm not really sure I want to try flashing the 3.41 bootloader.
What a pain in the A.
Now it's time to flash faux kernel.
Click to expand...
Click to collapse
So, the bootloader 3.41 is the problem?
Southmad said:
So, the bootloader 3.41 is the problem?
Click to expand...
Click to collapse
For some people, yes. No idea why.
veeman said:
http://www.clockworkmod.com/rommanager
You can download the Touch Recovery on the right side for Google Nexus 7 version. But make sure when you put in
Code:
fastboot flash recovery recovery-clockwork-touch-6.0.1.0-grouper.img
for step 5. instead of what they put.
Click to expand...
Click to collapse
Would that image work ok for Galaxy s3? Or there is no difference at all, just matter the 4.1.2 android version?
Cuz i updated my device throught Kies (cuzz from the device itself it didnt allow, stating that the image has been modifyied :angel: ) and after that even with the persistent mode on Super SU the root is gone
(OK, the board ate my first post; maybe this one will do better...)
I am trying to root my Nexus 4 in order to install Titanium Backup. (I have some user data to transfer over from my old Samsung Vibrant before I retire it.) I'm using the Nexus Toolkit for Linux, here:
http://forum.xda-developers.com/showthread.php?t=1999065
The first two steps work fine. I can unlock the bootloader and install clockwork mod. When I try to actually root the device and install su, though, I run into a problem. Specifically, going into recovery mode (either automatic through the toolkit or manually myself) I get the Andy the Android "error" icon (Android flat on his back, chest open, with a red warning triangle over it). That remains until I reboot the device.
Any suggestions? I'm not an experienced rooter (Ti Backup is the ony reason I'm even bothering), so keep it basic please.
Crell42 said:
(OK, the board ate my first post; maybe this one will do better...)
I am trying to root my Nexus 4 in order to install Titanium Backup. (I have some user data to transfer over from my old Samsung Vibrant before I retire it.) I'm using the Nexus Toolkit for Linux, here:
http://forum.xda-developers.com/showthread.php?t=1999065
The first two steps work fine. I can unlock the bootloader and install clockwork mod. When I try to actually root the device and install su, though, I run into a problem. Specifically, going into recovery mode (either automatic through the toolkit or manually myself) I get the Andy the Android "error" icon (Android flat on his back, chest open, with a red warning triangle over it). That remains until I reboot the device.
Any suggestions? I'm not an experienced rooter (Ti Backup is the ony reason I'm even bothering), so keep it basic please.
Click to expand...
Click to collapse
It sounds like you're losing recovery. Do you restart your device after you flash CWM?
Try flashing CWM manually through fastboot, don't restart the device (will overwrite custom recovery) and just go directly into recovery then flash SU.
Alternatively, make sure you're using the right version of CWM and/or double check that the writing process for CWM is going to completion. I don't know if you can disable the stock recovery overwrite without first having root, but you can also look into that
hoponpop said:
It sounds like you're losing recovery. Do you restart your device after you flash CWM?
Try flashing CWM manually through fastboot, don't restart the device (will overwrite custom recovery) and just go directly into recovery then flash SU.
Alternatively, make sure you're using the right version of CWM and/or double check that the writing process for CWM is going to completion. I don't know if you can disable the stock recovery overwrite without first having root, but you can also look into that
Click to expand...
Click to collapse
I'm using whatever version is included in the Universal Tooklkit download. It has two versions included, Standard and Touch. I've tried both, same effect.
Any pointers on "manual" installation of CWM? (As I said, rooting newbie.)
So this morning I got an update to fix the voLTE bug. I'm unlocked with twrp installed and rooted. Just for the sake of experimenting I tried installing it. Well that didn't work. Just gets stuck in twrp recovery and you have to power the phone off completely to get it to boot. I guess my question (even though it's a little early) is there a way to install the update without reverting back to stock?
EDIT: Link to the zip
https://drive.google.com/open?id=0BxqNotAWlwLUQ1Fzcjc2YXd4QzA
I don't believe so.
In the past you either had to go back to stock or wait on someone to create a compatible update for rooted devices.
Can you post link to zip?
If you are rooted, you can find the zip in cache folder in recovery.
Can you add what variant and build you are using before the update? Also the build afterwards?
KapilFaujdar said:
Can you post link to zip?
If you are rooted, you can find the zip in cache folder in recovery.
Click to expand...
Click to collapse
I got the update, but all I see on my magisk rooted G5+ in /cache/recovery are log files and the fstab files. Anywhere else to look?
gghose said:
I got the update, but all I see on my magisk rooted G5+ in /cache/recovery are log files and the fstab files. Anywhere else to look?
Click to expand...
Click to collapse
Yeah I can't find anything in that folder either.
I received the update and applied it. I am not rooted.
I have the XT1687 model.
My current build number is NPN25.137-35
My device BL unlocked, TWRP installed and rooted with magisck.
I'm getting the update notification and splash screens several times daily.
Anyone rooted try installing the update with Flashfire app?
bvsbutthd101 said:
So this morning I got an update to fix the voLTE bug. I'm unlocked with twrp installed and rooted. Just for the sake of experimenting I tried installing it. Well that didn't work. Just gets stuck in twrp recovery and you have to power the phone off completely to get it to boot. I guess my question (even though it's a little early) is there a way to install the update without reverting back to stock?
Click to expand...
Click to collapse
If you have systemless supersu, you should just be able to apply the update after reverting to stock recovery.
So I found where the zip downloads. I wonder what flashing it in twrp would do?
EDIT: Here's the link to the zip and I've put it in the OP.
https://drive.google.com/open?id=0BxqNotAWlwLUQ1Fzcjc2YXd4QzA
glight0 said:
My device BL unlocked, TWRP installed and rooted with magisck.
I'm getting the update notification and splash screens several times daily.
Anyone rooted try installing the update with Flashfire app?
Click to expand...
Click to collapse
OK, so I tried flashing recovery.img from stock firmware build 33. But the OTA update will not install, instead I get an error after downloading and rebooting (red triangle at recovery mode).
So I tried fully reverting to stock firmware but I decided to skip over erasing userdata. Afterward the OTA downloaded and installed successfully. Keeping userdata does not seem to have caused an issue.
My problem now though is how to get root back without having to wipe userdata after re-flashing TWRP.
Or is this not possible and if I want to root I must first wipe userdata so that TWRP can read internal memory?
bvsbutthd101 said:
So I found where the zip downloads. I wonder what flashing it in twrp would do?
EDIT: Here's the link to the zip and I've put it in the OP.
https://drive.google.com/open?id=0BxqNotAWlwLUQ1Fzcjc2YXd4QzA
Click to expand...
Click to collapse
Just tried flashing it with TWRP and no luck:
Verifying current system....
E3002: Package expects build thumbprint of 7.0/NPN25.137-35/37:user/release-keys or 7.0/NPN25.137-33/35:user/release-keys; this device has .
Updated process ended with ERROR: 7
which doesn't make much sense since I rooted the stock ROM (Build number reads NPN25.137-33).
If your using a custom recovery flash the stock recovery, then go to the stock recovery and using your computer flash using adb sideboard command. I assume you already know how to do this. Hope that helps.
gghose said:
Just tried flashing it with TWRP and no luck:
Verifying current system....
E3002: Package expects build thumbprint of 7.0/NPN25.137-35/37:user/release-keys or 7.0/NPN25.137-33/35:user/release-keys; this device has .
Updated process ended with ERROR: 7
which doesn't make much sense since I rooted the stock ROM (Build number reads NPN25.137-33).
Click to expand...
Click to collapse
I'm stuck in the same boat... no idea how to flash the stock recovery and sideboard, what that even means, or if that would break root. I just followed the step-by-step "how to root" video when I first got the phone
There's a workaround to disable the "advanced LTE" or whatever it was called, so I did that. But in the meantime until a more "user friendly" means of updating is available, is there a way I can get rid of this nag screen? Way back on an earlier device (Samsung Charge?) I remember manually editing a "build.prop" file or something to match the latest version so I wouldn't keep getting the software update nag. Is there something that will do the same here, or is there a system app I can freeze in TiB?
My best guess is freezing "Moto Actions 03.022.1.4-N" because it's showing "(updated)" on the side.
rellim113 said:
I'm stuck in the same boat... no idea how to flash the stock recovery and sideboard, what that even means, or if that would break root. I just followed the step-by-step "how to root" video when I first got the phone .
Click to expand...
Click to collapse
What he means is you need to download the stock rom, unzip it, then boot phone to bootloader mode and connect to PC. Then flash the recovery.IMG from the stock rom folder with command prompt:
Fastboot flash recovery recovery.img
Then you can on the phone tell it to boot to recovery mode. This will be a screen with Android on his back and the words NO Command on the bottom. Then plug to PC and use adb command to sideload the update zip like this:
adb sideload [nameofupdatefile].Zip
glight0 said:
What he means is you need to download the stock rom, unzip it, then boot phone to bootloader mode and connect to PC. Then flash the recovery.IMG from the stock rom folder with command prompt:
Fastboot flash recovery recovery.img
Then you can on the phone tell it to boot to recovery mode. This will be a screen with Android on his back and the words NO Command on the bottom. Then plug to PC and use adb command to sideload the update zip like this:
adb sideload [nameofupdatefile].Zip
Click to expand...
Click to collapse
Strange, reflashed the stock recovery and adb can't see it (adb devices returns nothing). And when trying to install it via the normal OTA way, the stock recovery tries to install but ends with an error.
That's what happened to me when I tried reverting to stock recovery and then trying to install update from phone Settings app.
I ended up having to revert to stock rom to get ota to apply with settings app. But now I am trying to root again but after installing TWRP data is encrypted again. So looks like I will have to wipe data before re-rooting.