[HOW-TO]UnBrick the UnBrickable Captivate - Captivate Android Development

{
"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"
}
Introduction:
After months of research and development, both hardware and software... I'm happy to announce UnBrickable Mod is a matter of modifing your phone once, with a single small wire. From that point on, you can click a button to unbrick. This can even be applied to a phone which is already bricked.
Instructions
You Must have UnBrickable Mod applied to your device. If you're not sure, run this tool under Linux: http://forum.xda-developers.com/showthread.php?t=1257434
You must have a Linux based OS installed. Get Ubuntu here: http://www.ubuntu.com It's Free!
You must have Java installed on your computer. You can use this link http://www.java.com/en/download/ or use your package manger ie. apt-get install openjdk-6-jre
Unbricking:
1. Apply UnBrickable Mod to your device: http://forum.xda-developers.com/showthread.php?t=1206216
2. Run UnBrickable Resurrector: http://code.google.com/p/hummingbird-hibl/downloads/list This will only work on linux currently. Install Linux or dual boot if you have windows.
3. Run Heimdall One-Click: http://forum.xda-developers.com/showthread.php?t=1266172 (or odin3 one-click),
4. repeat steps 2 and 3 with bootloader flashing enabled (Heimdall One-Click has a safety mechanism which requires you to flash once before flashing bootloaders).
conclusion
You've unbricked the unbrickable captivate... This should not have been difficult. If it was, you should learn teh computer better... Really. And with that said, I'm happy to announce that you no longer have to flash with a fear of bricking.
HIBL
The HIBL is the key to resurrecting a S5PC110 based processor. I'm going to let Rebellos explain the inner workings of the Hummingbird Interceptor Bootloader. It's really quite amazing. While my work is more hardware and high level tasks like making things into one-clicks, Rebellos' work involves reverse software engineering, assembly language, and more...
Tools
Windows32 command line app and drivers http://forum.xda-developers.com/attachment.php?attachmentid=709292&stc=1&d=1315091523
Linux one-click Resurrector: http://code.google.com/p/hummingbird-hibl/downloads/list
4SEP11: added 32 bit, miscellanious impovements to visuals
6SEP11: removed additional commands

