Related
Hi All,
Problem with TF700 with JB, rooted but not unlocked. I cannot enter into stock recovery: after volDown - volUP I have dead droid with red triangle. I think this my mistake: after was rooted in ICS .26, not unlocked, I tryed to install GooManager - after that I cannot enter to recovery in ICS. After that JB OTA installation was no problem, i backup and restore root, but still not have recovery.
So, now I have root in JB and can you point me to answer, how I can return stock recovery without unlock?
Thank you!
--
Roman
rusm said:
Hi All,
Problem with TF700 with JB, rooted but not unlocked. I cannot enter into stock recovery: after volDown - volUP I have dead droid with red triangle. I think this my mistake: after was rooted in ICS .26, not unlocked, I tryed to install GooManager - after that I cannot enter to recovery in ICS. After that JB OTA installation was no problem, i backup and restore root, but still not have recovery.
So, now I have root in JB and can you point me to answer, how I can return stock recovery without unlock?
Thank you!
--
Roman[/QUOTE
Turn off you tab, hold vol down then hold power button, as soon as you see the white text appeared on screen, release power button, then vol down button, tell me what you see on the screen? (how many icons?)
Click to expand...
Click to collapse
buhohitr said:
rusm said:
Hi All,
Problem with TF700 with JB, rooted but not unlocked. I cannot enter into stock recovery: after volDown - volUP I have dead droid with red triangle. I think this my mistake: after was rooted in ICS .26, not unlocked, I tryed to install GooManager - after that I cannot enter to recovery in ICS. After that JB OTA installation was no problem, i backup and restore root, but still not have recovery.
So, now I have root in JB and can you point me to answer, how I can return stock recovery without unlock?
Thank you!
--
Roman[/QUOTE
Turn off you tab, hold vol down then hold power button, as soon as you see the white text appeared on screen, release power button, then vol down button, tell me what you see on the screen? (how many icons?)
Click to expand...
Click to collapse
I can see 4 icons: RCK, dont remember )), usb, and wipe. I try all icons exept wipe: red triangle.
Click to expand...
Click to collapse
rusm said:
buhohitr said:
I can see 4 icons: RCK, dont remember )), usb, and wipe. I try all icons exept wipe: red triangle.
Click to expand...
Click to collapse
That's great, so now what do you try to do?? if you don't have any update zip, it will give you the error, but if you have an update zip in there it will pickup and install. Your red triange is normal.
Click to expand...
Click to collapse
buhohitr said:
rusm said:
That's great, so now what do you try to do?? if you don't have any update zip, it will give you the error, but if you have an update zip in there it will pickup and install. Your red triange is normal.
Click to expand...
Click to collapse
I think it may be the future problem if recovery is broken, i think this red triangle indicate that may be I erase something important.
It is not right, you say this behavior is normal? So, if it is all OK now with device, I will have fun))
Thank you very much!!
--
Roman
Click to expand...
Click to collapse
same problem
buhohitr said:
rusm said:
That's great, so now what do you try to do?? if you don't have any update zip, it will give you the error, but if you have an update zip in there it will pickup and install. Your red triangle is normal.
Click to expand...
Click to collapse
This relates to same problem I have . See cannot open recovery in JB in this same QA forum a little further back. I get the icons and when I pick recovery I get to Red triangle Andy but then no matter what combo of buttons pushed nothing happens. In my thread I was given a solution but I am locked but rooted and I believe had to be unlocked to use it. My question is can you get to recovery with a locked rooted tab to wipe cache etc . I can no longer get to that menu.
Click to expand...
Click to collapse
rusm said:
I think it may be the future problem if recovery is broken, i think this red triangle indicate that may be I erase something important.
It is not right, you say this behavior is normal? So, if it is all OK now with device, I will have fun))
Thank you very much!!
--
Roman
Click to expand...
Click to collapse
Tomv5314 said:
This relates to same problem I have . See cannot open recovery in JB in this same QA forum a little further back. I get the icons and when I pick recovery I get to Red triangle Andy but then no matter what combo of buttons pushed nothing happens. In my thread I was given a solution but I am locked but rooted and I believe had to be unlocked to use it. My question is can you get to recovery with a locked rooted tab to wipe cache etc . I can no longer get to that menu.
Click to expand...
Click to collapse
I think what buhohitr was saying is that RCK is a recovery that you can only boot into when there is an update file waiting to be updated on the microSD card. Otherwise, it does nothing but give you that Android with the Red Triangle.
I can confirm this on JB, never tried it while still on ICS.
johnlgalt said:
I think what buhohitr was saying is that RCK is a recovery that you can only boot into when there is an update file waiting to be updated on the microSD card. Otherwise, it does nothing but give you that Android with the Red Triangle.
I can confirm this on JB, never tried it while still on ICS.
Click to expand...
Click to collapse
It seems that the only solution is to unlock and put a custom recovery on . Unfortunately for me I did not unlock for warranty reasons and I updated to .30 and JB OTA and now it seems I have painted myself into a corner since I did not do nvflash or unlock downloads before accepting .30 and JB OTA. It appears ICS stock recovery is gone. Thanks for responses in this and my other thread Tom
see "Cannot use recovery after JB" in QA section further back
Tomv5314 said:
It seems that the only solution is to unlock and put a custom recovery on . Unfortunately for me I did not unlock for warranty reasons and I updated to .30 and JB OTA and now it seems I have painted myself into a corner since I did not do nvflash or unlock downloads before accepting .30 and JB OTA. It appears ICS stock recovery is gone. Thanks for responses in this and my other thread Tom
see "Cannot use recovery after JB" in QA section further back
Click to expand...
Click to collapse
No, you're not corner, you can easily downgrade from JB to .30 (download full version from Asus site), root your device, install superSU then save root with Voodoo OTA root keeper, then upgrade to JB through OTA, restore root using Voodoo OTA root keeper and you all set.
buhohitr said:
No, you're not corner, you can easily downgrade from JB to .30 (download full version from Asus site), root your device, install superSU then save root with Voodoo OTA root keeper, then upgrade to JB through OTA, restore root using Voodoo OTA root keeper and you all set.
Click to expand...
Click to collapse
I am rooted but locked boot loader. and I did save root with voodoo and do have Super SU.
my problem was no recovery. I am trying to get my other thread merged with this one where the solution I was given appears to be unlock then load CWM custom recovery for JB
Tomv5314 said:
I am rooted but locked boot loader. and I did save root with voodoo and do have Super SU.
my problem was no recovery. I am trying to get my other thread merged with this one where the solution I was given appears to be unlock then load CWM custom recovery for JB
Click to expand...
Click to collapse
If you downgrade back to .30 with full package then upgrade to JB it will fixed the issue.
Yip. I did exactly that.
Sent from my rooted BIONIC running ICS 6.7.247 (!) via Tapatalk 2
buhohitr said:
If you downgrade back to .30 with full package then upgrade to JB it will fixed the issue.
Click to expand...
Click to collapse
OK now I get what you are saying. lol full package upgrade Thanks I am going to redo things the way you have said tomorrow. thanks for the help
i had the same problem i upgraded to jb without unlocking first, i was rooted but couldnt access or install a recovery. read a couple threads and found out that the asus unlock tool works on JB also although it states that its only for ICS on the description. anyways unlocked the tablet and used goo to install twrp and everything works just fine.
As we wait for the JB update in US, I was wondering if there's a proven method to keep root on note 10.1?
grimloktt said:
As we wait for the JB update in US, I was wondering if there's a proven method to keep root on note 10.1?
Click to expand...
Click to collapse
I always use voodoo root keeper just to be safe
Sent from my EVO using xda premium
Install the update through mobile ODIN....
Install root without odin?
ultramag69 said:
Install the update through mobile ODIN....
Click to expand...
Click to collapse
I updated via Keis (bad mistake!) and lost my root. Even worse, I lost the ability to boot into cmd -- every time I do the Control + power routine I get booted into Android Recovery. Without the ability to get my tablet into download mode, I can't connect with Odin.
Please help --
Either........ is there another way to boot into download mode?
Or........... is there a way to install cmd on my tablet without using odin?
Please....... I am not new to rooting but I need a bit of detailed description. I'm very afraid of bricking my lovely tablet.
thanks,
Barb
Volume down+power button will get you into download mode volume up+power will get you into recovery
Sent from my EVO using xda premium
Robert542 said:
Volume down+power button will get you into download mode volume up+power will get you into recovery
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Thanks for the response -- however the process you describe does not work after this Kies upgrade. Volume down + power does not get me into download mode -- instead I get stuck in the Android system recovery (3e). (Same with the volume up+power.)
My only options in this Android sytem recovery are to:
reboot
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache
I am wondering -- what if I were to place the clockword mod recovery zip file on my sd card and then use "apply update from external storage", or simply reboot.
Any thoughts or suggestions? I was also told I might be able to get into download mode through adb.
Thanks again for dialogue.
Barbara
No chance... Stock recovery needs the zip files to have samsung approval, not only that but it won't allow a different region rom to be flashed either.... Looks like you screwed the pooch on this little puppy...
nabour said:
I updated via Keis (bad mistake!) and lost my root.
Click to expand...
Click to collapse
Did you update to JB?
Just clarify, please
ultramag69 said:
No chance... Stock recovery needs the zip files to have samsung approval, not only that but it won't allow a different region rom to be flashed either.... Looks like you screwed the pooch on this little puppy...
Click to expand...
Click to collapse
So just to clarify, you are saying that it doesn't matter whether I can get into download mode or not (which I was able to do, with ADB), because ANY clockwork mod recovery file that I find will be unloadable (because it won't "play" with stock recovery)? Is that correct?
Don't want to sound argumentative, but does that mean that anyone who upgrades their firmware via "official Samsung" will be unable to root in the future? That's not too cool.
But if so, I can live with it.
Again, I appreciate your time.
Barb
I know with the S3 there is a root tool that allows rooting via ADB but I don't believe this has been developed for the Note 10.1 as yet. Everything is done via ODIN... Unless you wish to try the 1st method from this thread to get root access - http://forum.xda-developers.com/showthread.php?t=1831152 - then install a version of CWM manually...
Stock root is very picky about what it will or wont flash.... Even if you have a stock rom, if the CSC oodes, region, doesn't match it will error out...
grimloktt said:
Did you update to JB?
Click to expand...
Click to collapse
No........ that's the goofy part of it. I had an upgrade waiting for me (under "settings, upgrade" and so I stupidly assumed it was the official jellybean. Wrong, wrong! I was simply upgraded to 4.0.4. I can't see any noticeable changes, except for the Android Recovery system having booted out my Clockwork recovery (and the root, of course.)
I've decided to wait a week or so until I get the official jellybean and then decide what to do.
It will also have given you a new template in s-notes - landscape and the scroll bar... It will also have given you the ability to use an exFAT formatted sd card... There were a few other tweaks but not too much...
Hi i got my docking station to day and the only thing that works is the mouse function, i cannot write anything anywhere, i have it to default swedish and i have uninstalled swift key but not sixaxis, i have restarted it several times, is it possible that my custom rom makes it incompatible? I use the twrp when i rooted it and customized it.
Thx
Stammis said:
Hi i got my docking station to day and the only thing that works is the mouse function, i cannot write anything anywhere, i have it to default swedish and i have uninstalled swift key but not sixaxis, i have restarted it several times, is it possible that my custom rom makes it incompatible? I use the twrp when i rooted it and customized it.
Thx
Click to expand...
Click to collapse
Yes custom rom does matter, most are not supporting dock, what custom rom you're using?
buhohitr said:
Yes custom rom does matter, most are not supporting dock, what custom rom you're using?
Click to expand...
Click to collapse
I use CROMI
Stammis said:
I use CROMI
Click to expand...
Click to collapse
CROMI should work fine with your dock.
buhohitr said:
CROMI should work fine with your dock.
Click to expand...
Click to collapse
Well then i have no idé, it couldnt be sixaxis that ruins things or?
Stammis said:
Well then i have no idé, it couldnt be sixaxis that ruins things or?
Click to expand...
Click to collapse
In settings-> Language & input, is it set to Asus/English hardware keyboard?
buhohitr said:
In settings-> Language & input, is it set to Asus/English hardware keyboard?
Click to expand...
Click to collapse
No swedish because that is what my keyboard is designed for
Stammis said:
No swedish because that is what my keyboard is designed for
Click to expand...
Click to collapse
So you don't have Swedish in the dropdown menu to select?
buhohitr said:
So you don't have Swedish in the dropdown menu to select?
Click to expand...
Click to collapse
I dont know what you mean by dropdown menue but the tablet is set to Swedish
Stammis said:
I dont know what you mean by dropdown menue but the tablet is set to Swedish
Click to expand...
Click to collapse
What I suggested is pick English to see if the keyboard is working.
buhohitr said:
What I suggested is pick English to see if the keyboard is working.
Click to expand...
Click to collapse
I did, but it does not work,i was thinking to reset the tablet and do the root and rom again since i also cant make my hdmi to work, but i will wait a little and see if i get any more suggestions.
Ps how do you do a cold boot when i have a customrom?
Stammis said:
I did, but it does not work,i was thinking to reset the tablet and do the root and rom again since i also cant make my hdmi to work, but i will wait a little and see if i get any more suggestions.
Ps how do you do a cold boot when i have a customrom?
Click to expand...
Click to collapse
Same procedure as with stock or with custom rom. Go into recovery, select the Android Icon with vol down then hit vol up twice to execute.
buhohitr said:
Same procedure as with stock or with custom rom. Go into recovery, select the Android Icon with vol down then hit vol up twice to execute.
Click to expand...
Click to collapse
I am sorry if I dont keep to the topic but when I have done the cold boot and wish to re do the root and custom rom, is it has simple as to plug in my SD card and run the recovery twrp and all apps and settings are restored?
Stammis said:
I am sorry if I dont keep to the topic but when I have done the cold boot and wish to re do the root and custom rom, is it has simple as to plug in my SD card and run the recovery twrp and all apps and settings are restored?
Click to expand...
Click to collapse
Haha you're in luck. There is a new tool that allow you to root while on JB rom. So I recommend to download the FULL ASUS rom from Asus website, unzip the file then use your twrp to flash this rom. After this, you will be on the latest 4.2 but you will lose root and TWRP. Then go here to get the tool http://forum.xda-developers.com/showthread.php?t=2230763 and root your JB. Once done download Goomanager from the market and install the latest TWRP. From here on you can flash what ever you like.
buhohitr said:
Haha you're in luck. There is a new tool that allow you to root while on JB rom. So I recommend to download the FULL ASUS rom from Asus website, unzip the file then use your twrp to flash this rom. After this, you will be on the latest 4.2 but you will lose root and TWRP. Then go here to get the tool http://forum.xda-developers.com/showthread.php?t=2230763 and root your JB. Once done download Goomanager from the market and install the latest TWRP. From here on you can flash what ever you like.
Click to expand...
Click to collapse
Alright so I got my device back from service and I read what you said, however this does not work unless I can boot TWRP right? That is the case right now, I get the android logo at first, then the logo falls over with a exclamation mark.
Stammis said:
Alright so I got my device back from service and I read what you said, however this does not work unless I can boot TWRP right? That is the case right now, I get the android logo at first, then the logo falls over with a exclamation mark.
Click to expand...
Click to collapse
Since you only have stock recovery, you need to do this:
1. Download the latest Asus full firmware from Asus site. Decompress downloaded .zip file (it will be another .zip)
2. Rename the new zip file to EP201_768_SDUPDATE.zip
3. Format FAT32 the MicroSD card that you will be using for the update process
4. Copy the file to (the root directory of) your MicroSD
5. Insert it into the tablet
6. Shutdown (power off) the tablet
7. Power it on by pressing and holding VOLUME DOWN and POWER buttons simultaneously
8. When you see white text in the top left corner of the screen, release the buttons, then press VOLUME UP button twice, the upgrade process
should start...
9. Wait patiently for 10 minutes or so
Once done, use Asus unlock tool to unlock then use motochopper to root and once rooted download Goomanager app from the market to install custom recovery (TWRP). Finally use TWRP to flash ROM/Kernel.
buhohitr said:
Since you only have stock recovery, you need to do this:
1. Download the latest Asus full firmware from Asus site. Decompress downloaded .zip file (it will be another .zip)
2. Rename the new zip file to EP201_768_SDUPDATE.zip
3. Format FAT32 the MicroSD card that you will be using for the update process
4. Copy the file to (the root directory of) your MicroSD
5. Insert it into the tablet
6. Shutdown (power off) the tablet
7. Power it on by pressing and holding VOLUME DOWN and POWER buttons simultaneously
8. When you see white text in the top left corner of the screen, release the buttons, then press VOLUME UP button twice, the upgrade process
should start...
9. Wait patiently for 10 minutes or so
Once done, use Asus unlock tool to unlock then use motochopper to root and once rooted download Goomanager app from the market to install custom recovery (TWRP). Finally use TWRP to flash ROM/Kernel.
Click to expand...
Click to collapse
okay, ill try that. First however I want to say that I have confirmed that the device is no longer unlocked and rooted does that change anything?
Stammis said:
okay, ill try that. First however I want to say that I have confirmed that the device is no longer unlocked and rooted does that change anything?
Click to expand...
Click to collapse
If you device is NOT unlocked, you can't flash TWRP or custom rom/kernel. You only can do root.
Edit: You need to unlock your device first using Asus unlock tool (Version 7) can be download from Asus website.
buhohitr said:
If you device is NOT unlocked, you can't flash TWRP or custom rom/kernel. You only can do root.
Edit: You need to unlock your device first using Asus unlock tool (Version 7) can be download from Asus website.
Click to expand...
Click to collapse
...sigh, I downloaded the unlock tool at bit.ly/InfinityUnlock but after installing I try to unlock I get an error message saying that it might be network issue, however it is clearly not, any ideas?
Ps: my device has 4.2.1
Stammis said:
...sigh, I downloaded the unlock tool at bit.ly/InfinityUnlock but after installing I try to unlock I get an error message saying that it might be network issue, however it is clearly not, any ideas?
Ps: my device has 4.2.1
Click to expand...
Click to collapse
Oh no ..not good. You have 2 options: 1) keep trying or 2) Need to escalate to Asus tech support, more info here http://forum.xda-developers.com/showthread.php?t=2187777&page=2
My Razr maxx hd (xt926) had been rooted and bootloader unlocked sitting on version 9.16.9 for a while. With KitKat available I downloaded the 9.18.49 rom file and reset the phone flashing it with the Blur_Version.9.30.1.XT926.Verizon.en.US rom and getting everything back to stock. At this point it shows build 9.8.1Q I loaded the KK rom on the SD card and tried to flash from stock recovery.
During verification it aborts, with an error
expects build fingerprint of xt926_verizon/vanquish:4.1.2/9.8.1q-94/56:user release-keys
this device has xt926_verizon/vanquish:4.1.2/9.8.1q-94-1/57:user/r
Any thoughts on how to deal with this?
try this posted by @zachariahpope http://crackflasher.com/blur_version-9-18-94-xt926-verizon-en-us-zip-motorola-droid-razr-hd-cdma-livinginkaos/
billycar11 said:
try this posted by @zachariahpope http://crackflasher.com/blur_versio...zip-motorola-droid-razr-hd-cdma-livinginkaos/
Click to expand...
Click to collapse
That's the file I was trying to flash
Sent from my DROID RAZR HD using Tapatalk
samabuelsamid said:
That's the file I was trying to flash
Sent from my DROID RAZR HD using Tapatalk
Click to expand...
Click to collapse
okay then sorry i was confused try this one.
https://drive.google.com/file/d/0B8pGrRdP0CpyckJnd2JoQklHSjQ/edit
posted by @Sabissimo
billycar11 said:
okay then sorry i was confused try this one.
https://drive.google.com/file/d/0B8pGrRdP0CpyckJnd2JoQklHSjQ/edit
posted by @Sabissimo
Click to expand...
Click to collapse
Bad news. I flashed that one from recovery and it put my phone into a boot loop
Time to start over from scratch
samabuelsamid said:
Bad news. I flashed that one from recovery and it put my phone into a boot loop
Time to start over from scratch
Click to expand...
Click to collapse
I was reading that it rewrites your recovery. Go back into your recovery (should be a new version) and try to I stall again.
Yeah you need to install 2 times.
Did it install the recovery?
billycar11 said:
Yeah you need to install 2 times.
Did it install the recovery?
Click to expand...
Click to collapse
I'll let you know later tonight. I had to reflash back to where I was so I'd have a working phone for my workday.
samabuelsamid said:
I'll let you know later tonight. I had to reflash back to where I was so I'd have a working phone for my workday.
Click to expand...
Click to collapse
Definitely, the reboot during the install back into recovery is what confused a lot of us who were part of the soak test and tried to apply it manually ourselves.
When you first go into recovery and install the OTA, it will reboot. At that point, it will boot back to the recovery screen. There, you must press volume up + power. That is different from the old vol up+ vol down.
Anyways, once you are back in the "hard to read" recovery (why did they reduce the brightness on the new recovery?), you need to go back and install the OTA again. This time it will continue on where it left off and apply the KK update to your system.
Profit!
You might want to go to my post here (
http://forum.xda-developers.com/showpost.php?p=52602576&postcount=1) and read some of the gotchas. Read them BEFORE you take the update so you don't bork your phone:
billycar11 said:
Yeah you need to install 2 times.
Did it install the recovery?
Click to expand...
Click to collapse
iBolski said:
Definitely, the reboot during the install back into recovery is what confused a lot of us who were part of the soak test and tried to apply it manually ourselves.
When you first go into recovery and install the OTA, it will reboot. At that point, it will boot back to the recovery screen. There, you must press volume up + power. That is different from the old vol up+ vol down.
Anyways, once you are back in the "hard to read" recovery (why did they reduce the brightness on the new recovery?), you need to go back and install the OTA again. This time it will continue on where it left off and apply the KK update to your system.
Profit!
You might want to go to my post here (
http://forum.xda-developers.com/showpost.php?p=52602576&postcount=1) and read some of the gotchas. Read them BEFORE you take the update so you don't bork your phone:
Click to expand...
Click to collapse
Thanks, I'll provide an update of how this works!
iBolski said:
Definitely, the reboot during the install back into recovery is what confused a lot of us who were part of the soak test and tried to apply it manually ourselves.
When you first go into recovery and install the OTA, it will reboot. At that point, it will boot back to the recovery screen. There, you must press volume up + power. That is different from the old vol up+ vol down.
Anyways, once you are back in the "hard to read" recovery (why did they reduce the brightness on the new recovery?), you need to go back and install the OTA again. This time it will continue on where it left off and apply the KK update to your system.
Profit!
You might want to go to my post here (
http://forum.xda-developers.com/showpost.php?p=52602576&postcount=1) and read some of the gotchas. Read them BEFORE you take the update so you don't bork your phone:
Click to expand...
Click to collapse
This all worked perfectly and I'm now rocking KitKat
iBolski said:
Definitely, the reboot during the install back into recovery is what confused a lot of us who were part of the soak test and tried to apply it manually ourselves.
When you first go into recovery and install the OTA, it will reboot. At that point, it will boot back to the recovery screen. There, you must press volume up + power. That is different from the old vol up+ vol down.
Anyways, once you are back in the "hard to read" recovery (why did they reduce the brightness on the new recovery?), you need to go back and install the OTA again. This time it will continue on where it left off and apply the KK update to your system.
Profit!
You might want to go to my post here (
http://forum.xda-developers.com/showpost.php?p=52602576&postcount=1) and read some of the gotchas. Read them BEFORE you take the update so you don't bork your phone:
Click to expand...
Click to collapse
One other question: My bootloader is unlocked, I'm trying to find the directions to root again under kitkat by manually sideloading. Anyone have a link?
samabuelsamid said:
One other question: My bootloader is unlocked, I'm trying to find the directions to root again under kitkat by manually sideloading. Anyone have a link?
Click to expand...
Click to collapse
All you need to do is flash CWM and then find a sideloadable SU package to sideload under CWM. That's it.
iBolski said:
All you need to do is flash CWM and then find a sideloadable SU package to sideload under CWM. That's it.
Click to expand...
Click to collapse
Thanks. Just a couple more questions before I do this to make sure I don't send my phone back into oblivion and have to start all over again. Is the CWM recovery specific to any particular version of Android, current one available for XT926 on clockworkmod.com download page is 6.0.4.4. Similarly, does SU need to be specific to this phone/KitKat rom?
I've rooted numerous phones before, always using a script like Razr Hd utility. This is my first attempt at manual root so I appreciate your patience
samabuelsamid said:
Thanks. Just a couple more questions before I do this to make sure I don't send my phone back into oblivion and have to start all over again. Is the CWM recovery specific to any particular version of Android, current one available for XT926 on clockworkmod.com download page is 6.0.4.4. Similarly, does SU need to be specific to this phone/KitKat rom?
I've rooted numerous phones before, always using a script like Razr Hd utility. This is my first attempt at manual root so I appreciate your patience
Click to expand...
Click to collapse
You need to download the new CWM for KK. xt926-KK-CWM-6048.img is the name. You can get it from here: http://forum.xda-developers.com/showpost.php?p=52564336&postcount=1
iBolski said:
You need to download the new CWM for KK. xt926-KK-CWM-6048.img is the name. You can get it from here: http://forum.xda-developers.com/showpost.php?p=52564336&postcount=1
Click to expand...
Click to collapse
good thing I asked first
Update: not rooted on KitKat!
samabuelsamid said:
My Razr maxx hd (xt926) had been rooted and bootloader unlocked sitting on version 9.16.9 for a while. With KitKat available I downloaded the 9.18.49 rom file and reset the phone flashing it with the Blur_Version.9.30.1.XT926.Verizon.en.US rom and getting everything back to stock. At this point it shows build 9.8.1Q I loaded the KK rom on the SD card and tried to flash from stock recovery.
During verification it aborts, with an error
expects build fingerprint of xt926_verizon/vanquish:4.1.2/9.8.1q-94/56:user release-keys
this device has xt926_verizon/vanquish:4.1.2/9.8.1q-94-1/57:user/r
Any thoughts on how to deal with this?
Click to expand...
Click to collapse
I have the same problem, but I'm getting the error message that expects your device. What was the image that you used? I have the vanquish:4.1.2/9.8
1Q-94/56:user.
samabuelsamid said:
good thing I asked first
Update: not rooted on KitKat!
Click to expand...
Click to collapse
Then you cannot use CWM and there is no safe strap for KK.
Also, root is now lost, but SamuriHL is working on a theory that might work. Unfortunately, it requires locked phones that have NOT taken the soak or OTA yet and we have to wait for the official KK FXZ image file before he can continue. If the phone has had the OTA or soak applied to it, then it can't be part of the test.
iBolski said:
Then you cannot use CWM and there is no safe strap for KK.
Also, root is now lost, but SamuriHL is working on a theory that might work. Unfortunately, it requires locked phones that have NOT taken the soak or OTA yet and we have to wait for the official KK FXZ image file before he can continue. If the phone has had the OTA or soak applied to it, then it can't be part of the test.
Click to expand...
Click to collapse
Sorry, that should have read NOW rooted. CWM worked fine as did Koush's superuser
samabuelsamid said:
Sorry, that should have read NOW rooted. CWM worked fine as did Koush's superuser
Click to expand...
Click to collapse
you know what, color me stupid.
I've been helping so many people that when I read "no root", I interpreted it as "locked bootloader".
My bad.
Maybe its the same as for G930F, idk...
Will be really helpful, thanks
utube guide
search utube for 'How to Root Galaxy S7 or S7 Edge on Android 7.0 Nougat w/ Magisk!'
pit1509 said:
search utube for 'How to Root Galaxy S7 or S7 Edge on Android 7.0 Nougat w/ Magisk!'
Click to expand...
Click to collapse
Why search youtube when all the how tos are rite here on xda?
Are you asking how to do it
=> Flash TWRP
=> Get into TWRP and flash a custom kernel. I'm using SuperKernel v2.8 and it works better than the stock.
=> Flash Latest SuperSU flashable zip file.
=> Reboot
UmarBurney said:
=> Flash TWRP
=> Get into TWRP and flash a custom kernel. I'm using SuperKernel v2.8 and it works better than the stock.
=> Flash Latest SuperSU flashable zip file.
=> Reboot
Click to expand...
Click to collapse
Mate, where can I get SuperKernel v2.8 and under which category in Odin do I need to flash it?
Where can I get the SuperSU zip?
Thanks a lot
TheMadScientist said:
Why search youtube when all the how tos are rite here on xda?
Are you asking how to do it
Click to expand...
Click to collapse
I meant I found a guide in YT but turns out it doesnt work for me (after installing the zips in TWRP the phone hold on the 'galaxy s7' logo and doesnt do anything)
pit1509 said:
I meant I found a guide in YT but turns out it doesnt work for me (after installing the zips in TWRP the phone hold on the 'galaxy s7' logo and doesnt do anything)
Click to expand...
Click to collapse
As,far as I know,you can't use magiskd
TheMadScientist said:
As,far as I know,you can't use magiskd
Click to expand...
Click to collapse
this guy claims otherwise
https://youtu.be/CjwSjiE76o8
pit1509 said:
I meant I found a guide in YT but turns out it doesnt work for me (after installing the zips in TWRP the phone hold on the 'galaxy s7' logo and doesnt do anything)
Click to expand...
Click to collapse
That's because you trigger DM variety. You need to flash custom kernel. And yes you can use magisk but I will recommend SuperSU for flawless root priviliges. I'm also using 930FD and it happened with me too in the beginning. So I flashed a custom kernel with dm variety disabled. You can get all the files from XDA forums. Just look for them in Exonys section.
---------- Post added at 07:52 PM ---------- Previous post was at 07:28 PM ----------
Okay here you go.
1) Download TWRP for Galaxy S7 FD from here twrp-3.1.1-0-herolte.img.tar.
2) Download SuperKernel v2.8 from here. Thanks to @Tkkg1994.
3) Download SuperSU Flashable Zip from Recovery Flashable.zip.
4) Download latest Odin from here. Also download the Samsung USB drivers.
Now that you have done downloading files. Let's go to the next steps.
5) Transfer the SuperSU Flashable Zip and SuperKernel Zip to your SD Card. Internal or external doesn't matter.
6) Extract and open Odin on your PC and restart your GS7 in download mode.
7) Connect your phone via a usb cable. If you see odin detected your phone, then it's fine. If it doesn't just reinstall Samsung USB Drivers in your PC.
8) Assuming that your PC has successfully detected your phone, click AP and browse to the TWRP File that you downloaded in your PC. Make sure to uncheck "Auto Reboot" in Odin. This is very important otherwise you will be stuck in the bootloop.
9) Now when the TWRP is flashed. Press and hold Power button + Home + Volume Down for some time and as soon as the screen goes black, switch your finger from Volume Down to Volume Up instantly, not leaving the other two buttons. Keep the buttons pressed until you see the TWRP screen.
10) After booting into TWRP slide right to allow modifications. Now go to Install and select the SuperKernel Zip, swipe right to flash.
11) After flashing SuperKernel, select the SuperSU zip and swipe right to flash.
12) After flashing, reboot system. The phone might reboots a couple to times but don't touch it. Let it complete the boot. That's it.
This is how I did. May the odds be in your favor. Good luck.
UmarBurney said:
That's because you trigger DM variety. You need to flash custom kernel. And yes you can use magisk but I will recommend SuperSU for flawless root priviliges. I'm also using 930FD and it happened with me too in the beginning. So I flashed a custom kernel with dm variety disabled. You can get all the files from XDA forums. Just look for them in Exonys section.
---------- Post added at 07:52 PM ---------- Previous post was at 07:28 PM ----------
Okay here you go.
1) Download TWRP for Galaxy S7 FD from here twrp-3.1.1-0-herolte.img.tar.
2) Download SuperKernel v2.8 from here. Thanks to @Tkkg1994.
3) Download SuperSU Flashable Zip from Recovery Flashable.zip.
4) Download latest Odin from here. Also download the Samsung USB drivers.
Now that you have done downloading files. Let's go to the next steps.
5) Transfer the SuperSU Flashable Zip and SuperKernel Zip to your SD Card. Internal or external doesn't matter.
6) Extract and open Odin on your PC and restart your GS7 in download mode.
7) Connect your phone via a usb cable. If you see odin detected your phone, then it's fine. If it doesn't just reinstall Samsung USB Drivers in your PC.
8) Assuming that your PC has successfully detected your phone, click AP and browse to the TWRP File that you downloaded in your PC. Make sure to uncheck "Auto Reboot" in Odin. This is very important otherwise you will be stuck in the bootloop.
9) Now when the TWRP is flashed. Press and hold Power button + Home + Volume Down for some time and as soon as the screen goes black, switch your finger from Volume Down to Volume Up instantly, not leaving the other two buttons. Keep the buttons pressed until you see the TWRP screen.
10) After booting into TWRP slide right to allow modifications. Now go to Install and select the SuperKernel Zip, swipe right to flash.
11) After flashing SuperKernel, select the SuperSU zip and swipe right to flash.
12) After flashing, reboot system. The phone might reboots a couple to times but don't touch it. Let it complete the boot. That's it.
This is how I did. May the odds be in your favor. Good luck.
Click to expand...
Click to collapse
I did exactly that the last time and it got stuck on boot (then I needed to reflash the stock ROM all over).
How do I disable dm variety? (I didn't know it need to)
pit1509 said:
I did exactly that the last time and it got stuck on boot (then I needed to reflash the stock ROM all over).
How do I disable dm variety? (I didn't know it need to)
Click to expand...
Click to collapse
Even flashing SuperKernel didn't work??? Strange.
UmarBurney said:
Even flashing SuperKernel didn't work??? Strange.
Click to expand...
Click to collapse
As I said I didnt disable dm variety, maybe thats the reason?
pit1509 said:
As I said I didnt disable dm variety, maybe thats the reason?
Click to expand...
Click to collapse
Bro, dm variety is an automatic feature included in the stock kernel. When you flash SuperKernel, your stock kernel is replaced by SuperKernel which has dm variety disabled already.
---------- Post added at 07:39 PM ---------- Previous post was at 07:38 PM ----------
I think you haven't tried flashing SuperKernel. I'm 100% sure that after flashing SuperKernel, you will be able to boot.
UmarBurney said:
Bro, dm variety is an automatic feature included in the stock kernel. When you flash SuperKernel, your stock kernel is replaced by SuperKernel which has dm variety disabled already.
---------- Post added at 07:39 PM ---------- Previous post was at 07:38 PM ----------
I think you haven't tried flashing SuperKernel. I'm 100% sure that after flashing SuperKernel, you will be able to boot.
Click to expand...
Click to collapse
Ah i get it... Idk what the problem then.. even when I flash twrp itself the phone stucks on boot :\
I'll keep looking
pit1509 said:
Ah i get it... Idk what the problem then.. even when I flash twrp itself the phone stucks on boot :\
I'll keep looking
Click to expand...
Click to collapse
Have you been able to boot into TWRP, ever???
UmarBurney said:
Have you been able to boot into TWRP, ever???
Click to expand...
Click to collapse
Yes I have. but somehow today it didnt worked .. i'm using Odin3_v3.12.3
It should work. Follow my instructions carefully. And also try to educate yourself on this. As much as you can. Read read and read. Good luck.
pit1509 said:
this guy claims otherwise
https://youtu.be/CjwSjiE76o8
Click to expand...
Click to collapse
I have the Verizon variant sorry which we cant use magisk I dont think.