Hi there,
I owned a T705C tablet which is China variant. No matter how I tried I cannot flash any aosp based rom into my tablet. Every time I get stuck at "patching system images unconditionally" when I try TWRP to flash a rom. I switched to abd sideload command to transfer rom from my computer, only to find that every rom stucks at 43% and won't progress any further.
Anyone has any idea to resolve the issue?
From my experience the China variant phone only gives you TD-lte support, every other specs remain the same. I flashed cyanogenmod into my note 3(N9008, also China variant) no problem with that.
Thank you so much for your kind help
Related
Hi,
After upgrading OTA to kitkat (australia version) one of my favourite apps stopped working and caused constant reboots to my tab3.
I tried to downgrade with odin to the stock 4.2.2 (auatralia, from sammobile) but I could not. After flshing, the "samsung galaxy tab 3" logo appeared but the tab never turned on, it kept rebooting and rebooting from ours. I tried the same with other 4.2.2 roms with the same results. However I was able to flash any 4.4.2 rom from sammobile.
After that I tried to flash some 4.2.2 roms using twrp and bindroid, I had the same rebooting problems. However, with twrp I can flash 4.4.2 based roms as pimpdroid.
So, I do not why, apparently my tab only accepts 4.4.2 roms... Any suggestions about what should I do to go back to 4.2.2?
Thanks for your time,
A.
Bootloop in P5210
Hi I'm trying to get back to 4.4.2 to 4.2.2 works because although there are excellent applications like Facebook that are causing me problems. But in trying to make the retoroceso as I usually do with ODIN stock form and I was left in a permanent reboot and does not pass the SAMSUNG logo .... solution? Thank you!:crying:
@planinsky, Have you tried a firmware for another region in the world? I live in the United States but have found firmware for the United Kingdom or Canada works best when I flash. There should not be any difference in the firmwares except for regionalization, but it seems some work and some don't work for me. Regional settings can always be tweaked in the Settings panel after install. Do you have a nandroid backup made in TWRP? Those usually always recover a device. I too had a problem having anything flash when I first started making my rom. 3 weeks I had a device that would not boot. So it is recoverable. Odin will save your device.
@planinsky and @MDCB try to download this firmware from Sammobile. This is for the UK 4.2.2 version. http://www.sammobile.com/firmwares/download/28243/P5210XXUANB4_P5210BTUANB1_BTU.zip/
I usually use ODIN 3.07. I assume you know the following but just in case. Remember to flash it in the PDA slot. Only have "Auto reboot" and "F. Reset time" checked.
Using Odin will reset anything the 4.4.2 builds have done to the partitions. If it doesn't work, I can only suggest to try again. When it comes to flashing, sometimes the TWRP builds for our device can be a little goofy in writing. I have not investigated completely. In the 4.2.2 roms I have flashed pimpdroid and cagrom, they seem to flash good with Moonbutt77's philz recovery with very little problems. I however cannot get 4.4 roms to flash in philz but only in TWRP. So sometimes the recovery itself seems to have a problem with the android version, or so it seems.
The above is only written from my experience on this device and cannot predict every situation.
Good luck.
Hi! Thanks for the tips.
Ufortunately, I have already tried 4.2.2 ROMS from different countries (from Sammobile): Australia (the original country of my Tab), UK, New Zealand, Belgium and US. None of them worked. I'm still downloading other ROMS but I'm startin to lose the faith... The custom ROMS I have tried, neither work and get into the bootloop.
The backup I have from TWRP is from a 4.4.2 so it's not a solution.
On the other hand, I can flash almost any 4.4.2 ROM with odin and/or TWRP. So I'm afraid I'll soon give up and I will accept that my Tab will not longer run the app I loved (Movistar TV)... Hopefully with the arrival of lollypop the developers will update the app and the bug which causes the crash will disappear.
So i tried flashing the pa_n7100-4.6-BETA4-20141009 rom as well as cm-11-20141008-SNAPSHOT-M11-n7100 onto what i'm sure is my note 2 n7100. While installing, at the start, the recovery says the rom is meant for a t03g while mine's a t0ltetmo. There is no way in hell my phone's a t-mobile : firstly , i live in india, a country free from the tyranny of t-mobile, and secondly, it says gt-n7100 on bootup from stock rom. I tried removing the version checking part in the rom, hoping to force install it anyway, but it just popped up 'error'. Then i tried flashing one of the few roms available for the t0ltetmo, the Slim-t0ltetmo-4.4.4.build.8.0-OFFICIAL-6945 rom. After a successful installation, it was just stuck on the boot screen. I'm not saying i dont like the shiny slimkat logo twirling around, but i would eventually like to use my phone too. I'm now back to my stock rom after flashing my friend's n7100 recovery image, and then factory resetting, because cwm 'lost' my backup file. Anyway, i'd love to have the new 5.0 cm12 alpha, but i'm apprehensive now. Help me? :crying:
Hello guys,
It's been a while since the last time I visited the SGS3 section, over a year ago I remember updating the bootloader in order to upgrade/flash to 4.4.4 which went very smooth and was a success. I gave the phone to a sibling who has been very happy with it for the last year and a half. Lately, the phone has been very unstable with the 4.4.4 KitKat ROM, WiFi doesn't turn on, Bluetooth is unstable, Unstable apps/Force closes. I tried a wipe/factory restore and re-flashed the ROM but the problems persisted.
I did a little research and liked what CyanogenMod is doing and since they are actively supporting the phone I decided to flash CM12.1 and the provided Open Google-Apps, CM12.1 flashed successfully but Open Google-apps refused to install, CWM displayed (Section 6) error which upon research it is common with CWM and the solution is to flash TWRP. I booted with CM12.1 in order to install TWRP Manager through the APK and flash TWRP but it force-closed when it searched for the device model. WiFi was working but Bluetooth was still unstable.
I would like to know what would be the best way to proceed in this case, I would like to upgrade the recovery to TWRP and flash CM12.1 or any other stable Lollipop ROM.
Thanks,
Oscar
absolute all credit to @audit13.
http://forum.xda-developers.com/showthread.php?t=3313734
perhaps this will help.
"err on the side of kindness"
I'm currently running my OP3 on Resurrection Remix 5.7.4 (MM 6.01), the phone has the latest version of TWRP and I've flashed other ROMs in the past without any issue
RR has proven to be quite unstable for me, the system UI keeps crashing, which renders the phone unusable until after a reboot so I wanted to flash Freedom OS as that worked quite well for me previously. When I tried to flash the ROM in TWRP the ROM seemed to flash successfully but when I rebooted, only the boot logo showed and then the screen went black and the phone refused to respond at all for about two hours, after that exactly the same thing happened. I managed to boot into recovery and tried flashing a different ROM but the result was the same every time, the only way to get the phone to work normally was to flash RR again/restore from a Nandroid backup, either way, the result is the same, I'm stuck on an unstable ROM and I don't know why, the last time I flashed these ROMs they worked fine, I followed all of the instructions for flashing said ROMs to the letter, I have the latest version of TWRP, etc, does anyone know what the problem could be?
Have you flashed the latest firmware? If not, I think this is why due to you being on a very old version (6.0.1) and as you are not flashing official OxygenOS you are not getting the newest firmware.
Download and flash the latest firmware here:
https://forum.xda-developers.com/oneplus-3/how-to/radio-modem-collection-flashable-zips-t3468628
Pick the right one for the ROM you are flashing (For Freedom OS installing firmware Open Beta 14 - Firmware + Modem under 7.1.1 should be good.)
Note: After you have flashed the firmware the next time you reboot the phone it will appear to not turn on for a few seconds, this is normal while it updates, don't worry
Let me know if you have any questions
Hello XDA people. I'm an enthusiast of flashing and testing android ROMs, but I am kinda rookie using this device.
The problem in question is that I cannot successfully flash any Android 10 and later ROMs on my device, I always face several problems after flashing and booting any ROM, such as the wifi's not working (got the exclamation mark on the icon), audio problems, mobile data increiblely slow, bluetooth and GPS issues, etc etc. I tried to flash official and supported ROMs like lineageos, evolutionx, pyxisos, havoc as well as unofficial roms, but I always get the same problems (the wifi issue is the problem that I want to fix the most)
I tried flashing the original MIUI firmware through recovery and bootloader method, I dirty/clean flashed the roms after and nothing, I also used factory reset, used OrangeFox, TWRP (official and unofficial versions) and I still have the same result. I tried every method I know and it seems I won't have the problem fixed. I don't know if it's that the firmware is not properly flashed, or if I deleted a partition. What can I do?
The device only works using the MIUI original firmare but I don't like it because of the bloatware and the waste of resources. I currently use MMX rom (a modified MIUI rom) in my device right now. It works well but It's currently outdated. I just want to use an AOSP based ROM and having my device updated. Please HELP ME!