Database Info

[Q] Huawei Y201 NFC U8666n-1 trouble

OK so I recently switched this neat, cheap and decent entry phone, and of course wanted to root and unlock the bootloader.
Using the technique outlined in http://forum.xda-developers.com/showthread.php?t=2066887 "[ROOT][CWM] Huawei Ascend Y201 Pro U8666" I managed to happily root the device. Meaning I could install droidwall and adfree, and uninstall one or two of the annoying Huawei apps. (Surprisingly there are less Vendor apps on this than the previous Ideos U8150 I had.)
So happy that that worked, I thought I would go to the next stage and unlock the boot loader, in preparation for maybe installing clockworkmod recovery. And eventually a ROM if I could find one that looked "safe" and sound.
Cranking up the "UnlockBootloader.exe" as before and clicking the unlock BOOTLOADER initiated something on my phone... However when I switched off my phone preparatory to rebooting, I found what I guess to be a bricked/borked device.
There's no vibrate, no flash on screen, no logo, no pink screen that other people talk about in the few reports I have found around the web. Just that the lower backlit soft buttons flash ten times and then nothing else happens. I can't even find information about what this obviously low level failure message means...
As you can guess, I have tried all sorts of things to get it going: battery removal; powering from USB while botting; any and all of the key press holds for boot; all to the same effect. Have tried several times to find anything similar on the net and can't seem to find anything similar. Especially the ten flash indicator
So my question is "Is this an absolute sign that the device is bricked?" I guess I could try to play the innocent and send it back under warranty, but I guess someone will realise it was my fault. Unless a memory failure happened at the exact time I was flashing/unlocking...
And a warning that same device owners should be careful when following the guide. I'm pretty sure I had everything as outlined. I'm running XP, didn't have it mounted, had fastboot off, etc... Although now its hard to check on the device to see if that was the case

and also
I should also perhaps add that before using UnblockBootLoader with root success, I tried the ICS "adb restore" directory traversal vulnerability, which is part of Root_with_restore, and was unsuccessful.
And that there's no life reported at a low, USB device level to my linux kernel, when plugged in now. So I can't even try a firmware patch using adb etc.

Of course I can't post a relevant cautionary note into the above mentioned thread, as I have yet to reach the 10 post milestone mark, enabling me to post in that section...

Hi,
Sorry for opening an old thread, have the same issue and just wanted to know if you manged to resolve this or it you just took it back to the shop?
Regard

No solution
No - I never managed to work out or find a solution. I just got a new one, and only went as far as the root'ing stage.
I have never seen an applicable ROM for this device anyway, so I guess it wasn't too much of an issue. And root'ing to get those crucial management apps installed, and also being able to remove some Huawei "cruft" is the real thing you need.

New Verizon Ellipsis 10 Tablet

I purchased the new Verizon Ellipsis 10 in late November. I believe the tablet was released for sale in mid November. My question is can it be rooted? I see the Ellipsis 7 and 8 can rooted. Wondering if anyone would be working on this or because it from Verizon no one cares. I can't find the tablet mentioned on any search that I do. I Have been checking daily to see if the device will have development on it. Thanks in advance for any information.

In the same boat. Need some help you smart tech guys out there. How can I root my Ellipsis 10?

I have the same tablet, and I do not think it could be rooted, at least not in the near future. The tablet comes encrypted (which I am not too happy about....I just noticed it) and cannot be decrypted, even if you do a factory reset. It runs fine as it is, but would be greatly enhanced if it could be decrypted. I also think there are very few devs on this forum that really care a lot about this tablet, so you may not see too much work being done on it.

Same here, just picked one up. Really hoping that there will be a root for this at some point soon. Someone please help us all out!

wish I would have saved the 50$ now, and got the Samsung tablet for free... it's OK, the biggest problem for me is the audio output being too quiet. all the "volume booster's" on the play store have been jenky, to say the least. if anyone has suggestions of a "good, volume booster", or work around, please let me know. thank you for you time.

