yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] shrekpido21:
the same for me

i have the same problem after i flash afterburner kernel v2.1.2

it says settings hast stopped and music has stopped too. pls tell me what to do hoping for a help. thanks in advance!:)
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] munidra15:
Can you provide the

download links

for both of this files.:o:good:
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] dodo2244:
The threads are here .....

Optimax

https://xdaforums.com/showthread.php?t=3387218

Afterburner

https://xdaforums.com/showthread.php?t=3551465
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] lgg2miniGreece:
is this for J710FN ? ( galaxy j7 2016) ?
[Nexus 6P Q&A, Help & Troubleshooting] Chochiwpg:
I just flashed back to the factory image and rooted my device. Prior to wiping the device and flashing back to the factory image I was on a custom ROM. I had a tasker profile setup that would disable deep idle mode and light idle mode during the day and have it activate overnight. It worked really well on the custom ROM, but on the factory image I just get error messages. I have granted tasker root permissions as well and tried in terminal emulator with root permissions but still get error messages. Yet if I try the same command via adb shell over my PC it works perfect. Here is the command I am trying to run, any ideas why it would work on my PC but not on my device with root permissions granted?

dumpsys deviceidle disable (This will disable deep idle mode and light idle mode)

dumpsys deviceidle enable (This will enable deep idle mode and light idle mode)

Any suggestions would be greatly appreciated. Also thanks to [MENTION=1334806]italia0101[/MENTION] for helping me with the commands and tasker profile, it was working great on the custom ROM.
[Nexus 6P Q&A, Help & Troubleshooting] Chochiwpg:
Update:

I ended up flashing another custom ROM and now the shell command is working as expected. Not sure why it wasn't on the factoy image but it is now. Peace :good:
[Nexus 6P Q&A, Help & Troubleshooting] swa100:
Same problem here, really driving me nuts
[Xperia SP Q&A, Help & Troubleshooting] Sushrut52:
This is an android problem.

I have the MiFit app installed for my MiBand 2 which i bought a week ago.

Now when i install this app my phone does not connect to wifi network,shows "Saved" and "Disconnected"

Why would this be?
[HTC Cavalier] madds:
hi is there a cavalier rom available? i want to port it to the htc breeze. thank's in advance.
[HTC Cavalier] ibeqa:
Check Wiki, there is a Dopod C730 ROM.

Cheers
[HTC Cavalier] loser:
ROM

