Related
Hi guys,
I need your advice related to rooting my Nexus phone I got from Google Play.
I will not install any custom ROM's, I simply need to spoof the carrier to T-Mobile, when I'm in Canada.
That said, I looked at few tutorials and from all of them, this one is mostly recommended:
http://forum.xda-developers.com/showthread.php?t=1529058
Before I proceed, I need your opinion about the tutorial and also if is possible to run on my phone just BusyBox, while rooted.
Thank you for your help.
To run root without CWM...
Simply uze the command "fastboot boot RECOVERYNAME.img" rather than the one in the guide.
This won't write a custom recovery to your phone...but boot into it one time only.
Jubakuba said:
To run rooted...
Simply uze the command "fastboot boot RECOVERYNAME.img" rather than the one in the guide.
Click to expand...
Click to collapse
Thank you. I'll work on it and let you know guys how it went.
Everything went very smooth, no issues. Well the hardest part was to get the right ADB drivers, as I did not wanted to install unsigned drivers. I'm going to work now, will post the drivers info when I come back. For reference, I have now root without CWM.
If I decide to revert back to stock, what is procedure?
I have the bootloader locked now, so I guess opening it again will erase everything including the root files. Let me know please.
Edit: To get the drivers rolling in Windows 7 64bits Ultimate, I used this tutorial.
TECK said:
Everything went very smooth, no issues. Well the hardest part was to get the right ADB drivers, as I did not wanted to install unsigned drivers. I'm going to work now, will post the drivers info when I come back. For reference, I have now root without CWM.
If I decide to revert back to stock, what is procedure?
I have the bootloader locked now, so I guess opening it again will erase everything including the root files. Let me know please.
Click to expand...
Click to collapse
As long as you have root...
http://forum.xda-developers.com/showthread.php?p=27878074
Will unlock/lock without wiping.
And as far as returning to stock...you haven't modified much thus far.
So deleting busybox and then superuser will work...if you haven't modified any system files.
Or you could always flash the stock images (this does erase your "SDcard" and everything will be back to an-out-of-the-box state).
https://developers.google.com/android/nexus/images
Jubakuba said:
Or you could always flash the stock images (this does erase your "SDcard" and everything will be back to an-out-of-the-box state).
https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
Thank you sir. Can you please let me know what is the list of commands?
Edit: I got them from the flash-all.sh shell script.
Nexus Images: https://developers.google.com/android/nexus/images
CWM: http://www.clockworkmod.com/rommanager/
Superuser: http://hosted.androidsu.com/superuser/
Root Device
1) Unlock the bootloader (if locked):
---
adb reboot bootloader
fastboot oem unlock
2) Install Supersuer + Root (match the file names with the ones downloaded):
---
adb push Superuser-3.1.3-arm-signed.zip /sdcard/
adb reboot bootloader
fastboot boot recovery-clockwork-6.0.1.0-maguro.img
Flash Superuser: On device, select "install zip from sdcard", then "choose zip from sdcard" and select "Superuser-3.1.3-arm-signed.zip". Confirm install then "+++++Go Back+++++" and "reboot system now".
3) Lock the bootloader (optional):
---
adb reboot bootloader
fastboot oem lock
Stock Device
1) Unlock the bootloader (if locked):
---
adb reboot bootloader
fastboot oem unlock
2) Install the image files (match the file names with the ones downloaded):
---
fastboot reboot-bootloader
fastboot flash bootloader bootloader-maguro-primelc03.img
fastboot reboot-bootloader
fastboot flash radio radio-maguro-i9250xxlf1.img
fastboot reboot-bootloader
fastboot -w update image-takju-jro03c.zip
3) Lock the bootloader:
---
adb reboot bootloader
fastboot oem lock
http://forum.xda-developers.com/showthread.php?t=1626895
Efrant's guide is perfect here.
I got them from the shell script (see above), thanks.
TECK said:
Edit: I got them from the flash-all.sh shell script.
Click to expand...
Click to collapse
Exactly, its that easy.
For the last two days I tried to revert my HTC One V back to stock android. As in, the way I got it when I first booted it up. I experienced that this progress was pretty difficult. Maybe this was because I was used to the AOSP niceness of Google's LG NExus 4 or because HTC made it very hard to say the least to downgrade/upgrade to their own stock ROM.
I may not have the original sources for all files because I deleted some original .zip files and only have the extracted files.
First off, I wouldn't do any of this if you have important files on your device, I wiped everything from my phone a dozen of times in the process and it didn't care because I didn't had any important files on their.
Alright, so what we want to achieve is to get to the latest version of HTC's RUU version "2.22.401.7". The RUU I could find was "2.22.401.1" so we're gonna have to d/l some OTA's later on via our device if everything is set up.
So obviously everyone who is trying to revert back has somewhere unlocked their bootloader by doing
fastboot oem get_identifier_token
and
fastboot flash unlocktoken Unlock_code.bin
Please remember this: ANY RUU will fail every single time if your device is LOCKED. It will ONLY work if it's unlocked or relocked.
So first off what we gonna have to do is relock/unlock our device. You can relock your device by going into fastboot[1] mode and running the following command:
fastboot oem lock
Myself have expierenced an error that told me it "FAILED". Please reboot your bootload:
fastboot reboot-bootloader
And check the locked status at the top. If it says "RELOCKED", succes! If it didn't, retry the command above.
Next, we're relocked so we can run the RUU. Please look at the text file at the RUU source [2] for the download links. In this .zip file are the files inside the RUU wizard. You can run the wizard by executing "ARUWizard.exe" and you can view the contents of the actual ROM in "rom.zip extracted" and you can find the original ROM in "rom.zip". Since these are the files the wizard will be using (except rom.zip extracted folder) please do not touch them.
Alright, so we've got the extracted files of the RUU and we're ready to update. Please boot your phone in fastboot mode and connect it to your computer via USB. Now run the "ARUWizard.exe" file and let it update. I couldn't think of a situation where this could go wrong, so please ask below if you face any problems.
The wizard will flash stock radio, recovery andsystem.img (the actual ROM you all know) so by doing this you lose your custom revovery.
When your phone boots up you've gotta go through 3-4 updates till it's on "2.22.401.7".
I recommend not flashing a custom recovery right away because when you install/download OTA updates it isn't able to flash it right. In the meantime if you want root[3] use this command:
adb install -s supersu.apk
When you're on the latest version you have to unlock your bootloader, otherwise you cannot flash a custom recovery or kernel or whatever. You can do this via HTC[4]. I think there are enough guides on how to do this, but in short:
- create an account with an legitimate email address
- Select "all other supported devices" from the list
- follow on screen instructions.
Seriously everything is on there, HTC made it really easy.
If you want to install a custom recovery I recommend using TWRP[5]. Please flash TWRP by booting into fastboot and running the following command:
fastboot flash recovery twrp_recovery.img
Troubleshooting
There isn't really a lot that can go wrong if you do this. But when you're stuck on a screen or you think your device is "bricked" or stuck in a bootloop do these things:
- First off, hold the power and volume down button till the device goes down. If it's down, release the buttons and then hold the same buttons again till you're in bootloader
If that doesn't work do either of these commands (make sure your device is connected via USB, hehe)
Make sure fastboot and/or adb is working first:
fastboot devices
adb devices
If fastboot is working:
fastboot reboot-bootloader
If ADB is working:
adb reboot bootloader
adb reboot recovery
If you have any questions, please ask me. I did a dozen of things these two days, I may forgotten something because I did a crapload of things all at once.
Cheers!
Sources:
[1] http://www.technewscentral.co.uk/enter-fastbootbootloader-mode-htc-one/id_7930
[2] http://rg.to/file/aaca8c0c03e655d6df78242b4cea931b/hov.zip.html
http://ul.to/dfmg5dnw
https://mega.co.nz/#!wBcUiIxD!uIkyqZLgFErSItBTu3K7RY3eyUmXVUg60rcB-B-QRWE
Please request other providers below.
[3] http://download.chainfire.eu/supersu
[4] http://www.htcdev.com/bootloader
[5] http://techerrata.com/browse/twrp2/primou
tl;dr
unlock bootloader -> run RUU -> done
This is great and all, but is this for the PRIMO-C or U? US version? etc... etc..
I have rooted my device using towel root which doesn't unlock the boot loader. I then used the twrp manager to install custom recovery. I am wondering how to restore everything back to factory as all the tutorials I have seen so far require an unlocked boot loader. Any help will be appreciated, thank you.
Flash a stock r for your phone
swagg blasted from TMO LG G3
jailbreakkid23 said:
Flash a stock r for your phone
swagg blasted from TMO LG G3
Click to expand...
Click to collapse
If I download a stock image from google and flash it from my nexus 7 using twrp will everything be restored to factory settings?
If the boot loader is locked does that mean I can just do a normal factory reset on the device and it will remove the recovery and root?
fastboot
Jordydaman said:
If the boot loader is locked does that mean I can just do a normal factory reset on the device and it will remove the recovery and root?
Click to expand...
Click to collapse
you have to install stock ROM by adb mode using fastboot command
you can't flash stock ROM via custom recovery.
@SidDev said:
you have to install stock ROM by adb mode using fastboot command
you can't flash stock ROM via custom recovery.
Click to expand...
Click to collapse
Would you mind finding a link for me ? I have never encountered this before as I have always unlocked the bootloader to root but this time I used towel root which was different as explained above.
Doesn't the boot loader have to be unlocked to flash a ROM via adb?
try this and press thanks
Jordydaman said:
Doesn't the boot loader have to be unlocked to flash a ROM via adb?
Click to expand...
Click to collapse
nope,
Step 1: Download the ADB/Fastboot files and the
USB drivers for Windows based PC first. The the
latest factory image for your Nexus device can be
downloaded directly from Google’s website .
ADB/Fastboot – Mac , Windows
USB drivers for Windows
Extract the contents of the ADB/Fastboot ZIP file
inside a new folder called ‘google’ on your desktop.
Extract and transfer the contents of the factory
image inside this folder as well. The list of files will
include a ZIP file containing the codename of your
Android device, two files with “flash-all” names, and
a bootloader image file. All the extracted contents of
the factory image should be inside the same folder
as the ADB and Fastboot file, otherwise you will get
a file not found error.
Make sure to install the ADB drivers as well if you
are running a Windows based PC.
Step 2: Now, reboot your Nexus device in bootloader
mode. This is usually done by switching off the
device, and pressing the Volume down + Volume Up
+ Power button simultaneously. If that does not
work, try the Volume down + Power button
combination.
After the device has booted into bootloader mode,
connect it to your PC.
Step 3: Open a new Terminal or Command Prompt
window, and navigate to the ‘google’ folder that you
created in Step 1. Before we start flashing the
factory image, we need to make sure that your
Nexus device is being detected by the PC.
fastboot devices
If you are using a Mac, then you need to prefix a “./”
before every Fastboot command. So, the above
command will look something like this on a Mac -:
./fastboot devices
The above command should confirm if your device is
indeed being detected by your PC or not. If it is,
then proceed to the steps below. If not, repeat the
steps above again. Make sure that you have properly
installed the drivers and are inside the correct
folder.
If you are running Windows, copy-paste the following
command in the command prompt window -:
flash-all.bat
On a Mac, copy-paste the following command -:
./flash-all.sh
The script will then automatically flash the full
factory image on your Nexus device. Once the
factory image has been flashed, your device will
automatically reboot. Keep in mind that the first boot
might take some time so please be patient.
If the flash-all.sh script gives you a fastboot not
found error on your Mac, open up the file in Text Edit
and add a “./” before every fastboot command.
The flash-all script included in the factory image
might not work for all. It has always been pretty
unreliable and has only worked once for me in the
last 2 years. If you are in the same boat as me, you
will have to flash each partition manually on your
device. This is slightly cumbersome though.
The command to manually flash a partition via
fastboot is “fastboot flash partition filename.img”. In
the factory image that you extracted in Step 1, you
will notice there is another ZIP file. Extract the
contents of that ZIP file inside the ‘google’ folder.
Now, its time to manually flash the partitions to your
Nexus device. We will first begin with the bootloader.
fastboot flash bootloader filename.img
Then, we will flash all other partitions. They don’t
necessarily need to be in the same order as I have
listed them below. The names of the image files in
the factory image will clearly indicate the partition
they are intended for as well.
fastboot flash boot filename.img
fastboot flash radio filename.img
fastboot flash recovery filename.img
fastboot flash userdata filename.img
fastboot flash system filename.img
Thank you very much I will try this today.
I couldn't flash all and when I flashed the bootloader it came up with failed bootloader is locked?
Enter this command to unlock the bootloader:
fastboot oem unlock
After unlocking, you can run flash-all.bat (or run manual fastboot commands to flash).
Hi guys, I hate to make a new post but I feel like I've exhausted all options. I'm getting a bootloop when flashing Viper 3.5.0 and ARHD 12.0. I have a T-Mobile GSM M9 with S-OFF . My bootloader currently locked. Here are my steps:
1. I've got Super CID
2. Flashed TWRP 2.8.7.0
3. Rooted
Then I wanted to put on a new rom:
4. Flashed different firmware from here: http://forum.xda-developers.com/one-m9/development/firmware-t3068243
I've tried 2.10.401.1 (International) / 2.7.531.6 (T-Mobile US) / 1.32.531.33 (T-Mobile US)
5. Flashed Viper 3.5.0 and AHD 12.0 with the wipe option after each firmware upgrade/downgrade. Each time I boot the phone up (no matter what firmware is used), Android will optimize all the apps, and it will sit at the Android setup screen for a second or two, and then just reboot. Android will optimize all apps again, I'll see the setup screen, and then the loop again.
Anybody have any suggestions? I'm sure I'm missing something simple. I don't need the bootloader unlocked since I have S-OFF, correct? Thanks in advance for any and all help!
Are you able to enter into twrp custom recovery? You can install the ROM zip from there. Other option would be the sideload method.
- Put in the rom you want to install into the same directory where the adb tool is. In your case custom rom isnt it? Rename it to something simple like rom.zip
- Shift+right click in the emtpy area where the ADB tool and your is and open the command prompt.
- Navigate through custom recovery > Advanced > ADB Sideload. Your phone should now be waiting for the rom you are about to send.
-Go back to your command prompt and type the following; adb sideload rom.zip
Note that the rom you are sending needs to be complete and have all the files needed in it.
Hi Nikolay82, thanks for the reply. I'm not having an issue flashing the ROM. The issue i'm experiencing is that my phone goes into an endless bootloop after the ROM is flashed.
sstrunks84 said:
Hi Nikolay82, thanks for the reply. I'm not having an issue flashing the ROM. The issue i'm experiencing is that my phone goes into an endless bootloop after the ROM is flashed.
Click to expand...
Click to collapse
Unlock your bootloader and try again. As far as I know the M9 prevents the system from booting correctly if the bootloader is locked and TWRP is installed.
The rom should flash the boot and fix the problem. As for unlocking your bootloader please check the following;
1. Register here; https://www.htcdev.com/
2. Once registered login and select the "Unlock Bootloader" > Get Started > Select your device.
3. If you do not see HTC One M9 listed, select Last option which is "All other supported Devices"
4. Click on "begin unlock bootloader"
5. Follow the instructions and open the command prompt where your ADB is and prepare phone for fastboot mode / download mode.
6. type in; fastboot oem get_identifier_token
7. You will now get a block of text, mark and copy only the area starting from <<< Identifier token start[block of code here] Identifier token end >>>> (mark also those <<<< and >>>>) c
8. Go back to the htc.dev where you logged in and paste in the code under "My device Identifier token" field and submit the query. Navigate to your e-email where they sent you the token and download file; Unlock_code.bin
9. In that mail you will also have a link to continue unlocking the bootloader process, click it,
10. Place the Unlock_code.bin file into the folder where your ADB tools are.
11. Open up the command prompt again and type in; fastboot flash unlocktoken Unlock_code.bin
12. New dialogue should appear asking you if you want to unlock. Please note that if you proceed everything on your phone will be wiped out, so make sure you backed up things you need.
13. Go back to bootloader mode and it should say "UNLOCKED". Same with download mode.
Thanks @Flippy498! Unlocking the bootloader did the trick!
So I tried to flash another rom by flashing TWRP and unlocking the bootloader, which worked and I then had installed Freedom Os. Then I locked the Bootloader to get the Message away, but know when you charge it or turn it on it is in an boot loop which repeats the Oneplus Logo what you normally see, but very short and after that it bobrates turns the screen off and it atart again. Or I can go into fastboot mode, but when I try to go into the recovery, it goes into the Boot Loop again. Is there a way to get the Original OS back? Ive already dopwnloaded it but I cant get in on there. Can you tell me how to fix it on my own?
[GUIDE] Mega Unbrick Guide for A Hard Bricked OnePlus 3 > METHOD 1
If you can access fastboot mode, connect the phone to a PC, then go to ADB and erase recovery using the command " fastboot erase recovery" and install TWRP 3.0.4-1 using the command " <fastboot flash recovery <recovery.zip/img> again.
Once you do that, boot into TWRP, go to wipe and wipe everything. Once you do that, transfer the stock OOS into the internal memory using copy-paste , then go to install , select the transferred file to install the OS or else go to advance setting in TWRP and select adb sideload and use the command "adb sideload <filename.zip>".
This should install the OS on the phone.
If you want to go complete stock, then you also need to install the stock recovery. Search the forum to get the relevent files or else you can download it from the OnePlus website and later on update to latest OS via OTA.
NEVER EVER LOCK THE BOOTLOADER , IF YOU'RE USING ANY ROM OTHER THAN STOCK OS AND STOCK RECOVERY
anup807 said:
If you can access fastboot mode, connect the phone to a PC, then go to ADB and erase recovery using the command " fastboot erase recovery" and install TWRP 3.0.4-1 using the command " <fastboot flash recovery <recovery.zip/img> again.
Once you do that, boot into TWRP, go to wipe and wipe everything. Once you do that, transfer the stock OOS into the internal memory using copy-paste , then go to install , select the transferred file to install the OS or else go to advance setting in TWRP and select adb sideload and use the command "adb sideload <filename.zip>".
This should install the OS on the phone.
If you want to go complete stock, then you also need to install the stock recovery. Search the forum to get the relevent files or else you can download it from the OnePlus website and later on update to latest OS via OTA.
NEVER EVER LOCK THE BOOTLOADER , IF YOU'RE USING ANY ROM OTHER THAN STOCK OS AND STOCK RECOVERY
Click to expand...
Click to collapse
Can you tell me how to go to adb? When doing it while being in fastboot I get the error "remote: Partition erase is not allowed"
revedar said:
Can you tell me how to go to adb? When doing it while being in fastboot I get the error "remote: Partition erase is not allowed"
Click to expand...
Click to collapse
Download Universal ADB software, download the latest version and install it.
TWRP 3.0.4-1
Official Oxygen OS 4.0.3
Official Recovery
Connect your phone to the PC and then navigate to installed folder, right click holding SHIFT key and select "Open command window here"
Inside command window type
adb devices
If all the drivers are installed properly, you should see you're device ID here.
then type
adb reboot bootloader
your phone will enter fastboot mode.
then type
fastboot devices
again you should see you're device ID here.
then follow the instruction , i've given earlier.
anup807 said:
Download Universal ADB software, download the latest version and install it.
TWRP 3.0.4-1
Official Oxygen OS 4.0.3
Official Recovery
Connect your phone to the PC and then navigate to installed folder, right click holding SHIFT key and select "Open command window here"
Inside command window type
adb devices
If all the drivers are installed properly, you should see you're device ID here.
then type
adb reboot bootloader
your phone will enter fastboot mode.
then type
fastboot devices
again you should see you're device ID here.
then follow the instruction , i've given earlier.
Click to expand...
Click to collapse
So i've downloaded the software, installed the driver and typed in cmd adb devices "adb devices List of devices attached" is returned, so it seems like there is going something wrong. Is it because the Driver is installed wrong or because "target reported max download size of 440401920 bytes
sending 'recovery' (22605 KB)...
OKAY [ 0.528s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.551s"
This is returned when trying to flash. Do I have to be in fastboot mode or something else to be able to follow your instructions? In Fast Boot is written that the Device State is locked and Secure Boot is enabled. I messaged Oneplus and hope they have a solution which can just unlock the Bootloader when being in fastboot mode, so everything is fine again. I hope you can help me, but I still wanna say thank your for now
Errr... fastboot can unlock the bootloader. fastboot oem unlock
emuandco said:
Errr... fastboot can unlock the bootloader. fastboot oem unlock
Click to expand...
Click to collapse
Thank you, but it dont works because i forgot to re-enable the oem modification and usb debugging in freedom os, maybe there is an option to do this without having this enabled but I didnt found it. So I wait for a helpful answer from somebody here or from Oneplus, I consider sending my smartphone to oneplus to let them repair it if I cant do it. Just saying that modding an S3, Asus transformer pad and nvidia shield is way easier.
never ever relock your bootloader while you in custom OS
oopstairs said:
never ever relock your bootloader while you in custom OS
Click to expand...
Click to collapse
Thank you for not helping me
revedar said:
Thank you for not helping me
Click to expand...
Click to collapse
Yeah I'm sorry I can't help you in your case. I'm just stating the fact. Sorry if I offended you.
Shouldn't it still be possible to reflash the properly signed official updates? TBH I never had such a problem and thus never had to cope with it. Same with recovery: http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3.img Try flashing this one with fastboot. It's the official one. By flashing this one you might fix your stuff over adb sideloading the official full update zips.
Try the unbrick guide provided in the 2nd post to your query. It should definitely help. Better contact OnePlus tech2 support and they'll flash your phone for you. They're really helpful.
emuandco said:
Shouldn't it still be possible to reflash the properly signed official updates? TBH I never had such a problem and thus never had to cope with it. Same with recovery: http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3.img Try flashing this one with fastboot. It's the official one. By flashing this one you might fix your stuff over adb sideloading the official full update zips.
Click to expand...
Click to collapse
I already tried to do this, but the console returns something like permission denied.
anup807 said:
Try the unbrick guide provided in the 2nd post to your query. It should definitely help. Better contact OnePlus tech2 support and they'll flash your phone for you. They're really helpful.
Click to expand...
Click to collapse
The MSM Software disconnects the smartphone while the process works
U cannot flash in adb while the bootloader is locked, u can not unlock the bootloader unless u can access ur OS, I am not sure y people was trying to get u to flash via fastboot the answer was provided to u in the 2nd post
^^^ This!
It's pretty much obvious fastboot flash will not work with a locked bootloader.
It's pretty obvious unlocking the bootloader will not work, while one can not access the OS.
Unbrick tool is the only option to bring it back to life, or sending it for RMA. If unbrick tool fails, try using different drivers and make sure it is connected with the stock cable (I've only tried with a Nilkin cable besides the stock one, which always failed at different stages during the process).
Not even sure drivers must be installed manually, I've never done that myself on Windows 10, as they were automatically installed (3 different's PC's, both on x86 and x64).
Which version of stock firmware did you last have? If it was 4.0.1 or earlier, then you can use
Code:
fastboot oem 4F500301
to issue a flash command even without unlocking the bootloader. If you are on that, then use that command and flash stock recovery and then flash stock zip.
rk2612 said:
Which version of stock firmware did you last have? If it was 4.0.1 or earlier, then you can use
Code:
fastboot oem 4F500301
to issue a flash command even without unlocking the bootloader. If you are on that, then use that command and flash stock recovery and then flash stock zip.
Click to expand...
Click to collapse
I had the most recent update installed. Is there a similar command at the moment?
revedar said:
I had the most recent update installed. Is there a similar command at the moment?
Click to expand...
Click to collapse
Don't think so.