What changed? Why could I root before, but not now? - Blu Vivo Air

I've spent a full day on this and no further ahead.
This is my wife's phone. A few months back (after Lollipop update) she was running into problems that I needed root to solve. I was lazy and tried Kingo Root and it worked on the first shot. Golden.
No problem but I screwed something up by being overzealous with deleting system apps and her cell data stopped working.
No biggie, I unrooted and did a factory reset and all seemed fine. But now I go to root it and... can't. Kingo Root fails.
Why?
But beyond that, I've followed every other tutorial on various other methods and every attempt ends in failure (stalls at startup screen, pre-animation. I've waited >1hr). I've had to reflash stock ROM several times.
In the stock bootloader under Check Root it says the bootloader is locked.
I've put on TWRP no problem, but that's what seems to stall the boot. I've read that TWRP is problematic with this phone and to use CWR (?) instead, but every link is dead, every tutorial regarding it is sketchy.
Advice?

Related

OTA Update Fails

Wtf got the ota update and its starts all good but then it hangs a yellow ! appears.. what can i do? i even did a factory reset i only was rooted and i took care of that.
zero313 said:
Wtf got the ota update and its starts all good but then it hangs a yellow ! appears.. what can i do? i even did a factory reset i only was rooted and i took care of that.
Click to expand...
Click to collapse
at least you are getting something OTA
Ditto
Unfortunately, I get the same thing. I was rooted, but I unrooted (not quite as thoroughly as you did, as I only used the "Unroot" option, but we got the same results). Wonder if it is something wrong with the update...
seanfrisbey said:
Unfortunately, I get the same thing. I was rooted, but I unrooted (not quite as thoroughly as you did, as I only used the "Unroot" option, but we got the same results). Wonder if it is something wrong with the update...
Click to expand...
Click to collapse
Did you change ANYTHING when rooted? Did you freeze, rename, modify or delete ANY of the files in the original ROM in any way, shape or form?
Same thing here
When I bought this device 3 weeks ago, I rooted it with z4root. Not too long after an update disabled z4root on the tablet.
I thought no big deal, but then today comes and I the OTA update won't work.
Anyone more experienced than me have any ideas of how to get this update applied properly?
Me too. Update failed to install. Not sure why. I have also tried unrooting.
FloatingFatMan said:
Did you change ANYTHING when rooted? Did you freeze, rename, modify or delete ANY of the files in the original ROM in any way, shape or form?
Click to expand...
Click to collapse
I'm confused, if I froze an application, didn't unfreeze it but did a factory reset...wouldn't that resolve the issue?
ok so i woke up this morning and my a500 notified me the there was an update available so as you can imagine I was very happy to finally have this, so i updated and when it was done it said update successuful but when I checked it still said 3.01......WTF
Not rooted ever..
Those interested in getting back their OTA, properly backing up their original ROMS or restoring them, please follow the tutorials in this thread:
Going back to stock TUTORIAL
Be helpful and provide your firmware if you have a backup so we can build a database for those who don't.
Be sure to report what is working and what is not working for you once you've tried the tutorials!
Unlike the 14 threads on these matter I take the responsibility as OP to upgrade my original post as firmwares and new info becomes available.
Let's create a focused troubleshooting and tutorial thread,
Thanks.
I'm rooted via gingerbreak and the update worked fine while still rooted. It did break root. Just had to re-apply gingerbreak and all is good, back to root with latest update.
gingerbreak worked with official 3.1 ?
it didn't work with 'leaked' 3.1 ?
OTA
Ok after long night and hours of research i found out a lot.
1 if you have modded ad hoc in wpa_supplicant file recover the original file
2 if you have modded the phone.apk and telephoneyprovider.apk to save battery this is the reason why you won't get the update.
i put these files back and instantly got an update, i mean the exact second i set those back
i can't believe this my updates keep failing to install. FING POS i tried everything, factory reset
i have tried everything, even factory reset, it fails while installing after reboot
acer support are a bunch of retards, they don't even know they sell tablets????????
need help i can't upgrade, it fails every time
does anyone know where the install logs are
the log is \cache\recovery\last-log
Oklahoma City, OK noon CST
First attempt failed:
Changed the wpa_supplicant back to original and all went smooth the second time
I never changed anything and it failed.
**Edit: I rebooted my devices and left it completely alone after unzip and it rebooted into recovery mode and seems to be installing **
I had the same problem, It was pretty disheartening.... but I unrooted my device, re-booted and tried again and SUCCESS!!!
But now I can't get it to re-root using gingerbreak... HELP!
SUCCESS!
Ok. I got OTA update 4.010.08 (122.71 MB) this morning. It failed.
So I unrooted my device. Re-started it and tried again... SUCCESS!
I tried using Gingerbreak to root it again. FAIL!
So I used this: http://forum.xda-developers.com/showthread.php?t=1138228
SUCCESS!
Hope this helps those of you who are having problems.
No need to unroot nor go to stock.
I had the same issues. Then I simply used Acer Recovery to install stock recovery and everything worked fine.
Ceger
Acer Recovery?
Did Acer Recovery come with the tablet?
I tried the update numerous times over the last 4 days. Most of the time the download would fail, which I put down to my slow internet connection and overloaded Acer servers. But about 5 times it would finish downloading and then error out on install with a message about the update being invalid. I tried rebooting several times during this process. I have never rooted the tablet and only have a few apps installed as it was a recent purchase.
Finally it worked when I ejected the external SD card and rebooted. It may be a coincidence, but anyone else who gets the "invalid update" warning during install on an unrooted device may wish to try this prior to the download/install.