Is the RUU_Cavalier_DOPODASIA_CHT_1.16.708.7_1.43.50.00_108_Ship.exe english? I am not able to upgrade...the one I picked up in Spore ..:(. Any help appreciated.
[HTC Cavalier] ibeqa:
First, all Dopod versions of Cavalier are bilingual (chinees and english), you can change language in settings.

The Dopod ROM on WIKI is a Hong Kong ROM.

Cheers
[HTC Cavalier] loser:
Still No joy

Thanks ibeqa. I understand that.

I have a 1.16.707.7 English ROM while the HK Rom is 1.16.708.7. But it fails to upgrade with an invalid vendor id error(Error 294). Few folks at HO FO is using the 1.16.708.7 without any issues. wonder how....
[HTC Cavalier] ibeqa:
Yes, I,m using that ROM too but forgot to change the signature.

I have a question, do you have a HTC S630, Dopod C730 or the Softbank version? Can you tell me your phone specs from device information. FYI there is no "free" CID unlock for Cavalier right now and you could brick your device if you flash the wrong ROM.

Cheers
[HTC Cavalier] loser:
Dopod C730

I have a Dopod C730 bought from Singapore.
[HTC Cavalier] ibeqa:
Did you register your phone on Dopod (HTC Asia) Singapore. If not, try that and check if the rom for Singapore has the same numbers.

Cheers and Happy New Year
[HTC Cavalier] loser:
Hmmm

Already registered. The only ROM available is the RUU_Cavalier_DOPODASIA_WWE_1.16.707.7_1.43.50.00_108_Ship.exe in the site, which I already have. Wonder whats the difference between 1.16.707.7 and 1.16.708.7?

Wish you a happy 2008 as well !!!
[HTC Cavalier] ibeqa:
I think that error 294 is "country error", that is why it won't let you flash HK ROM. Differences between 707.7 and 708.7 are minor, nothing regarding the interface but I would say a bit faster.

Cheers
[ZTE Axon 7 Questions & Answers] nsabir:
First of all, i live in Bangladesh. I asked a relative of mine who lives in Sweden to buy me this phone. So, there is no way for me to send this phone back to ZTE.

Now let me explain how i got into this huge mess. I installed twrp successfully using this post - https://xdaforums.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379

i only followed part A of this post. Then i needed to root. so i tried to flash supersu 2.79 first but failed. Then i tried to flash supersu 2.65 as someone commented that they failed with 2.79 but succeeded with 2.65. However, after flashing supersu 2.65 i soft bricked my phone. i could still access twrp 3.0.2. After a while, i downloaded b08 update.zip and tried to flash it through twrp but failed. then i saw this post - https://xdaforums.com/axon-7/how-to/guide-root-xposed-safetynet-stock-rom-t3530906

and this post - https://xdaforums.com/axon-7/development/recovery-official-twrp-zte-axon-7-t3515715

And tried to update twrp to 3.03. which then hard bricked my phone. now i cannot access anything. when i try to start my phone it shows the zte logo for a second and the whole screen goes blank with the red led.

same thing happens with volume up+power and volume down+power. And there is no way to turn the phone off. So, i waited a whole day for the phone to empty it's battery and tried to boot to edl mode using volume up+down but Qualcomm HS-USB QDLoader does not appear. The only thing i can get to connecting to my computer is handset diagnostic interface.

Now only a brilliant dev can help me. So can someone PLEASE Help me.

Also i've found this post is very similar to my problem https://xdaforums.com/axon-7/help/bricked-a2017g-b03-help-please-t3487635

Update: Fixed using this post >> https://xdaforums.com/axon-7/how-to/a2017-4th-category-brick-repair-manual-t3585898#post71764940

& this >> http://4pda.ru/forum/index.php?showtopic=814221&st=0#entry60102671
[ZTE Axon 7 Questions & Answers] Abiram26:
Why can't you boot into EDL mode?

That's strange to me...

Did you try another computer to see if it pops up there?

Then try to reflash recovery if you can...
[ZTE Axon 7 Questions & Answers] nsabir:
yes i have. but in the device manager, instead of Qualcomm HS-USB QDLoader, Handset Diagnostic Interface appears.

Furthermore, computers does not recognize any adb device when i connect my axon 7 :(:(:(:(

what do i do??? :(:(

Edit: when i uninstall Handset Diagnostic Interface from device manager and then connect my phone with both volume keys pressed, at first qusb_bulk appears but after automatic installation of hardware software it's Handset Diagnostic Interface all over again
[ZTE Axon 7 Questions & Answers] Abiram26:
Well I did some Google'ing for you and I guess the things in these threads might be your best bet:

http://www.modaco.com/forums/topic/343587-guide-de-bricking-a-zte-blade/ (same thread-ish on XDA: https://xdaforums.com/showthread.php?t=2163493 )

http://www.modaco.com/forums/topic/337757-update-save-ur-bricked-v880-and-also-the-imei/

However all these methods are not tested with the Axon 7 and seem pretty risky to me...

If I were you I'd send the phone back to Sweden so the relative can send it back to ZTE.

I'm not sure if this falls under the ZTE warranty stuff so they might charge you a bit; anyhow it's still the better option than throwing this phone away I'd say.

I don't think I can really help you here, sorry :s

PS: If you are going to try these risky methods; don't blame me if it goes wrong...

EDIT: You might also want to try to go to the ZTE website and try to get some support from there (customer support, support from the forum/community ther, etc.)

Perhaps they can give you the right tools to unbrick your Axon7 :)
[ZTE Axon 7 Questions & Answers] nsabir:
:crying::crying::crying::crying:

if only i could boot into edl mode :(:(:(
[ZTE Axon 7 Questions & Answers] Controllerboy:
I don't think your phone is in such a dire condition. I was contacted by [MENTION=5334294]raystef66[/MENTION] only last night. He made the same mistake as you did, trying to flash SuperSU via TWRP on a locked bootloader phone. However, he didn't take all steps you took.

If I were you, I'd try to somehow prevent the PC from automatically installing the ZTE DFU (Diagnostics) driver. You say the device appears to be in EDL mode when you connect it (QUSB_BULK) and then it installs new drivers. Can you somehow cancel that process?

Here's a microsoft guide on how to prevent your PC from automatically installing drivers. Maybe try that and reconnect your device. It might get recognised as QUSB_BULK and then you can restore your stock recovery via the Axon7tool? If you can do that, it shouldn't be a lost cause?
[ZTE Axon 7 Questions & Answers] DrakenFX:
Send me a PM with your Hangouts, let's see if I can help.
[ZTE Axon 7 Questions & Answers] nsabir:
I have tried this, but axon7tool does not recognize any adb device. When i input adb devices command in cmd there is no device. However, it did get recognized as QUSB_BULK after disabling automatic driver installation through group policy. What do i do?? :(:(

Edit: after seeing this post - https://xdaforums.com/axon-7/help/2017g-dfu-mode-investigation-t3511191

i'm really panicking. "Handset Diagnostic Interface" is DFU mode. "handset diagnostic interface (DFU) (ComX)" i just ignored the DFU part when posting. Does this mean i cannot unbrick my phone???

Please Help
[ZTE Axon 7 Questions & Answers] Oki:
You can make Windows to use the right driver so you will be able to use axon7tool. So if you have problems connecting to your phone as QUSB_BULK, download Zadig to your computer and replace your drivers with WinUSB ones. Open Zadig tool, go to Options and activate List all devices. Then select QUSB_BULK in the drop down control at the top and WinUSB in the lower control. Then click on the button to replace the driver. After this, QUSB_BULK should appear in the Device manager and you should be able to execute axon7tool and flash TWRP 3.0.2-2 signed again and continue with the unlock procedure.

If you have the QUSB_BULK with a warning icon then you need to install the Qualcomm usb driver.

All the answers on how to return to a working state or not falling into a soft brick like yours were just in the thread of the guide you didn't complete. Devices with the Qualcomm Snapdragon 820 are unbrickable. So do not panic, and read the whole thread [GUIDE] [A2017G] Install TWRP, Unlock BL, Flash Custom ROM.
[ZTE Axon 7 Questions & Answers] nsabir:
My QUSB_BULK is not with a warning sign. And i have already used Zadig.

At first, i couldn't get past DFU mode. But after following [MENTION=4464865]Controllerboy[/MENTION] instructions i am able to get QUSB_BULK in my device manager. But it's all the same.

For axon7tool to work the computer has to first recognize my a2017g as a adb device. That's where the problem is. My phone is not being recognized as an adb device. When i use adb devices on cmd there is no listed device. I have already tried this with other computers but the results are the same. :(:(

what do i do??:(:(
[ZTE Axon 7 Questions & Answers] Oki:
EDL mode has nothing to do with adb!!!!! adb only connects to recovery or a booted system. fastboot connects to bootloader, and Axon7tool communicates with the EDL bootstrap. In order to use Axon7tool (to flash or backup boot or recovery partitions) your computer has to detect your device as QUSB_BULK. Obviously in that mode adb or fastboot will not find your device in a compatible state.

What can you do?

1. read the whole thread, not just the opening post. As advised.

2. Use Axon7tool to flash the same TWRP 3.0.2-2 you flashed before. It is signed, so the bootloader detects it as a valid ZTE image even when the bootloader is still locked.

3. Unlock your A2017G phone.

4. enjoy flashing and reflashing all the multiple roms, patches, etc.
[ZTE Axon 7 Questions & Answers] nsabir:
Sir, i don't u understand my problem properly. Let me give u a thorough description.

When i press and hold the power button the phone vibrates shows ZTE logo for less than a second then the screen turns off and the LED turns red.

When i press volume up+power same thing happens.

When i press volume down+power same thing.

And i cannot power off my phone no matter what i do it always stays at that state until the battery is empty.

Then if i press volume up+down at the same time and insert usb red led turn on.

And when i insert the usb in any of these states only one thing appears on my device manager is "Handset Diagnostic Interface (DFU) (ComX)"

But if i Uninstall Handset Diagnostic Interface (DFU) (ComX) from device manager and disable automatic driver installation through group policy then QUSB_BULK appears with a yellow sign.

If i use Zadig to install winusb driver then the yellow sign disappears.

U r telling me to read the whole thread. I have done so. But in DFU mode adb devices command doesn't list any device. If my computer doesn't see my device as an adb device how can i do anything.

I have also tried to use axon7tool -w recovery command since my device is in qusb_bulk mode. But cmd says no device detected.

2017 DFU mode investigation

Bricked A2017G

These posts have given me a big scare. Since no one has been able to recover from the same condition that i am in right now.

That's why i'm asking the help of experts. Please help me.

I have also came to a conclusion myself that if a tool like this Flashing recovery or this ZTE Open Download Mode or maybe this [TOOL][ALPHA] ZTE Warp 4G Unbrick Tool is not developed then this particular Qualcomm Phone is Brickable.

I am saying this because after a good amount of googling i came to know that when qualcomm phones are bricked it goes into emergency download mode which shows as "Qualcomm HS-USB QDLoader 9008" or "Qualcomm HS-USB QDLoader 9006" on device manager. And there are a lot of guides to unbrick from that state. But only old ZTE devices go into "Handset Diagnostic Interface (DFU) (ComX)" mode aka DFU mode.

And there are different guides for different models.

This is why i am panicking and asking for the help of experts. If there was a guide to recover from this state this post wouldn't exist. So if u can, please help.

And sorry for my english, i tried my best.
[ZTE Axon 7 Questions & Answers] Oki:
Can you boot into the bootloader by pressing the button combination?
[ZTE Axon 7 Questions & Answers] nsabir:
No i cannot. Everything seems to be pointing back to DFU mode. :( :(

I need something like Method 5 of this post How to recover a ZTE Blade/Libra/v880 after a bad flash for A2017G
[ZTE Axon 7 Questions & Answers] Altomugriento:
Hi, maybe this can help you, is the chinese forum, i know is a shot in the dark, but your case i think need a special treatment, sorry for my english, the link:

http://www.myzte.cn/forum-1037-1.html

and the tutorials:

http://www.myzte.cn/forum.php?mod=forumdisplay&fid=1037&filter=typeid&typeid=2243

Use Google translator, and good luck, sorry if this is a waste of time for you, i am trying to help

PS: RMA chinese http://rma.zte.com.cn/
[ZTE Axon 7 Questions & Answers] nsabir:
please don't embarrass me by saying sorry. I appreciate the fact that u even attempted to help me. thank u. :)

I am going through the Chinese posts and hoping to find something useful.
[ZTE Axon 7 Questions & Answers] Altomugriento:
Do you find something useful? I think I find someone in that forum, exactly in your position, all the answers pointing to RMA for the fix, sorry, maybe later can take another look and search for a solution.

Enviado desde mi ZTE A2017U mediante Tapatalk
[ZTE Axon 7 Questions & Answers] Altomugriento:
https://xdaforums.com/showthread.php?t=3551590

Enviado desde mi ZTE A2017U mediante Tapatalk
[ZTE Axon 7 Questions & Answers] nsabir:
Thank you for the link. But i tried this miflash tools weeks ago.

Here is the full guide in my opinion for the mi flash tool.

http://www.androidbrick.com/unbrick...-you-have-the-right-kind-of-rom-qhsusb_dload/

Unfortunately, the A2017G does not have 9008 port. It has ZTE's own Handset Diagnostic Interface (DFU) (ComX) for which i need the latest version of ZTE firmware flasher. At the moment only ZTE have this. So, my bricked phone is a lost cause. :(
[Xperia Z5 Compact Q&A, Help & Troubleshooting] SwisSwiss:
folks im at my nerves end... (hello btw)

firstly a thousand apologies to the mods if im posting this in the wrong place and a thousand apologies more to the rest of you for asking a question that has probably been answered time and time again.....

I can't get round it, iv been able to unlock bootloader and I thought that would have been the hardest part.... but I think I cant get my hands on the right, up to date files, in order to root my current system... iv been doing a ton of reading and just as many rooting attempts on my phone but to no avail......

the closest iv got in the command window was "error: device 'null' not found", to my understanding this is a driver related issue?...I dont know... if someone could hold my hand (im scared) and walk me through the process step by step I would be very, VERY grateful....

P.s; in exchange I can help you install CFW on a PSP.....lol right? (I actually made a pandora battery back in the day and im still rather proud of that)
[Xperia Z5 Compact Q&A, Help & Troubleshooting] SwisSwiss:
UPDATE:........ So i think I was able to flash the proper Kernel (adroid plus kernal V42) but was unable to do flash recovery?

rootcheck says "root access is not properly installed on this device" still.....

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img

target reported max download size of 536870912 bytes

sending 'boot' (14956 KB)...

OKAY [ 0.479s]

writing 'boot'...

OKAY [ 0.143s]

finished. total time: 0.624s

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp-2.8

.7.0-E6653-20151114_material.img

error: cannot load 'twrp-2.8.7.0-E6653-20151114_material.img'

UPDATE:

So i was able to do a flash recovery by renaiming the twrp file to simply twrp and adapting the code typed in the command window...... this caused my phone to soft brick or enter a bootloop....

after some swearing and more reading I was able to do a flash recovery with twrp-3.0.2-0-E5823.img (again by typing the exact name of the .img file in the command window....duuhhhh).... this allowed my phone to boot properly (thank God)... but root checker still says "root access is not properly installed on this device".....

I feel as if im close to my goal, what am I doing wrong!?......that soft brick served me as a cold shower and a lesson....this is kinda fun!

FINAL UPDATE:

BOOOM!!! success..... only took me all day...... still one thing though, i was unable to back my system due to lack of space on my SD card.... am I boned in this regard or can I create a back up later?
[Xperia Z5 Compact Q&A, Help & Troubleshooting] RohitRath:
Thanks for the updates, i will try to follow your guide. how did you finally achieve success ?
[Xperia Z5 Compact Q&A, Help & Troubleshooting] Superrman:
i wonder if you backup the DRM keys\TA partition
[Xperia Z5 Compact Q&A, Help & Troubleshooting] SwisSwiss:
In regards to why i was unable to create a back up right away? Not sure, think it was simply a matter of volume...

Had a crappy 4gb micro sd In there....
[Lenovo A6000/Plus Questions & Answers] sushanthreddy1829:
Hellow developers

Thanks for everything...

And will you make jarvis Os for lenovo a6000???
[Moto G4 Plus Questions & Answers] Ismael034:
I need xposed for moto g4 in 7.0 Please help me
[Moto G4 Plus Questions & Answers] zeomal:
Please help yourself.
[Moto G4 Plus Questions & Answers] Ismael034:
But this is for 5.1-6.0, not 7.0
[Moto G4 Plus Questions & Answers] zeomal:
Xposed is not yet out for Nougat.
[Galaxy S III Q&A, Help & Troubleshooting] potatoknight8:
I am trying to flash the Stock ROM on my Galaxy S3 i9300. Constantly I am getting this Error.

<ID:0/003> Added!!

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> I9300XXUGNB6_I9300OJVGNB3_I9300XXUGNA8_HOME.tar.md 5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/003> Odin v.3 engine (ID:3)..

<ID:0/003> File analysis..

<ID:0/003> SetupConnection..

<ID:0/003> Initialzation..

<ID:0/003> Get PIT for mapping..

<ID:0/003>

<ID:0/003> There is no PIT partition.

<OSM> All threads completed. (succeed 0 / failed 1)

Note:

1)Device GT-i9300

2)I can ONLY goto the Download Mode.

3)Using Original Data Cable.
[Galaxy S III Q&A, Help & Troubleshooting] shivadow:
**this is "a last port to call" this is the last thing you should try**

Try flashing this via recovery: https://drive.google.com/file/d/0B4vTiHTBB629d2syOEV1MkdmTjg/view?usp=drivesdk

Then flash your stock rom via odin.

Beamed in by telepathy.
[Galaxy S III Q&A, Help & Troubleshooting] audit13:
Try different USB cables and USB 2.0 ports.
[Galaxy S III Q&A, Help & Troubleshooting] 西村大一:
Another EMMC brickbugged i9300. Unless you replace the EMMC chip on the PCB, your phone is kaput. Or get another motherboard. And don't even think about getting your stuff back. They're either done for or locked because what EMMC brick bug, as the name suggests, it's a bug of a specific batch of EMMC chips that after some number of IO operations or some other condition, it just locks, leaving only the first part of the EMMC working, < 1 megabyte in my researches. In reality, your EMMC is not done with, it could be accessed IF you have a device which can reset the EMMC controller or something like that.

Or just flash a .pit file for your device model and capacity, something like i9300 xxg.pit, replacing the xx with the capacity of the EMMC, 16, 32 or 64 gigabytes.

---------- Post added at 20:17 ---------- Previous post was at 20:16 ----------

There is no pit and you suggest flashing a bootloader? Non, non, non, you're wrong. And the man said he can ONLY ACCESS DOWNLOAD MODE. Read before you post.

---------- Post added at 20:19 ---------- Previous post was at 20:17 ----------

Don't think so.
[Galaxy S III Q&A, Help & Troubleshooting] audit13:
I have been flashing the captivate, s2, s3,s4,s5, note 1, note 2, note 3, note 4, etc. for several years and have often revived the "no pit partition" error when using incompatible it USB cables and ports.

If using the original USB cable doesn't work, try flashing with a pit file.
[Galaxy S III Q&A, Help & Troubleshooting] shivadow:
In my experience flashing a pit file will 9 times out of 10 doorstop the device. Flashing that bootloader "might" allow the emmc to reset, or it may doorstop the device. So, the choices are your way (90% chance of killing it) or my way (50% chance of killing it).

So logically thinking me chose not to reveal the ultimate killing method just yet. I also presumed that the ol' cable and port routine was already done seeing as he already has a response from the device.

I also presumed that after doing some research on the matter before I suggested it that, seeing as many other people have reported that it has fixed a no pit condition on "thought to be dead" devices, it would be a better option than attempting the said ultimate device killing option.

I also believe that there is a method for flashing the bootloader via download mode should a minor amount of research be done on Google.

So, it would be better if YOU did the research before commenting instead of coming out with useless, degrading, ignorant, self righteous, arsehole (full of s**t) posts like yours before taking random potshots at people who have actually spent a couple of years with the device in their hand and are still learning new things to this day. Maybe a more constructive comment like "you missed the bit where he can only get to download mode, maybe he could use the .tar version".. But no. Too much..

Beamed in by telepathy.