Hi. I ran into a situation. One day a few weeks back I was having issues with my phone. I decided to reflash the phone with a different ROM. I went into the developers menu, enabled debug (and maybe something else in that folder). Then rebooted the phone. Instead of the normal download mode or CWM/TWRP or recovery, I entered into a different menu. One I haven't seen before, and one I haven't seen since. I rebooted the phone but it was stuck in a reboot cycle. So again I tried to enter into a recovery mode or download mode. Again, the phone brought me to that strange menu (not the built in recovery). Since I was trying desperately to reflash my phone, I decided to try the menu options. One was to delete /system, another to delete /data, /cache etc. \\thinking that would do the same as formatting those partitions, I choose those options. I am still a novice, and I realize I made a mistake. When I rebooted, I was finally able to get into download mode. I successfully installed a boot manager (TWRP) and subsequently a ROM. However, when I tried formatting /dalvik, /cache, /system etc., there was only the /dalvik remaining. Everything else did not exist within the partitions to format. I searched for them throughout TWRP (and CWM) with no success. Anytime I install a new ROM, it says those items can't be found or don't exist.
How do I fix this problem? I've searched all over the net for weeks. Nothing pops up explaining how to rebuild the phone to have those partitions again. Please help.
PS. I tried adb, including creating a shell, and though it connects, there is nothing there. Odin also sees the phone, and I can flash it using Odin successfully.
Related
Hi All,
I have the Telstra HTC One XL, and have just recently attempted to install CM10 ROM - however have run into some problems that I would appreciate some advice to rectify. I had recently updated to Jelly Bean OTA.
I followed the guide on these forums - http://forum.xda-developers.com/showthread.php?t=1859478
I Successfully unlocked bootloader by following the steps at HTCdev.com
I Successfully installed TWRP Custom Recovery
I Downloaded CM10 as per - http://forum.xda-developers.com/showthread.php?t=1790032. I transferred this as well as Google Apps onto my phones storage.
When attempting to install CM10, I created the Nandroid backup as recommended, and proceeded to wipe the mentioned items using TWRP (a guide I saw said to wipe everything). This is when my Nandroid back-up got wiped. TWRP gives you the option to wipe cache, delvik cache, factory reset, system, external storage, internal storage and format data. I did alll of these, and this was my mistake I believe? I proceeded to try and install CM10 and gapps from internal storage (I had to re load these back on after I wiped everything), and the install of CM10 displayed as successful.
Upon rebooting to system, the HTC screen comes up first and then goes to the CM10 animation. The phone then stays on this animation (rotating circle) for up to 10-15 minutes.
I have read thread after thread with people experiencing similar issues, and have tried rectifying my problem with various versions of roms and different guides out there. I can still boot into recovery (TWRP) mode via bootloader, and this means I can still mount my phone's storage onto my PC and have access to the storage directory. As I have deleted the Nandroid backup though, and because the ROM's won't install, I am stuck in no man's land.
There must surely be a way to have a ROM installed (even if its back to stock Telstra) from the position I am in, it would be greatly appreciated if someone may be able to point me in the right direction.
Thanks,
Robbie
maybe yall need to "fastboot flash boot boot.img" now
robbie.d said:
TWRP gives you the option to wipe cache, delvik cache, factory reset, system, external storage, internal storage and format data. I did alll of these, and this was my mistake I believe?
Click to expand...
Click to collapse
Why do people keep doing this??? Just because TWRP gives you all those options, doesn't mean you should use them.
Sometimes, people will say to do a "full wipe" when flashing a ROM. But that term is a bit misleading. Factory reset (from TWRP, never from hboot), wipe Dalvik and wipe cache is all that is technically required when flashing a new ROM. Some people like to wipe more "just in case". But if you aren't completely confidant in what you are doing, keep in simple and don't make it more complicated than it needs to be.
I don't know if wiping everything is the cause of your woes, but it certainly didn't help, and caused you to do some extra steps.
Flash boot.img via fastboot as previously suggested. Otherwise, just try to re-download and flash the files agin. Its seems that some people are having troubles booting after flashing CM10 (even after doing the correct wipes and flashing boot.img). Doesn't seem to be much rhyme or reason, but just flashing again has fixed the problem for at least one person.
Thanks so much, such a simple fix! That has me booted up into CM10.
I have installed cm-10-20130107-NIGHTLY-evita and cm-10.0.0-evita , however with both of these versions, my touch screen is not working once it boots up. I can function with the volume up/down, and with the power buttons, but cannot get past my SIM card lock screen.
I noticed this thread http://forum.xda-developers.com/showthread.php?t=2083314 (no solution yet)...
Does anyone have a solution to this issue that seems a common one?
Alternatively, more than happy to get an alternative ROM on my phone in the interim...Can someone recommend me a ROM?
Again, I really appreciate the quick response to my problem, very happy my phone is in operation!
So, my previous post was a bit too optimistic. I've managed to get TWRP onto my phone, but when I went to actually load a custom ROM into it, I found that it couldn't read anything from my sdcard.
I'm having what appears to be a common problem: when I boot into Recovery, TWRP asks for a password. When I cannot provide it (because I have no idea what it is), TWRP is unable to access the data partition. Apparently, the partition is encrypted and I have no way to de-crypt it.
I've found dozens of other posts by users having this problem and the solution everyone is giving is to fully wipe the data partition and start over. But I *can't* wipe the data partition, because TWRP can't access it and fails almost immediately. I have tried a multitude of options, including:
* Installing old versions of TWRP - same behavior; asks for a password, fails to wipe/format the data partition.
* Installing ClockWork's recovery - same thing; fails to format/wipe the data partition
* Flashing back to stock recovery, using that to format my data partition; this worked fine but as soon as I put TWRP back, the problem came back.
On my last attempt, I used the stock recovery to completely wipe the data partition, and made absolutely sure that it never booted into anything but Download or Recovery modes after that. I was hoping that would prevent the stock software from ever re-encrypting the data, but somehow, when I booted TWRP, it still can't read my partitions. Note that my phone itself is not "encrypted" as far as the Settings application is concerned, but apparently Android is doing something behind the scenes anyway. There doesn't seem to be any option in the stock settings to turn off this encryption.
Is there any hope for getting a custom ROM onto this phone?
Thanks for the help!
Any solution? I'm running into the same issue where TWRP is asking for a password.
Hi @all
my TF101g sudenly got into bootloop at Eee logo. I can get into TWRP, get ADB connection to PC, tried everything I could find here in forum (PERI etc), but nothing helped.
At trying to format Data partition with ext2, I get an error. It seems that my Data partition is corrupted in such way that it can't be formated.
Any ideas what could I try?
Can I flash a stock ROM somehow?
I can flash from TWRP, but it does not seems to work. Tried KatKiss 4.4.36 (this one was installed at the moment of sudden bricking) and Android Revolution - none goes passt the Asus logo.
P.S. forgot to say how it happened - it rebooted at connecting it to the power source and after reboot got into loop.
Maybe you can go to twrp wipes, advanced wipe and than only click on data, than on the right "repair or change file system" I dont know why you wanna format to ext2? All my stuff is ext4, but I dont know if I changed it in the past.
TWRP wipes didn't help, and now it is too late to do anything. I tried to flash stock ROM, and I've lost TWRP. Now I have just the boot loop and no ADB, nothing.
weird, can you try to repair it in apx mode? (Volume Up & Power when the tablet is off). Maybe to flash stock rom again, or install twrp.
In 2013 i had the same problem in my tf101g, not did have solution here in xda, and not have. I tried solve the problem with myself. I not remember more. But, you will have to format your partition for ext4, then ext3, then ext2. In adb. Put in recovery, and go to pc. I not remember the codes. I will try to remember.
Hi mendez,
I found that solution too here in the forum, but it didn't work. I always got an error at formating, something about value too large.
I got a nexus 5 off of eBay, the seller said he had tried to root it and failed so I thought I would have a crack at it.
I thought it would be an easy restore but I ran into a few problems:
Phone originally came with 6.0.1 installed.
On android 5+ I could not access the standard recovery screen, and when I pressed power+volUp it just said formatting /data and would not move from that.
Rolled back to 4.4 and I got into the ususal recovery screen.
Tried to do a factory reset, but it again stuck at formatting /data.
I left it the entire night while I slept and it was still saying formatting /data. in the morning, nothing had changed.
Trying to boot the phone normally just left it on the 4 startup screen.
I've tried doing a full flash of stock android with each seperate part manually.
Also /data is unable to be mounted in any custom recovery, like it is corrupted or locked somehow.
With the stock recovery, it cannot be detected by adb, but in cwm it can.
EDIT: checking the /data folder in adb shell shows it's completely empty, and the same with system even after flashing and flashing again.
Can anyone advise me as to what might be the problem here?
Reflash all partitions manually, including userdata.img file. After flashing the last partition, boot directly into stock recovery and perform a factory wipe, then reboot.
Done that multiple times, I get the same result on stock android.
I don't want to root or anything like that right now, just get it back to a working state.
So you flashed the userdata.img file?
audit13 said:
So you flashed the userdata.img file?
Click to expand...
Click to collapse
yes multiple times
If you flashed userdata.img multiple times and the phone still can't perform a factory reset, the emmc chip may be damaged.
So, I made a big mistake.
I tried to encrypt my device, but it got stuck at 100%, so i rebooted it and now it's completely messed up.
When i boot it, it asks me for a password, when i enter it, it says decryption unsuccesful and my data is corrupt.
It gives me the option to reset the phone, which is fine, but it reboots the phone into recovery.
But i can't get into recovery, i can't read it properly but as far as i understand it fails to mount /data 5-ish times and then reboots again and tries to boot android again, bringing me to the password screen once again.
I don't care about data, i have backups, but i just want my phone working again.
TL : DR: phone boots, asks password, says data is corrupted, reset phone, goes into recovery, fails to mount partition, reboots, back to ask password.
If i have to do something in ADB let me know, i'm far from good with it but i can at least get it working...
Edit: RECOVERY WORKS! I got that one working again! Problem is that it still can't mount the /data partition so i can't seem to reset/wipe the phone properly.
Edit 2: Device is up and running again. I re-flashed the recovery via the bootloader and ADB, did a full wipe with the recovery because the re-flash fixed it and the wipe fixed the mount problem. After the /data partition could finally be mounted again i just flashed a ROM as usual with gapps and problem solved!
The microSD was broken too but after formatting that with a PC the phone could use it properly again. Did take a few tries tho, no idea why.