yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 4 Q&A, Help & Troubleshooting] SomeDuder:
So I've been having this strange issue for a year now, where I want to upgrade my SM-T530 (Tab4 10.1 wifi) to the stock Lolipop (5.0.whatever) ROM in order to get the damn kernel updated so I can access all these wonderful custom ROMs (Stuck on CM 12 atm...).

But whenever I flash a stock ROM for my model, it seems to freeze the screen after the boatloader. As in, everything seems to be working, sound and touchscreen, it just doesn't update/refresh the screen. Basically, the same behaviour as described in this post.

So here's the steps I took, in the hope that anyone can point me in the right direction:

Boot tablet in recovery (TWRP 3.0.1, in this case) and wipe Dalvik, /data, /cache, /system, basically everything)

Reboot tablet into bootloader/download mode

Using Odin 3.11.1, flash T530XXU1BOL2_T530PHN1BOE1_HOME.tar.md5 (Found here, which should be the correct ROM for my model (Bought in the Netherlands, but I have no idea where you folks are pulling this T530XX stuff from, it's nowhere to be found on the back))

Reboot tablet

After the 4th step, the tablet will be unresponsive for ~10 minutes (I think it's doing the whole "upgrading apps" thing that follows a new installation). After that, when I hit a certain area of the screen, I can hear the regular Android touchresponse, raising the volume also give the normal beeps and pushing the power button plays the "turning off screen" sound, but the screen stays active, showing the Samsung Galaxy Tab4 boot logo.

Soooo... Anyone care to take a guess what I'm doing wrong?

Personally, I think it might have to do with flashing the incorrect stock ROM, but for the life of me, I can't find out which T530-code I have. I've been flashing different ROMs, but no luck so far...

As for troubleshooting I've already tried:

The above procedure, afterwards flashed TWRP via Odin and flashed a custom ROM via TWRP. Same effect.

Variations of the above procedure, where I keep wiping the tablet after each step

Different custom ROMs
[Galaxy Tab 4 Q&A, Help & Troubleshooting] SomeDuder:
Ugh, nevermind.

Turns out I have an UK tablet (BTU-T530XXU1BOG2). After flashing a dozen or so ROMs, this one did the trick.

Oh well, problem solved :good:
[Nexus 6P Q&A, Help & Troubleshooting] Trinaaa:
Hey guys!

I´m facing a really annoying problem and i´m afraid it could be hardware related...

First of all, i didn´t use the 6p as my main phone so i cannot say since when this problem persists.

I wondered about this: i was connected to my wifi network. After sometime i looked at the phone - it was disconnected from the ap. I tried to re-enable it but no luck, just a restart brings it back. Used omni and thought, okay...might be an aosp thing.

Just installed CM (everything included, baseband, radio, vendor) - if i disable wifi and wanting to enable it again, i don´t get any access to my ap. If i restart the phone it´s there.

Please take a look at the video i made to show this problem. https://youtu.be/STUeUdZ3WyY

Thanks in advance!
[Nexus 6P Q&A, Help & Troubleshooting] Trinaaa:
Ummm... Nobody? :/
[Nexus 6P Q&A, Help & Troubleshooting] Trinaaa:
Okay, solved. Thread can be closed.
[Nexus 6P Q&A, Help & Troubleshooting] A380:
How?
[Nexus 6P Q&A, Help & Troubleshooting] pringled:
How did you fix it? MY wi-fi randomly ceased working a few days ago, too.
[General Questions and Answers] silky28:
Hey all,

A few years back I bought a spare phone off ebay. My main phone just broke and when I went to activate the spare, of course, it was imei blacklisted. I don't care that much since I have little $$$ into it but I've been trying to read up on the blacklist and have found little information.

After some research it seems that there are companies who claim that they can fix the problem (I've seen imiefix.com discussed on this board). I have no intention of doing that to my phone since the phone is worth less than the cost of the service but I struck up an email conversation with someone who claims to perform the service. In the discussion he told me that he actually clears the IMEI from the blacklist of certain companies and does not change or mask IMEI's or do anything else to change the phone. (he has provided me videos showing a phone on the blacklist before he does what he does and how the same IMEI is off the blacklist after his service) but I am still skeptical.

The main question I asked him was whether his service only removes the IMEI from the individual carrier's blacklist or if it removes it from the national and global blacklists (ie. will his service remove a T-Mobile blocked IMEI only from T-Mobile but leave it globally blocked for other carriers). In is response he provided this information he told me that phones are blocked for 2 reasons, 1) lost or stolen phones 2) failure to fulfull contractual obligations (ie. didn't pay subsidy). He told me that only lost/stole phones end up on the global or national blacklist, and that phones blocked for failure to pay are only blocked by the individual carrier.

is this information correct?

anyone have experience with these services?

I am conflicted about this blacklist thing. Yes, we need to find a way to protect consumers from theft and even carriers from fraud, and we shouldn't encourage the sale of stolen goods. But who does it benefit? the consumer? of course not. It is almost exclusively to the benefit of the carriers and manufacturers who get to pump more and more of their exorbitantly expensive phones into the market while thousands of useless phones sit around or end up in landfill. And, since there is such a delay in the time that it takes for phones to end up on the blocklist, and since the carriers seem to do nothing to stop fraud (ie. selling phones then reporting them stolen) the only people this hurts are the poor saps who dish out hundreds for a phone on the aftermarket just to have it locked on them a few months down the road.
[General Questions and Answers] silky28:
So playing around a bit I just saw a Tmobile phone on Ebay that is blocked by Tmobile. The ad gave the IMEI so I called Tmobile to enquire. The friendly CS rep checked and said the phone is indeed blacklisted but it is still attached to the account holder's account and she cannot tell me anything else. So long story short, person probably sold the phone to Ebay shop and told them it was Tmobile blacklisted. The store will sell the phone as having a bad IMEI but since it is only Tmobile blacklisted it can still be used on AT&T. Since, however, the phone is still on the other account it is likely that (and there is nothing to stop) the original owner will claim it lost or stolen within a few months, especially if they have theft protection. The new buyer, therefore, will get a phone to use for a couple of months until it is globally blacklisted but by then the Ebay complaint window will be closed so purchaser will be stuck.

They need to find a way to fix this. Instead of keeping the phone on an active account all blacklisted phones should be put into default accounts and cannot be changed in any way. Of course the carriers have no interest in doing this.
[Android General] felzam:
Thanks, I've been waiting weeks for this!

Can confirm TWRP works on my GR3 (TAG-L13) and was able to SuperSU from there.
[Android General] mac12m99:
Good :)

Now you can also install xposed and other mods, i'm uploading a zip that fully re-stock this device, so if something goes wrong you can easily restore :D (some kind of "official firmware" but based on my dump, because official does not exist)

edit: ah ok, you have a TAG-L13, so probably with this firmware your sim wont work :(
[Android General] MedNour:
what about tag l21
[Android General] mac12m99:
This guide will work and TWRP also, TAG-L01 and TAG-L21 are identical, the only problem is dual sim(so if i will succed compiling cyanogenmod, you probably can't use your sim)
[Android General] MedNour:
good news then but i will be able to use 1 sim and micro sd ????
[Android General] felzam:
Cyanogenmod would be wonderful! I have major push notification problems while on WiFi and would love to move away from EMUI. Would it work on different versions though (on any TAG-LXX)?
[Android General] mac12m99:
Micro sd not, but probably all sims will not work

Yes :D

I have compiled succesiful, but don't boot, i need more time...

Settings, protected apps, allow all apps that you want notification :)

Yes, but in dual sim devices proably sim will not work :(
[Android General] TheEversor:
Just wanted to say i'm also looking forward to see if an update to Android 6 is possible.
[Android General] mac12m99:
There is only a stock rom on internet and is android 5.0(for TAG-L22), so for now no 6.0 :(

My goal is compiling cyanogenmod 13(whitch is based on android 6), but it will take a lot of time.
[Android General] TheEversor:
I'm absolutely new to this kind of things, but would it be theoretically possible to cook the huawei rom for the Honor 5X (also known as GR5) that is Android 6, adding the drivers of the official Android 5 huawei rom of the GR3 or TAG-L01 ?
[Android General] mac12m99:
No, because has different hardware, i have to found a device that have the same processor whitch have android 6.0, but i will do late, first i have to build cm12.1(based on the same android version that have this device)
[Android General] Triglia:
Hang on boot and adb driver problem

Dear friends, I made a little mess and I need your help. :confused:

I followed the guide by mac12m99, but I did some mistakes. A little recap:

1) I became developer (7 taps on build) -> OK

2) I enabled ADB debug, OEM unlock -> OK

3) Connected the phone while OS was running and did "adb reboot bootloader" -> OK

the phone booted in "fastboot mode". Now I had a problem: I cannot connect the phone anymore: if I tried "adb devices" no device was found. I think this is a driver related problem (I use Win 7 64bit). I googled a lot, but I wasn't able to find a working driver to solve this issue.

And now I made my BIG mistake! Since I couldn't connect the phone correctly to unlock the bootloader, I tried Kingroot -> success. But I don't like Kingroot much, due to many permissions requested. So I switched Kingroot with superSU using a guide from another forum (sorry I cannot post links).

During the process superSU asked for upgrading and I did -> success, but... after reboot the phone hung on boot.

Panic! :( tried to factory reset it, but after boot still hung.

Now I don't know how to proceed.

So I need your help:

1) Where can I find the correct driver to connect Win7 64 bit to the phone in fastboot mode ?

2) How could I revive the phone ? I thought if I successfully connect the phone in fastboot mode, maybe I could unlock the bootloader and see if the boot proceeds.

Thank you for your help, and sorry form my English and my ignorance.
[Android General] Triglia:
Sorry but this content has been removed from Mediafire. Could you upload it again? Thankyou
[Android General] Triglia:
Hang on boot and adb driver problem - update

OK I solved the first problem: it was a driver related problem as suspected. I succeeded to flash recovery and from there superSU, but after reboot still hang. So I need the stock image to revert the situation. I didn't understand well which image I should use: the first one from Mediafire (not available) or the second one: dumped from your device ? If I should use the second one: what is the procedure? Thank you
[Android General] mac12m99:
Did you unlocked the bootloader?(i guess yes, because twrp booted)

If yes, you have done a factory reset, so it needs 3-4 minutes to re-create cache and then will be working :)

