Hi there!
This is my first post on xda, but I've come out with some fun findings.
{
"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"
}
The method of disabling secure boot is kind of complicated, and requires desoldering the BIOS chip and writing to the NVRAM data, however, it's a simple 1 byte entry called "SecureBootEnable".
There's also NVRAM variables listed "AntiRollBack", "KfAntiRollBack", and "OsAntiRollBack", and those can be disabled as well.
The BIOS is heavily stripped down and contains no setup menu, nor can I find a way to do USB boot as of yet.
The fork of Android is "Android-IA" (i.e. Intel's atom based android fork) and it calls an EFI file on the MMC for the bootloader.
I'm not sure if this unlocks the bootloader to custom roms as of yet, since after reflowing the bios chip a couple too many times I ripped one of the pads off and am waiting for a replacement.
Related
Right, I love experimenting with programming, and I totally adore reverse engineering stuff. So naturally with my Universal being windows-ish and all, and with that funny bootloader, I couldn't resists but do some experiments.
I used buzz's method of creating a nice new bootscreen:
{
"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"
}
However, in my eyes the process was too complicated. You first have to run stuff on your phone, then you need to convert the image, then use some exotic .batch file to flash it to your phone, and even overwriting bytes that aren't even needed to get it to work.
So I set off to create something better
Here's the first result, a package with a full HTML tutorial and everything you need. It still has a downside, namely that it actually hard-resets your device, but I'm still working on that
Get it here:
ftp://xda:[email protected]/Uploads/Universal/CreateBootScreenPackage.rar
At present, I have successfully installed XP operating system, all the normal functions (including wireless keyboard and handwriting). However, the use of a period of time, the wireless feature turned off by (the reasons for not drive), I would like to ask for this? The machine is a hardware problem? Or "HTC" sent via the Internet instructions? So I am very troubled by this, because of the need to open the wireless system must be to restore VISTA, and then the resumption of XP, though can be done, but to restore the system repeatedly, I am worried that there is damage to the hard disk, can I come down on how to solve this problem, thank you! ! !
{
"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"
}
This part can be ignored
I don't know what I did to my Zenny but now it has a corrupted boot.img,system.img and cannot be entered in recovery or fastboot. More, instead of showing the dead USB icon when I connect it with PC/Charger, it shows a red square that almost covers the screen. I cannot remember what I was doing last time. May be I just thought of making a new Zenny out of Zenny without a proper preparation.
Click to expand...
Click to collapse
Normal developers (who'll ask me to flash with xfstk or who does know a little but thinks, he knows the best must stay away.
{
"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"
}
Now,
I am trying to flash intel flash tool and it detects the phone but doesn't detect the zip. I have the latest version of everything. I cannot go to the customer care; I have none here.
Too see image: https://drive.google.com/file/d/0B6IEgguDI4GfeUEwNzZNcTE0MUU/view?usp=sharing
Hello,
This is my first post on XDA.
I have successfully gotten passive IMSI catching to work on my Nokia 1 which uses a Mediatek MT6737M as the baseband processor.
All I had to do was open the firmware image in Ghidra, use a custom script to populate function names from the debug symbol file under /system/etc/mddb, and apply patches to dump paging request messages.
With this method, you don't need any type of SDR for sniffing GSM.
It's also theoretically possible to sniff calls/SMS by making more modifications to the baseband.
You may grab a copy of the hacked baseband image (only working on Nokia 1 atm, root is required) under the Github username Irdev110
I will be working on releasing an actual app which automatically patches any compatible baseband image.
Sample output/demo:
{
"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"
}
my phone has this "System has been destroyed press power off", and my oem is lock, tried fastboot but it needs auth. Then i tried edl, qualcom was detected but i got this when i tried to flash.
{
"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"
}
Hi. Did you solve the problem? If not, you can use the file prog_emmc_firehose_8937_ddr.mbn from
Collection of Xiaomi Qualcomm Programmer EMMC Firehose Files
In this post, we have made available a collection of Qualcomm Programmer EMMC Firehose Files for some Xiaomi smartphones to help you un-brick or unlock FRP on your phone with ease. Be sure to download and use only the right file for your device; as whatever you do with the files provided below...
www.leakite.com