Related
Is there any possible way of accessing the internal storage through TWRP? I made the unfortunate mistake of wiping everything including the OS. I would like to access the internal storage drive so I can put in a ROM and flash. Any help would be greatly appreciated!
olive.knight said:
Is there any possible way of accessing the internal storage through TWRP? I made the unfortunate mistake of wiping everything including the OS. I would like to access the internal storage drive so I can put in a ROM and flash. Any help would be greatly appreciated!
Click to expand...
Click to collapse
If you can get ADB over recovery working, you can push files to internal storage.
Be aware that if you did a data partition wipe, TWRP may be unable to write anything to the internal storage partition until you've booted a stock ROM at least once. If this is the case, then you are best to flash a stock ROM from fastboot, then boot once, put the files you need on internal and then proceed from there.
cmstlist said:
If you can get ADB over recovery working, you can push files to internal storage.
Be aware that if you did a data partition wipe, TWRP may be unable to write anything to the internal storage partition until you've booted a stock ROM at least once. If this is the case, then you are best to flash a stock ROM from fastboot, then boot custom recovery directly from fastboot, put the files you need on internal and then proceed from there.
Click to expand...
Click to collapse
+1
Maybe try using an OTG cable and usb stick. I just went from CWM to TWRP and saw that there was an option to use otg. I did did a backup to the usb directly and it works great. The inbuild file explorer was also able to browse all the files on the usb stick as well
bk201doesntexist said:
+1
Click to expand...
Click to collapse
You edited my quote to say "then boot custom recovery directly from fastboot". Please don't edit me. It does NOT work if your data partition is fully wiped.
On the Galaxy Nexus if you do a full userdata partition wipe, it CAN'T be written by any custom recovery until you do one full boot cycle into a ROM. The custom recovery will fail to mount the data partition. Booting into a ROM regenerates that partition.
You can see this after unlocking the bootloader, which does a userdata wipe. If you flash custom recovery and try to go straight into custom recovery, it will simply find no writable partition at all. Notice that when you boot into system after a userdata wipe, it commences the boot cycle and then reboots itself one additional time. I suspect that first boot cycle regenerates the userdata partition, and then the second boot cycle continues as normal.
cmstlist said:
If you can get ADB over recovery working, you can push files to internal storage.
Be aware that if you did a data partition wipe, TWRP may be unable to write anything to the internal storage partition until you've booted a stock ROM at least once. If this is the case, then you are best to flash a stock ROM from fastboot, then boot once, put the files you need on internal and then proceed from there.
Click to expand...
Click to collapse
Thanks for your reply as well as everyone else that has contributed to my thread. I am able to get my device to be in fastboot mode but adb does not detect my device. It states:
* daemon not running. starting it now on port 5037 *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
If this method does not work, would you suggest me to purchase an OTG usb cable as an alternative?
Adb doesnt work in fastboot mode.
Sent from my i9250
Why don't you just fast boot flash stock and start all over?
Sent from my Nexus 4 using xda premium
olive.knight said:
Thanks for your reply as well as everyone else that has contributed to my thread. I am able to get my device to be in fastboot mode but adb does not detect my device. It states:
* daemon not running. starting it now on port 5037 *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
If this method does not work, would you suggest me to purchase an OTG usb cable as an alternative?
Click to expand...
Click to collapse
In fastboot mode, you need to use fastboot (not ADB) to flash the stock ROM. Then after regenerating the data partition with one boot cycle, go back into fastboot again and flash custom recovery if you don't still have it.
Never tried it myself, but it should be possible to flash a custom recovery right when you're flashing stock through fastboot. Not through flash-all.sh, but manually flashing system.img, boot.img and userdata.img, unzipped from the update-jop40d.zip file, plus cwm.img or twrp.img, and then boot up normally, or directly to custom recovery to push a rom/root/whatever.
Again, if the device already has the latest bootloader/bb version, there's no need to reflash it. If using flash-all.sh, just comment those out from the script.
Sent from my i9250
bk201doesntexist said:
or directly to custom recovery to push a rom/root/whatever.
Click to expand...
Click to collapse
... except that if the userdata partition was completely wiped, directly to custom recovery will not be able to access the data partition until it's been booted into system once.
cmstlist said:
... except that if the userdata partition was completely wiped, directly to custom recovery will not be able to access the data partition until it's been booted into system once.
Click to expand...
Click to collapse
i stand corrected.
still, how about flashing userdata.img before flashing a custom recovery?
edit: I'm sorry. I must prove you wrong this time. I just finished flashing back to stock with the following steps:
- fastboot erase system
- fastboot erase userdata
- fastboot erase boot
- fastboot erase recovery
- fastboot flash system system.img
- fastboot flash userdata userdata.img
- fastboot flash recovery twrp.img
- (manual reboot to recovery on the device)
- adb push ~/workbench/maguro/recovery_flashables/CWM-SuperSU-v0.99.zip /sdcard/
- (flash zip on recovery)
- (reboot system from recovery)
- rooted JOP40D, working fully.
bk201doesntexist said:
i stand corrected.
still, how about flashing userdata.img before flashing a custom recovery?
edit: I'm sorry. I must prove you wrong this time. I just finished flashing back to stock with the following steps:
- fastboot erase system
- fastboot erase userdata
- fastboot erase boot
- fastboot erase recovery
- fastboot flash system system.img
- fastboot flash userdata userdata.img
- fastboot flash recovery twrp.img
- (manual reboot to recovery on the device)
- adb push ~/workbench/maguro/recovery_flashables/CWM-SuperSU-v0.99.zip /sdcard/
- (flash zip on recovery)
- (reboot system from recovery)
- rooted JOP40D, working fully.
Click to expand...
Click to collapse
I'm sorry if we have had different experiences, but this is what I have experienced:
- fastboot flash userdata userdata.img
- fastboot flash recovery {CWM or TWRP}
- (manual reboot to recovery on the device)
- Attempt to adb push anything
- Error message (I don't remember exactly what)
- Attempt to mount the data partition from the mounts menu
- Error message
- Boot into the ROM once, then into recovery
- No more error messages
This was my experience both on Galaxy Nexus and Nexus 7 3G.
FWIW, my GNex was bought from WIND Mobile in Canada. I have heard that the Play Store Nexus units are sometimes a bit different (e.g. some have reported that the Play Store Nexus does not wipe userdata after unlocking bootloader).
zephiK said:
Why don't you just fast boot flash stock and start all over?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Oh I definitely want to do this but I don't exactly know how to flash stock in fast boot mode. I don't know how to load the zip file in internal storage. If you could provide me a link or instructions on how to proceed I would gladly appreciate it!
olive.knight said:
Oh I definitely want to do this but I don't exactly know how to flash stock in fast boot mode. I don't know how to load the zip file in internal storage. If you could provide me a link or instructions on how to proceed I would gladly appreciate it!
Click to expand...
Click to collapse
When you flash in fastboot, the files reside on your computer and are flashed over USB to the device.
cmstlist said:
When you flash in fastboot, the files reside on your computer and are flashed over USB to the device.
Click to expand...
Click to collapse
I tried using my computer to command my phone in fastboot mode but my computer keeps stating that the "USB device not recognized" and the cmd continues with < waiting for device >. Are my efforts to revive my phone a lost cause?
Search around for GNex fastboot drivers. And make sure you're using fastboot on the computer, not ADB.
Sent from my Galaxy Nexus using Tapatalk 2
cmstlist said:
Search around for GNex fastboot drivers. And make sure you're using fastboot on the computer, not ADB.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Thank you and very one else that contributed to my post. With your help and a dash of luck I finally managed to return my phone to working order. Thanks again and happy holidays!!!
Found this question from Googling, and I actually have an easy answer for it:
Load TWRP, connect the phone to your computer (I was on Windows), and you can access your Internal Storage and SD card normally through USB as an attached device.
Hi guys,
I would really appreciate any help getting out of this pickle (my first time trying to install a ROM).
Here's the situation:
- Running a Huawei P6-C00 Chinese phone
- Was interested in trying a custom ROM (e.g. CleanRom by @surdu_petru) in order to enable Google Apps
- Updated normally to B120 CN as instructed
- Rooted (using Root Wizard)
- Installed customer recovery (TWRP 2.6.3.3)
- Started flash process including advanced wipe in TWRP... wiped system, cache, davlik, etc... :crying:
- Realized that I didn't have the ROM .zip copied to the phone yet
Currently, I'm able to boot into TWRP but cannot connect using adb for sideload (TWRP just says starting sideload but never connects). What do you guys recommend? I don't have a backup of any working ROM or the stock image.
Is there a way to initiate a "standard" restore since I wiped all the caches? ...
Are there some tricks to getting ADB running so I can try to sideload the ROM again? ...
P6-C00 does not have an SD card, but is it possible to load the ROM onto a USB and read it from TWRP?
Thanks for any help!
Did u try connecting to adb?
Sent from my U9200 using XDA Premium 4 mobile app
some help
onetree said:
Hi guys,
I would really appreciate any help getting out of this pickle (my first time trying to install a ROM).
Here's the situation:
- Running a Huawei P6-C00 Chinese phone
- Was interested in trying a custom ROM (e.g. CleanRom by @surdu_petru) in order to enable Google Apps
- Updated normally to B120 CN as instructed
- Rooted (using Root Wizard)
- Installed customer recovery (TWRP 2.6.3.3)
- Started flash process including advanced wipe in TWRP... wiped system, cache, davlik, etc... :crying:
- Realized that I didn't have the ROM .zip copied to the phone yet
Currently, I'm able to boot into TWRP but cannot connect using adb for sideload (TWRP just says starting sideload but never connects). What do you guys recommend? I don't have a backup of any working ROM or the stock image.
Is there a way to initiate a "standard" restore since I wiped all the caches? ...
Are there some tricks to getting ADB running so I can try to sideload the ROM again? ...
P6-C00 does not have an SD card, but is it possible to load the ROM onto a USB and read it from TWRP?
Thanks for any help!
Click to expand...
Click to collapse
you can try it whith a linux pc (ubuntu)
i have the same problem
good luck!
onetree said:
Hi guys,
I would really appreciate any help getting out of this pickle (my first time trying to install a ROM).
Here's the situation:
- Running a Huawei P6-C00 Chinese phone
- Was interested in trying a custom ROM (e.g. CleanRom by @surdu_petru) in order to enable Google Apps
- Updated normally to B120 CN as instructed
- Rooted (using Root Wizard)
- Installed customer recovery (TWRP 2.6.3.3)
- Started flash process including advanced wipe in TWRP... wiped system, cache, davlik, etc... :crying:
- Realized that I didn't have the ROM .zip copied to the phone yet
Currently, I'm able to boot into TWRP but cannot connect using adb for sideload (TWRP just says starting sideload but never connects). What do you guys recommend? I don't have a backup of any working ROM or the stock image.
Is there a way to initiate a "standard" restore since I wiped all the caches? ...
Are there some tricks to getting ADB running so I can try to sideload the ROM again? ...
P6-C00 does not have an SD card, but is it possible to load the ROM onto a USB and read it from TWRP?
Thanks for any help!
Click to expand...
Click to collapse
Did you try it with fastboot?
Gesendet von meinem P6-U06 mit Tapatalk
ext4
taaeem said:
Did you try it with fastboot?
Gesendet von meinem P6-U06 mit Tapatalk
Click to expand...
Click to collapse
i know that he must use a linux pc that for the drivers
ext4 If say it right...
taaeem said:
Did you try it with fastboot?
Click to expand...
Click to collapse
Hi Taaeem,
Thanks for the hint. I read some posts on fastboot and tried the following, but could not get into fastboot mode.
Methods I tried
- Power off phone and then power on while holding vol-down button
- Select Reboot -> System option from TWRP, while holding volume down
- Select Reboot -> Bootloader option from TWRP
From what I understand, fastboot mode should be run from the /boot partition, which I didn't wipe. So any ideas how I can get into fastboot mode?
Thanks again!
Okay, I confirmed that I have at least some kind of fastboot access because I tried "fastboot reboot-bootloader" from command prompt on my PC, and it rebooted the phone (but the phone stayed on boot logo).
- Next time I get fastboot, should I run "fastboot flash [partition] [ROM-file.zip]"?
- If so, what partition should I specify? I'm confused about where this command will send the ROM file, and if so how do I find it from TWRP later on in order to install it?
Thank you!
One more update:
- Even though I'm stuck at boot logo when I try to enter fastboot mode, it looks like there is a somewhat working fastboot connection. I tried running "fastboot flash [partition] ROM.zip" but it fails after 16s ("remote: flash write failure" or "remote: partition does not exist"). I tried flashing to cache / data / system
Should I try @N!ELS huawei p6 suggestion of accessing by Linux? (I don't have one nearby) or am I using fastboot wrong?
Thanks!!
Also:
- I noticed that when I boot into TWRP the device shows as "..." in my system tray USB devices list.
- When I try to boot into fastboot mode, the device shows as "Android Sooner Single ADB Interface" (but phone is still stuck on boot logo)
- However I'm still not able to connect using ADB .. shows "error: device not found" in all cases)
- Finally, after powering off the phone does show the stock charging animation, which gives me hope that this can still be saved :crying:
onetree said:
One more update:
- Even though I'm stuck at boot logo when I try to enter fastboot mode, it looks like there is a somewhat working fastboot connection. I tried running "fastboot flash [partition] ROM.zip" but it fails after 16s ("remote: flash write failure" or "remote: partition does not exist"). I tried flashing to cache / data / system
Should I try @N!ELS huawei p6 suggestion of accessing by Linux? (I don't have one nearby) or am I using fastboot wrong?
Thanks!!
Also:
- I noticed that when I boot into TWRP the device shows as "..." in my system tray USB devices list.
- When I try to boot into fastboot mode, the device shows as "Android Sooner Single ADB Interface" (but phone is still stuck on boot logo)
- However I'm still not able to connect using ADB .. shows "error: device not found" in all cases)
- Finally, after powering off the phone does show the stock charging animation, which gives me hope that this can still be saved :crying:
Click to expand...
Click to collapse
fastboot mode on the P6 doesn't have any kind of ui for fastboot, so it stays on the boot logo, fastboot should work fine.
You could always find an USB OTG cable and connect a FAT32 partitioned mem stick with the .zip on it, TWRP allows flashing from USB memory as far as I know
You are definetely not out of hope, but im not sure about the compability of P6-U06 roms with the C00 variant.
onetree said:
One more update:
- Even though I'm stuck at boot logo when I try to enter fastboot mode, it looks like there is a somewhat working fastboot connection. I tried running "fastboot flash [partition] ROM.zip" but it fails after 16s ("remote: flash write failure" or "remote: partition does not exist"). I tried flashing to cache / data / system
Click to expand...
Click to collapse
Obviously you can't flash the whole zip file to every partition, infact you can't flash a .zip at all, atleast not in fastboot mode, .img extension is used. So don't try flashing the rom manually via fastboot, since you have a high risk of actually bricking the device, if not in the right hands.
Also when booted into TWRP, try "adb devices" in the cmd see if anything shows up.
onetree said:
One more update:
- Even though I'm stuck at boot logo when I try to enter fastboot mode, it looks like there is a somewhat working fastboot connection. I tried running "fastboot flash [partition] ROM.zip" but it fails after 16s ("remote: flash write failure" or "remote: partition does not exist"). I tried flashing to cache / data / system
Should I try @N!ELS huawei p6 suggestion of accessing by Linux? (I don't have one nearby) or am I using fastboot wrong?
Thanks!!
Also:
- I noticed that when I boot into TWRP the device shows as "..." in my system tray USB devices list.
- When I try to boot into fastboot mode, the device shows as "Android Sooner Single ADB Interface" (but phone is still stuck on boot logo)
- However I'm still not able to connect using ADB .. shows "error: device not found" in all cases)
- Finally, after powering off the phone does show the stock charging animation, which gives me hope that this can still be saved :crying:
Click to expand...
Click to collapse
Okay that's good when you are stuck at the logo and you can see your device at your PC you are in fastboot mode, from here you can work with fastboot commands NOT with ADB that will not work. Anyway isn't there a option in TWRP where you can mount your device to USB when that work you can just copy the files on your phone without to go with fastboot. When that don't work you must try to extract the .zip from the ROM you want to install and flash every image with fastboot I think that should work.
Gesendet von meinem P6-U06 mit Tapatalk
tauio111 said:
fastboot mode on the P6 doesn't have any kind of ui for fastboot, so it stays on the boot logo, fastboot should work fine.
You could always find an USB OTG cable and connect a FAT32 partitioned mem stick with the .zip on it, TWRP allows flashing from USB memory as far as I know
You are definetely not out of hope, but im not sure about the compability of P6-U06 roms with the C00 variant.
Obviously you can't flash the whole zip file to every partition, infact you can't flash a .zip at all, atleast not in fastboot mode, .img extension is used. So don't try flashing the rom manually via fastboot, since you have a high risk of actually bricking the device, if not in the right hands.
Also when booted into TWRP, try "adb devices" in the cmd see if anything shows up.
Click to expand...
Click to collapse
Okay so now I'm a bit paranoid about hard-bricking the device, and would rather not try my luck on a ROM that isn't approved for the P6-C00, haha...
At this point I just want to get a working OS installed (restore to the default for P6-C00 phone, even), and then maybe try to safely enable Google Apps. Any suggestions on how I can get this restored?
- I think the device came with a USB cable that is OTG.
- Seems like fastboot is also working, even though "fastboot getvar xxx" returns nothing useful
- ADB does not work while booted into TWRP (can't run shell, sideload, or list devices)
onetree said:
Okay so now I'm a bit paranoid about hard-bricking the device, and would rather not try my luck on a ROM that isn't approved for the P6-C00, haha...
At this point I just want to get a working OS installed (restore to the default for P6-C00 phone, even), and then maybe try to safely enable Google Apps. Any suggestions on how I can get this restored?
- I think the device came with a USB cable that is OTG.
- Seems like fastboot is also working, even though "fastboot getvar xxx" returns nothing useful
- ADB does not work while booted into TWRP (can't run shell, sideload, or list devices)
Click to expand...
Click to collapse
Download this rom for example https://disk.yandex.com/public/?hash=bhDlIAc5AqKh4RAB2IdatPdEfYVI9FH/Zky/UTGcH3M=
Extract the .z7 and run the flash_all.bat, this scripts flashes the rom via fastboot and you should get your device back up and running again. And from there you can update to a newer firmware version without problems.
If the bat doesn't work try this:
boot to fastboot
fastboot flash system system.img
fastboot flash cust cust.img
fastboot reboot recovery
Wipe cache and dalvik cache in twrp
tauio111 said:
Download this rom for example https://disk.yandex.com/public/?hash=bhDlIAc5AqKh4RAB2IdatPdEfYVI9FH/Zky/UTGcH3M=
Extract the .z7 and run the flash_all.bat, this scripts flashes the rom via fastboot and you should get your device back up and running again. And from there you can update to a newer firmware version without problems.
If the bat doesn't work try this:
boot to fastboot
fastboot flash system system.img
fastboot flash cust cust.img
fastboot reboot recovery
Wipe cache and dalvik cache in twrp
Click to expand...
Click to collapse
Thank you! I will try this tonight after work
tauio111 said:
Download this rom for example https://disk.yandex.com/public/?hash=bhDlIAc5AqKh4RAB2IdatPdEfYVI9FH/Zky/UTGcH3M=
Extract the .z7 and run the flash_all.bat, this scripts flashes the rom via fastboot and you should get your device back up and running again. And from there you can update to a newer firmware version without problems.
If the bat doesn't work try this:
boot to fastboot
fastboot flash system system.img
fastboot flash cust cust.img
fastboot reboot recovery
Wipe cache and dalvik cache in twrp
Click to expand...
Click to collapse
Thanks, tauio111! That worked and I now have a working phone again :victory:
I'm going to be a bit more careful about how to enable Google Apps... this is too much stress during the workweek haha.
Later on what do you think my best option would be?
- Wait for a confirmed easy to install ROM for P6-C00 that supports Google Apps
- Some other way to enable Google Apps with the standard firmware, since I am rooted?
Thanks :laugh:
onetree said:
Thanks, tauio111! That worked and I now have a working phone again :victory:
I'm going to be a bit more careful about how to enable Google Apps... this is too much stress during the workweek haha.
Later on what do you think my best option would be?
- Wait for a confirmed easy to install ROM for P6-C00 that supports Google Apps
- Some other way to enable Google Apps with the standard firmware, since I am rooted?
Thanks :laugh:
Click to expand...
Click to collapse
Easy, flash this via TWRP
tauio111 said:
Easy, flash this via TWRP
Click to expand...
Click to collapse
Thanks @tauio111 and everyone else who helped debug this.
I flashed stock recovery, updated official firmware to B120, re-flashed TWRP, flashed gapps, and now have a working phone with Gmail and Play Store!! :silly:
tauio111 said:
Download this rom for example https://disk.yandex.com/public/?hash=bhDlIAc5AqKh4RAB2IdatPdEfYVI9FH/Zky/UTGcH3M=
Extract the .z7 and run the flash_all.bat, this scripts flashes the rom via fastboot and you should get your device back up and running again. And from there you can update to a newer firmware version without problems.
If the bat doesn't work try this:
boot to fastboot
fastboot flash system system.img
fastboot flash cust cust.img
fastboot reboot recovery
Wipe cache and dalvik cache in twrp
Click to expand...
Click to collapse
I have the same problem and i do the same but nothing..
I tried to delete xposed installer and my phone stuck..
What can i do?
Edit:It s opened but i can t touch my screen.I try to put my password and i can t..
tauio111 said:
Download this rom for example (Removed to allow posting - faye2thesky)
Extract the .z7 and run the flash_all.bat, this scripts flashes the rom via fastboot and you should get your device back up and running again. And from there you can update to a newer firmware version without problems.
If the bat doesn't work try this:
boot to fastboot
fastboot flash system system.img
fastboot flash cust cust.img
fastboot reboot recovery
Wipe cache and dalvik cache in twrp
Click to expand...
Click to collapse
Heya Tauio111, I'm having the same problem as onetree and I've been frying my mind over this for the past 4 days before I came across your solution. I found that your link is no longer working, may I ask what that ROM is and where else I may find it? Thanks!
faye2thesky said:
Heya Tauio111, I'm having the same problem as onetree and I've been frying my mind over this for the past 4 days before I came across your solution. I found that your link is no longer working, may I ask what that ROM is and where else I may find it? Thanks!
Click to expand...
Click to collapse
A way that may help (i've done it with boot&recovery images). Using this tool http://forum.xda-developers.com/showthread.php?t=2433454 , might give you the *.img files necesary for flashing the stock rom through fast boot. All you need is to follow the instructions on the tool and have a stock rom (update.app file type), and some knowledge on how to use the fastboot.
Hi Guys,
I kinda did the same thing here.
I accidently wiped my system with TWRP v2.6.3.7
I also have a huawei ascend p6 u06
I didn't realize i never copied a rom to my device so i don't know how to install.
I can't seem to be able to use adb or fastboot and my device is not picked up by windows (8.1), it just says removable disk in my computer.
and under device manager it says P6-U06 under unknown devices.
I have tried to install a bunch of different drivers to attempt something but no luck.
Please help me.
Hey guys, as the title states, I'm struggling to install a custom ROM on my Nexus 5X, and I was hoping you guys could read what I did and tell me where I'm going wrong. This is my first time rooting via fastboot commands as whenever I try to root via NRT, SuperSU doesn't flash.
I've had a few failed attempts where my phone has been stuck in bootloop and I've flashed stock using Nexus Root Toolkit. I'll list what I do when trying to root, and if you could tell me where I'm going wrong, that'd be brilliant.
- My first step was to install stock (build number: MTC19T) via NRT
- Connect to the device via fastboot
- Bootloader is already unlocked so I don't bother with that
- Download SuperSU 2.74 in the phone
- Flash over a modified boot.img (found one for my build number on XDA by Tigerstown) via the fastboot commands
***I did this because when I tried to install the SuperSU zip from TWRP 3.0.2, my phone would reboot halfway through the flash and not root***
- Flash over the custom recovery (TWRP 3.0.2 for bullhead)
- Enter recovery from the bootloader
- Install SuperSU via TWRP
- Reboot the phone
- Check if I have root via a Root Checker app in the Play Store
***This part usually goes fine, I've tried it without the boot.img, but TWRP keeps rebooting the system when I try flashing SuperSU***
- Once my phone is rooted, I download Dirty Unicorns 6.0.1 and Banks Dynamic GApps to my phone (I've got these 2 downloaded to my laptop and I just transfer them over to my phone)
- I go back into recovery, I wipe the system (but not internal storage)
- Go to install in TWRP and try to install DU 6.0.1
***My problem here is that TWRP reboots halfway through the installation. I can't flash GApps after the ROM. My phone takes a while to boot up, but when it does, I have DU 6.0.1 even though the installation in TWRP didn't finish***
- I then go back into recovery to install GApps, but the same thing happens to TWRP, it freezes for a second and then reboots my phone.
***However, unlike DU, my GApps won't install. I've tried different a GApps package (Opengapps) but TWRP does the same thing every time***
To summarize, after I root and flash my ROM, I'm left with DU with no GApps. The issue I seem to be having is with TWRP not flashing GApps and I've tried a different version of it but the same thing ends up happening, it freezes for a second and then reboots my phone. I've also tried using SuperSU 2.65 but the same thing happens.
I know this is a long read, but any help would be seriously appreciated!
I haven't heard of twrp rebooting halfway through a flashing sequence before so I'm going to guess that something is corrupted.
I'll try to help you out as much as I can here but if twrp continues to reboot during a flashing sequence I would try to RMA the device and get a new 5X.
Based off what you have typed it sounds like you already have adb access on your computer so I'm going to suggest that you completely wipe the device with these commands:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase vendor
fastboot erase userdata
Reboot the device into bootloader mode and use this command:
fastboot format userdata <--- This is a must do so that twrp will mount data
Re-download the latest TWRP to make sure the one you have isn't corrupted and then flash it to the device using this command: fastboot flash recovery (name of twrp.img here)
Then flash the Cache.img and Vendor.img that is needed for the DU rom with these commands:
fastboot flash cache cache.img
fastboot flash vendor vendor.img
After the flashing is done boot into recovery mode and wipe the device using twrp. Reboot into recovery mode again. <---- this is a must do so that the other partitions will mount
Transfer the DU rom, Gapps, and SuperSU to the device and flash them while in twrp in this order:
1.) DU rom
2.) SuperSU
3.) Gapps
Reboot the device and you will have the DU with your choice of Gapps and root. Guaranteed.
HesThatGuy said:
I haven't heard of twrp rebooting halfway through a flashing sequence before so I'm going to guess that something is corrupted.
I'll try to help you out as much as I can here but if twrp continues to reboot during a flashing sequence I would try to RMA the device and get a new 5X.
Based off what you have typed it sounds like you already have adb access on your computer so I'm going to suggest that you completely wipe the device with these commands:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase vendor
fastboot erase userdata
Reboot the device into bootloader mode and use this command:
fastboot format userdata <--- This is a must do so that twrp will mount data
Re-download the latest TWRP to make sure the one you have isn't corrupted and then flash it to the device using this command: fastboot flash recovery (name of twrp.img here)
Then flash the Cache.img and Vendor.img that is needed for the DU rom with these commands:
fastboot flash cache cache.img
fastboot flash vendor vendor.img
After the flashing is done boot into recovery mode and wipe the device using twrp. Reboot into recovery mode again. <---- this is a must do so that the other partitions will mount
Transfer the DU rom, Gapps, and SuperSU to the device and flash them while in twrp in this order:
1.) DU rom
2.) SuperSU
3.) Gapps
Reboot the device and you will have the DU with your choice of Gapps and root. Guaranteed.
Click to expand...
Click to collapse
First of all, just wanted to say thanks for the reply. Unfortunately, I have a few questions (because I'm pretty new at rooting without NRT, so sorry for all these questions)
1) When I fastboot erase everything, is that basically getting rid of the Android OS from my device? If so, would I be able to recover it all by reflashing stock via NRT? (Just in case this goes horribly wrong)
2) What do you mean by adb access? Is that the terminal where you enter commands like "fastboot flash boot <boot.img>" after shift + right clicking on the explorer in windows? (I've been calling that fastboot access)
3) Where would I find the cache.img and vendor.img for DU? I've looked on the DU bullhead page but can't seem to find it.
4) When transferring files after I've flashed TWRP, would I have to sideload the ROM, SuperSU and GApps? I haven't been able to get the hang of that yet, they way I'm doing this is:
- opening the console command
- "adb usb"
- "adb devices"
- going into TWRP, advanced, sideload adb and swiping right
- "adb push <file>" ***not sure if this line is correct
My problem here is that when I swipe in my recovery, I seem to lose adb access. Am I doing this in the wrong order? Are there any other ways of sideloading?
Again, sorry for all the questions but I'm new at all of this and I really want root on my Nexus 5X.
thatguynaveed said:
First of all, just wanted to say thanks for the reply. Unfortunately, I have a few questions (because I'm pretty new at rooting without NRT, so sorry for all these questions)
1) When I fastboot erase everything, is that basically getting rid of the Android OS from my device? If so, would I be able to recover it all by reflashing stock via NRT? (Just in case this goes horribly wrong)
2) What do you mean by adb access? Is that the terminal where you enter commands like "fastboot flash boot <boot.img>" after shift + right clicking on the explorer in windows? (I've been calling that fastboot access)
3) Where would I find the cache.img and vendor.img for DU? I've looked on the DU bullhead page but can't seem to find it.
4) When transferring files after I've flashed TWRP, would I have to sideload the ROM, SuperSU and GApps? I haven't been able to get the hang of that yet, they way I'm doing this is:
- opening the console command
- "adb usb"
- "adb devices"
- going into TWRP, advanced, sideload adb and swiping right
- "adb push <file>" ***not sure if this line is correct
My problem here is that when I swipe in my recovery, I seem to lose adb access. Am I doing this in the wrong order? Are there any other ways of sideloading?
Again, sorry for all the questions but I'm new at all of this and I really want root on my Nexus 5X.
Click to expand...
Click to collapse
1) yes
2) yes
3) factory image zip found here
4) no, when you are in TWRP connect the phone to the computer you will get a window pop up that allows you to brows the internal storage of your device (sd card) you can freely move files back and fourth.
If you didn't execute "Fast boot Flash System 'system.img" not erase System Partition vis Recovery then no, it will not erase the system partition of the device.
Sent from my Nexus 5X using XDA-Developers mobile app
HesThatGuy said:
I haven't heard of twrp rebooting halfway through a flashing sequence before so I'm going to guess that something is corrupted.
I'll try to help you out as much as I can here but if twrp continues to reboot during a flashing sequence I would try to RMA the device and get a new 5X.
Based off what you have typed it sounds like you already have adb access on your computer so I'm going to suggest that you completely wipe the device with these commands:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase vendor
fastboot erase userdata
Reboot the device into bootloader mode and use this command:
fastboot format userdata <--- This is a must do so that twrp will mount data
Re-download the latest TWRP to make sure the one you have isn't corrupted and then flash it to the device using this command: fastboot flash recovery (name of twrp.img here)
Then flash the Cache.img and Vendor.img that is needed for the DU rom with these commands:
fastboot flash cache cache.img
fastboot flash vendor vendor.img
After the flashing is done boot into recovery mode and wipe the device using twrp. Reboot into recovery mode again. <---- this is a must do so that the other partitions will mount
Transfer the DU rom, Gapps, and SuperSU to the device and flash them while in twrp in this order:
1.) DU rom
2.) SuperSU
3.) Gapps
Reboot the device and you will have the DU with your choice of Gapps and root. Guaranteed.
Click to expand...
Click to collapse
Tried this method this morning, no luck though
Same thing kept happening, TWRP freezes for a second halfway through installing SuperSU (at extracting files) and then rebooting without root.
Gutted I can't get root on my phone
Since TWRP continues to reboot halfway through the flashing sequence I would recommend that you RMA the device and get a new 5X. There could possibly be a hardware failure occurring and with those it's best to try not to fix them yourself.
thatguynaveed said:
Tried this method this morning, no luck though
Same thing kept happening, TWRP freezes for a second halfway through installing SuperSU (at extracting files) and then rebooting without root.
Gutted I can't get root on my phone
Click to expand...
Click to collapse
Are you accepting when TWRP offers to root the phone for you? Don't! That feature does not work on MM and I think they took it out in 3.0x
Download SuperSU from Chainfire's website, flash the zip in Twrp and then install the SuperSU app from Play
berndblb said:
Are you accepting when TWRP offers to root the phone for you? Don't! That feature does not work on MM and I think they took it out in 3.0x
Download SuperSU from Chainfire's website, flash the zip in Twrp and then install the SuperSU app from Play
Click to expand...
Click to collapse
No, I can't even get to that stage. TWRP reboots whilst I'm trying to install SuperSU.
And by flashing the SuperSU zip, wouldn't I already have SuperSU on my phone? Why would I have to install it form the Play Store?
Anyways, I've given up on trying to root my 5X, like HesThatGuy said, my phone probably has some hardware issues and seeing as I bought my phone second hand, I can't replace it. So I'm just sticking with stock.
Thanks for the reply though mate :good:
Why in Matias Duarte's name are you rooting your phone before flashing a custom ROM? That is a massive waste of time and effort. DU is rooted. You dont need to root the stock ROM first.
First, redownload and fastboot flash TWRP. Redownload DU and the recommended GAPPS while you are at it. If you want to be unencrypted go to WIPE and select Format Data (this will nuke all photos, video, music, whatever on your phone. Back it up first). Don't reboot. Now plug your phone into your computer. Move DU and the GAPPS package you redownloaded to your phone. Wipe everything but internal storage. Add both DU and GAPPS to the flash queue. Flash those buggers. Enjoy.
Hello, I have sent my phone to warranty and after that I received a phone with NO RPMB and after many frustrations I found (with help of many users and forums) how to workaround this..
To start:
Download boot image from here
Download twrp from the official website
Change the name to boot.img and twrp.img and put it in the platform-tools folder
Open the terminal there
Download your favourite rom
Enter fastboot mode on your phone
!!!!After this you will loose all of your data!!!!
Paste this to the terminal
fastboot oem unlock
(select yes on your phone)
fastboot flash boot boot.img
fastboot flash recovery twrp.img
fastboot format userdata
fastboot format cache
Reboot to recovery (if it doesn't enter at the first time enter download mode again and restart to recovery)
After that you have twrp and can flash every rom.. yay!!!
Wipe everything.
Copy the rom zip to your phone using MTP
Install your fancy new rom
If you want to install magisk:
Install the magisk manager.
On the app select install and select patch image file. (it will create a new boot image already patched)
After that install the new image (patched_boot.img) using twrp
Do a clean instalation of your ROM (recomended) or a Factory Reset first
Reboot to twrp
Select install
Click in install image
Select patched_boot.img
Select install to boot partition
Reboot.
Install magisk manager and do the sugested setup.
You now have magisk working
Thanks to all the users that helped me!!
I had real trouble getting twrp to work the last time I tried this a few months ago. Followed the steps here and am now on pixel experience with magisk. Thanks!
Hello, im in the same situation of NO RPMB. This procedure will permanently lets have bootloader unlocked?
About Magisk, i can install it in usual way once im in the recovery? (I mean download latest stable version for Bullhead and flash via TWRP).
Thanks.
sigibian said:
Hello, im in the same situation of NO RPMB. This procedure will permanently lets have bootloader unlocked?
About Magisk, i can install it in usual way once im in the recovery? (I mean download latest stable version for Bullhead and flash via TWRP).
Thanks.
Click to expand...
Click to collapse
My bootloader is still unlocked after following this guide
For Magisk:
-Install your custom ROM and boot it up (without root)
-Then extract the boot.img from the ROM zip file and save it on your phone storage.
-Install the Magisk manager apk
-In Magisk manager, select install Magisk> choose the patch boot image option and -Select the boot.img you previously saved.
Once it's done, reboot into twrp and flash the patched boot.img. When you reboot Magisk will be working.
I've had no issues with my bootloader, even after an ota update for pixel experience.
Thank you, i will try it.
Another question. I never tried dowload mode before, as i read in other post i should Plug USB cable into pc, Hold volume up and power at the same time and plug phone into usb that's already connected to pc, right?
When in download mode i can fire up fastboot commands like im in bootloader mode?
So then after do last command fastboot format cache i can reboot to recovery from terminal using adb reboot recovery or i can / should do it from device?
About twrp it's ok to use the latest 3.2.3.0 official version or the 3.2.1 4core version from here as someone suggested from Reddit? https://forum.xda-developers.com/nexus-5x/development/recovery-twrp-3-2-1-4-core-t3796656
sigibian said:
Thank you, i will try it.
Another question. I never tried dowload mode before, as i read in other post i should Plug USB cable into pc, Hold volume up and power at the same time and plug phone into usb that's already connected to pc, right?
When in download mode i can fire up fastboot commands like im in bootloader mode?
So then after do last command fastboot format cache i can reboot to recovery from terminal using adb reboot recovery or i can / should do it from device?
About twrp it's ok to use the latest 3.2.3.0 official version or the 3.2.1 4core version from here as someone suggested from Reddit? https://forum.xda-developers.com/nexus-5x/development/recovery-twrp-3-2-1-4-core-t3796656
Click to expand...
Click to collapse
The official twrp works for fine for me, haven't tried the 4 core version but it can't hurt to try if you need it.
Power off your phone then press and hold volume - and power to enter bootloader, then connect to your pc and follow the steps in the OP
So i have to enter in bootloader mode? At point 6 of OP there is written to enter in the download mode, this makes me confusing.
Can anyone explain me latest 2 commands why they are needed?
fastboot format userdata
fastboot format cache
sigibian said:
So i have to enter in bootloader mode? At point 6 of OP there is written to enter in the download mode, this makes me confusing.
Can anyone explain me latest 2 commands why they are needed?
fastboot format userdata
fastboot format cache
Click to expand...
Click to collapse
This thread is fairly comprehensive;
https://forum.xda-developers.com/nexus-5x/general/moto-nexus-5x-sticky-roll-t3207487
Holding volume - and power takes you to fastboot mode (download mode essentially), theres also an option to reboot into recovery (selectable using the volume keys.)
Formatting user data and cache is necessary prior to installing a new rom (especially if moving from stock). You lose all data (back up first!) But a clean flash is the best place to start.
baddesthad said:
This thread is fairly comprehensive;
https://forum.xda-developers.com/nexus-5x/general/moto-nexus-5x-sticky-roll-t3207487
Holding volume - and power takes you to fastboot mode (download mode essentially), theres also an option to reboot into recovery (selectable using the volume keys.)
Formatting user data and cache is necessary prior to installing a new rom (especially if moving from stock). You lose all data (back up first!) But a clean flash is the best place to start.
Click to expand...
Click to collapse
Thanks for the explanation but for installing a new ROM usually you can do factory reset directly in TWRP, plus doing all the wipes, this should be enough.
About fastboot mode and download mode, they are completely different, fastboot mode: vol down + power, download mode for LG: Plug USB cable into pc, Hold volume up and power at the same time and plug phone into usb.
My question is what i can do in download mode? As OP says after entering download mode open terminal and use fastboot commands.
sigibian said:
Thanks for the explanation but for installing a new ROM usually you can do factory reset directly in TWRP, plus doing all the wipes, this should be enough.
About fastboot mode and download mode, they are completely different, fastboot mode: vol down + power, download mode for LG: Plug USB cable into pc, Hold volume up and power at the same time and plug phone into usb.
My question is what i can do in download mode? As OP says after entering download mode open terminal and use fastboot commands.
Click to expand...
Click to collapse
You need to use vol- and power to go into fastboot mode then connect to the pc. As for userdata and cache, if you don't clean them when coming from stock you will have issues (your data will be encrypted if you're on stock?). As I said this guide worked for me. The op was talking about fastboot mode in the 6th option (also there is much more information in the thread I linked above)
sorry for the confusing i wanted to say fastboot mode..
i knew the thread that you are saying but most people doesn't want to search so I made a little thread only with the needed parts..
I use it myself so I have a place to remember all the steps when I need to change the rom to a new one or when I make experiments and brick my phone XD
If anyone know anything else that should be in here just say, I really want to improve the post
Hi. I just went through the whole process several times (I have tried the different modified boot images from the dedicated post) and my device is still locked [emoji24] any suggestions?
fhartane said:
Hi. I just went through the whole process several times (I have tried the different modified boot images from the dedicated post) and my device is still locked [emoji24] any suggestions?
Click to expand...
Click to collapse
your device will always be locked this is a workaround to get twrp, new roms and magisk while it stays locked..
with twrp usable it won't matter if you are locked or not
PedroM.CostaAndrade said:
your device will always be locked this is a workaround to get twrp, new roms and magisk while it stays locked..
with twrp usable it won't matter if you are locked or not
Click to expand...
Click to collapse
Thanks for the answer. You mean that now I have twrp, I can flash custom Roms with my bootloader locked without any issue?
Envoyé de mon ONEPLUS A3003 en utilisant Tapatalk
Yes if you have TWRP you can install custom ROMs, custom Kernel's, magisk, super su, etc..
the locked bootloader only prevents you from using fastboot commands like the one needed for installing custom recovery
Now that you have TWRP you can use it for everything
Hello everyone, I also have a nexus 5x with motherboard that has been replaced under warranty and unfortunately I can't keep the bootloader unlocked.
I tried the procedure you have indicated, but at this point there is the problem, because after inserting the boot.img and twrp.img inside the phone, then when I go to do the unlocking procedure with 'fastboot oem unlock (select yes on your phone) 'in practice the memory is deleted on the phone, so I lose the previously uploaded files, and therefore I can no longer continue with the flash procedure of boot.img and twrp.img because they are no longer present in memory.
I hope I made myself understood, maybe I am wrong, or is there a way to solve this problem?
Fabiojoker said:
Hello everyone, I also have a nexus 5x with motherboard that has been replaced under warranty and unfortunately I can't keep the bootloader unlocked.
I tried the procedure you have indicated, but at this point there is the problem, because after inserting the boot.img and twrp.img inside the phone, then when I go to do the unlocking procedure with 'fastboot oem unlock (select yes on your phone) 'in practice the memory is deleted on the phone, so I lose the previously uploaded files, and therefore I can no longer continue with the flash procedure of boot.img and twrp.img because they are no longer present in memory.
I hope I made myself understood, maybe I am wrong, or is there a way to solve this problem?
Click to expand...
Click to collapse
fastboot is for the files on your PC not your phone
you need to put the files inside of platform-tools and then open cmd inside it and use the fastboot commands
fastboot will take the files of your PC
Hello, thank you for your information, since I haven't done modding on phones for a long time, I didn't remember exactly the procedure with fastboot and therefore I didn't understand where I had to put the files, but in the end I did it.
Thank you
PedroM.CostaAndrade said:
fastboot is for the files on your PC not your phone
you need to put the files inside of platform-tools and then open cmd inside it and use the fastboot commands
fastboot will take the files of your PC
Click to expand...
Click to collapse
Why is a custom boot image needed? I don't want to root.
Hi.
So I was messing around with the twrp custom recovery and (without thinking much of it) wiped everything in the advanced wipe menu :crying: (System, data, EVERYTHING)
I knew I had removed my OS and that I could just use the twrp recovery to install a new rom onto my phone BUT little did I know, when I tried to boot into the custom recovery, it would just loop the screen with the redmi logo
I am still able to boot into fastboot mode, and I have tried to flash the same twrp recovery but with no avail (It still loops the redmi logo screen)
So now I'm here to ask if there is any advice that you could give me to try and fix this problem that I have gotten myself in (I am not worried about deleting any of my personal files. I would just like to get twrp to boot so that I can install another rom)
Thanks in advance to anyone who can help me with this problem :highfive:
Hi, which rom are you trying to install? for android 9 use this recovery https://forum.xda-developers.com/re...overy-unofficial-twrp-recovery-redmi-t4002397, for android 10 this one... https://forum.xda-developers.com/showpost.php?p=82062075&postcount=7...
If what nuvulet said doesn't work, in fastboot, flash the exact same stock ROM you had before, let it boot and then flash TWRP.
nuvulet said:
Hi, which rom are you trying to install? for android 9 use this recovery https://forum.xda-developers.com/re...overy-unofficial-twrp-recovery-redmi-t4002397, for android 10 this one... https://forum.xda-developers.com/showpost.php?p=82062075&postcount=7...
Click to expand...
Click to collapse
Hi, thanks for the fast reply.
The stock android I had before I wiped everything was android 9, MIUI 11. I tried againt to flash the recovery through fast boot but (like before) when I try to boot into the recovery (by holding the volume up button as it reboots), the redmi logo keeps appearing and disappearing and doesn't go to the twrp recovery. At the current moment I don't have any OS installed (since it got deleted when I wiped everything)
Any other leads I could try?
wang1chung said:
If what nuvulet said doesn't work, in fastboot, flash the exact same stock ROM you had before, let it boot and then flash TWRP.
Click to expand...
Click to collapse
I'm not sure how I can flash the stock ROM without the twrp recovery. I had the impression that you needed twrp recovery in order to install ROMs in the first place.
If there is a method to flash a ROM using fastboot, please explain since my unexperienced self has no idea how to do this. :laugh:
Thanks for the fast reply too
Sqorpz said:
I'm not sure how I can flash the stock ROM without the twrp recovery. I had the impression that you needed twrp recovery in order to install ROMs in the first place.
If there is a method to flash a ROM using fastboot, please explain since my unexperienced self has no idea how to do this. :laugh:
Thanks for the fast reply too
Click to expand...
Click to collapse
MiFlash works through fastboot mode. It's also safer to flash with MiFlash, just make sure you have the correct ROM.
I can't find the guide right now, I'm at work
Ok, do you know adb fastboot... if not, follow this guide...
https://forum.xda-developers.com/showthread.php?t=2317790
Install usb adb drivers for RN8P if you don't have, try this for w10...
https://forum.xda-developers.com/redmi-note-8-pro/help/usb-drivers-t4035617
Download twrp for android 9 or android 10 from here...
https://forum.xda-developers.com/showpost.php?p=82115341&postcount=2
Put the recovery (*.img format) into installed adb folder...
Open cmd and navigate to inside adb folder...
Put the phone into fastboot mode (press volume- and power) connect usb and type in console...
adb devices (this start adb server)
Type...
fastboot devices (this return a device number, if not, something is wrong)
Type...
fastboot flash recovery *.img (change * for the name of the recovery file)
Disconnect the phone and press volume+ and power at the same time and now you have twrp intalled...
When start if the data is encrypted, push cancel, go to wipe, go to format data, type "yes", and confirm slide...
Now connect the phone to usb (if not recognize the phone, go to mount, and enable MTP)
Copy the rom in to internal storage for your android twrp version... search here
https://forum.xda-developers.com/redmi-note-8-pro/how-to/redmi-note-8-pro-android-10-public-t4072795
You have several versions... for eu, search in my post...
And the rest, install, select, etc. etc....
nuvulet said:
Ok, do you know adb fastboot... if not, follow this guide...
https://forum.xda-developers.com/showthread.php?t=2317790
Install usb adb drivers for RN8P if you don't have, try this for w10...
https://forum.xda-developers.com/redmi-note-8-pro/help/usb-drivers-t4035617
Download twrp for android 9 or android 10 from here...
https://forum.xda-developers.com/showpost.php?p=82115341&postcount=2
Put the recovery (*.img format) into installed adb folder...
Open cmd and navigate to inside adb folder...
Put the phone into fastboot mode (press volume- and power) connect usb and type in console...
adb devices (this start adb server)
Type...
fastboot devices (this return a device number, if not, something is wrong)
Type...
fastboot flash recovery *.img (change * for the name of the recovery file)
Disconnect the phone and press volume+ and power at the same time and now you have twrp intalled...
When start if the data is encrypted, push cancel, go to wipe, go to format data, type "yes", and confirm slide...
Now connect the phone to usb (if not recognize the phone, go to mount, and enable MTP)
Copy the rom in to internal storage for your android twrp version... search here
https://forum.xda-developers.com/redmi-note-8-pro/how-to/redmi-note-8-pro-android-10-public-t4072795
You have several versions... for eu, search in my post...
And the rest, install, select, etc. etc....
Click to expand...
Click to collapse
Yes, this is the method I used to flash the twrp recovery.
My problem was that even after installing it (using this method), i would still not be able to boot into the recovery.
However, it is fixed now. I used the Mi Flash tool in order to install the stock rom and then installed twrp after that. :good:
wang1chung said:
MiFlash works through fastboot mode. It's also safer to flash with MiFlash, just make sure you have the correct ROM.
I can't find the guide right now, I'm at work
Click to expand...
Click to collapse
I tried this method and IT WORKED!!
After installing Mi flash I was able to download the stock rom and install it through the program without any errors.
I was then able to finally boot into the OS and install twrp recovery, then install the custom rom! :laugh:
Thanks for this method. I would probably still be stuck on the Redmi logo if it weren't for this