I've been working off and on trying to get my P7310 Wifi updated beyond the 4.4 version of Android it was stuck on for a while.
I have TWRP installed and was eventually able to get a version of 5.11 installed and working but then saw that there is a later rom availble with 7.1 (aosp-7.1-p5wifi-20171005) I decided to try that. The ROM would not install using Odin.
I remembered that the original instructions I was following said to format the cache and that I had eventually formatted the user data from TWRP to get 5.11 working, I did that.
Now, when I fire it up, it goes straight into TWRP, and TWRP shows no file system at all. I can access download when booting if I need to, but even without pressing any keys, all I get is TWRP.
Have I completely screwed the tab up, or is there still hope?
Any advice would be appreciated, even if it's worst-case. At least I'll know I can put it aside for good.
Eric the Grey
Ok, after nearly 2 months and around 175 views, and no replies, I'm going to have to guess that there's no hope for this device and I might as well toss it in the e-recycle bin.
I just wanted to thank everyone who took a look at this with the intent of helping, even if you had no suggestion.
Have a wonderful new year everyone.
Eric the Grey
Eric the Grey said:
Ok, after nearly 2 months and around 175 views, and no replies, I'm going to have to guess that there's no hope for this device and I might as well toss it in the e-recycle bin.
I just wanted to thank everyone who took a look at this with the intent of helping, even if you had no suggestion.
Have a wonderful new year everyone.
Eric the Grey
Click to expand...
Click to collapse
Thanks for posting, I was also hoping to find a little new-life-hope about this tablet I think there could be a way, but it needs devoted advanced devs to make something out of it.
Related
NookColor Version 1.2
About 2ish months ago I bought a nook color for my significant other, but I was having problems getting sideloaded books to work right on it so I decided to try and root it. I'm not extremely tech savvy, but can usually do something like this if I have directions.I rooted with manualnooter-4-6-16 The root went well and it was working fine for a couple days until dummy me started messing with it, don't know what it was that "bricked" it but I had updated the flash player then was in the rom manager and hit the backup button. The keyboard was acting funny so I rebooted it, it got to the screen that says Nook Color with the little android dude in the bottom right (nook color devs) and that screen just kept replaying itself except it would stop at the first O in Color and start over. I tried doing some research and followed a couple tutorials on how to return the nook to stock, none has been successful. The first one I followed was video tutorial on youtube to return it to stock 1.0.1, when it asked me to format the data I got and error format data failed..I just skipped that step and moved on. It booted and still showed me the nook color devs screen and once it completely booted showed a "How do you want to finish this action?" With only Home and Softkeys as a choice, I hit home and all it was was a black screen with a bunch of errors. so I tried a different tutorial, the next one I tried was to return it to 1.2 I followed the instructions, it again gave me a error cannot format data, I ignored it..it booted to the nook devs screen and just kept playing over again. I'm lost on what to do, I've searched and searched.
If it matters I've been using a 16gb micro sd because thats all I have, and was using the 2gb clockwork recovery image. I just want it returned to stock, and can't for the life of me figure out how.
Please someone explain to me in the most dumbed down way how to fix this darned thing.
Don't know how serious "brick" it was on your definition but let say on scale of 10, yr NC is bricked level 9 . Still, no need to panic
1. Get the uSD card (2GB is enough)
2. make it flashable with CwM Recovery (ClockworkMod Recovery) either v3.0.2.8 or v3.2.0.1
3. hunt for "re-partition/re-format" thread, read through. I'll update the link if I find it, can't remember where on top of my head now.
4. perform the repartition/reformat back to original v1.2 NOOK
5. hunt for "restore to NOOK for v1.2". Again, I'll update the link later
6. flash it
7. keep all your fingers crossed
Will try that, thank you..Hope it works..seriously cant afford to spend another 250 dollars to replace it
Edit: Fixed The 8 interrupted boots seemed to have fixed it, thanks for your help!
Scintie said:
Will try that, thank you..Hope it works..seriously cant afford to spend another 250 dollars to replace it
Edit: Fixed The 8 interrupted boots seemed to have fixed it, thanks for your help!
Click to expand...
Click to collapse
Glad to hear that!!!!
I was rooted on 7.3.0 from the day I got my replacement kfhd less than a month ago. I forgot to turn off automatic updates and yesterday 7.3.1 installed and immediately I'm having problems. Some apps I had installed are gone, like No Lock and Apex Launcher (I'm almost positive that's which one I was using) for starters. I tried to reinstall No Lock since I have Nova Launcher working and I'm sick of unlocking twice. Downloaded No Lock, went into ES File Explorer to move it, and there is NOTHING in /data/app to move.
I'm almost afraid to see what other problems there are. I downloaded a root checker and it says I'm not rooted anymore. Well that explains a lot. However Google Play has hung around problem free, which you did need root for.
How should I proceed? I fried my fiancee's kfhd a month ago after I rooted it. I was attempting to install TWRP, screwed up, and bricked it. She went out and bought another tablet. I called Amazon and told them it just died for no reason so they sent a replacement which became mine. If I brick another kfhd I don't think Amazon is going to want to replace it again.
I know 7.3.1 was just sent OTA and not to everyone a few days ago (found that info on the forum somewhere) so has anyone re-rooted after getting it? What other things can I safely try?
It might seem kind of obvious but why not simply root again? I don't see any reason why it wouldn't work. I rooted my KFHD running 7.2.3 with Kindle Fire First Aide no problem. I'd imagine that 7.2.1 should be no problem. If you follow the steps in this thread it's pretty easy.
Also I should mention that it's pretty difficult to really brick your KFHD. If you get a factory cable (either make one yourself or order one from SkOrPn on here for pretty cheap) you can almost always fix any software problems. The factory cable essentially puts the KFHD in "factory" mode which lets you flash it in fastboot almost regardless of anything you've manage to damage. I messed up my KFHD pretty bad (stuck at the boot logo and would refuse to be be detected at all via usb) but with a factory cable it was super easy to fix.
MightyBraeburn said:
It might seem kind of obvious but why not simply root again? I don't see any reason why it wouldn't work. I rooted my KFHD running 7.2.3 with Kindle Fire First Aide no problem. I'd imagine that 7.2.1 should be no problem. If you follow the steps in this thread it's pretty easy.
Also I should mention that it's pretty difficult to really brick your KFHD. If you get a factory cable (either make one yourself or order one from SkOrPn on here for pretty cheap) you can almost always fix any software problems. The factory cable essentially puts the KFHD in "factory" mode which lets you flash it in fastboot almost regardless of anything you've manage to damage. I messed up my KFHD pretty bad (stuck at the boot logo and would refuse to be be detected at all via usb) but with a factory cable it was super easy to fix.
Click to expand...
Click to collapse
Rooting it again would probably work from what I know about rooting phones. I'm kinda hoping someone else has already done it so I know for certain that it's gonna work before I do it.
Maybe I have to be the person who finds out if simply rooting again fixes the issue.
Rooting again should fix the problem. I would try that first.
Worst case scenario it doesn't help and you have to do a factory restore or re-flash in which case you can simply restore a clean copy and then either disable the OTA updates or else, better yet, let it update all the way to 7.2.3 and then root the latest version.
Yeah, I think I'll give rooting it a shot. I PM'ed the guy that made the Kinology 7.3.1 ROM about rooting and then flashing recovery from where I'm at right now since I can't post in the “development" forum until I have 10 posts. He also said it should go fine from where I'm at. I'd love to flash that ROM, I'm just afraid of screwing up since I massively screwed up the first time I flashed a recovery.
I'll give it a shot tonight when I've got time to mess with it.
SGoatS said:
Yeah, I think I'll give rooting it a shot. I PM'ed the guy that made the Kinology 7.3.1 ROM about rooting and then flashing recovery from where I'm at right now since I can't post in the “development" forum until I have 10 posts. He also said it should go fine from where I'm at. I'd love to flash that ROM, I'm just afraid of screwing up since I massively screwed up the first time I flashed a recovery.
I'll give it a shot tonight when I've got time to mess with it.
Click to expand...
Click to collapse
It's not hard as long as you follow the instructions... It works flawlessly on mine.
Well I'm happy to say that rooting again after the 7.3.1 update Amazon snuck in on us went perfectly. So when others get that update and aren't sure if they can root again easily I hope they see this thread and know that it is no different than the first time you rooted.
-a- said:
It's not hard as long as you follow the instructions... It works flawlessly on mine.
Click to expand...
Click to collapse
My only concern is messing up the TWRP install. If I actually read the instructions a few times before doing it I shouldn't mess it up this time. I'm gonna look into it some more this week in my spare time and convince myself to do it. The extra encouragement of it working no problem is appreciated.
SGoatS said:
Well I'm happy to say that rooting again after the 7.3.1 update Amazon snuck in on us went perfectly. So when others get that update and aren't sure if they can root again easily I hope they see this thread and know that it is no different than the first time you rooted.
My only concern is messing up the TWRP install. If I actually read the instructions a few times before doing it I shouldn't mess it up this time. I'm gonna look into it some more this week in my spare time and convince myself to do it. The extra encouragement of it working no problem is appreciated.
Click to expand...
Click to collapse
You're welcome.
Sent From my Kindle Fire HD running CM10.1
Hi, I f_cked up.
Firstly, I've spent a few hours looking around the internet (including this forum) for answers but I can't find any so sorry if this has been answered (but I doubt it, I f_cked up pretty well).
My biggest issue at the moment is that, whenever I try and start my phone I get the error: "Unfortunately, the process com.android.phone has stopped" and I'm stuck in a constant cycle of restarts, unless I take my battery out. There is also other problems, but I'll tell you how I kept screwing up my phone.
So, I got my new phone, rooted it, all good. I deleted a bunch of system files I didn't need (not com.android.phone). I then decided I wanted the LWP Picker and a few other stupid little things back just to mess around with them, but for some reason the backups in RootUninstaller weren't working so I went looking for the APK's instead, none of which installed correctly.
Since my phone was pretty new and didn't have much data or apps on it anyway, I decided I'll reset it, without making a backup of course. Only problem is, once it deleted all my apps, it also deleted my Google Keyboard (der) which is no problem, except I f_cking deleted the Samsung Keyboard with RootUninstaller, so, errr, I couldn't do anything - including connecting to wifi or logging into my google account - oops.
So what do I do? I'll flash the ROM. I basically followed the instructions on a "theunlockr" website /2013/09/17/how-to-flash-a-custom-recovery-image-on-the-samsung-galaxy-s4-active/ - it's a .com and couldn't post direct links 'cause I'm new. No, I didn't do a custom.
So, basically, yes, I'm screwed. Can anyone help? Very urgent problem.
PS: Sorry if this thread seems rushed... it is.
Since I haven't really gotten a reply, I think I might have a unique problem. Does anybody at least have a nandroid backup or some other way to return the active to it's original form? Thanks again !
Have you tried Odin?
GT-i9295(i537) running SafeStrap
yankeesfan714 said:
Have you tried Odin?
GT-i9295(i537) running SafeStrap
Click to expand...
Click to collapse
I'm a bit of a noob at this (hence the problem). I used Odin to root the device and also to put CWM on it, but I don't know if I can use Odin in any other way? I also used tried to follow this thread /showthread.php?t=2395242 but the ROM wont transfer to my SD Card for some reason so I can't flash it using CWM. Any other suggestions? Trying to find another Micro SD Card I can use, but is there anything else i could do?
FIXED!!!
So basically, my phone is now in a working state again! I follow the CyanogenMod 10.2 (the thread I put above) after buying a new SD Card and it's working great so far! While I didn't really get much help in this thread, it was this forum that saved my arse so thanks! Hopefully I'll hang around a bit more
Howdy, folks. I just picked up an S2 and though it was supposed to ship with MM, either it's a refurb and the store is selling it as new, or the factory upgraded the ROM and the ad copy didn't match with the software version.
I specifically want MM so I can run Xposed and Xprivacy.
Can anyone point me to a way to get ahold of the OEM Samsung equivalent of an RUU so I can get back to MM on this device?
Thanks in advance!
Wow. I figured you Sammy guys would be all over this.
I'm looking for the factory stock MM ROM for a T813NZKSXAR. Can someone point the way? Sorry, but I'm new to Samsung devices, so I'm not up to speed on all the resources and I'm not finding anything that seems right either here at XDA or on a web search.
Could really use some help, here...
Thanks!
BillTheCat said:
Wow. I figured you Sammy guys would be all over this.
I'm looking for the factory stock MM ROM for a T813NZKSXAR. Can someone point the way? Sorry, but I'm new to Samsung devices, so I'm not up to speed on all the resources and I'm not finding anything that seems right either here at XDA or on a web search.
Could really use some help, here...
Thanks!
Click to expand...
Click to collapse
Head over to updato.com
Thanks for that. I'm still getting my head around all of this.
So, I actually did download that file, but wasn't sure if it was safe. I went ahead and flashed the MM firmware with Odin3.12.3, but I seem to be having some trouble applying TWRP.
I'm using twrp-3.2.0-0-gts210vewifi.img, but when done flashing in Odin, I can't seem to figure out the sequence to catch the machine before it boots back into the OS. Either that, or I have the wrong TWRP image, or something. I just can't seem to catch it right.
Any help would be appreciated.
Ok, got it sorted. Managed to get TWRP installed, but having trouble flashing Xposed. I'm using xposed-v88.2-sdk23-arm64 but as it flashes, there's an error saying that it can't write to the data partition, and on reboot, the Samsung name just keeps pulsing and the machine never gets to the OS. At least, not for about ten or fifteen minutes, which is the longest I waited.
Thanks again in advance for your help!
Haven't received any updates since 1/2019 so I downloaded a file from a link on xda and tried to fix it myself. While trying to update from my SD, I received an error in recovery mode shortly after I started to flash the zip. Since I couldn't get the phone to boot up, I decided to factory reset and start all over but now I'm in bootloop. I'm an idiot. Thank you so much for any help! I tried to search for links here before posting but I'm on a really old phone now so am having a difficult go. I have a Verizon sm-960U. And I'm a newbie at this. I used to mess around with my nexus 6 a lil but that was years ago. Thanks again and I don't mind donating money to get the device back up and running.
After more research on yt, looks like I should install Odin and go from there. Will give that a try.