Okay, so, what is Hummingbird Interceptor Boot Loader (HIBL)?
Basically: It allows to load any amount of data (limited by size of RAM block, the biggest one single block available is 256MB) through USB connection with PC under any specified address into memory and then execute it.
Technically: It does consist of 2 pieces fused together - BL1_stage1 and BL1_stage2.
Each stage starts from 16bytes (4 ARM WORDs) of secure boot header. In stage1 these are mandatory, in stage2 they can be random (nulled them in my code), so EntryPoint of each stage does start at its 0x10 offset.
BL1_stage1, loaded under 0xD0020000 address, is short code, digitally signed by Samsung. It has been released to break "Chain of Trust" and alter Secure Boot into Non-Secure Boot process. Literally stage1 just do some compare operations and then jumpout to BL1_stage2. (Yes, I also see no point of releasing hardware secured CPU version together with software which is bypassing it's security)
BL1_stage2, must be placed at 0xD0022000 address (it's fused together with stage1 into HIBL, so it's at 0x2000 offset of HIBL.bin) it is unsigned because Secure Boot Context, prepared by iROM (BL0) has been already ignored by stage1.
Its FASM_ARM sourcecode:
http://code.google.com/p/hummingbir...unk/HummingBirdInterceptorBootloader/HIBL.ASM
This is where the code start real work, it does begin with standard ARM core jump vector table (just to keep stick to standard, these aren't used anyway).
1. It does use I9000 BL1_stage2 functions (init_system) which I linked to it, these are used to init DMC controllers, as to this point code is executing in and working with very tiny, 96KB iRAM space, after calling this function it turns all 512MB of RAM available.
2. Make sure DMC is configured properly (write some value to address 0x40~~ memory space, then read it and compare with previously written)
3. Reinit iRAM heap to the BL0 initial state (to convince it USB dload mode haven't been called yet), by storing and restoring UART pointer only (to keep debug output flowing properly)
4. Call iROM usb_downloader function.
5. Read the address where downloaded data has been placed.
6. Jump into this address.
This, properly used provides similiar debug output (similiar, because its outdated testlog)
������������������������������������������������������������������������
Uart negotiation Error
----------------------------------------
Hummingbird Interceptor Boot Loader (HIBL) v1.0
Copyright (C) Rebellos 2011
----------------------------------------
Calling IBL Stage2
DONE!
Testing BL3 area
DONE!
iRAM reinit
DONE!
Please prepare USB dltool with BL3
Starting download...
0x00000000
Desired BL3 EP: 0x40244000
Download complete, hold download mode key combination.
Starting BL3...
//OUTPUT BELOW IS COMING FROM SBL
Set cpu clk. from 400MHz to 800MHz.
IROM e-fused - Non Secure Boot Version.
Click to expand...
Click to collapse
It opens infinite capabilities. Instead of SBL to unbrick, Uboot can be loaded, or any armlinux kernel. It's all up to you - XDA Developers.

Awesome job guys!! Hats-off to you!

Amazing work, very nice job guys!

woop woop
Sent from my SGH-I897 using XDA Premium App

Amazing work. Glad to see this finally finished and open to the community with a tutorial. I also heard you would be porting this to windows, and i will look forward to that. I have a virtual Ubuntu machine however i can not get adb to work
My dad is also thinking about picking up a $20 infuse, and therefore I would get his old captivate, giving me 2 captivates. If this happens i will defiantly take you up on your $30 offer, and transform one into a super dev phone, and the other my daily phone. Then maybe i can help Rebellos and you with some bootloader development.
But seriusly. Once again amazing work guys

donated to adam. sorry didn't split up between adam n rebellos... adam pls b fair n share... but seriously guys, this is epic development.do appreciate and donate.

Thanks.
I updated the jar. If you're having problems launching it, it's because I made the Ultimate UnBrickable Resurrector from source from my other project, Heimdall One-Click... I forgot to change something in the manifest at the last minute. Please redownload if it won't launch.
This should work on any device which identifies itself as an S5PC110 .... B/D. Sometimes, if you're lucky, any phone can brick itself in this state.

When using Virtual box, how will the phone show up on the USB list pre-Download mode download?

It's honestly easiest if you have the time to dual boot an Ubuntu OS on your current machine. It has a major bug still but I figured out the issue and contacted Adam on the fix for it.

connexion2005 said:
It's honestly easiest if you have the time to dual boot an Ubuntu OS on your current machine. It has a major bug still but I figured out the issue and contacted Adam on the fix for it.
Click to expand...
Click to collapse
Yeah... I've spent a good bit messing with it and the settings in VB but it wont detect. (I hope it doesn't have to do with my soldering).
Ill try try the dual booting tomorrow and give it another shot.

connexion2005 said:
It's honestly easiest if you have the time to dual boot an Ubuntu OS on your current machine. It has a major bug still but I figured out the issue and contacted Adam on the fix for it.
Click to expand...
Click to collapse
Its not a bug... your computer is too old. 64bit only for now.

great work adam.....appreciate it..though i m a riff box owner(just bought it for fun)..so wont need this mod....
but still its a great work for others....
cheerss!!!!!!

killer_raj said:
great work adam.....appreciate it..though i m a riff box owner(just bought it for fun)..so wont need this mod....
but still its a great work for others....
cheerss!!!!!!
Click to expand...
Click to collapse
Why open the phone every time you have a problem? Apply UnBrickable Mod once and you will never need a screwdriver to unbrick your device. If you have spare time now, apply the modification, then use the tool later.
Btw... I have two RIFF JTAG boxes...

AdamOutler said:
This should work on any device which identifies itself as an S5PC110 .... B/D. Sometimes, if you're lucky, any phone can brick itself in this state.
Click to expand...
Click to collapse
LOL @ the understanding the way of "being lucky"
Added HIBL explanation
http://forum.xda-developers.com/showpost.php?p=17135277&postcount=2
I'll be working 3 day in row today on win32 cmdline port. However, WIN32 drivers API is such big [email protected]&#$*[email protected]!&$&@. So may take abit more.

Rebellos said:
LOL @ the understanding the way of "being lucky"
Added HIBL explanation
http://forum.xda-developers.com/showpost.php?p=17135277&postcount=2
I'll be working 3 day in row today on win32 cmdline port. However, WIN32 drivers API is such big [email protected]&#$*[email protected]!&$&@. So may take abit more.
Click to expand...
Click to collapse
There is a bootloader combination which will put the phone into this mode. I don't know it though... so, lucky.

AdamOutler said:
Its not a bug... your computer is too old. 64bit only for now.
Click to expand...
Click to collapse
Ok cool I'll dual boot a 64bit Ubuntu box to confirm this. I wasn't aware there were both x32 and x64 smdkusbdl tools but I didn't write this either! I just found it interesting that after replacing the suspect files in the .jar file that it worked perfectly on my "old 32 bit test mule"...
Amazing work. I almost spit my drink out after using it.

Please make this thread a sticky!!!!

AdamOutler said:
Why open the phone every time you have a problem? Apply UnBrickable Mod once and you will never need a screwdriver to unbrick your device. If you have spare time now, apply the modification, then use the tool later.
Btw... I have two RIFF JTAG boxes...
Click to expand...
Click to collapse
i m using cappy for almost 10 months now...but i never hardbricked my phone ...(touchwood)...
i never had to open my phone ..as i said i just bought the riff box for fun..and to help others....
but u r right.. for ur mod..i will hav to open my phone just once...and after that i can brick it as many times as i want..and will never need to open it again to unbrick it....thats a plus point....

I have never bricked my phone...but now I never will.
killer_raj said:
i m using cappy for almost 10 months now...but i never hardbricked my phone ...(touchwood)...
i never had to open my phone ..as i said i just bought the riff box for fun..and to help others....
but u r right.. for ur mod..i will hav to open my phone just once...and after that i can brick it as many times as i want..and will never need to open it again to unbrick it....thats a plus point....
Click to expand...
Click to collapse
Sent from my SGH-I897 using XDA Premium App

Related

Bodhi Linux on Iconia - Alpha 2

Hello all,
I'm getting prepared to upload my Alpha 2 port of Bodhi Linux for our Iconia. The thread for the original release is here. In the next few days, I'll be uploading the files to my server, writing up guides, and taking any questions. I highly recommend installing a GNU/Linux distribution before even attempting this. Using Linux in a VirtualBox *should* work, but I can't promise that. As usual, if this product bricks your device, it's not my fault. By attempting to use this release, you agree that it is not my fault. The same goes for instantaneous combustion, natural disasters, and acts of God.
New Features:
New recovery.img compiled using the Iconia, not at x86 processor (dunno if this means anything)
The ability to download, compile, and install the kernel/modules right from the device, no computer needed (after initial installation).
mkbootimg and mkbootfs
Scripts to automate grabbing the files needed for WiFi to work
Untested (May work, but I didn't have time to play with):
Bluetooth
Sound
3D acceleration
Here are the links needed to get started (not done yet):
[Guide] Installing Bodhi Linux onto the Iconia
[Guide] Compiling/Installing your own kernel!
[Download] Bodhi Linux for Iconia
[Download] recovery.img
[Download] Kernel Source
Screenshot
{
"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'd like to thank everyone who made Alpha 2 possible, including all kernel devs, etc. I'd also like to thank Jeff over at the Bodhi Linux forums.
Please ask as many questions as you'd like, even before Alpha 2 is released.
UPDATE:
The image is now up. Use gparted to partition your micro sd as follows: at least 1.5 GB (i think, it could be more) as the first partition, ext4 format. Name that partition "bodhi". Partition 2: atleast 128 MB, fat32 format. When done, mount partitions. Extract the bodhi tarball to the root of your card. Do it like this:
sudo su
cd /media/bodhi/
tar -jxvf /home/name/bodhi_alpha2.tar.bz2
Then type in ls, you should see etc , home, and the like. If you see a folder, you did it wrong.
Copy recovery.img to the 2nd partition. In Acer Recovery Installer, flash it using this custom image. Copy your nvram.txt to the card as well. Reboot into recovery. Enter the terminal. Type in setupwifi . This will copy nvram.txt to the correct place. I'll be writing up some official guides to get this working. BTW, what do you guys think of Plasma Active Two?
UPDATE (23 / 02 / 2012) : Bodhi will be on the backburner for a while. I've school stuff to do, and will be playing around with the leaked ICS.
It is very good
- Have you tested backlight regulating?
- Can you patch the kernel to overclock tegra?
Do you still need an 8 gig micro sd card for this? you mentioned something in alpha 1 about that being fixed in later versions. I really want to try this on an old 4 gb sd card so hopefully that might be enough
Great work btw! keep it up!
loband_ml said:
It is very good
- Have you tested backlight regulating?
- Can you patch the kernel to overclock tegra?
Click to expand...
Click to collapse
I have not tested backlight regulating yet.
I'm not too good at kernel patching, but anyone who wants to play with the kernel will just have to type in "getkernel" and it will dl & unpack it.
Thanks for your interest!
chaosking121 said:
Do you still need an 8 gig micro sd card for this? you mentioned something in alpha 1 about that being fixed in later versions. I really want to try this on an old 4 gb sd card so hopefully that might be enough
Great work btw! keep it up!
Click to expand...
Click to collapse
It may work on a 4GB, I'm going to be doing some testing w/ one today. The current 8GB I'm using is only Class 4, and Bodhi works pretty well on this older card of mine.
I'm sounding repetitive, but thanks for your interest as well! At first, I didn't think anybody would care about this too much.
When can we expect the required files to be uploaded? (an estimated day perhaps?). And do USB peripherals work (e.g keyboard/mouse) and camera work? And do you think either eclipse or netbeans IDE will work when installed?
Will this work with any Linux distribution?
I was wondering if your Linux recovery kernel will work with other rootfs images like ubuntu or kde or backtrack?
newbkilla said:
When can we expect the required files to be uploaded? (an estimated day perhaps?). And do USB peripherals work (e.g keyboard/mouse) and camera work? And do you think either eclipse or netbeans IDE will work when installed?
Click to expand...
Click to collapse
It should be up tomorrow, but my ISP sucks. I'll try getting it up. I've noticed that usb keyboards and mice do work. The apple mouse doesn't, but that's probably just a kernel module I didn't compile. I'll get that in the next version, or you could compile your own, which is very fun to do (seriously, on of my favourite hobbies.) No clue on the cameras, haven't tested. Eclipse / Netbeans may work, you'll have to test and post the results, please.
chrisnave1 said:
I was wondering if your Linux recovery kernel will work with other rootfs images like ubuntu or kde or backtrack?
Click to expand...
Click to collapse
Yes, it works with Ubuntu. I'm pretty sure you could load kde up on the bodhi image, log out, then select it as your sessions. It may be slow. I recommend taking a look at the Plasma Active 2 interface, built by the KDE folks. It's pretty sweet. I've just got done downloading backtrack, and it may work. Not sure, either.
backtrack
could you possibly upload a backtrack raw image for our iconia... would love it, would also entice me to donating hehe
chrisnave1 said:
could you possibly upload a backtrack raw image for our iconia... would love it, would also entice me to donating hehe
Click to expand...
Click to collapse
GEEZ! I upload one or two distro ports and now YOU want ME to work on ANOTHER one?!?
Lol, jk. I love backtrack, of course I'll work on it.
Also, can you include the florence keyboard into the rootfs in the next releases?
I have troubles with it`s compiling (becouse i am noob)
I look forward to)
wow thanks much I am still an infant when it comes to compiling kernels or even rootfs image lol... I I was able to get aitcrack-ng but not gerix yet cannot find good repository for bt5 to add
So, I now have the images up on the site. The next day or so I'll be working on an in-depth tutorial. I'll also post a tutorial for downloading / compiling the sources straight from the device.
and can not install on internal memory?
dimon2242 said:
and can not install on internal memory?
Click to expand...
Click to collapse
With the current kernel, no. I stay away from that for now, to prevent bricking. You can compile a kernel using the source to aim at the internal card. This is not reccomended, and I take no responsibility for anything done.
Backtrack anytime!
I'm interested for Backtrack for sure.
This website might be helpful for backtrack:
http://roms.tiamat-dev.com/tiamat_xoom/backtrack-5-with-aircrack-for-motorola-xoom/
It seems possible to use USB wireless adapter and drivers with the Xoom, I am in the office for too long this week and I'm starting to look at that very closely.
Running an RTL8187 monitor on backtrack on Iconia A500 might be something that could be done...
djxtabay said:
I'm interested for Backtrack for sure.
This website might be helpful for backtrack:
http://roms.tiamat-dev.com/tiamat_xoom/backtrack-5-with-aircrack-for-motorola-xoom/
It seems possible to use USB wireless adapter and drivers with the Xoom, I am in the office for too long this week and I'm starting to look at that very closely.
Running an RTL8187 monitor on backtrack on Iconia A500 might be something that could be done...
Click to expand...
Click to collapse
Thanks for the link. You see, we don't have to worry about making Android compatible drivers. On the Iconia, my kernels don't boot under chroot. They load themselves, then point at any chosen partition. Simply compile the needed driver in the kernel, flash it, (or just load the module), and go from there.
i had in mind internal SD card)
dimon2242 said:
i had in mind internal SD card)
Click to expand...
Click to collapse
I'll compile you a special kernel to boot to internal memory. Which partition (mmcblk0px) do you want it to boot to? I cannot verify it will work. It may brick your device. I am not responsible for anything that may happen.
I type debian and debian for username and password and I recieve the following error message:
"GDM could not write to your authorization file. This could mean that you are out of disk space or that your home directory could not be opened for writing. In any case, it is not possible to log in. Please contact your system administrator."
/edit to add image taken on my phone.

[GUIDE]Flash different versions of FirefoxOs on Alcatel One touch Fire

Firefox OS
Alcatel One Touch Fire
{
"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"
}
How to Flash Succesfully Any verion of Firefox OS
Get the Build(user.img,boot.img,system.img,data.img)
download a build from here http://elsimpicuitico.wordpress.com/firefoxos/
make your own with the mozilla guide (so stop here and follow mozilla guide)https://developer.mozilla.org/en-US/Firefox_OS/Building_and_installing_Firefox_OS
get one from a friend
Plug-in your Alcatel Fire(Hamachi)
Make sure you have the "Remote Debugging" enabled(Settings > Device information > More information > Developer > Remote Debugging)
Look inside the .zip/tar.gz you had downloaded,there some "flash" files.If:
You are on windows:double click on "flash.bat"
You are on linux,open the terminal in the folder you had unzipped the build,and type"./flash"
Done
If you have a consumer phone, not a dev edition, you will not get root access on adb.
So you have to do this in a Linux machine(or with Cygwin):
shutdown phone
power on pressing "volume-"
it will get 'stuck' into the "alcatel" logo. don't worry it probably worked, this is the screen for fastboot mode as well.
plug in your computer and check `fastboot devices`. if any error here, go read one of the thousands guides for fastboot and android usb drivers
get any boot image from that page. ideally one from the same country as it may matter....
flash the boot image on your phone with. test first with `fastboot boot boot.img`. if it works, redo the above steps and make it permanent `fastboot flash boot boot.img`. You need any boot image that has default.prop setting the user for adb as 0 instead of the default 1.
If you want the ClockworkMod recovery i can update this post to explain how to flash it .
If you will have any problem ,I'll help you and I will update this thread with your problem with the fix
Some infos
When you turn On your Alcatel OTF,you have 4sec to hold "volume-" button just after powering it up. It will stop at initial Alcatel’s logo.If you are ona Linux computer you can confirm that it is connected by typing "fastboot devices"-
Th Codenme of this phone is:Hamachi.
Credits
Me and the owner of the Firefox Os Builds for Hamachi​
Thanks HawkeyeWPR. This and your site was very helpful for me and my Fire. Keep going!
Your provided version 1.4 is very nice and fast and I could choose beetween two recoverys (CWM or TWRP). Thats awesome.
HawkeyeWPR said:
Plug-in your Alcatel Fire(Hamachi)
Make sure you have the "Remote Debugging" enabled(Settings > Device information > More information > Developer > Remote Debugging)
Look inside the .zip/tar.gz you had downloaded,there some "flash" files.If:
Click to expand...
Click to collapse
If you have a consumer phone, not a dev edition, you will not get root access on adb.
So you have to:
shutdown phone
power on pressing volume down
it will get 'stuck' into the "alcatel" logo. don't worry it probably worked, this is the screen for fastboot mode as well.
plug in your computer and check `fastboot devices`. if any error here, go read one of the thousands guides for fastboot and android usb drivers
get any boot image from that page. ideally one from the same country as it may matter....
flash the boot image on your phone with. test first with `fastboot boot boot.img`. if it works, redo the above steps and make it permanent `fastboot flash boot boot.img`. You need any boot image that has default.prop setting the user for adb as 0 instead of the default 1.
gcbxda said:
If you have a consumer phone, not a dev edition, you will not get root access on adb.
So you have to:
shutdown phone
power on pressing volume down
it will get 'stuck' into the "alcatel" logo. don't worry it probably worked, this is the screen for fastboot mode as well.
plug in your computer and check `fastboot devices`. if any error here, go read one of the thousands guides for fastboot and android usb drivers
get any boot image from that page. ideally one from the same country as it may matter....
flash the boot image on your phone with. test first with `fastboot boot boot.img`. if it works, redo the above steps and make it permanent `fastboot flash boot boot.img`. You need any boot image that has default.prop setting the user for adb as 0 instead of the default 1.
Click to expand...
Click to collapse
The same process i've done,cause the boot.img file contains the kernel with access to grant "root" access,now I'll add this step to my guide ,Thanks
subnet_zero said:
Thanks HawkeyeWPR. This and your site was very helpful for me and my Fire. Keep going!
Your provided version 1.4 is very nice and fast and I could choose beetween two recoverys (CWM or TWRP). Thats awesome.
Click to expand...
Click to collapse
I'm the Only here experiencing some crashes in the Firefox Browser?
HawkeyeWPR said:
I'm the Only here experiencing some crashes in the Firefox Browser?
Click to expand...
Click to collapse
nope. It is inconsistent as hell right now. Try to compile an image or use a latest build and submit bug reports (it's a full weekend effort just to get started, i tell you that)
Sent from my Nexus One using xda app-developers app
Is there any chance to do video for this, since most blogs are on Spanish and i believe most of us have no expirience in this? :S
Facyber said:
Is there any chance to do video for this, since most blogs are on Spanish and i believe most of us have no expirience in this? :S
Click to expand...
Click to collapse
just follow the points. and when it mentions "look for a guid on something" it is because there are already a ton of video-or-not guides on that stuff
any point in particular you are having trouble?
But a warning, it is unstable. the shipped image has pretty much everything you need anyway (a stable browser)
upgrading to 1.4 will give you almost nothing else new. The browser still has no extra options. no add-ons. nothing. just tabs, back foward, clear history. that is all. most of the changes from 1.1 to 1.4 were in the gaia (ffos launcher) and even that, weren't too interesting ones to being with.
my advice is to stick with the shipped image if you are not going to code for ffos. Or at least help submiting bug reports.
gcbxda said:
just follow the points. and when it mentions "look for a guid on something" it is because there are already a ton of video-or-not guides on that stuff
any point in particular you are having trouble?
But a warning, it is unstable. the shipped image has pretty much everything you need anyway (a stable browser)
upgrading to 1.4 will give you almost nothing else new. The browser still has no extra options. no add-ons. nothing. just tabs, back foward, clear history. that is all. most of the changes from 1.1 to 1.4 were in the gaia (ffos launcher) and even that, weren't too interesting ones to being with.
my advice is to stick with the shipped image if you are not going to code for ffos. Or at least help submiting bug reports.
Click to expand...
Click to collapse
Root part. Don't have clue how, but I found friend coder who knows this stuff so hes gonna try first.
I have intention on building apps for Firefox OS only, so I would like to see new versions, since Telenor in my country is retarded, they ain't relased 1.3 yet, even its been almost a month since relase. -.-
Facyber said:
Root part. Don't have clue how, but I found friend coder who knows this stuff so hes gonna try first.
I have intention on building apps for Firefox OS only, so I would like to see new versions, since Telenor in my country is retarded, they ain't relased 1.3 yet, even its been almost a month since relase. -.-
Click to expand...
Click to collapse
Having a device in the older version is good for that... just so you have an idea, i got my phone in a mexican store. it came with 1.1 and no sign of update ...ever. so your users will NOT be on the latest version anyway.
i suggest you simply use the emulator. develop. and ocasionaly test your app on your 1.3 device for performance and multitouch tests
if you really want to flash just to test apps, not to use your phone daily, you don't even need root just to update the image. unless you want a backup...
just use fastboot to overwrite the system partition (the user interface and gecko code). No root needed. just 3 steps:
1. boot with volume down.
2. plug USB in computer when it gets stuck on the white alcatel screen.
3. `fastboot flash system <name_of_the_file_with_system.img>`
that is all you need.
you will still be able to re-do that any time, so, go crazy. there is no way to brick the phone with that. (your system may be unusable if you use a bad image, but you can always flash a good one later on)
Well I want to use it daily, using apps and stuff like that, but also want to develop. I thought to try for this low device until some better phone came, or even tablet, much faster and stronger, than that will be other story.
Actually,will ship:
The ZTE Open C has a 4-inch, 800x480 display, a dual-core 1.2GHz Qualcomm Snapdragon 200 processor, 3G networking; 1,400mAh battery, 512MB RAM, 2GB flash storage, and 3-megapixel camera. The Spanish carrier Telefonica will sell it in Venezuela and Uruguay in the second quarter of 2014, ZTE said.
The ZTE Open II has a 3.5-inch 480x320 display, dual-core 1.2GHz Qualcomm Snapdragon processor, 3G networking; 1,150mAh battery, 256MB RAM, 2GB flash storage, and 2-megapixel camera. Telefonica will sell this model in six countries
The Alcatel One Touch Fire S, the company's highest-end model, has 4G LTE networking, a 4.5-inch 960x540 IPS screen, a quad-core 1.2GHz processor, an 8-megapixel rear-facing camera and 2-megapixel front-facing camera, and support for near-field communications (NFC).
The Alcatel One Touch Fire E is a step down. It's also got a4.5-inch 960x540 screen, but not with in-plane switching, and its 1.2GHz processor is only a dual-core model. Its rear-facing camera has a 5MP resolution but its front-facing camera is only 0.3MP.
The Alcatel One Touch Fire C is the clear successor to 2013's model. Its 3.5-inch 480x320 screen is the same size, but it now is accompanied by a dual-core 1.2GHz processor. Its camera is pretty low-end, just a 0.3-megapixel model.
and DO NOT FORGET the 25$ model:
Allwinner A31 (1.2GHz); Cortex-A7 Quad-core, PowerVR 544MP2
4.5-inch screen (FWVGA 854×480 pixels)
Cameras: Rear: 5MP / Front: 2MP
3G UMTS quad-band (850/900/1900/2100)
8GB memory
256MB -1GB RAM (adjustable by developer)
A-GPS, NFC
Battery capacity: 1,800 mAh
Wi-fi: 802.11 b/g/n, Bluetooth, Micro USB
At the moment,iìm using my Alcatel OTF as main-daily-use phone,for twitter,mails,pictures,web-browsing,call&texting(+ Whatsapp),and i admit ,sometime he get me angry,but at least ,it's good,for a simple and daily use,but i recommend the 1.3 vers,1.4 it's buggy.
I know all about those new phones, It's kinda my job to know that.
Main reason why I'm not using as daily phone casue my main number is not in Telenor network (Thank God to that, they are most expensive here and yet give less free sms and minutes then other two) and in one shop they couldn't unlock it, whatever code they get it won't work, so I will wait little more and find new shop.
We already given up from Telenor relasing new version, believe me, they gonna relase 1.3 when 2.5 comes out. Mark my words.
I have a question about back up. Do I have to back up? Or can I simply root and then instal? I have no Idea hwo to back up image on Windows.
Firefox os
This is the first Time i've discovered this. When Will this be readily available in the U.S.? I can find the devices on amazon, but will they work with our carriers?
Rustydagger said:
This is the first Time i've discovered this. When Will this be readily available in the U.S.? I can find the devices on amazon, but will they work with our carriers?
Click to expand...
Click to collapse
If you want a device that works in US you can always buy one of the ZTE Open or Open C from the ZTE_US ebay store.
The Open is pretty much the same as the Alcatel Touch Fire
Sent from my V3 using Tapatalk
linr76 said:
If you want a device that works in US you can always buy one of the ZTE Open or Open C from the ZTE_US ebay store.
The Open is pretty much the same as the Alcatel Touch Fire
Sent from my V3 using Tapatalk
Click to expand...
Click to collapse
I agree ^^
Sent From My Samsung Galaxy Y s5360
Thank you for your guide-resume
I was trying to build the latest Firefox OS master branch, but unfortunately, due to some issues, I can't do it for now.
Unfortunately, the builds which the blog Simpliculitico gives are modified ones;
I'd like a clean pure one;
can someone send/upload an allready built and unmodified master image for One Touch Fire? I have no friends who can send me one
Thank you so much *
I tried to follow the instructions and got help on irc to create the custom kennel for that dammed phone.
Two weekends later and i failed every single time.
Never got even a half working one.
Also the one from the blog is far from perfect...
I wouldn't keep my hopes up.
Sent from my XT1053 using XDA Free mobile app
I agree with you,that's why now i will make a guide to have Official OTA from mozilla.

[SUCCESS] Interop-Unlocking LUMIA - with JTAG

Hi there
Well, as we really need Interop Unlock for our Lumia phones, i decided to check this out myself.
As i already have ATF Box for a long time, i decided to buy JTAG activation and dolphin clip + lumia jigs, that i do not have to solder my phone.
Also i have ordered a Lumia 520 testing phone on ebay.
So, as the ATF Team made an awesome JTAG software update, i'm trying to interop unlock that Lumia 520 the hardware way, as just software seems to be too tough...
Well, what i did so far:
1. Freshly flashed Lumia 520 RM-914 with latest stock rom
2. Did the setup/beginning after turning it on for 1st time
3. developer unlocked it with SDK on PC
4. Made Full Dump with JTAG from dev-unlocked phone
5. Mounted MainOS partition of dump with program "OSFMount" (-->appears as Local harddisk example drive E: )
6.Loaded the SOFTWARE hive with regedit on PC from "E:\Windows\System32\config"
7. Edited the following values:
PortalUrlInt = http://127.0.0.1
PortalUrlProd = http://127.0.0.1
MaxUnsignedApp = 10003
8. unloaded SOFTWARE hive
9. unmounted dump-image
10. wrote image back via jtag
I thought it might be a good Idea to dev-unlock the phone before messing with the registry, to make sure "DeveloperUnlockState = 1" gets written the "legal" way, as the key is not available in registry before.
Maybe it's better to just modify an existing key, than adding a new one...
Well, long story short: The result is not totally satisfying.
After writing the modified image back to the EMMC, the phone is booting up, but i can NOT deploy homebrew apps that require interop unlock, like @GoodDayToDies "EnableAllSideloading.xap" for example.
But i can deploy "nomal" apps like @cpuguys "Toastlauncher" and @GoodDayToDies "Webserver"
The weird thing: If i check the reg-values via WebServer on the Phone, i can see my edited values.
So the changes ARE written to the phone. The phone just doesn't use them...
So, the good thing: phone is booting with modified rom :good:
But, the bad thing: Changes are not working.
EDIT:
SUCCESS!!!
After adding
{
"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 could successfully sideload "EnableAllSideloading.xap"
After executing enableallsideloading i could sideload latest WPHTweaks build.
Now i have 3rd tile row enabled!
awesome!
Also member @myst02 is working on interop-unlocking the lumia phones. So we decided to make this a together-project.
See his achievements here: http://forum.xda-developers.com/showthread.php?t=2713098&page=10 :good:
reserved
to be able to sideload EnableAllSideloading.xap you need to change following registry key:
Software\Microsoft\SecurityManager\CapabilityClasses
add: MultiSz String
name: ID_CAP_DEVELOPERUNLOCK_API
value: CAPABILITY_CLASS_THIRD_PARTY_APPLICATIONS
have fun.
I have found this during smurfing on the internet.
Dont know if this is something worth trying, but maybe it gives you some pointers or help.
http://windowsphonehub.in/tutorials...eloper-unlock-windows-phone-sideload-10-xaps/
lordmaxey said:
Well, as we really need Interop Unlock for our Lumia phones, i decided to check this out myself.
Click to expand...
Click to collapse
Good job!
lordmaxey said:
Let's get this rolling, guys! :good:
Click to expand...
Click to collapse
BTW, it's not a real "hack", and not acceptable/affordable for the 99.9% Lumia users and developers...
Wow you did a fantastic job
as @error0x0000034 mentioned you forget to open DeveloperUnlock_API
Software\Microsoft\SecurityManager\CapabilityClass es
add: MultiSz String
name: ID_CAP_DEVELOPERUNLOCK_API
value: CAPABILITY_CLASS_THIRD_PARTY_APPLICATIONS
sensboston said:
BTW, it's not a real "hack", and not acceptable/affordable for the 99.9% Lumia users and developers...
Click to expand...
Click to collapse
Yeah, but it's at least something worth trying
ngame said:
Wow you did a fantastic job
as @error0x0000034 mentioned you forget to open DeveloperUnlock_API
Software\Microsoft\SecurityManager\CapabilityClass es
add: MultiSz String
name: ID_CAP_DEVELOPERUNLOCK_API
value: CAPABILITY_CLASS_THIRD_PARTY_APPLICATIONS
Click to expand...
Click to collapse
Oh, i see...
I'm just wondering that this CAP was not secessary on Ativ S?
Or am i wrong?
I really thought it was just the 3 regkeys quoted in the first post...
lordmaxey said:
Yeah, but it's at least something worth trying
Oh, i see...
I'm just wondering that this CAP was not secessary on Ativ S?
Or am i wrong?
I really thought it was just the 3 regkeys quoted in the first post...
Click to expand...
Click to collapse
I don't remember Ativ S Interop but I know it had a BootStrap app
maybe that app unlock this api i'm not sure but I know you have to open this cap first to run EnableAllCapabilities
Nice work :good:
so now , you can make a small bussines with this
interop unlock for only *** $
and you are now the one and only interop unlocked retail Lumia owner
ceesheim said:
Nice work :good:
so now , you can make a small bussines with this
interop unlock for only *** $
Click to expand...
Click to collapse
Haha Yay, i'm going to be rich *lol*
ceesheim said:
and you are now the one and only interop unlocked retail Lumia owner
Click to expand...
Click to collapse
No, not yet.
I'm trying to deploy the bootstrap samsung app to the 520 this afternoon. If it works, i maybe can deploy the other apps.
If not, i'm trying to open that CAP by editing the Dump again and writing it back via JTAG.
We'll see, but i'm curious
btw: Why are these damn smileys always displayed in the next line?
btw: Why are these damn smileys always displayed in the next line?
don't know , i just seen that too
lordmaxey said:
Haha Yay, i'm going to be rich *lol*
No, not yet.
I'm trying to deploy the bootstrap samsung app to the 520 this afternoon. If it works, i maybe can deploy the other apps.
If not, i'm trying to open that CAP by editing the Dump again and writing it back via JTAG.
We'll see, but i'm curious
btw: Why are these damn smileys always displayed in the next line?
Click to expand...
Click to collapse
Samsung Bootstrap uses some Samsung-specific DLLs as far as I know. This won't help you, tried this already on my Huawei Ascend W1. This won't work on your Lumia either I think. But its worth a try of course.
You'll have to edit the registry key I mentioned before to be able to sideload EnableAllSideloading.xap. You need to load the SOFTWARE file from Windows/System32/config again into your registry and edit following key. Maybe try using a registry editor on your phone before using the method you described above, but I don't think that this will work. So, you probably have no other choice than opening up your device again and edit the SOFTWARE reg-file. Then sideload EnableAllSideloading.xap and you'll be able to sideload pretty much everything you want.
Question for more experienced devs and hackers:
Is there a registry tweak or some settings anywhere else on the phone that we can access though JTAG and that allows us to boot the phone (Lumia in this case) as a mass storage device with full filesystem access? Like on the Huawei Ascend W1. This would simplify the process of changing registry keys a lot.
Best regards and good luck.
lordmaxey said:
Haha Yay, i'm going to be rich *lol*
No, not yet.
I'm trying to deploy the bootstrap samsung app to the 520 this afternoon. If it works, i maybe can deploy the other apps.
If not, i'm trying to open that CAP by editing the Dump again and writing it back via JTAG.
We'll see, but i'm curious
btw: Why are these damn smileys always displayed in the next line?
Click to expand...
Click to collapse
Bootstrap Samsung will not work on Lumia.
error0x0000034 said:
Samsung Bootstrap uses some Samsung-specific DLLs as far as I know. This won't help you, tried this already on my Huawei Ascend W1. This won't work on your Lumia either I think. But its worth a try of course.
You'll have to edit the registry key I mentioned before to be able to sideload EnableAllSideloading.xap. You need to load the SOFTWARE file from Windows/System32/config again into your registry and edit following key. Maybe try using a registry editor on your phone before using the method you described above, but I don't think that this will work. So, you probably have no other choice than opening up your device again and edit the SOFTWARE reg-file. Then sideload EnableAllSideloading.xap and you'll be able to sideload pretty much everything you want.
Click to expand...
Click to collapse
Like this then, right?
Ok, I'll try this next week, i sadly won't have time this weekend.
error0x0000034 said:
Question for more experienced devs and hackers:
Is there a registry tweak or some settings anywhere else on the phone that we can access though JTAG and that allows us to boot the phone (Lumia in this case) as a mass storage device with full filesystem access? Like on the Huawei Ascend W1. This would simplify the process of changing registry keys a lot.
Best regards and good luck.
Click to expand...
Click to collapse
No. once JTAG halts the phone, it's halted. You can't just "pause" the phone, make changes and continue booting. Sadly.
So, only chance is by writing the modified dump back.
It's not for Lumia only, it's a universal method for every WP8 devices (including emulator) that could enter MassStorage mode
And the Bootstrap app is not a magic, it use the system service by Samsung to modify the CapabilityClasses registry key mentioned by above and this could be done by modify reg hive directly
lordmaxey said:
Like this then, right?
Ok, I'll try this next week, i sadly won't have time this weekend.
Click to expand...
Click to collapse
exactly. I have done this on my Ascend W1 several times, but its easier, because I can enter Mass Storage Mode through bootloader.
No. once JTAG halts the phone, it's halted. You can't just "pause" the phone, make changes and continue booting. Sadly.
So, only chance is by writing the modified dump back.
Click to expand...
Click to collapse
I don't know how JTAG method works exactly, I only know that the device needed isn't cheap and can restore bricked phones. How it works? I have no idea, but I'm sure I'll learn quickly.
I will do some research on that soon. I'm a learning noob. :cyclops:
best regards,
error0x0000034
error0x0000034 said:
I don't know how JTAG method works exactly, I only know that the device needed isn't cheap and can restore bricked phones. How it works? I have no idea, but I'm sure I'll learn quickly.
I will do some research on that soon. I'm a learning noob. :cyclops:
Click to expand...
Click to collapse
Me neither
Most credits go to X-Shadow from advance-box team.
Because i had the Idea of modifying the phone dump and read/write via JTAG.
But usually, ATF only supported bootloader repair via JTAG. So i contacted X-Shadow and within only two weeks he updated the jtag-application, and added Custom Read/Write to every part of the EMMC.
That's how i could dump the rom, modify it and write it back.
Absolutely awesome work from that team, just releasing a software because of ONE single inquiry. :good::good::good:
Aw crap, I totally forgot to tell you to test a pure-interop app (like the bootstrap one). You interop-unlocked but failed to capability-unlock, and most WP8 homebrew requires both so of course you couldn't sideload it. DERP
But hey, if you successfully edited the capability class of ID_CAP_DEVELOPERUNLOCK_API - and it looks like you did, or could - then you can use EnableAllSideloading to capability-unlock the phone (it just edits all the other capabilities' classes). I could probably also write a "BootstrapNokia" app if you'd like; I think we have interop-based registry functions for WP8 Lumias, which would allow (for example) making SamWP8 Tools work on your Nokia as well.
SamWP8 tools on Nokia would be great.
I'll check that monday evening, when i'm back at my computer.
I'll keep you informed
GoodDayToDie said:
Aw crap, I totally forgot to tell you to test a pure-interop app (like the bootstrap one). You interop-unlocked but failed to capability-unlock, and most WP8 homebrew requires both so of course you couldn't sideload it. DERP
But hey, if you successfully edited the capability class of ID_CAP_DEVELOPERUNLOCK_API - and it looks like you did, or could - then you can use EnableAllSideloading to capability-unlock the phone (it just edits all the other capabilities' classes). I could probably also write a "BootstrapNokia" app if you'd like; I think we have interop-based registry functions for WP8 Lumias, which would allow (for example) making SamWP8 Tools work on your Nokia as well.
Click to expand...
Click to collapse
isn't it better to put FCROUTER and other samsung dlls in Windows folder?
as far as i know ID_CAP_INTEROPSERVICES allow it

Lumia 1520 Starting work on custom ROM !

Hi Everyone !!
Work on the first custom rom WP8 for Huawei w1 been completed successfully .
Time for something new !
I would like to announce that I start work on Custom ROM for nokia lumia 1520. First attempt at flashing the modified file ffu done successfully .
Unfortunately, in another attempt something went wrong. I switched the phone in Download mode, QPST can repair the phone but I dont have appropriate files (currently). I have Riff Box JTAG but this programator does not support L1520 and i need ATF jtag.
I'll keep you informed about the progress !! :fingers-crossed:
I collect money for the ATF and the new phone, otherwise I can't continue to work. In the future, project will be developed for many other devices with WP8.
Interesting. First of all: Congrats on the succesfull flash,
second of all: I hope you can resurrect your Lumia 1520 how did you get the 1520 to accept the modified rom though? Though Lumias check the signature after the flashing process has completed?
Thanks for congrats
I can ressurect my lumia in 2 ways:
1. I need have repair boot files for QPST
2. I need AFT JTAG
I have methods to cheat the verification process. In the same way I did in Huawei W1. :victory:
These are my priorities:
1. Development and refinement the ability to flash the modified FFU file.
2. Ability to run the phone in mass storage mode
3. Modification software
4. Adapting WP8CRUU for Luma 1520
WojtasXda said:
Thanks for congrats
I can ressurect my lumia in 2 ways:
1. I need have repair boot files for QPST
2. I need AFT JTAG
I have methods to cheat the verification process. In the same way I did in Huawei W1. :victory:
These are my priorities:
1. Development and refinement the ability to flash the modified FFU file.
2. Ability to run the phone in mass storage mode
3. Modification software
4. Adapting WP8CRUU for Luma 1520
Click to expand...
Click to collapse
Getting the boot files might be the trickier method, but you could try what I described in your other post. I guess the ATF Box is your best chance. I'll look through the 1520 update cabs maybe theres something in there that'll help you build the mbn boot image, like on htcs. (which are, for the 8s encrypted, for the 8x not, as far as I know.) If you feel okay with it you can shoot me a message with tips on how you managed to do that, if not, that's not a problem
WojtasXda said:
Thanks for congrats
I can ressurect my lumia in 2 ways:
1. I need have repair boot files for QPST
2. I need AFT JTAG
I have methods to cheat the verification process. In the same way I did in Huawei W1. :victory:
These are my priorities:
1. Development and refinement the ability to flash the modified FFU file.
2. Ability to run the phone in mass storage mode
3. Modification software
4. Adapting WP8CRUU for Luma 1520
Click to expand...
Click to collapse
Are you reading this thread: http://www.coolxap.com/forum-199-1.html ?
I received a lot of information about huawei w1 on this site. When read about it in December 2013.
Actually if the verification bypass works (which, knowing MS's tight security on Nokias, I highly doubt), it just needs to be released as a method, and after that, anyone can make their own custom ROM.
I'd definitely make some changes to the system (clear out some default apps, add some of my own, change the accent colours, allow interop and other caps to any apps, increase custom app limit), but that would break the built-in system updater. So beware modders, DO NOT use official updates when on modded firmware!
WojtasXda said:
Hi Everyone !!
Work on the first custom rom WP8 for Huawei w1 been completed successfully .
Time for something new !
I would like to announce that I start work on Custom ROM for nokia lumia 1520. First attempt at flashing the modified file ffu done successfully .
Unfortunately, in another attempt something went wrong. I switched the phone in Download mode, QPST can repair the phone but I dont have appropriate files (currently). I have Riff Box JTAG but this programator does not support L1520 and i need ATF jtag.
I'll keep you informed about the progress !! :fingers-crossed:
Click to expand...
Click to collapse
Hi,
I have an ATF Box (lordmaxey & me interop unlocked our Lumias with it, do you remember me ) and would like to help you. Feel free to PM me
Another question, did you just modify the .ffu file via Hex Editor? I've tried it myself a long time ago, but it didn't work and I had to repair it with my ATF. Is there a bug in newer Nokia FFU files?
myst02
feherneoh said:
Flashing the custom ROM is not hard, so I would give it a try
Just be sure you don't touch boot partitions, so you will be able to boot into flashmode
On L520, I could simply flash ANY ffu using CareSuite, so flashing works, just need idea, what to change in ROM
Click to expand...
Click to collapse
How are you able to bypass signature checking though? Funny how on Lumias you can apparently edit the MainOS Partition but cannot touch the Boot ones, and on HTC it's exactly the reverse.
Guys ... the only barrier that separates us from the Custom ROM are 2 files that i need to create and adapt to the device. I mean MPRG8974.mbn ((hex) and msimage8974.mbn . Anyone who has knowledge on this topic, please help !!
This is my other topic about mprg/misimage
http://forum.xda-developers.com/hardware-hacking/hardware/qpst-help-create-mprg-msimage-mbn-t2949492
Here is a lot of information about QPST
http://forum.xda-developers.com/showthread.php?t=2136738
how to build mprg and msimage [/url]
http://blog.csdn.net/ziyouwa/article/details/16331545
feherneoh said:
Start phone recovery process in CareSuite, select official firmware, press start
When it asks you, to connect the phone, just replace the ffu file with the modified one
Boot partition should not be touched, as the SoC checks its signature, and your phone will be stuck in quallcomm's DLMODE
Click to expand...
Click to collapse
how to modify FFU ? have you any tool for it ?
I know we can Convert it using ImgMounnt but how to reconvert it to ffu ?
feherneoh said:
Start phone recovery process in CareSuite, select official firmware, press start
When it asks you, to connect the phone, just replace the ffu file with the modified one
Boot partition should not be touched, as the SoC checks its signature, and your phone will be stuck in quallcomm's DLMODE
Click to expand...
Click to collapse
Okay, good, Are you sure that your phone will not reject the file when it encounters an error?
How do you think why was invented HSPL ?
For Huawei just enough to crack the flash tool in PC to be able to upload an unsigned app / ffu file. Phone does not validate the data but Huawei is different story. While working on the Custom ROM I used QPST with MPRG ,MSIMAGE, xml's and other files. JTAG also be useful. Without QPST not have been possible creating Custom ROM for Huawei.
Therefore necessary there is start working on the most needed things.
ngame said:
how to modify FFU ? have you any tool for it ?
I know we can Convert it using ImgMounnt but how to reconvert it to ffu ?
Click to expand...
Click to collapse
Do you think it is that simple? If yes, where are the custom roms? Where these modified files? Of course there are tools to build files ffu, signing and opening them, but they are not available for "ordinary" people.
Well ... I go learn and explore the dark side of QPST
Regards
WojtasXda said:
Okay, good, Are you sure that your phone will not reject the file when it encounters an error?
How do you think why was invented HSPL ?
For Huawei just enough to crack the flash tool in PC to be able to upload an unsigned app / ffu file. Phone does not validate the data but Huawei is different story. While working on the Custom ROM I used QPST with MPRG ,MSIMAGE, xml's and other files. JTAG also be useful. Without QPST not have been possible creating Custom ROM for Huawei.
Therefore necessary there is start working on the most needed things.
Do you think it is that simple? If yes, where are the custom roms? Where these modified files? Of course there are tools to build files ffu, signing and opening them, but they are not available for "ordinary" people.
Well ... I go learn and explore the dark side of QPST
Regards
Click to expand...
Click to collapse
I know it's not easy and simple and I know there's at least one tool to create and edit ffu files and it's also not public but i thought he developed a FFU Editor app ! or he flashed Custom Rom many times !
and also I think you mean Phone Image Designer of Microsoft :
{
"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"
}
feherneoh said:
I have used HxD hex editor to find the partition headers, then used OSFMount to mount them. You can either mount a part of the ffu, or copy the partition to a separate image
As far as I know (my bricked 520 proves it) SoC's built-in ROM checks the first partition's signature using the public key in Q-Fuse, so let's crack RSA and stuff like that. SPL/HSPL was used to load CE, NT on ARM uses UEFI
Click to expand...
Click to collapse
you bricked your phone when you try this way ?
If( YourAnswer == "Yes" )
{
MessageBox.Show("Surely This way can't be useful or it's not the complete way and we need to research more");
}
else
{
//More Details go here
}
feherneoh said:
This happened when I tried to modify first partition (shown in attachments in previous post)
I'm not sure, if I added that in this thread, too, but only try, if you have JTAG box, so you won't mess up everything
Click to expand...
Click to collapse
Unfortunately I have no JTAG box (riff , atf and etc.)
I will look for way you provide and check it .
I have to find someone with JTAG in Mashad,Iran . Is there anyone ?
it is necessary to learn how to create MPRG / MSIMAGE and use QPST Then jtag will not be needed. These files are obtained by reading the data from the memory EMMC in this case VHD would be the best solution.
OK OK your way worked
I could create 3 Partitions from my L920 (RM-821) Rom .
I couldn't access MainOS partition in this ROM .
sounds good to find this working way but need to work on it hours and hours .
feherneoh said:
Once found something like MPRG in ffu
Open another SoC's MPRG, and look for the first 8 0r 16 bytes in ffu file
Click to expand...
Click to collapse
I do not know if this is true, but MPRGXXXX.bin or MPRG.hex (Intel hex) suitable for many devices. Msimage is built only for the appropriate device.
@WojtasXda : Are you using caresuite to flash the rom, or do you have another tool?
Click to expand...
Click to collapse
Yes i have own tools for example WP8RUU or WP8CRUU
Things that might be of interest to a custom ROM developer:
* I've just made big progress in figuring out how capabilities work on the phone. Setting them via custom ROM is definitely one of the easier ways it might be done, if you can create arbitrary registry keys and set arbitrary values in them.
* One particularly valuable thing you could add to a non-Samsung ROM is the RPC driver/service/whatever that lets Samsung's RCPComponent library work. I don't know how hard it would be to hack that in, though. The binaries and the registry keys for the service shouldn't be hard to obtain, but I don't know if there will be problems with signatures or anything. Still, if you can get it working, this would mean that Samsung homebrew, and everything we can do with it (such as write arbitrary places in the registry and move files around as SYSTEM) becomes available on the 1520.
Somewhat relatedly, I find myself in need of a new phone (I think my ATIV S may be unrecoverable, and it wasn't even due to a hack I was doing!) and this piques my interest in getting a 1520...
feherneoh said:
Also (just an idea) RT certificates could be added. Maybe some(!) RT apps could run on the phones
Click to expand...
Click to collapse
These apps work now on WP8.1
wp8.1 supports appx and appxbundle formats so we don't have problem with running them on phones .
If you mean running apps like Multimedia 8 on phone I think we will run into resolution problem .
Not going to happen. First of all, the ported desktop apps only work when signature enforcement is off ("jailbroken") even *on RT*; until/unless we get a signature bypass for WP8 that's a complete non-starter.
The other major problem is that all the base libraries for RT are different than for WP. This extends all the way down to the really core stuff like Kernel32.DLL; RT (like normal Windows) has one, but WP8 doesn't (the functions are split into kernelbase.dll and kernel32legacy.dll). Then there's all the code (like support for the normal desktop interface) that WP8 just flat out doesn't have.
I'm not saying it's impossible to get RT code running on WP8... but it's probably easier to port the entire RT OS to the phone (which is *not* easy, but is possible) than it is to get RT software running on WP8 OS.

[ROOT][TOOL]AutoRoot

AutoRoot
MAJOR UPDATE AUTOROOT 1.1 WITH UI.!!
CHANGELOG
V 1.1 30/1/2017
1. Made an UI
2 .Now Download automatically TWRP and SuperSU
Instructions :
1.You MUST to have adb installed on your PC.
2.Connect your phone to your PC via USB cable.(type C to microUSB adapter costs~9.99).
3.Run AutoRoot
4.Click Download button. (This will download TWRP and SuperSU app)
5.Click Root button
Enjoy
PLEASE ASK ME IF YOU HAVE ANY TROUBLE.
DOWNLOAD
SCREENSHOTS
{
"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"
}
dimkyr said:
AutoRoot
I have developed this exe to help you to root your Nexus 5X.
Instructions :
1.You MUST to have adb installed on your PC.
2.Connect your phone to your PC via USB cable.(type C to microUSB adapter costs~9.99).
3.Run AutoRoot.exe.
4.Follow Instructions.
Enjoy
PLEASE ASK ME IF YOU HAVE ANY TROUBLE.
USEFULL LINKS
Twrp
SuperSU
ΤΗΕ VIRUS ALERT IS FAKE ! VIRUS TOTAL SCAN : https://www.virustotal.com/en/file/...9c40c8e11ca931c2cd1fa289/analysis/1484572253/
DOWNLOAD
Click to expand...
Click to collapse
Hi! Could you explain a little bit more about this tool. What does it do? Does it unlock bootloader? Does it flash TWRP? Does it root? How? Thanks!
CLPose said:
Hi! Could you explain a little bit more about this tool. What does it do? Does it unlock bootloader? Does it flash TWRP? Does it root? How? Thanks!
Click to expand...
Click to collapse
Hello, this tool unlock bootloader, install twrp and root your phone but you have to manually download twrp img and superSU zip.Now i am working to do this automatically.. I write it in batch and just using adb commands. Soon i will upload the code in github, it's a very easy code at all.
I am here to help everytime you want .
dimkyr said:
Hello, this tool unlock bootloader, install twrp and root your phone but you have to manually download twrp img and superSU zip.Now i am working to do this automatically.. I write it in batch and just using adb commands. Soon i will upload the code in github, it's a very easy code at all.
I am here to help everytime you want .
Click to expand...
Click to collapse
Why is this a thing? Why not just stick to the tried and true method of unlocking or use Nexus ToolKit?
v.0.0.0.1 ? What?
bradhoschar said:
Why is this a thing? Why not just stick to the tried and true method of unlocking or use Nexus ToolKit?
Click to expand...
Click to collapse
is it bad make your own tool?
dimkyr said:
is it bad make your own tool?
Click to expand...
Click to collapse
No, it isn't bad. But usually when someone makes a tool it has a high level of flexibility and the program is usually very dynamic. Yours is like 100% static. It's like written in stone what the program is going to execute so that makes this program not user-friendly at all. To be honest with you, it's a nice try. I mean it proves you know and know how to use various batch functionalities. But it's nothing to write home about. I'd suggest diving into something like Java or Python and let the user decide more options so eventually you have a dynamic, but very robust tool for people to use.
2¢
sprremix said:
No, it isn't bad. But usually when someone makes a tool it has a high level of flexibility and the program is usually very dynamic. Yours is like 100% static. It's like written in stone what the program is going to execute so that makes this program not user-friendly at all. To be honest with you, it's a nice try. I mean it proves you know and know how to use various batch functionalities. But it's nothing to write home about. I'd suggest diving into something like Java or Python and let the user decide more options so eventually you have a dynamic, but very robust tool for people to use.
2¢
Click to expand...
Click to collapse
Thank you for your advices! I am begginer with all this thing and i am looking to learn more and make more dynamic tools. I am searching but it's hard to find information about programming for smartphones. So i am looking for help but i don't know where to search.
[Sorry for my bad english]
very cool
thanks for your contribution, everybody started somewhere and there are tons of folks who want a quick no frills method of rooting phones of all makes, Ive done rooting for $ for folks who dont want to learn how for whatever reason and woulduse a tool like this to just get the job done quick & easy.
keep plugging away at it add as much functionality as you want, people just like to troll and down anybody on the 'net but would never have the balls to do it IRL.
Ive been around this forum since before android and have seen it grow, I wish people would be more appreciative and troll less, maybe this tool isnt for you, but it may be just what somebody else is looking for....
I know how to root and have done it many times, Im about to root a bullhead and im glad this tool is here, why do it by hand if somebody else automated it?
work smarter not harder.
bhang
bhang said:
thanks for your contribution, everybody started somewhere and there are tons of folks who want a quick no frills method of rooting phones of all makes, Ive done rooting for $ for folks who dont want to learn how for whatever reason and woulduse a tool like this to just get the job done quick & easy.
keep plugging away at it add as much functionality as you want, people just like to troll and down anybody on the 'net but would never have the balls to do it IRL.
Ive been around this forum since before android and have seen it grow, I wish people would be more appreciative and troll less, maybe this tool isnt for you, but it may be just what somebody else is looking for....
I know how to root and have done it many times, Im about to root a bullhead and im glad this tool is here, why do it by hand if somebody else automated it?
work smarter not harder.
bhang
Click to expand...
Click to collapse
Hi! Thanks for encouriging @dimkyr developing a easy-to-use and useful tool like this one. I think you're 100% right! :highfive: Did you try it yourself? OP, on how many devices did you test your tool? What about drivers for Windows? Could you add some screenshots? I'm trying to root my N5X (MM-MDA89E) and I just can't. I've successfully unlocked its bootloader with NRT, but NRT keeps failling when rooting (tried in my PC with Windows 10, in two other PC with W7, and other PC with Xubuntu) :crying:. I'd be glad to test this tool if it's 100% sure! I WANT ROOT! In case you don't notice, I'm a noob! But I can't afford bricking my new N5X. Thanks!
CLPose said:
Hi! Thanks for encouriging @dimkyr developing a easy-to-use and useful tool like this one. I think you're 100% right! :highfive: Did you try it yourself? OP, on how many devices did you test your tool? What about drivers for Windows? Could you add some screenshots? I'm trying to root my N5X (MM-MDA89E) and I just can't. I've successfully unlocked its bootloader with NRT, but NRT keeps failling when rooting (tried in my PC with Windows 10, in two other PC with W7, and other PC with Xubuntu) :crying:. I'd be glad to test this tool if it's 100% sure! I WANT ROOT! In case you don't notice, I'm a noob! But I can't afford bricking my new N5X. Thanks!
Click to expand...
Click to collapse
Thank you everybody !!
I tested this tool to my N5X and work perfectly. But it's weird that NRT failed..
It's always a chance to fail or brick.
I will post screenshot later in this day!
With regards
CLPose said:
Hi! Thanks for encouriging @dimkyr developing a easy-to-use and useful tool like this one. I think you're 100% right! :highfive: Did you try it yourself? OP, on how many devices did you test your tool? What about drivers for Windows? Could you add some screenshots? I'm trying to root my N5X (MM-MDA89E) and I just can't. I've successfully unlocked its bootloader with NRT, but NRT keeps failling when rooting (tried in my PC with Windows 10, in two other PC with W7, and other PC with Xubuntu) :crying:. I'd be glad to test this tool if it's 100% sure! I WANT ROOT! In case you don't notice, I'm a noob! But I can't afford bricking my new N5X. Thanks!
Click to expand...
Click to collapse
im on linux atm so no i havent tried it, if the toolkit isnt working just do it manually, follow a walk thru to the letter take your time, as long as u follow instructions for your build you will be fine(settings>about phone>build number.... mine is NBD90W which is 7.0 security patch level 0ct. 5,2016)
doing a root tutorial that matches your build will prevent most if not all of the hiccups that can come from incompatibilities in roms that are more complex than a noobie rooter needs to know.
bhang
Does it work on 7.1.1 (N4F26I)?
Thanks!
x987z said:
Does it work on 7.1.1 (N4F26I)?
Thanks!
Click to expand...
Click to collapse
Works on every edition of android

Categories

Resources