Hi,
I have rooted my DHD with the [ROM] Android Revolution HD 3.1
http://forum.xda-developers.com/showthread.php?t=840040
Click to expand...
Click to collapse
It works fine.
Then, experimentally I try to overclock my DHD with the instruction from this website:
http://hemorrdroids.net/overclock-undervolt-your-desire-hd/
Click to expand...
Click to collapse
My DHD can be overclocked max. to 1,228 Ghz, but the wifi doesn't work
even after step 21 (and also factory reset), what should I do now?
Have I bricked my DHD (wifi)?
Thanx in advance.
Hi your problem his here
21) Wait for your DHD to reboot and then type the following into the command prompt on your PC -
adb push bcm4329.ko /sdcard/bcm4329.ko
adb shell
su (authorise root access on your device)
mount -o remount,rw /dev/block/mmcblk0p25 /system (that’s zero p twentyfive)
cat /sdcard/bcm4329.ko > /system/lib/modules/bcm4329.ko
Click to expand...
Click to collapse
Have you done exactly as is says?
It would be easier to download a Kernel from the Dev section and flash it from recovery, rather than fastboot, as the WiFi modules will be included in the Kernel.
Yes, I've done step 21 exactly as it says.
My DHD can be overclocked max. to 1,228 Ghz.
Should I install the other ROM?
http://forum.xda-developers.com/showthread.php?t=842802
or
http://forum.xda-developers.com/showthread.php?t=835616 ??
Actually I don't know surely, what you mean with
"download a Kernel from the Dev section"
"flash it from recovery, rather than fastboot"
What is Kernel? Have I changed the kernel, when I rooted my DHD?
I'm just newbie in this case.
Thanks for your fast reply.
When you flash a kernel via fastboot chances are it will break the WiFi module.
You "push" a new module via adb to fix WiFi, that is step 21.
If you look in the Dev section there are threads for kernels that allow overclocking, these are flashed from recovery (ClockworkMod). When these kernels are flashed it will include the required WiFi module.
You obviously flashed a ROM via recovery, and its the same process for flashing a kernel.
No you didn't change your kernel while rooting, you changed your kernel when you followed step 19.
19) Type the following into the command prompt on your PC -
fastboot flash zimage zImage
This should upload a file to you DHD and flash it over the original.
Click to expand...
Click to collapse
What's a Kernel?
andyharney said:
When you flash a kernel via fastboot chances are it will break the WiFi module.
You "push" a new module via adb to fix WiFi, that is step 21.
If you look in the Dev section there are threads for kernels that allow overclocking, these are flashed from recovery (ClockworkMod). When these kernels are flashed it will include the required WiFi module.
You obviously flashed a ROM via recovery, and its the same process for flashing a kernel.
No you didn't change your kernel while rooting, you changed your kernel when you followed step 19.
What's a Kernel?
Click to expand...
Click to collapse
hmm.. what should I do now?
Should I get the other ROM [and Kernel]?
http://forum.xda-developers.com/showthread.php?t=842802
At least, now I know, that I didn't break the wifi, right?
Hi,
I have flashed the kernel with this tool:
http://forum.xda-developers.com/showthread.php?t=852357
The wifi still doesn't work at all...
Anybody can give me a solution?
It would be nice.
BR.
Ok, are you pushing the WiFi module after your handset has rebooted?
Save yourself a lot of grief by downloading THIS KERNEL and flashing it via Recovery.
andyharney said:
Ok, are you pushing the WiFi module after your handset has rebooted?
Click to expand...
Click to collapse
You mean the step 21?
I will try it again.
Save yourself a lot of grief by downloading THIS KERNEL and flashing it via Recovery.
Click to expand...
Click to collapse
How can I flash the kernel via recovery?
When I do it with this tool: http://forum.xda-developers.com/showthread.php?t=852357,
that means I flash by fastboot, doesn't it?
I've just flashed Revolution 3.2 and using Set CPU, my Wifi is also dead....
What does a kernel actually change?
andyharney said:
Ok, are you pushing the WiFi module after your handset has rebooted?
Save yourself a lot of grief by downloading THIS KERNEL and flashing it via Recovery.
Click to expand...
Click to collapse
I've tried this and wifi is still dead.
Would wiping then reflashing the revolution 3.2 rom do anything?
edit: seemed resetting my router worked, stupidly!
Related
To make things easier here is a link to BRD's update to 3.1 I suggest you check it out for an easy upgrade to 3.1.
http://forum.xda-developers.com/showthread.php?t=1074609
If you are already on 3.1 just flash the stock HRI66 system image and Tiamats boot image to get sd card support back from there you should be able to run BRDs update from the SD card in clockwork
I did this using CWR on a rooted Xoom
1. Copy the update to your sdcard and name it update.zip
2. Then you must flash the HRI66 stock boot and system imgs. No data is lost
3. After flashing through fastboot go directly to CWR and install update.zip from SD card
4. Then back to fastboot and flash the root31.img to your boot partion (link below)
5. Then reboot your xoom and push su using koush's original root instructions and you are rooted running 3.1
6. You can then use rom manager to reflash CWR.
Link to post with root31.img
http://forum.xda-developers.com/showthread.php?t=1073298
Other files easily found on xda
Just have to wait for an updated kernel to has sdcard support back.
All credit goes to the people that did the actual work I'm just listing instructions. And of course you assume all risk in flashing and modding your device.
Sent from my Xoom using my Xoom
After using this method to update, could we re-flash a custom kernel (such as Tiamat 1.4.1) - or would that be incompatible for some reasonn with the 3.1 update?
Nice find/tutorial... this may be what many of us have been waiting for. Me, personally, I am waiting for a flashable .zip one-step update process. I maintain hope that it'll happen =)
Sent from my Xoom using Tapatalk
dch921 said:
6. You can then use rom manager to reflash CWR.
Click to expand...
Click to collapse
Just use fastboot. That's what it's there for.
JFMFT said:
After using this method to update, could we re-flash a custom kernel (such as Tiamat 1.4.1) - or would that be incompatible for some reasonn with the 3.1 update?
Nice find/tutorial... this may be what many of us have been waiting for. Me, personally, I am waiting for a flashable .zip one-step update process. I maintain hope that it'll happen =)
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
Haven't tried it but worse case scenario just reflash root31.img
Sent from my Xoom using my Xoom
Nice! It worked perfectly!
I tried flashing Tiamat 1.4.1, wouldn't recommend it, you'll have to go right back to stock.
I am doing this right now on my XOOM. I will update this post when I am done.
Thank you for the instructions
EDIT: works perfectly!!
Got confused at first and followed the whole guide to originally root...but then realized that you do not flash rootboot.img.
Only do the following code:
1. adb remount
2. adb push su /system/bin
3. adb shell
4. ln –s /system/bin/su /system/xbin/su
5. chmod 4755 /system/bin/su
6. exit
7. adb push Superuser.apk /system/app
Click to expand...
Click to collapse
props worked great
Cansay that this worked great. I love the update and I love keeping my root. The device is running smoothly with the stock 3.1. Good post indeed.
Sent from my Xoom using Tapatalk
So a custom boot.img is a no go? Is this because of the different kernel or the (possibly different) initrd... for those that are confused by this question - remember a boot.img is comprised of the ramdisk and the kernel.
2. Then you must flash the HRI66 stock boot and system imgs. No data is lost
3. After flashing through fastboot go directly to CWR and install update.zip from SD card
Click to expand...
Click to collapse
How is step 3 possible? Every time I do step 2 I lose root (loading stock boot.img), and thus can't open CWR? Is there a way to get to CWR and install update.zip without root? I'm using it by going into recovery via an app.
sooner2k1 said:
How is step 3 possible? Every time I do step 2 I lose root (loading stock boot.img), and thus can't open CWR? Is there a way to get to CWR and install update.zip without root? I'm using it by going into recovery via an app.
Click to expand...
Click to collapse
This instruction is very unclear...
Blades said:
So a custom boot.img is a no go? Is this because of the different kernel or the (possibly different) initrd... for those that are confused by this question - remember a boot.img is comprised of the ramdisk and the kernel.
Click to expand...
Click to collapse
Of course not. You can have a ramdisk with ro.secure 0 and the stock kernel, or you can use any kernel you like that will run.
(IMO, it's better to root with as small a change as needed, and if you want to use a different kernel, you can do so if you want separate to the decision of wanting root)
sooner2k1 said:
How is step 3 possible? Every time I do step 2 I lose root (loading stock boot.img), and thus can't open CWR? Is there a way to get to CWR and install update.zip without root? I'm using it by going into recovery via an app.
Click to expand...
Click to collapse
Again, just use fastboot (because it's unlocked), then reboot into recovery. Does that not work?
ljwnow said:
This instruction is very unclear...
Click to expand...
Click to collapse
No its pretty simple you must not know what your doing
sooner2k1 said:
How is step 3 possible? Every time I do step 2 I lose root (loading stock boot.img), and thus can't open CWR? Is there a way to get to CWR and install update.zip without root? I'm using it by going into recovery via an app.
Click to expand...
Click to collapse
after you flashing boot.img and HRI66 system.img, type this in cmd, fastboot reboot
xoom will reboot to normal mode, then wait untill it completly settle to home screen, it will take sometime (it seems like bootloop but it does not, HC doing re-dalvik cache, so it takes time)..after it boot to normal mode type this in cmd, adb reboot recovery
you will reboot to cwm recovery (i'm guessing you have flash cmw before on 3.0.1) then follow the OP steps..
i'm on 3.1 now.. with no data loose and rooted ;-)
I am just wondering if sd card support is still there after the update (I am using tiamat kernel). Thanks
wsuo2006 said:
I am just wondering if sd card support is still there after the update (I am using tiamat kernel). Thanks
Click to expand...
Click to collapse
No sdcard support until we get a new kernel
Sent from my Xoom using my Xoom
I was wondering if anyone could package the stock 3.0.1 kernel and system.img into an update.zip so this can all be done using rom manager? Thinking about it most likely not cause moto has been pulling system dump images
Sent from my Xoom using XDA Premium App
dch921, would it be possible for you to please add the relevant links to your OP instead of saying to search XDA for them? If you do this, I will gladly sticky this guide.
Thanks!
Hello Everyone!
Two days before, I tried to install some costume ROM into my Galaxy W, but i wasn't successful. I had to flash with Odin.
In today, i decided to install a costume ROM all means. I have a stock rom 2.3.6. I do the rooting, after with odin i flashed the CWM. I put the selected rom into my sdcard, and with the CWM i started the install. The phone wrote, the install was succesfull, so i was very happy.
I did a reboot, and wait for the magic... but nothing. It wrote the samsung logo, after wrote the galaxy W logo, and freeze. I thougt it just installing itself, so i left back. Half hour after nothing, so i must used odin again, and install the stock rom. What do you change that, that I could install costum ROM? What problems am I doing?
To make things simpler flash stock ROM 2.3.5 as .6 can no longet be rooted.
Once ur have restored to .5 root it n flash CWM n flash ur desired ROM....
Sent from my GT-I8150 using xda premium
So i need to get a stock 2.3.5 ROM, and after do everything again? Where can i get that ROM?
It's interesting, becouse i can root my 2.3.6. I have a superuser icon, so i don't know!
To7aL said:
So i need to get a stock 2.3.5 ROM, and after do everything again? Where can i get that ROM?
It's interesting, becouse i can root my 2.3.6. I have a superuser icon, so i don't know!
Click to expand...
Click to collapse
2.3.6 can be rooted. I have rooted mine. But the only 'recovery method' will root it.
---------- Post added at 06:46 PM ---------- Previous post was at 06:43 PM ----------
To7aL said:
Hello Everyone!
Two days before, I tried to install some costume ROM into my Galaxy W, but i wasn't successful. I had to flash with Odin.
In today, i decided to install a costume ROM all means. I have a stock rom 2.3.6. I do the rooting, after with odin i flashed the CWM. I put the selected rom into my sdcard, and with the CWM i started the install. The phone wrote, the install was succesfull, so i was very happy.
I did a reboot, and wait for the magic... but nothing. It wrote the samsung logo, after wrote the galaxy W logo, and freeze. I thougt it just installing itself, so i left back. Half hour after nothing, so i must used odin again, and install the stock rom. What do you change that, that I could install costum ROM? What problems am I doing?
Click to expand...
Click to collapse
Did you wipe the phone through CWM before flashing the custom ROM ?
alidsd said:
2.3.6 can be rooted. I have rooted mine. But the only 'recovery method' will root it.
---------- Post added at 06:46 PM ---------- Previous post was at 06:43 PM ----------
Did you wipe the phone through CWM before flashing the custom ROM ?
Click to expand...
Click to collapse
Ehhhhh! not really....
2.3.6 can be rooted with SuperOneClick.....
I did it with my 2.3.6, after flashing new Stock ROM, lost root, but re-rooted with SOC, on this 2.3.6.......
EDIT: flashed this with ODIN
Phone: I8150XXKK1
PDA: I8150XXKK1
CSC: I8150OXXKJ6
but I acknowledge it does not work on all ROM's
The order I did:
1.) Root my phone like this: http://forum.xda-developers.com/showthread.php?t=1317394
2.) Flash the CWM with Odin
3.) Wipe all with CWM
4.) Select the .zip file, and install it. (http://forum.xda-developers.com/showthread.php?t=1441662)
5.) Reboot my phone after finish
6.) Wait for booting, but freeze at Galaxy W logo
I have: 2.3.6 | I8150XXKK1
BRB...Be rite back google sammobile.com there is a 2.3.5 FW
Sent from my GT-I8150 using xda premium
BRB? What means?
To7aL said:
BRB? What means?
Click to expand...
Click to collapse
Above you....
Sent from my GT-I8150 using xda premium
To7aL said:
The order I did:
1.) Root my phone like this: http://forum.xda-developers.com/showthread.php?t=1317394
2.) Flash the CWM with Odin
3.) Wipe all with CWM
4.) Select the .zip file, and install it. (http://forum.xda-developers.com/showthread.php?t=1441662)
5.) Reboot my phone after finish
6.) Wait for booting, but freeze at Galaxy W logo
I have: 2.3.6 | I8150XXKK1
Click to expand...
Click to collapse
OH you used OC ROM........
you check this in post: http://forum.xda-developers.com/showthread.php?t=1441662
*Disclaimer*: OC may break your phone!
Recommend to use SetCPU set your default speed to 1.4Ghz. Adjust to 1.8Ghz only when necessary. Also it is recommended to set a Profile that will lower the speed in temp > 50C, you know, just in case.
OC is very hardware dependant. If you cannot boot or experience crash too often, this is not for you. Get this non-OC ROM instead.
Faster = use more power = more heat = less battery! Let me know how's the battery is like.
OC code was modified and compiled by a friend...
Click to expand...
Click to collapse
Try this rom bro..it's a non OC kernel but with .35 its more stable I say..
http://forum.xda-developers.com/showthread.php?t=1438452
To7aL said:
The order I did:
1.) Root my phone like this: http://forum.xda-developers.com/showthread.php?t=1317394
2.) Flash the CWM with Odin
3.) Wipe all with CWM
4.) Select the .zip file, and install it. (http://forum.xda-developers.com/showthread.php?t=1441662)
5.) Reboot my phone after finish
6.) Wait for booting, but freeze at Galaxy W logo
I have: 2.3.6 | I8150XXKK1
Click to expand...
Click to collapse
Hey,
You are doing all the required steps but i think you didn't read the ROM's posts.
I think whenever anybody uses a custom ROM he should read the relevent Rom's post.
Your problem is already there and here is the solution :
http://forum.xda-developers.com/showpost.php?p=22087263&postcount=291
And, can I just add......if you use:
Code:
adb shell
su
dd if=/sdcard/download/boot.img of=/dev/block/mmcblk0p8
to flash boot.img........
Be careful, Please, Please....with dd command.....it is not called Data Destroyer for nothing
see here, already 1 Brick:
http://forum.xda-developers.com/showthread.php?t=1474191
irishpancake said:
And, can I just add......if you use:
Code:
adb shell
su
dd if=/sdcard/download/boot.img of=/dev/block/mmcblk0p8
to flash boot.img........
Be careful, Please, Please....with dd command.....it is not called Data Destroyer for nothing
see here, already 1 Brick:
http://forum.xda-developers.com/showthread.php?t=1474191
Click to expand...
Click to collapse
You are right @irishpancake, he need to take special care if this is the only way to flash kernel.
i think there should be a safest method for this. I used to use fastboot for this, or there used to be a Android Flasher for this purpose and the chances to brick the device was near to 1%.
i used to do like that : fastboot flash boot boot.img
Cann't Odin do that ?, keep in mind i am new to Samsung
With the non-OC kernel, i can easily install the rom... yeah!
I installed that: http://forum.xda-developers.com/showthread.php?t=1438452 but my mobilenet don't work... Need i set up somehow? When i installed the stock rom, i did't do anything, but my 3g were worked.
To7aL said:
With the non-OC kernel, i can easily install the rom... yeah!
I installed that: http://forum.xda-developers.com/showthread.php?t=1438452 but my mobilenet don't work... Need i set up somehow? When i installed the stock rom, i did't do anything, but my 3g were worked.
Click to expand...
Click to collapse
Check under "Settings" > "Wi-fi and network" > "Mobile networks". If "Use packet data" is unchecked, then that's your problem and unchecking it should solve it. If it is already checked or if you checked it and 3g still doesn't work, you should contact the dev.
To7aL said:
With the non-OC kernel, i can easily install the rom... yeah!
I installed that: http://forum.xda-developers.com/showthread.php?t=1438452 but my mobilenet don't work... Need i set up somehow? When i installed the stock rom, i did't do anything, but my 3g were worked.
Click to expand...
Click to collapse
u have to setup ur APN manually....or u can ask from ur carrier to send a network configuration by sms,etc..
I was trying to switch from elementalx to franco kernel t give it a try but little ol' me went into franco's kernel app and pressed install within the app while I was still on Elementalx kernel. So now my phone is stuck in a bootloop and I don't have my usb c adapter with me until this Saturday. Anyways, does anyone know if it's possible to unbrick my device without having to connect to a computer? Thanks.
Dirty flashing your ROM might do the job. Or restoring kernel backup if applicable.
Unfortunately I didn't make a backup. I'm on stock rom so I'm not sure how that would work either.
I guess you have system root which is not compatible with franco. So you would need to unroot or flash a kernel with the right sepolicy.
If you have flashed TWRP on your device, it's possible; otherwise no
LeoYL said:
If you have flashed TWRP on your device, it's possible; otherwise no
Click to expand...
Click to collapse
How so? Also, I used Heisenberg's root guide, no systemless.
If my guess is right and su is the Problem you could have a look at this post and try to do what the updater script (in the attachment) does manually via the terminal in TWRP (or in ist filemanager)
http://forum.xda-developers.com/showpost.php?p=63615067
ROM for Sony Smartwatch 3 [LCA43, Android 5.1.1]
ROM Features:
Stock LCA43 base
Disabled OTA updates
Custom Kernel tetra_2.x
TWRP recovery
Tweaks
Click to expand...
Click to collapse
Versions
v 2.0
Kernel tetra_2.27.1
Minor tweaks
v 1.0
Stock LCA43 base
Kernel tetra_2.22
Disabled Low Bit Ambient Mode (thanks to andrewia)
Minor tweaks
Click to expand...
Click to collapse
Installation:
Put ROM to your virtual SDCard
Boot into TWRP recovery
Select "Install", and choose ROM zip file
After installation completed- reboot watch
If necessary - make full wipe
Click to expand...
Click to collapse
Downloads
SW3_rom_v2
TWRP recovery
Click to expand...
Click to collapse
Big thanks to scrubber for his ROM backup!
Code:
[COLOR="Red"]DISCLAMER[/COLOR]
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or
you getting fired because the alarm app failed. Please do some research if you
have any concerns about features included in this ROM before flashing it!
YOU are choosing to make these modifications, and if you point the finger
at me for messing up your device, I will laugh at you.
If you like my work- Donate to me
Contributors:
alex6600
scrubber
Version Information
Status: Stable
Created 2016-04-27
Last Updated 2016-05-11
Reserved by OP
thanks alex6600.
can you upload original kernel to ?
edit : found on 4pda https://mega.nz/#!Rt8hBS5T!MHOufeqXYJqrcShyXG2_f3uLO7_ZlP_H6T0cVm0R4Hk
thanks again.
Thanks @alex6600!
Just factory reset, and downgraded from Marshmallow, to this ROM.
All is working well so far!
crunchybutternut said:
Thanks @alex6600!
Just factory reset, and downgraded from Marshmallow, to this ROM.
Click to expand...
Click to collapse
I honestly tried to use Marshmallow. Compiles kernels dozens of times. But no luck.
Reboots and lags does not suit me.
And decides to use 5.1.1, as more stable.
I'm all about this ROM as Marshmallow has just been one big rebooting mess!
However, during flashing everything went fine except the build.prop install...
Your line:
mount("ext4", "EMMC", "/dev/block/platform/sdhci.1/by-name/system", "/system", "max_batch_time=0,commit=1,data=ordered,barrier=1,errors=panic,nodelalloc");
Click to expand...
Click to collapse
Fails saying device is busy, or is not ready...???
Hobbzey said:
I'm all about this ROM as Marshmallow has just been one big rebooting mess!
However, during flashing everything went fine except the build.prop install...
Your line:
Fails saying device is busy, or is not ready...???
Click to expand...
Click to collapse
Did you mount system in twrp before install?
Sent from my HTC One_M8 using XDA-Developers mobile app
I got it sorted out actually, turns out it was because I was using the version of TWRP I got from here:
http://forum.xda-developers.com/sma...24h-twrp-root-busybox-kernel-adiutor-t3365990
I initially skipped installing the one you provided above because I already had that one installed, but switched to the one you provided and reflashed with no errors!
One last question, is it possible to turn off the rounded screen corners? Is that something that can be edited into the build.prop or is it in kernel?
Hobbzey said:
I got it sorted out actually, turns out it was because I was using the version of TWRP I got from here:
http://forum.xda-developers.com/sma...24h-twrp-root-busybox-kernel-adiutor-t3365990
I initially skipped installing the one you provided above because I already had that one installed, but switched to the one you provided and reflashed with no errors!
One last question, is it possible to turn off the rounded screen corners? Is that something that can be edited into the build.prop or is it in kernel?
Click to expand...
Click to collapse
Rounded screen corners is a kernel feature, not ROM.
And do you recommend your LCA43 kernel from here http://forum.xda-developers.com/sma...ment/kernel-sony-smartwatch-3-kernel-t3304102 or should we stick with the one already in the rom? Or are they one and the same?
Hobbzey said:
And do you recommend your LCA43 kernel from here http://forum.xda-developers.com/sma...ment/kernel-sony-smartwatch-3-kernel-t3304102 or should we stick with the one already in the rom? Or are they one and the same?
Click to expand...
Click to collapse
Rom include kernel v. 2.22.
Today I posted 2.23 in kernel thread.
Sent from my HTC One_M8 using XDA-Developers mobile app
Hi everyone, could someone please help me? I'm trying to downgrade my SW3 from MM to this rom, but I don't know how to do it. I've got installed windroid toolkit but it doesn't anything. I can't install twrp, unlock bootloader... nothing. I've got correctly installed ADB drivers, windroid recognises my watch, but this is everything I can do until here. I'm trying to do the downgrade because my battery flies twice per day, meanwhile in MM battery lasted up to 4 days... Has someone the same problem?
asecob said:
Hi everyone, could someone please help me? I'm trying to downgrade my SW3 from MM to this rom, but I don't know how to do it. I've got installed windroid toolkit but it doesn't anything. I can't install twrp, unlock bootloader... nothing. I've got correctly installed ADB drivers, windroid recognises my watch, but this is everything I can do until here. I'm trying to do the downgrade because my battery flies twice per day, meanwhile in MM battery lasted up to 4 days... Has someone the same problem?
Click to expand...
Click to collapse
Reboot to Fastboot, and flash the TWRP .img from there. (note: be sure you are in the directory where the twrp.img file is stored)
Code:
adb reboot bootloader
fastboot flash boot [I]twrp.img[/I]
fastboot reboot
adb reboot recovery
And viola. You can then flash this ROM.
Do you plan feature 6.0.1 update? What are benefits over stock...?
crunchybutternut said:
Reboot to Fastboot, and flash the TWRP .img from there. (note: be sure you are in the directory where the twrp.img file is stored)
Code:
adb reboot bootloader
fastboot flash boot [I]twrp.img[/I]
fastboot reboot
adb reboot recovery
And viola. You can then flash this ROM.
Click to expand...
Click to collapse
Thank you for your help, but unfortunately my watch didn't pass the white screen saying fastboot. PC was saying "waiting for device" for so much time. Am I doing something wrong?
crunchybutternut said:
Reboot to Fastboot, and flash the TWRP .img from there. (note: be sure you are in the directory where the twrp.img file is stored)
Code:
adb reboot bootloader
fastboot flash boot [I]twrp.img[/I]
fastboot reboot
adb reboot recovery
And viola. You can then flash this ROM.
Click to expand...
Click to collapse
Hello and thanks for the command lines.
I want to try it because my battery drain is too high with MM and kernel 3.10.1 (but no reboots).
But .... How can I use the virtual SDCARD? How do I have to do to put the zip file in this SD? AFter, I think it will be ok....
Thanks.
It's OK actually, just after twrp flash, I have "VIRTUAL SDCARD" on my windows pc, I put the zip and I flashed it in recovery.
Thanks
mickael91210 said:
Hello and thanks for the command lines.
I want to try it because my battery drain is too high with MM and kernel 3.10.1 (but no reboots).
But .... How can I use the virtual SDCARD? How do I have to do to put the zip file in this SD? AFter, I think it will be ok....
Thanks.
Click to expand...
Click to collapse
When the watch is connected to computer, type:
adb push rom_file.zip /sdcard/Download/
This command will copy ROM to /sdcard/Download directory.
alex6600 said:
When the watch is connected to computer, type:
adb push rom_file.zip /sdcard/Download/
This command will copy ROM to /sdcard/Download directory.
Click to expand...
Click to collapse
Thanks.... I was editing my post in the same time....
Thank you
More excellent work! Will we be able to root this (i.e. flash supersu.zip in TWRP)? Also, I can't seem to access the files (ROM.zip, TWRP.img), is the site down?
KittenSauce said:
More excellent work! Will we be able to root this (i.e. flash supersu.zip in TWRP)? Also, I can't seem to access the files (ROM.zip, TWRP.img), is the site down?
Click to expand...
Click to collapse
Webserver was in the planned maintenance. Now everything is working as it should.
SuperSu work fine. You can download SuperSu_2.46 here
I want to boot rooted kitkat 4.4 (tft) for getting the root function but every time i flash and boot it i getting in a wipe and the boot loading appears again and again.
what is the problem? I mentioned that after every boot the old data dont get deleted . maybe the old data is the problem. how can i delete everything like the partition?
moby.dog said:
I want to boot rooted kitkat 4.4 (tft) for getting the root function but every time i flash and boot it i getting in a wipe and the boot loading appears again and again.
what is the problem? I mentioned that after every boot the old data dont get deleted . maybe the old data is the problem. how can i delete everything like the partition?
Click to expand...
Click to collapse
How did you get a rooted ftf? I think that might be the problem. Unless you mean a prf... Best way to root KK is just flash stock ROM and use doomlord rootkit.
levone1 said:
How did you get a rooted ftf? I think that might be the problem. Unless you mean a prf... Best way to root KK is just flash stock ROM and use doomlord rootkit.
Click to expand...
Click to collapse
what is a prf?
Well probably i dont mean a rooted tft but that is what the guy in the guide was talking about but i also tryed a normal stock rom 4.4 and got the same problem, that my loading screen was repeating the whole time
how can i delete the partition?
moby.dog said:
what is a prf?
Well probably i dont mean a rooted tft but that is what the guy in the guide was talking about but i also tryed a normal stock rom 4.4 and got the same problem, that my loading screen was repeating the whole time
how can i delete the partition?
Click to expand...
Click to collapse
Are you using Flashtool or recovery? If you can get into recovery, just use 'wipe' option.
levone1 said:
Are you using Flashtool or recovery? If you can get into recovery, just use 'wipe' option.
Click to expand...
Click to collapse
no i dont get into recovery because i cant boot 4.4
moby.dog said:
no i dont get into recovery because i cant boot 4.4
Click to expand...
Click to collapse
If you want to be on 4.4, use Flashtool and flash a stock 4.4 ftf, then root with Doomlord. If you want to be on LP, use Emma, it will download and flash firmware for you.
Flashtool - http://www.flashtool.net/index.php
Emma - https://developer.sonymobile.com/open-devices/flash-tool/how-to-download-and-install-the-flash-tool/
KK ftf - https://forum.xda-developers.com/so...f-xperia-z1-compact-d5503-14-4-0-157-t3118047
how i described .. 4.4 is not loading after flashing! Doesnt matter which kind of 4.4
so i ask how can i delete everything?? bcs i think its matter of some data that still on my smartphone
moby.dog said:
how i described .. 4.4 is not loading after flashing! Doesnt matter which kind of 4.4
so i ask how can i delete everything?? bcs i think its matter of some data that still on my smartphone
Click to expand...
Click to collapse
When you flash with Flashtool, there is a box that says 'wipe'. Check the 'userdata' option.
thanks that worked!
When i do it like here with doom: https://forum.xda-developers.com/showthread.php?t=2620794
i cant boot after booting the boot.img
moby.dog said:
thanks that worked!
When i do it like here with doom: https://forum.xda-developers.com/showthread.php?t=2620794
i cant boot after booting the boot.img
Click to expand...
Click to collapse
Did you unlock bootloader? KK version 442 or 443? Add debugging enabled in settings? If all yes, I'm not sure why it wouldn't work. You could try different options, there are a few for KK - pimped kernel, Great devs kernel, and you could root with easy rootkit.
BTW - to restore your phone without flashing whole ROM again, check boxes under 'exclude' options for everything but kernel.
levone1 said:
KK version 442 or 443?
Click to expand...
Click to collapse
That version which you posted. 14.4.A.0.157
Bootloader is unlocked.
Usb Debugging is enable.
Is it the right doom version for my tft ? Can you please show me which doomversion i should boot? Because that one i showed you couldnt boot.
moby.dog said:
That version which you posted. 14.4.A.0.157
Bootloader is unlocked.
Usb Debugging is enable.
Is it the right doom version for my tft ? Can you please show me which doomversion i should boot? Because that one i showed you couldnt boot.
Click to expand...
Click to collapse
https://forum.xda-developers.com/showthread.php?t=2784900
I installed succesfully EasyRootTool v12.4 then i tried to install the lockeddualrecovery 2.8.26 choosed 2. and it tells me "Installation failed!"
Step 3: Setup of dual recovery. /system/bin/sh: su: not found
and this thing all the time: "adb server is out of date. killing..."
moby.dog said:
I installed succesfully EasyRootTool v12.4 then i tried to install the lockeddualrecovery 2.8.26 choosed 2. and it tells me "Installation failed!"
Step 3: Setup of dual recovery. /system/bin/sh: su: not found
and this thing all the time: "adb server is out of date. killing..."
Click to expand...
Click to collapse
Do you have root access when you turn on the phone? Did you make sure USB debugging is enable in settings, and also check 'allow USB debugging' pop-up when you connect to computer? If yes to all, just restart computer and/or phone, and reconnect and try again. XZDR is solid. If you have root, it will work. BTW - is bootloader unlocked or locked?
levone1 said:
Do you have root access when you turn on the phone? Did you make sure USB debugging is enable in settings, and also check 'allow USB debugging' pop-up when you connect to computer? If yes to all, just restart computer and/or phone, and reconnect and try again. XZDR is solid. If you have root, it will work. BTW - is bootloader unlocked or locked?
Click to expand...
Click to collapse
Bootloader unlocked: Yes
Rooting status: "here is nothing" i guess not
i restared everything still not work but i guess its because i dont get the root acces thats my main problem when should i have got it ?
Another Idea: When i install the EasyRootTool v12.4 it ends with "creating vm <loljavasucks>" is that what it supposed to write when its finished? When i keep that Easyroot window open and start the dual recovery installation, the easyroot tells me "done, checking if device is rooted... error: its not"
So i guess the problem is that i still not rooted my device but i thought that is what i am actually trying to do with easyroot..?
moby.dog said:
Bootloader unlocked: Yes
Rooting status: "here is nothing" i guess not
i restared everything still not work but i guess its because i dont get the root acces thats my main problem when should i have got it ?
Another Idea: When i install the EasyRootTool v12.4 it ends with "creating vm <loljavasucks>" is that what it supposed to write when its finished? When i keep that Easyroot window open and start the dual recovery installation, the easyroot tells me "done, checking if device is rooted... error: its not"
So i guess the problem is that i still not rooted my device but i thought that is what i am actually trying to do with easyroot..?
Click to expand...
Click to collapse
Ok, try this - download this zip https://mega.nz/#!lh9i0AYI!iH3Vw5keSNo66CHvq3c6V9HMCWAWJ5FIYcZZ35U254g It contains 2 files, one is a kernel and one is a recovery. Also download supersu 246 zip from here https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip?retrieve_file=1 and put it on your phone somewhere. Then connect in fastboot mode and flash the 2 IMG files:
'fastboot flash boot [name of kernel file].img'
'fastboot flash recovery [name of recovery file].img'
Then unplug and power on. When you see colored led, press volume key and you should get into recovery. When in recovery, flash supersu zip. Then power off, and connect in flash mode. Open Flashtool and flash the stock kernel from your ftf. Reboot and you should be rooted.
Thanks that worked! And now i flash the 4.4 stockrom and after that a prerooted version?
moby.dog said:
Thanks that worked! Can i flash the latest stockrom now?
Click to expand...
Click to collapse
You can flash whatever you want now. If you want stock 5.1, you can use Flashtool / Xperifirm to download ftf and flash, or use Emma. You will lose root, but you can get it back the same way you just did. If you want to root 5.1 that way, you can extract boot img from advanced kernel and download latest twrp img, and just fastboot those, and no need to reflash stock kernel afterwards.
Advanced kernel - https://forum.xda-developers.com/so...rnel-advanced-14-5-0-242-kernel-v1-0-t3096060
Twrp 3 for Z1c - https://www.androidfilehost.com/?fid=529152257862711713
Alternately, you could flash a prf, or any custom ROM you want
Ah okay i will try do you know how i can change my Lockbutton with my autofocus button? my lockbutton is broken and i never used the autofocus button before
edit: its actually dont worked after i booted kitkat again i lost my root and recovery mode its like i can only have the recovery mode or unrooted stock..
moby.dog said:
Ah okay i will try do you know how i can change my Lockbutton with my autofocus button? my lockbutton is broken and i never used the autofocus button before
edit: its actually dont worked after i booted kitkat again i lost my root and recovery mode its like i can only have the recovery mode or unrooted stock..
Click to expand...
Click to collapse
What did you flash?