Hey guys, I recently rooted my SGS3, and that worked. Only thing: I want to have the nexus version (http://forum.xda-developers.com/showthread.php?t=2076672) installed on my phone. I got into recovery mode, but when I try to install the two files, it says It doesnt have the signature needed.
It is a phone from EU, as I live in Amsterdam, Holland.
Someone please help?
Thnx!!
thejeffdroid said:
Hey guys, I recently rooted my SGS3, and that worked. Only thing: I want to have the nexus version (http://forum.xda-developers.com/showthread.php?t=2076672) installed on my phone. I got into recovery mode, but when I try to install the two files, it says It doesnt have the signature needed.
It is a phone from EU, as I live in Amsterdam, Holland.
Someone please help?
Thnx!!
Click to expand...
Click to collapse
Sounds like you're still on a stock recovery
If signature verification fails, you need to be on a custom recovery. Then you can turn signature verification off in settings. If you're not on Custom recovery, well you cant flash anything unofficial
rootSU said:
If signature verification fails, you need to be on a custom recovery. Then you can turn signature verification off in settings. If you're not on Custom recovery, well you cant flash anything unofficial
Click to expand...
Click to collapse
So, does this mean I have to root it again? What do I do?
I really want to have the nexus version installed.
And I rooted it without a laptop, though... My laptop hates me, cause it accepts every usb device, except for my phone. So I rooted it without my laptop..
Is there any change of still succeeding?
thejeffdroid said:
So, does this mean I have to root it again? What do I do?
I really want to have the nexus version installed.
And I rooted it without a laptop, though... My laptop hates me, cause it accepts every usb device, except for my phone. So I rooted it without my laptop..
Is there any change of still succeeding?
Click to expand...
Click to collapse
When you manually boot into recovery (From off, Vol down + Home + Power), what version does it say? How did you root?
So, I didnt find any Version info, But I rooted my phone with an app I found on the market, I think it was called RootBox or something.
Later I performed a factory reset, because my phone was getting anything but faster.
Anyway, thanks in advance for your support. I hope we can figure this out
thejeffdroid said:
So, I didnt find any Version info, But I rooted my phone with an app I found on the market, I think it was called RootBox or something.
Later I performed a factory reset, because my phone was getting anything but faster.
Anyway, thanks in advance for your support. I hope we can figure this out
Click to expand...
Click to collapse
When you boot into recovery, what does it say? maybe a photo will help?
But if you didnt use an S3 root method, you probably still have stock recovery. You'll need to download a recovery and flash via Odin. Follow the root guides in general to do this
Well, I havent been able to make a picture of the screens I see, but her are the things I sea, described:
*Starts with the Galaxy S3 logo screen*
*Change into Android Maintenance screen (The blue figure in its stomache)*
Then there are those blue rules:
Android System Recovery <3e>
Volume up/down to move highlight;
power button to select
Reboot system now
Apply update from AOB
Apply update from external storage
Wipe data/factory reset
Wipe cache partition
Apply update from cache.
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC-code : PHN
Successfully applied multi-CSC.
I know this is too muvh information, but I figured, if I tell you exactly what I see, then maybe you can tell me more.
Oh, by the way, I have rooted my phone with an app called SuperSU. It also asks for superusers permission.
And if I open up the rule Apply update from external storage, I can see the installation for Nexus, but then the next info pops up:
-- Install /sdcard/Download ...
Finding update package...
Opening update package...
Verifying update package...
E;signature verification failed
thejeffdroid said:
Well, I havent been able to make a picture of the screens I see, but her are the things I sea, described:
*Starts with the Galaxy S3 logo screen*
*Change into Android Maintenance screen (The blue figure in its stomache)*
Then there are those blue rules:
Android System Recovery <3e>
Volume up/down to move highlight;
power button to select
Reboot system now
Apply update from AOB
Apply update from external storage
Wipe data/factory reset
Wipe cache partition
Apply update from cache.
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC-code : PHN
Successfully applied multi-CSC.
I know this is too muvh information, but I figured, if I tell you exactly what I see, then maybe you can tell me more.
Oh, by the way, I have rooted my phone with an app called SuperSU. It also asks for superusers permission.
And if I open up the rule Apply update from external storage, I can see the installation for Nexus, but then the next info pops up:
-- Install /sdcard/Download ...
Finding update package...
Opening update package...
Verifying update package...
E;signature verification failed
Click to expand...
Click to collapse
You need to flash a custom recovery.. My favourite is Philz:
http://forum.xda-developers.com/showthread.php?t=2002953
Sent from my GT-I9300 using xda app-developers app
Before I donwload this... Can I do this without a usb connection? My laptop doesnt see my phone at all when I plug it in.
My laptop is kinda stupid, so is there a way?
krs360 said:
You need to flash a custom recovery.. My favourite is Philz:
http://forum.xda-developers.com/showthread.php?t=2002953
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Clicked the wrong reply button, sorry for dubble posting...
Before I donwload this... Can I do this without a usb connection? My laptop doesnt see my phone at all when I plug it in.My laptop is kinda stupid, so is there a way?
Mobile Odin
Sent from my GT-I9300 using Tapatalk 2
Related
And now I cant access my phone. When I turn it on i got black screen only with clock and battery info. I can grag the drawer down to turn on/of wifi, gps... and enter management when i long hold home button.
I need to find a way to install launcher. Bluuetoth wont work because it is not paired after factory reset. Wlan is useless. I cant install anything from SD either.
I cant use odin to flash firmware because i will loose warranty. And I cant take it to service center because I didnt unroot it.
The only way I see that can help is instal launcher throug recovery mode using update.zip file. But when i try to install it it says :
--Install from sdcard...
Finding update package...
Opening update package...
Installing update package...
Installation aborted...
I put golauncher.apk in update.zip file and signed it using autosign.
Can anyone help?
It may be I am doing something wrong while creating update.zip. Can someone do it for me and upload it with any launcher within it?
Thanks alot in advance!!!
Do you have the CWM 4.0.0.9 recovery installed or can you flash the CWM 4.0.0.9 recovery?
If you can then boot into CWM - mount the USB - copy over a modded rom like Fla.sh2X or FirstUA to the SD.
Then flash that rom.
If you have the 3e recovery - then I suggest flashing a rom with Odin.
or install via adb. google for an tutorial
@Baracs I do not have any recovery, I didn't figure out how to make one...
@downloadonlyaccount Thanks, I'll do a research.
speedy051 said:
@Baracs I do not have any recovery, I didn't figure out how to make one...
@downloadonlyaccount Thanks, I'll do a research.
Click to expand...
Click to collapse
to make it extra simple download Qtadb if you are not familiar with command shell.
speedy051 said:
And now I cant access my phone. When I turn it on i got black screen only with clock and battery info. I can grag the drawer down to turn on/of wifi, gps... and enter management when i long hold home button.
I need to find a way to install launcher. Bluuetoth wont work because it is not paired after factory reset. Wlan is useless. I cant install anything from SD either.
I cant use odin to flash firmware because i will loose warranty. And I cant take it to service center because I didnt unroot it.
The only way I see that can help is instal launcher throug recovery mode using update.zip file. But when i try to install it it says :
--Install from sdcard...
Finding update package...
Opening update package...
Installing update package...
Installation aborted...
I put golauncher.apk in update.zip file and signed it using autosign.
Can anyone help?
It may be I am doing something wrong while creating update.zip. Can someone do it for me and upload it with any launcher within it?
Thanks alot in advance!!!
Click to expand...
Click to collapse
Hold down the home key and hope you have file manager in recently used.
Sent from my GT-S5830 using xda premium
Okay, I'll try to help:
1. Get ClockworkMod 4.0.0.9 (the official one), and flash it through stock recovery. (Sorry, using my phone, can't link to the thread)
2. Install the update.zip file through CWM. Some update.zip files can only be flashed through CMW.
I really hope that helps.
Oh, and IMHO, you shouldn't have to worry about burning the warranty. It should still be valid if you can flash a stock firmware (from your appropriate region, of course).
I once took my phone to a Samsung Service Center just to check if thr warranty is already void -- with a recently flashed stock firmware from Asia -- and it isn't.
Sent from my GT-S5830 using XDA App
E:Short write of /tmp/sideload/package.zip (No space left on device)
The phone is rooted as I've searched on google and what little I could find says to have it rooted. Not exactly sure what to try. I've wiped and reset everything and still a no go. Doesn't matter which ROM is selected either. Thank you.
TommyStarwind said:
E:Short write of /tmp/sideload/package.zip (No space left on device)
The phone is rooted as I've searched on google and what little I could find says to have it rooted. Not exactly sure what to try. I've wiped and reset everything and still a no go. Doesn't matter which ROM is selected either. Thank you.
Click to expand...
Click to collapse
My best advice is to unroot and do a complete factory reset and try to root again
Go to rootgalaxynote.com and click the upper right tab to unroot
Sent from my SAMSUNG-SGH-I717 using xda premium
Jt004 said:
My best advice is to unroot and do a complete factory reset and try to root again
Go to rootgalaxynote.com and click the upper right tab to unroot
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
Just rooted it and checked it with super user downloaded ROM manager set it to Recovery mode from there and still the same error.
You should still try to unroot even if you just rooted. It fixes many problems
Sent from my SAMSUNG-SGH-I717 using xda premium
Do you have Clockwork recovery installed on your phone? How are you trying to install these custom ROMs? Are you using ROM Manager?
You don't need root to flash a Rom...
Get Odin
Get an Odin flashable version of cwm
Flash said recovery with Odin
Boot into recovery by holding all the buttons till you feel a vibrant and letting off the power button, or the adb command: adb reboot recovery (or since you have root, download a terminal emulator from the market enter the command: reboot recovery, then Grant superuser permission.)
Then Flash Rom in cwm...
Old version of TWRP maybe?
To run the ROM Manager I needed root access. I tried to load the ROM from the ROM Manager and also straight from manual recovery mode.
flappjaxxx said:
Old version of TWRP maybe?
Click to expand...
Click to collapse
Trying to install yours and i get
E:signature verification failed
That is stock recovery 3e...
Go read my post above...
THIS IS A LINK TO CWM TOUCH...JUST CLICK ANYWHERE HERE AND GET THE ODIN FLASHABLE VERSION
You do not need root to flash a Rom... Rom manager is not needed, and in fact just causes more problems than is worth
I don't think ROMmanager is even capable of flashing anything on the note. Someone correct me if I am wrong
You're correct...i wish that app would just go away and be erased from people's memories.
Actually i don't think Rom manager has worked on any Samsung device since eclair...as froyo was when they introduced 3e recovery, which requires signed update.zips, which only Samsung has the signature tool for.
So the update.zip Rom manager downloads to flash cwm with just gets stuck at "E: signature verification failed"
I'm still getting errors I'm going to search on youtube some more and see what could possibly be an issue. I go in with Up+home+power and erase everything I can in there and try to load from .zip and errors.
So I got it to work. I didn't really do anything differently except put it on my external SD card instead of my internal.
hello everyone i decided to create this thread for anyone who accidentally bricked their galaxy player 5.0 USA model or just wants to set their device to the original GB ROM & KERNEL.
all of these files i have found and i did not create anything but this tutorial for you guys!
ENJOY!!!!
you will need odin only
you will maintain root access
link to .zip download
http://www.4shared.com/zip/ynV2Lm_p/FullRestoreSGP50USA.html?
README File
*****************************************************
Ok this is how to fully restore your Samsung Galaxy Player 5.0 USA to factory defaults even if you are on jellybean or an other rom
this also works if you have soft-bricked your device.
1. open odin
2. select PIT and choose the G70-GalaxyPlayer5.0-8gig.pit
3. click start
4. let your device reboot and reboot it into download mode
5. open a fresh odin again without the pit selected
6. go to PDA and select package_us2.3.5.tar.md5
7. click start
--dont freak out if your device reboots and stays at the SAMSUNG logo just boot into download mode
8. open a fresh odin again
9. go to PDA and select ueki8_min.tar.md5
10. click start
NOTE-- when the device reboots you need to hold volume up and the power button to go to standard android recovery
11. in android recovery click factory reset and erase cache
12. reboot your galaxy player and it should look exacty as you bought it (plus superuser b/c you are still rooted)
13. if you want to all you need to go back to flashing roms is to put clockworkmod recovery on your device
14. your done
wnerena the
Thanks! This helped because most posts and tutorials don't point out that you have to do the pit / kernel / rom steps one at a time (and bootloaders). I was trying to slam dunk the pit, bootloaders and kernel in one update and it wasn't working.
Question: Where did you get the tar.MD5 file from???
Request Link
Hown can I get the download link?
Thanks a lot!
i would like a link also as im having the dreaded chagring issues and need it replaced
IDK
I don't remember. Sorry. The day I bricked my Galaxy Player was all a blur. All of these files i found online, in threads, etc. IDK where i got them from but all that matters is that they work!!!
Kenobz said:
Question: Where did you get the tar.MD5 file from???
Click to expand...
Click to collapse
DOWNLOAD!!!!
For all of you that have been asking i finally have been able to post it in this thread!!!!
LINK IS BELOW!!!!
OR UP TOP IN THE 1st POST!!
http://www.4shared.com/zip/ynV2Lm_p/FullRestoreSGP50USA.html?
wrojas said:
Hown can I get the download link?
Thanks a lot!
Click to expand...
Click to collapse
Not Working
I tried this, but my device randomly shuts off in the middle of the third step. I'm using Odin 3.09 and I have the correct model, Player 5.0 USA (YP-G70) PLEASE HELP:crying:
Thanks, a lot!
coltoverson said:
I tried this, but my device randomly shuts off in the middle of the third step. I'm using Odin 3.09 and I have the correct model, Player 5.0 USA (YP-G70) PLEASE HELP:crying:
Click to expand...
Click to collapse
is your device fully charged? try to flash the recovery file then turn off your device while plugged into a charger and let it charge. i had a similar problem. make sure you have the latest odin for the best possibility of fixing your device. then start from step 1 and try again. it took me several tries before it finally worked.
i kinda have bricked mine 4 different times and have used this to get out of all of them. meaning it should work!!!:laugh:
bassbrick15 said:
is your device fully charged? try to flash the recovery file then turn off your device while plugged into a charger and let it charge. i had a similar problem. make sure you have the latest odin for the best possibility of fixing your device. then start from step 1 and try again. it took me several tries before it finally worked.
i kinda have bricked mine 4 different times and have used this to get out of all of them. meaning it should work!!!:laugh:
Click to expand...
Click to collapse
And if you don't want to create a 4shared account... http://forum.xda-developers.com/showthread.php?p=39188127
Mevordel said:
And if you don't want to create a 4shared account... http://forum.xda-developers.com/showthread.php?p=39188127
Click to expand...
Click to collapse
Yep, thanks for the help! I just needed to stop and charge my device in between flashing the ROM and second ROM, and it worked!
Please advise
Thanks for this post, guys. My device is finally doing more than just displaying (phone)-!-(computer). I successfully flashed the .pit, kernel and rom, but now I get a screen that displays
u for format and reboot actions (in red)
Media files copy failed. (in yellow)
# Manual Mode#
--Appling Multi-CSC...
Successfully applied multi-CSC.(in yellow)
E:Failed to mount /cache (No such file or directory) (in red)
E:Can't mount /cache/recovery/recovery_kernel_log (in red)
E:copy_kernel_file :: Can't open /cache/recovery/recovery_kernel_log (in red)
And then the last 3 lines repeat twice.
The device will not shut down, either. It goes into a boot loop. Any advice will be much appreciated.
Thanks
edit: I got it! The home button works as enter. The OS is 2.3.5 instead if 2.3.7 but that's okay for now. I'm sure I'll try flashing a ROM soon. Any good ones?
haldav said:
Thanks for this post, guys. My device is finally doing more than just displaying (phone)-!-(computer). I successfully flashed the .pit, kernel and rom, but now I get a screen that displays
u for format and reboot actions (in red)
Media files copy failed. (in yellow)
# Manual Mode#
--Appling Multi-CSC...
Successfully applied multi-CSC.(in yellow)
E:Failed to mount /cache (No such file or directory) (in red)
E:Can't mount /cache/recovery/recovery_kernel_log (in red)
E:copy_kernel_file :: Can't open /cache/recovery/recovery_kernel_log (in red)
And then the last 3 lines repeat twice.
The device will not shut down, either. It goes into a boot loop. Any advice will be much appreciated.
Thanks
edit: I got it! The home button works as enter. The OS is 2.3.5 instead if 2.3.7 but that's okay for now. I'm sure I'll try flashing a ROM soon. Any good ones?
Click to expand...
Click to collapse
i'd keep with a GB rom if you want the camera and hotspot to work i'm using Cosmos 0.3. if you want JB get the cyanogenmod 10.2 with the sultan kernel thats what i switched from.
Intermittent Wifi
This Stock ROM saved my device but the wifi is intermittent. I do need the camera, as well. GB is fine but I was hoping for 2.3.6 or later. Really, I don't care as long as camera and wifi works. Also, can I change from SuperUser to SuperSU or will that mess things up?
haldav said:
This Stock ROM saved my device but the wifi is intermittent. I do need the camera, as well. GB is fine but I was hoping for 2.3.6 or later. Really, I don't care as long as camera and wifi works. Also, can I change from SuperUser to SuperSU or will that mess things up?
Click to expand...
Click to collapse
i would recommend using SuperSU its just my personal preference.
Thanks. How do I go about replacing Superuser? I flashed a ROM from Eryigit and Superuser is now a system app.
Sent from my YP-G70 using xda app-developers app
haldav said:
Thanks. How do I go about replacing Superuser? I flashed a ROM from Eryigit and Superuser is now a system app.
Sent from my YP-G70 using xda app-developers app
Click to expand...
Click to collapse
Install SuperSu from the Zip and it will do it for you.
There is no such file in the zip.
Sent from my YP-G70 using xda app-developers app
haldav said:
There is no such file in the zip.
Sent from my YP-G70 using xda app-developers app
Click to expand...
Click to collapse
Not the ROM zip, the SuperSU zip
http://download.chainfire.eu/supersu
Hi,
I have a rooted galaxy S2 on stock with the SuperSU application. I updated the SuperSU application today and when I opened it, it advised me to update the binary. I selected the option to update the binary via CWM (as that's my recovery tool). My phone then tried to reboot but is now stuck on the splash screen, I have access to ODIN mode which currently says CUSTOM BINARY DOWNLOAD: Yes (1 counts) but no access to CWM.
Please could anyone help? I have a feeling I would need to flash the kernel but am not really sure what the best way to fix this is. If possible I would like to keep all my data intact.
Any help is appreciated
Also apologies if I have posted this to the wrong section.
Thanks
peshmann said:
Hi,
I have a rooted galaxy S2 on stock with the SuperSU application. I updated the SuperSU application today and when I opened it, it advised me to update the binary. I selected the option to update the binary via CWM (as that's my recovery tool). My phone then tried to reboot but is now stuck on the splash screen, I have access to ODIN mode which currently says CUSTOM BINARY DOWNLOAD: Yes (1 counts) but no access to CWM.
Please could anyone help? I have a feeling I would need to flash the kernel but am not really sure what the best way to fix this is. If possible I would like to keep all my data intact.
Any help is appreciated
Also apologies if I have posted this to the wrong section.
Thanks
Click to expand...
Click to collapse
Sorry to persist, but has anyone got any suggestions on how to fix this? I'm on Jeboo kernel v1.2, stock JB firmware.
Thanks
Same problem for me, I updated the last version of SU and try to update binary choossing cmw/trwp. Now I have a bootlopp. onece it started few seconds after the phone reboot again and again.
peshmann said:
Sorry to persist, but has anyone got any suggestions on how to fix this? I'm on Jeboo kernel v1.2, stock JB firmware.
Thanks
Click to expand...
Click to collapse
Same problem for me. In download mode I flashed a stock jb rom, siyah kernel, then I restored the backup from cwm.
Sent from my GT-I9100 using xda app-developers app
chrisXL said:
Same problem for me. In download mode I flashed a stock jb rom, siyah kernel, then I restored the backup from cwm.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
After a few hours of struggling, I managed to get my phone back up and running.
All I did was flash the kernel with a Stock one eg. Philz (as I have stock JB firmware). Once flashed my phone booted up.
However I do have a issue with the SD card now, apps which were installed on my SD card were all greyed out even though I can access the data such as music and films off the card. Slightly strange. I did try mounting and unmounting, as well as reboot and that didn't help.
Considering downloading the apps again and simply moving to SD card and see if that works rather than an uninstall and reinstall.
SuperSU 1.86 binary update
Hi, i using HTC ONE with ARHD31.6 stock kernel. Also i have encountered bootloop issue after i did a update for superSU from v1.8 to v1.86. Tried both options and it stills resulted to bootloop. So far havent been able to find a solution for this so other then restored back to my previous backup.
Hi,
I have a rooted galaxy S2 on stock with the SuperSU application. I updated the SuperSU application today and when I opened it, it advised me to update the binary. I selected the option to update the binary via CWM (as that's my recovery tool). My phone then tried to reboot but is now stuck on the splash screen, I have access to ODIN mode which currently says CUSTOM BINARY DOWNLOAD: Yes (1 counts) but no access to CWM.
Please could anyone help? I have a feeling I would need to flash the kernel but am not really sure what the best way to fix this is. If possible I would like to keep all my data intact.
Any help is appreciated
Also apologies if I have posted this to the wrong section.
Thanks
Click to expand...
Click to collapse
I had the same problem (bootloop issue) on my Samsung win I8552 and I solved that reinstalling CWM trought ODIN :
1. First be sure USB Debugging is checked in ur device ( Settings>Developer Options>USB Debugging )
2. Extract the Odin file from the zip.
3. Open Odin3 (Run As Administrator).
4. Put your device in download mode. To do so, press Volume Down And Home And Power Button all together and when it vibrates release
Power Button but keep pressing left ones. You should have a triangle with an android janitor while it's saying downloading ..
VOL UP TO CONTINUE...
5. Now connect USB to PC ,you should see a blue rectangle with COM:xx and saying Added. It means that your device is ready to be flashed!
6. Go into the PDA section and select your .tar file.(CWM Recovery)
7. Dont check any option (F.reset time and Auto reboot are checked by default) So just uncheck Auto Reboot.
8. Now click Start.
9. When it's finished, it should say that "Res OK" in Odin..
10. Now remove ur USB and remove ur battery and put it back and power on your phone.
It must work now!
:highfive:
SuperSU Binary Update Boot problem
I have a rooted galaxy S2 using jeboo kernel and SuperSU application. I updated the SuperSU application today and when I opened it, it advised me to update the binary. I selected the option to update the binary via CWM. My phone then tried to reboot but is now stuck on the splash screen, I have access to ODIN mode which currently says CUSTOM BINARY DOWNLOAD: Yes (1 counts) but no access to CWM.
Please could anyone help
Try to reinstall a kernel via odin then reboot.
Sent from my GT-I9100 using XDA Free mobile app
I know this is an old topic, but the recent supersu update caused my phone to get stuck during booting:
The new update came over the playstore, it asked me to update the app. After that it said that the Super User Binary needs to be updated. I chose the option that does the update process in the CWM recovery.
Then this happend:
System shuts down, boots, I see that some kind of black screen gets displayed(softkeys on and the display stays blank), then it reboots and stops the boot on the Galaxy S2 splash screen. Now that I didnt even get to the samsung splash screen I flashed the Apolo Kernel as an tar file through odin
after that I was able to get one step further and was able to get the Samsung splash Screen but the Splash screen keeps on repeating over and over but after that I also had my recovery back.
Now I tried to Install SuperSU 2.16 as zip in the recovery. but the endless samsung screen persited. After that I used the 2.15 Beta file. but this didnt work either.
I also fixed permissions wiped cache & dalvic cache
Why wouldnt my system boot after the first initial update and how can I finally fix the boot "loop"?
Thank you very much guys!
Heraku said:
I know this is an old topic, but the recent supersu update caused my phone to get stuck during booting:
The new update came over the playstore, it asked me to update the app. After that it said that the Super User Binary needs to be updated. I chose the option that does the update process in the CWM recovery.
Then this happend:
System shuts down, boots, I see that some kind of black screen gets displayed(softkeys on and the display stays blank), then it reboots and stops the boot on the Galaxy S2 splash screen. Now that I didnt even get to the samsung splash screen I flashed the Apolo Kernel as an tar file through odin
after that I was able to get one step further and was able to get the Samsung splash Screen but the Splash screen keeps on repeating over and over but after that I also had my recovery back.
Now I tried to Install SuperSU 2.16 as zip in the recovery. but the endless samsung screen persited. After that I used the 2.15 Beta file. but this didnt work either.
I also fixed permissions wiped cache & dalvic cache
Why wouldnt my system boot after the first initial update and how can I finally fix the boot "loop"?
Thank you very much guys!
Click to expand...
Click to collapse
Try to reinstall your rom without wipe data. Don't update supersu via cwm!
Sent from my GT-I9100 using XDA Free mobile app
chrisXL said:
Try to reinstall your rom without wipe data. Don't update supersu via cwm!
Sent from my GT-I9100 using XDA Free mobile app
Click to expand...
Click to collapse
I was able to pull a logcat:
Could someone look into it and perhaps tell me how to fix it?
Heraku said:
I was able to pull a logcat:
Could someone look into it and perhaps tell me how to fix it?
Click to expand...
Click to collapse
Sorry to repeat myself, reflash your rom (no wipe). You will not lose anything.
It's the easiest way.
Sent from my GT-I9100 using XDA Free mobile app
after using complete unroot s6 keep in boot loop how to fix it?
If you use TWRP like me and have a recent backup of your system just restore it and it'll fix the boot loop.
chrisXL said:
Sorry to repeat myself, reflash your rom (no wipe). You will not lose anything.
It's the easiest way.
Sent from my GT-I9100 using XDA Free mobile app
Click to expand...
Click to collapse
thank u very much, this saved me from freaking out. it absolutely worked.
supersu binary reboot problem
first of all, get into recovery mode and copy the rom and gapps files to your internal storage through pc via usb cable.
then wipe the data, and make a clean flash of rom and gapps and reboot system.
I know this method will surely lose our data. but I have not found a solution at that particular instant other than this.
It happened to me.
Hope someone will surely solve this problem.
Thank you chrisXL, came across this thread from a Google search regarding my OnePlus2 using LinageOS after the SuperSU binary update. I simply went to INSTALL in TWRP and didn't use any wipe options. Phone booted right up after that! Thanks!!
Hi Guys, please help me. I flashed my moto g peregrine with the latest lineage os version. After that, i enable the the root option via TWRP with the addonsu.
After that, i downloaded via google store the SuperSU app i it asks to update the binary. I choosed the option via "TWRP" since the other option didn't work. After that, my phone is on bootloop (the symbol of lineage os is moving) and i can't acess to recovery mode.
What i can do?
j_moreno91 said:
Hi Guys, please help me. I flashed my moto g peregrine with the latest lineage os version. After that, i enable the the root option via TWRP with the addonsu.
After that, i downloaded via google store the SuperSU app i it asks to update the binary. I choosed the option via "TWRP" since the other option didn't work. After that, my phone is on bootloop (the symbol of lineage os is moving) and i can't acess to recovery mode.
What i can do?
Click to expand...
Click to collapse
Same problem here I had my mokke Rom pre rooted but titanium used to ask for SuperSU so installed the app from Google play and tried to install it via cwm/twrp and now it's stuck on the mokkee boot logo and can't even access my recovery what did you do solve the problem?
I tried to root my Samsung Galaxy S5 using Odin and an autoroot file. After that failed, I researched how to restore my phone to its original OS. I have not been able to do that either. I either can only boot to the Odin Mode screen or am locked on the T-Mobile logo screen.
BTW, I am new to phone rooting so more detailed explanations would be appreciated.
Are you able to boot to recovery? [ home+volume up+power]
If so you can reset from there.
If not you should be able download the stock firmware and flash it with Odin.
FOL1 is the latest - it takes a long time to download from Sam's.
http://www.sammobile.com/firmwares/database/SM-G900T/
Jim
otisdog is right, sammobile takes forever to download which is why you should download the exact same file they linked to, but from here:
https://www.androidfilehost.com/?fid=24407100847293882
Since cf-autoroot didn't work for you, you should just install TWRP with Odin and use TWRP to flash supersu zip, that's more or less what cf auto-root is doing anyway. Boot your phone into Odin mode (home, vol down, and power), connect your phone to PC with USB, and install twrp-3.0.0-0-klte-klte.img.tar with Odin (AP button, auto-reboot option disabled). When the status bar is filled, you need to immediately boot into TWRP without rebooting system (this is where you hold down home, vol up, and power). In TWRP, install supersu zip file. Now wipe cache and dalvik
If you reboot to normal android before booting into TWRP and flashing the supersu zip when TWRP is first installed, the operating system will overwrite TWRP with the stock recovery, and you have to try again.
Thanks OtisDog and thisisapoorusernamechoice.
While I am downloading TMB-G900TUVS1FOL1-20160111153316, I tried your directions for installing TWRP and had success. I was able to boot into TWRP. (First boot success since I started 10 days ago.) I downloaded supersu zip and have it on my Windows 10 computer. I assume that I do not unzip it in Windows, correct?
From TWRP I clicked on Install and got the phone's files. When I clicked on Select Storage, the USB storage choice has 0MB so the option is disabled. Should I have started TWRP with my USB cable still connected? My computer still recognizes that I am connecting something to it while TWRP is running.
If that is not the problem, how do I install supersu zip into my phone?
Dave4237 said:
Thanks OtisDog and thisisapoorusernamechoice.
While I am downloading TMB-G900TUVS1FOL1-20160111153316, I tried your directions for installing TWRP and had success. I was able to boot into TWRP. (First boot success since I started 10 days ago.) I downloaded supersu zip and have it on my Windows 10 computer. I assume that I do not unzip it in Windows, correct?
From TWRP I clicked on Install and got the phone's files. When I clicked on Select Storage, the USB storage choice has 0MB so the option is disabled. Should I have started TWRP with my USB cable still connected? My computer still recognizes that I am connecting something to it while TWRP is running.
If that is not the problem, how do I install supersu zip into my phone?
Click to expand...
Click to collapse
The supersu zip needs to be in your phone's internal storage or micro SD card. USB storage is not used for this
thisisapoorusernamechoice said:
The supersu zip needs to be in your phone's internal storage or micro SD card. USB storage is not used for this
Click to expand...
Click to collapse
Since my phone has no SD card slot, this sounds like a Catch 22. I can't get my phone to work without installing the supersu zip, but I can't install the supersu zip without getting my phone to work.
Fortunately, the file that OtisDog suggested DID work. THANK YOU. THANK YOU. THANK YOU.
My wife is also thrilled that I don't have a $160 brick. She sends hugs to both of you.
Dave4237 said:
Since my phone has no SD card slot, this sounds like a Catch 22. I can't get my phone to work without installing the supersu zip, but I can't install the supersu zip without getting my phone to work.
Fortunately, the file that OtisDog suggested DID work. THANK YOU. THANK YOU. THANK YOU.
My wife is also thrilled that I don't have a $160 brick. She sends hugs to both of you.
Click to expand...
Click to collapse
You don't need the SD card, you can put the supersu zip file in your phone's internal memory and flash it from there in TWRP. Also if you have a Galaxy S5, you have an SD card slot. It's on top of, yes literally on top of the SIM card slot, can be a little confusing and hard to see until you know what you're looking for (see attached pic for clarification, sorry for my halfassed paint job lol).
thisisapoorusernamechoice said:
You don't need the SD card, you can put the supersu zip file in your phone's internal memory and flash it from there in TWRP. Also if you have a Galaxy S5, you have an SD card slot. It's on top of, yes literally on top of the SIM card slot, can be a little confusing and hard to see until you know what you're looking for (see attached pic for clarification, sorry for my halfassed paint job lol).
Click to expand...
Click to collapse
Thanks for the photo. That helps.
My latest problem is that every time I restart my phone, some shortcuts (Hi, Google; Gallery; magazines; exercise; camera) are added to my home screens and the default home screen is changed. I suspect that by clearing one of the caches, I can fix this. What do I need to do?
You can go into settings and find "backup and reset".
In there uncheck the backup and then do the factory reset. This will wipe all data and reload the os like when the phone was new - you can then put on it what you want.
MAKE SURE you have anything that's on the phone now, that you want, backed up on your computer because it will get wiped off the phone.
Once you get the phone to where you want it we can work on rooting it.
Jim
The instructions from thisis... worked great for me, although I accidentally did a full wipe from TWRP - no biggie, I was backed up. Thanks!
I appreciate the clear and concise instructions I've seen so far, I got as far as flashing superSU zip and wiping cache and dalvik, what next?
NexMortifer said:
I appreciate the clear and concise instructions I've seen so far, I got as far as flashing superSU zip and wiping cache and dalvik, what next?
Click to expand...
Click to collapse
Reboot lol
Sent from my SM-N920G using XDA Labs
ShinySide said:
Reboot lol
Click to expand...
Click to collapse
wouldn't it be nice if that just worked?
sorry, enough sarcasm, I'll clarify, I got that far with everything going as intended, but after reboot, it's not rooted (according to rootchecker) and I don't know why. Additional device info:
SM-G900T
running 4.4.2 (it doesn't want to let me update for some reason, and I thought maybe old versions might be easier to root)
Baseband Version G900TUVU1CNK2
Build # is KOT49H.G900TUVU1CNK2
(if there's other info you need, let me know.)
NexMortifer said:
wouldn't it be nice if that just worked?
sorry, enough sarcasm, I'll clarify, I got that far with everything going as intended, but after reboot, it's not rooted (according to rootchecker) and I don't know why. Additional device info:
SM-G900T
running 4.4.2 (it doesn't want to let me update for some reason, and I thought maybe old versions might be easier to root)
Baseband Version G900TUVU1CNK2
Build # is KOT49H.G900TUVU1CNK2
(if there's other info you need, let me know.)
Click to expand...
Click to collapse
Yeah that's weird. Since you're running kit Kat should of installed system root. Or maybe I'm wrong on the zip being able to root kitkat/use system root instead of systemless.
Open the supersu app and see if it asks to update su binary
Otherwise I'd just try flashing it again in twrp or finding a much older supersu zip to flash. (Probably a 1.×× version)
You don't need to wipe caches tho.
Sent from my SM-N920G using XDA Labs
ShinySide said:
Open the supersu app and see if it asks to update su binary
Click to expand...
Click to collapse
App isn't showing up either, don't know if that's useful info or not.
NexMortifer said:
App isn't showing up either, don't know if that's useful info or not.
Click to expand...
Click to collapse
You are flashing it in twrp correct?
Because you should have SuperSU installed then
Sent from my SM-N920G using XDA Labs
ShinySide said:
You are flashing it in twrp correct?
Because you should have SuperSU installed then
Sent from my SM-N920G using XDA Labs
Click to expand...
Click to collapse
Yes, I did, and no, it didn't.
Well, I eventually gave up on that root technique, and ended up using This instead, so now I'm running 6.0.1, and it seems to be working alright, but SuperSU says "The SU bianary needs to be updated!" and when I click it, it offers me the options of "normal" and "TWRP/CWM" as ways to install the SU bianary.
I know just enough to know that I don't know what I'm doing, and thought I'd get some advice before I proceed to screw something up.
Which option should I go for, and if TWRP, do I need to re-flash it with Odin like I did to install the 6.0.1 ROM, or is the process different now?
NexMortifer said:
Well, I eventually gave up on that root technique, and ended up using This instead, so now I'm running 6.0.1, and it seems to be working alright, but SuperSU says "The SU bianary needs to be updated!" and when I click it, it offers me the options of "normal" and "TWRP/CWM" as ways to install the SU bianary.
I know just enough to know that I don't know what I'm doing, and thought I'd get some advice before I proceed to screw something up.
Which option should I go for, and if TWRP, do I need to re-flash it with Odin like I did to install the 6.0.1 ROM, or is the process different now?
Click to expand...
Click to collapse
I always just click normal. Then it'll ask to reboot and just allow it and you'll be good to go
Sent from my SM-N920G using XDA Labs
https://forum.xda-developers.com/tm...l/root-how-to-root-sm-g900t-firmware-t3358190
use that guide, follow it precisely and you will be fine