Today I received a notification about System updates on my Panasonic DMC-CM1 (5.0.2, 12.0274) and allowed the update to run. Now every time I reboot I am seeing a warning "System Updates" "Software Update Stopped, Please Try again". If I go to "About Phone" "System Updates" it says "Your phone is up-to-date" but it is still at 12.0274, it should be 12.0300.
I have also tried to install the update by downloading the .DAT file from the Panasonic website and copying it to the "Download" folder of my microSD, and updating from there. I get the same result.
Any ideas?
*bump*
Does anyone on XDA have any experience with the Panansonic CM1?
Same here. Are you rooted? — I reckoned that in my case root might be the culprit.
cybriks said:
Same here. Are you rooted? — I reckoned that in my case root might be the culprit.
Click to expand...
Click to collapse
I WAS rooted, but I unrooted with SuperSU. It makes no difference.
Exactly what I tried – to no avail.
Unrooting with SuperSU does not remove all changes done to the system...
---------- Post added at 02:31 PM ---------- Previous post was at 02:22 PM ----------
What I've tried this far:
unrooting through SuperSU -> nope
re-rooting, uninstallning xposed sdk, unrooting -> nope
re-rooting, re-enabling all services, unrooting -> nope
trying to flash the ealier update -> nope
---------- Post added at 02:46 PM ---------- Previous post was at 02:31 PM ----------
FlashFire gives me "/system/bin/app_process has unexpected content"
You have tried more than me. I tried reinstalling kingroot 4.5, rerooting then unrooting. Nope. This post on DPreview suggests that Developer setting is an issue. I've checked that, no difference for me.
Have you tried factory reset? I've not tried that yet because I haven't backed up this week.
JPCoetzee said:
You have tried more than me. I tried reinstalling kingroot 4.5, rerooting then unrooting. Nope. This post on DPreview suggests that Developer setting is an issue. I've checked that, no difference for me.
Have you tried factory reset? I've not tried that yet because I haven't backed up this week.
Click to expand...
Click to collapse
The "/system/bin/app_process has unexpected content" warning seems to be caused by changes made by Xposed. Uninstalling (by flashing the uninstaller with FlashFire) doesn't seem to do the trick, however.
cybriks said:
The "/system/bin/app_process has unexpected content" warning seems to be caused by changes made by Xposed. Uninstalling (by flashing the uninstaller with FlashFire) doesn't seem to do the trick, however.
Click to expand...
Click to collapse
The .DAT update files are zips. Maybe you could replace app_process32 with the one from 0P...0761_9274.DAT?
Have you tried factory reset?
Factory reset did not work.
However, I give you... *drumroll*... SUCCESS
Make sure you are rooted and that Xposed was properly uninstalled (by flashing the uninstaller with FlashFire)
Navigate with your file browser (I am using Solid Explorer) to /system/bin. (In the settings of Solid Explorer you have to enable display of the root folder)
Locate app_process32
Check whether you have app_process32.orig in the same folder
Change the name of app_process32 to whatever you like. Rename app_process32.orig to app_process32
Unroot.
Update system
The flashing will be done in three increments, with the device rebooting between each increment. Don't freak out, it's not a bootloop. Three circles underneath the android robot are changed to filled circles/dots, one for each increment.
After completing the flash, it took ages during the "optimizing apps"-process, but I was finally greeted with the "Update successful"-notification. The "about this phone"-section in settings now properly states version 12.0300 (though still Android 5.0.2).
Trying to acquire root was more of hit-and-miss. I had to run KingRoot several times, before it worked properly. SuperSU Me gave me different results on every run.
After the first run of KingRoot, it indicated success, but I could not to anything requiring root. SuperSU Me told me that KingRoot was not installed.
I re-ran KingRoot. Now SuperSU Me told me, that KingRoot is installed. Great. Trying to remove KingRoot, SuperSU Me stalled completely. Even KingRoot and the bloatware it installs crashed (giving system warnings). The result after this try basically was no root at all.
I re-ran KingRoot a third time, SuperSU Me works through both stages and notifies me of success. Amazing.
Running SuperSU afterwards however gives me a warning: "Another su-binary seems to be installed. Should I remove it" (or something similar, didn't jot it down).
After choosing yes, and a final reboot, everything seems to be back to normal with proper su, no KingRoot and latest version from Panasonic :good:
cybriks said:
Factory reset did not work.
However, I give you... *drumroll*... SUCCESS
Click to expand...
Click to collapse
I have never installed Xposed so I've never seen this error. Is it installed by Kingroot?
Great news, all the same!
JPCoetzee said:
I have never installed Xposed so I've never seen this error. Is it installed by Kingroot?
Great news, all the same!
Click to expand...
Click to collapse
Not that I am aware of. Take a look into the /system/bin folder and check whether you have app_process32 in differently named versions (I had app_process32 (which was a symlink) and app_process32.orig)
This didn't work for me There was an acc_process32_original and a symlink, but I think it was the SuperSU symlink. Anyway, no go. Back to the drawing board. Factory reset made no difference.
Which version of Kingroot did you use?
While having root, you could try to install FlashFire (if you haven't already). One of Chainfire's amazing tools.
Download the .dat-file to your phone and start to flash it with FlashFire. This will most certainly fail, but instead of simply rebooting upon failure, FlashFire should swiftly show you an error-message. Try to remember that and hunt down the problem by that.
You have to follow what is beeing displayed however, as FlashFire will abort the flashing and reboot just a few moments after displaying the error message.
I used KingRoot 4.65
Update: you probably wouldn't have to follow the display real-time. FlashFire should log to Internal memory > FlashFire > lastlog
cybriks said:
FlashFire should swiftly show you an error-message. Try to remember that and hunt down the problem by that.
Click to expand...
Click to collapse
Flashfire has helped me fix it! What a marvellous tool.
Ages ago I removed GCoupon - Panasonic/Lumix bloatware. Flashfire showed me that the update was failing on "/system/app/Gcoupon/Gcoupon.apk/ has unexpected contents". Gcoupon.apk was actually missing, so I replaced it with the version from the previous update file (0P0000121100000600110761_9274.dat).
I unrooted and restarted the update. After the 3 reboots and "Android is upgrading" I now have 12.0300. Using Kingroot 4.8.0 and Super-SUme I rooted on first attempt.
For my phone (without Xposed) the "app_process32 has unexpected contents error" is a red herring. When SuperSU is installed on a rooted device the app_process32 executable is replaced by a symlink to daemonsu so any update attempted on a rooted phone is bound to fail during the checking stage.
Thanks for your help!
JPCoetzee said:
Flashfire has helped me fix it! What a marvellous tool.
Click to expand...
Click to collapse
Great :good:
I tried to write a sum-up on the other thread as well: http://forum.xda-developers.com/showpost.php?p=65404103&postcount=40
Does anyone know how to get the CM1 into recovery mode? My CM1 is now in a boot loop after a failed panasonic update. The phone had been kingrooted, so that may be a contributing factor.
Anyway, I need to know how to get the phone into enter recovery mode, so I can do a reset.
Thank you.
allmankind said:
boot loop ... phone had been kingrooted, so that may be a contributing factor.
Click to expand...
Click to collapse
Something similar happened with my Sony Z3 (bootloop after kingroot on tablet with locked bootloader) and I had to reinstall the firmware using a Sony PC utility. Unfortunately Panasonic don't provide anything similar (I have asked their tech support).
If it can't be fixed using some generic PC software there is a Panasonic Service Centre here in the UK http://panasonic.dkavs.co.uk/
Thanks, but I am in Thailand. I have been in contact with Panasonic Japan, and they have refered me to Singapore. With the boot loop, it never gets to the stage where ADB can interact with the phone. But hopefully they will have something to allow either a factory reset, or a complete reloading fof the firmware.
As an aside, Japan told me the CM1 is in fact produced by the camera division (DMC-CM1 designation) and not the phone division.
After update firmware to 12.300, wifi tethering not working
DMC CM 1 Lockscreen
hello my CM1 have screenlock i dont know the pin anymore
anyone was able to make a Factory Reset with the phone?
i need some help please how to do a Factory Reset with the phone
it is show me in Windows as Android ADB Interface
or USB multimedia.
but if i use ADB SDK Manager it says Error no Devices found.
#i just need to do a factory reset. i also was trying to remove the Battery but i failed.
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!
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 :/
Hello,
I require some help as my phone has been acting really weird recently. I first bought a Samsung Galaxy S3 GT-I9300 earlier in September that was loaded with ICS. I am currently in Singapore and I got the phone from Starhub.
I attempted to root the phone in ICS, and succeeded in doing so. There were no problems at that point in time.
Recently, there was an update notification that kept prompting me to update to Jelly Bean. There were a few options if I wanted to postpone it: Update now, Remind in 30 minutes, 1 hour, and 3 hours. I found it really irritating, so I eventually just clicked to update it now.
The update went as planned, but when I restarted my phone, my SuperSU refuses to work. When I go into it, it tells me "The SU binary needs to be updated. Continue?" But when I click "Continue", it says Installation Failed! I have tried going to settings, disabling Superuser, and then attempting to use superuser to update the binary. It did not work. When I attempted to disable superuser under settings>SuperSU, it says "Uninstallation failed!"
I attempted to de-root using a guide from GalaxyS3Root website, which told me to download Odin Lite, Odin Kernel and Triangle Away.
However, Triangle Away refuses to work with an error message "Unfortunately, Triangle Away has stopped".
The Odin Lite also refuses to work by saying "Could not detect device model".
Am at a loss as to what to do now...
Tried using Titanium Backup as well, but it seems to be unable to back up my files without using Root.
Please help!!
You have several options. Easiest ones: just backup your stuff and either flash the lastest leak (ELK4) which is already rooted and has extra goodies or simply wipe your phone (get into recovery and factory reset it). Your rom (JB) wasn't rooted to begin with so you won't have root anymore. There's probably a way to do it without wiping but i usually don't bother. It's generally less of a hassle to backup and wipe.
Edit: oh sorry, missed the part where you couldn't backup without root. To be honest, i never use titanium, it always causes problems when i restore stuff. I just backup what i need by hand (sms's with a sms backup app, find my save's files, etc)
Thanks
kaynpayn said:
You have several options. Easiest ones: just backup your stuff and either flash the lastest leak (ELK4) which is already rooted and has extra goodies or simply wipe your phone (get into recovery and factory reset it). Your rom (JB) wasn't rooted to begin with so you won't have root anymore. There's probably a way to do it without wiping but i usually don't bother. It's generally less of a hassle to backup and wipe.
Click to expand...
Click to collapse
Thanks for the speedy reply!
To backup my stuff, I just have to plug my phone to my computer and drag &drop everything, yes?
Sorry I'm very new to the whole android thing, and I'm not very tech-savvy to begin with. When you say Flash the latest leak, how do I do this?
If I factory reset my phone now will I brick it?
That's such an overkill. Just boot into recovery mode and root your phone again with Odin. There are plenty of guides around.
michelleyabc said:
The update went as planned, but when I restarted my phone, my SuperSU refuses to work. When I go into it, it tells me "The SU binary needs to be updated. Continue?" But when I click "Continue", it says Installation Failed! I have tried going to settings, disabling Superuser, and then attempting to use superuser to update the binary. It did not work. When I attempted to disable superuser under settings>SuperSU, it says "Uninstallation failed!"
Click to expand...
Click to collapse
this is because after the update, your phone is no longer rooted.
michelleyabc said:
However, Triangle Away refuses to work with an error message "Unfortunately, Triangle Away has stopped".
Click to expand...
Click to collapse
Triangle Away is not required for rooted, it just resets a counter to 0. nothing very much to it.
michelleyabc said:
The Odin Lite also refuses to work
Click to expand...
Click to collapse
I think the best thing u can do right now is.
1. titanium backup to SD.
2. load a new rom via odin 3.04
3. install cf root to root the phone via odin 3.04
4. install titanium backup and restore your phone.
i know it can be very annoying because all the singaporean ah beng hp shops has no idea now to repair the phone.
(I cant post to the original thread, but im hoping someone here can help me please?)
Ive rooted 6 or so different android phones mainly using cf-autoroot, including an i9300, and never had any issues. But I have had a few issues rooting my 9503 using the cf-autoroot method (method #1 in this post). It aooeared to work, but SuperSU subsequently fell over, and Knox complained but after reading other posts I rectified that, but obviously not quite correctly:
After using cf-autoroot, SuperSU DID NOT appear in the apps list, but Google Play said it was installed but only presented the option to open it (not update or remove).
So I then tried flashing twrp (as per method #2 in this post) which all appeared to go successfully according to Odin. I was expecting to install superSU updater, as per step 3, but recovery mode appeared unchanged/stock so of course I couldnt flash anything as there was no option to do so. Yet there were no errors reported by Odin?
So I then got hold of the app file for SuperSU 1.93 and installed it (via Airdroid). It ran. It found knox. It removed it, and root was installed successfully (as verified by root checkers, titanium backup, droid wall and the like). So I concluded I had successfully rooted my 9305.
But when I reboot SuperSU falls over again on boot up, and the version I added via Airdroid has disappeared, and of course there is no root mode.
But I can then restore root access after a reboot simply by following the same process, namley installing the supersu apk via Airdroid.
Can anyone suggest what is the easiest way to get round this, or even why it's happening? And why is the later version of SuperSU disappearing on reboot?
non persistent SU after rooting Android 4.3 - solved
OK, so Im still unsure how I ended up successfully rooted ,but then reverting back to a non-working or incompatible SU version on reboot (presumably the version installed via cf-root?). It's news to me that an app installed via standard means can be overridden for any reason on reboot. One day someone might explain that or tell me the appropriate phrase to use for my friend google so he can explain it to me.
So what I was then trying to do was install a custom recovery so I could flash the latest SU, as per OP. Try as I might I cant. Even removing the battery once TWRP has been transferred using Odin the standard recovery still prevails. So that one is still unresolved.
But in the meantime, as with most well written apps, the answer is within SU itself. Going into Options in the Su installed via the standard app installer, I selected the option to install that SU as a binary. And it worked, so now SU persists across reboots.
Just in case someone else has the same issue, although judging by all the replies I suspect not (or maybe everyone else is able to post to the original thread, although I dont see this exact problem or solutio there).
If it didnt help anyone, sorry for wasting your time!
Hi,
I have the same problem : my root is lost after each reboot.
I must uninstall SuperSU, then update SuperSU end reboot to have the root again.
Could you give me your solution with simple words because I don't understand what you posted befort. Sorry for my bad english ...
Thanks.
Hello! I am an extremely newbie in rooting so this is my issue. I just rooted my S4 I9505XXUGNH8. I used odin and the root file from chainfire. It passed. So I thought there' s no problem but after 5 hours or so, when I lock my phone it restarts. Plus my bluetooth won't turn on. So I saw this option in SuperSU that I presumed will unroot my phone. I clicked it and say yes. I restarted my phone, the said app was not there anymore. Checked root checker and it says no proper root access or something like that so I thought I already unrooted my phone. I tried even SRS Root, it says that my device has no root. But the issues were still there. I tried to create new file from my sd card so I was expecting it will not work because of that Kitkat sd card restriction stuff but it worked. I tried to update my firmware but the phone didn't allow me because it was modified. So reinstall SuperSU again, and it says SU Binary not found, like that. Now I really have no idea what to do. Please help me. Thanks and sorry for my novel like post.
AdamSanJuan said:
Hello! I am an extremely newbie in rooting so this is my issue. I just rooted my S4 I9505XXUGNH8. I used odin and the root file from chainfire. It passed. So I thought there' s no problem but after 5 hours or so, when I lock my phone it restarts. Plus my bluetooth won't turn on. So I saw this option in SuperSU that I presumed will unroot my phone. I clicked it and say yes. I restarted my phone, the said app was not there anymore. Checked root checker and it says no proper root access or something like that so I thought I already unrooted my phone. I tried even SRS Root, it says that my device has no root. But the issues were still there. I tried to create new file from my sd card so I was expecting it will not work because of that Kitkat sd card restriction stuff but it worked. I tried to update my firmware but the phone didn't allow me because it was modified. So reinstall SuperSU again, and it says SU Binary not found, like that. Now I really have no idea what to do. Please help me. Thanks and sorry for my novel like post.
Click to expand...
Click to collapse
Seems like you might have used the auto root package from another firmware version as this sounds like some kernel issues. Since you know Odin works, then you can just reset and reinstall the NH8. This will get everything backup and running again (you can try not wiping, but possible issues can arise from this too - fair warning and best to backup internal storage to PC for safe keeping). As far as rooting goes afterwards, put Chainfire's SuperSU zip on your phone, find an updated custom recovery such as TWRP, Philz, or CWM and install via Odin. Once installed, you must immediately boot to recovery before the OS loads so you can use the recovery to install the zip or the stock system will rewrite the original recovery to it. Then you will be rooted with no other changes to the phone that could affect functionality or usability.
AdamSanJuan said:
Hello! I am an extremely newbie in rooting so this is my issue. I just rooted my S4 I9505XXUGNH8. I used odin and the root file from chainfire. It passed. So I thought there' s no problem but after 5 hours or so, when I lock my phone it restarts. Plus my bluetooth won't turn on. So I saw this option in SuperSU that I presumed will unroot my phone. I clicked it and say yes. I restarted my phone, the said app was not there anymore. Checked root checker and it says no proper root access or something like that so I thought I already unrooted my phone. I tried even SRS Root, it says that my device has no root. But the issues were still there. I tried to create new file from my sd card so I was expecting it will not work because of that Kitkat sd card restriction stuff but it worked. I tried to update my firmware but the phone didn't allow me because it was modified. So reinstall SuperSU again, and it says SU Binary not found, like that. Now I really have no idea what to do. Please help me. Thanks and sorry for my novel like post.
Click to expand...
Click to collapse
The root for I9505XXUGNH8 is there any just one click root and don't have to use computer
Sent from my GT-I9505