They have blocked it :confused:

If waiting don't work, for now do this:

-go here

-search for gr3

-download firmware

-flash it using twrp

If you have a TAG-L01 SIM will not work, but device is usable.

If you use the second one you can only flash stock recovery, because system partition is refused by bootloader :confused: , but i think you can flash it using adb and twrp(an advanced method, i you want i can explain :) )
[Android General] Triglia:
Since I'm using TAG-L01 TIM branded, I think I should use your dump. Please explain me how to do. Meanwhile I'm downloading your image.

What do you mean that the SIM won't work? I cannot use it as a telephone anymore???!!!

Thank you.
[Android General] mac12m99:
So waiting have not worked?

-boot into twrp

-place system.img in internal sdcard

-type this:

adb shell
dd of=/sdcard/system.img if=/dev/block/mmcblk0p22

-flash boot.img using the recovery method(install-install image ecc..)

-reboot and wait 3-4 minutes

But if my firmware wasn't deleted, you can restore by easily flash the zip :mad:

Because my firmware was deleted, i've linked to you the only "official firmware", that is for the TAG-L22, i've tested it on TAG-L01 and everything work but SIM not(this firmware is not branded), it means that using this will not work, but if you install another that work, SIM will work :)

Welcome :)
[Android General] Triglia:
Waited for about 15 min. but still hang.