Oh, No! Sadness!
mikekoz said:
I have the same tablet, and I do not think it could be rooted, at least not in the near future. The tablet comes encrypted (which I am not too happy about....I just noticed it) and cannot be decrypted, even if you do a factory reset. It runs fine as it is, but would be greatly enhanced if it could be decrypted. I also think there are very few devs on this forum that really care a lot about this tablet, so you may not see too much work being done on it.
Click to expand...
Click to collapse
Please, influence some senior devs to help you with this issue!

qtair7 firmware files
https: / / " www dropbox com " /s/f8ye7yw24mjqiva/IR7-20C59.7z?dl=0
just fix the text when u enter in address bar (-""'s,+.'s)

so i downloaded the IR7-20C59..7z package from the software upgrade/repair tool from verizon... I extracted the files and sent the boot.img to my tablet (qtair7) and used magisk manager to patch the boot.img then I used ubuntu to adb pull the magisk-patched-boot.img and modded it using abootimg and changed a few things from default.prop.. ro.secure=0 ro.debuggable=1 and drm.service.enabled=false .. (just saying im an amateur android enthusiast with little experience. ive played with image kitchens and compiled a kernel and ported a rom for the samsung on5 indie variant to have sound on my smg550t1. worked but all google services and apps crash constantly.. but anyways) i dont really know what im doing just saying this is what i did. repacked magisk-patched-boot-new.img then i sent the adb reboot fastboot command to my tablet and it fastboot flashing unlock , fastboot flashing unlock boot, fastboot flash boot magisk-patched-boot-new.img. fastboot continue, fastboot reboot.. the tablet boots and is rooted with magisk.. now i installed busybox to sbin. i have done this 2 times. im not sure if its the busybox or the magisk, but when i reboot following the above steps i get the verizon splash screen and in the bottom righthand corner of the screen it says modified. then boots to recovery. and now can only boot to recovery. now i have the upgrade/repair tool .iso on usb flashdrive that i use to repair my device from this state. which sometimes is a pita.. i have to continually attempt to repair sometimes it takes 2 days.. before it finally works.. i dont know why.. but it boots from fastboot the first time fine. and would like to know how to stop the soft bricking of my device or how i can obtain a twrp.img for this device QTAIR7.. please help ive been working on rooting my tablet for over a year. and feel that i am very close . thanx

Anyone interested in the system.img or any other partitions.. the Dropbox file is only the recovery flash files. I think. I know I couldn't edit system.img from the file with any kitchen but the system.img I dd'd from my device can be edited with kitchen. It's is 3.7gb so in not going to post unless someone can do something with them

Please share some info on the file you posted,..
jonthn41 said:
qtair7 firmware files
https: / / " www dropbox com " /s/f8ye7yw24mjqiva/IR7-20C59.7z?dl=0
just fix the text when u enter in address bar (-""'s,+.'s)
Click to expand...
Click to collapse
Hello, THANK YOU!! This is the most progress I have made in months! I don't know what it is, what it offers, or what to do with it yet, but it is a step!
Could you maybe say what it is, what it will do (how it helps..) and what to do with it?
My Verizon Ellipsis 10 (qtair7), even after wiping the cache, even after doing a factory reset, (even after 'disabling' all but FEW APPS!) JUST SPONTANEOUSLY REBOOTS every time i try to do anything, I try to watch a video it is fine for 5 minutes or an hour then I push volume up or touch the screen and suddenly it reboots, totally random, Clearing the cache gets it to works for a while but it always does it again it has NEVER been usable really,.. It pops up some screen often like"Google Play Services have stopped' something like that,.. Will this help with any of that? Make it more,. stable?
I wish I could just do ANYThING simple to make it better I just use it for video playback,.
THANK YOU!

