yashsingh1/xdaforums huggingface dataset:
[Huawei Ascend Mate 2] :
No, the bootloader code is still required. All I am going to do is modify the source via a hex editor so that I can input a code of my choosing and force it to accept that code and thus unlock my bootloader. That is very possible ;). Should of done this already but I wanted to give Huawei a chance - but they failed.
[Huawei Ascend Mate 2] arcadesdude:
I didn't know you could do that. Is it essentially just flashing your modified bootloader partition to the phone using adb like we flash the recovery partition?
[Huawei Ascend Mate 2] :
Pretty much, but not with adb. Using fastboot.
[Huawei Ascend Mate 2] xordos:
also, i guess you also need disable the verification chain? but how? I heard it probably start from very beginning, ROM, a real read only rom. if you flash hacked aboot, sbl probably refuse to boot it, right?
[Huawei Ascend Mate 2] :
With a bootloader being locked you are presumably limited on what can and cannot be flashed. With that in mind should a modification be incorrectly done for a device with a locked bootloader then it would be safe to say that the flash would be denied and no harm done. Because I will be modifying the source to accept my personal code then this will not have any affect towards flashing. The device will even accept it. Then, when I enter my code and reboot, the device will simply say it is unlocked. The only catch to this though is that if I flash back to the original then the bootloader should technically relock itself. I will open a thread on this procedure down the road when I get time and even include my mods so others may compare it with the stock to see the differences.
[Huawei Ascend Mate 2] xordos:
Regarding the limitation, early I thought you are going to modify/repackage the UPDATE.APP, as that way, if (a big if) it works, ideally you can flash to any partition. (There is some thread in xda that discussion about read/repackage the huawei UPDATE.APP)

But as we discussed briefly long time back, this whole thing is really really risky, if the booting path to fastboot got damage, then pretty much the phone is hard bricked.

Probably if you stick with flash with fastboot, then the risk will be lesser but man, this is scary stuff.. :)

Regarding the validation chain, I got info from following article:

http://www.newandroidbook.com/Articles/aboot.html

A few paragraph after the Figure One.

Let's see...

PS, maybe you can continue try some different email address and sent at correct time to Huawei for the code...

PS2, another thought, maybe inject a superSU to the UPDATE.APP system image will work? not sure how strict they are validating when flashing UPDATE.APP and/or when booting the system partition.
[Huawei Ascend Mate 2] :
I won't be using the update.app parsay. Merely needed it so I can locate the images I want by viewing it with a hex editor and then extracting them so that I can solely focus on those images using a hex editor and once I make my patch(s) then I will use fastboot to flash those images to their respective partitions on the device. It really isn't that risky as long as you know what to look for. I won't be that guy that says "oops" in this case lol. So, I'm not worried about possibly bricking this device one bit :).
[Huawei Ascend Mate 2] ScoobSTi:
Just curious, what are you planning to do that requires an unlocked bootloader?
[Huawei Ascend Mate 2] :
Something lol :-p
[Huawei Ascend Mate 2] Iguanadon:
I'm not sure why you can't get the code from Huawei ...but I'm kinda glad you can't. ;) seems your gathering nice info about this phone.
[Huawei Ascend Mate 2] ScoobSTi:
Just in case you're being super extremely nice and kind and trying to make a ROM for us, the other developer has hit a huge roadblock on CM11/12 you should know about.
[Huawei Ascend Mate 2] xordos:
Even he is not plan to build CM, but as the man who build first recovery for us, I think he wont stop until he can play with his own baby in his phone. :D
[Huawei Ascend Mate 2] Kostyan_nsk:
1. How are you going to flash image via fastboot if your bootloader is locked?

2. You have to hack fastboot image to pass throuth unlock code verification without or with some random code. But even if you do so, you won't be able to flash fastboot image via fastboot even with unlocked bootloader.

I would'nt touch fastboot at all 'cause it's a high risk to get a hard brick.

