I have a Galaxy i9100 from a uncle wich stoped to work, he said it sudenly stop and it doesn't want to come alive again
the reality, it was stuck on the samsung logo page, so i come with Vol+Power+Key to the recovery mode to make a wipe cache partition first (what did not solve the problem) and a data/factory wipe afterwards,
It worked, but only for a while, after I set up wifi and google acount and start download the samsung update, the mobile restart after few seconds and got stuck again the logo screen.
Wiped three times, always the same, after couple minutes of usage, it restart and got stuck
Also, it fails to load the "desktop", both the icons and the application menus
all I guess, is that the internal memory got corrupted or fails in some way,
how could I make a "memtest" or what else I can do to check if the mobile could be repaired?
the recovery mode says "Android system recovery <3e>" and it allows to apply updates from ADB, from external storage and from cache. Could I apply some update to make it work?
as I got told after an "interrogation", my uncle was using one of this "cleaner" and was removing own samsung apps becouse "I never using them" and suddenly got dead
that shouldn't be a problem if the internal memory is ok after making a factory reset, isn't it ?
If he used some root cleaner then not. Just try to download the firmware and update it with odin or check my link with xwms1 flashable zip in my signature. Then you only need to do if you are on stock to flash philz kernel temporary or the other one and reboot.
My build is included with stock kernel so no changes made. If you want full stock flash odexed. Cause all the normal official versions were odexes I believe
Goodluck with your uncles phone.
Sent from my GT-I9100 using Tapatalk
What Android version was installed on the phone? Do not say it was on 4.0.4, because then there is a big chance you bricked it by applying the factory reset ...
Sent from my Nexus 7 using xda app-developers app
AndDiSa said:
What Android version was installed on the phone? Do not say it was on 4.0.4, because then there is a big chance you bricked it by applying the factory reset ...
Click to expand...
Click to collapse
Not sure, I suppose the last one, because when I tried to update with Kies, it say me it is up to date
wulsic said:
If he used some root cleaner then not. Just try to download the firmware and update it with odin or check my link with xwms1 flashable zip in my signature. Then you only need to do if you are on stock to flash philz kernel temporary or the other one and reboot.
My build is included with stock kernel so no changes made. If you want full stock flash odexed. Cause all the normal official versions were odexes I believe
Click to expand...
Click to collapse
before read your comment, I found this two tutorials :
http://mobilenetworkcomparison.org.uk/tutorial-how-to-restore-the-stock-samsung-galaxy-s2-rom/#stock
http://mobilenetworkcomparison.org.uk/tutorial-rooting-and-installing-cyanogenmod-with-odin/#odin
Well...
If I instal Cyanogenmod, it works flawlessly, so, I tought everything was in place.
Then I installed the stock rom, and it fails again as earlier, stuck on loading "SAMSUNG" logo
once more Cyanogenmod, and then working
once more stockRom, and then stuck
so, I give my uncle with cyanogenmod, and he say that "this new operative system is more difficult and ugly than the other one..."
problem is, sort of, solved, but how comes I can't make the stock Rom working while cyanogenmod work ok ?
Related
Hello everybody,
First I'd like to thank to community for the hard work. I v read a countless amount of pages of this forum and I can't even imagine the time people spent helping on issues or writing tutorials.
So thank you if you re up to spend few minutes on my specific case (and sorry for the bad english).
Here is my device and the different version of kernel ...
1/ Rooting my device (tutorial in french translated from xda)
http://www.cnetfrance.fr/produits/guide-rooter-son-galaxy-s2-39763841.htm
S-Root version used: http://forum.xda-developers.com/showthread.php?t=1125414
Everything went pretty well when I rooted the GS2. I got the Superuser app so i figure it's ok.
I just used a modified kernel found on xda who was corresponding the my base band version (just the PDA in Odin).
2/ Installing a new ROM (Cyanogenmod by Rom Manager)
I followed : http://www.redmondpie.com/install-cm7-on-galaxy-s2-using-rom-manager-how-to-tutorial/ and http://wiki.cyanogenmod.com/wiki/Samsung_Galaxy_S_II:_Full_Update_Guide (official guide) using Rom Manager premium.
When i tried to reboot in Recovery (manually or with Rom Manager), i can't find the "Install the zip" option, I have 4 available: "Update from the zip", the 2 wiping/delete options and the reboot.
So obviously if i try to wipe files, wipe the cache then to update with the zip I have the following Error:
E: failed to verify whole-file signature
Do you have any idea what went wrong in the process ?
Should i flash the phone withOdin and change my base band version to another one ?
For info, I did the Permission Fix option in Rom Manager too. Didnt help.
Thanks a lot.
U need clockworkmod instaled first..
Sent from my GT-S5570 using xda premium
sgt_ray said:
Do you have any idea what went wrong in the process ?
Click to expand...
Click to collapse
You didn't install ClockworkMod Recovery.
Thanks for theses answers but I think I installed it with Rom Manager and i flashed it to the last version.
(joined file 1 : cwm rom manager.jpg)
When i reboot in recovery mode here is the only options available (and it's the problem i pointed out) :
(joined file 2 : 20111125_13221022.jpg)
Maybe a problem with my SD card ?
sgt_ray said:
but I think I installed it with Rom Manager and i flashed it to the last version.
Click to expand...
Click to collapse
As we've already said, you haven't installed CWM Recovery. You see at the top of your second photo where it says "Android system recovery (3e)"? That's stock recovery.
you can't install CWM recovery thru ROM manager.
just flash the CF Root Kernel for KI4 thru ODIN , you will have CWM recovery.
Hmm I understand about the CWM version I'm booting with, but as you can see on the first capture, my kernel version is a modified one i got after using Odin (puting this Kernel : GT-I9100_XXKI4_insecure.tar from http://forum.xda-developers.com/showthread.php?t=1101671).
I got the root access by S2 Root.
Ok I think I installed only the Kernel and not CF Root available here : http://forum.xda-developers.com/showthread.php?t=1103399
I ll try to redo Odin and stuff and let you know if I'm still alive.
So it's not great right now. I have installed CF Root with Odin, so I had CWM on my phone (I could see the application). Then after reboot with CWM Recovery and installing Cyanogenmod, the phone doesnt want to start anymore.....
I tried to apply the insecure kernel again with Odin but still impossible to download. I'm stuck on the screen with the yellow sign and written Galaxy S2.
HALP !!
I just tried to put back the official firware version : http://forum.xda-developers.com/showthread.php?t=1075278 and put it in my phone with Odin.
Ok, I dont have the yellow sign anywore but the phone is still stuck on the boot screen (where it's written Samsung GALAXY s II)...
What should I try ?
I'm still able to boot with CWM recovery but I didn't make any backup and nothing work.
Do you think the phone is dead ?
5 posts in a row?
So, just to clarify, you've tried to install CM7, which amongst other things tells you to do a nandroid backup, and also to flash twice in succession. Did you do either of these things? The instructions are there to be followed, don't just ignore them.
Ok my bad I didn't backup anything because I had no data to backup. This was maybe a bad move...
Anyway, I tried to flash it twice yes. Right now, i'm working with a modified Kernel (with CF Root), and booting in CWM Recovery. When I want to flash again by installing from the .zip I get a Satus 7 Error.
In CWM, every advanced options are apparently available but I dont know anything about them.
And just so you know, on my SD Card i have 1 update.zip and the update-cm-7.1.0-Galaxys2.... .zip from Cyanogen.
sgt_ray said:
Ok my bad I didn't backup anything because I had no data to backup. This was maybe a bad move...
Anyway, I tried to flash it twice yes. Right now, i'm working with a modified Kernel (with CF Root), and booting in CWM Recovery. When I want to flash again by installing from the .zip I get a Satus 7 Error.
In CWM, every advanced options are apparently available but I dont know anything about them.
And just so you know, on my SD Card i have 1 update.zip and the update-cm-7.1.0-Galaxys2.... .zip from Cyanogen.
Click to expand...
Click to collapse
Flash a stock rom with Odin and then root your phone again. Start reading and follow procedures when you want to flash custom roms again .See Intratechs`s thread for a stock rom
Thanks for your reply.
I did it, it didn't work, I mean i could flash with Odin but the reboot doesn't work : the start screen appeared without the yellow sign, but it's stuck on it.
--- update
FYI, I installed Rom Manager yesterday, it way interact in a bad way with CWM Recovery.
For now i can mount USB by CWM Recovery but cannot do anything else.
If you have a method to clean completely the phone ? Maybe the bootloader is broken...
sgt_ray said:
I just tried to put back the official firware version : http://forum.xda-developers.com/showthread.php?t=1075278 and put it in my phone with Odin.
Ok, I dont have the yellow sign anywore but the phone is still stuck on the boot screen (where it's written Samsung GALAXY s II)...
What should I try ?
I'm still able to boot with CWM recovery but I didn't make any backup and nothing work.
Click to expand...
Click to collapse
Wipe data and cache after flashing..
Sent from my GT-S5570 using xda premium
I did it. 20 times .
Maybe I should re partition my SD card...
--- update ---
I re partitionned my SD Card with Odin and tried to install a new stock ROM. Everything pass with Odin but to finalize the set up (while reboot), I got some errors and still the same problem during the boot. It's stuck !
I installed a insecure Kernel so I can access CWM Recovery but still stuck and now I can't mount anything .
Sorry to post again...
Finally I ordered a USB jig in case of...
I found this solution : http://forum.xda-developers.com/showpost.php?p=16902269&postcount=8
May try it this we.
sgt_ray said:
Sorry to post again...
Finally I ordered a USB jig in case of...
I found this solution : http://forum.xda-developers.com/showpost.php?p=16902269&postcount=8
May try it this we.
Click to expand...
Click to collapse
Good luck...
Sent from my GT-S5570 using xda premium
Hi,
This is my first post so i apologise if its in the wrong place. I have been running ICS 4.0.3 for quite some time and decided it was time to try a different ROM. I installed AOKP 4.1.1, gapps_jb_signed with Siyah kernel S2.4.1.5 ( i think). After a few days it kept hanging etc and switching off as i would expect a build in development to do. Anyway i flashed a new kernal to change the look (dark demonoid or something like that) and then rebooted. My phone was now properly bricked like i'd never seen before and would'nt even go into recovery mode. After a day or two of trying everything I could to get it to at least boot i flashed Siyah kernel knowing that it had a dual boot option. Low and behold it worked but only in the 2nd ROM mode where i was able to restore my old ICS 4.0.3 from Nandroid backup. The problem I have now is that when i try to do a factory restore/data wipe from within CWM it gets stuck at the data wipe point and eventually shuts down.
I have tried mounting and unmounting emmc,eft,system, data etc and wiping clean everything but to no avail.
When i try to restore the nandroid backup onto the 1st ROM partition it hangs when installing data and I have also tried reformating the data from within the dual boot options of siyah kernel. Nothing seems to work. Have i fried the chip or something? or am i just missing a procedure. My phone works but only if i keep it on siyah kernel and boot into the 2nd ROM option where i have ICS installed..
Any help would be appreciated.
Hi,<br />
This is my first post so i apologise if its in the wrong place. I have been running ICS 4.0.3 for quite some time and decided it was time to try a different ROM. I installed AOKP 4.1.1, gapps_jb_signed with Siyah kernel S2.4.1.5 ( i think). After a few days it kept hanging etc and switching off as i would expect a build in development to do. Anyway i flashed a new kernal to change the look (dark demonoid or something like that) and then rebooted. My phone was now properly bricked like i'd never seen before and would'nt even go into recovery mode. After a day or two of trying everything I could to get it to at least boot i flashed Siyah kernel knowing that it had a dual boot option. Low and behold it worked but only in the 2nd ROM mode where i was able to restore my old ICS 4.0.3 from Nandroid backup. The problem I have now is that when i try to do a factory restore/data wipe from within CWM it gets stuck at the data wipe point and eventually shuts down.<br />
<br />
I have tried mounting and unmounting emmc,eft,system, data etc and wiping clean everything but to no avail.<br />
<br />
When i try to restore the nandroid backup onto the 1st ROM partition it hangs when installing data and I have also tried reformating the data from within the dual boot options of siyah kernel. Nothing seems to work. Have i fried the chip or something? or am i just missing a procedure. My phone works but only if i keep it on siyah kernel and boot into the 2nd ROM option where i have ICS installed..<br />
<br />
Any help would be appreciated.
Click to expand...
Click to collapse
hi mate.can you please mention which roms you were using in dual boot?well yo be honest dual boot ain't a good idea.if you would ha e asked me.i would have recommented you not to do dual boot itch.anyways,coming to the issue.how did you try to flash rom while you got brick?which kernel you had?
Sent from my GT-I9100 using xda app-developers app
You were trying to change the look by flashing a kernel? I'm sorry, but that doesn't make sense. Also you really need to know which ROMs and kernel version you're on. There are ROMs compatible with siyah 4.1.5 and ROMs which are not.
Mention all (correct) details of your roms used and the kernel you're on. Maybe there's a solution there and someone will be able to point out if you've been doing something wrong. Dual boot is perfectly safe. I've been using siyah+ dual boot ever since the day I first rooted my phone and never had a problem.
Sent from my GT-I9100 using xda app-developers app
SGS2 Bricked on ROM 1 after downgrading from JB 4.1.1
Hi,
Sorry if i'm using the wrong terminology. If you hadn't guessed im pretty new to rooting etc and thought that changing the kernel also changed the theme/appearance. Anyway im currently running the following:See attachment.This only boots up on the 2nd ROM option. I cannot boot anything on the default 1st ROM and cannot even do a factory data wipe reset of the 1st ROM as CWM just hangs.
I Am Phooka said:
Hi,
Sorry if i'm using the wrong terminology. If you hadn't guessed im pretty new to rooting etc and thought that changing the kernel also changed the theme/appearance. Anyway im currently running the following:See attachment.This only boots up on the 2nd ROM option. I cannot boot anything on the default 1st ROM and cannot even do a factory data wipe reset of the 1st ROM as CWM just hangs.
Click to expand...
Click to collapse
My advice to you would be this:
1. Boot into recovery.
2. FORMAT cache, system, data and internal storage.
3. Boot into Download mode.
4. Flash an "all in one" OFFICIAL 4.0.3 firmware package using Odin. Place this in the PDA section and do not touch anything else.
5. Once it's finished flashing your device should restart and you should be good to go. With a clean, stock firmware.
Let me know if you have trouble
SGS" Bricked on ROM 1 after downgrade from JB 4.1.1.
Obagleyfreer said:
My advice to you would be this:
1. Boot into recovery.
2. FORMAT cache, system, data and internal storage.
3. Boot into Download mode.
4. Flash an "all in one" OFFICIAL 4.0.3 firmware package using Odin. Place this in the PDA section and do not touch anything else.
5. Once it's finished flashing your device should restart and you should be good to go. With a clean, stock firmware.
Let me know if you have trouble
Click to expand...
Click to collapse
Hi, Thanks for your help. I tried the above but when formating data it just hung and then eventually rebooted. I flashed the stock ROM anyway and now it just hangs at the Galaxy SII start screen, i even tried flashing it twice but that didn't help. I have also tried doing a factory data wipe from within the stock recovery after the flash but this still hangs and never completes. Is there a way of formating the data on the phone from within windows using a terminal emulator or something like that?. I have ROM Toolbox Pro on the device which has a terminal emulator as well if thats any good. For now i'll have to restore my nandroid backup I made this morning. mick
I Am Phooka said:
Hi, Thanks for your help. I tried the above but when formating data it just hung and then eventually rebooted. I flashed the stock ROM anyway and now it just hangs at the Galaxy SII start screen, i even tried flashing it twice but that didn't help. I have also tried doing a factory data wipe from within the stock recovery after the flash but this still hangs and never completes. Is there a way of formating the data on the phone from within windows using a terminal emulator or something like that?. I have ROM Toolbox Pro on the device which has a terminal emulator as well if thats any good. For now i'll have to restore my nandroid backup I made this morning. mick
Click to expand...
Click to collapse
he is saying go to stock rom by odin.i will give you a link where u can learn how to do it.i am from mobile right now.
Sent from my GT-I9100 using xda app-developers app
Tried stock rom. still wont boot
adilliano said:
he is saying go to stock rom by odin.i will give you a link where u can learn how to do it.i am from mobile right now.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Hi, Sorry for the delay in answering i have been away for a couple of days. I flashed a stock rom with odin and it flashed OK and I got a green pass but when my android reboots it gets stuck half way through the install and then crashes and then never gets past the galaxy logo boot screen. I think the kernel must install OK though as after flashing the stock ROM i lost my dual boot option and the phone was bricked again. The only way i can get it working again is to enter stock recovery and install CWM zip, then install superroot & busy box and then flash siyah. This then gives me the dual boot option in CWM recovery where I can restore from nandroid and reboot into the 2nd rom. The problem only happens when i am trying to install a rom in ROM 1 slot (default) on siyah. Whatever ROM it is it never gets past the data part of the install.
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?
Hey,
I have since become a S3 ... I have rooted it and wanted to play another Rome.
First I flashed my Carbon ... that was wonderful, but I had no wifi. Then I tried another Rom (with aroma installer). When I had WiFi, but since I have the menu did not like it and it was me too many Samsung Apps.
Now I have flashed me the Resurrection Remix, but the S3 boots constantly new to the CWM.
The same I have with CM11.
What am I doing wrong please?
lolamarcel said:
Hey,
I have since become a S3 ... I have rooted it and wanted to play another Rome.
First I flashed my Carbon ... that was wonderful, but I had no wifi. Then I tried another Rom (with aroma installer). When I had WiFi, but since I have the menu did not like it and it was me too many Samsung Apps.
Now I have flashed me the Resurrection Remix, but the S3 boots constantly new to the CWM.
The same I have with CM11.
What am I doing wrong please?
Click to expand...
Click to collapse
You need to install exactly like below don't miss any steps
-Installation-
1.- Wipe data / factory reset (mandatory if you coming from STOCK OR 4.2.X version or another ROM)
2.- Install the Main ROM
3- install gapps
4.- When you're back on recovery go to Advanced
5.- Wipe Dalvik Cache
6.- Fix Permissions
7.- Wipe Cache Partition
8.- Reboot
If it still not working flash TWRP recovery and use that to flash the rom
Hey,
I just did it. Then came the Samsung logo, phone restarts and I'm back in the CWM.
Have just flashed TWRP reboot (via CWM) Recovery and but still have CWM.
Grrrrrr ...... what for now
Better download official firmware from Sammobile and install thru Odin. Then Root and carry on with your favorite custom rom.
Yes I agree with KSKHH if problem still there return to stock with odin and start again..
tallman43 said:
Yes I agree with KSKHH if problem still there return to stock with odin and start again..
Click to expand...
Click to collapse
How are you doing? Your phone is working now?
Hey,
so suck an official firmware and flash it with Odin ... then the CWM away again?
If I then use the rooten begin I play me but come back on automatically, or not?
lolamarcel said:
Hey,
so suck an official firmware and flash it with Odin ... then the CWM away again?
If I then use the rooten begin I play me but come back on automatically, or not?
Click to expand...
Click to collapse
Steps:
Install ORIGIANAL firmware via ODIN
Don't need to root
INSTALL CUSTOM RECOVERY
Copy desired ROM into memory card (or intrernal, if dont have memory card)
Wipe all
Install
Profit
Hey,
I have now taken me this firmware:
I9300XXUGML2_I9300DTMGML2_I9300BOUGMK3_HOME.tar
Odin started, specified in the PDA tar file, made my S3 in the download mode, USB cable ran ... it was detected and was also flashed. Now I sit for at least 10 minutes and nothing happens.
The Samsung logo always changes its color and the LED on the top left light blue.
lolamarcel said:
Hey,
I have now taken me this firmware:
I9300XXUGML2_I9300DTMGML2_I9300BOUGMK3_HOME.tar
Odin started, specified in the PDA tar file, made my S3 in the download mode, USB cable ran ... it was detected and was also flashed. Now I sit for at least 10 minutes and nothing happens.
The Samsung logo always changes its color and the LED on the top left light blue.
Click to expand...
Click to collapse
Boot into recovery then factory reset..
hey,
exactly these thoughts I had just as well.
Meanwhile, I have written this text did something on the screen ... the phone goes again.
Thanks to all
So now just flash a recovery and then flash as usual custom of Rome?
Edit:
GT-I9300
Android 4.3
Baseband I9300BOUGMK3
Kernel: 3.0.31-2303192 [email protected]#1 FriDec 13 21:55:31 KST2013
Build: JSS15J.I9300XXUGML2
Edit2:
Hey,
so, now I have successfully flashed TWRP and tested.
Now I'll try to flash CM11 ... hopefully it starts this time also
Edit 3:
so, now it has worked wonderfully.
Thanks again for the help
I had an costume ROM installed, but at one point, while trying to change the recovery it bricked, and I just received errors like "Messenger has stopped" for every sing app (even system) and the screen all blacked, then I reinstalled the costume ROM again, but it got worse, cause I could only see a black screen, and had to remove the battery. So I decided to go back to the original recovery and installed the original, official ROM, and when I installed it appeared "Unfortunately System UI has stopped" every second, so I wiped the data in the original recovery mode and it worked, but now it appears the message: "Unauthorized actions have been detected" and it asks to restart my phone, that message is appeared all the time too. How do I get rid of it?
And the boot when i turn the device on is still the one from the ROM Note 7 style (white), how do I change that to?
If you still have TWRP installed you can try this method to change boot logo.
For the other problem try to use your last working backup, if it won't work - wipe everything and then flash original image throught Odin.
93drago said:
If you still have TWRP installed you can try this method to change boot logo.
For the other problem try to use your last working backup, if it won't work - wipe everything and then flash original image throught Odin.
Click to expand...
Click to collapse
I guess, I will need to install TWRP again, and do that to change the boot logo;
I never had a backup, so should I wipe everything again (In TWRP?) And then install the original ROM throught Odin again?
To be sure wipe everything including internal storage - recovery and download mode will remain, everything else will be lost so make a backup of important files. Download latest firmware from Sammobile and flash it through Odin (search for SamFirm on xda to download faster). That should do the work.
93drago said:
To be sure wipe everything including internal storage - recovery and download mode will remain, everything else will be lost so make a backup of important files. Download latest firmware from Sammobile and flash it through Odin (search for SamFirm on xda to download faster). That should do the work.
Click to expand...
Click to collapse
Ok, im going to test that when I get home, thanks
Jrmb said:
Ok, im going to test that when I get home, thanks
Click to expand...
Click to collapse
The same problem I've had phone then you should re-install the original here bootlogolar download and flash TWRP http://forum.xda-developers.com/gal...-logo-samsung-galaxy-alpha-boot-logo-t3311888 .
Everything worked, thanks guys