Hi,
i hope anyone from here can help me i think i have bricked my Phone.
I had a rooted phone with Modaco Rom and wanted to switch to DarchLegend or DarchDroid but i couldnt install one of them, i had only a boot-loop.
so i thought my RA-recovery-image is the problem, so i have installed the one from Darchrom with adb on my sdcard.
But now the recover image isnt working and also my phone have a boot-loop.
the only thing i have is fastboot but i cant do something like "fastboot boot image.img" because i get not allowed: remote.
any suggestions?
You could try flashing an old RUU again and start the rooting process from scratch?Did you do a full wipe before flashign the darchdroid rom?
I messed up i tried to reflash my phone back to stock from marshmallow rom on the thread here but i lost custom recovery and only thing i can get into is download mode, how can i fix this? I have abd install on my pc got the system image boot and recovery img but don't know what 2 do. Please help
xavier55 said:
I messed up i tried to reflash my phone back to stock from marshmallow rom on the thread here but i lost custom recovery and only thing i can get into is download mode, how can i fix this? I have abd install on my pc got the system image boot and recovery img but don't know what 2 do. Please help
Click to expand...
Click to collapse
Your phone is in fastboot mode, not download mode. Small, but distinct difference.
Since you've installed a custom ROM, your bootloader should be unlocked. However, it may be a good idea to issue the oem unlock command through fastboot anyways. Use "adb reboot bootloader" and "fastboot oem unlock" to ensure that your bootloader is unlocked.
Now, since your phone is in fastboot mode, you can do one of two things: 1. Flash a custom recovery and restore your device to stock, or 2. Flash a custom recovery and continue using a custom ROM. Either way, you will need to install TWRP or another custom recovery image of your choice. The TWRP thread is located here: http://forum.xda-developers.com/tmobile-lg-v10/development/recovery-unofficial-twrp-t3239740 Since you're already in the bootloader/fastboot mode, all you would need to do is download TWRP and use "fastboot flash recovery twrp.img" and then "fastboot boot twrp.img" to install TWRP. Please note that the 'twrp.img' will vary depending on which version you download, it will probably look more like 'twrp-2.8.7.1-h901.img'. You can just rename the file or use the full file name in the fastboot commands.
Once in TWRP, you can flash whatever ROM you want. To restore your phone to stock, go to this thread and flash the .zip in TWRP http://forum.xda-developers.com/tmo.../lg-h901-stock-images-device-restore-t3241170 after doing the standard wipe procedure. :good:
soltheman said:
Your phone is in fastboot mode, not download mode. Small, but distinct difference.
Since you've installed a custom ROM, your bootloader should be unlocked. However, it may be a good idea to issue the oem unlock command through fastboot anyways. Use "adb reboot bootloader" and "fastboot oem unlock" to ensure that your bootloader is unlocked.
Now, since your phone is in fastboot mode, you can do one of two things: 1. Flash a custom recovery and restore your device to stock, or 2. Flash a custom recovery and continue using a custom ROM. Either way, you will need to install TWRP or another custom recovery image of your choice. The TWRP thread is located here: http://forum.xda-developers.com/tmobile-lg-v10/development/recovery-unofficial-twrp-t3239740 Since you're already in the bootloader/fastboot mode, all you would need to do is download TWRP and use "fastboot flash recovery twrp.img" and then "fastboot boot twrp.img" to install TWRP. Please note that the 'twrp.img' will vary depending on which version you download, it will probably look more like 'twrp-2.8.7.1-h901.img'. You can just rename the file or use the full file name in the fastboot commands.
Once in TWRP, you can flash whatever ROM you want. To restore your phone to stock, go to this thread and flash the .zip in TWRP http://forum.xda-developers.com/tmo.../lg-h901-stock-images-device-restore-t3241170 after doing the standard wipe procedure. :good:
Click to expand...
Click to collapse
I'm kinda in the same boat now except that I already received the replacement device. Need to re-lock the old V10, but adb won't recognize my device at all. Any more option when that's the case? I can get into both download mode and fastboot. Phone is recognized by LGUP in download mode, but not by adb in fastboot mode for some reason.
(I've verified connection and driver using the other V10, the other V10 is recognized just fine)
soltheman said:
Your phone is in fastboot mode, not download mode. Small, but distinct difference.
Since you've installed a custom ROM, your bootloader should be unlocked. However, it may be a good idea to issue the oem unlock command through fastboot anyways. Use "adb reboot bootloader" and "fastboot oem unlock" to ensure that your bootloader is unlocked.
Now, since your phone is in fastboot mode, you can do one of two things: 1. Flash a custom recovery and restore your device to stock, or 2. Flash a custom recovery and continue using a custom ROM. Either way, you will need to install TWRP or another custom recovery image of your choice. The TWRP thread is located here: http://forum.xda-developers.com/tmobile-lg-v10/development/recovery-unofficial-twrp-t3239740 Since you're already in the bootloader/fastboot mode, all you would need to do is download TWRP and use "fastboot flash recovery twrp.img" and then "fastboot boot twrp.img" to install TWRP. Please note that the 'twrp.img' will vary depending on which version you download, it will probably look more like 'twrp-2.8.7.1-h901.img'. You can just rename the file or use the full file name in the fastboot commands.
Once in TWRP, you can flash whatever ROM you want. To restore your phone to stock, go to this thread and flash the .zip in TWRP http://forum.xda-developers.com/tmo.../lg-h901-stock-images-device-restore-t3241170 after doing the standard wipe procedure. :good:
Click to expand...
Click to collapse
thanks you saved me
baymon said:
I'm kinda in the same boat now except that I already received the replacement device. Need to re-lock the old V10, but adb won't recognize my device at all. Any more option when that's the case? I can get into both download mode and fastboot. Phone is recognized by LGUP in download mode, but not by adb in fastboot mode for some reason.
(I've verified connection and driver using the other V10, the other V10 is recognized just fine)
Click to expand...
Click to collapse
Yep. Your phone boots and everything, correct? Just factory reset it (Settings > Backup & Restore > Factory data reset). After its been reset, unlock it, turn on Developers Options, and enable USB debugging. After usb debugging is turned on, connect the v10 to your PC and be sure to hit "Always allow" when prompted by your phone. ADB should now be able to see your device.
If you can't get it to boot up, try restoring through LG UP/Bridge. I don't use any of LG's software, so I'm not sure what those apps can do and whether or not you'll be able to restore through them.
If nothing else, your phone is recognized in fastboot mode, so you can always manually flash the stock system images as well. You want to use the "fastboot flash boot boot.img", "fastboot flash recovery recovery.img", and "fastboot flash system system.img" commands After downloading the stock system images located in this thread: http://forum.xda-developers.com/lg-v10/development/lg-h901-stock-img-files-boot-recovery-t3238638
If you haven't ever flashed system images from fastboot, please read this first, as I am not responsible if your phone turns into a paperweight! https://developers.google.com/android/nexus/images#instructions While the instructions are for nexus devices, it works pretty much the same, except you'd want to use the individual commands instead of a flash-all script.
Hope this helps!
soltheman said:
Yep. Your phone boots and everything, correct? Just factory reset it (Settings > Backup & Restore > Factory data reset). After its been reset, unlock it, turn on Developers Options, and enable USB debugging. After usb debugging is turned on, connect the v10 to your PC and be sure to hit "Always allow" when prompted by your phone. ADB should now be able to see your device.
If you can't get it to boot up, try restoring through LG UP/Bridge. I don't use any of LG's software, so I'm not sure what those apps can do and whether or not you'll be able to restore through them.
If nothing else, your phone is recognized in fastboot mode, so you can always manually flash the stock system images as well. You want to use the "fastboot flash boot boot.img", "fastboot flash recovery recovery.img", and "fastboot flash system system.img" commands After downloading the stock system images located in this thread: http://forum.xda-developers.com/lg-v10/development/lg-h901-stock-img-files-boot-recovery-t3238638
If you haven't ever flashed system images from fastboot, please read this first, as I am not responsible if your phone turns into a paperweight! https://developers.google.com/android/nexus/images#instructions While the instructions are for nexus devices, it works pretty much the same, except you'd want to use the individual commands instead of a flash-all script.
Hope this helps!
Click to expand...
Click to collapse
Thanks for the follow up! No the phone would not boot at all and kept stuck at boot loop. I ended up just doing the OEM Lock and call it a day, the old device just won't boot to anything at this point.
I tried fastboot flash recovery recovery.img but it's giving some kinda kernel panic message and I was never able to get into recovery. This reminds me of the time when my Note 3 eMMC was fried, it wouldn't give a device ID to adb.
I think I am in the same boat too. I've been OEM unlocked yet recently my phone won't keep the TWRP recovery and keeps putting me into bootloop. I can't install a ROM and only thing I can do is fastboot mode. What did you do OEM lock the device? I am hoping that solution will get rid of that message bootloader unlocked during the bootloop and then I can try and get it serviced.
Hi guys,
I’m currently using a custom MM ROM and after learning how easy it is to get around the lockscreen, I would like to encrypt my device. Really, what’s the point of using PINs and having a fingerprint reader when anyone can just delete a few files and access your data?
So my question is does Kenzo support decrypt from TWRP? I succeeded in encrypting my data, but I can’t get TWRP to accept any PIN or password. I’m afraid to stay encrypted in case I need to access my data in TWRP. I don’t even know if its possible to make backups if you encrypt your data.
So, is there any way to access encrypted data in TWRP?
Good news for everyone interested in protecting their data! (I see there are no such people here.) I solved the problem where anyone could remove my lockscreen with the following method.
First, I flashed stock recovery. You can find it in any official fastboot ROM and flash it either in TWRP or Flashify and similar. Then, I disabled USB debugging (so that no one could use adb to remove the files). And finally I relocked my bootloader (with the command “fastboot oem lock”), which means that no one can flash TWRP in fastboot (you can still flash it in Flashify).
I will congratulate myself. Also, I no longer need to bother @vibhu0009 to implement decryption (I would still feel safer if he did it though )
Filip013 said:
Good news for everyone interested in protecting their data! (I see there are no such people here.) I solved the problem where anyone could remove my lockscreen with the following method.
First, I flashed stock recovery. You can find it in any official fastboot ROM and flash it either in TWRP or Flashify and similar. Then, I disabled USB debugging (so that no one could use adb to remove the files). And finally I relocked my bootloader (with the command “fastboot oem lock”), which means that no one can flash TWRP in fastboot (you can still flash it in Flashify).
I will congratulate myself. Also, I no longer need to bother @vibhu0009 to implement decryption (I would still feel safer if he did it though )
Click to expand...
Click to collapse
Hey! I am interested in unlocking bootloader ONLY and at the same time protect my data and you seem to be having experience in this situations. It would be great if u help.
Note: I am asking everything regarding xiaomi devices.
Q1. Do fastboot commands work if usb debugging is disabled?
Q2. When bootloader is locked, can we flash anything (unsigned roms or images) through fastboot or only signed packages or nothing?
Q3. If i have an unlocked bootloader, is it possible that anyone would flash a custom recovery (TWRP) through fastboot and use its file manager to copy my data to external otg or something even worse, delete my lock screen settings (password files) and have direct access to the device.
What would be the case If i have secure boot (password before bootup) turned on? Will he be able to access the files (encrypted) via recovery's file manager?
Q4. Suppose secure boot is turned on and anyone flashes custom recovery through fastboot, will it boot directly into the recovery or will it ask for password when booting first time into the newly flashed recovery. If it would boot directly into recovery, what will happen if one tries to access files through file manager of recovery. Will he be able to gain access to the files (copy, move, delete)?
Q5. Can a device be factory reset or completely erased including passwords and all by any fastboot commands. Can it be prevented if usb debugging is disabled?
Thanks in advance.
Hi. I have had the OnePlus X for a very long time, and I have recently bricked .
Ok, here it goes :fingers-crossed:. I had a OnePlus X running CM13 with TWRP but a locked bootloader. I decided to try cyanogenmod recovery but soon realized it was terrible.
I was unable to flash img. files and the UI was unappealing to me. However at that point I was able to reboot into my ROM (CM13) with no issues. Knowing this, I thought that the only way I could get TWRP back was through a fastboot command (fastboot flash recovery recovery.img).
For me to execute that command, I needed to unlock my bootloader first, so I took all the necessary steps in the developer options settings menu. I then booted into fastboot mode and executed this command: fastboot oem unlock. This was my big mistake, as I read up after that you should not unlock bootloader on a custom recovery.
After executing this command, it booted me into recovery. I tried many times without success to wipe data and flash a rom zip via external sd card but they never worked. To make things worse, I was unable to boot up the device. Whenever I tried to power on the device, it booted straight into recovery. I am able to boot into fasboot and recovery, but that is pretty much it. Can someone please help me? I am willing to donate.
If you were able to flash the Cyanogen recovery with a locked bootloader you should be able to flash the official OPX recovery as well. You can download that from this link: https://s3.amazonaws.com/oxygenos.oneplus.net/OPX_recovery.img
Then you should be able to unlock the bootloader!
Or if @Tanner1294's doesn't help, flashing stock rom via fastboot will surely help..
PS: Don't ever flash anything on a locked bootloader.
Hello,
I just received this weird phone I never heard or seen before and I need to root it. I'm afraid to start doing anything because I don't know if I will be able to flash back stock image (let alone find it) if anything goes south. Has anyone successfully tinkered their phone?
Yes. Managed to unlock and root mine yesterday, but with some caveats.
Some of the commands are different.
fastboot oem nubia_unlock NUBIA_NX619J
Is the command to start the bootloader unlock in Fastboot mode.
Then you can do
fastboot flashing unlock
To fully unlock the bootloader.
It appears you have to do the fastboot flashing unlock part each time in fastboot mode.
I flashed the boot.img modified with Magisk, had to reboot into fastboot again and redo flashing unlock before I could boot with my modified boot image. Everything since worked as expected.
One benefit to the Red Magic Mars is that it has an actual recovery partition and does not use the A/B slot partitioning system that so complicates other devices. So as long as you leave the recovery partition alone, you will be able to restore to stock using a USB C thumbdrive with the image file on it.