I have found unlock code in some partition of my device, but I dunno was it there initially or was written there after unlocking. If the first case is and fastboot just compares entered code with saved one in device, then you can try to make update.app with injected su, as xordos offered, to be able to read this partition.
[Huawei Ascend Mate 2] :
Injecting su into the update.app woukdnt work. The update.app has it's own crc and such. So to simply say, it won't work. You also answered your questions with remarks 1 and 2. One exception is that yes, you can flash the image. As for risks, it's only there if you mess something up - development typically is about taking risks ;). The fastboot image won't technically brick the device anyways. At best a soft brick may occur, but to be honest since "bricking" is up for discussion; bricking can occur simply by making a change to the build.prop file and not fixing it's permissions prior to rebooting. Unless you "hard" brick the device, then it can always be recovered.
[Huawei Ascend Mate 2] :
You said the image or images can't be flashed with a locked bootloader, while yes is technically true, but understand that it isn't 100%, because you see, when your device recieves an update initially the devices bootloader is expected to be locked, right? Yet, magically enough the update goes through, the phone reboots, you either hate or love the new update. Something to think about before actually saying an image can't be flashed :). Instead, I would have you ask yourself, "how?".
[Huawei Ascend Mate 2] :
And best believe, I want to play :D
[Huawei Ascend Mate 2] Kostyan_nsk:
Well, if you suppose that modified update.app wouldn't work let's think it won't... ;)

Don't confuse flash via stock recovery and locked fastboot. Try to flash recovery.img and see what fastboot will tell you. And also there's no image named fastboot, so you simply can't execute command "fastboot flash fastboot fastboot.img"

And don't confuse corrupted system partition with fastboot partition. If fastboot won't boot how will you flash images to recover your device? I haven't heard about any PC flash tool for Huawei (except devices on MTK). Saying hard brick, I was meant that you won't be able to unbrick it softly.
[Huawei Ascend Mate 2] :
I'm taking a big leap here but I am going to assume that you have never studied the processes or methods typically used for applying updates such as images, huh? I have been tampering with this type of manipulation since HTC. If you are familiar with HTC products then you may be familiar that HTC devices not only have a locked bootloader but also come with S-On. So, even if the bootloader is unlocked you are still limited unless you gain S-Off. A modified bootloader will get you that S-Off as well as other methods. Back in the day, an HTC owner would have to unlock the bootloader before gaining S-Off, but over the years, it is seen that most of the time you can actually gain S-Off, an unlocked bootloader, and never request support from HTC themselves. Take a guess how this would work? By flashing /writing the required images to their proper locations. This concept isn't much different with most Androids, with the exception of S-On and S-Off since that is an add on security feature which HTC themselves use. Not my first rodeo is what I am trying to say here :).
[Huawei Ascend Mate 2] :
http://xdaforums.com/showthread.php?t=2642403

You say it can't be done? Then you may want to ask yourself how is it possible after you read the xda thread in the above link :). Seems this xda member knows a little something too ;).
[Huawei Ascend Mate 2] Kostyan_nsk:
Hahaha :laugh:

In my device fastboot always returns "FAILED" when I'm trying to flash efi.img even with unlocked bootloader. And it doesn't have "fastboot" partition. There's "fastboot2" partittion and update.app contains it but it's not actually where device boots from, boot starts from block mmcblk0boot0 and it has no name. So it looks like Huawei made work on mistakes. :)

Dunno how it's in your device, we''ll see what you'll get... ;)
[Huawei Ascend Mate 2] :
:) sure thing.
[Huawei Ascend Mate 2] xordos:
Great readings...

So, from the HTC and Mate success, can we say the validation chain is not in place for many phones, or they are just not that strong enough so we can just update some (ex,) checksum while we hack some bytes? You know, usually when I see anything related to key/signing stuff, I feel it is hard to break.. :)

Play safe and let's see...
[Huawei Ascend Mate 2] Kostyan_nsk:
Any news?

Keep us updated. :)
[Huawei Ascend Mate 2] :
No, nothing yet. Got side tracked with making some changes to the device tree I use to build TWRP for my primary device. OmniRom 5.0 is giving issues unfortunately and was discussing them with Captain_Throwback, Dees_Troy and a few others. Currently syncing the Omni 4.4 branch real quick because I know my builds will work properly with it. z31s1g makes remarkable TWRP themes but currently my TWRP build won't play nice with one of his custom features which is the ability to change the themes color. I found the culprit in my BoardConfig.mk file and made a quick fix so now I want to test this fix for confirmation and to update z31s1g on the matter per request by him.
[ONE Q&A, Help & Troubleshooting] gray_wolf:
Hey folks

