Related
Hello,
Ii have rooted my S4 device with the procedure from XDA (root original rom with keeping update availability). This was done succesfully. After that TWRP was flashed without problems. Than i decided to installl Omega 9 custom rom. The installation went fine and i could use it for three days. A great rom but after a restart my device will not boot anymore and shows only the Samsung logo. Wiping is possible but trying to restore a backup failed....... Do i have to apply root again? Any help is appreciated to solve my problem! Thanks a lot.
Best regards,
Mark
Dataking said:
Hello,
Ii have rooted my S4 device with the procedure from XDA (root original rom with keeping update availability). This was done succesfully. After that TWRP was flashed without problems. Than i decided to installl Omega 9 custom rom. The installation went fine and i could use it for three days. A great rom but after a restart my device will not boot anymore and shows only the Samsung logo. Wiping is possible but trying to restore a backup failed....... Do i have to apply root again? Any help is appreciated to solve my problem! Thanks a lot.
Best regards,
Mark
Click to expand...
Click to collapse
Go to recovery and try wipe cache dalvik and fix permissions and reboot should work fine
.
Wipe Dalvik cache shows error: FAILED
Dataking said:
Hello,
Ii have rooted my S4 device with the procedure from XDA (root original rom with keeping update availability). This was done succesfully. After that TWRP was flashed without problems. Than i decided to installl Omega 9 custom rom. The installation went fine and i could use it for three days. A great rom but after a restart my device will not boot anymore and shows only the Samsung logo. Wiping is possible but trying to restore a backup failed....... Do i have to apply root again? Any help is appreciated to solve my problem! Thanks a lot.
Best regards,
Mark
Click to expand...
Click to collapse
Install Philz Touch recovery in downloadmode, this will help you http://d-h.st/wSF.
I reflashed Philz Touch with ODIN successfully but the recovery mode did not came up. How is this possible? Back to TWRP now with same problems......
If you already have the omega 9 rom in your phone...try to reflash it via recovery .....don't have to wipe data....but do it to be safe....I think it should work...I really hope it works...sorry about your phone
sadeshmagic said:
If you already have the omega 9 rom in your phone...try to reflash it via recovery .....don't have to wipe data....but do it to be safe....I think it should work...I really hope it works...sorry about your phone
Click to expand...
Click to collapse
Already flashed it several times but still hanging in the boot and no way to use the phone.
Dataking said:
Already flashed it several times but still hanging in the boot and no way to use the phone.
Click to expand...
Click to collapse
Well the only other option is to download a ROM that can be flashed via Odin.....hopefully your download mode works.....i think you can find several compatible ROMs in the forums.....try that out....as a last resort
sadeshmagic said:
Well the only other option is to download a ROM that can be flashed via Odin.....hopefully your download mode works.....i think you can find several compatible ROMs in the forums.....try that out....as a last resort
Click to expand...
Click to collapse
Well, download mode works fine, TWRP works fine, flashing ROM works fine, ROM itselfs works great, until i have to reboot. After booting it hangs in the boatloader and i have to flash rom again.........................to get access.
Dataking said:
Well, download mode works fine, TWRP works fine, flashing ROM works fine, ROM itselfs works great, until i have to reboot. After booting it hangs in the boatloader and i have to flash rom again.........................to get access.
Click to expand...
Click to collapse
Well do you merely flash the ROM? try wiping cache afterwards and setting permission....if that doesn't work try to reflash stock firmware....thats your best bet
:good::good::good::good:
I found the solution using method 3:
http://www.ibtimes.co.uk/articles/4...i9500-gti9505-unbrick-softbrick-hardbrick.htm
This will help some other people too.
Hi,
I previously had purity rom on my nexus 10. I decided to back to stock and use the xposed framework. So with 4.4.3 I flashed the stock images (manualy so it didn't wipe my sdcard partition), wiped data, cache and dalvick.
Stock 4.4.3 works fine, no issues here, but in acquiring root by flashing supersu update (both 93 and 99r3) root doesn't seem to stick. I can adb in and su from terminal, but when booting android supersu days it couldn't acquire root. I have tried other clockworkmod recovery and team win recovery so see if it was a bug with recovery, but no dice. Clockwork did occasionally say it lost root and press Yes to put it back, it did this on my nexus 5 and I still kept root.
I have even tried the universal nexus toolkit but that didn't work either. All methods I have tried have run the zip output fine, saying success.
Any ideas what's wrong. I assume I have done something wrong but can't find much information about root not working like this.
Did you try chainfire 2.00?
Link to Chainfire page
Hi,
Some time ago I've faced the same issue as you, what worked for me was using an older supersu flashable zip and after flashing it I flashed the latest. Don't know if it was placebo or something, but always worked for me .
~Lord
I did the exact same couple days ago after running Omnirom. I used this odex stock image http://forum.xda-developers.com/showthread.php?t=2529492
After the initial factory wipe I wiped dalvik,cache,data, and flashed SU after flashing the ROM but before reboot. Using latest TWRP. Hope this helps.
Hi guys im a bit rusty again in all this since i rooted my S3 and HTC desire years ago ,
I have an Galaxy S5 SM-G900F (bought seperately without any provider)(EU)
after 2-3 months now and getting the official android 5.0 upgrade, i thought it be time to Root my device again ,
i followed this link and how to from ChainFire "http://forum.xda-developers.com/showthread.php?t=2696537"
wich i been using on my Galaxy Tab 7 Lite(T110) as well and worked flawlessly
I followed the exact steps as usual , rooting went fine, phone rebooted as it should , i updated SUPERSU and its binaries and installed Ericson's Busybox,. ,and everything worked as it should ,
then i put off my phone and boot in to recovery mode to flash the Philz_touch_6.26.1-klte.zip (touch recovery)
when im in my stock recovery i facepalm'd myself because i hadnt put the flashable recovery file on my internal storage yet ,
so i wanted to reboot back in the phone so i could put the file on my internal storage so id be able to flash it from stock recovery ,,..
this is where it all got strange,.
My phone stays black after Boot logo, gives me errors like ,. SYSTEM UI STOPPED ,. and so on for about everything that keep the phone running , i mean really everything STOPS , after about 15 minutes and klicking away all the Stopped msg's , it just reboots again to do the same.
i tried starting the phone in SAFE MODE ,. . Same thing,...
this all just came up after i booted to STOCK RECOVERY ,. and back to Android without changing anything,.
Android 5.0
Stock Rom
CF Autoroot klte SM-G900F
Please help ?
Thank you in advance
Mike130784 said:
Hi guys im a bit rusty again in all this since i rooted my S3 and HTC desire years ago ,
I have an Galaxy S5 SM-G900F (bought seperately without any provider)(EU)
after 2-3 months now and getting the official android 5.0 upgrade, i thought it be time to Root my device again ,
i followed this link and how to from ChainFire "http://forum.xda-developers.com/showthread.php?t=2696537"
wich i been using on my Galaxy Tab 7 Lite(T110) as well and worked flawlessly
I followed the exact steps as usual , rooting went fine, phone rebooted as it should , i updated SUPERSU and its binaries and installed Ericson's Busybox,. ,and everything worked as it should ,
then i put off my phone and boot in to recovery mode to flash the Philz_touch_6.26.1-klte.zip (touch recovery)
when im in my stock recovery i facepalm'd myself because i hadnt put the flashable recovery file on my internal storage yet ,
so i wanted to reboot back in the phone so i could put the file on my internal storage so id be able to flash it from stock recovery ,,..
this is where it all got strange,.
My phone stays black after Boot logo, gives me errors like ,. SYSTEM UI STOPPED ,. and so on for about everything that keep the phone running , i mean really everything STOPS , after about 15 minutes and klicking away all the Stopped msg's , it just reboots again to do the same.
i tried starting the phone in SAFE MODE ,. . Same thing,...
this all just came up after i booted to STOCK RECOVERY ,. and back to Android without changing anything,.
Android 5.0
Stock Rom
CF Autoroot klte SM-G900F
Please help ?
Thank you in advance
Click to expand...
Click to collapse
Boot to recovery, wipe the caches, reboot, see how you get on then
*Detection* said:
Boot to recovery, wipe the caches, reboot, see how you get on then
Click to expand...
Click to collapse
thank you for your reply
i have wiped the Cache partitions as its the only cache to wipe in stock recovery,. rebooted ,. but still the same thing
Mike130784 said:
thank you for your reply
i have wiped the Cache partitions as its the only cache to wipe in stock recovery,. rebooted ,. but still the same thing
Click to expand...
Click to collapse
Did you use the latest version of ODIN to flash the CF Root?
Think Odin3 v3.10.6 is the latest current version
If you used an old version, try flashing it again using the new one, other than that, I can only suggest trying to fix permissions in recovery if it has that option, TWRP should have it, and finally a factory reset, which is not ideal
*Detection* said:
Did you use the latest version of ODIN to flash the CF Root?
Think Odin3 v3.10.6 is the latest current version
If you used an old version, try flashing it again using the new one, other than that, I can only suggest trying to fix permissions in recovery if it has that option, TWRP should have it, and finally a factory reset, which is not ideal
Click to expand...
Click to collapse
i used Odin3-v3.07
but after flashing the root everything worked installed superSU and updated it and its binaries and installed busybox,.
it all stopped working after i went into Stock Recovery and back
id prefer not to do a factory reset Wipe,. unless i really have to to fix it ,.
im going to try reflash with the latest version then,.
i have swapped SD card to galaxy tab to put the Flashable touch recovery on the SD card, and swapped back to the phone so i could Flash the Recovery when im in stock ,.
but ill try flashing Root with latest Odin first.. thank you
*Detection* said:
Did you use the latest version of ODIN to flash the CF Root?
Think Odin3 v3.10.6 is the latest current version
If you used an old version, try flashing it again using the new one, other than that, I can only suggest trying to fix permissions in recovery if it has that option, TWRP should have it, and finally a factory reset, which is not ideal
Click to expand...
Click to collapse
the new odin is a bit less informative (to me as beginner)
i managed to use AP to flash the root again
all goes fine , it reboots
and its now upgrading android as it says and opening app's
then Black screen again,. i klick a button,. and it shows me again all the STOPPED msg's of all internal apps that are crashing,. litterally all apps,
what can i do ?
If clearing cache didn't work, fixing permissions in recovery didn't work, only thing left I can think of is factory reset
--
*Detection* said:
If clearing cache didn't work, fixing permissions in recovery didn't work, only thing left I can think of is factory reset
--
Click to expand...
Click to collapse
i cant fix persmission in stock recovery and flashing the philz touch recovery didnt work something about not verify signature,.
al i can do i guess is wipe data factory reset ,.but im affraid it wont fix anything
Try TWRP recovery instead
http://teamw.in/project/twrp2/229
No reason a factory reset won't fix things, worst comes to worst, flash the whole ROM again from ODIN, that will fix everything as it wipes and reinstalls the lot
Grab a stock ROM from sammobile
Thank you for all your replys mate..
I managed to get it working again by doing a factory reset in stock recovery after I flashed root with latest odin
Even tho it was my last resort there was nothing else I guess .
I'm not sure tho if this will happen again when I go back to recovery like I did when this all happend the first time while I actually want to flash a more advanced recovery then stock recovery ..
But I'll take my chances and just leave it as it is
Again thank you for your help and suggestions .
This thread could be closed
Sent from my SM-G900F using XDA Free mobile app
Pleased you got it working again, I would say if you think you might want to flash another advanced recovery in the future, it might be best to do that now since you have already factory reset the phone, that way if this happens again, you don't lose months of data and settings and files that you have gathered between now and whenever you decide to flash recovery
*Detection* said:
Pleased you got it working again, I would say if you think you might want to flash another advanced recovery in the future, it might be best to do that now since you have already factory reset the phone, that way if this happens again, you don't lose months of data and settings and files that you have gathered between now and whenever you decide to flash recovery
Click to expand...
Click to collapse
i have actually ,. i installed the TWRP u mentioned,. by taking there app from the Playstore,. and flashed the new recovery, within android and without rebooting (just in case)
im used to the old CWM thats why i first wanted the Touch recovery as its based on it,
but always open for trying new things
Thank you
Good stuff
Id say the whole entering recovery / apps crashing thing was a problem with the ODIN version you used to root, too old for Lollipop is my guess, so I wouldn't worry about entering recovery again.
Background: So i bought this used S5 900f from someone and it gave me "recovery is not seandroid enforcing" error while rooting and installing recovery. i found a workaround for this error by immediately pulling the battery trick after root. I have installed TWRP and root and they work but this "Recovery is not seandroid enforcing error" still displays when i try to enter recovery for about 2-3 seconds and then the recovery boots.
Now the Problem is : My s5 900f is not saving Wifi password on any of the lollipop builds i have tried Many UK 5.0 (BTU) Builds from Sammobile , and Nordic Countries 5.0 as soon as i restart or shutdown m phone Wifi password is reset and i have to enter it again after turning my phone on again. Surprisingly When i downgrade to any of the kitkat Builds Wifi starts saving passwords just fine?
Things i have tried
Format, Clear dalvik cache, cache, data, system, internal Storage and install different 5.0 builds.
Enabling disabling Google backup, it doesn't help.
Kindly Help me out does Wifi not saving password has anything to do with this "Seandroid not enforcing Error" . And how to fix this issue i am at verge of smashing this phone. .....:angel:
http://forum.xda-developers.com/galaxy-s5/general/s5-forget-wifi-passwords-reboot-fix-t3105976
Thanks alot buddy, you just saved my phone....Phewwww do you know why it happened in the first place?
Buggy ROM is all I can think, it happened to me with a clean install of the latest LP ROM so I went looking for a fix for myself
I tweeted to Samsung UK about it, and they just talked to me like I was stupid, I guess they don't want to admit to it being their fault
UPDATE NOW after the build prop fix, i rebooted fine once... After installing TWRP the phone is crashing on boot up....touchwiz crashes along with all other programs it wont let me boot up. Maybe TWRP messed something up.
Try clearing the caches from recovery, the build.prop fix doesn't cause any issues like that, but I've had issues after flashing custom TWRP before, generally clearing caches / pulling battery fixes it
*Detection* said:
Try clearing the caches from recovery, the build.prop fix doesn't cause any issues like that, but I've had issues after flashing custom TWRP before, generally clearing caches / pulling battery fixes it
Click to expand...
Click to collapse
does your phone display "recovery is not seandroid enforcing" just before entering twrp? i tried clearing cache and battery pulling didnt work....now flashing earlier 5.O btu.
Yea, just means it's a custom recovery
*Detection* said:
Yea, just means it's a custom recovery
Click to expand...
Click to collapse
Some folks are able to flash any 5.0 build and they don't get the Build.Prop issue. i just reflashed and the issue came back...will re edit the build.prop till now i have rooted + installed TWRP no issues so far only build.prop left to be edited..... could you please tell me why is it persistent on some phones that even reflashing, formating doesn't help.
Unfortunately Nothing works....I have been more than patient with this device...been flashing and trying different things for 18 hours now. It works fine but after going to recovery (Just by entering it) and then rebooting will freeze my phone with "Unfortunately Media storage has stopped working...and everything else like touchwiz also crashes".......i was so...so wrong to move to a samsung This Definitely is my last samsung phone...for now i will keep trying different things.
Try a different recovery, Philz Touch, CWM etc
Are you definitely flashing the latest TWRP?
The way I install TWRP is using TWRP Manager from G Play store
https://play.google.com/store/apps/details?id=com.jmz.soft.twrpmanager&hl=en_GB
Install BusyBox first or it'll prompt you before doing anything
https://play.google.com/store/apps/details?id=stericson.busybox&hl=en_GB
The defaults it prompts you to change for locations can be left as they are
*Detection* said:
Try a different recovery, Philz Touch, CWM etc
Are you definitely flashing the latest TWRP?
The way I install TWRP is using TWRP Manager from G Play store
https://play.google.com/store/apps/details?id=com.jmz.soft.twrpmanager&hl=en_GB
Install BusyBox first or it'll prompt you before doing anything
https://play.google.com/store/apps/details?id=stericson.busybox&hl=en_GB
The defaults it prompts you to change for locations can be left as they are
Click to expand...
Click to collapse
Yeah i am using twrp-2.8.7.0-klte.img. Will try Philz now can u guide me to the correct CWM i cant find it anywhere. thanks
dork997 said:
Yeah i am using twrp-2.8.7.0-klte.img. Will try Philz now can u guide me to the correct CWM i cant find it anywhere. thanks
Click to expand...
Click to collapse
Should be able to find everything you need here
http://forum.xda-developers.com/showthread.php?t=2697523
Instructions for ADB manual install, and also ODIN
Philz is a big favourite over CWM - Id try Philz first
Strange your same model S5 takes a fit with TWRP, it works fine on my G900F
Might be worth trying the App install method I posted
*Detection* said:
Should be able to find everything you need here
http://forum.xda-developers.com/showthread.php?t=2697523
Instructions for ADB manual install, and also ODIN
Philz is a big favourite over CWM - Id try Philz first
Strange your same model S5 takes a fit with TWRP, it works fine on my G900F
Might be worth trying the App install method I posted
Click to expand...
Click to collapse
Thanks for your Help, i guess this problem is too complicated. Anyway this time i installed Philz recovery > formatted everything > remove user content and data > custom formatted everything > flashed 5.0 BTU. and surprisingly its saving WiFi passwords without any build prop changes. So i am going to leave it here . 5.0 Unrooted with stock recovery everything working (FOR NOW) . This time i used Odin 3.10 instead of 3.07. I hope it does not get stuck at boot logo and start crashing. Only one problem it kept connecting to "update server" evem tho i had disabled the auto update option from settings>about >updates . i restarted immediately hopefully it wont try to update again. Thanks again for your help.
Hi Geeks,
Let me explain the Root cause for this problem, I tried to Root my device with CF Auto root and it works fine without any issues, later i found sometimes my mobile hangs and restarts (once in a week very Rare).
Later I installed twrp recovery and accidentally wiped /system /internal /dalvik /cache everything (My foolish)
in No OS situation i tried to install Marshmallow 6.0.1 stock ROM .
after Odin finishes up its work, the mobile restarts for first time and gone through installing updates.... later few minutes No command robot is appearing.
when we restart the mobile it looping in boot screen(restarting at Samsung logo continuously)
changed battery and tried (No luck)
changed different recovery mode(No luck)
tried several times in the past week and went to Samsung service center they did the same thing what i did and informed to change the board which nearly cost 18K
azarhsaf said:
Hi Geeks,
Let me explain the Root cause for this problem, I tried to Root my device with CF Auto root and it works fine without any issues, later i found sometimes my mobile hangs and restarts (once in a week very Rare).
Later I installed twrp recovery and accidentally wiped /system /internal /dalvik /cache everything (My foolish)
in No OS situation i tried to install Marshmallow 6.0.1 stock ROM .
after Odin finishes up its work, the mobile restarts for first time and gone through installing updates.... later few minutes No command robot is appearing.
when we restart the mobile it looping in boot screen(restarting at Samsung logo continuously)
changed battery and tried (No luck)
changed different recovery mode(No luck)
tried several times in the past week and went to Samsung service center they did the same thing what i did and informed to change the board which nearly cost 18K
Click to expand...
Click to collapse
You will have to flash the cf auto root file.
This will fix the bootloop issue.
If it still persists, then you will have to flash the full recovery firmware.
Let me know if you want the link.
Sent from my SM-N9200 using Tapatalk
yashthemw said:
You will have to flash the cf auto root file.
This will fix the bootloop issue.
If it still persists, then you will have to flash the full recovery firmware.
Let me know if you want the link.
Sent from my SM-N9200 using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply yashthemw
I had wiped all the partitions including system and internal memory... this wont delete cf auto root??
and can you please give me the steps to do that if possible??
azarhsaf said:
Thanks for the reply yashthemw
I had wiped all the partitions including system and internal memory... this wont delete cf auto root??
and can you please give me the steps to do that if possible??
Click to expand...
Click to collapse
First of all there is nothing wrong if you wipe everything and flash stock rom.
Now, if it is bootlooping, that means, the partitions aren't correct. Therefore if you flash cf auto root file, it will reset all partitions.
Just simply flash the cf auto root file via odin.
Reporting Via N910G
yashthemw said:
First of all there is nothing wrong if you wipe everything and flash stock rom.
Now, if it is bootlooping, that means, the partitions aren't correct. Therefore if you flash cf auto root file, it will reset all partitions.
Just simply flash the cf auto root file via odin.
Reporting Via N910G
Click to expand...
Click to collapse
Tried flash CF auto root file via Odin... still same reboot issue and flashed again using stock ROM... same issue persists
[that is after odin flashed-> reboots entering recovery mode -> installing updates -> erasing -> installing app updates then reboots here (this happens while flashing stock rom)]
azarhsaf said:
Tried flash CF auto root file via Odin... still same reboot issue and flashed again using stock ROM... same issue persists
[that is after odin flashed-> reboots entering recovery mode -> installing updates -> erasing -> installing app updates then reboots here (this happens while flashing stock rom)]
Click to expand...
Click to collapse
Just flash the cf auto root file, nothing else.
Reboot the device after flashing cf auto root file.
Reporting Via N910G
yashthemw said:
Just flash the cf auto root file, nothing else.
Reboot the device after flashing cf auto root file.
Reporting Via N910G
Click to expand...
Click to collapse
sorry, the same problem again any other solutions for this issue ?
Can you please let me know what is the filesystem should be used for /system /internal and other partition...
because i changed to f2fs before and reverted back all to ext4 now (all partitions which is shown in twrp advance wipe).
any advise?
azarhsaf said:
Can you please let me know what is the filesystem should be used for /system /internal and other partition...
because i changed to f2fs before and reverted back all to ext4 now (all partitions which is shown in twrp advance wipe).
any advise?
Click to expand...
Click to collapse
I had tried ext2 once.
Reporting Via N910G
Can anyone please help to fix this issue???
yashthemw said:
I had tried ext2 once.
Reporting Via N910G
Click to expand...
Click to collapse
No luck yet
have you tried this:
https://www.androidfilehost.com/?fid=24411628330025773
Reporting Via N910G
You can try this:
Flash your latest official rom via PC Odin with option Nand Erase All.
Upon booting, if not going to start-up log-in screen, remove and put back battery. Then go to stock Recovery and Wipe cache and Wipe data/factory reset.
Be patient and wait several minutes as the first boot usually takes a long time.
This should fix your problem.
This is unfair... Changed my battery.. Now it is working perfectly... How the hell firmware update damaging battery..??
Any how i got redmi note 3 last week and now going to sell note 4
Thanks to all who helped here...