???Can't wipe phone/factory reset???

Ok so here is what is going on with my ATRIX... I have searched for answers and not found any so here I am. I wonder if anyone else has seen this. Please note I am not new to flashing, rooting, romming, etc... This week is my first go around with the ATRIX (or any other moto for that matter).
So I went from rooted 1.8.3, unlocked the BL, and was immediately prompted for the 4.51.9 OTA upgrade. I did this and everything was fine when done. No data loss or issues. I of course lost root and the unlock, so I went to taking care of this.
I rerooted but waited a few days and read more before unlock because of known brick issues. I didnt want to be there!
next I decided to try ROM MANAGER to flash CMW. Flashed but of course needed to unlock BL so I used the auto method by mramirez (auto script for known methods). Anyway no matter what I did after unlock I had to reflash everytime the recovery to be able to boot into it. It would not hold, and after 1 or 2 boots I would be back to android stock recovery.
So then I decided to try a rom or to. Flashed ninja and gingerblur with no issues, wiped data, cache, dalvik and rebooted into new rom with all my data still intact!!!! I wiped again, factory reset from recovery... still there! I did a factory reset from within android... still there!!!!
SO.... next I decided I need to flash moto firmware 4.51.9 to get back to stock. Did this and rebooted. Back to stock YES. Rooted-NO. All data still there!
SO... I reunlocked with the method that should have wiped my device and rooted again, install tenfar's CWM. Rebooted and all my stuff is still there!
Guys I am talking everything, accounts, wifi settings, alarms etc. All this flashing and wiping and resetting and I still retain everything!
Anyone care to take a stab at why?
EDIT: So far this time around CWM has stayed put after several reboots but I have not tried a reset today. (It is kinda nice not losing all that but I am pretty sure I should have lost it!)
You just need to delete the following file first:
/system/etc/install-recovery.sh
then you need to install again CWM as you did before.
What is happen is everytimr you reboot the phone is checking the recovery partitions and if the check is different it will rewrite the stock recovery, so you need to delete or rename that file and that will solve the issue...

Unstable & Unusuable

