[Q] Tab 3 7" Build numbers? - Galaxy Tab 3 Q&A, Help & Troubleshooting

Does anyone know if there is an issue trying to root specific versions of the 7" Tabs? I've had 3 Tabs and all 3 had different Build Numbers, the last 2 digits have been F1 and K1 ( I don't remember the first) but the first one nearly bricked trying to root, the screen was all messed up, the second one that was on K1 wouldn't install TWRP, it would act right but never boot into it, just into the stock recovery. I've not tried the new F1 yet, Best Buy is probably wondering why I'm returning and buying the same thing over and over.

Related

[Q] Semi Bricked Tab S

So i was messing around with the tab S 10.5 and accidentally deleted the nandroid backup and also full wiped the whole drive. I installed a different FW using odin, but the one thing I found out is, 1, knox is not present and SuperSU wont work, and 2, Charging through computer doesnt work. So my question is, is there an original firmware for my tab, i bought this in the US but cant find any, and ive been using a hong kong one. I believe the charging through computer doesnt work because of the wrong firmware.

Can Install any ROMS - Stuck at Galaxy Note II Screen

Hey all,
I have read all over the place but I honestly get more confused the more I read. I wanted to switch to another OS since my phone was starting to become bogged down (too many pictures, videos, old files, etc etc etc; My phone is my work tool since I'm a field sales engineer)
So I went ahead and rooted it with ODIN 3 v1.85 and I317-UCUBMK6.tar.md5. I also installed TWRP although I have no clue which version it is. I suppose it's the latest one. My bootloader is 4.3 (I think; I go to About Device and I see the android version 4.3)
I always do the full swipe and a NANDROID back up. However, when I flash a custom ROM, I always end up stuck on the Samsung Galaxy Note II screen. It won't go.
I have tried to install the following ROM's:
DN3 - Always says "Failed" when I try to flash, even when following instructions of reboot recovery and flash again.
JEDI X 20 - Go through the entire aroma installer - it installs - asks for reboot - when rebooting, stuck as Samsung Galaxy Note 2 screen
and it pretty much happens with all of them. I have decided to back to stock (because I was a retard and accidentally deleted my NANDROID backup) and now I find my WIFI is broken.
I pretty sure this has all been discussed in various threads but I rather bring it all into one so that all that are having the same issue as me (I read a lot of people complaining about this issue with very scattered replies) can have a single thread that addresses how to fix this.
Any help will be greatly appreciated.
I suppose you have an AT&T Note 2 so this section is wrong. Here is for N710X.
Look into THIS forum.
have an AT&T Note 2

[Q] CustomROM on Pro 10.1 Live Demo Unit SM-T520x

Good evening peeps,
My brother has been kindly given an ex demo unit of a Pro 10.1 (SM-T520x) for his son to use.
Does anyone have experience in bringing this back to a fully functioning unit?
I have tried to research as much as possible to avoid asking a question that has been asked many times before.
I can see quite a few threads for different models, each with their own set of challenges (missing hardware, partition size differences,
boot loops etc).
Do these units come with the retail mode app that can be unlocked using the passwords available online?
Am I able to flash a CustomROM to the device?.
Any tips are greatly appreciated.
Tom
Good morning all,
I just thought id pop back here and answer my own question (in case someone else searches looking for the answer).
You can indeed treat the SM-T520x exactly the same as a retail SM-T520
I took the plunge and went for it....
1) Rooted the tablet using 'CF-Auto-Root-picassowifi-picassowifixx-smt520' (via odin).
2) Installed Flashify from the app store.
3) Backed up recovery and kernel (from within flashify).
4) Installed TWRP from within flashify (Followed other advice and installed a 2.7.x.x version).
5) Made a full backup within TWRP.
6) Completed a FULL ADVANCED WIPE within TWRP (everything except external SD Card).
It was then ready for a customROM, I chose 'SMT520_GraveD_V3.0' and flashed it from within TWRP...
My nephen has been using it daily for over a week now and its brilliant. Only remnant left is the initial samsung splash screen still
says 'live demo unit'... but thats no issue at all.... he is well happy.
I hope that might help someone sometime
I have just bought an tab pro 8.4 ex demo unit and I was wondering the same as you did, so thanks for sharing the above info! It will help me a lot.
Did you change the splash screen? I'll probably change that when my tab arrives.
Thanks again, Andy

[Q] Nexus 7 random reboots

