Related
For people who cant excute flash all script
"Tells them of missing system ,recovery and user data "
U can do that by doing this:
Before runing the script u can use this codes when into bootloader (Before Executing Flash All Script)
Fastboot oem lock
Fastboot reboot bootloader
fastboot oem unlock
And Happy Flashing
I was wondering if this process is okay for updating to new versions using fastboot
Code:
1. Enable USB debugging and OEM unlock
2. Reboot into bootloader (volume-down + power)
3. fastboot flash bootloader {bootloader-shamu-xxx.img}
4. fastboot reboot-bootloader
5. fastboot flash radio {radio-shamu-xxx.img}
6. fastboot reboot-bootloader
7. fastboot flash boot boot.img
9. fastboot reboot-bootloader
10. fastboot flash system system.img
11. Boot into TWRP by selecting Recovery Mode on device and pressing power button
12. Flash supersu via TWRP (Install > Choose the zip package > swipe to confirm > main menu > reboot)
13. Reboot
Did I miss any steps or would I do something wrong with these steps?
Forerunner326 said:
I was wondering if this process is okay for updating to new versions using fastboot
Code:
1. Enable USB debugging and OEM unlock
2. Reboot into bootloader (volume-down + power)
3. fastboot flash bootloader {bootloader-shamu-xxx.img}
4. fastboot reboot-bootloader
5. fastboot flash radio {radio-shamu-xxx.img}
6. fastboot reboot-bootloader
7. fastboot flash boot boot.img
9. fastboot reboot-bootloader
10. fastboot flash system system.img
11. Boot into TWRP by selecting Recovery Mode on device and pressing power button
12. Flash supersu via TWRP (Install > Choose the zip package > swipe to confirm > main menu > reboot)
13. Reboot
Did I miss any steps or would I do something wrong with these steps?
Click to expand...
Click to collapse
youll have to unlock your bootloader again. but being rooted, why dont you just flash any of the rooted 5.1 stock roms or a 5.1 aosp rom? it would be much much easier.
simms22 said:
youll have to unlock your bootloader again. but being rooted, why dont you just flash any of the rooted 5.1 stock roms or a 5.1 aosp rom? it would be much much easier.
Click to expand...
Click to collapse
Why would I have to unlock the bootloader again if it is already unlocked? And I want to try using fastboot because it seems simple to me.
Forerunner326 said:
Why would I have to unlock the bootloader again if it is already unlocked? And I want to try using fastboot because it seems simple to me.
Click to expand...
Click to collapse
it is easy, enjoy
simms22 said:
it is easy, enjoy
Click to expand...
Click to collapse
So to reassure, the process I listed is good to use for updates?
Forerunner326 said:
So to reassure, the process I listed is good to use for updates?
Click to expand...
Click to collapse
yea, its fine, but you dont have to reboot the bootloader after each flash.
simms22 said:
yea, its fine, but you dont have to reboot the bootloader after each flash.
Click to expand...
Click to collapse
Rebooting the bootloader like this doesn't hurt correct?
Forerunner326 said:
Rebooting the bootloader like this doesn't hurt correct?
Click to expand...
Click to collapse
i wouldnt think so
simms22 said:
i wouldnt think so
Click to expand...
Click to collapse
What does rebooting the bootloader do?
Forerunner326 said:
What does rebooting the bootloader do?
Click to expand...
Click to collapse
just that, reboot the bootloader, nothing else. its been too long since i flashed a factory img! good thing too
Forerunner326 said:
Why would I have to unlock the bootloader again if it is already unlocked?
Click to expand...
Click to collapse
You don't.
Forerunner326 said:
Rebooting the bootloader like this doesn't hurt correct?
Click to expand...
Click to collapse
Doesn't hurt, no. You should reboot into the bootloader after flashing a bootloader and after flashing a radio, so that you are running those before you flash the other images. (Just flashing the bootloader doesn't start it up -- you need to reboot-bootloader to actually start the new bootloader.) It may not be necessary, but it is likely safer to flash new images when on the latest bootloader, just in case.
efrant said:
You don't.
Doesn't hurt, no. You should reboot into the bootloader after flashing a bootloader and after flashing a radio, so that you are running those before you flash the other images. (Just flashing the bootloader doesn't start it up -- you need to reboot-bootloader to actually start the new bootloader.) It may not be necessary, but it is likely safer to flash new images when on the latest bootloader, just in case.
Click to expand...
Click to collapse
Which is why I have "fastboot reboot bootloader" in place after the bootloader, radio, and boot image.
Forerunner326 said:
Which is why I have "fastboot reboot bootloader" in place after the bootloader, radio, and boot image.
Click to expand...
Click to collapse
It does absolutely nothing to boot into the bootloader after flashing the boot image, as the boot image doesn't "boot" in the bootloader. Only the bootloader and radio do.
efrant said:
It does absolutely nothing to boot into the bootloader after flashing the boot image, as the boot image doesn't "boot" in the bootloader. Only the bootloader and radio do.
Click to expand...
Click to collapse
Which means I can remove "fastboot reboot bootloader" after the boot image and nothing will be affected?
Forerunner326 said:
Which means I can remove "fastboot reboot bootloader" after the boot image and nothing will be affected?
Click to expand...
Click to collapse
Yes.
This is my method verified with 5.1.0 D and E variants, this will not wipe your device.
Download images from: https://developers.google.com/android/nexus/images#shamu
Extract all files to your comp including the main .tgz and the .zip inside that
{replace with actual file name}
Enable USB Debugging and OEM Unlock
Reboot into bootloader (vol-down + power) or adb reboot bootloader
fastboot flash bootloader {bootloader-shamu-xxx.img}
fastboot reboot-bootloader
fastboot flash radio {radio-shamu-xxx.img}
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash recovery recovery.img (optional if keeping TWRP or you can flash the latest TWRP here)
fastboot flash system system.img
fastboot flash cache cache.img
fastboot reboot (Or enter recovery and re-root if you kept TWRP)
efrant said:
Yes.
Click to expand...
Click to collapse
Is there anything else I should know before I flash any update files onto the device?
Forerunner326 said:
I was wondering if this process is okay for updating to new versions using fastboot
Code:
1. Enable USB debugging and OEM unlock
2. Reboot into bootloader (volume-down + power)
3. fastboot flash bootloader {bootloader-shamu-xxx.img}
4. fastboot reboot-bootloader
5. fastboot flash radio {radio-shamu-xxx.img}
6. fastboot reboot-bootloader
7. fastboot flash boot boot.img
9. fastboot reboot-bootloader
10. fastboot flash system system.img
11. Boot into TWRP by selecting Recovery Mode on device and pressing power button
12. Flash supersu via TWRP (Install > Choose the zip package > swipe to confirm > main menu > reboot)
13. Reboot
Did I miss any steps or would I do something wrong with these steps?
Click to expand...
Click to collapse
1 to 6 are good
7 fastboot flash system system.img
8 fastboot flash boot boot.img (stock or modified decrypted/custom kernel)
11, 12 13 are good.
gee2012 said:
1 to 6 are good
7 fastboot flash system system.img
8 fastboot flash boot boot.img (stock or modified decrypted/custom kernel)
11, 12 13 are good.
Click to expand...
Click to collapse
What about the cache image? Would it go after boot.img gets flashed? Or do I not worry about it?
This is what I have so far.
Code:
1. Enable USB debugging and OEM unlock
2. Reboot into bootloader (volume-down + power)
3. Connect to pc and load platform tools command window
4. fastboot flash bootloader {bootloader-shamu-xxx.img}
5. fastboot reboot-bootloader
6. fastboot flash radio {radio-shamu-xxx.img}
7. fastboot reboot-bootloader
8. fastboot flash system system.img
9 fastboot flash boot boot.img (stock or modified decrypted/custom kernel)
10. Boot into TWRP by selecting Recovery Mode on device and pressing power button
11. Flash supersu via TWRP (Install > Choose the zip package > swipe to confirm)
12. Reboot (Main menu > reboot)
You can do that after boot:
fastboot erase cache
fastboot flash cache cache.img
11, 12, 13.
I recently had to reinstall the android os due to something I did wrong, anyway my bootloader is relocked and I can't unlock it because s-on is active, and ontop of that I don't have it rooted because I just recently redid the OS. So basically I'm stuck here, any help would be greatly appreciated.
s-on still allows to unlock the bootloader
Turn on developer options and enable oem unlocking.
Then follow the steps
Step one
adb reboot download
Step two
fastboot oem get_identifier_token
Step three
go to htc-dev site input your code and get the unlock file e-mailed to you.
Step 4
again in download mode
do
fastboot devices to see if your device is in fastboot mode.
Step 5
fastboot flash unlocktoken unlock_code.bin
Step6
fastboot flash recovery twrprecovery.img
Step7
Download supersu flashable zip and copy to sd card
Step8
boot into twrp recovery using volume and power buttons. Select boot recovery from bootloader menu.
Step9
Install supersu zip in TWRP recovery.
Now you should be unlocked and rooted.
BigCountry907 said:
s-on still allows to unlock the bootloader
Turn on developer options and enable oem unlocking.
Then follow the steps
Step one
adb reboot download
Step two
fastboot oem get_identifier_token
Step three
go to htc-dev site input your code and get the unlock file e-mailed to you.
Step 4
again in download mode
do
fastboot devices to see if your device is in fastboot mode.
Step 5
fastboot flash unlocktoken unlock_code.bin
Step6
fastboot flash recovery twrprecovery.img
Step7
Download supersu flashable zip and copy to sd card
Step8
boot into twrp recovery using volume and power buttons. Select boot recovery from bootloader menu.
Step9
Install supersu zip in TWRP recovery.
Now you should be unlocked and rooted.
Click to expand...
Click to collapse
I'll give this a shot and get back to you, thanks!!
My phone can't boot . The display is " your device is corupt . It cant be trusted and will not boot after I root and install twrp, gapps , i have used the command "fastboot oem lock" "fastboot flashing lock" "fastboot oem relock" .
i can't unlock bootloader ( flasing unlock not allow )
my bootloader is lock
plz help me !
nil3m1 said:
My phone can't boot . The display is " your device is corupt . It cant be trusted and will not boot after I root and install twrp, gapps , i have used the command "fastboot oem lock" "fastboot flashing lock" "fastboot oem relock" .
i can't unlock bootloader ( flasing unlock not allow )
my bootloader is lock
plz help me !
Click to expand...
Click to collapse
You need to enable bootloader unlock through setting in developer option enable oem unlock, and then you can use the ' fastboot flashing unlock'
You can't root with locked bootloader as it will show an error message your device is corrupt,
At you situation now you should flash stock boot and then the phone will open and then you go to settings as i mentioned to enable oem unlock through developer option in settings
Fastboot unlock bootloader with long command, you will see it unlock temporarily till reboot, flash boot.img and recovery.img, reboot into recovery wipe data & cache, utilize USB otg to reinstall rom.
em902566 said:
You need to enable bootloader unlock through setting in developer option enable oem unlock, and then you can use the ' fastboot flashing unlock'
You can't root with locked bootloader as it will show an error message your device is corrupt,
At you situation now you should flash stock boot and then the phone will open and then you go to settings as i mentioned to enable oem unlock through developer option in settings
Click to expand...
Click to collapse
-I cannot boot into os to enable oem unlock ,I can't go into recovery
Hope you will help me,thank you
SuperDroidMe said:
Fastboot unlock bootloader with long command, you will see it unlock temporarily till reboot, flash boot.img and recovery.img, reboot into recovery wipe data & cache, utilize USB otg to reinstall rom.
Click to expand...
Click to collapse
I used the command "fastboot oem nubia_unlock NUBIA_NX629J" ,"fastboot flashing unlock" , command but it reported an error "flashing unlock not allow"
Please help me with what I should do. thank you
nil3m1 said:
I used the command "fastboot oem nubia_unlock NUBIA_NX629J" ,"fastboot flashing unlock" , command but it reported an error "flashing unlock not allow"
Please help me with what I should do. thank you
Click to expand...
Click to collapse
Okay now you have to download the stock cn version from official site, and extract the zip file , now olyou have to flash the stock boot image and recovery image
,Fastboot devices
,Fastboot fastboot oem nubia_unlock NUBIA_NX629J
,Fastboot flash boot boot.img
,Fastboot flash recovery recovery.img
,Fastboot reboot
And wait let it reboot at least 3 time
And it will work just fine ?
em902566 said:
Okay now you have to download the stock cn version from official site, and extract the zip file , now olyou have to flash the stock boot image and recovery image
,Fastboot devices
,Fastboot fastboot oem nubia_unlock NUBIA_NX629J
,Fastboot flash boot boot.img
,Fastboot flash recovery recovery.img
,Fastboot reboot
And wait let it reboot at least 3 time
And it will work just fine
Click to expand...
Click to collapse
it dont work . my device not boot with report " your device is corrupt .It can not be trusted and wil not boot " .
update?
nil3m1 said:
it dont work . my device not boot with report " your device is corrupt .It can not be trusted and wil not boot " .
Click to expand...
Click to collapse
did you fixed it? we have same situation.
godric12 said:
did you fixed it? we have same situation.
Click to expand...
Click to collapse
Use "Fastboot fastboot oem nubia_unlock NUBIA_NX629J" to unlock the bootloader and flash the correct boot img. Or you can go to stock recovery flash the whole system. It is caused by an unsigned boot file.
JerryYin said:
Use "Fastboot fastboot oem nubia_unlock NUBIA_NX629J" to unlock the bootloader and flash the correct boot img. Or you can go to stock recovery flash the whole system. It is caused by an unsigned boot file.
Click to expand...
Click to collapse
I have this error when installing the rom, what should I do to fix it?
mos98p said:
I have this error when installing the rom, what should I do to fix it?
Click to expand...
Click to collapse
Maybe you can check other post and find the solutions, there are someone already fix the phone with same issue
11/10/19 @ 3:05..successfully obtained root access for my 1st device!!
Bold N1
Rooted with Magisk
Flashed stock boot.img
Fastboot flash boot (boot.img)
Fastboot flash recovery (recovery.img)
I'm finally a big kid!!
What usb driver did you use? I'm stuck on fastboot <waiting for device>
ycgr2002 said:
What usb driver did you use? I'm stuck on fastboot <waiting for device>
Click to expand...
Click to collapse
Did u allow usb debugging in developer options ?
greeneyez15o said:
Did u allow usb debugging in developer options ?
Click to expand...
Click to collapse
Yes and allow for OEM Unlock. It's a windows 10 driver issue. I couldn't figure it out.
Luckily I was able to run in on a Linux computer. Fastboot worked fine and was able to unlock the bootloader!
Sergeantslaughter said:
11/10/19 @ 3:05..successfully obtained root access for my 1st device!!
Bold N1
Rooted with Magisk
Flashed stock boot.img
Fastboot flash boot (boot.img)
Fastboot flash recovery (recovery.img)
I'm finally a big kid!!
Click to expand...
Click to collapse
How exactly did you root it? What were the steps if you don't mind sharing. I've only rooted one phone and I followed a step by step tutorial on YouTube.
The easiest way I've found is to download magisk manager and the stock boot img for your device.open magisk manager and click install-download zip only.. then move the zip file and your stock boot img to the root of internal storage. Eg/storage/emulated/0/. Go back to magisk manager and click install/select and patch file. Navigate to where you stored your stock boot img and select it. Magisk will automatically flash and repck img file and will save it in your downloads folder as magisk_patched.img. enable and debugging in Dev options and reboot to bootloader. /Adb reboot bootloader. Once your phone is in fastboot mode type /fastboot devices to be sure your computer can recognize your phone. Should come back as a serial number followed by the word fastboot. Then type
Fastboot flash boot magisk_patched.img
You should get a success prompt. If successful then reboot using
Fastboot reboot
Once your phone loads back up check magisk manager to verify that everything is installed, should be two green checks. Then use a root checker to verify root.....and that's it!
Also, you have to make sure your bootloader is unlocked in order to do this....its very easy for the bold n1 just enable oem unlock in Dev options and the reboot to bootloader and type fastboot flashing unlock. Select yes on the prompt on your phone and then continue your process.
ycgr2002 said:
What usb driver did you use? I'm stuck on fastboot <waiting for device>
Click to expand...
Click to collapse
mtk droid tools all in one installer worked for me
davids_laughter said:
How exactly did you root it? What were the steps if you don't mind sharing. I've only rooted one phone and I followed a step by step tutorial on YouTube.
Click to expand...
Click to collapse
Did I mention that I did this on my Chromebook....no windows at all lol