this question was originally posted as my phone stuck in bootloop by itself
I've been using Slim Bean very neatly for the past 3 months until today
I charged my phone and I saw only battery icon (you know like when you charge it from no battery)
I unplugged and there is a red ! on top left corner in the GT-i9300t boot screen.
I was able to get to TWRP recovery, fortunately.
ok now I get it to boot what I did I restored to my NEATROM that I have backed up long time ago and before that I failed to restore to Slim Bean also.
I was happy it worked but
I'm now so confused as my newly RESTORED Neat rom looks like a new flash, with Samsung welcome screen and gmail login and all.
I have been restoring ROMS for some time now I know this ain't right, it should look like the state when I BACKED IT UP.
Is something wrong with my phone????
You must have backed up and restored a stock type rom .
Phone cannot change to stock by itself .
jje
I'm pretty sure it's not stock because I have been restoring it before and all the apps are there
now there's nothing
pinmemo said:
I'm pretty sure it's not stock because I have been restoring it before and all the apps are there
now there's nothing
Click to expand...
Click to collapse
Sounds like it failed to restore data
slaphead20 said:
Sounds like it failed to restore data
Click to expand...
Click to collapse
perhaps
This is getting even weirder, I cannot install Slim Bean or any AOSP ROM, only able to restore Samsung ROM with the same result...
grr
pinmemo said:
perhaps
This is getting even weirder, I cannot install Slim Bean or any AOSP ROM, only able to restore Samsung ROM with the same result...
grr
Click to expand...
Click to collapse
Time for a completely clean install,full wipe, Odin flash of stock firmware I reckon and start from scratch, easiest solution imho
slaphead20 said:
Time for a completely clean install,full wipe, Odin flash of stock firmware I reckon and start from scratch, easiest solution imho
Click to expand...
Click to collapse
your 'start from scratch' solution work thanks a lot! although different method
first I tried internal wipe, nothing changes
then here comes FORMAT DATA bam that fixed it :good:
unfortunately I didn't fulfill my curiosity as to what just happened
and I thought NANDROID back up is the best way to prevent any disaster ROM wise
it may not be made to withstand partition problem which is what I think happened.
The problem, to my recent realization actually happened after I recorded a very long video (20mins)...
Backup could have corrupt if in internal sd.
Sent from my GT-I9300 using Tapatalk 4 Beta
rootSU said:
Backup could have corrupt if in internal sd.
Sent from my GT-I9300 using Tapatalk 4 Beta
Click to expand...
Click to collapse
but it's in my external card. Copied over from my computer even.
Moving / copying files can also be a catalyst for corruption.
I've had the same issue with a backup from computer before.
My reference to internal sd was if your partitions are messed up, its likely your backup was corrupt.
It could even be the backup just didn't take properly. If you have md5 checking turned on then that is more likely.
Anyway, it can happen from time to time
Sent from my GT-I9300 using Tapatalk 4 Beta
ok next time I'll make sure MD5 was checked.
Related
I tried a new rom out this morning (miui 1.12.30 {2.3.7} {1-1-2012}), liked the interface of the rom, but the phone started to heat up immediately. I need to do some more research of why this happened. So I decided to go back to Unammed via a nandroid backup. When restoring i get this error
.android_secure.img not found. Skipping restore of /sdcard/.android_secure.
Click to expand...
Click to collapse
Any help would be appreciated.
gadget069 said:
I tried a new rom out this morning (miui 1.12.30 {2.3.7} {1-1-2012}), liked the interface of the rom, but the phone started to heat up immediately. I need to do some more research of why this happened. So I decided to go back to Unammed via a nandroid backup. When restoring i get this error
Any help would be appreciated.
Click to expand...
Click to collapse
Are you sure you wiped data and cache. Also dalvic. I always flash miui twice also. That happened to me once before and I re flagged and all is well. The reason it is overheating is cause it stays at Max frequency ( CPU). Anyways check out the Miui thread in development if you want to try it again.
As far as your restore error, I don't know.
One time at football camp, I put my shoulder pads in my arse.
I may try miui again in the future, just want to get back where i was before. Thanks.
gadget069 said:
I tried a new rom out this morning (miui 1.12.30 {2.3.7} {1-1-2012}), liked the interface of the rom, but the phone started to heat up immediately. I need to do some more research of why this happened. So I decided to go back to Unammed via a nandroid backup. When restoring i get this error
Any help would be appreciated.
Click to expand...
Click to collapse
I assume you have UnNamed back and all is working normally?
That message most likely means the restore was looking for something that was not present in the backup because it was not there to back up in the first place.
creepyncrawly said:
I assume you have UnNamed back and all is working normally?
That message most likely means the restore was looking for something that was not present in the backup because it was not there to back up in the first place.
Click to expand...
Click to collapse
Yes, everything seems to be running fine, I'm wondering if miui installed something that a nandroid wont write over. I also noticed in cwm i can use the power button to select the option i choose, actually i can use both the home and power button now. So something has changed in cwm i believe.
gadget069 said:
Yes, everything seems to be running fine, I'm wondering if miui installed something that a nandroid wont write over. I also noticed in cwm i can use the power button to select the option i choose, actually i can use both the home and power button now. So something has changed in cwm i believe.
Click to expand...
Click to collapse
sdcard/.android_secure is the hidden folder where apps2sd puts apps. It might be specific to cyanogen mod and miui, but not sure.
It happened when you first made your nandroid backup via cwm. The other day when I did a backup I watched it and saw the error skipping sdcard cause of no . android_secure . It has to do with cwm not being able to do a restore backup to our external sd. If you go in your external sdcard dir you will see the android secure file. So if next time you want your apps just move the file over for the backup and restore
Sent from my SAMSUNG-SGH-I777
Hi there,
i tried a lot of word combinations to get a thread with my specific problem but i didnt manage it to find one.
So here is the deal:
i have german galaxy s 2 (9100, bought in september 2011) and i flashed it last year with darkyrom HD something gingerbread-style.
so it was rooted and all that stuff.
it worked pretty fast and it was stable and it looked sleak.
Last year in November i put Ressurrection remix 3.x (dont know which version of it) on my phone.
It had a lot of crashes, freezes and while playing ingress it always drained around 20% of the battery within 10-20minutes.
So i stopped it. I put the last version of it 3.1.3. of it onto my phone with a full wipe, cache partition, factory reset onto my phones and the problems went keep going.
As an example:
-I couldnt access options where i can select ringtones or to see what is on the sd. it crashed and went back to the "main screen".
-Yesterday i tried around 15 roms, and nearly everything except militant rom keep crashing while iam installing them.
-Sometimes it crashes already while iam installing the rom, sometimes its after a couple of hours, that i cant access the rom any more.
-The newest problem is, that sometimes the power button doesnt respond, when i push it (in jelly bam)
Please explain, what iam missing or is my phone just broke?
It never fell down, no water or anything freaking other things.
I hope you can help me.
should i send it back or what is wrong?
i dnt knw bt samsung.. bt may b it happens coz of when ur changing ur rom gb to i cs or jb whole operating system is diff so u hav to format ur sd card to make it working.
Try that way too
Sent from my Xperia Neo V using xda app-developers app
Try changing kernel
Sent from my GT-i9100
sreehari.007 said:
i dnt knw bt samsung.. bt may b it happens coz of when ur changing ur rom gb to i cs or jb whole operating system is diff so u hav to format ur sd card to make it working.
Try that way too
Sent from my Xperia Neo V using xda app-developers app
Click to expand...
Click to collapse
so what do i have to do to make it work flawlessly?
i cant boot it right now without the power plug.... and the battery is at 90%....
so something is completely broken within the system....
jootanen said:
Try changing kernel
Sent from my GT-i9100
Click to expand...
Click to collapse
i thought the kernel is already included when you're installing one of the roms?
which one should i take?
or how wipe the whole system to have it like "out of the box"?
flash a stock ROM and see how it behaves.
Sent from the little guy
Sakujou_Kei said:
i thought the kernel is already included when you're installing one of the roms?
which one should i take?
or how wipe the whole system to have it like "out of the box"?
Click to expand...
Click to collapse
if you are rooted, you can try flashing NeatROM lite 4.2 based on LS8 and see how it behaves else flash official JB 4.1.2 using odin.
kmaq said:
if you are rooted, you can try flashing NeatROM lite 4.2 based on LS8 and see how it behaves else flash official JB 4.1.2 using odin.
Click to expand...
Click to collapse
ok, ill try that right now..
if not using odin and try to do something with my nand???
after cleaning and putting a stock rom on it and afterwards rooting it with cwm still the same problem: boot loop or while the first installation, it crashes.
so what to do?
just hang around with the stupid official one?
If you did everything from Factory reset to changing kernel, and everything is still bad like that. I think that there's something with your phone's hardware.
Sakujou_Kei said:
ok, ill try that right now..
if not using odin and try to do something with my nand???
after cleaning and putting a stock rom on it and afterwards rooting it with cwm still the same problem: boot loop or while the first installation, it crashes.
so what to do?
just hang around with the stupid official one?
Click to expand...
Click to collapse
after flashing the ROM via odin, reboot into recovery, wip/factory reset and then go in to mount & storage, make sure system, data and sd cards (internal & external if any) are all mounted if not mount it and reboot.
kmaq said:
after flashing the ROM via odin, reboot into recovery, wip/factory reset and then go in to mount & storage, make sure system, data and sd cards (internal & external if any) are all mounted if not mount it and reboot.
Click to expand...
Click to collapse
well, i tried that. still nothing. it crashes or i have a bootloop.
so whats up with this phone?
so except the stock rom, where i can boot into it, all custom firmwares just crash or work for a while and then they'll crash.
i dont get this.
it started just days ago, now i dont even can use anything....
Sakujou_Kei said:
well, i tried that. still nothing. it crashes or i have a bootloop.
so whats up with this phone?
so except the stock rom, where i can boot into it, all custom firmwares just crash or work for a while and then they'll crash.
i dont get this.
it started just days ago, now i dont even can use anything....
Click to expand...
Click to collapse
just as an example, when i tried to put on the neatrom-lite on my phone, it crashes while iam selecting the country. and this is just 2-3seconds after booting into the fresh and new system.
something is completely ****ed up....
so right now, i have the militant rom on my phone, got booted up, but the power button doesnt work.... when the phone is on...
so everytime, when i want to switch of the screen, i have to wait, or take of the battery. and switching on is only possible with the home button.
whats wrong?
Given you have the same problems on stock, hardware problem. Back to stock, reset counter, send it in for warranty service (if you have warranty), if not, take it to local mobile repair shops.
reseting the counter... with stock? how to do that? i thought this is only possible with root? and i thought, as soon as i root, there is something already on the counter?
Sakujou_Kei said:
reseting the counter... with stock? how to do that? i thought this is only possible with root? and i thought, as soon as i root, there is something already on the counter?
Click to expand...
Click to collapse
You have two option. Either flash a custom kernel (siyah, for example), then reset the counter using triangle away app. Then flash a stock firmware using odin. This wont increase the counter.
Or, if you have a USB jig, flash an older bootloader (have to careful here), then simply plug in the jig.
Sent from my GT-I9100 using xda app-developers app
hey, i got the problem:
i transferred a few files between the sd card and the internal storage of my device, and i realised, that the device is not able to fully transfer the files. it says after 40-50% that its done. is there a flash the roms via ODIN? or how to do that? just put the rom.zip as PDA?
Sakujou_Kei said:
hey, i got the problem:
i transferred a few files between the sd card and the internal storage of my device, and i realised, that the device is not able to fully transfer the files. it says after 40-50% that its done. is there a flash the roms via ODIN? or how to do that? just put the rom.zip as PDA?
Click to expand...
Click to collapse
Unzip first.
I'd advice you to read about flashing with odin and watch a couple of videos on youtube before you put yourself up to it or else you're gonna have a bad flash, and that means trouble.
Sent from the little guy
Hi
a couple of weeks ago I tried to flash a rom to my Samsung S GT i9000 Android 2.3.6 GINGERBREAD.XXJW4, I had root and went into cwm recovery and made a backup first. This is a bit hazy now as it was a while ago and I have tried so many things since then, but I think something must have happened during the back up??. Bottom line is the ROM didn't work and I had to reinstalled the back up (and have done so many times).
I have tried all different Roms from ice cream to CM but nothing works.
My problem is that every time I do a recovery of the backup it really causes problem with the phone.
If I try and install any programme from playstore or market (both via the phone or pc) it immediately closes when I try and open it up saying it unexpectedly closed. Shut down the phone and restart it - yep the app has now gone from the phone. Same thing happens with APKs.
I have tried uninstalling the back up via windows explorer, ADB, clockwordmod recovery a file manager on my phone. Doesn't matter what I do it is always there when I start the phone back up. If I uninstall any apps through settings / applications / manage applications, turn off the phone then back on and they are back.
I have tried to clear it by installing stock roms but the back up and all its files and apps etc are still there. I have tried factory formatting the phone via settings/ privacy, I have tried using the numbers and hashes on the keypad, I have carried out full wipes in recovery and the dalvik cache etc.
I have made further backups but they are deleted from the phone just like the apps.
If I take a photo or video and close my phone down they are deleted.
If I access Facebook and update the news feed to the current date, when I restart my phone it is back to the last thing I looked at prior to my backup.
I think the problem is that the phone is using the backup some how and this is stopping me from deleting it. Something like trying to uninstall a system file on a computer when it is running.
I think I have watched just about every video ever created on this topic and every thread on the internet to no avail.
Bottom line is the phone works to an extent. I can phone, text, use the internet etc but cannot install or delete any apps.
I would be really grateful if anyone out there has any ideas that I could try
Do a complete restore with Odin/hiemdall then reroot and install ROM, its hard to say what happened to your phone, but a compete install (with pit) should fix you right up
Best of luck
Sent from my Nexus 4 using Tapatalk 2
demkantor said:
Do a complete restore with Odin/hiemdall then reroot and install ROM, its hard to say what happened to your phone, but a compete install (with pit) should fix you right up
Best of luck
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
When you say do a complete restore.... Do you mean install a stock rom?
demkantor said:
Do a complete restore with Odin/hiemdall then reroot and install ROM, its hard to say what happened to your phone, but a compete install (with pit) should fix you right up
Best of luck
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I just tried that with pit - no joy. Still same problems. Phone is still not at stock.
Rodders289 said:
I just tried that with pit - no joy. Still same problems. Phone is still not at stock.
Click to expand...
Click to collapse
you have to format everything(system,data,cache,dalvic cache) using cwm before flashing with odin to get a fresh stock
Rodders289 said:
I just tried that with pit - no joy. Still same problems. Phone is still not at stock.
Click to expand...
Click to collapse
So in Odin/heimdall you flashed all partitions and pit? And the phone still didn't return to stock? Then the issues you're having sounds suspiciously like hardware, but I can't think of a hardware issue that could cause this.
Are there various stock versions Sammy put out? As in can you try an older/newer one?
sangalaxy said:
you have to format everything(system,data,cache,dalvic cache) using cwm before flashing with odin to get a fresh stock
Click to expand...
Click to collapse
Not really, if pit is checked then all partitions should get formatted, but it wouldn't hurt to do so.
Sent from my Nexus 4 using Tapatalk 2
demkantor said:
So in Odin/heimdall you flashed all partitions and pit? And the phone still didn't return to stock? Then the issues you're having sounds suspiciously like hardware, but I can't think of a hardware issue that could cause this.
Are there various stock versions Sammy put out? As in can you try an older/newer one?
Not really, if pit is checked then all partitions should get formatted, but it wouldn't hurt to do so.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
mm yeah I didn't noticed pit but did he tick repartition on odin
it should be ticked for that
sangalaxy said:
mm yeah I didn't noticed pit but did he tick repartition on odin
it should be ticked for that
Click to expand...
Click to collapse
That's to all for your replies. I am in Turkey at present on holiday but I am trying your suggestions, I did flash a pit with the repartition box ticked but still no joy. I took some roms out on a usb stick but think I need to try some others. Problem is I don't have a great download speed at present.
No matter what rom I use, AOSP or TouchWiz, I get a bootloop. Usually I can solve these issues myself, I've softbricked my Android devices tons of times since I got my first Android (Samsung Fascinate) in 2010, and I've managed to get out of all those situations, but this one has me stumped.
The problem began today. Randomly after booting into Philz Touch recovery, I got an error that read "could not mount /data to setup /data/media path." I used this fix and it worked, unfortunately, I lost all of my internal SD card data. However, since then, every 4.3 and 4.4 rom I've flashed (TouchWiz and AOSP) just doesn't work. To be more specific, I initially tried today's (8/02) Cyanogenmod nightly...bootlooped. Then I tried the rom I was on when the problem initially occurred...bootlooped. Then I flashed this rom later...bootlooped. Naturally, I did a factory reset/dalvik wipe/cache wipe before each rom flash.
Do I have to flash stock 4.1.2 again? I really don't want to if I can avoid it, but I'm downloading the rom anyway.
EDIT: I flashed 4.1.2...it bootlooped. I performed a factory reset and cache wipe and it STILL bootloops. Something I did notice is that it says "E: failed to mount /efs (Invalid Argument)." I noticed that earlier back when I was using Philz recovery as well. Could that be a reason for all of these bootloops?
Did you backup your efs data? I'll been flashing for years and never gave it a 2nd thought... until a few weeks ago when my kids while playing with the phone froze it... and I had efs errors and bootloops. ..
I was able to odin the efs backup but unfortunately I've also locked my bootloader (still not sure how I did that)...
Currently I'm running safe strap with 4.3 skynote-n3bula hybrid... do I miss kk? Yepper... but at least I have my phone back...
The efs fix is in this forum.. try search? ... I will look to see if I saved the files some where...
Sent from my SCH-I605 using Tapatalk
kingamra said:
Did you backup your efs data? I'll been flashing for years and never gave it a 2nd thought... until a few weeks ago when my kids while playing with the phone froze it... and I had efs errors and bootloops. ..
I was able to odin the efs backup but unfortunately I've also locked my bootloader (still not sure how I did that)...
Currently I'm running safe strap with 4.3 skynote-n3bula hybrid... do I miss kk? Yepper... but at least I have my phone back...
The efs fix is in this forum.. try search? ... I will look to see if I saved the files some where...
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
I unfortunately didn't backup my efs. I didn't know anything about efs until today when I ran into this problem and started googling around. Do you know of an efs backup that works? I'll give a search around the forums for a fix.
Tkun said:
I unfortunately didn't backup my efs. I didn't know anything about efs until today when I ran into this problem and started googling around. Do you know of an efs backup that works? I'll give a search around the forums for a fix.
Click to expand...
Click to collapse
http://forum.xda-developers.com/not...w-to-unbrick-hard-bricked-i605-n7100-t2825222
kingamra said:
http://forum.xda-developers.com/not...w-to-unbrick-hard-bricked-i605-n7100-t2825222
Click to expand...
Click to collapse
Thanks! I'll test this out.
Not sure what went wrong, but I've just had to use flashtool. I decided to flash one of the stock roms available. I don't feel any of what resulted was fault of the Rom so I won't specify. I made another backup of my tweaked Rom, and wiped as instructed and installed. Everything flashed ok but the Rom was a little buggy so I decided to restore my tweaked backup. Rebooted to reovery, wiped then selected which backup to restore. In short, the backup was showing no partitions available to restore and wouldn't work. So, I chose my original backup of stock and that showed everything so I restored. From there, the backup said complete so I rebooted. I ended up with the flashing red and blue led and could only boot to twrp. I tried to reflash the Rom zip but it failed to open. So here I am after using flashtool, which was an adventure as well. I'm curious if anyone else at all has had a similar experience? Is it possible my twrp was corrupt in some way?
Sent from my LGLS990 using Tapatalk
Had you ever tried to restore you backups prior? Just to make sure you had a good backup.
Did you use compression in TWRP? It's been an issue in the past. At least with the OG it was.
I have no other ideas. Sorry you had to go through that. But at least you got it fixed.
I hadn't restored prior to this, no. I think I did use compression on the second backup. Good point. One good thing, I don't have the ugly yellow spark boot ani any more. [emoji6]
Sent from my LGLS990 using Tapatalk
Evolution_Freak said:
I hadn't restored prior to this, no. I think I did use compression on the second backup. Good point. One good thing, I don't have the ugly yellow spark boot ani any more. [emoji6]
Sent from my LGLS990 using Tapatalk
Click to expand...
Click to collapse
Is this after Flashtool? The only way I know of to get it back is ##RTN#. And you'll need your MSL.
You shouldn't have Wi-Fi calling either then. That's the clincher.
Be safe and backup your EFS first though.
Evolution_Freak said:
I hadn't restored prior to this, no. I think I did use compression on the second backup. Good point. One good thing, I don't have the ugly yellow spark boot ani any more. [emoji6]
Sent from my LGLS990 using Tapatalk
Click to expand...
Click to collapse
i also used compression for my backup did you figure out if that was what caused the problem?
kMogs17 said:
i also used compression for my backup did you figure out if that was what caused the problem?
Click to expand...
Click to collapse
To be safe, boot into recovery and try to restore your backup. If you don't see the partitions listed, then it's probably compression.
Edit:
Don't wipe anything though!
Sent from my LGLS990 using Tapatalk
Evolution_Freak said:
To be safe, boot into recovery and try to restore your backup. If you don't see the partitions listed, then it's probably compression.
Edit:
Don't wipe anything though!
Sent from my LGLS990 using Tapatalk
Click to expand...
Click to collapse
Yep yep - Im glad this is my second LG, I never use compression thanks to all I've learned from the lgog. That sucks though dude, but lesson learned.
For the record, I've flashed several things and restored several backups already(I have two, odexed stock and deodexed stock) without any issues.
Evolution_Freak said:
Not sure what went wrong, but I've just had to use flashtool. I decided to flash one of the stock roms available. I don't feel any of what resulted was fault of the Rom so I won't specify. I made another backup of my tweaked Rom, and wiped as instructed and installed. Everything flashed ok but the Rom was a little buggy so I decided to restore my tweaked backup. Rebooted to reovery, wiped then selected which backup to restore. In short, the backup was showing no partitions available to restore and wouldn't work. So, I chose my original backup of stock and that showed everything so I restored. From there, the backup said complete so I rebooted. I ended up with the flashing red and blue led and could only boot to twrp. I tried to reflash the Rom zip but it failed to open. So here I am after using flashtool, which was an adventure as well. I'm curious if anyone else at all has had a similar experience? Is it possible my twrp was corrupt in some way?
Sent from my LGLS990 using Tapatalk
Click to expand...
Click to collapse
Noticed that you said you wiped before restore. I did that once on my G2 and ended up having to use flashtool.
leroybrute said:
Noticed that you said you wiped before restore. I did that once on my G2 and ended up having to use flashtool.
Click to expand...
Click to collapse
You should always wipe first IMO. There's always ghosts in the machine. It's just an added measure to give you a clean restore/flash. Most people that have issues with roms don't wipe, and dirty flash/restore.
I've never had an issue wiping all 4. And compression just seems to never work right. At least with all the G series.
engine95 said:
You should always wipe first IMO. There's always ghosts in the machine. It's just an added measure to give you a clean restore/flash. Most people that have issues with roms don't wipe, and dirty flash/restore.
I've never had an issue wiping all 4. And compression just seems to never work right. At least with all the G series.
Click to expand...
Click to collapse
If you wipe all four and your twrp isn't on your external SD card you're screwed if you want to restore.
I always wipe when installing roms, just not restoring. Habit from using phones without ext.
I also thought I saw a wipe script built into the restore option.
I called Sprint today to get my MSL. I needed to use the ##RTN# code to get the WiFi calling app and the other stuff back after flashtool. They had me do a factory reset first to see if that would do it but then gave me my MSL without question.
Thanks again for all the info learned in this thread. I finally got around to re-rooting and re-bumping and all were smooth and easy.
Sent from my Stump'd & Bump'd Sprint LG G3
engine95 said:
You should always wipe first IMO. There's always ghosts in the machine. It's just an added measure to give you a clean restore/flash. Most people that have issues with roms don't wipe, and dirty flash/restore.
I've never had an issue wiping all 4. And compression just seems to never work right. At least with all the G series.
Click to expand...
Click to collapse
I only had a problem with compression once on my OG for the rest of the time it worked fine and was a necessity because it had no external storage but anyway i just checked the compressed backup i made and the partitions show up under restore, but i havent tried it yet because i have no reason to. maybe when aosp comes out