Develop Bugs

[TOOL][Bricked-Installer][Guided|AutoUpdate][WIN/LNX][for all kernels]

Bricked-Installer
No more fiddling with fastboot/console tools.
This is a 100% guided install.​
Features:
Fully automated install
Install of ANY kernel zip as long as there are modules + a boot.img in there
Detecting your phone
Flashing is device specific to the device you have connected. (safer)
No matter where you are (fastboot/recovery/booted) you can just launch this installer and go!
Built using Qt from zero
I made it opensource (GPLv2), so everyone can pull it and make improvements
Multi-platform (If someone has a mac, build it & give me the file so I can add it.)
Autoupdater (from version 0.2 forward, so you can test this new feature with the release of 0.3 )
Automatic cache erase from fastboot​
Supported Devices:
Currently only the HTC One X.
More to come (+zImage install) soon.​
Prerequisites:
Having the Android debug bridge enabled (Settings -> Development -> USB debugging)
Having the zip you want to install somewhere on your PC
Follow the on screen instructions.​
Changelog @ bricked.de​
Download:
No Guarantees! If it kills your grandmother or your device, I am NOT responsible! If you understand this:
(If you download, please hit Thanks below my post! Thank you!)
*latest version* [WINDOWS] Click me
*latest version* [LINUX] Click me​
Where to complain about errors/bugs?
Please use the Issuetracker for bugs/errors/feature wishes!
Issuetracker @ https://github.com/showp1984/bricked-installer/issues
[email protected]
IRC Chat: Freenode IRC #bricked​
Source:
​

{
"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"
}

Reserved #2

Hopefully a nice new kernel to go with it soon

Thank you very much sir for this
So if i understand it corectly this will work even if we are not in fastboot mode right?
For example if you are on the homescreen and fully booted u can flash a kernel right?
Thanks again show-p.
Extremely appreciated mate

And the Jedi comes back.with the full force.
Sent from my HTC One X using Tapatalk 2

Nice job, works as advertised
Would you be able to add the "fastboot erase cache" command after you flash the boot img? I usually have problems booting into recovery if I don't do this.

DanteGR said:
Thank you very much sir for this
So if i understand it corectly this will work even if we are not in fastboot mode right?
For example if you are on the homescreen and fully booted u can flash a kernel right?
Thanks again show-p.
Extremely appreciated mate
Click to expand...
Click to collapse
It will reboot for you and do it's job
Goku80 said:
And the Jedi comes back.with the full force.
Click to expand...
Click to collapse
Help you I can!
Yes!
Hrmmmm!
/me grabs your flashlight and eats your cookies.
h00py said:
Nice job, works as advertised
Would you be able to add the "fastboot erase cache" command after you flash the boot img? I usually have problems booting into recovery if I don't do this.
Click to expand...
Click to collapse
done for the next version which will be around the corner soon (tm).

Pyramid?
Tried to use it with my OneX with Viper Rom.
Apparently the installer detected the phone as 'pyramid' instead of 'endeavoru'.
Any idea how to fix this?
And thanks for coming up with this!

faidz85 said:
Tried to use it with my OneX with Viper Rom.
Apparently the installer detected the phone as 'pyramid' instead of 'endeavoru'.
Any idea how to fix this?
And thanks for coming up with this!
Click to expand...
Click to collapse
That would be quite impossible, except your device is a pyramid, you have a pyramid connected, or your build.prop says pyramid.
PS: the screenshot does not work here.

NICE JOB !!!!

I think it is because I have pyramid in build.prop.
I never once owned any pyramid before.

Thank you guy, bentornato
Inviato dal mio GT-P1000 con Tapatalk 2