I have recently traded in my old Nexus 7 2012 for a 2013 model and since day one its been rebooting (a lot) also struggling to boot up (most of the time), It is running android 6.0.1 and after rooting TWRP recovery is not sticking either it seems to revert to stock recovery. After browsing the internet im not sure if its suffering hardware or software problems any help would be much appreciated thanks.
Twrp issue is discussed a lot recently in several threads. Late manufactured N7-13's, the ones preloaded with LP and not JB, have other Emmc chip. Regular Twrp not compatible. But a multirom Twrp is.
Concerning the reboot and boot issue. If already done a factor reset I don't know. Normally Ota's to new version leave a mess with bugs and decreased battery life. I always factory reset before and after big updates. (And easy restore everything with Tiranium). Sometimes via recovery only wiping cache partition is sufficient. Try that first.
Thanks I got TWRP to stick using Flashify and have tried resetting and reflashing but am still suffering from reboots/not booting up im beginning to think its a hardware issue from what ive read online.
Could installing lollipop help maybe then updating to Marshmallow?
After a bit of poking around inside and applying some insulating tape on the ribbon connectors I now have a usable device. Reboots once or twice a day and suffering with issues when typing (getting ip instead of o in portrait mode) so still not 100%. Am now waiting for a replacement tab. Just out of curiosity does anyone know how to find the date of manufacture without the box?
Got a replacement yesterday and what a difference. 100% better than the last one so it was definitely a hardware issue, and I got a refund for the waiting so basically its been a straight swap - my 16gb 2012 for this 32gb 2013 ?

Flashed TWRP to both A and B

So i followed the instructions to flash TWRP. this is the first time i have used a phone with the A and B type boot and when it was supposed to reboot to TWRP after flashing TWRP to A (my default boot.img was B) it instead loaded the OS. Confused i tried the process again and was relived to boot into TWRP. However i then discovered that TWRP had been flashed to both A and B. I am on the Three UK Razer phone and i can only access TWRP. I did a backup but I think it either didn't work or was wiped while i was trying to fix the issue. I would appreciate any suggestions or help anyone can offer. Thanks in advance.
Same here
And used also the backup files that was uploaded by one of members in here but so far not work
I purchased mine from amazon us
Anyway to fix our phones
Please
hi there, i got the same problem i flashed twrp exactly like you , i can only boot in twrp not in os . with boot.img from another guys here i managed get the bootanimation with the green circle but i can't boot or past that screen. i leave it for 4 hours ,drains the battery and shut itself off. after i read somewhere on this forum that if the boot partition(kernel) is matched with your system and won't boot in another phone ,i got the backup tried to restore none work. my phone is dead on the drawer , meanwhile i bought oneplus 5t sandstone white 128GB and i got like 12 roms on the Data partition and i don't know witch one to flash , so the difference for support for this two device is major . i will never buy a non popular phone
i will wait for them to release the factory image, (at the end of this year) i will flash it and i will sell it with 300 pounds less because razer
Just for you to know , they just released the robin phone factory image after that phone is obsolete
i also got a ****y phone from china witch is AndroidOne (xiaomi mi a1) witch meens is nexus /pixel like witch i got android 8.1 and in two weeks i got 4 updates streight from google .i was just amaze what support got this cheap phone . the point is next time when you buy a phone check if is popular on XDA forum
The razer phone got good spics and potential
But I wonder why it's unlike op5t in terms of support.
Let's skip the factory part but my main point on the developers in here , why we can't find help in here and support.
The reason there is fewer developers on this phone is cause there aren't factory images yet. Developers don't want to get there phone in a state that can't be reset and right now, that's razer phone. Razer has said that they are coming but I suspect like others, they haven't released them yet cause they are trying to get everything tweaked right before they release them. There really is no point having images for a phone that reintroduces issues they have already fixed with updates. I don't expect it will be much longer though.
OP and the like already have an established following that's why there are so many options. Also remember the 5t is still based on the 5 which already had a development community. Razer on the other hand is a new company and this is there first go at it. Once we see images released alot more developers will be more willing to jump on board. You see this with almost all new phone manufacturers.. You don't think htc and the like had developers lined up out the gate do you?
This phone wasnt released as a developer phone like the nexus line was. Razer has been quite good so far in terms of software updates and being in touch with the community as a whole.
I totally agree with you , my main point is to find solve for our corrupted phones and not only me having that issue.

Categories

Resources