[Q] Accessing CWM from powerd-off - Vega General

Hi! Is there any way for me to access the CWM from powerd-off mode? My ViewPad 10s has just stopped booting into Android, and it's kinda frustrating. I'm currently running JB Beta 3 and was hoping that I could flash the Beta 5 via CWM, so I don't lose my data. Or can I make the NVFlash version keep my data in one or another way?

I don't think you can get into recovery from boot with these tablets. Best bet is to remove the micro sd card and back up the information that you can. Then reinstall using nv flash. And try and restore and data you can that way.
Sent from my Galaxy Nexus using Tapatalk 2

2minuutes said:
Hi! Is there any way for me to access the CWM from powerd-off mode? My ViewPad 10s has just stopped booting into Android, and it's kinda frustrating. I'm currently running JB Beta 3 and was hoping that I could flash the Beta 5 via CWM, so I don't lose my data. Or can I make the NVFlash version keep my data in one or another way?
Click to expand...
Click to collapse
(Probably no use to you now but may help others...) You could try and flash recovery.img to the boot partition via nvflash:
sudo nvflash --bl bootloader.bin --download 7 recovery.img from linux or
nvflash.exe --bl bootloader.bin --download 7 recovery.img from windows

recovery?
the only thing i know you can do from power off is enter recovery mode, connect your vega to a pc by a usb cable..
Hold the power button, and count 6 seconds, after 6 seconds the screen will blink off, at this exact point release the power button and begin holding the back button for 6 seconds, after those 6 seconds keep the button held but hold the power button also for 2 seconds, so both are pressed, after those 2 seconds you should see the safely remove icon pop up in your startbar (like when you plug in a usb stick) and then let go of back, wait a second and let go of power
NOTE THIS WORKS ON ALL ROMS
at this point the screen will be blank but if you unplug every usb device but the vega cable, and the safely remove is still there then its in recovery.
if you havent used recovery mode before then install the vega recovry drivers off the myadventvega website by opening device manager, clicking your vega (should have a yellow triangle with a ! next to the icon) and click install driver, choose not to search online, say you have a CD or files, and point it to the folder which you downloaded from myadventvega [NOTE NOT THE FOLDER INSIDE THE FOLDER YOU DOWNLOADED< JUST THE FOLDER WITH TWO OTHER FOLDERS INSIDE IT.}
after you are free to download the rom of your choice (The nvflash mode) and run it to install it

Related

[Q] Possible Brick. Please help!

Hello,
I tried installing a ROM (Axura) for the first time on my Vibrant. This is what I did:
1. Rooted using z4root's app.
2. Backed up installed ROM (stock 2.1 update 1) using ROM Manager app.
3. Installed CWM.
4. Downloaded Axura v2.3.0.0 from their forum.
5. Placed it in internal SD and renamed to update.zip (backed up the original on my external SD). <-- Possibly the cause of my dismay.
6. Installed it through CWM.
It was installing fine till it got stuck at the fourth "copying file..." line. Was there for over an hour. Now, every time I boot my device it shows Vibrant splash screen and goes to Android System Recovery instead of loading up.
Can anyone please help me out? I think it's a soft brick, since recovery is still being loaded up. Please!
NOTE:
1. reinstall packages gives this error:
E:Can't open /sdcard/update.zip
(bad)
2. abd displays: "error: device not found".
1st you should not have changed auxura to update.zip
You need to odin back to stock.
I might be wrong
But changing name doesnt really matter. It look like u just got a bad download. Odin back and redownload the Rom.
bionix 1.2.1 with adw launcher ex
Yes odin back to stock. Then Root, then get CWM and install. Do not rename the Axura or any custom rom,, this will make it hard for you keeping track. THen after root go to recovery >install rom on sd card> choose> then find the one you want and click that one and you are good to go.
thanks for all the responses! I tried ODIN, but the issue is I can never get into download mode. If I press vol+/- and power I get into recovery. When I try the same with USB connected, the screen keeps looping at the charge screen.
ODIN was able to detect the device in recovery mode at times. but if I try recovery it gives cannot open port.
I'm following the steps (and the required files) from androidspin.com/2010/08/09/how-to-restore-or-recover-your-samsung-vibrant/
Turn the phone off hold up & down on the vibrant volume then plug the usb in while holding it down. Make sure odin is open first. No need to touch the power button.
Sent from my SGH-T959 using XDA App
When I try vol+/- and then plugging in the usb (not pressing power at all), it still brings me to recovery screen. the only difference is it skips the "Vibrant SAMSUNG" splash screen.
Also, i realized tht connecting to a different usb port, the command "adb devices" lists the device in recovery. but "adb reboot download" (or any othr reboot command) simply hangs thr, until break command is given..
Any help to get me into download mode? it's been only 4 months, I don't want to discard the device so soon.
azoicwight said:
When I try vol+/- and then plugging in the usb (not pressing power at all), it still brings me to recovery screen. the only difference is it skips the "Vibrant SAMSUNG" splash screen.
Also, i realized tht connecting to a different usb port, the command "adb devices" lists the device in recovery. but "adb reboot download" (or any othr reboot command) simply hangs thr, until break command is given..
Any help to get me into download mode? it's been only 4 months, I don't want to discard the device so soon.
Click to expand...
Click to collapse
Did you try pulling your battery. then press vol + - while holding the power button while inserting the battery?

