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?
Related
Recently I tried installing CM11 (jelly bean) on my Atrix 4g. It did not go through successfully as I was getting the symlinks error with code 7.
Prior to installing this ROM, I had taken two backups, unfortunately both on the Internal SD drive.
When I try to restore using Android Recovery, I get an error in recovering system - after some time. However, at the end of the restore I am able to boot the phone and am able to make and receive calls. I can't seem to get the WiFi to work anymore. The system shows that I am on
System Version 4.5.141.MB860.ATT.en.US
Android version is 2.3.6
I suspect that the internal SD card does not have enough space to restore completely, thus causing these issues. Is there a way to delete an extra backup? I am not able to connect the phone to USB and get to the SD card. The phone says that the SD card is not there, however, Android Recovery is showing me the two backups. However, Android Recovery is not giving me an option to delete the extra backup to create space.
Please let me know my options.
Thanks
Please help
dindoliya said:
Recently I tried installing CM11 (jelly bean) on my Atrix 4g. It did not go through successfully as I was getting the symlinks error with code 7.
Prior to installing this ROM, I had taken two backups, unfortunately both on the Internal SD drive.
When I try to restore using Android Recovery, I get an error in recovering system - after some time. However, at the end of the restore I am able to boot the phone and am able to make and receive calls. I can't seem to get the WiFi to work anymore. The system shows that I am on
System Version 4.5.141.MB860.ATT.en.US
Android version is 2.3.6
I suspect that the internal SD card does not have enough space to restore completely, thus causing these issues. Is there a way to delete an extra backup? I am not able to connect the phone to USB and get to the SD card. The phone says that the SD card is not there, however, Android Recovery is showing me the two backups. However, Android Recovery is not giving me an option to delete the extra backup to create space.
Please let me know my options.
Thanks
Click to expand...
Click to collapse
Can someone please guide me? All I want is to install any stable ROM on my Atrix 4g. But described above, I am having issues in flashing.
Okay, this is quite a long story, so I apologise in advance.
I decided to update my Galaxy S2 today to a newer ROM (SuperNexus 2) with the latest version of Android. I was coming from a CM9 build. I went through the usual process of backing up data and performing a full NANDROID backup via CWM Recovery, booted the phone again and transferred the backups to my PC via USB. These files transferred fine.
I then downloaded the zip files for the new ROM and proceeded to copy them to the internal storage of my phone. The copy dialog in Windows said that it was "discovering items" and stayed like this until I turned off USB transfer mode on the phone and removed it (ie. the files failed to copy) This happened a number of times and I didn't get anywhere. I have plenty of space free on the SD card, but just to make sure I started the phone in CWM again and formatted the SD card, and since I was going to do it anyway, the data and cache partitions too. When I booted the phone again, the files still wouldn't copy. I managed to copy a text file to the phone which was about 32kb but anything larger just seemed to fail.
I then went back into CWM and decided to partition the SD card, as I thought that it may have been corrupted somehow and needed to rebuild the filesystem. This however, caused even more problems as trying to format the SD card (In CWM) now just reported "Error, can not mount E:/sdcard".
Feeling fairly frustrated, I decided to download the Stock ICS ROM for the Galaxy S2 and install it via Odin, thinking that the problem was probably with CWM. The install went fine, but upon reboot the phone just stayed on the boot animation, no matter how long I left it. To make sure the install went smoothly I decided to try and reinstall the Stock ROM via Odin again, but now Odin didnt seem to get past the "Initializing.." stage.
So all in all, I now have a phone which wont boot into Android, cant copy anything to internal storage, and Odin wont seem to connect to.
I am convinced this is a software issue and therefore fixable. But maybe the internal storage was not working correctly in the first place. I have installed many ROMs before and never had such issues.
Anyone know anything about this or how I could potentially fix it? Thanks so much in advance!
Benji1992 said:
Okay, this is quite a long story, so I apologise in advance.
I decided to update my Galaxy S2 today to a newer ROM (SuperNexus 2) with the latest version of Android. I was coming from a CM9 build. I went through the usual process of backing up data and performing a full NANDROID backup via CWM Recovery, booted the phone again and transferred the backups to my PC via USB. These files transferred fine.
I then downloaded the zip files for the new ROM and proceeded to copy them to the internal storage of my phone. The copy dialog in Windows said that it was "discovering items" and stayed like this until I turned off USB transfer mode on the phone and removed it (ie. the files failed to copy) This happened a number of times and I didn't get anywhere. I have plenty of space free on the SD card, but just to make sure I started the phone in CWM again and formatted the SD card, and since I was going to do it anyway, the data and cache partitions too. When I booted the phone again, the files still wouldn't copy. I managed to copy a text file to the phone which was about 32kb but anything larger just seemed to fail.
I then went back into CWM and decided to partition the SD card, as I thought that it may have been corrupted somehow and needed to rebuild the filesystem. This however, caused even more problems as trying to format the SD card (In CWM) now just reported "Error, can not mount E:/sdcard".
Feeling fairly frustrated, I decided to download the Stock ICS ROM for the Galaxy S2 and install it via Odin, thinking that the problem was probably with CWM. The install went fine, but upon reboot the phone just stayed on the boot animation, no matter how long I left it. To make sure the install went smoothly I decided to try and reinstall the Stock ROM via Odin again, but now Odin didnt seem to get past the "Initializing.." stage.
So all in all, I now have a phone which wont boot into Android, cant copy anything to internal storage, and Odin wont seem to connect to.
I am convinced this is a software issue and therefore fixable. But maybe the internal storage was not working correctly in the first place. I have installed many ROMs before and never had such issues.
Anyone know anything about this or how I could potentially fix it? Thanks so much in advance!
Click to expand...
Click to collapse
I9100?
Can get to DL mode?
Can get to recovery?
Get an older Odin version and flash siyah just to see if it can be flashed again.
If you can get to recovery, Nuke Script is the way to go.
It sounds to me that maybe your memory is corrupt...
Not just yet, smells like soft brick.
Sent from the little guy
Hello guys,
I was using DorimanX v 119 10 series along with Slim Saber 08/24 release, then yesterday when the battery was around 18% it turned off randomly.
When I turned it on, I saw I was not getting options for Dual Boot and it took me straight to Primary ROM where it showed a message Internal Memory Damaged, format it on the notification bar.
Tried opening Titanium Backup and other apps to backup but SDCARD0(internal storage) was not mounted anywhere.
Restarted the phone and now its getting stuck on DorimanX logo.
Tried mounting from recovery and doesn't seem to work..
Is there anyway possible to recover my data? There are lots of information and photos that I need in that internal memory
Any help would be appreciated.
Thank you.
had that happen to me more than once on kitkat.
are you able to mount usb in recovery?
tried this?: http://forum.xda-developers.com/showthread.php?t=1646108
i went back to my jellybean backup and copied everything over to my computer.
I would be interested to hear how you are doing on this?
I recently had a crash on my S2 with the same version of DorimanX.
Had you repartitioned?
Thanks for your input guys.
@rgomia, the internal memory still shows corrupted and not able to read from it even from Aroma file manager
Actually I tried flashing slimsaber again and I could boot but still the internal memorys not readable from any file manager. Looks like I'll have to repartition it.
Was looking to somehow recover those lost data, but doesn't look like there's a chance
Reformatting worked and everything back to normal, Since I'm gonna get Redmi 1S anyway, I'll stay on slim kernal and use this as a backup phone. 5 years of important data and photos lost in the process :/
If your phone is bootable you should just mount it on your PC and run a file recovery program.
Your pictures are usually stored on your primary SD card.
Hi there,
First of all, I know that part of this mess was my fault. I had been using CM 10.1 on my Galaxy S2 for quite a while (since 2013, IIRC), but yesterday I decided to upgrade it to CM 12.1. The "CM Updater" app was not working so I decided to just download the .zip file, reboot into recovery mode and flash things from there. I managed to enter the recovery mode, but when I tried to flash the new CM I noticed I couldn't see the .zip file on my internal SDCard... Hmm, this was because my phone was encrypted (including my internal SDCard, of course). So I went back to my browser and did more research. I found a guy saying that, if your phone was encrypted, you could flash your device using the sideload mechanism *or* an external SDCard. Since I have an external SDCard, I chose this option.
Well, it doesn't much to figure out that things went bad. The main partition was overwritten during the installation and I've lost all encryption. However, that's not the worst part: I've also lost access to my internal SDCard! Now I cannot even make Android ask for its password. I really don't know what to do here. I've lost access to photos and videos from years ago. If I am correct, the upgrade process *did not* touch the internal SDCard at all; so my data is still there. Am I right? Do you guys think it's still possible to access it? I spent several hours trying to figure this out without success, so I decided to post my question here before I give up and reformat the internal SDCard.
Thank you in advance!
I am curious, how you manged to encrypt sdcard0 at all.
Never figured out how to do this on CM.
Nevertheless, I guess, Terminal/ADB might be the only option to decrypt and mount that partition. Unfortunately I don't know the commands on Android (on Linux it's cryptsetup).
Ok guys so i was faffing about with my tablet installing apps in the systsem directory (its rooted) so when i reset to factory they would still be there... all was good untill i installed to many and i got a message saying insuffient memory, and tablet, froze when rebooting its stuck on tab 4 loading screen..
i have an external memory and android recovery to work with as no pc recognizes this tablet, never have.
Things ive tried:
Wiping cache
resetting to factory
restarting tablet
installing a new rom
Tab 4 7.0 (kitkat)
What i think needs to be done... just not sure how to do it:
removing apps out the system directory or setting to default but im not sure how to do this with only android recovery that lets me update from external memory card?
£10 to who ever helps me solve this..
TWRP file manager .. you can remove files to gain space