Lately my OPO started to have some hiccups with battery. So the problem is that once my battery percentage goes below 40% my OPO turns off. When I try to turn on the phone it never boots up. Any idea why its happening and solution will be greatly appreciated.

Note: I tried to have full charge cycle (going from 100% to zero)but it never worked. I tried charging phone while its tuned off and turn it on once its fully charged but it didn't work either.

Thanks
[ONE Q&A, Help & Troubleshooting] PoisonWolf:
Sorry to tell you but your battery is likely physically malfunctioning and no amount of battery draining will fix it. Odds are, your battery has started bulging a little already.

Do you typically leave your OPO plugged into the wall charger for extended periods of time, even after it has reached 100%?

I damaged both my previous Note 1 and even a laptop batteries this way. Both would just shut off after dropping to a number like 50% or 55%. Both batteries had a bulge.
[ONE Q&A, Help & Troubleshooting] gray_wolf:
Here's my phone at almost zero charge just to test the battery
[ONE Q&A, Help & Troubleshooting] PoisonWolf:
So now it appears to be fine? It can go below 40%? I'm confused. Or are you saying that it happens intermittently?
[ONE Q&A, Help & Troubleshooting] gray_wolf:
Before I was in original CM 11S but after change my ROM it got back to normal and it goes below 40% by the way I know that its sounds so weird
[PDA2, XDA IIi, 2020i General] NeonPT:
selling in perfect condition, in box, with full acessories with warranty until july:

http://cgi.ebay.com/O2-XDA-IIi-Qtek...ryZ41343QQssPageNameZWDVWQQrdZ1QQcmdZViewItem
[One (M8) Q&A, Help & Troubleshooting] viscuosity:
Hey guys,

I'm currently running a HTC One M8 with Skydragon GPE rom w Kitkat.

I was just wondering if I need to flash a Sense ROM first before proceeding to converting my phone back to full stock?

I'm also S-on.

Thanks for your help!
[One (M8) Q&A, Help & Troubleshooting] xunholyx:
Run the splash they provide to return to Sense, then run the appropriate RUU for your MID to make sure you are re-partitioned correctly.
[One (M8) Q&A, Help & Troubleshooting] viscuosity:
Hey, I appreciate the reply. But I read somewhere that this is only applicable if I converted my device to GPE. Im only running a GPE ROM.

My device was originally running Sense 6.
[Galaxy Note II Q&A, Help & Troubleshooting] garbage911:
I did a search and most of the Wifi problems seem to describe knox security and bootloader issues.

Here, I wish to describe/discuss what seems to be a hardware problem in my n7100 note 2.

This occurs with stock and dr. ketan rom on 4.4.2 even with wifipatch applied (technically not needed).

OS 4.4.2

