I really enjoying experimenting with rooting my phone and flashing custom rom's.
Unfortunately my phone is in a boot loop now.
First I installed the OMNI rom, worked fine for a couple of days. Then I installed TWRP recovery what overwrote CWM Recovery what was on my phone before.
I wanted to flash PAC rom, I downloaded the rom and GAPP, booted in recovery mode. But when I tried to factory whipe my phone, it took a very long time and my battery went empty so it stopped wipping.
Now when I tried to boot it up it didn't go further then the LG logo. So I booted in recovery again and just installed the PAC Rom without the factory wipe. It was formatting like 10 minutes, after that the flashing continued and installed the ROM.
The Flashing:
######################
Formatting system
Extracting System files ...
Making Sym Links
Thanks for choosing PAC-MAN ROMS
Enjoying PAC-MAN now
Checking if loki-fying is needed
Updating partition details.....
E:unable to mount /cache
It look alright, so rebooted but didn't came further than the PAC-MAN Booting animation.
In the Mount section of TWRP only system and data are mounted. Cache and USB OTG are unchecked.
It says E: Unable to mount /cache
http://forum.xda-developers.com/showthread.php?t=2432476 This looks really helpfull. So i tried it but couldn't get in download mode first.
When I tried to start the upgrade the following happens:
Strat fn_startupgrade
Extract kdz file
kdz decrypt success
Extract file error
Then the program stopped working.
For me a bricked phone is a huge problem. I hope that you guys can help me to fix my phone.
I'm willing to give some money for the time and as a 'thank you' for helping me out.
PM me if it's needed for faster helping. After I will post the full solution here.
Thanks in advance!
Now that the cache is able to mount because I formatteded it with the make_ext4fs function.
Now I have to flash a rom through sideload because it freezes at the LG Logo.
The problem here is that my device doesn't show up in the command prompt because the drivers aren't working (The drivers I installed from the LG website)
I had the same issues with the drivers and sideloading. I just downloaded the android sdk then then went into the properties of the phone in "devices and printers" and had it search the the driver dir in the android sdk. Just choose the android adb bridge and it should be fine.
Did you fix the issue?
Related
hey guys, im back with stupid questions...
I wanted to upgrade my Nexus 7 32gb UMTS to 4.3 and used the Nexus 7 Toolkit (by Mark Skippen).
I was on a custom Rom and wanted to get back to Stock, so i could just use the update process by Google.
Downloading and Installing the ROM (including wipe of user data) by the Toolkit seemed to work and didnt show any error messages.
As is tried to boot my device into Android I got stuck in the bootloader.
When I tried to start it, a small white message "Booting failed" appeared in the top left corner. Nothing else happend.
I did everything again, no changes.
Next step was to google for a few mins, then I tried to install a custom recovery via Toolkit (which worked) and install a zip-file Rom via sideload.
Connection was there, the files got pushed onto the device but then "An Error Occured" popped up and everything stopped.
Installing a zip via usb-otg seemed promising, but this got me errors like "unable to mount /system" and "unable to mount /cache"...
when I tried to reboot from TWRP or ClockwordMod Recovery (tried the earlier described things with both recovieres) I got a message saying
"there is no OS installed, are you sure you want to reboot?"
Please help me, I really dont know how to fix this and I will need my Nexus 7 in 2 days (thats why I tried to reinstall and polish everything )
thanks for your help, I really appreciate it
Edit: tl;dr
Stuck in fastboot, no OS is installed. sideload / installing ROM via ADB / installing ROM via usb-otg doenst work, most certainly because /system and /cache cant be mounted
so AFAIK the real problem is that I cant mount those partitions, otherwise I could install a ROM and get out of fastboot/recovery easily. (just mounting them in custom recoveries didnt work btw)
IchStelleDummeFragen said:
hey guys, im back with stupid questions...
I wanted to upgrade my Nexus 7 32gb UMTS to 4.3 and used the Nexus 7 Toolkit (by Mark Skippen).
I was on a custom Rom and wanted to get back to Stock, so i could just use the update process by Google.
Downloading and Installing the ROM (including wipe of user data) by the Toolkit seemed to work and didnt show any error messages.
As is tried to boot my device into Android I got stuck in the bootloader.
When I tried to start it, a small white message "Booting failed" appeared in the top left corner. Nothing else happend.
I did everything again, no changes.
Next step was to google for a few mins, then I tried to install a custom recovery via Toolkit (which worked) and install a zip-file Rom via sideload.
Connection was there, the files got pushed onto the device but then "An Error Occured" popped up and everything stopped.
Installing a zip via usb-otg seemed promising, but this got me errors like "unable to mount /system" and "unable to mount /cache"...
when I tried to reboot from TWRP or ClockwordMod Recovery (tried the earlier described things with both recovieres) I got a message saying
"there is no OS installed, are you sure you want to reboot?"
Please help me, I really dont know how to fix this and I will need my Nexus 7 in 2 days (thats why I tried to reinstall and polish everything )
thanks for your help, I really appreciate it
Edit: tl;dr
Stuck in fastboot, no OS is installed. sideload / installing ROM via ADB / installing ROM via usb-otg doenst work, most certainly because /system and /cache cant be mounted
so AFAIK the real problem is that I cant mount those partitions, otherwise I could install a ROM and get out of fastboot/recovery easily. (just mounting them in custom recoveries didnt work btw)
Click to expand...
Click to collapse
Well . what you can try for now is download the latest factory images and flash them manually via fastboot .. See how that turns out. You can install any ROM via fastboot .. No issues what so ever.
In the factory images there will be a bootloader IMG.. Flash that first and then flash the remaining images ( I suggest manually or via the .bat or .sh files ) and then see if you can boot up android. Mostly should be possible.
And did you try rebooting inspire of the message " no is installed " appearing on the screen ? Maybe it will boot a ROM ? I remember facing this message after just flashing a rom sometimes. So don't worry.
As long as you have access too fast boot everything can be fixed at least w.r.t software.
Red Devil said:
Well . what you can try for now is download the latest factory images and flash them manually via fastboot .. See how that turns out. You can install any ROM via fastboot .. No issues what so ever.
In the factory images there will be a bootloader IMG.. Flash that first and then flash the remaining images ( I suggest manually or via the .bat or .sh files ) and then see if you can boot up android. Mostly should be possible.
Click to expand...
Click to collapse
It worked!!! Thank you so much.
Still wondering why it didnt flash the factory image as a whole while flashing every part step by step worked perfectly fine...
Red Devil said:
And did you try rebooting inspire of the message " no is installed " appearing on the screen ? Maybe it will boot a ROM ? I remember facing this message after just flashing a rom sometimes. So don't worry.
Click to expand...
Click to collapse
Yes, tried booting, but the device just restarted and returned to fastboot mode.
many thanks again
help plz
this is where I am at as well how do you get out of this. kinda a noob at this so a step by step would be great thanks
This is my second Samsung. I have put over a dozen different ROMs on my old Exhibit II 4G. Having said that, I realize many of you know more than I could ever hope to know. That is why I'm posting here. I have searched, but most of my searches take me to announcements of new CWM and TWRP recoveries.
I've had a Samsung Galaxy S4 Google Play Edition for over a month and still did not have a nandroid backup, so last night I installed ClockworkMod ROM Manager with the intention of flashing CWM Recovery. The app did not list my phone, so I told it to show all devices, where I found the i9505 (I don't remember if it was the i9505g or not). I told it to flash ClockworkMod Recovery, and selected the option that I had not yet flashed CWMR. I then used QuickBoot to reboot into recovery, where I performed my first nandroid to the microSD card.
When I rebooted after making that nandroid, it went right back to ClockworkMod Recovery. Subsequent reboots did the same thing. I could get into Odin mode with VolumeDown+Home+Power. Using Odin v3.09 I was able to flash the stock recovery. This did not resolve the boot-loop issue. Now it boots into the stock recovery, which is less functional than CWM. To me it is behaving as if the recovery tools were flashed to the /boot/ partition, or something is telling it to always boot from the recovery partition.
-In stock recovery, it will download ADB installations (from "apply update from ADB"), but every attempt fails it's signature verification. I have tried 6+ files, all have failed. I believe that the device has USB debugging enabled, but I cannot check while in this state.
-Stock recovery does not mount the microSD card, so I cannot install from there. CWM would mount the microSD card, but I did not think to try installs from the microSD at that time. Is it possible that I installed the wrong stock recovery?
-I do not know how to perform an ADB "push" with my phone in this state. To be honest, I have never done an ADB push. If I get to that stage, where on my S4 should I send a pushed file? "/system/bin"?
-If I try an adb push in this mode
-How do I get my phone to boot from the proper partition?
-If I have the wrong data in that partition, how do I get the correct information onto that partition?
Here is what it does when I try to sideload from stock recovery:
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify while-file signature
E:failed to verify while-file signature
E:signature verification failed
Installation aborted
Thank you in advance for any help!
Solved - i9505g soft-brick/boot-loop
My problem was resolved by flashing a stock recovery and ROM, found here: http://forum.xda-developers.com/showthread.php?t=2569510
The package named "I9505GUEUBML4_FULL_ROOTED.tar.md5.gz" flashed from Odin is what worked.
I am trying to flash my N4 with cyanogenmod following the official wiki.
I'm at the point where I've installed TWRP into recovery, I've wiped everything (I've even formatted them since I couldn't wipe all of it initially), and the only error I see is "unable to mount /usb-otg".
Then, I've "installed" the CN zip files for the 13 and 12 versions, none of them works in the sense that when I reboot the system, I'm always coming back to TWRP.
What's wrong? Any suggestion?
Thanks
I've the same problems with my nexus 4
gerardgerard said:
I am trying to flash my N4 with cyanogenmod following the official wiki.
I'm at the point where I've installed TWRP into recovery, I've wiped everything (I've even formatted them since I couldn't wipe all of it initially), and the only error I see is "unable to mount /usb-otg".
Then, I've "installed" the CN zip files for the 13 and 12 versions, none of them works in the sense that when I reboot the system, I'm always coming back to TWRP.
What's wrong? Any suggestion?
Thanks
Click to expand...
Click to collapse
Hi gerardgerard,
I also wanted to flash my Nexus 4 with Cyanogenmod 12.1. So I installed TWRP into recovery and wiped everything, like it's explained in the wiki. I can also see the error "unable to mount /usb-otg". When I want to reboot the system I always get back to TWRP. Cyanogenmod doesn't boot correctly. Did you find a solution for the problem?
same problem
Hi
I'm having the same problem. As follows:
Cause (my mistake): I have been using Cyanogen-mod nightlies for a couple of months on my Nexus 4, and made the grave mistake of leaving the phone to upgrade one night but without it being plugged in properly - and it ran out of power part way through! (At least, that's what I think happened).
Fortunately, it would boot into bootloader and I could use adb/fastboot. I (re)installed TWRP 2.8.7.0 (from my Mac, using fastboot). And that works fine - I can boot into twrp ok.
Next I loaded the latest nightly from cm (using fastboot - is this what people call sideloading?) and used twrp to install it. It goes through the installation fine (the only error message is that it can't mount /usb-otg). But when I reboot it just goes back to twrp.
I then tried installing the earlier cm nightly that I know worked, but with the same result.
Finally, before I first installed cm I did a backup (using twrp), and I have tried recovering that. It seems to do all the right things, but again when I reboot it just goes back to twrp.
Any suggestions would be welcome.
Thanks
J
Flash back to a completely stock ROM and run through the set up to make sure everything works. Then copy CM to the phone, reboot to fastboot, flash twrp, immediately boot into recovery using the volume and power button without leaving fastboot, wipe data, cache, system, flash CM, reboot.
If the phone will not boot after flashing a stock ROM, boot to fastboot, flash the userdata.img file, and immediately go to stock recovery without leaving fastboot, wipe data/cache, reboot.
It works now!
I managed to fix the problem ... I found this guide for the Nexus 5:
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
and I applied those instructions. It didn't work first time, so I just repeated them and now it's working. I used the 5.1.1 stock downloaded from https://developers.google.com/android/nexus/images#occam.
I guess this is what audit13 means in their post - so thanks are due there.
I will next reinstall twrp and cm and I don't expect any problems with that (having done it successfully before).
Smaje
Hello,
I'm trying to install a custom rom on my note 4.
I rooted successfully, and installed TWRP through flashify.
First issue I ran into is that the phone got stuck in a bootloop after installing TWRP. All fine I said, it's cool since I want to flash a ROM anyway.
I downloaded the ROM for my device, and after I clicked factory reset and tried installing the ROM, I got the error
Code:
unmount of /system failed; so such volume
I looked around online, some posts said that it's fine, the ROM will install anyways, but that's not the case. The ROM didn't install (the process is finishing way too quickly), and I'm still stuck at bootloops.
I'm running TWRP 3.0.2.0 (newest version), android 5.1.1, on my note 4 N910H.
I have access to TWRP and to download mode, and I can move files between the PC and my phone using an external memory card.
PLEASE HELP ME :crying:
Hi Guys.
I recently noticed that I couldn't create a backup with TWRP. Firstly, I thought it was a TWRP problem, as I had some issues installing it after the B588 update. So I flashed it again, but nothing changed. When my back up would reach about 70%, it would give me a reboot. Then I tried to install B588 again, to fix any errors. Although, I flashed it correctly, when I tried to restore the back up I had through Huawei's app, I got an unexpected reboot. So I decided to intall sokkoban's rom. During my first attempt to copy the zip files, it stoped the process. So I took the files directly to the SD card (with an adapter and not via usb cable). I re-flashed TWRP and then entered recovery, to flash the zip files (I am only able to enter custom recovery, only through xposed modules and adb commands since my latest update: 01-01-2017). After managing to enter TWRP, I tried to clear everything, but I got an error:
The message was: mkfs.fat /dev/block/mmcblk1p1 process ended with ERROR: 1 Unable to wipe sdcard. (just in case the image is not visible)
Can anyone help with this?
Currently I am trying to install the ROM ...
spirto82 said:
Hi Guys.
I recently noticed that I couldn't create a backup with TWRP. Firstly, I thought it was a TWRP problem, as I had some issues installing it after the B588 update. So I flashed it again, but nothing changed. When my back up would reach about 70%, it would give me a reboot. Then I tried to install B588 again, to fix any errors. Although, I flashed it correctly, when I tried to restore the back up I had through Huawei's app, I got an unexpected reboot. So I decided to intall sokkoban's rom. During my first attempt to copy the zip files, it stoped the process. So I took the files directly to the SD card (with an adapter and not via usb cable). I re-flashed TWRP and then entered recovery, to flash the zip files (I am only able to enter custom recovery, only through xposed modules and adb commands since my latest update: 01-01-2017). After managing to enter TWRP, I tried to clear everything, but I got an error:
The message was: mkfs.fat /dev/block/mmcblk1p1 process ended with ERROR: 1 Unable to wipe sdcard. (just in case the image is not visible)
Can anyone help with this?
Currently I am trying to install the ROM ...
Click to expand...
Click to collapse
This error is quite normal.....I have got this many times wiping everything and this isn't an issue...
With reboot during restore I think that your backup is corrupt at some point