So I flashed the latest firmware, after being unlocked, then rent back to bootloader, flashed recovery, went to recovery and installed file. Then restarted...now stuck in boot loop. It booted before I went to flash recovery in the new firmware just fine.
Do you need to flash something else when you flash recovery?
it says device is corrupt when I restart, but I was under the impression that screen comes up when bootloader is unlocked, so not sure if it means anything
Make sure your using the correct commands!
I did this, and i was accidentally flashing recovery to boot!
Before flashing your phone with new firmware your phone previously rooted in older firmware?
premchandar777 said:
Before flashing your phone with new firmware your phone previously rooted in older firmware?
Click to expand...
Click to collapse
yea, I unlocked it in old firmware, didnt realize my mistake and then downloaded image of newest from google, installed everything, booted fine, then went to send recovery and that causes the corruption/boot loopp
xamius said:
yea, I unlocked it in old firmware, didnt realize my mistake and then downloaded image of newest from google, installed everything, booted fine, then went to send recovery and that causes the corruption/boot loopp
Click to expand...
Click to collapse
The biggest problem in Samsung is that when we flash phone with new firmware it won't delete the entire /system instead it rewrites the /system(sub folders),if you rooted your phone previously which means /su will be made in previous /system folder,now when you flash with new firmware without wiping the previous /system completely,then new firmware will be just rewrites other folder leaving /su since original firmware won't contain /su,since your old /su now corrupted because of misleading binaries that's the reason for you problem
Its possible for you go to recovery now?
premchandar777 said:
The biggest problem in Samsung is that when we flash phone with new firmware it won't delete the entire /system instead it rewrites the /system(sub folders),if you rooted your phone previously which means /su will be made in previous /system folder,now when you flash with new firmware without wiping the previous /system completely,then new firmware will be just rewrites other folder leaving /su since original firmware won't contain /su,since your old /su now corrupted because of misleading binaries that's the reason for you problem
Its possible for you go to recovery now?
Click to expand...
Click to collapse
Samsung? I think you are in the wrong forum mate!
xamius said:
So I flashed the latest firmware, after being unlocked, then rent back to bootloader, flashed recovery, went to recovery and installed file. Then restarted...now stuck in boot loop. It booted before I went to flash recovery in the new firmware just fine.
Do you need to flash something else when you flash recovery?
it says device is corrupt when I restart, but I was under the impression that screen comes up when bootloader is unlocked, so not sure if it means anything
Click to expand...
Click to collapse
We had this problem with the n6 with marshmallow. The fix was to reboot system after flashing the recovery. Then reboot recovery flash SuperSU and a custom kernel before rebooting. Something in the kernel needed to be fixed to allow su. For the n6 there was a stock with fixes boot image available for this if you didn't want a custom kernel. I would suggest reflashing the factory image & reading the forums some more for a kernel that offers the fix you're after.
If you flashed everything from the new image then wouldn't that reset your phone? When you reset the phone it turns off usb debugging in the developer options. I don't know if this makes a difference when flashing in fastboot but after I unlocked the bootloader I booted the phone up, re-enabled developer settings and turned usb debugging back on. I then booted into fastboot and flashed the recovery and it worked fine.
Won't be druv said:
Samsung? I think you are in the wrong forum mate!
Click to expand...
Click to collapse
Sorry I have posted wrong forum but the solution to that problem is correct I feel.
Not sure if you flashed correctly. Follow the unlock root thread. If using SuperSU in addition to flashing to at least factory K you need to flash modified modified boot.img found on correct SuperSU thread.
premchandar777 said:
The biggest problem in Samsung is that when we flash phone with new firmware it won't delete the entire /system instead it rewrites the /system(sub folders),if you rooted your phone previously which means /su will be made in previous /system folder,now when you flash with new firmware without wiping the previous /system completely,then new firmware will be just rewrites other folder leaving /su since original firmware won't contain /su,since your old /su now corrupted because of misleading binaries that's the reason for you problem
Its possible for you go to recovery now?
Click to expand...
Click to collapse
yes I am able to reset everything after rebooting to OS using fastboot continue
what's the solution for this now, to root my phone again?
I have almost the same problem. My device is the sm-t110. I flashed twrp, thinking their android app can flash through zip files. which i dont think it can. I let the battery die to see if it would fix it. but it didnt. Now its not charging because of bootloop. Can't go into recovery mode. And i forced into recovery using flashible and now it tries to boot into recovery, even when charging. And the computer won't pick it up. So Odin won't work. I think of fixing by removing battery or see if samsung can fix it.
Related
I was able to flash an EVGA ROM successfully and also Shaky156's CWM recovery. Primary reason was to get rid of Chinese notifications completely. Problem is that I cannot get the 1.1 OTA update to install because of the CWM recovery. I tried to flash stock recovery via fastboot but was not successful. Tried different versions even the BAT_CWM_recovery but it won't accept any except Shaky's version. Also tried the Super Tool but it won't recognize the tablet. I have previously installed the SDK and can get fastboot to run. Will try version 1.5 if it works.
Freeje said:
I was able to flash an EVGA ROM successfully and also Shaky156's CWM recovery. Primary reason was to get rid of Chinese notifications completely. Problem is that I cannot get the 1.1 OTA update to install because of the CWM recovery. I tried to flash stock recovery via fastboot but was not successful. Tried different versions even the BAT_CWM_recovery but it won't accept any except Shaky's version. Also tried the Super Tool but it won't recognize the tablet. I have previously installed the SDK and can get fastboot to run. Will try version 1.5 if it works.
Click to expand...
Click to collapse
Always erase the partition beforehand.
fastboot erase boot
then... as an example
fastboot flash boot boot.img
or
fastboot erase recovery
then... as an example
fastboot flash recovery recovery.img
Make sure you are cautious never to loose fastboot ability. Other words if your bootloader can't be obtained from restarting and hold buttons down, then make sure you don't restart till you get a successful flashing. Always have the system ADB enabled and certified with the computer.
e8hffff said:
Always erase the partition beforehand.
fastboot erase boot
then... as an example
fastboot flash boot boot.img
or
fastboot erase recovery
then... as an example
fastboot flash recovery recovery.img
Make sure you are cautious never to loose fastboot ability. Other words if your bootloader can't be obtained from restarting and hold buttons down, then make sure you don't restart till you get a successful flashing. Always have the system ADB enabled and certified with the computer.
Click to expand...
Click to collapse
Did what you said but still no stock recovery installed. When I reboot after erasing the old recover and flashing the stock instead of going to recovery it just boots up. Looks like the recovery never gets flashed. I did check if the tablet is being recognized by the computer before any flashing. After flashing the stock recovery it says okay so I don't know what's happening.
Freeje said:
Did what you said but still no stock recovery installed. When I reboot after erasing the old recover and flashing the stock instead of going to recovery it just boots up. Looks like the recovery never gets flashed. I did check if the tablet is being recognized by the computer before any flashing. After flashing the stock recovery it says okay so I don't know what's happening.
Click to expand...
Click to collapse
Have you done an OEM unlock?
fastboot oem unlock
e8hffff said:
Have you done an OEM unlock?
fastboot oem unlock
Click to expand...
Click to collapse
Yes, tablet is unlocked. Says so when I boot into the bootloader. I have flashed Shaky's CWM and it installed fine. Don't know why the tablet does not like the stock recovery. Even tried BAT-cwm recovery but also failed to install. I'll just have to wait for someone to come up with a flashable ROM if the Kitkat update comes around.
Freeje said:
Yes, tablet is unlocked. Says so when I boot into the bootloader. I have flashed Shaky's CWM and it installed fine. Don't know why the tablet does not like the stock recovery. Even tried BAT-cwm recovery but also failed to install. I'll just have to wait for someone to come up with a flashable ROM if the Kitkat update comes around.
Click to expand...
Click to collapse
Do your best to get Bat_recovery for the recovery parititon and the 4.3.1 boot.img for the boot partition, shared on my Tegra Note Discoveries thread. Never flash the bootloader partition unless you are really know what you're doing. Then possible flash the system partition with Tom's system.img with;
fastboot erase system
fastboot flash system system.img
Tom's image should patch and is an English styled setup so you get all the Google Apps, etc.
e8hffff said:
Do your best to get Bat_recovery for the recovery parititon and the 4.3.1 boot.img for the boot partition, shared on my Tegra Note Discoveries thread. Never flash the bootloader partition unless you are really know what you're doing. Then possible flash the system partition with Tom's system.img with;
fastboot erase system
fastboot flash system system.img
Tom's image should patch and is an English styled setup so you get all the Google Apps, etc.
Click to expand...
Click to collapse
Here's what I did:
1. Erased the system and flashed the 4.3plus system zip.
2. Erased the boot image and flashed the 4.3plus boot image.
3. Erased the recovery and flashed the bat recovery.
4. Rebooted and got stuck on the Tegra Note screen. (flashing on and off).
Tried to experiment and flashed another boot image and this time got stuck on the Tegra Note screen but this time it was not flashing on and off. Turned it off but nothing happened, Pressed the key combination to boot to the bootloader mode but failed. I thought I bricked it and then tried to go the the apx mode and was successful. This time I pressed the bootloader key combination and thankfully was successful. I thought I bricked the tablet.
Is there a way to flash the 4.2.2 ROM? Read somewhere that someone flashed the old ROM and the stock recovery. Once done he was able to update to 4.3plus. I thought there was a flashable 4.2.2 ROM at rootjunky.com but when I clicked on the link I got an error message saying that the file does not exist. I asked the poster where he got the ROM and recovery but never got a reply.
I'll try to flash the 4.3 ROM back
homecare tegra note 7
Freeje said:
Here's what I did:
1. Erased the system and flashed the 4.3plus system zip.
2. Erased the boot image and flashed the 4.3plus boot image.
3. Erased the recovery and flashed the bat recovery.
4. Rebooted and got stuck on the Tegra Note screen. (flashing on and off).
Tried to experiment and flashed another boot image and this time got stuck on the Tegra Note screen but this time it was not flashing on and off. Turned it off but nothing happened, Pressed the key combination to boot to the bootloader mode but failed. I thought I bricked it and then tried to go the the apx mode and was successful. This time I pressed the bootloader key combination and thankfully was successful. I thought I bricked the tablet.
Is there a way to flash the 4.2.2 ROM? Read somewhere that someone flashed the old ROM and the stock recovery. Once done he was able to update to 4.3plus. I thought there was a flashable 4.2.2 ROM at rootjunky.com but when I clicked on the link I got an error message saying that the file does not exist. I asked the poster where he got the ROM and recovery but never got a reply.
I'll try to flash the 4.3 ROM back
Click to expand...
Click to collapse
have you tried extracting the Rom and nvflash into the same folder and running the "download.bat" to fix this? I haven't found a nvflash that works with tegra note 7
Tha T said:
have you tried extracting the Rom and nvflash into the same folder and running the "download.bat" to fix this? I haven't found a nvflash that works with tegra note 7
Click to expand...
Click to collapse
Don't know how to do that.
I've managed to flash a 4.2.2 ROM (tried the deodex version first) but not the stock recovery. Funny thing is that only Shaky156's version can be flashed. The big problem with the ROM is that there's no wifi and that sucks big time. It means I can't update the the firmware. Will try to flash the odex version and see the wifi works. There's no access to the files too. Good thing the bluetooth works.
REcovry
pls, what recovery works best with the homecare tegra note? prefarably one that allows backup/restore with external sd card
Freeje said:
I've managed to flash a 4.2.2 ROM (tried the deodex version first) but not the stock recovery. Funny thing is that only Shaky156's version can be flashed. The big problem with the ROM is that there's no wifi and that sucks big time. It means I can't update the the firmware. Will try to flash the odex version and see the wifi works. There's no access to the files too. Good thing the bluetooth works.
Click to expand...
Click to collapse
so did the odex$.2.2 work fine or what solution did you use? And where did you get your 4.2 rom ?
Freeje said:
I've managed to flash a 4.2.2 ROM (tried the deodex version first) but not the stock recovery. Funny thing is that only Shaky156's version can be flashed. The big problem with the ROM is that there's no wifi and that sucks big time. It means I can't update the the firmware. Will try to flash the odex version and see the wifi works. There's no access to the files too. Good thing the bluetooth works.
Click to expand...
Click to collapse
The no wifi problem is endemic of a broken/mismatched boot.img to system version. Get an original (eg EVGA version) boot.img not a modified rooted version, since SuperSU sideloaded will give proper root later on top of an original boot.img.
I have boot.img shared on Tegra Note Discovery thread.
Try using rootjunkie supertool and get new kit kat or flash another ROM very easy to use
Sent from my Moto G using XDA Premium 4 mobile app
Tha T said:
pls, what recovery works best with the homecare tegra note? prefarably one that allows backup/restore with external sd card
Click to expand...
Click to collapse
I can only get Shakys156 recovery to work but it does not have backup/restore to ext sdcard.
recovery
Freeje said:
I can only get Shakys156 recovery to work but it does not have backup/restore to ext sdcard.
Click to expand...
Click to collapse
ok, thanks. And have you finally fixed your wifi issue? I'm on 4.3+ deodex and mine doesn't even rotate the screen
e8hffff said:
The no wifi problem is endemic of a broken/mismatched boot.img to system version. Get an original (eg EVGA version) boot.img not a modified rooted version, since SuperSU sideloaded will give proper root later on top of an original boot.img.
I have boot.img shared on Tegra Note Discovery thread.
Click to expand...
Click to collapse
Are these the files that you're referring to?
TegraNote_bootimg_4p4rip.zip
TegraNote_bootimg_4p3p1rip.zip
I tried flashing the deodex version of 4.3+ and then flashed the boot image (from TegraNote_bootimg_4p3p1rip.zip) but I still get no wifi.
Tha T said:
ok, thanks. And have you finally fixed your wifi issue? I'm on 4.3+ deodex and mine doesn't even rotate the screen
Click to expand...
Click to collapse
No luck. I tried what e8hfff suggested but still got no wifi. I used to have a Korean version of the Galaxy S3 and I could flash the modded ROMS made for the international version only if it is converted. Some guy came up with a converter and you flash it after you have flashed the modded ROM. We might have to get something similar if we want to flash EVGA ROMs.
Right now I'm not that concerned with getting the Kitkat update since there's something wrong with it (write to SD card). Once they have come up with an update to correct the bug then I'll give it another try. SO for now, I'll stick to the 4.3 ROM.
Freeje said:
Are these the files that you're referring to?
TegraNote_bootimg_4p4rip.zip
TegraNote_bootimg_4p3p1rip.zip
I tried flashing the deodex version of 4.3+ and then flashed the boot image (from TegraNote_bootimg_4p3p1rip.zip) but I still get no wifi.
Click to expand...
Click to collapse
Yes try, TegraNote_bootimg_4p3p1rip.zip first as I haven't tested the 4.4 boot.img, and only use the boot.img within as there is another directory of the uncompress boot.
wifi
Freeje said:
No luck. I tried what e8hfff suggested but still got no wifi. I used to have a Korean version of the Galaxy S3 and I could flash the modded ROMS made for the international version only if it is converted. Some guy came up with a converter and you flash it after you have flashed the modded ROM. We might have to get something similar if we want to flash EVGA ROMs.
Right now I'm not that concerned with getting the Kitkat update since there's something wrong with it (write to SD card). Once they have come up with an update to correct the bug then I'll give it another try. SO for now, I'll stick to the 4.3 ROM.
Click to expand...
Click to collapse
Does shaky156's version have a working wifi or any rom at all, (even 4.2) that has wifi, my TN7 is next to useless without it
Hi all,
I have a bit of an issue with the latest OTA update currently being pushed out and looking for help how best to proceed.
I have unlocked and rooted the phone previously and recovery is TWRP. My phone is encrypted.
When I accepted the updated the phone rebooted and showed the TWRP splash screen which flashes on and off endlessly. If I turn the phone off and on again it restarts fine but after a few seconds the update process starts again. I am currently stuck in this loop.
Any advice as to how I can get out of this without wiping my phone?
I am wondering if I could flash the standard recovery to remove TWRP if this would work. Could it and if so, where can i get the standard recovery image.
Thanks and sorry of this is already covered, I searched but couldn't find it.
For XT1575.
http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
If you want to update be on stock rom i.e. unrooted and no xposed,nothing added or removed from system and also flash stock recovery.
After successful update flash twrp.
So, if I want to install the lastest update it's enough to unroot, remove xposed and flash stock recovery? Or it's better to flash full stock through fastboot?
So I managed to find a link to the full image for my device (XT1572 so the above link wouldn't work to the best of my knowledge - but thanks anyway @Hitti2)
I flashed the standard recovery and rebooted which stopped the endless loop. The update still fails to install but I can live with that for now.
I'll investigate further what I need to do to get the update to take properly but for now I have a functioning phone which is a good start to the day.
Thanks all.
Sent from my XT1572 using Tapatalk
Final installment. Update installed and a good. For anyone who stumbles across this with a similar issue, here is what I had to do.
Flash stock boot and recovery images to remove root and TWRP.
Reboot and let the update install.
Reflashed TWRP and SuperSU (both of which are now newer versions)
Job done. Now I know for the next update [emoji6]
There is a whole thread dedicated to this update in general.
lafester said:
There is a whole thread dedicated to this update in general.
Click to expand...
Click to collapse
Maybe there is but as I stated in the OP, I couldn't find the right information at the time of posting. Maybe helpful would be to also link the thread as it may help others.
@lafester could you link thread please.
Sent from my XT1572 using Tapatalk
Boot image?
Thanks for this info. I'm definitely still unable to install this update. I am stock, unrooted. I have flashed the stock recovery image, but not the boot image. Can you please point me to where i can find the stock boot image?
user7743 said:
Final installment. Update installed and a good. For anyone who stumbles across this with a similar issue, here is what I had to do.
Flash stock boot and recovery images to remove root and TWRP.
Reboot and let the update install.
Reflashed TWRP and SuperSU (both of which are now newer versions)
Job done. Now I know for the next update [emoji6]
Click to expand...
Click to collapse
nathlynn22 said:
@lafester could you link thread please.
Sent from my XT1572 using Tapatalk
Click to expand...
Click to collapse
This one possibly?
http://forum.xda-developers.com/moto-x-style/general/xt1575-february-2016-security-update-t3323126
---------- Post added at 10:42 PM ---------- Previous post was at 09:50 PM ----------
chuck-fu said:
Thanks for this info. I'm definitely still unable to install this update. I am stock, unrooted. I have flashed the stock recovery image, but not the boot image. Can you please point me to where i can find the stock boot image?
Click to expand...
Click to collapse
Maybe this one?
http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
Though I am having issues too... stuck at Error! after trying to install update with (what I assume is) stock recovery and boot.
chuck-fu said:
Thanks for this info. I'm definitely still unable to install this update. I am stock, unrooted. I have flashed the stock recovery image, but not the boot image. Can you please point me to where i can find the stock boot image?
Click to expand...
Click to collapse
evandena said:
Maybe this one?
http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
Though I am having issues too... stuck at Error! after trying to install update with (what I assume is) stock recovery and boot.
Click to expand...
Click to collapse
@evandena not that one. That is for a different model, I needed the firmware for the XT1572.
@chuck-fu I found a post here on XDA with a list of download links for various versions. I will dig out the link shortly and post it when I have access to my PC.
I extracted but the recovery and boot image files from that package. What you need are the images as close to possible from what is currently installed on your phone.
Edit: Here is the link to the thread with many Moto X Style images... Hopefully this will help
[Firmware] Moto X Style/Pure Stock Software
Thanks so much for trying to help. I went ahead and flashed the boot and recovery files for my model. I did the Boot image first, no luck. then i did the recovery, and this time andy thought a bit longer before giving me the Error! message. And then instead of my phone doing an autoreboot, it was stuck on the dead Andy and I needed to do hold down the power button to get it to shut down.
Anyone have any additional thoughts?
user7743 said:
@evandena not that one. That is for a different model, I needed the firmware for the XT1572.
@chuck-fu I found a post here on XDA with a list of download links for various versions. I will dig out the link shortly and post it when I have access to my PC.
I extracted but the recovery and boot image files from that package. What you need are the images as close to possible from what is currently installed on your phone.
Edit: Here is the link to the thread with many Moto X Style images... Hopefully this will help
[Firmware] Moto X Style/Pure Stock Software
Click to expand...
Click to collapse
I was having same issue. I am stock, rooted, unlocked bootloader.
Currently using TWRP 3.0
In order to update with the new OTA you need to find a download of the .zip files and manually install it.
If you try to do OTA update it will just keep getting stuck in recovery. To get out of this just cache wipe and reboot.
This phone has never been able to take OTAs for some reason. I wish I understood why. I tried to leave the thing stock to keep things simple, but it wasn't to be... anyway...
Thanks for the advice. Any idea where to get a download of the .zip files (is it really more than one zip file, or was that a typo)? I tried searching, but can't seem to find the right things to search for.
Also, once i have the zip file(s):
1) Do I just install it via TWRP like any other zip file?
2) to get rid of the OTA prompt, do i wipe the cache and reboot before or after i install the update via the zip?
Many thanks!
InFamousD147 said:
I was having same issue. I am stock, rooted, unlocked bootloader.
Currently using TWRP 3.0
In order to update with the new OTA you need to find a download of the .zip files and manually install it.
If you try to do OTA update it will just keep getting stuck in recovery. To get out of this just cache wipe and reboot.
Click to expand...
Click to collapse
I managed to update via OTA flashing the stock recovery, boot and system chunks. This is the procedure I do to update my wife's Nexus 5 and worked for the Moto X Style too. Remember to make a backup before in case something goes wrong.
Thanks for the info- what version do you have? I have the 1575 RETUS and can't find the system file. Is that basically flashing an entire ROM? Sorry, but i've flashed boot and recovery files before, as well as full ROMs but don't ever remember flashing a system file on its own.
Thanks!
Dunkel06 said:
I managed to update via OTA flashing the stock recovery, boot and system chunks. This is the procedure I do to update my wife's Nexus 5 and worked for the Moto X Style too. Remember to make a backup before in case something goes wrong.
Click to expand...
Click to collapse
chuck-fu said:
Thanks for the info- what version do you have? I have the 1575 RETUS and can't find the system file. Is that basically flashing an entire ROM? Sorry, but i've flashed boot and recovery files before, as well as full ROMs but don't ever remember flashing a system file on its own.
Thanks!
Click to expand...
Click to collapse
I have the 1572 RETEU, but you can find the stock firmware here: http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
If it's like the stock firmware that I have for the 1572 it should have all the img files and the system chunks. You just need to flash all the chunks like this:
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
This has to be done because Marshmallow doesn't allow any modification in the system or the boot image, and will not proceed with the OTA if the ROM is not full stock.
EDIT: You will not loose any data, but any modification to the system partition will be undone.
Dunkel06 said:
I managed to update via OTA flashing the stock recovery, boot and system chunks. This is the procedure I do to update my wife's Nexus 5 and worked for the Moto X Style too. Remember to make a backup before in case something goes wrong.
Click to expand...
Click to collapse
Thanks for your help once again. I manually flashed the system files like you listed, but for whatever reason, i'm still getting the same old Error. I'm pretty sure I'm on a stock ROM.
From this site: http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
I have flashed the XT1575 6.0 boot.img, recovery.img, then from the firmware, extracted the 8 sparsechunk files and flashed those as well. I still get the ERROR after a few seconds of trying to load the OTA.
Any other ideas by any chance? Did you do any kind of wiping in there somewhere? Did you just let the normal OTA try installing from within Android?
chuck-fu said:
Thanks for your help once again. I manually flashed the system files like you listed, but for whatever reason, i'm still getting the same old Error. I'm pretty sure I'm on a stock ROM.
From this site: http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
I have flashed the XT1575 6.0 boot.img, recovery.img, then from the firmware, extracted the 8 sparsechunk files and flashed those as well. I still get the ERROR after a few seconds of trying to load the OTA.
Any other ideas by any chance? Did you do any kind of wiping in there somewhere? Did you just let the normal OTA try installing from within Android?
Click to expand...
Click to collapse
I just let the normal OTA install after flashing system, boot and recovery, without wiping any partition. Maybe you can try a flash all the zip to make sure it's full stock and see if the OTA install. Just make a backup before in case nothing change.
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.
This morning I my phone pesented itself in TWRP.
Maybe this is because over the past days I repeatedly got notifications that a system upgrade wanted to install itself (I have a modified 26s X720 from Tora33).
I rejected those notifications.
Now I am stuck in TWRP and I cannot get around it. What I tried:
Reinstalling previous firmware (Tora33 26s) still on the phone
Restoring a TWRP backup from 6 months ago (TWRP didn't see it, maybe it's from a previous TWRP version, I now have v. 3.1)
Flash via fastbood factory image using Mauro's Tool All In One (error message "can't find file mke2fs.conf")
Wipe data, cache, dalvik cache, system; then install Mauro_V2.2 cleansed 23s firmware which I transferred to the phone
Every time it boots up in TWRP.
Your bricked you never flash ota with twrp you should read before doing anything.
The only thing that can help is ofil.
I suggest you study well before trying it.
Sent from my LEX720 using xda premium
mchlbenner said:
Your bricked you never flash ota with twrp you should read before doing anything.
The only thing that can help is ofil.
I suggest you study well before trying it.
Click to expand...
Click to collapse
Oh boy. Thanks anyway. OTA flashed itself, couldn't stop it. Maybe I made it worse by trying to fix.
The bootloader is not locked according to the AIO tool. I can flash succesfully any firmware, only after flashing the phone will still boot in TWRP. It is strange it still boots in TWRP. Is there no simpler trick like flashing the standard recovery and then flashing OFW?
You mention Ofil; do you think the guide described here work?
Wortelstok said:
Oh boy. Thanks anyway. OTA flashed itself, couldn't stop it. Maybe I made it worse by trying to fix.
The bootloader is not locked according to the AIO tool. I can flash succesfully any firmware, only after flashing the phone will still boot in TWRP. It is strange it still boots in TWRP. Is there no simpler trick like flashing the standard recovery and then flashing OFW?
You mention Ofil; do you think the guide described here work?
Click to expand...
Click to collapse
Yes, that QFIL guide is for the x720.
In my opinion, the best way to return stock is to push update.zip into phones main folder, then install stock recovery, then in this one install update zip then check that OS is working. If it is, then go into twrp and wipe. Can't do it?
I'll mention myself;
https://forum.xda-developers.com/le-pro3/how-to/guide-simple-to-return-to-stock-x720-t3618658
marik1 said:
In my opinion, the best way to return stock is to push update.zip into phones main folder, then install stock recovery, then in this one install update zip then check that OS is working. If it is, then go into twrp and wipe. Can't do it?
I'll mention myself;
https://forum.xda-developers.com/le-pro3/how-to/guide-simple-to-return-to-stock-x720-t3618658
Click to expand...
Click to collapse
If he was just going back stock that would work he flash 28s ota with twrp so this will not work.
Sent from my LEX720 using xda premium
No brick after OFW push 28s
The pushed (unvoluntary) update didn't brick my phone after all. This may be important for those that have modified stock ROMs with TWRP.
Not being able to restore OFW was a bug in Mauro's All-in-One tool which he fixed last night. After I could easily flash 20S or 26S stock from his repository. I would also recommend this as safest/easiest procedure. Afterwards you can just flash TWRP from the same tool and move from there.
By the way, immediately after flashing 20s the FW notified it wanted to update itself, again!
n my opinion, the best way to return stock is to push update.zip into phones main folder, then install stock recovery, then in this one install update zip then check that OS is working. If it is, then go into twrp and wipe. Can't do it?
Click to expand...
Click to collapse
Might have tried that
Hi
I was just trying to relock my bootloader on my device, so I patched the boot.img with magisk and ran unlockbl.sh again, it locked it fine but now it boot loops. I tried restoring a backup through twrp (I just boot the image) but doesn't work. Is there a way I can flash the .zip file downloaded from Asus? Anyone have any ideas?
Thanks
mike_1983 said:
Hi
I was just trying to relock my bootloader on my device, so I patched the boot.img with magisk and ran unlockbl.sh again, it locked it fine but now it boot loops. I tried restoring a backup through twrp (I just boot the image) but doesn't work. Is there a way I can flash the .zip file downloaded from Asus? Anyone have any ideas?
Thanks
Click to expand...
Click to collapse
I managed to boot it using the patched_boot.img so I went ahead and unlocked the bootloader again, it's booting now normally but I still wanted to lock the bootloader and put it back to factory settings? I tried booting with the boot.img from the asus website download but it freezes it.
mike_1983 said:
I managed to boot it using the patched_boot.img so I went ahead and unlocked the bootloader again, it's booting now normally but I still wanted to lock the bootloader and put it back to factory settings? I tried booting with the boot.img from the asus website download but it freezes it.
Click to expand...
Click to collapse
Not sure why you want to re-lock the bootloader, but if you do, you've re-enabled image verification, so it won't allow your patched_boot to load. Other changes made are stopping even the factory boot.img from being able to successfully complete.
You can very easily just go back to full stock, by simply installing the entire factory image from the Asus website. Just throw it on your sd card or somewhere on your internal storage that you can find, and install it with TWRP.
HTH
beachfl said:
Not sure why you want to re-lock the bootloader, but if you do, you've re-enabled image verification, so it won't allow your patched_boot to load. Other changes made are stopping even the factory boot.img from being able to successfully complete.
You can very easily just go back to full stock, by simply installing the entire factory image from the Asus website. Just throw it on your sd card or somewhere on your internal storage that you can find, and install it with TWRP.
HTH
Click to expand...
Click to collapse
Hi
Thanks for the help! I have managed to get it back to completely stock with locked bootloader. I am thinking of selling it so wanted it back to stock. I spent ages on it this afternoon! I did try and flash the factory image in twrp before, but it must have been when the bootloader was locked so it wasn't flashing properly (I also probably needed to have the .zip on a sd card rather than internal storage like I had before!) So I flashed it when the bootloader was unlocked and it booted up correctly, after a long anxious wait! Then I booted the patched_boot and it needed to update magisk so I could get su access, copied the unlockbl.sh files to the correct directory and ran the program it locked it and booted up normally, then I factory reset again to get rid of magisk manager.
Thanks again!
mike_1983 said:
Hi
Thanks for the help! I have managed to get it back to completely stock with locked bootloader. I am thinking of selling it so wanted it back to stock. I spent ages on it this afternoon! I did try and flash the factory image in twrp before, but it must have been when the bootloader was locked so it wasn't flashing properly (I also probably needed to have the .zip on a sd card rather than internal storage like I had before!) So I flashed it when the bootloader was unlocked and it booted up correctly, after a long anxious wait! Then I booted the patched_boot and it needed to update magisk so I could get su access, copied the unlockbl.sh files to the correct directory and ran the program it locked it and booted up normally, then I factory reset again to get rid of magisk manager.
Thanks again!
Click to expand...
Click to collapse
Well done ? so glad it got sorted x
Sent from my Asus P027 using XDA Labs