Hey,
Here's the context: I tried to install Elite ROM.
In the instructions there was this: "Wipe Everything in wipe section (dont wipe sdcard) and Change FileSystem of DATA Partition only to f2fs & FORMAT Data otherwise phone wont boot".
I was in TWRP and followed instructions.
Wipe everything: OK
Change filesystem of data partition to f2fs: OK
Format the data partition: not OK. It said me
Code:
/data : Device or resource busy.
. I couldn't do anything from there, or I thought this way at least... I think the f2fs filesystem f*cked it.
First error: I rebooted my phone. So yeah, now I'm not in TWRP anymore. I tried to boot into Recovery but Vol Up + Power brought me to Huawei eRecovery. I tried the Huawei eRecovery but it didn't work. Expected, because I installed TWRP and apparently it doesn't work anymore when you flash it. So OK.
Basically I want to get into TWRP because I could maybe solve the problem from here. I don't know how to solve this Device or resource busy, but there is a solution, like always.
Now, there is a problem. When I do
Code:
adb devices
or
Code:
fastboot device
, I get nothing. BUT, something encouraging is that I have HiSuite that shows up when I connect my phone to the PC, everytime, even if I close it. But then, HiSuite tells me to connect my phone, so I think it doesn't recognize the phone fully. Maybe it recognizes some hardware in my phone that matches Huawei phones, but still not really recognizing my phone. My phone is not appearing on the device list of Windows, I just have a "USB Mass Storage Device" in the USB controllers.
UPADTE: I managed to go into TWRP by pressing Vol Up + Vol Down + Power, so no need of ADB for now. I'm updating. Below, only for informational purpose.
UPDATE 2: As I managed to boot to TWRP, I was able to format /data and to install Kernel & ROM from my SD card! To boot in TWRP and not eRecovery, make sure you're pressing Vol Up + Vol Down + Power and not only Vol Up + Power.
The goal is to force ADB to see the phone so I can interact with it
So for now I have several theories I tried to follow, without success:
- Forcing Debugging mode on my phone (maybe it's only that)
- Find a version of ADB that can see the phone
- Find drivers that can recognize the phone fully
An other way could be to backup the partitions saved before in TWRP. But as I can't access to TWRP without ADB on this phone, for now I don't believe this is a path to explore.
Have you any other theories, and have you solutions for these 3 majors theories?
Thank you so much and see you,
Celgost
[VolUP]+[Power] - This works if the phone is turned off. When the "data" is busy, you need to reboot into the recovery mode from the TWRP.
It's true but not totally in that case. If you aren't in TWRP anymore and wiped all partitions, you cant Access TWRP neither with ADB nor with Vol UP + Power. Because Huawei added eRecovery, which coexists with other recoveries. My theory is that eRecovery is one layer below regular recoveries. You Can Access twrp only with Vol UP + Vol Down+ Power. I suppose there is a strict condition to boot into erecovery when there is not for Twrp.
It works always, you just need to release the buttons, after the appearance of the logo.
Related
[Q] HELP!!! Cant access recovery mode & WiFi isnt connecting at all [MIUI 1.11.25]
After I upgraded to the new MIUI rom, I noticed that the Gmail app and the Email app where crashing all the time so I thought it would be a good idea to to wipe the Dalvik cache, do a factory reset and reinstall the ROM...
I wanted to clear everything and start new... so I wiped the sdcard, sd-ext, data/cache, dalvik... then i flashed the Miui rom and made a new sd-ext3, made it 1Gb... the phone restarted normally, i installed the a2sd on the sd-ext3, everything was fine, I started re-downloading my programs. but then I restarted the phone and all the program I had installed were gone... and the a2sd+ partition was showing 0.00B of space while myy sdcard was showing that there was 1Gb missing... worse, the gapps (gmail, market etc) were gone... thought another factory reset would solve the issue, so I went into the settings/system/about phone/factory reset... it brought the gapps back but the a2sd was still showing 0.00B of space. not only that, but I couldnt connect to my wifi anymore (it keeps saying "obtaining ip adress")... also, ever since, I cant factory reset anymore... as soon as I do, the phone restart and is stuck in a bootloop... so I have to take out the battery and put it back to switch it on properly...
I tried to reboot it in recovery so that i could both reflash the MIUI ROM and re-install the sd-ext3 with less memory this time... but I couldnt get into the recovery mode no matter what. it was amon ra v2.2.1 recovery... I downloaded Rom Manager from the internet so I could switch recoveries, and I switched to clockworkmod, but still couldn't access the recovery. I thought Rom Manager wasnt not working properly so I tried flashing new recovery image through adb and fastboot, but it wouldnt even let me do it... looked for ways to bypass the recovery mode and flash the rom but it still wouldnt work... So now im stuck with the phone unable to go into recovery mode.
The phone otherwise still works, I still get and can make phone calls, but I cant connect to the internet unless using my credit, and even that for some reasons does not allow me to connect to google servers, meaning that I cannot use the Market...
How can I get My phone to work properly again?
I know you might have done this but I gotta ask the following:
- Did you pull out the battery, put it back in, and hold POWER + Trackball + Volume Down until you got to fastboot. Then select the recovery option?
- Can you please tell me what exactly it said when you tried to flash a new recovery to your phone via adb? What commands did you use to flash it in the first place.
Please provide more details so we can help you.
Is your phone unlocked? If so, the easiest way is to just reflash a recovery image using:
Code:
fastboot flash recovery "C:\location\to\recovery.img"
Then you can boot directly into the new recovery by changing the flash command to boot.
Code:
fastboot boot recovery "C:\location\to\recovery.img"
Then I would wipe the /system partition and reinstall MIUI.
Start a fastboot mode:
+ Download the fastboot http://dl.dropbox.com/u/8180983/N1/fastboot.zip
+ Extract the contents of fastboot.zip to some directory of your
preference
+ Download the su.zip http://dl.dropbox.com/u/8180983/N1/su.zip
+ Copy to the root of SD * Do not extract the contents, simply copy
to the root of SD *
+ Turn off your phone
+ Press and hold the trackball, press the power
+ The phone will connect in fastboot mode
+ Plug the USB cable
+ You will see a highlighted message "USB fastboot"
2 Unlock your bootloader:
<WARNING - This procedure below deletes all your
SETTINGS!>
+ At the command prompt / terminal, go to the directory where you
Drew fastboot.zip
+ If rWindows:
+ Go to Start> Run> cmd
+ Use the cd command to access the directory where you extracted the
fastboot.zip
+ Type-windows.exe fastboot devices
+ In the list will show your device
+ Type fastboot-windows.exe oem unlock
+ If it is Linux:
Run the + terminal of your choice
+ Use the force, become as root (su -)
+ Go to the directory where you extracted using fastboot.zip
cd
+ Enter. / Fastboot-linux devices
+ In the list will show your device
+ Enter. / Fastboot-linux oem unlock
+ If Mac, use the same steps as replacing the Linux
for fastboot. / fastboot-mac
+ Confirm unlocking
+ Now your phone will accept any customROM
3 Install any custom recovery:
- I used ClockworkMod, but there are others, such as Amon_Ra's.
http://mirror1.kanged.net/recoveries/recovery-clockwork-2.5.1.4-passi ...
+ If linux:
+ With the phone connected to usb fastboot mode and type:. /
linux-fastboot flash recovery <caminho/ para/ o/ arquivo/> / recovery-
clockwork-2.5.1.4-passion.img
+ If windows:
+ With the phone plugged into usb mode and type fastboot: fastboot-
windows.exe flash recovery <caminho/ para/ o/ arquivo/> / recovery-
clockwork-2.5.1.4-passion.img
+ If MAC:
+ With the phone connected to usb fastboot mode and type:. /
fastboot-mac flash recovery <caminho/ para/ o/ arquivo/> / recovery-
clockwork-2.5.1.4-passion.img
+ Okay, you installed a custom recovery and now has several
features such as nandroid backup / restore and etc..
- Accessing the custom recovery
Press + power and return to the bootloader menu, you will see an option
called RECOVERY, select it using the volume buttons and press
power to start the customrecovery
+ Will load a black screen with an exclamation point, press power
and the volume +
+ You are on the menu, scroll using the trackball or the keys
volume, to select, press the trackball
demoneyes905 said:
I know you might have done this but I gotta ask the following:
- Did you pull out the battery, put it back in, and hold POWER + Trackball + Volume Down until you got to fastboot. Then select the recovery option?
- Can you please tell me what exactly it said when you tried to flash a new recovery to your phone via adb? What commands did you use to flash it in the first place.
Please provide more details so we can help you.
Click to expand...
Click to collapse
I could get to the fastboot and was selecting the recovery option, but then it was stuck in a bootloop. When I was trying to flash using the command prompt it was saying that there were errors. but Dont worry, I fixed it. Turns out the errors were due to the fact that the command couldnt find the location of the image...
Something strange happened to me when i wiped all the partitions of my phone in TWRP 2.5.0.0,when the process whas ended, i found a strange directory called "0" and other one "twrp" in my internal memory...well,my sdcard is almost here. Now i want to flash a new rom via adb sideload or ad push....always different errors happened...OMG,may i use a pendrive with otg cable? What happened with my internal memory?
I thinked my device had a partial brick...this is not the first time i had problems like that, it happens to me in a One S when i did a factory reset via bootloader with no-stock recovery. I find a solution in that thread
http://forum.xda-developers.com/showthread.php?t=1630459
So i have tried the same solution on my one and it works fine.
1.Reinstall stock recovery from here in the way indicated.
http://forum.xda-developers.com/showthread.php?t=2265618
2.Enter bootloader and use the option "factory reset"
3.Wait until process is complete(you will see a phone with a green exclamation ).
4.The phone will reboot,push volume down button until enter in bootloader.
5.Use option fastboot and reflash your favorite recovery.
Voila!! Adb will recognice your device and you are now able to send any file to yur sdcard.
Thanks to all the people who has developed all tools needed for that solution
For Phone specs see signature.
I've damaged my display i.e. my LCD is broken so nothing is displayed but I can turn the phone on as my morning alarm does go off and the 'menu' and 'back' controls light up so board is functioning.
I have decided to sell it as is, so someone else can faff around with it if they want to repair it. What I need to do now is try and wipe my data off of the phone before selling.
BUT...I'm not sure what the steps are for the N7000. I have downloaded the Android SDK and ODIN. Have also seen these instructions elsewhere...
1. Download factory_reset.tar.md5
2. Open ODIN
3. put factory_reset.tar.md5 in PDA section and do not check/uncheck anything else...
4. Put your phone in download mode and connect it to PC..........................Not sure how to put the N7000 into download mode, tbh I had only ever heard of recovery mode. Instructions were as follows....
Volume down + home +power
That will lead to warning Page
Here you have to press volume up to enter download mode.
5. Hit start and it will flash and reboot.................................What exactly am I flashing here? I thought we were just wiping data why do I need to flash anything?
Is there another or better way of wiping the data or will the above work?
Thanks
What is the recovery you have? (before you say gain to check your signature, it states philz and running 4.2.2. So confused.).
Vol up + home + power for about 10 seconds should take you to recovery mode. Connect phone to pc and run adb devices. Check if the device is listed. Then using some Linux commands you can wipe data and your internal sd card.
About adb please Google.
Using odin, if you have the file you mentioned, (idk much about the file) but what it seems to do is when flashed using odin it will run flash a blank data & cache partiton thus performing factory reset. This will not wipe your internal storage.
nokiamodeln91 said:
What is the recovery you have? (before you say gain to check your signature, it states philz and running 4.2.2. So confused.).
Vol up + home + power for about 10 seconds should take you to recovery mode. Connect phone to pc and run adb devices. Check if the device is listed. Then using some Linux commands you can wipe data and your internal sd card.
About adb please Google.
Using odin, if you have the file you mentioned, (idk much about the file) but what it seems to do is when flashed using odin it will run flash a blank data & cache partiton thus performing factory reset. This will not wipe your internal storage.
Click to expand...
Click to collapse
Thanks for getting back to me. Never got 'adb devices' to work, don't know why. For the first time I've managed to get access to see my internal storage. As I had pattern security enabled on the phone I assume I must have managed to get into recovery mode and do what I believe was a factory reset.
Am I right in assuming my personal data i.e. contacts data has been deleted?
Don't know. What exactly did you do?
Hello
after i rooted my z3 compact and stuff i thought "hey, encrypting the data would be nice and safe" and did so.
after this i wanted to install some zip via recovery-mode and there are just errors telling me "cannot mount sdcard" and smth like that
i assume this is because the sdcard is encrypted.. .
did anyone know how i can use recoverymode again without flashing the whole firmware back again? oO
thank you
I have the same situation. Can't even enter recovery. You can copy paste files from the zip in the system with for example root explorer, set the correct permissions and reboot.
A working recovery would be better.
I'm on 6.0.1, rooted, locked bootloader and encrypted phone. Can't seem to enter recovery either. There's no green LED on phone reboot. Tried Power + vol up/down, no luck. Also volume up/down during boot, also nothing.
Is there no way to access recovery now?
sil_el_mot said:
did anyone know how i can use recoverymode again without flashing the whole firmware back again? oO
Click to expand...
Click to collapse
There is a TWRP 3.0.2.0 for Z3c available here
Apparently it does work with encrypted partitions, but you will probably have to encrypt the phone after installing TWRP, so this won't help you out of your situation.
Edit: there is a manual install of TWRP compatible with MM, once in recovery you could flash the 3.0.2.0 version and restart to recovery, but I haven't tried this and you may well end up in a bootloop with an unreadbale encrypted partition.
sil_el_mot said:
after i rooted my z3 compact and stuff i thought "hey, encrypting the data would be nice and safe" and did so.
after this i wanted to install some zip via recovery-mode and there are just errors telling me "cannot mount sdcard" and smth like that
i assume this is because the sdcard is encrypted.. .
did anyone know how i can use recoverymode again without flashing the whole firmware back again?
Click to expand...
Click to collapse
for those of you who have a working recovery and encrypted data partition and SDcard, there are two ways of using it:
1. VIA ADB SIDELOAD: TWRP have a ADB sideload feature. it means you can flash .zips directly from your computer, connected to your phone wia USB cable. steps: 1. go to TWRP, search for ADB sideload feature and turn it ON, 2. connect your phone to your computer, 3. open terminal on your computer and type:
Code:
ADB sideload "path/to/your/file.zip"
. bingo!
2. VIA USB OTG: Z3c support USB OTG (On The Go) so you can connect your USB key to your phone via USB OTG cable. you put .zips you want to flash to your USB, connect it to your phone when in TWRP and flash them from USB instead of encrypted partitions.
Hi All,
I've run into an issue whilst trying to flash LOS 15.1 on a Moto x4 (XT1900-01). After flashing LOS 15.01, I get the message "No OS Installed! Are you sure you wish to reboot?" for every Reboot menu option available in TWRP (3.2.3-1) (reboot options from Reboot menu: System, Recovery, Bootloader, Slot A, Slot B). I'm not sure what happened. Here are the steps I took prior to hitting this:
1. Unlocked the bootloader
2. Flashed TWRP per the instruction on TWRP for Payton on TWRP site
2-1. fastboot boot twrp-3.2.1-1.img
2-2. adb push twrp-3.2.1.zip /sdcard
2-3. Installed the twrp-3.2.1.zip from TWRP (apparently to install to boot partition on both slots)
3. Installed LOS 15.01:
3-1. Formatted via TWRP by doing Wipe -> Format Data
3-2. Advanced Wipe via TWRP by doing Advanced Wipe -> Select System
3-3. copied LOS to sdcard: adb push Lineage15.zip /sdcard
3-4. TWRP Install by Install -> select the Lineage15.zip
4. Once complete, select reboot and this is where the message "No OS Installed! Are you sure you wish to reboot?" comes up.
I haven't opted to reboot for fear of not being able to get back to recovery. I'm not sure what to do at this point. I'd like to understand what happened, but I would also like to find a way to recover from this and either get back to square 1 with stock ROM or even better complete the LOS install. Thanks in advance!
Just reboot recovery
St.Noigel said:
Just reboot recovery
Click to expand...
Click to collapse
I tried to reboot to recovery ignoring the error, I get nothing now. Phone won't turn on, can't key combo (vol up + power, vol down + power, any of them) and it just seems dead now. I've held each of the key combos for a couple minutes each, nada. Any thoughts from here?
mikeybravo said:
I tried to reboot to recovery ignoring the error, I get nothing now. Phone won't turn on, can't key combo (vol up + power, vol down + power, any of them) and it just seems dead now. I've held each of the key combos for a couple minutes each, nada. Any thoughts from here?
Click to expand...
Click to collapse
Did you try to connect phone to the PC? Is phone charged?
St.Noigel said:
Did you try to connect phone to the PC? Is phone charged?
Click to expand...
Click to collapse
Yes, phone was at about 98 percent when doing reboot. Plugged into computer (Mac), adb devices returns nothing. Not sure how this could've gone as bad as it seems it did? Not sure of anything else I can try here...
have you access to Windows or Linux PC? I know nothing about Mac... (
St.Noigel said:
have you access to Windows or Linux PC? I know nothing about Mac... (
Click to expand...
Click to collapse
Yes, I plugged into both Mac and PC. MDM installed on PC as well adb tooling. Plugging into either computer does nothing, doesn't show up in device list. Tried the key combos while connected to each (vol up + power, vol down + power, power, power + vol up + vol down all for a couple/few minutes each). What I don't understand is what the heck happened. TWRP should've been flashed to boot on both slots based on TWRP docs for Payton. I read something about some issues with A/B slot switching (or not switching), but if TWRP was flashed to boot on both slots, I would've expected to at least be able to get back to recovery? I'm not really sure what to do from here since I can't even get the phone to turn on.
I have had seen that message on my phone too. I just reboot and it works just fine.
I ran into the same problem. I managed to fix my phone. From what I understand this happens if no OTA update was flashed before to initialize the partition structure in slot B. Check out [1] which suggests to install copy-partitions-payton.zip via sideloading it into TWRP before installing Linageos.
Concerning your brick: Your phone should still be recognized by your computer. Check the device manager or lsusb on Linux. For me I got something like "Qualcomm, Inc. Gobi Wireless Modem (QDL mode)". Reading through the threads [2,3,4] it became clear to me that I needed a "blankflash" or the qboot utility to recover the phone. The utility talks to the phone via a serial interface over USB. Look through the threads to find the qboot utility. I needed many tries to find the correct qboot utility and to get it to successfully blankflash my phone. The --debug=2 command-line switch of qboot helped me to get confidence that something is happening at all. I needed to press vol+ and power before starting the qboot utility with "./qboot blank-flash --debug=2" on Linux. I think it was also necessary to then _not_ hold these buttons for too long. As I said the debug outputs help to figure this out. Good Luck!
[1] https://forum.xda-developers.com/moto-x4/development/rom-lineage-os-15-1-t3802265
[2] https://www.reddit.com/r/LineageOS/comments/9yahhc/i_hardbricked_my_new_phone_looking_for_advice/
[3] https://forum.xda-developers.com/moto-x4/help/moto-x4-hard-brick-t3777529
[4] https://forum.xda-developers.com/moto-x4/help/q-howto-x4-to-los-setup-bricked-t3883645
@macin42, thanks for the info on this. It makes sense, and I will give it a go. I'll follow up with the outcome as soon as I do; planning by the end of the weekend to give it a go.
@macin42, your instructions worked perfectly! Thanks so much for the help on this. As a recap on the issue: the problem for me was that I skipped the "Copy Partitions" step as it was a new phone and the phone hadn't received any "first" OTA updates. This step was necessary and wasn't mentioned in the official LineageOS install instructions on the LineageOS site. This step was mentioned however on the XDA LineageOS install instructions.
To recover from this, I followed the instructions that were given as help above by doing the following:
1. Downloaded the blankflash.zip from link provided above
2. Installed the Motorola Device Manager drivers (already had)
3. Installed adb and fastboot (already had)
4. Plugged in phone to PC via USB
5. Ran the following command while holding down the power up + volume buttons: qboot blank-flash --debug=2
NOTE: The qboot command didn't work for me the first time, but I re-tried a couple of times and it ended up working after the second or third try.
6. Once this completed the phone turned on and made it to the bootloader.
7. Once I made it here I was able to redo the steps that were given on the XDA thread to install LineageOS (post above), which were:
- Download the Copy Partitions zip from link above then:
- fastboot boot twrp.img
- adb sideload copy-partitions-payton.zip
- In TWRP, click "Wipe", "Format Data", then type "yes" as prompted.
- adb sideload lineageos-nightly.zip
- Navigate back to the Reboot menu in TWRP, select reboot, then select recovery, swipe to reboot. I did get the same "No OS installed" warning here but it wasn't an issue.
- This brought me to the LineageOS recovery.
- I chose to install Mind the GApps, so from the LineageOS recovery I selected Apply Update, Apply from ADB, then on computer adb sideload mind-gapps.zip
- Reboot
From here it was business as usual with the typical phone setup. Thanks again to those that helped on this!
Glad it worked out. In case your microphone and or sound does not work (silence in calls, recorder app does not work) please let me know - that's where i am currently stuck with my xt1900-7.