I have the same tab with the same issues. Rebooting, random cut out and full on reboot. Just before it became target practice I decided to take it apart, just because that's what I do when I'm bored and my ADHD is taking over. I looked up the tab on youtube to see if there was any vids of how to get it apart and found a guy that said he fixed the with the tablet that no one could figure out. Meh I was like ok I'll give him a couple seconds checked it out. He found that all connections, screws holding boards down, and power were all loose. Once he went through all of that it had fixed the issues. So I tried it and damn, everything from screws holding boards down to power feeds were all loose, really bad loose. Got mine working good now. Haven't had issues since. Now if I can get it rooted I'll be good. And I suspect the loose connections would also potentially cause the battery to go bad from excessive amperage draw and charge in short time, over time.

S5 glitching in and out of monitor mode? or just a patchwork mess?

Im new to all this so pay no attention if its nonsence...
My S5 G900f has a qualcomm snapdragon chipset, that doesn't support monitor mode, which i believe means that it doesnt support packet injections or packet capturing (driver related?)
using the dsploit.apk for things like session hijacking, replacing web page images of a target and using script 'injection' to inject custom java script into a target web page, all sounds like things you'd need monitor mode to do. and if it is then i was able to do it with my S5.
I dont know a lot about coding or how it all fits together and communicates with the hardware, so i may sound completely stupid, but this has done my head in for ages, so why not get it out there.
1. when i attempted to upgrade from my first custom rom, i had a bit of trouble, softbricked my phone and then flashed the two roms in various, alternate, wipe, format and install combinations until it finally booted to set up, and i stopped panicking. but this caused features from the first rom to appear within the second rom.
ie: 3minute battery mod was installed through a add-on zip along with the first rom and nothing to do with the second at all.
2. inconsistencies within the file system, like file names that were apps included with the first rom.
3. dsploit.apk was bugged and crashed every 5 or 10 minutes. then would seem to glitch or stutter for a couple seconds before correcting its self and accomplishing its pen test.
4. i also remember watching green text in the terminal as it failed to connect or ID some part of the system but continued to retry in quick succession until it glitched and worked. (i think this was a similar type of app i was trying out at the same time but instead of GUI stutters, i could see the text rapidly stuttering and glitching.)
4. the dsploit.apk worked for me back then, even though it was temperamental. ive downloaded the apk a couple times since with various roms and ive got no where with it...
was thinking maybe different aspects of the two roms had been filed or grouped together and created unstable triggers within the software, allowing it to briefly communicate with the chipset. i may be way off, but ive been sat here waiting for someone to solve this issue forever, i thought id share my thoughts, on the off chance it turns out to be something and i can finally get my S5 into monitor mode without OTG cables and other unwanted auxiliary components.
thanks in advance
G Carter

Do a clean install of you ROM, and please, don't panick. If you want to have a good time flashing ROMs and stuff, panicking is the last thing you want to do, it will cause stress and stress can lead to not being careful enough so stuff like this happens, well, always, if you are experiencing issues do a clean install. Just boot into recovery (I recommend TWRP) and wipe everything except external sd. Open ADB and sideload the ROM (or, if you have enough memory on a flash drive, plug it into your android and flash it from there) and then Google Apps.

Is this a hard-brick?

I've had my Oneplus One since the beginning of 2015, up until now it's been honestly fantastic, with very few issues whatsoever, certainly nothing that has bothered me at any rate. That's up until last night;
My phone was lying on my desk next to me with the screen on updating some applications whilst I was writing on my computer - suddenly, it starts to vibrate, one continuous long note, I naturally picked it up and looked at it, at which point the phone turn itself off in my hand. That was unfortunately the last I ever saw of my phone alive. This happened at about 6PM yesterday evening, since then I've tried everything within my power to get it to work. I can't access the bootloader, in order to get to fastboot (which would allow me to fix all my issues by enabling me to refresh the device), nor can I access my recovery. The phone turns on and displays nothing, it vibrates, but that's it.
The phone was running the latest COS13.1.1 update (X1) which I had flashed the day before, it was running the stock kernel for the ROM, the ROM was however rooted.
I know a fair amount about android, I also know a fair amount about the OPO, to me, I think something about the LOGO partition has gone wrong. The LOHO partition being responsible for the images shown in the bootloader, fastboot, splash screen etc.... I'm just not sure how that would have happened.
Either way, I don't know what to do, the one doesn't register to my computer in fastboot or adb , so both those routes seem closed. I primarily use a Mac for my work, I'm yet to try plugging the phone into a PC.
I've submitted a ticket to OP, and have spoken to an adviser who moved my case to a 'specialist', but I'm yet to hear back on that one.
Any help would be massively useful, because I need this phone for my work, and just general communication.
Thanks for reading,
Ben