faidz85 said:
I think it is because I have pyramid in build.prop.
I never once owned any pyramid before.
Click to expand...
Click to collapse
boot your phone into fastboot and start the program, it will then read out the devicename from fastboot directly (which can't be altered).
It should then say endeavoru and go on with it's business
PS: Screenshot works now
Please tell the ViperX guys to fix their build.prop

faidz85 said:
I think it is because I have pyramid in build.prop.
I never once owned any pyramid before.
Click to expand...
Click to collapse
I think it is because of the Gameloft compability on Venom Tweaks is activated

the problem is gameloft compatibility turn on,the initial build.prop after installation is correctly,in case you have turn on this tweaks turn it of and build.prop return to original,sorry for my bad english

Another German's piece of art, congratulations show-p1984!

perfect tool, comfortable, and most importantly it works perfectly, in fact, as previously mentioned, you may be wanting to add fastboot erase cache, and run. Now we just wait for his new version of the kernel , and so everything perfect. A greeting and thanks

Realy, realy good!! Thanks!

Great Job. Back with Bang
EDIT: not working for me on slimics 4.2 trying to flash faux beta 4 b3. It reboots from boot;oader and stays still. Also nothing happens while run in booted state except extracting zip

[TOOL] WinDroid Toolkit | Unlock | Root | Flash | Install | Huawei Watch

Link To Main Thread
{
"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"
}
About
The WinDroid Toolkit is a Windows program built in Visual Studio using the C# programming language that simplifies the rooting process for many Android devices. The toolkit makes it easy to unlock your bootloader, flash a custom recovery and gain permanent root. It also includes other functions such as flashing kernels, pushing files and installing apps. If you find it helpful, give me a thanks and a donation if you can. If you find a bug or have a feature request, feel free to leave a reply. Thanks!
Download
WinDroid Toolkit
Changelog
Check out this document for current and past changelogs.
Supported Devices
Check out this spreadsheet for a list of currently supported devices.
Device not supported? Make a request here!
Contribute
Check out the source code on GitHub here.
Disclaimers
Confirmed working by @chachin!
Please do not post, mirror, or take credit for this toolkit or any related work without explicit permission.
I am in no way responsible for any harm, damage, nuclear fission or bee infestation that may occur to your device through the use of this toolkit.

Reserved
Reserved.

Nice tool! Is flashing back completely stock an option for those who want?

suzook said:
Nice tool! Is flashing back completely stock an option for those who want?
Click to expand...
Click to collapse
Return to stock would be a great idea.

Like the look of this. Anyone try it yet? (Other than the developer)
EDIT: Also, return to stock would be awesome!

..

MuF123 said:
Guys, do NOT use this software without few things first:
-we have not seen source code of this, noone knows what it actually does to your watch
-this software is NOT made for huawei watch, this guy just made few buttons call some adb functions, however they are not customized for hwatch. Any of that can easily hardbrick your watch as far as we know.
Also this mass advertisement is really stupid. Post reported.
Click to expand...
Click to collapse
You can see the source code here, and the unlock command, as well as the rooting command, is the same for all smartwatches. The TWRP comes from this post, so it's completely safe. Please confirm things before you post.

..

MuF123 said:
I should confirm things before posting? YOU should confirm that while I have hwatch connected I can press any combination of buttons in your ADB wrapper and nothing bad happens. What about supersu? The option is there, have you tested it with hwatch? Please confirm things before you post.
Click to expand...
Click to collapse
Nothing bad can happen to a device that's not within the user's control. There are many checks in place to prevent errors, and the TWRP and SuperSU are specific to the HWatch. While I haven't personally tested them, I've confirmed that many users on the forum used that method to root their HWatch, so I implemented that into the toolkit. Go ahead and click any combination of buttons you want.

what's up with when I download this tool I get "Cannot save due to insufficient permissions. Please save to another location"

chachin said:
what's up with when I download this tool I get "Cannot save due to insufficient permissions. Please save to another location"
Click to expand...
Click to collapse
Try downloading on your PC, if you want to try it. (Always try at your own risk.)

kimtyson said:
Try downloading on your PC, if you want to try it. (Always try at your own risk.)
Click to expand...
Click to collapse
thats where im downloading it from.. using chrome i get that stupid error so dunno

chachin said:
thats where im downloading it from.. using chrome i get that stupid error so dunno
Click to expand...
Click to collapse
Here, try this :: https://drive.google.com/file/d/0B4b2dEm0P_xYMC1LbWFySGZNZEk/view?usp=sharing

ok i had to remove bitdefender and now its working fine... but when i open supersu that comes with this tool.. it fc's supersu.. while trying @Skin1980's kernel and kernel auditor app so how do i fix that? unless thats something i gotta go look somewhere else

..

MuF123 said:
Exactly THIS is what such a bulkly distributed tools gets to.
Just dont use this crap app noone really tested before publishing. Go for skin's kernel or anything other that has been proven to work, not just published to get likes/thanks.
Click to expand...
Click to collapse
all i did was remove bitdefender and it works now. so yeah i flashed skin's kernel too while iwas using the tool heh

chachin said:
all i did was remove bitdefender and it works now. so yeah i flashed skin's kernel too while iwas using the tool heh
Click to expand...
Click to collapse
Glad it worked out for ya. Just received my beautiful Huawei watch and will be checking out unlocking it...

i agree with most people.. would love it if we could have a "return to stock" option that would relock-bootloader in process and remove twrp and supersu just make it go back to complete stock heh just dreaming i think

WinDroid Toolkit v3.0 Is Now Out!
WinDroid Toolkit v3.0 has been released! It's a huge update with a material redesign, major recode and support for 43 new devices!
You can out more specific changes in the changelog here.
You can download the new update here.
All versions before v3.0 will not have their files updated anymore since I've moved from hosting on BasketBuild to Amazon S3. Please update to v3.0 to ensure you're getting the latest recovery and root files!

still working same as 2.6 nothing is wrong only wishing for the back to stock option would be cool and give it like a click twice or 3 times warnings about "you sure you wanna do it? there's no goin back!"

Removed System Files and Cannot Open the Phone since then. Help!?

Hi everybody,
This is my first post and come up with a problem regards my Nokia X+ phone.
I installed Lewa (from this site) onto my Nokia phone. After that, I accidentally removed important files (system files...). After that, I cannot start the phone and flashed using Nokia Flasher (from this site) and cannot install other Rom or OS at recovery mode.
I tried all the day, but no use. Please help me if you have solution for me?
I am eagerly waiting for your help.

Please show me a solution. I am almost thinking that my phone is no longer works. Hope somebody shows a solution for me.

Love Psyche said:
Please show me a solution. I am almost thinking that my phone is no longer works. Hope somebody shows a solution for me.
Click to expand...
Click to collapse
Which files did you remove?

Can you turn on the phone to fastboot mode?

YSH ALSAGER said:
Which files did you remove?
Click to expand...
Click to collapse
I removed System files and other important files using "Root Explorer" that comes with LEWA.
This is whole story in summary:
My phone model is Nokia X+. But rooted and installed LEWA OS from this forum. I didn't like LEWA and couldn't install other OS like Kitkat or Lollipup ROM. And without understanding the importance of that system files, I removed them.
When I restart my phone, it only shows LEWA starting symbol and cannot use my phone anymore.
* I tried to install other ROMs in recovery mode, but they are aborted while installing.
* I have not taken backups.
Feeling sad about what happened to my phone last day.
Is there any solution for me?

Enzo007 said:
Can you turn on the phone to fastboot mode?
Click to expand...
Click to collapse
What does it mean?
I tried Nokia Flasher and used all .img files and when I rebooted it shows Lewa starting symbol and be at the moment without any moment to forward. Any solution?
I also explained my problem in above reply clearly. Please read.

Love Psyche said:
What does it mean?
I tried Nokia Flasher and used all .img files and when I rebooted it shows Lewa starting symbol and be at the moment without any moment to forward. Any solution?
I also explained my problem in above reply clearly. Please read.
Click to expand...
Click to collapse
Try using nokia X manager.

Love Psyche said:
What does it mean?
I tried Nokia Flasher and used all .img files and when I rebooted it shows Lewa starting symbol and be at the moment without any moment to forward. Any solution?
I also explained my problem in above reply clearly. Please read.
Click to expand...
Click to collapse
Flash twrp 3.0.0 using Nokia X flasher /universal toolkit /fastboot then install any custom ROM
You can try to mount system from your current recovery before flashing

Enzo007 said:
Try using nokia X manager.
Click to expand...
Click to collapse
When I connected my phone with Nokia X Manager, I got this error.
{
"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"
}

You deleted the phone/screen resolution files. use nokia care suite for flashing.

Yahoo! I fixed it and will write detailed info tomorrow about how I did it.
Now suggest me to install a ROM that has no flaws. Is marshmallow available here for Nokia X?

Love Psyche said:
Is marshmallow available here for Nokia X?
Click to expand...
Click to collapse
Actually no. Maybe I will try to port it, when I'll have time to replace USB port in my Nokia X.
Love Psyche said:
Now suggest me to install a ROM that has no flaws.
Click to expand...
Click to collapse
http://forum.xda-developers.com/nokia-x/orig-development/rom-nokia-xl-cyanogemod-11-camera-t3303748 looks good.

BluRaf said:
Actually no. Maybe I will try to port it, when I'll have time to replace USB port in my Nokia X.
http://forum.xda-developers.com/nokia-x/orig-development/rom-nokia-xl-cyanogemod-11-camera-t3303748 looks good.
Click to expand...
Click to collapse
I have been to the thread. I found some bugs still have to be fixed. I found almost every ROM having bugs.
Is CRDROID good at now? I don't know but until Marshmallow ROM comes up by your talent.:good:

Love Psyche said:
Is CRDROID good at now?
Click to expand...
Click to collapse
I don't know, I haven't tested it :d
Love Psyche said:
I don't know but until Marshmallow ROM comes up by your talent. :good:
Click to expand...
Click to collapse
It will be my first try with Android porting, so don't expect good results too quickly :v

BluRaf said:
I don't know, I haven't tested it :d
It will be my first try with Android porting, so don't expect good results too quickly :v
Click to expand...
Click to collapse
I know. And I even know if developers like you are not here, we would have struck at very basic Nokia X android platforms. Kudos to you.
But I think this forum has at least one ROM without any errors. We don't have marshmallow, but what about Lollipup ROM (without errors)? If this forum has it, please give me link.

How to get rid of the "Your device is corrupt message"?

This looks like a pretty hard nut to crack. I don't know exactly what caused it. I was rooted for a few days and was just reflashing Magisk (messing about you could say) when it turned up. Previously, I just had the warning with yellow text which is what everyone gets after unlocking the bootloader. So here goes the overview, please bear with me:
===> I reset the phone by flashing OnePlus5TOxygen_43_OTA_006_all_1712062242_69a5125fb2eb4d87.ZIP (OxgengenOS 4.7.4). <===
Exact steps on how I did that:
1) I flashed the stock recovery image via fastboot ( I got it from Oneplus's website)
2) I booted into the stock recovery I flashed in step 1 and flashed the entire ZIP (the one with the long name above). Probably flashed the recovery twice but yeah.
But no dice. It will absolutely not go away. The zip does not contain any other IMG's apart from boot.img and recovery.img so I can't really flash other partitions like system via fastboot. I CAN flash system via my nandroid backup, and I did, but that still did not help.
Here is the error I got. It's from a google search but it resembles the error on the OPO5T very nicely. So can the experts chime in please?
{
"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"
}

