I've had a tough Android learning curve. Before I mess up again I have a few questions. I intend to flash Scott's "Clean Rom 5.0" onto my VZW S3 and don't fully understand his instructions or flashing instructions in general and always get confused during recovery process.
I have EZ Unlocker, twrp and have downloaded Clean Rom 5.0 onto my phone and can navigate to it in GooManage and choose it.
On the installation of the ROM his page shows the following
{
"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"
}
I know that I need to unlock (I have EZ Unlocker). When I click unlock I DO NOT hear "that was easy" (yes, the volume was up) but it only visually shows an "unlocked" message.
Leaving the unlocker using the home button I then I navigate to my GooManage app and and according to the installation instructions I am supposed to reboot to recovery. Here is where I get tangled up and it's because I don't fully understand the process from here. When I reboot into recovery from GooManager it does just that and of course places me into recovery. This is the point where I almost bricked my phone last week. I do not want a repeat of that.
My options in recovery of course are:
reboot system now
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache
According Scott's guide I only do a data/factory reset within recovery. Do I leave recovery afterwards and twrp to flash the ROM?
drzcharlie said:
My options in recovery of course are:
reboot system now
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache
According Scott's guide I only do a data/factory reset within recovery. Do I leave recovery afterwards and twrp to flash the ROM?
Click to expand...
Click to collapse
After reading your post you don't have a custom recovery installed. What you're seeing is the stock recovery. TWRP is an all touch interface with maybe six to eight options (or buttons). Few questions since you're new:
1) Did you root first? If so, what tool did you use?
2) For EZ Unlock, what version did you use? You should be using v1.2
3) Once rooted AND unlocked, follow this step. You need to open GooManager, press Menu, select "install openrecoveryscript" then it will provide two prompts to install TWRP 2.3
4) Open GooManager, select "Reboot Recovery"
5) Now you should be in TWRP, notice the difference? Select "Backup" and save this either to your internal or external sd card. This backup is also known as a "Nandroid."
6) Now I need you to backup your IMEI. Link:
http://forum.xda-developers.com/showthread.php?t=1852255
7) Now that you've backed up your IMEI and performed a Nandroid, it's time to flash CleanRom 5. Reboot into recovery, select "Wipe" then "Factory Reset," next "Wipe Dalvik," then go back to the main Recovery menu and select "install" to put CleanRom in your phone.
8) Done!
Edit: Added the link.
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
After reading your post you don't have a custom recovery installed. What you're seeing is the stock recovery. TWRP is an all touch interface with maybe six to eight options (or buttons). Few questions since you're new:
1) Did you root first? If so, what tool did you use?
2) For EZ Unlock, what version did you use? You should be using v1.2
3) Once rooted AND unlocked, follow this step. You need to open GooManager, press Menu, select "install openrecoveryscript" then it will provide two prompts to install TWRP 2.3
4) Open GooManager, select "Reboot Recovery"
5) Now you should be in TWRP, notice the difference? Select "Backup" and save this either to your internal or external sd card. This backup is also known as a "Nandroid."
6) Now I need you to backup your IMEI. Link:
http://forum.xda-developers.com/showthread.php?t=1852255
Edit:
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
1. Yes, rooted first. The tool I used - http://forum.xda-developers.com/showthread.php?t=1875914
2. EZ Unlock Version - Version 1.4
3. As indicated I installed openrecoveryscript just now
4. Wow, yes I see the difference!
5. Back up completed
6. Reading the IMEI link now.
Should I download "terminal emulator" for the IMEI part?
drzcharlie said:
1. Yes, rooted first. The tool I used - http://forum.xda-developers.com/showthread.php?t=1875914
2. EZ Unlock Version - Version 1.4
3. As indicated I installed openrecoveryscript just now
4. Wow, yes I see the difference!
5. Back up completed
6. Reading the IMEI link now.
Click to expand...
Click to collapse
Awesome. I have doubts about EZ Unlock v1.4. [Edited] Use EZ Unlock v1.2, then select "Unlock" and you're all set. Download via Rootzwiki:
http://rootzwiki.com/topic/32456-app-920-ez-unlock-14-easiest-way-to-unlock-your-bootloader/
I only recommend v1.2 since we had major issues awhile back with other versions of EZ Unlock.
Should I download "terminal emulator" for the IMEI part?
Click to expand...
Click to collapse
Edit: Yea, its available in the Play Store. You really only need to do the first two IMEI backup methods contained in the thread I provided.
SlimSnoopOS said:
Awesome. I have doubts about EZ Unlock v1.4. Could you reboot your phone and tell me if the Samsung boot logo flashes by super quick? You're properly unlocked if that boot logo flashes by fast. If it does not, uninstall your current version of EZ Unlock, download v1.2, then select "Unlock" and you're all set. Download via Rootzwiki:
http://rootzwiki.com/topic/32456-app-920-ez-unlock-14-easiest-way-to-unlock-your-bootloader/
I'd like to know if v1.4 produces the quick Samsung boot logo just for my own piece of mind. I only recommend v1.2 since we had major issues awhile back with other versions of EZ Unlock.
Edit: Yea, its available in the Play Store. You really only need to do the first two IMEI backup methods contained in the thread I provided.
Click to expand...
Click to collapse
When I rebooted the phone showed "Samsung" really briefly then went into the animation screen and finished booting. Is this what you wanted to know?
drzcharlie said:
When I rebooted the phone showed "Samsung" really briefly then went into the animation screen and finished booting. Is this what you wanted to know?
Click to expand...
Click to collapse
Yea, as long as it flashes by quickly and does not linger then you are properly unlocked. If it was stock and locked, the Samsung boot logo will sit on the screen for a few seconds.
I edited step 7 of my previous post to reflect the following:
-While in TWRP, you will "Factory Reset" and "Wipe Dalvik." This Factory Reset will wipe cache and dalvik cache.
EDIT: Use EZ Unlock v1.2 please.
SlimSnoopOS said:
Yea, as long as it flashes by quickly and does not linger then you are properly unlocked. If it was stock and locked, the Samsung boot logo will sit on the screen for a few seconds.
I edited step 7 of my previous post to reflect the following:
-While in TWRP, you will "Factory Reset" and "Wipe Dalvik." This Factory Reset will wipe cache and dalvik cache.
Click to expand...
Click to collapse
Ok, I think I am unlocked properly then. It was just up for a very fleeting moment. I downloaded terminal emulator and did the commands "su" and "reboot nvbackup" the phone rebooted and I returned to android and dismissed Terminal Emulator.
So, I guess I am about to find out if I have a brick or not with my first flash eh? EDIT: I just went back to EZ Unlocker and wanted to recheck unlocked status. It showed the Device Status as "Unknown". To be sure I clicked on "Unlock" THREE different times to get the phone to show a Device Status of "Unlocked" I also still DID NOT get the "that was easy" audio message. Is this a problem? Should I find and install the 1.2 version?
drzcharlie said:
Ok, I think I am unlocked properly then. It was just up for a very fleeting moment. I downloaded terminal emulator and did the commands "su" and "reboot nvbackup" the phone rebooted and I returned to android and dismissed Terminal Emulator.
So, I guess I am about to find out if I have a brick or not with my first flash eh?
Click to expand...
Click to collapse
On second thought, I'm going to go with my gut and tell you to use EZ Unlock v1.2. I would much rather we get this right the first time. Just use v 1.2 and you will undoubtedly be unlocked.
Other than that, everything should be all set.
EDIT: I just went back to EZ Unlocker and wanted to recheck unlocked status. It showed the Device Status as "Unknown". To be sure I clicked on "Unlock" THREE different times to get the phone to show a Device Status of "Unlocked" I also still DID NOT get the "that was easy" audio message. Is this a problem? Should I find and install the 1.2 version?
Click to expand...
Click to collapse
Looks like we posted simultaneously. Yea, use EZ Unlock v1.2. I edited each of my posts so reflect this as well.
SlimSnoopOS said:
On second thought, I'm going to go with my gut and tell you to use EZ Unlock v1.2. I would much rather we get this right the first time. Just use v 1.2 and you will undoubtedly be unlocked.
Other than that, everything should be all set.
Looks like we posted simultaneously. Yea, use EZ Unlock v1.2. I edited each of my posts so reflect this as well.
Click to expand...
Click to collapse
Once downloaded which folder to I place it in?
drzcharlie said:
Once downloaded which folder to I place it in?
Click to expand...
Click to collapse
You actually just click on the apk to sideload it. No need to move it to another folder. So, go to Settings/Security/and make sure "Unknown Sources" is checked. Make sure you uninstalled your current EZ Unlock v1.4. Either using a file manager or the Touchwiz "Downloads" folder, select "EZ-Unlock12.apk" to install it. You should hear the audio "That was easy" now, I just tested it to double check.
SlimSnoopOS said:
You actually just click on the apk to sideload it. No need to move it to another folder. So, go to Settings/Security/and make sure "Unknown Sources" is checked. Make sure you uninstalled your current EZ Unlock v1.4. Either using a file manager or the Touchwiz "Downloads" folder, select "EZ-Unlock12.apk" to install it. You should hear the audio "That was easy" now, I just tested it to double check.
Click to expand...
Click to collapse
I'm having a bit of a problem locating the 1.2 apk. I went to rootzwiki but can't seem to find it doing a search. Still looking EDIT: No luck finding it. Seems 1.4 is the current and I found no earlier version. I have checked back into my version twice and the Device Status shows Unlocked at this time.
drzcharlie said:
I'm having a bit of a problem locating the 1.2 apk. I went to rootzwiki but can't seem to find it doing a search. Still looking
Click to expand...
Click to collapse
In my second response to you, I provided a link to the exact thread already bud:
http://rootzwiki.com/topic/32456-app-920-ez-unlock-14-easiest-way-to-unlock-your-bootloader/
SlimSnoopOS said:
In my second response to you, I provided a link to the exact thread already bud:
http://rootzwiki.com/topic/32456-app-920-ez-unlock-14-easiest-way-to-unlock-your-bootloader/
Click to expand...
Click to collapse
Dang...sorry about that. Thanks for being so patient with me. My bad.
drzcharlie said:
Dang...sorry about that. Thanks for being so patient with me. My bad.
Click to expand...
Click to collapse
Haha trust me, it's fine. I threw a lot of information at you at once so its actually my fault.
Once this unlocks you, you may need to perform step B from the Backup IMEI thread. Once this is done, you should now have a folder in this directory: /sdcard/synergyrom/backup
!
SlimSnoopOS said:
Haha trust me, it's fine. I threw a lot of information at you at once so its actually my fault.
Once this unlocks you, you may need to perform step B from the Backup IMEI thread. Once this is done, you should now have a folder in this directory: /sdcard/synergyrom/backup
Click to expand...
Click to collapse
Ok, we now have the audio "That was easy" phew! Going to step B from the Backup IMEI thread. EDIT: I downloaded and successfully installed the Synergy Backup HWKeys
drzcharlie said:
Ok, we now have the audio "That was easy" phew! Going to step B from the Backup IMEI thread.
Click to expand...
Click to collapse
How did it go? If that folder gets created once you flash what you need to flash, you can now flash CleanRom 5.
SlimSnoopOS said:
How did it go? If that folder gets created once you flash what you need to flash, you can now flash CleanRom 5.
Click to expand...
Click to collapse
I believe everything is installed properly. I navigated to the file on my internal SD card called "/sdcard/synergyrom/backup" and it is there. I will follow your guide now and try the flash. Fingers crossed.
drzcharlie said:
I believe everything is installed properly. I will follow your guide now and try the flash. Fingers crossed.
Click to expand...
Click to collapse
Great, just reboot into TWRP and Factory Reset/Wipe Dalvik then install CleanRom 5. You will see it change from TWRP to Aroma installer, don't be shocked because this is awesomeness at its finest.
SlimSnoopOS said:
Great, just reboot into TWRP and Factory Reset/Wipe Dalvik then install CleanRom 5. You will see it change from TWRP to Aroma installer, don't be shocked because this is awesomeness at its finest.
Click to expand...
Click to collapse
It's now installing. I will report after it's finished. EDIT: It installed properly and I am now doing a google restore and now it is finished and installed. I don't know how to thank you enough for all the help you provided and the patience you showed along the way. I am bookmarking this guide for future reference. You sir, ROCK!
Pleasure to help you out and get you on your way!
Sent from my SCH-I535 using xda app-developers app
Related
Hello
I have Stock Nexus S i9023
I just followed the guide here: http://forum.xda-developers.com/showthread.php?t=1007782 and ended up with this
I followed the steps, unlocked the phone
But when it came for transfering the SuperUser.zip file.
I rebooted my phone into fastboot and selected "Recovery"
Here is what i get after the Google logo with the UNlock icon.
{
"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"
}
and after trying to boot it up again, i got the following screen
How should i proceed ?
If i restart the phone, it goes and shows the "Welcome to Nexus S -- Touch the android to begin" screen.
I did not proceed from there and just powered off my phone until i get some help from here.
I had the same problem while I was following a similar guide. Here's the solution:
In Part4, after step 7, instead of booting into "recovery", run the below command:
fastboot flash recovery 3024v3-i9023.img
Then , once you see the recovery flashed confirmation, proceed with Part4 Step 8.
PS: I couldn't see the pics that you posted.
jithinsarath said:
I had the same problem while I was following a similar guide. Here's the solution:
In Part4, after step 7, instead of booting into "recovery", run the below command:
fastboot flash recovery 3024v3-i9023.img
Then , once you see the recovery flashed confirmation, proceed with Part4 Step 8.
PS: I couldn't see the pics that you posted.
Click to expand...
Click to collapse
Here are the images:
1st:
http://static.zooomr.com/images/10110396_806a835e04_o.png
2nd:
http://static.zooomr.com/images/10110398_c733ede677_o.png
I got stuck at Part 4, did not manage to even install Superuser.zip file.
Should i start again from Part 4 ?
I have disconnected the phone from the PC's USB cable. Should i start again at the fastboot screen and insert the usb cable and go to CMS prompt and run fastboot flash recovery 3024v3-i9023.img ?
Here is the fastboot mode screen
http://static.zooomr.com/images/10110423_922e67c1bc_o.png
I tried to go through the Step 4 again.Here is what i got
Code:
C:\nexusroot>adb push su-2.3.6.1-ef-signed.zip /SDCARD/su-2.3.6.1-ef-signed.zip
error: device not found
C:\nexusroot>
What should i do now ?
But my computer is reading the ADB device
http://static.zooomr.com/images/10110424_d2db200065_o.png
Ibn Saeed said:
I tried to go through the Step 4 again.Here is what i got
Code:
C:\nexusroot>adb push su-2.3.6.1-ef-signed.zip /SDCARD/su-2.3.6.4-ef-signed.zip
adb server is out of date. killing...
* daemon started successfully *
error: device not found
C:\nexusroot>
What should i do now ?
But my computer is reading the ADB device
http://static.zooomr.com/images/10110424_d2db200065_o.png
Click to expand...
Click to collapse
try reinstalling stock rom...
here's the step by step method..
http://caleb1783.tistory.com/13
caleb1783 said:
try reinstalling stock rom...
here's the step by step method..
http://caleb1783.tistory.com/13
Click to expand...
Click to collapse
Ill try that and report back.
Thanks
EDIT: Part of the steps are in Korean ? Or is the english translated part enough ?
Are there supposed to be links to download in your guide ? If yes, i dont see any.
Here is what i see:
Should i go for the STock Rom from here:
http://forum.xda-developers.com/showthread.php?t=731989
Guys, im confused... How should i proceed ?
Ibn Saeed said:
Here are the images:
1st:
http://static.zooomr.com/images/10110396_806a835e04_o.png
2nd:
http://static.zooomr.com/images/10110398_c733ede677_o.png
I got stuck at Part 4, did not manage to even install Superuser.zip file.
Should i start again from Part 4 ?
I have disconnected the phone from the PC's USB cable. Should i start again at the fastboot screen and insert the usb cable and go to CMS prompt and run fastboot flash recovery 3024v3-i9023.img ?
Here is the fastboot mode screen
http://static.zooomr.com/images/10110423_922e67c1bc_o.png
Click to expand...
Click to collapse
From what I understand from those pictures, you haven't flashed the recovery. Try the step 3 again .
Ibn Saeed said:
Should i go for the STock Rom from here:
http://forum.xda-developers.com/showthread.php?t=731989
Guys, im confused... How should i proceed ?
Click to expand...
Click to collapse
Please use the stock rom from below thread:
http://forum.xda-developers.com/showthread.php?t=1063664
copy the zip to root of your sdcard (connect to computer and copy)
get into bootloader mode (Vol-Up + Power)
Flash recovery (refer my earlier post)
choose recovery
in the CWM screen choose install zip from sdcard
choose the zip file in first step
install.
jithinsarath said:
Please use the stock rom from below thread:
http://forum.xda-developers.com/showthread.php?t=1063664
copy the zip to root of your sdcard (connect to computer and copy)
get into bootloader mode (Vol-Up + Power)
Flash recovery (refer my earlier post)
choose recovery
in the CWM screen choose install zip from sdcard
choose the zip file in first step
install.
Click to expand...
Click to collapse
So i should go with installing the Stock Rom or should i proceed with the Rooting guide ?
Ibn Saeed said:
So i should go with installing the Stock Rom or should i proceed with the Rooting guide ?
Click to expand...
Click to collapse
If I were you I would do this:
1. Flash CWM recovery (fastboot flash revovery <image_name>.img)
2. Goto Recovery Mode
3. Choose Install zip from SDCard
4. Select the su....zip that you pushed earlier.
5. Install.
6. Reboot.
jithinsarath said:
If I were you I would do this:
1. Flash CWM recovery (fastboot flash revovery <image_name>.img)
2. Goto Recovery Mode
3. Choose Install zip from SDCard
4. Select the su....zip that you pushed earlier.
5. Install.
6. Reboot.
Click to expand...
Click to collapse
Thanks alot jithin, it worked and the original problem has been solved.
Now i am at the "Welcome to Nexus S" screen with out ant problem.
I flashed it with su--zip file as well.
Got the "Install from SDCARD complete" message and rebooted.
Is that all, now can i start with installing any ROM ? Should i use Rom Manager to isntall new ROMS ? I want to install Bugless Beast ROM.
Should i now go into the Nexus S and setup everything up ?
Ibn Saeed said:
Thanks alot jithin, it worked and the original problem has been solved.
Now i am at the "Welcome to Nexus S" screen with out ant problem.
I flashed it with su--zip file as well.
Got the "Install from SDCARD complete" message and rebooted.
Is that all, now can i start with installing any ROM ?
Should i now go into the Nexus S and setup everything up ?
Click to expand...
Click to collapse
wow! Good to hear that. Welcome to the ROOTED world
You now have a rooted stock Rom. You can install root only apps like Titanium Backup etc..
If you wish to install a custom Rom like CM7, then you will have to follow the above procedure, in this case download the CM7 rom to the root of your sdcard and the follow the steps I gave above. Instead of SU...zip, install the rom.zip.
Let me know how it goes
Edit:
I want to install Bugless Beast ROM.
Click to expand...
Click to collapse
I thought that was Froyo. Why would you want to downgrade from Android 2.x to 1.x?
jithinsarath said:
wow! Good to hear that. Welcome to the ROOTED world
You now have a rooted stock Rom. You can install root only apps like Titanium Backup etc..
If you wish to install a custom Rom like CM7, then you will have to follow the above procedure, in this case download the CM7 rom to the root of your sdcard and the follow the steps I gave above. Instead of SU...zip, install the rom.zip.
Let me know how it goes
Click to expand...
Click to collapse
So i follow the exact method as you have outlined here earlier:
Code:
1. Flash CWM recovery (fastboot flash revovery <image_name>.img)
2. Goto Recovery Mode
3. Choose Install zip from SDCard
4. Select the su....zip that you pushed earlier.
5. Install.
6. Reboot.
Did i understand you correctly ?
I want to try Bugless Beast first.
Did i understand you correctly ?
Click to expand...
Click to collapse
yes instead of su..zip, choose your rom..zip
I want to try Bugless Beast first.
Click to expand...
Click to collapse
Bugless bease, is AFAIK Android 1.x which is known as Froyo. Your Nexus S is by default Android 2.3.X which is called Gingerbird. If you put in Bugless Beast, I believe you will be downgrading the OS version.
A good starting guide will be this link
http://forum.xda-developers.com/showthread.php?t=1067813
jithinsarath said:
yes instead of su..zip, choose your rom..zip
Bugless bease, is AFAIK Android 1.x which is known as Froyo. Your Nexus S is by default Android 2.3.X which is called Gingerbird. If you put in Bugless Beast, I believe you will be downgrading the OS version.
A good starting guide will be this link
http://forum.xda-developers.com/showthread.php?t=1067813
Click to expand...
Click to collapse
Thanks for pointing that out
How about Matrix or NSCollab, would that be compatible?
Ibn Saeed said:
Thanks for pointing that out
How about Matrix or NSCollab, would that be compatible?
Click to expand...
Click to collapse
You would benefit from some reading mate... go through the link
http://forum.xda-developers.com/showthread.php?t=1067813
and read through the whole post. Each one would have their own preferences. For instance, I run stock android 2.3.7 on netarchy kernal. read about each ROM and then decide. Compatibility can be found from the ROM's thread in XDA
Signing off, Jithin
jithinsarath said:
You would benefit from some reading mate... go through the link
http://forum.xda-developers.com/showthread.php?t=1067813
and read through the whole post. Each one would have their own preferences. For instance, I run stock android 2.3.7 on netarchy kernal. read about each ROM and then decide. Compatibility can be found from the ROM's thread in XDA
Signing off, Jithin
Click to expand...
Click to collapse
Thanks ill go through.
Just found out that Bugless Beast is for 2.3.7
GPA v19
http://www.peteralfonso.com/2011/10/download-bugless-beast-v-gpa19-android.html
Just found another way to go around my original problem
Here is a video to solve my original issue through another way.
I thought it might help someone else.
Hi everyone,
I would like to install a custom ROM onto my HTC Desire S but I can't seem to find a guide that I can understand. I do have some experience in flashing a LG Arena if that would help.
Anyway, I have unlocked my bootloader with the official HTC tool yesterday and I have a bit of a problem.
If I want to S-OFF my phone with Revolutionary, I can't select my current HBOOT version (2.00.0002 or so).
My question is; what do I do next?
Thanks in advance
Sent from my HTC Desire S using XDA App
I'm pretty sure there are other ways to s-off now. If you do a search you should find them. But I'm not even sure if you need s-off to install roms if you have unlocked the bootloader
Sent from my DesireS using xda premium
You cannot S-Off with hboot 2.00.0002 (at least there's no way I saw here). You can though downgrade the hboot to 0.98.0000 following the steps in THIS guide, then you can S-Off with Revolutionary.
Even you decide not to downgrade, you should still be able to flash ROMs following the instructions from another topic (all credits should go to Skanob):
Originally Posted by Skanob
You should be able to change your recovery without any problem if your s-off or unlocked 2.xx.xx hboot s-on.
1. Get 4ext recovery.img
2. connect phone on fastboot
3. In cmd use these command to push the recovery image:
fastboot flash recovery D:\recovery.img (<- should be directory of 4ext recovery image)
fastboot reboot-bootloader
Now you should have 4ext recovery.
Sent from my HTC Desire S using XDA App
Click to expand...
Click to collapse
Once you have 4EXT Recovery installed, just reboot in recovery and flash the ROM you want
Alright, that helps me a lot! But don't I have to root my phone before I'll be able to install a custom ROM?
EDIT // If I browse to the 4ext website, I cannot download the .img but I can download the app, although it says that it can only be used on S-OFF devices. Where can I get this image file and how do I apply it to my phone? I'm very confused right now.
EDIT // When I was browsing through my Downloads folder, I saw a folder "4EXTRecovery_v2.1.0_bravo" that contained a file "recovery.img". I've used this earlier to unlock my bootloader. Can I use this one in Recovery as well?
Sent from my HTC Desire S using XDA App
You can also just obtain temporary root using for example the zergRush exploit:
http://forum.xda-developers.com/showthread.php?t=1296916
Nilscollection said:
Alright, that helps me a lot! But don't I have to root my phone before I'll be able to install a custom ROM?...
Click to expand...
Click to collapse
No you don't need root at that point. With the method described by Skanob you can flash 4EXT Recovery and after that you can flash a rooted ROM (all ROMs here at XDA are rooted anyways)
Nilscollection said:
...
EDIT // If I browse to the 4ext website, I cannot download the .img but I can download the app, although it says that it can only be used on S-OFF devices. Where can I get this image file and how do I apply it to my phone? I'm very confused right now.
...
Click to expand...
Click to collapse
Sorry cause I was not very clear from the beginning. I don't find it right now, there was a 4EXT flashable zip somewhere from which you could extract the recovery.img file. You can download THIS file (credits goes to caelli) then perform the following:
1. Rename file to PG88IMG.ZIP and place it on the root of your sdcard
2. Boot with vol down + power
3. Wait till the image is recognized (PG88IMG.ZIP is the standard name for radio images and system will recognize and try to flash it)
4. Press vol down for YES (to flash it)
5. Reboot (it'll ask you to press vol down or up for reboot)
After having that flashed, either enter recovery via powerup with vol down pressed and choosing Recovery from boot menu or by issuing on the computer adb reboot recovery command (with phone connected with USB cable). Either ways you'll end up in recovery from where you can flash a rooted ROM of your choice.
As alternative, you can extract the recovery.img from this zip file and follow the instructions that I've give to you in the previous post.
Nilscollection said:
...
EDIT // When I was browsing through my Downloads folder, I saw a folder "4EXTRecovery_v2.1.0_bravo" that contained a file "recovery.img". I've used this earlier to unlock my bootloader. Can I use this one in Recovery as well?
Click to expand...
Click to collapse
That is the file you should find though I don't know if it'll work. The one I've linked above works for Desire S since it was used by one of the members (you can find his post in the same topic where Skanob gives the instructions).
Good luck...
Well, it's been a while and I haven't get a single step closer to installing a custom ROM.
This website says that unlocking the bootloader also makes you perm root, is that true?
Anyway, I've tried rooting my phone using this guide but as soon as I press "root", SuperOneClick freezes and I can't do anything any more.
{
"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"
}
Can someone please help me with this?
Nilscollection said:
Well, it's been a while and I haven't get a single step closer to installing a custom ROM.
This website says that unlocking the bootloader also makes you perm root, is that true?
Anyway, I've tried rooting my phone using this guide but as soon as I press "root", SuperOneClick freezes and I can't do anything any more.
Can someone please help me with this?
Click to expand...
Click to collapse
No need, download the 4ext app, start it, go to online upgrade.
Choose the latest touch version (i would recommend it, but you can choose whatever you like) and hit download only.
Copy the received recovery.img to your pc and flash it at the commandline with
Code:
fastboot flash recovery recovery.img
.
Now you have a recovery.
Download the ROM you like and flash it with recovery.
Reboot to bootloader (no normal reboot in between, it's the last option in 4ext).
Flash the boot.img from the downloaded rom zip with
Code:
fastboot flash boot boot.img
Swyped from my Desire S far away from my PC (maybe)
Tectas said:
No need, download the 4ext app, start it, go to online upgrade.
Choose the latest touch version (i would recommend it, but you can choose whatever you like) and hit download only.
Copy the received recovery.img to your pc and flash it at the commandline with
Code:
fastboot flash recovery recovery.img
.
Now you have a recovery.
Download the ROM you like and flash it with recovery.
Reboot to bootloader (no normal reboot in between, it's the last option in 4ext).
Flash the boot.img from the downloaded rom zip with
Code:
fastboot flash boot boot.img
Swyped from my Desire S far away from my PC (maybe)
Click to expand...
Click to collapse
How do I flash this exactly? Where do I put "fastboot flash boot boot.img", or are these the options when in recovery mode?
EDIT // When I try to upgrade in 4EXT, it says I have to install BusyBox first. BusyBox then says I don't have my phone rooted. What should I do now? I have the free version of 4EXT, if that helps.
Nilscollection said:
How do I flash this exactly? Where do I put "fastboot flash boot boot.img", or are these the options when in recovery mode?
EDIT // When I try to upgrade in 4EXT, it says I have to install BusyBox first. BusyBox then says I don't have my phone rooted. What should I do now? I have the free version of 4EXT, if that helps.
Click to expand...
Click to collapse
Ok, another way, download the Android sdk and instal it.
When your finished open a terminal and type adb devices, if your device is shown as combination of letters and digits your good to go, otherwise download htc sync, instal it and afterwards uninstall it (it's just for the drivers, they won't be removed at uninstall).
Download the attached recovery.img, reboot your device to bootloader and attach it to pc.
Open a terminal and execute the recovery command (make sure you are in the folder where the img file is).
Afterwards boot to recovery flash the ROM and the boot img.
Here is the recovery.img
Pls tell me when you downloaded it, because i will delete the link afterwards.
Swyped from my Desire S far away from my PC (maybe)
Tectas said:
Ok, another way, download the Android sdk and instal it.
When your finished open a terminal and type adb devices, if your device is shown as combination of letters and digits your good to go, otherwise download htc sync, instal it and afterwards uninstall it (it's just for the drivers, they won't be removed at uninstall).
Download the attached recovery.img, reboot your device to bootloader and attach it to pc.
Open a terminal and execute the recovery command (make sure you are in the folder where the img file is).
Afterwards boot to recovery flash the ROM and the boot img.
Here is the recovery.img http://db.tt/9lvfKV7n
Pls tell me when you downloaded it, because i will delete the link afterwards.
Swyped from my Desire S far away from my PC (maybe)
Click to expand...
Click to collapse
I downloaded it! I'll try it now. Thanks a lot!
EDIT // I got into 4EXT Recovery, now what? Should I put my desired ROM onto my SD-card?
Since you unlocked with htcdev, you need to flash the boot.img of your desired ROM separately. You have to do this each time you install a new ROM.
on your PC, extract the boot.img from your ROM file. put both ROM file (probably zip) and the boot.img on your Sd card. (You might create an extra folder for stuff like that on your SD card)
Get into recovery, make backup and wipe and format all. (not SD card
Then choose "flash zip from Sd card"when you're in recovery and flash the ROM first, second the boot.img.
Reboot your phone and you're done.
Edit: try endymion 3.4
Sent by my fingers to your head.
eyahl said:
Since you unlocked with htcdev, you need to flash the boot.img of your desired ROM separately. You have to do this each time you install a new ROM.
on your PC, extract the boot.img from your ROM file. put both ROM file (probably zip) and the boot.img on your Sd card. (You might create an extra folder for stuff like that on your SD card)
Get into recovery, make backup and wipe and format all. (not SD card
Then choose "flash zip from Sd card"when you're in recovery and flash the ROM first, second the boot.img.
Reboot your phone and you're done.
Edit: try endymion 3.4
Sent by my fingers to your head.
Click to expand...
Click to collapse
Alright, gonna try. Let's hope this works!
I'm pretty sure you'll be happy... Post your result here
The phone might take some minutes for the first boot. just be patient
Sent by my fingers to your head.
eyahl said:
I'm pretty sure you'll be happy... Post your result here
The phone might take some minutes for the first boot. just be patient
Sent by my fingers to your head.
Click to expand...
Click to collapse
Could that be like +5 minutes?
Nilscollection said:
Could that be like +5 minutes?
Click to expand...
Click to collapse
Yep. For me it took once about fifteen minutes.
Just.be.patient.
Sent by my fingers to your head.
eyahl said:
Yep. For me it took once about fifteen minutes.
Just.be.patient.
Sent by my fingers to your head.
Click to expand...
Click to collapse
Nope, just had to flash the boot.img as well! ICS works all great now, I love it!
Thank you SO MUCH for your time / effort, all of you
Nilscollection said:
Nope, just had to flash the boot.img as well! ICS works all great now, I love it!
Thank you SO MUCH for your time / effort, all of you
Click to expand...
Click to collapse
well, we told you very often to do so:
Tectas said:
Download the ROM you like and flash it with recovery.
Reboot to bootloader (no normal reboot in between, it's the last option in 4ext).
Flash the boot.img from the downloaded rom
Click to expand...
Click to collapse
Tectas said:
Afterwards boot to recovery flash the ROM and the boot img.
Click to expand...
Click to collapse
eyahl said:
flash the ROM first, second the boot.img.
Click to expand...
Click to collapse
and its written in so many guides...
anyways, always happy to help, have fun with flashing roms, and dont forget to backup everytime...
eyahl said:
well, we told you very often to do so:
and its written in so many guides...
anyways, always happy to help, have fun with flashing roms, and dont forget to backup everytime...
Click to expand...
Click to collapse
Indeed, I guess I skipped it in excitement. But hey, it worked in the end!
I'm really glad you all helped me!
I wrote this guide do to the general lack of information for users about the Jellybean update. This guide is basic in nature and will provide you with all the tools and links you need to update from an ICS based ROM to the official JB ROM then re-root or prepare for custom ROM.
If you already have the Official JB Update simply unlock it and proceed to Section #2. This guide was intially intended for those who cannot update because of Asus stupid lock out program once you unlock.
Warning
I have tested this guide on my device multiple times and never have one single issue. I cannot say it will work perfect for you! I am not responsible for anything that goes wrong including but not limited to; A $500 brick! The economy imploding worse, Nuclear war, End of the world on 12/12/12!
Pre-requisites
Unlocked bootloader
Custom Recovery
Any version of TF700T
Windows 7 or Windows 8 PC
General Overview
Flash Asus JB update
Flash TWRP 2.2.3
Flash SuperSU or Custom ROM
Profit!
Please do not be afraid to ask for help!
This guide was written for people who need help. I didint write it for myself because I already know how to do it, lol
Donations gratefully accepted but never expected!
Please hit Thanks and Rate the thread 5 Stars
Click to expand...
Click to collapse
-Scott
Section 1 - Flash Asus JB update
Obtain the appropriate Jellybean update from the Asus Support Site HERE
Go to Downloads and pick the local / region specific update file for your device. For the intent of this guide I will focus on the US Based variant but all other devices will follow the exact same steps.
{
"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"
}
After you download the Jellybean update you must extract the zip file in the zip (I dont know why they did this!). The name of the first zip file will be "US_epad_user_10_4_4_16_UpdateLauncher.zip"
The zip file inside of that will be "US_epad-user-10.4.4.16.zip" This is the file we will flash to update to JB!
To do this open the first zip file with your zip [rogram of choice, (as you can see I use 7zip) and pull out the only other zip file in there (US_epad-user-10.4.4.16.zip).
Once you have that file copy it to you internal SD card. Although, untested, external SD should work too.
Now.... Reboot to recovery. To do this power down the device, and then Hold Volume Down and then press power untill you get a menu that says press XX key to boot to recvoery.
Once in recovery you MUST wipe data before you continue!
Now flash the ROM file you just copied like it was a plain old fashioned custom ROM or Root.zip. Just select it and flash!
Once the flash is done reboot. Dont be scared... This will take a LONG time... Maybe in upwards of 3 to 5 minutes. This is normal. Its completely rebuilding the device!
Once the device is all booted up and you are at your desktop we can proceed to Section 2.
Section 2 - Flash TWRP 2.2.2.3
First we need to obtain TWRPREcovery. You are free to use any version you want, including ClockworkMod (although I highly discourage CWM and recomend TWRP).
You can find TWRP HERE. Remember I recommend the 2.2.2.3 version. 2.3.0.0 gave me some issues.
Now that you have the file download you need to rename it to "recovery.blob" for use with my tool!
Now download the attached tool and unzip it. It contains the fastboot and ADB files you will need to flash the recovery.
Next place the recovery.blob in the folder
Turn on USB Degging in the developer menu of the device. This is very important otherwise you will be just sitting there forever, lol
Now initiate the "Recovery Install Tool.bat" file. This will reboot you to bootloader and flash the recovery for you ;c)
Done!
Section 3 - Flash SuperSU or Custom ROM
Needless to say I am partial to custom ROMS ;c) But I know some may be content with just flashing root so I will show you how to obtain the correct root file and or ROM and give a brief over view on how to flash them. This section will be pretty routine and will not contain a lot of new info for most of you!
Obtain my favorite root app, SuperSU, from HERE
Copy to storage
Reboot to recovery
Flash and Be rooted!
Same steps for a custom ROM. The best Custom ROM can be found HERE! ;c)
Section 4 - Thanks!
Thanks to Dess_troy for making TWRP for our devices!
Thanks to Chainfire for the root app!
Thanks to all the Developers on XDA that have taught me (in one way or another) everything I know!
Special Thanks to all the CleanROM users who have inspired me to push CleanROM to be the premier custom ROM for your Android Device!
Please feel free to rebuild this for the Linux or Mac platform and re-distrubute!
So, the very first step is unlocking the bootloader, correct?
Sent from my S2 Skyrocket using XDA app
scrosler said:
Pre-requisites
Unlocked bootloader
Custom Recovery
Any version of TF700T
-Scott
Click to expand...
Click to collapse
A number of people have asked and I have usually replied that it is possible to use the Asus provided UnLock tool - the one on the website that says is only compatible with ICS - with a tablet that has been updated to JB.
In short the Unlock tool works in Jellybean!
You might want to add this as an addendum to your original post.
Cheers,
Eric
i apologize for my beligerant question but if i want to try the new cwm touch recovery, do i just rename it to recovery.blob? when i downloaded it it was the usual iso. when renamed it didnt change anything so i dont wanna brick my tab. figured id ask first. thanks for the awesome walk through tho man. i really apreciate it. loving your roms. have 2.0 downloaded already. also can you pm the link to your tf300 kernel you used? i need to show off some high quadrant numbers lol
Confused...
How do I get a custom recovery on my tablet before this whole process? I've read thru some threads, do I need to be rooted first on ICS before starting this process of updating to JB? I'm not getting the official ASUS JB OTA...I've checked for the update about 500 times, I'm just not getting it.
At this point, I have an unlocked but unrooted, and wiped stock TF700T on ICS. Whats my next step?
BlastTyrantKM said:
So, the very first step is unlocking the bootloader, correct?
Sent from my S2 Skyrocket using XDA app
Click to expand...
Click to collapse
BlastTyrantKM said:
How do I get a custom recovery on my tablet before this whole process? I've read thru some threads, do I need to be rooted first on ICS before starting this process of updating to JB? I'm not getting the official ASUS JB OTA...I've checked for the update about 500 times, I'm just not getting it.
At this point, I have an unlocked but unrooted, and wiped stock TF700T on ICS. Whats my next step?
Click to expand...
Click to collapse
Click to expand...
Click to collapse
This guide is for people who have already unlocked there device any may have had a custom ROM installed pre-JB.
You fall into a unique and rather off situation. I have never heard of some one not getting the OTA.
You could follow these steps but as a pre-step...
Download and unlock with the Asus unlock tool. Its on the same download page.
Download an ICS based recovery and use that in in place of the one noted for now. And then just start at Section 2. Then start back over at Section 1.
Basically we will put a recovery on your device in Section 2. Then start over at step 1 by applying the JB build then put a recovery back on, as it gets wiped off by Asus builds and your all set.
So I got the OTA JB update from Asus. I unlocked the boot loader using the Asus app. I downloaded and extracted US_epad-user-10.4.4.16.zip then threw it on the insternal SD card ( /storage/sdcard0 ). I rebooted with the volume key press and selected recovery. It gave me a message saying "booting recovery kernel". The next thing I see is an android on his back with a red exclamation sign.
What am I doing wrong?
beowolfschaefer said:
So I got the OTA JB update from Asus. I unlocked the boot loader using the Asus app. I downloaded and extracted US_epad-user-10.4.4.16.zip then threw it on the insternal SD card ( /storage/sdcard0 ). I rebooted with the volume key press and selected recovery. It gave me a message saying "booting recovery kernel". The next thing I see is an android on his back with a red exclamation sign.
What am I doing wrong?
Click to expand...
Click to collapse
The stock recovery will only flash firmware zips with a certain name. Rename the zip to EP201_768_SDUPDATE.ZIP and try again.
I upgraded to jb firmware and lost root. My 700T is unlocked. I thought I followed the procedure correctly but I did not get the message correct message when I ran the program. My device is not rooted. Can you tell me what I might be doing wrong.
yes you lose root. this will make your tf700 like the factory jellybean firmware which is not rooted. go back to op and keep reading. each section builds on the previous. first get the jellybean firmware. im still playing with mine stock its so damn smooth. then you flash a custom recovery using his tool. then you flash the zip which gives you root. then i would make a back up so you can always get back to that point. then you can look into custom roms like scotts sweet clean rom for tf700 series
joseph473 said:
I upgraded to jb firmware and lost root. My 700T is unlocked. I thought I followed the procedure correctly but I did not get the message correct message when I ran the program. My device is not rooted. Can you tell me what I might be doing wrong.
Click to expand...
Click to collapse
beowolfschaefer said:
So I got the OTA JB update from Asus. I unlocked the boot loader using the Asus app. I downloaded and extracted US_epad-user-10.4.4.16.zip then threw it on the insternal SD card ( /storage/sdcard0 ). I rebooted with the volume key press and selected recovery. It gave me a message saying "booting recovery kernel". The next thing I see is an android on his back with a red exclamation sign.
What am I doing wrong?
Click to expand...
Click to collapse
If you have the JB Update why ware you trying to install it again? Proceed to section #2. You just need the Recovery and the Root portion. Skip step 1.
joseph473 said:
I upgraded to jb firmware and lost root. My 700T is unlocked. I thought I followed the procedure correctly but I did not get the message correct message when I ran the program. My device is not rooted. Can you tell me what I might be doing wrong.
Click to expand...
Click to collapse
To me it looks like you are trying to run the batch file without extracting the contents.
Thank you for this guide! Although it took me some time to understand it as I was on non-rooted/locked JB stock rom.
---------- Post added at 01:34 PM ---------- Previous post was at 01:29 PM ----------
scrosler said:
If you have the JB Update why ware you trying to install it again? Proceed to section #2. You just need the Recovery and the Root portion. Skip step 1.
Click to expand...
Click to collapse
I actually had similar problem as this guy. I was already on JB and the guide is made for people that are on ICS.
scrosler said:
To me it looks like you are trying to run the batch file without extracting the contents.
Click to expand...
Click to collapse
I am using a borrowed PC. I am a Mac user so forgive my ignorance. But when I look at the folder with Scott's Tool in it it looks like everything is extracted.
scrosler said:
If you have the JB Update why ware you trying to install it again? Proceed to section #2. You just need the Recovery and the Root portion. Skip step 1.
Click to expand...
Click to collapse
I actually tried this last night with no luck. I guess it was something funny with my desktop in that it couldn't connect using fast boot. Anyway I brought it in to work and ran it here and everything is fine. I am going to throw your stock/root rom on it now. Thanks for your help!
CWM-SuperSU-v0.96.zip
Hello,
thanks a lot for the guide, it is really clear and detailed.
My question is something I did not find on the previous question and it is more a double check to be sure I am not doing something I should not.
You say to install SU with the package copied on the internal SD, and you added a link to the SU thread. in this thread, the only SU as a package you can find is CWM-SuperSU-v0.96.zip, as it is CWM, will it work if I install it with TWRP? or there is special settings in this package that will not be recognised by TWRP?
Thanks in advance for your help
Regards
Have a rooted Verizon HTC One M8. Didn't have a custom rom on it. I was just happy with not having ads, and being able to have access to files on the phone. The one problem that I kept having was it constantly telling me that I needed to do an update. I tried freezing Update files in Titanium Backup, but I would still see the notifications. Followed advice elsewhere on the internet, and tried to Force Close Download Manager. I then went into TWRP and wiped Cache and Dalvic Cache. Now, it's completely stuck on the white HTC screen on bootup. I can boot into Recovery, but I'm not sure what to do to get the phone back to working condition.
Please help! This is not the Sunday afternoon that I was envisioning today. I just wanted the update notifications to stop.
SmoovySmoov said:
Have a rooted Verizon HTC One M8. Didn't have a custom rom on it. I was just happy with not having ads, and being able to have access to files on the phone. The one problem that I kept having was it constantly telling me that I needed to do an update. I tried freezing Update files in Titanium Backup, but I would still see the notifications. Followed advice elsewhere on the internet, and tried to Force Close Download Manager. I then went into TWRP and wiped Cache and Dalvic Cache. Now, it's completely stuck on the white HTC screen on bootup. I can boot into Recovery, but I'm not sure what to do to get the phone back to working condition.
Please help! This is not the Sunday afternoon that I was envisioning today. I just wanted the update notifications to stop.
Click to expand...
Click to collapse
Were You temp rooted or did you s off?
dottat said:
Were You temp rooted or did you s off?
Click to expand...
Click to collapse
I am S-Off'd.
SmoovySmoov said:
I am S-Off'd.
Click to expand...
Click to collapse
I have two solutions. One that wipes and one that doesn't. The one that doesn't you will need to reflash twrp and a su.zip when done but it's easy. Sound ok?
Run the exe on the first post here. Make sure your phone is in fastboot mode.
http://forum.xda-developers.com/showthread.php?t=2883845
Official RUU 3.28.605.4 EXE/ZIP
dottat said:
I have two solutions. One that wipes and one that doesn't. The one that doesn't you will need to reflash twrp and a su.zip when done but it's easy. Sound ok?
Run the exe on the first post here. Make sure your phone is in fastboot mode.
http://forum.xda-developers.com/showthread.php?t=2883845
Official RUU 3.28.605.4 EXE/ZIP
Click to expand...
Click to collapse
So this would take me back to not rooted, or am I reading that incorrectly? If so, is there no way to stay rooted, just to reflash stock rom?
Yes. But you will still get nagged to update too. If you want to simply flash stock then flash this one via recovery. http://forum.xda-developers.com/showthread.php?t=2914922
[ROM][10/22/14] - Stock Rooted 4.4.4 - OTA 3.28.605.4 - W/P - BusyBox and Root - UP!
Rerooting the phone after updating using the exe is easy to do though
SmoovySmoov said:
So this would take me back to not rooted, or am I reading that incorrectly? If so, is there no way to stay rooted, just to reflash stock rom?
Click to expand...
Click to collapse
dottat said:
Yes. But you will still get nagged to update too. If you want to simply flash stock then flash this one via recovery. http://forum.xda-developers.com/showthread.php?t=2914922
[ROM][10/22/14] - Stock Rooted 4.4.4 - OTA 3.28.605.4 - W/P - BusyBox and Root - UP!
Rerooting the phone after updating using the exe is easy to do though
Click to expand...
Click to collapse
So, I have your original method downloading. Are you saying that after I flash that, and then reroot it (which I will need help with as well, since I used Sunshine before), I won't get nagged to do an update all the time?
SmoovySmoov said:
So, I have your original method downloading. Are you saying that after I flash that, and then reroot it (which I will need help with as well, since I used Sunshine before), I won't get nagged to do an update all the time?
Click to expand...
Click to collapse
You will be up to date. When you flash twrp You can grab the latest su.zip from here http://download.chainfire.eu/supersu
Wipe cache when flashing su.
Sunshine was an exploit to gain s off. Not root. S off means you can flash whatever you want. In this case, root is just an app you flash.
dottat said:
You will be up to date. When you flash twrp You can grab the latest su.zip from here http://download.chainfire.eu/supersu
Wipe cache when flashing su.
Sunshine was an exploit to gain s off. Not root. S off means you can flash whatever you want. In this case, root is just an app you flash.
Click to expand...
Click to collapse
Still have about 15 minutes on the download. Sorry for all the questions, but I want to make sure I get what all you are saying.
1) Once the download finishes, I run the program and follow the prompts. This will return me to stock, not rooted.
2) I then need to flash SuperSU using TWRP. This will get me rooted again? Where do I place the .zip on my external SD card? I've had problems with TWRP in that I never see anything that I can install when I go to the Install screen there. It just says TWRP. No files. I try to navigate to the external SD, but there's never anything there that I can install.
SmoovySmoov said:
Still have about 15 minutes on the download. Sorry for all the questions, but I want to make sure I get what all you are saying.
1) Once the download finishes, I run the program and follow the prompts. This will return me to stock, not rooted.
2) I then need to flash SuperSU using TWRP. This will get me rooted again? Where do I place the .zip on my external SD card? I've had problems with TWRP in that I never see anything that I can install when I go to the Install screen there. It just says TWRP. No files. I try to navigate to the external SD, but there's never anything there that I can install.
Click to expand...
Click to collapse
You have a working fastboot/adbsetup? You only need fastboot for this exercise to work.
---------- Post added at 03:19 PM ---------- Previous post was at 03:09 PM ----------
Here's a quick how to..for after you run that exe.
Take the su.zip to your internal storage.
Download twrp 2.8.1.0 here
http://techerrata.com/browse/twrp2/m8_wlv
Download fastboot/adb here
https://www.androidfilehost.com/?fid=23501681358559711
Extract the fastboot/adb zip. Copy the new twrp image into this new folder. Open the newly extracted folder and while holding the shift button right click on your mouse. Select open command prompt here.
Put phone in fastboot mode and connect to your pc. Run the following command to flash twrp.
Fastboot flash recovery openrecovery-twrp-2.8.1.0-m8_wlv.img
After this completes select boot loader on the phone screen. Then select recovery. Choose wipe and select advanced. Only select cache and wipe. When done hit the home button icon at the bottom. Then click install. Scroll down and find your su.zip and flash it. Reboot when done
dottat said:
You have a working fastboot/adbsetup? You only need fastboot for this exercise to work.
Click to expand...
Click to collapse
Not 100% on that one. Are you meaning having adb set up on my computer? If so, no. I tried once before, and couldn't figure out what I was doing. I achieved root by using Sunshine to S-Off, and then Klingo One Click Root Method.
SmoovySmoov said:
Not 100% on that one. Are you meaning having adb set up on my computer? If so, no. I tried once before, and couldn't figure out what I was doing. I achieved root by using Sunshine to S-Off, and then Klingo One Click Root Method.
Click to expand...
Click to collapse
Edited my last post
dottat said:
Edited my last post
Click to expand...
Click to collapse
It keeps saying that the Update Utility cannot see my phone.
SmoovySmoov said:
It keeps saying that the Update Utility cannot see my phone.
Click to expand...
Click to collapse
Can you install team viewer and pm me the details to screen share.
dottat said:
Can you install team viewer and pm me the details to screen share.
Click to expand...
Click to collapse
I wasn't in fastboot. It's updating now.
SmoovySmoov said:
I wasn't in fastboot. It's updating now.
Click to expand...
Click to collapse
? good
dottat said:
You have a working fastboot/adbsetup? You only need fastboot for this exercise to work.
---------- Post added at 03:19 PM ---------- Previous post was at 03:09 PM ----------
Here's a quick how to..for after you run that exe.
Take the su.zip to your internal storage.
Download twrp 2.8.1.0 here
http://techerrata.com/browse/twrp2/m8_wlv
Download fastboot/adb here
https://www.androidfilehost.com/?fid=23501681358559711
Extract the fastboot/adb zip. Copy the new twrp image into this new folder. Open the newly extracted folder and while holding the shift button right click on your mouse. Select open command prompt here.
Put phone in fastboot mode and connect to your pc. Run the following command to flash twrp.
Fastboot flash recovery openrecovery-twrp-2.8.1.0-m8_wlv.img
After this completes select boot loader on the phone screen. Then select recovery. Choose wipe and select advanced. Only select cache and wipe. When done hit the home button icon at the bottom. Then click install. Scroll down and find your su.zip and flash it. Reboot when done
Click to expand...
Click to collapse
Okay, so I completed the first part, and am back to not rooted. Not completely following your instructions above, though. I extracted the fastboot/adb file to my Desktop. It's just those files. There's no folder. Are you saying I just need to create a folder with them in it, and then add the twrp file to it?
SmoovySmoov said:
Okay, so I completed the first part, and am back to not rooted. Not completely following your instructions above, though. I extracted the fastboot/adb file to my Desktop. It's just those files. There's no folder. Are you saying I just need to create a folder with them in it, and then add the twrp file to it?
Click to expand...
Click to collapse
Unzip the rar file and then continue
Edit...You should have extracted to a folder not current directory. You want those files within a folder and then yes place the twrp in there too
Once you run through this all it will make better sense going forward.
dottat said:
Unzip the rar file and then continue
Edit...You should have extracted to a folder not current directory. You want those files within a folder and then yes place the twrp in there too
Once you run through this all it will make better sense going forward.
Click to expand...
Click to collapse
Feel like I'm close, but it's not 100% yet.
Got the phone back to operational. Went looking in apps, and SuperSU was not listed. Everything says that I'm rooted, but it was not there. Googled SuperSU apk, and followed a link to download it via Google Play. Redownloaded it, and when opened, it says "There is no SU binary installed, and SuperSU cannot install it." Also, the damn update that started this whole mess just popped up on the screen again.
SmoovySmoov said:
Feel like I'm close, but it's not 100% yet.
Got the phone back to operational. Went looking in apps, and SuperSU was not listed. Everything says that I'm rooted, but it was not there. Googled SuperSU apk, and followed a link to download it via Google Play. Redownloaded it, and when opened, it says "There is no SU binary installed, and SuperSU cannot install it." Also, the damn update that started this whole mess just popped up on the screen again.
Click to expand...
Click to collapse
Did you flash the su.zip in recovery?
Also, since you wiped cache the ota should be gone. Go to settings and chose app manager. Slide over to the right until you see all at the top. Hit the magnifying glass and search for htcdm. When it finds it click on it. Force stop and clear data for it.
Also, since you are running stock with just a few tweaks of your own, you may want to flash santods ota killer zip. It would prevent what started this off in the first place and remove the leftover prompt in the same shot.
https://www.androidfilehost.com/?fid=23329332407587434
UPDATE: Hey guys! Easiest way to update to the new Nougat firmware & reroot with SuperSU currently is to install this debloated rom I just made. It does it all in one flash.
https://forum.xda-developers.com/showthread.php?p=72098300
----------
No doubt, there's already a ton of posts about this, but I decided to make this guide anyway for those who maybe prefer SuperSU over Magisk and just want to update Android and reroot quickly and easily. This method will get you rooted before you even boot up the Nougat firmware for the first time. Just be sure, of course, to BACKUP ALL YOUR DEVICE DATA BEFORE DOING THIS.
NOTE: If you use the Samsung Health app then be sure to read this post through to the end.
DOWNLOADS:(click to open links)
Odin
Nougat stock firmware
TWRP
SuperSU Nougat Fix Zip(Do not use the official SuperSU zip. It will result in "stuck at creating image" error.)
no-verity-opt-encrypt(Attached below.)
1) Install & open Odin. Uncheck "Auto Reboot" in the Options tab. Then follow the instructions pictured below to flash the firmware package to your device.
{
"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"
}
2) Once it's finished recheck "Auto Reboot" and flash TWRP the same way. IMMEDIATELY AFTER IT REBOOTS and the screen goes blank, hold Volume Up, Home key and power buttons to boot into TWRP. (Otherwise it will launch Android setup.)
NOTE: If for whatever reason the firmware and TWRP won't flash back to back then just reboot into Download mode again and finish with flashing TWRP. It seems that will happen on occasion on more recent versions of Odin.
3) Once TWRP loads, connect your device and drag and drop the "no-verity" and "supersu" files(from above) to the root of your sdcard.
4) Go to "Install" and select the "no-verity-opt-encrypt" file. Then click the "Add more Zips" button and add the SuperSU file as well and swipe to flash.
5) Reboot into Android and complete device setup.
You should now be rooted with Nougat and SuperSU!
BONUS:
Easy way to fix the Samsung Health "device has been compromised" or "can't be opened on a rooted device" errors.
1) Download an app from the Play Store called "BuildProp Editor".
2) Search for "ro.config.tima".
3) Click on it and change the "1" to a "O".
4) Reboot device.
If this helped you, then please consider hitting the "Thanks" or Donate button. Thank you!
bogarty said:
No doubt, there's already a ton of posts about this, but I decided to make this guide anyway for those who maybe prefer SuperSU over Magisk and just want to update Android and reroot quickly and easily. This method will get you rooted before you even boot up the Nougat firmware for the first time. Just be sure, of course, to BACKUP ALL YOUR DEVICE DATA BEFORE DOING THIS.
NOTE: If you use the Samsung Health app then be sure to read this post through to the end.
DOWNLOADSclick to open links)
Odin
Nougat stock firmware
TWRP
SuperSU Nougat Fix Zip(Do not use the official SuperSU zip. It will result in "stuck at creating image" error.)
no-verity-opt-encrypt(Attached below.)
1) Install & open Odin. Uncheck "Auto Reboot" in the Options tab. Then follow the instructions pictured below to flash the firmware package to your device.