How to install custom roms like Corvus5 and other ?

How to install custom roms like Corvus5 and other ? with
CWM?
I got my Vega 2 days ago and first thing I did was put Vegacomb on it, here's a guide I knocked myself up from various forums to do that:
turn on tablet and turn on USB debugging
shut down the Vega (hold down power for 6 seconds)
Launch VegaTools
go to extras tab
Start USBDeview
within USBDeview find and uninstall all nVideia devices (right click and uninstall)
with vega turned off, connect to PC via USB
hold the back button for 2 seconds
while still holding back, hold power buttons for 2 seconds
release power button but hold the back button for 2 seconds
the Vega should then boot into recovery (nothing on screen, not even backlight)
Windows will find a new device with no drivers
Start AUDI by right clicking and running as administrator
choose “I want to install the Advent “stock ROM” using recovery”
The red box at the bottom should now say “The recovery driver is NOT correctly installed. Proceed to step 3”
Press the Next step button.
proceed to press the “Part C: Install correct driver” button, and in the prompt choose “Just get on with it. Do it for me!” and click the Do it button.
Installing ModdedStock:
run the VegaModdedStock_v1.10_v2.exe file as Administrator.
turn the tablet on
Installing VegaComb:
go into Recovery App (on the Vega)
this will enter clockwork recovery
(volume = up & down, power = enter, back = back)
nandroid backup
Partition the SD card to allow Apps2SD
Turn on USB host to put the vegacomb ROM on the SD card
wipe data/factory reset
wipe cache partition
advanced > wipe dalvik cache
toggle signature verification (set to disabled)
choose zip from SD
find the vegacomb ROM
choose zip from SD
find the vegacomb ROM update
reboot system now
done!
ql4w0j7 said:
How to install custom roms like Corvus5 and other ? with
CWM?
Click to expand...
Click to collapse
Hello mate,
If your like me and wantra simple walk through... follow this guide
http://www.hungrycodemonkey.com/blo...t-vega-android-tablet-vegacomb-beta-–-part-2/
just remember to includded the modded stock rom, its not in this guide but some one has commented about it so follow there link.

[Q] DVC P10 (Venus Pad)