Not used to posting my own answer but maybe this will help someone. You need a full reflash with the Qualcomm tools. OPO support can do this, or anyone with the flashing tool, the correct firmware image, and drivers (the latter being easy to find).
There are tutorials online to do this, the only thing missing is the correct firmware image.
To summarise the requirements:
1) Qualcomm drivers (easy to find)
2) Qualcomm Flash tool MsmDownloadTool V4.0.exe (fairly easy to find)
3) The correct *.ops firmware image (hard to find and you need the password)

Yeah we had been trying to crack the password with no success, hopefully someone will, thank u for the info

Bradl79 said:
Yeah we had been trying to crack the password with no success, hopefully someone will, thank u for the info
Click to expand...
Click to collapse
I can tell you its lenght if that helps? That should narrow down the amount of combinations. Unless its different per download link they send.

Yes please that would cut down a lot

Bradl79 said:
Yes please that would cut down a lot
Click to expand...
Click to collapse
For OnePlus 5T "OxygenOS 4.7.2-171116.zip" it is exactly 10 characters. The driver RAR-password is a lot longer (>20). Don't even try to brutefoce that.

If we already have the opt file someone could just set up a keylogger on their machine and have op support do the remote flash and thus capture the password from them lol

Bradl79 said:
Yes please that would cut down a lot
Click to expand...
Click to collapse
Jeroen1000 said:
For OnePlus 5T "OxygenOS 4.7.2-171116.zip" it is exactly 10 characters. The driver RAR-password is a lot longer (>20). Don't even try to brutefoce that.
Click to expand...
Click to collapse
Has any one had any luck with the password? I'm in the same soup as well!