boot loader: n7100ZSUFNL1 (I believe this bootloader should be ok - correct me if I'm wrong).

model GT-n7100

ISSUE

- the wifi icon doesn't turn on or wifi drops out when the system is running hot. This happened the first time after I flashed a ROM/upgraded and I thought it was a ROM issue.

- however, more recently, I have managed to keep the wifi signal absolutely stable when i open up the back cover and run a fan blowing on the back/cpu area at the top back of the phone around the camera area.

- with fan cooling => completely stable

- without fan cooling => drops out when system under load or randomly.

for some reason, omega rom had a problem for me where it kept disconnecting irrespective of the heat

I have seen discussions of our phone overheating but this seems to be a hardware problem with the wifi module.

I presume that there may be micro fractures with the wifi chip solder (seems to be a theme in electronics) that may be causing wifi problems with overheating.

This happened with an iphone 4 voice audio processing chip once for me and the "online community" had figured out a fix by taping in a "pressure mount" for the chip.

//blog.lovefone.co.uk/iphone-4-faulty-microphone-audio-chip-problem

Any suggestions on taping in a heatsink or pressure against the wifi module?

Help would be appreciated. Just adding to the knowledgebase in the community.
[Galaxy Note II Q&A, Help & Troubleshooting] sms2000:
When Samsung adopted RoHS some range of devices plagued with badly soldered BroadCom chips. I personally know one S3 and two Note 2 (one is mine own) with all the same problem: no WiFi from time to time and likely no BT too.

I paid ~100 euros to change the main board with BC chip guaranteed working about half a year ago.
[Galaxy Note II Q&A, Help & Troubleshooting] garbage911:
Thanks for the quick reply and confirmation.

After ordering a new midframe; playing around with screws and disassembling it a few times; it does feel like a solder joint/connection issue.

I haven't heard much feedback from the net on this problem which is why i raised it.

Others on the net have mentioned loosening the screws securing the motherboard down. I will try that as well but I presume that with a loose solder joint; overtightened screws may warp the motherboard just enough for the connection to flake out.

THanks again.

PS - if anyone else has the same problem/suspicion; please chime in.
[Galaxy Note II Q&A, Help & Troubleshooting] garbage911:
So, in follow up.

Adding aluminum tape to the wifi chip didn't seem to work. I took it off and reseated the midframe where the antenna is located.

Still was getting dropped wifi.

Disassembled; took a small screwdriver and gently lifted the wifi contacts from the motherboard up so that it makes better contact with the midframe.

Seemed to help.

It's definitely hardware. Whether it's a problem with the WIFI chip or with the antenna; i don't know but it's somewhere along that line.

Crazy hardware gremlins
[AT&T Samsung Galaxy Note II] chavist:
Hello XDA family,

I've been using ezkat for a while and wanted to try a lollipop rom. Flashed Nameless worked flawlessly until I got to work and needed to go to my company's private website. No browser I used would pull up the site on Nameless or any other AOSP rom. Has anyone ever had this happen and how did you fix it. Ezkat is TW 4.4.2 and Nameless is 5.0 Lollipop.

Thanks in advance
[Xposed General] R_Chin:
Hello, I want to remove the little quick settings bar on kitkat 4.4.2 (the one that shows up in the notification panel). I just want to get rid of it to make the notification panel more like jellybean and clean it up. Is there any module to do this or does anyone know a good way? Tjhanks
[Fire HD 6 and 7 Q&A, Help & Troubleshooting] Prisonedalien:
I am on windows 7 and for some reason I can not drag and drop a file into my Fire HD 6. It also says the driver is not installed correctly but I can still view the internal storage on it. I have looked for a solution but have found nothing. Any help would be appreciated. I wish they made Androids less complicated...
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] QA Bot:
Q&A for [ROM][MK2] TriForceROM 5.4 - It's a Secret to Everybody! {2/10/14}

Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.

Before posting, please use the forum search and read through the discussion thread for [ROM][MK2] TriForceROM 5.4 - It's a Secret to Everybody! {2/10/14}. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.

Thanks for understanding and for helping to keep XDA neat and tidy! :)
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] liquidrea1ity:
ng5 firmware

I'm getting a message about being under a 10 post limit, so I don't know who's going to see this or not, but here goes:

I recently replaced my old s4 with a new tri band model running ng5 firmware. Even on the Sprint 720t thread, it has been difficult to find anyone running a firmware this new. I know there are issues involved with the Knox bootloader when trying to downgrade firmware, but it's it also a problem to flash a tw Rom based on an older firmware?

My last S4 was on mf9 the whole time, running nothing but aosp roms, so I didn't have to worry about Knox and it's associated issues. I haven't even rooted this new one, I'm just trying to get all my ducks in a row before I start flashing, especially because I plan on staying with Touchwiz for a while this time around.

Would I be better off just waiting for sacs lp Rom based on a newer firmware? Again, I haven't had to deal with Knox, but I'm not really concerned about the warranty, I just want everything to function. I've read a lot of posts about users with borked Wi-Fi and the like, and all kinds of work around for Knox issues.

Sorry that this has become such a long post, and thank you for any advice.
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] mcbmail:
Questions before going past 3.1

Hello,

Thanks for the great work on this ROM! I had several questions before i tried to proceed past TF 3.1 & MF9. I think i have a handle on how best to upgrade firmware from the "All Sprint Firmwares" post. But i have some questions as to what it will look like afterwards.

My initial setup was a rooted stock ROM of MF9 on a non-spark Gs4. I was able to flash and update to TF 3.1. I have the most current Philz as my recovery.

1. Can i go from MF9 straight to MK2 for the latest TriForce Rom?

2. If i do flash to MK2 will that make my current build inoperable? That to say once i flash the firmware by the Odin instructions will i be able to boot into my 3.1 Rom as previous?

3. Can i go straight from 3.1 to 5.x once the firmware is done?

