Related
i was trying to flash the firefox os and while i was fastboot flashing the system.img it got stuck and said failed. i then flashed the twrp recovery but then couldn't find my back up and if i try to sideload it says E:Unable to mount /system, /cache then also can't open destination log file: /cache/recovery, need help thanks
Flash the stock images
Chromium_ said:
Flash the stock images
Click to expand...
Click to collapse
i tried doing that but in between the system flash it failed, i was able to get a rom on by ad pushing, couldn't sideload but now im trying to go back through flashing the stock images and it just gets stuck at sending something everytime
Guys, i just bought an used Nexus 4 and after flashing the cwm recovery and trying to boot in the recovery mode i get a few errors stating:
cant mount cache/recovery
cant open cache/recovery
I notice there are a few topics about this and the solution is to adb push or something, but the adb push command wont work in recovery for me, says device not found and i know my drivers are correct since i can fastboot and do stuff.
I actually got the device running perfectly flashing Chroma via sideload, but cwm wont work! I cant access anything from inside cwm... I also tried twrp and no luck.
I also tried a full original image flash, no luck
Can you please help me with this?
Thanks
luizffgarcia said:
Guys, i just bought an used Nexus 4 and after flashing the cwm recovery and trying to boot in the recovery mode i get a few errors stating:
cant mount cache/recovery
cant open cache/recovery
I notice there are a few topics about this and the solution is to adb push or something, but the adb push command wont work in recovery for me, says device not found and i know my drivers are correct since i can fastboot and do stuff.
I actually got the device running perfectly flashing Chroma via sideload, but cwm wont work! I cant access anything from inside cwm... I also tried twrp and no luck.
I also tried a full original image flash, no luck
Can you please help me with this?
Thanks
Click to expand...
Click to collapse
when you flashed the factory image it should have brought you back erasing and replacing everything. In fastboot did you flash the bootloader, radio, system partitions (.IMG), recovery partition, and so on.? If not try this steps guide http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312/page194 its pretty detailed but it helped me after I wiped everything off my phone trying to learn. If that's a bit too much then try searching for wugfresh nexus toolkit. Both will wipe everything from your nexus then replace it and should get everything going
Hi guys
I decided to try and and unlock and root my phone as soon as I got it. But somewhere along the line things didn't go to plan, and I've got a phone with TWRP (3.0.2-b-b10) on it, and that's about it (stupidly I didn't do a back up as I'd not set anything up on the phone yet). I can still put it into Factory Test Mode, and run 'adb reboot edl' to put into a place where I can communicate with it using tenfar's tool.
First time out, everything seemed to go fine, but when I booted up the phone after running through the process, the wifi wasn't working. This meant I couldn't get through the first stage of phone set up (select language, then wifi, nothing I tried would get me beyond that, as I guess a phone without wifi isn't much use).
So I went back into wiped a few things, tried tenfar's tool again with no luck; wifi still no working. I followed the steps on here, but the ADB commands failed.
Code:
C:\Users\Stephen\AppData\Local\Android\sdk\platform-tools>adb shell dd if=/dev/z
ero of=/dev/block/bootdevice/by-name/modemst1 bs=16384
dd: /dev/block/bootdevice/by-name/modemst1: Permission denied
After some more messing, I wiped the OS (yeah, idiotic). Anyway, so I download Draken's boot and stock from another post, but when trying to flash them via TWRP, they failed. I downloaded them on mac, and copied them to a exFAT SD card. It complains about failed to mount /firmware and no MD5 file found, then I get:
Code:
Could not find 'META-INF/com/google/android/update-binary' in the zip file
And it finishes. Same with the stock file. So now I'm in the process of downloading the B20.zip from here in the hope there is something in there I can flash to get the OS back on the phone. any other suggestions?
Thanks in advance,
Sok
Had the same issue with rooting using Tenfar's tool. I used TWRP to flash a fresh B10 and start over. Send a PM if you need/want help.
Now I'm following the instructions here, and I keep getting the error:
Code:
Failed to mount '/firmware' (Invalid argument)
Then it tells me that the B20 zip file from Draken is corrupt.
I may or may not have TWRP installed. Because, it's stuck on the bootloader when it switches on. I can only get into fastboot. Not more than that. No more Recovery mode. All the tutorials I see online for flashing with QFIL is only for A6000 (not Plus). I have A6000 Plus. What do I have to get it back on the track?
I've searched on other topics about this. But, they're all for A6000. I don't wanna brick more. So, any help would be appreciated.
If u can enter into fast boot then flash the twrp
U can watch at YouTube about flashing twrp
If u cant flash the twrp or get into the twrp !!!
Then flash the stock ROM ...!!!
kamesh_kraken said:
I may or may not have TWRP installed. Because, it's stuck on the bootloader when it switches on. I can only get into fastboot. Not more than that. No more Recovery mode. All the tutorials I see online for flashing with QFIL is only for A6000 (not Plus). I have A6000 Plus. What do I have to get it back on the track?
I've searched on other topics about this. But, they're all for A6000. I don't wanna brick more. So, any help would be appreciated.
Click to expand...
Click to collapse
Most tutorials for A6000 work for the "Plus" variant and vice versa, so it might be worth checking them out.
Also if you had usb debugging on and can send commands to your device from ADB, you can boot into recovery by this command:
fastboot boot recovery xxxx.img
Where "xxxx" is the name of the recovery file which must be in the adb folder.
Feel free to ask if any query
StillrunsKK said:
Most tutorials for A6000 work for the "Plus" variant and vice versa, so it might be worth checking them out.
Also if you had usb debugging on and can send commands to your device from ADB, you can boot into recovery by this command:
fastboot boot recovery xxxx.img
Where "xxxx" is the name of the recovery file which must be in the adb folder.
Feel free to ask if any query
Click to expand...
Click to collapse
I was like why didn't I try this before.
You know what happened? The boot process on "Command Prompt" screen went fine. I heard the unplugging the device and replugging the device sound very well. But during all these process it stays on Fastboot mode forever.
I have the latest TWRP loaded for temporary boot process. (3.2.1)
Besides from that
I was finally able to flash with QFIL tool. But still stucks at Lenovo POWERED BY android logo. QCom Downloader didn't work. But QFIL tool did work. I was able to finally come over the "sahara error" by quickly clicking "Download" button after connecting the cable. Then it flashed all the files. Then it finished downloading. But then if I try to switch it on, it wouldn't boot. Still stucks at the screen that I mentioned earlier.
StillrunsKK said:
Most tutorials for A6000 work for the "Plus" variant and vice versa, so it might be worth checking them out.
Also if you had usb debugging on and can send commands to your device from ADB, you can boot into recovery by this command:
fastboot boot recovery xxxx.img
Where "xxxx" is the name of the recovery file which must be in the adb folder.
Feel free to ask if any query
Click to expand...
Click to collapse
Sorry!
I tried it with Stock Recovery of A6000 (not plus). It booted into recovery.
Now, I can boot into TWRP. Looks like all the partitions are gone. How do I recover that?
StillrunsKK said:
Most tutorials for A6000 work for the "Plus" variant and vice versa, so it might be worth checking them out.
Also if you had usb debugging on and can send commands to your device from ADB, you can boot into recovery by this command:
fastboot boot recovery xxxx.img
Where "xxxx" is the name of the recovery file which must be in the adb folder.
Feel free to ask if any query
Click to expand...
Click to collapse
Sorry for previous post.
I tried to boot with Stock Recovery. It booted to recovery. But then I tried with TWRP again. It worked.
Looks like all the partitions are gone. How do I retain it?
kamesh_kraken said:
Sorry for previous post.
I tried to boot with Stock Recovery. It booted to recovery. But then I tried with TWRP again. It worked.
Looks like all the partitions are gone. How do I retain it?
Click to expand...
Click to collapse
Just flash a new ROM
StillrunsKK said:
Just flash a new ROM
Click to expand...
Click to collapse
Nope. Doesn't work. Tried that too. Ends up with Error 7 and Error 6. Modified Updater Scripts. Still same problem. Shows Failed to mount /system /data /cache.
jameeljb6 said:
If u can enter into fast boot then flash the twrp
U can watch at YouTube about flashing twrp
If u cant flash the twrp or get into the twrp !!!
Then flash the stock ROM ...!!!
Click to expand...
Click to collapse
Haha. I know how to do that. Thing is, I can't boot into System or Recovery normally even if I flash via Fastboot. I can only boot to recovery by "fastboot boot recovery.img" Then in TWRP there, I can't flash any roms as it shows Failed to mount /system /data /cache all the time. Tried fixing with "repair file system" option in TWRP. Still doesn't work.
kamesh_kraken said:
Nope. Doesn't work. Tried that too. Ends up with Error 7 and Error 6. Modified Updater Scripts. Still same problem. Shows Failed to mount /system /data /cache.
Click to expand...
Click to collapse
What os version were you previously upon? what TWRP version are you using?
Which ROM are you trying to flash?
StillrunsKK said:
What os version were you previously upon? what TWRP version are you using?
Which ROM are you trying to flash?
Click to expand...
Click to collapse
This one had 5.0.2. The latest stock ROM provided by Lenovo. I used both 3.2.1-0 and 3.1.0 both seems to provide same "Failed to mount /system /data /cache" error. Even stock recovery shows that.
Trying to flash RR 5.8.5
kamesh_kraken said:
This one had 5.0.2. The latest stock ROM provided by Lenovo. I used both 3.2.1-0 and 3.1.0 both seems to provide same "Failed to mount /system /data /cache" error. Even stock recovery shows that.
Trying to flash RR 5.8.5
Click to expand...
Click to collapse
Use the TWRP provided in the RR thread.
Wipe everything except MicroSD, if it shows any error while wiping, repair the partition in which the error arises and then wipe. After that flash the HEX firmware in RR thread and then flash ROM.
(Side Question : how did you land up in this situation?)
StillrunsKK said:
Use the TWRP provided in the RR thread.
Wipe everything except MicroSD, if it shows any error while wiping, repair the partition in which the error arises and then wipe. After that flash the HEX firmware in RR thread and then flash ROM.
(Side Question : how did you land up in this situation?)
Click to expand...
Click to collapse
The TWRP I mentioned 3.1.0 was obtained from RR forum only where dev mentions "F2FS" support. It does show the same error that I mentioned earlier. I did repair, resize, format, change file system. What ever I do, I always get the mount error on 3 partitions. Can't flash any ROMs either. Shows that error 7 and 6. I even deleted the assert line. It would only land me on error 6. I even googled and tried to get rid of that error. But after the error 6 or 7, it shows the same "mount failed".
Not my device. One of my client's. Received as not working.
Can't flash via TWRP, "failed mount system", twrp sideload not working either.. stuck
I need my phone for work tomorrow so any help would be greatly appreciated.
I'm on TWRP 3.2.3-1 and was using the latest stock oreo rom from here: https://forum.xda-developers.com/g5...o-twrp-flashable-stock-builds-coming-t3830482
My phone suddenly didn't have a reception today, after rebooting I regained reception but couldn't make calls. I rebooted to recovery and tried to dirty flash the same stock twrp flashable oreo rom that I was using and it failed. Apparently the OS got corrupted. I tried repeatedly to flash the ROM and then noticed I was getting an error : failed to mount system , invalid argument. I couldn't mount system via the Mount tab in TWRP and I couldn't find anything helpful to resolve this error.
I did some more research downloaded the fastboot flashable ROM from here : https://forum.xda-developers.com/g5-plus/how-to/moto-g5-plus-fastboot-flash-stock-oreo-t3848433 and tried to flash the rom via adb using adb sideload in twrp but twrp doesn't seem to load that function correctly. In the elevated command prompt in the adb directory I type adb sideload filename.zip and it just freezes up my PC. My device does show up with the adb devices command and shows " *Serial Number* RECOVERY ".
I don't understand what to do with the instructions in the fastboot flash stock thread I posted above and I'm at the limit of my knowledge. No idea how to proceed... any help is greatly appreciated.
I tried extracting the xml.zip into the adb folder and rebooted to bootloader/AP Fastboot Flash Mode and was going to try the commands in the fastboot Rom thread but my device only shows up in adb devices when I load twrp. uhhhhgggghhhhhh guess I'll have to buy a backup phone tomorrow while I try to get this one working
Holy hell.... I didn't realize since I was in the fastboot/bootloader I had to use "fastboot devices" command to see the device. Tried that and saw the device listed, so I created a .bat file using the commands in the fastboot roms thread above and I have a functional device again. Whohoooooo!
Did you try to format /System/ as EXT4?