Related
In short my power button is broke, so i need to flash cyanogen so i can use volume to wake my device, but my phone is unusable but i think i can get into ADB, so can i?
have you tried using touch recovery http://clockworkmod.com/rommanager
i guess this would only work if you can get into bootloader mode
I tried that initally but i got a Status 7 error, however ill try again now
did you dl recovery today because the beta one from yesterday gave that error but if you redownload from clockwork site today it is updated. i got the error yesterday but i dl'd one from today and didnt get error flashing rom
---------- Post added at 02:58 PM ---------- Previous post was at 02:56 PM ----------
are you using fastboot to flash recovery?
Im trying to use flashboot to do it but whenever i do fastboot flash recovery.img i get an error
Unknown partition 'recovery.img'
error: cannot determine image filename for 'recovery.img'
so i cant even flash a recovery lol.
The correct command is "fastboot flash recovery NameOfRecoveryHere.img"
Sent from my ice cream powered Nexus S
That may be why it didnt work lol. I have managed to install cyanogen, i discovered i can use the search key instead of power whilst navigating the menu however to my horror Cyanogen no longer has 'volume to wake' installed lmao.
there are other roms out there that do like this one http://forum.xda-developers.com/showthread.php?t=1423404
Thanks, but i found out if i disable a screen lock i can wake with volume by default on ICS!
Then i covered one lockscreen with lock widgets haha, sorted. thanks guys
Hello there,
I just experienced a much-dreaded boot loop (both OS and Bootloader) when installing the newest Android Revolution Google Edition. I have the HTC One m7 (international), Canada.
I hope that what happened to me would help somebody else.
1. What I did:
I installed the latest TeamWin recovery 2.5.0.0
I then flashed Android Revolution 5.2
2. What happened:
a. There was an install error message
b. The phone got into a double boot loop: it would not load the Operating System and it would also not get into Recovery Mode. It was a constant loop.
3. Why did this happen:
You need TeamWin Recovery 2.6.3.3-m7 or else you end up with a bricked phone.
4. How I solved the problem:
Do this before start:
Install ADB and Fastboot if you don't have it. I use a Linux distro, but there are ADB and Fastboot files for Windows / Mac computers.
Google the Team Win Recovery file, download it and place it in the same folder where you have ADB and Fastboot.
Download Android Revolution GE Edition 5.2 and place the file in the same folder (ADB and Fastboot)
Now, the actual steps:
4.a) Press the power and volume down button at the same time. You will enter the HTC boot menu
4.b) Connect the phone to the computer
4.c) Select Fastboot on the phone, the volume buttons let you navigate, the power button is "enter"
4.d) Open a terminal / command line in your computer. Navigate to the ADB/Fastboot folder. Type: Fastboot devices. You should see the HTC One connected. Type: fastboot erase cache
4.e) Type on the computer: fastboot flash recovery twrp-2.6.3.3-m7.img
4.f) If things go well, you will see the message: sending 'recovery' (9184 KB)... OKAY writing 'recovery'... OKAY
4.g) Type in the computer terminal/ command line: fastboot boot twrp-2.6.3.3-m7.img
You should be now able to access the TeamWin recovery. Your phone is still useless, but at least the boot loop to recovery has been solved.
5. Installing the ROM
If you had your Android Revolution already in the internal SD card, you can flash it like any other custom ROM. This time, it will work.
If you don't have any ROM in your SD card, use the following command on the computer terminal: adb push [file name] Remember that the file must be in the same folder than ADB
Voilá! Your phone is back in business. I hope someone will find this useful. Good luck.
You're a lifesaver! Installed latest HD Revolution last night via CWM and got the bootloop. I also couldn't access the device in fastboot due to windows 8.1
This morning in work, I got back to recovery as my work pc is still on W7, and flashed TWRP but the same problem persisted. I was getting an error in the log at the end of the Aroma installer.
Stumbled across your post, and installed the slightly newer twrp and I'm now on the welcome wizard, so looking good.
Thanks!
You're a lifesaver! Weird how the recovery has so much influence (sorry if Im talking nonsense here, I just wasnt aware it could influence an install this much)
I got tired of CyanogenMod (especially taking photos looks like crap) so wanted my Sense back, nothing better out there than Rev HD
You're a champion!
Updated my girlfriend's phone but we were still on 2.5.x.x.
Once I flashed ARHD it would just boot in to recovery every time we turned it on. No amount of wipes and re-flashes would work.
Updated recovery to 2.6.3.3 and re-flashed and it's working great now!
Thanks!
---------- Post added at 12:10 PM ---------- Previous post was at 12:10 PM ----------
You're a champion!
Updated my girlfriend's phone but we were still on 2.5.x.x.
Once I flashed ARHD it would just boot in to recovery every time we turned it on. No amount of wipes and re-flashes would work.
Updated recovery to 2.6.3.3 and re-flashed and it's working great now!
Thanks!
---------- Post added at 12:11 PM ---------- Previous post was at 12:10 PM ----------
You're a champion!
Updated my girlfriend's phone but we were still on 2.5.x.x.
Once I flashed ARHD it would just boot in to recovery every time we turned it on. No amount of wipes and re-flashes would work.
Updated recovery to 2.6.3.3 and re-flashed and it's working great now!
Thanks!
You're a champion!
Updated my girlfriend's phone but we were still on 2.5.x.x.
Once I flashed ARHD it would just boot in to recovery every time we turned it on. No amount of wipes and re-flashes would work.
Updated recovery to 2.6.3.3 and re-flashed and it's working great now!
Thanks!
Massive thank you
Just registered to say that this forum post was a real life saver. Thank you so so much!
Best regards,
Rob
Thanks too
Hi
After trying to install crombi on tf700 using twrp 2.7 something went wrong and now tablette is bootlooping on twrp screen.
Cpnnected the tablette to laptop and nothing appears in the M'y Computer Windows.
Checked on device manager and found 'transformer' writen there with yellow exclamation Mark.
Tried to update driver with nô success.
Any help Will be greatly appreciated
Thanks
We need more information.
What did you come from?
What's your bootloader and rom versions?
Did you do a full wipe?
Describe in detail the procedure you followed.
berndblb said:
We need more information.
What did you come from?
What's your bootloader and rom versions?
Did you do a full wipe?
Describe in detail the procedure you followed.
Click to expand...
Click to collapse
Hi and thanks for the reply.
The tablet was on the latest Cromi-x and bootloader.
Did a full wipe and begun installing crombi
The tablet was stuck a long time on formatting so I had to regoot
After the reboot it was unable to moiunt E,
Tried to do another full wipe and now the tablet is just bootlooping on the TWRP splashscreen.
Any suggestion?
Formatting with TWRP 2.7 can take 90 minutes. You should not have interrupted it.
Can you get into fastboot?
Or alternatively you can try to get an adb connection when the tablet is looping.
berndblb said:
Formatting with TWRP 2.7 can take 90 minutes. You should not have interrupted it.
Can you get into fastboot?
Or alternatively you can try to get an adb connection when the tablet is looping.
Click to expand...
Click to collapse
Thanks for the answer so just connect the tablet, open cmd and do adb devices ?
Will try it in 30 min as I am not home
Tried the adb devices on a command windows in the platform-tools directory and nothing comes after hitting enter
Anything else to try?
What about fastboot? Boot with Volume Down and Power. Then try
'fastboot devices'
Sent from my DROID4 using Tapatalk
allotesting said:
Thanks for the answer so just connect the tablet, open cmd and do adb devices ?
Will try it in 30 min as I am not home
Tried the adb devices on a command windows in the platform-tools directory and nothing comes after hitting enter
Anything else to try?
Click to expand...
Click to collapse
Nothing? something must come up. What does it say? Command not found? No devices found?
sbdags said:
Nothing? something must come up. What does it say? Command not found? No devices found?
Click to expand...
Click to collapse
Hi
When I try the fastboot devices command it comes back to the invite with nothing written
When I try the adb devices nothing after list of devices attached
And the tablet keeps on bootlooping on the teamwin splash screen
And as already stated in device manager I find the mention transformer with yellow mark
Hi
Something new after I tried to update driver
Tried the fastboot command and it found something
It gives me s bunch of numbers and letters and recovery at the end
Is it good doctor?
Tried to install TWRP using fastboot -I 0x0B05 flsh recovery TWRP.blob and it sots there with the message <waiting for device> and tablet is still bootlooping:crying:
allotesting said:
Tried to install TWRP using fastboot -I 0x0B05 flsh recovery TWRP.blob and it sots there with the message <waiting for device> and tablet is still bootlooping:crying:
Click to expand...
Click to collapse
Are you in the boot loader when you issue that command?
By the way the bunch of numbers and letters are 0123456789ABCDEF and I have ASUS android ADB Interface under ASUS Android Devices in device manager
I don't know if this helps
Thanks
allotesting said:
By the way the bunch of numbers and letters are 0123456789ABCDEF and I have ASUS android ADB Interface under ASUS Android Devices in device manager
I don't know if this helps
Thanks
Click to expand...
Click to collapse
Yes that is normal. What happens when you flash twrp with fasboot. What does it report back?
allotesting said:
By the way the bunch of numbers and letters are 0123456789ABCDEF and I have ASUS android ADB Interface under ASUS Android Devices in device manager
I don't know if this helps
Thanks
Click to expand...
Click to collapse
Ok, I think we need to clear up some things:
If the tablet is bootlooping it cannot be in the bootloader and fastboot mode (you are in the bootloader menu when you see the 3 icons: RCK, Android, Wipe Data). But if you see the adb interface in Device Manager while it is looping you should have an adb connection and
Code:
adb devices
should return a similar but different string of numbers and letters.
Code:
adb reboot-bootloader
should boot you into the bootloader which is also fastboot mode.
In fastboot you should be able to flash TWRP with the command you posted, minus the typos naturally.
It has to be
Code:
fastboot devices
and it has to return the string of letters and numbers, then:
Code:
fastboot -i 0x0B05 flash recovery twrp.blob
Try that and report back
Hi there, I have the exact same problem. I tried searching all over about the time for a full wipe and couldn't find anything. So after about an hour I hard powered down. Of course, when I started researching the recovery look, I found the info (roughly 90-120 minutes). Here is what I have done to try to rectify, perhaps you can help. I booted into the bootloader and ran the following commands:
C:\>fastboot devices
015d2bbcc413ea10 fastboot
C:\>cd adb
C:\adb>dir
Volume in drive C has no label.
Volume Serial Number is 48F6-D102
Directory of C:\adb
04/29/2014 11:49 PM <DIR> .
04/29/2014 11:49 PM <DIR> ..
04/25/2014 06:59 AM 819,200 adb.exe
04/25/2014 06:59 AM 96,256 AdbWinApi.dll
04/25/2014 06:59 AM 60,928 AdbWinUsbApi.dll
04/25/2014 06:59 AM 160,256 fastboot.exe
04/29/2014 11:49 PM 6,443,112 openrecovery-twrp-2.7.0.0-tf700t.blob
5 File(s) 7,579,752 bytes
2 Dir(s) 672,096,153,600 bytes free
C:\adb>ren openrecovery-twrp-2.7.0.0-tf700t.blob twrp.blob
C:\adb>dir
Volume in drive C has no label.
Volume Serial Number is 48F6-D102
Directory of C:\adb
04/29/2014 11:50 PM <DIR> .
04/29/2014 11:50 PM <DIR> ..
04/25/2014 06:59 AM 819,200 adb.exe
04/25/2014 06:59 AM 96,256 AdbWinApi.dll
04/25/2014 06:59 AM 60,928 AdbWinUsbApi.dll
04/25/2014 06:59 AM 160,256 fastboot.exe
04/29/2014 11:49 PM 6,443,112 twrp.blob
5 File(s) 7,579,752 bytes
2 Dir(s) 672,096,088,064 bytes free
C:\adb>fastboot -i 0x0B05 flash recovery twrp.blob
sending 'recovery' (6292 KB)...
OKAY [ 2.459s]
writing 'recovery'...
OKAY [ 7.564s]
finished. total time: 10.023s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.022s
Click to expand...
Click to collapse
When I reboot into the bootloader and click RCK I get the TEAMWIN logo (blue screen). About every 2-3 seconds the screen goes black and the TEAMWIN logo shows again.
Thoughts?
---------- Post added 30th April 2014 at 12:16 AM ---------- Previous post was 29th April 2014 at 11:56 PM ----------
I decided to play around a little more to see what I could do. I pushed TWRP v2.6.3.2 to the device replacing v2.7. Finally I was able to get into TWRP. However, now I am stuck. TWRP asks me for a password that was never set (I don't have one). I hit cancel and the main menu and I show as having -1mb of internal storage.
If I try any commands, I am told that there aren't permissions to access the partitions. I feel like I am getting closer.
If I tell TWRP to FORMAT DATA in the WIPE menu, recovery restarts and asks me for my password again.
Thoughts?
BigKenW said:
Hi there, I have the exact same problem. I tried searching all over about the time for a full wipe and couldn't find anything. So after about an hour I hard powered down. Of course, when I started researching the recovery look, I found the info (roughly 90-120 minutes). Here is what I have done to try to rectify, perhaps you can help. I booted into the bootloader and ran the following commands:
When I reboot into the bootloader and click RCK I get the TEAMWIN logo (blue screen). About every 2-3 seconds the screen goes black and the TEAMWIN logo shows again.
Thoughts?
---------- Post added 30th April 2014 at 12:16 AM ---------- Previous post was 29th April 2014 at 11:56 PM ----------
I decided to play around a little more to see what I could do. I pushed TWRP v2.6.3.2 to the device replacing v2.7. Finally I was able to get into TWRP. However, now I am stuck. TWRP asks me for a password that was never set (I don't have one). I hit cancel and the main menu and I show as having -1mb of internal storage.
If I try any commands, I am told that there aren't permissions to access the partitions. I feel like I am getting closer.
If I tell TWRP to FORMAT DATA in the WIPE menu, recovery restarts and asks me for my password again.
Thoughts?
Click to expand...
Click to collapse
It seems as if TWRP thinks your data partition is encrypted.
Boot into recovery, make sure you have an adb connection with
Code:
adb devices
if that returns a string of letters and numbers try
Code:
adb killall recovery
This should get you back to recovery and then try to format data again.
Good luck
berndblb said:
It seems as if TWRP thinks your data partition is encrypted.
Boot into recovery, make sure you have an adb connection with
Code:
adb devices
if that returns a string of letters and numbers try
Code:
adb killall recovery
This should get you back to recovery and then try to format data again.
Good luck
Click to expand...
Click to collapse
Thanks for the advice. I actually reflashed to 5.7 and the password request is no longer there. That said, the device cannot mount anything inside. When I try ADB devices I am returned with nothing. That seems odd to me if fastboot commands work.
I searched around and a lot of people returned to full stock. I could also try the WIPE DATA option in the bootloader. But everything I have read is that is VERY bad. If I did that, even if I had to repush TWRP, would that be bad?
---------- Post added at 12:55 AM ---------- Previous post was at 12:33 AM ----------
BigKenW said:
Thanks for the advice. I actually reflashed to 5.7 and the password request is no longer there. That said, the device cannot mount anything inside. When I try ADB devices I am returned with nothing. That seems odd to me if fastboot commands work.
I searched around and a lot of people returned to full stock. I could also try the WIPE DATA option in the bootloader. But everything I have read is that is VERY bad. If I did that, even if I had to repush TWRP, would that be bad?
Click to expand...
Click to collapse
OK, I was able to get ADB going. The computer I was using didn't have the driver setup. That is fixed. The killall recovery command doesn't seem to work.
---------- Post added at 01:18 AM ---------- Previous post was at 12:55 AM ----------
BigKenW said:
Thanks for the advice. I actually reflashed to 5.7 and the password request is no longer there. That said, the device cannot mount anything inside. When I try ADB devices I am returned with nothing. That seems odd to me if fastboot commands work.
I searched around and a lot of people returned to full stock. I could also try the WIPE DATA option in the bootloader. But everything I have read is that is VERY bad. If I did that, even if I had to repush TWRP, would that be bad?
---------- Post added at 12:55 AM ---------- Previous post was at 12:33 AM ----------
OK, I was able to get ADB going. The computer I was using didn't have the driver setup. That is fixed. The killall recovery command doesn't seem to work.
Click to expand...
Click to collapse
Alright, nothing I can do will fix this thing. The internal drive shows 0mb. I even tried installing CWM and I can't mount any partitions. I would like to return to full stock. I can't seem to find anything like an RUU or other tool to do this. Can someone please direct me to the best thread to do so?
After I am back stock I will unlock the bootloader again.
I will follow all the commands when I will be back from work. It's 3:30 here in Montreal thanks guys
BigKenW said:
Thanks for the advice. I actually reflashed to 5.7 and the password request is no longer there. That said, the device cannot mount anything inside. When I try ADB devices I am returned with nothing. That seems odd to me if fastboot commands work.
I searched around and a lot of people returned to full stock. I could also try the WIPE DATA option in the bootloader. But everything I have read is that is VERY bad. If I did that, even if I had to repush TWRP, would that be bad?
---------- Post added at 12:55 AM ---------- Previous post was at 12:33 AM ----------
OK, I was able to get ADB going. The computer I was using didn't have the driver setup. That is fixed. The killall recovery command doesn't seem to work.
---------- Post added at 01:18 AM ---------- Previous post was at 12:55 AM ----------
Alright, nothing I can do will fix this thing. The internal drive shows 0mb. I even tried installing CWM and I can't mount any partitions. I would like to return to full stock. I can't seem to find anything like an RUU or other tool to do this. Can someone please direct me to the best thread to do so?
After I am back stock I will unlock the bootloader again.
Click to expand...
Click to collapse
To return to stock just download the Asus firmware, unzip it once and flash the resulting zip in recovery.
Your bootloader will stay unlocked. You just have to flash a custom recovery again, reboot and then flash the rom.
allotesting said:
I will follow all the commands when I will be back from work. It's 3:30 here in Montreal thanks guys
Click to expand...
Click to collapse
Hi all
Back from work but all the commands were uselee
In device manager I have ASUS android ADB interface after updating manually the 'transformer' that I had with the yellow matk
When trying adb devices it comes with 0123456789ABCDEF all the hexadecimal digits so seems to me that the machine does not recognize the tablet itself
When trying fastboot devices and hit enter it comes back to the >invite
When trying adb reboot-bootloader it just sits there with even no >invite
Forgot to mention that the word recovery comes after the 0123456789ABCDEF on the adb devices
Anything else to try? Thanks
After some people and me discovered that there is no real collection for the most up-to-date recoveryimages, for Cyanogenmod based Roms i decided to create this thread in order to change this.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Recoverys:
PhilZ Touch Recovery 6.59.0 (CWM Version 6.0.5.0)
TWRP 3.0.0
Installation
Download the recovery images in the Download section reboot your phone into fastboot mode and execute the command
Code:
fastboot flash recovery *name of the recoveryimage you downloaded*.img
in fastboot.
When you want to flash it from your phone, navigate into the folder where you downloaded the recoveryimage and execute the command:
Code:
dd if="*name of the recoveryimage you downloaded*.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
as root in Terminal Emulator.
Download Castor (LTE-Version):
PhilZ Touch Recovery
TWRP 2.8.7.0
TWRP 3.0.0 (only aosp m and cm13 compatible)
Download Castor_windy (WIFI-Version):
PhilZ Touch Recovery
TWRP 2.8.7.0
TWRP 3.0.0 (only aosp m and cm13 compatible)
Sources:
PhilZ Touch Recovery
TWRP
XDA:DevDB Information
[TWRP/CWM/PhilZ]Recovery Collection, Tool/Utility for the Sony Xperia Z2 Tablet
Contributors
rcstar6696
Version Information
Status: Beta
Created 2015-03-12
Last Updated 2015-07-30
Reserved
Other Information:
Nothing at the Moment
Reserved
Have fun and report back
I hope all is working
rcstar6696 said:
Have fun and report back
I hope all is working
Click to expand...
Click to collapse
thanks for the update. in the file name before the extension of extra space
openrecovery-twrp-2.8.5.0-castor_windy .img
venoom said:
thanks for the update. in the file name before the extension of extra space
openrecovery-twrp-2.8.5.0-castor_windy .img
Click to expand...
Click to collapse
Thanks the Name is fixed
Thanks @rcstar6696! These threads are what we need more, up-to-date and clear I'll try these asap..
anyone able to get this TWRP to work with CM12? I have flashed it successfully in fastboot and it allows me to boot the latest official cm12 3/11 and it boots fine. I cant boot into TWRP. When i use advanced reboot from within CM12 to boot to recovery, it boots to the cyanogenmod recovery and not Twrp.
Edit: I just tried to reboot to recovery using volume up on power up and got into TWRP. Seems that the advanced reboot feature in CM wont allow me to boot to twrp, you have to do it manually.
bacon612 said:
anyone able to get this TWRP to work with CM12? I have flashed it successfully in fastboot and it allows me to boot the latest official cm12 3/11 and it boots fine. I cant boot into TWRP. When i use advanced reboot from within CM12 to boot to recovery, it boots to the cyanogenmod recovery and not Twrp.
Edit: I just tried to reboot to recovery using volume up on power up and got into TWRP. Seems that the advanced reboot feature in CM wont allow me to boot to twrp, you have to do it manually.
Click to expand...
Click to collapse
I will test it later this weekend philz touch works without problems
Is some (or many of these) recovery compatible with cm updater? Unable to test it just yet, but soon..
Not sure. I'll mess around this afternoon. I'm a little confused how I have access to two recoveries
rockknee said:
Is some (or many of these) recovery compatible with cm updater? Unable to test it just yet, but soon..
Click to expand...
Click to collapse
cwm is compatible with the cm updater
The others are not tested with the updater
I was finally able to unlock the bootloader and throw some custom stuff on my tab but... It didn't kinda go the way I thought first As a sonynoob I wanted to just install cm first with the instructions from their wiki, well the cm recovery I first installed sucked really bad. I have no idea what the others have done to get adb push (or sideload) working with it but I obviously had a device with cm boot.img and nothing on my internal storage due to unlocking process. And that got damn recovery didn't have option to mount usb-otg nor my fastboot on PC didn't recognize any adb devices, sideload did nothing. I reinstalled all drivers multiple times, still nothing. Then I flashed TWRP from this thread and vòla, everything worked. So I'm very grateful from these recovery images right here! TWRP seems to be very functional, haven't tried cm updates yet tho... :good:
bacon612 said:
anyone able to get this TWRP to work with CM12? I have flashed it successfully in fastboot and it allows me to boot the latest official cm12 3/11 and it boots fine. I cant boot into TWRP. When i use advanced reboot from within CM12 to boot to recovery, it boots to the cyanogenmod recovery and not Twrp.
Edit: I just tried to reboot to recovery using volume up on power up and got into TWRP. Seems that the advanced reboot feature in CM wont allow me to boot to twrp, you have to do it manually.
Click to expand...
Click to collapse
I just tried to boot TWRP recovery from advanced boot menu and it actually worked. Only different most likely is that I installed twrp before I had flashed cm. So if you can't get it to work otherwise you can always try to fastboot erase the whole device and start from scratch by installing first twrp.
rockknee said:
I was finally able to unlock the bootloader and throw some custom stuff on my tab but... It didn't kinda go the way I thought first As a sonynoob I wanted to just install cm first with the instructions from their wiki, well the cm recovery I first installed sucked really bad. I have no idea what the others have done to get adb push (or sideload) working with it but I obviously had a device with cm boot.img and nothing on my internal storage due to unlocking process. And that got damn recovery didn't have option to mount usb-otg nor my fastboot on PC didn't recognize any adb devices, sideload did nothing. I reinstalled all drivers multiple times, still nothing. Then I flashed TWRP from this thread and vòla, everything worked. So I'm very grateful from these recovery images right here! TWRP seems to be very functional, haven't tried cm updates yet tho... :good:
I just tried to boot TWRP recovery from advanced boot menu and it actually worked. Only different most likely is that I installed twrp before I had flashed cm. So if you can't get it to work otherwise you can always try to fastboot erase the whole device and start from scratch by installing first twrp.
Click to expand...
Click to collapse
I have a new z2 tablet with 4.4.4 KitKat and I want to install a custom OS. I already unlocked the bootloader.. Please put me through the steps you followed to achieve this
toole said:
I have a new z2 tablet with 4.4.4 KitKat and I want to install a custom OS. I already unlocked the bootloader.. Please put me through the steps you followed to achieve this
Click to expand...
Click to collapse
Instruction to flash is in op.
You need to set up your PC with adb and fasboot. (Google)
Put your tab in bootloader mode. Power on and vol down. Blue led indicates you are in bootloader mode.
Use said fast boot command as stated in op to flash the recovery you want.
Use recovery to flash your previously downloaded CyanogenMod build.
---------- Post added at 11:30 AM ---------- Previous post was at 11:29 AM ----------
rockknee said:
I was finally able to unlock the bootloader and throw some custom stuff on my tab but... It didn't kinda go the way I thought first As a sonynoob I wanted to just install cm first with the instructions from their wiki, well the cm recovery I first installed sucked really bad. I have no idea what the others have done to get adb push (or sideload) working with it but I obviously had a device with cm boot.img and nothing on my internal storage due to unlocking process. And that got damn recovery didn't have option to mount usb-otg nor my fastboot on PC didn't recognize any adb devices, sideload did nothing. I reinstalled all drivers multiple times, still nothing. Then I flashed TWRP from this thread and vòla, everything worked. So I'm very grateful from these recovery images right here! TWRP seems to be very functional, haven't tried cm updates yet tho... :good:
I just tried to boot TWRP recovery from advanced boot menu and it actually worked. Only different most likely is that I installed twrp before I had flashed cm. So if you can't get it to work otherwise you can always try to fastboot erase the whole device and start from scratch by installing first twrp.
Click to expand...
Click to collapse
Which build of CyanogenMod are you running. Fxp or official from CyanogenMod
---------- Post added at 12:03 PM ---------- Previous post was at 11:30 AM ----------
bacon612 said:
Not sure. I'll mess around this afternoon. I'm a little confused how I have access to two recoveries
Click to expand...
Click to collapse
Second reboot to recovery from cm got me right to twrp. Not sure why it didn't the first time.
bacon612 said:
Instruction to flash is in op.
You need to set up your PC with adb and fasboot. (Google)
Put your tab in bootloader mode. Power on and vol down. Blue led indicates you are in bootloader mode.
Use said fast boot command as stated in op to flash the recovery you want.
Use recovery to flash your previously downloaded CyanogenMod build.
---------- Post added at 11:30 AM ---------- Previous post was at 11:29 AM ----------
Which build of CyanogenMod are you running. Fxp or official from CyanogenMod
---------- Post added at 12:03 PM ---------- Previous post was at 11:30 AM ----------
Second reboot to recovery from cm got me right to twrp. Not sure why it didn't the first time.
Click to expand...
Click to collapse
Thanks ill give it a trial.. I can't get fastboot commands to work on my windows 8.1 laptop.. fed up: (
bacon612 said:
Instruction to flash is in op.
You need to set up your PC with adb and fasboot. (Google)
Put your tab in bootloader mode. Power on and vol down. Blue led indicates you are in bootloader mode.
Use said fast boot command as stated in op to flash the recovery you want.
Use recovery to flash your previously downloaded CyanogenMod build.
---------- Post added at 11:30 AM ---------- Previous post was at 11:29 AM ----------
Which build of CyanogenMod are you running. Fxp or official from CyanogenMod
---------- Post added at 12:03 PM ---------- Previous post was at 11:30 AM ----------
Second reboot to recovery from cm got me right to twrp. Not sure why it didn't the first time.
Click to expand...
Click to collapse
I'm running the official cm builds.
---------- Post added at 07:33 PM ---------- Previous post was at 07:28 PM ----------
toole said:
Thanks ill give it a trial.. I can't get fastboot commands to work on my windows 8.1 laptop.. fed up: (
Click to expand...
Click to collapse
What does the fastboot say then? No device found or sth like that? If so, try these drivers http://forum.xda-developers.com/showthread.php?t=2635830
Should work after you have installed those.. I had problems with win8 too because PC didn't recognize any fastboot devices. Btw you can always try and see if the device is recognized by "fastboot devices" command.
---------- Post added at 07:36 PM ---------- Previous post was at 07:33 PM ----------
rcstar6696 said:
cwm is compatible with the cm updater
The others are not tested with the updater
Click to expand...
Click to collapse
Twrp is compatible as well! Just informing even tho you or others might have already noticed that too.. Just flashed the latest nightly succesfully
rockknee said:
I'm running the official cm builds.
---------- Post added at 07:33 PM ---------- Previous post was at 07:28 PM ----------
What does the fastboot say then? No device found or sth like that? If so, try these drivers http://forum.xda-developers.com/showthread.php?t=2635830
Should work after you have installed those.. I had problems with win8 too because PC didn't recognize any fastboot devices. Btw you can always try and see if the device is recognized by "fastboot devices" command.
---------- Post added at 07:36 PM ---------- Previous post was at 07:33 PM ----------
Twrp is compatible as well! Just informing even tho you or others might have already noticed that too.. Just flashed the latest nightly succesfully
Click to expand...
Click to collapse
Interesting. Was twrp still there after the nightly flash? Or did it get overwritten with the cm recovery?
bacon612 said:
Interesting. Was twrp still there after the nightly flash? Or did it get overwritten with the cm recovery?
Click to expand...
Click to collapse
It didn't get overwritten. After I had updated one nighlty using cm updater I even did one clean flash (due to random wakelocks I got) and twrp booted from advanced boot menu correctly. Shouldn't this be normal behaviour? It's kinda weird tho to have one recovery on the FOTA partition and other integrated to boot partition, clearly twrp overcomes somehow the cm recovery that is on the boot..
will this work with the latest lollipop stock?
EDIT: Still open to suggestions, but am going to try the method posted Here and see if this works. (I have been searching forums, but I didn't find this link until after I posted, sorry admins)
So I was screwing around and booting TWRP through fastboot earlier(fastboot boot twrp-etc.etc), and ran the zip to install it in a stupid way(adb sideload, which I wasn't thinking and should have just flashed in fastboot first).
Now my bootloader comes up, but I have no recovery, and for some reason fastboot is not detected by my Windows PC or my Fedora Linux system.
If I turn the phone off and back on, it gives me ERROR: Slot Unbootable: Load Error.
Am I mega-screwed with a hard-brick since Windows and Linux can't even detect the phone in fastboot/bootloader anymore?
I've been researching was to get into the Qualcomm EDL, but can't find many resources in regards to the Pixel 2
Bought this device from a reputable dealer on Swappa, and it turns out the phone is still in warranty with Google, but not sure if it will cover something
that is obviously my own ****-up
Here's a short list of details that I'm going assume anyone who could help will need to know:
Bootloader: Unlocked
Bootloader: Shows up and gives me standard options [Start->Restart Bootloader->Download Mode->Recovery->Barcodes->Power-Off]
Spitting out ERROR: Slot Unbootable: Load Error
System partition: None
Recovery partition: Corrupted/none
Fastboot: Not working at all(was previously working, and still detects my Verizon Pixel if I go into bootloader menu)
Same exact problem Here...
---------- Post added at 04:41 PM ---------- Previous post was at 03:46 PM ----------
FIXED
I fixed it by completely draining the battery by maintaining the power button held with a rubberband. Then when the little red light was flashing I plugged the phone in the pc and after a few seconds the bootloader showed up and my phone was detected.
Optional: When flashing stock with flash-all.bat I was always betting ''archive does not contain xxxx'' and then my phone wouldn't boot. Ultimately I extracted the 20+ files in the zip image file and manually flashed all img files with fastboot, then I relocked the bootloader and now everything is working fine !
emile567 said:
Same exact problem Here...
---------- Post added at 04:41 PM ---------- Previous post was at 03:46 PM ----------
FIXED
I fixed it by completely draining the battery by maintaining the power button held with a rubberband. Then when the little red light was flashing I plugged the phone in the pc and after a few seconds the bootloader showed up and my phone was detected.
Optional: When flashing stock with flash-all.bat I was always betting ''archive does not contain xxxx'' and then my phone wouldn't boot. Ultimately I extracted the 20+ files in the zip image file and manually flashed all img files with fastboot, then I relocked the bootloader and now everything is working fine !
Click to expand...
Click to collapse
You didn't need to drain the battery completely. Just holding the power button for 10seconds is sufficient for the phone to be detected.