4. One of the main reasons i've stayed at 4.2.2 is the move app to SD functionality. (As well as trying to stay away from Knox.) Does the 5.4/MK2 build have move apps to SD capabilities?

Thanks again,
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] cessch:
return to stock

hi,

since knox came out i am always nervous about returning to stock on a samsung device i have a sph-l720 i want to sell but first i have to return it to stock. can anyone help me?

build triforcerom 5.4 baseband version l720vppufnae

my email is cessch yahoo com
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] bilgerryan:
Just Odin a stock ROM from www.sammobile.com
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] Painkiller7:
Hi everyone,

Phone - SPH-L720 / Sprint Galaxy S4

Rooted - Clockwork

TriForceRom 5.4 - Full install

Android 4.3

I installed the updated version of TriForce Rom about 2 months ago. It has worked great until the last 2 days it my phone began rebooting periodically throughout the day.

- Sometimes it wont even get past the "Samsung Galaxy S4" logo.

- Sometimes I can't get it back on without taking the battery out and back in after a few seconds.

- Sometimes after booting to the home screen and loading all the apps, within 20-30 seconds the "turn off / reset" window pops up and automatically turns the phone off without me doing anything.

- Sometimes when I press the power button to dim the screen the "Turn Off / Reboot" screen pops up and then 2-3 seconds later the phone shuts off. Other times the pressing the power button just dims the screen.

- If I leave it alone for a while it will automatically reboot 10+ min after it shuts off.

- The memory is 85-90% full so I deleted a bunch of apps and random files. It still randomly reboots.

- I noticed the top portion of the power button doesn't "click", but the bottom portion of the power button does make the little "click sound".

Is the rom acting up?

Is my battery shot and I need a replacement?

Is my power button bad and in need of replacement?

Hope someone can point me in the right direction to a solution. Thanks!
[Android General] zijin_cheng:
[YOUTUBE]nooxrzICb_c[/YOUTUBE]

You can buy the phone here for $130, and it goes down even further with a coupon code.

Finally got my blog up, so go ahead and click the link below to visit the text review! Its formatted much better than on forums :)

http://www.mobiletechasia.com/?p=30
[Android General] emipuscas:
app space question

Hi

I want to buy this phone but there's something i'm very interested in, and maby you can help me. How much space is there available for installing apps? I presume it has to give at least 2gb of the 16 it has built in. The biggest problem being the 4.4 wich saves all app data to the dedicated rom partition. I need many apps installed and am used with arhd custom rom's on my SG Note2.

Hope you can help me with this info to help me decide. (The easy way to find out is by accessing the Apps tab under Settings, and on the bottom it tells how much space is used from how much available)

Thanks in advance. Great review ;)
[Android General] zijin_cheng:
Thanks! Mine says 4GB is partitioned as internal and the other 7-8GB is the internal SDcard. Hope this helps
[Android General] pablimc:
some x9 issues

Whats up guys. i've got my x9 about a week ago and I had some problems:

-The front camera shows a little bit red light when taking a picture with low light

-The screen protector gets TOO lined so easily

-The screen sensibility is quite low, specialy while pushing "a". "s" and "l" charactersv in my keyboard.

Has anybody experiended some similar problems?

Cheers
[Android General] zijin_cheng:
Haven't experienced the first two, if the screen sensitivity is too low for you, you can change that by turning on gloves touch mode i nthe settings.
[Android General] Krystyna:
How about CUBOT X11 smartphone?
[Android General] zijin_cheng:
I really recommend getting a phone with the MTK6732/MTK6752 processor, it's much smoother, so don't get the Cubot X11.
[Android General] Krystyna:
Do you know Ulefone Be Touch this phone? I want to buy this phone, but Elephone P7000 is also good phone, which phone should I buy.
[Android General] zijin_cheng:
I recommend the Elephone P7000 over hte Ulefone Be Touch because of the bigger battery.
[Android General] jon sylk:
Cubot X9 battery life

[MENTION=4774219]zijin_cheng[/MENTION].... i read a review where it said battery life was horrible! Could you verify those assertions in regards to how you used the used the phone?
[Android General] zijin_cheng:
It's honestly average, but your opinion of how good the battery life will depend on YOUR usage. Check out the hard numbers here:

http://www.mobiletechasia.com/?p=30&page=3