In the file image "zt...G-L01_stock.gz", there is only 1 file "HUAWEI TAG-L01 stock" about 3.8Gb uncompressed. There is no "system.img " file.

I cannot restore a different ROM, I need to use the phone. Please could you send me the correct file? I sent you a private message with my direct contacts.
[Android General] Triglia:
[SOLVED] hang at boot after Kingroot to superSU switch

After 2 days of test, and with the essential help of mac12m99 :highfive:,

I succeeded to revive my phone. It was necessary to flash the "update.zip" from the first post (but unavailable in the last days) and my phone was back, then I started again from scratch.

A suggestion: DO NOT try to switch from Kingroot to superSU using "superSUME", because you'll end in soft brick as I did.

If you gained root access through Kingroot and you want to switch to superSU, you should do the following:

1) Be sure that Kingroot is installed and working

2) Disable root from Kingroot itself, and uninstall Kingroot (you can do everything within Kingroot's options)

3) reboot in recovery (TWRP)

4) install superSU from TWRP

5) reboot: you are rooted again but with superSU and the phone is still working :good:

So, a big THANK YOU to mac12m99, for his precious help and patience and happy modding to everyone.
[Android General] mac12m99:
I have updated the download links of stock rom and dump, now this links works :D

Thanks to Triglia for the upload! :)
[Android General] mac12m99:
Cyanogenmod 12.1 is out! :D

http://xdaforums.com/android/development/rom-cyanogenmod-12-1-huawei-gr3-p8-lite-t3454677
[Android General] pinketta90:
help me!

