Related
None of the "similar" threads have people with this problem. I can access Recovery (Clockwork Mod v5.8.4.0), I can do everything within Recovery, full wipe, erase dalvik cache etc, BUT it still will not get past "HTC quietly brilliant".
I got into this mess by trying to flash a kernel. I think the battery was about 15%.
I can mount the sd card via usb, so I'm going to extract the back-up I did before getting into this bootloop.
I've tried this:
If you have Custom ROM on or nandroid backup internal SD card
Reboot in recovery (If your still in fastboot, choose "Reboot Bootloader" and then go into recovery)
Restore a Nandroid Backup or flash Custom ROM
Reboot and go into fastboot
Clean cache in fastboot
Click to expand...
Click to collapse
ANd this
IF YOU HAVE SIGNED RECOVERY:
1.- GO TO FASTBOOT
2.- HIT "SHUT DOWN"
3.- WITH THE POWER OFF PUT IT TO CHARGE
4.- RED LIGHT NOTIFICATION SHOWS THE CHARGING PROGRESS.
5.- NEXT DAY YOU WILL SEE A SOLID GREEN LIGHT NOTIFICATIONS FOR A COMPLETE CHARGE.
Click to expand...
Click to collapse
I haven't tried relocking yet. This is the ultimate last resort. Is there a way to know what percentage my battery is?
Any help greatly appreciated before I throw it at the wall and replace with an S3 :silly:
I've got 3737mV
JagSem said:
I've got 3737mV
Click to expand...
Click to collapse
try reflashing boot.img
fastboot erase cache
fastboot flash boot boot.img
o m f g
I have been stressing to absolute hell and back because I was messing around with kernels and managed to bollocks it up. It never occurred to me to extract the boot.img from the backup and flash that through hboot at the same time doing the backup. THANK YOU!! :good::good::good::good::good::good:
JagSem said:
o m f g
I have been stressing to absolute hell and back because I was messing around with kernels and managed to bollocks it up. It never occurred to me to extract the boot.img from the backup and flash that through hboot at the same time doing the backup. THANK YOU!! :good::good::good::good::good::good:
Click to expand...
Click to collapse
Glad u got it sorted
Very Similar Problem - Please Help!
I was wondering if anyone can help me. I have the same problem, all it says is 'HTC Quietly Brilliant' and it is stuck in a reboot cycle.
I was watching a YouTube tutorial on how to flash CM10 onto my One X (I do have ClockworkMod and all of that stuff installed already). Everything was going well, but the video only briefly (for maybe a second) mentioned the fact that you have to put the CM10 zip folder onto the phone storage before you flash the boot.img. I went on and followed the steps and tried to flash the boot.img, but as I said earlier, all the phone will do is reboot over and over again. I have charged it to full battery so this should not be a problem when I go to fix it.
I would be really grateful for any help on the subject as I contacted the person who made the tutorial, and he has not responded. Thanks in advance.
Just an update if anyone has the same problem as I did, all I had to do was go into ClockworkMod and go to:
Mounts and Storage > Mount USB Storage
Then, just connect the device to your PC and put the zip folder on phone storage. Then, flash the boot.img, and install the zip from SD card in ClockworkMod. Hope this helps.
Havoc2510 said:
Just an update if anyone has the same problem as I did, all I had to do was go into ClockworkMod and go to:
Mounts and Storage > Mount USB Storage
Then, just connect the device to your PC and put the zip folder on phone storage. Then, flash the boot.img, and install the zip from SD card in ClockworkMod. Hope this helps.
Click to expand...
Click to collapse
which boot? i've same problem!! where i can find boot.img?
thank's in advance
br
How to install Custom ROM on HTC One X.
agentot said:
which boot? i've same problem!! where i can find boot.img?
thank's in advance
br
Click to expand...
Click to collapse
First off, I'm sorry if you already knew most of the instructions below, or if you are an experienced user. I'm just writing the full steps out so that any user, novice or otherwise, can follow the steps and get their phone working. I will also assume that your phone is already rooted and has ClockworkMod installed.
Before anything else, make sure you have HTC Sync downloaded so that you have the drivers.
Okay, when you are trying to install a custom ROM, you have to put the full zip file on the phone storage. What I would do is create a new folder in C: drive called 'Android' or 'HTC ROM' or whatever you want to put. For the rest of the answer, I will call it AndroidF (android folder). Copy this zip folder into AndroidF. If you go into the zip folder (don't unzip it), you should find a disk image file called 'boot' or 'boot.img'. Copy this out so that it sits in AndroidF too (do not move it!). Once it is in AndroidF, rename it boot.
Once you have done this, go into the bootloader and go to recovery. This will take you to ClockworkMod. From there go to:
Mounts and Storage > Mount USB Storage
Then, connect the phone to your PC and put the zip folder onto the phone. Then, tap unmount, and go back to the bootloader. Click fastboot, and make sure that it says 'Fastboot USB'. If not, just unplug the phone and plug it back in again, and this message should be there. Leave the phone once this has happened.
Go back to AndroidF, and hold shift, right click and choose "Open Command Window Here". Command Prompt should pop up. Then type the following,
fastboot flash boot boot.img
If this works, skip to the next paragraph. If not, type fastboot flash boot boot.img.img. This should then work.
Go back to the phone, and select HBoot. Then go to the recovery from here. Once in the recovery, go to:
Install zip from SD card > Choose zip from SD card
Find the zip file and install it. And voila! Your phone should be running whatever ROM you have picked. If you have any more problems, message me back and I will try and help as well as I can
You can use "adb push" and "adb pull" in recovery to copy files from and to your phone, but you have to mount sdcard from recovery first.
to browse storage directly on the phone you can use "adb shell" and then "ls" and "cd directoryname" to find file which you want to copy from the device.
Hi folks,
I tried to modify the platform.xml file to enable some write permissions. As far as I can tell, the app I used to modify the file didn't write it back correctly, and now my device is what might be called "semi-bricked."
Almost everything force closes, WiFi and write permissions seem to be broken, and I can't seem to get my Galaxy Nexus to communicate with my PC via USB.
I tried booting into CWM and mounting some /system, but I'm not sure how to access it since fastboot/adb don't seem to recognize the device.
I've also booted into some sort of recovery (fastboot?) that looks like the attached image. But I can't get it to do anything except boot up into the normal OS when I click the power button.
Any suggestions on how I can get access back to my device so I can repair/replace the platform.xml file and restore functionality to my phone?
Thank you very much!
Deozaan said:
Hi folks,
I tried to modify the platform.xml file to enable some write permissions. As far as I can tell, the app I used to modify the file didn't write it back correctly, and now my device is what might be called "semi-bricked."
Almost everything force closes, WiFi and write permissions seem to be broken, and I can't seem to get my Galaxy Nexus to communicate with my PC via USB.
I tried booting into CWM and mounting some /system, but I'm not sure how to access it since fastboot/adb don't seem to recognize the device.
I've also booted into some sort of recovery (fastboot?) that looks like the attached image. But I can't get it to do anything except boot up into the normal OS when I click the power button.
Click to expand...
Click to collapse
No it is not bootloader. to access to the bootloader turn on your device long pressing power, volume up and volume down buttons together (don't use odin).
To access to cwm recovery from bootloader just press volume down button until you see "recovery" option, then press power button and it will boot in recovery.
which rom are you using?
solution: download the zip file of your rom and extract the file you modified, make a zip (if you can't make a flashable zip i'll post an attachment for you) and flash it in recovery
enryea123 said:
No it is not bootloader. to access to the bootloader turn on your device long pressing power, volume up and volume down buttons together (don't use odin).
To access to cwm recovery from bootloader just press volume down button until you see "recovery" option, then press power button and it will boot in recovery.
which rom are you using?
solution: download the zip file of your rom and extract the file you modified, make a zip (if you can't make a flashable zip i'll post an attachment for you) and flash it in recovery
Click to expand...
Click to collapse
Thanks for the reply.
I actually did manage to get my PC to recognize the device via USB/adb and I copied the file back to the way it should have been. But that didn't fix anything, so I ended up doing a wipe/factory reset. Everything works now but things still seem a bit. . . off. For instance, it takes a while after my phone boots up before the WiFi will actually connect. It used to be connected almost immediately. And it takes a while for the alarm icon to load/show up in the notification area at the top. And I can't find the option in the settings anymore to use USB debugging. There are lots of little things like that, where it works, but it just doesn't quite work like it used to. . .
And to answer your question, I'm using the stock ROM that came with the Galaxy Nexus (from Google Play Store).
Deozaan said:
Thanks for the reply.
I actually did manage to get my PC to recognize the device via USB/adb and I copied the file back to the way it should have been. But that didn't fix anything, so I ended up doing a wipe/factory reset. Everything works now but things still seem a bit. . . off. For instance, it takes a while after my phone boots up before the WiFi will actually connect. It used to be connected almost immediately. And it takes a while for the alarm icon to load/show up in the notification area at the top. And I can't find the option in the settings anymore to use USB debugging. There are lots of little things like that, where it works, but it just doesn't quite work like it used to. . .
And to answer your question, I'm using the stock ROM that came with the Galaxy Nexus (from Google Play Store).
Click to expand...
Click to collapse
first: to make the "developer settings" appear go settings/About phone and tap on build number 7 times (google has hidden it in 4.2).
said that, you can:
1) fix permissions in cwm recovery (under advanced menu)
2) download a zip of your rom and flash it in recovery
3) if your bootloader is unlocked (you see a padlock when you boot your phone) you can flash a factory image to return completely stock.
4) if your bootloader is locked you can follow the 3) method but you will lose all your sdcard data.
enryea123 said:
first: to make the "developer settings" appear go settings/About phone and tap on build number 7 times (google has hidden it in 4.2).
said that, you can:
1) fix permissions in cwm recovery (under advanced menu)
2) download a zip of your rom and flash it in recovery
3) if your bootloader is unlocked (you see a padlock when you boot your phone) you can flash a factory image to return completely stock.
4) if your bootloader is locked you can follow the 3) method but you will lose all your sdcard data.
Click to expand...
Click to collapse
Thanks again for the response.
I got developer settings to appear. Hooray! Fix Permissions is one of the first things I did to try to repair the platform.xml file when things were broken. I ran it again (but from ROM Manager rather than from CWM Recovery) and it didn't seem to have any effect on the weird sluggishness when first booting up.
My bootloader is unlocked. Will I have to root again if I flash one of those factory images? I'm currently backing up the contents of my "SD card" in case I have to completely wipe the entire thing.
Deozaan said:
Thanks again for the response.
I got developer settings to appear. Hooray! Fix Permissions is one of the first things I did to try to repair the platform.xml file when things were broken. I ran it again (but from ROM Manager rather than from CWM Recovery) and it didn't seem to have any effect on the weird sluggishness when first booting up.
My bootloader is unlocked. Will I have to root again if I flash one of those factory images? I'm currently backing up the contents of my "SD card" in case I have to completely wipe the entire thing.
Click to expand...
Click to collapse
well, you can firstly try to flash a zip of your rom (search on xda or google), it should fix.
the fastboot flash method is the google method so you won't need root (you just have to go into fastboot and connect your phone to your computer, doesn't matter if you have root, or a different rom/kernel/recovery).
If you don't know you to flash from fastboot try first to flash the rom zip.
having a backup of the sdcard is always a good idea :good:, i have 2 backups of mysdcard on 2 different hard drives of my computer and the pictures i take with the camera are automatically uploaded on my dropbox .
enryea123 said:
well, you can firstly try to flash a zip of your rom (search on xda or google), it should fix.
the fastboot flash method is the google method so you won't need root (you just have to go into fastboot and connect your phone to your computer, doesn't matter if you have root, or a different rom/kernel/recovery).
If you don't know you to flash from fastboot try first to flash the rom zip.
Click to expand...
Click to collapse
Weird things are happening. I was making a backup of the "SD Card" and partway through, things stopped copying over. And pretty much everything got erased from it. No big deal, since I'd already copied the important stuff first.
But CWM Recovery won't flash the zip file. It keeps telling me the update failed. I verified the hash on the zip I downloaded and it is the same as what is listed on Google's site. But it just won't flash in CWM.
Deozaan said:
Weird things are happening. I was making a backup of the "SD Card" and partway through, things stopped copying over. And pretty much everything got erased from it. No big deal, since I'd already copied the important stuff first.
But CWM Recovery won't flash the zip file. It keeps telling me the update failed. I verified the hash on the zip I downloaded and it is the same as what is listed on Google's site. But it just won't flash in CWM.
Click to expand...
Click to collapse
wait, are you in cwm recovery o just in stock recovery (they are different)? have you previously installed a cwm recovery using fastboot? which zip are you trying to flash?
edit: ok you know what is rom manager so i think that you are in cwm.
edit2: try this zip http://goo.im/devs/bigxie/maguro/bigxie_maguro_OTA_JOP40D-signed.zip
enryea123 said:
wait, are you in cwm recovery o just in stock recovery (they are different)? have you previously installed a cwm recovery using fastboot? which zip are you trying to flash?
edit: ok you know what is rom manager so i think that you are in cwm.
edit2: try this zip
Click to expand...
Click to collapse
I was in CWM Recovery. I was using the zip file that I extracted from the link you gave me for Google's stock ROMs (I can't post external links yet):
(Factory Images "takju" for Galaxy Nexus "maguro" (GSM/HSPA+) (with Google Wallet) --> Android 4.2.1 (JOP40D))
Strangely enough, after "failing" to flash the zip, I had to log into my Google account again because I had selected the option to Wipe Data and Cache, and most things seem to be working very well again. One odd thing I'm still noticing, though, is that some things don't seem to be syncing properly. For example, if I archive some of my email in the Gmail app, then log into Gmail on my PC, the mail is still unread in my inbox. My phone downloads the new mail just fine. But the changes I make on my phone (reading, archiving, deleting, etc.) don't seem to be syncing to anywhere else.
I'm downloading the zip you suggested. I'll give that a try. Thanks!
enryea123 said:
edit2: try this zip http://goo.im/devs/bigxie/maguro/bigxie_maguro_OTA_JOP40D-signed.zip
Click to expand...
Click to collapse
Try this one
Deozaan said:
I was in CWM Recovery. I was using the zip file that I extracted from here the link you gave me (I can't post external links yet):
(Factory Images "takju" for Galaxy Nexus "maguro" (GSM/HSPA+) (with Google Wallet) --> Android 4.2.1 (JOP40D))
Strangely enough, after "failing" to flash the zip, I had to log into my Google account again because I had selected the option to Wipe Data and Cache, and most things seem to be working very well again. One odd thing I'm still noticing, though, is that some things don't seem to be syncing properly. For example, if I archive some of my email in the Gmail app, then log into Gmail on my PC, the mail is still unread in my inbox. My phone downloads the new mail just fine. But the changes I make on my phone (reading, archiving, deleting, etc.) don't seem to be syncing to anywhere else.
I'm downloading the zip you suggested. I'll give that a try. Thanks!
Click to expand...
Click to collapse
That is not a flashable zip! It is a factory image, it must be flashed via fastboot using a computer.
enryea123 said:
That is not a flashable zip! It is a factory image, it must be flashed via fastboot using a computer.
Click to expand...
Click to collapse
Just to be sure I explained myself clearly, I downloaded that Google provided factory image (a .tgz file) and inside it I found a zip file named "image-takju-jop40d.zip" which is what I tried to flash.
That said, I've just recently finished downloading the one you just suggested to me and I will give that one a try soon. Thank you again for your help. I really appreciate it.
I got it working again. The ROM you gave me failed signature verification in CWM Recovery, but I told it to install anyway and it worked. Thank you.
The problem I was having with Gmail not syncing was that I used Titanium Backup to restore my data, but because all the data from my "SD card" got erased, Titanium Backup itself lots its settings, so my Device ID was different. I guess Gmail relies on the device ID for syncing.
Thank you so much for your help! I learned a lot from the experience.
Glad i helped you. well this is one of the reasons why i don't restore data with titanium (especially system data).
and by the way:
Deozaan said:
Just to be sure I explained myself clearly, I downloaded that Google provided factory image (a .tgz file) and inside it I found a zip file named "image-takju-jop40d.zip" which is what I tried to flash.
That said, I've just recently finished downloading the one you just suggested to me and I will give that one a try soon. Thank you again for your help. I really appreciate it.
Click to expand...
Click to collapse
To fully reset and install a clean rom using fastboot you have to extract the bootloader-blabla.img and radio-blabla.img files from the tar.gz archive and then extract the 4 .img files inside the zip (that is inside the tar.gz) and flash this 6 .img files connetting your phone in bootloader mode to your computer and using fastboot in terminal (in fact this procedure reinstall the recovery too).
hi
i already unlock the bootloader, install custom recovery TWRP, and done a backup
i also copy my backup to PC
now i'm confuse
- i need to root the phone or can i just flash the new room?
- if i need to root the phone i found an italian guide on 4.0 and attach file, can i use that? i have 4.1.1 on mine now
i'm not interested to have HTC stock with root but what i want is to install MIUI ROM
this is the only guide i found in english that explains how to install the rom
external link (i can't post it) miuiandroid.com/community/threads/installing-the-htc-one-x-required-s-on-steps.16592/
what i understand is:
- boot my device power + menu down, to see the FASTBOOT USB i have to select FASTBOOT
- flash the boot.img
- press the power button once (HBOOT i guess), click volume down, highlight recovery & press power
- Flash the downloaded ROM via recovery normally and it followup at this link
external link (i can't post it) miuiandroid.com/community/threads/how-to-update-upgrade-miui.15424/
i need to copy the img rom in SD ROOT before starting with all this process
- now i need to Wipe data/factory reset, Cache Wipe & Dalvik Cache Wipe in all tutorial i found this is done with clockworkmod
in TWRP under menu WIPE i guess are System, Cache, Dalvik buttons
after that i'm note sure if i need to flash italian language, if i don't need and i can just download it later i tihink is not a big deal
unless is all in chinese
is the metod correct?
do i have to copy ROM file in .zip format as i download?
here where i found ROM
from official site grey button miui.com/download-7.html
OR
from UK web site miuiandroid.com/community/threads/3-4-28.20232/
the boot.img is here
point 3 miuiandroid.com/community/threads/installing-the-htc-one-x-required-s-on-steps.16592/
i'm not sure if would be better to use clockworkmod, since most tutorials use that..
thanks
Doesn't matter which recovery you use. Yes just place the zip file on your sd card. Flash boot.img as you already said. Perform a full wipe and then flash the Rom zip. Reboot and its done.
The Roms are pre-rooted so you dont need to worry about that. Italian language should be included i guess.
Sent from my HTC One X using xda app-developers app
Heres what i do :
1) Put Rom.zip on SD card
2) Put boot.img in fastboot folder
3) fastboot erase cache
4) fastboot flash boot boot.img
5) fastboot erase cache
6) Reboot into recovery
7) Full wipe (except sd card)
8) Install rom
9) Enjoy new rom
Andy
i did my first mess but fortunally i could restore since i had copy the backup on my mac too
i don't know what went wrong but this is what happened:
- i did how was told before, but actually i download boot.img and rom from 2 different sites
- after reboot it didn't move from first screena waited for 15 minutes almost, so i did reboot in recovery tri to wipe but nothing happened
- so i decide to restore... but it did boot even if it was successful
- i thought that if i flashed the boot.img first time i may need to do it again, i found boot.emmc.win, rename it to boot.img, flash it and then i restored successfully
:victory:
now, to try a different rom i need to restore (maybe is safer)? can i copy the rom from recovery or fastboot?
what can it be wrong with my miui rom? could it be boot.img and rom file mismatch? can't find where to download both
al404 said:
i did my first mess but fortunally i could restore since i had copy the backup on my mac too
i don't know what went wrong but this is what happened:
- i did how was told before, but actually i download boot.img and rom from 2 different sites
- after reboot it didn't move from first screena waited for 15 minutes almost, so i did reboot in recovery tri to wipe but nothing happened
- so i decide to restore... but it did boot even if it was successful
- i thought that if i flashed the boot.img first time i may need to do it again, i found boot.emmc.win, rename it to boot.img, flash it and then i restored successfully
:victory:
now, to try a different rom i need to restore (maybe is safer)? can i copy the rom from recovery or fastboot?
what can it be wrong with my miui rom? could it be boot.img and rom file mismatch? can't find where to download both
Click to expand...
Click to collapse
extract the boot image from the rom you are going to use
ok, i tryed again but now it get stack on Mi black screen
i waited 8 minutes but nothing happens, i also tried to wipe cache and davik, nothing happens
at list i get to black Mi screen
do i need to delete the boot.img from ROM zip?
what could it be?
1st u didn't mention which phone u r using
2nd dn't get confuse while downloading rom n .img file
Type in google
(Ur phone model) android development xda
U'll find all the stuffs related to ur phone
So try this 1 n remember before updating or rooting or anythg related to ur which can mess ur phone or can brick ur phone
I suggest u read twice the thread n procedures n also check thrice the stuff which u gonna need to perform ur act.
Sent from my GT-N7100 using xda premium
al404 said:
ok, i tryed again but now it get stack on Mi black screen
i waited 8 minutes but nothing happens, i also tried to wipe cache and davik, nothing happens
at list i get to black Mi screen
do i need to delete the boot.img from ROM zip?
what could it be?
Click to expand...
Click to collapse
i would try a different rom for now, viperx perhaps. and the boot image is in the rom zip, extract the boot img from the rom and put it in your fastboot folder then copy the rom to your sdcard. once you have done that, fastboot erase cache, flash the boot image, fastboot erase cache again, then back into recovery, wipe cache and dalvik just to be sure then use recovery to flash the rom and hey presto. all of the above is assuming you have the one x international tegra 3
I have htc one x european terga 3, as far as I know mini is only for tegra 3
what you describe is exactly what I did:
- I leave the rom zip ad it is, I didn't remove boot.imf that I extract, correct?
- when I flash I hit hoot fastboot, connect USB and fastboot change in fastboot USB, to go back I select Hboot and and hit power, prom there recovery
- I did unlock bootloader but did not get rooted my phone, could it be that?
al404 said:
I have htc one x european terga 3, as far as I know mini is only for tegra 3
what you describe is exactly what I did:
- I leave the rom zip ad it is, I didn't remove boot.imf that I extract, correct?
- when I flash I hit hoot fastboot, connect USB and fastboot change in fastboot USB, to go back I select Hboot and and hit power, prom there recovery
- I did unlock bootloader but did not get rooted my phone, could it be that?
Click to expand...
Click to collapse
read this post. at least twice!! http://forum.xda-developers.com/showthread.php?t=2069904 do not do the "unlock bootloader" section as you already did that
@nogotaclue sorry i read so many, and some of them sayed that root was not necessary if you flash a new rom, other sayed it could still be necessary... now i rooted with the app and did a new backup that i'm coping on PC
reading further it says: to wipe, install rom, and flash boot.img after
"Now go back and press install. Go to the folder where the ROM you downloaded, is located in. Select the ROM and slide the screen to flash it. After it flashes, press the back button. Press Reboot and Reboot into bootloader. Open the ROM you downloaded from your computer. You should see boot.img. Extract it to your computer. Open my toolkit and press Flash a Kernel. Locate the boot.img and it will flash it."
al404 said:
@nogotaclue sorry i read so many, and some of them sayed that root was not necessary if you flash a new rom, other sayed it could still be necessary... now i rooted with the app and did a new backup that i'm coping on PC
reading further it says: to wipe, install rom, and flash boot.img after
"Now go back and press install. Go to the folder where the ROM you downloaded, is located in. Select the ROM and slide the screen to flash it. After it flashes, press the back button. Press Reboot and Reboot into bootloader. Open the ROM you downloaded from your computer. You should see boot.img. Extract it to your computer. Open my toolkit and press Flash a Kernel. Locate the boot.img and it will flash it."
Click to expand...
Click to collapse
yes you can do it that way, i usually flash first but sometimes it does not work, so just flash it last as it says in the tutorial
after root, with the same steps, the ROM starts... but
touch screen is not working :crying:
now i'm gonna look arond to see if i found some post about that
this (kernel patch) solved my last issue
http://miuiandroid.com/community/threads/hox-miui-v5-official-release.20215/page-2
al404 said:
this (kernel patch) solved my last issue
http://miuiandroid.com/community/threads/hox-miui-v5-official-release.20215/page-2
Click to expand...
Click to collapse
So everything working now ?
Sent from my underpants using Daz and Lenor summertime
YES :good: without that path touchscreen wasn't working :victory:
hope is not going to mess all up with first update
People,
I got to install the Cyanogen Firmware on my Xperia ZL (6503) and i'm give a problem.
I follow the instructions on the http://wiki.cyanogenmod.org/w/Install_CM_for_odin
and download the file cm-10.1.2-odin.zip in this page:
http://download.cyanogenmod.org/?type=stable&device=odin
When I select the option Factory Default, the CWM show the message: Error Mounting /sdcard/.android_Secure! and no mount the internal sdcard. I'm install the .zip file from the external sdcard, and stuck on logo of Cyanogen.
Any fix for this error?
Do you mean you are unable to perform a factory reset? You can do this without using CWM. Inside of the phone settings, backup & restore, there is an option to reset to factory.
If you mean you are unable to install the zip, then maybe you need to install a different version of recovery.
ryude said:
Do you mean you are unable to perform a factory reset? You can do this without using CWM. Inside of the phone settings, backup & restore, there is an option to reset to factory.
If you mean you are unable to install the zip, then maybe you need to install a different version of recovery.
Click to expand...
Click to collapse
Humm, i'm not do factory reset before install the Cyanogenmod. I'm install the boot.img with CWM provided with cyanognen file. What's the difference do factory reset directly in original rom?
hudfer said:
Humm, i'm not do factory reset before install the Cyanogenmod. I'm install the boot.img with CWM provided with cyanognen file. What's the difference do factory reset directly in original rom?
Click to expand...
Click to collapse
Ah you're attempting to flash the boot.img file? You have to use fastboot I believe in order to flash it.
1. You must have unlocked bootloader of your device. You can do so from here.
2. Download Fastboot here.
3. Place Fastboot.zip and the boot.img files onto your Desktop.
2. Extract files from the Fastboot archive to your Desktop. Move the boot.img file into the Fastboot folder.
3. Turn ON the USB debugging option on your device by going to Menu>>Settings>>Developer options>>USB debugging.
4. Once enabled, connect your device to your PC via USB cable.
5. Launch a Command Prompt Window on the Desktop of your PC. To do so, press and hold the Shift button on your keyboard and right-click on any blank area on the screen, then choose Open command window here.
6. Type in following command into the Command Prompt Window:
adb reboot bootloader
7. Your device will reboot into the bootloader mode.
8. Once inside bootloader mode, enter the following command into Command Prompt.
fastboot flash boot boot.img
9. Once the file’s flashed, reboot your device.
10. And you’re all set! You now have CWM recovery!
ryude said:
Ah you're attempting to flash the boot.img file? You have to use fastboot I believe in order to flash it.
1. You must have unlocked bootloader of your device. You can do so from here.
2. Download Fastboot here.
3. Place Fastboot.zip and the boot.img files onto your Desktop.
2. Extract files from the Fastboot archive to your Desktop. Move the boot.img file into the Fastboot folder.
3. Turn ON the USB debugging option on your device by going to Menu>>Settings>>Developer options>>USB debugging.
4. Once enabled, connect your device to your PC via USB cable.
5. Launch a Command Prompt Window on the Desktop of your PC. To do so, press and hold the Shift button on your keyboard and right-click on any blank area on the screen, then choose Open command window here.
6. Type in following command into the Command Prompt Window:
adb reboot bootloader
7. Your device will reboot into the bootloader mode.
8. Once inside bootloader mode, enter the following command into Command Prompt.
fastboot flash boot boot.img
9. Once the file’s flashed, reboot your device.
10. And you’re all set! You now have CWM recovery!
Click to expand...
Click to collapse
Thank's for the explanation, but i'm have executed all the commands described by you and not work. Is the same commands on cyanogen wiki page. The CWM appears the same error and i'm install the cyanogen, but stucks in logo and the android is not start.
hudfer said:
Thank's for the explanation, but i'm have executed all the commands described by you and not work. Is the same commands on cyanogen wiki page. The CWM appears the same error and i'm install the cyanogen, but stucks in logo and the android is not start.
Click to expand...
Click to collapse
You should flash a stock FTF image using Flashtool. After you have completed this, you can try again.
ryude said:
You should flash a stock FTF image using Flashtool. After you have completed this, you can try again.
Click to expand...
Click to collapse
After hours of research, I resolved the problem. I`m followed the steps described on cyanogen wiki, adding the first step Factory Restore on original sony firmware and the problem persists. After launched the CWM, I select the option "Format /data" and after "Format /sdcard". After selected this options, the error message not appears again and the Cyanogen firmware install and launch successful! Probably with format, deleted some key or protection in internal sdcard. Thanks for the help!
hudfer said:
After hours of research, I resolved the problem. I`m followed the steps described on cyanogen wiki, adding the first step Factory Restore on original sony firmware and the problem persists. After launched the CWM, I select the option "Format /data" and after "Format /sdcard". After selected this options, the error message not appears again and the Cyanogen firmware install and launch successful! Probably with format, deleted some key or protection in internal sdcard. Thanks for the help!
Click to expand...
Click to collapse
I'm happy you were able to resolve your problem. How are you liking CyanogenMod so far?
ryude said:
I'm happy you were able to resolve your problem. How are you liking CyanogenMod so far?
Click to expand...
Click to collapse
The Cyanogen is always incredible, i'm use this custom rom since my Galaxy S2. The rom is very fast and clean. I most like in this version, the option "Expand Desktop", in particular opinion, the best configuration on the rom.
hudfer said:
The Cyanogen is always incredible, i'm use this custom rom since my Galaxy S2. The rom is very fast and clean. I most like in this version, the option "Expand Desktop", in particular opinion, the best configuration on the rom.
Click to expand...
Click to collapse
I'm have a first problem with full screen mode: the game "Kingdom Rush" not launch.
does not work for me
hudfer said:
After hours of research, I resolved the problem. I`m followed the steps described on cyanogen wiki, adding the first step Factory Restore on original sony firmware and the problem persists. After launched the CWM, I select the option "Format /data" and after "Format /sdcard". After selected this options, the error message not appears again and the Cyanogen firmware install and launch successful! Probably with format, deleted some key or protection in internal sdcard. Thanks for the help!
Click to expand...
Click to collapse
Hi,
I have the same issue, but after trying: "Format /sdcard" I get "Error formatting /sdcard!"
Please help! I'm researching 2 days in a row and can't find a solution.
flutur said:
Hi,
I have the same issue, but after trying: "Format /sdcard" I get "Error formatting /sdcard!"
Please help! I'm researching 2 days in a row and can't find a solution.
Click to expand...
Click to collapse
you just format your sdcard as FAT32, that's how i solved my problem
Same problem in Razr 925
ShanksVo said:
you just format your sdcard as FAT32, that's how i solved my problem
Click to expand...
Click to collapse
I have the same problem in my Razr 925. I installed with CWM 6.0.3.6-10.2 cm from the external SD.
1) First I tried from the inside SD, I never realized that appeared "Warning: No file_contexts", and install the zip of cm-10.2, the result was "Error mounting / data" "Error mounting / sdcard /. Android_secure".
2) From the external memory I managed to do it, but the logo remains Cyanogen cycling.
3) I tried to restore the backup, but "Can not mount / sdcard".
Now I don't know what to do, I researched and solution is always restart from the official android, in my case I can not start the official android. I need help please !:crying:
If you don't want to format your SD-card
flutur said:
Hi,
I have the same issue, but after trying: "Format /sdcard" I get "Error formatting /sdcard!"
Please help! I'm researching 2 days in a row and can't find a solution.
Click to expand...
Click to collapse
If you aren't able to (as in your case) or simply don't want to (as in mine, where I didn't have an external SD card handy); you can simply upgrade your recovery software.
In my case, Carbon ROM JB for the GT-N7000 came with CWM 6.0.3.5 which couldn't flash newer ROMs (like Carbon KitKat), and had issues with the internal SD card including the one in the topic of this post. Since I had just wiped my current ROM and didn't want to start up an ADB sideload session, I simply flashed PA (which came with CWM 6.0.3.7, a minor version bump but a huge difference here) and after rebooting to recovery again (I didn't even have to boot to PA), everything worked again.
(My first post that could be even considered remotely useful on XDA, so please tell me if it helped you!)
Thanks!
hudfer said:
After hours of research, I resolved the problem. I`m followed the steps described on cyanogen wiki, adding the first step Factory Restore on original sony firmware and the problem persists. After launched the CWM, I select the option "Format /data" and after "Format /sdcard". After selected this options, the error message not appears again and the Cyanogen firmware install and launch successful! Probably with format, deleted some key or protection in internal sdcard. Thanks for the help!
Click to expand...
Click to collapse
Finally!
PS: Do -not- try to encrypt your nexus 4 if you put 5.0 on it X(
i cannot install anything in TWRP atm
it says "could not find ´META-INF/com/google/android/update-binary´in zip file.
Any bright ideas ?
Citroon said:
i cannot install anything in TWRP atm
it says "could not find ´META-INF/com/google/android/update-binary´in zip file.
Any bright ideas ?
Click to expand...
Click to collapse
It looks so simply but did you take a look to your rom zip? open with a zip explorer like winzip in /META-INF/com/google/android and here you must find this file
SubwayChamp said:
It looks so simply but did you take a look to your rom zip? open with a zip explorer like winzip in /META-INF/com/google/android and here you must find this file
Click to expand...
Click to collapse
it's not only with the roms, it's with everything
i've tried to flash new firmware, gapps and nothing works :/
well, what version of twrp do you use? try first with oficcial 3.0.2.0, bootloader unlocked? check usb debbugging and allow oem unlock in developer options, sometimes neccessary mount system or enable MTP in recovery
SubwayChamp said:
well, what version of twrp do you use? try first with oficcial 3.0.2.0, bootloader unlocked? check usb debbugging and allow oem unlock in developer options, sometimes neccessary mount system or enable MTP in recovery
Click to expand...
Click to collapse
im using the official 3.0.2.0, i currenly have no RoM installed so i can't boot into anything
Citroon said:
im using the official 3.0.2.0, i currenly have no RoM installed so i can't boot into anything
Click to expand...
Click to collapse
try first formatting data, wipe everything except where placed your rom zip (int or extSD), mount system and flash again
SubwayChamp said:
try first formatting data, wipe everything except where placed your rom zip (int or extSD), mount system and flash again
Click to expand...
Click to collapse
Tried that, still having the error:crying:
Citroon said:
i cannot install anything in TWRP atm
it says "could not find ´META-INF/com/google/android/update-binary´in zip file.
Any bright ideas ?
Click to expand...
Click to collapse
ok, go to format the data and then write YES, but u will lose your data, so, backup your files, and then restore them. should be working !!
StonebridgeGr said:
ok, go to format the data and then write YES, but u will lose your data, so, backup your files, and then restore them. should be working !!
Click to expand...
Click to collapse
Doesn't work either, this is really weird to me, i've been flashing for a few years now, and never encountered this issue before.
-also note that i'm not amazing at this
Citroon said:
Doesn't work either, this is really weird to me, i've been flashing for a few years now, and never encountered this issue before.
-also note that i'm not amazing at this
Click to expand...
Click to collapse
ok. which image did u flash? which guide did u followed to flash twrp ? ( because a newiest image of TWRP RECOVERY for mi max is up )
StonebridgeGr said:
ok. which image did u flash? which guide did u followed to flash twrp ? ( because a newiest image of TWRP RECOVERY for mi max is up )
Click to expand...
Click to collapse
i've tried about every RoM available.
I also want to note that i have flashed with this version of TWRP before (3.0.2.0)
StonebridgeGr said:
ok. which image did u flash? which guide did u followed to flash twrp ? ( because a newiest image of TWRP RECOVERY for mi max is up )
Click to expand...
Click to collapse
tried about every rom available, and other things just to see what would work and what wouldn't (nothing can flash)
im currently running 3.0.2.0 and have flashed with this version of TWRP before, but suddenly it stopped working
Citroon said:
Tried that, still having the error:crying:
Click to expand...
Click to collapse
Probably a bad flashing and you are needing repari partitions, for that I recommend start from beginning again:
- flash miui rom for fastboot (unpack zip rom in your adb folder for better performance, connect device to pc into mode fastboot, be sure device be recogniced typing; fastboot devices then right click mouse and execute like admin over "flash all".
- then to install rom you can flash again twrp via fastboot typing any place adb folder and placing file recovery.img this folder; fastboot flash recovery recovery.img
- then go to recovery with hardware keys and flash supersu v.2.79
SubwayChamp said:
Probably a bad flashing and you are needing repari partitions, for that I recommend start from beginning again:
- flash miui rom for fastboot (unpack zip rom in your adb folder for better performance, connect device to pc into mode fastboot, be sure device be recogniced typing; fastboot devices then right click mouse and execute like admin over "flash all".
- then to install rom you can flash again twrp via fastboot typing any place adb folder and placing file recovery.img this folder; fastboot flash recovery recovery.img
- then go to recovery with hardware keys and flash supersu v.2.79
Click to expand...
Click to collapse
oh boy, i guess im screwed for now then.
i only have access to a macbook for the next few days, tried installing fastboot on it but that's a complete nightmare
Citroon said:
oh boy, i guess im screwed for now then.
i only have access to a macbook for the next few days, tried installing fastboot on it but that's a complete nightmare
Click to expand...
Click to collapse
two things; I assume that trying to flash from extSD, if yes with file explorer of recovery copy to internal memory, maybe an issue to reading extSD, also you can to install a newer version of recovery 3.0.3.2 works sometimes for me and last here you have a reading page about install fastboot on mac (nightmare) http://www.stechguide.com/setup-adb-and-fastboot-on-mac-easy-step-by-step-guide/
SubwayChamp said:
two things; I assume that trying to flash from extSD, if yes with file explorer of recovery copy to internal memory, maybe an issue to reading extSD, also you can to install a newer version of recovery 3.0.3.2 works sometimes for me and last here you have a reading page about install fastboot on mac (nightmare) http://www.stechguide.com/setup-adb-and-fastboot-on-mac-easy-step-by-step-guide/
Click to expand...
Click to collapse
I finally got it working
I was so stubborn that I decided to install Windows Bootcamp on my mac
it was as simple as reinstalling TWRP and do a clean wipe, now i can install roms and all the other things as i please again.
-Thank you for your help!