I have a Samsung Galaxy tab 2 GT-P5110 which I had successfully installed CM12 onto. I decided to set up work email which insisted that I encrypt the device. I believe that the process completed successfully.
At that point I decided that I would like to flash the device with CM12.1. Restarted the process (Factory reset, Wipe Cache, Wipe dalvik cache) and flash the new CM12.1 zip file from external SD card.
I cannot now get to the recovery mode and the device doesn't always boot into anything recogniseable. The screen goes black and blacker! I have manaed to get to the CM logo and then a screen asking me for the PIN for the encryption. The next screen tells me that the PIN is right but the data is corrupt. It gives me the option to "RESET TABLET" but that really doesn't do anything and won't let me in to the recovery menu.
I can get into the Download mode and connect Heimdall up to it.
Is there anything that anyone can point me at that will help me to unbrick it?
I hope I've passed on enough information to help. It seems to me I need to somehow re-format the internal SD but I can't get to any menu that will allow me to do that.
Any thoughts anyone?
Ta
Fixed It
I seem to have fixed it. I flashed the CWM Recovery rather than the recovery that I had been trying to use and I got control of the device back. Not sure why that made a difference but this time the Android Robot came on screen with the 3D polygon rotating inside it and it seems to be running correctly now and updated to Android 5.1 ... Magic!
Related
My friend has a Captivate. He lost all his google apps, android market, gmail, etc. He flashed gapps.zip from his recovery and now his phone is not working right. When he flashed a new rom to his phone, and it brought up the welcome screen it shows it for about 2 seconds and then reboots. He is also almost unable to access the recovery becuase of this, but even when he finally was able to access it and wipe everything, dalvik, cache, data/system, it still has issues. Nothing is fixing the issues from the gapps.zip. He was wondering if there is a way to wipe his entire phone from a update.zip file. Any help would be appreciated. Thank you in advance.
Please note that even when he wipes everything in recovery and flashes a new ROM, it still reboot on the welcome screen and he is unable to resolve this issue.
Ok, so he has now wiped all cache and system files, now instead of showing teh galaxy S logo with the cyanogen logo underneath, it shows just the AT&T screen, but it will not go any furhter, it just sits there. He says that because he is now unable toget into android he cannot access the recovery and the volume up/down is not responding. Is his phone Bricked?
Have you used Odin 1-click to revert back to stock?
had my friend use the Odin 1 click and he said it still did not work. He cannot get the volume up/down trick to work, when before all this it worked just fine. I am going to guess that the only thing he could try is the jig method. He swaers that Odin3 is not doing anything
Hi,
This is my first post on this website. I have owned a RCA Tablet (RCT6378W2 purchased on Black Friday from Walmart) for about 9 months now. Last night, while using it, it sort of stopped for about a minute. Then the screen had some lines on it, and the unit restarted itself. However, after this, it could not get past the RCA Boot Screen with the dogs on it. I tried leaving on this screen overnight with no success. Because the unit turns on and hangs on the boot screen, I figured it was likely a software or operating system corruption issue. Since then, I have figured out how to enter the recovery system v4.2.01 (holding volume + and Power). I have tried:
1. Wipe Cache Partition --- did not resolve problem
2. Wipe Data/factory reset --- seems to have been successful, but still not boot.
3. Apply update from cache -- there are no choices available to choose from.
It seems that unless I can find a way to make a self-booting SD card (is that possible?), then I am stuck with only 3 options (apply update from ADB, Update RKimage from external storage, and apply update from external storage). I have read many threads and websites, but have had no success. It seems that these are some of my obstacles:
1. I cannot seem to find a stock RCA rom image for this device. It appears that RCA has not made these available as other manufacturers have done. If you are able to find this, please send me a link!
2. I have tried to make a self-booting SD card using Phoenix Card, but can't find an .img that works with it. I have also tried using a generic sd card image and custom rom to install, but have failed at that. I have never rooted a device before or installed a custom rom.
3. I have tried looking for custom roms, but can't find one that is compatable with this tablet (seems they are mostly for the big name tablets). I have tried downloading Cyanogenmod for Nook Color (I heard this would work), but the recovery system does not seem to allow for any other firmwares to be installed (unless I am doing something wrong)
4. This tablet is not rooted, nor has the developer tool options been enabled (which I cannot do now that it doesn't boot)
Do you have any ideas? As stated, I am new to all of this, so please answer in detail if you can. Please help!
Hello to everyone, posting this here as I don't have access to ask in the forum post for BlissPop - I.E fresh user
I'm having issues with my "recalled" shield tablet (wifi), I had it flashed to BlissPop successfully previously but when I tried reflashing it the other day I was met with a major roadbump: It just won't load the ROM.
The tablet freezes at the screen following the installing and optimization of each application - basically my screen is stuck at a small wall of text saying the following:
"BlissPop is starting...
Powered by Team Bliss
Starting apps.
Please wait for the optimization process to finish."
And before you ask, yes I have waited long enough (left it on through the night just to be sure - this thing won't load).
My procedure is as follows.
Bootloader is CWM and it is rooted beforehand.
1st off going into recovery mode.
#2 Wipe data/cache/dalvik cache - done
#3 Installed BlissPop via sideload, then gapps_pico afterwards (I've tried wiping cache+dalvik before installing gapps to no help.)
#4 Rebooting from CWM, here I've tried both allowing and denying CWM to "fix" root settings.
I've tried the first ROM I installed (when wifi/lte versions were available) and the newer releases - same problem with both.
After this I am met with this screen that won't budge, anyone got a possible solution to this issue?
Hey I just received my replacement tablet and was going through this process too. I did some digging around and found / remembered that having an external SD card socketed can cause this problem. So I powered my device off, removed the card and then rebooted without major issue.
Hope this helps.
I don't have any SD card in my tablet though, thanks anyways.
Did you format system?
If not then do format system/data/cache
Sent from my P4S using Tapatalk
Tried doing a format of system as well as data/cache/dalvik, still getting same result :/
Not sure its still helpful or not...i saw the xda thread regarding to this thread and whoever tried to flash the last zip got stuck at boot. So I'm guessing if you will flash a different one (by this time maybe they upload a new one) maybe you could get rid of it..
Sent from my P4S using Tapatalk
When I switched to BlissPop I had to format /data because TWRP was unable to wipe it. TWRP offers that option unter "advanced wipe". Might be the same with CWM.
any help my phone stuck on this boot loop and i dont know what to do now , any fix ? i dont wanna have broken phone i did everything that u guys said nothing works
Hello everyone. I am an old member, seeing as I registered almost four years ago, but I guess either your database was refreshed and it lost my username, or I only lurked. So, as the title suggests I have one of those lowly, inexpensive, down right cheap Kyocera phones. Here is what I have figured out so far. I was able to root it using Kingroot. That went splendidly, though because of my over adventurousness I decided to swap some apps out. I added a new launcher to the /system/app folder and wanted to upgrade the com.android.settings.apk with one from a newer build. This phone (was) running Android 4.0.4 Kyocera release r77 build date 2013. Apparently Kyocera loves to lock the bootloader so if I was able to spin a custom system rom I wouldn't be able to flash it. Another thing which discovered was upon boot up the system checks the integrity of app the system apps. If one of them fails the check it will not boot the system fully. I was able to recover the stock boot/recovery/system roms from a thread on here, but I seem to be stuck in a soft brick loop. One thing that another thread said, the thread that had the rom images, it said that you could used ADB to flash the roms to the phone. Thing is, when I boot the phone it restarts, and if I put it into recovery mode (press and hold volume down plus power for ten to fifteen seconds) the only options I have are "reboot system now", "wipe data/factory reset", "wipe cache partition." There is no "flash update from sd card" or wipe dalvik cache option. As I have said before, I could try to flash the rom to it using adb but I believe that wiping the system partition unset the USB debugging setting. When I connect it to my computer windows device manager notices the kyocera removable device for a second then as the phone reboots it goes away. Setting it into recovery mode does not make it show up in windows. Is there any way I can flash the stock rom onto it? Any android sdk or adb trick I can use that can boot it into some recovery mode? I was trying to see if I can get it to boot into download mode but seeing as it has soft keys and not a physical home button I do not know if I can manage that. I was thinking that maybe they tied one of the physical keyboard buttons to the home button but I have yet to uncover that one. Any help would be appreciated.
Zestypanda said:
Hello everyone. I am an old member, seeing as I registered almost four years ago, but I guess either your database was refreshed and it lost my username, or I only lurked. So, as the title suggests I have one of those lowly, inexpensive, down right cheap Kyocera phones. Here is what I have figured out so far. I was able to root it using Kingroot. That went splendidly, though because of my over adventurousness I decided to swap some apps out. I added a new launcher to the /system/app folder and wanted to upgrade the com.android.settings.apk with one from a newer build. This phone (was) running Android 4.0.4 Kyocera release r77 build date 2013. Apparently Kyocera loves to lock the bootloader so if I was able to spin a custom system rom I wouldn't be able to flash it. Another thing which discovered was upon boot up the system checks the integrity of app the system apps. If one of them fails the check it will not boot the system fully. I was able to recover the stock boot/recovery/system roms from a thread on here, but I seem to be stuck in a soft brick loop. One thing that another thread said, the thread that had the rom images, it said that you could used ADB to flash the roms to the phone. Thing is, when I boot the phone it restarts, and if I put it into recovery mode (press and hold volume down plus power for ten to fifteen seconds) the only options I have are "reboot system now", "wipe data/factory reset", "wipe cache partition." There is no "flash update from sd card" or wipe dalvik cache option. As I have said before, I could try to flash the rom to it using adb but I believe that wiping the system partition unset the USB debugging setting. When I connect it to my computer windows device manager notices the kyocera removable device for a second then as the phone reboots it goes away. Setting it into recovery mode does not make it show up in windows. Is there any way I can flash the stock rom onto it? Any android sdk or adb trick I can use that can boot it into some recovery mode? I was trying to see if I can get it to boot into download mode but seeing as it has soft keys and not a physical home button I do not know if I can manage that. I was thinking that maybe they tied one of the physical keyboard buttons to the home button but I have yet to uncover that one. Any help would be appreciated.
Click to expand...
Click to collapse
Hi and thank you for using XDA Assist
If you can access your recovery it is already a good thing, try first to wipe data and see how it goes.
nilac said:
Hi and thank you for using XDA Assist
If you can access your recovery it is already a good thing, try first to wipe data and see how it goes.
Click to expand...
Click to collapse
So, I boot into recovery and I do the wipe data/factory reset then the wipe cache partition for good measure and it still halts on boot. Same thing. Boot, kyocera logo, virgin mobile boot splash, then it halts where it would normally go into android. Then it reboots. Rinse repeat.
Any suggestions? I sorta need the information off the phone.
Objective: I am hoping to be able to boot my existing system to recover data such as SMS, call logs, app data, and so on - obviously it was inadvisable to start messing around without backing up my data, particular with my amateurish capabilities. But that's the situation I am in. For some reason I thought that just replacing the Recovery was not going to risk my data. Its been over 5 years since the days when I would regularly flash my new phones with cyanogenmod, and my abilities were very basic even then.
Context: G930FD with stock rom, baseband ETC? - apparently for Dubai, which does not allow VoLTE or WiFi calling, which is what I was trying to fix when I got myself into this.
the Events:
- I enabled ADB and used Heimdall on Windows 7 to flash twrp-3.3.1-0-herolte.img
- initial attempts failed to complete download. I booted back into the system and applied OEM Unlock. Flashed successfully.
- chose the 'allow modification' option or whatever it says, not the Read-only option
- I did NOT check at that point to see if the system would reboot properly. I instead right away made a full back-up to my external SD.
That's all I did. After the back-up was complete I rebooted, and arrived at "SAMSUNG Galaxy S7" endless boot loop.
best guess: this is related to samsung encryption? TWRP file manager says that DATA is 0MB.
Again, I am desperately hoping that someone can help me recover my existing system. The threads I found on this subject all lead to wiping the phone and flashing a new rom.
thanks.
digging in deepr
I went ahead and rooted by loading SuperSU otg through TWRP.
Now I get passed the first splash screen that was previously boot looping (Galaxy S7, powered by Android), and I get to the 2nd splash screen (glowing SAMSUNG logo). It does not boot loop, just glows in and out endlessly and never loads.
Is that progress? Or maybe its worse.
t.krug said:
I went ahead and rooted by loading SuperSU otg through TWRP.
Now I get passed the first splash screen that was previously boot looping (Galaxy S7, powered by Android), and I get to the 2nd splash screen (glowing SAMSUNG logo). It does not boot loop, just glows in and out endlessly and never loads.
Is that progress? Or maybe its worse.
Click to expand...
Click to collapse
Reflash TWRP with Odin, boot TWRP, wipe cache, reboot.
Thanks.
I think greenman at sammobile had the answer --> NEW: S7 5 file firmware options (this forum wont let me post a link).
But I botched the execution and the CSC file overwrote my data. Crushing blow. I would say lesson learned, except that I already knew better and risked my data anyway. Sad.
I have a backup I made at the first launch of TWRP - but I assume its worthless since TWRP was not reading the encryption. Its only 3.7GB.
Side note - I did achieve the original goal of replacing the Emirati rom with one that activates WiFi calling and VoLTE.
Has this issue been solved?
I never recovered my data if that's what you mean. Did you look up greenman at sammobile? It sounds like someone followed his directions and was able to flash just the system files without overwriting their data. I think you had to modify the csc_home file. It was a bit beyond my skill level.
Oh, I was just wondering if your phone was still bricked. I didn't read your last message properly before replying lol. My bad.
I'm not personally having issues with a device, I was just curious if I could help at all.