It sounds melodramatic but maybe someone else has encountered the same problem and can help.
I got my phone last week and used it for a couple hours before I decided to root and flash a custom ROM onto the phone. I didn't realize that the kernel had dmverity and proceeded to try and root my phone like any other phone.
I followed the usual steps in installing root for the first time. I used Odin to flash twrp onto the phone and proceeded to restart into recovery. I had forgotten to copy supersu to my phone before I restarted it and this is where my problems began. I swiped on the twrp page where it warns of dmverity but because I didn't transfer supersu I had to restart the phone and get it on. The problem being the phone was now stuck in a bootloop and I somehow managed to get supersu onto the memory and flashed it. I was able to boot into the rom but it was extremely unstable. I could work for maybe 5 minutes before the phone froze, got very hot, then shut down. It would go into a bootloop and succeed maybe 1/20 times, all the while the phone got very hot. I flashed a custom rom onto it and it kind of worked but would still freeze and restart every once in a while. I found the stock bootloader, rom, cp, csc, and flashed those. My phone is now stock everything but the crashes still occur frequently (basically every time I try to use it) and I'm at a total loss as to what to do.
I've rooted all of my phones since I got my S3 several years ago and I've never had a problem like this. Anyone know how I can fix this? My phone is model G935w8 so I know it has the exynos processor and rooting is possible, but I must've done something horribly wrong for it to be like this. Any help is appreciated.

Lost Root Randomly - Re-root is Impossible

I upgraded my Note 4 (SM-N910C) to Android 6.0.1 earlier this year and it's been rooted ever since.
Most recently I was using the Chainfire's systemless root with SuperUserSU and SUhide.
However, when attempting to use toggle root 2 days ago I was given a "No Super User Binary installed" message.
So it seems my device unrooted itself somehow and I've been pulling my hair out ever since trying to re-root it.
Since then I've tried re-flashing SuperUserSU, tried Magisk which had worked in the past and finally tried CF-autoroot.
I've even gone so far as to re-flash my original stock rom, wipe the device and start over with no luck.
I'm 7 hours in today and out of ideas. My Note 4 has not only rid itself of root, but become immune to root.
Firmware Auto-update is off. The only idea I've had is that the device HAS reset while root was toggled off, and I hear this can cause you to lose root. But surely everything I've done should have fixed that.
If anyone has and idea's I'd HIGHLY appreciate the help.

issues while attempting to root...

Hello there all, for the past few hours I've been attempting to root my AT&T Samsung Galaxy S7 Edge (SAMSUNG-SM-G935A). I have had several issues with this process that I am going to detail below, any and help is very, very appreciated.
I believe I have tried this four to five times, to no avail, and each time it has gotten somewhat better I believe.
The first time, I got through the process of using ODIN correctly, it displayed me with the PASS graphic and I continued onward. I went on to the Fast Boot step where I attempted to install SuperSU and it looked like it had worked to me, but this was my first attempt so that honestly doesn't mean much. Anyway, I opened up my phone, SuperSU was not there, and I used the Root Checker. The Root Checker told me it hadn't installed correctly. I pondered for a bit as to what I should do and ran the process again from the beginning. However, the second time I swapped to a better USB port on my PC and there was a difference in the performance of Fast Boot, and SuperSU had installed. I went to my Root Checker, and it again told me that there was no root. I believe I tried once more, I then Factory Reset my device. After I did this, I went through the same process again, following along perfectly to text directions and video tutorials and it installed SuperSU, but no root was there.
I believe I may have done it once or twice since the Factory Reset. Another thing I would like to note about this process was that from the very beginning it has given me the "symptoms of a root". By this I mean the lag, different icons in the carrier bar up top, and possibly more. One other thing I noticed was that even when I had Factory Reset my device, it still gave me the icon on my start up screen. The icon that shows the unlocked lock and says "custom" beneath it.
As I said in the beginning, any and all help is greatly appreciated. Thank you all in advance!

Categories

Resources