Related
I'm having a problem rooting my Nexus One (I have also read the newbie FAQ and searched the forum to no avail) - I have followed the instructions listed on the androidandme site.
When I try to unlock using fastboot I get this returned:
C:\....\Desktop\android-sdk-windows\tools>fastboot oem unlock
... INFOErasing userdata...
FAILED (status read failed (Too many links))
When I start the phone in fastboot mode it now says *** UNLOCKED *** at the top of the screen. I then flashed Amon-Ra's recovery image, as below:
C:\....\Desktop\android-sdk-windows\tools>fastboot flash recovery recovery-
RA-nexus-v1.6.2.img
sending 'recovery' (3954 KB)... OKAY
writing 'recovery'... OKAY
I assumed everything was going to be fine despite the issues unlocking. On trying to boot into recovery mode all I get is a screen with an exclamation mark and the android robot.
On turning the phone on as usual it seems that I can not run "Root required" apps such as the N1 torch.
I have tried running the OEM unlock command again but it seems to think that it has worked, as below:
C:\....\Desktop\android-sdk-windows\tools>fastboot oem unlock
... INFODevice was already unlocked!
OKAY
It would seem from the newbie guide that I still need to flash the recovery image but that seems to be going fine. I can't see that I've messed up so far so is there some way to "unroot" my phone or go through the OEM unlock process again?
Thanks.
You already unlock your bootloader, now put your rom of choice in the root of your sdcard, now flash again
AmonRa recovery, but this time don't reboot, after you you flash the recovery, flash the rom, and reboot.Now you should have su permition. Remember to nandroid backup before flashing the rom.
jongie123 said:
You already unlock your bootloader, now put your rom of choice in the root of your sdcard, now flash again
AmonRa recovery, but this time don't reboot, after you you flash the recovery, flash the rom, and reboot.Now you should have su permition. Remember to nandroid backup before flashing the rom.
Click to expand...
Click to collapse
I tried this, but still don't have root permissions - any thoughts?
I have read and searched and read some more and searched some more, and now just need some help...
Thanks in advance.
2 options, either install superboot from the Modaco's site to gain su, or flash Cyanogen's google adon.
jongie123 said:
2 options, either install superboot from the Modaco's site to gain su, or flash Cyanogen's google adon.
Click to expand...
Click to collapse
I suggest One thing. Pay 15.47 american Usd, at Online Kitchen for Modaco, Viola, Your done, always rooted.. Always Su'd up..
The Bootloader is simple on a windows machine, and so is root.. On Modaco's site there is a whole tutorial on this.. Plus search the threads, a whole ish load too..
i"d pay the 15.47.. Just Nike it, Just do it.. It's so much easier.. Just click-click, bake, download, flash, done..
Go..Go..!
jongie123 said:
You already unlock your bootloader, now put your rom of choice in the root of your sdcard, now flash again
AmonRa recovery, but this time don't reboot, after you you flash the recovery, flash the rom, and reboot.Now you should have su permition. Remember to nandroid backup before flashing the rom.
Click to expand...
Click to collapse
Thanks, I managed to flash the custom ROM this way, however I can't boot into recovery mode unless I boot from fastboot. Is this to be expected or should I be able to just turn on the phone, unconnected to the computer, while holding volume-down and boot into recovery mode?
If you just need root, get 'superboot'. It needs to be flashed to the "boot" partition (after unlocking the bootloader).
What it does is copy the root files to the data ROM and sets up permissions the first time the phone is booted (runs some sort of script I guess).
Link to superboot (free), make sure you get the right version:
http://android.modaco.com/content/g...erd79-epe54b-superboot-rooting-the-nexus-one/
look up "get root back".... Try these commands via ADB:
adb remount
adb shell chmod 6755 /system/xbin/su
....This should "fix_permision" and get you root back, IF you ever had it....
papermonk said:
Thanks, I managed to flash the custom ROM this way, however I can't boot into recovery mode unless I boot from fastboot. Is this to be expected or should I be able to just turn on the phone, unconnected to the computer, while holding volume-down and boot into recovery mode?
Click to expand...
Click to collapse
Using adb you can issue "adb reboot recovery" and wind up in recovery mode. You can also hold down the power button and trackball (connected or disconnected from the computer) and enter fastboot. From there, select bootloader and then recovery.
I am trying to unlock g1 but it fails showing "too many links". It does not do anything else.
sadhuKashmir said:
I am trying to unlock g1 but it fails showing "too many links". It does not do anything else.
Click to expand...
Click to collapse
If you are rooting a G1, correct me if I am wrong, but couldn't you just use one of the one click root methods?
I thought all of the patches denying one click root were contained in official FW's of GB and the G1 did not get it.
[Q] From TWRP back to stock Recovery & locked Bootloader, keeping root & Custom ROM?
Hey everyone,
around new years eve I found out that the Android Device Manger's remote wipe is not secure enough for my needs, as it doesn't wipe the data (pictures, app data etc.) on the virtual "sdcard" of the HTC One's storage. So a potential thief could easily access my Custom Recovery and simply by flashing a custom ROM gain access to the data.
I described the problem in more detail over here: http://forum.xda-developers.com/showthread.php?t=2598154
While unlocking a friend's phone I noticed that during the "fastboot oem unlock" procedure all data is wiped from the device. Something I totally forgot about.
This behavior is exactly what I want if my device gets stolen.
I can accept the hassle to deal with a temporary custom recovery or ways to perform an online nandroid, without the comfort of a Custom Recovery and having to lock the Bootloader again after every Custom ROM upgrade. (Yes, it will be a pain in the b*ttocks, but I want my data to be inaccessible.)
What do I have:
HTC One (international GSM version)
HTCdev.com unlocked
SuperCID
TWRP as Custom Recovery
Rooted CustomRom (SinLess in my case) installed
What I want:
Bootloader to be locked (so that you can't simply flash a Custom Recovery)
Stock Recovery (so that you can't simply flash a Custom ROM)
being able to make a nandroid backup, before unlocking again
keeping root and the Custom ROM
keeping SuperCID (req. for SinLess)
I don't want to make a mistake, so I am asking for some guidance. :angel:
I am assuming correctly that just flashing the Stock Recovery image is enough to get rid of TWRP?
I know that this temporary loading of a Recovery was a thing some time ago (HTC Desire), but I haven't looked into it for years now.
Is this still possible and how do I do it? Does this allow me to perform a nandroid backup with a locked bootloader?
Otherweise: If my bootloader is locked and my recovery reverted to stock, is there a way to nandroid backup my HTC One? I know about the App "Online Nandroid" (Play Store Link) that allows to perform a nandroid backup on a rooted phone without booting to recovery. Does it work with the HTC One?
What happens if I "relock" this htcdev.com unlocked phone? Will I simply be able to use "fastboot oem unlock" (followed by a full wipe) to unlock the bootloader again? Or are there more strings attached, like requiring htcdev.com again or any other problems?
Is the CID setting affected by any of this?
Am I missing something else?
Will the following routine be my way to go if I want to flash something (ROM, Kernel etc.)?
Backup Apps: Titanium Backup
Perform full nandroid Backup (App: Online Nandroid?)
Pull nandroid Backup, Titanium Backup Files and all Data from /sdcard/
Unlock phone --> result: full wipe of device (no big deal, as everything is backed up)
Flash Custom Recovery
Push Installation files for (rooted) Custom ROM, Kernel etc.
Push Titanium Backup Files
Install (rooted) Custom ROM, Kernel etc.
Boot Phone, set it up as usual and restore Titanium Backup
Push Data back to /sdcard/
Flash Stock Recovery
Relock Bootloader
Is this correct?
Or did I miss something?
Thanks in advance
noone? :angel:
I would highly appreciate any guidance on this. Thanks in advance
spaboleo said:
noone? :angel:
I would highly appreciate any guidance on this. Thanks in advance
Click to expand...
Click to collapse
Well, instead of doing what ur trying to do, you can encrypt the phone. A full phone encryption will prevent any changes made to any of the phone partitions. Thus, a ROM cannot be flashed in TWRP recovery, which serves your purpose and is easier than what u mentioned. However, decryption will factory reset the phone.
To answer your points:
1. Yes, flashing the Stock Recovery image will get rid of TWRP. But, im not 100% sure whether the ROM will work properly on stock recovery
2. You can definitely load a recovery without flashing it. Not tried on a locked bootloader. Sorry
3. Not sure whether the Root will be maintained after locking the bootloader and flashing stock recovery. If it is, then the Online Nandroid will definitely work
4. No strings attached. oem unlock will definitely do the trick
5. Nope, u will still be S-OFF. No CID is changed
spaboleo said:
no one?
Click to expand...
Click to collapse
Since you have s-off just use revone to unlock the bootloader without wiping data.
Procedure to lock things down:
Code:
fastboot flash recovery stock_recovery.img
fastboot oem lock
Procedure to return to unlocked/custom recovery:
Code:
adb push revone /data/local/tmp
adb shell
su
cd /data/local/tmp
chmod 755 revone
./revone -u
reboot bootloader
fastboot flash recovery twrp_recovery.img
You could also do revone with file explorer and terminal emulator and then flash TWRP directly in the OS using Flashify. This would allow you to return to unlocked with custom recovery without needing a computer.
raghav kapur said:
Well, instead of doing what ur trying to do, you can encrypt the phone. A full phone encryption will prevent any changes made to any of the phone partitions. Thus, a ROM cannot be flashed in TWRP recovery, which serves your purpose and is easier than what u mentioned. However, decryption will factory reset the phone.
To answer your points:
1. Yes, flashing the Stock Recovery image will get rid of TWRP. But, im not 100% sure whether the ROM will work properly on stock recovery
2. You can definitely load a recovery without flashing it. Not tried on a locked bootloader. Sorry
3. Not sure whether the Root will be maintained after locking the bootloader and flashing stock recovery. If it is, then the Online Nandroid will definitely work
4. No strings attached. oem unlock will definitely do the trick
5. Nope, u will still be S-OFF. No CID is changed
Click to expand...
Click to collapse
Thank you
Well I looked into encryption and it would require to use a PIN or Password lock instead of the Patternlock I prefer.
There was some mod that derived a PIN from a pattern input to work around this limitation, but I don't think it's the best idea to fiddle around with system files of that level.
But after reacing cschmitt's post, about the fact that there is a way to unlock the bootloader without wiping, my whole thoughts from the initial post are pointless
I guess using Android encryption is the only way.
Is it possible to use phone encryption together with location-based (wifi-based) disabling of the encryption using the "SecureSettings Plugin" for Tasker?
cschmitt said:
Since you have s-off just use revone to unlock the bootloader without wiping data.
Procedure to lock things down:
Code:
fastboot flash recovery stock_recovery.img
fastboot oem lock
Procedure to return to unlocked/custom recovery:
Code:
adb push revone /data/local/tmp
adb shell
su
cd /data/local/tmp
chmod 755 revone
./revone -u
reboot bootloader
fastboot flash recovery twrp_recovery.img
You could also do revone with file explorer and terminal emulator and then flash TWRP directly in the OS using Flashify. This would allow you to return to unlocked with custom recovery without needing a computer.
Click to expand...
Click to collapse
Wow! Thanks for pointing that out.
So the bootloader lock does not offer the sufficient protection that I am looking for
Unless...I return to S-On each and every time a I want to flash a rom or an Update.
Can I be sure that with S-On revone does not work to unlock the bootloader without wiping?
(edit: Warning Comment: don't do that...read below)
Thanks everyone
spaboleo said:
Thank you
Well I looked into encryption and it would require to use a PIN or Password lock instead of the Patternlock I prefer.
There was some mod that derived a PIN from a pattern input to work around this limitation, but I don't think it's the best idea to fiddle around with system files of that level.
But after reacing cschmitt's post, about the fact that there is a way to unlock the bootloader without wiping, my whole thoughts from the initial post are pointless
I guess using Android encryption is the only way.
Is it possible to use phone encryption together with location-based (wifi-based) disabling of the encryption using the "SecureSettings Plugin" for Tasker?
Wow! Thanks for pointing that out.
So the bootloader lock does not offer the sufficient protection that I am looking for
Unless...I return to S-On each and every time a I want to flash a rom or an Update.
Can I be sure that with S-On revone does not work to unlock the bootloader without wiping?
Thanks everyone
Click to expand...
Click to collapse
Nope, sorry. Remote encryption is impossible. You will need to manually choose the encryption option in security settings
P.S. Please hit the THANKS button if you think I helped you
spaboleo said:
Wow! Thanks for pointing that out.
So the bootloader lock does not offer the sufficient protection that I am looking for
Unless...I return to S-On each and every time a I want to flash a rom or an Update.
Can I be sure that with S-On revone does not work to unlock the bootloader without wiping?
Click to expand...
Click to collapse
The locked bootloader still offers the same level of protection. Unlocking via fastboot still wipes data, and the only way to unlock it via revone (which does not wipe data) is to be booted into the OS, which is protected by your password/PIN/pattern lock. (You might want to disable ADB while not using it, but in current versions ADB require authorization before it will connect to a new computer, and that would require unlocking your device with the password/PIN/pattern in order to approve the connection.)
If you have a locked bootloader with stock recovery it's not possible to use revone to unlock the bootloader via fastboot or adb, so you're still protected.
You cannot use revone to unlock bootloader if s-on.
An whatever you do do not go back to s-on.
cschmitt said:
The locked bootloader still offers the same level of protection. Unlocking via fastboot still wipes data, and the only way to unlock it via revone (which does not wipe data) is to be booted into the OS, which is protected by your password/PIN/pattern lock. (You might want to disable ADB while not using it, but in current versions ADB require authorization before it will connect to a new computer, and that would require unlocking your device with the password/PIN/pattern in order to approve the connection.)
If you have a locked bootloader with stock recovery it's not possible to use revone to unlock the bootloader via fastboot or adb, so you're still protected.
You cannot use revone to unlock bootloader if s-on.
An whatever you do do not go back to s-on.
Click to expand...
Click to collapse
I was initially S-OFF. I had to S-ON the phone to give it for warranty repair. I can simply use Rumrunner to S-OFF the phone again right? Or are there any other complications?
Thank you
raghav kapur said:
I was initially S-OFF. I had to S-ON the phone to give it for warranty repair. I can simply use Rumrunner to S-OFF the phone again right? Or are there any other complications?
Click to expand...
Click to collapse
There have been a number of cases of going back to s-on with locked bootloader and then not being able to unlock the bootloader again or regain root, so could not s-off again.
cschmitt said:
The locked bootloader still offers the same level of protection. Unlocking via fastboot still wipes data, and the only way to unlock it via revone (which does not wipe data) is to be booted into the OS, which is protected by your password/PIN/pattern lock. (You might want to disable ADB while not using it, but in current versions ADB require authorization before it will connect to a new computer, and that would require unlocking your device with the password/PIN/pattern in order to approve the connection.)
If you have a locked bootloader with stock recovery it's not possible to use revone to unlock the bootloader via fastboot or adb, so you're still protected.
You cannot use revone to unlock bootloader if s-on.
An whatever you do do not go back to s-on.
Click to expand...
Click to collapse
Thank you!
I thought the revone command was operable via fastboot/adb from the bootloader as well.
That is good news.
So one question remains.
Is there a way to access data from the stock recovery (maybe locating via "adb shell ls..." and then using "adb pull...") when s-off with a locked bootloader?
Assuming adb is turned off in the OS (developer options) if not used?
If this isn't possible this seems to be the perfect solution
I thank you sincerely!
spaboleo said:
So one question remains.
Is there a way to access data from the stock recovery (maybe locating via "adb shell ls..." and then using "adb pull...") when s-off with a locked bootloader?
Assuming adb is turned off in the OS (developer options) if not used?
Click to expand...
Click to collapse
All that's available in stock recovery in the ability to flash an HTC signed zip (official OTA, for example) and to factory reset.
There is no backup/restore/adb access/file manager like in a custom recovery.
Perfect :good: :laugh:
Sorry for asking that many questions, but as user the motto is "better safe than sorry".
I unlocked and s-offed my HTC One around June-August 2013 and besides a quick TWRP update here and there and a monthly ROM upgrade there was absolutely no need to fiddle around with it more.
Aftermarket development has become that reliable that it's actually possible to find a good "set it and forget it" daily driver setup.
And since I am not a developer and don't deal with those questions on a regular basis, I'm always not 100% sure if I get all the facts right.
Thanks for helping me out with this one!
I'm going to try it next weekend or next week: Going to backup my data and simulate a potential theft with the locked bootloader and reverted to stock recovery. Remote-Wiping the device, unlocking the bootloader conventionally via fastboot and making sure that this wipes all user-data on the phone. And then I'm going to give that booted into OS, revone unlock a try and simulate a potential rom upgrade, just as you described it.
Right now I just can't risk my daily driver phone, as I wouldn't have the time to set it up again.
Thanks for your extended help
Finally feeling secure again on Android.
I flashed the decryption img file and then did ADB back to stock including system, cache, etc, and now my phone is bricked and won't let me in it or the bootloader because its not encrypted. I want my phone back 100% stock now with encryption please anyone let me know how. I know how to ADB back to stock just not back to stock with encrypted. I was using my phone fine after ADB to stock until I rebooted and tried flashing TWRP+Root, then it messed up and I can't get in it.
imablackhat said:
I flashed the decryption img file and then did ADB back to stock including system, cache, etc, and now my phone is bricked and won't let me in it or the bootloader because its not encrypted. I want my phone back 100% stock now with encryption please anyone let me know how. I know how to ADB back to stock just not back to stock with encrypted. I was using my phone fine after ADB to stock until I rebooted and tried flashing TWRP+Root, then it messed up and I can't get in it.
Click to expand...
Click to collapse
ADB won't help you in this situation. You need to use fastboot and flash the factory image. Power off your device and boot directly into bootloader holding power and volume down simultaneously. Once in bootloader, connect to PC, navigate to your platform tools folder, (or if you have ADB/fastboot set as a path environment) open a command window and type:
fastboot devices
If your serial number comes up, you may proceed to flashing the factory image. Those instructions are here:
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
I did this fastboot adb back to stock with all the proper images, and then I went to install custom recovery and root after the restore and now I'm locked out of my device because of the no encryption??? what am I missing
imablackhat said:
I did this fastboot adb back to stock with all the proper images, and then I went to install custom recovery and root after the restore and now I'm locked out of my device because of the no encryption??? what am I missing
Click to expand...
Click to collapse
What do you mean locked out? Is TWRP asking for a password? Or is your bootloader locked?
twrp is asking for a password an when I try and boot into system it says unencrypted and only shows the power off button from there, it knows its still unencrypted.
imablackhat said:
twrp is asking for a password an when I try and boot into system it says unencrypted and only shows the power off button from there, it knows its still unencrypted.
Click to expand...
Click to collapse
Post #2 in the TWRP thread.
http://forum.xda-developers.com/showthread.php?p=56891965
so if I enter the default password in TWRP it will unlock my Recovery and I'll be able to reboot system and my phone will be normal again?? and encrypted?, I don't want a password on TWRP or on my phone.
entering the password works for TWRP and thats fine but I still cannot access my phones system when restarting, it comes up and says encryption unsuccessful, and i can only restart.
imablackhat said:
entering the password works for TWRP and thats fine but I still cannot access my phones system when restarting, it comes up and says encryption unsuccessful, and i can only restart.
Click to expand...
Click to collapse
Flash a ROM in TWRP.
Just flash the stock factory image and be done with it.. Do NOT relock the bootloader yet.
rootSU said:
Just flash the stock factory image and be done with it.. Do NOT relock the bootloader yet.
Click to expand...
Click to collapse
You have set a standard that we all need to follow. i.e. always including that last sentence.
Hi guys,
I am kind of stuck here.
I am using the xtrasmooth rom with the elemental x kernel (Marshmallow) and everything worked fine. Today I decided to add a little more security, so in the security settings I required a password when starting up android. I had been using the feature a while ago on android 5.x and everything worked fine.
Somehow my phone crashed today and now I am stuck on bootloop. It is not even asking me to enter a password.
However, I can access the recovery (TWRP) normally after entering my password to decrypt storage. I tried to wipe system and restore a backup. Still no success. I did a fresh clean install but no sucess again. It's always stuck on bootloop.
I don't want to factory reset or flash the complete stock image, since I do not want to lose my data. I tried to active ADB Sideload in TWRP, but somehow that is stuck at "starting adb" after cancels after a while with no success.
Do you guys maybe have an idea how to fix the problem? I guess I would need to disable the password but I do not know how to do that without an functioning rom.
Many thanks for your help!!
Reboot to your bootloader and use fastboot to flash
Sent from my Nexus 6 using Tapatalk
stupid me. That would have worked too.
I just connected my phone to the computer using twrp, used the file browser to push a file to the phone (regular storage) and installed another Light rom that is close to stock.
Everything worked fine. Must be a ROM or Kernel Issue. I will report to the according thread in this forum.
Thanks!!
I made a huge mistake when I installed Stock ROM using TWRP. I went from stock to Custom ROM as I didn't know my Leeco password.Now neither I am able to get past the login screen nor able to get my device to detect in adb ITS FRESH DEVICE NOW.Can anyone help me in Fixing this?
Problems here:-
1. On stock ROM stuck on Leeco account login which I cant enter the password of.
2. on stock recovery dont have TWRP
3. WANT MY PHONE TO LIVE
4. Fastboot accessible.
I need to use the device whether with stoc rom or any custom rom.
Will doing hard reset help ?
Aaditya21396 said:
I made a huge mistake when I installed Stock ROM using TWRP. I went from stock to Custom ROM as I didn't know my Leeco password.Now neither I am able to get past the login screen nor able to get my device to detect in adb ITS FRESH DEVICE NOW.Can anyone help me in Fixing this?
Problems here:-
1. On stock ROM stuck on Leeco account login which I cant enter the password of.
2. on stock recovery dont have TWRP
3. WANT MY PHONE TO LIVE
4. Fastboot accessible.
I need to use the device whether with stoc rom or any custom rom.
Will doing hard reset help ?
Click to expand...
Click to collapse
Please execute the command:-
format userdata
from pc in fastboot mode