Hey folks! I have an Acer A500 that I have been working on "with" dibb_nz over the past week. I have no idea what was on it originally, it came to me nearly dead. After a TON of attempts and hard work from dibb, I now have Skrilax's bootloader and recovery installed. I flashed CM10-10 Flex_V6 ROM from Civato onto the device successfully. Here is the problem: no matter how I boot up, it either goes directly into "Power off - Shutting down" then vibrates and blanks out or, after a fresh install, it will say "Android is upgrading", "Optimizing apps", "Starting Apps", then on to the Power Off-shutting down thing.
Does anyone have any clue what may be going on here? I have tried earlier ROMS, all from Civato, but with the same Power OFF result.
Any help would be MUCH appreciated!
Thanks in advance,
Sharkguy
hey sharkguy, I've been combinf forums and threads with no joy at all, the only thing I haven't checked is the rom thread, might pay you to look thru that, just in case its rom related ( I doubt it really, but there maybe other reports such as yours ) If I ever come across something I'll be sure to get back to you, good luck m8
Calling @Moscow Desire---are you out there Mr Moscow?? Ever heard of something like this before, my friend, very strange....Hope you are well MD its been awhile
dibb_nz said:
hey sharkguy, I've been combinf forums and threads with no joy at all, the only thing I haven't checked is the rom thread, might pay you to look thru that, just in case its rom related ( I doubt it really, but there maybe other reports such as yours ) If I ever come across something I'll be sure to get back to you, good luck m8
Calling @Moscow Desire---are you out there Mr Moscow?? Ever heard of something like this before, my friend, very strange....Hope you are well MD its been awhile
Click to expand...
Click to collapse
Hey Dibb! Offhand, I think it may be the old power part that used to be flashed with stock ROMs. Forget what its actually called. Typically we removed this from the install as its generally not needed. That's a guess, but am at work for the night so can't check my stuff. Could explain the shutdown. But if it shuts down when updating the apps, then its probably bad memory partition.
But I'll lean more towards the power part. Will have to check a stock ICS ROM. Might need to make a separate flash install just for it. It it would boot to the display and it had horrible display and battery issues then that would be it.
Well, that sounds complicated. I should have the new battery by the weekend so let me at least try that before anyone gets all technical. Unfortunately I dont know anyone with another a500 to test batteries...
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk
Moscow Desire said:
Hey Dibb! Offhand, I think it may be the old power part that used to be flashed with stock ROMs. Forget what its actually called. Typically we removed this from the install as its generally not needed. That's a guess, but am at work for the night so can't check my stuff. Could explain the shutdown. But if it shuts down when updating the apps, then its probably bad memory partition.
But I'll lean more towards the power part. Will have to check a stock ICS ROM. Might need to make a separate flash install just for it. It it would boot to the display and it had horrible display and battery issues then that would be it.
Click to expand...
Click to collapse
Hey MD good to see u my friend
oh, the eec thing? Rings a bell...
The bad memory partition, do you mean the memory chip itself or just the partition.
I've just never heard of the faulty chip causing a spontaneous shut down, sure has me beat....and I Hate that, lol
But thanks for the response MD, if you can offer any solution from your archives of knowledge and wisdom, I know someone who'd be forever grateful
Have a great day all!!
rgds Donna
Yeah Dib, the eec thing. Just couldn't remember. Usually we just removed that command from the install script as usually once it was flashed at the factory, rarely did you ever have to flash it again. I will have to look and see in the next couple of days. Worth a shot though. Might be able to put it in a CWM install.
Oh, forgot to add @sharkguy
As with a damaged partition, if the memory got hosed in that particular partition, whichever, there's not a whole lot that can be done. Could try running babsector, but not sure if it would fix it or not. There's been success running it before, but only about 30% as I can tell. Devblks can get physically damaged. Usually the partitions are large enough to mark the bad spots as bad, and still be able to install things. That's what babsector did I think as near as I can tell.
A faulty chip "could" cause a shutdown, especially if it couldn't create the dalvak which is kind of the next step when "starting applications" If I guess right, although I would think it would bootloop rather than shut down. As you say, I've never heard of a power off before, unless the eec was bad and it thinks the battery is dead.
I'm just curious if the OP has done a full format on internal memory via CWM? Before installing. Not the usual wipes, but going into advanced, and triggering the full format. I used it after running that CM stuff awhile back, as it messed up everything (lots of testing). Needed a clean sweep of the internal memory.
As you see, I am still around Just with being a senior mod, not a lot of time for messing with things.
I'm still leaning towards eec pwr. (I'm using beer logic at this point)
Bear with me on this. Let's say the eec got hosed somehow. It happens on occasion. And you install several custom roms, which of course don't have eec pwr in the install script as we removed it. Here's what I know.
1) Battery won't charge and is always going to shut down
2) No response on the touch screen if indeed the OS starts.
3. Tab shuts down after OS start.
So you see why I am leaning towards this.
MD
EDIT: The reason why we removed eec from the custom roms to begin with, primarily as it really wasn't needed, but it "could" cause an issue if the flash went bad. But considering the OP has UID and NVFlash, that isn't an issue now.
dibb_nz said:
Hey MD good to see u my friend
oh, the eec thing? Rings a bell...
The bad memory partition, do you mean the memory chip itself or just the partition.
I've just never heard of the faulty chip causing a spontaneous shut down, sure has me beat....and I Hate that, lol
But thanks for the response MD, if you can offer any solution from your archives of knowledge and wisdom, I know someone who'd be forever grateful
Have a great day all!!
rgds Donna
Click to expand...
Click to collapse
Hey MD, thanks for thr insight on my issue. I worked closely with Dibb_nz for close to a week. I am not entirely sure if I did the wipe you mentioned, but believe me, if I could find a way to format, erase, wipe or clear memory I did. Everything you described as what you knew is correct with one exception: if it is relevant the touch screen works in recovery mode.
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk
sharkguy said:
Hey MD, thanks for thr insight on my issue. I worked closely with Dibb_nz for close to a week. I am not entirely sure if I did the wipe you mentioned, but believe me, if I could find a way to format, erase, wipe or clear memory I did. Everything you described as what you knew is correct with one exception: if it is relevant the touch screen works in recovery mode.
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk
Click to expand...
Click to collapse
Always works in recovery, as it is independent of the OS...
Righto. I figured it didnt matter in this case. But yes, the rest of the facts are as you understand them.
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk
sharkguy said:
Hey MD, thanks for thr insight on my issue. I worked closely with Dibb_nz for close to a week. I am not entirely sure if I did the wipe you mentioned, but believe me, if I could find a way to format, erase, wipe or clear memory I did. Everything you described as what you knew is correct with one exception: if it is relevant the touch screen works in recovery mode.
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk
Click to expand...
Click to collapse
The FULL wipes as stated in the guide m8 or via fastboot erase.
@Moscow Desire _bab sector was run and successfully, boot loader and recovery installed with no errors.
As far as the eec thing I do have a copy of that in my stash if that's any help, but no idea how to apply it????
Sent from my HTC_PN071 using Tapatalk
Well at this point I am open to anything. I just passed up on a steal of a deal on a Samsung Galaxy Tab 3 7" so im itching to know I made the right choice. I am at your mercy. Doesnt look like I will have that battery until saturday at the earliest, but so far all of the work I have done on it has been with AC power and has been successful.
Sent from my SGH-I317M using xda app-developers app
sharkguy said:
Well at this point I am open to anything. I just passed up on a steal of a deal on a Samsung Galaxy Tab 3 7" so im itching to know I made the right choice. I am at your mercy. Doesnt look like I will have that battery until saturday at the earliest, but so far all of the work I have done on it has been with AC power and has been successful.
Sent from my SGH-I317M using xda app-developers app
Click to expand...
Click to collapse
Well m8 I dunno if u made the right choice there, I guess only time will tell...there is this thread http://forum.xda-developers.com/showthread.php?t=2617196. I cannot recommend it but then my tab has never been in that state...and I'm not sure I could bring myself to put it in the oven lol...u nut wanna take a look at it any way
Sent from my HTC_PN071 using Tapatalk
Oh I've heard of ppl doing such things, but I'm luckily far mor fortunate than that. I am an electronics technician and have access to far for humane methods than an oven! Maybe I will see if I can still get the deal, then hack the a500 to pieces after geting the new battery in the mail. Lol
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk
sharkguy said:
Oh I've heard of ppl doing such things, but I'm luckily far mor fortunate than that. I am an electronics technician and have access to far for humane methods than an oven! Maybe I will see if I can still get the deal, then hack the a500 to pieces after geting the new battery in the mail. Lol
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk
Click to expand...
Click to collapse
Well, you'll be in your element then,lol...Yeh, your issue is rather unique...with babsector not returning any error its out of my area of expertise!!! But I do know that Acers build quality isn't the best....from power buttons falling out to the memory chip failure and their dodgy soldering techniques, i'm leaning towards a hardware fault 'somewhere'....
But then, it does seem strange the tab powers off during "updating apps" that points to software doesn't it???? Have look in the guide for fastboot commands (if you still have the unlocked bootloader on there) I'd erase all partitions, /system, /data, /cache etc....then run babsectot again to repartition -flash a rom and see what happens...or use tdv4 to do the same, but no rom flash needed for that as it comes with HC 3.2.1 rooted and cwm.
Anyways m8 keep us updated - and fingers crossed you end up with a positive resolution
rgds Donna
One of the last things I think I did was tdv4 without a rom flash. It still came up with the same issue. I did notice that when I took the battery out to charge on the equipment at work (closely monitored of course) to see if there was an issue with the charging circuit, that I could still do all of the same things as before with just the AC plugged in. No battery. This is why I bought a battery to try that out. The Galaxy 3 guy realized what a steal he was offering me and bumped up his price so it looks like I'm stuck woth the A500.
Thanks for the crossed fingers!!
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk
Well new battery us in and seems to charge just fine. In fact the tablet would not even attempt to power on before without AC so that is a plus. However, the same thing happens still. Boots up, and as soon as it enters the OS it gies straight to powering down.
What was the EEC thing you guys were discussing? Would it potentially help here?
Thanks again!
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk
Used all of the elements at my disposal at work to reflow the board without any change in the status of the tablet. Any ideas based on that EEC thing you guys discussed above?
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk
sharkguy said:
Well new battery us in and seems to charge just fine. In fact the tablet would not even attempt to power on before without AC so that is a plus. However, the same thing happens still. Boots up, and as soon as it enters the OS it gies straight to powering down.
What was the EEC thing you guys were discussing? Would it potentially help here?
Thanks again!
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk
Click to expand...
Click to collapse
sharkguy said:
Used all of the elements at my disposal at work to reflow the board without any change in the status of the tablet. Any ideas based on that EEC thing you guys discussed above?
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk
Click to expand...
Click to collapse
Soz m8 been full on at work to even check emails let alone reply...phew!!!!
As MD pointed out above, the EEC file thing, devs have dealt with that particular issue, but b/c yours is a relatively unique issue I guess it can't be ruled out...
Have you managed to take a look at fastboot and using the erase command to delete EVERYTHING - at least u can be sure its as clean as can be, then using babsector with an appropriate rom and see what happens there.
In that "tab flu" thread there are links to another thread (somewhere) re: eec thing - If you find it can link it here in this thread and I'll track down the file -
Oh, just to be clear - when it boots into to the OS and powers off - is it completely shutting down i.e. power led is off or is it actually booting to apx mode, black screen power lite on...whats the chances of a vid so we can see exactly what it does???
rgds dibb
Sure I can video it for ya, but how should I link it? Can I link to YouTube on these forums?
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk
sharkguy said:
Sure I can video it for ya, but how should I link it? Can I link to YouTube on these forums?
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk
Click to expand...
Click to collapse
Ok, so new development, so to speak. As you can see from the crappy video I shot just now, I can boot the tablet into the start of the OS, but it hangs at Powering Down. The new part is that I had to manually shut it off, it did not do that itself this time. I showed you the power light (orange) and when I press it again, it does power on, but is still hung up on the same screen. I don't know if that helps any, but now you can see it. By the way, sorry it is upside down, it was the only way to show you the power button after it booted.
http://youtu.be/pG_efbq6DZg
Related
Dear all,
Maybe strange.........
I just cant brick my note! Not that i want to but how? before i knew the brickbug i did:
Odin flash to a leak ICS
Rebooted in CWM And wiped Factory default.. No problem
At one time i even formatted EMMC however its called.
At this time ICS brickbug shows up in this forum and i downloaded the APK brickbug app and i seem to be vulnarable.
Today a friend comes in with a bricked note.. tellin me he was flshing from odin and it hung on first part of flash without starting. He removed phone after 30 secs.
please take notice that it can take up to 2 minutes to start flashing.
any thoughts on this story?
jeroen180 said:
Dear all,
Maybe strange.........
I just cant brick my note! Not that i want to but how? before i knew the brickbug i did:
Odin flash to a leak ICS
Rebooted in CWM And wiped Factory default.. No problem
At one time i even formatted EMMC however its called.
At this time ICS brickbug shows up in this forum and i downloaded the APK brickbug app and i seem to be vulnarable.
Today a friend comes in with a bricked note.. tellin me he was flshing from odin and it hung on first part of flash without starting. He removed phone after 30 secs.
please take notice that it can take up to 2 minutes to start flashing.
any thoughts on this story?
Click to expand...
Click to collapse
Go to the church and donate 10 euros...
You might not be so lucky next time around.
Because you didn't brick doing 1 wipe, doesn't mean that you cannot brick..
It's like getting struck by lightning, maybe you will survive the first, but it
might not save you a second time...
Well, it is a brick bug, so it is only a chance - not definitive. I have stock ICS infected with the bug, but haven't nor plan on flashing or anything like that so...
friedje said:
Go to the church and donate 10 euros...
You might not be so lucky next time around.
Because you didn't brick doing 1 wipe, doesn't mean that you cannot brick..
It's like getting struck by lightning, maybe you will survive the first, but it
might not save you a second time...
Click to expand...
Click to collapse
Back on first HTC android phone )G1) i got it bricked 3 times by flashing SPL 3 times. Anywayz Android is much better (for me) then IOS from crapple. Only HTC dreams where crap in quality since the board has been replaced 5 times due hardware failures...
Now back on business:
I know im lucky. But still .. what causes the randomness of bricking. I mean it is there or it is not? Maybe god exists. I love my note too much to brick it
jeroen180 said:
Back on first HTC android phone )G1) i got it bricked 3 times by flashing SPL 3 times. Anywayz Android is much better (for me) then IOS from crapple. Only HTC dreams where crap in quality since the board has been replaced 5 times due hardware failures...
Now back on business:
I know im lucky. But still .. what causes the randomness of bricking. I mean it is there or it is not? Maybe god exists. I love my note too much to brick it
Click to expand...
Click to collapse
It isn't random. There are just multiple conditions that need to come together to trigger it. Read the thread about it to understand better the hows and why's.
friedje said:
It isn't random. There are just multiple conditions that need to come together to trigger it. Read the thread about it to understand better the hows and why's.
Click to expand...
Click to collapse
Even if all the conditions are met there's still a good chance it won't happen. IIRC there are also versions of emmc chips that don't have the brickbug.
pboesboes said:
Even if all the conditions are met there's still a good chance it won't happen. IIRC there are also versions of emmc chips that don't have the brickbug.
Click to expand...
Click to collapse
Well the fact of having a dangerous chip is one of the conditions....
So if you don't have it then not ALL the conditions are met..
Believe me if all the conditions are met, it will brick, it"s not random.
Then, Jeroen stated that he tested with Chainfires app, and he does have the faulty chip.
Finally I haven't seen a Note in the wild yet that doesn't have a faulty chip.
I feel like the OP. Before I knew of the bug I flashed and wiped many times. But I only flash stock roms. I don't know if that helped or not.
Sent from my GT-N7000 using xda premium
No, I'm not crazy! I'm actually attempting to use a home made program to see if I can unbrick it. Does anyone know how I could do this? Thanks!
Don't know sorry but it's so fun
We spend so much time to avoid that happen ...
Sent with my GT-P7500 CM10
corybantic said:
No, I'm not crazy! I'm actually attempting to use a home made program to see if I can unbrick it. Does anyone know how I could do this? Thanks!
Click to expand...
Click to collapse
Try flashing recovery in odin and disconnect it in the middle
...
Flash a rom with odin and use repartition.
This will brick your device.
Sent from my GT-P7500 using XDA Premium HD app
Flash a rom from another device works, too.
corybantic said:
No, I'm not crazy! I'm actually attempting to use a home made program to see if I can unbrick it. Does anyone know how I could do this? Thanks!
Click to expand...
Click to collapse
Well, the other ones pretty much covered your query. I want to ask what happens if your program fails? And you mean soft or hard brick?
Sent from my amazing 10.1 galaxy tab
Like all the folks before me, flashing wrong rom from other device probably would brick it... BUT to really, really brick it messing up the bootloader is always a good way to go.
Can you short it out?
Ooops,I guess I should've been clearer! I'm trying to brick it without rooting it, i.e., perhaps some code that I could input at the bootloader?
Panos_dm said:
Well, the other ones pretty much covered your query. I want to ask what happens if your program fails? And you mean soft or hard brick?
Sent from my amazing 10.1 galaxy tab
Click to expand...
Click to collapse
Well if it fails, then I guess I gotta try - or come up with - a different program. The thing is, I had two SGT 10.1, one recently went back to Best Buy after the ICS update started freezing up my internet (not tripping tho, I was able to get a raincheck for the Note 10.1! Good thing I got the Product Replacement Plan!: victory, so I have literally a spare SGT 10.1 to mess around with. I've already rooted it and flashed different roms as well as unrooted it back to factory settings. So, to be honest, I simply have a tablet for having a tablet's sake right now.
I'm actually trying to "hard" brick it. The thing is my little program works on a "soft" brick palette so it has (usually) been able to unbrick an inadvertantly bricked phone as well as the SGT 10.1. I'm trying to see if I can brick it without rooting it to see if I can resuscitate it back to working condition.
"hard"brick it means you'd have to produce an hardware faillure, You wouldn't be able to fix an hardware failure unless you change the part that failed.
IE: Your memory chip has fried, your CPU overheated FUBAR, this kinda things
Well mine is pretty screwed. Wish I knew how it happened so I can tell you, but I don't. Yesterday I watched a movie on it and put it on the table. Later when I wanted to use it, nothing happens.
If I plug it into my PC I can get it into APX mode, but thats all. The backlight doesn't even go on. On NVflash I get the rcm version = 0x4, which means I got a locked bootloader.
When on charge, also nothing happens. The camera flash just flashed about every 2 seconds. Same thing when I keep the power button held in.
I could try your app for you on mine if you want...
Hey, I've seen many threads about people bricking their phone, and I don't wanna end up like them.
So, I want to unlock bootloader,root and flash kernel, I've read using TOOLKIT isn't the best thing to do, so I'll follow this tutorial.
My question is, what can go wrong? How to prevent anything from going wrong?
Sorry if it's a stupid question, but it's my first Android and I rather ask than be sorry, thanks in advance.
Ciclop said:
Hey, I've seen many threads about people bricking their phone, and I don't wanna end up like them.
So, I want to unlock bootloader,root and flash kernel, I've read using TOOLKIT isn't the best thing to do, so I'll follow this tutorial.
My question is, what can go wrong? How to prevent anything from going wrong?
Sorry if it's a stupid question, but it's my first Android and I rather ask than be sorry, thanks in advance.
Click to expand...
Click to collapse
Just make sure anything u do you read the thread and defiantly the op and only flash stuff that made for the N4 u should be good. Read read read and learn. I've only bricked one phone and I know what I did wrong its very hard to brick a phone so long as u don't just go flash stuff u dont know what it is.
Oh yea don't over clock your phone and run benchmarks its stupid and has fried a few also. I'm onderclocked to 1134 and I still run smooth as butta.
Sent from my Nexus 4 using Xparent Blue Tapatalk 2
Ciclop said:
Hey, I've seen many threads about people bricking their phone, and I don't wanna end up like them.
So, I want to unlock bootloader,root and flash kernel, I've read using TOOLKIT isn't the best thing to do, so I'll follow this tutorial.
My question is, what can go wrong? How to prevent anything from going wrong?
Sorry if it's a stupid question, but it's my first Android and I rather ask than be sorry, thanks in advance.
Click to expand...
Click to collapse
For a REAL hard brick on a Nexus device, you really have to do something wrong. Like I did with my Nexus S .
A real hard brick, one that isn't even repairable with a JTAG brick repair service, it never happens with a Nexus device. Well, ALMOST never. I made it happen. I don't even know what I did wrong, but apparently I screwed up the radio. Even the best of the best (Adam Outler) wasn't able to repair it. It happened the day after I installed a new ROM and a mod. The battery drained really fast. After it was dead, I plugged it in the charger, booted up my phone, started the browser, and BAM. Dead. Forever.
But I wouldn't worry about those things. Just don't do too much overclocking, because there are ways to screw up the hardware inside. Almost all bricks are fixable. If you can access fastboot mode you're okay. If you can't, there are still ways to fix it, but it might cost you some money. I don't know if Adam Outler's Unbrickable Resurrector tool works with the N4, but that's also an option if you think you really screwed up.
1) Make sure that you never flash a file that wasn't designed for the Nexus 4 (MAKO)
2) Make sure that you don't have empty batteries when you flash. 50% would be a safe minimum (though I personally frequently flash with much less than that)
3) Flashing radios / bootloaders is traditionally amongt the most dangerous operations that you can do. Make sure to check MD5 on all radios (you can check on every file if you want to be super careful)
Note: the reality is that with a nexus device, it's almost impossible to brick your device. Even if you do all of the things above wrong, you'r probably still safe. BUT, you were looking for advise--so follow those three points and you should be fine.
OP, read the link in my signature about toolkits and it will answer your question.
Sent from my Nexus 4 using xda premium
Thank you all for quick replies!
I only plan on flashing Franco's/Faux's kernel, hopefully everything will go well
unlocking the BL on a nexus is very easy. I am not sure if you need a toolkit for that.
but yeah use one if you feel more comfortable with it.
also as of now do not overclock the processor as that has been causing some bricks AFAIK.
Androyed said:
For a REAL hard brick on a Nexus device, you really have to do something wrong. Like I did with my Nexus S .
A real hard brick, one that isn't even repairable with a JTAG brick repair service, it never happens with a Nexus device. Well, ALMOST never. I made it happen. I don't even know what I did wrong, but apparently I screwed up the radio. Even the best of the best (Adam Outler) wasn't able to repair it. It happened the day after I installed a new ROM and a mod. The battery drained really fast. After it was dead, I plugged it in the charger, booted up my phone, started the browser, and BAM. Dead. Forever.
But I wouldn't worry about those things. Just don't do too much overclocking, because there are ways to screw up the hardware inside. Almost all bricks are fixable. If you can access fastboot mode you're okay. If you can't, there are still ways to fix it, but it might cost you some money. I don't know if Adam Outler's Unbrickable Resurrector tool works with the N4, but that's also an option if you think you really screwed up.
Click to expand...
Click to collapse
My N4 its bricked, I contact Google for RMA. Now, my history...
N4 bought 13/nov.
-Rooted with Nexus 4 Toolkit
- ROMS installed: 1- Stock (default) 2- Minco 3- Xylon (when i got bricked)
- Kernels:1- Stock (default) 2- Franco 3- Faux (when i got bricked)
In kernel Ops: (Last Faux beta kernel)
- Underclock: (YES, READ, UNDER): 1mgz at max
- Undervolt: -137 mv all freqs
- GPU Downgraded to 200mhz
- Screen settings changed
- Hapatic feedback downgraded to 50%
That was my config. Now comes the drama...
My phone was perfectly OK at less for 2 days with that kernel and ROM combination (because i've updated few days before got bricked) So, my phone even with the downgrade config was so smoth and everything was perfectly ok.... the night of new year, when I was taking a shower, my N4 was charging SO SLOW, i dont give a f*ck and continue my night so normal, then I went out to my gf house, i have like 30 % and decide to charge again, starts charging slow again, now im worried about it so i decide to restart the phone, and problem still there... but now the device was overheating so much and the phone got discharged because i got to go, when I come to my house in the morning, i put the charger, the only thing it do is blink red led, nothing else.
Conclusion:
When your phone got bricked doesn't mean you have the guilty, because mine was STABLE for at least 2 days, for my, it was an hardware prob.
Now, the only way, RMA.
So if I was you, I lock my bootloader again.
Hey there XDA Samsung Galaxy S4 Community, I come to you today to ask, If something should go wrong(mainly a user error) while flashing a new rom/kernel and my phone starts bootlooping like a fruit bowl, is there a fail safe for this phone? Like for the Samsung Infuse 4g no matter what you messed up on the phone all you had to do was put it into download mode and flash stock rom via Oden. It was pretty much unbrickable unless you totally noobed something xD So I was just wondering if this beautiful sex god of a phone had the same fail safe. Get back at me
MaliciousIntent69 said:
Hey there XDA Samsung Galaxy S4 Community, I come to you today to ask, If something should go wrong(mainly a user error) while flashing a new rom/kernel and my phone starts bootlooping like a fruit bowl, is there a fail safe for this phone? Like for the Samsung Infuse 4g no matter what you messed up on the phone all you had to do was put it into download mode and flash stock rom via Oden. It was pretty much unbrickable unless you totally noobed something xD So I was just wondering if this beautiful sex god of a phone had the same fail safe. Get back at me
Click to expand...
Click to collapse
Same with the GS4, if you get to download mode, flash back to stock with odin, no issues here.
TheAxman said:
Same with the GS4, if you get to download mode, flash back to stock with odin, no issues here.
Click to expand...
Click to collapse
Awesome. I've been wondering that, Now I feel well enough about it to finally flash a ROM on my new baby xD
MaliciousIntent69 said:
Awesome. I've been wondering that, Now I feel well enough about it to finally flash a ROM on my new baby xD
Click to expand...
Click to collapse
Whatever rom you choose, just make sure you read, you will be ok, in fact, the hard brick is hard to do on this phone, but it could happen. Good luck
Some of us can testify that soft bricking your device when you start out definitely makes you start reading a lot more. LOL Unless you try flash a rom from a totally different device, you should be able to reboot into recovery and just wipe and restore. If I don't bootloop more than once a week I'm not flashing enough.
Phoneguy589 said:
Some of us can testify that soft bricking your device when you start out definitely makes you start reading a lot more. LOL Unless you try flash a rom from a totally different device, you should be able to reboot into recovery and just wipe and restore. If I don't bootloop more than once a week I'm not flashing enough.
Click to expand...
Click to collapse
Haha i know exactly how that is xDD I used to be an insane flashaholic on my Infuse 4G mainly because the community for that phone was amazingly large at the time.
+1
Isn't having a bootloop not a part of the process, if your not bootlooping, your not FLASHING enuf! yeah baby.
TheAxman said:
if your not bootlooping, your not FLASHING enuf! yeah baby.
Click to expand...
Click to collapse
That's a reckless attitude to have toward your $700 device. And that's fine; I'm not here to tell you how to treat your phone. However, I really don't think you should post cavalier comments like that that might teach new users to do the same.
I've owned an HTC Inspire, a Galaxy S2, and a Galaxy S4. I've flashed many roms/kernels/recoveries/modems on all of them, and not once have I ever caused a boot loop. You just have to read, and never do anything before you know exactly what it is you're doing.
mattdm said:
That's a reckless attitude to have toward your $700 device. And that's fine; I'm not here to tell you how to treat your phone. However, I really don't think you should post cavalier comments like that that might teach new users to do the same.
I've owned an HTC Inspire, a Galaxy S2, and a Galaxy S4. I've flashed many roms/kernels/recoveries/modems on all of them, and not once have I ever caused a boot loop. You just have to read, and never do anything before you know exactly what it is you're doing.
Click to expand...
Click to collapse
Same here. Never once bootlooped. There's a difference between constantly flashing and correctly flashing.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
plwalsh88 said:
Same here. Never once bootlooped. There's a difference between constantly flashing and correctly flashing.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
There's also a difference between flashing things that are untested / should work and things that have been fleshed out so to speak.
I flash a lot of untested stuff (mostly built by others, some by me) and have boot looped my phone at least 10 times since 5 May when u bought it.
Bootloops are not damaging as the software is juat not loading (hence the loop). As long as you dont mess with bootloaders you should b3 fine (and loki is not touching the bootloader just feeding it false info)
Sent from my GT-I9505 using Tapatalk 4 Beta
mattdm said:
That's a reckless attitude to have toward your $700 device. And that's fine; I'm not here to tell you how to treat your phone. However, I really don't think you should post cavalier comments like that that might teach new users to do the same.
I've owned an HTC Inspire, a Galaxy S2, and a Galaxy S4. I've flashed many roms/kernels/recoveries/modems on all of them, and not once have I ever caused a boot loop. You just have to read, and never do anything before you know exactly what it is you're doing.
Click to expand...
Click to collapse
All it is, is a statement saying that you are going to get bootloops, guess you guys are perfect. but they happen, easily recoverable, so I think my statements holds true.
Moving along!
_Dennis_ said:
There's also a difference between flashing things that are untested / should work and things that have been fleshed out so to speak.
I flash a lot of untested stuff (mostly built by others, some by me) and have boot looped my phone at least 10 times since 5 May when u bought it.
Bootloops are not damaging as the software is juat not loading (hence the loop). As long as you dont mess with bootloaders you should b3 fine (and loki is not touching the bootloader just feeding it false info)
Sent from my GT-I9505 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Completely agree and knew that would be the response. But based on their posts it sounded more like ROM hopping than testing.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Please read forum rules before posting
Questions and help issues go in Q&A and Help sections
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Reset in recovery mode and TWRP have a much....
Mainly in file folders. Its normal?
Enviado de meu Nexus 7 usando o Tapatalk 2
fgenari said:
Reset in recovery mode and TWRP have a much....
Mainly in file folders. Its normal?
Enviado de meu Nexus 7 usando o Tapatalk 2
Click to expand...
Click to collapse
Really? It's a recovery. You're only going to see it at most a few times a day. Yes, it is obviously going to be laggier than the android OS.
Keion said:
Really? It's a recovery. You're only going to see it at most a few times a day. Yes, it is obviously going to be laggier than the android OS.
Click to expand...
Click to collapse
Yes....really. The lagginess on one or a few devices could be a sign of a future problem. A bad flash, a bad download........ Please realize that even a problem you consider small may merely be a symptom of something bigger. Now, back to the original question....
Yes, i get a bit of lagginess. Not in file folders, but when it opens. When booting into recovery, mine will sit at the twrp splash screen for upwards of 30 seconds. All versions i have tried does the same. My other two N7s dont do it. So far, nothing more dramatic has occured, so i am not to worried yet.
Sent from my Nexus 7 using xda premium
rebel1699 said:
Yes....really. The lagginess on one or a few devices could be a sign of a future problem. A bad flash, a bad download........ Please realize that even a problem you consider small may merely be a symptom of something bigger. Now, back to the original question....
Yes, i get a bit of lagginess. Not in file folders, but when it opens. When booting into recovery, mine will sit at the twrp splash screen for upwards of 30 seconds. All versions i have tried does the same. My other two N7s dont do it. So far, nothing more dramatic has occured, so i am not to worried yet.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Vey thanks guys!!!
rebel1699 said:
Yes....really. The lagginess on one or a few devices could be a sign of a future problem. A bad flash, a bad download........ Please realize that even a problem you consider small may merely be a symptom of something bigger. Now, back to the original question....
Click to expand...
Click to collapse
I don't think that's how it works.
Read a book, eggnog.
Keion said:
I don't think that's how it works.
Read a book, eggnog.
Click to expand...
Click to collapse
Thats exacy how it works. Certain behavior can be indicitive of software, or even hardware failures, or either in the future. That is the entire point of TROUBLESHOOTING. Either way, questions like this are the point of the sub forum. It is what it was made for. Hence the name Q&A. And yes, I read books. It was kinda required while attaining my electronics engineering degree. If you dont have a constructive response to an honest question, just move on.
And as Forrest Gump says- "And thats all i got to say about that"
Op- If the problem persists or gets worse, you may want to redownload twrp and reflash to make sure you did not have a bad flash last time. If that does not work, then erase the recovery partition through fastboot to make sure there are no partition errors. Then while still in fastboot, flash twrp again. Its no sure thing, but it will eliminate repairable partition problems. Mine browses the filesystem very quickly and smoothly. Just gotta try different things till you find the root issue.
Sent from my SAMSUNG-SGH-I727 using xda premium
rebel1699 said:
Thats exacy how it works. Certain behavior can be indicitive of software, or even hardware failures, or either in the future. That is the entire point of TROUBLESHOOTING. Either way, questions like this are the point of the sub forum. It is what it was made for. Hence the name Q&A. And yes, I read books. It was kinda required while attaining my electronics engineering degree. If you dont have a constructive response to an honest question, just move on.
Click to expand...
Click to collapse
No it's not. If you got a "bad" recovery, then it simply won't work. Smoothness of the thing won't be impacted.
Moreover, if it works, and flashes stuff fine, then there is no reason to troubleshoot. This really should be obvious, especially to someone with an "electronics engineering degree".
What, you gonna freak out about a bad flash, everytime your device drops a frame?
Step it up, kouhai.
Keion said:
No it's not. If you got a "bad" recovery, then it simply won't work. Smoothness of the thing won't be impacted.
Moreover, if it works, and flashes stuff fine, then there is no reason to troubleshoot. This really should be obvious, especially to someone with an "electronics engineering degree".
What, you gonna freak out about a bad flash, everytime your device drops a frame?
Step it up, kouhai.
Click to expand...
Click to collapse
An error in a filesystem can indeed cause shudder. Perhaps you can explain why his lags in the file browsing, yet mine does not. Maybe why mine spends 30 seconds at twrp splash, and almost all others do not. Considering you never asked any questions before you decreed his problem was nothing invalidates you automatically. How long is the lag? 1 second? 2-3 seconds? Even longer? What version of twrp is he running? Has he tried a reflash? You told him he had no issue with 0 info. It was just plain lazy. And yes, a bad flash or small errors can indeed still allow the recovery to run, but with glitches. Devs resolve alot of problems here by identifying a bad flash. It is one of the most common issues. One bit out of place during a flash can cause it to run, but with strange and undesireable behavior. You really need to educate yourself.
Now, impart your invaluable knowledge to the questions above, and then maybe ill take you seriously. Considering he ignored you, that should tell you something. Btw, does file browsing lag in twrp for you?
But to be fair, I am running a custom multirom version, further customized by the added timur kernel to allow host mode charging while in recovery.
Sent from my SAMSUNG-SGH-I727 using xda premium