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.
Related
I cant not view files on my internal SD card. For example pictures in the gallery only display blank thumbnails but ARE THERE. This means i cant download anything and save it (Apps from the play store are fine) but i CAN view files with no problem while connected to a computer and move files to my phone on there with no issues but downloading straight to the phone wont work. I was flasing experemental roms when this happend and yes, i did make a back up but this made no diffrence. I have flashed stock 4.0.2, 4.0.3, locked the bootloader, unroooted, re unlocked the bootloader but the problem persists. Any idea's anyone?
Can you clarify if it's only existing files that are already on your phone, or does this happen for all new files created on your phone as well (taking new photos and videos for example).
Sent from my Galaxy Nexus using Tapatalk
-
Yes it does, but apps are not effected. But these are put on a diffrent space on the phone i think. But no, for example when i take a picture it will not save it, i cannot download files of the internet either. Any idea's would be appreciated
JustArchiee said:
[snip]
Any idea's would be appreciated
Click to expand...
Click to collapse
Copy your data to your computer, erase all the partitions on your device, and re-flash your ROM.
efrant said:
Copy your data to your computer, erase all the partitions on your device, and re-flash your ROM.
Click to expand...
Click to collapse
+ 1
Sent from my Galaxy Nexus using Tapatalk
Ok just to make sure (Yes - im a noob) just plug it into the computer and wipe everything yes?
How to wipe your device completely
JustArchiee said:
Ok just to make sure (Yes - im a noob) just plug it into the computer and wipe everything yes?
Click to expand...
Click to collapse
N00b step-by-step
1) Ensure you have the drivers installed properly on you computer;
2) Copy everything you want to keep off of your device (i.e., to the cloud, to your computer, etc.);
3) Reboot your device into fastboot mode: turn it off, then hold vol+ & vol- & press and hold power;
4) Plug your GN to your computer;
5) Download the attachment to your computer, and extract the contents to a directory;
5a) Download this and extract the files within to the same directory (extract ALL archives, including the zip inside the second archive);
6) Open a command prompt in that directory;
7) Make sure your computer recognizes your device by typing: fastboot devices
8) Wipe everything by typing the following:
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot erase recovery
fastboot erase cache
9) Flash the ICL53F system partition: fastboot flash system system.img
10) Flash the ICL53F data partition: fastboot flash userdata userdata.img
11) Flash the ICL53F boot partition: fastboot flash boot boot.img
12) Download CWM from here, save it to the same directory and rename it to cwm.img
13) Flash CWM: fastboot flash recovery cwm.img
14) Now you are on the stock ROM with CWM recovery. You can flash whatever ROM you want now in recovery.
Ok all good till '9)' i get 'cannot determine image filename for system.img'
Is there a certion way to open Command prompt?
Ahh don't worry i used wugfreash to flash everything. Thanks so much for you help - Will donate
JustArchiee said:
Ok all good till '9)' i get 'cannot determine image filename for system.img'
Is there a certion way to open Command prompt?
Click to expand...
Click to collapse
For others whovarevhaving that issue: you need to extract ALL the archives. There is a zip inside the archive inside the main archive...
Sent from my Galaxy Nexus using Tapatalk
This may have been a permissions issue. I wish I'd replied sooner
Sometimes pushing files to /sdcard from an incorrectly programmed ROM or over ADB in recovery can result in making "root" the owner of all the files. I experienced this when I pushed a bunch of files to my phone over ADB while in ClockworkMod.
I posted a solution here: http://forum.xda-developers.com/showthread.php?p=23767694
Getting GN tomorrow, I've read all the [REF] posts and I've been working with Samsung devices since Samsung has been making devices.
I know little about Nexus devices, and I am surprised at how easy this process seems to be.
Naturally I'm suspicious, so I come to you to make sure I have this all straight:
1 adb fastboot oem unlock
2 rom manager > install clockworkmod
3 flash rom/gapps in recovery
Ya? No ODIN? No messing with partitions? Is it really as easy as these 3 steps?
kthanks
Step 1.5 is to root while using fastboot. Use efrant's guide in the "stickies" for the commands and sequence. It's very easy.
If you follow your steps as you wrote them (without the rooting commands in fastboot) then ROM Manager will install but you won't be able to flash the CWM recovery because there is no root.
Good luck!
Doc_rockulus said:
Getting GN tomorrow, I've read all the [REF] posts and I've been working with Samsung devices since Samsung has been making devices.
I know little about Nexus devices, and I am surprised at how easy this process seems to be.
Naturally I'm suspicious, so I come to you to make sure I have this all straight:
1 adb fastboot oem unlock
2 rom manager > install clockworkmod
3 flash rom/gapps in recovery
Ya? No ODIN? No messing with partitions? Is it really as easy as these 3 steps?
kthanks
Click to expand...
Click to collapse
Learn to do it all yourself, makes life a LOT easier!
1. fastboot oem unlock. Phone will reboot once you've done this so once booted go back to the bootloader
2. fastboot flash recovery recovery.img (download the latest CWM here and rename it recovery.img)
3. fastboot reboot
4. Once back in Android copy the ROM to your phone (and GAPPs if you need them). I'd also use a wipe script to format the phone before flashing the new ROM. You can get mike1986's one here
5. Turn on USB Debugging
6. adb reboot-bootloader
7. Go into recovery
8. Flash Super Wipe script (if you're going to use one)
9. Flash ROM
10. Flash GAPPs (if required)
11. Reboot phone
12. Enjoy!
EddyOS said:
Learn to do it all yourself, makes life a LOT easier!
1. fastboot oem unlock. Phone will reboot once you've done this so once booted go back to the bootloader
2. fastboot flash recovery recovery.img (download the latest CWM here and rename it recovery.img)
3. fastboot reboot
4. Once back in Android copy the ROM to your phone (and GAPPs if you need them). I'd also use a wipe script to format the phone before flashing the new ROM. You can get mike1986's one here
5. Turn on USB Debugging
6. adb reboot-bootloader
7. Go into recovery
8. Flash Super Wipe script (if you're going to use one)
9. Flash ROM
10. Flash GAPPs (if required)
11. Reboot phone
12. Enjoy!
Click to expand...
Click to collapse
To clarify, the fastboot oem unlock command only unlocks the bootloader, correct?
At what part of the process is root obtained? I've never seen/tried a CWM flash prior to root/SU.
Am I obtaining root simply by flashing the root enabled rom?
I wouldn't call that "Doing it myself"
That's right. Once the bootloader is unlocked you can then flash new files to the different partitions on the device (system, data, recovery, boot, etc...). Root is obtained when you flash the SuperSU package in CWM or when you flash a custom ROM (as they tend to be pre-rooted)
When I say 'do it yourself' I mean all the steps of unlocking the bootloader, flashing CWM manually, etc. as opposed to using apps that do it all for you
Doc_rockulus said:
Getting GN tomorrow, I've read all the [REF] posts and I've been working with Samsung devices since Samsung has been making devices.
I know little about Nexus devices, and I am surprised at how easy this process seems to be.
Naturally I'm suspicious, so I come to you to make sure I have this all straight:
1 adb fastboot oem unlock
2 rom manager > install clockworkmod
3 flash rom/gapps in recovery
Ya? No ODIN? No messing with partitions? Is it really as easy as these 3 steps?
kthanks
Click to expand...
Click to collapse
yup, that's pretty much it.
1. fastboot OEM unlock
2. fastboot flash a custom recovery(differs from ROM manager)
3. flash the su binaries or a custom ROM in your new recovery
4. reboot and profit
Put the rom you want on your sd card before you do any of this actually. Then get yourself into fastboot mode. Then do the
fastboot oem unlock.
Fastboot flash recovery "name of recovery.img"
fastboot boot recovery
Install ROM
Actually come to think of it, maybe the oem unlock erases sd card, putting ROM on before unlocking might not be good. Most roms have root permission anyhow so you don't gotta worry about getting root if your flashing a custom rom.
M3drvr said:
Put the rom you want on your sd card before you do any of this actually. Then get yourself into fastboot mode. Then do the
fastboot oem unlock.
Fastboot flash recovery "name of recovery.img"
fastboot boot recovery
Install ROM
Click to expand...
Click to collapse
if you put the rom you want in your storage before you fastboot oem unlock, then it wont be there when you need to flash it, considering the contents of your storage gets erased when you fastboot oem unlock.
simms22 said:
if you put the rom you want in your storage before you fastboot oem unlock, then it wont be there when you need to flash it, considering the contents of your storage gets erased when you fastboot oem unlock.
Click to expand...
Click to collapse
Ya i thought of that after i posted. That was my bad. Although you could boot into recovery, mount the sd card so computer sees it, copy the rom into phone then flash it. Rather than rebooting to system and using rom manager.
M3drvr said:
Ya i thought of that after i posted. That was my bad. Although you could boot into recovery, mount the sd card so computer sees it, copy the rom into phone then flash it. Rather than rebooting to system and using rom manager.
Click to expand...
Click to collapse
No you can't mount the sdcard as the nexus does not have mass storage
Sent from my Galaxy Nexus using Tapatalk 2
Zepius said:
No you can't mount the sdcard as the nexus does not have mass storage
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Then i have a messed up phone, cause when i'm in recovery i can drop files into my phone from my computer.
M3drvr said:
Then i have a messed up phone, cause when i'm in recovery i can drop files into my phone from my computer.
Click to expand...
Click to collapse
+1
Thanks guys, I've got it. Rooted, CM10.1 in record time.
First device I've had that hasn't put up a fuss during this process.
Now that I'm in CM10.1 can I use AOSP kernel or do I need one based off of CM?
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.
This is a basic guide to flash a rom via recovery in Mi A3 as title says.
Is created to help all those that want but can't.
Please read before act, and if you don't understand....well read again.
Mi A3 is a device with treble support, and while is not difficult to flash a rom,is a little bit tricky process.
So here are the detailed steps to do achieve that.
First things first, you've got to have your bootloader unlocked. Follow below steps to do that:
-Enable developer options by going to settings/about phone and clicking 5 times on build number.
Inside developer options:
-Find and enable OEM unlocking.
-Find and enable USB debugging.
In adb tools type:
-
Code:
adb devices
reboot to bootloader.
-
Code:
adb reboot bootloader
Unlock bootloader(you will lose all your data).
Code:
fastboot flashing unlock
When the device reboot, boot once again in fastboot by powering off then power on while pressing vol down button.
Type command to full unlock bootloader.
Code:
fastboot flashing unlock_critical
Proceed to recovery flash
Notice that you've got to have all files ready, either inside external sd or in your pc. All files are at the end of this thread as links or attachments.
Also i'm suggesting OrangeFox recovery for now because is the most stable.
-First you following the orangefox recovery installation guide:
- Download the OrangeFox zip file from here or the link at the end and copy it to your device (internal or external storage)
- Extract the recovery.img from the zip and store it, on the folder where you have adb and fastboot files, on your PC
- Open a cmd line and execute these commands (being on that folder, of course):
-
Code:
adb devices
(to make sure your device is detected)
-
Code:
adb reboot bootloader
(to reboot into fastboot mode)
-
Code:
fastboot getvar current-slot
(to check what's your current active slot)
-
Code:
fastboot set_active b
(if your active slot was a, if it was b then change it to a)
-
Code:
fastboot erase boot
-
Code:
fastboot flash boot recovery.img [b](OR WHATEVER NAME YOUR RECOVERY HAVE)[/b]
-
Code:
fastboot reboot
(NOTE : Before hitting "Enter", long press Vol + on your device until you see the Android One logo.
-->> By doing this your device will be forced to boot into Recovery and not into System <<--
- Install the OrangeFox zip (always install the latest build available and always keep a copy of recovery zip file in your external sd)
- Change slot to the one that was active on the beginning of these steps and reboot to Recovery (just to make sure that the slot, in fact, was changed)
After orangefox recovery is installed, you are ready to flash your rom.
You can move your rom files inside your external or internal memory(prefer external to avoid deleting them accidentally).
To do that you can either do it before the whole procedure, or after the recovery installation since you have mtp and adb available.
Copy them drag them or push them via adb(i'm not going to extend the adb push command here)
Now the flashing steps:
-Go to partition manager inside orangefox recovery and select data/format data(red button) and press format.Type YES.
-Go back and find the rom file inside your target directory(internal or external).
-Select the rom file and flash it.
-DO NOT REBOOT.
-Go back where you have the orangefox zip file, select it and flash it.
-Leave the device as is because after the installation it will reboot itself to recovery once again.
-Once the recovery starts again go to the target folder that you have the remaining files.
-Flash magiskV20.zip (if you want your device to be rooted).
-Flash Gapps if there are any or skip this step if your ROM provider have them included.
-Flash patchnofde10 zip to avoid data encryption(if you don't do that the rom will NOT boot).
-Reboot to system and enjoy.
All files are available to the links below.
Patchnofde file is attached to this post.
I'm not responsible if you cause a nuclear war or your cat or dog stop talking to you.
Credtits to:
Orangefox recovery team https://orangefox.tech/
Orangefox recovery dev for Mi A3 https://forum.xda-developers.com/mi-a3/development/official-orangefox-recovery-mi-a3-t3986177
Topjohnwu for the Magisk and Magisk manger https://******************/
XDA Forum because they exist
All devs that put some hard work for you to have a custom recovery and a custom rom and all they hear is questions about ho to do things.
Respect them and read before post a questions.
:angel::angel::angel:
Thanks for the detailed guide, always good to have it :good: :good:
my device is encrypted and if I boot a recovery it shows the data encrypted. How to remove encryption ?
drozo8o8 said:
my device is encrypted and if I boot a recovery it shows the data encrypted. How to remove encryption ?
Click to expand...
Click to collapse
Read it first then do it.
Patchnofde is for the encryption.
sotmax said:
Read it first then do it.
Patchnofde is for the encryption.
Click to expand...
Click to collapse
nvm I think I got it
Can anybody please help? I just bought this phone and followed this guide to the letter. The phone just boots back into recovery, whatever ROM I flash.
Is there support for Android backup and restore
Please tell steps for the same also
As it is not working for me
Mobile is Booting to recovery again after restoring backup
ReekyMarko said:
Can anybody please help? I just bought this phone and followed this guide to the letter. The phone just boots back into recovery, whatever ROM I flash.
Click to expand...
Click to collapse
Okay I got it to boot to Havoc OS but my wifi and gsm calls stopped working. Also videos were flashing during playback. I guess I was doing something wrong during the whole flashing process and the device ended up without the correct firmware.
I have reverted back to stock using one of the fastboot ROM flashing scripts and everything is fine, though I would like to go Android 10 without GAPPS if possible.
Thank you very much for the guide. Do you recommend any backup with orange box? If I want to revert to stock rom, do I need to know something?
How could I update the ROM?
darkjm93 said:
Thank you very much for the guide. Do you recommend any backup with orange box? If I want to revert to stock rom, do I need to know something?
Click to expand...
Click to collapse
You can go back to stock by flashing stock image with mi flashtool
ReekyMarko said:
Can anybody please help? I just bought this phone and followed this guide to the letter. The phone just boots back into recovery, whatever ROM I flash.
Click to expand...
Click to collapse
That's because you didn't follow it to the letter.
You have to flash Patchnofde to boot to rom.
vishwadeepmanu said:
Is there support for Android backup and restore
Please tell steps for the same also
As it is not working for me
Mobile is Booting to recovery again after restoring backup
Click to expand...
Click to collapse
Same as above.
If you don't flash patch for the encryption, you ll end up to recovery again. Also I recommend to read carefully the steps with the recovery flashing. You have to be sure that the slot is what it was at the beginning.
A out the Android backup, yes. You can take and restore backups freely.
Hello,
@sotmax
Thank you for your guide.
@ANyOne i have unlocked the bootloader, but after that, when i'm in fastboot mode, i'm not being detected by the adb devices command. Any idea why ?
mkpanic said:
Hello,
@sotmax
Thank you for your guide.
@ANyOne i have unlocked the bootloader, but after that, when i'm in fastboot mode, i'm not being detected by the adb devices command. Any idea why ?
Click to expand...
Click to collapse
Because ADB and fastboot are different modes and using different commands. In fastboot use "fastboot devices".
_mysiak_ said:
Because ADB and fastboot are different modes and using different commands. In fastboot use "fastboot devices".
Click to expand...
Click to collapse
Thank your for the answer.
If I only want to root the stock installing Orange, this guide works?
fastboot set_active command is not working...only fastboot options are displayed..Any solution?
sibikallikkat said:
fastboot set_active command is not working...only fastboot options are displayed..Any solution?
Click to expand...
Click to collapse
fastboot --set-active=a
fastboot --set-active=b
hi, i followed the guide to flash los17 with BiTGApps.
I also flashed the nofde patch. The phones boots normaly but i have no access to internal storage. All the folders have random numbers and letters. Any ideas?