Hello XDA
I was wondering if there possibility for me to, flash (or use an app) an kernel to my stock rom? I am rooted, but I have stock recovery.
Also to be 100% sure: There is a risk of flashing a kernel right?
TheStigx said:
Hello XDA
I was wondering if there possibility for me to, flash (or use an app) an kernel to my stock rom? I am rooted, but I have stock recovery.
Also to be 100% sure: There is a risk of flashing a kernel right?
Click to expand...
Click to collapse
You can flash kernel with CWM app or odin mobile and after you'll have custom recovery.
There is a small risk that you will softbrick the phone.
This means that you can encounter some startup problems or just plain broken phone.
But dont worry, soft bricks are almost harmless and all problems have an easy solution nowadays.
Gent.XDA said:
There is a small risk that you will softbrick the phone.
This means that you can encounter some startup problems or just plain broken phone.
But dont worry, soft bricks are almost harmless and all problems have an easy solution nowadays.
Click to expand...
Click to collapse
Yeah, I thought that too. But I have read those threads about how to recovery it from soft brick, and I think it isn't a problem.
078gregory said:
You can flash kernel with CWM app or odin mobile and after you'll have custom recovery.
Click to expand...
Click to collapse
Oh, What CWM app? You mean rom manager? That can only help me with roms
TheStigx said:
Yeah, I thought that too. But I have read those threads about how to recovery it from soft brick, and I think it isn't a problem.
Oh, What CWM app? You mean rom manager? That can only help me with roms
Click to expand...
Click to collapse
Do not use rom manager .
Root + CWM .
http://forum.xda-developers.com/showthread.php?t=1103399
from the guide in stickies .
Clockworkmod is a 'custom recovery' made by xda member koush. Every phone had a recovery partition designed so that if the user messes up a ROM installation, they can recover their phone. CWM is a modified recovery installed into the recovery partition that allows advanced control over ROM recovery, installation and much more.
Features of CWM include:
- NANDroid Backup, This allows you to completely back up your existing ROM with all its files, data and apps
- Restore Backup, Restores a previous backup (obviously...)
- ROM installation, Allows you to install a ROM contained inside a flashable .zip file
- Wipe data/Factory reset, completely erases all of your data contacts, apps etc, leaving your phone 'as new'
Amongst others...
How to install CWM
If you have already rooted your phone using the CF-root Kernel, then you already have CWM! If not, then just install the kernel linked to above in the 'how to root your phone' section
How to make a NANDroid backup using CWMBackups are important because they allow you to restore your ROM incase flashing goes wrong, or you phone starts playing up and displaying wierd bugs.
To make a backup, you need to boot into CWM recovery (done through the 'cwm' app installed onto your phone when you flash the cf-root kernel). Then, you need to navigate down to 'backup/restore' using the volume keys, and select it using the home key. From here, just click 'backup' and you are all set! Leave your phone make the backup (its takes some time) and then just reboot when it tells you its finished. To restore your backup, do the same but instead of clicking backup, click 'restore' instead. Choose which backup you would like to restore and leave the phone to do its magic. Done.
How to install a ROM using CWMInstalling a ROM using CWM is a lot less hassle then installing via Odin. The ROM developer will specify which method of installing their ROM you can use, but it is usually done by a CWM flashable .zip.
To flash:
1. Boot into CWM as described above
2. Navigate to 'install zip from sd card'
3. Select it, and then navigate to 'install zip from sdcard' again!
4. Select the ROM you downloaded from your sd card
5. Navigate down to yes
6. Let CWM install you new ROM!
jje
TheStigx said:
Oh, What CWM app? You mean rom manager? That can only help me with roms
Click to expand...
Click to collapse
Go to Chainfires thread in Original android development section and download the cf root file that match to your current rom.
Flash it with odin, You will have custom CWM
That would be a good idea!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
JJEgan said:
Do not use rom manager .
Root + CWM .
http://forum.xda-developers.com/showthread.php?t=1103399
from the guide in stickies .
Clockworkmod is a 'custom recovery' made by xda member koush. Every phone had a recovery partition designed so that if the user messes up a ROM installation, they can recover their phone. CWM is a modified recovery installed into the recovery partition that allows advanced control over ROM recovery, installation and much more.
Features of CWM include:
- NANDroid Backup, This allows you to completely back up your existing ROM with all its files, data and apps
- Restore Backup, Restores a previous backup (obviously...)
- ROM installation, Allows you to install a ROM contained inside a flashable .zip file
- Wipe data/Factory reset, completely erases all of your data contacts, apps etc, leaving your phone 'as new'
Amongst others...
How to install CWM
If you have already rooted your phone using the CF-root Kernel, then you already have CWM! If not, then just install the kernel linked to above in the 'how to root your phone' section
How to make a NANDroid backup using CWMBackups are important because they allow you to restore your ROM incase flashing goes wrong, or you phone starts playing up and displaying wierd bugs.
To make a backup, you need to boot into CWM recovery (done through the 'cwm' app installed onto your phone when you flash the cf-root kernel). Then, you need to navigate down to 'backup/restore' using the volume keys, and select it using the home key. From here, just click 'backup' and you are all set! Leave your phone make the backup (its takes some time) and then just reboot when it tells you its finished. To restore your backup, do the same but instead of clicking backup, click 'restore' instead. Choose which backup you would like to restore and leave the phone to do its magic. Done.
How to install a ROM using CWMInstalling a ROM using CWM is a lot less hassle then installing via Odin. The ROM developer will specify which method of installing their ROM you can use, but it is usually done by a CWM flashable .zip.
To flash:
1. Boot into CWM as described above
2. Navigate to 'install zip from sd card'
3. Select it, and then navigate to 'install zip from sdcard' again!
4. Select the ROM you downloaded from your sd card
5. Navigate down to yes
6. Let CWM install you new ROM!
jje
Click to expand...
Click to collapse
kachrukamble said:
Go to Chainfires thread in Original android development section and download the cf root file that match to your current rom.
Flash it with odin, You will have custom CWM
Click to expand...
Click to collapse
But I wish to keep my stock recovery. Can't I use this recovery : http://forum.xda-developers.com/showthread.php?t=1501719
?
Related
Okay okay.. hello. I'm a new girl at XDA and thus new to all this rooting stuff.
First and foremost, I'm on Android 2.3.6. I used the XWLA4 insecure kernel to flash my SGS2 (since my official Samsung kernel is indeed XWLA4) and used S2Root to install BusyBox and superuser, but I had no CWM recovery so I manually installed CWM 4.0.0.2 via Odin.
It worked like a charm Now came the time to flash a custom firmware. I was thinking of MIUI, CM7 (because I didn't like stock ICS that much) and this new Fatal1ty Extreme ROM. In fact, I liked said ROM so much that I wanted to have it on my phone + the Red theme. And that's where the annoyance began..
I've carefully read all the instructions, but I didn't understand one:
"Copy the ROM to the Root dir of your SD card."
I thought it was just some directory in my USB storage, so I connected my device to my computer and connected the USB storage, yet I didn't find any folder named "Root" or anything that resembled a root directory.
After 1 hour of googling and extensive research, I was so annoyed that I just dragged the ROM + Theme to my USB storage.
I boot into CWM recovery, did a wipe (data/factory reset, dalvik cache wipe etc.) and then installed the ROM. When I rebooted, THIS happened:
I was stuck at the first screen, the one that said "Samsung Galaxy SII" on it with the yellow triangle!
And this screen did not go away until I boot my phone into download mode and flashed the official XWLA4 kernel from Samsung, aka unroot my phone.
After Unroot, my phone worked like normal. No bootloops, no being stuck on the first screen etc.
Can someone please shed light on this? Touchwiz isn't exactly my cup of tea anymore and I really would like to give my phone a custom look ._.
Thanks in advance
EDIT: It seems that this problem seems big, as every ROM that I flash (with wipes) takes <5 seconds to finish, and that usually means that it's a bad flash ._.
Can someone tell me how to solve this?
I've carefully read all the instructions, but I didn't understand one:
"Copy the ROM to the Root dir of your SD card
Root = copy the rom to the sd card not inside any folder .
DO NOT put anything in usb storage it is not the instructions for anything SD CARD only internal not the external one .
Connect phone to pc in usb mass storage mode copy the rom to the phones internal sd card only .
follow with CWM and root phone via Odin
Root + CWM .
http://forum.xda-developers.com/showthread.php?t=1103399
Then boot to recovery and install the rom .
That is an excellent choice of rom by the way .
jje
JJEgan said:
I've carefully read all the instructions, but I didn't understand one:
"Copy the ROM to the Root dir of your SD card
Root = copy the rom to the sd card not inside any folder .
DO NOT put anything in usb storage it is not the instructions for anything SD CARD only internal not the external one .
Connect phone to pc in usb mass storage mode copy the rom to the phones internal sd card only .
follow with CWM and root phone via Odin
Root + CWM .
http://forum.xda-developers.com/showthread.php?t=1103399
Then boot to recovery and install the rom .
That is an excellent choice of rom by the way .
jje
Click to expand...
Click to collapse
Well, I didn't put it in any folder and certainly not in the folder that says "usbStorage" on it. Please excuse me for my aloofness in this matter as I still don't quite understand how to access my internal SD card.
I have USB-debugging enabled and when I connect to my storage, I have something like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So, which one of these is the internal SD card? ._.
How i just reinstalled fatality rom .
Pick CWM and Root LA4
Flash via Odin
Download rom
Phone setting activate USB mass storage and copy the rom to the phone .
Boot to recovery mode vol up + home + Pwr release at first splash screen
Install/choose zip from sd card select fatality confirm yes
Installs reboot wait for rom to initialize then set it up .
jje
JJEgan said:
How i just reinstalled fatality rom .
Pick CWM and Root LA4
Flash via Odin
Download rom
Phone setting activate USB mass storage and copy the rom to the phone .
Boot to recovery mode vol up + home + Pwr release at first splash screen
Install/choose zip from sd card select fatality confirm yes
Installs reboot wait for rom to initialize then set it up .
jje
Click to expand...
Click to collapse
Doesn't work Tried that, but still doesn't go past the first screen..
EDIT: Maybe I should just flash it and then wait for it to boot.. I read similar situations where people flashed ROMs and they too were stuck on a boot screen, but in reality it really took so long due to the caches being rebuilt ._.
I'll try that. If anyone has suggestions, post in here
Azure Flame Kite said:
Doesn't work Tried that, but still doesn't go past the first screen..
EDIT: Maybe I should just flash it and then wait for it to boot.. I read similar situations where people flashed ROMs and they too were stuck on a boot screen, but in reality it really took so long due to the caches being rebuilt ._.
I'll try that. If anyone has suggestions, post in here
Click to expand...
Click to collapse
could you tell me where are you now? on which firmware? roooted/ or stock...
and which rom are you willing to flash?
zaheedahmed said:
could you tell me where are you now? on which firmware? roooted/ or stock...
and which rom are you willing to flash?
Click to expand...
Click to collapse
Unrooted again.
I want to flash Fatal1ty Extreme with the Fatal1ty Red Theme package ._.
I'm on the stock XXKI4 firmware with the XWLA4 kernel ._.
When I root my phone with CF-Root-SGS2_XW_OXA_LA4-v5.0-CWM5 kernel from Chainfire, the root is fine but when I flash Fatal1ty via CWM, it says "installation complete" but I can't get past the first screen ._.
When I root my device with the XWLA4 insecure kernel and then root it with S2Root, still nothing.
I even tried flashing Redpill 1.3 (auto-root) and then flash Fatal1ty, still nothing..
I'm always stuck at the first screen ._.
Full wipe. Aka wipe data and cache from recovery then install ROM.
Envoyé depuis mon GT-I9100 avec Tapatalk
Paradoxxx said:
Full wipe. Aka wipe data and cache from recovery then install ROM.
Envoyé depuis mon GT-I9100 avec Tapatalk
Click to expand...
Click to collapse
According to her first post, she already did that.
I boot into CWM recovery, did a wipe (data/factory reset, dalvik cache wipe etc.) and then installed the ROM. When I rebooted, THIS happened:
Click to expand...
Click to collapse
Fatality_Extreme(2). Rename that file. Delete the (2). Same for the theme zip.
5kops said:
Fatality_Extreme(2). Rename that file. Delete the (2). Same for the theme zip.
Click to expand...
Click to collapse
Will do, but what exactly would renaming it accomplish? ._.
Looking at the pic you posted you've downloaded the rom and theme twice (?). It will prevent a sucessful flash. Experience.
5kops said:
Looking at the pic you posted you've downloaded the rom and theme twice (?). It will prevent a sucessful flash. Experience.
Click to expand...
Click to collapse
Yeah, I downloaded them twice ._. But they are only once in my phone's storage.
Agree numbered zip makes no difference if it ends as .zipYou can even rename the zip.
jje
Sent from my GT-I9100 using xda premium
The flash after full wipe is always successfull, but it doesn't boot. Even if I wait 10-15 minutes -_-
Does it work with any other rom?
5kops said:
Does it work with any other rom?
Click to expand...
Click to collapse
I'll try another ROM to see if this boot problem is specific to Fatal1ty or if something's wrong with my phone ._.
Azure Flame Kite said:
Well, I didn't put it in any folder and certainly not in the folder that says "usbStorage" on it. Please excuse me for my aloofness in this matter as I still don't quite understand how to access my internal SD card.
I have USB-debugging enabled and when I connect to my storage, I have something like this:
So, which one of these is the internal SD card? ._.
Click to expand...
Click to collapse
JJEgan said:
Agree numbered zip makes no difference if it ends as .zipYou can even rename the zip.
jje
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Well every time I tried flasing a file like that ( e.g : update-cm-9-20120331-CODEWORKX-galaxys2-signed(2).zip) it will not work.
I tried two different ROMs: The Thebyani ICS one and the VK ICS one.. both have the same problem as Fatal1ty: They're stuck on the boot screen.
EDIT: It seems that this problem seems big, as every ROM that I flash (with wipes) takes <5 seconds to finish, and that usually means that it's a bad flash ._.
Can someone tell me how to solve this?
Okay, here's a sum-up of the problem thus far:
1. Root is fine with any kernel, device functions without any problems.
2. When I want to flash a custom ROM via CWM, it takes <5 seconds to finish and is stuck at the boot logo.
3. Unrooting solves this.
Something must be faulty with the device... Flashing kernels and back to stock is without any complications, yet when I wanna flash a custom ROM, it's stuck at the boot logo ._.
I was running the new Jellybean ROM just fine but decided to revert back to the AOKP ICS ROM. I did a backup of my JB rom in CWM and then did a restore of the backup from the AOKP ROM. But I forget to do a factory wipe. The ROM booted up fine the first time and then after a reboot it was just endlessly running the boot animation.
I could only boot into download mode so I tried to use PC Odin to flash a ROM I had but the program gets stuck at factoryfs.img. Please can anyone offer assitance?!
If you're to that point, flash back to stock first before you do anything else using creepyncrawlys guide in the dev section.
BROKKANIC said:
If you're to that point, flash back to stock first before you do anything else using creepyncrawlys guide in the dev section.
Click to expand...
Click to collapse
Sadly... I have tried this and it still gets stuck.
Using the downloads here: http://forum.xda-developers.com/showpost.php?p=18859438&postcount=199
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Have you tried this:?
http://forum.xda-developers.com/showthread.php?t=1286432
benjamingdelacruz said:
Have you tried this:?
http://forum.xda-developers.com/showthread.php?t=1286432
Click to expand...
Click to collapse
I have. This is what I did first. It gets to about 30% and gets stuck.
AngelsNecropolis said:
I was running the new Jellybean ROM just fine but decided to revert back to the AOKP ICS ROM. I did a backup of my JB rom in CWM and then did a restore of the backup from the AOKP ROM. But I forget to do a factory wipe. The ROM booted up fine the first time and then after a reboot it was just endlessly running the boot animation.
I could only boot into download mode so I tried to use PC Odin to flash a ROM I had but the program gets stuck at factoryfs.img. Please can anyone offer assitance?!
Click to expand...
Click to collapse
You don't have to do a wipe when restoring a nandroid backup on our phones, since it overwrites the entire data partition anyway. I'm wondering if ClockworkMod versions could be at the root of this. You didn't say which JB you were using, and I am not up on AOKP, but did the JB rom have CWM 6.0.1.1? and AOKP have the 5.x version? I think these are supposed to be backward compatible, but I'm wondering if restoring a 5.x backup with the 6.0.1.1 version could be at fault here. Just clutching at straws for a reason.
As far as recovering, go to the Download Repository, and first try flashing the complete firmware package with bootloaders. If that doesn't work, then try flashing the critical parts individually, i.e. secondary bootloader and param.lfs. If that doesn't work, there is a pit file there also, so you can flash the stock package with repartition. I assume you understand the risks.
I was using the SuperNexus JB rom. They did have different cwm versions but not sure which they were. Luckily I found an md5 file that would load 100% using pc Odin. Any tar file I tried to use first wouldn't load. Then I was successfully able to use the gingerbread stock with root tar listed in the unbrick section and then install a kernel with cwm to do the restore again. So I'm back to the AOKP. Only took 5 hours to fix this time. Ugh.
Sent from my SGH-I777 using Tapatalk 2
AngelsNecropolis said:
I was using the SuperNexus JB rom. They did have different cwm versions but not sure which they were. Luckily I found an md5 file that would load 100% using pc Odin. Any tar file I tried to use first wouldn't Loa. Then I was successfully able to use the gingerbread stock with root tar listed in the unbrick section and then install a kernel with cwm to do the restore again. So I'm back to the AOKP. Only took 5 hours to fix this time. Ugh.
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
Mind posting that file? It might come in handy.
The file is 618mb. I'll try to find the site where I downloaded it from.
Sent from my Galaxy S II running AOKP Jellybean
AngelsNecropolis said:
The file is 618mb. I'll try to find the site where I downloaded it from.
Sent from my Galaxy S II running AOKP Jellybean
Click to expand...
Click to collapse
I found the file on this site: http://www.droidreader.com/2012/05/how-to-un-brick-or-fix-soft-bricked.html
It's the Recovery Package for ICS that I used: http://hotfile.com/dl/146748985/809318f/I9100XXLPH.zip.html
The zip contains an md5 file which PC Odin was successfully able to load entirely. I suppose the md5 fixed something that was screwed up which prevented the tar files from completely loading.
Then I was able to successfully flash the kernel + rooted UCKH7 system package found here. Next I flashed a gingerbread Siyah kernal found here in order to gain access to CWM and restore my previous backup.
AngelsNecropolis said:
I found the file on this site: http://www.droidreader.com/2012/05/how-to-un-brick-or-fix-soft-bricked.html
It's the Recovery Package for ICS that I used: http://hotfile.com/dl/146748985/809318f/I9100XXLPH.zip.html
The zip contains an md5 file which PC Odin was successfully able to load entirely.
Click to expand...
Click to collapse
thats all i9100 stuff. Please dont confuse the masses posting that crap here.
MotoMudder77 said:
thats all i9100 stuff. Please dont confuse the masses posting that crap here.
Click to expand...
Click to collapse
Well that crap helped unsoft brick my phone. I only had to use the md5 file in order to get the correct TAR files to work.
AngelsNecropolis said:
I found the file on this site: http://www.droidreader.com/2012/05/how-to-un-brick-or-fix-soft-bricked.html
It's the Recovery Package for ICS that I used: http://hotfile.com/dl/146748985/809318f/I9100XXLPH.zip.html
The zip contains an md5 file which PC Odin was successfully able to load entirely. I suppose the md5 fixed something that was screwed up which prevented the tar files from completely loading.
Click to expand...
Click to collapse
Which .tar.md5 file did you use? And which proceedures in the tutorial did you follow?
Then I was able to successfully flash the kernel + rooted UCKH7 system package found here. Next I flashed a gingerbread Siyah kernal found here in order to gain access to CWM and restore my previous backup.
Click to expand...
Click to collapse
I'm surprised you were able to enter download mode to complete this step, since the I9100 package you used previously contained bootloaders. The secondary bootloader for the I9100 would change the button configuration for entering download mode and recovery mode.
creepyncrawly said:
Which .tar.md5 file did you use? And which proceedures in the tutorial did you follow?
I'm surprised you were able to enter download mode to complete this step, since the I9100 package you used previously contained bootloaders. The secondary bootloader for the I9100 would change the button configuration for entering download mode and recovery mode.
Click to expand...
Click to collapse
I tried using files:
I777UCKH7 OCD With Root.exe
UCKH7_stock_root.tar
uckk6_stock_rooted.tar
ATTGalaxyS2Unroot_SGH-i777.tar
I9100_CODE_I9100XXLPH_CL118559_REV02_user_low_ship.tar.md5
None of the tar files would complete. The md5 was located in the zip that I downloaded from the previously mentioned site. The file did load a ROM whose hard button configuration didn't match my phone model. Only the menu and home buttons worked and home was actually back. But I didn't have to do anything in the ROM. Download mode was still VOL Down + Power button.
After loading the md5 file I was able to use the exe but when the ROM loaded I wasn't able to get past the setup wizard. I would click on the android in the middle and either it wouldn't respond or different processes kept force closing. I remember one was a google framework process and there were like 2 others that popped up.
Everytime one of the other files failed I had to redo the md5 because the tars would get stuck again. So after several attempts I finally was able to use the UCKH7_stock_root.tar file to move forward with restoring my soft bricked phone.
Maybe someone can list the md5 file of the UCKH7_stock_root.tar incase PC Odin gets stuck like this for someone else? Though I'm no expert so I can't be sure if the tar vs md5 was what fixed the issue. I just know that file helped even if it wasn't the right one for my phone and, to my knowledge, caused no other issues once I used the correct tar files. I'm happily running the new AOKP JB ROM with no issues thus far.
Hello guys I’m here with a noob guide for who are very new to Rooting and how to install a new ROM on SGS2,
But this guide after rooting process will be same to flash the Custom ROM on other devices as well.
Rooting of GB devices
I'm not responsible for any harm to your device in this process, you are doing it on your own risk. By doing this you're voiding warranty of your product.
2.3.3/2.3.6 User should have to take a look on Chainfire's CFRoot method. However 2.3.3 can be rooted through recovery but 2.3.6 can't be without CFRoot method.
Needed tool for rooting GB
PC
Samsung USB drivers
Odin3
CFRooted stock kernel
Instructions-
Follow these instructions to the letter. Do not touch any buttons or checkboxes that are not listed below to touch!
Unzip the attached CF-Root-xxx-vX.X.zip
(USB) Disconnect your phone from your computer
Start ODIN
Click the PDA button, and select CF-Root-xxx-vX.X.tar
Put your phone in download mode
(USB) Connect the phone to your computer
Make sure repartition is NOT checked
Click the START button
Wait for the phone to reboot
Done
Now you have rooted phone with custom recovery. Thanks to @Chainfire for his awesome work.
Rooting of ICS
So for rooting the SGS2 we have a lots of guides but there is the much safe way to root it flashing the script via Stock recovery. So Philz has overcome to this problem with his awesome Kernel and with this thread named [ICS/JB]Universal Rooting for most phones, Any ROM, now with CWM6.
Instructions-
Copy the Root_XXX.zip file you downloaded to externalsd card
Boot into stock recovery (volume up+home+power), and select "apply update from external storage". Now select the Root_XXX.zip file downloaded above and you are rooted
To unroot, do the above steps and replace the file Root_XXX.zip by the attached Unroot_SuperUser-Busybox-Uninstaller-Update2-signed.zip. It will delete superuser, su and busybox packages.
Download links-
Root_SuperSU.0.98-Busybox.1.20.2-signed.zip
Unroot_SuperUser-Busybox-Uninstaller-Update2-signed.zip
Thanks to @Phil3759 for his awesome thread. Now you need custom kernels which should have the custom recovery, for that you can use DorimanX or Siyah kernel which are brickbug free.
Or you can just download the PhilzKernelCWM.zip with your matched code or at least similar kernel code and put it on your external SD card and then reboot into recovery by Holding the three combo key (Volumeup + Home + Power) and then choose option “Install Update zip” and choose the PhilzCWM.zip and flash it. After flashing done, you have rooted your Phone successfully with SuperSU installed. Now reboot to the recovery again and backup your ROM.
For JB release rootingJust flash the philz kernel from the stock recovery and you are rooted.
Now time to Backup your current ROM before flashing the new Custom ROM on your device, it is recommended in case when something happen bad. If you are running 4.0.3 or 4.0.4 then the backup process is very simple just reboot into recovery and then touch the Backup option and that’s all, your all apps, contacts, sms and data will be backed up by default, and this backup will be placed on external sd card in Clockworkmod/Backup path by default.
But if you are running JB 4.1.2 then the backup job is not easy on all recovery’s. There is an extra folder called Preload is very important one where your all system apps have been placed, which is not included in simple backup process. So the drill starts here…..Reboot into recovery select option “Backup and Restore”
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now select the option “Advance Backup and Restore”
Now select the “Custom Backup Job”. There you have tick the “Preload” folder and then scroll down and “Start custom Backup job” And then it will ask where you want to store the backup on you “Intenal/External Stroage”. After selecting the storage path it will start the backup process. When it finished you are ready to install the new ROM.
Note: If you don’t want to do this manually then I recommend the Apolo kernel which can backup the Preload by default no need of custom backup
NOTE: Before doing the below steps, backup your all apps and data using “Helium” or “Go backup” from play store to restore them on your newly flashed ROM. As after wipe data/reset you will lost all your contacts, Sms’s, and app and their data.
Now select the option “Wipe Data/ Factory reset” and then choose the second option “Clean to Install a New ROM”.
Note: I’ve seen this option in Philz only which is for Samsung only, non Samsung users have to select the first option and then follow these steps:
Wipe cache
Advanced/Wipe Dalvik cache
Now Select the option “Install Zip” and choose your zip from either Internal SD card or External SD Card wherever you have put the downloaded ROM zip file and flash it. Let’s finish the process and now reboot your system, it will take about 5-10 Min on first boot so don’t panic.
My credit and thanks
A big thanks to my NeatROM family.
Good work buddy. :thumbup:
Sent from my iPad using Tapatalk HD
Jeetu said:
Good work buddy. :thumbup:
Sent from my iPad using Tapatalk HD
Click to expand...
Click to collapse
Thanks buddy. I really want to make it good. Just shout for edit anything there.
Sent from my GT-I9100 using Tapatalk 4
Jeetu said:
Good work buddy. :thumbup:
Sent from my iPad using Tapatalk HD
Click to expand...
Click to collapse
+1 :thumbup:
Sent from my NeatRom'ed GT-I9300 wifi hotspoting from my NeatRom'ed GT-I9100
---------- Post added at 01:57 PM ---------- Previous post was at 01:57 PM ----------
avirk said:
Thanks buddy. I really want to make it good. Just shout for edit anything there.
Sent from my GT-I9100 using Tapatalk 4
Click to expand...
Click to collapse
Check pm mate
Sent from my NeatRom'ed GT-I9300 wifi hotspoting from my NeatRom'ed GT-I9100
_Sale_ said:
+1 :thumbup:
Sent from my NeatRom'ed GT-I9300 wifi hotspoting from my NeatRom'ed GT-I9100
---------- Post added at 01:57 PM ---------- Previous post was at 01:57 PM ----------
Check pm mate
Sent from my NeatRom'ed GT-I9300 wifi hotspoting from my NeatRom'ed GT-I9100
Click to expand...
Click to collapse
Thanks master. You are always welcome. If its nee any edit just tell me.
Sent from my GT-I9100 using Tapatalk 4
Great Guide
Good Job Done :good::good:
Great guide mate
Envoyé depuis mon GT-I9100 en utilisant Tapatalk 4
Nyc my bro :thumbup::thumbup::thumbup:
Kepp it Up
Sent from my GT-I9500 using Tapatalk 2
A big Thanks to all of you guys.
Sent from my GT-I9100 using Tapatalk 4
Hey avirk, nice job. :thumbup:
3 things to mention:
1. There's no Philz kernel for GB ROMs.
2. They will end up with Superuser, not SuperSu
3. I think after ticking preload in Custom backup job, it is a good idea to Save Philz settings because it needs to stay ticked for restoring backup with preload included as well.
Cheers.
Nice Avirk, good luck :thumbup:
Sent from my Galaxy S2 using XDA Premium 4 mobile appNeed to extend you battery life?Just follow the Bob's battery guide.
@avirk:
Well done mate !
I have just added this guide to the first post of the New Members friendly Q&A thread.
electricsheepdreamer said:
Hey avirk, nice job. :thumbup:
3 things to mention:
1. There's no Philz kernel for GB ROMs.
2. They will end up with Superuser, not SuperSu
3. I think after ticking preload in Custom backup job, it is a good idea to Save Philz settings because it needs to stay ticked for restoring backup with preload included as well.
Cheers.
Click to expand...
Click to collapse
Hmm, For GB link edited with CFroot, and there is any .ini file is missing on my phone so I'm not able to save the settings for Philz so couldn't take any SS for that. If anyone can provide me SS I'll edit the guide again. :good:
gorandroid said:
Nice Avirk, good luck :thumbup:
Sent from my Galaxy S2 using XDA Premium 4 mobile appNeed to extend you battery life?Just follow the Bob's battery guide.
Click to expand...
Click to collapse
Thank you mate.
It_ler said:
@avirk:
Well done mate !
I have just added this guide to the first post of the New Members friendly Q&A thread.
Click to expand...
Click to collapse
Thanks, and that's an honour for me that my first guide and its placed there. Thanks again for look into it and link it there. :victory:
@avirk ,
Good job mate as always :good:
Sent using my Premium-Zanpakutō {斬魄刀} powered by my Shinigami soul <+> ლ(◣_◢)ლ
Christian Nothing said:
@avirk ,
Good job mate as always :good:
Sent using my Premium-Zanpakutō {斬魄刀} powered by my Shinigami soul <+> ლ(◣_◢)ლ
Click to expand...
Click to collapse
Thanks mate, I really appreciate all of your help.
Do i need to install custom recovery like other phones or unlock boot loader to install custom roms?
So ur guide means,
1- install kernel via phone's current stock recovery
2- back up current stock rom "apparently ics for me"
3- place new custom rom zip i got from forum on sd card
4- go to restore factory and format
5- open phone's based recovery mode and choose install zip from sd? And flash rom
That's it? If yes, do i need to reinstall zip kernel to get root again?
Thx dude a lot u r a life saver
Sent from my C6603 using xda premium
ahassouna said:
Do i need to install custom recovery like other phones or unlock boot loader to install custom roms?
So ur guide means,
1- install kernel via phone's current stock recovery
2- back up current stock rom "apparently ics for me"
3- place new custom rom zip i got from forum on sd card
4- go to restore factory and format
5- open phone's based recovery mode and choose install zip from sd? And flash rom
That's it? If yes, do i need to reinstall zip kernel to get root again?
Thx dude a lot u r a life saver
Sent from my C6603 using xda premium
Click to expand...
Click to collapse
If you are on ICS then download the philz kernel and flash it under stock recovery, if possible see if there is the philz available for your firmware. Read the Philz thread carefully.
Place the zip of rom on your sd you got from forum.
After flashing the philz your phone is rooted and you have custom recovery.
Just reboot to recovery again and you will see it.
When you will backup it will backup your current kernel and recovery automatically which would be philz.
If your phone is not locked by any carrier then you don't need to unlock its bootloader its already unlocked.
Do a factory reset from the recovery not from the phone.
Wipe cache and then under Advanced wipe dalvik cache, strongly recommended to not get the bootloop.
Now flash the ROM zip and reboot the phone after completing the flash of zip.
Note: Please read the OP carefully how can you get back your apps and data.
If still have any doubt just ask me without any hesitation. Good luck.
Sent from my GT-I9100 using Tapatalk 4
ahassouna said:
Do i need to install custom recovery like other phones or unlock boot loader to install custom roms?
So ur guide means,
1- install kernel via phone's current stock recovery
2- back up current stock rom "apparently ics for me"
3- place new custom rom zip i got from forum on sd card
4- go to restore factory and format
5- open phone's based recovery mode and choose install zip from sd? And flash rom
That's it? If yes, do i need to reinstall zip kernel to get root again?
Thx dude a lot u r a life saver
Sent from my C6603 using xda premium
Click to expand...
Click to collapse
If you will install a custom ROM like CM, JellyBam, SlimBean(aosp/aokp based), Or my favourite NeatRom(Sammy based custom rom) you don't need to root them again they are all rooted.
After flashing any of these ROM your current kernel will be overwrite by these ROM's default kernel which comes with CWM 6.+. So no need to install the custom recovery again.
And you can't install a ROM with stock recovery you need a custom recovery. If I'm not clear you can ask any time.
It's much much better, I was going to send you a PM about GB root but now it's done, great job mate, really great
Sent from GT-I9100 using Tapatalk 4
Nice effort mate!
Added to my personal list of help threads.. Thanks!!
Most of the people on xda getting error while flashing new update on YU yureka.
so i have created this thread to solve there's problems :highfive:
you just have to follow some steps.
1.you should be on stock recovery.
if you do not have stock recovery then here is LINK
************************************************************
2. now you need big data pack you have to download whole updated stock rom which is approx 643.767 MB
here is LINK.
3. now put this in internal storege(not in any folder or ext_sd card)
4. go to recovery and apply update. and choose this zip file and flash it :good:
and now very important step. Hit thanks button :laugh:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Do i need to be on stock Cm12 ROM to do this?? I am currently running Pac Rom.
Thanks!
sunny765 said:
Do i need to be on stock Cm12 ROM to do this?? I am currently running Pac Rom.
Thanks!
Click to expand...
Click to collapse
yes bro if you want update then you should be on stock if you have backup ur stock rom then just restore it.
koi yaar ye recovery ko flashable zip mai kar k dona plss. direct cwm se stock recovery flash ho esa
Rakesh251 said:
koi yaar ye recovery ko flashable zip mai kar k dona plss. direct cwm se stock recovery flash ho esa
Click to expand...
Click to collapse
have tried flishify app?
LINK
flash using this.
i have not tried yes but search.
Why is it 643 mb the update is just 130mb
thearjunraju said:
Why is it 643 mb the update is just 130mb
Click to expand...
Click to collapse
'cos it's the "whole updated stock rom", i.e., stock rom + the latest update rolled into one convenient easy-to-use package. read the op.
i was reading stock kernel was needed
i know kernel is usually in the full build
so
1. do we need the stock kernel?
2. Will TA backup work?
3. do we need to clear cache and data?
4. Will the existing 3rd party kernel and recoveries work after the update?
As far as I know from my limited flashing experience, the custom kernel will get overwritten by those present in the ROM being flashed.
Sent from my A0001 using XDA Free mobile app
oemaritradey said:
i know kernel is usually in the full build
so
1. do we need the stock kernel?
2. Will TA backup work?
3. do we need to clear cache and data?
4. Will the existing 3rd party kernel and recoveries work after the update?
Click to expand...
Click to collapse
1. you should be on stock kernel.
2.after upgrading your mobile you should take backup again. becoz why you want to revert back to older version ?
3.no need to clear cache and data.
4. yes you can flash any kernel and recovery . i had updated it and i am on TWRP.
*************************************************************************************************************************
feeroz123 said:
As far as I know from my limited flashing experience, the custom kernel will get overwritten by those present in the ROM being flashed.
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
yes you are right but still there is thread on yu forum for it and they said that you should be on stock kernel by the way you can flash it on your current kernel if you see any error then you can flash stock kernel and flash this update
ashish_zarekar said:
1. you should be on stock kernel.
2.after upgrading your mobile you should take backup again. becoz why you want to revert back to older version ?
3.no need to clear cache and data.
4. yes you can flash any kernel and recovery . i had updated it and i am on TWRP.
*************************************************************************************************************************
yes you are right but still there is thread on yu forum for it and they said that you should be on stock kernel by the way you can flash it on your current kernel if you see any error then you can flash stock kernel and flash this update
Click to expand...
Click to collapse
Please flash any custom kernel to see if it works or not :3
oemaritradey said:
Please flash any custom kernel to see if it works or not :3
Click to expand...
Click to collapse
I am on thunderzap kernel
enjoy happy flashing .
best of luck
ashish_zarekar said:
1. you should be on stock kernel.
2.after upgrading your mobile you should take backup again. becoz why you want to revert back to older version ?
3.no need to clear cache and data.
4. yes you can flash any kernel and recovery . i had updated it and i am on TWRP.
*************************************************************************************************************************
yes you are right but still there is thread on yu forum for it and they said that you should be on stock kernel by the way you can flash it on your current kernel if you see any error then you can flash stock kernel and flash this update
Click to expand...
Click to collapse
LOL i tried falshing stock kernel with flashify both time i didnt get wifi signal(MAC UNKNOWN) xD Am not switching over to new update anytime soon....
Flashed this full ROM. Successful !! :highfive:
But I lost Root access and the stock recovery.
I am trying to flash it in fastboot mode, but its stuck at this message:
target reported max download size of 268435456 bytes
sending 'recovery' (8394 KB)...
Without stock recovery, I can't flash the Root.zip file to get root access.
feeroz123 said:
Flashed this full ROM. Successful !! :highfive:
But I lost Root access and the stock recovery.
I am trying to flash it in fastboot mode, but its stuck at this message:
target reported max download size of 268435456 bytes
sending 'recovery' (8394 KB)...
Without stock recovery, I can't flash the Root.zip file to get root access.
Click to expand...
Click to collapse
yes i know when you flash this rom you will lose your root.
and why are you flashing it in fastboot mode ?
this rom is flashable in stock recovery only dont do that.
and what were you doing while you got that error message ?
ashish_zarekar said:
yes i know when you flash this rom you will lose your root.
and why are you flashing it in fastboot mode ?
this rom is flashable in stock recovery only dont do that.
and what were you doing while you got that error message ?
Click to expand...
Click to collapse
I meant, I lost the stock recovery as well. SO I was trying to flash the stock recovery image file in fastboot mode as usual. But it gives me error as I mentioned earlier. My phone is connected to PC while I try to flash the recovery image file. I suspected the drivers got erased, but thats not the case.
Only when I install stock recovery, the Root.zip file can be flashed using it ( to root the phone again). Because flashing the zip files from new Cyanogen Recovery is not at all working. Some R/W or backmap/bitmap kind of issue comes when I try to flash using the updated recovery.
feeroz123 said:
I meant, I lost the stock recovery as well. SO I was trying to flash the stock recovery image file in fastboot mode as usual. But it gives me error as I mentioned earlier. My phone is connected to PC while I try to flash the recovery image file. I suspected the drivers got erased, but thats not the case.
Only when I install stock recovery, the Root.zip file can be flashed using it ( to root the phone again). Because flashing the zip files from new Cyanogen Recovery is not at all working. Some R/W or backmap/bitmap kind of issue comes when I try to flash using the updated recovery.
Click to expand...
Click to collapse
what? you lost your stock recovery ? how is it possible ? it means you dont have any recovery ?
have not face yet.
and how did you flash root.zip file using stock recovey
stock recovery does not have option to flash. it always have update option.
you can flash root.zip file using custom recovery only.
Thankyou for this post... can you please advice to update this ota
I am in stock rom with twrp recovery + sandy kernel
what are the steps to update this ota... can you tell step by step
thank you in advance
m_rajaganesh said:
Thankyou for this post... can you please advice to update this ota
I am in stock rom with twrp recovery + sandy kernel
what are the steps to update this ota... can you tell step by step
thank you in advance
Click to expand...
Click to collapse
DO NOT SPAM.
read carefully i already told the steps in my first POST
download stock kernel and flash it.
download stock recovery and flash it.
now download whole rom from my post and flash it.
ashish_zarekar said:
what? you lost your stock recovery ? how is it possible ? it means you dont have any recovery ?
have not face yet.
and how did you flash root.zip file using stock recovey
stock recovery does not have option to flash. it always have update option.
you can flash root.zip file using custom recovery only.
Click to expand...
Click to collapse
I am sorry, I put it in wrong terms.
The CWM recovery (having basic look with text in blue that can be opted only using hardware buttons and not touch) is not shown for me now. The Cyanogen Recovery it shows me now looks new (with Apply Update option that can be opted by touch as well). THis new recovery fails whenever I try to flash any zip with it. The error being R/W error or something.
With the old recovery (CWM recovery) I could/did flash the Root.zip. After flashing this full ROM (having the patch), the old recovery is lost. It shows only the new recovery. And with it the Root.zip can not be flashed as it fails, as I mentioned earlier.
May be I will get you screenshots of the new Cyanogen recovery to explain what I mean.
Old CWM Recovery:
New Cyanogen Recovery:
Disclaimer!
I, xRaZeR_FuZioNx, or anyone else who is affiliated with this project are not responsible for any kind of damage to your device in any way.
Please use it at your own risk! Whatever you do with your phone is your own choice!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hey guys! Here's TWRP 3 for the Samsung Galaxy Core Prime (G360T/G360T1).
Screenshots:
Installation:
Put your phone into download mode, and connect it to a computer.
Flash TWRP via ODIN.
Boot into TWRP using the key combo (Volume Up, Home, and Power).
Downloads:TWRP 3.0.0-0
Bugs:
MTP may not work correctly.
SlimPickins will not flash. Recommended to flash using TWRP 2, make a backup of the System, then upgrade to TWRP 3.
Special Thanks To:
Y300-0100 - Major contributor, helped fix issues.
Let me just steal this...
You made your own? Checking this out now!!!
Sent from my SM-G360T1 using Tapatalk
bogarty said:
You made your own? Checking this out now!!!
Sent from my SM-G360T1 using Tapatalk
Click to expand...
Click to collapse
Yes, but not without the help of @Y300-0100.
xRaZeR_FuZioNx said:
Disclaimer!
I, xRaZeR_FuZioNx, or anyone else who is affiliated with this project are not responsible for any kind of damage to your device in any way.
Please use it at your own risk! Whatever you do with your phone is your own choice!
Hey guys! Here's TWRP 3 for the Samsung Galaxy Core Prime (G360T/G360T1).
Screenshots:
Installation:
Put your phone into download mode, and connect it to a computer.
Flash TWRP via ODIN.
Boot into TWRP using the key combo (Volume Up, Home, and Power).
Downloads:TWRP 3.0.0-0
Bugs:
MTP may not work correctly.
Special Thanks To:
Y300-0100 - Major contributor, helped fix issues.
Click to expand...
Click to collapse
YASSS!! TWRP 3 is out! Now at least recovery can look nicer and much improved now.
FYI, I was able to successfully make a nandroid backup and restore said backup on TWRP 3.0.0-0. However, with 3.0.0-0 I was unable to clean install Slim Pickins Rom. When that happened I rebooted into download mode, reinstalled TWRP 2.8.7.0, which I was then able to clean install Slim Pickins with
thisisapoorusernamechoice said:
FYI, I was able to successfully make a nandroid backup and restore said backup on TWRP 3.0.0-0. However, with 3.0.0-0 I was unable to clean install Slim Pickins Rom. When that happened I rebooted into download mode, reinstalled TWRP 2.8.7.0, which I was then able to clean install Slim Pickins with
Click to expand...
Click to collapse
Thank you for letting me know. I can confirm this issue appears at the "formatting system" step. I'll look into this issue and see what may be causing it.
thisisapoorusernamechoice said:
FYI, I was able to successfully make a nandroid backup and restore said backup on TWRP 3.0.0-0. However, with 3.0.0-0 I was unable to clean install Slim Pickins Rom. When that happened I rebooted into download mode, reinstalled TWRP 2.8.7.0, which I was then able to clean install Slim Pickins with
Click to expand...
Click to collapse
Twrp 3.0 has options mount system as read only on start up. Was that option ticked?
Y300-0100 said:
Twrp 3.0 has options mount system as read only on start up. Was that option ticked?
Click to expand...
Click to collapse
I don't believe so, if you're referring to the prompt that comes up the first time you boot into TWRP, I told it to go ahead and modify /system/ or whatever. Also I was able to restore a nandroid backup (including the system partition) in TWRP 3.0.0-0 before I came across this issue. Since my memory is imperfect at best, I'll retest it again tonight once I have the free time and access to my phone (it's actually my gf's but she's sold on the whole custom ROM scene since I showed her how much CM improved my S5; now she won't stop asking if I've gotten CM to build successfully yet for this phone lol)
thisisapoorusernamechoice said:
I don't believe so, if you're conflict bing to the prompt that comes up the first time you boot into TWRP, I told it to go ahead and modify /system/ or whatever. Also I was able to restore a nandroid backup (including the system partition) in TWRP 3.0.0-0 before I came across this issue. Since my memory is imperfect at best, I'll retest it again tonight once I have the free time and access to my phone (it's actually my gf's but she's sold on the whole custom ROM scene since I showed her how much CM improved my S5; now she won't stop asking if I've gotten CM to build successfully yet for this phone lol)
Click to expand...
Click to collapse
So as I thought. Wipe system definitely working but there must be some conflict between updare binary and updater script with twrp since you restored system. First recovery wipe system and than restore it.
this conflict is common when rom is made with kitchen.
So wait for cm. It won't be to long
Y300-0100 said:
So wait for cm. It won't be to long
Click to expand...
Click to collapse
God I can't wait. I synced the repos but I can't seem to get it to build, no matter what I tinker with
thisisapoorusernamechoice said:
FYI, I was able to successfully make a nandroid backup and restore said backup on TWRP 3.0.0-0. However, with 3.0.0-0 I was unable to clean install Slim Pickins Rom. When that happened I rebooted into download mode, reinstalled TWRP 2.8.7.0, which I was then able to clean install Slim Pickins with
Click to expand...
Click to collapse
Unfortunately, that was the case for me, too. I was able to wipe but not able to install the Slim Pickins ROM. It came up with an error. So I had to go back to TWRP 2.8.7.0 and successfully install the ROM.
Thanks
I've hung out in the irc almost every day and got to see this be made and released thanks all to who contributed to it now to make cm
I flashed this via an app, and I got a recovery loop. I don't have access to a computer so I can't use odin. Any way to fix this recovery loop?
X_shinobi.apk_X said:
I flashed this via an app, and I got a recovery loop. I don't have access to a computer so I can't use odin. Any way to fix this recovery loop?
Click to expand...
Click to collapse
What app did you use? The only app I know of that flashes Odin files is "Mobile Odin" by Chainfire, but I think it's still not compatible with our device, so the only way to flash TWRP is via Odin and the only way for you to fix boot is to flash either Trapkernel or the stock firmware in Odin. The only other way I can think of is if you maybe had TWRP 2 installed before this and you're still able to boot into it and restore a previous backup.
Sent from my SM-G360T1 using Tapatalk
bogarty said:
What app did you use? The only app I know of that flashes Odin files is "Mobile Odin" by Chainfire, but I think it's still not compatible with our device, so the only way to flash TWRP is via Odin and the only way for you to fix boot is to flash either Trapkernel or the stock firmware in Odin. The only other way I can think of is if you maybe had TWRP 2 installed before this and you're still able to boot into it and restore a previous backup.
Sent from my SM-G360T1 using Tapatalk
Click to expand...
Click to collapse
I just extracted the file, then just used rom installers flash image feature. And I fix it by using twrps terminal command feature and just dd my stock recovery I keep as a backup.
X_shinobi.apk_X said:
I just extracted the file, then just used rom installers flash image feature. And I fix it by using twrps terminal command feature and just dd my stock recovery I keep as a backup.
Click to expand...
Click to collapse
OK. I think I know what the problem was. Yes you can flash the recovery.img in a flash tool app. I just verified that it does work for this recovery too by using an app called "Rashr" and successfully flashing from TWRP 2 to TWRP 3 using the extracted recovery.img for TWRP 3. When it's done though it asks if you want to reboot to recovery, which you must've done. You can not select reboot to recovery from anywhere on this device without causing a recovery loop. I'd say you could try flashing the boot.img from the Trapkernel.zip in your flash tool app too to fix boot, but since you can't use apps right now and have no way to access a backup, then you will need to find a computer to fix your device.
Sent from my SM-G360T1 using Tapatalk
bogarty said:
OK. I think I know what the problem was. Yes you can flash the recovery.img in a flash tool app. I just verified that it does work for this recovery too by using an app called "Rashr" and successfully flashing from TWRP 2 to TWRP 3 using the extracted recovery.img for TWRP 3. When it's done though it asks if you want to reboot to recovery, which you must've done. You can not select reboot to recovery from anywhere on this device without causing a recovery loop. I'd say you could try flashing the boot.img from the Trapkernel.zip in your flash tool app too to fix boot, but since you can't use apps right now and have no way to access a backup, then you will need to find a computer to fix your device.
Sent from my SM-G360T1 using Tapatalk
Click to expand...
Click to collapse
Yeah I figured it out, I planned for such a problem and made backup of the stock recovery so I could use the terminal from advanced options to flash it. Let me know when they solve this issue.
Sent from my SM-G360T1 using XDA-Developers mobile app
X_shinobi.apk_X said:
Yeah I figured it out, I planned for such a problem and made backup of the stock recovery so I could use the terminal from advanced options to flash it. Let me know when they solve this issue.
Sent from my SM-G360T1 using XDA-Developers mobile app
Click to expand...
Click to collapse
Try using flash fire by chainfire if you still need to install twrp and can't use a PC. It's the successor to mobile Odin and is compatible with way more devices including virtually every Samsung device. Flashify might work too. Obviously either app will require root
X_shinobi.apk_X said:
Yeah I figured it out, I planned for such a problem and made backup of the stock recovery so I could use the terminal from advanced options to flash it. Let me know when they solve this issue.
Sent from my SM-G360T1 using XDA-Developers mobile app
Click to expand...
Click to collapse
I think the "reboot to recovery" causing a recovery loop issue might be a system one. It's always been an issue on this device. There are quite a few versions of TWRP now for the SM-G360T1, but all if them do it. I think it even did it with the stock recovery too. Not a big deal though in my mind. Just have to remember to always reboot normal.