I upgraded to 4.0.3R5 a few weeks ago and rooted straight away. The rooting process didn't seem successful until I noticed Titanimum Backup saying I have Root. So I assumed I had and proceeded to restore a backup up my apps and re-install the missing ones from the store. I have now noticed when I power cycle I loose root. Power cycle again and I have root. Everything works fine (except stuff requiring root) until I go back to the Root version of the boot. I have noticed that when I'm on a rooted version I have 2 or more extra apps (the position of SuperSU moves to the next page) and using root explorer I notice my Vendor folder is there, it's missing when I boot and don't have root)
So any idea whats going on ? Is it and easy fix ?
Reroot I had no problems
Sent from my LT28i using xda app-developers app
defsix said:
I upgraded to 4.0.3R5 a few weeks ago and rooted straight away. The rooting process didn't seem successful until I noticed Titanimum Backup saying I have Root. So I assumed I had and proceeded to restore a backup up my apps and re-install the missing ones from the store. I have now noticed when I power cycle I loose root. Power cycle again and I have root. Everything works fine (except stuff requiring root) until I go back to the Root version of the boot. I have noticed that when I'm on a rooted version I have 2 or more extra apps (the position of SuperSU moves to the next page) and using root explorer I notice my Vendor folder is there, it's missing when I boot and don't have root)
So any idea whats going on ? Is it and easy fix ?
Click to expand...
Click to collapse
There are two system partitions.... system0 & system1.... seems yor tab does not like the rooted system so chooses to boot the normal system from time to time. Weird Try to reinstall the rom then reboot and see if your on the same one still. Then reboot couple of times and check.... then proced with root.
Mine was doing this I had r5 and r1a rooted.... it was a pain in the arse too
So do you think I could delete one of the systems?
I will stick it out until the next version is out if it's too much hassle.
Sent from my LT26i using XDA Premium HD app
Check out the all in one tool v5 when it comes out tonight my guess is itll fix ure problem!!
Sent from my LT28i using xda app-developers app
Will try at the wknd.
Sent from my LT26i using XDA Premium HD app
stifilz said:
There are two system partitions.... system0 & system1.... seems yor tab does not like the rooted system so chooses to boot the normal system from time to time. Weird Try to reinstall the rom then reboot and see if your on the same one still. Then reboot couple of times and check.... then proced with root.
Mine was doing this I had r5 and r1a rooted.... it was a pain in the arse too
Click to expand...
Click to collapse
So how do I reinstall the rom? mine came with R5 already installed.
Thanks.
[email protected] said:
So how do I reinstall the rom? mine came with R5 already installed.
Thanks.
Click to expand...
Click to collapse
Use AIO tool. 'Rescue back-door'. Then manually flash the file through recovery. Zip file link in signature and a FAQ including how to flash from recovery.
Well, the "Rescue back-door" was the reason I got to the 50% root in the first place...at least it seems like it. I had root working just fine, then tried "Rescue back-door" AIO 4.0 it asked for update, so I did it, and from that it went south.
Anyhow here are the steps I took to fix this :
I've used AIO 5.2 to unroot (had to boot twice to get to the rooted system), then let it download and install update, which it failed at the end as usual. Then started root process in AIO and during first reboot disconnected usb cable, because from previous experience AIO would fail because after first root it would start system without the previous root steps. Then rebooted tablet and plugged in usb cable, let AIO finish rooting and voila, root stayed after reboot, it fixed it.
I don't know if removing cable actually helped, or v5.2 has better rooting process then v5.0 had, or all this is irrelevant because I was messing with the tablet, flashing and trying and trying until it gave in...
[email protected] said:
Well, the "Rescue back-door" was the reason I got to the 50% root in the first place...at least it seems like it. I had root working just fine, then tried "Rescue back-door" AIO 4.0 it asked for update, so I did it, and from that it went south.
Anyhow here are the steps I took to fix this :
I've used AIO 5.2 to unroot (had to boot twice to get to the rooted system), then let it download and install update, which it failed at the end as usual. Then started root process in AIO and during first reboot disconnected usb cable, because from previous experience AIO would fail because after first root it would start system without the previous root steps. Then rebooted tablet and plugged in usb cable, let AIO finish rooting and voila, root stayed after reboot, it fixed it.
I don't know if removing cable actually helped, or v5.2 has better rooting process then v5.0 had, or all this is irrelevant because I was messing with the tablet, flashing and trying and trying until it gave in...
Click to expand...
Click to collapse
So after a few more days messing with this i'm still stuck. I booted into recovery , performed a factory rest, rebooted and did it again. Then I re-installed a full install of R5 , rebooted, factory reset. When I first boot I have (IRC) 30 apps, powercycle again I have 33 (IRC) apps, it appears I have extra ones that only appear in the vendor directory, again IRC. So rooted both partitions , double booting each time AIO said it was rebooting, I had root on both sides, however certain apps when started on the different partition were losing their settings. So with Root Explorer I decided to do a little trimming on one partition, I deleted the vendor and system folders and the tablet rebooted. So now I have one dead partition and one good. The good one works fine and is rooted, when I reboot it gets stuck in a boot loop at the Sony logo, press and hold the power button for a few secs and it reboots again , apps and settings unaffected.
So how do I have 2 partitions and how do i delete one ?
Related
Today someone asked me to help him. He said when he tried to root, it told him he was already rooted and when he tried to unroot, it said he wasnt rooted. Also 8 failed boot factory reset showed no changes except would result in hang from nook Zergy. I offered my services because I was in town. This is how I got his device working and what I went through. Maybe this will help you.
Story: This guy got his nook tablet from craigs list and it still had all the previous owners information on it. So, not knowing any better, they just went to the menu and used the factory reset option on a rooted device. This caused a wipe, but there were problems. All the personal info was gone, but when trying to reroot with nook zergy, either the script froze or said it was already rooted. After doing the 8 failed reboots- the same happened. Over the next few days I am going to try and video tape this and see if I can recreate it and show you all step by step how to fix it.
Symptoms:
Nook zergy script failing half way or saying already rooted even though there are no root apps or SU after full wipe
What I tried: I tried 8 failed boot reset to fix and it would not completely wipe the root, for some reason, something was still there telling the zergy script that it was still rooted, or would allow initial script to run and freeze
What worked: So, since something still thinks it is rooted and I cant use the unroot app unless there is a super user app to gain permission, the only solution was to download the super user apk, sideload it and then sideload and run the unroot script. After this is done, the unroot script can then get superuser permissions to fully unroot the tablet so the scripts can fully run again. This worked Flawlessly
I hope this helps you, I am going to try to replicate this and shoot a video of it over the next few days.
This Also Seemed to Work...
My root went through fine, but after the root my "n" buttom quit working and
I wound up in almost exactly the same place as above. I got out of it by:
1) Downloaded the "acclaim_update.zip" image found in the thread about Nook 1.4.0 from SDCard above, putting that on an SDCard and the rebooting to run and load it. When it first rebooted, the "n" worked but as is typical with Android
there were "leftovers" (files, etc.) still left from the previous installs.
2) So I went in to Settings and ran the "Erase and Deregister" option which seemed to clean out the leftovers and leave everything where it should have
been.
Hope this helps someone else.
Rev
albertwertz said:
What worked: So, since something still thinks it is rooted and I cant use the unroot app unless there is a super user app to gain permission, the only solution was to download the super user apk, sideload it and then sideload and run the unroot script. After this is done, the unroot script can then get superuser permissions to fully unroot the tablet so the scripts can fully run again. This worked Flawlessly
Click to expand...
Click to collapse
This fix worked for me as well.
I had my tablet rooted and when the ota got pushed out it broke my root. So I went back to 1.4.0 and re-rooted. But the script died halfway through and had the same symptoms listed above. Not fully rooted, but not fully unrooted either.
I had to sideload the superuser app and then unroot. Then start the root process all over again.
Unroot NT but it stops in the registration
I unroot the tablet with the file acclaim, but when i go to the registration come out the error"sorry we're having trouble setting up your nook.please shutdown the device and try again".I try hard reset more times but nothing.Can i by-pass the registration or root the device at start?
andrea89 said:
I unroot the tablet with the file acclaim, but when i go to the registration come out the error"sorry we're having trouble setting up your nook.please shutdown the device and try again".I try hard reset more times but nothing.Can i by-pass the registration or root the device at start?
Click to expand...
Click to collapse
Albert Wertz posted a video showing how but I'm not allowed to post outside links yet. Go to youtube and search for this video: sAASnHPn4PM
albertwertz said:
Today someone asked me to help him. He said when he tried to root, it told him he was already rooted and when he tried to unroot, it said he wasnt rooted. Also 8 failed boot factory reset showed no changes except would result in hang from nook Zergy. I offered my services because I was in town. This is how I got his device working and what I went through. Maybe this will help you.
Story: This guy got his nook tablet from craigs list and it still had all the previous owners information on it. So, not knowing any better, they just went to the menu and used the factory reset option on a rooted device. This caused a wipe, but there were problems. All the personal info was gone, but when trying to reroot with nook zergy, either the script froze or said it was already rooted. After doing the 8 failed reboots- the same happened. Over the next few days I am going to try and video tape this and see if I can recreate it and show you all step by step how to fix it.
Symptoms:
Nook zergy script failing half way or saying already rooted even though there are no root apps or SU after full wipe
What I tried: I tried 8 failed boot reset to fix and it would not completely wipe the root, for some reason, something was still there telling the zergy script that it was still rooted, or would allow initial script to run and freeze
What worked: So, since something still thinks it is rooted and I cant use the unroot app unless there is a super user app to gain permission, the only solution was to download the super user apk, sideload it and then sideload and run the unroot script. After this is done, the unroot script can then get superuser permissions to fully unroot the tablet so the scripts can fully run again. This worked Flawlessly
I hope this helps you, I am going to try to replicate this and shoot a video of it over the next few days.
Click to expand...
Click to collapse
Hi Albert
sorry to be bothering you , but i know your prolly the only one that can help me with this problem i have with my nook tablet
im replying to your reply :
so regarding this , im in need of your help here , same thing happend to me , didnt have superuser and was not fully rooted or not fully unrooted , but i did as you said i sideloaded superuser and unroot off this therd you posted and still the same probleam eco worked problem , what am i doing wrong ... the superuser doesnt seem to pop up when i run unroot ... how can i make superuser work properly ?
hope to can help
- Erik
Hopefully Albert has the answer for you. He's a clever one.
If this post helped click the thanks button!
OKAY, so I was getting my phone ready to flash CM9 when it's released. I used my .iso disk to SBF just fine. Wiped date and cache and got ready to ROOT. I use Pete's Motorola Root tools to do so. Done this a few times, so I know what I'm doing here. It tells me it's "Running Exploit 1 of 3..." Done, reboots. Running Exploit 2 of 3 done. Again, reboots. "Running Exploit 3 of 3......." and it just hung up on that for quite a while. It ended up telling me ROOT access was successful but was unable to push superuser.apk.
So without using the UnRoot my Phone option first, I just decided to hit ROOT again. This time it went through all the stages just fine and superuser is on my phone. I just tested this with ROM toolbox pro and it does grant it SU permissions. I am only wondering if this could have messed up some files somewhere on my phone, somehow. This is the first time ever Pete's 1 click root tool ever gave me an issue. Just curious if I should play it safe and SBF again and try once more to root without issue or if my phone should just be fine as is........ Thanks
RoyJ said:
OKAY, so I was getting my phone ready to flash CM9 when it's released. I used my .iso disk to SBF just fine. Wiped date and cache and got ready to ROOT. I use Pete's Motorola Root tools to do so. Done this a few times, so I know what I'm doing here. It tells me it's "Running Exploit 1 of 3..." Done, reboots. Running Exploit 2 of 3 done. Again, reboots. "Running Exploit 3 of 3......." and it just hung up on that for quite a while. It ended up telling me ROOT access was successful but was unable to push superuser.apk.
So without using the UnRoot my Phone option first, I just decided to hit ROOT again. This time it went through all the stages just fine and superuser is on my phone. I just tested this with ROM toolbox pro and it does grant it SU permissions. I am only wondering if this could have messed up some files somewhere on my phone, somehow. This is the first time ever Pete's 1 click root tool ever gave me an issue. Just curious if I should play it safe and SBF again and try once more to root without issue or if my phone should just be fine as is........ Thanks
Click to expand...
Click to collapse
The EXACT same thing happened to me a few hours ago...it was the first time I had to restart rooting with Pete's and I use it all the time. I checked with Root Checker and TiBU and so far everything has been fine.
Sent from my DROID X2 using Tapatalk 2
Yeah, everything seems fine. I was just wondering if it could have left some broken files on my phone that would cause bugs or glitches after the flash
did you install system recovery/ bootstrap
can you boot into clockwork/ BSR , if you can you should be good
sd_shadow said:
did you install system recovery/ bootstrap
can you boot into clockwork/ BSR , if you can you should be good
Click to expand...
Click to collapse
Yes, that was never a problem. However upon trying to flash CM9 it just hung on installing for over 30 minutes. I just SBF'ed again and rooted with NO issues this time. About to try to flash again. Wish me luck!
Edit: So after I rooted without any problems I tried installing it again and it worked!
Awesome! Enjoy I wonder if it helps is people formatted their system as well before going to cm9? On the dinc2 when going between ginger bread and ics you must wipe system also.
My friend gave me a droid razr which is rooted and has a custom rom installed on it. I was able to charge the device and boot into the OS however the phone simply will not be recognized by the computer. I've tried 3 different cables to no avail, there must be something wrong with the USB port itself.
Is there any way to unroot the device and get back to stock without having to connect the phone to the computer? I am able to put the SD card into a different phone in order to transfer files to it.
Thanks alot in advance
lysdexik said:
My friend gave me a droid razr which is rooted and has a custom rom installed on it. I was able to charge the device and boot into the OS however the phone simply will not be recognized by the computer. I've tried 3 different cables to no avail, there must be something wrong with the USB port itself.
Is there any way to unroot the device and get back to stock without having to connect the phone to the computer? I am able to put the SD card into a different phone in order to transfer files to it.
Thanks alot in advance
Click to expand...
Click to collapse
Using the app SuperSU, there's an option for "full unroot" in the settings. If you plan on keeping the ROM, I wouldn't unroot if I were you. If you DON'T plan on keeping the ROM, then you're pretty much hopeless to remove it without connecting to a computer. Are you sure the drivers are installed for the device? You say the phone charges, so I doubt it's the port. Do USB options show up in the notification tray on the phone when you plug it in to a computer?
Fracta1 said:
Using the app SuperSU, there's an option for "full unroot" in the settings. If you plan on keeping the ROM, I wouldn't unroot if I were you. If you DON'T plan on keeping the ROM, then you're pretty much hopeless to remove it without connecting to a computer. Are you sure the drivers are installed for the device? You say the phone charges, so I doubt it's the port. Do USB options show up in the notification tray on the phone when you plug it in to a computer?
Click to expand...
Click to collapse
There are no usb options that appear in the notification window, and since I posted this the phone has quit charging . I'm not sure how he went about rooting the phone because when I went into the recovery, it was still the stock recovery that was installed. I did a factory reset on the device and when I booted it back up it asked me to activate before I could go any further. I tried using my sim card from my galaxy nexus but it gave me an error. I was thinking that I might bring the phone to verizon and see if it activates with a clean sim card and then look to see if it is still rooted or not.
Also, after further digging I found out that he actually did not install a custom ROM, all he did was root the device. So if I can get into the SuperSU app I will go ahead and unroot the device.
lysdexik said:
There are no usb options that appear in the notification window, and since I posted this the phone has quit charging . I'm not sure how he went about rooting the phone because when I went into the recovery, it was still the stock recovery that was installed. I did a factory reset on the device and when I booted it back up it asked me to activate before I could go any further. I tried using my sim card from my galaxy nexus but it gave me an error. I was thinking that I might bring the phone to verizon and see if it activates with a clean sim card and then look to see if it is still rooted or not.
Also, after further digging I found out that he actually did not install a custom ROM, all he did was root the device. So if I can get into the SuperSU app I will go ahead and unroot the device.
Click to expand...
Click to collapse
From what I know, the ports on the RAZR are poorly designed and prone to break. I had issues with HDMI detection a while ago and had to send it in for repairs.
Factory resets do not unroot the device.When you get the chance to use the SuperSU app (you may have to download it from the market), it should be easy to unroot it, but it's hard to say when the method isn't known.
And as far as I know, can't you just use wi-fi to complete initial setup?
Fracta1 said:
From what I know, the ports on the RAZR are poorly designed and prone to break. I had issues with HDMI detection a while ago and had to send it in for repairs.
Factory resets do not unroot the device.When you get the chance to use the SuperSU app (you may have to download it from the market), it should be easy to unroot it, but it's hard to say when the method isn't known.
And as far as I know, can't you just use wi-fi to complete initial setup?
Click to expand...
Click to collapse
Ok, I got the device activated and yeah it appears that it is still rooted. You mentioned downloading SuperSU off of the marketplace, as only Superuser was installed on the phone.
I downloaded SuperSU and when I try to open it I am getting the error ("There is no SU binary installed, and SuperSU cannot install it. This is a problem!").
So yeah, I am not sure where to go from here, the port is still not working so I need to do something before the battery dies.
lysdexik said:
Ok, I got the device activated and yeah it appears that it is still rooted. You mentioned downloading SuperSU off of the marketplace, as only Superuser was installed on the phone.
I downloaded SuperSU and when I try to open it I am getting the error ("There is no SU binary installed, and SuperSU cannot install it. This is a problem!").
So yeah, I am not sure where to go from here, the port is still not working so I need to do something before the battery dies.
Click to expand...
Click to collapse
Try an app like Root Checker or Got Root? to make sure the device IS rooted. I have messily unrooted a device before and while it WAS unrooted, it left Superuser and Busybox behind.
If it IS rooted, find an app of your choice (System Tuner Pro, Titanium Backup...) and uninstall root apps (Superuser). Cover up root best you can. I've handed a boot-looping device in for repairs with no carrier trouble, so I'm sure you'll be fine.
If it ISN'T... Well, you're hopeless without a computer as far as I can say.
Also, it may not help, but if your device is indeed rooted, you could also go into Superuser, swipe left and try to update the binaries so you can try SuperSU again.
Fracta1 said:
Try an app like Root Checker or Got Root? to make sure the device IS rooted. I have messily unrooted a device before and while it WAS unrooted, it left Superuser and Busybox behind.
If it IS rooted, find an app of your choice (System Tuner Pro, Titanium Backup...) and uninstall root apps (Superuser). Cover up root best you can. I've handed a boot-looping device in for repairs with no carrier trouble, so I'm sure you'll be fine.
If it ISN'T... Well, you're hopeless without a computer as far as I can say.
Also, it may not help, but if your device is indeed rooted, you could also go into Superuser, swipe left and try to update the binaries so you can try SuperSU again.
Click to expand...
Click to collapse
I'm going to try Root Checker right now to see if its actually rooted like you said. I actually updated the Superuser app earlier and SuperSU still wasn't working so I'm starting to think it may have lost root somehow.
I also tried using Superuser Update Fixer and manually flashing the SU binary file from recovery but since the phone is still on stock recovery it wouldn't work.
I was also thinking that I could try and cover up root with titanium backup as you said, that was going to be my last step but since the battery is getting lower and lower I may have to go that route and hopefully not have a problem with Verizon. I guess it also helps that the stock recovery and ROM are still installed on it.
This is just a side project for me, I have a galaxy nexus myself and I have never had any trouble with it.
UPDATE: I just used both of the root checking applications you suggested and they both say that the phone is not actually rooted. Root Checker just spit out a message saying it wasn't rooted and Got Root? said that it located busybox but could not obtain root access. I'm going to try and clean things up with titanium backup.
UPDATE 2: When I installed titanium backup, the app asked me for root permissions and I hit grant. When I open superuser it shows it as giving permission to titanium backup but I can't find Superuser in the list of applications within titanium backup itself. There has to be another way to remove superuser.
UPDATE 3: I just tried to delete the superuser.apk file using root explorer and I get a pop-up saying that it won't allow me to delete that APK because my phone is not rooted. Ugh.. now I'm stuck.
lysdexik said:
I'm going to try Root Checker right now to see if its actually rooted like you said. I actually updated the Superuser app earlier and SuperSU still wasn't working so I'm starting to think it may have lost root somehow.
I also tried using Superuser Update Fixer and manually flashing the SU binary file from recovery but since the phone is still on stock recovery it wouldn't work.
I was also thinking that I could try and cover up root with titanium backup as you said, that was going to be my last step but since the battery is getting lower and lower I may have to go that route and hopefully not have a problem with Verizon. I guess it also helps that the stock recovery and ROM are still installed on it.
This is just a side project for me, I have a galaxy nexus myself and I have never had any trouble with it.
UPDATE: I just used both of the root checking applications you suggested and they both say that the phone is not actually rooted. Root Checker just spit out a message saying it wasn't rooted and Got Root? said that it located busybox but could not obtain root access. I'm going to try and clean things up with titanium backup.
UPDATE 2: When I installed titanium backup, the app asked me for root permissions and I hit grant. When I open superuser it shows it as giving permission to titanium backup but I can't find Superuser in the list of applications within titanium backup itself. There has to be another way to remove superuser.
UPDATE 3: I just tried to delete the superuser.apk file using root explorer and I get a pop-up saying that it won't allow me to delete that APK because my phone is not rooted. Ugh.. now I'm stuck.
Click to expand...
Click to collapse
Yeah... Sorry about your luck
You could try sending it into Verizon still. They may fix it. Perhaps not for free. Even if not at all, at least it's just a side project?
That's about all I can think of :/
Just got to know that Pantech has released the much awaited Jelly Bean 4.1 for the Flex through OTA AT&T software update.
Like many others, I'm using the flex outside US, therefore, cannot update my flex.
Would request someone to upload the OTA JB zip file.
Can't wait to see Jelly Bean on the Flex.
PS: Check out the Pantech website for this great news
This is good news. I wish I wasn't rooted with CWMR so I could get this. Tried flashing stock recovery.img and boot.img files but get NOT SUPPORT.
Anyone know a way to get this phone back to complete stock so we can get the Jell Bean goodness?
I managed to unroot and restore stock recovery.
Got prompted for the update, it downloaded and installed fine!
This little Flex seems quite a bit better with Jelly Bean. Wish it had been 4.2 but 4.1 is fine.
Tersanyus said:
I managed to unroot and restore stock recovery.
Got prompted for the update, it downloaded and installed fine!
This little Flex seems quite a bit better with Jelly Bean. Wish it had been 4.2 but 4.1 is fine.
Click to expand...
Click to collapse
Can you upload the update file?
How did you unroot?
Sent from my PantechP8010 using xda app-developers app
Not rooted anymore so probably can't get the update file. It was like 264MB or something.
Not planning to root this phone again.
Interesting that the Pantech diag menu shows still rooted and tampered, it's definitely not rooted.
It should be 100% stock.
If you know of a way to get the file off the phone I can look for it.
---------- Post added at 01:09 PM ---------- Previous post was at 12:52 PM ----------
I knew from experience I had to go to stock recovery and unroot to update.
I flashed a stock rooted nandroid backup I had made after rooting initially.
To unroot I think I went into the SuperUser app and choose option to unroot.
Stock recovery file is posted in a thread here somewhere, had recovery.img and boot.img.
Tried flashing those in fastboot but only got NOT SUPPORT mesage.
I took a flashable zip file that had CWM recovery.img file in it and replaced it with the stock recovery.img and flashed it in CWM.
Once stock recovery was on the phone when I tried to use it I only got a little android symbol lying on its back with a red exclamation point.
Phone booted fine and worked ok
Couldn't get it to see the AT&T update until this morning.
Things I have noticed in this new Jelly Bean build for our little Flex:
Of the stock AT&T apps only 3 I could disable (ugh), why no Disable button
good news
Tersanyus said:
Not rooted anymore so probably can't get the update file. It was like 264MB or something.
Not planning to root this phone again.
Interesting that the Pantech diag menu shows still rooted and tampered, it's definitely not rooted.
It should be 100% stock.
If you know of a way to get the file off the phone I can look for it.
Click to expand...
Click to collapse
Basically you will find the update in the /cache folder.
I'm not sure if you you can access this folder without being rooted. You can give it a try using the ES File Explorer.
Let me know if you get the update.
ES File Manager did see the cache folder and all the other system folders. It was empty. I'm sorry, I factory reset the phone last night from stock recovery since it was not updating built in apps properly. Never seen stock recovery on this phone before. It has an option for root. I selected it. Downloaded a few root checker apps, not rooted.
I'm sorry if I hadn't reset it last night I might have found the file. I'm sure it will turn up somewhere. This little Flex doesn't have much in the way of development but someone here at XDA will get it sooner or later.
Tersanyus said:
ES File Manager did see the cache folder and all the other system folders. It was empty. I'm sorry, I factory reset the phone last night from stock recovery since it was not updating built in apps properly. Never seen stock recovery on this phone before. It has an option for root. I selected it. Downloaded a few root checker apps, not rooted.
I'm sorry if I hadn't reset it last night I might have found the file. I'm sure it will turn up somewhere. This little Flex doesn't have much in the way of development but someone here at XDA will get it sooner or later.
Click to expand...
Click to collapse
Oh that's bad!
Actually, there's another way. If you can share your system nandroid backup, maybe that can help.
Try Rooting
Tersanyus said:
ES File Manager did see the cache folder and all the other system folders. It was empty. I'm sorry, I factory reset the phone last night from stock recovery since it was not updating built in apps properly. Never seen stock recovery on this phone before. It has an option for root. I selected it. Downloaded a few root checker apps, not rooted.
I'm sorry if I hadn't reset it last night I might have found the file. I'm sure it will turn up somewhere. This little Flex doesn't have much in the way of development but someone here at XDA will get it sooner or later.
Click to expand...
Click to collapse
Why dont you try to root with this method http://forum.xda-developers.com/showthread.php?t=1886460 ,its the same you used to root 4.0.4 I guess, should work, pull out the update and then unroot the phone as you dont want it rooted.
It happened to me, even rooted I wanst able to see /data content with ES File Blablabla, then tried with root explorer and worked fine.
I'm not going to root this Flex. It's not a primary phone for me (never was). It is used as a spare now and can be used by novice users in my family and friends. Don't want them to have a rooted phone. I'd been wanting to get this phone back to complete stock for a while but hasn't really put much effort into it.
When I saw that Pantech released JB for Flex a few days ago that was my motivation to get it back to stock. Frankly I was surprised I was able to get it back to stock and not brick the phone!
I'm uploading the stock rooted rom I have. Luckily I saved that on my computer. It's uploading to Dropbox now so it will take a while.
Thanks for your help
Tersanyus said:
I'm not going to root this Flex. It's not a primary phone for me (never was). It is used as a spare now and can be used by novice users in my family and friends. Don't want them to have a rooted phone. I'd been wanting to get this phone back to complete stock for a while but hasn't really put much effort into it.
When I saw that Pantech released JB for Flex a few days ago that was my motivation to get it back to stock. Frankly I was surprised I was able to get it back to stock and not brick the phone!
I'm uploading the stock rooted rom I have. Luckily I saved that on my computer. It's uploading to Dropbox now so it will take a while.
Click to expand...
Click to collapse
Well, thanks for the file, I'm outside US and even on stock, update notification doesn't prompt.
I got mine back to Stock, but when I hit check for upgrade it says..."Previous session is running. Please Try Later"
I have wiped it several times. any ideas?
Wait...
kneemeister said:
I got mine back to Stock, but when I hit check for upgrade it says..."Previous session is running. Please Try Later"
I have wiped it several times. any ideas?
Click to expand...
Click to collapse
I can see ATT's software updater sucks, we just can wait for our friend's upload.
Here it is: Link removed, Dropbox suspended it.
That should be a stock but rooted rom. Nothing else done to it at all. At least. I had that on the phone for a while as a backup when I was playing with roms for the flex.
Probably only going to leave this link up for a day. I'd make your own nandroid backup first. You'll probably get an md5 error in CWMR but there are instructions for fixing that around. I think it was ADB commands that had to fix it. I know the instructions for clearing the md5 error are in one of the flex rom threads, not that there were many of those. The standard disclaimer applies, if this nandroid backup bricks your phone, I can't help you.
I got the same previous session message too. Then it said no update after wiping. I think the best thing is just wipe and don't check for updates. Leave phone on, wifi on and wait for the phone to check on it's own. I got the prompt in a few hours.
Hope this helps you.
So, need to flash stock recovery after restoring nandroid correct?
Sent from my PantechP8010 using xda app-developers app
Likely if you do not flash stock recovery in CWMR the update will fail. I tried to take the update before flashing stock recovery, it failed each time. I had already unrooted though. Pretty much what I have learned from flashing various phones over the years is that if you are not stock completely any OTA updates from the carrier will fail or soft brick your device.
I think the Flex was one where I had just that issue. There was some AT&T update a few months back, I said to apply it and I got stuck in recovery. Every time I rebooted the phone it just booted to recovery. Found out if I went into the diag screen on the Flex and choose reboot from there I could boot normally. Eventually I figured out I had the wrong boot.img on the phone. Once that was fixed the phone booted fine. But the update never worked.
You can try to take the update with CWMR but I doubt it will work and could brick or soft brick. I've learned to never take an OTA update from the carrier if you are not completely stock.
Still waiting
Tersanyus said:
Likely if you do not flash stock recovery in CWMR the update will fail. I tried to take the update before flashing stock recovery, it failed each time. I had already unrooted though. Pretty much what I have learned from flashing various phones over the years is that if you are not stock completely any OTA updates from the carrier will fail or soft brick your device.
I think the Flex was one where I had just that issue. There was some AT&T update a few months back, I said to apply it and I got stuck in recovery. Every time I rebooted the phone it just booted to recovery. Found out if I went into the diag screen on the Flex and choose reboot from there I could boot normally. Eventually I figured out I had the wrong boot.img on the phone. Once that was fixed the phone booted fine. But the update never worked.
You can try to take the update with CWMR but I doubt it will work and could brick or soft brick. I've learned to never take an OTA update from the carrier if you are not completely stock.
Click to expand...
Click to collapse
Im on stock and I cant update, no root, stock recovery, Ive been waiting for the update and nothing.
I dont know if is because Im outside US
I got mine back to stock and unrooted, but the upgrade still fails at about 25% and reboots. If I clear cache and wipe, it will download again, then fail again. Even after flashing back to stock, recovery still says rooted and so does the software upload screen. But I have confirmed that I am no longer rooted. I am about to give up.
Hello!
A few weeks ago, HTC sends me an update to fix the Heartbleed Bug from Android 4.1. On my device I have root and Xposed. If I install the update, would it remove my root and Xposed? It's my first Android Update after rooting
Thanks,
Weely_XD
I think you have to go back to full stock (Rom,recovery,bootloader locked) to update, so yes update remove root.
Could someone that installed this confirm if root was lost or not?
Thanks!
I will not be changed
romy25 said:
I will not be changed
Click to expand...
Click to collapse
of course not, but what about your phone, LOL
Well, I went ahead and installed the stock recovery and this OTA-update.
Everything seemed fine so I re-installed a new copy of TWRP (same version number as I had before)... Confused me totally. It was asking me to root again as soon as I quit recovery, which I did a few times... But I could never finish the installation of SuperSU. It always failed...
I was messing around with this for 2 days, until I for some reason tried to install TWRP from another "old" file I found on my computer (the exact same file I used when i rooted my phone the first time).
Now everything worked fine...
I guess the other recovery image was corrupt, incorrect, or something else...
Well, the mess was sorted out at least, and I still have root, did not have to reset my phone, and everything else seems to be OK.
Thanks! :good: