Guys, I need help, I'm almost Entering Depression, Then half an hour Crying (lie was so 10 minutes).
And the NEXT, I Own hum Xperia Z1, and logo Out When I tried one version 5.0 HK I give um flash via flashtools, not caring root and recovery, thought That would solve AFTER THAT Test of ... I installed the 5.0 normal, and even works well so far, the only That there Out OE root recovery Make Pro 5.0 and I decided to try the method consists of in The Breaking of hum recovery logically in KK, Install zip hum of pre-rooted rom 5.0 and logo AFTER flashing a contradictory From some 5.0 flashtools Pelô, but WHEN I was Do I went back to the normal KK, I root and installed double recovery, IT normally comes no charge, and that it gives access to / system A Message Appears Both OS in recoverys saying "E: Unable to mount '/ system' 'and has not flashing As nothing, ate I tried to flash the rom iHacker 6.2 KK Only What do NOT Pass kernel, I wonder if anyone has gone through IT and How Does solve, I'm desperate.
Thank you.
I want to help. But I'm gonna be honest with you. I did not understand a single thing you said.
Also please post on the Q&A section, not the General section
Related
Hi everybody.
In the past I already flashed custom ROM to routers, so I thought I had the skill to undergo the path of flashing ROM to a phone.
Wrong.
I have countless tabs opened tried to solve my stucked phone, and my PC is running out of memory; and I'm running out of hope.
I own a S Plus GT-i9001.
I wanted to get rid of all the bloatware present in the phone, so I gained root privileges.
Like explained here. It worked perfectly.
Since deleting all the unnecessary apps didn't look working, I thought "well, it is a rainy day, you had this device for a while, why don't you flash some ROM?"
So,
1. I followed this guide, but, needless to say, Rom Manager was not fulfilling to its duty. Indeed I backuped everything I needed, but the stock rom
2. I followed then this guide, point 3, to install ClockworkMod Recovery directly. Before, everytime I tried to enter the recovery menu, I was bounced to the original recovery menu, because ROM manager did not succeed.
With this guide, I managed to boot into ClockworkMod Recovery.
I then started backing up the ROM to the external SD, and it seemed working.
It was popping out with a message "E:Can't mount /cache/recovery/command", but since all the operations went successful, I did not care much (fail, I suppose)
3. I tried to boot back into the phone, before installing the new ROM, just to double check I saved everything, and then the drama began. I was just continuously bounced back at CWM Recovery menu, no way to get in the phone.
I tried anyway to install the AOSP 4.0.4. and all the steps went successful, but still nothing, I would always reboot automatically into CWM Recovery.
4. I tried restore from backup in external SD, it ran successfully, but still couldn't load the phone
5. I then googled into the "E:Can't mount /cache/recovery/command" error, so I ended up somewhere that they were advising to flash FeaCore Phoenix Recovery tool. Indeed it did not display anymore such an error
6. I tried again with he AOSP 4.0.4 ROM, but it showed then the following error
Code:
assert failed: getprop("ro.product.device") == "thunderc" || getprop("ro.build.product") == "thunderc"
so I ended up here and changed the zip accordingly.
7. I also tried this instructions here to perform the most ultimate massive wiping.
8. I installed the AOSP 4.0.4, and the update-Gapps-ICS-20712.zip, it worked, no errors.
Still, it reboots into the recovery menu.
I can't get out of this damned recovery menu, it is crazy! I have used so many recovery tools in PCs, you usually are able to leave them, maybe not able to restore the OS, but you never get stuck into a circle of hell like this!
Please, does anyone has some advice for me? I don't want to waste a 6-months old device
thank you!
You should reflash CWM with odin like this then try flashing a rom again.
If that doesn't work flash a stock frimware through Odin also with the AriesVE.ops file active.
All guides tell you to put the "recovery-clockwork-5.5.0.4-ariesve.tar.md5" or the stock firmware file as "one package". Doing that results into large file errors or odin getting stuck on "downloading..."
Putting the file under phone got my phone back to life, after softbricking it by using CWM 6 thouch.
switchboy said:
You should reflash CWM with odin like this then try flashing a rom again.
If that doesn't work flash a stock frimware through Odin also with the AriesVE.ops file active.
All guides tell you to put the "recovery-clockwork-5.5.0.4-ariesve.tar.md5" or the stock firmware file as "one package". Doing that results into large file errors or odin getting stuck on "downloading..."
Putting the file under phone got my phone back to life, after softbricking it by using CWM 6 thouch.
Click to expand...
Click to collapse
man, you saved my life!
you and the powerful, mighty Odin, god of the Valhalla!
oh, it feels so awesome!
but since I never learn (that was enough of a message to tell me to stop messing around)...
how do I install the ROM I'd like, go through the same process (my phone is now as as when I bought it) or can I use somehow Odin?
jv_guano said:
man, you saved my life!
you and the powerful, mighty Odin, god of the Valhalla!
oh, it feels so awesome!
but since I never learn (that was enough of a message to tell me to stop messing around)...
how do I install the ROM I'd like, go through the same process (my phone is now as as when I bought it) or can I use somehow Odin?
Click to expand...
Click to collapse
I realised that, since I flashed the recovery-clockwork-5.5.0.4-ariesve.tar you provided, if I would boot in recovery mode, it would be still there.
and it is.
but still it is showing the error
E:Can't mount /cache/recovery/command and, needless to say, it is not loading the ROM correctly, it stucked again
I don't get which part am I doing wrong!
jv_guano said:
I realised that, since I flashed the recovery-clockwork-5.5.0.4-ariesve.tar you provided, if I would boot in recovery mode, it would be still there.
and it is.
but still it is showing the error
E:Can't mount /cache/recovery/command and, needless to say, it is not loading the ROM correctly, it stucked again
I don't get which part am I doing wrong!
Click to expand...
Click to collapse
Well, I sorted it out (absolutely, in a mysterious way!!! )
I downloaded the recovery-clockwork-6.0.1.2-ancora.tar.md5 from here, and I followed again your instructions for flashing it with Odino (rigorously NOT ticking one package).
When rebooted, I had the AOSP 4.0.4 Stock, shiny and sparkling!
without even entering the recovery menu and reinstalling!
but I guess I will need to do a clean install again, now that seems that CWM 6 is digested by my phone
Well guys... I'm afraid that I'm in big trouble at the moment.
Hopefully this might sound familiar and some smart guys can help me out.
This afternoon I flashed the latest version of the Galaxy Project ROM for the i9305. I came from v16.10, and some older version of Philz Recovery. Flashed everything with the Aroma installer, without any troubles, and it worked. During the installation process, I've selected to install the newest v6.48.4 of Philz.
After a few hours, I wanted to re-flash the rom again, because I didn't like the transparent theme. But.. whenever I flash it now, the process stops at "Setting permissions". Then the phone shuts down, and reboots into recovery. Tried with both Philz and CWM recovery, latest versions and slightly older. Don't know that the issue is, recovery problem?
With the new versions of these recoveries, there is no more " fix permissions" option, that would be my first idea.
I cannot restore my older back-up, which sucks. And I really don't want to perform a "clean install" with losing all my files, as I just came back from half a year in South Africa and all my photos are still on my internal SD
Hopefully someone can help me out
Regards
EDIT: Turns out that I got this issue also if I try to flash other roms.
If I flash a stock version of Android 4.3 via Odin, do I keep all my photos? Can anyone confirm this?
Odin shouldn't touch internal storage, unless you explicitly tell it to.
Hi guys, i just rooted my device using TWRP. As i am new to all this, i tried flashing CM11 ROM but i was getting "failed" message again and again. Then mistakenly i used option of "Advance Wipe" and wiped everything. Now while booting up the device i am going to recovery but there is no backup available and i am unable to install any ROM as the custom ROM is also deleted along with backup. Please help me out on this. Thanks...
Hemant17 said:
Hi guys, i just rooted my device using TWRP. As i am new to all this, i tried flashing CM11 ROM but i was getting "failed" message again and again. Then mistakenly i used option of "Advance Wipe" and wiped everything. Now while booting up the device i am going to recovery but there is no backup available and i am unable to install any ROM as the custom ROM is also deleted along with backup. Please help me out on this. Thanks...
Click to expand...
Click to collapse
I have done that a few times by mistake I would download the rom on a thumb drive and use my otg cable to plug it in flash it from the thumb drive in recovery.
You can also side load it as well, yet I have never done it that way so you would have to search that.
I have also read some say download the rom to your pc and and plug in phone and drag the rom to your sdcard.
If all else fails you can always return to stock via rsd or mfastboot as long as you can get into download mode.
Thanks a lot for your prompt response. I am having Moto x 2013 edition and tried to flash CM11 ROM using thumb drive in recovery mode but the "failed" message was coming , is it a compatibility issue of ROM with My device? As i told that i am new to all these things can you please guide me or share with me a link for any good ROM which i could flash on my Moto x and make it functional again.
Also if i want to get back to my stock ROM i.e. Kitkat 4.4 then how to do it? will i be able to update to lollipop in future?
Sorry for asking so many questions and thanks again for your support.
It sounds more like you should flash your phone back to stock and leave it there until you understand what you're doing. With the number of guides available anymore, the entire flashing process should be dead simple and difficult to mess up. Add to the fact that wiping/formatting partitions always prompts for confirmation before actually deleting things, and it shows that you don't really have any knowledge about what is going on. Keeping your phone stock until you do know what you're doing is only going to save you from having a paperweight in the long run.
Thanks a lot!!!! with your support i am able to flash my phone on cyanogen12
Thanks agian...
Dear All,
I'm very new in Android, and trying to get rooted LP on my Z1. So I have KK 4.4.4. with root, BU and dual recovery "Z1-DualRecovery-LOCKED_FIXED6".
I've got "C6903_Customized RU_1276-7743_14.5.A.0.242_R2D flashable-signed" which copied to internal and external SDCARD's. In recovery mode I did all wipes, but when I' trying to to flash device, it gives me following error:
This might take a while...
assertfailed: package_extract_fie("system.ext4" , "/dev/block/platform/msm_sdcc.1/by-uuid/F9CDF7BA-B834..... and so on)
Install from sdcard complete.
Gents, I need your support, because I tried already a lot of times, but seems that something goes wrong, and I'm afraid to damage the phone.
Thanks beforehand.
Hello all my fellow Huawei P7 users. Last week, I finally decided to update my Huawei from EMUI 2.3 (B136) to "next level". For some reason, when I tried to download the rom through Updater, error was reported. something with "checksums". So I download rom, and tried "local update"... and it's gone (TWRP was installed, don't know if this could be reason). So yeah, our beloved bootloop became my second friend. So I tried to restore stock rom, with stock recovery 3.0, extracted from updater.app, recovery.img and boot.img, created dload on sd, started procedure, "Verifying install package" and at some point just "FAIL". Tried even with the first stock ROM (Because in manual there was no "previous versions") still got "FAIL". Tried to install "MyRom 1.2", again bootloop, as far I concerned it's because I don't have "stock rom". So I tried, X-Rom. and you know what, it worked without any problems. Even though I like it, I still want back to stock ROM. So I want to ask you my dear friend. how I can get back my stock ROM? If I again try "very first stock rom" and it will "FAIL", is there anything else I can to do bring back my stock? Or maybe someone knows, why it "fails" to verify package
RocketDoge said:
Hello all my fellow Huawei P7 users. Last week, I finally decided to update my Huawei from EMUI 2.3 (B136) to "next level". For some reason, when I tried to download the rom through Updater, error was reported. something with "checksums". So I download rom, and tried "local update"... and it's gone (TWRP was installed, don't know if this could be reason). So yeah, our beloved bootloop became my second friend. So I tried to restore stock rom, with stock recovery 3.0, extracted from updater.app, recovery.img and boot.img, created dload on sd, started procedure, "Verifying install package" and at some point just "FAIL". Tried even with the first stock ROM (Because in manual there was no "previous versions") still got "FAIL". Tried to install "MyRom 1.2", again bootloop, as far I concerned it's because I don't have "stock rom". So I tried, X-Rom. and you know what, it worked without any problems. Even though I like it, I still want back to stock ROM. So I want to ask you my dear friend. how I can get back my stock ROM? If I again try "very first stock rom" and it will "FAIL", is there anything else I can to do bring back my stock? Or maybe someone knows, why it "fails" to verify package
Click to expand...
Click to collapse
If I'm getting this right, you're currently on EMUI 2.3. If that's true, you'll need older version of TWRP like 2.8.1.0 for EMUI 2.3. Once in recovery you need to wipe ALL DATA by confirming YES. Once everything deleted you'll be able to flash stock recovery and force-update the stock ROM (EMUI 2.3). I had a similar problem until I realised that I was using wrong version of TWRP.