Hi, I'm new in this forum.
I'm looking for a firmware which is working on my Venus Pad. I've flashed it a few weeks ago and since the flashing its only displaying a message which says ''If you have Paid for a newer Version of Android you've...''.
Please could anyone help me. The Tablet is'nt starting anymore until the message. I couldent get into the clockwork recovery menu. I want to flash it but I dont know which program I need and which firmware I could use.
Greetz
Taitanium
Bad flash?
Try to reflash or try different modded stock?
I've flashed it with clockwork, but now I couldnt get into the cwm. I need a program to flash it and a working firmware. Please help me, the tablet was so expensive-.-
Try the ROM again or try a different ROM that will partition you Nand ram differently to avoid the bad blocks that are causing the error.
You will need to flash it with NVflash recovery to restore it to functionality.
The previous flash didn’t write properly to your boot partition so you cant boot android and select reboot to recovery (which will boot CWM recovery from the recovery partition). Because you cant boot Android there is no way easy was to boot the recovery partition (where CWM recovery is located). The way to fix this is to use NVflash recovery to flash a ROM with a PC.
To put the tablet into NVflash mode the table first needs to be switch off properly. Sometimes it looks off when its not. To get around the hold the power button for 10 second before you start the back/power button thing. Now hold the back button for at least 2 seconds, without releasing the back button press the power button for 2 seconds and then release it, now keep holding the back button for a further 2 second. You will now be in NVflash mode, if you where connected to the PC while you did the back/power button thing the Pc should have pinged to say the device has been

[Solved-Q] Must be a moron, but I just can't get vol+/power-button to CWM-R to work

