Hi Guys,
I was trying to install a custom rom on my galaxy tab.I downloaded Rom Manager from market and was trying to take backup by booting my phone and tried to take Nandroid backup but not able to find that when I rebooted my tab.So i tried to find a app on market by searching "nandroid" and found 3 apps as a search result and I downloaded 3rd app from market.
After that I rebooted my tab and It is not coming up.It is showing samsung startup screen and then screen is active but not showing anything and keep on vibrating in every few seconds.I am not able to see anything on my screen now but I can get reboot screen with options like:-
reboot
clear cache data
wipe out all data
Please let me know what should I need to do to get my tab up and running... Its very urgent...
Thanks in advance
I'm having the same issue w/ my HTC Thunderbolt (ADR6400). I followed the directions and used the files referenced in the forums here. This is the "Easy Flash" app method. I did have the 605.6 software on the device stock from HTC. I was initially not able to get past step one (it would not actually write the files. After trying it about 5 times, it finally flashed and rebooted on its own and installed the old 1.03.605.10 software. It took a long time to finally boot back up, and now every time I try to connect it via USB w/ Debugging Mode on to do steps 2 and 3 it crashes the device and like Survivor's Tab situation, gets stuck w/ the boot-up screen
Is there a way to either A) get around this crashing-on-debugging-mode issue to finish the rooting, or B) restore it to its original firmware? At least it turns on, but I posted in this thread since the solution for him is probably the same as for me (whatever that might be). I've rooted other Linux-derived OSes before (Ie, WebOS 1.4x), and didn't have these kinds of issues. Any ideas would be most helpful to both of us.
My Device Info:
Rooted, AT&T Galaxy Note 2 running 4.1.2...no custom ROMs, kernals, tweaks or mods, etc...
The Issue:
I've been ignoring the latest OTA update that AT&T has been pushing since my device is rooted. However, unbeknownst to me at the time, my phone got into my toddlers hands last night and I'm assuming he accidentally pressed something that caused the download process to begin.
What I've Tried So Far:
The phone will boot up like normal, but when I try to select anything then the screen goes black showing nothing but the notification bar. Then after a few seconds the phone auto-reboots itself. Sometimes it hangs on the Samsung splash screen while I hear notifications going off in the background. From recovery, I've selected to wipe data/factory reset and wipe Dalvik cache, but no change. I had one Clockwork mod backup on my extSDcard that won't restore giving me and MD5 mismatch error. It was only from a couple weeks ago so it was created from this device. I'm a relatively seasoned Android OS tweaker but its been a while since I've been actively doing anything but rooting. I need some suggestions as to how I should proceed....thanks in advance
Momomuffins said:
My Device Info:
Rooted, AT&T Galaxy Note 2 running 4.1.2...no custom ROMs, kernals, tweaks or mods, etc...
The Issue:
I've been ignoring the latest OTA update that AT&T has been pushing since my device is rooted. However, unbeknownst to me at the time, my phone got into my toddlers hands last night and I'm assuming he accidentally pressed something that caused the download process to begin.
What I've Tried So Far:
The phone will boot up like normal, but when I try to select anything then the screen goes black showing nothing but the notification bar. Then after a few seconds the phone auto-reboots itself. Sometimes it hangs on the Samsung splash screen while I hear notifications going off in the background. From recovery, I've selected to wipe data/factory reset and wipe Dalvik cache, but no change. I had one Clockwork mod backup on my extSDcard that won't restore giving me and MD5 mismatch error. It was only from a couple weeks ago so it was created from this device. I'm a relatively seasoned Android OS tweaker but its been a while since I've been actively doing anything but rooting. I need some suggestions as to how I should proceed....thanks in advance
Click to expand...
Click to collapse
In Settings/About Device: you can tell which build you have or if you had the update or not. The phone was prolly shipped with MA4..or MC3. The newer update was MH3.
I don't know if updating if would cause that issue though.
Mebby it's something that the toddlers did or coincidental hardware issue.
You might need a reset from in the device..under Setting/Backup Reset..this may erase all you data and info on the SDCard
If you are still having issues...mebby an Odin back to stock MA4 and test again
qkster said:
In Settings/About Device: you can tell which build you have or if you had the update or not. The phone was prolly shipped with MA4..or MC3. The newer update was MH3.
I don't know if updating if would cause that issue though.
Mebby it's something that the toddlers did or coincidental hardware issue.
You might need a reset from in the device..under Setting/Backup Reset..this may erase all you data and info on the SDCard
If you are still having issues...mebby an Odin back to stock MA4 and test again
Click to expand...
Click to collapse
Once the phone boots and the pre-home screen displays ready to swipe. Once I swipe, like I'm trying to access the home screen, the entire display goes black except the status/notification bar. If I power off the screen and back on again, the swipe screen displays again, swipe it again, it goes black again. The status bar, volume selection pop-up display on the screen are responsive and functional. I just can't navigate through the phone whatsoever past the swipe screen. It's like the home screen UI/launcher doesn't exit. Previous to the problem, I was running Smart Launcher Pro with no problems....this is by far the weirdest issue I've ever run across
Momomuffins said:
Once the phone boots and the prOute-home screen displays ready to swipe. Once I swipe, like I'm trying to access the home screen, the entire display goes black except the status/notification bar. If I power off the screen and back on again, the swipe screen displays again, swipe it again, it goes black again. The status bar, volume selection pop-up display on the screen are responsive and functional. I just can't navigate through the phone whatsoever past the swipe screen. It's like the home screen UI/launcher doesn't exit. Previous to the problem, I was running Smart Launcher Pro with no problems....this is by far the weirdest issue I've ever run across
Click to expand...
Click to collapse
It could be a launcher issue.. perhaps an inverted color scheme
Flash a different launcher or rom in cwm..or odin to stock
Or push a different launcher then install and reinstall your own
qkster said:
It could be a launcher issue.. perhaps an inverted color scheme
Flash a different launcher or rom in cwm..or odin to stock
Or push a different launcher then install and reinstall your own
Click to expand...
Click to collapse
Just did Odin to Stock...successful...BUT the phone booted up and I have the "Android is upgrading...<starting apps.>" box...its been sitting there for at good 15min+...
Also...once the screen went black earlier the phone would reboot even after wiping it clean of absolutely everything...something somewhere got seriosuly borked...
Momomuffins said:
Just did Odin to Stock...successful...BUT the phone booted up and I have the "Android is upgrading...<starting apps.>" box...its been sitting there for at good 15min+...
Click to expand...
Click to collapse
***UPDATE***
Pulled the battery and booted into stock recovery....wiped data/factory reset/wipe cache...reboot...I was able to nav further into the UI than I was previously able to like into the SMS app and system settings then BAM...auto-reboot again and the famous "Android is upgrading..." box is back...sitting there...again...this is insanity...it's no longer rooted, stock firmware, no data aside what's generated during the initial device set-up... SAME shiz as far as the reboot and the spontaneous, hanging OTA upgrade...
Hello, there.
Get prepared for a lot of bad bad stuff..
So, my Galaxy Nexus was running on a CM-11 Snapshot build, with AOSP kernel. Yesterday, out of the blue, the phone started to get terribly slow and not responsive at all. After a few minutes, it restarted, only to do the same. A couple of minutes maybe, booting up, then get slow and reboot - it did this constantly, and it still does.
I have tried to go into clockworkmod recovery - wiped cache, wiped dalvik cache, wipe user data (factory reset). The phone booted up again, but my apps, etc. were still there! Nothing had happened. I did it a couple of times, but nothing at all.
Then, I have found a .zip file that was still on my memory, with the latest snapshot I had installed. I tried installing it with the install from sd card option, but when it loaded up again, I was still seeing the same apps, background etc.! Nothing had happened and no error message.
Decided to leave the "custom" days behind, I downloaded the stock image for my Gnex. However, since it is a yakjuxw build, I had to flash the yakju option - so not the ideal "stock" package. Using the google installer, I was unable to proceed, since the bootloader number was different than the one that the installer expected, so it exited.
I have found online the amazing Nexus Root Toolkit from WugFresh. I tried to flash it from there, enabling the "force flash" option.
It started out ok.. But when it went to the "system" portion, it took 25 minutes (!) to complete and then in the "user data" portion, it said "write failure".
Still, rebooted and I was still seeing my apps etc. What on earth is happening?
Honestly, I would expect that it would be bricked by now, with all these rom flashes and factory resets. I even tried flashing the stable CM version for it, but still nothing had changed.
Any help would be greeeeatly appreciated.
Yeah im pretty sure your emmc is fried. So you have two options: buy a new phone or a new motherboard. You van check by locking the bootloader if its still unlocked upon reboot your emmc is fried..
Sent from my Galaxy Nexus using XDA Free mobile app
I runned "fastboot oem lock' from my command line, and I got the status "OK".
Then I pressed "restart bootloader" on my phone, but it still says "lock state - unlocked".
So I suppose, I should let it rest in piece, or change the motherboard?
I think a motherboard is more expensive than a new phone. If it is just let it die. If it isnt you can buy a new motherboard and swap it. But I dont think that is a smart move now. The moto g for example is a awesome phone for (i think) almost the price of a new mobo.
Sent from my Galaxy Nexus using XDA Free mobile app
same problem here
It makes me wonder, I'm having the exact same issue just a couple of days later. Is this the planned obsolescence thing?
withend said:
Hello, there.
Get prepared for a lot of bad bad stuff..
So, my Galaxy Nexus was running on a CM-11 Snapshot build, with AOSP kernel. Yesterday, out of the blue, the phone started to get terribly slow and not responsive at all. After a few minutes, it restarted, only to do the same. A couple of minutes maybe, booting up, then get slow and reboot - it did this constantly, and it still does.
I have tried to go into clockworkmod recovery - wiped cache, wiped dalvik cache, wipe user data (factory reset). The phone booted up again, but my apps, etc. were still there! Nothing had happened. I did it a couple of times, but nothing at all.
Then, I have found a .zip file that was still on my memory, with the latest snapshot I had installed. I tried installing it with the install from sd card option, but when it loaded up again, I was still seeing the same apps, background etc.! Nothing had happened and no error message.
Decided to leave the "custom" days behind, I downloaded the stock image for my Gnex. However, since it is a yakjuxw build, I had to flash the yakju option - so not the ideal "stock" package. Using the google installer, I was unable to proceed, since the bootloader number was different than the one that the installer expected, so it exited.
I have found online the amazing Nexus Root Toolkit from WugFresh. I tried to flash it from there, enabling the "force flash" option.
It started out ok.. But when it went to the "system" portion, it took 25 minutes (!) to complete and then in the "user data" portion, it said "write failure".
Still, rebooted and I was still seeing my apps etc. What on earth is happening?
Honestly, I would expect that it would be bricked by now, with all these rom flashes and factory resets. I even tried flashing the stable CM version for it, but still nothing had changed.
Any help would be greeeeatly appreciated.
Click to expand...
Click to collapse
Google's secret weapon to make us buy the new Nexus 6.
I don't know why that happens though - dual core processor, with this amount of RAM. Tech-specs-wise, GNex has nothing to be jealous about than mid-range smartphones right now.. Unless, the CPU architecture from 2012 is so bad that it can't run properly today's apps.
Hey guys, I have these problems too. Just bought the Galaxy Nexus from a friend for €15 (cracked screen) and from the moment I turn it on, (sometimes at Nexus logo, sometimes on lockscreen.. ) it reebot itself. Again and again.
Unlocked the bootloader by toolkit or manually by fastboot but after the reboot it's locked again, as you said. I've tried Odin too with same results. The strange thing it's that it took time to do things but after the reboot, it's like I haven't done anything. I mean, even if I delete an app, or wipe data from recovery (not custom), when it turns on, it's always the same.
It's like a challenge to me. Anyone can help? I can't just give up >.<
Inviato dal mio Nexus 4
What the hell, just finished answering another thread with same issue (forum.xda-developers.com/galaxy-nexus/help/wipe-flash-restarting-help-t2908788). Happened to me last week, very same, never touched the phone, always stock.
What the hell is going on here???
Is there any way to get any log files to determine what the hell is going on?
Mine opens up for a few minutes, maybe 3-4 and it seems to be working well.. It gradually gets unresponsive and ultimately restarts.. So, if there is anything to do during these 3-4 minutes, I would be glad to know..
If you have backed up your sdcard data to your computer, and are prepared to start from scratch (i.e. flashing bootloader and recovery via fastboot, etc.), you can do a full erasure with "fastboot -w" in fastboot mode. This has worked for me in the past to fix data corruption, of which it sounds like you may be a victim. See if that works, but make sure you've backed up your sdcard backups and other data you want to keep first!!!!!!!!
7175 said:
If you have backed up your sdcard data to your computer, and are prepared to start from scratch (i.e. flashing bootloader and recovery via fastboot, etc.), you can do a full erasure with "fastboot -w" in fastboot mode. This has worked for me in the past to fix data corruption, of which it sounds like you may be a victim. See if that works, but make sure you've backed up your sdcard backups and other data you want to keep first!!!!!!!!
Click to expand...
Click to collapse
Already tried, uneffective. Everything, no matter how low level (e.g. Odin) has no effect, like the memory is write-protected. I've read elsewhere this means the eMMC is fried, but if you go backwards in this forum you see many ppl had the very same problem in the past few days/weeks. Very strange indeed.
I'm having exactly the same issue, was running CM11 mod too. Could it be a cyanogen fail?
Atreb92 said:
I'm having exactly the same issue, was running CM11 mod too. Could it be a cyanogen fail?
Click to expand...
Click to collapse
No. I've always been on stock.
fabrice79 said:
No. I've always been on stock.
Click to expand...
Click to collapse
But could it really be a hardware fail? It's pretty strange tho that multiple device have the same hardware issue in such a short time difference
Atreb92 said:
But could it really be a hardware fail? It's pretty strange tho that multiple device have the same hardware issue in such a short time difference
Click to expand...
Click to collapse
That's what I say, but just go backwards and have a look at older post. I subscribed to ~10 posts until 15 Oct then I got tired of browsing backwards...
I'm allready looking at older posts thats why i'm saying it's pretty strange that there is a massive hardware fail for this many devices. If it's a software fail there must be a solution somehow.
Same problem by 31th December...
Yeah, i have the same problem since august 2014. This thread confirmes for me, that my Gnex is really dead. It is sad, it served my very well and i wanted to use it as secondary phone and as mobile hotspot.
Same for me at the beginning of december
This problem I've faced one time and that meant that EMMC is fried, as fellow members said earlier.
If you overwrite the storage and reboot then everything's the same means that you can't write (somehow) thus emmc is dead. Write failure also means that EMMC is dead.
It's really sad, but that's it
Hi, I just updated to 2.20.40.139 on my stock ROM. Then selected the option encrypt device. Now If I change the theme to any one of the ZENUI theme provided in the system itself I face strange problems mainly on lock screen. The lock screen is now totally blurred,if I have set a PIN or a Pattern I can not see them , thus it is quite problematic to unlock the device. Other problems include laggish animation, distorted image & video in any application including system boot or start up.
Any one facing the same problem.
Any one with a solution ...
please guide me.
I don't have any issues except for installation if xposed. I believe its the encryption.
Sorry that i can't help. One suggestion is to wipe cache and dalvik.
Tiongkia said:
I don't have any issues except for installation if xposed. I believe its the encryption.
Sorry that i can't help. One suggestion is to wipe cache and dalvik.
Click to expand...
Click to collapse
Thanks buddy, I once again reset the mobile now without encryption. It's working fine now with all the themes and personalisation option with background change in phone and dialer also no issue now at boot or start up screen. All animations , image & video all OK.
Thanks again...it was the encryption that caused all those issues.
Very sorry to say that the issue arises again and again.
I applied full 1.12gb ROM wiped Cache partion so many times. When I do so initially it is OK like the problem has been resolved I become happy but sadly after 1 hour or so it's the same issue.
I observed that 2/7 part (Upper part) of the screen is OK while the lower 5/7 part of screen freezes ...it is seen that the last screen was frozen at shut down becomes the first screen after I restart the device. For example as I use 2 layer mode (All apps drawer mode with gride size 5*5 ) the uper 1 row is free from the bug and works as per my wish while lower 4 rows is freezed in bar code style. the same bar code style is seen even in fast boot mode or in recovery mode.
Somebody suggested it might be display / screen related hardware issue......but I wonder how hardware related issue does not affect in some apps like SMS and other apps why does it gets resolved for one hour or so after full firmware updation.
Now i'll try to downgrade to 2.20.40.97 again and see if it reinstate me to earlier bug free device and a happy end user.
I hope some geeks out there might have good suggestion and must help me.
Thanks.
A bit of backstory: I was tasked with "reviving" a couple of Samsung tablets, of which my main focus has been an old SM-T210.
The whole idea was to utilize custom ROMS to get it working properly again (surprise surprise, it didn't work.)
Alas, I followed the summary of about four instructional videos on how to run TWRP on the device. I had made a backup of the system and everything had been going well... Until I wiped everything on the device and decided to install a new ROM.
As it turned out, I found it next to impossible to find a new ROM to run on the afforementioned device. This meant I had to re-install the backup to get it working. This recovery, however, brought with it multiple problems.
Firstly, the power button does not function properly anymore (ie. It doesn't display the power off and restart functionality, rather turning off the tablet completely). Secondly, an app called "Factory mode" appears; when opened it looks like a miscoded calculator with no actual functionality whatsoever. Finally, and most concerning, whenever on the home menu or the app drawer, a notice with black background yellow letters appears; it reads the specs of the tablet. It doesn't take up all the screen space, nor does it appear when utilizing any application.
I am confused and quite concerned about these problems, and wanted to ask: can anyone help me with this? Is there even a fix to it?
archaicAbystoma said:
A bit of backstory: I was tasked with "reviving" a couple of Samsung tablets, of which my main focus has been an old SM-T210.
The whole idea was to utilize custom ROMS to get it working properly again (surprise surprise, it didn't work.)
Alas, I followed the summary of about four instructional videos on how to run TWRP on the device. I had made a backup of the system and everything had been going well... Until I wiped everything on the device and decided to install a new ROM.
As it turned out, I found it next to impossible to find a new ROM to run on the afforementioned device. This meant I had to re-install the backup to get it working. This recovery, however, brought with it multiple problems.
Firstly, the power button does not function properly anymore (ie. It doesn't display the power off and restart functionality, rather turning off the tablet completely). Secondly, an app called "Factory mode" appears; when opened it looks like a miscoded calculator with no actual functionality whatsoever. Finally, and most concerning, whenever on the home menu or the app drawer, a notice with black background yellow letters appears; it reads the specs of the tablet. It doesn't take up all the screen space, nor does it appear when utilizing any application.
I am confused and quite concerned about these problems, and wanted to ask: can anyone help me with this? Is there even a fix to it?
Click to expand...
Click to collapse
sounds like your best bet is to download the full firmware set and install with Odin. Odin 3.07 works best for this tablet.
Latest 4.4.2 Firmware
Odin v 3.07
gr8nole said:
sounds like your best bet is to download the full firmware set and install with Odin. Odin 3.07 works best for this tablet.
Latest 4.4.2 Firmware
Odin v 3.07
Click to expand...
Click to collapse
After test: Ok, I have set it back to og firmware. Sadly the screen still shows. I was finally able to take a pic:
https://imgur.com/GRsQoLf
. (not letting me embed)
archaicAbystoma said:
After test: Ok, I have set it back to og firmware. Sadly the screen still shows. I was finally able to take a pic:
https://imgur.com/GRsQoLf
. (not letting me embed)
Click to expand...
Click to collapse
If you do a google search for ”Samsung exit factory mode” you will find several videos/posts with options.