hi. i have the same problem. i have a soft bricked my new gr 3. it's in bootloop on tim animation. how can i flash update.zip? through inside recovery or by twrp? i cant access to fastboot through adb. device isnt found. but i can access in fastboot mode with soft keys. help me, i am very sad!
[Android General] pinketta90:
QUOTE=pinketta90;68667059]hi. i have the same problem. i have a soft bricked my new gr 3. it's in bootloop on tim animation. how can i flash update.zip? through inside recovery or by twrp? i cant access to fastboot through adb. device isnt found. but i can access in fastboot mode with soft keys. help me, i am very sad![/QUOTE]

[SOLVED] My smartphone is yet here. thanks to Triglia and this 3d.
[Android General] mac12m99:
You can by twrp :)

If you don't have installed, install using fastboot:

fastboot flash recovery twrp.img
[Android General] mac12m99:
Sorry for my absence, but now i'm back! :D

I've fixed SIM and camera in cm12.1 :)

http://xdaforums.com/android/development/rom-cyanogenmod-12-1-huawei-gr3-p8-lite-t3454677
[Android General] Alkatraz82:
hello i have the same problem I find myself on the phone with tim logo without being able to go ahead, I made the bull**** to switch to super kingroot of using super sume, I tried to download the update.zip file but I can not because the problem rislovere he says corrupted file potrersti help me please I'm stuck with my phone and I can not use it.
[Android General] mac12m99:
I'm tested and update.zip can be downloaded without any problems, maybe you mean "i have downloaded but i can't flash it because it say corrupted file?", in this case rememeber that you need to unlock bootloader and install twrp :)

if not, please specify better
[Android General] Alkatraz82:
parto dal fatto che avevo lavorato con kingroot poi volendo passare a super su ho installato super sume ma al momento di riavviare il mio smartphone si è bloccato al logo iniziale senza andare avanti lasciato anche un ora ma niente è rimasto sempre con il logo, cosi ho deciso di scaricare update.zip ma quando vado a fleshare mi dice che il file è corrotto, e cosi non posso procedere da twrp non posso accedere perchè la mia porta usb dello smartphone è rovinata, posso solo cercare d'installare da update ma non riesco, per favore come posso risolvere questo problema? siate pazienti grazie mille.

---------- Post added at 07:22 PM ---------- Previous post was at 07:13 PM ----------

forse con update.app potrei risolvere ma io non riesco a trovarlo da nessuna parte, come posso trovare questo file?
[Android General] damastergame:
Please help... stock on bootloop after rooting, bootloder is lock, y trie to flash recovery :

C:\adb>fastboot flash recovery recovery.img

target reported max download size of 134217728 bytes

sending 'recovery' (11456 KB)...

OKAY [ 0.887s]

writing 'recovery'...

FAILED (remote: failed to get download permission because status is locked!)

finished. total time: 0.902s
[Android General] mac12m99:
You can't flash recovery because bootloader is locked, if you have TAG-L22 you can fix using stock firmware, if not the only way is to unlock the bootloader and then flash(check the first post).

If you don't use mobile data you can try also my cm12.1 :)

PS

what root method you used?

I have a lot of report about this issue with kingroot, but when i was using official firmware i've done it without problems, i don't know why so many people have this issue :confused:
[Android General] nader97:
Is this a CM13 rom for huawei GR3 or what ?
[Android General] Roldan1983:
I got the same error... What did you do?
[Android General] mac12m99:
You have to unlock bootloader, flash recovery and then flash this(or the dual sim variant, if your device is dualsim, check first post).

If you don't want to unlock the only way is to use the dualsim variant(because is the official one so can be flashed in stock recovery).
[Android General] Budi Fauzan:
thanks for your guide sir. but i want to ask you, because this thread is for huawei tag lxx, and p8 lite i want to ask something. if i use a p8 lite rooting method, will it works for my tag-l32 ?
[Android General] Budi Fauzan:
before i unlock my bootloader, should i backup my DRM keys ? or it doesn't necessary ?
[Android General] C4lM:
what?

#noobquestion :)

If i install p8 lite's official 6.0 ROM on tag-l21, wil it work?
[Android General] antonioroa:
Please HELP: Huawei TAG-L23

Hello from Colombia, South America.

I have a bricked TAG-L23 after one attempt to root via Kingo Root. I can access the menu recovery and I can, posibly, reflash a valid image for this model.

I downloaded your dualsim TAG-L22 but is not valid for flash via recovery menu because my phone is L23. How I can flash TWRP in my L23?