randallstevens said:
Has any one had any luck with the password? I'm in the same soup as well!
Click to expand...
Click to collapse
still going... only on 4th character out of 10 been running for a couple days

Bradl79 said:
still going... only on 4th character out of 10 been running for a couple days
Click to expand...
Click to collapse
Do you mean you have the first three? If so can you share or PM it? Not sure if you mean that brute forcing has reached only a permutation of 4 characters.

randallstevens said:
Do you mean you have the first three? If so can you share or PM it? Not sure if you mean that brute forcing has reached only a permutation of 4 characters.
Click to expand...
Click to collapse
It is Bruteforcing meaning I started with 10 characters
1111111111
And it's still trying to decrypt, I am at something aroun
111111gw7&
So it's going one by one going through each character

Question (bootloader) Failed to get unlock data [ SOLVED ]

I recently got this Moto G40F and wanted to try Android 12 so bad.. I found out that Moto is Treble Compatible and so went to unlock bootloader as the first step.. and here I am having this weird issue that doesnt have a proper fix. I saw that this Moto devices use unlock code like in Huawei.. but Im getting this error while trying to get the device ID for getting the unlock code..
{
"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"
}
i have tried installing Motorola Drivers.. didnt help at all, Can someone help me around this issue please.. I want to experience Android 12 so bad..
Im using Minimal ADB and Fastboot in Windows 10 with Motorola Drivers.. i will attatch the fastboot getvar all below if it helps..