2) Once it's finished recheck "Auto Reboot" and flash TWRP the same way. IMMEDIATELY AFTER IT REBOOTS and the screen goes blank, hold Volume Up, Home key and power buttons to boot into TWRP. (Otherwise it will launch Android setup.)
3) Once TWRP loads, you should do a full "advanced wipe" of everything(except the internal and usb storages) before moving forward. Afterwards, connect your device and drag and drop the "no-verity" and "supersu" files(from above) to the root of your sdcard.
4) Go to "Install" and select the "no-verity-opt-encrypt" file. Then click the "Add more Zips" button and add the SuperSU file as well and swipe to flash.
5) Reboot into Android and complete device setup.
You should now be rooted with Nougat and SuperSU!
BONUS:
Easy way to fix the Samsung Health"device has been compromised" or "can't be opened on a rooted device" errors.


1) Download an app from the Play Store called "BuildProp Editor".
2) Search for "ro.config.tima".
3) Click on it and change the "1" to a "O".

4) Reboot device.
If I've helped you, then please consider hitting the "Thanks" button. Thank you!

[/HIDE]
2) Once it's finished recheck "Auto Reboot" and flash TWRP the same way. IMMEDIATELY AFTER IT REBOOTS and the screen goes blank, hold Volume Up, Home key and power buttons to boot into TWRP. (Otherwise it will launch Android setup.)
3) Once TWRP loads, you should do a full "advanced wipe" of everything(except the internal and usb storages) before moving forward. Afterwards, connect your device and drag and drop the "no-verity" and "supersu" files(from above) to the root of your sdcard.
4) Go to "Install" and select the "no-verity-opt-encrypt" file. Then click the "Add more Zips" button and add the SuperSU file as well and swipe to flash.
5) Reboot into Android and complete device setup.
You should now be rooted with Nougat and SuperSU!
BONUS:
Easy way to fix the Samsung Health"device has been compromised" or "can't be opened on a rooted device" errors.
2) Once it's finished recheck "Auto Reboot" and flash TWRP the same way. IMMEDIATELY AFTER IT REBOOTS and the screen goes blank, hold Volume Up, Home key and power buttons to boot into TWRP. (Otherwise it will launch Android setup.)
3) Once TWRP loads, you should do a full "advanced wipe" of everything(except the internal and usb storages) before moving forward. Afterwards, connect your device and drag and drop the "no-verity" and "supersu" files(from above) to the root of your sdcard.
4) Go to "Install" and select the "no-verity-opt-encrypt" file. Then click the "Add more Zips" button and add the SuperSU file as well and swipe to flash.
5) Reboot into Android and complete device setup.
You should now be rooted with Nougat and SuperSU!
BONUS:
Easy way to fix the Samsung Health"device has been compromised" or "can't be opened on a rooted device" errors.

