So I was playing Family Fued last night on my phone and pressed the home button. After doing so, my phone screen turned black and became unresponsive so I held the power button and rebooted. Upon booting the phone got stuck on the boot animation.
So I tried dirty flashing my ROM, gapps, and kernel. The phone booted then got stuck on the Starting Apps toast with a continuous progress wheel. I tried a combination of wiping caches and dirty flashing to no avail. I was running francos kernel with -75 UV, but flashed a kernel without UV to be sure. I'm still unable to get past the starting apps toast when I restore to the backup I made.
I just want to get it to boot so I can retrieve some important text messages. Any help is appreciated. Thanks in advance.
Sent from my Nexus 4 using xda premium
If you're getting as far as the starting apps dialog, you should be able to get a logcat of the boot process, which will go a long way in diagnosing the problem, and if it is recoverable.
I'm thinking either a framework file got corrupted, or even more likely, your data partition is corrupted and upon bootup, dalvik can't write to /data/dalvik-cache while attempting to "optimize" apps, and it therefore hangs.
This is all just conjecture of course, and I could be completely wrong, but a log will surely help.
JsChiSurf said:
If you're getting as far as the starting apps dialog, you should be able to get a logcat of the boot process, which will go a long way in diagnosing the problem, and if it is recoverable.
I'm thinking either a framework file got corrupted, or even more likely, your data partition is corrupted and upon bootup, dalvik can't write to /data/dalvik-cache while attempting to "optimize" apps, and it therefore hangs.
This is all just conjecture of course, and I could be completely wrong, but a log will surely help.
Click to expand...
Click to collapse
How would I pull the log cat? Also, is there a way I could salvage corrupted data?
Sent from my Nexus 4 using xda premium
nbeebe24 said:
How would I pull the log cat? Also, is there a way I could salvage corrupted data?
Click to expand...
Click to collapse
You need to stream the output of logcat via (assuming windows) your command prompt console using adb:
adb logcat > log.txt
Then upload the log.txt file for review. That's the best place to start and see what it says.
JsChiSurf said:
You need to stream the output of logcat via (assuming windows) your command prompt console using adb:
adb logcat > log.txt
Then upload the log.txt file for review. That's the best place to start and see what it says.
Click to expand...
Click to collapse
Okay I'll pull the log when I get home. Are you able to read those?
Sent from my Nexus 4 using xda premium
I've read a logcat or two in my day
Sent from my Nexus 4 using xda app-developers app
JsChiSurf said:
I've read a logcat or two in my day
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Do I have to wait until the cursor in the command prompt stops blinking to give you the log?
nbeebe24 said:
So I was playing Family Fued last night on my phone and pressed the home button. After doing so, my phone screen turned black and became unresponsive so I held the power button and rebooted. Upon booting the phone got stuck on the boot animation.
So I tried dirty flashing my ROM, gapps, and kernel. The phone booted then got stuck on the Starting Apps toast with a continuous progress wheel. I tried a combination of wiping caches and dirty flashing to no avail. I was running francos kernel with -75 UV, but flashed a kernel without UV to be sure. I'm still unable to get past the starting apps toast when I restore to the backup I made.
I just want to get it to boot so I can retrieve some important text messages. Any help is appreciated. Thanks in advance.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
The last time I was stuck in Starting APps, I did a factory data reset in Recovery Mode, and it worked.
Here's what I got so far http://pastebin.com/pf3b5gc8
opticaldh said:
The last time I was stuck in Starting APps, I did a factory data reset in Recovery Mode, and it worked.
Click to expand...
Click to collapse
That defeats the purpose of trying to recover my text messages. It boots fine from other back ups and fresh installs but not from the particular backup I started a thread about.
Sent from my Nexus 4 using xda premium
Titanium backup pro allows you to restore text message from android backups.
Not sure if the free version does it but I did find two other apps that are free that you can try.
1)app extractor (found on google play)
2) nand manager http://forum.xda-developers.com/showthread.php?p=35367320#post35367320
Sent from my Nexus 4 using xda app-developers app
Titanium or any other app, at this point, won't do any good at this point since the phone won't boot up all the way
The logs definitely show things look pretty FUBAR'ed. Though not optimistic, the first thing I'd try is to reboot to recovery and click 'fix permissions' via the 'Advanced' tab (assuming TWRP), and see if that does anything.
If that doesn't help any, and you don't care about trying to continue down the path of getting the ROM to boot, and all you do care about (mostly) is saving your text messages, assuming they are still there, what I would do is, from recovery, adb pull the data folder where the mms/sms/call log database is stored, do a full wipe, install a fresh rom, and then after first boot, reboot back to recovery and restore the data you pulled (this is all titanium is doing anyway).
You could even make a nandroid of your current bad setup if the above didn't work for some reason.
To get the current data for mms/sms/calls, first, reboot to recovery:
Code:
adb reboot recovery
Via your command prompt, make a directory in the same folder from where you are running adb, and then change into it, as follows:
Code:
mkdir com.android.providers.telephony
cd com.android.providers.telephony
Then, while still in recovery mode, pull your data:
Code:
adb pull /data/data/com.android.providers.telephony .
After you've successfully pulled your data, wipe the phone completely, install your new ROM, gapps, etc, and let it boot up completely, then reboot back to recovery again. Once back up in recovery, push the data back to the phone.
(make sure you are still inside the 'com.android.providers.telephony' directory you created via your command prompt)
Code:
adb push . /data/data/com.android.providers.telephony
That should restore you previous database, cache, etc.
Reboot the phone and cross your fingers
That's what I was essentially suggesting, but I didn't know how to manually do it.
From his current ROM that works he could use tb or the other two apps to restore just his SMS from his nandroid backup
Sent from my Nexus 4 using xda app-developers app
marsdta said:
That's what I was essentially suggesting, but I didn't know how to manually do it.
From his current ROM that works he could use tb or the other two apps to restore just his SMS from his nandroid backup
Click to expand...
Click to collapse
Problem is, he doesn't have a current ROM that works.
But, he could first wipe and install a fresh ROM all together, and then install Titanium, and use it to restore the above referenced data from a Nandroid.
Though, he'd FIRST have to/want to Nandroid the current bad ROM in order to make sure the nandroid has the most current data, else any new text messages would be lost since the previous nanadroid.
After doing all of that, it'd be much simpler/quicker to just follow the instructions provided above
All of this, of course, is based on bailing on the current ROM, but for the sake of challenge, I'd love to try and get it going as well, based on making changes and following the impact via logcat.
Well I feel dumb. I mixed up a couple threads that were talking about the same thing. Only in the other they did have a nandroid.
I should not be responding when I'm half asleep.
Edit - maybe I didn't mix up but its now I've only been up maybe for a bit. Had to drive brother to school. But reread his op and this caught my eye " I'm still unable to get past the starting apps toast when I restore to the backup I made."
So he does have a current nandroid of the bad ROM?
Sent from my Nexus 4 using xda app-developers app
marsdta said:
Well I feel dumb. I mixed up a couple threads that were talking about the same thing. Only in the other they did have a nandroid.
I should not be responding when I'm half asleep.
Click to expand...
Click to collapse
No worries, the concept / principle is still sound We're all here to help!
JsChiSurf said:
No worries, the concept / principle is still sound We're all here to help!
Click to expand...
Click to collapse
Now I'm getting "Error while restoring /system" when I try to restore my derped backup
nbeebe24 said:
Now I'm getting "Error while restoring /system" when I try to restore my derped backup
Click to expand...
Click to collapse
Why are you trying to restore your derped backup? Did you already wipe and update to a fresh ROM?
JsChiSurf said:
Why are you trying to restore your derped backup? Did you already wipe and update to a fresh ROM?
Click to expand...
Click to collapse
Yes, I'm already running a fresh install. I'm a little confused by your instructions above. Which setup am I pulling the telephony data from? The bad nandroid?
Sent from my Nexus 4 using xda premium
nbeebe24 said:
Yes, I'm already running a fresh install. I'm a little confused by your instructions above. Which setup am I pulling the telephony data from? The bad nandroid?
Click to expand...
Click to collapse
Last I read, you never got past the starting apps dialog, so all of my instructions are based on the fact that that's where you're at.
If you've already make a nandroid of the bad version and are up and running on a new ROM, this process changes.
In this case, what I would do is pull the the data partition nandroid file (in your TWRP/BACKUPS folder), "data.ext4.win", off of your sdcard, add the ".tar" extension (this is all these files are):
data.ext4.win.tar
Then open the above file with WinRAR, navigate to the same /data/data/com.android.providers.telephony/ folder referenced in my previous instructions and pull the content out of the .tar.
Then, go into recovery and use adb to push the contents of the "/data/data/com.android.providers.telephony" that you extracted from the .tar file and push back to your phone.
Or, if you use titanium, as mentioned above, you could try and extract it right out of the nandroid file directly while the new ROM is running.
Related
Now that i've finally managed to root my SNS, what should i do now? :O
(What are some good roms, etc)
Look at all of the choices available and find the rom you like the most.
I'd personally recommend,
Lightweight and speed: oxygen
Cm7 is another cool rom
Miui is good as well.
Kernel: netarchys 1.3.7 with proton voltage condolences to undervolt and use voodoo functionality
Sent from my Transformer TF101 using XDA Premium App
I'm a bit confused as to what I installed while I was rooting.
I installed Clockwork 3.0.2.4 but what exactly is this?
isinisterx said:
I'm a bit confused as to what I installed while I was rooting.
I installed Clockwork 3.0.2.4 but what exactly is this?
Click to expand...
Click to collapse
It allows you to flash custom Roms and perform backups (restore your phone to a given point in time)
Sent from my Transformer TF101 using XDA Premium App
OK, now before I rooted my phone I backed up my entire phone (copy and paste to desktop), but I still lost all my apps in the app store? any way of getting these back?
isinisterx said:
OK, now before I rooted my phone I backed up my entire phone (copy and paste to desktop), but I still lost all my apps in the app store? any way of getting these back?
Click to expand...
Click to collapse
Yes, but you'd have had enabled back up to your Google account before you rooted and have to enable it on the rooted phone again, then the market will try to restore all apps.
If you didn't you got to do it manually (recommend doing it via webside market for easier accessing old apps), then get Titanium Backup and save all your apps.
isinisterx said:
OK, now before I rooted my phone I backed up my entire phone (copy and paste to desktop), but I still lost all my apps in the app store? any way of getting these back?
Click to expand...
Click to collapse
No. Redownload them and back it up using a backup apply. I'd recommend tianjin backup pro. It costs $6 but its worth it. It backs up ur apps/games and data along with it.
Every rom flash involving a factory reset will wipe your apps. With titanium backup pro, you can one click restore everything
Sent from my Transformer TF101 using XDA Premium App
Ok,
Final question is that how do i go about installing the rom? I downloaded it and transferred it to the memory card.
I go into fastboot and into recovery.
Then.?
isinisterx said:
Ok,
Final question is that how do i go about installing the rom? I downloaded it and transferred it to the memory card.
I go into fastboot and into recovery.
Then.?
Click to expand...
Click to collapse
1. Download the ROM
2. mount the phone's USB
3. put it on the root of the /sdcard/ while mounted
4. unmount
5. go into recovery
6. wipe factory settings, data cache, dalvk cache (advanced)
P.S. i'd recommend getting clockwork 4.0.0.2 from the dev forums, its a lot better. better organization on wipes
7. flash the ROM (if you're flashing CM7, you have to flash Gapps afterwards) [flash zip from sdcard]
this flash applies to any flashable zips including kernels/roms/radios... DO NOT FLASH BOOT ANIMATIONS. you put them in /system/media/ if you choose to do so
8. reboot
how do u install teh clockwork 4.0.0.2?
isinisterx said:
how do u install teh clockwork 4.0.0.2?
Click to expand...
Click to collapse
if you can please, hit the "thanks" button for all of my posts otherwise i wont help anymore because ive been posting on a timely fashion and I think I deserve something for my help.
http://forum.xda-developers.com/showthread.php?t=988686
download respective to your phone model
put it in /sdk/tools (you need adb environment setup)
go into bootloader mode
type "fastboot flash 4002-orange.img" or whatever color you downloaded.
zephiK said:
if you can please, hit the "thanks" button for all of my posts otherwise i wont help anymore because ive been posting on a timely fashion and I think I deserve something for my help.
http://forum.xda-developers.com/showthread.php?t=988686
download respective to your phone model
put it in /sdk/tools (you need adb environment setup)
go into bootloader mode
type "fastboot flash 4002-orange.img" or whatever color you downloaded.
Click to expand...
Click to collapse
Kk I thank'd all your posts.
Do I have to install the htc sync?
isinisterx said:
Kk I thank'd all your posts.
Do I have to install the htc sync?
Click to expand...
Click to collapse
No? Not sure where you get "HTC Sync" from. This is a Samsung phone, not a HTC one.
Finally, i have solved it !!! A couple of days ago, i forgot my pattern and clicked on forgot pattern, but i didn't get a prompt to turn on wifi. So basically, i was stuck, unless i wanted to do a factory reset and lose all of my data. Here's my unique solution to this problem, :
First of all, you need to be rooted and to have usb debugging ON. Otherwise, it won't work.
Second, you need to install wug's nexus toolkit, because it gives you an option to boot with a modified boot.img which has root privileges, go to advanced, you'll see it (if you know of any other way to boot up such an image, use it, because when you get locked out with the ,,forgot pattern'', your root won't work, that's why you need this boot image).
Here's what i did:
First, i booted the modified boot image and by using either adb or the toolkit, i pulled /data/data and /data/app to my pc.
Second, I made a full wipe and set up my N7 as usual. At this point, you need a good root file explorer in order to get to the /data folder. I installed colornote (from the app backup i made, because i wan't sure that there was a new version and,if there was, it could be a possible failure, because i wasn't sure how it would behave with the last version's data) and rebooted (in order for colornote to get into the dalvik cache).
Third, i opened up colornote's folder in /data/data and just replaced the databases folder with the one from my backup and i went to /data/dalvik-cache and deleted the corresponding color note dalvik file. Afterwards, i just rebooted and voila, all my stuff that i had written in color note was staring at me.
Now, i want to mention that i've only tried this with colornote (as it was my foremost priority to get to the essays that were stored there) and i've tried this on only 4.1.2. I can't guarantee that it will work on other apps or that you won't get damage to your precious Nexus 7, so please, proceed with caution, and don't blame me if something unexpected comes up. Good luck !!!
P.S. If you get more than one device or emulator, it's because you have bluestacks, disable or uninstall it, and you're good to go !!!
Did you try any of the suggestions offered to you in the other thread you started on this topic?
They seem like way less effort and some of them don't involve any wiping.
BTW when you do an adb pull you lose all file ownership and mode information; it is important to restore those correctly.
iAndroidOS said:
Second, you need to install wug's nexus toolkit, because it gives you an option to boot with a modified boot.img which has root privileges, go to advanced, you'll see it (if you know of any other way to boot up such an image, use it, because when you get locked out with the ,,forgot pattern'', your root won't work, that's why you need this boot image).
Click to expand...
Click to collapse
You can do whatever you want with the custom recovery - it is unaffected by the lock condition. You are complicating things by using a toolkit.
good luck
If you have USB debugging enabled you can just use adb to delete the pattern file and then unlock the tab.
Sent from my GT-I9000 using xda premium
NIMBAH said:
If you have USB debugging enabled you can just use adb to delete the pattern file and then unlock the tab.
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
I tried that and it didn't work
bftb0 said:
Did you try any of the suggestions offered to you in the other thread you started on this topic?
They seem like way less effort and some of them don't involve any wiping.
BTW when you do an adb pull you lose all file ownership and mode information; it is important to restore those correctly.
You can do whatever you want with the custom recovery - it is unaffected by the lock condition. You are complicating things by using a toolkit.
good luck
Click to expand...
Click to collapse
Thank you for reminding me, it is imperative to restore the permissions
iAndroidOS said:
I tried that and it didn't work
Click to expand...
Click to collapse
Weird I've done it a few times and its always worked. How did you do it ?
Sent from my GT-I9000 using xda premium
NIMBAH said:
Weird I've done it a few times and its always worked. How did you do it ?
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
I dunno, i went into adb and used the adb shell rm /data/system/gesture.key
command and as soon as it finished, i unplugged my N7 and rebooted it, and the login prompt was still there.
Anyone having trouble making nandroid backups using clockworkmod? I'm using the latest version of clockworkmod touch and stock 4.4. I run the backup, it appears to run fine, says it's finished, but when I reboot there is no backup files. This has happened multiple times, including getting burnt by modifying a system file and then finding out my backup is non-existent. I'm used to TWRP, but someone told me it doesn't work with 4.4 so I switched.
Sent from my Nexus 10 using xda app-developers app
gc84245 said:
Anyone having trouble making nandroid backups using clockworkmod? I'm using the latest version of clockworkmod touch and stock 4.4. I run the backup, it appears to run fine, says it's finished, but when I reboot there is no backup files. This has happened multiple times, including getting burnt by modifying a system file and then finding out my backup is non-existent. I'm used to TWRP, but someone told me it doesn't work with 4.4 so I switched.
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
Maybe you are looking into the wrong directory.. mine is located at Device\Data\Media\Clockworkmod\Backup.
Hope that helps!
mfaisal98 said:
Maybe you are looking into the wrong directory.. mine is located at Device\Data\Media\Clockworkmod\Backup.
Hope that helps!
Click to expand...
Click to collapse
That was it, thanks!
I guess I'm used to TWRP where it is saved under /sdcard/TWRP, plus I was thrown off by the clockworkmod folder at /sdcard/clockworkmod
I just wasted a couple hours setting everything up because I couldn't find the backup
Background
- I'm using PAC 4.2.2 ever since I bought my Nexus 4 and was quite happy with the ROM until yesterday
- I started losing out the GSM signal for the past 2 weeks, it would intermittently go off and then come back by itself after a few seconds, at times few minutes (never thought it could be a ROM issue, is it?)
- Google started pushing its update and I had to manually stop data for Google Services from Settings -> Data Usage
Problem
Yesterday while updating Angry Birds from the Play Store the Play store crashed. I tried to open it but it would continue to crash as soon as it would try to load it.
I rebooted the device however since then its stuck on the google logo and doesn't proceed.
I have TWRP recovery installed and when it boots in to (Fastboot is it called?) it shows Secure Boot - enabled and Lock State - unlocked.
Few foolish things that I tried yesterday (in desperation) that might have already screwed up my phone beyond recovery....
1. Wiped Cache and Dalvik Cache and tried to reboot but it didn't work
2. Flashed the new PAC 4.2.3 version that I had downloaded way back but still no success
3. Tried to take a backup from TWRP recovery however while restoring it fails and shows the message 'Restore Failed'
I really wish to recover the media that is in the phone and contacts if possible.
I have Google Nexus 4 Toolkit (not sure of the version but its like 8-10 months old) installed in my laptop and if I connect the phone and start the toolkit it recognizes the phone against adb (shows a serial number) but when I try to back it up it stops at 'Waiting for adb mode...'
I'm a total noob when it comes to recovery etc. so would really appreciate any help that leads to data recovery in my phone somehow, thanks!
Internal memory is accessible through ADB over recovery so you could easily get your data if it is still there. About the contacts - if they are Google contacts and saved to your gmail - happy days, nothing to worry about. But if they are phone contacts I don't think you'll be able to restore them.
Do you know what is the worst thing about smart phones? That the owner should be smarter than the device in order to operate it.
Sent from my Nexus 4 using xda app-developers app
evdrmr said:
Internal memory is accessible through ADB over recovery so you could easily get your data if it is still there.
Click to expand...
Click to collapse
What would be the steps that I'd have to follow for this? I have TWRP recovery installed.
EDIT: I even tried a complete wipe but it doesn't work. Also tried using CWM as recovery, that didn't work either. Installed the Unified_Android_ToolKit (latest version), updated all USB/adb drivers but whenever I try to backup anything through the toolkit all I get is that it is waiting for the adb mode or its waiting for the USB debugging to be enabled (which I can't since I can't get the phone to boot up).
Any ideas?
Don't try to restore any data after full wipe. It won't work. Flash factory images to get your device into operable state again but before that go to Device Manager and make sure that the phone is recognized by the computer and the drivers for it are properly installed. Good luck. Can you still access twrp recovery?
Sent from my Nexus 4 using xda app-developers app
evdrmr said:
Don't try to restore any data after full wipe. It won't work. Flash factory images to get your device into operable state again but before that go to Device Manager and make sure that the phone is recognized by the computer and the drivers for it are properly installed. Good luck. Can you still access twrp recovery?
Click to expand...
Click to collapse
After having given up all hope to retrieve any data or contacts I wiped the entire phone, format data I mean. However, with that I've ended up with no OS on the phone, I can access TWRP though. Not sure how badly I've ended up screwing the phone. :silly:
Not badly at all... Reboot your phone into Boot loader mode. Download the Google factory images of your choice and run the flash-all.bat file. Enjoy your fully restored phone in a couple of minutes.
Sent from my Nexus 4 using xda app-developers app
evdrmr said:
Not badly at all... Reboot your phone into Boot loader mode. Download the Google factory images of your choice and run the flash-all.bat file. Enjoy your fully restored phone in a couple of minutes.
Click to expand...
Click to collapse
How exactly do I run the flash-all.bat file? I tried flashing the factory image using the Unified Toolkit however there comes an error message stating that there is some issue in the program and it has to close. This happens somewhere midway when it starts flashing system.img and recovery.img
EDIT: I can't get in to recovery mode any more and neither can I flash any recovery
EDIT2: Don't ask me what I did, somehow managed to get the phone running in the 4.2.2 version of stock factory image. 4.4 wasn't working for some reason. Setting it up for use now.
Question: Can I simply download 4.4 factory image and install it on my Nexus 4 which came with 4.2.2. when I bought it?
Simply: Yes
Sent from my Nexus 4 using xda app-developers app
evdrmr said:
Simply: Yes
Click to expand...
Click to collapse
Even when I wasn't able to follow any of the instructions you provided (my bad though) I would like to thank you for just posting on the thread man! :good:
BTW a good news that I'd want to share is that my contacts were backed up I lost on the media but its fine I think, probably a good lesson for future.
I'm updating to 4.3 from system update as of now, will use it as it is for time being and move on to 4.4 sometime later maybe. Not sure whether 4.4 will be available for update OTA once I move to 4.3 but I'm happy with whatever's left of the phone for now...thanks again!
I installed the HORSEMAGEDDON ROM and it worked - for the most part. But it kept giving me annoying errors about different apps that were attempting to update every time I turned it on. So I tried to restore my backup that I had made with CWM 6.0.2.8. However the backup apparently did not restore properly because it now boot loops back into CWM any time I try to start it. I get the errors:
E:Can't open cache/recovery/log
E:Can't open cache/recovery/log
E:Can't open cache/recovery/last_log
E:Can't open cache/recovery/last_log
So I tried to reflash HORSEMAGEDDON but it still loops back into the CWM recovery screen.
I have wiped everything according to the instructions on the HORSEMAGEDDON thread.
HELP!! This happened to me on another U8800-51 phone and I wound up hard bricking it trying to get back to stock.
Anybody???
Does anybody have any ideas on how I can fix this?
Did you wipe cache/dalvik cache?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
iheartsamsung said:
Did you wipe cache/dalvik cache?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Yes. I did a wipe of data and factory reset as well.
What I would do is get an SD card with a custom rom on it and try installing it from recovery menu
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Obviously you have been having problems with that rom, so go with something different.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
iheartsamsung said:
Obviously you have been having problems with that rom, so go with something different.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Okay. Here is what I did step by step:
1. I was on Stock 2.2.2 Froyo and flashed HORSEMAGEDDON successfully. But I had some errors related to updates since it was such an old ROM the updates were all for much newer versions of the apps tied to 4.x.x.
2. I attempted to restore my backup made with CWM 6 to return to the stock. It said it completed successfully but when I rebooted it just looped into the recovery screen with the error messages posted in my first post.
3. So I tried to reflash HORSEMAGEDDON and it said it completed successfully. But it still bootloops into recovery.
4. I can access most of the features of the recovery. I can access the pink screen and swap recovery versions. I can access my SD card from my PC when I mount it from recovery.
5. Yes, I did do full wipes with each attempt to reflash.
The ROM was not the problem. It worked and worked well other than update issues for apps. It was only after attempting to restore to stock I ran into issues.
The problem appears to be something was corrupted when I tried to restore my backup, even though it said it completed successfully.
So if I try to flash yet another custom ROM, even if I could find one I trust given all of the version issues etc., I don't think it would act any differently. But if somebody can recommend one I am all ears. Keep in mind I have a -51 phone so it will have to be for that or the PRO.
Given that, how can I get back to stock? Am I the only person who has ever had this problem? I don't believe that is the case, so somebody must know how to fix it or can point me to a procedure to repair the internal memory.
Help!!
I'm new at xda so it's not letting me post an external link. Google "bootlooping" and the first one in list is from xda, just follow the instructions
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Thanks but.....
iheartsamsung said:
I'm new at xda so it's not letting me post an external link. Google "bootlooping" and the first one in list is from xda, just follow the instructions
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
None of the fixes on this link seem to apply to my situation.
When I said "bootloop" I may have misused the term. What happens is I power up, it goes to logo screen for about 10 seconds, shuts down and restarts to logo screen then goes into recovery after about 5 seconds. From other info that I have found it is due to a corrupt bootloader and I need to reflash the bootloader. Problem is, reflashing the bootloader i.e. CWM, does no good at all.
I am also hampered by lack of info specific to the -51 model. And I cannot find a copy of the stock ROM anywhere that is for the -51.
So essentially I am screwed. All of that said, I have found a new phone for $40.00 so all is not lost. It's a U8800 but not the -51 or PRO. I don't plan on customizing it, I'll just stick with stock. After trashing two phones even after following the advice to "BACKUP" I think enough is enough. Backing up did me no good whatsoever in both cases.
In my estimation, the culprit is CWM, or at least the versions I used.
If anybody has any advice I'm all ears.