Related
So I've been lurking around here for a while and you guys are amazing.
But I'm having some issue getting clockworkmod back onto my Sola. I was running Cyanogenmod 9.1 from the free xperia project, but it was giving me some issues and I was looking to flash a new ROM. But somehow I lost my CWM installation and can't get it back on.
Right now, I am running stock ICS that it rooted with the.54 firmware. Bootloader is unlocked. Things I have tried thus far:
1. Installing CWM via RecoverX: didn't work. When I ran the utility with the phone on, when it got the point of installing CWM, it would freeze up, said it was not responding, and then go straight to the screen saying it was finished. But it didn't actually do anything or install anything. If I tried running the utility with my phone in fastboot mode, it said my phone wasn't connected (and all the ADB drivers are installed properly)
2. Installing via Flashtool: Even though Flashtool has the option to install a recovery, that option has always been grayed out for me so I can't click it and run it.
3. Installing via fastboot: I tried running the "fasboot flash recovery" command to flash a custom recovery, but it comes back with a message saying the recovery partition can't be found.
What I can do, though, is boot to CWM. If I go use the fastboot command "fastboot flash boot <file name>", it will flash CWM and I can boot to it. I'm not exactly sure what it does, but it isn't flashing to the recovery partition because after doing this I can't load my stock ICS. It just gets to the Sony logo and hangs or goes through a bootloop. I also can't use this to flash a ROM from a zip file.
So I'm kind of at a loss here as to what to do. I've done lots of searching and reading, but all the tools people say to use don't seem to be working. Any idea what I'm doing wrong?
Flash a stock based kernel..you will find many threads on Xperia Sola Development
Try This
That is what i used to install CWM on my xperia sola...(And also be sure that your phone is rooted before installing it)
Hit Thanks :good: if i helped!!
I wiped my device and now can't install CM because it thinks it is castor and not castor_windy. It is a wifi z2 tablet.
I used tool from this thread to gain root. After I used root checker basic to check I was rooted and it said I was.
http://forum.xda-developers.com/showthread.php?t=2784900
I used tool from this thread to install custom recovery, I believe successfully. I was able to reboot into recovery afterwards.
http://forum.xda-developers.com/showthread.php?t=2794175
To try and install CM I tried to follow the instructions in this post.
http://forum.xda-developers.com/showpost.php?p=53994500&postcount=1
To do 4&5 in twrp, I wiped cache, system and dalvik. I got the problem in the following picture (pictures are all links because I couldn't work out how to get them small enough to attach).
https://drive.google.com/file/d/0BxoU7oR5AJUeVnE4LXpEd0t6c0k/edit?usp=sharing
It eventually formatted all three.
I then tried to install CM, PA gapps, and recovery (as suggested in the recovery thread to make sure keep recovery after reboot). This happened.
https://drive.google.com/file/d/0BxoU7oR5AJUeT2pkZE53UUdRUDA/edit?usp=sharing
I didn't make a backup in advance because I am an idiot. I do have TA backed up.
What did I do wrong and how can I fix it please?
If I understand you correctly, you have tried too flash CM without unlocking your bootloader first.
As far as I know, this is not possible: Due to the locked bootloader, the CM Kernel cannot be installed and hence CM won't work anyways.
With locked bootloader, you can only flash stock-based ROMs which share the Kernel with the original ROM.
You can use flastool to flash a TFT (stock firmware), then your tablet should work again.
For flashing a real CM which requires an unlocked bootloader see here: http://forum.xda-developers.com/showthread.php?t=2708194
Bootloader unlocking: http://forum.xda-developers.com/showthread.php?t=2747676
Have fun!
BabelHuber said:
If I understand you correctly, you have tried too flash CM without unlocking your bootloader first.
As far as I know, this is not possible: Due to the locked bootloader, the CM Kernel cannot be installed and hence CM won't work anyways.
With locked bootloader, you can only flash stock-based ROMs which share the Kernel with the original ROM.
You can use flastool to flash a TFT (stock firmware), then your tablet should work again.
For flashing a real CM which requires an unlocked bootloader see here: http://forum.xda-developers.com/showthread.php?t=2708194
Bootloader unlocking: http://forum.xda-developers.com/showthread.php?t=2747676
Have fun!
Click to expand...
Click to collapse
Thank you. You are exactly correct, I didn't unlock the bootloader first.
Would this flashtool work given I am currently in twrp and have no OS? If it would it is showing the links for the ROM for SGP511 and this is 512. Is it the same or do I need a different link for the ROM?
http://xperiafirmware.com/8-firmware/50-sony-xperia-z2-tablet-wi-fi-sgp512
Thanks. Trying to have fun.
spanielhead said:
Thank you. You are exactly correct, I didn't unlock the bootloader first.
Would this flashtool work given I am currently in twrp and have no OS? If it would it is showing the links for the ROM for SGP511 and this is 512. Is it the same or do I need a different link for the ROM?
http://xperiafirmware.com/8-firmware/50-sony-xperia-z2-tablet-wi-fi-sgp512
Thanks. Trying to have fun.
Click to expand...
Click to collapse
Look at developer.sonymobile.com/unlockbootloader
IRRC you need to use fastboot to unlock the device. Afterwards, you can install Cm. If you are lucky you don't need to flash a stock ROM first.
BabelHuber said:
Look at developer.sonymobile.com/unlockbootloader
IRRC you need to use fastboot to unlock the device. Afterwards, you can install Cm. If you are lucky you don't need to flash a stock ROM first.
Click to expand...
Click to collapse
Thank you. Have unlock key from Sony now.
I am currently in recovery. Should I be able to reboot the bootloader from recovery and get into fastboot that way? (Reminder I have no OS.)
spanielhead said:
Thank you. Have unlock key from Sony now.
I am currently in recovery. Should I be able to reboot the bootloader from recovery and get into fastboot that way? (Reminder I have no OS.)
Click to expand...
Click to collapse
OK I tried this and bad things. Before the device was detected by my laptop, now it is not and it hangs at the sony logo and no led. Am I f***ed?
spanielhead said:
OK I tried this and bad things. Before the device was detected by my laptop, now it is not and it hangs at the sony logo and no led. Am I f***ed?
Click to expand...
Click to collapse
I would suggest non Sony software anyway. I still have my bootloader, but since it's not allowed to be unlocked I can't use Sony software either.
spanielhead said:
OK I tried this and bad things. Before the device was detected by my laptop, now it is not and it hangs at the sony logo and no led. Am I f***ed?
Click to expand...
Click to collapse
Not at all :good:
By long-pressing the power button (10 seconds or so) the tablet shuts down
Do the following:
- Get your Sony unlock key
- Install the Android SDK (Software Developers Kit) on your PC
- Install all necessary Xperia drivers (Google is your friend, don't remember where I got mine from)
Using fastboot:
- Connect your tablet to the PC while simultaneously pressing 'Volume up'. When the LED is blue you are in fastboot mode
- Unlock your tablet like described by Sony
- Install CWM from fastboot mode
- Reboot
- Enter recovery (press 'Volume up' when the LED is pink)
Copy files to tablet:
- Use the adb command line tool from Android SDK (in the same folder as fastboot)
Copy CM11 and GAPPs to tablet:
via Windows CMD: adb push filename.zip /sdcard/ROMs/filename.zip
- Flash CM11/ GAPPS via recovery
Done!
BabelHuber said:
Using fastboot:
- Connect your tablet to the PC while simultaneously pressing 'Volume up'. When the LED is blue you are in fastboot mode
- Unlock your tablet like described by Sony
Click to expand...
Click to collapse
Have restored device to stock, then rooted and installed custom recovery (as in original post).
Can't get into fastboot mode. Trying as stated above fails. Screen stays off with blue LED. Same thing happens if I reboot into bootloader via flashify or recovery. fastboot devices then does not detect device. It does for my phone so think that means fastboot works.
I must have missed something (again). Thank you for your patience.
Edit: bootloader now unlocked with flashtool.
Edit 2: Used flashtool to fastboot flash boot.img from M9 snapshot (was this my mistake, not CM10?). Now can only get into fastboot, can't get into recovery. Without recovery I require an img file of the rom, is that correct?
hasenbein1966 said:
I don't understand why you guys are so generous with your time and energy and write at length to help people who are too lazy and too careless to read properly and thus f*** up their devices...
Click to expand...
Click to collapse
I made a mistake, possibly multiple mistakes. I will continue to make mistakes. This forum is for people like me who don't know what they are doing to ask for help. No one has to offer that help. I am greatly appreciative when they do.
spanielhead said:
Can't get into fastboot mode. Trying as stated above fails. Screen stays off with blue LED.
Click to expand...
Click to collapse
When the screen stays off with blue LED, you ARE in fastboot mode!
In case fastboot does not work, you haven't installed the according drivers on your PC.
spanielhead said:
Used flashtool to fastboot flash boot.img from M9 snapshot (was this my mistake, not CM10?). Now can only get into fastboot, can't get into recovery. Without recovery I require an img file of the rom, is that correct?
Click to expand...
Click to collapse
You must have done something wrong - I had no problems whatsoever.
Just try it again:
- Flash CWM as described
- Factory reset, format system, format data, wipe cache, wipe Dalvik cache (format data/media only if the internal SD-card should be wiped, too!)
- Flash the boot.img from the CM11 ZIP-file
- Enter CWM and use the adb push-command to flash CM11/GAPPs
- Install CM11 and GAPPs via recovery
Good luck :good:
BabelHuber said:
When the screen stays off with blue LED, you ARE in fastboot mode!
In case fastboot does not work, you haven't installed the according drivers on your PC.
You must have done something wrong - I had no problems whatsoever.
Just try it again:
- Flash CWM as described
- Factory reset, format system, format data, wipe cache, wipe Dalvik cache (format data/media only if the internal SD-card should be wiped, too!)
- Flash the boot.img from the CM11 ZIP-file
- Enter CWM and use the adb push-command to flash CM11/GAPPs
- Install CM11 and GAPPs via recovery
Good luck :good:
Click to expand...
Click to collapse
Did you ever manage to install cm11?
I have the same error, device thinks is Castor when its a sgp512. I tried both and soft bricked it, got out, rooted it again and still have the same error. I did unlock the bootloader, i am rooted, I know how to go into fastboot, flashmode, cwm, twrp, etc. But CM11 does not work!
Very frustrating.
Any ideas?
anyone?
Edit: Problem was that I wasnt flashing the kernel first as stated here: http://wiki.cyanogenmod.org/w/Install_CM_for_castor_windy
Are you saying you missed this one
fastboot -i 0xfce flash boot boot.img
BabelHuber said:
When the screen stays off with blue LED, you ARE in fastboot mode!
In case fastboot does not work, you haven't installed the according drivers on your PC.
You must have done something wrong - I had no problems whatsoever.
Just try it again:
- Flash CWM as described
- Factory reset, format system, format data, wipe cache, wipe Dalvik cache (format data/media only if the internal SD-card should be wiped, too!)
- Flash the boot.img from the CM11 ZIP-file
- Enter CWM and use the adb push-command to flash CM11/GAPPs
- Install CM11 and GAPPs via recovery
Good luck :good:
Click to expand...
Click to collapse
I finally found some time to do this. Flashed boot.img using fastboot (didn't work using flashtool which I think was the most recent problem), flashed m9 in recovery, downloaded and adb pushed then flashed pa zero day GAPPS in recovery, and all is right with the world.
@BabelHuber how might I buy you a beer or coffee to thank you properly?
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.
So I am stuck on TWRP 2.7.1.0 and i am running slimrom 4.4.4 on a c6833 and the reason for this is because it's the only thing that will boot on my phone. There was some intense trial and error a few months ago and a few days with a bricked phone but I finally got it running again, and I am nervous about messing things up again.
I am wanting to move to a more up to date ROM either scrubber port 5.1 or remix 5.1.1, but they both ask for updated TWRP to install. And I can't update TWRP using the TWRP tool from the store. It downloads but when it tries to install it says there is a problem. Previously, trying to update TWRP would result in SONY bootloops. I was about to try the dd method but just wanted to make sure it was safe.
I am a bit of an idiot (I got rid of my encrypted keys on day 2 of owning the phone) so any help would be appreciated.
Thanks!
walkingagh said:
...
Click to expand...
Click to collapse
The easiest way is to use Rashr. It should set everything up automatically. You may then reboot to recovery from the ROM, or by holding Vol- when the LED turns purple on boot-up.
If that doesn't work, for whatever reason, try dd or Flashtool. Using Flashtool, you can flash openrecovery-twrp-2.8.5.0-togari.img with the phone in Fastboot mode.
Let me know if you have any further questions!
Used Rashr...and now I can't get into recovery. I can still boot into my phone, but booting into recovery just fails with a yellow LED?
So Rashr still says I have 2.7.1.0 installed. :/
walkingagh said:
Used Rashr...and now I can't get into recovery. I can still boot into my phone, but booting into recovery just fails with a yellow LED?
Click to expand...
Click to collapse
Alright, you likely need a newer kernel first. Using Flashtool, you can flash this boot.img (newest AICP kernel) to the boot partition using the Fastboot mode (or use fastboot manually from the Flashtool/x10flasher_lib folder with "fastboot flash boot boot.img"). At this moment, you'll no longer be able to boot into the ROM, so make sure you've done all necessary backups and are ready to install a newer ROM. Then use Flashtool/Fastboot to flash the openrecovery-twrp-2.8.5.0-togari.img file to your recovery/FOTAKernel partition ("fastboot flash recovery openrecovery-twrp-2.8.5.0-togari.img"). You should be able to enter recovery now.
Awesome thanks! Will I need to do this each time I flash a ROM? Or can I just jump from something like scrubber to something else?
I know this is an old thread but is that the boot image I need to run TWRP 3? If so, can I do this via dd?
Triflot said:
Alright, you likely need a newer kernel first. Using Flashtool, you can flash this boot.img (newest AICP kernel) to the boot partition using the Fastboot mode (or use fastboot manually from the Flashtool/x10flasher_lib folder with "fastboot flash boot boot.img"). At this moment, you'll no longer be able to boot into the ROM, so make sure you've done all necessary backups and are ready to install a newer ROM. Then use Flashtool/Fastboot to flash the openrecovery-twrp-2.8.5.0-togari.img file to your recovery/FOTAKernel partition ("fastboot flash recovery openrecovery-twrp-2.8.5.0-togari.img"). You should be able to enter recovery now.
Click to expand...
Click to collapse
That file has expired, any chance you can re-post it?
I messed up i tried to reflash my phone back to stock from marshmallow rom on the thread here but i lost custom recovery and only thing i can get into is download mode, how can i fix this? I have abd install on my pc got the system image boot and recovery img but don't know what 2 do. Please help
xavier55 said:
I messed up i tried to reflash my phone back to stock from marshmallow rom on the thread here but i lost custom recovery and only thing i can get into is download mode, how can i fix this? I have abd install on my pc got the system image boot and recovery img but don't know what 2 do. Please help
Click to expand...
Click to collapse
Your phone is in fastboot mode, not download mode. Small, but distinct difference.
Since you've installed a custom ROM, your bootloader should be unlocked. However, it may be a good idea to issue the oem unlock command through fastboot anyways. Use "adb reboot bootloader" and "fastboot oem unlock" to ensure that your bootloader is unlocked.
Now, since your phone is in fastboot mode, you can do one of two things: 1. Flash a custom recovery and restore your device to stock, or 2. Flash a custom recovery and continue using a custom ROM. Either way, you will need to install TWRP or another custom recovery image of your choice. The TWRP thread is located here: http://forum.xda-developers.com/tmobile-lg-v10/development/recovery-unofficial-twrp-t3239740 Since you're already in the bootloader/fastboot mode, all you would need to do is download TWRP and use "fastboot flash recovery twrp.img" and then "fastboot boot twrp.img" to install TWRP. Please note that the 'twrp.img' will vary depending on which version you download, it will probably look more like 'twrp-2.8.7.1-h901.img'. You can just rename the file or use the full file name in the fastboot commands.
Once in TWRP, you can flash whatever ROM you want. To restore your phone to stock, go to this thread and flash the .zip in TWRP http://forum.xda-developers.com/tmo.../lg-h901-stock-images-device-restore-t3241170 after doing the standard wipe procedure. :good:
soltheman said:
Your phone is in fastboot mode, not download mode. Small, but distinct difference.
Since you've installed a custom ROM, your bootloader should be unlocked. However, it may be a good idea to issue the oem unlock command through fastboot anyways. Use "adb reboot bootloader" and "fastboot oem unlock" to ensure that your bootloader is unlocked.
Now, since your phone is in fastboot mode, you can do one of two things: 1. Flash a custom recovery and restore your device to stock, or 2. Flash a custom recovery and continue using a custom ROM. Either way, you will need to install TWRP or another custom recovery image of your choice. The TWRP thread is located here: http://forum.xda-developers.com/tmobile-lg-v10/development/recovery-unofficial-twrp-t3239740 Since you're already in the bootloader/fastboot mode, all you would need to do is download TWRP and use "fastboot flash recovery twrp.img" and then "fastboot boot twrp.img" to install TWRP. Please note that the 'twrp.img' will vary depending on which version you download, it will probably look more like 'twrp-2.8.7.1-h901.img'. You can just rename the file or use the full file name in the fastboot commands.
Once in TWRP, you can flash whatever ROM you want. To restore your phone to stock, go to this thread and flash the .zip in TWRP http://forum.xda-developers.com/tmo.../lg-h901-stock-images-device-restore-t3241170 after doing the standard wipe procedure. :good:
Click to expand...
Click to collapse
I'm kinda in the same boat now except that I already received the replacement device. Need to re-lock the old V10, but adb won't recognize my device at all. Any more option when that's the case? I can get into both download mode and fastboot. Phone is recognized by LGUP in download mode, but not by adb in fastboot mode for some reason.
(I've verified connection and driver using the other V10, the other V10 is recognized just fine)
soltheman said:
Your phone is in fastboot mode, not download mode. Small, but distinct difference.
Since you've installed a custom ROM, your bootloader should be unlocked. However, it may be a good idea to issue the oem unlock command through fastboot anyways. Use "adb reboot bootloader" and "fastboot oem unlock" to ensure that your bootloader is unlocked.
Now, since your phone is in fastboot mode, you can do one of two things: 1. Flash a custom recovery and restore your device to stock, or 2. Flash a custom recovery and continue using a custom ROM. Either way, you will need to install TWRP or another custom recovery image of your choice. The TWRP thread is located here: http://forum.xda-developers.com/tmobile-lg-v10/development/recovery-unofficial-twrp-t3239740 Since you're already in the bootloader/fastboot mode, all you would need to do is download TWRP and use "fastboot flash recovery twrp.img" and then "fastboot boot twrp.img" to install TWRP. Please note that the 'twrp.img' will vary depending on which version you download, it will probably look more like 'twrp-2.8.7.1-h901.img'. You can just rename the file or use the full file name in the fastboot commands.
Once in TWRP, you can flash whatever ROM you want. To restore your phone to stock, go to this thread and flash the .zip in TWRP http://forum.xda-developers.com/tmo.../lg-h901-stock-images-device-restore-t3241170 after doing the standard wipe procedure. :good:
Click to expand...
Click to collapse
thanks you saved me
baymon said:
I'm kinda in the same boat now except that I already received the replacement device. Need to re-lock the old V10, but adb won't recognize my device at all. Any more option when that's the case? I can get into both download mode and fastboot. Phone is recognized by LGUP in download mode, but not by adb in fastboot mode for some reason.
(I've verified connection and driver using the other V10, the other V10 is recognized just fine)
Click to expand...
Click to collapse
Yep. Your phone boots and everything, correct? Just factory reset it (Settings > Backup & Restore > Factory data reset). After its been reset, unlock it, turn on Developers Options, and enable USB debugging. After usb debugging is turned on, connect the v10 to your PC and be sure to hit "Always allow" when prompted by your phone. ADB should now be able to see your device.
If you can't get it to boot up, try restoring through LG UP/Bridge. I don't use any of LG's software, so I'm not sure what those apps can do and whether or not you'll be able to restore through them.
If nothing else, your phone is recognized in fastboot mode, so you can always manually flash the stock system images as well. You want to use the "fastboot flash boot boot.img", "fastboot flash recovery recovery.img", and "fastboot flash system system.img" commands After downloading the stock system images located in this thread: http://forum.xda-developers.com/lg-v10/development/lg-h901-stock-img-files-boot-recovery-t3238638
If you haven't ever flashed system images from fastboot, please read this first, as I am not responsible if your phone turns into a paperweight! https://developers.google.com/android/nexus/images#instructions While the instructions are for nexus devices, it works pretty much the same, except you'd want to use the individual commands instead of a flash-all script.
Hope this helps!
soltheman said:
Yep. Your phone boots and everything, correct? Just factory reset it (Settings > Backup & Restore > Factory data reset). After its been reset, unlock it, turn on Developers Options, and enable USB debugging. After usb debugging is turned on, connect the v10 to your PC and be sure to hit "Always allow" when prompted by your phone. ADB should now be able to see your device.
If you can't get it to boot up, try restoring through LG UP/Bridge. I don't use any of LG's software, so I'm not sure what those apps can do and whether or not you'll be able to restore through them.
If nothing else, your phone is recognized in fastboot mode, so you can always manually flash the stock system images as well. You want to use the "fastboot flash boot boot.img", "fastboot flash recovery recovery.img", and "fastboot flash system system.img" commands After downloading the stock system images located in this thread: http://forum.xda-developers.com/lg-v10/development/lg-h901-stock-img-files-boot-recovery-t3238638
If you haven't ever flashed system images from fastboot, please read this first, as I am not responsible if your phone turns into a paperweight! https://developers.google.com/android/nexus/images#instructions While the instructions are for nexus devices, it works pretty much the same, except you'd want to use the individual commands instead of a flash-all script.
Hope this helps!
Click to expand...
Click to collapse
Thanks for the follow up! No the phone would not boot at all and kept stuck at boot loop. I ended up just doing the OEM Lock and call it a day, the old device just won't boot to anything at this point.
I tried fastboot flash recovery recovery.img but it's giving some kinda kernel panic message and I was never able to get into recovery. This reminds me of the time when my Note 3 eMMC was fried, it wouldn't give a device ID to adb.
I think I am in the same boat too. I've been OEM unlocked yet recently my phone won't keep the TWRP recovery and keeps putting me into bootloop. I can't install a ROM and only thing I can do is fastboot mode. What did you do OEM lock the device? I am hoping that solution will get rid of that message bootloader unlocked during the bootloop and then I can try and get it serviced.