Related
Hi All,
1. Will unlock the bootloader wipe out the phone? If so how to root 2.3.6 without losing data?
I want to backup my data in the N1, then do flash the CM7 mod onto that.
It's in retail 2.3.6, I want to backup my data first.
sms, did with sms backup and restore.
call logs and bookmarks, how I backup them?
apps, want to backup with titanium backup, but hasn't root the phone yet.
I found the root guide for 2.3.6 here
https://bexton.net/2011/10/12/bexboot-root-nexus-one-passion-grk39f/
But it wants me to unlock the bootloader first, unlock the bootloader will wipe the phone so I will lost my data right?
apps can be redownloaded, so how I backup my call logs and bookmarks without root (yet)?
--
another question is I see the note for the latest N1 CM7 build is
'The latest radio is needed to run CyanogenMod 7'.
I can see my phone already has baseband of 5.08.00.04, do I need to do anything related to the radio while I flashing CM7?
Regards,
Sorry, there is NO way to back up your data if you are on 2.3.6 with a locked bootloader and without root.
I'm on stock 2.3.6.
Tried using the bexboot method, but it goes through all the steps and does nothing.
The bat file at the end doesn't reboot my phone or root.
I have also tried downgrading my device, but every time i go into fastboot, it says I have the wrong img file, or the file can't be found. I have properly renamed the file and put it on my sd card. no luck.
please help
patelkartik27 said:
I'm on stock 2.3.6.
Tried using the bexboot method, but it goes through all the steps and does nothing.
The bat file at the end doesn't reboot my phone or root.
I have also tried downgrading my device, but every time i go into fastboot, it says I have the wrong img file, or the file can't be found. I have properly renamed the file and put it on my sd card. no luck.
please help
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=18527514&postcount=1853
patelkartik27 said:
I'm on stock 2.3.6.
Tried using the bexboot method, but it goes through all the steps and does nothing.
The bat file at the end doesn't reboot my phone or root.
I have also tried downgrading my device, but every time i go into fastboot, it says I have the wrong img file, or the file can't be found. I have properly renamed the file and put it on my sd card. no luck.
please help
Click to expand...
Click to collapse
Sry for the late response, but i've been on a business trip. The issue with my first version of bexboot was, that it was compiled from a heavily "prestressed" system with lots of modifications. Thus i rebuilt the boot image from a complete clean source.
So if somebody is still looking for an "idiot-proof" way to root a Nexus One on stock GRK39F, check out the updated version release of Bexboot v2.0 what have been confirmed working from people who had issues with v1:
https://bexton.net/2011/11/07/bexboot-for-passion-version-2-root-for-nexus-one-with-android-grk39f/
Greets!
Bexton said:
Sry for the late response, but i've been on a business trip. The issue with my first version of bexboot was, that it was compiled from a heavily "prestressed" system with lots of modifications. Thus i rebuilt the boot image from a complete clean source.
So if somebody is still looking for an "idiot-proof" way to root a Nexus One on stock GRK39F, check out the updated version release of Bexboot v2.0 what have been confirmed working from people who had issues with v1:
https://bexton.net/2011/11/07/bexboot-for-passion-version-2-root-for-nexus-one-with-android-grk39f/
Greets!
Click to expand...
Click to collapse
What is the advantage of doing this, if all you have to do is flash a custom recovery and flash this from recovery??
efrant said:
What is the advantage of doing this, if all you have to do is flash a custom recovery and flash this from recovery??
Click to expand...
Click to collapse
Hey Efrant,
well, actually there is no big difference. But if i should find some, maybe:
A) ALL-IN-ONE
* It comes packed with all you need.
* There is no need to have the SDK installed before using it.
* You don't need to flash a custom recovery before using it.
B) STOCK
* As you don't need a custom recovery to flash it, you also don't need to overwrite any of the original stock ROM files. So actually your system stays completely untouched.
C) UP-TO-DATE
* It installs the latest versions of Superuser APK / su binary, rather than the linked ones.
The bottom line: Actually it was built for "beginners", to provide a simple to use method to root a stock ROM. You can download a zip archive, connect an untouched, never used/modified stock phone to a computer, type two/three commands in a terminal window, the phone reboots, you have root and the system is still pure stock. That's what it's all about..
Cheers!
Bexton said:
Hey Efrant,
well, actually there is no big difference. But if i should find some, maybe:
A) ALL-IN-ONE
* It comes packed with all you need.
* There is no need to have the SDK installed before using it.
* You don't need to flash a custom recovery before using it.
B) STOCK
* As you don't need a custom recovery to flash it, you also don't need to overwrite any of the original stock ROM files. So actually your system stays completely untouched.
C) UP-TO-DATE
* It installs the latest versions of Superuser APK / su binary, rather than the linked ones.
The bottom line: Actually it was built for "beginners", to provide a simple to use method to root a stock ROM. You can download a zip archive, connect an untouched, never used/modified stock phone to a computer, type two/three commands in a terminal window, the phone reboots, you have root and the system is still pure stock. That's what it's all about..
Cheers!
Click to expand...
Click to collapse
Thanks for the explanation. Good work.
But just to address some of your points:
A) ALL-IN-ONE:
if you don't install the SDK, you still need to install the fastboot and ADB drivers anyway - there is no difference between using this method or any other method, i.e., either the SDK or the drivers themselves have to be installed for your device to be recognized by the computer.
B) STOCK:
flashing a custom recovery on a stock ROM does not really overwrite anything, because once you boot your device, the stock recovery is automatically flashed back by the ROM.
no ROM files are touched by flashing a custom recovery.
C) UP-TO-DATE
I linked to the wrong thread in my post.. oops I meant to link here: http://androidsu.com/superuser/
efrant said:
Thanks for the explanation. Good work.
But just to address some of your points:
A) ALL-IN-ONE:
if you don't install the SDK, you still need to install the fastboot and ADB drivers anyway - there is no difference between using this method or any other method, i.e., either the SDK or the drivers themselves have to be installed for your device to be recognized by the computer.
B) STOCK:
flashing a custom recovery on a stock ROM does not really overwrite anything, because once you boot your device, the stock recovery is automatically flashed back by the ROM.
no ROM files are touched by flashing a custom recovery.
C) UP-TO-DATE
I linked to the wrong thread in my post.. oops I meant to link here: http://androidsu.com/superuser/
Click to expand...
Click to collapse
Well, as said: actually there's no big difference. And yeah, indeed you're right about the recoveries. But to address one of your (/my) points:
The SDK is an application package that needs to be installed.
Fastboot, as well as the ADB are standalone executables; there is nothing to be installed. These executables are just a tiny part of the whole SDK Package. There's no need to download and install all the SDK Package, if you'd need just the adb, the fastboot and the drivers. Thus you'd save at least some time (and bandwith).
Also, when i'll include the install script tomorrow (as it has been with v1), it will reduce the number of commands you have to type in the terminal to two.
So the bottom line: eventhough you're right about (almost all of) your contras, if you'd need to start with an untouched phone and computer it's definitely faster - and i think, also just simpler - to do it "my way".
But.. anyway.. it's the same way.
---------- Post added at 10:46 PM ---------- Previous post was at 10:34 PM ----------
PS: And therefore - to re-answer your initial question:
efrant said:
What is the advantage of doing this, if all you have to do is flash a custom recovery and flash this from recovery??
Click to expand...
Click to collapse
Depending on your working environment, it simply can save some time.
First I would like to thank PlayfulGod and mtmichaelson for the development that makes this work. The other credits as mentioned in the bat file are djrbliss, DRockstar, koush, Raidzero, thecubed, and firon.
This All in One will root, unroot, install and uninstall CWM without any pre setup on your V8 & V9 Revo. Super easy!
I modified the LG-Esteem-Revo_AIO.zip to work on my Revo and thought others would find it useful. I modified the bat file and moved a few things around. I tested all of the options on my V8 Revo. When using this your phone will reboot several times during the process. Please note that your phone needs to have USB Debugging enabled and the phone needs to be in Internet Connection mode.
I am NOT a phone expert!!! So please remember that if you have any trouble!
Please give all credit to the developers as shown above.
The original file was no good. Sorry!
*** NEW FILE LINK ***
http://www.filefactory.com/file/7f2w7g1h3i99/n/Root-CWM_zip
Filefactory is adding the ' before and after the file name. I have NO idea of why. Just rename the file without the ' and it works as expected!
I added another copy of the file here:
https://www.box.com/s/8867602e2ff53649c37b
CWM would NOT work on my wife's rooted Revo after using this tool. I had to use the LGNPST tool and replace the V8 software. Worked perfectly afterward! Rooted and CWM V8!!!
Mark Once Again said:
First I would like to thank PlayfulGod and mtmichaelson for the development that makes this work. The other credits as mentioned in the bat file are djrbliss, DRockstar, koush, Raidzero, thecubed, and firon.
This All in One will root, unroot, install and uninstall CWM without any pre setup on your V8 Revo. Super easy!
I modified the LG-Esteem-Revo_AIO.zip to work on my Revo and thought others would find it useful. I modified the bat file and moved a few things around. I tested all of the options on my V8 Revo. When using this your phone will reboot several times during the process. Please note that your phone needs to have USB Debugging enabled and the phone needs to be in Internet Connection mode.
I am NOT a phone expert!!! So please remember that if you have any trouble!
Please give all credit to the developers as shown above.
http://www.filefactory.com/file/4g1l2reuoyxz/n/V8_All_In_One_-_Root_and_CWM.zip
Click to expand...
Click to collapse
Has anyone tried this yet? I'm trying to get my ZV8 to root, but I don't know how.
SmokinHawtVegasChic said:
Has anyone tried this yet? I'm trying to get my ZV8 to root, but I don't know how.
Click to expand...
Click to collapse
This is how apparently
Sent from my VS910 4G using xda premium
Make sure you backup your current setup before trying any new root method. Ive been saved countless times by this and some people are just to lazy to let the phone backup for ten minutes, because they get over excited by being able to root a new version.
Sent from my ASUS Transformer Pad TF300T using XDA Premium HD app
File replaced
The original file was bad. Sorry!
New link posted above and here:
http://www.filefactory.com/file/7f2w7g1h3i99/n/Root-CWM_zip
Filefactory is adding the ' before and after the file name. I have NO idea of why. Just rename the file without the ' and it works as expected!
Additional info - Needs stock V8 to work!
CWM would NOT work on my wife's rooted Revo after using this installation tool. I had to use the LGNPST tool and replace the V8 software. Worked perfectly afterward! Rooted and CWM V8!!!
Mark Once Again said:
CWM would NOT work on my wife's rooted Revo after using this installation tool. I had to use the LGNPST tool and replace the V8 software. Worked perfectly afterward! Rooted and CWM V8!!!
Click to expand...
Click to collapse
Wait how do i do that? :/
you mean use lgpnst?
see here: http://forum.xda-developers.com/showthread.php?t=1337386
my download failed...
it will only let me download the file once and my download failed can u plz post a new link? or a torrent??
---------- Post added at 03:06 AM ---------- Previous post was at 02:09 AM ----------
just tried it, went straight to zv8 and rooted with esteem aio, works perfect thanks so much
I uploaded another copy here:
https://www.box.com/s/8867602e2ff53649c37b
Hope it works better.
My vz9 OTA keeps failing, even after running Stock Recovery in this AIO...others having the same issue?
---------- Post added at 02:16 PM ---------- Previous post was at 02:04 PM ----------
also, when I choose the "Unroot and Stock Recovery" option it says:
"The system cannot find the batch label specified - UNROOTSTOCK"
ok I downloaded from the newer box.com link and that solved the cannot find the UNROOTSTOCK issue. But I still cannot successfully push stock recovery. It says
# is not recognized as an internal or external command
I tried it on my Revo. I got the same message. When the phone booted back up it had the stock recovery and root was gone. I don't know why the message shows up but the result was correct. Hope it helps. Hopefully someone with more knowledge can improve this. I put CWM and root back on without a hitch with option 2.
I successfully reverted back to stock recovery using this thread's AIO - I chose option 4 for stock recovery. I didn't chose 'unroot and stock recovery'. After that the OTA successfully pushed VZ9 to my device without error and I re-rooted using the Esteem root method here:
http://forum.xda-developers.com/showthread.php?t=1621625
After that, I used this thread's AIO Option 2: root and recovery to get CWM back. root just failed because I was already rooted using the Esteem method but CWM re-installed.
Only hiccup is after I re-rooted, my phone booted and hung at the black screen after about 3 seconds of the intro splash. I hard reset and restored all of my data (cwm - advanced restore - data only) using a CWM backup I did just before beginning. Maybe if I wiped dalvik and cache before starting it might have prevented that bump in the road?
All good now: VZ9 rooted with CWM and my phone and data just as it was before the OTA.
jeff_roey said:
I successfully reverted back to stock recovery using this thread's AIO - I chose option 4 for stock recovery. I didn't chose 'unroot and stock recovery'. After that the OTA successfully pushed VZ9 to my device without error and I re-rooted using the Esteem root method here:
http://forum.xda-developers.com/showthread.php?t=1621625
After that, I used this thread's AIO Option 2: root and recovery to get CWM back. root just failed because I was already rooted using the Esteem method but CWM re-installed.
Only hiccup is after I re-rooted, my phone booted and hung at the black screen after about 3 seconds of the intro splash. I hard reset and restored all of my data (cwm - advanced restore - data only) using a CWM backup I did just before beginning. Maybe if I wiped dalvik and cache before starting it might have prevented that bump in the road?
All good now: VZ9 rooted with CWM and my phone and data just as it was before the OTA.
Click to expand...
Click to collapse
When you did option for to install Stock Recovery did you get the "# is not a recognized internal or external command" as part of the activity string?
dbeauch said:
When you did option for to install Stock Recovery did you get the "# is not a recognized internal or external command" as part of the activity string?
Click to expand...
Click to collapse
I honestly don't recall. My phone did reboot 3 times and the final command line message informed me that stock recovery was installed. Aside form that, I didn't pay much attention to the string messages.
jeff_roey said:
I successfully reverted back to stock recovery using this thread's AIO - I chose option 4 for stock recovery. I didn't chose 'unroot and stock recovery'. After that the OTA successfully pushed VZ9 to my device without error and I re-rooted using the Esteem root method here:
http://forum.xda-developers.com/showthread.php?t=1621625
After that, I used this thread's AIO Option 2: root and recovery to get CWM back. root just failed because I was already rooted using the Esteem method but CWM re-installed.
Only hiccup is after I re-rooted, my phone booted and hung at the black screen after about 3 seconds of the intro splash. I hard reset and restored all of my data (cwm - advanced restore - data only) using a CWM backup I did just before beginning. Maybe if I wiped dalvik and cache before starting it might have prevented that bump in the road?
All good now: VZ9 rooted with CWM and my phone and data just as it was before the OTA.
Click to expand...
Click to collapse
Does this work with Broken Out? Or were yo running stock when you used this?
My Revo is Broken out and works fine.
My wife's Revo is stock and works fine.
I have a heavily modified version of BO and after trying both option 4 and 5 the update failed.
sleepycarl5150 said:
I have a heavily modified version of BO and after trying both option 4 and 5 the update failed.
Click to expand...
Click to collapse
Yeah same for me man. I had to use LGNPST to go back to V7, then did OTA updates to V8 then V9. So I am on V9 now unrooted, and stock, waiting for MT or someone else to do a V9 ROM...hopefully I don't have to wait long...BING SUCKS!
Hello,
I'm trying to root my S5830 but it's not working. I have had it rooted before because I installed Samsung's stock android version 2.3.6 (The phone originally came with 2.2.1 I think).
The exact stock firmware on the phone is GINGERBREAD.XWKTQ.
I tried applying the universal_gb_root_v25 file in recovery mode and it seems to be working. There's no errors or anything and it tells me the device has been rooted and to restart. However after restarting, the device does not appear to be rooted at all, RootValidate tells me root access is not available. What am I doing wrong?
Thank you!
Cannot root S5830 2.3.6
brummbeere said:
Hello,
I'm trying to root my S5830 but it's not working. I have had it rooted before because I installed Samsung's stock android version 2.3.6 (The phone originally came with 2.2.1 I think).
The exact stock firmware on the phone is GINGERBREAD.XWKTQ.
I tried applying the universal_gb_root_v25 file in recovery mode and it seems to be working. There's no errors or anything and it tells me the device has been rooted and to restart. However after restarting, the device does not appear to be rooted at all, RootValidate tells me root access is not available. What am I doing wrong?
Thank you!
Click to expand...
Click to collapse
have you just installed custom recovery?
I remeber you need first to root the phone and later install custom recovery.
If you not installed custom recovery, try to flash the attached file.
daniga74
daniga74 said:
have you just installed custom recovery?
I remeber you need first to root the phone and later install custom recovery.
If you not installed custom recovery, try to flash the attached file.
daniga74
Click to expand...
Click to collapse
Thanks, what custom recovery are you talking about? I just entered the default android recovery mode by pressing HOME and POWER buttons on startup. I tried the upd_1 file in recovery mode and it ran okay, but unfortunately it didn't fix the problem.
brummbeere said:
Thanks, what custom recovery are you talking about? I just entered the default android recovery mode by pressing HOME and POWER buttons on startup. I tried the upd_1 file in recovery mode and it ran okay, but unfortunately it didn't fix the problem.
Click to expand...
Click to collapse
I talk about CWM /clockwork) 5.0.2.6
This fixed it for me:
http://forum.xda-developers.com/showthread.php?t=1850070
So it seems the problem was there was not enough space left and I first had to run Delete_thinkdroid.zip to free up some space. After that I applied upd_1.zip and now the phone is rooted.
Please click one of the Quick Reply icons in the posts above to activate Quick Reply.
---------- Post added at 01:14 PM ---------- Previous post was at 01:13 PM ----------
glad to know now it works!!!
Well done
If you need to root your device, I've a post too when you can find a couple of script to get some free internal space in order to achieve your goal
I would install KITKAT on my Galaxy S i9000 using the TWRP recovery.
In the list of devices on which you can mount the TWRP not indicated the Galaxy S I9000.
It 'an error or you can not?
1. download http://forum.xda-developers.com/showthread.php?t=1644240
2. download CodeROM-5.1.1-20150825-galaxysmtd
3. extract boot.img and rename it to zImage
4. run tar.bat
Result attached for convenience. All credits go to the devs!
Fragone said:
1. download http://forum.xda-developers.com/showthread.php?t=1644240
2. download CodeROM-5.1.1-20150825-galaxysmtd
3. extract boot.img and rename it to zImage
4. run tar.bat
Result attached for convenience. All credits go to the devs!
Click to expand...
Click to collapse
I will choose the ROM later.
Now I have already choosed the procedure to save EFS files.
Now I'm choosing what type of recovery use.
I repeat: I would use TWRP but my smartphone does not appear in the list of supported devices.
On the contrary, in all the guides TWRP is indicated as an alternative to CWR.
Original TWRP is not available for i9000.
BUT: The CodeROM-Team managed to make it running onto i9000. Therefore, you need to extract TWRP from their ROM, convert it to an Imagefile and upload it with ODIN. This works!
Hello, I would like to also do this as stated in the OP. The image in the kernel.tar, that's what I have to flash the i9000 with Odin? Do I have twrp recovery then in the i9000?
Fragone said:
1. download http://forum.xda-developers.com/showthread.php?t=1644240
2. download CodeROM-5.1.1-20150825-galaxysmtd
3. extract boot.img and rename it to zImage
4. run tar.bat
Result attached for convenience. All credits go to the devs!
Click to expand...
Click to collapse
I downloaded the attached kernel attachment and flashed it with Odin. After doing this, the phone booted up in TWRP 2.8.7.0, but deleted the stock ROM. That's not all, I cannot do anything anymore with the phone, because the phone gives error with every ROM I try to install: "Unable to mount '/system'" and "Unable to mount '/data'". The phone does not boot in download mode either.
The big question is now, how to solve these errors? Can anyone help?
bronxboy1 said:
I downloaded the attached kernel attachment and flashed it with Odin. After doing this, the phone booted up in TWRP 2.8.7.0, but deleted the stock ROM. That's not all, I cannot do anything anymore with the phone, because the phone gives error with every ROM I try to install: "Unable to mount '/system'" and "Unable to mount '/data'". The phone does not boot in download mode either.
The big question is now, how to solve these errors? Can anyone help?
Click to expand...
Click to collapse
It seems that this Recovery with CWM does not support any other ROMs than CodeROM . Had the same problem lately, but in my case I expected it to be due to the fact that i changed the Filesystem of /system and /data to F2FS, but apparently that was not the main cause. (By the way- don't do that. It took me 2 days to get it back to EXT again).
The only way to solve it was to flash a complete Stock ROM with ODIN (I had to do it twice until everything was working again), using the files you'll find in the Stock-Rom-DB. I used this ones (sorry, no link atm, but you'll find it easily):
CSC_OXXJVC.tar.md5 3'778'609 20.04.2012 23:42 -a--
PDA_XWJW5_Sbl.tar.md5 285'562'932 20.04.2012 23:40 -a--
PHONE_XXJW4.tar.md5 12'585'010 27.04.2012 16:17 -a--
s1_odin_20100512.pit 1'744 06.08.2010 16:56 -a--
Luckily this did not affectet the area where the phones special data is located (IMEI and so on, donnot remeber the correct name for that).
I'm now back onto latest official CM10, because newer releases had quite a few issues, especialy bad connectivity (dont know why). With android 4.4.4 everything is working perfectly again.
Hope that helps to fix the problems my file did!
---------- Post added at 05:13 PM ---------- Previous post was at 05:08 PM ----------
Fragone said:
It seems that this Recovery with CWM does not support any other ROMs than CodeROM . Had the same problem lately, but in my case I expected it to be due to the fact that i changed the Filesystem of /system and /data to F2FS, but apparently that was not the main cause. (By the way- don't do that. It took me 2 days to get it back to EXT again).
The only way to solve it was to flash a complete Stock ROM with ODIN (I had to do it twice until everything was working again), using the files you'll find in the Stock-Rom-DB. I used this ones (sorry, no link atm, but you'll find it easily):
CSC_OXXJVC.tar.md5 3'778'609 20.04.2012 23:42 -a--
PDA_XWJW5_Sbl.tar.md5 285'562'932 20.04.2012 23:40 -a--
PHONE_XXJW4.tar.md5 12'585'010 27.04.2012 16:17 -a--
s1_odin_20100512.pit 1'744 06.08.2010 16:56 -a--
Luckily this did not affectet the area where the phones special data is located (IMEI and so on, donnot remeber the correct name for that).
I'm now back onto latest official CM10, because newer releases had quite a few issues, especialy bad connectivity (dont know why). With android 4.4.4 everything is working perfectly again.
Hope that helps to fix the problems my file did!
Click to expand...
Click to collapse
> The phone does not boot in download mode either
Did not see that before. I never had such an issue. Try it again, but do not push the power button more than 10 seconds, else the phone reboots again and again.
Sometimes, Download mode works even thought you cannot see anything on screen. try to connect the device to your PC and launch ODIN, you'll see if it can connect.
Tnx for your reply Fragone. It took me a while, had to wait on a USB jig for me to get the phone in download mode.
Unfortunately I did format to f2fs, how did you get back to ext? As for the other files, I did get my hands on an original rom, but I have to go look for the files you mentioned and try it with those, as the stock rom does not boot either. If you have the links, I'd be much abliged. Right now I go to sleep, just got home from the graveyard shift.
So someone finally returned my i9000 to me after a few years of use and I'm looking to put a current ROM on it so I can use it as a test phone. I keep seeing TWRP as the custom recovery used for the new ROMs. And yet like umberto, I've found there's no official custom TWRP for this phone. I'm pretty familiar with using TWRP on all my other devices.
So back to the original question of this thread - is there a way to get TWRP on the phone? It looks like Fragone's suggestion isn't the right way to go? The only thing I could find in my thread searches was a suggestion to use Mackay's ROM to get 2.8.1.0 and then (theoretically) it's on there so you could move to other ROMs. Any help?
D
@umberto santulli @dnaod
On the i9000, kernel & recovery share the same image, thus the recovery cannot be flashed separately. Therefore there is no i9000 on the TWRP site.
Yes, there are several kernels that feature TWRP, but you must be careful: kernel must be compatible with the ROM, otherwise, bootloop is result.
tetakpatalked from 1+One
tetakpatak said:
@umberto santulli @dnaod
Yes, there are several kernels that feature TWRP, but you must be careful: kernel must be compatible with the ROM, otherwise, bootloop is result.
tetakpatalked from 1+One
Click to expand...
Click to collapse
Thanks for this warning. I've flashed MacKay's ROM and am playing with it right now. I was planning on flashing OmniROM later using this same TWRP but I'm guessing I should read quite a bit more carefully with every ROM to see if they're compatible.
dnaod said:
Thanks for this warning. I've flashed MacKay's ROM and am playing with it right now. I was planning on flashing OmniROM later using this same TWRP but I'm guessing I should read quite a bit more carefully with every ROM to see if they're compatible.
Click to expand...
Click to collapse
There should be no problem to change the ROM. Just mind that the kernel & recovery share the image. I was using Omni 4.4.4 by kasper_h and Mackay kernel with TWRP
tetakpatalked from Nexus 7 flo
Ok, so here is an explanation of what I have going on here. My ultimate goal is to install Magisk on my phone (Running Kitkat 4.4) . I have learned that in order to do that, I need to install a custom recovery on my phone. I have learned that normal custom recoveries cannot be installed on AT&T phones because they have double locked bootloaders or something of that nature, but that Safestrap can work around it. So after finding all that out I successfully installed Safestrap then went on to install Magisk, but when I tried to install the zip, I was told that it is only compatible with Android 5.0 minimum. Fast-forward, I install Lollipop 5.0 on my phone successfully. I then go back and install safestrap, however it appears that it is now not compatible with my upgraded kernel and will not show me the custom recovery on startup... So it seems as if Safestrap will only work for me on Kitkat, but what I need it to do I can only do on Lollipop. Am I simply out of luck, or is there some cleaver way around this?
I appreciate any help I can get on the matter.
Did you root your phone while on KK? If not, you may be out of luck now. There are a few lollipop rooted rooms that will work and you can keep using SS but you must already be rooted. Mine is still rooted with SS, I am not upgrading for the foreseeable future.
johnkirchner said:
Did you root your phone while on KK? If not, you may be out of luck now. There are a few lollipop rooted rooms that will work and you can keep using SS but you must already be rooted. Mine is still rooted with SS, I am not upgrading for the foreseeable future.
Click to expand...
Click to collapse
Yes, I rooted my phone while still on KK, then I used Flashfire to upgrade to LP which allowed me to still keep root.
Unfortunately I am not sure why SS isn't working for you, not sure if the lollipop Rom you installed is having issues with it or what? As for the locked boot loader, these phones are like fort Knox. SS is merely a bypass that does not replace an unlocked boot loader.
Justhere4GO said:
Yes, I rooted my phone while still on KK, then I used Flashfire to upgrade to LP which allowed me to still keep root.
Click to expand...
Click to collapse
Ok so if you have three of these four things it should work for you depending if your running a g900a or 870a ,1. you will need the kernel flasher ,900a takes nce kernel flasher , 870a requires ng3 kernal flasher , these are model specific. 2. Busybox installed . 3. Safestrap. 4 safetrap flashable kernels.zips. install busybox, install whichever specific kernel flasher you have per your model, install safetrap. Make sure you have the flashable kernel zip for lollipop on external sd for safe keeping. Cuz if you wipe internal sd for any reason and the zip you will have to resort to the odin flashable versions and odin. Then flash kk kernel with flasher apk then you should enter ss ,flash install magisk then install again the recovery flashable kernel .zip for lollipop and then reboot back into lollipop. All good.
Sent from my SM-G900F using XDA-Developers mobile app
captivated1971 said:
Ok so if you have three of these four things it should work for you depending if your running a g900a or 870a ,1. you will need the kernel flasher ,900a takes nce kernel flasher , 870a requires ng3 kernal flasher , these are model specific. 2. Busybox installed . 3. Safestrap. 4 safetrap flashable kernels.zips. install busybox, install whichever specific kernel flasher you have per your model, install safetrap. Make sure you have the flashable kernel zip for lollipop on external sd for safe keeping. Cuz if you wipe internal sd for any reason and the zip you will have to resort to the odin flashable versions and odin. Then flash kk kernel with flasher apk then you should enter ss ,flash install magisk then install again the recovery flashable kernel .zip for lollipop and then reboot back into lollipop. All good.
Click to expand...
Click to collapse
Alright, now we're getting somewhere. So I downloaded NCE Kernel Flasher (I have 900a), along with the G900A_OC4_Stock_KERNEL_Recovery-Flashable.zip file. So is that file the stock kernel for Lollipop to bring me back after using the program? From what the instructions say, it looks like the NCE Kernel Flasher already comes with the Kitkat kernel in it, but I am still not certain I am reading this correctly.
My second question is about the Magisk program itself if you have any insight on that which you could offer. It is recommended that it be installed on a stock rom, and I believe I need to be unrooted when I put it on to make it work correctly. So while I'm in the safestrap recovery via NCE Flasher, should I do a factory reset first, then flash magisk, then flash the stock kernel zip?
Justhere4GO said:
Alright, now we're getting somewhere. So I downloaded NCE Kernel Flasher (I have 900a), along with the G900A_OC4_Stock_KERNEL_Recovery-Flashable.zip file. So is that file the stock kernel for Lollipop to bring me back after using the program? From what the instructions say, it looks like the NCE Kernel Flasher already comes with the Kitkat kernel in it, but I am still not certain I am reading this correctly.
My second question is about the Magisk program itself if you have any insight on that which you could offer. It is recommended that it be installed on a stock rom, and I believe I need to be unrooted when I put it on to make it work correctly. So while I'm in the safestrap recovery via NCE Flasher, should I do a factory reset first, then flash magisk, then flash the stock kernel zip?
Click to expand...
Click to collapse
Really i havent messed with magisk at all so i cant say anything about that . But yes after you flash it or install it just go back to the install button and install the kernel zip to get you back to lollipop. Then reboot. And yes they are only stock kernels because the bootloader wont let us use custom kernels
Sent from my SM-G900F using XDA-Developers mobile app
---------- Post added at 10:56 AM ---------- Previous post was at 10:55 AM ----------
But on your second question i dont see how you can install it and not be rooted . Because you have to be rooted to have ss running.
Sent from my SM-G900F using XDA-Developers mobile app
captivated1971 said:
Really i havent messed with magisk at all so i cant say anything about that . But yes after you flash it or install it just go back to the install button and install the kernel zip to get you back to lollipop. Then reboot. And yes they are only stock kernels because the bootloader wont let us use custom kernels
Sent from my SM-G900F using XDA-Developers mobile app
---------- Post added at 10:56 AM ---------- Previous post was at 10:55 AM ----------
But on your second question i dont see how you can install it and not be rooted . Because you have to be rooted to have ss running.
Sent from my SM-G900F using XDA-Developers mobile app
Click to expand...
Click to collapse
Ok, thanks. I successfully booted up into SS mode. I made a backup just in case I need it, then did a factory reset. I chose my Magisk file through the install option, and confirmed it for installation. But now is shows that it is flashing the file, but I have been stuck on the same screen for roughly 20 minutes so far, with no progress on the status bar. From all of the videos I've seen, it looks like this flashing procedure shouldn't take longer than a minute or so, and I fear that something has gone wrong. I know I need to flash my Lollipop kernal back prior to leaving SS, but if my phone is indeed frozen, if I take out the battery and power it up, will I still get a SS Recovery prompt prior to my Samsung logo popping up so I can restore the backup and my correct kernel, or am I on the path to bricksville?
captivated1971 said:
Really i havent messed with magisk at all so i cant say anything about that . But yes after you flash it or install it just go back to the install button and install the kernel zip to get you back to lollipop. Then reboot. And yes they are only stock kernels because the bootloader wont let us use custom kernels
Sent from my SM-G900F using XDA-Developers mobile app
---------- Post added at 10:56 AM ---------- Previous post was at 10:55 AM ----------
But on your second question i dont see how you can install it and not be rooted . Because you have to be rooted to have ss running.
Click to expand...
Click to collapse
So I did just take out the battery, and was able to get back into custom recovery and restore my backup. I tried to install magisk a few more times to no avail. (Kept saying installing but never progressed) My only thought is that maybe because Magisk is not compatible with Kitkat, I would need to update the kernel back to lollipop first before installing magisk. My concern though is, if that is not what the issue is, then restoring my kernel will keep me from being able to re-enter custom recovery to restore my data if I need to. Does that sound like it could be a plausible reason that the file will not install?
Also, if I do attempt to update the kernel in SS, should I still be able to use Odin to restore a stock rom if I have to pull the battery on my device again due to it freezing during installaion? (I've only used Odin twice, so I'm not 100% sure of it's capabilities).
Justhere4GO said:
So I did just take out the battery, and was able to get back into custom recovery and restore my backup. I tried to install magisk a few more times to no avail. (Kept saying installing but never progressed) My only thought is that maybe because Magisk is not compatible with Kitkat, I would need to update the kernel back to lollipop first before installing magisk. My concern though is, if that is not what the issue is, then restoring my kernel will keep me from being able to re-enter custom recovery to restore my data if I need to. Does that sound like it could be a plausible reason that the file will not install?
Also, if I do attempt to update the kernel in SS, should I still be able to use Odin to restore a stock rom if I have to pull the battery on my device again due to it freezing during installaion? (I've only used Odin twice, so I'm not 100% sure of it's capabilities).
Click to expand...
Click to collapse
Hows it goin? Sorry i dont pop in all the time here . Yes odin will work fine everytime as long as its all stock .but it will wipe everything again except external sd card . So if you saved a backup to internal sd it will be wiped . If you saved to ext sd it will still be there if you have to odin . And everything else will be gone also like ss and kernal flasher and all itll be pure stock again also will erase root.
Sent from my SM-G900F using XDA-Developers mobile app
---------- Post added at 11:06 AM ---------- Previous post was at 11:01 AM ----------
Everything is returnable from on these phones unless you update the bootloader past oc1. Then no root . Even if you hardbrick where it will hardly do nothing but make a sound when plug it to your computer is fixable . But it is a lengthy process and hope you two of them to be able to fix the other or do the right method and be able to flash an image to an sdcard to get you into download mode .lol unless you brick it and just sell it to me for 5 bucks lol.
Sent from my SM-G900F using XDA-Developers mobile app
captivated1971 said:
Hows it goin? Sorry i dont pop in all the time here . Yes odin will work fine everytime as long as its all stock .but it will wipe everything again except external sd card . So if you saved a backup to internal sd it will be wiped . If you saved to ext sd it will still be there if you have to odin . And everything else will be gone also like ss and kernal flasher and all itll be pure stock again also will erase root.
Sent from my SM-G900F using XDA-Developers mobile app
---------- Post added at 11:06 AM ---------- Previous post was at 11:01 AM ----------
Everything is returnable from on these phones unless you update the bootloader past oc1. Then no root . Even if you hardbrick where it will hardly do nothing but make a sound when plug it to your computer is fixable . But it is a lengthy process and hope you two of them to be able to fix the other or do the right method and be able to flash an image to an sdcard to get you into download mode .lol unless you brick it and just sell it to me for 5 bucks lol.
Sent from my SM-G900F using XDA-Developers mobile app
Click to expand...
Click to collapse
Ok, good to know. I retried booting into SS, reinstalling lollipop kernel, then installing Magisk, but it still froze without any progress. I think the problem is that I the phone is rooted, and Magisk may only be able to be installed on an unrooted phone (It is meant to replace traditional root with a systemless version that can be toggled on and off). But like you said, I cannot get into my custom recovery unless I'm rooted, so that is the predicament I currently find myself in. I actually tried to uninstall root via SuperUser, but that also froze from me when it showed it was supposed to be uninstalling. I'm not sure if that is due to my phone being rooted on KitKat, and that carrying it over into Lollipop ingrained it to the point where I cannot easily take it out. Anyways, it's looking pretty grim for me being able to install this on my device, but I think I may have to go lurking around in a Magisk forum for my next lead.
Anyways, I really appreciate your help in the matter leading me to how to run SS on Lollipop; I'm sure it will come in hand in the future!