So, last night i was using my tablet and it started acting weird. youtube videos not loading, apps locking up, etc. So I decided to reboot my tab to resolve it. But now it wont boot. The boot animation stops part way through, and after a while it turns itself off.
My next thought was to go to recovery, but that doesnt work either. When I try to enter recovery it hangs at the twrp splash screen. At this point I dont know what to do
Any ideas?
What ROM were you on?
Sent from my Infamous Tab.
slim bean
Bigandrewgold said:
slim bean
Click to expand...
Click to collapse
It sounds like a bad flash. Perhaps try using Odin to reflash a working recovery again? Then do a complete wipe and restore a backup to get working again.
If that doesn't work it sounds like its stock firmware time...
Sent from my Infamous Tab.
djmatt604 said:
It sounds like a bad flash. Perhaps try using Odin to reflash a working recovery again? Then do a complete wipe and restore a backup to get working again.
If that doesn't work it sounds like its stock firmware time...
Sent from my Infamous Tab.
Click to expand...
Click to collapse
I just flashed cwm and it loads, but when trying to wipe data it stalls and eventually crashes, guess ill try stock firmware
ugh, flashed stock in odin and it is stuck at this screen, not moving, and its been there for a good 5 minutes
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Damn. If you have flashed stock firmware you will have stock android recovery...however using it is rather scary because of the potential for the emmc brick bug. If you weren't able to wipe the device before flashing the stock firmware you're probably locking up on a bad driver or lib or something.
Do you have adb access to the device? Are you able to pull a Logcat?
Sent from my Infamous Tab.
ok, I got it working. I rebooted from that screen, did a factory reset in stock recovery, flashed cwm, and rebooted a few more times and I finally was able to get it booted up.
Bigandrewgold said:
ok, I got it working. I rebooted from that screen, did a factory reset in stock recovery, flashed cwm, and rebooted a few more times and I finally was able to get it booted up.
Click to expand...
Click to collapse
Phew!!!
Yeah man, factory resets in stock recovery are really scary. Good job getting back on a custom recovery. Make sure it is a newer recovery (CWM 6+) so you are safe when you run a FR.
Get re-rooted and back into a ROM with a safe kernel too and you're golden congrats!
Sent from my Infamous Tab.
Related
I have unlocked bootloader successfully. I then used the new version of Rom Manager to flash CWM. Everything seemed good. I rebooted into Recover from Rom Manager (I can't figure out how to boot into it from startup). I then did a back up of my current image. Then i installed prebeta4.zip. Everything seemed to go great. I then wiped the cache and rebooted. The CM7 boot animation started up great, but then my screen went black and the boot animation ran again. THis is happening over and over. Does anyone have any suggestions on what to do? I would love to run CM7, but at this point i would like a phone that starts up as well Any suggestion you all got, please let me know. Thanks guys!
wipe data and reflash
how do i do that. I can't seem to figure out how to boot into recovery?
jake.perkinsr said:
I have unlocked bootloader successfully. I then used the new version of Rom Manager to flash CWM. Everything seemed good. I rebooted into Recover from Rom Manager (I can't figure out how to boot into it from startup). I then did a back up of my current image. Then i installed prebeta4.zip. Everything seemed to go great. I then wiped the cache and rebooted. The CM7 boot animation started up great, but then my screen went black and the boot animation ran again. THis is happening over and over. Does anyone have any suggestions on what to do? I would love to run CM7, but at this point i would like a phone that starts up as well Any suggestion you all got, please let me know. Thanks guys!
Click to expand...
Click to collapse
Bootloop on your phone? It seems the problem is that the phone isn't booting...
CONGRATULATIONS!!! YOU WIN!!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
also, do i just wipe the cache and then reflash the zip? Do i then wipe the cache one more time before reboot? I can't for the live of me figure out how to boot into CWM though?
jake.perkinsr said:
how do i do that. I can't seem to figure out how to boot into recovery?
Click to expand...
Click to collapse
Power on your phone while holding the volume down button till it says fastboot, then scroll down using the volume down button till you see android recovery and select with volume up.
You can only scroll down so if you pass it, loop back around.
Sent from my MB860 using xda premium
Two posts for this?
pull battery on the phone, put back in power on holding down volume
wipe data and cache and also dalvik cache, reflash and then wipe them one more time for good measures lol
Any way I can get it to boot without wiping? The problem occurred when I accidently did the 3 key method to get into cwm... forgetting you're not supposed to.. and then flashed glitch's new kernel.
Plug into computer, turn on, open command prompt, type adb shell, type reboot recovery. Next flash the kernel in the proper recovery.
good day.
chopper the dog said:
Plug into computer, turn on, open command prompt, type adb shell, type reboot recovery. Next flash the kernel in the proper recovery.
good day.
Click to expand...
Click to collapse
adb shell on the computer or phone? I can't even boot the phone.
On the computer to enter into recovery then flash kernel.
quedi12 said:
On the computer to enter into recovery then flash kernel.
Click to expand...
Click to collapse
doesn't it only work though if the phone is in usb debugging mode?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I don't know what to do. I've tried flashing cwm via odin again.. tried wiping... tried reinstalling kernel / rom. nothing but a bootloop everytime now.
There have been some problems with the Glitch Kernel and the newest Cyanogen nightlies causing it to Bootloop. The Glitch developer is aware and working on it. I had to revert back to stock and start over. For now im staying at CM7 nightly 35 and using Glitch.
DakotaS96 said:
There have been some problems with the Glitch Kernel and the newest Cyanogen nightlies causing it to Bootloop. The Glitch developer is aware and working on it. I had to revert back to stock and start over. For now im staying at CM7 nightly 35 and using Glitch.
Click to expand...
Click to collapse
X2
Had to atlas pit and repartition, then back to build 35 was the only way I could get rid of the boot loop when trying to go to the newest nightly build.
Sent from my SCH-I500 using XDA App
to fix the adb problem I had to install the drivers.. which I DID but the instructions on the wiki were wrong... so it took awhile to find where they got installed to. I finally got the newest cwm + glitch v12 kernel to work though. Took all day!!!
I had to same problem, just had to restore the CWM backup
Well i think I have screwed up beyond repair.Yesterday I had sucessfully rooted my new s4 that came with VRUAMDK. just rooted no custom roms or anything. I then loaded Titanium backup and froze the verizon update app. Installed Goo Manager and made a nandroid backup with TWRP.
Today I froze the Weather widget app among others. Decided I wanted the weather widget back, so I defrosted it. It WOULD NOT come back. So I defrosted everything. Still no weather widget. Then I thought I would just unroot and go back to stock. Followed Dark Menace's Pm instructions and followed them to the letter. When I rebooted from using superSu to unroot. I noticed a notifcation that a software update was available, obviously it was since it was unfrozen. I did not click it. But a few seconds later my phone reboots into recovery mode with TWRP I thought that was very strange. Upon completion,and booting it said "Android is being updated" Well at that point I was sick! Sure enough now I'm at VRUAME7.
What can I do? probably nothing correct?
Oh and a few minutes after all this a popup said "software update failed to complete nothing was changed" or some-such. But I'm still at me7 and I have a unlocked padlock on bootup
Lesson learned don't screw with it if it aint broke!
Oh I STILL don't have my weather widget back.
I appreciate any assistance.
Thanks,
EDIT:
I'm not really broke about being on ME7 its just that I wish I could get rid of the padlock on boot and wipe all the backups (nandroid) just in case the phone dies. At this point it will just be a paperweight.
Would a wipe data/factory reset at least get me all the way onto me7? I seem to be stuck somewhere in between.
Here's where I'm at now
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Fixed!
Flashe VRUAME7 stock restore --> booted up with padlock --> rebooted in recovery mode --> wipe cache --> booted without padlock! Now at ME7 with no update errors --> did factory reset to get rid of all the twrp and TiBU files. So at least it is working fine now.
Thanks for all the info on the site!
Hello Guys,
This evening I decided to root my phone and install Jelly Beans ROM for Samsung Verizon Galaxy S4, I began by rooting my phone using Towelroot, everything was great so far. Then I tried to install a CWm Recovery but I failed doing that, I followed a youtube video but I kept getting "loki aboot version does not match device".
I read somewhere else that I could use Safestrap as recovery, I followed all the instructions installed busybox etc...
I finally went into recovery mode and Installed Jely Beans V7. The installer ran fine and I followed all the options the installation finished and it was time to reboot, I hit reboot and the phone never came back.
All I see now is a Samsung boot screen with an unlocked padlock in the bottom, the phone keeps rebooting and I had a hard time getting into recovery, when I finally did it seems like a different recovery and only gives me the options to apply updates and to wipe data.
The android robot is dead with a red triangle.
Please help what can I do???
I take it you missed the part that you can only flash non-touchwiz roms & cwm on phones with an mdk bootloader?
Plenty of threads on here on how to fix this, I'm on my phone otherwise I'd post links
5841
rrrrrrredbelly said:
I take it you missed the part that you can only flash non-touchwiz roms & cwm on phones with an mdk bootloader?
Plenty of threads on here on how to fix this, I'm on my phone otherwise I'd post links
Click to expand...
Click to collapse
Thanks, and yes I guess i missed that part, I am still learning.
If you or any body can please post a link on how to fix it, it would be great.
Thanks!
Even Worst
To make matter worst now I have a screen that says "Firmware upgrade encountered an Issue. Please select recovery mode in Kies & try again.
I've tried Kies but it does not recognize my phone, I cannot do anything anymore.
Please help it is my only phone and I need it bad.
Thanks
Update
I tried following this instructions:
[ODIN][TAR] Complete Device Wipe/Repartition and Emergency Recovery for VRUEMJ7 Build
http://forum.xda-developers.com/showthread.php?t=2507253
I downloaded the file but cannot install it with Odin I get Fail! each time.
This are my error msgs...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please Help
You have flash the same firmware you had before you started.
Do you know what build you were on?
Sent from my NCC-1701 using Tapatalk.
Fixed!
riker147 said:
You have flash the same firmware you had before you started.
Do you know what build you were on?
Sent from my NCC-1701 using Tapatalk.
Click to expand...
Click to collapse
Sweet thanks finally fixed it! using Full-Wipe NG6
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I read a post that said this is efs factory problem. I have no network connection, no screen lock, wifi disconnected after rebooting. I know there is a way to fix by change something in /efs, but my problem is my device isn't rooted! I tried almost all methods to root this GT-I9300 like framaroot, one-click root, etc and I also tried to flash cwm through Odin
but always stuck on that step (even when tried to flashing stock ROM again)
there are no progress bar at all, even I waited for almost 20 minutes!
Can someone help me to fix this problem? Remember, my phone doesn't rooted, so please don't give me an advice that require device to be rooted. Thanks a lot
Flash cfautoroot via odin to root it. If it is completely stock just flash the latest firmware twice via odin (wipe data and cache after the first flash but before second flash.
Sent from my HTC One M9 using Tapatalk
shivadow said:
Flash cfautoroot via odin to root it. If it is completely stock just flash the latest firmware twice via odin (wipe data and cache after the first flash but before second flash.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
I flashed cfautoroot with no luck. It's totally same like when I flash cwm or stock ROM, there is no progress bar at all for about 20 minutes!
I also tried many times to flash the stock ROM and for sure already wiped data from stock recovery.
anyone?
Your nand is what's known in the trade as "f**ked". If it attempts pit mapping from a stock rom you can assume it's dead.
You can try flashing a pit file but I highly doubt it'll do anything constructive.
On the bright side it probably wasn't your fault. I'd say the nand was borked and your attempts highlighted it.
Sent from my HTC One M9 using Tapatalk
shivadow said:
Your nand is what's known in the trade as "f**ked". If it attempts pit mapping from a stock rom you can assume it's dead.
You can try flashing a pit file but I highly doubt it'll do anything constructive.
On the bright side it probably wasn't your fault. I'd say the nand was borked and your attempts highlighted it.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
so what should I do now? is there any way to fix this out?