Ok, so i've read up that your able to fastboot a new recovery, but i havnt been able to find a link with a stock recovery kernel.
Basically im not entirely sure if i infact DID unlock my bootloader tbh.
Bootloader (1.00 e) released by "WW_epad-10.4.4.20-20121026" A03
The story is i've bought it some while ago of course, and its been lieing around on the table for a few months.. Basically busy life and other ****. Yesterday i looked at it and was, oh right! Turn it on, and it bootloop on me, apparently common issue with a JB version. herpaderpa on android but fck that..
And when i use a update file on the sd card, i cant install that to update the stock firmware due to the dead droid with the triangle..
From what i can gather around, if i have fastboot option, then its unlocked ? Yes, no ?
If so, could anyone give a hint as to whut the duck i've missed when reading the big full guide thread on the infinity Im starting to become rather desperat. Never had this kind of behaviour with my android devices before, Sure a goofed usb driver for fastboot here and there.. But never a dead droid with triangle..
SOLUTION :
Follow this chaps guide http://forum.xda-developers.com/showthread.php?t=1755576
using his alternative method, and at step 2.
DO AS HE WRITES! Using upper case letters on the file your moving to the sd card, EP201_768_SDUPDATE.zip as such! It works!
My droid kept showing up dead, untill i changed to upper case letters... Then the darn thing came to life!
The dead android is the stock recovery telling you it could not apply an update. If you tap the power button you might even get an error message, but I am not sure if that works only after you activated the recovery using the bootloader menu.
If your device is unlocked, you can install an unofficial recovery or kernel, and it will display "The device is UnLocked" in the upper left corner when you turn it on. Caution: People have reported that locked devices still allow "fastboot erase", but not "fastboot flash".
_that said:
The dead android is the stock recovery telling you it could not apply an update. If you tap the power button you might even get an error message, but I am not sure if that works only after you activated the recovery using the bootloader menu.
If your device is unlocked, you can install an unofficial recovery or kernel, and it will display "The device is UnLocked" in the upper left corner when you turn it on. Caution: People have reported that locked devices still allow "fastboot erase", but not "fastboot flash".
Click to expand...
Click to collapse
In that case, how can i go about bringing my tablet out of this infernal boot thing? I've tried flashing the twrp kernel, but i dont see any change, when i sent the flash it dit get a blue bar on the bootloader indicated full. So i assumed it could send the loader..
Basically i just want to firmware upgrade with the latest stock firmware, But i tried dumping the file on an sd card, and then go into the bootloader But it did not recognize it and start an update. also i couldnt go into the RCK selection, due to the dead droid.
What exactly did you do, exactly which file(s) did you try to flash, and what exactly happened? And does "I couldn't go into the RCK selection" mean that you never see the bootloader menu, that it doesn't work, or that you don't know how to use it?
Ok, basically, when i start the pad, it never goes beyon the ASUS screen.
Im able to get into the bootloader, here i have 4 icons, RCK, Android, USB, Wipe Data.
When i select RCK it brings the dead droid after a droid thats working.
If i enter USB i can use fastboot. What i've tried here is to do the http://www.teamw.in/project Twrp recovery using http://forum.xda-developers.com/showthread.php?t=1833212 guide *** Custom Recovery Installation ***
However i dont think that it ever was sent to the tablet. Not sure.
I know how to move around in bootloader power + volume down = mennu, then tap the volume to switch between icons, and the other volume to select.
Power + other volume = AXP iirc in stead of bootlaoder.
Did not try to flash any files when the dead droid thing / bootloop started. I basically did an OTA update iirc to a newer version a good while ago. And then life became fcked for me for a periode so playing with the tablet wasnt really an option for enjoyment. It then drained of battery of course, and here now after having it charged up. i realise about this odd bootloop for one of the older droid software versions.
theorion said:
Basically im not entirely sure if i infact DID unlock my bootloader tbh.
Click to expand...
Click to collapse
_that said:
If your device is unlocked, you can install an unofficial recovery or kernel, and it will display "The device is UnLocked" in the upper left corner when you turn it on.
Click to expand...
Click to collapse
Do you already know if your device is unlocked?
_that said:
Do you already know if your device is unlocked?
Click to expand...
Click to collapse
No, it does not say unlocked any where
theorion said:
No, it does not say unlocked any where
Click to expand...
Click to collapse
OK, that explains why installing TWRP didn't work.
Now if you would describe in detail what you did to install the latest firmware, maybe someone could tell you why that didn't work.
Did you unzip the downloaded firmware update once (the result being another zip file)?
The unzipped zip is what you have to put on your sd card. Then the recovery should recognize it when you boot.
If that does not work, try to rename the unzipped zip: EP201_768_SDUPDATE.zip
and put that file into the root of you sd card.
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
1. Downloaded ASUS Transformer Pad TF700T Firmware: V10.6.1.14.8 Only for WW SKU (Android 4.2.1) from the TF700F download page selecting android as os.
2. Have a 2gb microsd, i formated as fat 32, using all standard alocation and stuff with windows' own formatting tool.
3. I unzipped the downloaded ZIP file so i have a WW_epad-user-10.6.1.14.8.zip that now contains a meta-inf folder, and a blob file.
4. renamed the zip file to ep201_768_sdupdate.zip, however i did use lowercase... Could that be the issue ? Basically i presumed that the uppercase was only to make people aware of a change.
5. boot the device using the power + volume, and enter recovery mode.
6. Dead droid..
Update as i was writing this, i thought, though it wasn't said specificly, i renamed the EP201_768_SDUPDATE to uppercase, and decided to give that a go.. Now the droid is working its ass off...
F**** i feel like a complete bloddy retard! Gawd i hope it works now then...
And its alive... OMG! If only i had renamed the darn file to uppercase, i would have fixed it using the guides... 2 days ago, before i even resorted to open a post.. Thanks guys! Though i realised my own damn fault, your desire to aid regardless are bloddy brilliant!
theorion said:
And its alive... OMG! If only i had renamed the darn file to uppercase, i would have fixed it using the guides... 2 days ago, before i even resorted to open a post.. Thanks guys! Though i realised my own damn fault, your desire to aid regardless are bloddy brilliant!
Click to expand...
Click to collapse
Oh yeah, Linux is case sensitive alright. Get the case wrong and it has no idea what you talkin' bout Willis.
Hi,
This is my first post on this forum and I might sound like a total dummy (cos I am when it comes to rooting/flashing android devices).
My Nexus 4 was suffering from poor battery performance and to correct that I thought of trying my hands at rooting it and flashing it with a custom ROM. However, being a noob, little did I realize what I was getting myself in to.
Now, after unlocking the boot loader, when I tried to boot my device from recovery mode, it just wouldn't fire up, but kept showing the rotating dots of lollipop boot screen.
After a lot of fiddling, I managed to mess up even further as now, the rotating dots are also not appearing and I just get Google logo twice and after that the device's screen just keeps blinking with a faded background light on the screen.
I used Nexus4Root to root the device and have ADB installed on my Mac OS X machine.
Is there anything I can do to bring my Nexus 4 back to life?
Any help is appreciated.
Thanks.
ajxkid said:
Seems like unlocking your Boot loader have not been successful , Toolkits are not always dependable. I think you should unlock ur Boot loader manually with adb and fastboot .
You could find guides for that all over the web. Go on and try that..
Good luck
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for the response. I think I did manage to unlock the Boot loader, as I can see that in the status when I switch ON the phone in 'recovery mode'. The problem is that I am not able to boot the phone through recovery mode. As I said, it goes in a sort of boot loop. It does not boot from normal mode, same thing happens (boot loop).
Is it possible to flash the factory image in the current state of device? The device is not detected by my Mac when I try to fastboot it.
Any guides/threads I can look at with similar information? Have been looking up quite a lot online, but to no avail.
Thanks again!
According to other XDA entires I've read, the unlocked bootloader warning can not be disabled. However, I was browsing through my phone, and I came across the location for regular boot animations. How come the main boot animation is stored on the system but the warning is on the bootloader? Also, there were some text files (in screenshots) in there. They didn't seem to specify anything about an unlocked bootloader warning, but idk. I'm just really confused as to why Sony would store part of their boot animation on one partition and part on another. Any ideas? Thanks so much. (btw i know this might sound weird - im not insanely advanced, just curious)
idk how to delete threads lol, but here are the attachments. also u can kinda guess but the last word in the title is bootloader
Normal bootanimation is placed in /system because it's not so important.
If your device has corrupted system, the device can't show unlocked bootloader warning when you boot it.
The boot sequence of Android is like this: Bootloader -> Kernel -> System
Hi guys,
EDIT: Seems like i should have searched better before posting this. Just found https://forum.xda-developers.com/pixel-2/help/brick-t3897949. I'll come back if i dont find anythign there...
EDIT 2: https://forum.xda-developers.com/showpost.php?p=79137071 was the solution. Just keep pressing the power button (even if the device keeps trying to boot up) in fastboot. After like 20 times it tried to boot-up, i checked 'fastboot devices' and it actualy appeared. Then i was able to './flash-all.sh' the factory image!
i bought a Pixel 2 some days ago to get into AOSP development. I built a fresh AOSP using the "official" guide (No extras, vendor blobs from Google directly, ...).
After flashing system/vendor/boot it failed to boot. No big deal - just flash a factory image again - or not ... no devices available in fastboot. And it gets worse: It won't even show up in lsusb.
Sooooo, i think i bricked my brand-new Pixel 2. I can start in fastboot-mode (Actually it starts in fastboot-mode even when i'm plugging it in to charge), and it shows an error "ERROR: Slot Unbootable: Load Error".
- Fastboot starts but the device does not provide a USB-Interface
- Fastboot shows "ERROR: Slot Unbootable: Load Error"
- Unable to load the battery
- Recovery/Download-Mode not starting aswell
Is there anything i can do about this besides throwing it away? :crying: Any hints are appreciated.
Br,
Thomas
opthomas-prime said:
fastboot devices' and it appeared. Then i was able to './flash-all.sh' the factory image!
Click to expand...
Click to collapse
In "Device State: Locked" it wouldn't be possible to flash anything, right?
opthomas-prime said:
Just keep pressing the power button (even if the device keeps trying to boot up) in fastboot. After like 20 times it tried to boot-up, i checked 'fastboot devices' and it actualy appeared. Then i was able to './flash-all.sh' the factory image!
Click to expand...
Click to collapse
It worked! :angel: Thank you very much!
Thank you so much!!!!
SGH-i200 said:
In "Device State: Locked" it wouldn't be possible to flash anything, right?
Click to expand...
Click to collapse
Yes thats a good question are these phones bootloader locked that having been semi bricked and then used the power button to get it into fastboot that allows flashing? Ive seen this question asked and no one has said yes or no.
tmachovec said:
Yes thats a good question are these phones bootloader locked that having been semi bricked and then used the power button to get it into fastboot that allows flashing? Ive seen this question asked and no one has said yes or no.
Click to expand...
Click to collapse
SAME HERE! Someone must be able to answer yes or no right?
I've had the same thing with my walleye but it's bootloader unlocked so was able to flash a full factory image to restore it. If on a locked bootloader but you'd only be able to flash/sideload a full factory OTA image to try and rescue it (which I've no experience of trying)
Hey there, I was wondering if I can get rid of the Your device is unlocked and can’t be trusted screen, since it’s pretty annoying. I don’t want to lock my bootloader again, since I have root and such, I just want to get rid of the screen. It can even just be a black screen for 5 seconds. Thanks
Edit: Thank you @WoKoschekk for helping me! It now has the original bootscreen.
Flash the attached and unpacked logo_custom.bin:
fastboot flash logo logo_custom.bin
The warning screen is replaced by the normal boot logo. Here you can download the tool I used: https://forum.xda-developers.com/t/...ker-source-code-included-version-2-4.2848667/
WoKoschekk said:
Flash the attached and unpacked logo_custom.bin:
fastboot flash logo logo_custom.bin
The warning screen is replaced by the normal boot logo. Here you can download the tool I used: https://forum.xda-developers.com/t/...ker-source-code-included-version-2-4.2848667/
Click to expand...
Click to collapse
Alright, I'll try it out.
Thanks
WoKoschekk said:
Flash the attached and unpacked logo_custom.bin:
fastboot flash logo logo_custom.bin
The warning screen is replaced by the normal boot logo. Here you can download the tool I used: https://forum.xda-developers.com/t/...ker-source-code-included-version-2-4.2848667/
Click to expand...
Click to collapse
I have tried, and it works!! Thank you!!
I followed the instructions in this thread: https://forum.xda-developers.com/t/...of-root-warning-screens-hide-bad-key.3967463/ and used the Blue logo there.
It's not a perfect match though, I can see the blue color change slightly when it advances to the real blue logo. I also don't have "bad key", so I see a bunch of hex numbers on the screen along with the blue logo.