Database Users

HELP!?!?!

I have an epic that has the one click root. It has been working great but today i downloaded this new app called SGS battery icon mod2 and after i selected a layout, it restarted and then it just stayed at the startup screen thats black and white letters. says "samsung www .samsungmobile .com" and i cant turn off the phone unless i pull the battery.

Were you running a custom rom?
Sent from my SPH-D700 using XDA App

Time for an odin restore or three finger boot into clockwork recovery and do a few wipes.
Sent from my SPH-D700 using XDA App

Not sure but it seems the the app is not compatible for the epic. Like stated above if your running a custom rom. Reflash it and see if it'll start. If not than you may have to do a complete wipe through clockwork. Or if you made a backup just restore it.
Sent from Epic Experienced Epic

Correct me if I am wrong.......

Had my X for a week now. It is rooted and running DarkSlideBlur 4.2, I have several other ROM's I am wanting to try out......
If I understand what I have been reading right, I can use Nandroid Backups to return to ROM's I like, or is it better to reflash them?
Trying to avoid the whole setup process....
Thanks in advance
Mace

A nandroid would be the route to go. It restores your phone to the exact state it was when you backed it up. Every call text message everything will be as it was.

Nandroid all the way. Works every time
Sent from my HTC Glacier using XDA App

MaceBewley said:
Had my X for a week now. It is rooted and running DarkSlideBlur 4.2, I have several other ROM's I am wanting to try out......
If I understand what I have been reading right, I can use Nandroid Backups to return to ROM's I like, or is it better to reflash them?
Trying to avoid the whole setup process....
Thanks in advance
Mace
Click to expand...
Click to collapse
As already stated, a nandroid is a best bet. Just keep in mind if you do any updates (OTA) and the radio gets updated (i.e. 2.3.15 to 2.3.340) an old nandroid will brick your phone due to an older bootloader
Sent from my DROIDX using XDA App

Thanks guys! I thought that was the case, as I have been all over these forums "researching" for a couple months before I got the X!
Now off to research "Radio"?? (thats a new one to me)

But what if you mount your system and get stuck in the bootup. i cant even get to the recovery. i dont know what to do.

Nandroid always has your back. Something gets screwed and you are stuck in a boot loop, plug in the usb or charger, pull the battery, put it in and boot up. That will hijack back into Clockwork.
Always Wipe Data/Factory Reset, Wipe Cache/Advanced/Wipe Dalvik before you flash a new ROM and you "almost" always avoid a boot loop.
Sent from my DROIDX using XDA App

that is clockwork recovery, the stock recovery is accessed with a combination of hard keys which i am not sure which they are off the top of my head. in that you can wipe, but unfortunately no nandroid restore.

I tried every rom out there. The fastest most stable best battery life is stock. Deodexed stock. You can theme and font.
Sent from my DROIDX using XDA Premium App

mattmartin77 said:
that is clockwork recovery, the stock recovery is accessed with a combination of hard keys which i am not sure which they are off the top of my head. in that you can wipe, but unfortunately no nandroid restore.
Click to expand...
Click to collapse
The hard keys are volume down and camera button if you wanted to know

Thats to get to the bootloader. Recovery is home and power and hold on until it comes up. To get into safe mode you hold power and the menu button
Sent from my DROIDX using XDA Premium App

Gal Tab 10.1 I/O WIFI - shows only 13gb instead of 32!

Hi!
My lovely galaxy tab 10.1 entered into the famous boot loop.
A friend of me got to recover my tablet by wiping all data, flaching boot and recovery again and installing the 3.1.
When He gave it back to me, we realize that the internal memory was only 13gb instead of the previous 32gb.
I tried to "format the SD" through the recovery but with the recovery that I istalled trhough Rom Manager it allows only 4gb, so I didn't try.
I don't have many details of what was the recovery process, and I'm a proud owner of the GT sice 4 or 5 days. I didn't find anybody with a similar problem.
Any suggestion?

Do a factory reset and it will come back
Sent from my GT-P7510 using XDA Premium App

Thanks a lot for your answer. What do youou mean exactly with a factory reset? Should i install a clean rom, or there is a simplier way to do it? I assume that i will need to reroot afterwards.

Settings>privacy>factory reset

I did a factory reset. It deletes all rhe data on the tab, butbit doesnt really format the internal storage. It still shows only 13gb.
Any other posbility?

maybe your "friend" substitute your 32gb with a 16gb model. because reformating the int sdcard in recovery will bring back the full space. no matter what.
my 16gb model shows 13gb space. see what i mean ...

double check serial Nos etc on box.

I don't think he changed the tab.
I wanted to format the int sdcard in recovery, but when I reboot in recovery, I dont see any option to format the sdcard. It is maybe "format data"?

When i had to save my io from a bootloop. I too only got 13 free after... A factory reset actually does wipe and format the memory. Worked for me
And theres quite a few other threads about it...
Sent from my GT-P7510 using XDA Premium App

Are all of the io edition of the tab 32 gb? I thought since they were giving it out for free it would be 16 gb
Sent from my GT-P7510 using Tapatalk

maybe it was wrong repartitioned during the flash - this would be my guess...