1) Download an app from the Play Store called "BuildProp Editor".
2) Search for "ro.config.tima".
3) Click on it and change the "1" to a "O".
4) Reboot device.
If I've helped you, then please consider hitting the "Thanks" button. Thank you!

Click to expand...
Click to collapse
Nice guide!
Sent from my SM-N920T using XDA Labs
rmarinella said:
Nice guide!
Click to expand...
Click to collapse
Thank you! Holy OP quote though. Haha!
Any problems with Samsung Account after root? Mine works fine unrooted but won't stay logged in after. Curiosity and what not....
DrRootso said:
Any problems with Samsung Account after root? Mine works fine unrooted but won't stay logged in after. Curiosity and what not....
Click to expand...
Click to collapse
I had same problem but it fixed....i am deodexed rooted with magisk clean installed and setup with mobile data thats all i did and works fine for now
Sent from my T-Mobile Samsung Galaxy Note5 using XDA Labs
odin
when I try to connect my phone to odin its not reading the phone where it says added. anyone else experience this in this version of odin? I have usb debugging checked, plus oem checked. I have also tried different usb cables and other odin applications.......weird.
skills2015 said:
when I try to connect my phone to odin its not reading the phone where it says added. anyone else experience this in this version of odin? I have usb debugging checked, plus oem checked. I have also tried different usb cables and other odin applications.......weird.
Click to expand...
Click to collapse
Try to download the drivers here:
http://org.downloadcenter.samsung.c...G_USB_Driver_for_Mobile_Phones_v1.5.45.00.exe
DrRootso said:
Any problems with Samsung Account after root? Mine works fine unrooted but won't stay logged in after. Curiosity and what not....
Click to expand...
Click to collapse
I have not experienced any issues myself. Everything should work fine on stock firmware. The only problem I found was with Samsung Health not working with root, but I provided the fix for that in the OP. Maybe try removing the account in Settings and adding it back manually.
bogarty said:
I have not experienced any issues myself. Everything should work fine on stock firmware. The only problem I found was with Samsung Health not working with root, but I provided the fix for that in the OP. Maybe try removing the account in Settings and adding it back manually.
Click to expand...
Click to collapse
I dont think it will let him added it will say session expired even after entering it again....he might have to factory reset and setup again or setup via mobile data
Sent from my T-Mobile Samsung Galaxy Note5 using XDA Labs
JonathanRAZ said:
I dont think it will let him added it will say session expired even after entering it again....he might have to factory reset and setup again or setup via mobile data
Click to expand...
Click to collapse
Strange I haven't seen this issue. Is it a Magisk problem? I signed into Samsung Account during initial device setup and its been working fine.
bogarty said:
Strange I haven't seen this issue. Is it a Magisk problem? I signed into Samsung Account during initial device setup and its been working fine.
Click to expand...
Click to collapse
No is not magisk i have it installed and all is fine on this side.....it can be on setup the problem the first time i had i setup with wifi and after changing to mobile dta had session expired....i dont know if is that or not but since i have setup via mobile data it works fine no problems
Sent from my T-Mobile Samsung Galaxy Note5 using XDA Labs
JonathanRAZ said:
No is not magisk i have it installed and all is fine on this side.....it can be on setup the problem the first time i had i setup with wifi and after changing to mobile dta had session expired....i dont know if is that or not but since i have setup via mobile data it works fine no problems
Click to expand...
Click to collapse
Weren't you using that unrooted rom from the other thread? Maybe there was a problem there.
bogarty said:
Weren't you using that unrooted rom from the other thread? Maybe there was a problem there.
Click to expand...
Click to collapse
No i was stock rooted with magisk......then was on my own deodexed rom.....then now i am on that unrooted rom.....and later on will be on a new one i will make after installing windows 10
Sent from my T-Mobile Samsung Galaxy Note5 using XDA Labs
thanks for this. sadly volte isnt working for me so ill be using the stock tweaked rom, hopefully it works. but using this root method. thanks again!
justin94 said:
thanks for this. sadly volte isnt working for me so ill be using the stock tweaked rom, hopefully it works. but using this root method. thanks again!
Click to expand...
Click to collapse
Still don't get how anyone could be having any issues with any Android features. If you're flashing the stock firmware, everything should work. VoLTE seems to be working fine for me.
bad flash probably. but this root method worked on that stock tweaked rom. everything is working.
Anyone know the differences between magisk and supersu? Pros and cons for both.. I was thinking about doing the magisk root but I've always rooted with supersu.
Sent from my SM-N920T using Tapatalk
I followed the steps but it doesn't seem to be working well for me. I can flash the stock FW fine but when I try to flash TWRP odin doesn't go through the process. I shut down the phone and went back into download mode and that allowed me to flash TWRP. I booted immediately into TWRP and flashed the two files (no-verity & Nougat Root SU - no Kernel ) from the links provided. I performed the wipe as suggested before flashing the two files in TWRP. When I reboot the phone I'm greeted with the message Kernel not seandriod enforcing. Is it because I'm using the wrong Root SU file?
Maximus2102 said:
I followed the steps but it doesn't seem to be working well for me. I can flash the stock FW fine but when I try to flash TWRP odin doesn't go through the process. I shut down the phone and went back into download mode and that allowed me to flash TWRP. I booted immediately into TWRP and flashed the two files (no-verity & Nougat Root SU - no Kernel ) from the links provided. I performed the wipe as suggested before flashing the two files in TWRP. When I reboot the phone I'm greeted with the message Kernel not seandriod enforcing. Is it because I'm using the wrong Root SU file?
Click to expand...
Click to collapse
Nevermind. I was able to get passed it but I flashed Magisk instead. I'm up and running with Rooted Nougat.
geeshiet said:
Anyone know the differences between magisk and supersu? Pros and cons for both.. I was thinking about doing the magisk root but I've always rooted with supersu.
Click to expand...
Click to collapse
I made this tutorial because I've always felt SuperSU to be more reliable personally. The last rom I had forced you to use Magisk and I didn't like it. Magisk just kind of seems like too bulky of a package for me. Too much extra stuff, going on and sometimes(a couple versions back) the package updates can be faulty and even cause device reboots. SuperSU, to me, just seems lighter and more reliable and concise.
Maximus2102 said:
when I try to flash TWRP odin doesn't go through the process.* I shut down the phone and went back into download mode and that allowed me to* flash TWRP.
Click to expand...
Click to collapse
Rebooting is fine, though there shouldn't be a problem flashing both in a row. It does take about 10-20 seconds or so sometimes before it will let you load the next one.
Maximus2102 said:
When I reboot the phone I'm greeted with the message Kernel not seandriod enforcing.* Is it because I'm using the wrong Root SU file?
Click to expand...
Click to collapse
The kernel not seandroid enforcing message has never been anything to worry about. It's just Samsung's of way of telling you that the kernel has been modified to allow for root. You shouldn't have that message though with SuperSU, as SuperSU uses a systemless root method. So if you're seeing that, then you've done something additional that's modified the kernel. What "Root SU file" did you mean? Flashing the SuperSU zip roots the device. No extra files are needed.
Maximus2102 said:
Nevermind. I was able to get passed it but I flashed Magisk instead. I'm up and running with Rooted Nougat.
Click to expand...
Click to collapse
You got rid of SuperSU because you saw "kernel not seandroid enforcing" message? Again that message is nothing to be concerned about. You'll see the same thing if you install a custom kernel, but again, if you were seeing that message during this process, then you did something wrong or did an extra step.