I am trying to install a /e/ OS in an old, but otherwise fully functional, Nexus 4 phone. I followed the steps described in
gitlab.e.foundation/e/wiki/en/wikis/device/mako/install. I have successfully unlocked the device, and I can reboot into the bootloader by means of adb reboot bootloader from my Linux system, when the Nexus 4 is connected to it via a USB cable. So far so good.
The next step consists of installing a custom recovery. I therefore went to twrp.me to download a TWRP image for this device - LG mako. I downloaded the most recent one, and copied it to the Nexus 4 with the following commands
adb reboot bootloader
fastboot flash recovery twrp-x.x.x.x-mako.img
where x.x.x.x represents the version number of the image. When I do this I see a fleeting message at the bottom of the Nexus 4 bootloader screen, to the effect that the image has been copied. I then press on the Power button, and the Nexus 4 reboots normally. When the Nexus 4 is up and running, I use the
adb reboot recovery
command from my Linux box (I never disconnected the USB cable) to reboot in recovery mode. The Nexus 4 goes blank for a few seconds, then I get the twirly boot up animation, and finally I get an Android icon at the center of an otherwise black screen. The Android is lying on its back, with a lid open on its torso, and a red triangle with an exclamation mark in it. Things stay like that for a minute or two, and then the system reboots spontaneously in normal mode. I end up again with a functional Android device. That's good, but the recovery mode does not seem to be working.
The thing is, I have tried with ten different twrp images for Nexus 4 mako from twrp.me, and the behavior has been exactly the same with all of them. I am therefore beginning to wonder if I am doing something systematically wrong here?
I will try with all the different twrp images, but if somebody has any ideas as to what is going on, and how to solve the problem, their feedback would be much appreciated.
I think you are missing this part:
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
Click to expand...
Click to collapse
Key combo for mako is "power + volume down"
Nitin
Once you flash TWRP, immediately boot directly to it - while still in the bootloader menu, use volume buttons to highlight the Recovery mode and press the power button. If you don't do that, TWRP will be overwritten by the stock recovery (as you've already experienced).
nitin.chobhe said:
I think you are missing this part:
Key combo for mako is "power + volume down"
Nitin
Click to expand...
Click to collapse
OK, thanks; I certainly missed it. I'll try, but It might be a tricky undertaking , for the volume up/down button in this phone is difficult to get to work.
n0b0dy666 said:
Once you flash TWRP, immediately boot directly to it - while still in the bootloader menu, use volume buttons to highlight the Recovery mode and press the power button. If you don't do that, TWRP will be overwritten by the stock recovery (as you've already experienced).
Click to expand...
Click to collapse
Thanks. However, I can see no relevant entry in the bootloader menu. The entries that it displays are the following:
Fastboot Mode
Product_Name - mako
Variant - mako 8GB
HW Version - rev_11
Bootloader Version - MAKOZ30f
Baseband Version - M9615A-CEFWMAZM-2.0.1701.07
Carrier Info - None
Serial Number - 01cxxxxxxx
Signing - production
Secure Boot - enabled
Lock State - unlocked
ijkabc said:
Thanks. However, I can see no relevant entry in the bootloader menu. The entries that it displays are the following:
Fastboot Mode
Product_Name - mako
Variant - mako 8GB
HW Version - rev_11
Bootloader Version - MAKOZ30f
Baseband Version - M9615A-CEFWMAZM-2.0.1701.07
Carrier Info - None
Serial Number - 01cxxxxxxx
Signing - production
Secure Boot - enabled
Lock State - unlocked
Click to expand...
Click to collapse
You have to use volume button to see the options and power button to select the option.
Refer this video: https://www.youtube.com/watch?v=e0FVHFg6t2I
From time 2.53 to 3.53 to understand how it works. Note that the video is for hardware reset; so do not follow the next steps. I linked the video for you to understand how the bootloader mode works and how you can select the options. You need to select option "Recovery".
Nitin
ijkabc said:
Thanks. However, I can see no relevant entry in the bootloader menu. The entries that it displays are the following:
Fastboot Mode
Product_Name - mako
Variant - mako 8GB
HW Version - rev_11
Bootloader Version - MAKOZ30f
Baseband Version - M9615A-CEFWMAZM-2.0.1701.07
Carrier Info - None
Serial Number - 01cxxxxxxx
Signing - production
Secure Boot - enabled
Lock State - unlocked
Click to expand...
Click to collapse
Press the volume button, Fastboot mode will switch to a different mode, keep pressimg until you see the recovery one and press the power button to boot.
Thanks everybody. The problem was that my dodgy volume button led me to think that Start was the only option in the bootloader menu. After a few attempts I was able to coax it into changing from Start to Recovery, and from that moment onward the installation of the /e/ OS proceeded without any glitches.
Related
I have installed 4.2.2 on nexus 7. As I had skipped account login at welcome screen, i could not login the account. I altered the apk of login. After factory reset my device has hanged on setup on welcome screen. I tried installing custom rom through stock bootloader but the bootloader says installation failed. How do I solve thia problem guys???
subin.nexus7 said:
don't know the exact steps, but i got it out of the APX mode and into the bootloader.
1. Tablet plugged into computer.
2. Held Volume Down + Volume Up + Power (simultatenously) for three seconds
3. And then released all, and pressed Power again.
4. Tablet booted into bootloader.
I thought that unlocking the bootloader ALWAYS voided the warranty, but in anycase I flashed reflashed ALL stock and locked the bootloader. Will be sending it to ASUS now. Thanks again!
EDIT:
So I wanted to verify that it was a CPU problem, and I downloaded StabilityTest again and ran the CPU load test. It crashed within two minutes, and went into AXP mode again. To get it out of AXP mode, the correct instructions:
1. Plug in the usb into computer
2. Hold Volume Down + Volume Up + Power simultaneously for like 15 seconds
3. The bootloader should show up.
4. If it doesn't, unplug the usb cable, and plug it back in and then repeat the these procedures.
Click to expand...
Click to collapse
Very helpful! I don't have a problem but I've read about others stuck in APX mode. This should be pinned if it works for those stuck in APX. Maybe you should change the thread title to something about APX solution so it draws some attention.
kieso said:
Very helpful! I don't have a problem but I've read about others stuck in APX mode. This should be pinned if it works for those stuck in APX. Maybe you should change the thread title to something about APX solution so it draws some attention.
Click to expand...
Click to collapse
Well... being stuck in APX doesn't necessarily mean your hardbricked. (Corrupt or erased bootloader).
But being hardbricked DOES mean your device will default to APX mode.
To use a mathematical metaphor, one is a SUBSET of the other.
-------
bftb0 has posted an exhaustive list of Nexus 7 button press combos here...
http://forum.xda-developers.com/showthread.php?t=2133986
... which includes how to pro-actively get into APX mode... although until somebody figures how to nvFlash the N7, APX is sort of redundant.
Rgrds,
Ged.
Delete
subin.nexus7 said:
I have installed 4.2.2 on nexus 7. As I had skipped account login at welcome screen, i could not login the account. I altered the apk of login. After factory reset my device has hanged on setup on welcome screen. I tried installing custom rom through stock bootloader but the bootloader says installation failed. How do I solve thia problem guys???
Click to expand...
Click to collapse
I'm sort of confused about the relationship between your edited post and what (apparently ?) kieso quoted, but I'll throw out a few suggestions:
1) AFAIK, there is no way to flash a dev ROM using fastboot (only the boot image of a dev ROM can be flashed this way). You said "bootloader", not "custom recovery" ... so that implies using fastboot. If that is not the case, then your use of terminology is not correct. (It's a computer - reporting details correctly is incredibly important).
2) If you bypass the WiFi login, an account can be added at any time later using the settings menu or simply by launching the Google Play (market) app - there is no need to "alter the apk of login", whatever that means.
3) I would recommend at this point that you start completely over by flashing a factory ROM using fastboot - see the sticky thread about returning to stock using fastboot. If you already have the 4.18 bootloader installed, I recommend you avoid like the plague any operation involving flashing the bootloader.
4) It should be obvious from the trouble that you got yourself into that you should learn what nandroid backups are and that you START USING THEM. The first thing you do after rooting is "make a backup", not "flash a ROM"
good luck
Thanq so much.But still some clarification needed
Now What do I do? My nexus 7 can't pass through at welcome screen saying saying unfortunately setup wizard has stopped. and in recovery{i have no custom recovery, I use bootloader 4.18} i cant flash any rom. I just want to start device any how.. any way.. Is there any way??
subin.nexus7 said:
Now What do I do? My nexus 7 can't pass through at welcome screen saying saying unfortunately setup wizard has stopped. and in recovery{i have no custom recovery, I use bootloader 4.18} i cant flash any rom. I just want to start device any how.. any way.. Is there any way??
Click to expand...
Click to collapse
I guess I am having trouble understanding the sum total of information you have provided - I guess you have omitted some information or mis-stated something. No custom recovery sort of implies a full stock device, but yet you previously mentioned modifying/changing an .apk in /system... normally that would be possible only with a rooted ROM or a custom recovery to do that.
If your tablet is 100% stock, a factory reset of the tablet should allow you to boot once again - at the cost of deleting everything you put on the device, including all files you put on the (pseudo-) SD card.
If that is the case:
- press and hold power+vol-down until the bootloader screen shows up
- use vol-up/vol-down to select "start recovery" and press the power button
- an android lying on it's back should show up; this is the stock recovery splash screen, so
- press power+vol-up simultaneously for about one second - the stock recovery menu should show up
- select factory reset (with vol-up/vol-down) and press the power button.
good luck
bftb0 said:
I guess I am having trouble understanding the sum total of information you have provided - I guess you have omitted some information or mis-stated something. No custom recovery sort of implies a full stock device, but yet you previously mentioned modifying/changing an .apk in /system... normally that would be possible only with a rooted ROM or a custom recovery to do that.
If your tablet is 100% stock, a factory reset of the tablet should allow you to boot once again - at the cost of deleting everything you put on the device, including all files you put on the (pseudo-) SD card.
If that is the case:
- press and hold power+vol-down until the bootloader screen shows up
- use vol-up/vol-down to select "start recovery" and press the power button
- an android lying on it's back should show up; this is the stock recovery splash screen, so
- press power+vol-up simultaneously for about one second - the stock recovery menu should show up
- select factory reset (with vol-up/vol-down) and press the power button.
good luck
Click to expand...
Click to collapse
when you say at the cost of deleting everything, does this include deleting everything in the bootloader because thats what I did when I used the command "fastboot erase bootloader"
Yes, I know, everyone knows how to enter safe mode, bootloader, and recovery.
I found there are some inconsistencies to entering and using recovery depending on your which software you are running. In addition there are multiple ways of entering stock recovery.
Also I always see people asking this question because somehow the keypress order is not intuitive.
Entering Safe Mode
Tablet booted and running Android
Press/Hold Power button until power menu shows up
Tap/Hold Power off option
Choose OK to reboot in safe mode
Tablet powered down
Press/Hold Power button until Google screen shows up, RELEASE Power button
Press/Hold VolDn until Android has booted up
If successful, you will see Safe mode overlayed on bottom left of screen.
Entering Bootloader (ie fastboot mode)
Tablet booted and running Android
From adb
adb reboot bootloader
can also choose recovery from menu after bootloader comes up
From app
Use Quick Boot from Google Play
Tablet powered down
Power+VolDn while booting to enter bootloader
Release buttons after you see bootloader screen
Entering Stock Recovery
Tablet booted and running Android
From adb
adb reboot recovery
From app
Use Quick Boot from Google Play
Tablet powered down
Power+VolUp while booting to enter recovery
You can release buttons after you see Google on screen
When Stock Recovery starts you will see the Android fallen down screen
To bring up the Recovery menu
Power+VolUp to show recovery menu
Must be this sequence Press/Hold Power, THEN Press/Release VolUp, release Power
Within menu
VolUp to move up
VolDn to move down
Power to select
In addition, I found an inconsistency with JSS15J stock recovery that wasn't in the JWR66N recovery
While at the Android fallen down screen if you mistakenly press
VolUp
instead of
Power+VolUp
you will still get the Recovery menu.
However, VolUp will no longer function. It will instead become a toggle for switching between the Recovery menu and the Android fallen down screen
Android fallen down screen
VolUp to toggle recovery menu
Within menu
VolUp does not work since it toggles recovery menu
VolDn to move down
Power to select
sfhub said:
Entering Stock Recovery
Tablet booted and running Android
From adb
adb reboot recovey
Click to expand...
Click to collapse
Are you sure with this command. I think it must be => adb reboot recovery <= or am I wrong ???
pRo_lama said:
Are you sure with this command. I think it must be => adb reboot recovery <= or am I wrong ???
Click to expand...
Click to collapse
Sorry, typo, fixed.
i`m on completely stock JSS15Q and i cant get into stock recovery. When im trying i see "no command" and red exclamation mark on the laying robot. What should i do?
laska300 said:
i`m on completely stock JSS15Q and i cant get into stock recovery. When im trying i see "no command" and red exclamation mark on the laying robot. What should i do?
Click to expand...
Click to collapse
sfhub said:
Entering Stock Recovery
Tablet powered down
Power+VolUp while booting to enter recovery
You can release buttons after you see Google on screen
When Stock Recovery starts you will see the Android fallen down screen
To bring up the Recovery menu
Power+VolUp to show recovery menu
Must be this sequence Press/Hold Power, THEN Press/Release VolUp, release Power
Within menu
VolUp to move up
VolDn to move down
Power to select
Click to expand...
Click to collapse
Please see RED section
Does the presence or absence of the red exclamation triangle mean anything?
Wot does safe mode do?
Anderson2 said:
Does the presence or absence of the red exclamation triangle mean anything?
Click to expand...
Click to collapse
I don't remember if there are two images one with and one without the triangle. I think I've only seen the image with the red exclamation point.
I've never seen anything to indicate the red exclamation mark is something you need to pay attention to.
Now if you apply an update and there is an error, then that is something I would pay attention to.
LoVeRice said:
Wot does safe mode do?
Click to expand...
Click to collapse
It doesn't load the stuff you added.
It is similar to safe mode on a PC, used to diagnose whether the issue is in the stock ROM or is in something you introduced by installing some app.
I Have a probleme
since a bought TAB 3 10.1 and it's boot into safe mode i'v restart it and turrn it off the back on but it didn't go what should i do ?
This thread is about nexus 7.
sfhub said:
This thread is about nexus 7.
Click to expand...
Click to collapse
oh sorry i was panic so i searched in every thing
Bootloader
If none of that works, try the command with a dash "adb reboot-bootloader" Depends on your device sometimes, sometimes unplugging your device right after you enter this command will keep it from getting stuck at the boot logo screen. If that doesn't work, hold the power button to power device down and then boot it into recovery instead using the button combo. Then you can wipe cache & start all over again.
I'm not even able to get into Recovery. I can get to the bootloader, then I select "Recovery mode" and it shows the Google logo, but it never goes into recovery. I have let it sit at the Google logo for a couple of hours, and end up just holding down the power button to shut it down.
I have tried Skipsofts toolkit, as well as Wug's, to try to unlock the bootloader. This ends up with the device hanging at the "Unlock bootloader" screen after selecting "Yes". Again, I have left it in this state for well over an hour with no change.
Here's some info on my 2013 Nexus 7:
KitKat 4.4.4
Never rooted
Never unlocked bootloader
HW version rev-e
Bootloader version FLO-04.02
I suspect my Nexus knew I was supposed to go on travel next week and is faking sick.
Any help would be appreciated. Thanks.
Hi guys i have a google nexus 5 and it is locked state. It is getting booted again and again but it jiust reaches google logo and again restarts. Safe boot is also enabled so i cant enter in recovery mode also. Please help me ASAP.
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.
My Nexus 7 wifi is stuck with the four rotating circles.
I tried rebooting with Nexus repair tool kit. (I am no expert).
I am asked to enable USB debugging on the device via the settings menu.
How do I do this if the device cannot be accessed beyond the screen that shows the dead android?
Is there a simpler way than Nexus RTK?
Thanks
Do you still need help? You can try and hold down the power button until it powers down. Then hold the power and volume down button down until you see the android guy. Then use the volume keys until you get to enter recovery mode. Then wipe data/factory reset and then reboot. You should be good after that.
AndrewInman said:
Do you still need help? You can try and hold down the power button until it powers down. Then hold the power and volume down button down until you see the android guy. Then use the volume keys until you get to enter recovery mode. Then wipe data/factory reset and then reboot. You should be good after that.
Click to expand...
Click to collapse
Thanks!
Yes, I do.
I followed the instructions. When I choose Recovery, the Google logo comes up followed by the four circles.
I don't know whether this will help, but this is the info I get in the boot loader and recovery screens:
Product name: grouper
Variant: grouper
MW version: ER3
Bootloader version 4.23
Baseband version: NA
Signing: not defined yet
Lock state: unlocked
Serial: 015d32901440e1a
Please advise how I should proceed.
Hello,
Here are the details on my Samsung Nexus 10 tablet...
Product Name: manta
Variant: wifi
H/W Version: 8
Bootloader Version: mantamf01
Carrier Version: none
Serial Number: r3201042hze
Lock State: locked
Reboot Mode Flag: none
OS: 5.?
My tablet was running really slow, then one day the tablet would not get past the "Google" banner/logo. So I cannot delete my Google ID from the tablet. I can do the three finger startup (power button, volume up, volume down) and get into the "Recovery Mode", which is as far as I can get. I have tried the power button and volume up, expecting to see the android dude with the "red triangle". I cannot see the little dude with the red triangle.
Any ideas on how a can perform a factory reset on this tablet?
So you can’t factory reset through recovery? What happens when try?
ConstantlyCurious said:
Hello,
Here are the details on my Samsung Nexus 10 tablet...
Product Name: manta
Variant: wifi
H/W Version: 8
Bootloader Version: mantamf01
Carrier Version: none
Serial Number: r3201042hze
Lock State: locked
Reboot Mode Flag: none
OS: 5.?
My tablet was running really slow, then one day the tablet would not get past the "Google" banner/logo. So I cannot delete my Google ID from the tablet. I can do the three finger startup (power button, volume up, volume down) and get into the "Recovery Mode", which is as far as I can get. I have tried the power button and volume up, expecting to see the android dude with the "red triangle". I cannot see the little dude with the red triangle.
Any ideas on how a can perform a factory reset on this tablet?
Click to expand...
Click to collapse
The key combo (power and both volume buttons) puts the device in bootloader (fastboot) mode.
From there when you select the recovery option (using the volume keys) and select it (using the power button), it should boot into recovery.
The recovery screen will show the crashed Android dude.
Then press the power and volume up (the one further away from the bower button) to toggle the recovery menu.
If you do not see the crashed Android dude, then you did not boot into recovery, instead you are stuck in limbo.
It is possible your emmc is dead, if so no easy fix.
---
With all that said, it has been a while since either of mine have been locked or on stock Android.
Since you can boot into bootloader (fastboot), if you have platform-tools setup on your computer, you can should be able to connect to it in fastboot mode.
Then from the command line on you computer you could try running fastboot -w that will wipe the cache and userdata partitions.
With updates to platform-tools, fastboot might not be fully compatible with older devices.
I am not sure if the fastboot format command will recognize manta properly.
You will need to unlock it first but, another option would be to flash the last full factory image from Google.
The default flashall script will wipe data on install.
When you unlock the bootloader, it will also wipe userdata.
---
Factory Images for Nexus and Pixel Devices
developers.google - [WebSite] - Link
SDK Platform Tools
developers.google - [WebSite] - Link
Google Nexus 10
[xdaForum] - Link
---
Cheers.
Arealhooman said:
So you can’t factory reset through recovery? What happens when try?
Click to expand...
Click to collapse
Sounds more like it is not booting into recovery for some reason. ¯\_(ツ)_/¯
Cheers.
Nothing happens, when I get into the recovery menu, I should see a red triangle in the android dude, no red triangle.
Arealhooman said:
So you can’t factory reset through recovery? What happens when try?
Click to expand...
Click to collapse
I do not know your device, but doesn’t the recovery menu usually have options.
Arealhooman said:
I do not know your device, but doesn’t the recovery menu usually have options.
Click to expand...
Click to collapse
Hello,
Here is what I have found on how to do a factory reset. I cannot get the red triangle in the android robot.
Google Nexus 10Factory Reset Instructions (Recovery Mode)
If your tablet is on, power it off.
Press and hold Volume Up + Volume Down + Power until the device powers on. You should see an image of an Android lying on its back.
Press Volume Down twice, until the screen says "Recovery mode."
Press Power to restart into "Recovery mode." You should see an image of an Android with a Red triangle after a few minutes.
While holding down Power, tap Volume Up
Use the volume keys to scroll to "wipe data/factory reset" and press Power to select it
Scroll down to "Yes - erase all user data" and press Power to select it