lofi2op said:
I recently got this Moto G40F and wanted to try Android 12 so bad.. I found out that Moto is Treble Compatible and so went to unlock bootloader as the first step.. and here I am having this weird issue that doesnt have a proper fix. I saw that this Moto devices use unlock code like in Huawei.. but Im getting this error while trying to get the device ID for getting the unlock code..View attachment 5331525
i have tried installing Motorola Drivers.. didnt help at all, Can someone help me around this issue please.. I want to experience Android 12 so bad..
Im using Minimal ADB and Fastboot in Windows 10 with Motorola Drivers.. i will attatch the fastboot getvar all below if it helps..
View attachment 5331529
Click to expand...
Click to collapse
Use the SDK Platform-tools direct from Google
[Index] Setting up and Using ADB/Fastboot
Setting up and Using ADB/Fastboot [INDEX] Helpful Information Welcome, this thread has been created to encompass everything you may need for Using ADB. Please only post in this thread with feedback on how to improve this document. Do not post...
forum.xda-developers.com

sd_shadow said:
Use the SDK Platform-tools direct from Google
[Index] Setting up and Using ADB/Fastboot
Setting up and Using ADB/Fastboot [INDEX] Helpful Information Welcome, this thread has been created to encompass everything you may need for Using ADB. Please only post in this thread with feedback on how to improve this document. Do not post...
forum.xda-developers.com
Click to expand...
Click to collapse
i tried this.. and this time i also tried using windows powershell (if that changes anything) and i still have the issue

lofi2op said:
i tried this.. and this time i also tried using windows powershell (if that changes anything) and i still have the issue
View attachment 5331789
Click to expand...
Click to collapse
Try different USB ports or and different PC

sd_shadow said:
Try different USB ports or and different PC
Click to expand...
Click to collapse
still same issue persists...

lofi2op said:
still same issue persists...
Click to expand...
Click to collapse
Any updates? Were you able to unlock the bootloader? If not try asking for help here. Even I failed to unlock the bootloader of my device.

JJSingh said:
Any updates? Were you able to unlock the bootloader? If not try asking for help here. Even I failed to unlock the bootloader of my device.
Click to expand...
Click to collapse
yes.. i still have the issue and couldn't get a proper fix, and yes i have posted it there too.. they moved it to the developer's threads and are working on it. i'll update when i get a fix

English Community-Lenovo Community
here you guys can keep up with what's happening..

check this out. and please keep me posted through the comments.

lofi2op said:
still same issue persists...
Click to expand...
Click to collapse
Is it resolved? I am having same issue. Please anyone share its solution. Thanks

[email protected] said:
Is it resolved? I am having same issue. Please anyone share its solution. Thanks
Click to expand...
Click to collapse
Some user reported after september security patch update bootloader is unlockable now

Could you find its solution? Bootloader is not getting unlocked in Moto G40.. seems some high technology embedded by Motorola

Sagarking said:
Some user reported after september security patch update bootloader is unlockable now
Click to expand...
Click to collapse
Is there any solution to it? Please suggest
Is it only for Motorola mobiles only or for all Android users for all fones?
In that case there should not be any option under developer options to select it.
Any suggestions please

FINALLY..... MOTOROLA G40 FUSION AND G60 are now unlockable after updating to the latest security patch ( RRI31.Q1-42-48 )