So for fun I decided to try to build CyanogenMod (Vision) on my Mac w/Snow Leopard 10.6.5. (VMs? Who uses VMs?)
After some trial, error, and improvisation... it actually worked. A fresh, piping-hot CM 6.1 RC1 update.zip built right on my Macbook Pro. And it even installed and ran on my phone. Holy crap.
Too fun to keep to myself. So I decided to write up what I did, and the result was this guide that takes you through the steps of pulling, building, and installing your own version of CM for the T-Mobile G2 from source.
Obviously don't even consider doing this without permaroot, a g2, a nandroid backup of everything, and the willingness to fail a couple times.
Cheers.
Build CyanogenMod for Vision (Mac Edition)
Build CyanogenMod for Nexus One (Mac Edition)
Update: The instructions are confirmed! A 2nd person (rhcp) has gotten this to work, so I'm thinking the instructions are decent.
Another Update: Nexus One version available too.
I run a 2007 white macbook with intel processor. will give it a try
daveyboi said:
I run a 2007 white macbook with intel processor. will give it a try
Click to expand...
Click to collapse
Cool. One of the issues is that I had a bunch of stuff installed w/mac ports before I even started the build-- I don't know which of them might have been necessary but I didn't explicitly need to add because they weren't missing. So if you discover "oh, it's not building because xyz is missing", just add it to the list of required port packages.
The libX stuff came about in just that manner. The person who was testing for me had broken builds until he installed that. I'd already added it previously so I didn't experience the issue.
I think it's pretty awesome you wrote this up. All hobbyists should be willing to give this a try, IMO.
btw. the link on the wiki for macports,org comes up as a .com
daveyboi said:
btw. the link on the wiki for macports,org comes up as a .com
Click to expand...
Click to collapse
Fixed. Thx.
BTW-- one cool thing about building it yourself is you don't have to worry about gapps. All the Google Apps and even the T-Mobile Wifi Calling app transfers to your new ROM.
Success!
So I heard back from rhcp. The walkthrough worked to the end. He now has a full build and was able to get it on his phone.
If anyone is interested in trying this for a phone other than the vision, I might be able to port the instructions over for something else... shouldn't be too hard.
can someone write a guide or point me to a guide for win xp 64
sundar2012 said:
can someone write a guide or point me to a guide for win xp 64
Click to expand...
Click to collapse
Mac OS is Unixy enough to pull this off. It would be very difficult to do this directly under Windows--even building the ARM toolchain would be nontrivial.
If you are a Windows user, I recommend installing VirtualBox with an Ubuntu image and following the standard Android build process.
Templated it...
I made this a template so now things like the Nexus One build instructions are easy:
http://wiki.cyanogenmod.com/index.php?title=Compile_CyanogenMod_for_Passion_(Mac)
Yeps works great. Thanks bro. Been trying to do this since day 1
Sent from my T-Mobile G2 using XDA App
MODS,
Can this be sticky? I think it should be put other places too.
This is the first how-to to get a full building env setup on a Mac!
Glad it worked for ya. I have to apologize if the page kept ****ing up, but some jackwad interested individual kept moving everything around on the wiki and reformatting because he thinks it's more "aesthetic"... I think it makes it way harder to understand.
After a lot of back and forth and arguing, the page was frozen "the good way" for a week. But I'm worried that this penis interested person will mess with it as soon as he gets a chance.
And as i type this, RC1 is officially here!
Update: Hopefully the layout controversy has been resolved.
I ran into an error- any help?
No CM in the target directory???!!!
Code:
make: *** No rule to make target `vendor/htc/vision/proprietary/libganril.so', needed by `out/target/product/vision/system/lib/libganril.so'. Stop.
make: *** Waiting for unfinished jobs....
Notice file: device/htc/vision/libsensors/NOTICE -- out/target/product/vision/obj/NOTICE_FILES/src//system/lib/hw/sensors.vision.so.txt
here is the line in extract-files.sh that pulls it. I checked my phone, and I no gots!
Code:
adb pull /system/lib/libganril.so ../../../vendor/htc/$DEVICE/proprietary
and this is the output from extract-files.sh. I saw that there were a few other files that did not exist.
Code:
remote object '/system/app/MS-HTCVISION-KNT20-02.apk' does not exist
994 KB/s (42512 bytes in 0.041s)
1483 KB/s (34948 bytes in 0.023s)
855 KB/s (9700 bytes in 0.011s)
1386 KB/s (13884 bytes in 0.009s)
1376 KB/s (13900 bytes in 0.009s)
1567 KB/s (62636 bytes in 0.039s)
1778 KB/s (76168 bytes in 0.041s)
1267 KB/s (11490 bytes in 0.008s)
1653 KB/s (31858 bytes in 0.018s)
1304 KB/s (31858 bytes in 0.023s)
127 KB/s (513 bytes in 0.003s)
58 KB/s (288 bytes in 0.004s)
37 KB/s (186 bytes in 0.004s)
127 KB/s (499 bytes in 0.003s)
91 KB/s (459 bytes in 0.004s)
1445 KB/s (32768 bytes in 0.022s)
1337 KB/s (27340 bytes in 0.019s)
1657 KB/s (79784 bytes in 0.046s)
1853 KB/s (166956 bytes in 0.087s)
1924 KB/s (1866396 bytes in 0.947s)
1890 KB/s (210620 bytes in 0.108s)
1465 KB/s (17788 bytes in 0.011s)
1258 KB/s (13976 bytes in 0.010s)
1673 KB/s (81028 bytes in 0.047s)
1167 KB/s (9260 bytes in 0.007s)
576 KB/s (9268 bytes in 0.015s)
1672 KB/s (89372 bytes in 0.052s)
remote object '/system/lib/libganril.so' does not exist
1279 KB/s (18116 bytes in 0.013s)
1574 KB/s (38464 bytes in 0.023s)
1306 KB/s (13492 bytes in 0.010s)
994 KB/s (9300 bytes in 0.009s)
1937 KB/s (495580 bytes in 0.249s)
remote object '/system/lib/libkineto.so' does not exist
1597 KB/s (25900 bytes in 0.015s)
1343 KB/s (25972 bytes in 0.018s)
1875 KB/s (580140 bytes in 0.302s)
1760 KB/s (184640 bytes in 0.102s)
1226 KB/s (14540 bytes in 0.011s)
1830 KB/s (522216 bytes in 0.278s)
1383 KB/s (13928 bytes in 0.009s)
1634 KB/s (61308 bytes in 0.036s)
1557 KB/s (69704 bytes in 0.043s)
1750 KB/s (292888 bytes in 0.163s)
1933 KB/s (981868 bytes in 0.496s)
909 KB/s (5424 bytes in 0.005s)
remote object '/system/lib/librilswitch.so' does not exist
My G2 is unrooted and does not have the OTA updates installed, if that makes a difference. I followed the directions to a T, except I used a slightly different name for the sparseimage and had two beers while the source was downloading. My Mac also had a few of the requisite files installed already from other projects.
Thanks for taking the time to make the wiki!
This reference to "MS-HTCVISION-KNT20-02.apk" looks like a problem the missing OTA. I think that's the wifi-calling app, and I know Cyanogen added support to transfer the wifi-calling stuff over to CM 6.1.
So maybe try installing the OTA and then see if the files transfer. If it works, I'll add a note to the build instructions.
gee one said:
I ran into an error- any help?
and this is the output from extract-files.sh. I saw that there were a few other files that did not exist.
Code:
remote object '/system/app/MS-HTCVISION-KNT20-02.apk' does not exist
My G2 is unrooted and does not have the OTA updates installed, if that makes a difference.
Click to expand...
Click to collapse
fattire said:
This reference to "MS-HTCVISION-KNT20-02.apk" looks like a problem the missing OTA. I think that's the wifi-calling app, and I know Cyanogen added support to transfer the wifi-calling stuff over to CM 6.1.
So maybe try installing the OTA and then see if the files transfer. If it works, I'll add a note to the build instructions.
Click to expand...
Click to collapse
OK- it looks like I'll need another beer...
I flashed the OTA and confirmed that the missing files are now where they are suppose to be. Compiling takes almost as long as downloading the source, but now the homecooked CM-6.1.0-RC1-vision is hot and fresh!
I got my G2 on Monday and I didn't even know what a hacker was. Now, thanks to fattire, xda-developers, and CyanogenMod, now I is one!
I can't wait to cook me up some Donut rom for the G2!
gee one said:
I got my G2 on Monday and I didn't even know what a hacker was. Now, thanks to fattire, xda-developers, and CyanogenMod, now I is one!
Click to expand...
Click to collapse
Dude, you just made my day
I see that Cyanogen is requiring less and less from your phone with every new commit...
Gonna rebuild my stuff too right now. Can't wait for the new scheduler. Dunno if it will be better than brainfuck, but it's getting good reviews anyway.
BUMP.
Can a mod please stickie this? Thanks!
fattire said:
So for fun I decided to try to build CyanogenMod (Vision) on my Mac w/Snow Leopard 10.6.5. (VMs? Who uses VMs?)
After some trial, error, and improvisation... it actually worked. A fresh, piping-hot CM 6.1 RC1 update.zip built right on my Macbook Pro. And it even installed and ran on my phone. Holy crap.
Too fun to keep to myself. So I decided to write up what I did, and the result was this guide that takes you through the steps of pulling, building, and installing your own version of CM for the T-Mobile G2 from source.
Obviously don't even consider doing this without permaroot, a g2, a nandroid backup of everything, and the willingness to fail a couple times.
Cheers.
Build CyanogenMod for Vision (Mac Edition)
Build CyanogenMod for Nexus One (Mac Edition)
Update: The instructions are confirmed! A 2nd person (rhcp) has gotten this to work, so I'm thinking the instructions are decent.
Another Update: Nexus One version available too.
Click to expand...
Click to collapse
I'm finally running some homebrewed CM on my G2. At first, I had a few problems with force closing and bootloops. Apparently, I had a bad SD card. As soon as I switched to the stock one, CM6.1 started running straight and stable.
Awesome! That makes 4 known successes. I'd like to see if it works on N1. Having someone try it.
Related
Hi.
I've played short with amss.bin and changed 1 Byte somewhere in "useless" Text.
Multiloader seems to check this manipulation...
Any idea where in file is CRC, Hash or something like that?
Also any idea if RSA 2048 is activated for Bootloader or AMSS?
Best Regards
i have heard that in bada 1.2 roms its activated but the old ones...
Some packages include more then 2 files:
dbl.mbn
boot_loader.mbn
In T-Mobile Firmware I found also few ELF files...
decrypted_boot_loader.bin is decrypted with PSAS.
Best Regards
I think there are 3 Boot Loader.
We know only 2 files:
dbl.mbn----------------> human readable (find Text like Qualcomm)
boot_loader.mbn--------> encrypted (decrypt with PSAS for instance)
DBL------> Device Boot Loader
FSBL-----> Fail Safe Boot Loader
OSBL-----> OS Boot Loader
Check out Qualcomm manual in QPST... see Screenshots.
Check out above post from me... there are ELFs included...
Maybe start with:
BL3_univ_s.elf
If you wish Android porting.
If I'm wrong, please correct me.
Best Regards
And if wwe would dual-boot android then wich loader would we need to edit. and how would we disassemble it?
And if wwe would dual-boot android then wich loader would we need to edit. and how would we disassemble it?
Click to expand...
Click to collapse
As I saw on S8000 project it seems they "only" change boot_loader.mbn.
But it seems it was not encrypted.
This time on S8500 it is encrypted...
As we can not encrypt them, decrypt is not problem... also enough ELF files are floating around.
First Question is. How write not encrypted boot_loader.mbn to S8500 without killing the handset.
This is the very, very basic Question. Long time before """IDA"""...
So again.
RIFF Box JTAG could help to understand, if Security is low enough to write modified Bootloader back to handset.
All other things are dreams.
Best Regards
Edit 1.
But it could be, that dbl.mbn prevent modification of boot_loader.mbn.
Or other Checks are integrated to prevent easy Bootloader change.
For JTAG user... Is it possible to erase NAND from 0 to 20000 (first 2 MB).
Attention! Not best idea as much harder to write then... also with JTAG.
But is this area protected by something? RSA Keys?
Nand write protection?
Edit 2.
S8500 is 5 x bigger then S8000 boot_loader.mbn
300 KB against 1600 KB
So I'm pretty sure Samsung integrated more Security...
Hi All.
Now i playing with porting android to my s8500.
I see that the Korean m130k very similar to our S8500(shw-m120s),
see pics files from FCC site.
and now I'm looking for bootloader files for m130k.
Also, I have Riff box
@ oleg_k
Thank you very much for these interessting infos.
I will contact you later via PM as I have several Questions...
I found this:
http://www.gadgetfolder.com/samsung-galaxy-k-shw-m130k-android-smartphone.html
Best Regards
Adfree,
will be interesting to talk with you.
Regards
I've investigated JTAG dump...
First 4 MB in 2 GByte moviNAND looks like that:
Code:
000000-16BB0E Boot boot_loader.mbn (not encrypted)
16BB10-1BFF7F 337 KB 0000 (empty) part of Boot
1BFF80-1BFFFF ??? 128 Bytes (RSA ???)
1C0000-1FFFFF 256 KB FFFF (empty)
200000-244B27 DBL dbl.mbn
244B28-3FFFFF 1,7 MB FFFF (empty)
400000 AMSS amss.bin
Now I spent some time to find used boot_loader.mbn and dbl.mbn to be sure that not additional Data is written... this takes some time...
Edit:
In this Dump Version S8500+XX+JD9 is used. I hope I will find Firmware with Bootfiles for compare...
Edit 2.
S8500XXJD2.zip no Bootfiles
S8500XXJD3.zip no Bootfiles
S8500XXJD4.zip no Bootfiles
S8500XXJDA.zip no Bootfiles
S8500XXJDB.zip no Bootfiles
I found 4-5 packages with XXJDx in name... now I will download them all. Hopefully I find Bootfiles that matches S8500+XX+JD9
Edit 3.
Found only XXJDx without Bootfiles...
Last try for today is S8500XXJDZ.zip, but I have download problems... need more then 2 hours...
Good work adfree. You are great.
This seems more interesting than anothers ports.
Okay, I found in S8500XXJDZ.rar
S8500+XX+JD9
dbl from JTAG Dump is 100 % identical.
Last 1024 Bytes are not written into memory...
dumped DBL = dbl.mbn
But dumped boot_loader(.mbn) is with Changes... later more.
0-1FFFF identical
20000-??? long, long empty... FFFFFF
More infos will come later.
Best Regards
It seems much easier as I thought.
No private Data like IMEI... if not removed from JTAG Dump (first 4 MB before AMSS).
In Bootloader part is only once written Block with FF (empty). So
128 KB Block is empty.
boot_loader.mbn is split into 2 parts...
I will make JTAG template for XXJL2 as example.
This I can upload.
Best Regards
adfree said:
It seems much easier as I thought.
No private Data like IMEI... if not removed from JTAG Dump (first 4 MB before AMSS).
In Bootloader part is only once written Block with FF (empty). So
128 KB Block is empty.
boot_loader.mbn is split into 2 parts...
I will make JTAG template for XXJL2 as example.
This I can upload.
Best Regards
Click to expand...
Click to collapse
keep it up buddy.
Okay. Based on my knowledge and JTAG dump...
I have prepared template for JTAG based on XXJL BOOTFILES.
Last 1024 Bytes of decrypted files are NOT written into moviNAND, I cut them:
boot_loader.mbn_part2.bin
dbl.mbn_part2.bin
boot_loader.mbn_PART1 is filled with 1 Block FF (128 KB) at 0x20000
Result is 4 MB file... 0 - 0x400000... Bootarea before AMSS.
Position 1BFF80-1BFFFF looks really like RSA 1024...
Check first 16 Bytes of boot_loader.mbn_part2.bin
Maybe this is the MD5 Hash which should be in the Signature?
Maybe someone knows the Cert or public Key to decrypt the Signature...
XXJB6 has no Sigs...
Anyway.
Without Test if 0 - 0x400000 can replaced via JTAG, we have no progress.
Best Regards
ATTENTION! Please NOT use these files to flash with Multiloader!
You will brick your handset.
Edit.
Added S8500 XXJB6...
Added S8530 XXJK2
Hi adfree good work here!!
Sorry I can't help you, it's over my knowledge
Keep going dude
adfree said:
Last 1024 Bytes of decrypted files are NOT written into moviNAND
Click to expand...
Click to collapse
Just a correction here - the last 1024 are not encrypted in the same way as the rest of the file and they are in fact written, but to a different location
adfree said:
Position 1BFF80-1BFFFF looks really like RSA 1024...
Click to expand...
Click to collapse
I stand corrected if I'm looking at the wrong place, but it doesn't look much like a RSA key to me - it's not odd, so it's not a private exponent and MSB is not set, so it's not a modulus.
is there any easy task in this
i want to help but i am not a programmer
so what can i do????
Just a correction here - the last 1024 are not encrypted in the same way as the rest of the file and they are in fact written, but to a different location
Click to expand...
Click to collapse
Yes, interesting. Like an Log file/Flash history... if I search for tktoolver...
This is far after 500 MB...
I hope this is not relevant for Boot.
Position 1BFF80-1BFFFF looks really like RSA 1024...
Click to expand...
Click to collapse
I think this is the Signature... maybe. So boot_loader.mbn is signed by RSA 1024.
Only an idea, but I could be wrong. XXJB6 has not such 128 Byte Block.
There are also more different boot_loader.mbn possible.
Ehm, JE7 has different... called XX+JEE
I will compare few, but between JL2 and JDZ whole 128 Bytes differs...
I know this only from RSA 2048, where 256 Byte Signature for BenQ Qualcomm handsets...
Best Regards
At the moment I try to find matching Bootloader from S8530... for S8500+XX+JL2
Or other matching combination.
S8530XEJL2
S8530+XX+JK9
S8530XEJL4
S8530+XX+JK9
Maybe with S8530+XX+JL1 more luck...
I hope I will find combo, in same month. Maybe minor differences...
Best Regards
Edit.
Hmmmm, strange S8530 Bootloader most older then S8500...
S8530+XX+JK2
S8530+DD+JK3
S8530+XX+JK9
S8530+XX+JL1
Hello !
I found really nice app from samsung. Samsung video editor . http://www.youtube.com/watch?v=-dZSQkPdg2g
When I try to install this app but
C:\SDK>adb install "C:\video editor.apk"
1067 KB/s (11402403 bytes in 10.432s)
pkg: /data/local/tmp/video editor.apk
Failure [INSTALL_FAILED_MISSING_SHARED_LIBRARY]
I know where is the problem becouse i don't have samsung library.Can i install that library to my Desire?
Hello
So I'm like many in here i hard brick my Nokia x using swapper 2
So Phone total died for now and it's look like the only way to fix it by Nokia care or atf jtag (hardware flasher)
but i have seen on Nokia lumia forums They can fix it by editing the bootloader partition using HxD software
it's not that hard to fallow the tutorial but i don't think it's the same setups for our android Nokia
you can see the video in here with the setups
https://www.youtube.com/watch?v=3kuk4QQWwds
or in text here
https://docs.google.com/file/d/0B75VZ-4C1TxaOEdmbGp6RFdCVWc/edit
Now what we need a dev that can help as to do the same
it makes no sense every time one of as flash wrong room or install an app and he's phone gets hard brick will have to send he's phone to Nokia care to get fix ...
So guys Please Help i'm sure we can do this :good:
Thank You ...
murders10 said:
Hello
So I'm like many in here i hard brick my Nokia x using swapper 2
So Phone total died for now and it's look like the only way to fix it by Nokia care or atf jtag (hardware flasher)
but i have seen on Nokia lumia forums They can fix it by editing the bootloader partition using HxD software
it's not that hard to fallow the tutorial but i don't think it's the same setups for our android Nokia
you can see the video in here with the setups
or in text here
https://docs.google.com/file/d/0B75VZ-4C1TxaOEdmbGp6RFdCVWc/edit
Now what we need a dev that can help as to do the same
it makes no sense every time one of as flash wrong room or install an app and he's phone gets hard brick will have to send he's phone to Nokia care to get fix ...
So guys Please Help i'm sure we can do this :good:
Thank You ...
Click to expand...
Click to collapse
I'm looking into it right now,
Thank you Please Please keep as updated :highfive:
This can be seriously done. Give me time till tomorrow. I'm 70% sure this can work.
Dom3616 said:
This can be seriously done. Give me time till tomorrow. I'm 70% sure this can work.
Click to expand...
Click to collapse
Ok good lucky and thank you for your time :good:
i really can't wait :laugh::laugh:
murders10 said:
Ok good lucky and thank you for your time :good:
i really can't wait :laugh::laugh:
Click to expand...
Click to collapse
murders10 said:
Hello
So I'm like many in here i hard brick my Nokia x using swapper 2
So Phone total died for now and it's look like the only way to fix it by Nokia care or atf jtag (hardware flasher)
but i have seen on Nokia lumia forums They can fix it by editing the bootloader partition using HxD software
it's not that hard to fallow the tutorial but i don't think it's the same setups for our android Nokia
you can see the video in here with the setups
https://www.youtube.com/watch?v=3kuk4QQWwds
or in text here
https://docs.google.com/file/d/0B75VZ-4C1TxaOEdmbGp6RFdCVWc/edit
Now what we need a dev that can help as to do the same
it makes no sense every time one of as flash wrong room or install an app and he's phone gets hard brick will have to send he's phone to Nokia care to get fix ...
So guys Please Help i'm sure we can do this :good:
Thank You ...
Click to expand...
Click to collapse
I want you both to goto this guide: https://docs.google.com/file/d/0B75VZ-4C1TxaOEdmbGp6RFdCVWc/edit
Charge your Nokia X for some time.
Then follow steps 3 and 4 from the guide ONLY. And see if you are able to accomplish that. If yes, report back.
---------- Post added at 06:21 AM ---------- Previous post was at 06:20 AM ----------
Have you guys followed this tutorial? http://forum.xda-developers.com/showthread.php?t=2666410
Dom3616 said:
I want you both to goto this guide: https://docs.google.com/file/d/0B75VZ-4C1TxaOEdmbGp6RFdCVWc/edit
Charge your Nokia X for some time.
Then follow steps 3 and 4 from the guide ONLY. And see if you are able to accomplish that. If yes, report back.
---------- Post added at 06:21 AM ---------- Previous post was at 06:20 AM ----------
Have you guys followed this tutorial? http://forum.xda-developers.com/showthread.php?t=2666410
Click to expand...
Click to collapse
Hi
i did follow step 3 and 4 and i did accomplished to read the disk using HxD
about the second tutorial i already treed that after my phone bricks but Nokia care dos not detect my phone only windows do as Disk and ask me to format the partition
thank you
murders10 said:
Hi
i did follow step 3 and 4 and i did accomplished to read the disk using HxD
about the second tutorial i already treed that after my phone bricks but Nokia care dos not detect my phone only windows do as Disk and ask me to format the partition
thank you
Click to expand...
Click to collapse
Okay, then download this file: http://nds2.fds-fire.nokia.com/fds_fire/1402/1312/7339526780/92B5C621_RM980_10.0.3_oemsbl.mbn
Then, option this in HxD and copy it to the place where the guide tells you to. Basically, follow the entire guide completely but use this file instead of the one in that guide.
Again, this is only circumstantial so don't get your hopes up.
Dom3616 said:
Okay, then download this file: http://nds2.fds-fire.nokia.com/fds_fire/1402/1312/7339526780/92B5C621_RM980_10.0.3_oemsbl.mbn
Then, option this in HxD and copy it to the place where the guide tells you to. Basically, follow the entire guide completely but use this file instead of the one in that guide.
Again, this is only circumstantial so don't get your hopes up.
Click to expand...
Click to collapse
i did follow the guide step by step and i used the oemsbl.mbn but it didn't work
same thing windows only detect the phone as a disk thats all.
murders10 said:
i did follow the guide step by step and i used the oemsbl.mbn but it didn't work
same thing windows only detect the phone as a disk thats all.
Click to expand...
Click to collapse
Then I can say that this is hard luck as the partition table might be different on Lumia than Nokia X. Sorry folks.
Dom3616 said:
Then I can say that this is hard luck as the partition table might be different on Lumia than Nokia X. Sorry folks.
Click to expand...
Click to collapse
we just need the right sector
lets just wait for someone with better Knowledge
Thank you Dom
murders10 said:
we just need the right sector
lets just wait for someone with better Knowledge
Thank you Dom
Click to expand...
Click to collapse
Yes. And we also need to know which BL file to flash.
Did anyone figure it out. Just formatted my emmc memory. My NX does not boot in recovery or boot loader.it doesn't even show the Nokia logo. It just vibrates
KenyanDroid said:
Did anyone figure it out. Just formatted my emmc memory. My NX does not boot in recovery or boot loader.it doesn't even show the Nokia logo. It just vibrates
Click to expand...
Click to collapse
Sorry but No
only Nokia care or atf jtag flasher can fix this for now
lets hope for one of the dev find a way like they did with the lumia and Samsung For the Lumia they use the hex edit to fix it and for the samsung thy made the sd card bootable to flash the bootloader partition back
It might help.....
Hi every one i found this partition table of my bricked nokia x using gdisk command on linux,.
Code:
Number Start (sector) End (sector) Size Code Name
1 1 40 20.0 KiB 0700 Linux/Windows data
2 41 540 250.0 KiB 0700 Linux/Windows data
3 541 102940 50.0 MiB 0700 Linux/Windows data
5 131072 135167 2.0 MiB 0700 Linux/Windows data
6 135168 141311 3.0 MiB 0700 Linux/Windows data
7 141312 147455 3.0 MiB 0700 Linux/Windows data
8 147456 153599 3.0 MiB 0700 Linux/Windows data
9 153600 157695 2.0 MiB 0700 Linux/Windows data
10 157696 165887 4.0 MiB 0700 Linux/Windows data
11 165888 167935 1024.0 KiB 0700 Linux/Windows data
12 167936 169471 768.0 KiB 0700 Linux/Windows data
13 169472 175615 3.0 MiB 0700 Linux/Windows data
14 175616 202767 13.3 MiB 0700 Linux/Windows data
15 202768 223247 10.0 MiB 0700 Linux/Windows data
16 223248 243727 10.0 MiB 0700 Linux/Windows data
17 243728 270879 13.3 MiB 0700 Linux/Windows data
18 270880 1212959 460.0 MiB 0700 Linux/Windows data
19 1212960 1417759 100.0 MiB 0700 Linux/Windows data
20 1417760 1417799 20.0 KiB 0700 Linux/Windows data
21 1417800 3875399 1.2 GiB 0700 Linux/Windows data
22 3875400 6615623 1.3 GiB 0700 Linux/Windows data
23 6615624 6697543 40.0 MiB 0700 Linux/Windows data
24 6697544 6718023 10.0 MiB 0700 Linux/Windows data
25 6718024 7516743 390.0 MiB 0700 Linux/Windows data
26 7516744 7634942 57.7 MiB 0700 Linux/Windows data
The only problem is the name of the partition.If someone used gdisk in their working nokia x then we might get the name of the partition table.
Hello
I have a SIM unlocked Samsung Galaxy Note 3 Neo SM-N7505 here in Germany. I use Ubuntu OS and have installed Heimdall to do the root but unsure of how to repackage the data in the firmware .zip I got here
http://www.sammobile.com/firmwares/database/SM-N7505/DBT/
I extracted this but it seems that N7505XXUCNG5_N7505DBTCNG1_N7505XXUCNG2_HOME.tar.md5 is a Odin type of update.
Can someone point me to where I can find the Firmware below that I can use with Heimdall or help me convert the one I have?
UPDATE:
Read my reply below or above this one.
Firmware for GALAXY Note 3 Neo LTE SM-N7505
Model SM-N7505
Model name GALAXY Note 3 Neo LTE
Country Germany
Version Android 4.4.2
Product code DBT
PDA N7505XXUCNG5
CSC N7505DBTCNG1
Still await a helpful persons support...
I was able to Odin flash it , but I still am wanting a linux/unix way to admin my firmware or ROMs. Any help would be awsome.
Note 3 neo forum is here: https://forum.xda-developers.com/note-3-neo
Did you try flashing cfautoroot with Heimdall?
https://autoroot.chainfire.eu
Re: Still await a helpful persons support...
audit13 said:
Note 3 neo forum is here: https://forum.xda-developers.com/note-3-neo
Did you try flashing cfautoroot with Heimdall?
https://autoroot.chainfire.eu
Click to expand...
Click to collapse
I am not fully able to. Most of them will not work. I download it. I am able to hook up my phone all good ready to go. Can copy and make a PITT file of my phones drive layout. All systems go. As soon as I load the new ROM or Firmware to root the phone. I get a error that either the file is not compatable with Heimdall or I get this file is missing the Android Meta xml Heimdall needs for setting up the permissions and configurations.
It really gets me since I am pretty technical and write code i am at a loss why this file is always missing. Why fail to put a file in that is that important? Then you read on that and find 10,000 ways to write one. Alas not one are specific and if they are so easy to whip up one yourself why dont any of the 10,000 simply write one and spend their time teaching how to write hard scripts and code. Also not B*ching just really tired of the same old various types of info sprinkled with vauge and unclear steps or actual files to use as guides.
When I write a tutorial or a walkthrough its very clear. When I read most of the rooting or dealing with Heimdall and phones its like trying to locate that ring Frodo sought-after for so long.
I really appreciated that you responded. If you can maybe help me it would be great if I located a way to root my phone without a computer at all. I really think since everyone pretty much can root or unlock the damn things the phone would just have a option with a popup that you agree voids the warranty and poof its rooted...
lol
Thanks for taking time to message me!
:good:
Scott
Unfortunately, I do not use Linux so I am not sure what else to suggest other than possibly loading a temporary Windows installation onto your computer to flash cfautoroot via Odin.
Hi ScottsDesk
In the end, did you reach to root your phone from Ubuntu ? This is exactly what I want to do : when I've understood which will be the first way I'll choose to use a free'd phone, I want to walk this path with Linux. I can't understand why all the guys here being fans of free devices can even think to use Windows to gain control over their android : it is a shame (I must admit I'm a 0-skilled dev, so I can even allow myself to find strange there is so much Java therein Android ).
But ATM, I don't even know if I'll use CF-auto-root or if there exists a custom ROM that is running bug-free our device after days and days parsing this forum. The sad thing is I don't feel skilled enough to dig in the most serious solution (ChainFire's abandonned Unofficial CM12.1 for SN-M7505) to see if NFC is still really KO (ATM I have to remember some reported bugs have easy workarounds : lockscreen lag : disable Aquarell &/| wavelets effect and lowen swappiness from 130 to something around 50 (I'd try even far less, like on SSDs), and a delay in video recording sound : disable the "Google OK" thing).
I hope you'll read this
PS : it seem heimdall has what what we need (--no-reboot argument to follow what the guys say at some point to not reboot, instead remove battery).
I just gave try, just to see, but it fails and don't know what yet :
Code:
sudo heimdall print-pit --verbose
[sudo] password for me:
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
length: 18
device class: 2
S/N: 0
VID:PID: 04E8:685D
bcdDevice: 021B
iMan:iProd:iSer: 1:2:0
nb confs: 1
interface[0].altsetting[0]: num endpoints = 1
Class.SubClass.Protocol: 02.02.01
endpoint[0].address: 83
max packet size: 0010
polling interval: 09
interface[1].altsetting[0]: num endpoints = 2
Class.SubClass.Protocol: 0A.00.00
endpoint[0].address: 81
max packet size: 0200
polling interval: 00
endpoint[1].address: 02
max packet size: 0200
polling interval: 00
Claiming interface...
Setting up interface...
libusbx: error [op_set_interface] setintf failed error -1 errno 71
ERROR: Setting up interface failed!
Releasing device interface...
Also, did you understand this strange advice ? : some advise to make a backup (boot.img above all) before we do anything else : but I booted the phone in recovery mode and I can't see nandroid backup option...
Hello all,
I acquired this AT&T J2 Core Plus that was google frp locked etc etc and I was able to only find the COMBINATION ROM, but I have yet to find the stock firmware. I think sammobile was the only place that had it, but at 15 kb/s that would take forever..... can anybody help me out and upload the firmware to their drive account or androidfilehost or even be nice enough to PM me their sammobile info so I could fix this phone?
Thank you!
Stock firmware doesn't really download at 15 kb/s, they just put that there to make you want to pay, I guess.
Just create a free account and downloads usually go at 600 kb/s or more, depending on your connection.