Develop Bugs

HTC Desire C root problem

Hello, I want to root my HTC Desire C with Superboot R1 but I cant. When I try it on Windows, the cmd shows me:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When I try it on Ubuntu it shows me boot.img error or something similarly. Please, help me, I dont know what I am doing wrong.
Thanks

Are you f**king kiding me?! At first I must root the phone. Please dont spam this thread. Thanks

Are you running it as administrator? If you do, please try simply launching it without admin rights.
And no, he is not "f**king kiding" you. You don't need root to flash a new ROM, you need custom recovery for that job.

Yes, I run it as administrator and I tried it without admin rights too. It just doesnt work.
In Linux it shows me:
downloading 'boot.img'... FAILED (status malformed (1 bytes))
Click to expand...
Click to collapse
And I know that I dont need root to flash a rom, but for flashing rom I need recovery and recovery needs root permissions. I rooted a lot of android devices and I know what I do and how it works. But this phone is really hard to root.
Thanks for reply

Try redownloading the boot.img, that's all I can think of.
You can also try this fastboot for Windows, it works fine with my Desire C.

Thanks
I think that in Windows is problem in drivers. Here is screen of drivers list:
As you can see (sorry, Iam from Slovakia and so I have Slovak language in Windows), I havent driver for Android Phone and I think that this is the main problem. But why it wont works in Linux?
I can try your fastboot but I think that it will not works because I havent Android Phone driver.
And in Linux, how I can redownloading boot.img?

Just download it again from Modaco. I think that is the problem.
And if you're interested I can give you drivers for Windows 8 that work with fastboot, being a little weird sometimes though.

Yes, when I double click on boot.img it shows me that the file is damaged. But I downloaded it from modaco again and it shows me that same.
I would like to ask you if you could me upload the drivers which works, because I would like to root this phone finally.
Thanks

I really hope your OS is 64 bit, turns out I don't have 32 bits drivers. I hope this can solve the problem, even though I doubt to(fingers crossed). If it doesn't work, then I really don't know what the problem could be.

YES!!! You are really fantastic! Thank you so much, finally my phone is rooted. Thank you so much

Whoa! Nice, I'm really glad I helped. :highfive:

HTC root / root problem
IF YOU HAVE ANY SOFTWARE PROBLEM AFTER ROOTING OR WANT JUST ROOT OR UNROOT YOUR (ANY) HTC THEN GO TO htchelp.weebly.com YOU WILL EASLY FIX IT IN 5 MINUTES. YOU CAN USE ANY HTC MODEL WITH ANY ANDROID VERSION
---------- Post added at 11:57 PM ---------- Previous post was at 11:45 PM ----------
IF YOU HAVE ANY SOFTWARE PROBLEM AFTER ROOTING OR WANT JUST ROOT OR UNROOT YOUR (ANY) HTC THEN GO TO htchelp.weebly.com YOU WILL EASLY FIX IT IN 5 MINUTES. YOU CAN USE ANY HTC MODEL WITH ANY ANDROID VERSION

[Need Help] ZE551ML Bootloop and No Fastboot

