I may have bricked, want to know what went wrong and if it's permanent. Thanks, here's how it happened.
I was running one of the Omnirom nightly builds. I got a notification saying there was a new build, I decided to try it hoping it would improve my battery life. I had TWRP installed so I thought it would be ok (I chose to let it update automatically which I guess was my mistake). It did the update or tried to at least, but when it tried to boot it just gets stuck on the Asus screen. The one with the loading bar. Volume up or down with power button does nothing but get back to the same screen. Reset (using a pin) and volume up or down does the same thing. I thought the only way to permanently boot was doing the wipe option on the recovery menu, but maybe I am wrong. Is it possible to permanently brick doing what I did? Thanks. Any possible solutions?
mechz01 said:
Is it possible to permanently brick doing what I did? Thanks. Any possible solutions?
Click to expand...
Click to collapse
Unlikely. What always works, if you can put it into fastboot, is install the Asus stock ROM. That will reformat/reinstall every partition.
Berend de Boer said:
Unlikely. What always works, if you can put it into fastboot, is install the Asus stock ROM. That will reformat/reinstall every partition.
Click to expand...
Click to collapse
That's holding the reset button down plus volume down right? Doesn't seem to work.
mechz01 said:
That's holding the reset button down plus volume down right? Doesn't seem to work.
Click to expand...
Click to collapse
Try long holding VOL DOWN & POWER BUTTON ....
Can you get to the bootloader this way ?
Thx Josh
lj50036 said:
Try long holding VOL DOWN & POWER BUTTON ....
Can you get to the bootloader this way ?
Thx Josh
Click to expand...
Click to collapse
Thanks for the Reply
No, it just gets me back to the same screen. This is supposed to get me to the recovery menu right?
If it matters,my bootloader is unlocked.
mechz01 said:
Thanks for the Reply
No, it just gets me back to the same screen. This is supposed to get me to the recovery menu right?
If it matters,my bootloader is unlocked.
Click to expand...
Click to collapse
Well there is not much that can be done then.....
No fastboot with a locked bootloader .....
No bootloader to boot into recoovery .....
No nvflash blobs with a locked bootloader ..
Short of a motherboard you have a paperweight .....
Sorry for the back news ......
Thx Josh
Hello
Hi
I had basically the same situation of this topic, the only i can access to fastboot.
I formated all my tablet, basically is nothing in the memory
when i tried to access over the recovery, is stuck, only blink.
Fastboot commands works but i dont know how i can recover all.
I know i need to install everything.
Can someone let me know what i can install (Kernel, firmware, rom(I want lollipop).
I had already TWRP 2.8.0
Thanks in advance
lj50036 said:
Well there is not much that can be done then.....
No fastboot with a locked bootloader .....
No bootloader to boot into recoovery .....
No nvflash blobs with a locked bootloader ..
Short of a motherboard you have a paperweight .....
Sorry for the back news ......
Thx Josh
Click to expand...
Click to collapse
My bootloader is unlocked, unless I am misunderstanding what you're saying. On the Asus screen it says this device is unlocked. Not sure why I can't access any of the options though, unless my volume buttons is busted or something.
jcbeau09 said:
Hi
I had basically the same situation of this topic, the only i can access to fastboot.
I formated all my tablet, basically is nothing in the memory
when i tried to access over the recovery, is stuck, only blink.
Fastboot commands works but i dont know how i can recover all.
I know i need to install everything.
Can someone let me know what i can install (Kernel, firmware, rom(I want lollipop).
I had already TWRP 2.8.0
Thanks in advance
Click to expand...
Click to collapse
First step: Install new TWRP
1. Download TWRP recovery from here: http://techerrata.com/browse/twrp2/tf300t; I would advise v. 2.8.4.0
2. Put 'openrecovery-twrp-2.8.3.0-tf300t.blob' in fastboot folder of pc and rename to twrp.blob for faster typing.
3. Put tab in fasboot mode and connect.
4. Use command
Code:
fastboot -i 0x0b05 flash staging twrp.blob[enter]
fastboot -i 0x0b05 reboot[enter]
5. Let tab reboot to OS (will stay on ASUS screen, because you don't have OS as of now).
6. Reboot to bootloader screen and go to recovery (RCK); now you can flash any custom ROM you like.
Good luck!
mechz01 said:
No, it just gets me back to the same screen. This is supposed to get me to the recovery menu right?
Click to expand...
Click to collapse
No! Recovery comes way after fastboot mode. Recovery is loaded from your memory card. But something went wrong with your memory card, so you can't load that.
Once you booted your tablet into fastboot, type :"fastboot devices" on your PC. If it shows your tablet, you can easily flash a new ROM.
Berend de Boer said:
No! Recovery comes way after fastboot mode. Recovery is loaded from your memory card. But something went wrong with your memory card, so you can't load that.
Once you booted your tablet into fastboot, type :"fastboot devices" on your PC. If it shows your tablet, you can easily flash a new ROM.
Click to expand...
Click to collapse
I would like to know how you are going to flash a new rom with fastboot ?
Thx Josh
Related
Hi all,
Been given a Nexus S i9023 by my brother who has been "tampering" with it and now it seems a bit messed up.
When booting up - it gets stuck on the "Google" screen with a padlock on it... I can get into fastboot and I can flash recovery but when I attempt to load any recovery - I get that same Google screen with the padlock! I've downloaded a stock rom and even flashed system etc via fastboot but that still gets me nowhere past the damn padlock!!
I've tried to "fastboot boot recovery.img" and I still get the Google screen with the padlock but it says "Fastboot status - OK" on the bottom left.
I've searched and searched but everyone just seems to give tips on how to flash recovery. I know how to flash recovery; it just seem to be going into it though! Could the internal memory be screwed?
Thanks for any advice!
Sounds strange for sure. You try from within the OS? Enable USB debugging and adb reboot recovery.
Doubt it will work but its worth a shot
albundy2010 said:
Sounds strange for sure. You try from within the OS? Enable USB debugging and adb reboot recovery.
Doubt it will work but its worth a shot
Click to expand...
Click to collapse
The phone stops at Google with the padlock on boot! Can't even get into the OS. Going to try to unbrick it and Odin but left my ubuntu laptop at my parents and can't be bothered to go get it... couldn't get it to work booting off cd rom. Kept giving me the "SBL Injection Failure Failed to find device" error booting ubuntu on a CD!
You may have a storage issue.
I seen you tried to flash system and boot recovery with fastboot ( which should have booted) but did you try to flash them all and wipe. The command is fastboot -w update file name.
I think Odin is a windows only tool anyways by the way.
albundy2010 said:
You may have a storage issue.
I seen you tried to flash system and boot recovery with fastboot ( which should have booted) but did you try to flash them all and wipe. The command is fastboot -w update file name.
I think Odin is a windows only tool anyways by the way.
Click to expand...
Click to collapse
No idea why I said Odin - I meant the unbrickable recovery thing.
I tried Odin with a Jig last night; got it into download mode and flashed with odin. Got the same result.
fastboot -w also gives the same issue...
If I have a storage issue - is there any way I can tell?
Basically you can tell by the issues you're having. Doing all the proper stuff to flash images etc and still having a booting/working device.
As far as a actual diagnostic tool I don't know of one. But it sure sounds like a hw issue to me.
I have the following problem: since a few weeks I'm unable to enter recovery.
This is what I do:
- shut down my phone
- press the power button while holding the volume up
- than I get a screen where I can choose from 4 options using the volume controls and selecting an option with the power button
- I select 'Recovery' and press the power button
- I get the usual black screen with Google logo and padlock
- but instead of getting into my recovery, I get a black screen with a Droid lying down, the 'chest' opened and some kind of small warning triangle above it..somebody who knows what I have to do??
Thanks in advance
Pironi90 said:
I have the following problem: since a few weeks I'm unable to enter recovery.
This is what I do:
- shut down my phone
- press the power button while holding the volume up
- than I get a screen where I can choose from 4 options using the volume controls and selecting an option with the power button
- I select 'Recovery' and press the power button
- I get the usual black screen with Google logo and padlock
- but instead of getting into my recovery, I get a black screen with a Droid lying down, the 'chest' opened and some kind of small warning triangle above it..somebody who knows what I have to do??
Thanks in advance
Click to expand...
Click to collapse
Reflash your recovery using fastboot.
polobunny said:
Reflash your recovery using fastboot.
Click to expand...
Click to collapse
And where can I find how to do this? I'm a total newbie for this kind of stuff and I found some hits on google (e.g. http://forum.xda-developers.com/showthread.php?t=1757146) but I'm actually a bit scared to damage my phone or something by doind something wrong or applying some method that's actually made for another device or so.. :s
Pironi90 said:
And where can I find how to do this? I'm a total newbie for this kind of stuff and I found some hits on google (e.g. http://forum.xda-developers.com/showthread.php?t=1757146) but I'm actually a bit scared to damage my phone or something by doind something wrong or applying some method that's actually made for another device or so.. :s
Click to expand...
Click to collapse
Flash custom recovery.img part
http://wiki.cyanogenmod.org/wiki/fastboot#Flash_Custom_Recovery.img
You need ADB (and ADB drivers installed, strongly recommend PDANet Android Drivers) and fastboot executable.
Custom recovery I suggest you use Clockworkmod Recovery.
I imagine your phone is already unlocked?
polobunny said:
I imagine your phone is already unlocked?
Click to expand...
Click to collapse
I think so yes, I could access recovery before if that's what you mean by unlocked
Pironi90 said:
I think so yes, I could access recovery before if that's what you mean by unlocked
Click to expand...
Click to collapse
When u boot on the Google screen on the bottom centre does it have a padlock? If so then it is unlocked.
You are entering recovery. Stock recovery
If you want a custom one either flash with fastboot or if you're rooted with a app. Goo manager. Rom manager etc.
Keep it mind that if you're on a stock ROM the custom recovery gets overwritten back to stock when the phone boots up the os
Q
UselessSniper001 said:
When u boot on the Google screen on the bottom centre does it have a padlock? If so then it is unlocked.
Click to expand...
Click to collapse
Then my phone is unlocked yes
polobunny said:
You need ADB (and ADB drivers installed, strongly recommend PDANet Android Drivers) and fastboot executable.
Custom recovery I suggest you use Clockworkmod Recovery.
I imagine your phone is already unlocked?
Click to expand...
Click to collapse
In installed the drivers and I installed the fastboot executable, but what do I have to do next? If I run the fastboot.exe, it just quickly shows a CMD-window and then disappears.
Edit:
I just discovered that, when I'm at the bootloader (I think it's called that way, the screen where you can select recovery), and I choose to reboot, I get the same 'error' as when I try to enter recovery.
Edit:
Alright, I was able to flash a new recovery, using cmd, but now when I try to enter my recovery, the phone gets stuck at a black screen with Google logo and padlock...
I have same problem as wolverine_2k who made the post. My nexus, can't start, I tried reboot and recovery but didn't work. After reboot or recovery I see Google logo, than Nexus screen and that is it. It didn't move to home screen and it stay with lighting screen all the time till I remove the battery. I can't power off it and don't know what to do. I can't transfer data with my PC (it don't recognize the device - only notice that "unknown device" is connected). Please any ideas?
P.S.: My English is not good, if someone answer do it simple please
Thanks!
Hello everyone, it's my first time that I'm stuck in this stupid way. now I'm with JB not-root and Team Win recovery in boot loop. he asks for the password to decrypt data and you can not wipe or mount anything. I can do reboot but he goes right into recovery without being able to get into fastboot. what i can do now for return to stock. boot loader are unlocked.thz for all help.:highfive:
What bootloader & what recovery?
Ti2 said:
What bootloader & what recovery?
Click to expand...
Click to collapse
Team Win 2,4,4,0 boot loader version i cant see
4.2.1 rom?
Ti2 said:
4.2.1 rom?
Click to expand...
Click to collapse
the last JB official from site.
pierpa86 said:
Team Win 2,4,4,0 boot loader version i cant see
Click to expand...
Click to collapse
if you cant mount the sdcard mean probably you need twrp 2.4.4.0-4.2
lk2l said:
if you cant mount the sdcard mean probably you need twrp 2.4.4.0-4.2
Click to expand...
Click to collapse
i can't
i only need to stop recovery loop for have FastBoot or Adb... and HOW ?
pierpa86 said:
i only need to stop recovery loop for have FastBoot or Adb... and HOW ?
Click to expand...
Click to collapse
?? if you hold the power button until switch off and immediatly push the volume down button, you should have the RCK screen to use fastboot right??
lk2l said:
?? if you hold the power button until switch off and immediatly push the volume down button, you should have the RCK screen to use fastboot right??
Click to expand...
Click to collapse
no i can't i push power + up or down nothing same story. stupid error:silly:
pierpa86 said:
no i can't i push power + up or down nothing same story. stupid error:silly:
Click to expand...
Click to collapse
try to reed this
http://forum.xda-developers.com/showthread.php?p=31842894
I hope can help you
lk2l said:
try to reed this
http://forum.xda-developers.com/showthread.php?p=31842894
I hope can help you
Click to expand...
Click to collapse
It will only work on UNLOCKED devices
It requires access to Fastboot to prepare device first time
It won’t work on fully bricked devices (See 2.)
You need to keep files safe!
If you upgraded to Offiical JB it *won’t* work!
i'm not have fastboot and i'm on Official JB
i have try to enter on APX mode but i can't
did you try to install the asus pc sync (it shoul install the driver for use adb & fastboot) and after boot into recovery
from prompt you should be able to use adb
write adb devices
and if you can see the code of the devices may you can still have a possibility to flash troght adb
ok man i understand the problem today
i have flashed the last TeamWin Recovery but not compatible with 4.2.1 but 4.1 stock rom and now all partition can't be mounted in recovery, i have found adb in broken recovery and push recovery img for flash with dd command and all done in shell but nothing flashed !! then "adb reboot bootloader" for try to reflash with fastboot, same story all done in shell but nothing flashed !! ok no problem i try to boot android in boot menu and damn partition is ok and android booting !!!!!!! :laugh:
ok remain 2 way. use dd in terminal emulator but can't without root permission and use nvflash but it's not work with JB confirm ?
waiting for a tool using an exploit for root from internal android and try dd or next update for nvflash.
any idea ? and sorry for my very bad english
Key driver not found.. Booting OS
Android cardhU-User bootloader (1.00 e) released by "WW_epad-10.6.1.8-20130225" A03
Starting Fastboot USB download protocol
[RCK] [ANDROID] [WIPE DATA]
when try flash in fast boot get freeze !!
Same issue here. I'm able to use Adb reboot bootloader command. And get to boot loader. From there I can cold boot Linux. So I have my i
Os but if it reboots. It goes back to the twrp locked.
Sent from my Galaxy Nexus using xda app-developers app
klownin5643 said:
Same issue here. I'm able to use Adb reboot bootloader command. And get to boot loader. From there I can cold boot Linux. So I have my i
Os but if it reboots. It goes back to the twrp locked.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
and what do you think about ?
if you can boot the system may you can verify again the bootloader whit asus tool from the website maybe for any unsense reason it's locked....
ops wrong tread
Ok, I just tried some stuff and:
1. I can also access fastboot and OS.
2. Trying to flash modified TWRP with fastboot freezes bootloader.
3. In-system can't open .RAR files.
4. After manually transfering unpacked V8 unlocker from PC it says there's an "unknown problem" when trying to install unlocker. It supposedly upgraded from V7 to V8 app without problem.
In bootloader it says at the top of the screen that "Key driver not found... Booting OS". After that it lists bootloader info ( v. 1.00 e ).
Looks like recovery's bricked with some further issues in the OS itself.
EDIT:
Bricked the OS. Tried reflashing stock system and now bootloader freezes when trying to boot OS. My guess would be that fastboot can still erase stuff but most likely can't write ( at least not properly ). Google/Asus probably know of a way to restore our tablets but Asus clearly prefers to replace motherboards.
I have to think whether it's worth it for me to replace the MB but most likely will just sell the thing for parts.
whan you try to re-flash the system somthing goes in the wrong way? do you still have fastbooy access? was the usb debug on?
sorry but which rar you can't open?
I had upgraded to 4.2 firmware (WW_epad-user-10.6.1.8) using the second method described on http://forum.xda-developers.com/showthread.php?t=2187982. This worked well and everything was working until I messed up today D: I was trying to flash SuperSU using TWRP but it couldn't recognize my Internal SD Card so I thought there might be something wrong with my installation. When I entered the bootloader I noticed the message: Key driver not found.. Booting OS. I don't know what this means. I did not read the first thread in the General section and tried to do a restore using the 4.2 firmware package. I used the "fastboot flash system blob" command and this time everything was messed up. The blue bar that appears on installation is no longer appearing and I have an "unrecoverable bootloader" error. Nothing I did worked! What should I do?? Please provide me some simple steps. I used these commands before flashing system blob...
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
This was a very stupid move on my part but I thought this would allow a clean install D: D: Please help!
gee man you completely wiped the sucker, you may be bricked =(. i would start by trying to fastboot flash the patched version of twrp. unless you can boot into twrp already then try to flash the asus package again thru twrp. also, could twrp see your internal sd before you bricked?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
markymark567 said:
gee man you completely wiped the sucker, you may be bricked =(. i would start by trying to fastboot flash the patched version of twrp. unless you can boot into twrp already then try to flash the asus package again thru twrp. also, could twrp see your internal sd before you bricked?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
No, that is the reason why I wiped everything (stupid move I know)...TWRP was screwed up to begin with. I flashed 2.5 JB version and it couldn't detect my internal SD card. I made sure it was the right model and everything so TWRP messed me up. I don't know how to flash a working version of TWRP since I don't know what version works with 4.2 tf300 firmware.
sonar2854 said:
No, that is the reason why I wiped everything (stupid move I know)...TWRP was screwed up to begin with. I flashed 2.5 JB version and it couldn't detect my internal SD card. I made sure it was the right model and everything so TWRP messed me up. I don't know how to flash a working version of TWRP since I don't know what version works with 4.2 tf300 firmware.
Click to expand...
Click to collapse
there is a modded 2.4.4 version i believe that sees all correctly. the post on how to root and update describe and link it. but being now you flashed the wrong one. you cant mount anything to flash correct one. i think you are s.o.l. i hope iam am wrong. good luck.
kaos420 said:
there is a modded 2.4.4 version i believe that sees all correctly. the post on how to root and update describe and link it. but being now you flashed the wrong one. you cant mount anything to flash correct one. i think you are s.o.l. i hope iam am wrong. good luck.
Click to expand...
Click to collapse
I'm not sure how to flash it...I tried fastboot flash recovery twrp.blob (2.4.4.0 v4.2). It just freezes although the cmd says it was successful
I keep getting a bootloader error (0x0000000) everytime I try and enter RCK, Android, Wipe Data... Is there a way to reinstall the bootloader? WW_epad 10.6.1.8
No mate
As of now there's no solution to that.
Do ppl ever read before they flash? I've never seen as much bricks as I've seen on this device since the new 10.6x.x Asus bootloader... it's a shame
Read read read, understand understand understand, then read more. I almost feel sorry for you guys who are "just flashing away"
FML :crying::crying:
sonar2854 said:
I keep getting a bootloader error (0x0000000) everytime I try and enter RCK, Android, Wipe Data... Is there a way to reinstall the bootloader? WW_epad 10.6.1.8
Click to expand...
Click to collapse
Bump!
I have a couple of questions.
I would like to know about your bootloader (how many icons and which ones) and whether you can still get into twrp.
tobdaryl said:
Bump!
I have a couple of questions.
I would like to know about your bootloader (how many icons and which ones) and whether you can still get into twrp.
Click to expand...
Click to collapse
Okay, so when I press Volume Down + Power, I enter the bootloader. The bootloader has three icons: RCK, Android Logo, Wipe Data. I have no access to TWRP since there is a unrecoverable bootloader error 0x0000000 when I try to enter RCK.
sonar2854 said:
Okay, so when I press Volume Down + Power, I enter the bootloader. The bootloader has three icons: RCK, Android Logo, Wipe Data. I have no access to TWRP since there is a unrecoverable bootloader error 0x0000000 when I try to enter RCK.
Click to expand...
Click to collapse
The odds are slim but let's try a couple of things.
From power off, hold power and volume down, release when you see the icons. You should see the entering fastboot message in the upper left.
fastboot -i 0x0B05 reboot bootloader
if that fails
Power off and use the same procedure.
fastboot reboot bootloader
Tell me the result.
tobdaryl said:
The odds are slim but let's try a couple of things.
From power off, hold power and volume down, release when you see the icons. You should see the entering fastboot message in the upper left.
fastboot -i 0x0B05 reboot bootloader
if that fails
Power off and use the same procedure.
fastboot reboot bootloader
Tell me the result.
Click to expand...
Click to collapse
Okay, I tried both and it doesn't work without adding a hyphen in between reboot and bootloader so reboot-bootloader. Otherwise, with the hyphen added, both work.
sonar2854 said:
Okay, I tried both and it doesn't work without adding a hyphen in between reboot and bootloader so reboot-bootloader. Otherwise, with the hyphen added, both work.
Click to expand...
Click to collapse
Sorry for that mistake. Now try rck and let's see if the bootloader is now accepted. If we are lucky the result has changed.
tobdaryl said:
Sorry for that mistake. Now try rck and let's see if the bootloader is now accepted. If we are lucky the result has changed.
Click to expand...
Click to collapse
Eh...I don't really know how to explain this but this is what happened. Once the bootloader rebooted after entering the CMD command, I pressed volume up to access RCK and there was a "blink" and there is now a green glowing square around the Android Icon. I cannot move the volume up or down (it is frozen on the Android Icon with the green square glowing), so I don't know what that "blink" was. If i try to press volume up now there is the bootloader error again.
sonar2854 said:
Eh...I don't really know how to explain this but this is what happened. Once the bootloader rebooted after entering the CMD command, I pressed volume up to access RCK and there was a "blink" and there is now a green glowing square around the Android Icon. I cannot move the volume up or down (it is frozen on the Android Icon with the green square glowing), so I don't know what that "blink" was. If i try to press volume up now there is the bootloader error again.
Click to expand...
Click to collapse
Download the 10.4.2.20 stock firmware. Unzip once and rename the resulting zip EP201_768_SDUPDATE.zip. Place this on your external sdcard and boot into your bootloader. Volume up on RCK.
tobdaryl said:
Download the 10.4.2.20 stock firmware. Unzip once and rename the resulting zip EP201_768_SDUPDATE.zip. Place this on your external sdcard and boot into your bootloader. Volume up on RCK.
Click to expand...
Click to collapse
Um, I don't have an external SD Card? The only SD Card I have is the Internal Storage
sonar2854 said:
Um, I don't have an external SD Card? The only SD Card I have is the Internal Storage
Click to expand...
Click to collapse
Uh!
Tell me what 2.5 JB version is.
Unzip 10.6.1.8 stock firmware twice and place the blob file into the directory with adb and fastboot. Boot into the bootloader and don't press anything.
fastboot -i 0x0B05 flash system blob
fastboot -i 0x0B05 reboot
if the command fails try again without -i 0x0B05
tobdaryl said:
Uh!
Tell me what 2.5 JB version is.
Unzip 10.6.1.8 stock firmware twice and place the blob file into the directory with adb and fastboot. Boot into the bootloader and don't press anything.
fastboot -i 0x0B05 flash system blob
fastboot -i 0x0B05 reboot
if the command fails try again without -i 0x0B05
Click to expand...
Click to collapse
When you say 2.5 JB version...are you talking about TWRP? I don't think TWRP is on the tablet because I can't access it. All I saw was a blink when I pressed volume up on RCK, not TWRP? I have tried flash system blob before I posted here and it did nothing. There is no progress bar when fastboot flashing =/ I think it froze. Yup it froze, just tried to do fastboot reboot-bootloader and it said failed. Also, after the system was done writing, after 2 seconds it said complete so it didn't work.
sonar2854 said:
When you say 2.5 JB version...are you talking about TWRP? I don't think TWRP is on the tablet because I can't access it. All I saw was a blink when I pressed volume up on RCK, not TWRP? I have tried flash system blob before I posted here and it did nothing.
Click to expand...
Click to collapse
I understood about twrp and flashing system blob but I thought we had been able to get stock recovery working instead of twrp.
I 'm sorry that is all I have with no sdcard and no adb.
tobdaryl said:
I understood about twrp and flashing system blob but I thought we had been able to get stock recovery working instead of twrp.
I 'm sorry that is all I have with no sdcard and no adb.
Click to expand...
Click to collapse
I have never used the stock recovery so what is it supposed to look like? Is it that dead Android with the battery because that didn't show up? I will try and get an external sd card tomorrow and try it if you think it might work. I have the 4.2 bootloader so are you sure that I should put Version V10.4.2.20 and recover using that version? Anyways, if it ends up not working, I would just like to say thank you very much for trying.
no access to recovery
I've got big problem. My One Mini is fine until I try to go into recovery. It refuses to go there.
I get fastboot and bootloader menus fine. It enters bootloader, but if I try to go into recovery, it just goes back to the main bootloader menu.
The problem started when I flashed CWMRecovery. Fastboot and adb recognise my phone, and accept commands, but when I try to fastboot flash recovery in it sends an error message. File not found.
I tried " fastboot boot recovery.img" but that just froze the machine .
When I try to get into recovery from rom manager or ROM toolbox pro, it takes me to the fastboot menu, not into recovery, and we're back to square one, as above.
Running android 4.3 Sense 5.5 software 2.12.401.1 Supercid 11111111
rooted and unlocked
To get the phone to work again, I have to hold power down for about 10 secs direct from fastboot/bootloader...may have to do this several times before it boots into Android.
If I turn power off from bootloader, it returns to bootloader when I power up again.
If I don't turn the phone off, once in main application, it's all OK.
Ho hum.
As I say , it works like a dream until I want to go into recovery.
Any ideas, please?
Thanks
Hi
Boblud said:
I tried " fastboot boot recovery.img" but that just froze the machine .
Click to expand...
Click to collapse
The correct command to flash the recovery is
Code:
fastboot flash recovery your_recovery_image.img
see also: wiki.cyanogenmod.org/w/Doc:_fastboot_intro
Booting into recovery should be possible with
Code:
adb reboot recovery
I didnt tried CWM on the Mini, but used it on my old Marvel. I'm satisfied with TWRP for the Mini.
greetings
Yes, thanks. I know the commands should work...but that's the trouble..they don't!
I can get into the recovery menu...HBOOT /FASTBOOT / RECOVERY and so on, but selecting "RECOVERY" simply sends me back to HBOOT menu.
I can't flash anything under FASTBOOT, either. I've been doing this sort of thing for several years without trouble....until now!
So come on chaps..thinking caps on , please.
Boblud said:
Yes, thanks. I know the commands should work...but that's the trouble..they don't!
I can get into the recovery menu...HBOOT /FASTBOOT / RECOVERY and so on, but selecting "RECOVERY" simply sends me back to HBOOT menu.
I can't flash anything under FASTBOOT, either. I've been doing this sort of thing for several years without trouble....until now!
So come on chaps..thinking caps on , please.
Click to expand...
Click to collapse
lock the bootloader RUU back to stock and start over ?
clsA said:
lock the bootloader RUU back to stock and start over ?
Click to expand...
Click to collapse
Thanks, will do when I can find ruu to download! Any pointers, please?
Uhm.... have u read Frequently Asked Questions by @KidCarter93 ?
KidCarter93 said:
[SIZE=+1]Q11: I have a custom recovery installed but I can't boot into it.[/SIZE]
Use the command - fastboot erase cache.
You should now be able to boot into recovery.
Click to expand...
Click to collapse
Maybe it helps.
Boblud said:
Thanks, will do when I can find ruu to download! Any pointers, please?
Click to expand...
Click to collapse
here's the RUU
http://www.androidruu.com/getdownlo...14_10.20.40.4408L_release_333483_signed_2.exe
clsA said:
here's the RUU
http://www.androidruu.com/getdownlo...14_10.20.40.4408L_release_333483_signed_2.exe
Click to expand...
Click to collapse
Thanks for help all round.
The RUU wouldn't run: it reported an unknown error, but having done so, it must have done something, as when I rebooted, I had access to recovery once again...briefly! Then it went again.
Anyway, I re locked / unlocked , locked a few times, and hey presto, it's sprung back into life!
I was trying to get the latest twrp '2.8.7.2'. I downloaded it and flashed the img to recovery and nothing seemed to happen so I tried flashing it to boot then I tried to reboot the system. Now when I try to turn it on I get stuck on the Google like it is turning but it just gets stuck. I tried Charging it now when I charge it I get stuck on the battery logo. When I try booting it Booting it into recovery(twrp) I get a black screen. I can tell the Screen is on because of the dim glow it gives off but it is not doing anything. Note: I am some what of a noob when it comes to this stuff, My nexus 5 was running Marshmallow, and I was running the Xtra smooth rom (it is very close to stock). Plz help. I have also just found out that the reason im getting the bootloop is I flashed the wrong version of TWRP need a fix PLZ HELP.
Did you try flashing stock recovery or twrp 2.8.7.1?
audit13 said:
Did you try flashing stock recovery or twrp 2.8.7.1?
Click to expand...
Click to collapse
I cant flash anything because it is stuck. If you can tell me how to do that it would be great. also I gave you the thanks thing.
Judah04 said:
I cant flash anything because it is stuck. If you can tell me how to do that it would be great. also I gave you the thanks thing.
Click to expand...
Click to collapse
All you have to do is boot into your bootloader (Power + Volume Up + Volume Down at the same time) and flash the stock recovery.
fastboot flash recovery recovery.img
Chances are you flashed an incorrect version of TWRP meant for another phone hence the boot loop.
asawoszc said:
All you have to do is boot into your bootloader (Power + Volume Up + Volume Down at the same time) and flash the stock recovery.
fastboot flash recovery recovery.img
Chances are you flashed an incorrect version of TWRP meant for another phone hence the boot loop.
Click to expand...
Click to collapse
When i boot into recovery mode the screen is on but it is black.
asawoszc said:
All you have to do is boot into your bootloader (Power + Volume Up + Volume Down at the same time) and flash the stock recovery.
fastboot flash recovery recovery.img
Chances are you flashed an incorrect version of TWRP meant for another phone hence the boot loop.
Click to expand...
Click to collapse
Also yes i do think I flashed the wrong TWRP. how do I flash the correct TWRP when I can't even get back into a tool to flash it?
Judah04 said:
When i boot into recovery mode the screen is on but it is black.
Click to expand...
Click to collapse
You dont need recovery, you need bootloader.
telep said:
You dont need recovery, you need bootloader.
Click to expand...
Click to collapse
Can you please explain to me exactly what to do. thank you. also my bootloader is unlocked. I also can get to fastboot so what is the diffrence between bootloader and fastboot.
Hold down the volume +, volume -, and power button. You'll be taken to a screen with the word START at the top. Now, connect the phone to your Windows computer using the USB cable, open a command prompt and type "fastboot flash recovery nameof twrpfile.img", press the enter key, use the volume button to select recovery, use the power button to enter recovery, press the power button, press volume + button, and you should enter TWRP.
Thank you but I do not own a windows computer
Then look up the respective commands. You flashed twrp over your kernel, you need to flash a proper boot.img (kernel) if you want the phone to boot. Fastboot is ran through bootloader. Flash the proper kernel in bootloader using fastboot.
wangdaning said:
Then look up the respective commands. You flashed twrp over your kernel, you need to flash a proper boot.img (kernel) if you want the phone to boot. Fastboot is ran through bootloader. Flash the proper kernel in bootloader using fastboot.
Click to expand...
Click to collapse
Thank you this sounds like it will work. But can you put it in more simple terms and give me links? plz. thx in advance.
Do you have access to a Windows computer to flash the commands? How did you flash TWRP?
audit13 said:
Do you have a computer?
Click to expand...
Click to collapse
I have a macbok air running mac os x 10.5.8.
audit13 said:
Do you have access to a Windows computer to flash the commands? How did you flash TWRP?
Click to expand...
Click to collapse
I flashed TWRP using the TWRP app it installed TWRP 2.8.7.1 I also unlocked the bootloader with a similar app.
This might help: http://forum.xda-developers.com/goo...olkit-root-twrp-recovery-unroot-11-6-t2515640
audit13 said:
This might help: http://forum.xda-developers.com/goo...olkit-root-twrp-recovery-unroot-11-6-t2515640
Click to expand...
Click to collapse
Just cheked it out I tried it and it didn't work but thx anyway. btw I am running android 6.0.
audit13 said:
This might help: http://forum.xda-developers.com/goo...olkit-root-twrp-recovery-unroot-11-6-t2515640
Click to expand...
Click to collapse
It might not have been working because I did not enable USB Debuging. :crying:
USB debugging is required for adb commands. With fastboot mode, debugging isn't necessary.
audit13 said:
USB debugging is required for adb commands. With fastboot mode, debugging isn't necessary.
Click to expand...
Click to collapse
Can you please walk me through this i am some what of a beginner when it comes to some of these things. I can try the tool kits agin but need help.