Hey guys,
recently I unlocked my bootloader without problems. Now I tried to install twrp 2.8.2.0 on my phone. I am full stock on 4.4.4.
I downloaded the file (http://techerrata.com/browse/twrp2/hammerhead) and I renamed it to recovery.img.
With the command "fastboot flash recovery recovery.img" I successfully flashed the new recovery. After that I chose "restart Bootloader" and after that I tried to select "Recovery mode".. Now the "teamwin" gets on my screen and suddenly my device boot up. I can't get into the recovery mode.
As I tried the second time, I tapped on the screen while "teamwin" stood there and suddenly my device vibrated like hell.
What I did wrong there guys? Was it a corrupt file or something?
Every answer would be very appreciated. =)
Oh damn, I think i got it now.
As it seems I am too stupid to inform myself before flashing the TWRP 2.8.2.0, which doesn't boot.
Sorry for this unecessary thread! I'll flash a previous version then! :3
2.8.1.0 works flawlessly. I still haven't been able to get 2.8.2.0 to work, I've given up trying.
Sent from my Nexus 5
It's a known bug with TWRP 2.8.2. For some reason it works for a handful people but I and others haven't been able to get it to work once, and I know I've tried everything you could possibly think of. Stick with 2.8.1 for now.
Related
Hey everyone,
I got a Nexus S that gets stuck on the Google logo when it starts up. I can get the phone into the bootloader and I can also clear the data from the phone but that hasn't fixed it. If you have any suggestions, please respond to the thread. Thank you!
I had this issue once for some reason... I had to take out the battery and put it back in, then boot into recovery and wipe the cache/davlik cache... Have you tried that yet??
brenix said:
I had this issue once for some reason... I had to take out the battery and put it back in, then boot into recovery and wipe the cache/davlik cache... Have you tried that yet??
Click to expand...
Click to collapse
Yah, i just did it and it didnt solve my problem but thanks for the suggestions
Sounds to me like you flashed an incompatible kernel. Have you recently flashed anything?
lostgoatX7 said:
Sounds to me like you flashed an incompatible kernel. Have you recently flashed anything?
Click to expand...
Click to collapse
No but the person I purchased it from might have. Does anyone know how to load stock android becuase I'm not experienced with rooting.
Looks like he bricked it, lucky for you, it's a Nexus. You have to find a stock Gingerbread ROM and flash it with ODIN or maybe through recovery. Look around for a stock ROM.
Sent from my Xoom
any solution?
hi guys.i have the same issue.does anyone have a solution for this?
i had the same problem.....what i did was cleared everything on recovery and flashed cyanogenmod and now is all good (this was of course after changing my underwear lol )
Smokexz said:
Looks like he bricked it, lucky for you, it's a Nexus. You have to find a stock Gingerbread ROM and flash it with ODIN or maybe through recovery. Look around for a stock ROM.
Sent from my Xoom
Click to expand...
Click to collapse
how can I do it?
I got the same problem.
Nexus S stuck at Google lOgo
I have the same Issue
Here is the Boot Loader Details.
Boot Loader version is : I9020XXKA3
baseband : I9020XXKB1
Locked sTate : LOCKEd
I have downloaded the stock nandroid , but not able to put it on the phone memory.
then tried to unlock the BOOT Loader in order to install Clock..Recovery , but there also after selecting Yes while Running Fastboot oem unlock , phone does not do anything.
then tried to load the file using ADB mode, but when i run adb devices , it doesnt show any device. or when i run adb remount it says "Error device not found"
Please help me get out of it.....
Similar problem
Ahoy!
I have a similar problem. Bought the phone in the States so I'm not in a position to go into psychological warfare with some poor high school kid working in Best Buy. Plus, all this is totally my fault...
I dropped my phone down the can (if it was a Blackberry I would have flushed) and manged to rescue it through handy desiccant (open shoe box gel packets) and rediscovering religion *cough* until this is sorted *cough*.
When I eventually fired her back up (the battery had flatlined btw) I'm stuck on the Google screen. So battle commenced...
The phone was stock 2.3.4, never rooted, no CW Recovery.
T-Mobile I9020T.
I sorted the Win 7 USB device issue
Can see it with fastboot but not adb.
Can access the bootloader screen so tried the Recovery option but it just goes into Google splash screen each time.
Flashed various versions of CW recovery (herring, mecha) to it but hitting the Recovery menu on the bootloader screen just keeps going to the Google splash screen.
This is where I complicated things because I'm a complete and utter noob to the rooting game.
I'm fairly sure I was careless early on with the appropriate versions of the full stock and singular recovery images I was trying to flash, so this might be useful information.
I downloaded ODIN and tried it briefly but it didn't seem to recognise my phone (I keep reading the ODIN needs to be tricked into recognising the phone). I also keep reading the ODIN is unnecessary if you have fastboot access so let this line of inquiry slide.
I downloaded a full Clockwork Mod Stock Nandroid (Stock-GRH78-Nandroid) and attempted to flash it all. The boot img failed due to a "FAILED exceed blocks" problem, so I tried this (classic noob try anything):
"Got a failure when trying to flash back a 8Mb boot.img?
From example above I started from a boot.img smaller than the full boot partition but if you create a new boot.img or start from an image of the full partition taken manually or with clockworkmod, boot.img will be 8Mb-large (8388608) and fastboot fails with "FAILED exceed blocks 0x00000020 > 0x0000001e".
I'm not really sure about what size the file should be but as it's filled with zeroes till reaching 8Mb, I decided to cut it:
0x00000020 => 0x0000001e means for me 8388608 / 0x20 * 0x1e = 7864320, so I did:
dd if=boot.img of=boot2.img bs=262144 count=30
fastboot flash boot boot2.img"
Click to expand...
Click to collapse
This worked! noob W1NNAR!!!11one111!!
I got the same thing with the recovery and the same "trick" worked. When it got around to the system img it eventually failed with a "Magic number" problem. Checking this problem out made me realise I can't keep messing around and should "get help".
As a further note I'm aware that the recovery can get flashed each time to stock after a reboot so I've been flashing CW Recovery and then trying to boot into Recovery straight away. Still getting stuck on the Google Splash screen.
I haven't found anyone with my problem that couldn't get sorted with CW so I'm either completely boned or missing something ridiculously easy. Been trying things for over a week - I'm getting close to selling her for scrap.
Have you turned S-Off?
-Remember, Android hell is a real place and you will be sent there at the first sign of defiance-
hand_of_henry said:
As a further note I'm aware that the recovery can get flashed each time to stock after a reboot so I've been flashing CW Recovery and then trying to boot into Recovery straight away. Still getting stuck on the Google Splash screen.
I haven't found anyone with my problem that couldn't get sorted with CW so I'm either completely boned or missing something ridiculously easy. Been trying things for over a week - I'm getting close to selling her for scrap.
Click to expand...
Click to collapse
Do "fastboot erase recovery" then flash a different ClockworkMod build. Try 3.0.2.4
Sent from my Nexus S using XDA App
Thanks Matt.
Just tried erasing (hadn't before) and flashing 3.0.2.4 - no dice. Tried erasing and 3.0.2.5 and no luck either.
twitch153 said:
Have you turned S-Off?
-Remember, Android hell is a real place and you will be sent there at the first sign of defiance-
Click to expand...
Click to collapse
Maybe I'm missing a blindingly obvious step.
My exact steps are:
Starting phone into bootloader screen (Volume + Up)
Erasing the recovery (as of Mike's post above)
Flashing the recovery (ensuring the recovery file is named "recovery.img")
On success of that selecting the Recovery menu item.
Each time I get Google Splash screen.
hand_of_henry said:
Maybe I'm missing a blindingly obvious step.
My exact steps are:
Starting phone into bootloader screen (Volume + Up)
Erasing the recovery (as of Mike's post above)
Flashing the recovery (ensuring the recovery file is named "recovery.img")
On success of that selecting the Recovery menu item.
Each time I get Google Splash screen.
Click to expand...
Click to collapse
Try to use fastboot to go into recovery directly instead of flashing recovery and choosing it from the bootloader menu.
"fastboot boot recovery.img" and see how this goes.
Edit: try this recovery as well
http://forum.xda-developers.com/showthread.php?t=988686
Sent from my Nexus S using XDA Premium App
How long do you wait on the splash screen? I recall this happening to me once but I thinkbi just let it sit and recovery eventually showed up after a while.
Sent from my Nexus S using XDA App
asafru said:
Try to use fastboot to go into recovery directly instead of flashing recovery and choosing it from the bootloader menu.
"fastboot boot recovery.img" and see how this goes.
Edit: try this recovery as well
http://forum.xda-developers.com/showthread.php?t=988686
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
Thanks asafru,
I tried booting into recovery but again, no luck. I did it with one of the recovery builds you suggested (the cyan recovery but having trawled that thread I'm not sure what the difference is between the colours).
matt2053 said:
How long do you wait on the splash screen? I recall this happening to me once but I thinkbi just let it sit and recovery eventually showed up after a while.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
That's a fair point - I had expected to see the recovery screen fairly sharpish.
I've waited 15 minutes now on the splash screen for flashings of cw 3.0.2.4, 3.0.2.5 and the mysterious cyan build of 4.0.0.2.
I imagine this is an appropriate amount of time for the recovery to kick in?
I've tried all these recoveries using the Recovery menu item and also using the booting directly recovery method that asafru suggests above.
I'm having issues getting recovery to work on a Verizon version xoom. I first flashed CWM version 4.0.0.4. The first time I tried to boot into it, it was stuck on the android with the red triangle for a long time before finally getting into it (coincidentally when I was hitting the volume key, don't know if that's related). Anyway, since then I haven't been able to get into it. It will be suck on the red triangle screen for a minute or two before rebooting into the stock rom (I'm running stock ICS). Since then, I've tried flashing the new TWRP 2.2.2 or whatever version it is and it has no effect. It's still doing the same thing. Any clue what's wrong?
So what I'm reading is suggesting that the android guy I'm seeing is the stock recovery. I'm not sure how that's happening. I'm installing the recovery using fastboot on my PC and being in the bootloader on my xoom. The prompts on both appear to confirm success.
I haven't tried this yet as I'm at work, but I think I've got the issue sorted. The following is what appears to be happening from what I've read.
1. I've still got the custom recovery stalled. When the Android guy pops up, one needs to press volume up to enter the options. Otherwise, it reboots.
2. The recovery flashes are taking because I'm booting back into the rom after a flash. The system's built in recovery protection is re-flashing the original recovery at that point.
3. To make my CWM/TWRP/whatever flash stick, I'll need to power down and then boot directly into the recovery.
I'll post again tonight to say if this works. Hopefully this thread can help out others who have the same issue.
If you don't get that to work fastboot img from link..
http://forum.xda-developers.com/showthread.php?t=1074979
fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img
Well, after trying to install a ROM through TWRP the phone rebooted and froze on the HTC screen. I then go back into bootloader and try to get into recovery but the splash screen pops up and then the phone reboots. I can get into CWM however when trying to sideload any .zips there I get an error. Not really sure what to do at this point. I probably should have stopped playing with it when I fixed it the first time, ha.
Edit: I fixed my problems! Very happy, ended up restoring some of the firmware from the OTA's and TWRP started working again. Just flashed ROM and fully functionally.
Tim3worx said:
Well, after trying to install a ROM through TWRP the phone rebooted and froze on the HTC screen. I then go back into bootloader and try to get into recovery but the splash screen pops up and then the phone reboots. I can get into CWM however when trying to sideload any .zips there I get an error. Not really sure what to do at this point. I probably should have stopped playing with it when I fixed it the first time, ha.
Edit: I fixed my problems! Very happy, ended up restoring some of the firmware from the OTA's and TWRP started working again. Just flashed ROM and fully functionally.
Click to expand...
Click to collapse
which ota did you flash? what network provider you on? im having same problems, did you flash ota in twrp?
tr1gg3r84 said:
which ota did you flash? what network provider you on? im having same problems, did you flash ota in twrp?
Click to expand...
Click to collapse
My provider is AT&T. I used the UK OTA from this link http://db.tt/LrIEemZ4 . Its part of this thread in general http://forum.xda-developers.com/showthread.php?t=2422885. Basically what was happening is that I had flashed a ROM which didn't work out and so it would just hang on the white HTC screen. I figured no big deal I'll just go into recovery and flash another one I know works. That didn't work out. Any time I tried to go into recovery the TWRP splash screen would pop up for a second then the phone would reboot. Which kind of had me puzzled because I flashed ClockWorkMod for recovery and it would at least get me into recovery but still adb sideload was giving me errors so I flashed TWRP again even though it wasn't working either.. I pulled the boot.img out of the Firmware.zip in the OTA and flashed that with fastboot. At that point I had tried just about everything and was about to give up but to my surprise that seemed to fix it. I was able to go into recovery no problem. Sideloaded the ROM and everything went great. I'll probably not be messing with my phone like that for a bit haha. It was the second night in a row that I had wiped an OS off the phone and struggled to figure out how to get it working. Glad its all good now though. Good luck to you!
cant change recovery / device rebooting
Hi, i have a similar problem,
I've unlocked with htcdev everything is fine.
Then I installed Twrp-2.6.0.0.img as recovary.
I'm not able to mount the internal storage, so I had to push the ROMs via ADB.
starting a ROM 1st time seems to be ok.
restart is also ok.
shutdown and power on is rebooting every ~15sec.
I tried to change my bootloader.
fastboot flash recovery recovery-clockwork-touch-6.0.3.6-m7ul.img -> volume keys are responding
fastboot boot recovery-clockwork-touch-6.0.3.6-m7ul.img -> volume keys are NOT responding
recovery isn't starting until i run following commands:
fastboot flash recovery Twrp-2.6.0.0.img -> volume keys are responding
fastboot boot Twrp-2.6.0.0.img -> volume keys are NOT responding
but after resetting the device + entering recovery it's there
thanks for your ideas/help
Today I wanted to flash a CM12 lollipop ROM
I unlocked the bootloader with succes, adb commands said that the recovery .img was flashed okay!,
So i got the following issue,
My oneplus one won't boot in to recovery, or is stuck at the Oneplus logo, or the 1+ logo just disappears and the screen goes crazy with green and blue lines... and i see weird things on screen. a normal boot and fastboot is fine everything is just ok, but not recovery,
I tried TWRP, PHILZ TOUCH,CWM, even to stock CM recovery doesn't flash anymore
i did many tutorials and followed step by step im sure thats not the problem.
I tried with the oneplus one toolbox and command window but nothing
Need help!
DaiMinzz said:
Today I wanted to flash a CM12 lollipop ROM
I unlocked the bootloader with succes, adb commands said that the recovery .img was flashed okay!,
So i got the following issue,
My oneplus one won't boot in to recovery, or is stuck at the Oneplus logo, or the 1+ logo just disappears and the screen goes crazy with green and blue lines... and i see weird things on screen. a normal boot and fastboot is fine everything is just ok, but not recovery,
I tried TWRP, PHILZ TOUCH,CWM, even to stock CM recovery doesn't flash anymore
i did many tutorials and followed step by step im sure thats not the problem.
I tried with the oneplus one toolbox and command window but nothing
Need help!
Click to expand...
Click to collapse
Hi, maybe your recovery images are corrupt. Had that once, thought I was going crazy. Redownload, compare md5 sums (I know it sucks...), perhaps use a different browser to download, then flash again. Good luck!
stevekind said:
Hi, maybe your recovery images are corrupt. Had that once, thought I was going crazy. Redownload, compare md5 sums (I know it sucks...), perhaps use a different browser to download, then flash again. Good luck!
Click to expand...
Click to collapse
Still the same problem didn't work
Im sure everthing on the pc went ok, but my Oneplus has recovery bug
OK, I know this is a problem that many before had and I've researched the subject thoroughly. But I've only found ways to recover your phone from the soft-brick (one of those fake rubber bricks used in movies:laugh status which was something I did by myself by flashing a stock recovery via odin.
Now my problem is a different one: I have updated my s6 to stock 6.0.1 and all went fine. I then rooted the phone by installing SpaceX kernel and went on to flash recovery via odin. That is when the problem occurred and I've not been able to solve it. I tried flashing also via flashify but with the same result, i.e. phone frozen at the samsung galaxy s6 screen with the damn "recovery is not ......".
What could I try? Anyone knows how to circumvent this issue?
Thanks for any help.
Luca
Just flash this TWRP http://www.mediafire.com/?16c1zxj8gdz3mj4 (AP in Odin with F. Reset Time and Auto Reboot checked), it will boot automatically to recovery,
You will have a working recovery, but it can't reboot or shutdown the phone.
For that, click to "Advanced", "Terminal", and when the keyboard shows up, just type "reboot" or "halt"(without the ") et click on "enter".
Reboot: reboots the phone (the phone will reboot in system)
Halt: shutdown the phone
DJPops said:
Just flash this TWRP http://www.mediafire.com/?16c1zxj8gdz3mj4 (AP in Odin with F. Reset Time and Auto Reboot checked), it will boot automatically to recovery,
You will have a working recovery, but it can't reboot or shutdown the phone.
For that, click to "Advanced", "Terminal", and when the keyboard shows up, just type "reboot" or "halt"(without the ") et click on "enter".
Reboot: reboots the phone (the phone will reboot in system)
Halt: shutdown the phone
Click to expand...
Click to collapse
Thanks: I will try that right away and report back here. Is the procedure of rebooting and shutting down the phone permanent or is it just the 1st boot (I sense it is a permanent thing, but I hope it isn't). If, later on I flash a custom rom and then re-flash the recovery, will this thing go away?
Why is this seandroid thing happening? Are you able to explain it to me?
It's not permanent
Just the first boot. "It erase a boot script that say to your device to boot into recovery" (small explanation, it's not exactly that).
This happen sometimes when you try to update the Su binary via the SuperSU app (it try to reboot the device into recovery, but sometimes it doesn't work and the device is "stuck" on the recovery)
This message shows up on every boot if you have a custom kernel, and if you boot on recovery, it will maybe shows up (depend of your recovery).
It was stucking on this screen because the recovery that you tried to flash is not compatible with marshmallow bootloader. The link in my first answer is a working marshmallow TWRP, for S6 (not S6 edge/+).
DJPops said:
Just flash this TWRP http://www.mediafire.com/?16c1zxj8gdz3mj4 (AP in Odin with F. Reset Time and Auto Reboot checked), it will boot automatically to recovery,
You will have a working recovery, but it can't reboot or shutdown the phone.
For that, click to "Advanced", "Terminal", and when the keyboard shows up, just type "reboot" or "halt"(without the ") et click on "enter".
Reboot: reboots the phone (the phone will reboot in system)
Halt: shutdown the phone
Click to expand...
Click to collapse
Woohoo! It worked! I have a custom recovery, although i have to reboot the phone with a crank
Thanks a lot. Now I'm gonna go on messing it up some more!
DJPops said:
It's not permanent
Just the first boot. "It erase a boot script that say to your device to boot into recovery" (small explanation, it's not exactly that).
This happen sometimes when you try to update the Su binary via the SuperSU app (it try to reboot the device into recovery, but sometimes it doesn't work and the device is "stuck" on the recovery)
This message shows up on every boot if you have a custom kernel, and if you boot on recovery, it will maybe shows up (depend of your recovery).
It was stucking on this screen because the recovery that you tried to flash is not compatible with marshmallow bootloader. The link in my first answer is a working marshmallow TWRP, for S6 (not S6 edge/+).
Click to expand...
Click to collapse
Alas, it seems that it is permanent! It doesn't reboot into anything (neither system nor recovery. Haven't tried download, but I assume it would be the same thing). Furthermore it gets stuck and needs to be rebooted by pressing voldown and power. then it turns on into recovery again. It is a small price to pay, so no worries, but I always like to understand why things happen!
Could I have done another mistake?
Out of interest what random recovery did you give him? lol
Try arter97s mod of twrp 3.0.0-0
http://arter97.com/browse/exynos7420/recovery/twrp/g920fi/
Seems to be the best working mod of latest twrp at the moment. No issues booting etc, just no USB otg support currently.
Sent from my SM-G920I using Tapatalk
self_slaughter said:
Out of interest what random recovery did you give him? lol
Try arter97s mod of twrp 3.0.0-0
http://arter97.com/browse/exynos7420/recovery/twrp/g920fi/
Seems to be the best working mod of latest twrp at the moment. No issues booting etc, just no USB otg support currently.
Sent from my SM-G920I using Tapatalk
Click to expand...
Click to collapse
Oh yes!! This one really works all the way, reboot and all. However, af as you know, is there any of the previous version of TWRP that "agrees" with M bootloader?
Thanks mate
Luca
ManhIT modded recovery not a random recovery you know :mrgreen:
Haha, I was just wondering since it was just a mediafire link saying flash this.
Glad that arters recovery worked a bit better for you.
Recovery's are a bit hit and miss at the moment. That's the best one I've found so far.
I still haven't even got marshmallow, still rocking the latest lollipop which suffers similar problems.
Sent from my SM-G920I using Tapatalk
Oh okay, I'm french and I found this link on a french forum...
I used this recovery on my 920F and apart the reboot, it's working perfectly !