Related
Hello guys,
I have S-OFF, supercid, relocked bootloader phone
First I installed Firmware package from 2.17.401.1 RUU sucressfully my terminal quoted and then after reboot My phone was not reacting to any tipping on the screen. I only reached the screen where it demands the pin to type in.
So I flashed it again with firmware.zip from 1.29.401.12. Flash sucessfully (terminal quoted) and now it rebooted to the htc one logo and nothing else happens. I even cannot turn it off. Please help.
Update: I managed to reboot it but it is not reacting when i want to put in my PIN
Put the device under direct light (perhaps like a bulb) and press the power and volume down buttons together until the device reboots. While it is under direct light, do not cover the light sensors (on the left of the upper speaker grill) with your hand.
TarekElsakka said:
Put the device under direct light (perhaps like a bulb) and press the power and volume down buttons together until the device reboots. While it is under direct light, do not cover the light sensors (on the left of the upper speaker grill) with your hand.
Click to expand...
Click to collapse
ok i now restarted it but the touchscreen does not react when it asks me to put in the PIN
Reflash ROM..
Sent from my HTC One
Sindroid said:
Reflash ROM..
Sent from my HTC One
Click to expand...
Click to collapse
I flashed firmware 1.29.401.12 it again and same no reaction with touchscreen
Re-lock your bootloader (this will most probably wipe content of your device)
Copy downloaded .zip to fastboot.exe location (e.g. c:/SDK/platform-tools/fastboot.exe)
Re-name .zip file to firmware.zip
Open command prompt
Boot your device in fastboot mode (vol down + power ===> fastboot)
Connect device to the PC
In command prompt cd to fastboot.exe location
Make sure you have correct modeid and cidnum (type: fastboot getvar all)
Type: fastboot oem lock (if your device is not relocked yet)
Type: fastboot oem rebootRUU and wait for device to reboot
Type: fastboot flash zip firmware.zip and wait for process to complete
Sometimes flashing for the first time doesn't work, so flash firmware.zip again just to make sure.
Type: fastboot flash zip firmware.zip and wait for process to complete
Type: fastboot reboot
Unlock your bootloader and flash custom recovery if you are going to use custom ROM.
I did everything till step 14. Rom i have not installed yet because i want to install the firmware first.
Exxorzist said:
I flashed firmware 1.29.401.12 it again and same no reaction with touchscreen
Re-lock your bootloader (this will most probably wipe content of your device)
Copy downloaded .zip to fastboot.exe location (e.g. c:/SDK/platform-tools/fastboot.exe)
Re-name .zip file to firmware.zip
Open command prompt
Boot your device in fastboot mode (vol down + power ===> fastboot)
Connect device to the PC
In command prompt cd to fastboot.exe location
Make sure you have correct modeid and cidnum (type: fastboot getvar all)
Type: fastboot oem lock (if your device is not relocked yet)
Type: fastboot oem rebootRUU and wait for device to reboot
Type: fastboot flash zip firmware.zip and wait for process to complete
Sometimes flashing for the first time doesn't work, so flash firmware.zip again just to make sure.
Type: fastboot flash zip firmware.zip and wait for process to complete
Type: fastboot reboot
Unlock your bootloader and flash custom recovery if you are going to use custom ROM.
I did everything till step 14. Rom i have not installed yet because i want to install the firmware first.
Click to expand...
Click to collapse
I've had the same issue. Which rom do you use? CM wasn't working for me, so I had to flash Sense rom like ARHD 11 or Trickdroid 7.5
I also flashed the older firmware.zip and still no touch responsiveness. You will also have to flash a newer cwm touch recovery if you are using it, helps navigating through aroma http://goo.im/devs/Flyhalf205/M7/Recovery/recovery-clockwork-touch-6.0.3.2-m7.img
Exxorzist said:
I flashed firmware 1.29.401.12 it again and same no reaction with touchscreen
Re-lock your bootloader (this will most probably wipe content of your device)
Copy downloaded .zip to fastboot.exe location (e.g. c:/SDK/platform-tools/fastboot.exe)
Re-name .zip file to firmware.zip
Open command prompt
Boot your device in fastboot mode (vol down + power ===> fastboot)
Connect device to the PC
In command prompt cd to fastboot.exe location
Make sure you have correct modeid and cidnum (type: fastboot getvar all)
Type: fastboot oem lock (if your device is not relocked yet)
Type: fastboot oem rebootRUU and wait for device to reboot
Type: fastboot flash zip firmware.zip and wait for process to complete
Sometimes flashing for the first time doesn't work, so flash firmware.zip again just to make sure.
Type: fastboot flash zip firmware.zip and wait for process to complete
Type: fastboot reboot
Unlock your bootloader and flash custom recovery if you are going to use custom ROM.
I did everything till step 14. Rom i have not installed yet because i want to install the firmware first.
Click to expand...
Click to collapse
You need to flash this firmware: http://www.androidrevolution.nl/downloader/download.php?file=2.17.401.1-custom.zip again, and then flash the custom recovery stated above this post. Next, flash the latest Android Revolution which is on the newest base which other roms don't have yet. This should fix your issue. CM roms cannot be used by your device in its current state, as the touch drivers aren't compatible. You must use a Sense rom
MacHackz said:
You need to flash this firmware: http://www.androidrevolution.nl/downloader/download.php?file=2.17.401.1-custom.zip again, and then flash the custom recovery stated above this post. Next, flash the latest Android Revolution which is on the newest base which other roms don't have yet. This should fix your issue. CM roms cannot be used by your device in its current state, as the touch drivers aren't compatible. You must use a Sense rom
Click to expand...
Click to collapse
I flashed the firmware again sucessfully to 2.17.401.1
Since 2 days my Bootloader is relocked again but I am S-OFF. When I want to flash custom recovery I do have to unlock it again? How do I do that because I am still not able to use touchscreen and type in PIN?
George_Mn said:
I've had the same issue. Which rom do you use? CM wasn't working for me, so I had to flash Sense rom like ARHD 11 or Trickdroid 7.5
I also flashed the older firmware.zip and still no touch responsiveness. You will also have to flash a newer cwm touch recovery if you are using it, helps navigating through aroma http://goo.im/devs/Flyhalf205/M7/Recovery/recovery-clockwork-touch-6.0.3.2-m7.img
Click to expand...
Click to collapse
Exxorzist said:
I flashed the firmware again sucessfully to 2.17.401.1
Since 2 days my Bootloader is relocked again but I am S-OFF. When I want to flash custom recovery I do have to unlock it again? How do I do that because I am still not able to use touchscreen and type in PIN?
Click to expand...
Click to collapse
type fastboot oem flash unlocktoken unlock_code.bin
MacHackz said:
type fastboot oem flash unlocktoken unlock_code.bin
Click to expand...
Click to collapse
Thanks. I unlocked it and flashed the custom recovery
./fastboot-mac flash recovery recovery.img
sending 'recovery' (7422 KB)... OKAY
writing 'recovery'... OKAY
Then i rebootet it and touchscreen is still not reacting. Shall I now flash the revolution hd rom?
Exxorzist said:
Thanks. I unlocked it and flashed the custom recovery
./fastboot-mac flash recovery recovery.img
sending 'recovery' (7422 KB)... OKAY
writing 'recovery'... OKAY
Then i rebootet it and touchscreen is still not reacting. Shall I now flash the revolution hd rom?
Click to expand...
Click to collapse
Does touchscreen work in recovery mode?
What ROM do you currently have?
MacHackz said:
Does touchscreen work in recovery mode?
What ROM do you currently have?
Click to expand...
Click to collapse
Yes touchscreen works in recovery. I am at the moment not using any rom. I have bought a branded phone and all I did was giving it S-OFF, unlock bootloader, supercid, root.
And now after I flashed firmware 2.17, i simply want to put a rom on it like Revolution HD 11
Exxorzist said:
Yes touchscreen works in recovery. I am at the moment not using any rom. I have bought a branded phone and all I did was giving it S-OFF, unlock bootloader, supercid, root.
And now after I flashed firmware 2.17, i simply want to put a rom on it like Revolution HD 11
Click to expand...
Click to collapse
Flash Android Revolution 11 and it should work! :fingers-crossed:
MacHackz said:
Flash Android Revolution 11 and it should work! :fingers-crossed:
Click to expand...
Click to collapse
Stupid question. How do I get the zip file onto my Phone? Because I cannot type in my pin and then connect it as usual and pulling it via Android File Transfer over to my phone.
Exxorzist said:
Stupid question. How do I get the zip file onto my Phone? Because I cannot type in my pin and then connect it as usual and pulling it via Android File Transfer over to my phone.
Click to expand...
Click to collapse
Check my ADB push guide in my sig, jump to step 3
No need to relock bootloader when S-Off. If you upgrade firmware. If you upgrading to 2.17 f/w u need to flash new recovery as well.
Use sideload in recovery to reflash ROM.
Sent from my HTC One
MacHackz said:
Check my ADB push guide in my sig, jump to step 3
Click to expand...
Click to collapse
You are my hero!!!!!
Everything works great. Is there also the camera update included that was released by HTC in 1.29 because before I had 1.28.
Exxorzist said:
You are my hero!!!!!
Everything works great. Is there also the camera update included that was released by HTC in 1.29 because before I had 1.28.
Click to expand...
Click to collapse
It's all included You can also check the modded camera apk in my signature which allows you to take photos and focus using your volume buttons
Glad it worked
Thank you so much for this tip I thought I was SOL when it went into the WSOD and I couldn't turn it off.
This only works coming from KNX01R!
Edit, Camazza has found you can flash the stock 5.0.1 bootloader and sideload the update. See here http://forum.xda-developers.com/g-watch-r/development/manual-ota-update-root-t2969845
Download the update here http://android.clients.google.com/p....signed-lenok-LWX48P-from-KNX01R.149e0c34.zip
1. Root using tonu42's method here http://forum.xda-developers.com/g-watch-r/development/root-root-twrp-r-t2960511
2. After verifying you have root re install the stock recovery for 4.4w.2 from intersectRaven here http://forum.xda-developers.com/g-watch-r/development/stock-boot-recovery-g-watch-r-t2956964 (same command used during rooting).
3. Boot in the system and upload the update
adb push 149e0c34d0ab10d3e356d6301915dcc04552d9db.signed-lenok-LWX48P-from-KNX01R.149e0c34.zip /sdcard/update.zip
4. adb shell
5. cp /sdcard/update.zip /cache/update.zip
6. echo 'boot-recovery ' > /cache/recovery/command
7. echo '--update_package=/cache/update.zip' >> /cache/recovery/command
8. reboot recovery
9. Update installs
Thanks to tonu42 for root and intersectRaven for the stock boot.
Use at your own risk.
Does it remain rooted after the update ?
Would applying the update return the watch to stock? Including upgrading the bootloader and such?
I'm interested in manually updating, but I'd want the watch to be completely stock afterwards.
The bootloader and recovery are updated to stock, but, the device has still been oem unlocked so a fastboot oem lock command will need to be issued. This does remove the lock icon and the watch shows as locked, but, I don't know if lg can tell that is has been unlocked at one time. Root is lost after the update and will need to be reapplied.
nxt said:
Would applying the update return the watch to stock? Including upgrading the bootloader and such?
I'm interested in manually updating, but I'd want the watch to be completely stock afterwards.
Click to expand...
Click to collapse
superdave said:
The bootloader and recovery are updated to stock, but, the device has still been oem unlocked so a fastboot oem lock command will need to be issued. This does remove the lock icon and the watch shows as locked, but, I don't know if lg can tell that is has been unlocked at one time. Root is lost after the update and will need to be reapplied.
Click to expand...
Click to collapse
Yup, I knew that part so didn't ask. But I finally got it working (had issues flashing recovery, had to switch usb ports).
All is good now, thanks!
EDIT: Looks like SuperSU is still installed though (won't run)
Everything else seems stock, I even did oem lock/unlock a few times, recovery is stock
Between step 4 and 5 you need to type su
You'll lose root and I am working on a fix.
Sent from my A0001 using XDA Free mobile app
Why all this manipulations? Why not use ADB Sideload?
superdave said:
The bootloader and recovery are updated to stock, but, the device has still been oem unlocked so a fastboot oem lock command will need to be issued. This does remove the lock icon and the watch shows as locked, but, I don't know if lg can tell that is has been unlocked at one time. Root is lost after the update and will need to be reapplied.
Click to expand...
Click to collapse
I don't think LG cares as long as the lock icon is gone. I've already screwed up and sent them a G2 that was on older radios with TWRP installed, and they sent it back factory flashed to the latest firmware (ZVA at the time).
AntonChernov said:
Why all this manipulations? Why not use ADB Sideload?
Click to expand...
Click to collapse
I'd like to know as well, which method is better/safer, this or ADB sideload?
Adb does not work in Stock recovery that is why twrp is needed, . I am having the same issue with supersu crashing once booted. I have not had a chance to look at it yet. If you shell in and su before the phone boots su works fine though.
Actually there's a faster and safer way that does not involve rooting.
1) Unlock Bootloader
2) Flash 5.0.1 Stock Recovery
3) Enter recovery and sideload update (it works in the new recovery)
4) Profit
Nice, good catch. I'll add that to the first post.
Camazza said:
Actually there's a faster and safer way that does not involve rooting.
1) Unlock Bootloader
2) Flash 5.0.1 Stock Recovery
3) Enter recovery and sideload update (it works in the new recovery)
4) Profit
Click to expand...
Click to collapse
superdave said:
Nice, good catch. I'll add that to the first post.
Click to expand...
Click to collapse
I did the same as following and it's work for me:
recoveryll.bin => 5.0.1 Recovery http://forum.xda-developers.com/g-watch-r/development/stock-boot-recovery-g-watch-r-t2956964
1. adb reboot bootloader
2. fastboot oem unlock
3. fastboot boot recoveryll.bin
4. Select adb sideload then
adb sideload 149e0c34d0ab10d3e356d6301915dcc04552d9db.signed-lenok-LWX48P-from-KNX01R.149e0c34.zip
5. Done
6. Reboot to fastboot
7. fastbook oem lock
5.0.1 Recovery work with adb
kanzone said:
I did the same as following and it's work for me:
recoveryll.bin => 5.0.1 Recovery http://forum.xda-developers.com/g-watch-r/development/stock-boot-recovery-g-watch-r-t2956964
1. adb reboot bootloader
2. fastboot oem unlock
3. fastboot boot recoveryll.bin
4. Select adb sideload then
adb sideload 149e0c34d0ab10d3e356d6301915dcc04552d9db.signed-lenok-LWX48P-from-KNX01R.149e0c34.zip
5. Done
6. Reboot to fastboot
7. fastbook oem lock
5.0.1 Recovery work with adb
Click to expand...
Click to collapse
hey I am trying the same method:
ok, so I unlocked the bootloader, flashed the 5.0.1 recovery, then booted to recovery, selected the adb sideload (the watch now says "Now send the package you want to apply to the device with "adb sideload <filename>"..."
however, in CMD, adb devices is not returning anything. there is no 'new devices connected' sound in windows when removing/replacing the watch from the cradle.
can someone please tell me what am I doing wrong?
b0gd4n said:
hey I am trying the same method:
ok, so I unlocked the bootloader, flashed the 5.0.1 recovery, then booted to recovery, selected the adb sideload (the watch now says "Now send the package you want to apply to the device with "adb sideload <filename>"..."
however, in CMD, adb devices is not returning anything. there is no 'new devices connected' sound in windows when removing/replacing the watch from the cradle.
can someone please tell me what am I doing wrong?
Click to expand...
Click to collapse
adb version
make sure the adb version is > 1.0.32
kanzone said:
adb version
make sure the adb version is > 1.0.32
Click to expand...
Click to collapse
hey, nevermind, I did fastboot flash recovery, not adb boot recovery. I just did that, and I am now uploading the zip....exiting!
thanks!
So wait, the command to flash recovery is what exactly? I've seen 3 different commands on this very page. Also, we do it from the bootloader screen, right?
i am unlocked and rooted with twrp and everytime I try and fastboot the boot img. it says "remote image is not a boot image?
what the hell am i doing wrong?
I have also tried to fastboot a new recovery and I get the same thing?
Are you trying to restore the stock recovery? If so, you fastboot flash recovery recovery.img on the stock image.
cottageboy said:
i am unlocked and rooted with twrp and everytime I try and fastboot the boot img. it says "remote image is not a boot image?
what the hell am i doing wrong?
I have also tried to fastboot a new recovery and I get the same thing?
Click to expand...
Click to collapse
hi,
when I am trying to flash the recovery I get this error:
fastboot flash rcovery recoveryll.img
target reported max download size of 268435456 bytes
sending 'rcovery' (6634 KB)...
OKAY [ 0.312s]
writing 'rcovery'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.403s
adb version
Android Debug Bridge version 1.0.32
any idea?
do I need to flash the new boot.img before?
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.
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
ATTENTION: THIS PROCESS WILL WIPE ALL OF YOUR USER DATA. PROCEED AT YOUR OWN RISK. I am not responsible for your phone.
steps:
1- Download rom and entract archives (this brings included plataform-tools) and open cmd in the same folder
2- Just enable OEM unlocking in developer options, reboot your phone to Fastboot mode and unlock the bootloader with following command:
fastboot flashing unlock
Click to expand...
Click to collapse
Then confirm unlock on the phone.
fastboot flashing unlock_critical
Click to expand...
Click to collapse
3- Please check current slot as well and change to slot a
fastboot getvar current-slot
Click to expand...
Click to collapse
fastboot --set-active=a
Click to expand...
Click to collapse
4- Close cmd window and execute 00Flash.bat archive and wait to finish flashing, reboot phone and enjoy
-Extra- u want to root only download put archive in same folder and flash boot-magisk.img and install magisk apk
fastboot flash boot_a boot-magisk.img
Click to expand...
Click to collapse
fastboot flash boot_b boot-magisk.img
Click to expand...
Click to collapse
--------------------
Edited by SyCoREAPER
Thread Locked until Kernel source is provided.