I did a factory reset both via settings/security/factory reset and recovery/factory reset and in none of the cases deleted any file in the storage.
Do you know if there is any alternative way to fully format the storag e, via addb or fastboot?

Any help? Could you suggest me another way to format the internal storage of my gt? I already tried the factory reset in the recovery.
Sent from my GT-P7510 using xda premium

are you using stock retail recovery or have you flashed cmw and usomg that recovery?

I have the cwm recovery. I flashed it with the rom manager
Sent from my GT-P7510 using xda premium

I am having the same problem. I am so sick of this tablet and its boot looping problems. I am going to try fastboot wiping the device and reflashing the stock recovery tomorrow.
-frank
Sent from my Nexus S 4G using xda premium

I wonder what u guys r doing to get enuff bootloops for it to be a real issue... Have had my io tab since they came out and only once (before the retail was even out) has it happened to me and only after i was messing with things...
Sent from my GT-P7510 using xda premium

I am not "doing" anything to make this happen. Most of the time it happens like this:
1) Use tab for a while at night before bed.
2) Plug in tab on nightstand, turn out light got o bed.
3) Wake up next morning, click power button to wake tab Tab and it is on the infamous Entering Upload mode.
4) After which it goes into boot loop mode.
So, after reflashing the stock recovery, the factory reset trick worked. Apparently whatever call the factory reset does will not work with Clockwork.
Well, at least this time I made a nandroid backup using fastboot boot clockwork so when it fails the next time I can restore it.
-frank

Maybe its cwm causing the headaches, i havnt even bothered with it yet on this tab
Sent from my GT-P7510 using xda premium

Except I did not have that on my tab until this last crash. Before that I kept everything still unrooted like I got it. I took it off again when the reset failed so we will see if/when it crashes again.
-frank
Sent from my Nexus S 4G using xda premium

[SOLVED]Device stuck in bootloop

Hey guys,
Regardless of my low post count, I'm not a noob when it comes to rooting\unlocking\flashing. With that being said, I've run into a few problems with my Nexus 4. I was making a nandroid backup of my most recent CM 10.1 nightly and decided to flash back to stock rooted in order to fix my bluetooth issues. When attempting to restore, I received an error stating that my MD5 sum didn't match. This happened to all but one of my backups and it would old restore part of my data before failing on the "working" backup. It would boot just fine, but it was basically a factory image and none of my downloaded applications restored execpt the icons. I realized that this image was pretty unstable so I took it one step further..... I decided to restore to factory stock by flashing the factory images from google (I snagged a copy before google pulled them). I ran the flash-all.bat and it restored everything with no issues.....but now it gets stuck on the nexus "X" during boot. I left it for about an hour and it's still on the "X". At this point, I decided to relock the bootloader and call google.
I realized that something is probably corrupt so I called Google and got an RMA but I won't get a new phone until LG makes more Nexus 4's (Nexi?, lol).
Does anyone have any ideas what could have happened? ANy ideas on how to fix this? I'd much rather fix this damn thing instead of going thru the RMA process.

Boot into stock recovery, clear cache and factory reset. You'll be up and running.
Sent from my Nexus 7 using xda premium

Maybe I'm more of a newb than I realize, lol.
How do I do that via stock rocovery? I just have the red triangle. I know how to do that in Team Win and CWM, but not in stock.

Boot into the bootloader by holding volume down and power.
Use the volume key to toggle to recovery and press power to select.
When you see the exclamation. Press volume up and power to open the recovery menu.
Then clear cache and factory reset.
Sent from my Nexus 7 using xda premium

El Daddy said:
Boot into the bootloader by holding volume down and power.
Use the volume key to toggle to recovery and press power to select.
When you see the exclamation. Press volume up and power to open the recovery menu.
Then clear cache and factory reset.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I went ahead and unlocked the bootloader again and flashed CWM touch in the meantime. I cleared cache and reset. Same result. It's just hanging on boot.

No you need to do this in the stock recovery.
Sent from my Nexus 7 using xda premium

El Daddy said:
No you need to do this in the stock recovery.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
If I knew who you were......i'd kiss ya. Thanks man. It's fixed.
Now, just out of curiousity, why does that only work in stock recovery instead of a custom recovery?

Not entirely sure. The stock recovery wipe clears everything including data/media/
There also seems to be an issue with the bootloader not properly wiping the device. Hopefully they can fix the bug in a future update.
No kiss needed. Just a thanks and a virtual high five will do.
Sent from my Nexus 7 using xda premium

El Daddy said:
Not entirely sure. The stock recovery wipe clears everything including data/media/
There also seems to be an issue with the bootloader not properly wiping the device. Hopefully they can fix the bug in a future update.
No kiss needed. Just a thanks and a virtual high five will do.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I see what you mean about not wiping everything.....after all the wiping and flashing, it still had my same custom wallpaper from my CM 10.1 ROM when it booted. Weird.
Thanks again.

That's not because of something not getting wiped.
Its because your wallpaper syncs to Google. It's auto downloaded and applied when signing in for the first time.
Sent from my Nexus 7 using xda premium

PLEASE HELP. Boot loops to recovery

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.