Related
hello everyone,
Must say without alot of your great posts and walkthroughs i wouldn't of even considered the wicked things my little Gio can do. But i have seem to always have 1 problems when flashing my cell.
I get a "No Service" after 6 hours and can never get it to pick up my Virgin Sim card. I have tried GioPro 1.2 to 1.6, CyanogenMod 7 and 9 and even some Europe firmwares that are supposedly work with it.
So i am assuming that alot of these firmswares/roms don't work with Canada services or phones/areas or is this a common glitch in custom roms. Any help or direction on fixing a issue like this would be more then amazing right about now.
thank you all for your time
Vaughn
after flashing gioprio, it also flashed your baseband. flash a stock rom based for the m model, or flash a baseband only, wich is for the M mode, and you're fine
voetbalremco said:
after flashing gioprio, it also flashed your baseband. flash a stock rom based for the m model, or flash a baseband only, wich is for the M mode, and you're fine
Click to expand...
Click to collapse
i have never thought of that, thank you so much. I will report back with my results!
ok this is where you guys start to hate me, tried figure out where to locate a stock baseband and i got a one package for giopro 1.0 (GioPro_v1.6.tar) and my stock firmware for bell/virgin phone (GT-S5660M_BMC_S5660MUGKG3_S5660MUGKG3_S5660MBMCKG3.tar) and finally my GIO_v1.0.ops.
but where about do i locate a stock baseband for the 5660m or am i replacing one files from the stock firmware (GT-S5660M_BMC_S5660MUGKG3_S5660MUGKG3_S5660MBMCKG3.tar) to the GioPro custom (GioPro_v1.6.tar),
i hate to be that guy but i been battling this for a few weeks.
voetbalremco said:
after flashing gioprio, it also flashed your baseband. flash a stock rom based for the m model, or flash a baseband only, wich is for the M mode, and you're fine
Click to expand...
Click to collapse
Can you flash a ROM to get European 3G frequencies with a Canadian phone?
I could compile a .tar.md5 of the S5660MUGKG3 Baseband only if you want?
(Flash it through Odin)
Because I have a GT-S5660M model also, so I always keep a backup of Stock Rom in my PC.
SUCESS! for now that is.
I was able to create a AMSS only .tar for flashing using Cygwin Terminal and this command
cd /cygdrive/c/baseband
tar -xvf S5660MUGKG3_S5660MUGKG3_S5660MBMCKG3_home.tar amss
tar -H ustar -c amss > S5660M AMSS.tar
Click to expand...
Click to collapse
then was able to flash just the one package, seems to have left the other parts of the GioPro Rom installed.
Vaughn Whiskey said:
SUCESS! for now that is.
I was able to create a AMSS only .tar for flashing using Cygwin Terminal and this command
then was able to flash just the one package, seems to have left the other parts of the GioPro Rom installed.
Click to expand...
Click to collapse
Yup! What I was going to do!
Peteragent5 said:
I could compile a .tar.md5 of the S5660MUGKG3 Baseband only if you want?
(Flash it through Odin)
Because I have a GT-S5660M model also, so I always keep a backup of Stock Rom in my PC.
Click to expand...
Click to collapse
Can this method be used to enable European 3G frequencies on the Gio?
Was having the same issues as OP - then realized I incorrectly flashed to 2.3.6 (for the 5660), now I'm trying to get back to stock 5660M 2.3.4 after downloading the S5660MUGKG3_S5660MUGKG3_S5660MBMCKG3 hotfile from droidangel - problem being it isn't a one file md5/tar... the rar contains like 9 files, image files and rfs. I've attached the rar contents.
View attachment 1132111
How do I use these files?? If it's not possible, does anyone have a lead on a one file for the stock 5660M 2.3.4 from Canada?
fyi, unrooted, unlocked
Thanks in advance
sob.... thought I had figured it out, went to samfirmware, got excited - their file was a different size from the droidangel...unfortunately same garbage, same list of image & rfs files instead of a single md5/tar
---------- Post added at 10:16 PM ---------- Previous post was at 09:53 PM ----------
what a jackass I am
I'm only posting this because I have a low level of shame and I noticed a few others while googling who were having the same problem as me..hopefully this helps them
the solution and why i'm a jackass = i was unraring the tar file..hence the contents (image, rfs etc) which were not useable by odin
i was selecting the wrong file... trying to use odin to select one of the files inside the tar... after uncompressing the tar....
brutal... anyway, hopefully this helps others
Help!
Okay guys, Heres my problem... And I need guidelines because im new to all this. I installed the fake ics on my phone and because it started to limit what I could do on my phone I decided to go back to android 2.2. I used odin to go back but I think i selected the wrong Rom for my network and where I live. I live in Canada and I use Virgin mobile as my network. Now that I got Android 2.2 back I never get any network! How do I flash a new Baseband Version? and Where do I get the Baseband version for Bell/Virgin? Also If you could give me the download for The Official Android 2.2 rom and not a custom one.. it would be nice =)
It's going to be 2.3 (Gingerbread) and not 2.2 (Froyo) that you'll want to install.
There have been multiple posts and you should just have used the search function, then asked whatever questions you might have had left.
Get the MUGK3 stock ROM from here or samfirmware, flash it with Odin.
Again, simple, beginner stuff for which there are multiple tutorials. The search function is your friend.
Darkshado said:
It's going to be 2.3 (Gingerbread) and not 2.2 (Froyo) that you'll want to install.
There have been multiple posts and you should just have used the search function, then asked whatever questions you might have had left.
Get the MUGK3 stock ROM from here or samfirmware, flash it with Odin.
Again, simple, beginner stuff for which there are multiple tutorials. The search function is your friend.
Click to expand...
Click to collapse
So I found one on samfirmware but its MUGKG3? Is that fine or different? and where on xda forums can i download the 2.3 gingerbread non custom for canada ( bell)?
Sobey2012 said:
So I found one on samfirmware but its MUGKG3? Is that fine or different? and where on xda forums can i download the 2.3 gingerbread non custom for canada ( bell)?
Click to expand...
Click to collapse
Yeah it's that --> MUGKG3
If you are on EXT4, don't use it with ODIN. It'll bootloop your phone.
It's fine if you're on a RFS filesystem
Peteragent5 said:
Yeah it's that --> MUGKG3
If you are on EXT4, don't use it with ODIN. It'll bootloop your phone.
It's fine if you're on a RFS filesystem
Click to expand...
Click to collapse
Lol Im new to android, Whats ext4 and RFS? And What else instead of odin can do it with? also I have the GT-S5660, NOT THE GT-S5660M so does it make huge difference?
Sobey, I got your message, but really this is the sort of discussion best kept in the thread. If you got your phone from VMC, it's a 5660M. In fact, a GT-S5660 would not work with Virgin at all.
Peteragent5: He could flash the whole stock MUGKG3 ROM with Odin and reformat /cache and /data with the stock recovery.
Darkshado said:
Sobey, I got your message, but really this is the sort of discussion best kept in the thread. If you got your phone from VMC, it's a 5660M. In fact, a GT-S5660 would not work with Virgin at all.
Peteragent5: He could flash the whole stock MUGKG3 ROM with Odin and reformat /cache and /data with the stock recovery.
Click to expand...
Click to collapse
But in About Phone it says GT-S5660 but ill trust your word. So I should download the Mugkg3 rom and use odin to get it into my phone? and do empty cache and data? Okay ill try this now and let you know if it works. I need your help with one more thing, Last time i used odin I followed a tutorial for where to put each file in which odin slot such as BOOT, PHONE, PDA, etc etc. Can you tell me which file needs to go in which slot? Or is it one package and I just click open package? Sorry man for asking to many questions but itll really help. Also I cant find the ops file!
Peteragent5 said:
Yeah it's that --> MUGKG3
If you are on EXT4, don't use it with ODIN. It'll bootloop your phone.
It's fine if you're on a RFS filesystem
Click to expand...
Click to collapse
doesnt that mean after installing anyvustom rom that uses ext4 you cant use odin any more?!
definetely isnt true, otherwise you could never use odin any moreafter rom flash
Sobey2012 said:
But in About Phone it says GT-S5660 but ill trust your word. So I should download the Mugkg3 rom and use odin to get it into my phone? and do empty cache and data? Okay ill try this now and let you know if it works. I need your help with one more thing, Last time i used odin I followed a tutorial for where to put each file in which odin slot such as BOOT, PHONE, PDA, etc etc. Can you tell me which file needs to go in which slot? Or is it one package and I just click open package? Sorry man for asking to many questions but itll really help. Also I cant find the ops file!
Click to expand...
Click to collapse
You could make the "About Phone" model string say anything by editing the proper file. As I've said before: if your Gio worked with Virgin Mobile Canada at all, it a 5660M. The Europe/Asia 5660 doesn't have the proper HSPA bands.
Look up the differences between the different Gio models. Now. Use the search function.
There's also one or two tutorial threads here with both Odin 4.42 and the GIO_v1.0.ops file linked.
The stock rooted ROM I uploaded a while ago, as well as the OEM one from samfirmware.com are usually the "one package" kind. If you're unsure, open the tar (or tar.md5) file with a proper archiving program (7-Zip works well and is free open-source) and have a look. There should be many files, including but not limited to: amss, arm11boot, mibib, oemsbl, qcsbl, boot.img, recovery.img and system.rfs.
Quick recap:
Flash the MUGK3 ROM with Odin.
If the phone bootloops, got in the stock recovery and do a factory reset, in other words, reformat the partitions.
Done!
UPDATED 2013/11/21: Added more warnings.
This is for US SGH-T999 devices ONLY. If there is ANY letter after your model such as 'L' or 'V' DO NOT FLASH THIS OR YOU WILL DEFINITELY BRICK YOUR PHONE! For SGH-T999V VLDLD1 firmware, please see this thread: http://forum.xda-developers.com/showthread.php?p=41701398
DO NOT flash this if you are running latest 4.3 (*MJC) firmware. It WILL brick your device. Currently there is NO way to downgrade from MJC firmware without a brick due to the Knox security stuff added to that firmware release.
Currently I don't have a SGH-T999L firmware update script, sorry. If someone would like to work with me on guinea pigging it and has heimdall installed, PM me and we'll get it done in no time.
This is the latest firmware update for US T-Mobile (SGH-T999) that flashes the UVDMD5 radio and bootloader with a convenient update.zip. Flashing it on anything other than the US SGH-T999 is strongly not advisable. It will likely brick your phone. It CANNOT be used on the Canadian T999V variant.
This script flashes all of the firmware that comes with the UVDMD5 OTA -- this upgrades the firmware as if you had just flashed the whole package through Odin, but without actually touching system, recovery, kernel, etc. There are two versions of the script -- one just does the bootloader+firmware, the other does bootloader+firmware+modem.
What are these firmware files?
rpm.mbn - Resources and Power Manager
sbl2.mbn - Part of Secondary Bootloader
sbl3.mbn - Part of Secondary Bootloader
aboot.mbn - AP Bootloader
tz.mbn - Trust Zone
NON-HLOS.bin - Modem / Radio
Why do I want this?
If your phone has old enough firmware, newer CM10.1 builds will no longer install on it. It is unknown if updating to UVDMD5 from UVDLJC, for example, has any noticeable positive effects. No known negative effects have been reported and the Odin method ends up upgrading all this stuff anyway.
Note that you can flash the above files via heimdall but this updater below is handy as you don't need heimdall, download mode, etc. All you really have to do is flash it in recovery.
Flashable UVDMD5 Bootloader / Firmware / Modem update.zip: https://dl.dropboxusercontent.com/u/173554095/T999 Devel/T999_UVDMD5_firmware_v4.zip (md5: d040ea4193234cbe9a36f95ffa780086)
Above flashable update without modem: https://dl.dropboxusercontent.com/u/173554095/T999 Devel/T999_UVDMD5_noradio_v4.zip (md5: 4c4aa065ee7c86dccea92ec7856a7af4)
OLDER UVDLJC Firmware update.zip script (w/modem) -- only if you specifically need it for some reason.: https://dl.dropboxusercontent.com/u/173554095/T999 Devel/T999UVDLJC_firmware.zip (md5: 537b69ec54ce6a3580a9c56ca379e72c)
Instructions:
(1) Put this .zip file on the root of your sdcard.
(2) Reboot to recovery
(3) Choose .zip file from sdcard and select this file and flash it.
(4) Reboot and you're done. I didn't find any wiping of any kind necessary.
NOTE: If you plan to flash anything else, please at least reboot recovery or it won't pick up the bootloader change.
Changes:
v1: Initial release. Modified someone's UVDLJC firmware update.zip script to update to UVDMD5.
v2: Removed certs from a previous update.zip that could've been causing signature verification errors with some recoveries.
v3: Updated Edify script courtesy of @Aerowinder
v4: Corrected a derp in package_extract_dir() (my fault) that prevented v3 from working at all. I've since tested v4 personally and verified it.
Many thanks to whomever put together the original update.zip and to Khaytsus and invisiblek for pointing me in the right direction. Also many thanks to all who've tested it and provided feedback. There is no greater enjoyment than in helping people.
I've also hacked together a firmware backup script that works for both T999 and T999V: http://forum.xda-developers.com/showthread.php?p=41548550
DISCLAIMER: I do not take any credit for this stuff, I just put it together. I am not liable for your device if you break it, etc etc. READ THE WARNINGS BEFORE PROCEEDING.
Trying crazy stuff like this freaks me out.....but I wonder if anyone has tried it tho!
Sent from my SGH-T999 using Tapatalk 2
I tried the new .zip you made and it worked. Flashed and now have newest bootloader.
Sent from my SGH-T999 using Tapatalk 2
re: bootloader
OhhCoreey said:
I tried the new .zip you made and it worked. Flashed and now have newest bootloader.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
What's the point of having the NEWEST bootloader, how is it any better than a 1 year old bootloader?
Misterjunky said:
What's the point of having the NEWEST bootloader, how is it any better than a 1 year old bootloader?
Click to expand...
Click to collapse
You need the new bootloader to flash new CM10.1 nightlies. Cyanogen posted it.
Sent from my SGH-T999 using Tapatalk 2
itzsmokey said:
Trying crazy stuff like this freaks me out.....but I wonder if anyone has tried it tho!
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
You can always try the original UVDLJC I linked that will work with latest nightlies. I used my own update.zip file that I posted here and my phone works fine now using the latest UVDMD5 full firmware (incl. radio).
Oh yeah -- both these update.zips contain the radio so if you don't want the MD5 or LJC radio, better update it to something else afterward.
You can check my work, read the META-INF/com/google/android/updater-script file. You can dd all those mmcblk0pX partitions to backup files, too. Maybe I'll make a firmware back up script while I'm at it.
There's nothing really scary about this -- you get these exact same files flashed to your phone in the same place if you use the UVDMD5 stuff in Odin, except you'll probably overwrite your recovery and system as well and spend extra time restoring it.
Steps for using it, in case this is unclear:
(1) Put this .zip file on the root of your sdcard.
(2) Reboot to recovery
(3) Choose .zip file from sdcard and select this file and flash it.
(4) Reboot and you're done. I didn't find any wiping of any kind necessary.
I'm running cm10.1-20130513-d2tmo with imoseyeon's leankernel 5.9 on my SGH-T999. Haven't upgraded to the newer nightly yet as nothing looked interesting enough in the changelog.
Oh and:
Code:
[email protected]:/ # getprop ro.bootloader
T999UVDMD5
OhhCoreey said:
You need the new bootloader to flash new CM10.1 nightlies. Cyanogen posted it.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
ok, thanks now I know I don't need it because I just am not a fan of the CM10/AOKP/AOSP roms.
Good luck with it.
Misterjunky said:
ok, thanks now I know I don't need it because I just am not a fan of the CM10/AOKP/AOSP roms.
Good luck with it.
Click to expand...
Click to collapse
FWIW, I'm getting much better radio performance after switching to UVDMD5 modem. YMMV but I'm definitely getting better up/down and stronger signal indoor where I had terrible signal. But you you can just flash the modem separately from this .zip -- there's a thread in the d2tmo dev forum with the modems and their recovery flashable update.zip files.
The OP of said thread also undertook a project to allow people to post on some shared Google Map what modem they're using and their results, so you might want to look into what works best for your area too if you care about getting better signal or speed.
Cyanogen pushed the assert for newer bootloaders in the 5/14 nightly I believe as there were lots of people complaining about random crashes and supposedly much fewer reports on newer firmwares. I actually wasn't having this problem very much with LeanKernel, though it did seem to be happening like crazy at some point.
I actually didn't know about all the bootloader versions for our phones until today, it was interesting diving into all this stuff. I discovered at the beginning I was running with the same firmware the device had shipped with and if Cyanogen hadn't pushed for the newer bootloaders, I might have let things be. But since he pushed for it, I decided might as well have the latest stuff.
Cheers
mnasledov said:
You can always try the original UVDLJC I linked that will work with latest nightlies. I used my own update.zip file that I posted here and my phone works fine now using the latest UVDMD5 full firmware (incl. radio).
Oh yeah -- both these update.zips contain the radio so if you don't want the MD5 or LJC radio, better update it to something else afterward.
You can check my work, read the META-INF/com/google/android/updater-script file. You can dd all those mmcblk0pX partitions to backup files, too. Maybe I'll make a firmware back up script while I'm at it.
There's nothing really scary about this -- you get these exact same files flashed to your phone in the same place if you use the UVDMD5 stuff in Odin, except you'll probably overwrite your recovery and system as well and spend extra time restoring it.
Steps for using it, in case this is unclear:
(1) Put this .zip file on the root of your sdcard.
(2) Reboot to recovery
(3) Choose .zip file from sdcard and select this file and flash it.
(4) Reboot and you're done. I didn't find any wiping of any kind necessary.
I'm running cm10.1-20130513-d2tmo with imoseyeon's leankernel 5.9 on my SGH-T999. Haven't upgraded to the newer nightly yet as nothing looked interesting enough in the changelog.
Oh and:
Code:
[email protected]:/ # getprop ro.bootloader
T999UVDMD5
Click to expand...
Click to collapse
Seen this after I flashed it.....it works perfect, I did a clean install just to have things fresh.
Sent from my SGH-T999 using Tapatalk 2
I don't know if I have a newer bootloader or not but flashed cm 10.1 and it runned perfect how do I know if I have it.
mnasledov said:
You can always try the original UVDLJC I linked that will work with latest nightlies. I used my own update.zip file that I posted here and my phone works fine now using the latest UVDMD5 full firmware (incl. radio).
Oh yeah -- both these update.zips contain the radio so if you don't want the MD5 or LJC radio, better update it to something else afterward.
You can check my work, read the META-INF/com/google/android/updater-script file. You can dd all those mmcblk0pX partitions to backup files, too. Maybe I'll make a firmware back up script while I'm at it.
There's nothing really scary about this -- you get these exact same files flashed to your phone in the same place if you use the UVDMD5 stuff in Odin, except you'll probably overwrite your recovery and system as well and spend extra time restoring it.
Steps for using it, in case this is unclear:
(1) Put this .zip file on the root of your sdcard.
(2) Reboot to recovery
(3) Choose .zip file from sdcard and select this file and flash it.
(4) Reboot and you're done. I didn't find any wiping of any kind necessary.
I'm running cm10.1-20130513-d2tmo with imoseyeon's leankernel 5.9 on my SGH-T999. Haven't upgraded to the newer nightly yet as nothing looked interesting enough in the changelog.
Oh and:
Code:
[email protected]:/ # getprop ro.bootloader
T999UVDMD5
Click to expand...
Click to collapse
NM
Sent from my SGH-T999 using xda app-developers app
I thought about making one of these. The only reason I didn't is because I don't know how Odin is working.
If it is just using an equivalent to dd, then why do the filenames have different extensions? Why do they have extensions at all? WTB Odin source code.
Aerowinder said:
I thought about making one of these. The only reason I didn't is because I don't know how Odin is working.
If it is just using an equivalent to dd, then why do the filenames have different extensions? Why do they have extensions at all? WTB Odin source code.
Click to expand...
Click to collapse
It is just DD which is what basically Odin would do anyway. The filenames are irrelevant. It's what data goes to which mmcblk0 partition. The file names are what they are as they are taken from the T999 UVDMD5 Odin .zip and for clarity. Why would I rename aboot.mbn to some random file name?
Just run heimdall print-pit some day and you can see how your eMMC is partitioned and what goes where. I could've flashed all these files with heimdall using the correct named partition identifiers rather than numeric identifiers, but I found it more convenient to make a flashable update.zip.
Update however you want, but as someone who doesn't use Windows and doesn't like screwing around with heimdall / Download Mode much, just dd'ing the files to the correct partitions was the most elegant solution I could find.
Nice work!
I don't know if you just copied the other one, but the comments in the script are great, it's easy to tell what's what. I may try to make one of these that doesn't flash the system bits, so the folks running CM10 that just want the latest nightly can just flash a zip and carry on instead of asking a billion questions. I think that means only including the aboot, rpm, tz, and modem pieces, right? The sbl ones aren't needed if you want to stay with CM.
mondokat said:
I don't know if you just copied the other one, but the comments in the script are great, it's easy to tell what's what. I may try to make one of these that doesn't flash the system bits, so the folks running CM10 that just want the latest nightly can just flash a zip and carry on instead of asking a billion questions. I think that means only including the aboot, rpm, tz, and modem pieces, right? The sbl ones aren't needed if you want to stay with CM.
Click to expand...
Click to collapse
Thanks though I can't take credit for writing the script. I just extracted the UVDLJC firmware updater script written by another dev, substituted the UVDMD5 files in, updated the script with the new SHA1 sums, and re-zipped it, thus making a flashable UVDMD5 updater script.
It does not flash the system -- it just flashes aboot, rpm, tz, modem, and some sbl files. I run CM10.1 and was able to just flash this without killing any of my system stuff. Recovery, system, kernel, etc. are all preserved. You can make a backup (as anyone should anyway), but you shouldn't need to do any restore or even a cache wipe after flashing either UVDLJC or UVDMD5 updater since it's just bootloader, modem, and some other pieces unrelated to system/kernel.
In retrospect, it would've been trivial to extend the script to create backups of the current partitions on the phone. In fact, I'm pondering a "firmware flasher" script that gives one a menu of different firmwares and ability to backup/restore for fun. Then again, I've never touched these firmware bits until Cyanogen necessitated a newer bootloader in CM10.1.
Anyway, I modified this script for myself at first and I had spent the whole day trying to research the topic without too much info. I saw S3s from other carriers had update ZIPs and was frustrated at the lack of one for d2tmo. After testing it on myself successfully and realizing how safe it is, I decided to just release it so people can benefit from it by upgrading their firmware or ripping it apart and learning how it works and/or making it better.
On a side note, do you know what the SBL files are for? You say they're not needed for CM but I ended up updating them anyway (as this script does) and it didn't break anything with CM. I figured it was best practice to just update them, but I could be wrong. Any insight on this would be greatly appreciated as I couldn't find much info.
Thanks for putting this together it has made a huge difference for me with the new radio I have gained 7 mb down and 3 mb up from this I'm running jovy stockoaroma rom right now :thumbup: great idea I was going to odin so I could update that now I don't have to...
Sent from my SGH-T999 using Tapatalk 2
How can you check what bootloader you have?
Sent from my SGH-T999 using xda premium
mnasledov said:
On a side note, do you know what the SBL files are for? You say they're not needed for CM but I ended up updating them anyway (as this script does) and it didn't break anything with CM. I figured it was best practice to just update them, but I could be wrong. Any insight on this would be greatly appreciated as I couldn't find much info.
Click to expand...
Click to collapse
Here's what I found:
http://tjworld.net/wiki/Android/HTC/Vision/BootProcess
SBL = Secondary Boot Loader
According to the article, the sbl is something like an efi bios, basically it turns on a bunch of hardware bits and then hands off to the next stage of booting. So I guess now we know. :silly: I'd think if you are updating the boot loader, you'd want to include the secondary bootloader as well. Probably your zip file is correct in that if you update any of those pieces, you should PROBABLY update all of them to the same revision, just in case.
Which means EXTRA thanks to you, for doing the work. Now when people say "why can't I flash the latest CM10?" we can just point to this thread and say "flash that first".
:highfive:
Thanks op so much for this. Running the latest cm nightlies again
Sent from my SGH-T999 using xda premium
djtheraven said:
How can you check what bootloader you have?
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Just open up a shell either in your ROM or CWM Recovery (adb shell) and run:
Code:
$ getprop ro.bootloader
It should print out something like "T999UVDMD5"
I had T999UVALG1 before I upgraded the firmware.
EDIT: If you're going to do it in CWM Recovery, you might have to do it as root. Make sure to adb kill-server as root to kill any adb servers that may be running and a subsequent adb shell should grant you access.
Newbie here, my Dhd is s-on, ive been flashing and custom rom and kernels to it via cwm and as always i have to flash the boot.img both rom/kernel to fully installed it. Now I want to update my kernel to the newest pacharx release for better battery. but It doesnt have the boot.img which im use to flashing.. when i extract here is what i get:
zImage
unpackbootimg
modclean.sh
mkbootimg.sh
mkbootimg
dd
how do i install this kernel?
i tried flashing the zImage but it doesnt work... please help
You do not extract anything from that zip, just flash it whole from the recovery as you would any boot.img
Sent from my Desire HD using xda app-developers app
ilans93 said:
You do not extract anything from that zip, just flash it whole from the recovery as you would any boot.img
Sent from my Desire HD using xda app-developers app
Click to expand...
Click to collapse
i've already done that but since im on s-on i cant flash the rom via cwm, it needs to be in fastboot... i used to flash kernel with boot.img files on it,but now im just lost with this kernel i want to flash because i cant find the boot.img..
anythingbutipod said:
i've already done that but since im on s-on i cant flash the rom via cwm, it needs to be in fastboot... i used to flash kernel with boot.img files on it,but now im just lost with this kernel i want to flash because i cant find the boot.img..
Click to expand...
Click to collapse
That IS a kernel, not a ROM. Just flash it via fastboot then... You can also do it via ADB if you know how to, if not, use the search bar
ilans93 said:
That IS a kernel, not a ROM. Just flash it via fastboot then... You can also do it via ADB if you know how to, if not, use the search bar
Click to expand...
Click to collapse
I know how to.flash via fastboot and abd, my question is what file should i flash since theres no boot.img file in the kernel... Sorry newbie here
anythingbutipod said:
I know how to.flash via fastboot and abd, my question is what file should i flash since theres no boot.img file in the kernel... Sorry newbie here
Click to expand...
Click to collapse
According what I've read in other posts you can't flash a raw kernel.zip with s-on.
It has also been pointed out that a boot.IMG is Rom specific, so they most likely wouldn't be interchangeable between different roms
Sent from my HTC Desire HD using xda app-developers app
anythingbutipod said:
I know how to.flash via fastboot and abd, my question is what file should i flash since theres no boot.img file in the kernel... Sorry newbie here
Click to expand...
Click to collapse
boot.img is a kernel so don't search for a boot.img in a kernel.zip - it's the same thing only not compressed. ranger4740 is correct. You shouldn't use boot.img from one ROM and put it on another, but that's not what you asked for... As for the fact that you can't flash a kernel.zip with S-ON, I didn't know about that so I can't help you there... Sorry :/ Try asking your question in the kernel thread...
ilans93 said:
boot.img is a kernel so don't search for a boot.img in a kernel.zip - it's the same thing only not compressed. ranger4740 is correct. You shouldn't use boot.img from one ROM and put it on another, but that's not what you asked for... As for the fact that you can't flash a kernel.zip with S-ON, I didn't know about that so I can't help you there... Sorry :/ Try asking your question in the kernel thread...
Click to expand...
Click to collapse
Ok, i also tried to do some research and read some forums, seems my only way to s-off my dhd, which i will be researching next... Thanks:fingers-crossed:
My desired rom has already updated with the kernel that i wanted flash ,so my battery life is now great, although there a bug in battery charging where in it notifies late yet it charges the phone batt. (not that big if a deal for me). Also i created an aroma zip file to install all system update on my phone since the original update flashes the kernel... Thanks for the replies "learn a lot from all those researches i made" :victory:
I started making my ROM with Android Kitchen and I dumped system folder from ftf file.
But I cannot find META-INF and boot.img to use for ROM.
I tried using MIUI v4 META-INF and boot.img but I get status 6 error while installing ROM. By Kitchen's FAQ it means something is up with update-script. So, I need to find stock boot.img for latest ICS Arc S firmware and associated META-INF with update-script.
I searched for those files for more than 8 hours, still can't find them.
I hope if anyone posts them that I could be able to normally install ROM without a problem.
Thank you in forward.
Err, there is no stock boot.img. All stock kernels are provided in the stock firmware packages also known as FTF files.
Depending on what you need it for, you can download the source code(, make the modifications) and compile it yourself.
Hmmm, how am I going to make custom ROM without boot.img if it is needed(or is it?).
I can't get any other custom kernel because I want to make ROM for locked bootloader phone.
Do you know what should I do to complete ROM if i can't have stock boot.img?
A_B_E_D said:
Hmmm, how am I going to make custom ROM without boot.img if it is needed(or is it?).
I can't get any other custom kernel because I want to make ROM for locked bootloader phone.
Do you know what should I do to complete ROM if i can't have stock boot.img?
Click to expand...
Click to collapse
For roms built on stock Rom, u shouldnt have any kernel inside the flashable zip
Sent from my LT18i
Sahaab said:
For roms built on stock Rom, u shouldnt have any kernel inside the flashable zip
Sent from my LT18i
Click to expand...
Click to collapse
Yeah, that's what I though after someguyfromhell wrote a post and I made a new zip without boot.img and deleted write_raw_image line from update-script.
Right now I am searching for solution to other problem(some folders and files are not showing up on my sdcard while viewing it in Windows, so I have no space to drop ROM in there, will try when I fix this).
Thank you both for replies, will try to fix this soon.
A_B_E_D said:
Hmmm, how am I going to make custom ROM without boot.img if it is needed(or is it?).
I can't get any other custom kernel because I want to make ROM for locked bootloader phone.
Do you know what should I do to complete ROM if i can't have stock boot.img?
Click to expand...
Click to collapse
If you are going to do a ROM for locked bootloaders, then there is no boot.img needed at all. Locked bootloader means stock kernel, means no boot.img.
Also, it is not needed. Some ROM developers supply their own kernels together with the ROM, however it is not a requirement.
Updated July 23, 2014. The recovery only for Stock JB 4.1, 4.2
The New Installer is for Windows OS.
Please Set USB debug "ON" in phone and adb driver is already installed in Windows OS and of course Full root.
Link download:
rachitrawat said:
try this : http://d-h.st/QsQ
:fingers-crossed:
Click to expand...
Click to collapse
New info:
All recovery is worked as expected, recovery: CWM, PHILZ-touch, and TWRP only on firmware 4.1-4.2.
And always read the last 10 post.
gamer649 said:
Just backing up my XM now, after I have done that I will start the testing on lower firmwares. Been a busy day and I've only been able to start doing stuff for the recoveries.
EDIT 1: Well, got some good news to report, on the 4.1.2 firmware for the Xperia M SS all 3 recoveries boot as expected (I haven't tested them). I will test on the 4.2.2 Xperia M DS firmware tomorrow morning.
EDIT 2: Some more good news, on the 4.2.2 firmware for the Xperia M DS only thw CWM and philZ recoveries boot as expected, I can't seem to install TWRP as I keep getting protocol errors in the installer. Again, I haven't tested them.
@rachitrawat Results are now up for you to look at
Click to expand...
Click to collapse
pedroj666 said:
Confirmed working on my XM. :good:
I just installed "recoverie Philz" on my XM with android 4.2.2 and it works 100%.:laugh:
Many thanks for the most excellent work.
Translated by google translator. sorry
Click to expand...
Click to collapse
Requirement:
Must be full root
Quick Installation:
Download and extract the installer on your windows pc - http://d-h.st/QsQ
Open or click twice install.bat
Follow instruction on screen.
Don't forget to allow the pc, to access adb on the phone.
And allow adb shell in superSU.
How to boot the recovery:
Whatever which the recovery you use. Here the way.
Power off the phone. And then turn it on.
Wait until the pink LED is shown.
Press the vol up button, 1 second after the pink LED is shown.
Then the phone should boot to the recovery.
Mini FAQ:
Q: the phone not shown the pink LED
A: please check this files are in the right folder/directory.
/system/xbin/busybox
/system/bin/recovery.tar
/system/bin/recovery.sh
and this's script type file /system/bin/e2fsck
the original file is renamed to /system/bin/e2fsck.bin
This method is for PhilZ Touch or Stock CWM 6.0.4.9? I see in this thread.. Can we try this to Xperia M Dual? Because XMD have PhilZ Recovery now.. Thanks in advance..
Sorry For My Bad English :fingers-crossed:
Maybe the problem of it not running stems from /mnt/idd and /SDCard (External), I'm suggesting this because I cannot find them on the partion listing of my device. Or maybe that's just me being an idiot.
Just been looking through the init.qcom.sh file in the recovery.tar folder and I have found it asks for "baseband='cat ro.baseband'", however the closest I can get to that is ro.si.version.sw_revision.
Have you changed the mountpoints about accordingly in the .fstab files in the recovery.tar /etc/ folder? That could also be another reason.
Also, take a look at the default.prop in the recovery.tar folder, that has all the Xperia L specs and stuff in it.
Naufal Sidik said:
This method is for PhilZ Touch or Stock CWM 6.0.4.9? I see in this thread.. Can we try this to Xperia M Dual? Because XMD have PhilZ Recovery now.. Thanks in advance..
Sorry For My Bad English :fingers-crossed:
Click to expand...
Click to collapse
The file in attachment is stock CWM 6.0.4.9 XMS.
Of course we can port it to XMD, but now the method isnt working.
In near future maybe we can have both rec. like Xperia L, now have stock cwm and philz.
Okey Sip
gamer649 said:
Maybe the problem of it not running stems from /mnt/idd and /SDCard (External), I'm suggesting this because I cannot find them on the partion listing of my device. Or maybe that's just me being an idiot.
Just been looking through the init.qcom.sh file in the recovery.tar folder and I have found it asks for "baseband='cat ro.baseband'", however the closest I can get to that is ro.si.version.sw_revision.
Have you changed the mountpoints about accordingly in the .fstab files in the recovery.tar /etc/ folder? That could also be another reason.
Also, take a look at the default.prop in the recovery.tar folder, that has all the Xperia L specs and stuff in it.
Click to expand...
Click to collapse
Hi Bro.
I thinks its only output some error if the partition is not found, and continue the batch process anyway.
I was compared the init.qcom.sh file with same file from Xperia L,and i found the different only in line like this
Code:
from xperia m cwm
chmod -h 775 /data/system/sensors
from cwm xperia L
chmod 775 /data/system/sensors
and some more line contain chmod command
In Linux "chmod -h" mean will print the help page of that command.
Please let me clear this, the recovery.tar file is taken from stock CWM for xperia M single, not from xperia L.
And of course the mountpoint is correct according to partition in xperia M.
And about the default.prop file its same with stock cwm for xperia M, please take alook into it.
Thanks for your reply
Code:
Note:
I must clear its, the recovery.tar file is taken from Working CWM that currently used by many kernel for xperia M single.
I've only been looking into the recovery what I got from the XL section, I haven't looked into the stuff we have got for unlocked bootloaders just yet. I'll probably do that soon
Sent from my C1905 using XDA Premium 4 mobile app
gamer649 said:
I've only been looking into the recovery what I got from the XL section, I haven't looked into the stuff we have got for unlocked bootloaders just yet. I'll probably do that soon
Sent from my C1905 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
hmm, can you please just download my attachments in OP? so you can check the files
Thanks.
Sure, I'll probably do that later.
Sent from my C1905 using XDA Premium 4 mobile app
I would love to help out right now. This is a really cool project and i wish we can get a fully functioning recovery for out device, keep up the good work and effort guys
paper13579 said:
I would love to help out right now. This is a really cool project and i wish we can get a fully functioning recovery for out device, keep up the good work and effort guys
Click to expand...
Click to collapse
Hi Paper
Btw i do this project is for users who have locked bootlader permanently, and of course not all user adb friendly.
For me i have Bootloader unlock allowed=yes but not unlocked yet
Just had a look at the files you have attached and I think it is the .fstab files what need editing properly to get it into a bootable state. However I am unsure so don't assume I am right.
ndrancs said:
Hi Paper
Btw i do this project is for users who have locked bootlader permanently, and of course not all user adb friendly.
For me i have Bootloader unlock allowed=yes but not unlocked yet
Click to expand...
Click to collapse
Yes i know that bro. My phone is bootloader unlock allowed: no
Just had a look to the default.prop file in the recovery.rar you have attached in the first post. I am correct in assuming that this recovery was extracted from the Pac ROM? The default.prop has a lot of values relating to that in it. That may be another issue.
gamer649 said:
Just had a look to the default.prop file in the recovery.rar you have attached in the first post. I am correct in assuming that this recovery was extracted from the Pac ROM? The default.prop has a lot of values relating to that in it. That may be another issue.
Click to expand...
Click to collapse
Here the original link and thread for the recovery.
IMG:
CWM
Original Thread
Yes maybe but i found this line in the default.prop file.
Code:
ro.pacstats.url=http://stats.pac-rom.com
ro.pacstats.name=PAC-man
Any suggestion ?
ndrancs said:
Here the original link and thread for the recovery.
IMG:
CWM
Original Thread
Yes maybe but i found this line in the default.prop file.
Code:
ro.pacstats.url=http://stats.pac-rom.com
ro.pacstats.name=PAC-man
Any suggestion ?
Click to expand...
Click to collapse
1) Remove all unique properties to Pac ROM & any other custom ROM information.
2) Remove any values to the properties what contain Pac ROM and custom ROM values (possibly populating them with stock values?).
3) Get the original default.prop from the firmware we want to use and insert that into the recovery.tar instead (I don't think this will work as the one I found on my device is hardly populated).
If anything a mixture of all three may be appropriate.
gamer649 said:
1) Remove all unique properties to Pac ROM & any other custom ROM information.
2) Remove any values to the properties what contain Pac ROM and custom ROM values (possibly populating them with stock values?).
3) Get the original default.prop from the firmware we want to use and insert that into the recovery.tar instead (I don't think this will work as the one I found on my device is hardly populated).
If anything a mixture of all three may be appropriate.
Click to expand...
Click to collapse
Have try it but still no luck, its just display sony logo, and then reboot after a few minutes.
Does it boot at all? If it still boots at least that's something.
Sent from my C1905 using XDA Premium 4 mobile app
You're asking for troubles guys.
First of all, correct me if I'm wrong, I'm not experienced with fastboot yet. You have root and rom with busybox, regardless if stock or not. Isn't it possible to simply just flash proper boot.img in kernel block? Bootloader is required to use fastboot and flash unsigned images, by using root in the ROM you're not touching bootloader at all. And including custom recovery in stock boot.img is pretty damn easy.
Second thing, you're trying to do potentially dangerous thing. Dangerous as hell, this can lead to pretty serious filesystem corruptions, as lazy unmounting (umount -l) is never safe. I have knowledge about what you're trying to do, as I included pocket debian in my ArchiDroid since ages and it also uses chroot capability, but it extends android, not trying to hack it and run remote code. Killing services, unmounting filesystems and patching things is not proper thing to do.
gamer649 said:
Does it boot at all? If it still boots at least that's something.
Sent from my C1905 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I have added a debug code to e2fsck.sh and recovery.sh, just to make sure all command are execute and see the output if there something wrong.
The result of e2fsck.sh is there not something wrong its just run as is must.
And same with recovery.sh it run ok to the end off the script, chroot command.
After chroot command i cant make the log.
Maybe this recovery will run on stock JB 4.2 like in Xperia L.
JustArchi said:
You're asking for troubles guys.
First of all, correct me if I'm wrong, I'm not experienced with fastboot yet. You have root and rom with busybox, regardless if stock or not. Isn't it possible to simply just flash proper boot.img in kernel block? Bootloader is required to use fastboot and flash unsigned images, by using root in the ROM you're not touching bootloader at all. And including custom recovery in stock boot.img is pretty damn easy.
Second thing, you're trying to do potentially dangerous thing. Dangerous as hell, this can lead to pretty serious filesystem corruptions, as lazy unmounting (umount -l) is never safe. I have knowledge about what you're trying to do, as I included pocket debian in my ArchiDroid since ages and it also uses chroot capability, but it extends android, not trying to hack it and run remote code. Killing services, unmounting filesystems and patching things is not proper thing to do.
Click to expand...
Click to collapse
Please... read my OP carefully.
I see @Rachit Rawat and @[Nut} have successfully add recovery to stock rom Jb 4.2 for xperia L and Xperia Z too with locked bootloader condition.
May i try to explain, with this method we just hijack the boot process of stock kernel, stock ramdisk to boot our custom boot script to launch the recovery. just like that. and about the unmout -l (lazy unmout) its to unmount every mountpoint that was mounted by original ramdisk so before the recovery launch its clean from mountpoint of original ramdisk.
Please check @Rachit Rawat thread here
Xperia L stock recovery
http://forum.xda-developers.com/xperia-l/orig-development/cwm-recovery-installer-t2589320
thanks for you reply.