Hi
I have tried to install Liquid Smooth onto my HTC One X (UK) but now all i get is the HTC Logo screen. I followed all the instructions to the letter and realised I made a mistake. When I suppose to copy the Liquid Rom Zip to my phone storage I copied to my external HD instead. so when I when to install the zip file I found it wasn't there. When I rebooted my phone all I get now is the HTC logo screen.
I have tried fastbood erase cache - but that didn't work
I have tried doing a restore of my back up but did nothing.
I can still access the fastboot menu etc from the phone but i cannot access the internal storage to copy the zip file across for me to install it so it appears I have no operating system on my phone I might be wrong though.
Any help would be much appreciated.
Related
Hi all,
I bought a Proscan PTL7035-PL (preloaded with Android ICS 4.04) last Christmas. I rooted with a great success and have it running a full-fledged Google Play store. The only drawback is that all apps go to the internal sd which has only 2gb of storage space. I tried a couple of ways swapping the internal and external sds. None of them has worked. Then I followed one from http://forum.xda-developers.com/showthread.php?t=1991583. Basically by modifying the mount point of the internal flash and external sd as described in the file vold.fstab , the hope was to make the system use the big sd storage for apps and data storage etc.
Here is where my nightmare began. After reboot, my tablet stuck at the android logo and the booting never finished. I kind of know that my mounting points messed things up. The fix can be as easy as just restore the backup copy of vold.fstab which I have on the tablet. The problems are that:
1) There is no way to access the system folder of the android device now as the device itself cannot finish booting; and it can't communicate with a PC via USB.
2) Even if I can force it boot into the Android System Recovery 3e, it is not much a help as it needs a certified ROM or backup copy to recover. The official ROM is not out yet and I don't have a backup copy.
It looks like my device has been soft bricked. So how to pull it out?
Anyone ever solve this?
Android2013_ said:
Hi all,
I bought a Proscan PTL7035-PL (preloaded with Android ICS 4.04) last Christmas. I rooted with a great success and have it running a full-fledged Google Play store. The only drawback is that all apps go to the internal sd which has only 2gb of storage space. I tried a couple of ways swapping the internal and external sds. None of them has worked. Then I followed one from http://forum.xda-developers.com/showthread.php?t=1991583. Basically by modifying the mount point of the internal flash and external sd as described in the file vold.fstab , the hope was to make the system use the big sd storage for apps and data storage etc.
Here is where my nightmare began. After reboot, my tablet stuck at the android logo and the booting never finished. I kind of know that my mounting points messed things up. The fix can be as easy as just restore the backup copy of vold.fstab which I have on the tablet. The problems are that:
1) There is no way to access the system folder of the android device now as the device itself cannot finish booting; and it can't communicate with a PC via USB.
2) Even if I can force it boot into the Android System Recovery 3e, it is not much a help as it needs a certified ROM or backup copy to recover. The official ROM is not out yet and I don't have a backup copy.
It looks like my device has been soft bricked. So how to pull it out?
Click to expand...
Click to collapse
Long story short, similar issue. Has Rooted my 9 year olds Tablet, (Same as Op), and actually had it running great. Well, I was installing Gapps, via root explorer, and my Son was talking, and I forgot to Mount the System Folder that I was Replacing with the gapps one, R/W - it stayed R/O and never got replaced.
Thus the other 2 folders I changed to R/W are stuck that way. I think it was the entire Root Folder, and One more. I can elaborate.
Is there a way to fix this, as the tablet will not boot properly. (Hangs on Splash Screen), then if I attempt recovery, it gets stuck at the Android with the Red Triangle coming out of his belly, but no Menu Choices.
Anyone?
First off, I am no expert so please be gentle! I previously rooted my old Samsung Galaxy S i9000 and installed ICS, which went OK, but the phone became quite slow and unstable. I was advised to install RemICS and downloaded all the zip files from this forum, and put them on the external SD card. I followed the developer's instructions to the letter, as well as reading everything I could find on the subject. The reset and data wiping went fine, but the installation of the ROM didn't. It halted with an error message -`ROM incompatible, trying to use an invalid partition'. I repeat that this is supposed to be the specific ROM for the i9000. The phone now won't boot into recovery. It stops with an orange Android logo and the text `Powered by Mackay Kernel'. It won't boot into download mode either. The Mackay screen stays there however long I leave it. I really need help from the ROM developer but I can't post to that forum. How can I either boot into recovery or into download mode? Is this ROM reliable? What could I have done wrong?
More info:
Presumably everyone is on holiday! But just in case anyone is reading, there is further news. The reason I could not start recovery mode was that the button sequence was different from what I had been told. It now boots reliably into Mackay (which of course is TWRP). I have found that the phone is unable to mount the partitions DATA and SYSTEM - they seem to be corrupted. Hence it has not wiped DATA, although TWRP wrongly reports success. I have tried updating the partitions to ext3 or ext4 but this fails every time. I could format the thing from Windows but that will wipe everything including recovery of course. I need a tool to repair these partitions, but have not found anything so far. This may well have been the reason the phone was getting creaky in the first place.
I have copied a new ROM to the external SD card, using a card reader, and inserted this into the phone. Strangely the TWRP file manager reports that EXTERNAL SD is a sub-folder of SD CARD, and that is empty. The file manager does not show the real external SD card. But the real external SD shows up on the Windows USB connection. What is going on?
When I try to mount the partitions, DATA and SYSTEM can't be checked - the other partitions (Cache, sdcard, and emmc are all checked).
kingGrn Copeland
Well for the benefit of anyone else with the same problem, I have managed to re-flash the ROM back to stock. It just took 3 days of intensive web browsing until I understood how to do it, and found software that worked - a lot of stuff out there has errors.
To summarise, the problem was:
1. Data and System partitions became damaged, so phone became unstable.
2. Attempt to upgrade ROM failed because of damaged partitions.
3. Could not boot phone into recovery or download because button combination was different from what I was told.
The solution was:
4. Boot into download mode using correct button combination.
5. Re-flash back to stock ROM and re-partition using Odin.
Yes, someone did tell me that, and I would have done that straight away if I could have gotten into download mode. We live and learn
The solution was:
4. Boot into download mode using correct button combination.
5. Re-flash back to stock ROM and re-partition using Odin.
Click to expand...
Click to collapse
Thanks this wa useful for me too.
Hello everyone,
I had to factory reset my cinko slim android phone given that it didn't boot anymore (it was stuck at the opening logo). The recovery mode was the only thing available (I use a stock rom).
I had all my phone contacts stored in the internal memory so before doing that I made a backup to my sd card using the stock recovery (it made a 1gb .backup file in my sd card).
After wiping all the datas, I was able to use my phone without any problem but the recovery mode wasn't available anymore (the device gets stuck on the android logo when trying to access it).
So I tried to load the .backup file into another android device from its respective recovery mode but a message appeared reading ''checksum compare fails''.
Is there a way I can access all my datas from this .backup file and get back my phone contacts?
Thank you very much for your help
Solution?
Hi momomr,
exactly the same happened to me yesterday. Did you solve this problem somehow?
Thanks for answer
momomr said:
Hello everyone,
I had to factory reset my cinko slim android phone given that it didn't boot anymore (it was stuck at the opening logo). The recovery mode was the only thing available (I use a stock rom).
I had all my phone contacts stored in the internal memory so before doing that I made a backup to my sd card using the stock recovery (it made a 1gb .backup file in my sd card).
After wiping all the datas, I was able to use my phone without any problem but the recovery mode wasn't available anymore (the device gets stuck on the android logo when trying to access it).
So I tried to load the .backup file into another android device from its respective recovery mode but a message appeared reading ''checksum compare fails''.
Is there a way I can access all my datas from this .backup file and get back my phone contacts?
Thank you very much for your help
Click to expand...
Click to collapse
Hi guys,
I can't work out why but when I go to wipe all settings then install custom rom from zip file in cmw recovery, it completes normally but after the reboot it just stays on the android bot. I went back into recovery and managed the phone through usb to my PC & saw that in the phone storage there was nothing where there is obviously supposed to be boot files. I have installed this custom rom before & it has been no problem. I also have tried a few other roms (all that i've tried before & they all work) and the same thing happens. I have found one rom that worked strangley and when I manged the phone on my PC i saw that it has placed the boot files on the sd card (not the phone storage).
how can i fix this.
i am very new to rooting so please no complicated talk
can someone not help? this is a big issue.
ill try and explain the problem in more detail below...
i have been messing with my phone lately using CMW TOUCH to wipe my data then install rom from zip. everything was going great until now.
i want to install a rom (that i have installed before.so i know its compatible with my phone), i go through tge same procedure of wiping data then installing from zip.all goes the way it should with it telling me its installing from zip, after a while it tells me to reboot the phone. when i do all that happens is it stay on the green android bot for 1 min then reboots. i went into CMW TOUCH to connect phone to pc & found out that it installed nothing, nothing on the phone storage and on the sd card except the custom rom.
i have tried this with few other roms all with the same results.
NOW...
ive managed to find a rom that will install so it is functional all except recently after a reboot it has stopped detecting the sim，weird.
i connected the phone to my pc to find that all boot files are stored on the sd card not phone storage like it used to.
i had an idea that i will try later today and that is to move the custom rom over to the phone storage from the sd card. remove the sd card during install. maybe that will force the install to use the phone storage for the boot files
will let you know the outcome
jamos
i have just tried to install the rom with the sdcard removed from phone & the same thing happened. even though during the installation it tells me that it is formatting system then installing it installs nothing to the phone storage.
Hey guys, its been a long time since I've been on here asking questions, but I am completely stumped. I got an Irulu Victory 1S china phone. I achieved root, installed CWM. Problem was there was not enough storage space on main drive, as it was partitioned at 800mb for system apps and 5gigs internal SD storage. I found an app specifically for that phone manufacturer that partitioned the drive to 2.5 gigs. Flashed new Rom, Cyogen, now I am stuck in a boot loop. I can get into CWM no problem. But no matter what Rom I install, even after clearing delvik, cache, system, it just boot loops. I found from manufacturers website the original disk img files, but when using MTKtools it says disk size doesn't match file. I found a a blog that has a more detailed instructions on how to modify MBR and EBR1 using editors, but nothing on how to fix size issues. Any help is appreiated. I have win10 and Linux Mint systems if that helps any. Im assuming that there is a file or something I need to edit to get new roms to boot. I can do remote desktop sessions as well if needed. Im not computer dumb, but I know enough to get around windows and linux.
PS: I can only boot into recovery, when I ADB Shell it, it comes up as 123456789ABCDE RECOVERY as device. Cant seem to pull or push any files this way.
Update; Ok so I tried using EBR edit tool. Modified EBR to 2.5 gigs. Did a system, cache, and delvik wipe. Tried to install rom. Now it finds package, starts to open it, and then goes back to CWM main page. Tried several Roms with same results. It starts to install, but then flashes back to main recovery page. Now Im even more confused!