Here, try this http://http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732

Recover files from bootlooping Zenfone6

Dear all,
from the occasional reboot my Zenfone performed every now in a while (which didn't bother me too much) it now reboots so fast that it usually has not yet booted to the point where I could get data off the device before it reboots again.
As always, the backup is too old and I want to extract some data off the device. Most important are a few KBs worth of text notes. Here come some questions:
- It seems to be a hardware fault. Are there educated guesses what may give me a few last moments with the device to extract data? Heat? Freezing?
- Are there professional data recovery companies dealing with smartphones such that they can extract data from the chips without the phone working?
- As it is a Qualcomm device: Would any access via QDLoader work or would it be as unstable as the rest of the phone?
I appreciate any input. And yes, I know that I didn't backup often enough.
Thanks,
weaker

which rom are you on?

Sorry for the late reply.
I'm on stock ROM with Magisk. In the end when it became worse, I let Magisk restore the images but this definitely seems to be hardware-related. I also did no overclocking and I don't use games on the phone so I think that it is also not a thermal issue.
To keep the interested ones updated how it evolved: The situation is now as follows:
I tried to boot into recovery via fastbooting the TWRP (the one I used many times successfully for my phone) after one of the phone bootings was stable for enough seconds so have ADB contact and go to fastboot mode. I hoped to be able to interact more stabily in the recovery. However, the result was that the phone rebooted (I am unsure if the TWRP transfer was finished before that) and then the charging screen appeared and the charging screen remained constantly on, even when pulling the cable. It didn't react to any keypresses in that state.
I let it drain the battery (which was only a few hours as the screen was always on). Then, I plugged the phone in and it booted normally and was stable for 15 minutes or so, which gave me enough time to save the most important data. Phew.
This session however seemed to be the last farewell. The phone started to bootloop and I switched it off*. Now the phone has always a black off screen and doesn't respond to anything: Pressing (and holding) the power button, also in combination with Vol+ or Vol-. Also plugging a cable to charge doesn't create any reaction.
* switching it off worked the following way: The unlocked bootloader shows that one could press the power button to pause the boot. I can't think of why this might be a useful function in a normal situation. However, in my situation I could pause the boot and after some time it would switch off. That way I could at least break the bootloop.

you will have to boot into qloader to be able to recover your phone...
follow step by step exactly what is mentioned in the below link, ypu should be able to recover your phone :
Here’s how to unbrick Asus ZenFone 6 (Asus 6z) from QDLOADER 9008 mode - PiunikaWeb
Is your Asus ZenFone 6 (Asus 6z) hard-bricked? You can use still flash via QDLOADER 9008 mode to give a new life to your dead handset.
piunikaweb.com

Sorry to be the prick here, but next time post this in Q&A section. This one is for posting development (Kernels and ROMs)

OK, no offense taken. I thought that I would need to resort to some TWRP magic to get data off my device.
@MOD: Feel free to move thread where it fits best.

For the sake of completeness:
The phone is back from RMA. According to the sparse documentation they exchanged the mainboard and battery and some connector. Some firmwares are now newer than on the old mainboard (little surprise here). Bootloader unlock worked also on the new phone (some report that this would not work by default after an RMA, for me it did).
So, ASUS did a great job dealing with the issue.