This is a painful message to write, but I am desparate. This should be so simple!
Have a U8800 standard (at least it says only "U8800" in settings/about phone.
What have I done:
- Upgraded some time ago to 2.3.5 Rev B522 from Huawei.
- Then rooted it with SuperOneClick.
- Installed ClockWorkMod from Play Store.
- Downloaded CWM Recovery 5.5.0.4 stable from xda and placed the file into the /.cust-backup/image folder via Remount.
- Turned off Fast boot under settings/applications
:: What worked/happened.
- Rooting went fine, ES file explorer and others get root-permissions ok.
- But got into CWMRecovery only via CWM program (Choosing "Reboot into recovery"). Never with the holding buttons vol+ and power-button during power-on.
Figured it was that locked bootloader on B522 that was the problem.
What I did:
- Followed the instructions in http://forum.xda-developers.com/showthread.php?t=1457490 (Get your pink screen back).
- In CWM Recovery flashed "update-B518-bootloader.zip".
- Got "ok installed or something to that effect" from CWM Recovery.
:: What worked/happened.
- Still could not get into CWMRecovery via button-holding. Tried reflashing the B518 bootloader a few times, but just no difference.
Read somewhere that each Huawei firmware-release comes with it's own bootloader, so lets try to install Huawei B518.
- Only place I could find the image was here http://huaweiideosx5.blogspot.no/2012/03/u8800-b518-23-software.html
- U8800V100R001C00B518G001.zip
- Had to take out the external SD-card to get the /sdcard/dload directory on the internal SD-card.
-Seems to be important to have dload on the internal SD-card and not the external.
- Booting the phone with vol+, vol-, power did not start the downgrade, but was able to trigger it via settings/storage/software upgrade.
After downgrade to B518 (Checked version in settings/about phone):
- Deleted /sdcard/dload directory.
- Rooted with SuperOneClick
- Installed ClockWorkMod from play store again.
- Put CWM Recovery 5.5.0.4 into ./cust_backup/image again (think this was unecessary. I think it was already there but did it anyways)
- Turned off Fast boot under settings/applications.
:: What worked/happened.
- The phone is now in B518 software, but still can not get into CWM Recovery via keypressing at boot.
I hold the vol+ and power-buttons all the way to "desktop" so to say, but can not for the life of me get into CWM Recovery that way. Getting into CWM recovery 5.5.0.4 via instructing CWM application to boot into recovery works fine, though.
I am drooling at the thought of ICS Aurora, but I don't dare before I can reliably get into CWM Recovery via keypress.
Sorry if this is very stupid post, but I have tried so much.
Maybe the volume buttons are faulty? Turn off the phone and try this: hold down volume up; while holding press power button as long as the logo comes up. Release power button but continue holding volume up. If it did not work, try doing same with volume down.
Yeah, do what Blefish advised you but do it while the phone is off and charging. I have a kinda broken power key and with this 'trick' it boots faster and more reliable. Keep holding the 3 buttons until you see the recovery.
Sent from my U8800
Thank you both for trying to help me here!
Unfortunately I have had no luck with your suggestions.
Re: Broken keys.
Power and volume-buttons seems to work well when the phone is on. Also when I boot into recovery through the CWM program, navigate to advanced/key-test, the vol+, vol- and power button seems to work well there too.
On pressing the power-button, CWM-R reports Key: 116
On pressing the vol+-button, CWM-R reports Key: 115
On pressing the vol--button, CWM-R reports Key: 114
So I think the keys must be ok, right?
Blefish: I did what you suggested, as I understood it.
When the phone boots, there are three stages of logos.
1. A static logo of Huawei's red "fan?".
2. A short "comet" animation.
3. An animated logo of Huawei's "fan", where some highlight flashes from left to right over the fan.
I hold the power-button in until I see the first static logo, then let go of the power-button and hold the volume-key(s).
Is this the same stage in the boot-process that you were thinking of?
I have tried vol+, vol- and both vol+ and vol-, together with releasing the power-button at that point.
Have not had any success with that, and ended on the "desktop" each time.
AceDroidX: I tried your suggestion as well.
I did this:
1. Shut down the telephone
2. Plugged in the power.
3. A "fan"-logo appears which is replaced by an animated battery.
4. Upon seeing the animated battery, I tried the various key-hold variants.
- vol+ and power : Ended up at desktop.
- vol- and power : Ended up at desktop.
- vol+ and vol- and power : Ended up at desktop.
So not much success either.
I am out of ideas... Can it be that B522 bootloader that still lingers in there, not replaced by installing the B518 software?
Well, idk what else to suggest.. Maybe your problem is here?
Downloaded CWM Recovery 5.5.0.4 stable from xda and placed the file into the /.cust-backup/image folder via Remount.
Click to expand...
Click to collapse
I remember that when i mount my phone in linux, there was a partition with just the image folder. Some files like boot.img and recovery.img where there. Try to put the recovery image in there and see if it makes any difference.
I'd like see your versioninfo, can you upload a screenshot?
You can check mine from B528
AceDroidX: When I use Remount, I am able to mount that partition as read/write so that I can copy CWM's Recovery image in there. I think it is identical as mounting it up remotely, as you do. I am after all able to boot into CWM-Recovery, just not by key-pressing? I suppose I could boot into Linux and try to mount up the partitions as you do.
Hi kilroystyx: I can not figure out where to find a similar-looking page as the one you have in your picture.
I have the settings/about phone, if that is an older version of what you have there?
Treq01 said:
Hi kilroystyx: I can not figure out where to find a similar-looking page as the one you have in your picture.
I have the settings/about phone, if that is an older version of what you have there?
Click to expand...
Click to collapse
You have to dial *#*#2846579#*#*
Off.. I completely forgot about that place!
Here are the right screenshots.
What can you see from this?
Treq01 said:
Off.. I completely forgot about that place!
Here are the right screenshots.
What can you see from this?
Click to expand...
Click to collapse
Based on the screenshots your installation is fine.
Just one last shoot based on what AceDroidX says, with phone off press Vol+ and hold then connect USB cable to PC or charger and stay holding Vol+ then wait...wait and what you see?
hi all,
i'm using some ics roms and it seems ics supports natively vol++power button to take screenshots but it doesnt work for me... do you know if there are some custom ics rom where it will work?
thank you
Wow.. It is hard to believe.. but I have actually ... eventually found a way to get into that CWM-Recovery every time.
It is a combination of your suggestions.
I have been doing variations, trying to figure something out and eventually there is a method.
What I must do, on this phone, in order to get into CWM-R is this:
1. If the charging cable is in, then unplug first.
2. Turn the phone off.
3. Take out the battery and put it back in.
- This makes a difference on my phone, at least. I am not able to get into CWM-R wihtout taking the battery out first.
4. Press and hold Vol+
5. With Vol+ being pressed continously, insert the charging-cable.
6. Wait for the Fan-animation to finish and the "battery-charging" animation to start.
7. When the battery-charging animation is running and the screen eventually goes black, keep holding the Vol+ button for some time.
- Sometimes it works to keep holding the Vol+ button for only a second or two. Sometimes I must hold it up to 30 seconds.
7. Press and hold the power-button in addition to the Vol+
8. Wait for CWM-Recovery to start.
Thank you very much for your help.
Now I think I can try for ICS!
imsonica said:
hi all,
i'm using some ics roms and it seems ics supports natively vol++power button to take screenshots but it doesnt work for me... do you know if there are some custom ics rom where it will work?
thank you
Click to expand...
Click to collapse
Try Vol- and Power ON

[TUTORIAL][CM11][4.4.2] CyanogenMod Tutorial for Sony Xperia Tablet Z (pollux)

I went through a lot of searching and trouble to install CM11 on my Xperia Tablet Z, and I'd like to share a tutorial I made for anyone who is also wanting to accomplish this.
All links are in Dark Green because I cannot post links yet.
1. Download and extract the ADB+Fastboot+Drivers zip (alexpja.com/sony/adb-fastboot-win.zip)
2. Now we’ll unlock the bootloader.
a. If you do not have a Phone app (like I don’t on the SGP351), you can either get the IMEI from About -> Status in the settings OR you can find the IMEI right after the IC code, nearby the barcode on the bottom of the tablet.
b. If you do have a Phone app, enter *#06# to retrieve the IMEI.
c. Save this for later use.​3. Place the tablet into fastboot mode and connect it to the computer.
a. Power off the device
b. Connect USB to computer
c. While plugging in the other side of the USB cable into the tablet, hold down the Vol + button.
d. If your speakers are on, you should a sound.
e. We have to install the drivers for fastboot. Open devmgmt.msc via the Run window or in the Start menu and in Other Devices section, you should see S1 Service or S1 Fastboot (anything containing S1).
i. If it is showing a yellow exclamation mark: Follow 3.e.i.1. If it is not, continue to 3.f.
1. We need to download Flashtool and use the driver setup. Download Flashtool (unrestrict.li/flashtool) and install it.
2. Find cmd.exe, right click it, and select Run as administrator.
a. Type in
Code:
bcdedit /set testsigning on
and press enter.
b. Reboot your computer.​3. Once you have rebooted the computer, open the folder where you installed Flashtool (default: C:\Flashtool).
4. Open up the drivers folder and open Flashtool-drivers.exe.
5. Select the first two driver choices (Flashmode and Fastboot) and select “Xperia Tablet Z Drivers” and continue.
6. A new window will appear, continue on with that.
7. A window like this may appear a few times, just press Install this driver software anyway.
8. Run 3.e.2. again and run
Code:
bcdedit /set testsigning off
. Reboot your PC now or after the tutorial.​f. The LED pulse light above it should be emitting a blue-ish color. The screen will be dark.​4. Now we’ll verify if you have fastboot running.
a. Open the tools folder that was extracted from the ADB ZIP and double-click on START.cmd to open Command Prompt in the current directory (all it does is literally open cmd.exe, you can edit the script to verify).
b. Run the command
Code:
fastboot -i 0x0fce getvar version
. If you get
Code:
<waiting for device>
, then you did something wrong. Retrace your steps! (For example, I get
Code:
version: 0.5
)​5. Go to (unlockbootloader.sonymobile.com) and continue until you reach the screen where you put type in the IMEI and an email address. Type in the first 14 digits of the IMEI (remove the last one) and your email address (not sure if name is required). You should get an email instantly with the key.
6. In the Command Prompt, run
Code:
fastboot -i 0x0fce oem unlock 0xKEY
where KEY is the key you received in the email from Sony.
7. Download whatever release you would like to use on the tablet (I’m using CM 11 nightly) from (download.cyanogenmod.org/?device=pollux)
a. Optional: Also download gapps for Google apps such as Gmail, Google Play Services, etc. (wiki.cyanogenmod.org/w/Google_Apps)​8. Extract the ZIP file (but don’t delete it either) and copy boot.img to the tools folder.
9. If your device is still turned off, turn it on and enable USB storage mode. Copy the CM zip to either the internal storage (sdcard) or, if one is inserted, the microSD card (sdcard1).
10. Place it into fastboot mode again (#3).
11. Go back into the Command Prompt and enter:
a.
Code:
fastboot -i 0xfce flash boot boot.img
b.
Code:
fastboot -i 0xfce reboot
c. Enter recovery.
1. Once it shuts down, rapidly tap the Vol + button in order to get into the recovery.
2. Grep_The_Truth's tip: Look at the LED. It will turn orange and afterwards it'll turn purple. You want to press Vol+ as soon as it changes colors.​12. Select “wipe data/factory reset” and wipe it. Afterwards, go back to main menu.
13. Select “Install zip” and either select “Choose zip from /sdcard” (internal storage) or “Choose zip from /storage/sdcard1” (microSD card).
I’ve had varying experience with installing from the /sdcard because sometimes it doesn’t want to mount /data while wiping (/data/media which is /sdcard is safe in wipe) the tablet, so if you were to install the zip from /sdcard with the error present, it would screw things up. I prefer the microSD card route (/storage/sdcard1), and you don’t even need a big one. 512MB works just fine. The actual path would be /sdcard/0/ when looking for the cm.zip in the internal storage.
14. When you have chosen to install from either /sdcard or /storage/sdcard1, select the cm.zip and install it.
a. If you downloaded gapps.zip, install it the same way as you did with the cm.zip.​15. Go back to the main menu now and select “reboot system now”
a. Once, I had the option to install root access before rebooting, I declined (was planning on rooting after tutorial) but it gave me root anyway.​
That’s it! You can now use CyanogenMod with the Sony Xperia Tablet Z.
Getting in to recopvery
I just struggled with entering recovery for way too long and I want to help others avoid this. I kept finding vague instructions.
The step I want to clarify is:
c. Once it shuts down, rapidly tap the
Code:
Vol +
button in order to get into the recovery.
Click to expand...
Click to collapse
This didn't work for me because if you press Vol+ too soon it goes right back in to fastboot mode. If you press it too late you will miss the recovery mode. You only have to press Vol+ once.
Please change step c. to read:
Look at the LED. It will turn Orange and then Purple. You want to press Vol+ as soon as it changes from Orange to Purple to enter recovery mode.
Grep_The_Truth said:
I just struggled with entering recovery for way too long and I want to help others avoid this. I kept finding vague instructions.
The step I want to clarify is:
This didn't work for me because if you press Vol+ too soon it goes right back in to fastboot mode. If you press it too late you will miss the recovery mode. You only have to press Vol+ once.
Please change step c. to read:
Look at the LED. It will turn Orange and then Purple. You want to press Vol+ as soon as it changes from Orange to Purple to enter recovery mode.
Click to expand...
Click to collapse
I'll add it along with mine, because I can do it with no problem.
alexpja said:
I'll add it along with mine, because I can do it with no problem.
Click to expand...
Click to collapse
alexpja Thanks for your tutorial, this is very detailed and easy to follow.
my Xperia is SGP321.
I put it into practice and the results it gives me the "oem unlock" is:
FAILED: (remote: Command nor allowed).
I guess you should treat my tablet has the bootloader locked and not allowed (for now??) the unlocked.
I hope someone gives us the opportunity to unlock the devices and in the future can be unlocked.
I had the same experience where at times the steps were a little confusing, especially for a beginner. Each set of instructions would either leave something out or skim over it as if everyone already knew it. That's understandable since they were probably written for that audience. I soft-bricked my SGP311 at least 10 times.
I was even going to write something like this but I got lazy.
One suggestion I would offer is to request the bootloader unlock key first since it sometimes takes a little while and a person can reduce the possibility of having to stop and wait just when they are making progress.
And for anyone going this route for the first time, don't make my mistake - flash exactly what the instructions say to flash, particularly boot.img. Once you have that recovery flashed you have a lot more control over your device. If something goes wrong in a following step like getting boot loops you can still fix it. But if you get annoyed and start poking at it then you can mess up the recovery. Then you have to reset everything to stock and just about start over.
While I don't want to say something stupid like claiming the tablet is indestructible, I found that whether I got stuck in a boot loop I couldn't get out of or screwed it up so bad that all I could get from the tablet was an occasional LED flash, I could always restore it using Emma. It's annoying to have to start all over but it's a huge relief when it boots normally.
for me flashing was fine and without any error but my Tab doesn't boot up with CM flashed...any idea?
Hanging at reboot
Hi.
I tried this procedure on my sony xperia tablet z 311. It unlocked fine and wrote boot.img fine but on reboot command, I get a red light and it hangs there.
I've managed to get it back to fastboot mode (pressing power and vol+, some white blinking lights).
But that's it, that's all I can do with this right now. It's a brick that can get into fastboot mode and that's it. Any time I write a boot.img (have tried a different one also), it writes fine but hangs with a red light at reboot.
Edit:
Used Sony's Emma in flash mode to get back to stock, tried again and it worked.
Maybe the problem was using the pollux instead of pollux_windy download, my bad.
Guess my bootloader won't be unlocked. This is A lot of work. Good job on the write up though maybe one day I'll tackle it.
BOOT LOOP Step 9
All was going well, but step 9 powering on device, now its looping.....Ill use flash tools to put jelly bean on and try again, since i was trying with kitkat...why i suspect kitkat is the issue, before i used to be able to unlock and lock boot-loader with jelly bean but with kitkat it didn't work, which i then forced it via cmd
No GPS
I used the tutorial for my Pollux Windy (WiFi Only) and used the latest nightly. everything went well but my GPS is now broken. Is this a known issue?
kevinsickles said:
Is this a known issue?
Click to expand...
Click to collapse
yep! use search to find out more.
mulebreath said:
Hi.
I tried this procedure on my sony xperia tablet z 311. It unlocked fine and wrote boot.img fine but on reboot command, I get a red light and it hangs there.
I've managed to get it back to fastboot mode (pressing power and vol+, some white blinking lights).
But that's it, that's all I can do with this right now. It's a brick that can get into fastboot mode and that's it. Any time I write a boot.img (have tried a different one also), it writes fine but hangs with a red light at reboot.
Edit:
Used Sony's Emma in flash mode to get back to stock, tried again and it worked.
Maybe the problem was using the pollux instead of pollux_windy download, my bad.
Click to expand...
Click to collapse
Hi,
I've been trying with my Xperia Tablet Z Wi-Fi SGP311. Ran into the same problem. On reboot command the LED was stuck on red for 10 minutes and the cmd window was still open. I unplugged the USB and the LED would not turn off. Tried some things, I don't remember specifically what, but it got the LED to turn off. Now my device can't be detected. I've downloaded Emma and it is not recognising my tablet. I've tried to plug the USB in while hold Vol +, Vol -, and the Power button. No detection for any. All I can do with my tablet is make the LED flash white, purple and red in rapid succession by holding Vol + and Power for 5 seconds.
Anyone know what's happened? I suspect I've completely bricked it :L
EDIT: Apparently there are different modes which you can cycle through. If you hold down Vol + and Power for 5 seconds, the LED will flash according to which mode the tablet is in. The different modes give these flashes:
- 1 White flash
- 3 Rapid which flashes
- A white, purple and red flash in quick succession
To switch between the modes, I hold down Vol+ and Power, and after 5 seconds it will take around 3 more seconds to change modes. One of these modes will not appear unless plugged into a PC. What do these mean and can I do anything with it? Tablet is still bricked.
EDIT2: I've managed to get Emma to recognise my tablet. Turns out the modes do have different purposes. I should be fine now, problem solved. I will just leave the solution here in case anyone runs into the same problem.
Unplug your device and hold Vol + and Power for 10 seconds. At the 5 second mark your LED should flash white ONCE. Keep both buttons held and within 5 more seconds, your LED will flash white THREE times consecutively. This will allow you to enter Flashmode (plug in USB while holding Vol -) and Fastboot (plug in USB while holding Vol +). For Emma to recognise your device, enter Flashmode and you can restore and try again.
Bootloop
I've tried many times to flash cyanogenmod onto my Xperia Tablet Z (SGP311). This is a Wi-Fi only tablet and I have downloaded the versions of CM from (download.cyanogenmod.org/?device=pollux_windy) I've followed all of the steps and tried all of the versions of CM down to 10.2 (I used GApps10.2 for CM10.2). Each version gets stuck in bootloop. I've cleared all data (in CWM - wipe data/factory reset, wipe cache partition, wipe delvik cache) before flashing CM and GApps; however, when I try to clear data I get an error. This is what the tablet says:
-- Wiping Data...
Formatting /data...
Error mounting /data!
Skipping format...
Formatting /cacha
Formatting /sd-ext...
Formatting /sdcard/.android_secure!
Skiiping format...
Data wipe complete.
Click to expand...
Click to collapse
I'm thinking the "Error mounting /data" is the problem, but I'm not entirely sure, nor am I sure of how to fix it.
Any suggestions?
EDIT: Turns out I'm just really bad with Android stuff. I ended up flashing the original Xperia software, unlocking the bootloader (according to this tutorial's instructions), then I downgraded to 4.1.2, rooted my tablet (forum.xda-developers.com/showpost.php?p=53063218&postcount=14) and installed the PhilZ and TWRP custom recoveries. I didn't get to use them in the end. For some reason CWM kept coming up no matter what combination of buttons I pressed while rebooting. After downgrading and rebooting, I followed the rest of the instructions on this tutorial (from step 7). This time I got no errors while cleaning the disk, cache and delvik cache. Flashed the zip files, rebooted the device and voila, Cyanogenmod11!
Again, I'll leave this edit here in case someone runs into a similar problem. I couldn't get any version of CM until I rooted first.
I followed this guide and bricked my device. If anyone has any tips - PLEASE HELP!
I tried to flash CM11, all seemed to be going great until CM11 and Gapps where installed any I hit "Reboot system now" in CVM. The device never booted again (I which I knew why!), and is now pretty much dead. I can however:
- Enter Flashmode
- Enter Fastboot mode
- Relock/Unlock bootloader
- Emma recognizes my device just fine in flashmode.
So I still think there is some hope, right?
I have tried installing the firmware that Emma suggests, doesn't work.
I have tried flashing a firmware I found on the internet with Flashtool, doesn't work.
I have tried relocking the bootloader and trying to repair the device through SUS, doesn't work.
So, PLEASE, help my sort this out! I would be forever greatful!
tp_88 said:
I followed this guide and bricked my device. If anyone has any tips - PLEASE HELP!
I tried to flash CM11, all seemed to be going great until CM11 and Gapps where installed any I hit "Reboot system now" in CVM. The device never booted again (I which I knew why!), and is now pretty much dead. I can however:
- Enter Flashmode
- Enter Fastboot mode
- Relock/Unlock bootloader
- Emma recognizes my device just fine in flashmode.
So I still think there is some hope, right?
I have tried installing the firmware that Emma suggests, doesn't work.
I have tried flashing a firmware I found on the internet with Flashtool, doesn't work.
I have tried relocking the bootloader and trying to repair the device through SUS, doesn't work.
So, PLEASE, help my sort this out! I would be forever greatful!
Click to expand...
Click to collapse
download a proper stock (not bricked) firmware for your device and flash with flashtool.
Rootk1t said:
download a proper stock (not bricked) firmware for your device and flash with flashtool.
Click to expand...
Click to collapse
What makes you think that the stock firmwares I've tried are bricked? I've since my post tried one which I downloaded through Flashtool - same result.

Categories

Resources