So, recently I tried to use this ROM: http://forum.xda-developers.com/zenfone2/development/stock-rom-ul-z00a-ww-2-20-40-168-t3354526
after revert back from CM13 custom ROM: http://forum.xda-developers.com/zen.../rom-cyanogenmod-13-0-nightly-builds-t3264492
But the result is my phone stuck in Asus logo.
Tried to access recovery by pressing power button + volume up but cannot go into recovery.
Tried to connect phone to PC via USB cable but the phone is not detected (cannot try fastboot from PC).
Here is what I did before my phone bricked:
1. Reboot into recovery (I'm using TWRP)
2. Wipe everything except MicroSD
3. Install SuperSU (downloaded from the thread)
4. Install ROM v168 (downloaded from the thread)
5. Reboot system
After that my phone stuck in Asus logo.
Tried to search solution from many sources still no luck. Already posted in the thread but still no answer from anyone.
Please help because I don't have backup phone :crying:
Thanks.

Did you really flash supersu before you flashed the Rom? That's probably the cause. Have you tried any of the bootloop solutions posted here yet?
Sent from my ASUS_Z00A using Tapatalk

If you cant go recovery try using this method..
It goddamn works ��
Requires sometime to understand it though. But you'll get it ��
http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256

Vinaygan said:
If you cant go recovery try using this method..
It goddamn works ��
Requires sometime to understand it though. But you'll get it ��
http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
Click to expand...
Click to collapse
Yup, tried this method and my phone is resurrected.
But the content of that tutorial was hard to understand at the beginning

kenbo111 said:
Did you really flash supersu before you flashed the Rom? That's probably the cause. Have you tried any of the bootloop solutions posted here yet?
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
I've followed the steps provided in the thread so I assumed that superSU was flashed already.
How to verify if it's flashed or not? Can I verify before moving on to the next step?
My phone is resurrected now thanks to steps provided by summit.
Could it be because I was using TWRP before?

i had problem like you. i dont have bootloader and fastboot. i use xFSTK-Downloader.
success.
i can help you
fb: facebook.com/hieulanhat123
sorry my English i am from vietnam

I tried the summit method on a Win10 machine but it doesn't detect the phone on xFSTK-Downloader, can somebody help me?
This is how the phone looks right now:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

arturocr said:
I tried the summit method on a Win10 machine but it doesn't detect the phone on xFSTK-Downloader, can somebody help me?
This is how the phone looks right now:
Click to expand...
Click to collapse
Bruh...
I've successfully recovered my phone using xFSTK
On a win10 os
---------- Post added at 02:01 PM ---------- Previous post was at 01:50 PM ----------
arturocr said:
I tried the summit method on a Win10 machine but it doesn't detect the phone on xFSTK-Downloader, can somebody help me?
This is how the phone looks right now:
Click to expand...
Click to collapse
1. Make sure your device shows up for awhile during boot
(when the phone vibrates upon boot)
2. Make sure you selected MOOREFIELDS.
3. Once done selecting the files " change the gp override flag under OPTION to 0x80000807"

[Q] ADB Error:closed after commands

After I flashed a ROM (a dev official rom since my device has a locked bootloader), now I cannot flash anything else.
I get the 'error:closed' message whenever I try to adb sideload, or adb tcp, or adb usb.
Since my phone is bootlooped I cannot unlock the bootloader or try other things outside adb.
Has anyone ever faced this kind of error?
C:\Users\rikku>adb version
Android Debug Bridge version 1.0.32
Revision eac51f2bb6a8-android
C:\Users\rikku>adb devices
List of devices attached
1c576f70 sideload
C:\Users\rikku>adb usb
error: closed
Click to expand...
Click to collapse

mkioshi said:
After I flashed a ROM (a dev official rom since my device has a locked bootloader), now I cannot flash anything else.
I get the 'error:closed' message whenever I try to adb sideload, or adb tcp, or adb usb.
Since my phone is bootlooped I cannot unlock the bootloader or try other things outside adb.
Has anyone ever faced this kind of error?
Click to expand...
Click to collapse
Changing miui roms still require the bootloader to be unlocked.

mkioshi said:
After I flashed a ROM (a dev official rom since my device has a locked bootloader), now I cannot flash anything else.
I get the 'error:closed' message whenever I try to adb sideload, or adb tcp, or adb usb.
Since my phone is bootlooped I cannot unlock the bootloader or try other things outside adb.
Has anyone ever faced this kind of error?
Click to expand...
Click to collapse
Have you tried using Ubuntu and regular adb or something?
If you can't change anything on the phone start changing the way you try to fix it with the PC.
Maybe the linux adb will force it to work or something.
Sorry no specific answer but could be worth a try. If you have the determination there is a chance to fix it.
Your absolute last option is EDL with the test point on the inside of the phone. If you can't send it back to the seller its better to have a phone with a broken seal on the back (just repair it yourself after) than a fully assembled paper weight

Dobsgw said:
Have you tried using Ubuntu and regular adb or something?
If you can't change anything on the phone start changing the way you try to fix it with the PC.
Maybe the linux adb will force it to work or something.
Sorry no specific answer but could be worth a try. If you have the determination there is a chance to fix it.
Your absolute last option is EDL with the test point on the inside of the phone. If you can't send it back to the seller its better to have a phone with a broken seal on the back (just repair it yourself after) than a fully assembled paper weight
Click to expand...
Click to collapse
I tried both xiaomiadb and normal adb, all give the same error, on Mac OS X and Windows 10. Seems to me the problem is in the phone, I dunno.... Thanks a ton tho!

mkioshi said:
I tried both xiaomiadb and normal adb, all give the same error, on Mac OS X and Windows 10. Seems to me the problem is in the phone, I dunno.... Thanks a ton tho!
Click to expand...
Click to collapse
Seriously try Linux

Dobsgw said:
Seriously try Linux
Click to expand...
Click to collapse
I installed a virtual Ubuntu machine, did the passthrough but no dice
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

mkioshi said:
I installed a virtual Ubuntu machine, did the passthrough but no dice
Click to expand...
Click to collapse
good day please was this problem solved cause i have the same screen as above

Can't find my device in fastboot mode

Hi, i want to unlock the bootloader of my old Redmi note 5, but there's a problem, when I go into fastboot mode, the Xiaomi's software can't find it, even using ADB the device is impossible to find. If I turn it on normally i can find it. Why it happens?

Hey u may give this a try as based on my understanding Xiomi devices will require u to install mi flashtool on PC as it has driver installation option. Remember some times you are required to disable driver signature verification.

I recently had trouble with fastboot as well. I eventually sorted it by installing the correct drivers, from here: http://bigota.d.miui.com/tools/xiaomi_usb_driver.rar
I don't remember having to disable driver signature enforcement (usually to do this you have to use an advanced boot option as shown in Option 2 here) but maybe it happened automatically.

plusminus_ said:
I recently had trouble with fastboot as well. I eventually sorted it by installing the correct drivers, from here: http://bigota.d.miui.com/tools/xiaomi_usb_driver.rar
I don't remember having to disable driver signature enforcement (usually to do this you have to use an advanced boot option as shown in Option 2 here) but maybe it happened automatically.
Click to expand...
Click to collapse
I installed the driver but nothing changed. I post a screenshot of the situation , as soon as i go into fastboot mode the adb can recognize the device, but after few seconds not.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Fruso01 said:
I installed the driver but nothing changed. I post a screenshot of the situation , as soon as i go into fastboot mode the adb can recognize the device, but after few seconds not.
View attachment 5260567
Click to expand...
Click to collapse
Weird.
Maybe try a different cable?

Fruso01 said:
I installed the driver but nothing changed. I post a screenshot of the situation , as soon as i go into fastboot mode the adb can recognize the device, but after few seconds not.
View attachment 5260567
Click to expand...
Click to collapse
U might be using an Amd based system. Usb 2.0 hub is ur solution

Fruso01 said:
I installed the driver but nothing changed. I post a screenshot of the situation , as soon as i go into fastboot mode the adb can recognize the device, but after few seconds not.
View attachment 5260567
Click to expand...
Click to collapse
lool win10 sh1t... use usb 3 reg patch or usb 2.0 hub. Search it on xda forum.
Btw. There is no problems on w7 and linux lool.

drnightshadow said:
lool win10 sh1t... use usb 3 reg patch or usb 2.0 hub. Search it on xda forum.
Btw. There is no problems on w7 and linux lool.
Click to expand...
Click to collapse
Can you tell me about this usb 3 reg patch?
Actually i am outstation and don't have my usb hub and i want to do faatboot commands

Why my note 5 pro not connecting with pc after installing any custom rom.i have proper usb driver and everything like adb fastboot..but not showing any device in my computer ...can anyone help me

Banty448 said:
Why my note 5 pro not connecting with pc after installing any custom rom.i have proper usb driver and everything like adb fastboot..but not showing any device in my computer ...can anyone help me
Click to expand...
Click to collapse
Read the thread and don't be troll. You didn't even read post before you post it your own. Ignorance is a bliss.
Good luck and stay safe.

Question Is there anyway to get rid of this?

I don't want to login or create emojis but it keeps popping up asking if i want to. Any way to remove this?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Package Disabler or a adb edit will stop it from running at startup. You can try to disable or uninstall the app in settings but many times you don't have that option.
Any dependencies it may have will also be affected as well... don't go too nuts.

blackhawk said:
Package Disabler or a adb edit will stop it from running at startup. You can try to disable or uninstall the app in settings but many times you don't have that option.
Any dependencies it may have will also be affected as well... don't go too nuts.
Click to expand...
Click to collapse
So which app is that?

I have the OnePlus 10 Pro and I don't believe you can remove it. However, apart from where you see the message it should not appear anywhere else, except maybe within the OnePlus Store app.

birdie said:
So which app is that?
Click to expand...
Click to collapse
Don't know, don't have that phone make.
It's pretty easy to figure it out especially with PD.

seancojr said:
I have the OnePlus 10 Pro and I don't believe you can remove it. However, apart from where you see the message it should not appear anywhere else, except maybe within the OnePlus Store app.
Click to expand...
Click to collapse
You can op membership and account need to be uninstalled via adb debloater. Has ui to do it.
Sent from my OnePlus 10pro
[TOOL] ADB AppControl 1.8.0 🚀 Ultimate App Manager & Debloat Tool + Tweaks
ADB AppControl 🚀 Root is not required. Works with any Android device. Can do almost everything you dreamed about with applications. ADB AppControl - the desktop program, that will allow you to easily manage applications on your android device...
forum.xda-developers.com

blackhawk said:
Don't know, don't have that phone make.
It's pretty easy to figure it out especially with PD.
Click to expand...
Click to collapse
I've checked all the packages, nothing is "easy".

Option 1:
Open Termux application
Su
(superuser prompt)
"pm uninstall --user 0 com.oneplus.account"
Option 2:
"adb shell pm uninstall --user 0 com.oneplus.account"
Reboot
To restore:
"adb shell cmd package install-existing com.oneplus.account"
Option 3:
https://forum.xda-developers.com/t/...mate-app-manager-debloat-tool-tweaks.4147837/
Adb control application tool

The below is actually sufficient on the OnePlus 11, EU version running OxygenOS 13 build A.10:
Code:
adb shell pm uninstall --user 0 com.oneplus.account
Success
This doesn't work:
Code:
adb shell pm uninstall --user 0 com.oneplus.membership
Failure [not installed for 0]

birdie said:
I've checked all the packages, nothing is "easy".
Click to expand...
Click to collapse
That's the harder way...

blackhawk said:
That's the harder way...
View attachment 5913467
Click to expand...
Click to collapse
Have you used the phone we are discussing? Why are you posting the pic of a different device running some random app?

birdie said:
Have you used the phone we are discussing? Why are you posting the pic of a different device running some random app?
Click to expand...
Click to collapse
Haven't you solved this yet? Any more questions?
There is at least one way to solve this on a none rooted Android using adb or ladb as previously mentioned. That's assuming that it can't be resolved in settings or the easiest way using that "random app" I showed you. Pick your poison...
*punches ignore button*