Afternoon all!
I'm got the Renovate 1.1 ROM running on my device and all is fine and dandy with it, except that I'm now not able to get into CWM properly.
My phone downloaded the OTA update for Renovate to address some minor issues, rebooted into Recovery and installed them itself, then rebooted. All very well, you may say, but upon restarting it then wanted to do it all over again, saying that the same update was available. Now whenever I try to get into CWM to do anything, all it does is automatically launch the Aroma installer for this damned update over and over, no matter how many times I let it complete the install!
I've tried a factory reset from the bootloader, and even overwriting CWM in fastboot but it still does the same thing. Stuck like this, I can't even reinstall the ROM.
Any thoughts on what I can do to get this sorted? At a loss now and my knowledge is limited.
Thanks.
10xOXR said:
Afternoon all!
I'm got the Renovate 1.1 ROM running on my device and all is fine and dandy with it, except that I'm now not able to get into CWM properly.
My phone downloaded the OTA update for Renovate to address some minor issues, rebooted into Recovery and installed them itself, then rebooted. All very well, you may say, but upon restarting it then wanted to do it all over again, saying that the same update was available. Now whenever I try to get into CWM to do anything, all it does is automatically launch the Aroma installer for this damned update over and over, no matter how many times I let it complete the install!
I've tried a factory reset from the bootloader, and even overwriting CWM in fastboot but it still does the same thing. Stuck like this, I can't even reinstall the ROM.
Any thoughts on what I can do to get this sorted? At a loss now and my knowledge is limited.
Thanks.
Click to expand...
Click to collapse
does the rom still boot up ? if so check for the ota file.zip on the sdcard and delete it !
Mr Hofs said:
does the rom still boot up ? if so check for the ota file.zip on the sdcard and delete it !
Click to expand...
Click to collapse
Thanks for that! Deleted the zip that was store in the OTA folder and then uninstalled the OTA app itself. CWM complained about not being able to find the zip in question, but I was able to wipe the phone and reinstall the ROM (plus the update manually).
Good !
CASE CLOSED !
Related
I have a Verizon GNex, Toro. I was running PA 3.60 4.2.2 and all was fine, but I go the bug for 4.3
I flashed FTL 4.3 rom for toro, had it booted up the first time, and was loading apps and setting up my phone, when it froze after about 15 minutes and I had to pull battery.
I tired to reboot but it got stuck on Google logo for 10-15 each time, nothing would happen, so I wiped and tried to restore my old backups, all of them failed, i try to restore everything but data and is it says successful in TWRP (v2.5.0.0) but when I go to reboot system it hangs again on the Google logo for long periods of time, I've waited upwards of 15 minutes.
I still have the PA 3.60 files in my downloads so I tried to wipe and flash it back on my phone, again it hangs at the Goggle logo and wont go past it.
I can get to the bootloader, I can get to TWRP, but nothing else.
Any advice on what I should try next?
Do I need to flash a stock image? I'm at work at the moment so I will have to wait till later to do it, but at home I have a Mac, which makes things that much more confusing for me.
mhport2 said:
I have a Verizon GNex, Toro. I was running PA 3.60 4.2.2 and all was fine, but I go the bug for 4.3
I flashed FTL 4.3 rom for toro, had it booted up the first time, and was loading apps and setting up my phone, when it froze after about 15 minutes and I had to pull battery.
I tired to reboot but it got stuck on Google logo for 10-15 each time, nothing would happen, so I wiped and tried to restore my old backups, all of them failed, i try to restore everything but data and is it says successful in TWRP (v2.5.0.0) but when I go to reboot system it hangs again on the Google logo for long periods of time, I've waited upwards of 15 minutes.
I still have the PA 3.60 files in my downloads so I tried to wipe and flash it back on my phone, again it hangs at the Goggle logo and wont go past it.
I can get to the bootloader, I can get to TWRP, but nothing else.
Any advice on what I should try next?
Do I need to flash a stock image? I'm at work at the moment so I will have to wait till later to do it, but at home I have a Mac, which makes things that much more confusing for me.
Click to expand...
Click to collapse
Did you flash the new bootloader before you tried to flash the 4.3 ROM? I've heard that it is unnecessary but I would highly recommend using the bootloader designed for the current version of Android. What were the exact steps you took to flash the new 4.3 ROM?
I'm beginning to suspect that people are either getting bad downloads or the data cables being used are not working properly which is causing bad flashes. This is just speculation, but I am using the data cable supplied with my phone and have yet to have one single problem flashing the 4.3 ROM.
jaizero said:
Did you flash the new bootloader before you tried to flash the 4.3 ROM? I've heard that it is unnecessary but I would highly recommend using the bootloader designed for the current version of Android. What were the exact steps you took to flash the new 4.3 ROM?
Click to expand...
Click to collapse
No, I did not flash a new bootloader, I followed the FTL steps he posted except for wiping cache and davilk cache.
Instructions:
1) Download ROM:
Dev-Host: http://d-h.st/s7b
2) Download Gapps:
Dev-Host: http://d-h.st/UDe
Source: http://forum.xda-developers.com/show...38&postcount=1
*** Goo.im Gapps for 4.2.2 did not work. Use other Gapps at your own risk! ***
3) Download SuperSU:
Dev-Host: http://d-h.st/h3h
4) Backup Device
5) Flash the zips in order
Click to expand...
Click to collapse
jaizero said:
Did you flash the new bootloader before you tried to flash the 4.3 ROM? I've heard that it is unnecessary but I would highly recommend using the bootloader designed for the current version of Android. What were the exact steps you took to flash the new 4.3 ROM?
I'm beginning to suspect that people are either getting bad downloads or the data cables being used are not working properly which is causing bad flashes. This is just speculation, but I am using the data cable supplied with my phone and have yet to have one single problem flashing the 4.3 ROM.
Click to expand...
Click to collapse
I downloaded the files directly from chrome on the phone. Is that a problem? That is how I have done most of the ROM's I have ever downloaded.
Try this..
Boot into recovery
Factory reset
Wipe dalvik/cache
Install ROM
Install Gapps
Install SU zip
Reboot
The first boot can take a few minutes so be patient. You'll sit at the "Google" screen for a minute or two then the "android" boot animation for 2-5 minutes. I also wouldn't recommend restoring any backups as I ran into some issues doing this. If you can get the ROM to boot do a fresh install of all your apps from the Play Store.
I never flashed the bootloader and I have had zero problems with flashing and booting 4.3. I dont know what people are doing to have issues. One thing I can think of is after flashing everything and you select restart device, it gives you this option that doesnt usually show up. I cant think of the wording. Something about "erasing flash something or other". there is a whole list of "No" and one line of "erase....". Are people clicking the option to erase and get problems from it? I always just select to go back and it restarts.
jsgraphicart said:
I never flashed the bootloader and I have had zero problems with flashing and booting 4.3. I dont know what people are doing to have issues. One thing I can think of is after flashing everything and you select restart device, it gives you this option that doesnt usually show up. I cant think of the wording. Something about "erasing flash something or other". there is a whole list of "No" and one line of "erase....". Are people clicking the option to erase and get problems from it? I always just select to go back and it restarts.
Click to expand...
Click to collapse
The OP is using TWRP which is what I used and I got no such options.
---------- Post added at 11:47 AM ---------- Previous post was at 11:45 AM ----------
mhport2 said:
I downloaded the files directly from chrome on the phone. Is that a problem? That is how I have done most of the ROM's I have ever downloaded.
Click to expand...
Click to collapse
It could be, I can't speculate on that as I have only downloaded the files to my PC.
jaizero said:
The OP is using TWRP which is what I used and I got no such options.
Click to expand...
Click to collapse
Oh. I never use TWRP. I have never liked it. I dont know how TWRP handles stuff then.
jaizero said:
Try this..
Boot into recovery
Factory reset
Wipe dalvik/cache
Install ROM
Install Gapps
Install SU zip
Reboot
The first boot can take a few minutes so be patient. You'll sit at the "Google" screen for a minute or two then the "android" boot animation for 2-5 minutes. I also wouldn't recommend restoring any backups as I ran into some issues doing this. If you can get the ROM to boot do a fresh install of all your apps from the Play Store.
Click to expand...
Click to collapse
I have tried this a few times now, it just hang at the Google Logo, I have waited 15 minutes now, that shouldn't be right.
mhport2 said:
I have tried this a few times now, it just hang at the Google Logo, I have waited 15 minutes now, that shouldn't be right.
Click to expand...
Click to collapse
My next suggestion is going to be a /system wipe. Not sure If you want to go this route but if you choose to (at your own risk)..
Boot into recovery
Factory reset
wipe dalvik/cache
wipe /system
install ROM
install Gapps
install SU zip
reboot
As a warning if this doesn't work you will not have a booting system. You will be forced to reinstall an older factory image via fastboot.
Do you have a 4.2.2. ROM saved on your SD card that you can install? It might be a good idea to get a booting system first before trying anything else from this point on.
Still nothing works, I formatted all data and do not have an OS at this point.
When I get home I will adb sideload a 4.2.2 rom and gapps (Most likely Mmuzzy for the time being) from my mac and install it in TWRP. I've done this before and it should work and get me out of this mess.
Thanks for your help.
mhport2 said:
Still nothing works, I formatted all data and do not have an OS at this point.
When I get home I will adb sideload a 4.2.2 rom and gapps (Most likely Mmuzzy for the time being) from my mac and install it in TWRP. I've done this before and it should work and get me out of this mess.
Thanks for your help.
Click to expand...
Click to collapse
did it work? i am also having this problem but when i go into my bootloader it tells me my device is tuna even though its a toro if that matters. and to make things wierder when i try to adb it says i dont have fastboot even though i had it less than 3 hrs ago when i was flashing the rom.(supernova) it worked then i shut off and rebooted the next morning and i just get stuck at the google logo. if anyone can help me i would appriciate it.
OK, so I went into TWRP 2.6.0.0 and tried to flash CM 10.2. It came up with an error so I restored using the backup I had made, and after the restore it told me that root permissions had been lost, and asked if I wanted to fix it. I swiped to rix root permissions, and now it doesn't seem to be able to boot up.
It gets through the boot animation fine, bu gets stuck on the final screen where it flashes SAMSUNG across the screen. I can boot back into TWRP and have tried wiping data and starting fresh, installing a different ROM, everything I can to try to get it to start fresh, but the phone always gets stuck at the same screen flashing SAMSUNG.
Any ideas of what I should do to remedy this problem??
BlackHayze said:
OK, so I went into TWRP 2.6.0.0 and tried to flash CM 10.2. It came up with an error so I restored using the backup I had made, and after the restore it told me that root permissions had been lost, and asked if I wanted to fix it. I swiped to rix root permissions, and now it doesn't seem to be able to boot up.
It gets through the boot animation fine, bu gets stuck on the final screen where it flashes SAMSUNG across the screen. I can boot back into TWRP and have tried wiping data and starting fresh, installing a different ROM, everything I can to try to get it to start fresh, but the phone always gets stuck at the same screen flashing SAMSUNG.
Any ideas of what I should do to remedy this problem??
Click to expand...
Click to collapse
Start fresh again but this time in TWRP goto wipe/system that will rid all old rom files which sounds like your issue, worth a shot
SGSIIIJB said:
Start fresh again but this time in TWRP goto wipe/system that will rid all old rom files which sounds like your issue, worth a shot
Click to expand...
Click to collapse
Hopefully I can get a fast response here, I did that, but got a warning "No OS installed" before rebooting. Is that just telling me no ROM installed or does that literally mean that there is not an OS on the phone anymore? The second option seems unlikely but I don't want to risk it and mess things up even further.
BlackHayze said:
Hopefully I can get a fast response here, I did that, but got a warning "No OS installed" before rebooting. Is that just telling me no ROM installed or does that literally mean that there is not an OS on the phone anymore? The second option seems unlikely but I don't want to risk it and mess things up even further.
Click to expand...
Click to collapse
well after you wipe everything including system you need to install a rom. IF your NOT currently OTA updated to 4.3 use billard's zip:::::
[ROM/RESTORE][!MD4 OTA!](5-10)Quick Return to UNROOTED STOCK WITH FLASH COUNT RESET
Wipe everything :/system
Flash billards zip
Flash root.zip to keep root
Flash recovery zip to keep custom recovery
reboot
SGSIIIJB said:
well after you wipe everything including system you need to install a rom. IF your NOT currently OTA updated to 4.3 use billard's zip:::::
[ROM/RESTORE][!MD4 OTA!](5-10)Quick Return to UNROOTED STOCK WITH FLASH COUNT RESET
Click to expand...
Click to collapse
OK, I'll try to find a ROM to install really quickly just in case, but the problem comes in somehow I get an error on every single ROM I try to install, still don't know the issue, as I have installed many ROMs on my One without issue (this is my mom's S3, she just wants tethering to be a native feature on her phone.)
BlackHayze said:
OK, I'll try to find a ROM to install really quickly just in case, but the problem comes in somehow I get an error on every single ROM I try to install, still don't know the issue, as I have installed many ROMs on my One without issue (this is my mom's S3, she just wants tethering to be a native feature on her phone.)
Click to expand...
Click to collapse
If that's the case, I'd recommend this ROM: http://forum.xda-developers.com/showthread.php?t=2549136 I installed the SPHL710_ALLINONE_MK3_ODEX_12-04-2013_1030pm.zip which includes the latest stock 4.3 without all the KNOX stuff and with native tethering.
It also wipes the system partition for you.
Good luck!!
BlackHayze said:
OK, I'll try to find a ROM to install really quickly just in case, but the problem comes in somehow I get an error on every single ROM I try to install, still don't know the issue, as I have installed many ROMs on my One without issue (this is my mom's S3, she just wants tethering to be a native feature on her phone.)
Click to expand...
Click to collapse
Shouldnt be getting any errors installing/switching roms if your wiping correctly, If native tether is all your after then most if not all custom roms come with it enabled or you can keep stock rom and just flash the hotspot mod [MOD][Deodex][Odex][MB1][MC3][MD4][MK3]Hotspot Mod - Working 4G
BAReese said:
If that's the case, I'd recommend this ROM: http://forum.xda-developers.com/showthread.php?t=2549136 I installed the SPHL710_ALLINONE_MK3_ODEX_12-04-2013_1030pm.zip which includes the latest stock 4.3 without all the KNOX stuff and with native tethering.
It also wipes the system partition for you.
Good luck!!
Click to expand...
Click to collapse
Thank you! I will give this one a shot!
SGSIIIJB said:
Shouldnt be getting any errors installing/switching roms if your wiping correctly, If native tether is all your after then most if not all custom roms come with it enabled or you can keep stock rom and just flash the hotspot mod [MOD][Deodex][Odex][MB1][MC3][MD4][MK3]Hotspot Mod - Working 4G
Click to expand...
Click to collapse
I'm just as confused as anyone as to why I'm getting errors. The phone has proper root access and is running on TWRP, the same recovery I use on my One, and I have done at least 50-60 flashes of ROMs on that phone, without issue. I keep getting virtually the same error, something wrong with executing the updater binary in zip.
BAReese said:
If that's the case, I'd recommend this ROM: http://forum.xda-developers.com/showthread.php?t=2549136 I installed the SPHL710_ALLINONE_MK3_ODEX_12-04-2013_1030pm.zip which includes the latest stock 4.3 without all the KNOX stuff and with native tethering.
It also wipes the system partition for you.
Good luck!!
Click to expand...
Click to collapse
The ALLINONE worked! Thank you so much for the help guys! I appreciate it!
I have the AT&T version, but I did S-Off, converted to the Dev Edition (CID BS_US002) and now have the stock recovery back on because I'm trying to apply the OTA update which provides a patch to the GPS.
I've applied a previous OTA successfully (after I went back to a stock recovery, of course).
But this time, it fails partway through and shows the red triangle with exclamation point. I was able to boot the phone to Recovery and do a Vol+ & Power which enabled me to select a handful of different options, chose to do the option of installing an OTA .zip file. Anyways I browsed to the OTA file in internal phone storage, executed it and it stops and fails on the following message: "cimext9.odex has unexpected contents". I am stumped because Google couldn't help. But, something similar happened to another person and they had installed Adaway which must have changed system files. I did have AdblockPlus installed for a while but uninstalled it - so could ABP be the culprit, and now what are my options that would enable this OTA to get installed on my phone?
Thanks in advance. Still learning, appreciate the help this board has provided me so far.
I had the same issue with this update, even though previous ones had installed fine. I didn't have adaway installed and never found out what was causing my issue, in the end I flashed a clean .3 and done the update, which installed fine. Then I used Helium to install all my app data and rooted it after that. Had to setup all my root apps again but now running .4
It looks like I'm going to have to flash the stock ROM again because something apparently isn't stock anymore.
Can I do this but keep the apps installed, contacts, music/files, etc? Or does it go back to factory reset?
When I done it i had to install all my apps and stuff again but there might be a way of saving all your stuff, someone else might be able to help you with that, I haven't had an android device that long
oaklandm said:
I had the same issue with this update, even though previous ones had installed fine. I didn't have adaway installed and never found out what was causing my issue, in the end I flashed a clean .3 and done the update, which installed fine. Then I used Helium to install all my app data and rooted it after that. Had to setup all my root apps again but now running .4
Click to expand...
Click to collapse
Thanks. This will show my ignorance, but by flash the .3, do you mean get the .3 OTA and flash that in the stock recovery, or do you mean grab a .3 nandroid backup?
oaklandm said:
I had the same issue with this update, even though previous ones had installed fine. I didn't have adaway installed and never found out what was causing my issue, in the end I flashed a clean .3 and done the update, which installed fine. Then I used Helium to install all my app data and rooted it after that. Had to setup all my root apps again but now running .4
Click to expand...
Click to collapse
oaklandm said:
When I done it i had to install all my apps and stuff again but there might be a way of saving all your stuff, someone else might be able to help you with that, I haven't had an android device that long
Click to expand...
Click to collapse
Yeah I do not have THAT much, but I've done this a few times and have things just the way I like them. Oh well.
us3rnotfound said:
Thanks. This will show my ignorance, but by flash the .3, do you mean get the .3 OTA and flash that in the stock recovery, or do you mean grab a .3 nandroid backup?
Click to expand...
Click to collapse
I meant grab the nandroid backup, don't know if just a factory restore from the menu would do the job. I just thought that if I'm starting from scratch then I might as well flash .3 : )
Please Anyone...
My phone was in Good status before i went to bed last night... I remembered i was playing music on it before i slept off. I woke up lightly in the middle of the night i heard the music still playing. Tiredly, i pushed the Power button and Switched off the device and continued my sleep.
I woke up this morning to switch on my phone and it started this annoying reboot. It boots up to the homescreen and the next 2 seconds, it freezes , trips off and restart. If allowed to Restart, it would follow the same cycle on and on. I was rooted and running Sickness Insane Hybrid V6. I decided to boot into recovery but could not get into Recovery, it hangs on the TWRP Splashscreen. I have restored the Firmware via Odin, the problem persists... I flashed Philz Recovery via Odin and was able to get into Recovery but when i try to perform Factory & Data Reset, the Phone goes off and restarts....
I have gone back to stock via Odin, Rooted and flashed Philz Recovery via Odin, and tried to flash the Insane Hybrid.... The flashing completes but after booting the phone it kept restarting... I also noticed all my apps are still installed even after Going Back to stock and flashing a new ROM.
Any help on what i can do please?
SOLUTION!!!
Thanks! Thanks!! Thanks!!!
In respect to my previous Device Problem, I found a solution to it and here it is should anyone fall in the same shoe!!!
Since i was Flashing Stock in Odin and Custom ROMs, I noticed all my previously installed apps were still present which i dont expect it to be. Then i though one of those apps would have gone Haywire and causing that problem. So i had to get rid of all the installed apps. I cant do that because the Phone would not settle for me to uninstall them, i can not get into TWRP to wipe all Internal Device... Great i can get into Philz Recovery but can not do a Factory Reset... So i flashed the AROMA File Manager in Philz Recovery which enabled me to access my Device files. I navigated to "data/app" and deleted all the Apps. I exited the recovery, Flashed stock in Odin and Voila!!!!
PROBLEM SOLVED!!! No more restarts!!! But the TWRP i used to flash before still would not load up... Still hangs on the "TEAMWIN" splashscreen. Should solve that too soon....
Thanks...
Incase, this solution worked for you... Give me a Thumb!!! CatchYah!!!
?
Pp.
PanchoPlanet said:
?
Pp.
Click to expand...
Click to collapse
Hello please, can you point out to any Flashable Wipe Script to wipe my Device?
Using Aroma FM in Recovery, i noticed tonnes of some error files, if i decide to mark and delete them, it hangs up... My device can no longer boot to Homescreen. How can i wipe my Device please.... System,Data, Cache.... If possible all the folders in the Device.
Sounds like you need to flash stock firmware using odin.
Start fresh with full wipes, don't know anything about this aroma fm in recovery stuff (probably cause of your problem ), keep it simple.
Flash stock run phone for several hours, see if everything works properly.
If you can't live without a custom recovery use CWM, I see a lot issues concerning twrp in posts all the time.
Pp.
PanchoPlanet said:
Sounds like you need to flash stock firmware using odin.
Start fresh with full wipes, don't know anything about this aroma fm in recovery stuff (probably cause of your problem ), keep it simple.
Flash stock run phone for several hours, see if everything works properly.
If you can't live without a custom recovery use CWM, I see a lot issues concerning twrp in posts all the time.
Pp.
Click to expand...
Click to collapse
Thanks, But i have being getting the problem even before trying to use AROMA File Manager.... I only use AROMA FM to see if i could manually delete every folder in the phone. I have FLASHED STOCK over a Hundred times.... Its still the same!!!
Now, after some more researches... i was asked to use the Re-Partion option on Odin with a PIT File... Please can you point out to where i can get SGH-M919 Pit File?
Have never used a pit file but have seen requests for it in development, ShinySide has a semi stock ROM and may have it for you. Flashing a pit file can be tricky so proceed with caution and follow instructions to the letter. Maybe putting a request for it with instructions in ShinySide's thread can get you fixed up.
Here .…..... http://forum.xda-developers.com/showthread.php?t=2873695
Pp.
sent from my microwave running lollipop 5.0.
Following want to now how this turns out so I can fully fix my buggered device.
strtkempo said:
Following want to now how this turns out so I can fully fix my buggered device.
Click to expand...
Click to collapse
Sorry i'm replying late. Already fixed my Device... Can yo explain the current Bug State of your Device and the present behaviour...
Always Quote or Mention me so i can always attend to it...
I have rooted firetv 1 with latest rBox pre-rooted ROM. I have noticed if I put the box in sleep mod for a while, it will change to TWRP recovery screen when wake it up. I have to reboot it every time in order to back to normal. Anyone has the same problem?
Thanks.
Seattleweather said:
I have rooted firetv 1 with latest rBox pre-rooted ROM. I have noticed if I put the box in sleep mod for a while, it will change to TWRP recovery screen when wake it up. I have to reboot it every time in order to back to normal. Anyone has the same problem?
Thanks.
Click to expand...
Click to collapse
Most folks that have had this problem is because they did not block updates properly. And you have an update in the hopper. And TWRP being your last line of defense is blocking the installation of that update since it is not a PreRooted ROM. So each time your device is idle it tries to install the update. And TWRP stops it at reboot.
Luckily there are solutions.
http://www.aftvnews.com/how-to-stop...rom-installing-on-a-fire-tv-or-fire-tv-stick/
And at the very least do Method 1. But both Method 1 & Method 5 are what is recommended to stop this from happening in the future.
http://www.aftvnews.com/how-to-block-software-updates-on-the-amazon-fire-tv-or-fire-tv-stick/
Y314K said:
Most folks that have had this problem is because they did not block updates properly. And you have an update in the hopper. And TWRP being your last line of defense is blocking the installation of that update since it is not a PreRooted ROM. So each time your device is idle it tries to install the update. And TWRP stops it at reboot.
Luckily there are solutions.
http://www.aftvnews.com/how-to-stop...rom-installing-on-a-fire-tv-or-fire-tv-stick/
And at the very least do Method 1. But both Method 1 & Method 5 are what is recommended to stop this from happening in the future.
http://www.aftvnews.com/how-to-block-software-updates-on-the-amazon-fire-tv-or-fire-tv-stick/
Click to expand...
Click to collapse
Thanks you very much. I believe I did one BEFORE flash to new pre-root ROM. I tried to do it again this morning, found the superuser is not there anymore after flash to pre-root ROM from rbox. I am confused since I rooted firmware and unlocked bootlocker. I does not me to install superuser anymore. Please help me:crying::crying::crying:
Seattleweather said:
Thanks you very much. I believe I did one BEFORE flash to new pre-root ROM. I tried to do it again this morning, found the superuser is not there anymore after flash to pre-root ROM from rbox. I am confused since I rooted firmware and unlocked bootlocker. I does not me to install superuser anymore. Please help me:crying::crying::crying:
Click to expand...
Click to collapse
If you are able to still go into TWRP. I would try to flash the latest PreRooted ROM using a USB Stick. Also make sure you include a MD5 for safety. DO NOT WIPE anything but Dalvik Cache & Cache. See if that restores your PreRooted FW back to normal. This is just a guess since it has never happened to me before.
Maybe someone with this problem the fixed things can chime in. Others that this has had happened to did not have access to TWRP.
Y314K said:
If you are able to still go into TWRP. I would try to flash the latest PreRooted ROM using a USB Stick. Also make sure you include a MD5 for safety. DO NOT WIPE anything but Dalvik Cache & Cache. See if that restores your PreRooted FW back to normal. This is just a guess since it has never happened to me before.
Maybe someone with this problem the fixed things can chime in. Others that this has had happened to did not have access to TWRP.
Click to expand...
Click to collapse
FIXED!!!
I tried to install superuser apk , but failed. Since I still have access to TWRP, I installed with flashable superuser. Then I cleared OTA and blocked the updates again with your suggestion. I did Method 1 before, but forgot to do it again after update. Thank you very much!!!
Seattleweather said:
FIXED!!!
I tried to install superuser apk , but failed. Since I still have access to TWRP, I installed with flashable superuser. Then I cleared OTA and blocked the updates again with your suggestion. I did Method 1 before, but forgot to do it again after update. Thank you very much!!!
Click to expand...
Click to collapse
np, glad it is back to normal.
Method 1 helps when you flash a new PreRooted ROM. And Method 5 helps to make sure your FW version is never low enough to think an update would apply to your device. Method 5 needs to be redone when ever you flash a ROM. And Method 1 must be redone when ever you factory reset thru TWRP or clean more then the Dalvik Cache & Cache thru TWRP. NEVER do a factory reset from FireOS 5. Only use TWRP for that.
Forgot to add. NEVER INCLUDE SYSTEM IN ANY OF YOUR WIPES. Flashing a PreRooted ROM will take care of System. So leave it alone. Most bricks happen because folks wipe SYSTEM & they do not Flash a PreRooted ROM before doing a reboot.