Related
WTF is going on, why has this (in the history of this phone) apparently never been asked? I feel like I'm taking crazy pills over here, just trying to flash a simple rom.
i can access mine through CWM.
yes yes, the only thing i noticed that is different on this phone is that when i make a nandroid it puts it on my external sd instead of my internal but it still sees my internal.
If cwm is not recognising the internal sd card....you have a corrupt partition. You need to odin
Stock. Tar boot into stock recovery wipe data/cache 3 times each reboot. Then root/ flash cwm recovery back onto the phone and then wipe and flash your rom
whitesox311 said:
WTF is going on, why has this (in the history of this phone) apparently never been asked? I feel like I'm taking crazy pills over here, just trying to flash a simple rom.
Click to expand...
Click to collapse
Are you getting this message after you root the device? I had this same issue and realize I needed to first root the device, open ROM manager to give it root access then reboot. After that it was OK.
silver03wrx said:
If cwm is not recognising the internal sd card....you have a corrupt partition. You need to odin
Stock. Tar boot into stock recovery wipe data/cache 3 times each reboot. Then root/ flash cwm recovery back onto the phone and then wipe and flash your rom
Click to expand...
Click to collapse
This............^^^^^^^^^^^^^^
This just started yesterday and i cant stop it. My phone reboots and says that memory is nearly full, then goes into a bootloop. I cant stop it long enough to back up texts, phone contacts and call log which is REALLY important; is there a way to back that up through recovery?
i'm really desperate here!
Edit: I can get the phone working through a format, but i need to be able to get contacts and sms backed up
Alternitavely, is there a way to run a clockword mod backup on an android emulator on my comp, so i can back up my important stuff?
what you should try doing is putting your sd card directly into your computer and delete stuff you don't need to get back so memory and then once you do that out it back into your phone
i cleared up the memory, internal and external. the stupid ROM is still broken
if its just the rom go to a different one and redownload mikrom later to make sure nothing happened in the initial download
If you haven't already, try removing some apps through adb, then reflash the ROM only wiping dalvik and cache. You shouldn't lose any of your text, call logs or contacts if you don't wipe data.
Sent from my PG06100 using Tapatalk
From The Hacker Manifesto:
I made a discovery today. I found a computer. Wait a second, this is cool. It does what I want it to. If it makes a mistake, it's because I screwed it up. Not because it doesn't like me... Or feels threatened by me.. Or thinks I'm a smart ass.. Or doesn't like teaching and shouldn't be here...
Click to expand...
Click to collapse
I love it sooooo the rom isnt stupid, the team of developers supporting it are amazing and you should setup adb and get a logcat, also you should nandroid before you flash so in case it goes wrong you can flash back, like insurance but you actually get something from this without paying..
if you did nandroid boot into bootloader and select recovery (hold volume down and power on use volume button to highlight recovery and power button to select)
I'm not sure if mikrom wipes or not but there's always that advanced restore option in cwm recovery flash rom, restore data and sd-ext if you have a ext partition with important data on it.
crump84 said:
If you haven't already, try removing some apps through adb, then reflash the ROM only wiping dalvik and cache. You shouldn't lose any of your text, call logs or contacts if you don't wipe data.
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
I managed to get some apps removed, its no longer giving me the memory-full error, but its still bootlooping a minute or so after loading. going to try the cache and davlik wipes, then a another install....
JKILO said:
From The Hacker Manifesto:
Click to expand...
Click to collapse
thanks I always do a nandroid backup before doing a format; doesnt help. I can load the clean rom just fine, but when i restore, it goes into bootloop again....
sparksco said:
I'm not sure if mikrom wipes or not but there's always that advanced restore option in cwm recovery flash rom, restore data and sd-ext if you have a ext partition with important data on it.
Click to expand...
Click to collapse
ok, ill try this.
Also, how do i set up an sd-ext to automatically backup texts and call history etc to it?
crump84 said:
If you haven't already, try removing some apps through adb, then reflash the ROM only wiping dalvik and cache. You shouldn't lose any of your text, call logs or contacts if you don't wipe data.
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
did not work - goes back to bootloop. how do i install ADB?
Jedman67 said:
did not work - goes back to bootloop. how do i install ADB?
Click to expand...
Click to collapse
http://developer.android.com/sdk/index.html
Beginner's Guide to Installing the SDK and Getting Started with ADB
If nothing else, like Jkilo said, provide a logcat and maybe someone could take a look.
Did you ever get this fixed?
The usual way of fixing this is formatting /system, wiping dalvik, wiping cache, and reflashing the rom.
VICODAN said:
Did you ever get this fixed?
The usual way of fixing this is formatting /system, wiping dalvik, wiping cache, and reflashing the rom.
Click to expand...
Click to collapse
no. what i did was a backup, complete factory reset, wipe, dalvik wipe, etc - several times each, including a full on sd-card format, which took me hours to reload everything back on - and then reflashed MikShift. It worked fine for about a day, but then it started to go into bootloops again, so i again did a backup, full reset and all wipes, and restored data only to the new flash of mikshift. Once again its bootlooping.
LOG: ive been off the forums for several months, how do i get this log?
IMAGE: When i go into bootloader and enter recovery, it shows me a message in green text
"PG06diag.zip
No image!
PG06diag.nbh
No image or wrong image!
PG06img.zip
No image!
PG06img.nbh
No image or wrong image!"
At this point, im ready to RUU back to factory unrooted, so i can take it back to sprint and get it replaced.
I should not need to reflash the ROM every single day.
Jedman67 said:
no. what i did was a backup, complete factory reset, wipe, dalvik wipe, etc - several times each, including a full on sd-card format, which took me hours to reload everything back on - and then reflashed MikShift. It worked fine for about a day, but then it started to go into bootloops again, so i again did a backup, full reset and all wipes, and restored data only to the new flash of mikshift. Once again its bootlooping.
LOG: ive been off the forums for several months, how do i get this log?
IMAGE: When i go into bootloader and enter recovery, it shows me a message in green text
"PG06diag.zip
No image!
PG06diag.nbh
No image or wrong image!
PG06img.zip
No image!
PG06img.nbh
No image or wrong image!"
At this point, im ready to RUU back to factory unrooted, so i can take it back to sprint and get it replaced.
I should not need to reflash the ROM every single day.
Click to expand...
Click to collapse
OK
0) Run a backup with titanium backup.
1) First of all go to clockwork -> mounts storage -> FORMAT /SYSTEM.
2) Wipe /cache, wipe dalvik, wipe/data, factory reset, repartition sd card.
3) Redownload the rom or try a proven ROM like UKE or CM7-255. If AOSP MAKE SURE TO FLASH GAPPS.
NO NEED TO RUU.
4) DO NOT RESTORE YOUR BACK UP. See how stable the phone runs.
5) If the phone is still unstable try a different battery.
6) Do not flash a custom kernel.
i formatted my backup SD card, and copied the essential data to it, and i have it running in the phone now. it seems to be running fine so far, i suspect the other SD may have gotten corrupt or physically damaged
Vic: every single time this has happened, i first went to clear the data and dalvik caches and ran a factory reset, all through the CWM recovery interface. Then when i reinstall mikshift, i restore the data using advanced restore, wait 24-48 hours, bootloops start all over again.
after two days of running on the new sd card, i start getting bootloops again. it must be a problem with the phone or the OS, but at this point i dont care anymore.
Is there a guide to RUU back to stock unroot? this phone is going back to sprint by weeks end, period.
thanks for the help folks.
Jedman67 said:
Vic: every single time this has happened, i first went to clear the data and dalvik caches and ran a factory reset, all through the CWM recovery interface. Then when i reinstall mikshift, i restore the data using advanced restore, wait 24-48 hours, bootloops start all over again.
after two days of running on the new sd card, i start getting bootloops again. it must be a problem with the phone or the OS, but at this point i dont care anymore.
Is there a guide to RUU back to stock unroot? this phone is going back to sprint by weeks end, period.
thanks for the help folks.
Click to expand...
Click to collapse
Here's the 2.2 RUU zip http://forum.xda-developers.com/showthread.php?t=971550 Just put it on the root of sd, boot in hboot and let it do its thing.
Or you can run the RUU exe, just download and run from your pc. It's pretty self explanatory http://forum.xda-developers.com/showthread.php?t=1335068
Jedman67 said:
Vic: every single time this has happened, i first went to clear the data and dalvik caches and ran a factory reset, all through the CWM recovery interface. Then when i reinstall mikshift, i restore the data using advanced restore, wait 24-48 hours, bootloops start all over again.
after two days of running on the new sd card, i start getting bootloops again. it must be a problem with the phone or the OS, but at this point i dont care anymore.
Is there a guide to RUU back to stock unroot? this phone is going back to sprint by weeks end, period.
thanks for the help folks.
Click to expand...
Click to collapse
The problem is you didn't format /system.
Redownload the Rom. Then follow THIS GUIDE when you flash.
VICODAN said:
The problem is you didn't format /system.
Click to expand...
Click to collapse
Exactly 10 char
---------- Post added at 12:34 AM ---------- Previous post was at 12:31 AM ----------
prboy1969 said:
Redownload the Rom. Then follow THIS GUIDE when you flash.
Click to expand...
Click to collapse
Yeah that guide is great for flashing sense roms since "most" sense roms don't format/wipe the system partition correctly. Aosp roms you just do a data facotry wipe and everything installs just fine
hello, last week i bricked my tf300, this is what happened...
i installed the energy rom along with the 4.2.1 bootloader, i was already using twrp 2.4.3.0 and it seemed to work fine for a while but then i had problems with a double screen after trying a different rom (cant remember which) anyway i tried the usual resets and wipes to to fix it but no joy. I then used the wipe data in bootloader thinking a full clean wipe would sort it but it just booted straight into twrp.
in twrp nothing will mount apart from system, ive used fastboot to flash various stock blobs, proper twrp img etc but even tho fastboot said everything flashed ok, i still boot into the old twrp which wont mount anything apart from system.
i then got an old 8 gig sd card and put stock roms and energy rom on root of the sd card , in twrp i mounted system but cant mount cache, data or sd card but strangely, i was able to copy the above roms from the sd card and move them to the mounted system partition which i was then able to install the energy rom with aroma installer , happy days i thought until after installation it rebooted straight to twrp again asking for password?
when i try to install stock roms by the above method it fails because cache isnt mounted. i think the twrp is corrupted, how do i fix this?
could someone with the know how tell me what im doing wrong,? should i full wipe again? should i wipe the twrp and how do i do this?
i am sort of a newb to this and any advice would be great
Hello all,
I've installed cromi-x 5.1.2 one month ago, without any problems. But today, after a night in charge (tablet off), I can't boot on cromi-x, I'm blocked on cromi-x logo with waiting cursor which turns, turns, turns
I can access to twrp only but I never do a backup. Numerous reboots done without effects.
Any help will be heplfull :good:
Thx for your help
tanis73 said:
Hello all,
I've installed cromi-x 5.1.2 one month ago, without any problems. But today, after a night in charge (tablet off), I can't boot on cromi-x, I'm blocked on cromi-x logo with waiting cursor which turns, turns, turns
I can access to twrp only but I never do a backup. Numerous reboots done without effects.
Any help will be heplfull :good:
Thx for your help
Click to expand...
Click to collapse
I believe that you have a bootloop... Can you tell us what is your bootloader version or firmware version? What is your TWRP version also? You may need to wipe your system to get it up and running again...
Thx LetMeKnow,
I'm using twrp 2.6.1.0. Bootloader number is 10.6.1.14.10-20130601.
When you tell about a wipe, full wipe with full install of the rom again? I will have to do a backup, data only is enough for apps installed?
thx
tanis73 said:
Thx LetMeKnow,
I'm using twrp 2.6.1.0. Bootloader number is 10.6.1.14.10-20130601.
When you tell about a wipe, full wipe with full install of the rom again? I will have to do a backup, data only is enough for apps installed?
thx
Click to expand...
Click to collapse
Your TWRP and firmware are good... I think that your data partition is corrupted and these are my suggestions..
1. In your TWRP, go to Advance and file manager, copy all your personal stuff to your external SD so you will not loose them when you format your data partition.
2. In your TWRP, do a nandroid backup of system, data, and boot
3. Try this first, Wipe everything except your system and your external SD and reboot...:fingers-crossed: If your device is up and running then it is telling you that you have a data partition corruption.. So your data backup from TWRP is useless..
4. If step 3 did not work, then your system is corrupted..You may want to do these.
--Format your data partition
--Wipe everything except your external SD
--Reinstall Cromi x and reboot so you a totally clean installion...
--Now you can restore your data backup and hope that it is not corrupted
--Good luck ....:fingers-crossed:
LetMeKnow said:
Your TWRP and firmware are good... I think that your data partition is corrupted and these are my suggestions..
1. In your TWRP, go to Advance and file manager, copy all your personal stuff to your external SD so you will not loose them when you format your data partition.
2. In your TWRP, do a nandroid backup of system, data, and boot
3. Try this first, Wipe everything except your system and your external SD and reboot...:fingers-crossed: If your device is up and running then it is telling you that you have a data partition corruption.. So your data backup from TWRP is useless..
4. If step 3 did not work, then your system is corrupted..You may want to do these.
--Format your data partition
--Wipe everything except your external SD
--Reinstall Cromi x and reboot so you a totally clean installion...
--Now you can restore your data backup and hope that it is not corrupted
--Good luck ....:fingers-crossed:
Click to expand...
Click to collapse
It's not a bootloop if he's stuck on the boot animation. If it keeps booting back - then yes, but getting stuck on the boot animation has happened to me numerous times (and always when I was on a Hund's kernel - sorry LMK, but Hund's just doesn't work on my tab), which a simple Factory Reset (the default option in the TWRP "Wipe" menu) took care of.
If that doesn't work, then yes - you will have to format data.
berndblb said:
It's not a bootloop if he's stuck on the boot animation. If it keeps booting back - then yes, but getting stuck on the boot animation has happened to me numerous times (and always when I was on a Hund's kernel - sorry LMK, but Hund's just doesn't work on my tab), which a simple Factory Reset (the default option in the TWRP "Wipe" menu) took care of.
If that doesn't work, then yes - you will have to format data.
Click to expand...
Click to collapse
The only way to diagnose the cause of "stuck at boot animation" (i.e. to gain insight instead of trying random things involving data loss) is to read the logcat.
Hello guys
Thx for all these infos. Finallly, it was the data...
Just before your answers, I've tried a wipe of cache and dalwik cache. Android's apps updated, and stuck again on logo animation.
So I've tried to update to 5.2a, with no format of data, the same arrived.
I've reinstalled the 5.2a with full wipe, and now it's ok (I will have to do it again, some options unselected are finally necessary. I will go back on 5.1.2 one if no update of 5.2a in the week.)
How can the data be corrupted? I remember, I've had installed an apk from googleplay, this apk can be faulty?
Thx
I seem to be having the same issue with the same version of CROMI and TWRP 2.4.4.0 so I wiped the tablet and put the ROM on a microsd to reflash. For some reason, I'm not seeing the zip file in the file manager or the install option. Please help.
tkdftw said:
I seem to be having the same issue with the same version of CROMI and TWRP 2.4.4.0 so I wiped the tablet and put the ROM on a microsd to reflash. For some reason, I'm not seeing the zip file in the file manager or the install option. Please help.
Click to expand...
Click to collapse
Try with a microsd formated in fat32, this should help.
TF700 with Chrimi-x 5.2a
Hi Guys,
First post. I installed Chromi x 5.2a to my TF700 and it was working great.
I was looking at the options and it said I was using the 4.1 JB theme but I could switch to 4.2 Theme of JB. I did, and when my tablet restarted, I get a black screen and a bunch of errors once in a while.
Is there a way I can change it back to 4.1? I can't access the OS only TWRP.
Thanks!
ColomboD said:
Hi Guys,
First post. I installed Chromi x 5.2a to my TF700 and it was working great.
I was looking at the options and it said I was using the 4.1 JB theme but I could switch to 4.2 Theme of JB. I did, and when my tablet restarted, I get a black screen and a bunch of errors once in a while.
Is there a way I can change it back to 4.1? I can't access the OS only TWRP.
Thanks!
Click to expand...
Click to collapse
Weird. I would re-flash the rom. It installs to the 4.1 launcher by default - but something is off... That shouldn't have happened.
Did you clean install CROMi-X?
Hi folks.
I'm facing a really weird problem. My friend's N5 doesn't want to boot with Lollipop, it shows the boot animation, but nothing happens, more than an hour and nothing.
I tried to flash back to kit kat. It indeed booted, but just to say that the camera and gallery has stopped, and gallery couldn't find any storage. When I go to the storage section in the settings, it doesn't show the pictures, music and other sources, just available space, cache and apps.
I tried to flash a custom rom to, but they all give me bootloops.
I never had this problems with my n4, so i don't know what to do anymore.
Any solutions?
Flash lollipop with fastboot. Then boot into the stock recovery and do a factory reset. Everything will be fine.
Sent from my Nexus 9 using XDA Free mobile app
I've already tried that, didn't work :crying:
Floydroider said:
I've already tried that, didn't work :crying:
Click to expand...
Click to collapse
You flashed the factory image with FASTBOOT and still had this problem? You sure?
Hmm. Try fastboot formatting all the partitions and then flashing the image again. Can't hurt.
_MetalHead_ said:
You flashed the factory image with FASTBOOT and still had this problem? You sure?
Click to expand...
Click to collapse
Yes, i'm absolutely sure. I'm used to use fastboot to flash my Nexus 4. I downloaded the proper factory image from Google and flashed it using both flash-all.bat and manual input in the cmd.
I tried to erase the partitions, format using TWRP, and install a custom ROM.
With twrp I can see the the internal storage partition, and even mount it to access by computer. But when the device boots, it just can't see the partition.
I put a song in the internal storage with twrp just to test, and when the device booted it didnt recognize the song, but when I got back to recovery, it was still there.
It seens that the problem is in the internal storage, but I don't know how to fix, and what could have caused it.
* Sorry, my english is bad :/
Floydroider said:
Yes, i'm absolutely sure. I'm used to use fastboot to flash my Nexus 4. I downloaded the proper factory image from Google and flashed it using both flash-all.bat and manual input in the cmd.
I tried to erase the partitions, format using TWRP, and install a custom ROM.
With twrp I can see the the internal storage partition, and even mount it to access by computer. But when the device boots, it just can't see the partition.
I put a song in the internal storage with twrp just to test, and when the device booted it didnt recognize the song, but when I got back to recovery, it was still there.
It seens that the problem is in the internal storage, but I don't know how to fix, and what could have caused it.
* Sorry, my english is bad :/
Click to expand...
Click to collapse
Try wiping cache in TWRP.
Wakamatsu said:
Hmm. Try fastboot formatting all the partitions and then flashing the image again. Can't hurt.
Click to expand...
Click to collapse
Tried that. I first used fastboot erase, didn't work, and then I use twrp to format to another fs. After that, I flashed the image again. Still nothing.
_MetalHead_ said:
Try wiping cache in TWRP.
Click to expand...
Click to collapse
I have wiped everything lots of times.
It's the first time I have a hard time trying to fix an android phone...
Now I flashed kitkat image again. It booted but with the storage problem. Then I update via notification, and it stuck in lollipop boot animation.
I will let it booting through the night. Or it boots after a couple of hours or the battery dies.
Floydroider said:
I have wiped everything lots of times.
It's the first time I have a hard time trying to fix an android phone...
Click to expand...
Click to collapse
Yeah this seems kinda crazy. Usually when stuff gets messed up like this a factory image clears it up. In your case, I honestly don't know what else to recommend. Sorry I can't be of more help.
Replace internal storage, nothing else you can do
Nothing worked in the end. My friend will send the phone to tech support.
Thank you guys for the help.
:good: