CLOSED
it works on sk17a?? sorry for the noob question but, i need to know
bbooff said:
I didn't have to do much.
Just minor modifications on my existing kernel for 4.0.2A.0.42
Works exactly as in 4.0.2A.0.42
INSTRUCTIONS:
Run cmd in the folder that contains fastboot.exe.Unzip boot.zip in the same folder.Connect your sk17i in fastboot mode(shutdown your device,hold volume up and connect your device to your pc via usb (blue led lights up)).
Type:fastboot flash boot boot.img
ENJOY!
Click to expand...
Click to collapse
bbooff do you mind to share how to modify stock kernel?
i want to make make some modification on xperia active stock kernel.
thank you.
my firmware is 4.0.2.A.0.58 flashed from SE PC Companion, rooted by darklords method, unlocked bootloader from SE dev site with SE key. When flashing the boot.img from fastboot can access clockworkmod recovery but home hardware key and msc mtp modes failed.
SOLVED! Post 5 solution.
Do the following mughalgxt:
Flash your device again using SEUS.If SEUS tells you that your software is the latest, choose REPAIR.Then, flash the custom kernel, without rooting first.If the problem persists,let me know...
puppet13th, take a look at this:
http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
Woa thnx for that link
bbooff said:
puppet13th, take a look at this:
http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
Click to expand...
Click to collapse
thank you,i will check it out.
Tried this myself for my Active. Thing is, even though i follow the instructions listed in the site OP gave and this site also:
http://forum.androidspin.com/showthread.php/3973-ADVANCED-How-To-Mod-BOOT-amp-RECOVERY but all i end up with is a softbrick. When I initially try and flash the boot.img on the device i get this error:
"writing 'boot'... FAILED (remote: Wrong range:0x10008000-0x10360b0b. Ok:0x00200000 - 0x03dfff)"
Click to expand...
Click to collapse
Tried adding base 0x00200000 to the cmdline part but no cigar. Also how do you extract the boot.img from your device since its not listed in the mtd's?
flashed it, got OKAY at the end and superuser was installed.
i can't however get into CVM. it's volume down key after Sony Erricssson letters appears right?
i did however have it rooted already with zergrush method, but i dont think that cant interfere with getting into recovery.
i had no issues getting into recovery when i had CM installed.
sulkie,
you need to to press and release the power on/off key just once, as soon as the (white) sony ericsson logo turns brighter.
dumraden said:
Tried this myself for my Active. Thing is, even though i follow the instructions listed in the site OP gave and this site also:
http://forum.androidspin.com/showthread.php/3973-ADVANCED-How-To-Mod-BOOT-amp-RECOVERY but all i end up with is a softbrick. When I initially try and flash the boot.img on the device i get this error:
Tried adding base 0x00200000 to the cmdline part but no cigar. Also how do you extract the boot.img from your device since its not listed in the mtd's?
Click to expand...
Click to collapse
same here.i use flashtool to decrypt firmware files downloaded by SEUS.then i got kernel.sin then i use sin2img from Xperia ROM manager to convert kernel.sin to kernel.img. the converted file can't be splited using split_bootimg.pl. it's says wrong android magic or someting like that.
if you want to test the kernel just use these command :
Code:
fastboot boot kernel.img
Bboff,sorry for asking this,if i flash ur kernel and then relock my BL ,can i receive updata OTA without bricking my phone?
bbooff,
does this kernel support voice call recording?
rm001 said:
bbooff,
does this kernel support voice call recording?
Click to expand...
Click to collapse
This kernel supports whatever the stock kernel supports.
Black_jackss said:
Bboff,sorry for asking this,if i flash ur kernel and then relock my BL ,can i receive updata OTA without bricking my phone?
Click to expand...
Click to collapse
Some mentioned having problems with update OTA, so i do not recommend it.You can receive updates via SEUS without any problems if you relock your bootloader.This is guaranteed
bbooff,
Is it possible to add the support for voice call recording to your kernel (and/or to your HYBROMs)? Or it`s too difficult? Just in case, if it can help you: it is added in KRsH Kernel v2.0 (MiniPro)
rm001 said:
bbooff,
Is it possible to add the support for voice call recording to your kernel (and/or to your HYBROMs)? Or it`s too difficult? Just in case, if it can help you: it is added in KRsH Kernel v2.0 (MiniPro)
Click to expand...
Click to collapse
Check this app from the market:RECORD MY CALL
Tested with HYBROM v3 on my custom kernel about a minute ago.
Records any call and works fine.
(so, both kernel and rom obviously support call recording)
bbooff said:
Check this app from the market:RECORD MY CALL
Tested with HYBROM v3 on my custom kernel about a minute ago.
Records any call and works fine.
(so, both kernel and rom obviously support call recording)
Click to expand...
Click to collapse
There are a lot of apps for call recording, but they record the sound from microphone, not from the line, so if you are on the street it becomes useless. The official ROM 100% doesn`t support line recordins, I checked. For example, if you set the option "use root/use kernel recording" instead of "use microphone", they produce an empty records.
Nevertheless I`ll try this app also, thank you very very much.
rm001 said:
There are a lot of apps for call recording, but they record the sound from microphone, not from the line, so if you are on the street it becomes useless. The official ROM 100% doesn`t support line recordins, I checked. For example, if you set the option "use root/use kernel recording" instead of "use microphone", they produce an empty records.
Nevertheless I`ll try this app also, thank you very very much.
Click to expand...
Click to collapse
Sorry..
I didn't quite understand what you meant before.It is clear now.
I will see what i can do...(But not in the near future...)
Related
I've got a problem, but I'm not sure if it's been addressed anywhere else on here, I've searched through several pages. I've found a situation that was similar, but not the same. So I'm putting it out there, and hoping someone will solve it:
I've got a Sony Ericsson Live with Walkman (WT19i)
I rooted my phone, unlocked it's bootloader, and flashed a ROM; everything went well until it rebooted. Now I'm stuck at the point where the "Sony Ericsson" logo is shown, i've been stuck there for almost 30 minutes now.
Any help possible? Any at ALL would be MUCH appreciated.
akshay7394 said:
I've got a problem, but I'm not sure if it's been addressed anywhere else on here, I've searched through several pages. I've found a situation that was similar, but not the same. So I'm putting it out there, and hoping someone will solve it:
I've got a Sony Ericsson Live with Walkman (WT19i)
I rooted my phone, unlocked it's bootloader, and flashed a ROM; everything went well until it rebooted. Now I'm stuck at the point where the "Sony Ericsson" logo is shown, i've been stuck there for almost 30 minutes now.
Any help possible? Any at ALL would be MUCH appreciated.
Click to expand...
Click to collapse
What ROM are you trying to flash on your phone?
Did you checked first if the Bootloader was actually unlocked?
Did you flash a custom kernel thru fastboot?
Custom ROM needs custom kernel.
Sent from my WT19i using xda premium
melander said:
What ROM are you trying to flash on your phone?
Did you checked first if the Bootloader was actually unlocked?
Did you flash a custom kernel thru fastboot?
Click to expand...
Click to collapse
I was trying to flash HYBROM.
Bootloader was unlocked for sure as I had installed Coconut previously, which also requires bootloader unlock.
No worries though; i solved my problem. I flashed an older firmware, along with a bootload relocker, with Flashtool. Now my phone has switched on, to my stock ROM. Still no clue how to flash hybrom ROM as it caused the same problem even after wiping dalvik cache and all other data (which was the solution provided by dev)
Someguyfromhell said:
Custom ROM needs custom kernel.
Sent from my WT19i using xda premium
Click to expand...
Click to collapse
Okay, please help me understand: What is a custom kernel and how do i install it? Everywhere I've looked there's been no mention of the need for a custom kernel
akshay7394 said:
Okay, please help me understand: What is a custom kernel and how do i install it? Everywhere I've looked there's been no mention of the need for a custom kernel
Click to expand...
Click to collapse
check first page of hybrom thread
Installation instructions
Needs unlocked bootloader
(actually hybrom does not contain a boot image.Thus, when you install hybrom you don't mess with your boot image at all.BUT recovery from nAa is installed in /system and while system is formated during the installation of hybrom,recovery messes with it self.That's why unlocked bootloader and a custom kernel with recovery is necessary for now to install hybrom)
Click to expand...
Click to collapse
melander said:
check first page of hybrom thread
Click to expand...
Click to collapse
I did not deny that a custom kernel is needed, I wanted to know how to flash/use a custom kernel?
To flash a custom kernel you need to have flashtool (sticky thread on the dev section) so:
1.- you download the custom kernel (it is a boot.img file)
2.- open flashtool
3.- connect your phone to your computer while the phone its off and you are holding the volume up key without releasing it the notification led should turn on blue.
4.- if the phone it's not recognized go to the flashtool folder and install the drivers located on the drivers folder once it is done repeat step 3 and it should be recognized.
5.- once your device it's connected click the thunderbolt icon on flashtool in the new screen select fastboot mode and continue.
6.- in the new screen click on select kernel to flash and browse to the boot.img you downloaded.
7.- check the flashtool log to make sure everything is fine if it is you are good to go.
Hope it helps.
ginryu said:
To flash a custom kernel you need to have flashtool (sticky thread on the dev section) so:
1.- you download the custom kernel (it is a boot.img file)
2.- open flashtool
3.- connect your phone to your computer while the phone its off and you are holding the volume up key without releasing it the notification led should turn on blue.
4.- if the phone it's not recognized go to the flashtool folder and install the drivers located on the drivers folder once it is done repeat step 3 and it should be recognized.
5.- once your device it's connected click the thunderbolt icon on flashtool in the new screen select fastboot mode and continue.
6.- in the new screen click on select kernel to flash and browse to the boot.img you downloaded.
7.- check the flashtool log to make sure everything is fine if it is you are good to go.
Hope it helps.
Click to expand...
Click to collapse
Thankyou, this does help. One last question: Are there several different custom kernels? Does WHICH kernel i get matter, or is any kernel usable on any phone?
akshay7394 said:
Thankyou, this does help. One last question: Are there several different custom kernels? Does WHICH kernel i get matter, or is any kernel usable on any phone?
Click to expand...
Click to collapse
Depending on the ROM, you want to install, you need correct kernel.
CM ROMs work only with FXP kernels, included in their topic.
MIUI ROMs have only specific kernels also, included in their topic.
Stock-based ROMs(XROM, Hybrom) work with Rage Kernel, X Kernel, bbooff's kernel, all these are in Development section, just search.
Glad to be helpful anything else just let us know.
Thanks very much!
I have a live with walkman from 3 etwork. the bootloader is locked. can I still flash hybrom 16 through CWM?
check service menu,
confirm if bootloader can be unlocked.
it should state "bootloader unlock allowed : yes".
after unlocking bootloader then there will be no problem installing hybrom
check this thread for more info about unlocking bootloader.
raymond_76 said:
I have a live with walkman from 3 etwork. the bootloader is locked. can I still flash hybrom 16 through CWM?
Click to expand...
Click to collapse
No. You must have unlocked bootloader. Also, for Hybrom, you must install custom kernel also.
Sent from my WT19i using xda premium
akshay7394 said:
I was trying to flash HYBROM.
Bootloader was unlocked for sure as I had installed Coconut previously, which also requires bootloader unlock.
No worries though; i solved my problem. I flashed an older firmware, along with a bootload relocker, with Flashtool. Now my phone has switched on, to my stock ROM. Still no clue how to flash hybrom ROM as it caused the same problem even after wiping dalvik cache and all other data (which was the solution provided by dev)[/QUO}
could you direct me through flash tool please
i have the exact same problem trying to load the same rom.
---------- Post added at 07:27 PM ---------- Previous post was at 07:22 PM ----------
raymond_76 said:
I have a live with walkman from 3 etwork. the bootloader is locked. can I still flash hybrom 16 through CWM?
Click to expand...
Click to collapse
I tried this now im stuck on the boot screen
Click to expand...
Click to collapse
Unlock your bootloader first.
What ROM are you trying to install?
Someguyfromhell said:
Unlock your bootloader first.
What ROM are you trying to install?
Click to expand...
Click to collapse
"ROM: CyanogenMod 7.2 FXP115"
The ROM you're using, is it good? and how (relatively) stable is it? Do the stereo speakers/Walkman button work?
akshay7394 said:
"ROM: CyanogenMod 7.2 FXP115"
The ROM you're using, is it good? and how (relatively) stable is it? Do the stereo speakers/Walkman button work?
Click to expand...
Click to collapse
Yes, it is fine for me, no problems at the moment. Stereo speakers require a tweak, link in my signature. Walkman button doesn't work.
Sent from my WT19i using xda premium
Someguyfromhell said:
Yes, it is fine for me, no problems at the moment. Stereo speakers require a tweak, link in my signature. Walkman button doesn't work.
Sent from my WT19i using xda premium
Click to expand...
Click to collapse
Fantastic How'd you flash it? same as hybrom? (Unlock bootloader then flash?)
I believe this might be possible. If someone is willing to give this a try, a developer for example? Try to extract your own bootloader from you phone, re-pack it for CWM as a flashable file and upload. I don't know anything when it comes to the proceedure of how this is done, but fishing about this forum area "http://forum.xda-developers.com/forumdisplay.php?f=855" might lead to a few clues. However this is a different device from a different manufacturer, they have managed to extract the BL. Not sure how. But it proves it must be possible, no? Im desperate for a bootloader unlock. Can't believe my operator is not allowing this.
Won't work. Just won't. Adding to the list.
K900 said:
Won't work. Just won't. Adding to the list.
Click to expand...
Click to collapse
Okay, no worries. What about this, wouldn't it work if we managed to load a custom kernel AFTER the original kernel is already loaded? A bit like 2nd-init in CWM? Just suggesting as many things as I can so you can either shoot them down in flames and add them to the list, or if something pops up that we COULD possibly try, you can help forward it for development. If it fails it fails...
Booting the custom kernel still requires an unlocked bootloader right? Then you are going to have to boot an enirely new android system on top of your basic one to boot custom kernels.
Correct me if i'm wrong
Sent with my Sony Xperia S using a little bit of KA magic.
JoelChrist_ said:
Booting the custom kernel still requires an unlocked bootloader right? Then you are going to have to boot an enirely new android system on top of your basic one to boot custom kernels.
Correct me if i'm wrong
Sent with my Sony Xperia S using a little bit of KA magic.
Click to expand...
Click to collapse
Well the thought behind my suggestion is that since the kernel is loaded officially, it means the key is already bypassed due to the official kernel going through which then means if we can load a new kernel as the Rom loads or just before it loads yet still after the original kernel has loaded then the key must still be bypassed and this new custom kernel can be loaded? People should keep giving suggestions!
Sent from my LT26i using xda premium
It might just work, but you would need 2 boot partitions right?
We could make a script that boots the second kernel before the first kernel boots the system.
Sent with my Sony Xperia S using a little bit of KA magic.
It's hardly possible to boot the kernel as late as the earliest possible injection (install-recovery) on locked BL.
No way to make a delay on that time given?
keewanchoapsss said:
No way to make a delay on that time given?
Click to expand...
Click to collapse
We can delay it, but to be able to hot boot a kernel, we need to push it back (so we can jump in earlier) not forward.
K900 said:
We can delay it, but to be able to hot boot a kernel, we need to push it back (so we can jump in earlier) not forward.
Click to expand...
Click to collapse
You can do it on post boot iirc, just overwrite /system/bin/chargemon with a custom script, mv chargemon to charger, and at the end of the script run charger.
only problem with this is you need a way of hijacking in the kernel (I have no idea how to do this).
KeiranFTW said:
You can do it on post boot iirc, just overwrite /system/bin/chargemon with a custom script, mv chargemon to charger, and at the end of the script run charger.
only problem with this is you need a way of hijacking in the kernel (I have no idea how to do this).
Click to expand...
Click to collapse
Yeah, the exact problem is we need to hot swap the kernel. It's possible (by using something similar to Uptrack, i.e. dynamically replacing code in memory), but needs to happen early enough so that nothings breaks if it goes wrong.
Can't we just do something similar to dualboot, but with the option to choose between boot system and boot the second kernel?
Sent with my Sony Xperia S using a little bit of KA magic.
JoelChrist_ said:
Can't we just do something similar to dualboot, but with the option to choose between boot system and boot the second kernel?
Sent with my Sony Xperia S using a little bit of KA magic.
Click to expand...
Click to collapse
Dualboot needs to be handled by the bootloader or the kernel itself, but we can't modify either on locked bootloader.
Dualboot different kernel it's only possible if there's a custom bootloader ( with a 2nd boot partition for the 2nd kernel , and possibility to switch kernel before booting it [ like dualboot BL of iconia a500/501 ]
Dualboot different roms it's possible by having 2 roms that uses the same kernel , so you can switch rom after kernel boot ( like siyahkernel )
For extract bootloader I think it should be possible by reverse engineering fastboot executible ( if it can put .ta key to unlock bootloader , I think fastboot can also read bootloader partition [ it's quite impossible it can write but it can't read ]) and add the command to read and save bootloader
EDIT : for extract bootloader try to extract it from loader.sin ( 7-zip give me that file is broken , but I think it has strange compression method or some protection to avoid extraction)
EDIT2 : algorithm for compress/decompress loader into loader.sin its LZMA but for some reason 7-zip cannot decompress it
If we'll found a good lzma sompressor/decompressor it will be easier to extract , edit , and repack bootloader for flash by loader.sin with flashtool
EDIT3 (too edit in this post ) : Founded romanger tool that can convert sin to img , but problem remain , tomorrow I will try to use new version of flashtool ( 0.9) to extract loader .sin.... in changelog it's wrote that thay added loder.sin extract from sony fileset ..... maybe it will work
Forzaferrarileo said:
Dualboot different kernel it's only possible if there's a custom bootloader ( with a 2nd boot partition for the 2nd kernel , and possibility to switch kernel before booting it [ like dualboot BL of iconia a500/501 ]
Dualboot different roms it's possible by having 2 roms that uses the same kernel , so you can switch rom after kernel boot ( like siyahkernel )
For extract bootloader I think it should be possible by reverse engineering fastboot executible ( if it can put .ta key to unlock bootloader , I think fastboot can also read bootloader partition [ it's quite impossible it can write but it can't read ]) and add the command to read and save bootloader
EDIT : for extract bootloader try to extract it from loader.sin ( 7-zip give me that file is broken , but I think it has strange compression method or some protection to avoid extraction)
EDIT2 : algorithm for compress/decompress loader into loader.sin its LZMA but for some reason 7-zip cannot decompress it
If we'll found a good lzma sompressor/decompressor it will be easier to extract , edit , and repack bootloader for flash by loader.sin with flashtool
EDIT3 (too edit in this post ) : Founded romanger tool that can convert sin to img , but problem remain , tomorrow I will try to use new version of flashtool ( 0.9) to extract loader .sin.... in changelog it's wrote that thay added loder.sin extract from sony fileset ..... maybe it will work
Click to expand...
Click to collapse
You are massively wrong here.
1) hotbooting a kernel is indeed possible, I can give you related links later, but for now just Google KSplice Uptrack.
2) Fastboot has nothing to do with Sony's cryptography, it is a Google tool that is open source as a part of AOSP. If you are talking about flashtool, it is also open source, so there is absolutely no magic involved on the PC. Flashtool reads and writes the loader as raw data, not trying to decipher it. If you still want to mess with loader.sin, it's unlikely to be LZMA compressed because that means an even lower level of software is required to decompress it. A 'good LZMA decompressor' you're looking for is unsurprisingly called lzma, is open source and should come preinstalled in most Linux distributions.
3) To flash anything, even the bootloader, with flashtool or any other method, you'll need to sign it with Sony's key or find a way to bypass the validation in Sony's stock bootloader. This also means that even if you manage to modify the bootloader code, you will not be able to flash it on locked devices unless one of the above happens.
But where in the loader file, or any stock file can we find the validation of sony?
Sent with my Sony Xperia S using a little bit of KA magic.
JoelChrist_ said:
But where in the loader file, or any stock file can we find the validation of sony?
Sent with my Sony Xperia S using a little bit of KA magic.
Click to expand...
Click to collapse
In the file header. The problem is it's an asymmetric signature. So 1) you need different keys to sign and to verify signatures and 2) the signature itself depends on the file's content, so when the file is changed, it'll no longer be valid.
Are bootloader files also verified by Sony?
I don't think so, because the bootloader is the first software to start so it cant be checked by some other software right?
If all this is correct, cant we pull the bootloader file in some way, and replace it with an unlocked or unlockable version?
Correct me if I'm wrong
Sent with my Sony Xperia S using a little bit of KA magic.
JoelChrist_ said:
Are bootloader files also verified by Sony?
I don't think so, because the bootloader is the first software to start so it cant be checked by some other software right?
If all this is correct, cant we pull the bootloader file in some way, and replace it with an unlocked or unlockable version?
Correct me if I'm wrong
Sent with my Sony Xperia S using a little bit of KA magic.
Click to expand...
Click to collapse
The new bootloader is verified by the old bootloader.
K900 said:
The new bootloader is verified by the old bootloader.
Click to expand...
Click to collapse
In that case, if we remove the bootloader, and flash the other one, there is no bootloader to verify it right?
Sent with my Sony Xperia S using a little bit of KA magic.
i 've got an amaze 4g t-mobile recently.it works perfectly.but then,i updated to ICS through OTA...
Everything work fine except Wifi,i cant turn on wifi at all.It only show error when i try to turning on ...
I did search the whole forums,trying everthing i can do..unlock boot loader/rooted/s-off/flash 4EXT recovery/flash many cook rom (android revolution,fastrom,energy rom..),kernel(ruby-faux123 v007/v008/v015/v016..)
finally i reverted back to Stock GB with "PH85IMG_Ruby_TMOUS_1.43.531.3_Radio_1.08.550L.19DC_30.66.550L.08D_release_228638_signed".
but wifi still shows ''error'' at all,when i try to turning on hotspot ,the phone force to reset .
currently:
Stock GB:2.3.4
Sense:3.0
Kernel:2.3.35.13 build 144#1
Baseband:1.08.550L.19DC_30.66.550L.08D
Buildnumber:1.43.531.3
Bootloader unlocked and s-off.
Hoping there is anyone else can understand my bad english and help me .
Since you're s-off try updating back to ics via the most recent file in the stock ruu thread and see if it resolves it.
sent from a smooth place where my fingers trace across the screen to see your face and make you scream!
thanks sir
i try to flashing this kernel into my stock GB:Amaze-EKF-009b-sense.zip
hope it works
ronaldinho_07 said:
thanks sir
i try to flashing this kernel into my stock GB:Amaze-EKF-009b-sense.zip
hope it works
Click to expand...
Click to collapse
Kernel won't change much, but the wifi drivers being present in the kernel just might help, let me know your results.
Dark Nightmare said:
Kernel won't change much, but the wifi drivers being present in the kernel just might help, let me know your results.
Click to expand...
Click to collapse
as you have said,i just flashed the above kernel (Amaze-EKF-009b-sense.zip) into stock GB,but wifi error is still there
after that,i updated to ICS via RUU and flashed this kernel from here : http://forum.xda-developers.com/showthread.php?t=1362759 (at #5)
Nothing changes.
at the first time,i have flashed the Amaze ICS(v015) kernel via 4EXT touch recovery,flashed kernel successfully .
(http://forum.xda-developers.com/showthread.php?t=1359951)
but i think i go wrong somewhere,because the following instruction said:
CWM Flash Instructions: (NO LONGER SUPPORTING CWM METHOD DUE TO HTC's STUPID S-ON UNLOCK!!!)
1. Copy file to SDcard
2. Reboot to CWM recovery
3. Flash the Zip file (if you noticed an error, Flash the same file the 2nd time)
4. Reboot, Done!
i read carefully the second way
Easy Kernel Flasher Instructions:
1. download the above file (via phone directly or to a PC)
2. unzip to a folder then depends on PC or Linux
[ Windows ] open command prompt window and type Flash.bat
[ Linux ] open terminal window and type ./Flash.sh (make sure permission is set to 755 for the Flash.sh)
3. Let the script complete!
,downloaded the kernel,extracted into a folder on my pc.
but i dont see any "Flash.bat'' and dont know how to flash it.
but in the folder that i've just extracted.i found two file:
wl12xx.ko and wl12xx_sdio.ko
putting the whole folder modules into the this kernel (http://forum.xda-developers.com/showthread.php?t=1362759) and run flash.bat...
after flashing,both wifi and bluetooth broken
when i try to turning them on,they turn off instantly
//sorry sir for the bad english
Try to run my AIO tool, which can be found here: http://forum.xda-developers.com/showthread.php?t=1762936
If that doesn't work, more likely than not, it's a hardware issue, as my AIO tool will install a MOSTLY stock RUU with a stock kernel. If that doesn't work, I strongly doubt anything else would work either.
Make sure you follow the directions for the tool.
Keylogger_0 said:
Try to run my AIO tool, which can be found here: http://forum.xda-developers.com/showthread.php?t=1762936
If that doesn't work, more likely than not, it's a hardware issue, as my AIO tool will install a MOSTLY stock RUU with a stock kernel. If that doesn't work, I strongly doubt anything else would work either.
Make sure you follow the directions for the tool.
Click to expand...
Click to collapse
thanks sir,i'll try
btw,i try to flashing faux123-kernel via CWM recovery,but i's aborted
then,i force to flash faux123-kernel via 4EXT touch recovery and succeed
but i still cant turn on wifi,it just says error
can anyone give me an advise,pls
That memory block is probably damaged.
sent from a galaxy you'll never see.
do you think it's related to wifi hardware issues
ronaldinho_07 said:
do you think it's related to wifi hardware issues
Click to expand...
Click to collapse
It could be that as well, did you call tmo and tell em about it?
Dark Nightmare said:
It could be that as well, did you call tmo and tell em about it?
Click to expand...
Click to collapse
i cant do that because i live in vietnam sir
btw,when i was in a custom rom with fraux's kernel.it would just stay in dim grey and say "turning wifi on" and freeze there for a while,then saying "Error''
but,when i tried to copying "wlan12xx.ko,wlan12xx_sdio.ko" from Fraux kernel to Amaze stock kernel modules folder.Flashed it.
then,i turned it on and the wifi turned off itself instantly without saying error
there was wifi error same here :
http://forum.xda-developers.com/showthread.php?t=1796358
thanks for your helps sir :good:
ronaldinho_07 said:
i cant do that because i live in vietnam sir
btw,when i was in a custom rom with fraux's kernel.it would just stay in dim grey and say "turning wifi on" and freeze there for a while,then saying "Error''
but,when i tried to copying "wlan12xx.ko,wlan12xx_sdio.ko" from Fraux kernel to Amaze stock kernel modules folder.Flashed it.
then,i turned it on and the wifi turned off itself instantly without saying error
there was wifi error same here :
http://forum.xda-developers.com/showthread.php?t=1796358
thanks for your helps sir :good:
Click to expand...
Click to collapse
Did you try the fix permissions someone mentioned?
sent from a galaxy you'll never see.
Dark Nightmare said:
Did you try the fix permissions someone mentioned?
sent from a galaxy you'll never see.
Click to expand...
Click to collapse
yes.i did sir
now,i try to reverting to stock GB 2.3.4 again
i've call to a store near my house,they said that if amaze's wifi chip were as same as hd2's wifi chip,the cost would be about $35
ronaldinho_07 said:
yes.i did sir
now,i try to reverting to stock GB 2.3.4 again
i've call to a store near my house,they said that if amaze's wifi chip were as same as hd2's wifi chip,the cost would be about $35
Click to expand...
Click to collapse
Hmmm...doubt it's the same but ill Google the hardware to see if it's replaceable.
sent from a galaxy you'll never see.
Dark Nightmare said:
Did you try the fix permissions someone mentioned?
sent from a galaxy you'll never see.
Click to expand...
Click to collapse
Dark Nightmare said:
Hmmm...doubt it's the same but ill Google the hardware to see if it's replaceable.
sent from a galaxy you'll never see.
Click to expand...
Click to collapse
thanks so much
nice day sir,and i have to go to bed ,it's 3h40 AM in vietnam
//updated.
after flashing many times,problem solved
Necro'd.
Dark Nightmare said:
Hmmm...doubt it's the same but ill Google the hardware to see if it's replaceable.
Click to expand...
Click to collapse
Anyone have any info as to how or where to repair the wifi chip on the amaze? I'm having the same problem and am quite certain that is it hardware issue as the problem started after dropping the phone and without flashing or changing anything, fixing permissions and flashing stock RUU's, kernels, etc of no help. Hoping that something is possible, would be great if it was as simple as a loose ribbon cable...
Dark Nightmare said:
Did you try the fix permissions someone mentioned?
sent from a galaxy you'll never see.
Click to expand...
Click to collapse
Hello,
Here is my situation. I got S-off, SuperCID, unlocked on my HTC amaze unbranded version. Then got ICS stock RUU to run.
The wifi, bluetooth worked fine. However, I have to compile the kernel for this exact version (matched radio, baseband kernel, etc). I downloaded the source from HTCdev (the one with TI WLAN sources), and compiled it. Then I got the zImage repacked so that it can run on the device. Then I see that the wifi, bluetooth shows "error".
The kernel build "readme.txt" located me to the kernel object files such as wl12xx.ko. So I planned to push them in to the device with command "adb push wl12xx.ko /system/lib/modules" but failed. I got super user permission ("adb shell", "su") but still cannot get the kernel objects to the device with adb command. Is there a way to handle this?
My final objective is to get the compiled kernel (with no wifi, bluetooth error) running.
PS. Doesn't actually matter if it is GB or ICS.
Thank you in advance.
spencerjang said:
Hello,
Here is my situation. I got S-off, SuperCID, unlocked on my HTC amaze unbranded version. Then got ICS stock RUU to run.
The wifi, bluetooth worked fine. However, I have to compile the kernel for this exact version (matched radio, baseband kernel, etc). I downloaded the source from HTCdev (the one with TI WLAN sources), and compiled it. Then I got the zImage repacked so that it can run on the device. Then I see that the wifi, bluetooth shows "error".
The kernel build "readme.txt" located me to the kernel object files such as wl12xx.ko. So I planned to push them in to the device with command "adb push wl12xx.ko /system/lib/modules" but failed. I got super user permission ("adb shell", "su") but still cannot get the kernel objects to the device with adb command. Is there a way to handle this?
My final objective is to get the compiled kernel (with no wifi, bluetooth error) running.
PS. Doesn't actually matter if it is GB or ICS.
Thank you in advance.
Click to expand...
Click to collapse
It's easier if you swap the neccesary files with faux kernel zip and flash it from recovery or make your own flashable zip.. That way the modules and zimage get flashed without having to use adb
Sent from my HTC_Amaze_4G using XDA Premium 4 mobile app
ravike14 said:
It's easier if you swap the neccesary files with faux kernel zip and flash it from recovery or make your own flashable zip.. That way the modules and zimage get flashed without having to use adb
Sent from my HTC_Amaze_4G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Oh, I downloaded faux's kernel I believe version 31 (from a dropbox someone linked). and failed to flash from sd card! Any suggestions?
spencerjang said:
Oh, I downloaded faux's kernel I believe version 31 (from a dropbox someone linked). and failed to flash from sd card! Any suggestions?
Click to expand...
Click to collapse
Why it failed? The error?
Sent from my HTC_Amaze_4G using XDA Premium 4 mobile app
So... I realize there's multiple threads of people asking help on unbricking in general, but I accidentally re-locked the bootloader before flashing a stock kernel.
... Is this phone now a lost cause?
lolstebbo said:
So... I realize there's multiple threads of people asking help on unbricking in general, but I accidentally re-locked the bootloader before flashing a stock kernel.
... Is this phone now a lost cause?
Click to expand...
Click to collapse
Repair it with PC Companion or SEUS.
And why did you relock the bootloader???
SmG67 said:
Repair it with PC Companion or SEUS.
And why did you relock the bootloader???
Click to expand...
Click to collapse
It keeps giving me a "no software is available for your phone" message.
I meant to flash the stock kernel on it, but, for some reason, I brain farted and accidentally locked the bootloader.
lolstebbo said:
It keeps giving me a "no software is available for your phone" message.
I meant to flash the stock kernel on it, but, for some reason, I brain farted and accidentally locked the bootloader.
Click to expand...
Click to collapse
If you're on gingerbread or lower than you should be able to unlock it again with flashtool, as far as i'm aware. Try a stock firmware flashable with flashtool, there should be some available in the x10mini pro development section of this forum.
SmG67 said:
If you're on gingerbread or lower than you should be able to unlock it again with flashtool, as far as i'm aware. Try a stock firmware flashable with flashtool, there should be some available in the x10mini pro development section of this forum.
Click to expand...
Click to collapse
I can't even get Flashtool to recognize it, though; it was on MiniCM10 and nAa's kernel before the accident. I have the stock ROM and kernel ready, I just.... did the wrong step first on accident.
lolstebbo said:
I can't even get Flashtool to recognize it, though; it was on MiniCM10 and nAa's kernel before the accident. I have the stock ROM and kernel ready, I just.... did the wrong step first on accident.
Click to expand...
Click to collapse
You don't need to have it recognised in order to flash it... just put it in flashmode...
SmG67 said:
You don't need to have it recognised in order to flash it... just put it in flashmode...
Click to expand...
Click to collapse
It doesn't work; I can't even get to the bootloader unlock opinion. The "Plugins" drop-down menu is empty and fastboot gives me an error message when I try to flash anything.
I guess it's R.I.P for this phone?
lolstebbo said:
It doesn't work; I can't even get to the bootloader unlock opinion. The "Plugins" drop-down menu is empty and fastboot gives me an error message when I try to flash anything.
I guess it's R.I.P for this phone?
Click to expand...
Click to collapse
I hope you meant to say flashtool, and not fastboot? our phones don't support fastboot. Always choose flashmode...
The Plugins drop-down should be empty because the ROM you're on is unsupported for the unlock-plugin.
However, you should be able to flash the stock kernel, Hold on...
This should be flashable with flashtool. I can't guarantee that it will make your phone work properly, but it will give you back the stock kernel, and possible enable you to unlock your bootloader again, or at least enable you to flash the other firmware you had lying around...
SmG67 said:
I hope you meant to say flashtool, and not fastboot? our phones don't support fastboot. Always choose flashmode...
The Plugins drop-down should be empty because the ROM you're on is unsupported for the unlock-plugin.
However, you should be able to flash the stock kernel, Hold on...
This should be flashable with flashtool. I can't guarantee that it will make your phone work properly, but it will give you back the stock kernel, and possible enable you to unlock your bootloader again, or at least enable you to flash the other firmware you had lying around...
Click to expand...
Click to collapse
ohmygodiloveyousomuchrightnow. Thanks so much. It can boot up now, but nothing responds after it boots into the lock screen. Beats the phone being completely bricked, though.
lolstebbo said:
ohmygodiloveyousomuchrightnow. Thanks so much. It can boot up now, but nothing responds after it boots into the lock screen. Beats the phone being completely bricked, though.
Click to expand...
Click to collapse
The same thing happened to my xperia mini pro (U20a) when trying to update through SEUS and the software in the pc (PC companion) crashed by performing an illegal operation(Now it is no longer recognized by seus). This result my phone turning into a brick with only a big triangle with ! mark and a phone's picture was displayed on the screen when it turned on. I have never rooted the phone or installed Xrecovery/busybox (learned about them from this forum threads only). So I was anxiously following this thread and installed Flashtool and downloaded the ftf file (220MB) specified in this thread. Then voila, the flash was successful with this and the phone switched on. Now the second level of problem starts. None of the keys ( even the power key) or touch screen responds once the phone boots up.However the SIM is responding to the incoming calls (although cannot receive them as the touch screen is not operational). The battery is 100% charged and sim signal is 100% with sd card successfully mounted . Every time I need to remove the battery to switch it off. The display is now showing current date time (in a blue background) and a lock(left) and speaker (right) icons. Everything is stalled here. Downloaded two more firmwares and bundled them(sin files) in flash tool, but none worked except this fft file.
Please help
PS I have attached the flash tool log file for this flash.
To both of you: Try Repair with PC Companion.
1. Leave the phone unplugged
2. Start PC Companion
3. Choose Support Zone
4. Choose Update
5. It can find no update because your phone is unplugged
6. Click the Repair-link it shows
7. Follow the instructions from there on.
Hope that works, if not: Download this and flash with flashtool.
Thanx for the quick reply.
I have started the pc companion and go to the repair option. However after selecting the model from the list, it started updating. Then BANG!! Again the program performed an illegal operation and shutdown by the window XP.. The entire PC screen hanged and I had to manually kill it by pressing ALT+Ctrl+Del . So it seems this method will not work in my laptop.
Downloading your FTF file and trying it in flash tool. Hope it will work.:crying:
PS: your link is now pointing to the zip file and I have tried the UK version of that already ( by building the ftf from sin files in flash tool) with no improvement. Can you give a ftf file directly like the last one ? Thanx in advance.
bukaida said:
Thanx for the quick reply.
I have started the pc companion and go to the repair option. However after selecting the model from the list, it started updating. Then BANG!! Again the program performed an illegal operation and shutdown by the window XP.. The entire PC screen hanged and I had to manually kill it by pressing ALT+Ctrl+Del . So it seems this method will not work in my laptop.
Downloading your FTF file and trying it in flash tool. Hope it will work.:crying:
PS: your link is now pointing to the zip file and I have tried the UK version of that already ( by building the ftf from sin files in flash tool) with no improvement. Can you give a ftf file directly like the last one ? Thanx in advance.
Click to expand...
Click to collapse
No need to make it yourself, just rename the zip-file you download to .ftf and flash it.
SmG67 said:
No need to make it yourself, just rename the zip-file you download to .ftf and flash it.
Click to expand...
Click to collapse
Renamed the file from zip to ftf and put it inside the firmwares folder under flash tool. But during firmware selection while flashing, it is not showing anything ( only your earlier ftf file is visible). Am I doing something wrong?
bukaida said:
Renamed the file from zip to ftf and put it inside the firmwares folder under flash tool. But during firmware selection while flashing, it is not showing anything ( only your earlier ftf file is visible). Am I doing something wrong?
Click to expand...
Click to collapse
Possibly... Rename it to U20.ftf and see if it shows up in the list then
SmG67 said:
Possibly... Rename it to U20.ftf and see if it shows up in the list then
Click to expand...
Click to collapse
Renamed from original UK_2.1_minipro.zip to U20.ftf but still not visible in firmware list. Screenshot attached.
bukaida said:
Renamed from original UK_2.1_minipro.zip to U20.ftf but still not visible in firmware list. Screenshot attached.
Click to expand...
Click to collapse
Did you remove the other one you flashed earlier?
Not sure what's going wrong there, it should show up...
You did restart flashtool?
If you are still there
I removed and reinstalled the flash tool. Followed the procedure discussed so far. Still it is not showing in the list.Screen shot attached. The U20 option which is showing is for your earlier ftf file (kernel_locked) and not the renamed one (however if I bundle the sin files and create the ftf by specifying build number, version etc..) it is showing. However , flushing with that made no improvement. It took sometime to respond as I was trying these.
bukaida said:
I removed and reinstalled the flash tool. Followed the procedure discussed so far. Still it is not showing in the list.Screen shot attached. The U20 option which is showing is for your earlier ftf file (kernel_locked) and not the renamed one (however if I bundle the sin files and create the ftf by specifying build number, version etc..) it is showing. However , flushing with that made no improvement. It took sometime to respond as I was trying these.
Click to expand...
Click to collapse
Try this
SmG67 said:
Try this
Click to expand...
Click to collapse
My bandwidth for this month has ended. However I still have night unlimited facility. So I will download it at night. One more thing, when the download is handled by firefox, the file size is showing as 120 MB but in Internet Download manager, it is 213MB. What is the actual size ?
hi
i'm looking for working app for honor 7 for record calls, do you know about one without root?
thanks
Boldbeast call recoeder availabe on play store .auto record doesnt work you have to use it in manual mode see support page for honor 7 on their site
and there is something that works with auto record?
thank you
I7210I said:
and there is something that works with auto record?
thank you
Click to expand...
Click to collapse
As per my knowledge none for that you have to root then you can use huwaei s stock call rec. App but boldbeast is also good it records both way with good clarity
I7210I said:
and there is something that works with auto record?
thank you
Click to expand...
Click to collapse
Yes there is, but require you to change to Chinese Stock ROM ver PLK-TL00C01B388
I am currently using it now. Previously I was on Malaysia Stock Rom PLK-L01C636B371 then decided to flash over to chinese stock.
Amazingly this rom has the ability to have the automated call recorder and other nice build in function, such as Eye Comfort, App Twin etc.
Yes, Stock rom + no root = works. :highfive:
fiezwan said:
Yes there is, but require you to change to Chinese Stock ROM ver PLK-TL00C01B388
I am currently using it now. Previously I was on Malaysia Stock Rom PLK-L01C636B371 then decided to flash over to chinese stock.
Amazingly this rom has the ability to have the automated call recorder and other nice build in function, such as Eye Comfort, App Twin etc.
Yes, Stock rom + no root = works. :highfive:
Click to expand...
Click to collapse
do you have link for that please?
and also i will try the boldbeast too
I7210I said:
do you have link for that please?
and also i will try the boldbeast too
Click to expand...
Click to collapse
I use Huawei Firmware Finder to download the ROM (See attachment)
https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146
Then flash it like this step:
https://forum.xda-developers.com/honor-7/help/to-destroyed-ur-h7-noob-friendly-t3554793
* I used boldbeast before. yes, that one is the best and suitable to use. but can't do auto record, so end up i use this chinese rom
Good Luck! :highfive:
so it leaves only one option
fiezwan said:
I use Huawei Firmware Finder to download the ROM (See attachment)
https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146
Then flash it like this step:
https://forum.xda-developers.com/honor-7/help/to-destroyed-ur-h7-noob-friendly-t3554793
* I used boldbeast before. yes, that one is the best and suitable to use. but can't do auto record, so end up i use this chinese rom
Good Luck! :highfive:
Click to expand...
Click to collapse
where is the exact model i need to download rom for according to these pictures?
thank you
I7210I said:
where is the exact model i need to download rom for according to these pictures?
thank you
Click to expand...
Click to collapse
You need to click at "Common base" tab
Then find the model
Then click at the filelist to download the zip file
See attachment for reference
Hope this would help :highfive:
thank you,
what about the Huawai Update Extractor?need to download too?
also at the list it written 3.13GB and actually it's 1.6GB is it right?
I7210I said:
thank you,
what about the Huawai Update Extractor?need to download too?
also at the list it written 3.13GB and actually it's 1.6GB is it right?
Click to expand...
Click to collapse
I do not know why it contains bigger than usual, but for me, bigger files should be better.
Why would you wanted a 390 when there is 396 with latest security patch?
Anyway, I think you would want to have a look at my complete user-manual for changing the rom. (see attachment)
:highfive:
Hope this would help!
fiezwan said:
I do not know why it contains bigger than usual, but for me, bigger files should be better.
Why would you wanted a 390 when there is 396 with latest security patch?
Anyway, I think you would want to have a look at my complete user-manual for changing the rom. (see attachment)
:highfive:
Hope this would help!
Click to expand...
Click to collapse
the 390 i have now, which exact version do i need to search for??
also the extractor stuck at the cust file..is it OK!?
also attached how the unbrick folder looks now, it's ok?
and as i read at the other thread, there is instructions:
Type the following into the CMD window previously opend:
1- fastboot devices (should list up ur H7)
2- fastboot flash boot boot.img (flashes the Honor7 boot.img to the H7)
3- fastboot flash system system.img (flashes the system wich maybe corrupted)
4- fastboot flash recovery recovery.img (flashes the stock recovery and removes trwp)
5- fastboot reboot
is these is instead of the multi tool?it's easyer
I7210I said:
the 390 i have now, which exact version do i need to search for??
also the extractor stuck at the cust file..is it OK!?
also attached how the unbrick folder looks now, it's ok?
and as i read at the other thread, there is instructions:
Type the following into the CMD window previously opend:
1- fastboot devices (should list up ur H7)
2- fastboot flash boot boot.img (flashes the Honor7 boot.img to the H7)
3- fastboot flash system system.img (flashes the system wich maybe corrupted)
4- fastboot flash recovery recovery.img (flashes the stock recovery and removes trwp)
5- fastboot reboot
is these is instead of the multi tool?it's easyer
Click to expand...
Click to collapse
erm, if the extractor stuck as cust file, you can always re-extract it 1 more time. if it still fails, maybe the zip file is corrupted and you need to re-download again. otherwise, just choose different Stock zip file.
the other thread that you saw - asking you to type in those command in fastboot is also a correct way.
only the function of the multi-tool = you do not need to type in any commands. it will help you to do it. its the same thing.
both way will work. your choice.
have you not try it yet?
fiezwan said:
erm, if the extractor stuck as cust file, you can always re-extract it 1 more time. if it still fails, maybe the zip file is corrupted and you need to re-download again. otherwise, just choose different Stock zip file.
the other thread that you saw - asking you to type in those command in fastboot is also a correct way.
only the function of the multi-tool = you do not need to type in any commands. it will help you to do it. its the same thing.
both way will work. your choice.
have you not try it yet?
Click to expand...
Click to collapse
Did it before on Nexus , not on honor.
About the version , what exactly version do I need?
The 396 is the same as I have and not the Chinese one..
Thank you
Sent from my Nexus 6P using Tapatalk
I7210I said:
Did it before on Nexus , not on honor.
About the version , what exactly version do I need?
The 396 is the same as I have and not the Chinese one..
Thank you
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
If you need the automated call recorder build in - you need PLK-TL00C01B388 stock rom
and flash it either via multitool step by step like i provide before, or use fastboot command.
After using the method, your phone will change to chinese stock rom.
fiezwan said:
If you need the automated call recorder build in - you need PLK-TL00C01B388 stock rom
and flash it either via multitool step by step like i provide before, or use fastboot command.
After using the method, your phone will change to chinese stock rom.
Click to expand...
Click to collapse
thank you,
one last clearence, same languages in all the rom's correct?
and does the google apps will be the same after install these rom?
also the problem with the extraction of the cust persist even after few times of extracting maybe i need jsut to root and use call recorder by skvalex?
I7210I said:
thank you,
one last clearence, same languages in all the rom's correct?
and does the google apps will be the same after install these rom?
also the problem with the extraction of the cust persist even after few times of extracting maybe i need jsut to root and use call recorder by skvalex?
Click to expand...
Click to collapse
Language: You can choose English while setting the phone up
Google apps will not be there - due to their policy. However, there is always a work around. You need to download and install Google Play service + Google Contact in order to make it sync.
Please refer the line below for installing Google Play:
https://forum.xda-developers.com/showpost.php?p=57280942&postcount=4
one of the users at the device needs hebrew, is it available there?
thank you
I just replace my stock Europe ROM in Honor 7 with PLK-TL00C01B388. I don't have any problem so far. I don´t even lost my settings or data.
Is it here way how I can remove stock Huawei app like Browser, HiStudy, Phone Finder or HiWallet? Another question is about Yellow pages in Contact, how I can remove this?