Ok, first time post, and root for me.
TIFU. I rooted without any issue. I thought, hey that was easy, lets install a ROM. Boom, success! Not hard at all.
Well, I have a SM-910T [100% positive, I bought it from T-Mo]. I installed SimplROM. Once it loaded up, the device no longer recognizes the SIM card. I went to the "About Phone" and now its says SM-N910F. So I tried to install a different (multiple) ROM, but it fails and aborts saying, I need a trltexx but I have a trtle. "Status 7". Next I went into the zip and erased the first line of the "update-script". That fixed the Status 7, but is still aborts installation with no status code. This happens with all ROMs for SM-N910T.
I wiped everything. I mean everything. Now I'm stuck boot looping. But I can still boot to recovery, so thats good.
Any help?
OK, so turns out I did have a recovery file for SimplROM so I'm not boot looping anymore. But all the other problems still persist.
Related
So I'm trying to get my VZN Galaxy Tab back on its feet. After trying to get Gingerbread in it so I can use Netflix - and failing - I'm going through a lot of motions.
Okay. First I rooted it with Super One Click. I should have been happy with that, but noooo. Then I tried flashing GB on it (I wish I can remember which ROM I started with...it's a mess. I think the pit file was gt-p1000_mr? Does that sound right?).
When that didn't work, I went to the much-cross-posted procedure for returning it to stock using Heimdall and SCH-i800_VZW_stock. Tried it five times. Each time, it booted into the Galaxy Tab/Samsung logos, then a fast glimpse of scrambled letters for a second followed by twinkly music, then black nothingness. It would then bootloop. I attempted to boot into recovery to wipe data/cache, but I couldn't get there. Vol-Up/Pwr just brought up the logo and scrambled video again.
Since I was still able to get into download mode, I tried flashing another ROM...this one the "P1000XXJQ1_P1000XXJQ1_P1000XXJPZ" method. With this, I was able to also flash CWM so I have SOME recovery mode. Sadly, booting brings up the GT/SAMSUNG logos and I get the spacey animation, but after that, again - blackness. This time, however, the Menu/Home/Back/Search buttons light up, so something's happening in there.
Also, booting into CWM, I cannot get my sdcard to be recognized. I tried different cards, so there's something goofy with the slot itself, I'm guessing.
So nothing is really working, but since I can get into CWM and also download modes, I'm holding out hope that this is not completely bricked.
I just need to find the right method of getting it back to a functioning tablet. If anyone has any suggestions, I'm all eyes. Thanks so much.
UPDATE: I tried reflashing stock using the tried and true method. But this time, I went in and flashed CWM replacing the stock recovery which never worked for me. I got the Galaxy Tab/Samsung logo, and at long last, the animated VZW logo. Then it would bootloop there. I booted into CWM recovery and wiped the data/system and the cache from the first page. It still booted and bootlooped the same. This time, I booted into recovery, went to the mounts and storage section and formatted the system, data and cache. Opening logo only. CWM again, and got a whole bunch of "cache missing" messages. But I think I'm getting closer. Back to work.
UPDATE II: So the farthest I can get is the animated VZW logo using the combo of the stock flash through Heimdall, then flashing CWM with Odin. Still no sdcard access. Anything I should try here? Thanks.
same question here
Did anyone figure out how to restore Verizon tab?
I finally upgraded my wife's Verizon Tab to the 7/25/12 CM9 nightly four days ago. In that time, she's experienced two random sleep-of-death instances, from which I succesfully recovered. Today, however, she put her Tab down after using it for a bit, went back to it later, and it was off again, and very warm. She plugged it in and tried to re-start it, but it would hang on the CM9 splash screen forever.
I tried to re-start it and got the same results.
Then I tried booting into CWM Recovery to reboot from there, but got the same results.
I tried to fix permissions in CWM, but CWM became unresponsive.
I rebooted into CWM again and tried to restore a nandroid, but it failed since /data couldn't be mounted.
I then tried to flash the 7/28 nightly, but it couldn't mount /data either.
I used Heimdall to reflash Recovery and kernel (5.0.2.7 if I remember correctly) I had used to upgrade to CM9, and then tried to flash the 7/28 CM9 again. This time, after a very quick flash sequence, and a very long time (20 minutes) on the CM9 splash screen, it finally moved on to the boot animation, and eventually booted...right into a screen that said "Encryption Unsuccesful."
Per that screen's instructions, I elected to do a factory reset and reboot. After a very long time, the Tab rebooted to the same error screen.
Bottom line is, I've since learned the "Encryption Unsuccesful" bug is an ICS one (especially with unofficial ROMs), and it does a number on your internal and external data partitions/SD card. I was lucky in that the SD card didn't get wiped, but my Tab is unrecoverable. My latest attempt is to load a rooted stock Verizon ROM/recovery/kernel using Heimdall, but after almost an hour, I've just made it to the "Verizon Wireless" boot animation. Most threads I've read on this issue end up in dead-ends, and I couldn't find a single one that pertained to the Original Galaxy Tab, much less Verizon's.
Does anyone have any ideas as to what else I can do?
Good evening, everyone.
Few hours ago, my N6 randomly shut down and not booting up to the system. I tried to re-install the factory image for 5.0.1 but I got stuck at bootloader screen. I tried every options available from bootloader screen(Start, Recovery mode, Restart bootloader etc.) but it performed nothing but coming back to the bootloader screen. When I tried to use 'Nexus Root Toolkit' to install new system and whenever the process was trying to initiate the process, it is giving me same error message 'FAILED <remote failure>'
What can I do from here?
I appreciate your attention.
chg911225 said:
Good evening, everyone.
Few hours ago, my N6 randomly shut down and not booting up to the system. I tried to re-install the factory image for 5.0.1 but I got stuck at bootloader screen. I tried every options available from bootloader screen(Start, Recovery mode, Restart bootloader etc.) but it performed nothing but coming back to the bootloader screen. When I tried to use 'Nexus Root Toolkit' to install new system and whenever the process was trying to initiate the process, it is giving me same error message 'FAILED <remote failure>'
What can I do from here?
I appreciate your attention.
Click to expand...
Click to collapse
If your bootloader is unlocked, you should be able to either flash the stock factory image, or re-flash each partition separately through the tool-kit. Since you're getting remote errors with the toolkit, double check that you have the right drivers installed, the tookit and a search on the forum should help with that.
did you already try :
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Don't want to raise any alarms already but I shut mine down on Sunday night (Unlocked/ Rooted/ custom kernel & rom) in order to boot in Recovery and flash a new kernel version and:
1) The sdcard looked empty, it read ~ 26 GB free (I had no more than 20 gb free before reboot) and no folders whatsoever.
2) The phone was stuck at the Google logo heating up but going nowhere.
As I said don't want to start assuming things but the phone randomly going "nuts" and losing all data is scary... I had to spent my entire day yesterday flashing stock 5.0.1 back and re-setting up everything. I followed the guide posted above (http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008 oh, go with Method 2 and it will work fine).
Out of curiosity how does your SD look like from recovery? Oh, but then you say you can't even boot to Recovery. Which recovery do you have? (I had/have TWRP 2.8.3.1 ). Anyway to repair it you only need to be able to boot into Bootloader properly I guess.
Hello all. I have been in the Android root community for a little over three years, and even after tinkering with the various devices I've owned since, I cannot get my T599N to come out of its current bootloop.
A background: I had been checking some things in my settings app (running stock, rooted), and I ended up just force closing the settings app to get out of it quickly. Well, this action deleted all of my text messages, and later on it removed my notification bar and made my wallpaper go black. I ended up booting into recovery mode to try and clear the cache. After it cleared, I rebooted, and bam, the bootloop started.
Now, here's what's interesting. The phone is in a bootloop where it displays the first boot message (SGHT599N Galaxy Exhibit or whatever), and then it tries to boot into cwm recovery, displays the loading screen for that for 2 seconds, and just reboots again. I've tried installing a stock rom from ODIN with no success. The rom apparently loads onto the device but it's still in the bootloop. After this, I tried to install philz recovery to try to install a zipped rom to get the device to somehow boot. I tried to factory reset it for installing purposes, and it just reboots. The device will literally clear everything but /data, so that makes me think that it may be a file system problem. I really need to get it to work, as I am out of a phone right now.
Does anyone have any suggestions? I've tried everything I know.
I'm a complete newbie to android phone modding, and I was really proud of myself when I was able to install the Cyanogen 12.1 and Google Apps onto my Samsung S3 Mini. However, I made the mistake of trying to put my work email on it, which requires that my phone be encrypted. Well, I guess the encryption and rooted phone didn't want to play nice together, so I got the error message that my phone would be factory reset. Boo! Well, it got worse. Instead of a factory reset, my rooted phone now is stuck in what I have now learned is called a bootloop. Basically I turn my phone on, and the Cyanogen start screen (with the text "TEAMWIN") just infinitely flashes on the screen until I pull the battery.
I have tried using Odin 3.07 and cm12.1_golden.nova.20160210.ODIN_TWRP.tar.md5. I do the three button system boot, connect the usb, run Odin, get the phone recognized, and then install the .md5 in the PDA section of Odin. It tells me that it succeeded, but when I restart my phone it's still the same bootloop. I also tried swearing, but that didn't help either.
Has anyone else out there had experience with Cyanogen and this particular error? I would love to get this phone working again... preferably with either a Lollipop version of android or back to Cyanogen 12.1.
Any info would be greatly appreciated! Thanks everyone.
So I've got an update if anyone's interested... I can't call it progress, but it's a different problem now.
I was able to download and use Odin to do what was shown on this link: http://forum.xda-developers.com/showthread.php?t=2122548&highlight=root
Everything worked in Odin, the phone rebooted, and went to the Team Win Recovery Project diagnostics screen, rebooted again, and then to the samsung logo. However, it immediately goes to the "Encryption Failed" error screen, and the only option is to 'reset device'. Of course, doing this just reboots the phone and it then has the Team Win loading screen, Team Win Recovery Project diags screen, Samsung logo, and back to the 'Encryption Failed' screen again. So now I have a new infinite loop to solve. *sigh*
any thoughts?
Have you been able to get into TWRP? If you are, maybe you could wipe everything from there and flash the recovery version of your ROM.
I was able to put the stock bootloader onto the phone using Odin, download the original tar from here: http://live.samsung-updates.com/index.php?device=GT-I8190, then used the stock bootloader to install it from the sd card. Everything went fine, but now when I boot the phone it just hangs on the Samsung Galaxy S3 mini GT-i18190 start screen indefinitely. Is this progress, or have I created a new problem now?
You're playing around with heavy stuff. I won't recommend using an upgrade flash (CM over Odin) as an full flash. Please try flashing a stock image.
If you did something wrong to the partitioning, then it's likely to not allow you to do a successfull factory reset. Maybe you can try re-flashing a stock Odin image with PIT repartitioning.
Remember to try to backup the EFS folder, doing that kind of flash might wipe it.