Related
i am noob here, so i need a little help.
after reading many guides and watching videos, i rooted my htc evo 3d gsm using htcdev method.
flashed clockworldmod recovery v 5.0.2.0
installed supersu v1.30
now my phone is unlocked with s-on
i did a nandroid backup
tried to install a custom rom by wipping all 3 datas
installed this rom
http://forum.xda-developers.com/showthread.php?t=2161968
but nothing happened.
i m still running the stock rom.
I found these instructions but couldnt understand them
Code:
- Extract boot.img from zip and put into your folden when you have fastboot.
- Put rom into sd
- Full wipe from recovery
- Flash rom
- Flash boot.img with an erase cache before and after boot flash
can anyone help me plz
thanx in advance
The easiest method available is to flash 4EXT recovery and turn on smartflash in options. this way you wont need to flash boot.img every time you install a rom.
If you still want to know what that guy was trying to say then read on.
during unlocking you must have used adb.exe and fastboot.exe files. you need to extract boot.img file from your ROM zip and put it in the folder where adb and fastboot files are located.
after that open cmd and navigate to that folder. then connect your phone in fastboot mode (turn off phone and hold power+vol down to boot into bootloader and select fastboot from menu)
the phone should now show "FASTBOOT USB". now enter this command in cmd without the inverted commas: "fastboot flash boot boot.img"
it should something like sending and write OK in cmd
then reboot phone.
P.S. that rom is very similar to stock rom with little visual differences. check in settings>about phone>software number.. if it shows skydragon3D then your rom flashed correctly
thank you so much man
I have the castor windy version 16gb SGP511. I was previously rooted but not unlocked. I unlocked the boot loader. Installed the twrp image on the pac man thread which i think was dual recovery cause Philz,Cwm came out, so I can install lollipop version of the rom. Made a backup of the stock rom. Followed this instructions - Install the Lollipop ROM + GApps+SuperSU using whatever Recovery you have.
- Turn off device completely.
- Press <Volume Up> and plug USB cable.
- LED should turn blue.
- Send command: "fastboot erase recovery"
- Send command for Castor_Windy: "fastboot flash recovery TWRP_Castor_Windy.img"
- Send command for Castor: "fastboot flash recovery TWRP_Castor.img"
- Unplug USB cable.
- Device will reboot.
- When LED turns pink press <Volume Up> and <Volume Down> several times.
- You should now see TWRP
I wasnt fast enough so stock rom booted. I used Adb reboot recovery to access recovery and did as the above mentioned. Wiped i tried to install the rom which failed. Rebooted back to system and got stuck in Sony boot up screen. I can access fastboot. Read though the forums I have to find a ftf or a system image file and use a flash tool. What ftf file or system image my I use use which will let me root my device again.
Thanks Steve
Kamaleon said:
What ftf file or system image my I use use which will let me root my device again.
Thanks Steve
Click to expand...
Click to collapse
Try this Xperia downloader tool. Should let you see which versions are which. If you want an easy root, then stay away from the KitKat builds, unless you want to unlock bootloader.
http://forum.xda-developers.com/cro...xperifirm-xperia-firmware-downloader-t2834142
Use Flashtool to flash your downloaded ftf file. Just make sure your device is charged.
http://forum.xda-developers.com/showthread.php?t=2335555
I believe flashtool will even install the drivers for your 511
Thanks for the reply. Flashed ftf file and my tablet is up an running. Do I have to unlock my bootloader again or is it unlocked already?
Kamaleon said:
Thanks for the reply. Flashed ftf file and my tablet is up an running. Do I have to unlock my bootloader again or is it unlocked already?
Click to expand...
Click to collapse
Well, now this depends.
If you previously had KK running, and flashed a original version JellyBean ROM, then it probably locked the bootloader again.
If you flashed the same version as you had previously installed, then it didn't lock it again.
Moscow Desire said:
Well, now this depends.
If you previously had KK running, and flashed a original version JellyBean ROM, then it probably locked the bootloader again.
If you flashed the same version as you had previously installed, then it didn't lock it again.
Click to expand...
Click to collapse
Thanks. Yes i was unlocked already, went through the process again to verify. Trying to upgrade my firmware which is 17...........402. to a kk build firmware. I have the old cwm recovery 6.0.4.6. being trying to upgrade or even change recovery to any recovery except dual recovery. Through fastboot which none of them stick. Fastboot erase recovery
fastboot flash recovery recovery.img all of them(CWM,TWRP,PHILZ). The process goes smoothly but when I access recovery the old recovery comes up. What seems to be problem? I cant change my recovery or even upgrade it. I never have had this problem before some insight needed before i take a wrong turn. LOL.
Kamaleon said:
Thanks. Yes i was unlocked already, went through the process again to verify. Trying to upgrade my firmware which is 17...........402. to a kk build firmware. I have the old cwm recovery 6.0.4.6. being trying to upgrade or even change recovery to any recovery except dual recovery. Through fastboot which none of them stick. Fastboot erase recovery
fastboot flash recovery recovery.img all of them(CWM,TWRP,PHILZ). The process goes smoothly but when I access recovery the old recovery comes up. What seems to be problem? I cant change my recovery or even upgrade it. I never have had this problem before some insight needed before i take a wrong turn. LOL.
Click to expand...
Click to collapse
You mean the "factory" recovery comes up.
Well, just for info, you don't need to run the fastboot "erase" command when installing a recovery. Not necessary as the new image file will overwrite the existing.
Also, you don't exactly need to flash a recovery either. You can connect via USB, boot to bootloader, and run the "fastboot boot recovery.img (or whatever you named it) as long as your custom recovery is in the same folder as the fastboot.exe. This will just the custom recovery without installing it, thus allowing you to flash stuff.
As to why your fastboot flash isn't sticking, I'm new to the Sony tab, so haven't learned all the quirks yet as compared to Acer tabs.
Moscow Desire said:
You mean the "factory" recovery comes up.
Well, just for info, you don't need to run the fastboot "erase" command when installing a recovery. Not necessary as the new image file will overwrite the existing.
Also, you don't exactly need to flash a recovery either. You can connect via USB, boot to bootloader, and run the "fastboot boot recovery.img (or whatever you named it) as long as your custom recovery is in the same folder as the fastboot.exe. This will just the custom recovery without installing it, thus allowing you to flash stuff.
As to why your fastboot flash isn't sticking, I'm new to the Sony tab, so haven't learned all the quirks yet as compared to Acer tabs.
Click to expand...
Click to collapse
I mean cwm recovery v6.0.4.6 comes up the one I installed Doomlords thread with the advanced kernel. I ran fastboot erase recovery command to see if the new recoverys would stick and replace it but it didn't. I have done your instructions before hand thats how I am accessing the bootloader. "fastboot boot recovery.img all add this command to see If the new recovery would pop up. Thanks for the reply.
Kamaleon said:
I mean cwm recovery v6.0.4.6 comes up the one I installed Doomlords thread with the advanced kernel. I ran fastboot erase recovery command to see if the new recoverys would stick and replace it but it didn't. I have done your instructions before hand thats how I am accessing the bootloader. "fastboot boot recovery.img all add this command to see If the new recovery would pop up. Thanks for the reply.
Click to expand...
Click to collapse
Well, here's what I think is going on.
1. You installed Doomlords kernel. Note that this is a foto-kernel, which means the kernel itself has a partition that contains a recovery. What this means, is that as long a the fota-kernel was not replaced, then that specific recovery will be there.
2. You flashed a normal recovery. Now, I think this is there, but because of the fota-kernel, the fota-kernel is taking precedence.
Like I said, I don't know a lot about this Sony tab and the different partitions,as they are different from other tablets I am familiar with.
What puzzles me, is that if you flash a new "ftf" without changing any options in Flashtool, it "should" rewrite "every" partition on the tab, and install Stock recovery.
Now, based on my experience with Acer A500x and A700x tablets, I can say there are times when your issue happens. Rare, but it does happen. Things say they flash ok, but the old stuff still remains. The only option at that point, was to go back to a totally original version of the firmware.
Not sure I'm helping you on this. But the good thing, is that you can Fastboot Boot Recovery.
MD
Moscow Desire said:
Well, here's what I think is going on.
1. You installed Doomlords kernel. Note that this is a foto-kernel, which means the kernel itself has a partition that contains a recovery. What this means, is that as long a the fota-kernel was not replaced, then that specific recovery will be there.
2. You flashed a normal recovery. Now, I think this is there, but because of the fota-kernel, the fota-kernel is taking precedence.
Like I said, I don't know a lot about this Sony tab and the different partitions,as they are different from other tablets I am familiar with.
What puzzles me, is that if you flash a new "ftf" without changing any options in Flashtool, it "should" rewrite "every" partition on the tab, and install Stock recovery.
Now, based on my experience with Acer A500x and A700x tablets, I can say there are times when your issue happens. Rare, but it does happen. Things say they flash ok, but the old stuff still remains. The only option at that point, was to go back to a totally original version of the firmware.
Not sure I'm helping you on this. But the good thing, is that you can Fastboot Boot Recovery.
MD
Click to expand...
Click to collapse
I started from zero again flashed ftf Firmware SGP511_17.1.1.A.0.402. Verfied that i was bootloader unlocked I still was. Used fastboot to flash Dooms Kernel, without a problem used cwm revovery to flash Supersu. Tried to upgrade my firmware with the prerooted rooms in thread flashed with out a problem but no difference was provided. Verified in settings and initial firmware stands (SGP511_17.1.1.A.0.402). Tried to flash CM12 got stuck on a bootloop. Fastboot flashed the boot img provided didn't work for me so I flahed Teslas rom Followed instructions provided
1. Make sure you have CWM installed and a working nandroid backup
2. Download the ROM.
3. Place the ROM on your SD-Card.
4.Extract boot.img included in zip and fastboot flash it via Flashtool or CMD
5. Reboot to recovery.
6. Wipe data-factory reset/cache partition/dalvik cache
7. Flash the ROM.
Flash went through but when I try to access recovery through the rom or adb recovery doesnt come up. The tablet just stays black on recovery screen and the tablets led turns yellow. I have adb access so went to access fastboot flashed different recoverys. None of them (flashed without a problem), work but if a flashed Dooms I have access to recovery again, but loose functionality of the rom it gets stuck on sony screen. I have to do the steps all over again without a working recovery. This has being a learning experience I am HTC guy so the process with sony products is new to me as well. So where do you think I should go on from here; flash a newer ftf or lock and unlock my bootloader again to see if something happens or just move on jajajajj . Anyways thanks a lot for your help.
Kamaleon said:
I started from zero again flashed ftf Firmware SGP511_17.1.1.A.0.402. Verfied that i was bootloader unlocked I still was. Used fastboot to flash Dooms Kernel, without a problem used cwm revovery to flash Supersu. Tried to upgrade my firmware with the prerooted rooms in thread flashed with out a problem but no difference was provided. Verified in settings and initial firmware stands (SGP511_17.1.1.A.0.402). Tried to flash CM12 got stuck on a bootloop. Fastboot flashed the boot img provided didn't work for me so I flahed Teslas rom Followed instructions provided
1. Make sure you have CWM installed and a working nandroid backup
2. Download the ROM.
3. Place the ROM on your SD-Card.
4.Extract boot.img included in zip and fastboot flash it via Flashtool or CMD
5. Reboot to recovery.
6. Wipe data-factory reset/cache partition/dalvik cache
7. Flash the ROM.
Flash went through but when I try to access recovery through the rom or adb recovery doesnt come up. The tablet just stays black on recovery screen and the tablets led turns yellow. I have adb access so went to access fastboot flashed different recoverys. None of them (flashed without a problem), work but if a flashed Dooms I have access to recovery again, but loose functionality of the rom it gets stuck on sony screen. I have to do the steps all over again without a working recovery. This has being a learning experience I am HTC guy so the process with sony products is new to me as well. So where do you think I should go on from here; flash a newer ftf or lock and unlock my bootloader again to see if something happens or just move on jajajajj . Anyways thanks a lot for your help.
Click to expand...
Click to collapse
Well, I'm not sure which route to take.
However, I will tell you what I have learned the other day.
I have the 521 with unlocked bootloader. Rooted with my own boot.img, flashed SuperSU using "flashboot boot recovery.img" (yeah, sometimes it doesn't show on the display, so it takes a few times).
Now, other day I was going to check out the new LyPop pre-rooted. Fastboot flash recovery recovery,img, and it won't boot it to recovery like it should. Like it's not flashed. Tried it a couple times. Now, I didn't install the dual recovery as I'm not sure how that kernel (boot.img) will interact with my current tabs OS. Not to mention I need it for my work until tomorrow. But strangely it sounds like the same issue you have.
This weekend I will investigate it. As for me, I will probably flash the Stock ftf lyPop build, and just root it using a modified boot.img.
One thing I do know, is flashing a custom recovery to the "recovery" partition, doesn't seem to work like it used to work on other devices. It seems the flashing to the "Fota kernel" partition seems to be the only method that works. This is what happens when you flash that dual recovery, or any recovery that has a boot image using "Fota". Probably explains why you can't get rid of it using "fastboot erase recovery". because it's erasing the wrong partition. Only flashing a full ftf gets rid of it, because the ftf has a new FotaKernel it flashes.
Eh, something like that. Will look at it this weekend.
Hi, my brothers xt 1022 its bricked on initial looping.
The original bootloader works, i try hard reset, wipe data, but doesnt work.
I got unlock bootloader, because debug is disable, i dont be twrp or cwm or stock recovery works.
In the last time i try most tutorials for recovery with fasboot, .bat files, but doesnt worked.
i try send stock recovery in the update via sideload.
In this mode adb devices show the xt but returns error closed on adb usb.
I try kill-server but error closed persist
The sideload of zip rom goes to 100% but xt returns error to update.
Please help me
updating
in fastboot in try to twrp = incomplete boot image for booting.
how do i give the backup files via sideload, to try move the files and try recovery like a backup via side load, its possible?
update 2
I edit the adb_usb.ini and include id of device in recovery update adb and in fastboot. with the 2 adress include the name in managment device change to faastboot condor S. But still dont work the install twrp etc
Help
Hi, with fastboot these comands i have sucsses
fastboot flash partition gpt.bin
version downgraded for primary gpt
fastboot flash motoboot motoboot.img
downgraded for tz
fastboot flash boot boot.img
downgraded for boot
the outhers comand for flash doesnt work
Please help me with unbricked theses paper holder moto e
In android device info
show my device
condor_niibr_ds-user 4.4.4 KXC21.5-44 2 release-keys
kxc21.5-44
Anybody show me one rom .zip , to sideload from stock recovery. Or this rom to reinstal via sideload
Thanks
Hey guys.
SGP312 model here, unlocked bootloader.
not sure what i did wrong here - i got to Fastboot mode and the blue light is on, when i run "Fastboot devices" i get the device name.
so i followed the explanation here: https://forum.xda-developers.com/xp...pment/ub-twrp-v3-2-1-xperia-tablet-z-t3735110
and did: "fastboot flash boot twrp-3.2.1-0-pollux_windy.img"
however, now my phone won't boot, and when i type "adb reboot recovery" i get "error: device not found" (even thought "Fastboot devices" gives me a response")
i tried fixing it with Flashtool, and everything works well until i get to "Wait for Flashmode" and im instructed to "unplug, power off, pres vol down, plug in USB cable" - this simply doesn't do anything =X
so.... how do i get out of this? all i want to do is install one of the newer roms from the forum (either Marshmallow or Oreo)
can anyone help me get out of this issue i've gotten myself into?
Caniv said:
Hey guys.
SGP312 model here, unlocked bootloader.
not sure what i did wrong here - i got to Fastboot mode and the blue light is on, when i run "Fastboot devices" i get the device name.
so i followed the explanation here: https://forum.xda-developers.com/xp...pment/ub-twrp-v3-2-1-xperia-tablet-z-t3735110
and did: "fastboot flash boot twrp-3.2.1-0-pollux_windy.img"
however, now my phone won't boot, and when i type "adb reboot recovery" i get "error: device not found" (even thought "Fastboot devices" gives me a response")
i tried fixing it with Flashtool, and everything works well until i get to "Wait for Flashmode" and im instructed to "unplug, power off, pres vol down, plug in USB cable" - this simply doesn't do anything =X
so.... how do i get out of this? all i want to do is install one of the newer roms from the forum (either Marshmallow or Oreo)
can anyone help me get out of this issue i've gotten myself into?
Click to expand...
Click to collapse
you flashed recovery to boot. So only recovery exists in boot section.
Of course tablet won't boot afterwards, as there is not kernel.
Download custom rom you want to install, unpack boot.img from roms zip files and flash via "fastboot flash boot boot.img"
Afterwards enter recovery and flash custom rom zip, gapps or whatever you need.
Rootk1t said:
you flashed recovery to boot. So only recovery exists in boot section.
Of course tablet won't boot afterwards, as there is not kernel.
Download custom rom you want to install, unpack boot.img from roms zip files and flash via "fastboot flash boot boot.img"
Afterwards enter recovery and flash custom rom zip, gapps or whatever you need.
Click to expand...
Click to collapse
I made same stupid mistake, so after getting the boot.img and ur command I get waiting for device. Any solution?
NoSuperHero said:
I made same stupid mistake, so after getting the boot.img and ur command I get waiting for device. Any solution?
Click to expand...
Click to collapse
enter recovery if it is installed and flash boot.img from there.
Rootk1t said:
you flashed recovery to boot. So only recovery exists in boot section.
Of course tablet won't boot afterwards, as there is not kernel.
Download custom rom you want to install, unpack boot.img from roms zip files and flash via "fastboot flash boot boot.img"
Afterwards enter recovery and flash custom rom zip, gapps or whatever you need.
Click to expand...
Click to collapse
I did the same thing knowing the outcome and then successfully flashed Lineage.
For future reference, with the Xperia Tablet z where should I be flashing the recovery if not to boot:
"fastboot flash *What goes here?* twrp-3.x.x-0-pollux_windy.img"
big ach said:
I did the same thing knowing the outcome and then successfully flashed Lineage.
For future reference, with the Xperia Tablet z where should I be flashing the recovery if not to boot:
"fastboot flash *What goes here?* twrp-3.x.x-0-pollux_windy.img"
Click to expand...
Click to collapse
Code:
dd if=/sdcard/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
where twrp.img is your recovery image.
Hello, I'm kind of new at this (this is my first post) so be gentle
So, the last few days I've been trying to install a new rom on my phone (Redmi Note 4X) and the problems started with the model. I only seem to find Redmi Note 4 roms, and as I've come to find, mine is supposed to be the mido one (correct me if I'm wrong though). I have unlocked the bootloader, I have installed and enabled the fastboot on my phone, so the next step was to install the latest TWRP.
There came more problems; I tried doing this through the app and it just wouln't flash it. So I found a guide on how to root my phone and install a new recovery through adb and I followed it. It didn't work. I couldn't find the right twrp version for my phone. When I finally did realise my phone needed mido, I found the latest from the TWRP website. It wouldn't load through adb again. I found a thread about a fixed mido version, which finally worked for me. But my brother who was helping me, and isn't as much of a noob as I am (he has flashed rom and recoveries many times on his Nexus 5X), decided that I necessarily need the latest twrp if I'm going to flash a new rom, so he flashed the new twrp through the old one, and soft bricked my phone (I think). So I'm searching for a guide to unbrick it. (Which I can't seem to find to work at least).
To conclude;
I have unlocked my bootloader
I have access to the fastboot
I tried to flash a recovery
I failed many times, but I managed it
I flashed the latest twrp and bricked my phone
I don't have access to the recovery
My phone is still on a bootloop
I am not sure about which phone model I have
Help!
Thanks in advance.
1. Just check your phone model on its box. If its Snapdragon version (Mido), then just install it via fastboot. (code: fastboot flash recovery twrp-midoxx.img). If you are success, then try to reboot to recovery (fastboot boot twrpmido-xx.img). After booted, then you just manage to rom.zip you want to install. If you don't have it, then download it before from your PC and push it to your phone. Or just enable Mtp checklis from TWRP n copy that file to your internal phone/sdcard. Wipe all/factory reset except internal storage. Then you dan install rom.zip normally. N reboot. (Note: if you are on MIUI and wanted to always stay on it, just flash the file called lazyflasher.zip. n' wipe cache n art cache only then reboot). Flashing custom recovery on stock MIUI Will manage the device Going to bootloop)
2. If you have mediatek version (nikel), searching the fastboot Rom from miui website and flash it normally via fastboot. (SP Flash tool)
Warning: flash the wrong rom file into wrong phone Will make your device brick. So becarefull n knowing what model/code name you have.
Dyt199412syam said:
1. Just check your phone model on its box. If its Snapdragon version (Mido), then just install it via fastboot. (code: fastboot flash recovery twrp-midoxx.img). If you are success, then try to reboot to recovery (fastboot boot twrpmido-xx.img). After booted, then you just manage to rom.zip you want to install. If you don't have it, then download it before from your PC and push it to your phone. Or just enable Mtp checklis from TWRP n copy that file to your internal phone/sdcard. Wipe all/factory reset except internal storage. Then you dan install rom.zip normally. N reboot. (Note: if you are on MIUI and wanted to always stay on it, just flash the file called lazyflasher.zip. n' wipe cache n art cache only then reboot). Flashing custom recovery on stock MIUI Will manage the device Going to bootloop)
2. If you have mediatek version (nikel), searching the fastboot Rom from miui website and flash it normally via fastboot. (SP Flash tool)
Warning: flash the wrong rom file into wrong phone Will make your device brick. So becarefull n knowing what model/code name you have.
Click to expand...
Click to collapse
Hello and thanks for the reply. I have the snapdragon version, but all I'm asking is how am I supposed to flash the lazyflasher without accessing the recovery? Through adb?
fionik said:
Hello and thanks for the reply. I have the snapdragon version, but all I'm asking is how am I supposed to flash the lazyflasher without accessing the recovery? Through adb?
Click to expand...
Click to collapse
Firstly, enter fastboot mode on your device. Connecting to pc and flashing the twrp for mido. "fastboot flash recovery twrp-mido.img". Then boot to it using " fastboot boot twrp-mido.img". Then you will enter the recovery (twrp) in a second. Copy the lazyflasher into your phone (enable mtp first in Mount option in twrp) that you downloaded from pc. Just flash the lazyflasher.zip and reboot.
And why you don't want to flash lazyflasher when it very easy to flash it using recovery twrp? adb? You mean android debugging? Actually, you cant flash a .zip file into your system partition except through fastboot mode. However, fastboot mode (in cmd) only recognize a .img file. I just try to tell you the easier method to make your device boot up.
Dyt199412syam said:
Firstly, enter fastboot mode on your device. Connecting to pc and flashing the twrp for mido. "fastboot flash recovery twrp-mido.img". Then boot to it using " fastboot boot twrp-mido.img". Then you will enter the recovery (twrp) in a second. Copy the lazyflasher into your phone (enable mtp first in Mount option in twrp) that you downloaded from pc. Just flash the lazyflasher.zip and reboot.
And why you don't want to flash lazyflasher when it very easy to flash it using recovery twrp? adb? You mean android debugging? Actually, you cant flash a .zip file into your system partition except through fastboot mode. However, fastboot mode (in cmd) only recognize a .img file. I just try to tell you the easier method to make your device boot up.
Click to expand...
Click to collapse
As I said above, I can only access the fastboot, and I get errors in the adb when I try to flash the twrp image.
fionik said:
As I said above, I can only access the fastboot, and I get errors in the adb when I try to flash the twrp image.
Click to expand...
Click to collapse
Share your error please.
Try fastboot boot twrp.img