Hi
I will get my N7 in Calender week 37, this is the week starting with the 10. September.
Now I have some questions.
1. I want to root it, like my arc S. I also know how to root. Unlock the BL, flash CWM using fastboot flash recovery recovery.img, then flash SuperSU Package via CWM. Is this ok? Somewhere i read, i have to delete any file in /system. Is this right?
2. If my BL is unlocked and a custon recovery is flashed, will i still be able to update OTA?
3. If my Bootloader is unlocked, a lock will be shown under the Kernel logo. If I relock the Bootloader using fastboot oem relock, will the lock still be there?
Thank you!
Gesendet von meinem Arc S mit Tapatalk 2
Please answer!
Gesendet von meinem Arc S mit Tapatalk 2
Comeon, please answer.
Gesendet von meinem Arc S mit Tapatalk 2
papayayoghurt said:
1. I want to root it, like my arc S. I also know how to root. Unlock the BL, flash CWM using fastboot flash recovery recovery.img, then flash SuperSU Package via CWM. Is this ok? Somewhere i read, i have to delete any file in /system. Is this right?
Click to expand...
Click to collapse
You should run CWM at least once after flashing it; it should automatically correct the ROM-wants-to-overwrite-recovery problem so that you don't have to delete some /system file. So after flashing, you would do
Code:
fastboot boot recovery.img
(I'm assuming from your sample instructions that you've renamed the recovery to "recovery.img". If not, replace it with whatever the file name is.)
Note: I'm basing this suggestion on paulobrien's earlier advice (which was for an outdated version of CWM). I'm not actually an expert at this stuff.
papayayoghurt said:
2. If my BL is unlocked and a custon recovery is flashed, will i still be able to update OTA?
Click to expand...
Click to collapse
I think so (don't trust me on this) but I'm also pretty sure it'll remove root. I recommend just going fullon with custom ROM so you don't have to worry about this.
papayayoghurt said:
3. If my Bootloader is unlocked, a lock will be shown under the Kernel logo. If I relock the Bootloader using fastboot oem relock, will the lock still be there?
Click to expand...
Click to collapse
No.
papayayoghurt said:
Hi
I will get my N7 in Calender week 37, this is the week starting with the 10. September.
Now I have some questions.
1. I want to root it, like my arc S. I also know how to root. Unlock the BL, flash CWM using fastboot flash recovery recovery.img, then flash SuperSU Package via CWM. Is this ok? Somewhere i read, i have to delete any file in /system. Is this right?
2. If my BL is unlocked and a custon recovery is flashed, will i still be able to update OTA?
3. If my Bootloader is unlocked, a lock will be shown under the Kernel logo. If I relock the Bootloader using fastboot oem relock, will the lock still be there?
Thank you!
Click to expand...
Click to collapse
Before stating some answers, please don't continually bump your thread, it was a total of 5 hours... A couple of days, maybe... We have lives...
Now here is my answers to your questions:
1. This is OK, you dont need to touch anything in /system
2. Yes, and no. They will appear, but to keep it as is, may be a bit more involved.
3. The lock will be gone, it will look like nothing was different.
For points 1 and 2, I referred to http://www.nexustablets.net/forum/n...-7-windows-keep-root-through-ota-updates.html. It has a pretty good walkthrough on how to do things.
papayayoghurt said:
Comeon, please answer.
Gesendet von meinem Arc S mit Tapatalk 2
Click to expand...
Click to collapse
Dude - we don't work for you - you can't expect answers instantly!! Man, is that annoying! Give people time - they will answer your questions - or if you are in such a hurry for answers (as apparently you are), do some searching on your own! Geez...
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
thebobp said:
You should run CWM at least once after flashing it; it should automatically correct the ROM-wants-to-overwrite-recovery problem so that you don't have to delete some /system file. So after flashing, you would do
Code:
fastboot boot recovery.img
(I'm assuming from your sample instructions that you've renamed the recovery to "recovery.img". If not, replace it with whatever the file name is.)
Click to expand...
Click to collapse
Do i have to do fastboot boot recovery.img before or after fastboot flash recovery recovery.img?
But thanks for the answers and sorry for pushing.
EDIT: the link of mouse_man solved all my questions. Thanks!
Gesendet von meinem Arc S mit Tapatalk 2
Related
OK, by no means am I new to this stuff but since I mainly creep around in the evo lte forums I've been out of the loop regarding the 4.1.2 updates here. I've been looking around trying to grab bits and pieces of info and noticed there is a new bootloader but there was confusion regarding how to update it. So here's what I have to know:
1. What is the best way to go about updating the boot loader? Relock and update via ota and then re unlock and whatnot or is there a way to push the boot loader via fast boot or placing a file on the internal storage like the evo.
2. Is the nexus toolkit updated to handle the unlocking and rooting of the new update or do I have to use terminal commands, not a problem if I have to.
3. Did the update finally fix the issue of getting into recovery without being connected to a computer?
Thanks in advance to anyone who takes the time to fill me in
Sent from my Nexus 7 using Tapatalk 2
Anyone?
Sent from my Nexus 7 using Tapatalk 2
1. I can't find the original link, but I attached a flashable ZIP that will update the bootloader from recovery. You can also push this IMG file through fastboot to update it to the latest one.
2. Yes, the Nexus 7 Toolkit was updated to be able to handle rooting and unlocking of the latest update.
3. Yes, the update allows you to boot into recovery from bootloader now.
Hope this helps you!
thanks for the info i found a link to the new 3.41 bootloader on googles dev site so im just gonna fastboot flash it. and thank god they fixed that recovery issue finally haha :good:
WindyCityRockr said:
I can't find the original link, but I attached a flashable ZIP that will update the bootloader from recovery.
Click to expand...
Click to collapse
Then I guess you don't have to lock it first and unlock it later, right?
Sent from my Nexus 7 using Tapatalk 2
I am testing work very well
https://play.google.com/store/apps/details?id=net.segv11.bootunlocker
Sent from my Nexus 7 using Tapatalk
somboons said:
I am testing work very well
https://play.google.com/store/apps/details?id=net.segv11.bootunlocker
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
After youve unlocked it to root. So you still lose your data the first time you unlock it.
In thread in my country , I saw tut for unlock boot loader without lose data in first time In nexus 10 I think in nexus 7 2013 work too but I did not test it yet.
the method is
1. Put recovery image to sdcard.
2. Download
http://download.chainfire.eu/372/SuperSU/UPDATE-SuperSU-v1.86.zip
Save to sdcard
3. Boot to bootloader and use command
fastboot boot recovery.img
4. Install zip file for root
5. Reboot
6. Install BootUnlocker and Open
You can unlockboot loader without lose data
#### I did not it yet ####
Sent from my Nexus 7 using Tapatalk
somboons said:
the method is
1. Put recovery image to sdcard.
Click to expand...
Click to collapse
Which recovery image should be used for that? Standard recovery, CWM, TWRP?
CWM or TWRP can use
Sent from my LG-D802 using Tapatalk
somboons said:
In thread in my country , I saw tut for unlock boot loader without lose data in first time In nexus 10 I think in nexus 7 2013 work too but I did not test it yet.
the method is
1. Put recovery image to sdcard.
2. Download
http://download.chainfire.eu/372/SuperSU/UPDATE-SuperSU-v1.86.zip
Save to sdcard
3. Boot to bootloader and use command
fastboot boot recovery.img
4. Install zip file for root
5. Reboot
6. Install BootUnlocker and Open
You can unlockboot loader without lose data
#### I did not it yet ####
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
This method is not working...
You can't fastboot boot something without an unlocked bootloader
Michealtbh said:
You can't fastboot boot something without an unlocked bootloader
Click to expand...
Click to collapse
And you cant unlock your bootloader without wiping...
somboons said:
I am testing work very well
https://play.google.com/store/apps/details?id=net.segv11.bootunlocker
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
yep, I installed it too...
however one important thing you should not forget (copy/past from a review) :
"Works great but be careful Once you have unlocked and rooted your phone this app works great to lock the bootloader again. But use caution when updating OTA. I allowed an OTA update to Android 4.4.2 while locked and I lost root access (expected) but because I didn't unlock before the update, I am now locked without a way to unlock unless I wipe the phone. Great app. Just make sure you know what it does and how to use it."
--> unlock before to apply an OTA
I've the b140 rooted (android 5) with unlocked Bootloader and TWRP.
What is the right way to update to b320 (android 6) without bootloop and similar?
unroot first, replace TWRP with stock recovery
How unroot? Only flashing stock recocery? Where i can download stock recocery and how flash?
walter4991 said:
How unroot? Only flashing stock recocery? Where i can download stock recocery and how flash?
Click to expand...
Click to collapse
Use this : http://forum.xda-developers.com/honor-7/general/honor-7-multi-tool-t3281176 to install stock recovery (I used 320)
To unroot go to SU app and use unroot option in settings, then reboot.
miodzicho said:
Use this : http://forum.xda-developers.com/honor-7/general/honor-7-multi-tool-t3281176 to install stock recovery (I used 320)
To unroot go to SU app and use unroot option in settings, then reboot.
Click to expand...
Click to collapse
I must flash again b140 than b320?
walter4991 said:
I must flash again b140 than b320?
Click to expand...
Click to collapse
Well I did upgrade from b180 to b320
So i must flash b140 to b180 and finally b180 to b320 correct?
I have deleted update file, but there inside, when you unzip it, you can find .txt file where is exactly path described. From earlier FW version, and from 180. Please see.
I've doing the update, now i'm on b320!
Can i root with multi tool?
Yes you can. Use twrp sminki ang 2.62. On first reboot will fail, just do reboot manually.
Gesendet von meinem PLK-L01 mit Tapatalk
miodzicho said:
Yes you can. Use twrp sminki ang 2.62. On first reboot will fail, just do reboot manually.
Gesendet von meinem PLK-L01 mit Tapatalk
Click to expand...
Click to collapse
I must flash TWRP before root?
So the right way is:
1) With multitool flash TWRP recovery
2) With multitool apply root.
It's correct?
Exactly. In multitool will tell you steps.
Gesendet von meinem PLK-L01 mit Tapatalk
Perfect. Device Rooted!
@miodzicho Thank you very much!
Achieved today. Rooted with KingRoot 4.9.0.142. Took 3 times but root is achieved!
finally!! thanks for the heads up.
I think mine finally worked on the 6th attempt
so just keep going until it works!!!!
SoreGums said:
finally!! thanks for the heads up.
I think mine finally worked on the 6th attempt
so just keep going until it works!!!!
Click to expand...
Click to collapse
The down side is that you won't be able to get any OTA updates. The process would be to revert to 1.5, then let all the updates apply and then repeat the root process.
tomlogan1 said:
The down side is that you won't be able to get any OTA updates. The process would be to revert to 1.5, then let all the updates apply and then repeat the root process.
Click to expand...
Click to collapse
I dont have this problem (dont tested test release) just unroot in supersu. Maybe your install recovery.sh isnt original?
Gesendet von meinem LG-D855 mit Tapatalk
tschmid said:
I dont have this problem (dont tested test release) just unroot in supersu. Maybe your install recovery.sh isnt original?
Gesendet von meinem LG-D855 mit Tapatalk
Click to expand...
Click to collapse
Have not messed with the recovery.sh unlesss Kingo Root causes that. I believe that there is a thread I saw somewhere to replace Kingo with supersu. Will try to see if that will help.
Done f*cking with this
tomlogan1 said:
Have not messed with the recovery.sh unlesss Kingo Root causes that. I believe that there is a thread I saw somewhere to replace Kingo with supersu. Will try to see if that will help.
Click to expand...
Click to collapse
Found an app that was supposed to add supersu instead of KingoRoot. Link is http://missingtricks.net/replace-kingroot-kinguser-with-supersu-superuser-android-guide/. Tried the option to use super su me pro.
App said it worked but went into an extended boot loop. Had to revert, again, to 1.5 and now coming back to current. Going to stay unrooted for the foreseeable future.
Plain android is SO much better.
tomlogan1 said:
Found an app that was supposed to add supersu instead of KingoRoot. Link is http://missingtricks.net/replace-kingroot-kinguser-with-supersu-superuser-android-guide/. Tried the option to use super su me pro.
App said it worked but went into an extended boot loop. Had to revert, again, to 1.5 and now coming back to current. Going to stay unrooted for the foreseeable future.
Plain android is SO much better.
Click to expand...
Click to collapse
How does one revert to 1.5? I'm a noob but I just wanted to root and have a backup plan in case it goes south. Thanks!
Also, will Kingoroot work on 2.0.305
Madethisjustnow said:
How does one revert to 1.5? I'm a noob but I just wanted to root and have a backup plan in case it goes south. Thanks!
Also, will Kingoroot work on 2.0.305
Click to expand...
Click to collapse
Try cwm Recovery and flash supersu. Theres also a flashable 2.0.305 in this forum
Gesendet von meinem Nexus 6P mit Tapatalk
tschmid said:
Try cwm Recovery and flash supersu. Theres also a flashable 2.0.305 in this forum
Gesendet von meinem Nexus 6P mit Tapatalk
Click to expand...
Click to collapse
The Cyanogen recovery also works well. Have verified that using Supersu unlike other exploits allows you to unroot, upgrade and then reroot. Much better than King Root or Kingo root.
tomlogan1 said:
The Cyanogen recovery also works well. Have verified that using Supersu unlike other exploits allows you to unroot, upgrade and then reroot. Much better than King Root or Kingo root.
Click to expand...
Click to collapse
Btw I've made some progress with cm-13.0 hope i can upload soon a Test Version ?
Gesendet von meinem Nexus 6P mit Tapatalk
tschmid said:
Btw I've made some progress with cm-13.0 hope i can upload soon a Test Version
Gesendet von meinem Nexus 6P mit Tapatalk
Click to expand...
Click to collapse
Wonderful! Let me know if you need someone to test. Happy to help and hope to be off of Remix as we are probably not going to get any real support from Jide.
i agree with tomlogan -- i'd definitely love to give CM a try! thank you for your work!
tschmid said:
Try cwm Recovery and flash supersu. Theres also a flashable 2.0.305 in this forum
Gesendet von meinem Nexus 6P mit Tapatalk
Click to expand...
Click to collapse
thanks for responding! do you think you could make a step by step tutorial of how to use cwm on the remix? i apologize if that is asking too much. I've only used towelroot on my (4.4) phone a while ago. thanks in advance!
Madethisjustnow said:
thanks for responding! do you think you could make a step by step tutorial of how to use cwm on the remix? i apologize if that is asking too much. I've only used towelroot on my (4.4) phone a while ago. thanks in advance!
Click to expand...
Click to collapse
In the thread CM13 there was a zip of cwm recovery. But the link is availble further in the thread it's also here
Using fastboot you flash it to your tablet (for example fastboot flash recovery recoveryxxxxx.zip )
Reboot bootloader, and flash superuser from chainfire's site.
Madethisjustnow said:
thanks for responding! do you think you could make a step by step tutorial of how to use cwm on the remix? i apologize if that is asking too much. I've only used towelroot on my (4.4) phone a while ago. thanks in advance!
Click to expand...
Click to collapse
I presume you already have enabled developer options under settings. You should also have ADB installed. Here is my version:
Download SuperSu from the market. Option - Pay the author - worth it to keep good software coming.
Connect your tablet via USB.
Have the recovery (cwm or cyanogen) located in your ADB directory.
Open a command prompt (Windows) For Linux, ask someone else.
Move to your ADB directory and type ADB Devices. Hit Enter.
If you are OK with ADB you should get a serial number as verification.
Then enter ADB reboot bootloader. Hit enter.
Then enter fastboot boot (recovery name). Hit enter.
This will take a few minutes. If all is OK you should have a screen on your tablet with an option to install upgrade etc.
Select Supersu and hit enter.
If you reboot now, you will be rooted, but with the stock recovery. If you are OK with that reboot, otherwise you will need to flash the recovery (cwm or cyanogen) with a command fastboot flash recovery (recovery name).
This worked for me. Good luck.
Cyanogen Mod Recovery
tomlogan1 said:
I presume you already have enabled developer options under settings. You should also have ADB installed. Here is my version:
Download SuperSu from the market. Option - Pay the author - worth it to keep good software coming.
Connect your tablet via USB.
Have the recovery (cwm or cyanogen) located in your ADB directory.
Open a command prompt (Windows) For Linux, ask someone else.
Move to your ADB directory and type ADB Devices. Hit Enter.
If you are OK with ADB you should get a serial number as verification.
Then enter ADB reboot bootloader. Hit enter.
Then enter fastboot boot (recovery name). Hit enter.
This will take a few minutes. If all is OK you should have a screen on your tablet with an option to install upgrade etc.
Select Supersu and hit enter.
If you reboot now, you will be rooted, but with the stock recovery. If you are OK with that reboot, otherwise you will need to flash the recovery (cwm or cyanogen) with a command fastboot flash recovery (recovery name).
This worked for me. Good luck.
Click to expand...
Click to collapse
Courtesy of Herr Schmidt. I did not make this recovery, but it is my every day recovery.
Thank you, Thomas.
help needed. I stuck on flyme 6 nougat beta. I have no recovery. Bootloader is locked, rooted. Any ideas how to back to stable rom or any other rom or install recovery somehow?
Sent from my PRO 5 using Tapatalk
SIeniuss said:
help needed. I stuck on flyme 6 nougat beta. I have no recovery. Bootloader is locked, rooted. Any ideas how to back to stable rom or any other rom or install recovery somehow?
Sent from my PRO 5 using Tapatalk
Click to expand...
Click to collapse
U have to replace recovery.img and bootloader file inside Flyme ZIP file if u want to maintain them
PYCON said:
U have to replace recovery.img and bootloader file inside Flyme ZIP file if u want to maintain them
Click to expand...
Click to collapse
From which version should I replace this files and how to install it then?
Sent from my PRO 5 using Tapatalk
SIeniuss said:
help needed. I stuck on flyme 6 nougat beta. I have no recovery. Bootloader is locked, rooted. Any ideas how to back to stable rom or any other rom or install recovery somehow?
Click to expand...
Click to collapse
Flyme beta don't have recovery?
SIeniuss said:
From which version should I replace this files and how to install it then?
Sent from my PRO 5 using Tapatalk
Click to expand...
Click to collapse
From no versions Recovery.img file must be replaced from TWRP img file and Bootloader file from unlocked bootloader file. Now it's late, I'm sorry but your phone is died
al_gxl said:
Flyme beta don't have recovery?
Click to expand...
Click to collapse
Yes, of course, but stock recovery... U need TWRP recovery
PYCON said:
From no versions Recovery.img file must be replaced from TWRP img file and Bootloader file from unlocked bootloader file. Now it's late, I'm sorry but your phone is died
Yes, of course, but stock recovery... U need TWRP recovery
Click to expand...
Click to collapse
But I think you can also install other Flyme version without recovery
al_gxl said:
But I think you can also install other Flyme version without recovery
Click to expand...
Click to collapse
For sure, u can flash original Flyme rom without TWRP but stock recovery must work.or u can try Flashtool and similar tools from a PC if u r able to have a signed token.
I'm just thinking. Is it able to push recovery into system files via root explorer? All we need to know is what files and where paste it... Is it possible?
Sent from my PRO 5 using Tapatalk
SIeniuss said:
I'm just thinking. Is it able to push recovery into system files via root explorer? All we need to know is what files and where paste it... Is it possible?
Sent from my PRO 5 using Tapatalk
Click to expand...
Click to collapse
If the phone runs android system correctly, it's possible I think...
I'm using this phone. It works fine, the only problem is that recovery is not turning on
Sent from my PRO 5 using Tapatalk
Did you repair your phone now?
I flash the official ROM first, then I flash twrp recovery. Now my phone cant reboot system stuck on the logo screen. in fastboot mode, PC cant recognizes the phone. adb can't find the phone. how can I repair my phone to normal
liuxu1027 said:
Did you repair your phone now?
I flash the official ROM first, then I flash twrp recovery. Now my phone cant reboot system stuck on the logo screen. in fastboot mode, PC cant recognizes the phone. adb can't find the phone. how can I repair my phone to normal
Click to expand...
Click to collapse
Official rom... ok.... TWRP.... ok.... BUT BOOTLOADER ?! U've forgot it ?!
PYCON said:
Official rom... ok.... TWRP.... ok.... BUT BOOTLOADER ?! U've forgot it ?!
Click to expand...
Click to collapse
Yes............
No, I didn't repaired it yet. Still waiting for ideas
Sent from my PRO 5 using Tapatalk
liuxu1027 said:
Did you repair your phone now?
I flash the official ROM first, then I flash twrp recovery. Now my phone cant reboot system stuck on the logo screen. in fastboot mode, PC cant recognizes the phone. adb can't find the phone. how can I repair my phone to normal
Click to expand...
Click to collapse
I have the same problem in MS Windows, and i have to use Linux works bether with Android
Sorry i haven't readed all, just install oficial rom and start from 0 with the unlocking of bootloader, in TWRP flash the original rom
2uk! said:
I have the same problem in MS Windows, and i have to use Linux works bether with Android
Sorry i haven't readed all, just install oficial rom and start from 0 with the unlocking of bootloader, in TWRP flash the original rom
Click to expand...
Click to collapse
But how to start from 0 without any recovery? To install new system we need recovery, to install recovery we need to unlock bootloader and this is not possible on this flyme version
Sent from my PRO 5 using Tapatalk
Only way to solve this is taking the phone to technical service. Done it myself. Be careful tought, they will try to make you change the entire mother board (280€), but if you insist they will "find a way" to install the correct software in your phone and leave it as if it was new
SIeniuss said:
But how to start from 0 without any recovery? To install new system we need recovery, to install recovery we need to unlock bootloader and this is not possible on this flyme version
Click to expand...
Click to collapse
if you or someone else needs,
https://forum.xda-developers.com/meizu-pro-5/how-to/tutorial-restore-hard-bricked-lost-t3838461
here is solution.
woolikum said:
if you or someone else needs,
https://forum.xda-developers.com/meizu-pro-5/how-to/tutorial-restore-hard-bricked-lost-t3838461
here is solution.
Click to expand...
Click to collapse
Yeah, I found it earlier. It works. Pro 5 is alive
Wysłane z mojego Mi Note 2 przy użyciu Tapatalka