Please help.

Thanks.
[Android General] ervius:
Hi all, from this little bat, you can change TIM boot logo to original huawei boot logo:

http://www85.zippyshare.com/v/Gb9aaSo3/file.html

modified script from original:

http://xdaforums.com/p8lite/general/solved-how-to-change-boot-animation-t3263160

use it at your own risk, I made and used it and now huawei logo on my P8 Lite Smart phone, no more TIM logo at boot

(Only for boot logo, not for boot animation, for it refer to original script of other 3d)
[Android General] mac12m99:
I was trying to do something like this time ago, and i hard briked(flashed a non-compatible logo.bin), so i wouldn't try anymore, but thanks :)

Someone other confirm this work?(can hard-brik do at your own risk)
[Android General] ervius:
maybe you used wrong size image into logo.bin, with this device, it worked well or I didn't post it.
[Android General] mac12m99:
No, i've flashed wrong logo.bin (taken from another mt6735 device) thinking that i will be able to restore using fastboot, but i was wrong in this phone if wrong logo is flashed there's no way to recover :(

But now i've tried your logo.bin and it was fine, thanks a lot, i will add on firstpost :)

PS

where you've taken this logo.bin?
[Android General] ervius:
I've found image in 3d mensioned by me, dedicated to P8 lite, same resolution, build logo.bin with this tool (only after seen it was compatible with the P8 lite smart cpu!)

https://sites.google.com/site/kadanutilities/home/logobuilder-en

and changed on bat the partition to overwrite: was different section that the one for P8 Lite.

and remember, I tested it on my own phone, and it is from ITALY and branded by "TIM"! so other way, could cause problems on your phone, but if you have same mine (Italian P8 Lite Smart Tim branded), I'm quite shure that you will be able to flash it without problem.
[Android General] mac12m99:
ok thanks for the info ;)

I have the same and in fact it worked, but all TAG-Lxx is the same, so it will work on every :)
[Android General] mastermoon:
hello guys.. trying debrand my p8 lite smart i forced the update of the wrong file and now ii can't boot nor get in fastboot mode... only black.. if i connect the usb to pc i ear the sound of connection and disconnection... before that i has unlocked bootloader and twrp.. can i have chance to rebirth the phone?
[Android General] mac12m99:
What wrong file you've flashed?

Are you sure you can't get into fastboot mode?

Try to presso power button + volume up for some seconds, you will enter boot menu, select recovery or fastboot.

If you can enter your phone is ok :)

If not, you device is on and you can't reboot?

Try to connect to usb and give "adb devices", if there is any device connect you are ok, give "adb reboot recovery" and you are now in twrp :)

If not the only way is let it discharge...

To unbrand try : this guide(without patch, is not working)
[Android General] mastermoon:
i forced the wrong update.zip and the phone shutdown.. the screen stay black and if i connect to pc is recognized as mtk usb port...

EDIT:

i found a sp tools flashable rom for GR3 TAG-L21C328B128 and seems is unbricked... i powered up phone and it's have the original tag-l01c212b123 stock rom... it's normal?
[Android General] mac12m99:
If you flashed a zip made for TAG-Lxx you are ok, if you flashed another device you may brick(because of wrong kernel).

What? You made SP Flash tool working!?

Can you send me the files you used?

no :confused:

It seems you are a little confused of what you are doing on you device :D
[Android General] Mammt_:
Hi, i have a p8 lite smart totally unrooted and with unlocked bootloader. Today I wanted to update the firmware using the Huawei firmware finder and it managed to get an update named TAG-L01C212B127, next the phone as rebooted to install it. Once installed the phone can not fit on Android remaining firm to bootanimation and I do not know what to do. I can enter in the stock recovery, pls help
[Android General] mastermoon:
Enter recovery and try to do a full wipe..
[Android General] migliamario:
good morning friends,

anyone can help me?

My Tag-l01 is on tim logo and wont boot...this after the OTA update. My bootloader is locked and if I try to flash update.zip the update stop because the signature is wrong! can I solve my problem???
[Android General] mac12m99:
You need to unlock bootloader to flash this file.

What update you've flashed?

Try first to make a factory reset from recovery and wait some minutes(first boot will take a lot)
[Android General] migliamario:
I'have not flashed nothing...OTA Update.

Yes I've do a factory reset but don't wont start...I've wait 1 hour.

The bootloader is locked.

I think that I've to find the update.zip with signature...someone can help me?